diff --git a/marked/M/T-REC-M.100-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.100-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e76af27d793f9718816883d72f4751ad572de95f --- /dev/null +++ b/marked/M/T-REC-M.100-198811-I_PDF-E/raw.md @@ -0,0 +1,164 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.100** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTRODUCTION AND GENERAL PRINCIPLES** + +--- + +**SERVICE CIRCUITS** + +**ITU-T Recommendation M.100** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.100 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +© ITU 1988, 1993 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# **SERVICE CIRCUITS** + +To facilitate the general maintenance of the international telephone network, *service circuits* should be set up as may be necessary between relevant maintenance units taking part in the international service. + +For the purposes of this Recommendation, a distinction is made between the following types of service circuit: + +- **Direct service circuit**: a telephone or teleprinter (teletypewriter) service circuit serving only two stations and linking them directly. + +*Note* – It will also be necessary to consider the communications required by technical staff for setting up and maintaining very long circuits routed over a number of major systems in tandem, e.g. London-Singapore circuits. These may require service circuits to be interconnected. + +- **Omnibus service circuit** (see Figure 1/M.100 below): a telephone or teleprinter (teletypewriter) service circuit serving more than two stations connected in series, any or all of which may make connection to the service circuit simultaneously. +- **Multiterminal service circuit** (see Figure 2/M.100 below): a telephone or teleprinter (teletypewriter) service circuit serving more than two stations and having at least one branching point. On each *branch* of this circuit a certain number of stations can be connected in series. Every station served can enter the circuit individually. + +*Note* – Attention is drawn to the possible use of selective signalling on omnibus and multiterminal service circuits and to the problems that may arise in achieving the necessary stability on such circuits. + +It is recommended that for the maintenance of international circuits: + +- 1) all attended stations should be connected direct to the public telephone network; +- 2) the terminal stations of an international system should be provided with a direct telephone service circuit; +- 3) terminal and intermediate stations on an international system should be provided with an omnibus telephone service circuit; +- 4) where the provision of direct teleprinter (teletypewriter) service circuits is impracticable or uneconomical, important repeater stations on international routes should be provided with international telex facilities; + +The equipment of the telegraph local end used on service telegraph circuits must be capable of transmitting and receiving signals conforming to International Telegraph Alphabet No. 2 and must be in accordance with the provisions of CCITT Recommendations; + +- 5) maintenance staff responsible for international circuits should have authority to make priority calls in the international telephone service [1]; + +![Diagram of an omnibus service circuit showing send and receive paths between terminal and intermediate stations.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +The diagram illustrates an omnibus service circuit with two parallel transmission paths. The top path represents the 'send' direction, starting from a terminal station 'A' (marked with 'T' and an arrow pointing right) and passing through intermediate stations 'C', 'D', and 'E' (each marked with 'T' and an arrow pointing right). It ends at terminal station 'B' (marked with 'T'). The bottom path represents the 'receive' direction, starting from terminal station 'B' and passing through the same intermediate stations 'E', 'D', and 'C' (each marked with 'R' and an arrow pointing left) back to terminal station 'A' (marked with 'R'). A box containing the letter 'I' (representing an attenuator) is connected between the two paths at station 'B'. + +CCITT - 36501 +d01-sc + +T ○ → send + +R ○ → receive + +**A B** terminal international centres or terminal repeater stations + +**C D E** intermediate international centres or intermediate repeater stations + +**[I]** attenuator looping the two directions of transmission + +Diagram of an omnibus service circuit showing send and receive paths between terminal and intermediate stations. + +FIGURE 1/M.100 +Example of an omnibus service circuit + +![Diagram of a multiterminal service circuit showing a main line with stations A, G, E, H, F, J, B. Branching stations C, I, K, D are connected to the main line. Arrows indicate 'send' (T) and 'receive' (R) directions. Squares with 'I' represent attenuators.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +The diagram illustrates a multiterminal service circuit. A horizontal main line connects terminal international centres or terminal repeater stations A, G, E, H, F, J, and B. Station A is on the left, and station B is on the right. Intermediate international centres or intermediate repeater stations G, H, and J are located along this main line. Branching off the main line are two sets of stations: one set consisting of C, I, and D, and another consisting of K and D. Station C is connected to station I, which is connected to station D. Station K is also connected to station D. Each station is represented by a rectangle. Squares containing the letter 'I' represent attenuators that loop the two directions of transmission. Arrows indicate the direction of transmission: 'T' for send and 'R' for receive. The diagram shows how these service circuits are interconnected between various points in the network. + +Diagram of a multiterminal service circuit showing a main line with stations A, G, E, H, F, J, B. Branching stations C, I, K, D are connected to the main line. Arrows indicate 'send' (T) and 'receive' (R) directions. Squares with 'I' represent attenuators. + +CCITT - 36511 + +d02-sc + +T ○ → send + +R ○ → receive + +A B C D terminal international centres or terminal repeater stations + +E F international centres (or repeater stations) with branching facilities + +G H I J K intermediate international centres or intermediate repeater stations + +I attenuator looping the two directions of transmission + +FIGURE 2/M.100 + +## **Multiterminal service circuit** + +- 6) all service circuits should in general conform to the Recommendations of the CCITT in respect of their quality and maintenance. However, service circuits may have a restricted quality which must nevertheless be such as to provide efficient communication when maintenance personnel have to use languages other than their mother tongue; +- 7) in the event of a major interruption involving service circuits, these should be accorded priority in restoration; +- 8) the terminal stations of a long international submarine cable system should be provided with a direct teleprinter (teletypewriter) service circuit; +- 9) terminal and intermediate stations on a long international submarine cable system should be provided with an omnibus teleprinter (teletypewriter) service circuit. + +The CCIR has issued Recommendation 400-2 concerning service circuits for radio-relay links. (For the convenience of readers, this Recommendation is reproduced below. CCIR Report 444 [2] also applies.) + +# **SERVICE CHANNELS TO BE PROVIDED FOR THE OPERATION AND MAINTENANCE OF RADIO-RELAY SYSTEMS** + +(Question 4/9, Geneva, 1982) + +(1956 – 1959 – 1963 – 1966 – 1970) + +The CCIR, + +# CONSIDERING + +- a)* that service channels are required for the maintenance, supervision and control of radio-relay systems; +- b)* that if, for any reason, the radio-relay system itself fails to function, communication between various stations along the route, and from those stations to other points is likely to assume special importance; +- c)* that agreement is desirable on the number and function of the service channels to facilitate the planning of radio-relay systems; +- d)* that service channels will be used to provide: + - omnibus voice circuits, + - express voice circuits, + - supervisory circuits, + - control and operational circuits; +- e)* that service channels will not be connected to the public telephone network, + +# UNANIMOUSLY RECOMMENDS + +that, on international radio-relay systems: + +1. all staffed stations should be connected directly to the public telephone network; +2. when a radio-relay link is extended by means of short cable sections, and these cable sections and the radio-relay link taken together constitute a regulated line section, the terminal stations of the radio-relay link itself should have speaker circuits to the stations at the ends of the regulated line section; +3. a telephone service channel (omnibus voice circuit) should be set up to connect together all the stations on the system, whether staffed or not; +4. a second telephone service channel (express voice circuit) should be provided for direct telephonic communication between the staffed stations receiving supervisory signals; +5. provisions for the transmission of supervisory and control signals should be subject to agreement between the Administrations concerned; +6. the telephone service channels should possess, whenever possible, the characteristics (excluding noise power) recommended by the CCITT for international telephone circuits and, in particular, should be able to transmit the frequency band 300 to 3400 Hz; +7. all telephone service channels (including those used for supervisory and control circuits) up to a length of 280 km should, whenever possible, not exceed a mean noise power in any hour of 20 000 pW0p psophometrically weighted, at a point of zero relative level. + +*Note* – Service channels may be provided over an auxiliary radio-relay system, over the main radio-relay system, or by other unrelated means, either on a primary or stand-by basis. In the case of express voice circuits, the use of regular multiplex channels within the telephony baseband is acceptable, where this is possible. + +# **References** + +- [1] CCITT, *Instructions for the International Telephone Service*, Articles 46 to 49, ITU, Geneva, 1985. +- [2] CCIR Report *Service channels for analogue radio-relay systems*, Vol. IX, Report 444, ITU, Geneva, 1986. + +--- + +\* This Recommendation applies to radio-relay systems which will transmit at least 60 telephone channels or a television signal and comprise two staffed terminal stations, in which the signals are demodulated to baseband, and any number of unstaffed intermediate stations, This Recommendation applies, where appropriate, to trans-horizon radio-relay systems. \ No newline at end of file diff --git a/marked/M/T-REC-M.1012-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1012-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422f8e241d2880c8e68e3e94b869d6a0f9427bdf --- /dev/null +++ b/marked/M/T-REC-M.1012-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d63d12739a0bfa782391eb486074787d3c8a61e302171c075c34cc9ff870280 +size 7517 diff --git a/marked/M/T-REC-M.1012-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.1012-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..953b836d1ef83ab2659791730b97b38aa8ad7611 --- /dev/null +++ b/marked/M/T-REC-M.1012-198811-I_PDF-E/raw.md @@ -0,0 +1,106 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1012** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL LEASED CIRCUITS** + +--- + +**CIRCUIT CONTROL STATION FOR +LEASED AND SPECIAL CIRCUITS** + +**ITU-T Recommendation M.1012** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.1012 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **CIRCUIT CONTROL STATION FOR LEASED AND SPECIAL CIRCUITS** + +### **1 Definition of circuit control station** + +The circuit control station is that point within the general maintenance organization which fulfils the control responsibilities for leased and special circuits, for example circuits used for voice-frequency telegraphy, facsimile and phototelegraphy. + +### **2 Responsibilities** + +The circuit control station is responsible for ensuring that the circuit assigned to it is set up and maintained to the required end-to-end standards in both directions of transmission and that, if the circuit fails, the outage time is kept to a minimum. The circuit control station carries out this responsibility by directing, and/or coordinating other stations as necessary to ensure that satisfactory service is provided for which it has been assigned control. + +### **3 Functions** + +3.1 Arranging for the setting up of the circuit and of the signalling equipment associated directly with the circuit and the related adjustments. + +3.2 Controlling transmission measurements for the setting up and lining up of international circuits to within the recommended limits and keeping records of reference measurements (initial measurements). + +3.3 Receiving fault reports from the: + +- circuit user or his representative, either directly or via nominated fault report points; +- staff at the maintenance entities; +- transmission maintenance point (international line) (TMP-IL) (see Recommendation M.1014); +- sub-control station either directly or via the TMP-II. + +When the circuit control station receives a fault report from the circuit sub-control station a unique reference number should be issued and given to the sub-control station. (If national practices already involve the issue of a unique reference number this may be used.)1) The reference number is recorded with the fault report by both the circuit control and sub-control stations. + +3.4 Controlling routine maintenance measurements and tests on the due dates if scheduled, using the specified methods and in such a way that interruptions to service are limited to the shortest possible durations. + +3.5 Obtaining cooperation from the circuit sub-control station, either directly or via the TMP-IL. + +3.6 Directing the location of faults to the national line or the terminal national section in its own country, or beyond the national line to the international line, or to a foreign country. + +3.7 Controlling the withdrawal of circuits from service. + +3.8 Controlling the return of circuits to service, for example, after fault clearance, routine measurements, etc. + +3.9 Arranging for withdrawal of circuits from service with the customer. + +3.10 Keeping records of the routing of the leased and special circuits. + +3.11 Knowing the possibilities of rerouting any circuit under its control. + +--- + +1) Where no such unique reference number exists, Administrations may wish to consider a format containing the following elements: serial number/day of month/time (e.g. 47/03/1400G). + +3.12 Advising the customer (or ensuring that this be done) of the progress of fault clearance if appropriate, for example in the case of lengthy outages, and ensuring that the customer is advised when the fault has been corrected. + +3.13 Keeping accurate records of circuit outages. The information recorded should be agreed with the circuit sub-control station and should include: + +- the reference number mentioned in § 3.3; +- the circuit outage time; +- the location of the fault that is, in a national or international circuit section or in the renter's equipment; +- the general nature of the fault. + +### **4 Appointment of control stations** + +For each international leased or special circuit, a circuit control station is nominated by common agreement between the technical services of the Administrations concerned. For making the choice, special consideration will be given to the location of the principal user and the length of the circuit within the territory of each terminal country. + +For unidirectional constituted circuits the circuit control station should be located in the receiving country. + +The circuit control station may be located at or near the terminal repeater station serving the user or at the terminal international centre which defines the terminal of the international line in the control country. + +The considerations involved in locating the circuit control station in a given country include the following: + +- availability of staff; +- availability of adequate staff expertise; +- availability of communication with user and other pertinent locations; +- ability to fulfil the functions indicated in this Recommendation. \ No newline at end of file diff --git a/marked/M/T-REC-M.1013-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1013-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422f8e241d2880c8e68e3e94b869d6a0f9427bdf --- /dev/null +++ b/marked/M/T-REC-M.1013-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d63d12739a0bfa782391eb486074787d3c8a61e302171c075c34cc9ff870280 +size 7517 diff --git a/marked/M/T-REC-M.1014-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1014-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..422f8e241d2880c8e68e3e94b869d6a0f9427bdf --- /dev/null +++ b/marked/M/T-REC-M.1014-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d63d12739a0bfa782391eb486074787d3c8a61e302171c075c34cc9ff870280 +size 7517 diff --git a/marked/M/T-REC-M.1015-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1015-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a9c685895b23e79cadf62213b44226e93e5207a --- /dev/null +++ b/marked/M/T-REC-M.1015-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a4d6f1181fb021d7aea56d330d7892711e59dcf176b2c7c3c477e468224fe18 +size 7449 diff --git a/marked/M/T-REC-M.1015-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg b/marked/M/T-REC-M.1015-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fc85ab2566fa720df670c4e819cb906e3d73cc8 --- /dev/null +++ b/marked/M/T-REC-M.1015-198811-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:343569517e32ff59a889be681141ba4a4ad08900d8a6daa99cc356c0df7070d3 +size 52066 diff --git a/marked/M/T-REC-M.1015-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/M/T-REC-M.1015-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdcec069892228a0f4ea65fe8e528b8abddf72f0 --- /dev/null +++ b/marked/M/T-REC-M.1015-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae946a8fafcaac7dee2eba3081230157f62894c133d0396a50a815743c510828 +size 75074 diff --git a/marked/M/T-REC-M.1015-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/M/T-REC-M.1015-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24fb2f95ab6f38dcff9b7a2c6a57075fdbd85565 --- /dev/null +++ b/marked/M/T-REC-M.1015-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dca6da311dc12d8aedc444b0cbebbb19a8fe59958ff5a352f34aeba8b71a952 +size 65146 diff --git a/marked/M/T-REC-M.1020-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1020-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54ac6935348f4d093baeca909f60cf15694b98c6 --- /dev/null +++ b/marked/M/T-REC-M.1020-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53de04d1b6e6386f9f66899e3168367fe4d4d83b3baf95725a521b1c577b7949 +size 8220 diff --git a/marked/M/T-REC-M.1020-199303-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg b/marked/M/T-REC-M.1020-199303-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..199af4ae966e794c04af855a28de37deea290ee3 --- /dev/null +++ b/marked/M/T-REC-M.1020-199303-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c60a3fa8225df99bdf11cd775ac7b0edcba6da265405cfba1c09115cd0b61064 +size 54493 diff --git a/marked/M/T-REC-M.1020-199303-I_PDF-E/68aa26525c9346e4590a15c75d394e9d_img.jpg b/marked/M/T-REC-M.1020-199303-I_PDF-E/68aa26525c9346e4590a15c75d394e9d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10c41698607f3096596fd2acabb442b87122b5d7 --- /dev/null +++ b/marked/M/T-REC-M.1020-199303-I_PDF-E/68aa26525c9346e4590a15c75d394e9d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:653c1635e443c0d1ce85d125b130a88b6922e33532eaa7a9386f8a5310b2cb44 +size 53578 diff --git a/marked/M/T-REC-M.1020-199303-I_PDF-E/ac99eff233b8fe51d30f499e7413c345_img.jpg b/marked/M/T-REC-M.1020-199303-I_PDF-E/ac99eff233b8fe51d30f499e7413c345_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f010b830188ac01e8d65aa23d17918adf898b065 --- /dev/null +++ b/marked/M/T-REC-M.1020-199303-I_PDF-E/ac99eff233b8fe51d30f499e7413c345_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa9f5b9c7c848d28a5a581861eab61d29d563a06b57be75837287544551ee8b1 +size 38256 diff --git a/marked/M/T-REC-M.1025-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1025-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1eb09ac35cbf2d0afdf3133e07b0ce3887d9d96 --- /dev/null +++ b/marked/M/T-REC-M.1025-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7d1dd18f15d76aef5352dc4751bd38221833ecb4e4b8170135b7598d5ad03b3 +size 8207 diff --git a/marked/M/T-REC-M.1025-199303-I_PDF-E/4086a572c080354982c11f1de4d6921d_img.jpg b/marked/M/T-REC-M.1025-199303-I_PDF-E/4086a572c080354982c11f1de4d6921d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c197f7494f8d857dc117c8bbdc970f833959a0d8 --- /dev/null +++ b/marked/M/T-REC-M.1025-199303-I_PDF-E/4086a572c080354982c11f1de4d6921d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02177017f6c079be68fde856bf7a592bfa87c500f20ee31ea1ba10bce52a0cdf +size 32159 diff --git a/marked/M/T-REC-M.1025-199303-I_PDF-E/55d2bfe1c3d04e86df8d7a104d802172_img.jpg b/marked/M/T-REC-M.1025-199303-I_PDF-E/55d2bfe1c3d04e86df8d7a104d802172_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..963f141c3d75ab6924b55e51e8de32d02cec3dfd --- /dev/null +++ b/marked/M/T-REC-M.1025-199303-I_PDF-E/55d2bfe1c3d04e86df8d7a104d802172_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da1c0b95918101d6d265952865bf664e4d4591ff6ad0ac598b74937c2d491dcb +size 52224 diff --git a/marked/M/T-REC-M.1025-199303-I_PDF-E/925f55ce69802b9d3b00546382663ee2_img.jpg b/marked/M/T-REC-M.1025-199303-I_PDF-E/925f55ce69802b9d3b00546382663ee2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8946e9c13e4cfe292d3b342bcf37ad978cd9f03 --- /dev/null +++ b/marked/M/T-REC-M.1025-199303-I_PDF-E/925f55ce69802b9d3b00546382663ee2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6669b05c5743b52f469b860fc1ac7fe59c4fa4b5ef331a77f76dae888f97b85 +size 51362 diff --git a/marked/M/T-REC-M.1030-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.1030-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4bdb93302f7b322adc5e5424100a989e867d8190 --- /dev/null +++ b/marked/M/T-REC-M.1030-198811-I_PDF-E/raw.md @@ -0,0 +1,160 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1030** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL LEASED CIRCUITS** + +--- + +**CHARACTERISTICS OF ORDINARY +QUALITY INTERNATIONAL LEASED +CIRCUITS FORMING PART OF +PRIVATE SWITCHED TELEPHONE +NETWORKS** + +**ITU-T Recommendation M.1030** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.1030 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **CHARACTERISTICS OF ORDINARY QUALITY INTERNATIONAL LEASED CIRCUITS FORMING PART OF PRIVATE SWITCHED TELEPHONE NETWORKS** + +## **1 General** + +### **1.1 Scope** + +This Recommendation details the characteristics of an international leased circuit intended to form part of a private switched telephone network. The requirements of this Recommendation are intended to ensure the provision of a circuit suitable for telephony purposes. Such circuits may be used either singly, and thus provide for speech communication between two private telephone exchanges in different countries, or as part of a connection within a private switched telephone network covering two or more countries. + +It should be noted that not all Administrations provide circuits of the type covered by this Recommendation. + +Recommendation G.171 [1] contains the transmission planning considerations upon which the characteristics given in § 2 below are based, and specifies the maximum number of circuits in tandem which the transmission plan permits1). + +### **1.2 Terminology** + +#### **1.2.1 Circuit access points** + +The term “circuit access points” is used in this Recommendation with the same meaning as that given in Recommendation M.565 [2]. The precise location of, and relative levels at, the circuit access points are determined by the involved Administrations in collaboration with the renter concerned. + +#### **1.2.2 Four-wire circuits** + +This term is intended to cover circuits which are switched on a 4-wire basis, are available via 4-wire circuit access points, and do not contain 2-wire circuit sections. + +#### **1.2.3 Two-wire presented circuits** + +This term is used to cover circuits which do not meet the criteria set out in § 1.2.2 above, for example, circuits between exchanges using 2-wire switching. + +## **2 Characteristics** + +### **2.1 Nominal overall loss** + +It is not possible to specify the nominal overall loss between actual switching points, or between circuit access points, because of the freedom afforded Administrations in choosing the relative transmission level at these points. + +In order to ensure satisfactory loss and stability performance on end-to-end connections within private switched networks, the overall loss of interconnecting international leased circuits may need to be the subject of bilateral discussion between the terminal Administrations. In this connection, see also § 3 below. + +### **2.2 Loss/frequency distortion** + +The limits for overall loss relative to that at 1020 Hz are given in Figure 1/M.1030 and Figure 2/M.1030 for 4-wire and 2-wire presented circuits respectively. It may be noted that the limits in Figure 2/M.1030 are the same as those appearing in Recommendation M.1040, § 2.2. + +--- + +1) Recommendation G.171, § 1 [1] states that for connection between private telephone networks and the public network, when permitted, “assurance cannot always be given that transmission performance to CCITT standards will be obtained.” The same may be said for connections achieved by a user over which an Administration has no control, for example, between two or more private networks by virtue of user provided private automatic branch exchanges (PABXs). + +Exceptionally, where a 2-wire private telephone exchange originates and terminates traffic in an otherwise 4-wire network, the 4-wire section of an international leased circuit terminated on that exchange should meet the requirements of Figure 1/M.1030. + +![Figure 1/M.1030: Limits for overall loss of the circuit relative to that at 1020 Hz for 4-wire circuits. The graph shows loss in dB on the y-axis (from -2 to 10) against frequency in Hz on the x-axis (from 0 to 3000). A reference point is marked at 1020 Hz, 0 dB. The loss is 0 dB from 300 Hz to 500 Hz, then drops to -3 dB at 500 Hz, and remains at -3 dB until 2000 Hz. At 2000 Hz, it rises to 6 dB and stays until 2800 Hz. Between 2800 Hz and 3000 Hz, it rises to 10 dB. Below 300 Hz and above 3000 Hz, the loss is not less than 0.0 dB.](e94f3bbb6f7501b9a1344dd0210e5dd8_img.jpg) + +Figure 1/M.1030: Limits for overall loss of the circuit relative to that at 1020 Hz for 4-wire circuits. The graph shows loss in dB on the y-axis (from -2 to 10) against frequency in Hz on the x-axis (from 0 to 3000). A reference point is marked at 1020 Hz, 0 dB. The loss is 0 dB from 300 Hz to 500 Hz, then drops to -3 dB at 500 Hz, and remains at -3 dB until 2000 Hz. At 2000 Hz, it rises to 6 dB and stays until 2800 Hz. Between 2800 Hz and 3000 Hz, it rises to 10 dB. Below 300 Hz and above 3000 Hz, the loss is not less than 0.0 dB. + +*Note* – Below 300 Hz and above 3000 Hz the loss shall not be less than 0.0 dB but is otherwise unspecified. These frequencies should be confirmed or amended after further study. + +FIGURE 1/M.1030 + +**Limits for overall loss of the circuit relative to that at 1020 Hz for 4-wire circuits** + +![Figure 2/M.1030: Limits for overall loss of the circuit relative to that at 1020 Hz for 2-wire presented circuits. The graph shows overall loss in dB on the y-axis (from -3 to 16) against frequency in Hz on the x-axis (from 0 to 3000). A reference point is marked at 1020 Hz, 0 dB. The loss is 0 dB from 300 Hz to 400 Hz, then rises to 9 dB at 400 Hz, and remains at 9 dB until 2000 Hz. At 2000 Hz, it rises to 16 dB and stays until 2800 Hz. Between 2800 Hz and 3000 Hz, it drops to -3 dB. Below 300 Hz and above 3000 Hz, the loss is not less than 0.0 dB.](09af5b86cf9391543d22db5f2129b3ca_img.jpg) + +Figure 2/M.1030: Limits for overall loss of the circuit relative to that at 1020 Hz for 2-wire presented circuits. The graph shows overall loss in dB on the y-axis (from -3 to 16) against frequency in Hz on the x-axis (from 0 to 3000). A reference point is marked at 1020 Hz, 0 dB. The loss is 0 dB from 300 Hz to 400 Hz, then rises to 9 dB at 400 Hz, and remains at 9 dB until 2000 Hz. At 2000 Hz, it rises to 16 dB and stays until 2800 Hz. Between 2800 Hz and 3000 Hz, it drops to -3 dB. Below 300 Hz and above 3000 Hz, the loss is not less than 0.0 dB. + +*Note* – Below 300 Hz and above 3000 Hz the loss shall not be less than 0.0 dB, but is otherwise unspecified. These frequencies should be confirmed or amended after further study. + +FIGURE 2/M.1030 + +**Limits for overall loss of the circuit relative to that at 1020 Hz for 2-wire presented circuits** + +### 2.3 Variations of overall loss with time + +For all circuits, variation with time of the overall loss at 1020 Hz (including daily and seasonal variations but excluding amplitude hits) should be as small as possible but should not exceed $\pm 4$ dB. + +### 2.4 Random circuit noise + +The nominal level of psophometric noise power depends upon the actual constitution of the circuit, in particular upon the length of circuit of frequency division multiplex systems involved. The provisional limit for circuits of lengths greater than 10 000 km is $-38$ dBm0p. However, circuits of shorter length will have substantially less random noise (see Annex A to this Recommendation and Recommendation M.1050, § 3.5). + +### 2.5 Echo + +The provisions of Recommendations G.122 [3] and G.131 [4] concerning echo control should be observed in so far as they are applicable. + +## 3 Stability + +National systems interfacing with the international leased circuits dealt with in this Recommendation should comply with the stability requirements of Recommendation G.122 [3]. + +Recognizing that national private switched networks (planned in accordance with national transmission standards) may ultimately be interconnected by international leased circuits, involved Administrations may need to discuss the actions necessary to ensure adequate stability of the resulting international private switched network. + +## ANNEX A + +(to Recommendation M.1030) + +### Random circuit noise + +Figure A-1/M.1030 displays random noise versus length of circuit of FDM carrier systems and is presented as a guide to the random noise performance which may be found on an international leased circuit. + +![Figure A-1/M.1030: Random circuit-noise performance graph. The Y-axis is 'Random noise' in dBm0p, ranging from -55 to -35. The X-axis is 'Length of circuit of FDM carrier systems' in km, on a logarithmic scale from 200 to 20,000. A shaded diagonal band shows the relationship between length and noise level.](d6226b6d22b1babc1eeeb93e07cc9cc4_img.jpg) + +The graph shows the relationship between random noise (in dBm0p) and the length of an FDM carrier system circuit (in km). The Y-axis is labeled 'Random noise' and ranges from -55 to -35 dBm0p. The X-axis is labeled 'Length of circuit of FDM carrier systems' and is on a logarithmic scale with values 200, 500, 1000, 2000, 5000, 10000, and 20000 km. A shaded diagonal band represents the noise performance, starting at approximately -51 dBm0p for 500 km and rising to approximately -38 dBm0p for 20,000 km. The text 'CCITT-37060 d03-sc' is visible in the bottom right corner of the graph area. + +| Length of circuit of FDM carrier systems (km) | Random noise (dBm0p) | +|-----------------------------------------------|----------------------| +| 500 | -51 | +| 1000 | -48 | +| 2000 | -45 | +| 5000 | -41 | +| 10000 | -39 | +| 20000 | -38 | + +Figure A-1/M.1030: Random circuit-noise performance graph. The Y-axis is 'Random noise' in dBm0p, ranging from -55 to -35. The X-axis is 'Length of circuit of FDM carrier systems' in km, on a logarithmic scale from 200 to 20,000. A shaded diagonal band shows the relationship between length and noise level. + +FIGURE A-1/M.1030 +**Random circuit-noise performance** + +*Note* – At the present time the section of the circuit provided by satellite (between earth stations) employing FDM techniques contributes approximately 10 000 pW0p (–50 dBm0p) of noise. Therefore, for the purpose of determining maintenance limits for noise measurement on leased circuits, the length of the section provided by satellite may be considered to be equivalent to 1000 km in Figure A-1/M.1030. + +The contribution to noise of a circuit section provided by satellite employing TDM techniques remains as a subject for further study. + +## **References** + +- [1] CCITT Recommendation *Transmission plan aspects of private operated networks*, Vol. III, Rec. G.171. +- [2] CCITT Recommendation *Access points for international telephone circuits*, Vol. IV, Rec. M.565. +- [3] CCITT Recommendation *Influence of national systems on stability, talker echo and listener echo in international connections*, Vol. III, Rec. G.122. +- [4] CCITT Recommendation *Stability and echo*, Vol. III, Rec. G.131. \ No newline at end of file diff --git a/marked/M/T-REC-M.1045-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1045-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5bd1715b3a587fc50847d304004966466f21fed --- /dev/null +++ b/marked/M/T-REC-M.1045-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50a606405f6e113c99bc45a761e9826662fb99db9219576e7043fc02933a015c +size 8297 diff --git a/marked/M/T-REC-M.1050-199806-I_PDF-E/raw.md b/marked/M/T-REC-M.1050-199806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..16c57cd65bdee50c40359206176c53220e86735c --- /dev/null +++ b/marked/M/T-REC-M.1050-199806-I_PDF-E/raw.md @@ -0,0 +1,619 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1050** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(06/98) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International leased circuits + +--- + +**Lining up an international point-to-point leased +circuit with analogue presentation to the user** + +ITU-T Recommendation M.1050 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.1050** + +# **LINING UP AN INTERNATIONAL POINT-TO-POINT LEASED CIRCUIT WITH ANALOGUE PRESENTATION TO THE USER** + +## **Summary** + +This Recommendation provides two methodologies to ensure effective lining up of an international leased circuit with analogue presentation to the user. + +## **Source** + +ITU-T Recommendation M.1050 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of June 1998. + +## **Keywords** + +Analogue presentation, end-to-end line up, international leased circuit, section-by-section line up. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | | Page | +|-------|-------------------------------------------------------------------------------|-------------| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Terminology and definitions ..... | 2 | +| 4 | Abbreviations ..... | 2 | +| 5 | General ..... | 3 | +| 6 | Lining up the constituent parts of the circuit ..... | 3 | +| 6.1 | National sections ..... | 3 | +| 6.1.1 | Overall loss at reference frequency ..... | 3 | +| 6.1.2 | Loss/frequency distortion (special quality circuits only) ..... | 4 | +| 6.1.3 | Group-delay distortion (special quality circuits only) ..... | 4 | +| 6.2 | International section ..... | 4 | +| 6.2.1 | Overall loss at reference frequency ..... | 4 | +| 6.2.2 | Loss/frequency distortion ..... | 4 | +| 6.2.3 | Group-delay distortion (special quality circuits only) ..... | 4 | +| 6.3 | International link ..... | 4 | +| 7 | Lining up the overall circuit ..... | 4 | +| 7.1 | Overall loss ..... | 5 | +| 7.2 | Loss/frequency distortion ..... | 5 | +| 7.2.1 | Ordinary quality circuits ..... | 5 | +| 7.2.2 | Special quality circuits ..... | 5 | +| 7.3 | Group-delay distortion (special quality circuits only) ..... | 5 | +| 7.4 | Variation with time of the overall loss at 1020 Hz ..... | 6 | +| 7.4.1 | Amplitude hits (special quality circuits only) ..... | 6 | +| 7.4.2 | Other variations ..... | 6 | +| 7.5 | Random circuit noise ..... | 6 | +| 7.6 | Impulsive noise (special quality circuits only) ..... | 6 | +| 7.7 | Phase jitter (special quality circuits only) ..... | 6 | +| 7.8 | Total distortion (special quality circuits only) ..... | 6 | +| 7.9 | Single tone interference (special quality circuits only) ..... | 7 | +| 7.10 | Frequency error (special quality circuits only) ..... | 7 | +| 7.11 | Harmonic and intermodulation distortion (special quality circuits only) ..... | 7 | +| 7.12 | Crosstalk (special quality circuits only) ..... | 7 | +| 7.13 | Power source interferences (special quality circuits only) ..... | 7 | +| 8 | Section-by-section line-up ..... | 7 | +| 8.1 | Lining up the analogue-type section ..... | 8 | +| 8.1.1 | National sections ..... | 8 | +| 8.1.2 | International section ..... | 10 | +| 8.2 | Lining up the digital-type section ..... | 10 | +| 8.2.1 | National sections ..... | 10 | +| 8.2.2 | International section ..... | 11 | + +| | | | +|-------|------------------------------------------------------------------------------------|----| +| 8.3 | Overall circuit ..... | 11 | +| 8.3.1 | Configuration and testing of digital-type sections bounded by A/D converters ..... | 11 | +| 8.3.2 | Overall lineup ..... | 11 | +| 9 | Additional reference measurements..... | 11 | +| 10 | Functional checks ..... | 11 | +| 11 | Transmission level checks ..... | 12 | +| 12 | Level limiters..... | 12 | +| 13 | Marking of equipment associated with special quality circuits ..... | 12 | +| 14 | Short-time rerouting of special quality leased circuits ..... | 12 | + +# LINING UP AN INTERNATIONAL POINT-TO-POINT LEASED CIRCUIT WITH ANALOGUE PRESENTATION TO THE USER + +*[Published as M.89 in 1964; revised and renumbered as M.102 in 1968; +new as M.111 and M.113 in 1968; revised in 1972; combined with M.102 (part), +M.111 (part) and M.113 and revised in 1976; renumbered M.1050 in 1980; +revised in 1984, 1988, 1993 and 1998]* + +## 1 Scope + +This Recommendation deals with the lining-up of both ordinary quality point-to-point leased circuits (the characteristics of which are specified in Recommendation M.1040 [15]), and special quality point-to-point leased circuits (the characteristics of which are specified in Recommendations M.1020 [12] and M.1025 [13]), which are provided by analogue transmission systems or by a mixture of analogue and digital systems. + +## 2 References + +The following ITU-T Recommendations contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendation listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.101 (1996), *The transmission plan*. +- [2] ITU-T Recommendation G.122 (1993), *Influence of national systems on stability and talker echo in international connections*. +- [3] ITU-T Recommendation G.131 (1996), *Control of talker echo*. +- [4] CCITT Recommendation G.134 (1988), *Linear crosstalk*. +- [5] CCITT Recommendation G.151 (1980), *General performance objectives applicable to all modern international circuits and national extension circuits*. +- [6] CCITT Recommendation G.224 (1984), *Maximum permissible value for the absolute power level (power referred to one milliwatt) of a signalling pulse*. +- [7] CCITT Recommendation G.232 (1984), *12-channel terminal equipments*. +- [8] CCITT Recommendation H.13 (1988), *Impulsive-noise measuring instrument for telephone-type circuits*. +- [9] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- [10] CCITT Recommendation M.580 (1988), *Setting up and lining up an international circuit for public telephony*. +- [11] CCITT Recommendation M.1010 (1988), *Constitution and nomenclature of international leased circuits*. +- [12] ITU-T Recommendation M.1020 (1993), *Characteristics of special quality international leased circuits with special bandwidth conditioning*. +- [13] ITU-T Recommendation M.1025 (1993), *Characteristics of special quality international leased circuits with basic bandwidth conditioning*. +- [14] CCITT Recommendation M.1030 (1988), *Characteristics of ordinary quality international leased circuits forming part of private switched telephone networks*. + +- [15] CCITT Recommendation M.1040 (1988), *Characteristics of ordinary quality international leased circuits.* +- [16] CCITT Recommendation M.1060 (1988), *Maintenance of international leased circuits.* +- [17] ITU-T Recommendation M.1340 (1996), *Performance allocations and limits for international data transmission links and systems.* +- [18] ITU-T Recommendation M.1370 (1993), *Bringing-into-service of international data transmission systems.* +- [19] ITU-T Recommendation M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH path, sections and transmission systems.* +- [20] ITU-T Recommendation O.41 (1994), *Psophometer for use on telephone-type circuits.* +- [21] CCITT Recommendation O.71 (1988), *Impulsive noise measuring equipment for telephone-type circuits.* +- [22] CCITT Recommendation O.81 (1972), *Group-delay measuring equipment for telephone-type circuits.* +- [23] CCITT Recommendation O.91 (1988), *Phase jitter measurement equipment for telephone-type circuits.* +- [24] CCITT Recommendation O.95 (1980), *Phase and amplitude hits counters for telephone-type circuits.* +- [25] CCITT Recommendation O.111 (1988), *Frequency shift measuring equipment for use on carrier channels.* +- [26] CCITT Recommendation O.132 (1988), *Quantizing distortion measuring equipment using a sinusoidal test signal.* +- [27] CCITT Recommendation M.810 (1988), *Setting up and lining up of an international voice-frequency telegraph link for public telegraph circuits (for 50, 100 and 200 baud modulation rates).* +- [28] CCITT Recommendation V.2 (1988), *Power levels for data transmission over telephone lines.* +- [29] CCITT Recommendation V.55 (1988), *Impulsive noise measuring instrument for telephone-type circuits.* +- [30] CCITT Recommendation O.42 (1984), *Equipment to measure non-linear distortion using the 4-tone intermodulation method.* + +## 3 Terminology and definitions + +Terminologies and definitions relating to this Recommendation are provided in Recommendation M.60 [9]. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations. + +| | | +|-----|---------------------------------| +| A/D | Analogue/Digital | +| ES | Errored Second | +| FDM | Frequency Division Multiplexing | +| PCM | Pulse Code Modulation | +| RP | Renter's Premises | +| SES | Severely Errored Second | +| TIC | Terminal International Centre | +| TNC | Terminal National Centre | + +## 5 General + +Figure 1 shows the constituent parts of an international point-to-point leased circuit. + +![Diagram of an international point-to-point leased circuit showing its constituent parts: Renter's premises (RP), Terminal national centre (TNC), and Terminal international centre (TIC).](562f471e8153729557e6a4ee6343c32c_img.jpg) + +The diagram illustrates the components of an international leased circuit. It shows a sequence of nodes: RP (Renter's premises), TNC (Terminal national centre), TIC (Terminal international centre), TIC, TNC, and RP. The circuit is divided into three main sections: a 'National section' between the first RP and TNC, an 'International section (International line)' between the two TICs, and another 'National section' between the second TNC and the second RP. Below these, an 'International link' is shown between the two TICs, and the entire 'International leased circuit' is indicated between the two RPs. A reference code 'T0405040-94/d01' is present in the bottom right. A legend at the bottom left defines the abbreviations: RP for Renter's premises, TNC for Terminal national centre, and TIC for Terminal international centre. + +Diagram of an international point-to-point leased circuit showing its constituent parts: Renter's premises (RP), Terminal national centre (TNC), and Terminal international centre (TIC). + +**Figure 1/M.1050 – The constituent parts of an international point-to-point leased circuit** + +Test signals transmitted over the international section and link should be applied at a level of $-10$ dBm0. + +The method of line-up described in clauses 6 and 7 below requires that appropriate personnel be present at the renter's premises in the two terminal countries to carry out overall, end-to-end tests of the characteristics of international leased circuits. The cooperation of staff at the terminal international centres may also be required to overcome language or technical difficulties. + +Recognizing that differing national practices may mean that the required degree of international coordination is difficult to achieve, and acknowledging that it may not be possible to arrange simultaneous attendance at the two renter's premises because of time zone differences or restricted access to those premises, clause 8 below describes a method of circuit line-up using a section-by-section approach. + +It should be noted that the end-to-end line-up approach (see clauses 6 and 7) and the section-by-section approach (see clause 8) are not compatible. Thus, Network Operators/Service Providers must agree, on a bilateral basis, which approach they will adopt. + +When a section is entirely routed over a digital transmission system, the section-by-section approach is preferred. + +## 6 Lining up the constituent parts of the circuit + +After the circuit has been set up, the following lining-up procedure should be followed in each direction of transmission. + +### 6.1 National sections + +When analogue access to the circuit is available at the terminal international centre, the following tests should be performed regardless of whether the national section is provided by analogue circuit sections or a combination of analogue, mixed and digital circuit sections. + +#### 6.1.1 Overall loss at reference frequency + +Each national section should be lined up at the reference frequency according to national practices between the terminal national centre and international centre. Note should be taken of the requirement concerning the receiving relative level in 2.1/M.1020 [12], 2.1/M.1025 [13] and 2.1/M.1040 [15]. For international leased circuits forming part of a private switched network, the loss of the national section must be consistent with meeting the required overall loss of the circuit as agreed between Network Operators/Service Providers (refer to 2.1/M.1030 and to clause 3/M.1030 [14]). A record should be kept of the levels received (including any measurements made at intermediate national test points). National sections beyond the terminal national centre must also be lined up. + +#### **6.1.2 Loss/frequency distortion (special quality circuits only)** + +The loss/frequency distortion should be measured at several frequencies. The limits of Table 1/M.580 [10] (column headed "between circuit access points") have to be met, if necessary, by means of an equalizer. + +#### **6.1.3 Group-delay distortion (special quality circuits only)** + +For circuits in conformity with Recommendation M.1020 [12], the limits to be applied are those given in Figure 2/M.1020 [12]. In the case of circuits in conformity with Recommendation M.1025 [13], the group-delay distortion should be measured and recorded for subsequent maintenance purposes. Any obvious abnormal condition shall be cleared. + +### **6.2 International section** + +When analogue access to the circuit is available at the terminal international centres, the following tests should be performed regardless of whether the international section is provided by analogue circuit sections or a combination of analogue, mixed and digital circuit sections. + +#### **6.2.1 Overall loss at reference frequency** + +The sections comprising the international line (see Figure 2/M.1010 [11]) should be lined up so that when, at the sending terminal international centre, a test signal at a level of $-10 \text{ dBm}0$ is connected to the input of the international line, the level received at the other terminal international centre is as close as possible to $-10 \text{ dBm}0$ . The level at intermediate test points should also be as close as possible to $-10 \text{ dBm}0$ . + +#### **6.2.2 Loss/frequency distortion** + +The loss/frequency distortion should be measured at several frequencies. The appropriate limits of Tables 1/M.580, 2/M.580 and 3/M.580 [10] (column headed "between circuit access points") have to be met, if necessary, by means of an equalizer. + +#### **6.2.3 Group-delay distortion (special quality circuits only)** + +For circuits in conformity with Recommendation M.1020 [12], the limits to be applied are those given in Figure 2/M.1020 [12]. In the case of circuits in conformity with Recommendation M.1025 [13], the group-delay distortion should be measured and recorded for subsequent maintenance purposes. Any obvious abnormal condition shall be cleared. + +### **6.3 International link** + +If it is possible, after the national and international sections have been lined up and connected together at the terminal international centres, measurements should be made of the international link between terminal national centres. These measurements should be of overall loss at reference frequency and loss/frequency distortion and should be recorded for subsequent maintenance purposes. + +## **7 Lining up the overall circuit** + +The constituent parts of the circuit having been satisfactorily lined up, the line-up of the overall circuit between renter's premises should now be made. + +Where loop facilities exist, these may be used to obtain reference measurements, for subsequent maintenance. Care must be taken to avoid simultaneous operation of loop facilities should they exist at both terminals. + +### 7.1 Overall loss + +The loss at 1020 Hz should be measured and recorded. Note should be taken of 2.1/M.1020 [12], 2.1/M.1025 [13] and 2.1/M.1040 [15]. For international leased circuits forming part of a private switched network, the overall loss of the circuit should be adjusted to the value agreed between Network Operators/Service Providers (see 2.1/M.1030 [14] and clause 3/M.1030 [14]). + +If 2-wire operation is intended, the curve in Recommendation G.131 [3] may be used to determine if an echo suppressor/canceller is necessary. Where appropriate, the stability of the circuit should be checked against the requirements of Recommendation G.122 [2]. Inasmuch as the same sort of plant is used for leased circuits as is used to provide the "national system" of Recommendation G.101 [1], this should ordinarily present no problem. References to virtual switching points (*extrémités virtuelles* in French) in the G series Recommendations should be interpreted as "points in the two directions of transmission on the international line at equal relative level". + +### 7.2 Loss/frequency distortion + +#### 7.2.1 Ordinary quality circuits + +The loss/frequency distortion should meet the limits of 2.2/M.1030 [14] or of 2.2/M.1040 [15] as appropriate. Equalization should not normally be required to meet these limits. + +#### 7.2.2 Special quality circuits + +The loss/frequency distortion should be measured at several frequencies and recorded. To meet the limits given in Figure 1/M.1020 [12] or in clause 1/M.1025 [13], as appropriate, *mop-up* equalization may be necessary (see Notes 1 and 2). + +### 7.3 Group-delay distortion (special quality circuits only) + +The group-delay distortion should be measured using a measuring set in accordance with Recommendation O.81 [22]. + +**7.3.1** In the case of circuits to Recommendation M.1020 [12], the limits to be met are given in Figure 2/M.1020 [12]. The maximum unequalized group-delay distortion to be expected at the receiving end is three times that of Figure 2/M.1020 [12] (see Notes 1 and 2). + +**7.3.2** In the case of circuits to Recommendation M.1025 [13], the limits to be met are given in Figure 2/M.1025 [13] (see Notes 1 and 3). + +**Notes concerning 7.2.2 and 7.3** (Equalization of loss/frequency distortion and group-delay distortion on special quality leased circuits): + +NOTE 1 – The precise location of any necessary equalizers is left to Network Operators/Service Providers to decide according to national practices. Equalizers built into the modems are not part of the international leased circuit as it is defined in Recommendation M.1010 [11]. + +The Network Operator/Service Provider at the receiving end of the circuit is responsible for seeing that the circuit meets the overall distortion limits in the receiving transmission direction. + +Routing restrictions may be necessary to achieve the loss/frequency and group-delay distortion limits specified. Factors that may contribute to difficulties in meeting these limits are the number of through-group filters in group links, the number of channel translating equipments, the use of edge channels, heavily loaded cable, etc. + +NOTE 2 – Equal distortion limits have been allocated to the national circuit section at the transmitting end, the international line and the national circuit section at the receiving end. + +Individual cases of section limits being slightly exceeded can be accepted if the other sections do not attain their limits, so that the admissible overall unequalized distortion of three times the section limits at the receiving end is met. + +NOTE 3 – Any necessary equalization to bring the overall group-delay distortion within the specified limits should be carried out at one location only for each direction of transmission. + +### 7.4 Variation with time of the overall loss at 1020 Hz + +#### 7.4.1 Amplitude hits (special quality circuits only) + +Amplitude hits should be measured with an instrument complying to Recommendation O.95 [24] and recorded. The limits specified in Recommendations M.1020 [12] and M.1025 [13], as appropriate, should not be exceeded. + +#### 7.4.2 Other variations + +The variation of overall loss at 1020 Hz should be measured over a period of a few hours to check that the limits specified in Recommendations M.1020 [12], M.1025 [13] and M.1030 [14] are not exceeded. If the results are not satisfactory, the check should be continued to allow the trouble to be investigated and cleared. + +### 7.5 Random circuit noise + +Random circuit noise may be measured with a psophometer complying with Recommendation O.41 [20]. + +With the circuit correctly terminated, the psophometric noise power at the end of the circuit should be measured and recorded. The measured noise power should meet the requirements of Recommendations M.1020 [12], M.1025 [13], M.1030 [14] or M.1040 [15], as appropriate1. Where the measured noise is higher by 5 dB or more than the appropriate value in these Recommendations or is higher than -38 dBm0p, whichever is the more stringent requirement, a fault should be suspected and action taken to locate and remedy it where possible. It may be useful to compare noise measurements on circuits of identical or similar constitution to help locate a possible fault. + +### 7.6 Impulsive noise (special quality circuits only) + +Impulsive noise should be measured with an instrument complying with Recommendation O.71 [21] and recorded. It should meet the limits given in Recommendation M.1020 [12] or in Recommendation M.1025 [13] as appropriate. + +A method of measurement is described in Recommendations H.13 [8] and V.55 [29]. + +It should be noted that satisfactory impulsive noise performance on a circuit is likely to be achieved if the circuit is routed via a 64 kbit/s digital path complying with Recommendation M.2100 [19]. + +### 7.7 Phase jitter (special quality circuits only) + +Phase jitter should be measured using an instrument complying with Recommendation O.91 [23] and recorded. + +The limits given in Recommendation M.1020 [12] or in Recommendation M.1025 [13], as appropriate, should not be exceeded, and routing restrictions (for example, minimizing the number of modulating equipments) may be necessary to achieve the objective limit. + +### 7.8 Total distortion (special quality circuits only) + +When the circuit includes any digital circuit sections, a measurement of total distortion should be made using an instrument complying with Recommendation O.132 [26]. Such a measurement will include contributions from quantizing distortion, random noise, harmonic distortion and single tone interference. The minimum signal-to-total distortion ratio is given in Recommendations M.1020 [12] and M.1025 [13]. However, if this minimum ratio is satisfied, it should not be assumed that all the parameters which contribute to the measurement are satisfactory. The total distortion measurement is not a substitute for the individual measurements specified in this Recommendation. + +--- + +1 Recommendation O.41 [20] specifies a flat filter of 3.1 kHz bandwidth for unweighted noise measurements on data circuits. If this filter is used, the noise values given in Recommendations M.1020 [12] to M.1060 [16] do not apply because they are based on the use of psophometric weighting. Therefore, further study is required to determine the appropriate values for unweighted circumstances. + +### **7.9 Single tone interference (special quality circuits only)** + +The method of measurement is under study. + +### **7.10 Frequency error (special quality circuits only)** + +The frequency error introduced by the circuit should be measured and recorded. A method of measurement is given in Recommendation O.111 [25]. + +The limits specified in Recommendation M.1020 [12] or in Recommendation M.1025 [13], as appropriate, should be met. + +### **7.11 Harmonic and intermodulation distortion (special quality circuits only)** + +Harmonic distortion should be measured by injecting a 700 Hz test frequency of $-13\text{ dBm}0$ at the transmit end of the circuit. The level of any individual harmonic at the receiving end should not exceed the limit given in Recommendation M.1020 [12] or in Recommendation M.1025 [13] as appropriate. + +Alternatively, by bilateral agreement between Network Operators/Service Providers, a measurement of second and third order intermodulation products using an instrument complying with Recommendation O.42 [30] should be performed. The limits are for further study. + +The results should be recorded. + +### **7.12 Crosstalk (special quality circuits only)** + +Crosstalk attenuation between different circuits and between the forward and reverse direction of the same circuit should meet the characteristics given in Recommendations M.1020 [12] and M.1025 [13]. Measuring techniques for the measurement of this parameter are described in Recommendations G.134 [4] and G.232 [7]. The bandwidth of the measuring equipment should not exceed 10 Hz. + +### **7.13 Power source interferences (special quality circuits only)** + +Admissible values of power source interferences are given in Recommendations M.1020 [12] and M.1025 [13]. + +A test reference frequency of 1020 Hz at a level of 0 dBm0 has to be used for the measurement of this parameter. Levels of unwanted side components should be measured at frequencies up to $\pm 400\text{ Hz}$ (see Recommendation G.151 [5]) from the test reference frequency. + +## **8 Section-by-section line-up** + +The section-by-section approach to the line-up of international leased circuits has been devised to minimize the need for international coordination and to overcome those situations where end-to-end line-up is not practical or possible. + +Sections are defined in Figure 1. + +Two section types will be considered depending on the transmission bearer: + +- analogue-type section where the section is routed over an analogue transmission system or a mixture of analogue and digital systems but, in any case, an analogue access to the circuit is available at the TIC; +- digital-type section where the section is entirely routed over a digital transmission system. It is assumed that a digital access to the circuit at the nominal bit rate is available at both ends of the section. + +A national section where the terminal section is routed over an analogue transmission system and the sub-section bounded by TNC and TIC (national line, see Figure 2/M.1010 [11]) is fully digitized should be categorized as an analogue-type section referring to the definition above. However, this classification may cause some difficulties in lining-up operations. In this case, the national section should be split into two sub-sections lined up independently. The terminal section shall be lined up according to analogue-type section specifications and the national line shall be lined up according to digital-type section specifications. Allocating national section loss/frequency and group-delay distortion limits to the terminal section should not cause any problem as digital systems do not normally impair these parameters. + +### 8.1 Lining up the analogue-type section + +Loss/frequency and group-delay distortion limits are apportioned to the international and national sections as follows (see Figure 2): + +- International section: one third; +- National sections: one third. + +The resulting limits for the international and national sections are given in Tables 1 and 2 for loss/frequency and group-delay, respectively. + +![Diagram illustrating the apportionment of overall distortion limits to national and international sections of international leased circuits. The diagram shows a circuit path from Renter's premises on the left, through a Terminal international centre, an International section, another Terminal international centre, and finally to Renter's premises on the right. The path is divided into three segments, each labeled '1/3 (one third)'. The first segment is a National section, the second is an International section, and the third is a National section. A legend at the bottom left shows a dashed box with a triangle labeled 'Renter's equipment' and a solid line with a circle labeled 'Measuring point'.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +The diagram shows a horizontal line representing a leased circuit path. At the far left and far right are dashed rectangular boxes labeled 'Renter's premises'. Inside each box is a triangle symbol representing 'Renter's equipment'. A solid line with a circle (the 'Measuring point') connects the equipment inside the premises to the rest of the circuit. The circuit then enters a 'National section' (indicated by a double-headed arrow above the line). It reaches a 'Terminal international centre' (marked by a circle on the line). The next segment is an 'International section' (also indicated by a double-headed arrow above). It reaches another 'Terminal international centre' (marked by a circle). The final segment is another 'National section' leading to the second 'Renter's premises'. Below the line, three double-headed arrows indicate the apportionment of distortion limits: the first 'National section' is labeled '1/3 (one third)', the 'International section' is labeled '1/3 (one third)', and the final 'National section' is labeled '1/3 (one third)'. A small text code 'T0405050-94/d02' is in the bottom right corner. A legend at the bottom left shows a dashed box with a triangle labeled 'Renter's equipment' and a solid line with a circle labeled 'Measuring point'. + +Diagram illustrating the apportionment of overall distortion limits to national and international sections of international leased circuits. The diagram shows a circuit path from Renter's premises on the left, through a Terminal international centre, an International section, another Terminal international centre, and finally to Renter's premises on the right. The path is divided into three segments, each labeled '1/3 (one third)'. The first segment is a National section, the second is an International section, and the third is a National section. A legend at the bottom left shows a dashed box with a triangle labeled 'Renter's equipment' and a solid line with a circle labeled 'Measuring point'. + +**Figure 2/M.1050 – Apportionment of overall distortion limits to national and international sections of international leased circuits** + +#### 8.1.1 National sections + +The following tests should be performed regardless of whether the national section is provided by analogue circuit sections or by a combination of analogue, mixed and digital circuit sections. + +##### 8.1.1.1 Overall loss + +Each national section should be lined up at the reference frequency according to national practices between the terminal national centre and international centre. Note should be taken of the requirement concerning the receiving relative level in 2.1/M.1020 [12], 2.1/M.1025 [13] and 2.1/M.1040 [15]. For circuits forming part of a private switched network, the loss of the national section must be consistent with meeting the required overall loss as agreed between Network Operators/Service Providers (see 2.1/M.1030 [14] and clause 3/M.1030 [14]). A record should be kept of the levels received (including any measurements made at intermediate national test points). National sections beyond the terminal national centre must also be lined up. + +**Table 1/M.1050 – Apportionment of loss/frequency distortion limits** + +| Frequency range | Overall loss relative to that at 1020 Hz (dB) | | | | | | +|-----------------|---------------------------------------------------------|--------------|--------------|---------------------------------------------------|--------------|--------------| +| | National sections
(as per Recommendations) | | | International section
(as per Recommendations) | | | +| | M.1020 | M.1025 | M.1040 | M.1020 | M.1025 | M.1040 | +| Below 300 Hz | Loss shall not be less than 0 dB, otherwise unspecified | | | | | | +| 300-400 Hz | – | – | Ø to –1.0 | – | – | Ø to –1.0 | +| 300-500 Hz | +2.0 to –0.7 | +4.0 to –0.7 | – | +2.0 to –0.7 | +4.0 to –0.7 | – | +| 400-2000 Hz | – | – | +3.0 to –1.0 | – | – | +3.0 to –1.0 | +| 500-2500 Hz | – | +2.7 to –0.7 | – | – | +2.7 to –0.7 | – | +| 500-2800 Hz | +1.0 to –0.3 | – | – | +1.0 to –0.3 | – | – | +| 2000-2800 Hz | – | – | +5.3 to –1.0 | – | – | +5.3 to –1.0 | +| 2500-3000 Hz | – | +4.0 to –0.7 | – | – | +4.0 to –0.7 | – | +| 2800-3000 Hz | +2.0 to –0.7 | – | Ø to –1.0 | +2.0 to –0.7 | – | Ø to –1.0 | +| Above 3000 Hz | Loss shall not be less than 0 dB, otherwise unspecified | | | | | | +| Ø Unspecified | | | | | | | + +**Tableau 2/M.1050 – Apportionment of group-delay distortion limits** + +| Frequency range | Limits for group delay relative to the minimum measured group delay in the 500-2800 Hz (ms) | | | | +|-----------------|---------------------------------------------------------------------------------------------|-------------|---------------------------------------------------|-------------| +| | National sections
(as per Recommendations) | | International section
(as per Recommendations) | | +| | M.1020 | M.1025 | M.1020 | M.1025 | +| Below 500 Hz | Unspecified | – | Unspecified | – | +| Below 600 Hz | – | Unspecified | – | Unspecified | +| 500-600 Hz | 1.0 | – | 1.0 | – | +| 600-1000 Hz | 0.5 | 1.0 | 0.5 | 1.0 | +| 1000-2600 Hz | 0.17 | 0.5 | 0.17 | 0.5 | +| 2600-2800 Hz | 1.0 | 1.0 | 1.0 | 1.0 | +| Above 2800 Hz | Unspecified | | | | + +##### 8.1.1.2 Loss/frequency distortion + +The loss/frequency distortion should be measured at several frequencies. The limits in Table 1 (column headed "National sections") have to be met, if necessary, by means of an equalizer (see Note 1). + +##### 8.1.1.3 Group-delay distortion (special quality circuits only) + +The limits in Table 2 (column headed "National sections") have to be met, if necessary, by means of an equalizer (see Note 1). + +##### **8.1.1.4 Other characteristics (special quality circuits only)** + +The remaining characteristics of special quality international leased circuits (see 2.4-2.11/M.1020 [12] and 2.4-2.11/M.1025 [13]) should be treated in accordance with the national practices of the Network Operators/Service Providers concerned, bearing in mind the constitution of the national sections involved. Note that it may not be necessary to measure all such characteristics. For example, quantizing distortion need only be checked when a PCM system is involved, while phase jitter and frequency error might be omitted where the national section is provided solely by audio line plant. + +It should be noted that satisfactory impulsive noise performance on a circuit is likely to be achieved if the circuit is routed via a 64 kbit/s digital path complying with Recommendation M.2100 [19]. + +The limits given in 2.4-2.11/M.1020 [12] and in 2.4-2.11/M.1025 [13], as appropriate, apply to the overall circuit, and cannot therefore be exceeded by either national section. + +#### **8.1.2 International section** + +The following tests should be performed regardless of whether the international section is provided by analogue circuit sections or a combination of analogue, mixed and digital circuit sections. + +##### **8.1.2.1 Overall loss** + +The sections comprising the international line (see Figure 2/M.1010 [11]) should be lined up so that when, at the sending terminal international centre, a test signal at a level of $-10 \text{ dBm}0$ is connected to the input of the international line, the level received at the other terminal international centre is as close as possible to $-10 \text{ dBm}0$ . The level at intermediate test points should also be as close as possible to $-10 \text{ dBm}0$ . + +##### **8.1.2.2 Loss/frequency distortion** + +The loss/frequency distortion should be measured at several frequencies. The limits in Table 1 (column headed "International section") have to be met, if necessary, by means of an equalizer (see Notes 1 and 2). + +##### **8.1.2.3 Group-delay distortion (special quality circuits only)** + +The limits in Table 2 (column headed "International section") have to be met, if necessary, by means of an equalizer (see Notes 1 and 2). + +##### **8.1.2.4 Other characteristics (special quality circuits only)** + +Bearing in mind the constitution of the international section, the remaining characteristics of special quality circuits (as specified in 2.4-2.11/M.1020 [12] and 2.4-2.11/M.1025 [13]) should be checked using the measuring instruments and methods of measurement mentioned in clause 7 above. + +The limits given in 2.4-2.11/M.1020 [12] and 2.4-2.11/M.1025 [13] apply to the overall circuit, and cannot therefore be exceeded by the international section. Staff responsible for the line-up of international leased circuits at the terminal international centres should assess, based on the measured values for the international and national sections, whether or not the overall limits will be met. + +It should be noted that satisfactory impulsive noise performance on a circuit is likely to be achieved if the circuit is routed via a 64 kbit/s digital path complying with Recommendation M.2100 [19]. + +### **8.2 Lining up the digital-type section** + +#### **8.2.1 National sections** + +The national section is provided by a digital link. Tests should be performed according to national practices to ensure that the link shows satisfactory error performance. + +A performance allocation methodology derived from those described in Recommendation M.1340 [17] may be used to calculate ES and SES performance limits applicable to this link. Percentage performance allocation attributable to this link is the responsibility of the Network Operator/Service Provider concerned. However, it is suggested that national section allocation should not exceed 30% of the overall allocation. This figure would become 15% for the TIC-TNC section. + +In the above cases, it is assumed that limits specified for analogue parameters will be met. + +#### 8.2.2 International section + +The international section is provided by a digital link. It is assumed that limits specified for analogue parameters will be met if this link complies with Recommendation M.1370 [18]. + +The ES and SES performance limits of this digital link should be calculated by using the error performance allocation methodology described in clause 3/M.1340 [17]. + +### 8.3 Overall circuit + +#### 8.3.1 Configuration and testing of digital-type sections bounded by A/D converters + +Digital-type sections are directly connected together. Where an analogue-type section is to be connected to a digital-type one, an A/D converter is installed at the end of this digital-type section. Where a national section is a digital-type one, an A/D converter is installed at customer premises. + +A test should be performed to check overall loss on any portion of the circuit bounded by A/D converters. A 1020 Hz test signal at a level of $-10$ dBm0 is sent to the input of the circuit section; the level received at the other end is as close as possible to $-10$ dBm0. + +#### 8.3.2 Overall lineup + +The constituent analogue and digital link sections of the circuit having been satisfactorily lined up, they should be connected together. + +Where appropriate and possible, the overall circuit should be checked for satisfactory operation (see clause 10 below). + +**Notes concerning 8.1.1.2, 8.1.1.3, 8.1.2.2 and 8.1.2.3** (Equalization of loss/frequency distortion and group-delay distortion on special quality leased circuits): + +NOTE 1 – The precise location of any necessary equalizers is left to Network Operators/Service Providers to decide according to national practices. Equalizers built into the modems are not part of the international leased circuit as it is defined in Recommendation M.1010 [11]. + +Routing restrictions may be necessary to achieve the loss/frequency and group-delay distortion limits specified. Factors that may contribute to difficulties in meeting these limits are the number of through-group filters in group links, the number of channel translating equipments, the use of edge channels, heavily loaded cable, etc. + +NOTE 2 – The Network Operator/Service Provider at the receiving end of the circuit is responsible for seeing that the international section meets the distortion limits in the receive direction of transmission. + +## 9 Additional reference measurements + +As part of the lining-up procedure, it may be considered useful to make reference measurements at intermediate points by high-impedance bridging methods, and/or by measurements made on a loop-basis. Such measurements should be carried out under the direction of the circuit control station. + +## 10 Functional checks + +Where appropriate and possible, the complete circuit should be checked for satisfactory operation as follows: + +- Circuit signalling should be checked for satisfactory operation. When the signalling current is transmitted at the level permitted by national regulations, the limits given in the relevant Q-series Recommendations should not be exceeded at the input to the international line. +- Tests should be made to determine if excessive echo, instability or other impediments to satisfactory operation, are present. For example, by means of a bilateral agreement, the additional characteristics mentioned in clause 6/M.1060 [16] may be checked. + +## 11 Transmission level checks + +It should be verified by direct measurement if possible (otherwise by calculation) that when the renter's apparatus is transmitting signals at the level permitted by national regulations, the following limits (see Note 3) are not exceeded at the input to the international line: + +- Data transmission (Recommendation V.2 [28]) –13 dBm0 +- Voice-frequency telegraphy + - Amplitude - modulated } +Frequency - modulated } see 4.1/M.810 [27] +- Phototelegraph or facsimile + - Amplitude modulation (white level) –3 dBm0 + - Frequency modulation –13 dBm0 +- Simultaneous transmission of various signals + - Total power –13 dBm0 + +NOTE 1 – The above limits apply when the whole of the bandwidth is devoted to one particular transmission at any one time. When the band is divided among two or more types of transmission, the power levels permitted by the various Recommendations mentioned above should be reduced by the quantity $10 \log (3100/x)$ dB, where $x$ is the nominal bandwidth in hertz occupied by the transmission concerned. + +NOTE 2 – In addition to the above specification, discrete frequency signals must comply with the requirements of Recommendation G.224 [6]. + +NOTE 3 – These are considered too high by some Network Operators/Service Providers, and additional study of these limits is anticipated in the future. + +## 12 Level limiters + +Where level-limiting devices are fitted on the circuit, they should not introduce distortion when the levels transmitted are within the permitted limits. + +## 13 Marking of equipment associated with special quality circuits + +In order to reduce to a minimum interruptions on the circuits, it is necessary that all equipment associated with such circuits (e.g. amplifiers, channel translating equipment, distribution frames, etc.) be positively marked so that the maintenance staff can readily identify it and can therefore avoid causing interruptions to the circuit inadvertently when they carry out maintenance work in repeater stations and exchanges. + +## 14 Short-time rerouting of special quality leased circuits + +The *make good* of a special quality circuit in case of a breakdown or planned outage needs special attention in order to keep the circuit characteristics within the required limits. + +If there is a breakdown or planned interruption of a transmission system, rerouting should be carried out as far as possible at group, supergroup, etc., or digital path level. This would normally not seriously affect the attenuation and group-delay distortion. When such a rerouting of transmission links cannot be effected or when only the circuit concerned is faulty, a reroute circuit or circuit section of similar constitution as that in service should be chosen, in particular with regard to the number of FDM carrier sections and the relative number of analogue and digital circuit sections. The procedure of short-time rerouting at audio level can be facilitated if nominated reroute circuit sections having the same characteristics as the circuit sections of the regular route are available. This consideration also applies to the local line sections. + +The circuit control station, if not directly involved, should be apprised of short-time rerouting which might affect the operation of the circuit. If a complete line-up is not practical, e.g. due to the expected short duration of the rearrangement, it is a minimum requirement that at least a check of the circuit overall loss at reference frequency and a measurement of the random circuit noise should be made. + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.1060-198811-I_PDF-E/2df09d249c38abee55dbf0526dd6da0a_img.jpg b/marked/M/T-REC-M.1060-198811-I_PDF-E/2df09d249c38abee55dbf0526dd6da0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..388e80cdb9fe9cb7792b8adc237924fc06b0d41b --- /dev/null +++ b/marked/M/T-REC-M.1060-198811-I_PDF-E/2df09d249c38abee55dbf0526dd6da0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:133f35cb86dd096f0f7d4db5560f099b4535f8306c3335c683fb640212930c93 +size 40880 diff --git a/marked/M/T-REC-M.1060-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1060-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a9c685895b23e79cadf62213b44226e93e5207a --- /dev/null +++ b/marked/M/T-REC-M.1060-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a4d6f1181fb021d7aea56d330d7892711e59dcf176b2c7c3c477e468224fe18 +size 7449 diff --git a/marked/M/T-REC-M.110-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.110-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ae5b9a589b851c16dea4515505e87e60c193df37 --- /dev/null +++ b/marked/M/T-REC-M.110-198811-I_PDF-E/raw.md @@ -0,0 +1,148 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.110** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTRODUCTION AND GENERAL PRINCIPLES** + +--- + +**CIRCUIT TESTING** + +**ITU-T Recommendation M.110** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.110 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **CIRCUIT TESTING** + +## **1 Access points for testing purposes** + +Access points are required to enable lining-up and subsequent maintenance operations to be performed on international circuits. The required access points are as follows: + +1.1 Recommendation M.565 describes and defines the access points needed for international public telephone circuits, these points being referred to as “circuit access points” and “line access points”. + +Line access points and circuit access points (or appropriate means for reaching the circuit access points) should be provided for testing all circuits which are used for the provision of international telecommunication services. + +Where a circuit uses channel associated signalling, it should be possible to identify and measure at the circuit access points, the signal-transmission parameters, e.g., type of signal, sequence, timing, duration, level and frequency. + +1.2 Test access points should also be provided for circuits connected through a repeater station in transit from one country to another. Such access points are known as “intermediate access points”. + +1.3 On a leased circuit, the circuit access points are regarded as being located in the renter's premises, at the demarcation point where connections are made to the terminal equipment used on the circuit1). + +1.4 Test access points should also be available at the terminal international centre for circuits terminating within the country at a place remote from the international centre, for example, in the premises of the users of leased circuits or in a voice-frequency telegraph terminal station, etc. Such access points, known as line access points, should be available directly or indirectly to the transmission maintenance point (international line) as defined in Recommendation M.1014 [1] for such circuits. + +1.5 In addition to those mentioned in §§ 1.1 to 1.4 above, access points should be provided on the audio input and output of FDM channel multiplex and primary PCM multiplex equipments. + +1.6 Access points for testing purposes should be provided on all primary order digital paths. Such access points, known as digital path access points, should be located as near to the ends of the digital path as possible. + +With suitable digital test equipment, such digital path access points enable in-service circuit monitoring to be carried out when, for example, digital paths are directly interfaced with digital exchanges or transmultiplexers. + +When the digital path is out of service, this same point can be used to transmit and receive signals for both digital path and circuit testing. + +1.7 Figure 1/M.110 shows an example of the basic access points for international telephone circuits terminated on an analogue exchange, and for a variety of other telephone-type circuits. Figure 2/M.110 shows the basic access points for telephone circuits terminated on a digital exchange. Figures 1/M.110 and 2/M.110 both show that remote access has been provided to the “circuit access points” of automatic telephone circuits. + +1.8 Series M Recommendations relating to the various types of international circuits specify how the above-mentioned access points should be used for line-up and maintenance purposes. + +--- + +1) The access points required for digital leased circuits have yet to be specified. This matter is for further study by Study Group IV, in association with Study Group XV. + +![Diagram showing various circuit types and their access points. On the left, a vertical list of circuit types is shown: Transit circuit, Automatic telephone circuit, Manual telephone circuit, Telegraph systems, Facsimile circuit, Leased telephone circuit, Leased telegraph system, Leased telegraph and speech circuit, and Leased data circuit. Each circuit type is connected to a series of symbols representing access points and equipment. A bracket labeled 'Note 1' groups two transmission paths: one for 'Analogue transmission' (AE -> CTE) and one for 'Digital transmission' (RS -> PCM MUX -> Digital path access point). A legend on the right defines the symbols: solid line for Analogue transmission, dashed line for Digital transmission, CTE for Channel translating equipment, PCM MUX for PCM multiplex equipment, a dot for Circuit access point, a dot with an 'R' for Circuit access point remotely extended, an X for Line access point, a square with a diagonal line for Digital path access point, an 'I' for Intermediate access point, RS for Relay set or signalling converter, AE for Audio equipment, FAX for Facsimile equipment, DT for Data terminal, a comb-like symbol for Telegraph multiplexing equipment, TAE for Test access equipment (Note 2), a telephone handset for Telephone, a switchboard symbol for Switchboard, and a curved line with a switch for Analogue switch.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +Diagram showing various circuit types and their access points. On the left, a vertical list of circuit types is shown: Transit circuit, Automatic telephone circuit, Manual telephone circuit, Telegraph systems, Facsimile circuit, Leased telephone circuit, Leased telegraph system, Leased telegraph and speech circuit, and Leased data circuit. Each circuit type is connected to a series of symbols representing access points and equipment. A bracket labeled 'Note 1' groups two transmission paths: one for 'Analogue transmission' (AE -> CTE) and one for 'Digital transmission' (RS -> PCM MUX -> Digital path access point). A legend on the right defines the symbols: solid line for Analogue transmission, dashed line for Digital transmission, CTE for Channel translating equipment, PCM MUX for PCM multiplex equipment, a dot for Circuit access point, a dot with an 'R' for Circuit access point remotely extended, an X for Line access point, a square with a diagonal line for Digital path access point, an 'I' for Intermediate access point, RS for Relay set or signalling converter, AE for Audio equipment, FAX for Facsimile equipment, DT for Data terminal, a comb-like symbol for Telegraph multiplexing equipment, TAE for Test access equipment (Note 2), a telephone handset for Telephone, a switchboard symbol for Switchboard, and a curved line with a switch for Analogue switch. + +CCITT-69980 + +d01-sc + +TDM = Time division multiplex +VF = Voice frequency multiplex + +Note 1 — Circuits may be routed by analogue or digital transmission media. + +Note 2 — Access may be provided by the normal exchange switching equipment, or by separately provided test access switching equipment. + +FIGURE 1/M.110 + +Access points for analogue international telephone circuits and other telephone-type circuits + +![Diagram of access points for digital international telephone circuits. A 'Digital exchange' box contains a 'Digital switch' (X) connected to three 'Exchange terminals' (ET). Each ET is preceded by a 'Theoretical location of circuit access point' (dashed box with a dot). The top path leads to 'Digital transmission' through a square symbol. The middle path leads to 'Analogue transmission' through a 'PCM MUX', an 'RS' (Resampler), and a square with an X. The bottom path leads to 'Analogue transmission' through a square symbol and a 'T MUX'. A 'TAE' (Terminal Access Equipment) is connected to the switch and to an external point 'R' via a 'Digital or analogue' line. Note 2 points to the TAE connection.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +CCITT-69990 +d02-sc + +Diagram of access points for digital international telephone circuits. A 'Digital exchange' box contains a 'Digital switch' (X) connected to three 'Exchange terminals' (ET). Each ET is preceded by a 'Theoretical location of circuit access point' (dashed box with a dot). The top path leads to 'Digital transmission' through a square symbol. The middle path leads to 'Analogue transmission' through a 'PCM MUX', an 'RS' (Resampler), and a square with an X. The bottom path leads to 'Analogue transmission' through a square symbol and a 'T MUX'. A 'TAE' (Terminal Access Equipment) is connected to the switch and to an external point 'R' via a 'Digital or analogue' line. Note 2 points to the TAE connection. + +![Symbol for Digital switch: a square with an X Symbol for Exchange terminal: a rectangle with ET Symbol for Theoretical location of circuit access point: a dashed box with a dot Symbol for Transmultiplexer: a rectangle with T MUX](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +| | | +|--|----------------------------------------------| +| | Digital switch | +| | Exchange terminal | +| | Theoretical location of circuit access point | +| | Transmultiplexer | + +Symbol for Digital switch: a square with an X Symbol for Exchange terminal: a rectangle with ET Symbol for Theoretical location of circuit access point: a dashed box with a dot Symbol for Transmultiplexer: a rectangle with T MUX + +*Note 1* — Other symbols are as indicated in Figure 1/M.110. + +*Note 2* — Access is normally provided by the exchange switching equipment. + +FIGURE 2/M.110 + +**Access points for digital international telephone circuits** + +## 2 Measuring and testing equipment + +2.1 The basic types of measuring equipment needed in an analogue environment are: + +- signal generators (fixed and variable frequency oscillators and calibrated sending units), +- level-measuring sets, +- calibration units, +- psophometers, +- standard frequency source (or access to such a source), +- equipment for signalling tests. + +In addition, delay distortion measuring equipment, frequency counters, interruption recorders, programme meters, impulsive noise counters, phase jitter meters, automatic transmission measuring equipment, and equipment for non-linear and total distortion measurement may be required. + +2.2 The basic types of test and measuring equipment needed in a digital environment are as mentioned in § 2.1 above. This need can be met by equivalent digital test/measuring equipment, or by analogue equipment and the use of a “test coder/decoder” to convert digital access points to analogue access points. In some situations, testers for the following will prove useful: + +- bit error ratio; +- error-free or errored seconds; +- code violations; +- timing jitter; +- frame alignment. + +2.3 The actual requirements for a particular testing centre will depend upon the types of circuit existing at that centre, and the range of tests and measurements that are specified for those circuits in the relevant Series M Recommendations. Reference should also be made to the “facility” requirements specified for the testing points defined in Recommendations M.717, M.718 and M.719. + +2.4 The implementation of the worldwide transmission and switching plans makes it necessary for international circuits to be lined up and maintained to a very high degree of accuracy. + +It is essential, therefore, to use measuring equipment of high accuracy and stability in order that the maintenance requirements given in the relevant Series M Recommendations for circuits are met, and to ensure uniformity of measurement results. + +To this end it is desirable that measuring equipment provided for lining-up and maintaining all classes of circuits should, wherever possible, conform to the measuring instrument specifications given in the Series O Recommendations. Where no CCITT specification is available, the best order of accuracy and stability should be provided, consistent with cost and type of measurement to be made. + +# Reference + +- [1] CCITT Recommendation *Transmission maintenance point international line (TMP-IL)*, Vol. IV, Rec. M.1014. \ No newline at end of file diff --git a/marked/M/T-REC-M.1130-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1130-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5724dddb0631c7b3da6cc1dc7f6ae93d978a90ab --- /dev/null +++ b/marked/M/T-REC-M.1130-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b697f1f89b3584c606562ea134607091ac54e193693a197e87ada685013c885 +size 8277 diff --git a/marked/M/T-REC-M.1130-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.1130-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a233a1be8043030aa774657e4ce93244d393b2 --- /dev/null +++ b/marked/M/T-REC-M.1130-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:077957f8bbb120e1048f89eefa950f0904b4d7cc6b5a0eae39e45317220aea9f +size 5987 diff --git a/marked/M/T-REC-M.1140-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/M/T-REC-M.1140-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68905e04789b70e2faf2f187f3d619432678a06d --- /dev/null +++ b/marked/M/T-REC-M.1140-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ef83a821ea2b276e53aee69b16d9cc1c0621fb6eb1254b656fa70f47556492 +size 99620 diff --git a/marked/M/T-REC-M.1140-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1140-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..114ada82a155841895be88edabe3f0e44a987929 --- /dev/null +++ b/marked/M/T-REC-M.1140-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:568a956cd506c57e7ad41b63949aa3db1fabb2712aa3e4134d3c6c8f95742fb4 +size 8147 diff --git a/marked/M/T-REC-M.1140-199210-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/M/T-REC-M.1140-199210-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ff122a132014645fdddb0a4d2dce85215533fc9 --- /dev/null +++ b/marked/M/T-REC-M.1140-199210-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12ea759ba81b7d62a588c9ce6e1f39378ae60b124cd37740d6e3b0524a2a2cf5 +size 65362 diff --git a/marked/M/T-REC-M.1140-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.1140-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bdbd3c75125eb8ffbbe9e5f0979872bf655ac97 --- /dev/null +++ b/marked/M/T-REC-M.1140-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b44669678f892f96182ce0504a041b555d5bbcb2c7594c697e8325c83e1afc5 +size 6813 diff --git a/marked/M/T-REC-M.1140-199210-I_PDF-E/e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg b/marked/M/T-REC-M.1140-199210-I_PDF-E/e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bd2078f910020eaa8aa941c545bf42dacd46568 --- /dev/null +++ b/marked/M/T-REC-M.1140-199210-I_PDF-E/e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee929f0f04668a7858ef508fd66caf9acd77d7a7bdb028a6bba0e960237e4e32 +size 60525 diff --git a/marked/M/T-REC-M.1140-199210-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/M/T-REC-M.1140-199210-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381b62afb4c0ec98010015662cec1e278107a84c --- /dev/null +++ b/marked/M/T-REC-M.1140-199210-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3affbc725e73941c7a47f3131921a486a0e05bf2a8b4b7ff8d0c2146c5df518 +size 72541 diff --git a/marked/M/T-REC-M.1160-199704-I_PDF-E/raw.md b/marked/M/T-REC-M.1160-199704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ee37dc19f5c60f21d3da91c7733cd321c0337e4b --- /dev/null +++ b/marked/M/T-REC-M.1160-199704-I_PDF-E/raw.md @@ -0,0 +1,415 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1160** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/97) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Mobile telecommunication systems and services + +--- + +**Maintenance aspects of aeronautical mobile +telecommunication service via satellite** + +ITU-T Recommendation M.1160 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **ITU-T RECOMMENDATION M.1160** + +# **MAINTENANCE ASPECTS OF AERONAUTICAL MOBILE TELECOMMUNICATION SERVICE VIA SATELLITE** + +## **Summary** + +This Recommendation describes special maintenance requirements for the Aeronautical Mobile-satellite Service. + +### **Source** + +ITU-T Recommendation M.1160 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 19th of April 1997. + +### **Keywords** + +Inmarsat-Aero System; Maintenance Aspects; Satellite Aeronautical Mobile. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---| +| 1 | General..... | 1 | +| 1.1 | Scope..... | 1 | +| 1.2 | References..... | 1 | +| 2 | Available services ..... | 1 | +| 3 | System configuration ..... | 2 | +| 3.1 | Aeronautical satellite system ..... | 2 | +| 3.1.1 | Space segments..... | 2 | +| 3.1.2 | Aircraft Earth Station (AES) ..... | 2 | +| 3.1.3 | Aeronautical Ground Earth Station (GES) ..... | 2 | +| 3.1.4 | Test Terminal (TT)..... | 3 | +| 3.1.5 | Network Channel Management System (NCMS) ..... | 3 | +| 3.2 | Interconnection with the international public switched telephone/data network..... | 3 | +| 4 | General maintenance principles..... | 4 | +| 5 | Lining-up and maintaining public switched telephone/data circuits ..... | 4 | +| 6 | Lining-up and maintaining aeronautical satellite circuits..... | 4 | +| 6.1 | Control, sub-control and responsibilities..... | 4 | +| 6.1.1 | General..... | 4 | +| 6.1.2 | Assignment of control stations ..... | 4 | +| 6.1.3 | Assignment of sub-control stations ..... | 4 | +| 6.1.4 | Responsibilities of control and sub-control station ..... | 4 | +| 6.2 | Transmission characteristics ..... | 5 | +| 6.3 | Lining-up procedures..... | 5 | +| 6.4 | Fault reporting procedures ..... | 5 | +| 6.5 | Maintenance procedures ..... | 5 | +| 7 | Maintenance organization for aeronautical satellite system..... | 6 | +| 7.1 | Maintenance organization as applicable to Inmarsat..... | 6 | +| 7.1.1 | Aircraft earth station maintenance responsibility ..... | 6 | +| 7.1.2 | Ground earth station maintenance responsibility..... | 6 | +| 7.1.3 | Network channel management system maintenance responsibility..... | 6 | +| 7.1.4 | Network operations centre maintenance responsibility..... | 6 | +| 7.2 | Cooperation between the general maintenance organization
(Recommendation M.710 [5]) and the aeronautical satellite maintenance
organization ..... | 7 | + + + +# **MAINTENANCE ASPECTS OF AERONAUTICAL MOBILE TELECOMMUNICATION SERVICE VIA SATELLITE** + +*(1992; revised in 1997)* + +## **1 General** + +### **1.1 Scope** + +The purpose of this Recommendation is to describe the special maintenance procedures and facilities that are required for the maintenance of the Inmarsat aeronautical mobile telecommunication system via satellite, and to define interrelationship and interworking issues of such systems with terrestrial voice and data public/private networks. Wherever possible, the standard maintenance procedures and facilities specified in the M- and O-Series Recommendations, and appropriate X-Series Recommendations for data should be followed for the maintenance of these systems. + +### **1.2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation M.715 (1988), *Fault report point (circuit)*. +- [2] CCITT Recommendation M.716 (1988), *Fault report point (network)*. +- [3] CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network*. +- [4] CCITT Recommendation M.1140 (1992), *Maritime mobile telecommunication services via satellite*. +- [5] CCITT Recommendation M.710 (1988), *General maintenance organization for the international automatic and semi-automatic telephone service*. +- [6] ITU-T Recommendation F.127 (1996), *Operational procedures for interworking between the international telex service and the service offered by the Inmarsat-C system*. +- [7] ITU-T Recommendation X.25 (1996), *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*. + +## **2 Available services** + +The aeronautical mobile telecommunication system is intended for the provision of telephone, fax and data communication services to and from aircraft. The range of possible applications for these services includes airline crew and passenger communications (public correspondence), airline operations communications, air traffic control services and distress urgent/safety calls. + +## **3 System configuration** + +### **3.1 Aeronautical satellite system** + +The major elements of the aeronautical satellite system are as follows (see Figure 1): + +- a) the space segment including satellites (one for each ocean region); +- b) the Network Channel Management System (NCMS) for each satellite region; +- c) aeronautical Ground Earth Stations (GESs); +- d) Aircraft Earth Stations (AESs). + +#### **3.1.1 Space segments** + +The space segment comprises the satellite communications transponder(s) for each ocean region and associated frequency bands assigned for use by the aeronautical mobile-satellite system. The ocean regions are the Atlantic East, the Atlantic West, the Pacific and the Indian Ocean. + +#### **3.1.2 Aircraft Earth Station (AES)** + +An aircraft earth station interfaces with the space segment (at L-band) for communications with aeronautical ground earth stations, for the purpose of setting up communication with the existing airborne equipment, and with crew and passenger telephone, packet and circuit mode (Recommendation V.22) data, positioning and other avionics equipment, in accordance with the relevant technical and operational requirements. + +The AES may have various combinations of voice and/or data channels/circuits in typical configurations that define its class and transmission capabilities. The AES interfacing to voice and data terminations can also vary from a simple telephone to complex PBX-like arrangements for voice/circuit mode data and/or a number of packet-mode (ISO 8208) DTEs individually addressable. + +#### **3.1.3 Aeronautical Ground Earth Station (GES)** + +An aeronautical ground earth station interfaces with the space segment (at C-band and L-band), on the one hand, and with the fixed voice and data networks on the other hand. It operates in accordance with the relevant technical and operational requirements for communications with AESs. + +Each GES contains access control and signalling equipment which controls access to the satellite communication system and also acts as a gateway, interfacing with the PSTN and PSPDN or private data network communication links. The GES forms the link between the ground fixed network subscribers and airborne users. + +![Figure 1/M.1160 – Configuration of an aeronautical GES and Aircraft Earth Station. The diagram shows two main components: the Aeronautical (Ground) Earth Station (GES) and the Aircraft Earth Station (AES), connected by a satellite communication link. The GES includes terrestrial networks, telephony and data units, AERO channel units, NCMS Aero, IF combiners and splitters, C-band and L-band equipment, and an AES Test terminal. The AES includes a PBX with RF, IF, and CP units, connected to crew and passenger telephones and terminals. A legend defines the symbols for Earth Station and Satellite, and the abbreviations for AES, RF, IF, CP, NCMS, and PBX.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +**Legend:** + +- Earth Station (Symbol: circle with cross) +- Satellite (Symbol: circle with antenna) +- AES Aircraft Earth Station +- RF Radio Frequency (equipment) +- IF Intermediate Frequency (equipment) +- CP Channel Processing (equipment) +- NCMS Network Channel Management System +- PBX Private Branch Exchange + +Figure 1/M.1160 – Configuration of an aeronautical GES and Aircraft Earth Station. The diagram shows two main components: the Aeronautical (Ground) Earth Station (GES) and the Aircraft Earth Station (AES), connected by a satellite communication link. The GES includes terrestrial networks, telephony and data units, AERO channel units, NCMS Aero, IF combiners and splitters, C-band and L-band equipment, and an AES Test terminal. The AES includes a PBX with RF, IF, and CP units, connected to crew and passenger telephones and terminals. A legend defines the symbols for Earth Station and Satellite, and the abbreviations for AES, RF, IF, CP, NCMS, and PBX. + +NOTE 1 – $+R'$ dBr and $-S'$ dBr in the aeronautical ground earth station correspond to the levels $+R'$ dBm and $-S'$ dBm using a modulation signal with the level of 0 dBm0. + +NOTE 2 – $+R$ dBr and $-S$ dBr in the aeronautical earth station correspond to the levels of $+R$ dBm and $-S$ dBm using a modulation signal with a level of 0 dBm0. + +NOTE 3 – See Figure 1/M.1140 [4] for 4-wire test access points. + +NOTE 4 – Interface protocols for data are those given in Recommendations F.127 [6] and X.25 [7]. + +**Figure 1/M.1160 – Configuration of an aeronautical GES and Aircraft Earth Station** + +#### 3.1.4 Test Terminal (TT) + +A test terminal is an aircraft earth station, installed at an aeronautical GES, used for test purposes: it can be either a real AES or special equipment simulating all AES capabilities for testing purposes. + +#### 3.1.5 Network Channel Management System (NCMS) + +Each ocean region is served by a NCMS which manages circuit mode channel resources and controls access of the AES to the system. It can be independent of the GES or co-located at designated ground earth stations. A network channel management system interfaces via the space segment (at C-band) with the GESs for the purpose of managing a common pool of circuit mode satellite channels for optional frequency reuse between spot beams of the same region or between different regions. Alternatively, NCMS functions may be incorporated into all GESs of a region until a full NCMS becomes operational for that region. This becomes possible since in such cases a fixed pool of channels is permanently allocated to each GES. + +### 3.2 Interconnection with the international public switched telephone/data network + +A circuit between the International Switching Centre (ISC) and aeronautical GES is considered as equivalent to an international public switched telephone/data circuit. + +X.75 links are used for interfacing with PSDN sub-networks, while X.25 links may be used for directly accessing private service providers or airline networks. + +## **4 General maintenance principles** + +In an international connection which includes an Inmarsat aeronautical earth station, the aeronautical satellite system may be regarded, from a transmission point of view, as a national network. Nevertheless, it should be noted that the aeronautical satellite circuit is set up between the aeronautical ground earth station and the aircraft earth station on a demand assignment basis. Therefore, an aeronautical ground earth station in the aeronautical satellite system may not have direct or full responsibility for the maintenance of a particular aeronautical satellite circuit and a particular aircraft earth station all of the time. The operation and maintenance of the overall aeronautical satellite system is the responsibility of the aeronautical satellite system operator, e.g. Inmarsat. + +The maintenance organization in each participating Administration is, in general, responsible for the maintenance of the aeronautical satellite circuit usually under the guidance and coordination of the Inmarsat Network Operations Center (NOC)1 and/or Network Channel Management System (NCMS). + +## **5 Lining-up and maintaining public switched telephone/data circuits** + +The circuit between the International Switching Centre (ISC) and the aeronautical ground earth station should be lined up and maintained in accordance with those M-Series Recommendations appropriate to international public switched telephone/data circuits. + +## **6 Lining-up and maintaining aeronautical satellite circuits** + +### **6.1 Control, sub-control and responsibilities** + +#### **6.1.1 General** + +The assignment of control and sub-control stations and respective responsibilities must address the configuration of the aeronautical satellite system. A control station must be assigned as regards circuits, and, in addition, sub-control stations as required for efficient maintenance. + +#### **6.1.2 Assignment of control stations** + +The aeronautical ground earth station is the control station for the aeronautical satellite circuit. + +#### **6.1.3 Assignment of sub-control stations** + +In principle, the aircraft earth station should act as the sub-control station for the aeronautical satellite circuit. However, the required staff and facilities may not be available on an aircraft to meet the circuit sub-control responsibilities. + +#### **6.1.4 Responsibilities of control and sub-control station** + +Control stations dealing with aeronautical satellite circuits should fulfil the responsibilities of control stations as defined in the M-Series Recommendations. The same applies to sub-control stations. + +--- + +1 Previously called Network Control Centre (NCC). + +### 6.2 Transmission characteristics + +The transmission characteristic and maintenance parameters for GES-AES control and communication (voice and data) channels and the Bit Error Rates shall be as specified by Inmarsat aeronautical system definition and maintenance procedures for such channels. + +The overall attenuation/frequency limits are shown in Table 1. + +**Table 1/M.1160 – Attenuation/frequency limits** + +| Transmission parameters | Maintenance limits (dB) | +|------------------------------------------------------------------------------------------------|-------------------------| +| Attenuation frequency relative to the attenuation at reference frequency | (Note) | +| 300 to 400 Hz | –2.0 to +4.4 | +| 400 to 600 Hz | –1.2 to +2.6 | +| 600 to 2400 Hz | –1.2 to +1.2 | +| 2400 to 2700 Hz | –1.2 to +2.6 | +| 2700 to 3400 Hz | –1.2 to +4.4 | +| NOTE – The 1020 Hz reference tone used for measuring the attenuation shall be set at –10 dBm0. | | + +### 6.3 Lining-up procedures + +Special Line-up Procedures defined by Inmarsat for starting or restoring service need to be followed to assure: + +- proper broadcast of satellite network configuration parameters to AESs in region; +- final adjustments of GES e.i.r.p. and frequency parameters under the supervision of the Inmarsat network operations centre; +- proper interworking with other GESs in region; +- that AFC pilot receivers have locked and AFC loops are established; +- proper operation of all channel types and proper functioning of basic data and voice services in both directions (Air-to-Ground and Ground-to-Air), etc. + +### 6.4 Fault reporting procedures + +Fault report points (circuit) should be identified in accordance with Recommendation M.715 [1]. + +Fault report points (network) should be identified in accordance with Recommendation M.716 [2]. One such point is required for the aeronautical satellite system and is assigned to the network operations centre. However, general international networking problems should in the first instance be referred to the fault report points (network) concerned. Inmarsat network or system operating procedures are applicable giving a detailed explanation of fault reporting procedures. + +Exchange of contact point information should be in accordance with Recommendation M.1510 [3]. + +### 6.5 Maintenance procedures + +It is desirable that routine measurements on the aeronautical satellite circuits be performed to confirm that the transmission parameter limits continue to be maintained. These maintenance procedures are important with respect to the aeronautical ground earth station transmission performance. + +## **7 Maintenance organization for aeronautical satellite system** + +### **7.1 Maintenance organization as applicable to Inmarsat** + +The maintenance responsibility within the aeronautical satellite network is divided among the aircraft earth station, the ground earth station, the network channel management system, and the network operations centre. + +#### **7.1.1 Aircraft earth station maintenance responsibility** + +The aircraft earth station must be capable of communicating reliably with the ground earth station and may act as a sub-control station with responsibilities to the GES. As a sub-control station, it is responsible for reporting noticeable degradations in the aeronautical satellite circuits to the GES and for reporting AES-related problems to manufacturers or system integrators. + +#### **7.1.2 Ground earth station maintenance responsibility** + +The ground earth station provides interworking communication functions and has the overall coordination responsibility between the GES and the international public voice/data network, including the responsibility of reporting problems to the network coordination station and the network operations centre as required. It serves as a gateway between the terrestrial networks and the AESs within the coverage area of the particular satellite region. In order to perform its functions, database log-on updates are exchanged between it and the NCMS of its ocean region. As such it has significant capability of detecting and reporting failures of its own equipment. + +#### **7.1.3 Network channel management system maintenance responsibility** + +The network channel management system provides communication, limited monitoring, maintenance and support functions within the aeronautical satellite system. + +- a) Communication NCMS functions include: + - assigning circuit mode channels to a GES as needed according to traffic load by optimizing space segment (channel) resources within spot beams of its region and between adjacent regions; + - maintaining a list of active AESs and updating GESs of its ocean region with this information, communicating also with NCMSs of other regions for their proper global update. +- b) Maintenance and monitoring functions may include: + - assisting in performing routine system tests; + - providing minimum capability of the GES performance monitoring in its region and corresponding alarms. +- c) Other supporting functions include: + - coordinating network actions in its ocean region in case of serious failure or GES outage; + - providing performance reports for its region. + +#### **7.1.4 Network operations centre maintenance responsibility** + +The network operations centre provides administrative, operational and maintenance functions within the aeronautical satellite network. + +- a) Administrative functions include: + - acting as the fault report point (network); + +- preparing controlling and disseminating system information; + - providing a focal point for aircraft (or their agents, etc.), Administrations or service providers. +- b) Routine and normal operational functions include: +- liaising with the various space segment suppliers; + - monitoring, identifying and clearing of unauthorized transmissions; + - scheduling and coordinating the bringing-into-service of GESs and network channel management system; + - carrying out monitoring of transmission parameters and collecting call-record data for statistic, charging and fault analysis; + - analysing traffic and performance data provided by network coordination stations and GESs. +- c) Emergency and/or corrective (maintenance) actions, in case of: +- space segment failures; + - extended channel management system failures; + - failures or outages of individual GESs; + - incorrect operation of AESs; + - interference in the network of any kind. + +### **7.2 Cooperation between the general maintenance organization (Recommendation M.710 [5]) and the aeronautical satellite maintenance organization** + +Figure 2 illustrates the interrelationship between the general maintenance organization and the aeronautical satellite maintenance organization (Inmarsat). + +![Diagram showing the interrelationship between the general maintenance organization and the aeronautical satellite maintenance organization (Inmarsat).](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the interrelationship between the general maintenance organization and the aeronautical satellite maintenance organization (Inmarsat). It is divided into two main sections by a horizontal dashed line, with the top section representing the aeronautical satellite maintenance organization and the bottom section representing the general maintenance organization. + +**Aeronautical satellite maintenance organization (Inmarsat):** + +- Aircraft earth station manufacturer's or agent's maintenance organization +- Aircraft earth station +- Ground earth station (containing Satellite termination and Terrestrial termination) +- Network operations centre +- Network channel management system + +**General maintenance organization (Rec. M.710 [5]):** + +- International switching centre + +**Interconnections:** + +- Exchange of maintenance information between the organizations:** Indicated by a double-headed arrow with a hollow diamond. This occurs between the Network channel management system and the Ground earth station, and between the General maintenance organization and the Aeronautical satellite maintenance organization. +- Exchange of maintenance information within the organization:** Indicated by a solid double-headed arrow. This occurs between the Network operations centre and the Network channel management system, between the Network operations centre and the Ground earth station, and between the Aircraft earth station and the Aircraft earth station manufacturer's or agent's maintenance organization. + +T0406320-96 + +Diagram showing the interrelationship between the general maintenance organization and the aeronautical satellite maintenance organization (Inmarsat). + +**Figure 2/M.1160 – Interrelationship between the general maintenance organization (Recommendation M.710 [5]) and the aeronautical satellite maintenance organization (Inmarsat)** + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.1170-199704-I_PDF-E/raw.md b/marked/M/T-REC-M.1170-199704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b0d9ea3d6a5bff2e75890d08e8324686d88bee7a --- /dev/null +++ b/marked/M/T-REC-M.1170-199704-I_PDF-E/raw.md @@ -0,0 +1,393 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1170** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/97) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Mobile telecommunication systems and services + +--- + +**Maintenance aspects of mobile digital +telecommunication service via satellite** + +ITU-T Recommendation M.1170 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **ITU-T RECOMMENDATION M.1170** + +# **MAINTENANCE ASPECTS OF MOBILE DIGITAL TELECOMMUNICATION SERVICE VIA SATELLITE** + +## **Summary** + +This Recommendation describes general maintenance aspects of mobile-satellite digital systems for maritime and/or land use predominantly based on INMARSAT-M and INMARSAT-B maintenance requirements. + +### **Source** + +ITU-T Recommendation M.1170 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 19th of April 1997. + +### **Keywords** + +INMARSAT-B, INMARSAT-M; Maintenance Aspects, Mobile Satellite Digital Systems. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 1 General..... | 1 | +| 1.1 Scope..... | 1 | +| 1.2 References..... | 1 | +| 2 Available services..... | 1 | +| 3 System configuration..... | 2 | +| 3.1 Space segment..... | 2 | +| 3.2 Earth facilities..... | 2 | +| 3.2.1 Land Earth Station (LES) ..... | 2 | +| 3.2.2 Mobile Earth Station (MES)..... | 4 | +| 3.2.3 Ship Earth Station (SES) ..... | 4 | +| 3.2.4 Test terminal..... | 4 | +| 3.2.5 Network Coordination Station (NCS) ..... | 4 | +| 4 General maintenance principles..... | 4 | +| 5 Lining-up and maintaining circuits..... | 4 | +| 5.1 Terrestrial circuits..... | 4 | +| 5.1.1 Lining-up and maintaining international public switched telephone circuits | 4 | +| 5.2 Mobile satellite digital circuits ..... | 5 | +| 5.2.1 Control, sub-control and responsibilities..... | 5 | +| 5.2.2 Transmission design characteristics ..... | 5 | +| 5.2.3 Fault reporting procedures..... | 5 | +| 6 Test facilities at mobile earth stations..... | 5 | +| 6.1 Automatic testing..... | 5 | +| 6.2 Manual testing..... | 5 | +| 7 Maintenance organization for the mobile satellite digital system..... | 6 | +| 7.1 Maintenance organization as applicable to the INMARSAT-B/M system..... | 6 | +| 7.1.1 Mobile Earth Station (MES)/Ship Earth Station (SES) maintenance responsibility..... | 6 | +| 7.1.2 Land Earth Station (LES) maintenance responsibility..... | 6 | +| 7.1.3 Network Coordination Station (NCS) maintenance responsibility ..... | 6 | +| 7.1.4 Network Operations Centre (NOC) maintenance responsibility ..... | 6 | +| 7.2 Cooperation between the general maintenance organization
(Recommendation M.710 [7]) and the maritime satellite maintenance organization. | 7 | + + + +# **MAINTENANCE ASPECTS OF MOBILE DIGITAL TELECOMMUNICATION SERVICE VIA SATELLITE** + +*(Geneva, 1997)* + +# **1 General** + +## **1.1 Scope** + +The purpose of this Recommendation is to describe general maintenance procedures and facilities that are required for the maintenance of the mobile digital telecommunication system via satellite (INMARSAT-M and INMARSAT-B, denoted as INMARSAT-M/B hereafter) and define interrelationship and interworking issues of such systems with terrestrial voice and data networks. Wherever possible, the standard maintenance procedures and facilities specified in the M- and O-Series Recommendations, and appropriate X-Series Recommendations for data should be followed for the maintenance of these systems. + +## **1.2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation M.715 (1988), *Fault report point (circuit)*. +- [2] CCITT Recommendation M.716 (1988), *Fault report point (network)*. +- [3] CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network*. +- [4] ITU-T Recommendation F.127 (1996), *Operational procedures for interworking between the international telex service and the service offered by the INMARSAT-C system*. +- [5] ITU-T Recommendation X.25 (1996), *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*. +- [6] CCITT Recommendation M.1140 (1992), *Maritime mobile telecommunication services via satellite*. +- [7] CCITT Recommendation M.710 (1988), *General maintenance organization for the international automatic and semi-automatic telephone service*. +- [8] CCITT Recommendation O.11 (1992), *Maintenance access lines*. + +## **2 Available services** + +The mobile digital telecommunication system is intended for the provision of telephone, facsimile, telex and data communication services. + +## **3 System configuration** + +The INMARSAT-M/B system consists of the following major elements per ocean region (see Figure 1): + +- a) the space segment including satellites; +- b) the Network Coordination Station (NCS); +- c) Land Earth Stations (LESs); +- d) Mobile Earth Stations (MESs); +- e) Ship Earth Station (SES); + +### **3.1 Space segment** + +The space segment comprises the satellite communications transponder(s) for each ocean region and associated frequency bands assigned for use by the INMARSAT-M/B system. The ocean regions are the Atlantic East, the Atlantic West, the Pacific and the Indian Oceans. + +## **3.2 Earth facilities** + +### **3.2.1 Land Earth Station (LES)** + +A land earth station in the mobile-satellite service is an earth station which interfaces with the space segment (at C-band and L-band) on the one hand and with the fixed voice and data networks on the other hand. + +![Configuration of INMARSAT-M/B system diagram showing Land Earth Station (LES), Mobile Earth Station (MES)/Ship Earth Station (SES), and their internal components connected via a satellite communication link.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The diagram illustrates the configuration of the INMARSAT-M/B system. It consists of two main stations: the Land Earth Station (LES) and the Mobile Earth Station (MES) / Ship Earth Station (SES), connected by a satellite communication link. + +**Land Earth Station (LES):** This station is connected to terrestrial networks for telephony, facsimile, telex, and data. It contains a block for "Telephony facsimile telex and data" which outputs signals at levels $+R'$ dBr and $-S'$ dBr (Note: these correspond to $+R'$ dBm and $-S'$ dBm using a modulation signal with the level of 0 dBm0). These signals pass through "Channel units" and then to an "IF combine and splitters" block. Below this block is a "MES/SES Test" unit. The "IF combine and splitters" block connects to "C-band equip" and "L-band equip", which in turn connect to an earth station antenna. This antenna communicates with a satellite via a "C-band" uplink and an "L-band" downlink. + +**Mobile Earth Station (MES) / Ship Earth Station (SES):** This station receives signals from the satellite via an "L-band" antenna. The signal passes through a block labeled "R F I F C P" (Radio Frequency, Intermediate Frequency, Channel Processing). Below this block is the "MES/SES" unit. The "R F I F C P" block connects to four terminals: "Telephone terminal", "Facsimile terminal", "Telex terminal", and "Data terminal". + +**Communication Link:** The link between the LES and the MES/SES is labeled "Communication link" and involves a satellite. + +**Legend:** + +- RF Radio Frequency (equipment) +- IF Intermediate Frequency (equipment) +- CP Channel Processing (equipment) +- Earth station (represented by a circle with a cross) +- Satellite (represented by a circle with a dot) + +**System Definitions:** + +- MES/SES:** The Mobile Earth Station or Ship Earth Station. +- Mobile satellite digital circuit:** The path from the LES to the MES/SES. +- Mobile local system:** The internal components of the MES/SES connecting to the terminals. +- Mobile satellite digital system:** The combination of the mobile satellite digital circuit and the mobile local system. + +T0406470-96 + +Configuration of INMARSAT-M/B system diagram showing Land Earth Station (LES), Mobile Earth Station (MES)/Ship Earth Station (SES), and their internal components connected via a satellite communication link. + +NOTE – $+R'$ dBr and $-S'$ dBr in the land earth station correspond to the levels $+R'$ dBm and $-S'$ dBm using a modulation signal with the level of 0 dBm0. + +Figure 1/M.1170 – Configuration of INMARSAT-M/B system + +### **3.2.2 Mobile Earth Station (MES)** + +A mobile earth station in the mobile-satellite service is a station which provides an interface for connection of a mobile satellite digital circuit to a mobile local system (see Figure 1). This generic definition applies to both maritime and land mobile (INMARSAT-M) terminals. + +### **3.2.3 Ship Earth Station (SES)** + +A ship earth station in the mobile-satellite service is a maritime station which provides an interface for connection of a mobile satellite digital circuit to a mobile local system (see Figure 1). + +### **3.2.4 Test terminal** + +A test terminal is a ship or mobile earth station installed at each LES and used for test purposes. In this regard, the maritime test terminal may carry out some tests, normally considered to be within the province of a sub-control station, on behalf of a mobile earth station. + +### **3.2.5 Network Coordination Station (NCS)** + +Each ocean region is served by an NCS which manages common space segment resources and controls access of MESs to the system. The NCS provides central control of satellite channel resources to LESs and MESs/SESs within an ocean region. It maintains a pool of frequencies, assigns frequencies on demand to LESs, and supervises and monitors the use of these frequencies. In addition, it administers common data, e.g. MES/SES identify lists and system parameters, and is responsible for collection of call-record information for statistical purposes. + +## **4 General maintenance principles** + +In an international connection which includes a mobile earth station, the mobile satellite digital system may be regarded, from a transmission point of view, as analogous to a national network, and the mobile local system as analogous to a subscriber terminal within that network. Nevertheless, it should be noted that the mobile satellite digital circuit is set up between the land earth station and the mobile earth station on a demand assignment basis. Therefore, a land earth station in a mobile system may not have direct responsibility for the maintenance of a particular mobile satellite digital circuit and a particular mobile earth station all of the time. The operation and maintenance of the overall INMARSAT mobile satellite digital system is the responsibility of the mobile satellite digital system operator. + +The maintenance organization in each participating Administration is, in general, responsible for the maintenance of the mobile satellite digital circuit usually under the guidance and coordination of the Network Operations Centre (NOC) and/or NCS. + +## **5 Lining-up and maintaining circuits** + +## **5.1 Terrestrial circuits** + +### **5.1.1 Lining-up and maintaining international public switched telephone circuits** + +The circuit between the international telephone switching centre and the land earth station should be lined up and maintained in accordance with those M-Series Recommendations appropriate to international switched telephone/facsimile/data circuits and specific procedures of the INMARSAT mobile satellite system operator. + +## **5.2 Mobile satellite digital circuits** + +### **5.2.1 Control, sub-control and responsibilities** + +##### **5.2.1.1 General** + +The assignment of control and sub-control stations and respective responsibilities must be addressed according to the configuration of the mobile satellite digital system. A control station must be assigned to each circuit and, in addition, sub-control stations as required for efficient maintenance. + +##### **5.2.1.2 Assignment of control stations** + +The land earth station is the control station for the mobile satellite digital circuit. + +##### **5.2.1.3 Assignment of sub-control stations** + +In principle, the ship earth station or the mobile earth station should act as the sub-control station for the mobile satellite digital circuits. However, the required staff and facilities may not always be available to meet the circuit sub-control responsibilities. + +##### **5.2.1.4 Responsibilities of control and sub-control station** + +Control stations dealing with mobile satellite digital circuits should fulfill the responsibilities of control stations as defined in the M-Series Recommendations. The same applies to sub-control stations. + +#### **5.2.2 Transmission design characteristics** + +The transmission design characteristics for such satellite channels are defined by the satellite system operator for the INMARSAT-M/B system. + +### **5.2.3 Fault reporting procedures** + +Fault report points (circuits) should be identified in accordance with Recommendation M. 715 [1]. Fault report points (network) should be identified in accordance with Recommendation M.716 [2]. One such point for the INMARSAT networks is the Network Operations Centre (NOC). However, international networking problems should be referred to the fault report points (network) concerned. Exchange of contact point information should be in accordance with Recommendation M.1510 [3]. + +## **6 Test facilities at mobile earth stations** + +## **6.1 Automatic testing** + +Mobile units operated in mobile environments would not in general have personnel with adequate expertise for testing and maintaining equipment connected to the international network. Therefore, remote automatic testing of a mobile earth station would be possible by including automatic test equipment at the land earth station and the mobile earth station. The required facilities include quiet termination test line and loop around test line as given in Recommendation O.11 [8]. + +## **6.2 Manual testing** + +It should be possible to undertake manual testing of the transmission performance of mobile earth stations. This type of test is essential when a mobile earth station is being lined-up after it has been repaired. It should be possible to initiate the test either from the land earth station or from the mobile earth station. + +## **7 Maintenance organization for the mobile satellite digital system** + +## **7.1 Maintenance organization as applicable to the INMARSAT-B/M system** + +The maintenance responsibility within a mobile satellite digital network is divided among the mobile earth station, the land earth station, the network coordination station, and the network operations centre. + +### **7.1.1 Mobile Earth Station (MES)/Ship Earth Station (SES) maintenance responsibility** + +The mobile earth station must be capable of communicating reliably with the land earth station and may act as a sub-control station with responsibilities to the land earth station. As a sub-control station, it is responsible for reporting noticeable degradation in the mobile satellite digital circuits to the land earth station and for reporting mobile earth station problems to the manufacturer's or mobile's maintenance agent. + +### **7.1.2 Land Earth Station (LES) maintenance responsibility** + +The land earth station provides communication functions and has the overall coordination responsibility between the mobile earth station and the international public switched telephone network, and the responsibility of reporting problems to the network coordination station and the network operations centre as required. + +### **7.1.3 Network Coordination Station (NCS) maintenance responsibility** + +The network coordination station provides communication, maintenance, monitoring and support functions within the mobile satellite digital system. + +- a) Communication functions include: + - transmitting the signalling channel to the mobile earth station; + - assigning communication channels on demand; + - maintaining a list of busy mobile earth stations. +- b) Maintenance and monitoring functions include: + - assisting in performing routine system tests; + - monitoring the performance of land earth station; + - monitoring, identifying and clearing of unauthorized transmissions. + +### **7.1.4 Network Operations Centre (NOC) maintenance responsibility** + +The operations centre provides administrative, operational and maintenance functions within the mobile satellite digital network. + +- a) Administrative functions include: + - acting as the fault report point; + - preparing, controlling and disseminating system information. +- b) Routine and normal operational tasks include: + - carrying out some limited monitoring of transmission parameters; + - analyzing traffic and performance data provided by network coordination stations and land earth stations. +- c) Emergency and/or corrective actions, including, as required, the issue of broadcast network advisory message to mobile earth stations, in case of: + - space segment failures; + +- failures of individual land earth stations; +- incorrect operation of mobile earth stations; +- interference in the network. + +## 7.2 Cooperation between the general maintenance organization (Recommendation M.710 [7]) and the maritime satellite maintenance organization + +Figure 2 illustrates the interrelationship between the general maintenance organization and the mobile satellite maintenance organization (INMARSAT). + +![Diagram illustrating the interrelationship between the general maintenance organization and the mobile satellite maintenance organization (INMARSAT).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the interrelationship between the general maintenance organization and the mobile satellite maintenance organization (INMARSAT). It is divided into two main sections by a horizontal dashed line: the Mobile satellite maintenance organization (top) and the General maintenance organization (Rec. M.710 [7]) (bottom). + +**Mobile satellite maintenance organization (top section):** + +- A box labeled "MES/SES manufacturer's or agent's maintenance organization" is connected to a box labeled "Mobile earth station/Ship earth station" by a double-headed arrow. +- The "Mobile earth station/Ship earth station" is connected to a box labeled "Land earth station" by a double-headed arrow. +- The "Land earth station" is connected to a box labeled "Network operations centre" by a double-headed arrow. +- The "Network operations centre" is connected to a box labeled "Network coordination station" by a double-headed arrow. + +**General maintenance organization (Rec. M.710 [7]) (bottom section):** + +- A box labeled "International switching centre" is connected to the "Land earth station" by a double-headed arrow. + +**Inter-organization connections:** + +- The "Land earth station" is split into two sub-sections: "Satellite termination" (top) and "Terrestrial termination" (bottom). +- The "Network coordination station" is connected to the "Terrestrial termination" section of the "Land earth station" by a double-headed arrow. +- A vertical double-headed arrow on the right side of the dashed line connects the "Mobile satellite maintenance organization" and the "General maintenance organization (Rec. M.710 [7])". + +**Legend:** + +- $\longleftrightarrow$ Exchange of maintenance information between the organizations +- $\leftrightarrow$ Exchange of maintenance information within the organization + +T0406480-96 + +Diagram illustrating the interrelationship between the general maintenance organization and the mobile satellite maintenance organization (INMARSAT). + +**Figure 2/M.1170 – Interrelationship between the general maintenance organization (Recommendation M.710 [7]) and the mobile satellite maintenance organization (INMARSAT)** + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.1230-199605-I_PDF-E/raw.md b/marked/M/T-REC-M.1230-199605-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..af5b5d397d7e419c88b472844796f2524a8b2fa7 --- /dev/null +++ b/marked/M/T-REC-M.1230-199605-I_PDF-E/raw.md @@ -0,0 +1,464 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1230** + +(05/96) + +SERIES M: MAINTENANCE: INTERNATIONAL +TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, +TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS +International public telephone network + +--- + +**Method to improve the management +of operations and maintenance processes +in the International Telephone Network** + +ITU-T Recommendation M.1230 + +(Previously «CCITT Recommendation») + +--- + +# ITU-T M-SERIES RECOMMENDATIONS **MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation M.1230 was revised by ITU-T Study Group 4 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 12th of May 1996. + +--- + +## NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +© ITU 1996 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------------------------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 General ..... | 1 | +| 3 Assessment of network performance from the point of view of maintenance ..... | 2 | +| 4 Major NP parameters for end-to-end measurements ..... | 3 | +| 5 Review of present methods for assessing overall (end-to-end) network performance ..... | 4 | +| 5.1 Test calls methods (intrusive measurements) ..... | 4 | +| 5.2 Service Quality observations (non-intrusive measurements) ..... | 5 | +| 5.3 Considerations of the methods of network performance assessment ..... | 6 | +| 6 General method for the optimization of the Operations and Maintenance (O&M) processes ..... | 6 | +| Annex A – Example of Context Difficulty Index (CDI) in an O&M environment where transmission aspects are predominant ..... | 8 | +| References ..... | 9 | + +## **ABSTRACT** + +This Recommendation describes general guidelines for Telecommunications Operators in order that they can improve the QOS and NP through the optimization of Operation and Maintenance (O&M) processes focusing on the customer satisfaction of the telephone service. The proposed method foresees the correlation between the assessment performance results of the international telephone network with a general index which represents the difficulty levels of O&M environment. + +## **KEYWORDS** + +Context Difficulty Index (CDI), Customer, Maintenance, Network Performance (NP), Operations, Operations and Maintenance (O&M) processes, Quality of Service (QOS), Telecommunications Operator (TO) – Administrations, ROAs, Carriers, etc. + + + +# METHOD TO IMPROVE THE MANAGEMENT OF OPERATIONS AND MAINTENANCE PROCESSES IN THE INTERNATIONAL TELEPHONE NETWORK + +*(Melbourne, 1988; revised in 1996)* + +## 1 Scope + +This Recommendation provides a reference model which includes both the description of the main parameters and different methods to assess the network performance. The description of a Context Difficulty Index (CDI) which is related to several components of the network and the O&M environment is also provided. It is possible to evaluate the service level performance from CDI and thus decide for any change or intervention as required to improve the perceived quality of the service to the customer. + +It is not the intention of this Recommendation to: + +- i) suggest any particular method or technology for the assessment of the network performance; +- ii) standardize any specific O&M process (e.g. internal organization, O&M procedure, etc.); +- iii) establish any specific objectives, target and thresholds for QOS and NP parameters; +- iv) set any level of Customer Satisfaction. + +The choice or decision on all the above issues is left to individual TO or to specific arrangements between TOs (e.g. when TOs jointly establish formal Service Quality Agreements with the major aim to develop mutually acceptable performance standards and to enable customer expectations to be met [14]). + +## 2 General + +With the increased liberalization and consequent competitive telecommunication scenarios, there is an increased need to find out in various ways how the network is performing to meet customer expectation. All Network and/or Service Providers, who in the past provided only network capacity and then maintained performance level by using different maintenance methods specified in ITU-T Recommendations, are now more and more focused on the improvement of NP and QOS1) as experienced by customers. + +To meet these main objectives, each TO has introduced and developed a wide range of test procedures and quality assessment methods2) in order to test the network both objectively and subjectively and to ensure a better and better QOS to their customers [1] to [20]. + +It is also very important to note that modern telecommunication systems have a great deal of built-in facilities through which it is possible to ensure a continuous and automatic supervision of performance parameters. + +--- + +1) QOS is defined as “the collective effect of service performance which determines the degree of satisfaction of a user of the service” [16]. Thus QOS is of concern to the user of the Service Provider. When the Network Provider is also the Service Provider he is responsible for the QOS. + +2) Continuous interrelationship and exchange of information in this area is necessary between ITU-T SG 4 and SG 2. In fact many Recommendations of E-Series describe QOS and NP concepts, parameters and methods for their measurements and they also contain suggestions on how to establish Service Quality Agreements [14] and also Customer Satisfaction Point [13] between Telecommunications Operators. + +## 3 Assessment of network performance from the point of view of maintenance + +\*Network Performance (NP)\* is a statement of the performance of connection element or concatenation of connection elements employed to provide a service and it is defined and measured in terms of parameters which are meaningful to Network Providers for different purposes [16]. Furthermore, it is to be noted that NP is defined independently of terminal performance and customer's actions and it is also service independent in that it must be able to support all the services the particular network is required to transport. + +The QOS experienced by a customer is a very broad concept and depends on a combination of factors some of which are not under the direct responsibility of maintenance staff, for example: + +- calling and called customer behaviour (i.e. percentage of non-successful calls related to premature abandonment or not answered calls for various reasons such as ring tone no answer, busy tone received or subscriber busy, etc.); +- planning and provisioning of the network and whether sufficient network resources (i.e. circuits, switching equipment) are provided to meet the number of call attempts by customers (e.g. percentage of non-successful calls due to lack of trunks/circuits); +- the degree to which network management or any other control system or tool is employed. + +It should be emphasized that the assessment of network performance is of primary importance to Network Providers for the “efficient maintenance” of their international telephone network [19]. + +Therefore, it is very important to assess the network performance through end-to-end measurements and to collect all results in order to activate any corrective maintenance action as needed to re-establish the level of performance as required. + +From the point of view of Maintenance, the assessment of international telephone network performance involves a measurement of the capability of the overall network (end-to-end, i.e. international section plus two national sections), to establish a switched connection of good transmission quality whenever required. + +The general reference model for overall (end-to-end) measurements is reported in Figure 1. + +![Diagram of the reference model for overall (end-to-end) measurements. It shows a Customer connected to a CTE (Customer's Terminal Equipment), which is connected to a National network (LE + TE). This is followed by an International network (ISC, IN, ISC) and another National network (TE + LE). The CTE on the other side is connected to another Customer. The entire network section between the two CTEs is labeled 'Network' and 'End-to-end path'. A legend defines the abbreviations: CTE (Customer's Terminal Equipment), LE (Local Exchange), TE (Transit Exchange), ISC (International Switching Centre), and IN (International Network).](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +Diagram illustrating the reference model for overall (end-to-end) measurements. The diagram shows a Customer connected to a CTE (Customer's Terminal Equipment), which is connected to a National network (LE + TE). This is followed by an International network (ISC, IN, ISC) and another National network (TE + LE). The CTE on the other side is connected to another Customer. The entire network section between the two CTEs is labeled 'Network' and 'End-to-end path'. + +Legend: + +- CTE Customer's Terminal Equipment (e.g. telephone, data terminal, fax terminal, etc.) +- LE Local Exchange +- TE Transit Exchange +- ISC International Switching Centre +- IN International Network + +Diagram of the reference model for overall (end-to-end) measurements. It shows a Customer connected to a CTE (Customer's Terminal Equipment), which is connected to a National network (LE + TE). This is followed by an International network (ISC, IN, ISC) and another National network (TE + LE). The CTE on the other side is connected to another Customer. The entire network section between the two CTEs is labeled 'Network' and 'End-to-end path'. A legend defines the abbreviations: CTE (Customer's Terminal Equipment), LE (Local Exchange), TE (Transit Exchange), ISC (International Switching Centre), and IN (International Network). + +FIGURE 1/M.1230 +Reference model for overall (end-to-end) measurements + +## 4 Major NP parameters for end-to-end measurements + +According to existing Recommendations, the parameters essential to objectively measure the Quality of Service as perceived by customers, may be categorized into two main areas [12]: + +### a) *Call connectivity* + +The essential parameters required to assess the connectivity quality are: + +- Start Dial Signal Delay (SDSD); +- Call disposition (e.g. reasons for unsuccessful call completion, e.g. wrong number, unknown tone, congestion, etc.); +- Post Dialling Delay (PDD); +- Call Completion Rate [or Answer Seizure Ratio (ASR)]. + +Call failures are categorized as due to network faults, equipment failure and network congestion. + +### b) *Transmission quality* + +The essential parameters contributing to the transmission quality (call clarity) are: + +- Transmission loss; +- Attenuation distortion; +- Total distortion; +- Group delay distortion; +- Idle channel noise; +- Impulsive noise; +- Round-trip delay; +- Echo; +- Clipping. + +It is important to note that for compatibility between manufacturers and TOs, it is essential to have a common measurement methodology3). This will ensure that measured results are comparable between TOs and thus it will improve their cooperation in all joint activities and also the quality of the telephone service as offered to mutual customers. + +As examples of network parameters, a list of main parameters for voice and non-voice calls is given below. This is not an exhaustive list. + +#### *Voice* + +- Circuit loss; +- Circuit noise; +- Impulsive-noise; +- Cross-talk (unintelligible); +- Terminal balance; +- Echo, control devices, delay, loss, stability; +- Propagation time, digital processing; +- Impedance mismatch; +- Quantization, non-linear and attenuation distortions and bandwidth; +- Speech detectors parameters, switched loss clipping, interruptions, freeze-out, fading; +- Power loads on cables and carriers, leakage, imbalances. + +--- + +3) This requires further study/definition. + +#### *Non-voice* + +- Impulsive-noise, frame slips, jitter, hits, drop-outs, distortion, circuit loss, cross-talk, interruptions; +- Burst errors; +- Echo; +- Delay; +- Out of synchronism; +- Noise; +- Group delay distortion. + +## **5 Review of present methods for assessing overall (end-to-end) network performance** + +At present the following methods of measuring international telephone networks are available. + +### **5.1 Test calls methods (intrusive measurements)** + +There are currently four types of test calls which can be carried out both manually or automatically to assess the functioning of international circuits, namely [4]: + +#### a) *Type 1 test calls* + +These test calls are conducted between two directly connected international centres to verify that the transmission and signalling performance on an international circuit of a given group are satisfactory. + +#### b) *Type 2 test calls* + +These test calls are conducted between two international centres not directly connected to verify transit operational facilities of an intermediate international centre. + +#### c) *Type 3 test calls* + +These test calls are conducted from an international centre to a subscriber type number in the national network of the distant country (in general as a result of a particular kind of fault). + +#### d) *Subscriber-to-subscriber type test calls* + +These type of test calls are conducted with test equipment having the characteristics of an average subscriber line in one national network to similar equipment in the national network of a distant country. + +The main existing Recommendations that describe subscriber-to-subscriber end-to-end measurements are: + +- **Recommendation M.1235 – “Use of automatically generated test calls for assessment of network performance” [20]** + +This Recommendation describes the use of automatic subscriber-to-subscriber test calls performed either in system-independent test call generators and test call responders, or by built-in facilities performing the same functions. Call-through testing as described in this Recommendation, can be used to check the performance on routes, circuits, switches and associated equipment. It should be noted that these test calls programmes should be carried out both during non-busy and busy periods and they have to be carefully planned. This means they have to be agreed between TOs concerned in order to avoid any kind of interference by a contemporaneous use of the same test number for other utilization. In this Recommendation are also defined the criteria for the choice of the number of test calls to be generated towards each switched destination and as it is stated, this number is mainly dependent on the frequency of difficulties encountered towards a certain destination (i.e. fewer test calls are needed to identify the network performance level when the rate of difficulties encountered is high). + +- **Recommendation E.434 – “Subscriber-to-subscriber measurements of the public switched telephone network” [12]** + +This Recommendation defines the methods and processes for testing, the measurements required, the elements of an end-to-end system and the operation of an end-to-end system, and it also contains Recommendations to define interfaces and protocols. + +It is to be noted that also in this Recommendation the number of test calls depends on the parameters to be measured and the desired accuracy for those parameters. Further the number of test calls should be large enough to provide statistically valid results within the desired accuracy for each parameter measured, and small enough to allow the data to be collected over a fairly short period of time. Particular consideration should be given to trunk size of traffic volumes on the route when test call quantities are being determined. + +Another consideration (limitation), is to keep the best period for measurements relatively short to ensure the availability of the test device, and therefore to avoid conflicts that might result in the use of responders. It is important to observe that “such conflicts” could also have an impact on the accuracy of results as test calls may have failed to complete because the terminating responder was in use for a different test programme rather than a real network failure. + +In conclusion, also this method requires careful coordination and scheduling for test calls programmes between the TOs concerned. + +### **5.2 Service Quality observations (non-intrusive measurements)** + +Another way of supervising the total through connection capabilities of the network is to make Service Quality observations. The definition of “Service observation” [2] is the following: “Monitoring to obtain a complete or partial assessment of the quality of telephone calls, excluding test call”. + +There are three methods to perform service observations: + +- Manual observations – This is the monitoring of telephone calls by an observer without using any automatic data-recording machine. + +This method provides all the data required in specific tables, namely: Table 1/E.422 [3] and Table 1/E.423 [4]. With this method, observations can be carried out with a minimum of equipment. Furthermore observations can allow the detection of a number of abnormalities that cannot be detected automatically (e.g. very poor speech transmission, or difficulty with audible tones). + +- Semi-automatic observations – This is the monitoring of telephone calls using equipment that records some data automatically (e.g. equipment such as exchange, in which information being observed, number dialled by the subscriber, metering pulses and time of call, is recorded automatically on some means suitable for data processing). + +This method also provides all data required in Tables 1/E.422 and 1/E.423, but a greater accuracy compared with manual observation is possible because there is an automatic recording of the number dialled, the time of the call, etc. In addition, it is possible for the observer to devote greater attention to the more critical conditions being checked during observations of calls. + +- Automatic observations – This is the monitoring of telephone calls without an observer. + +This method allows: continuous observation, a larger sample, to process data automatically, etc. + +There are two types of automatic observations: + +- Internal automatic observations that can be made in the switching centre itself (on the incoming side or the outgoing side or in between). + +Main considerations of this method are: Only line signalling, such a seizure, answer, etc. can be monitored and also register signals as long as they do not pass through the exchange in an end-to-end signalling procedure; signals received are monitored if the exchange itself operates correctly in that respect and this also applies to the outgoing signal. + +This observation technique is described in Recommendation E.425 [6], where it is underlined that its major advantage is that a large volume of call records can be collected and because a large volume of data can be obtained, this allows a day-to-day evaluation of Network Performance. The type of data collected can be related to effective network problems and calling and called subscriber behaviour [Call Failure Code Analysis (CFCA)]. Nowadays, the usefulness of such CFCA for CCSS No. 7 analysis is more and more increasing in line with the worldwide introduction of CCSS No. 7 in the national and international networks. It is to be noted that daily analysis of this information is of great importance in trouble detection, and coupled with a good maintenance response, it represents a powerful means to provide the best quality of service. The disadvantage is that this method does not have the capability of detecting tones or speech and therefore cannot present a complete representation of all call dispositions. To overcome this disadvantage it is recommended to use this method with Recommendation E.422. + +- ii) External automatic observations that are made by means of monitoring equipment that is supervising the traffic on incoming and outgoing lines. With this technique all signalling signals can be monitored, the detection of tones, speech and data is possible if advanced equipment is used. It also provides the data required in Tables 2/E.422 and 2/E.423 and as its application is very flexible it can be used instead of manual or semi-automatic observation techniques. + +### **5.3 Considerations of the methods of network performance assessment** + +The attention of the TOs is drawn to the following: + +- 1) The above methods are not exclusive. The nature of information obtained (e.g. verification of call completion rate, transmission quality, influence of international and national sections) will depend on the method of Network Performance assessment employed. +- 2) While there is a recognized need to continuously assess the performance of the international telephone network, the actual method by which this is achieved depends upon the arrangements within and between TOs and on the switching technology employed. +- 3) The choice of methods is left to individual TOs, to decide on the basis of their own particular circumstances. Information obtained (e.g. verification of call completion rate, transmission quality, influence of international and national sections) will depend on the method of Network Performance assessment. + +## **6 General method for the optimization of the Operations and Maintenance (O&M) processes** + +Against the background of present network developments, the major aim of a TO is to move towards the implementation of integrated telecommunications and relevant management systems in order to properly manage the level of network performance and Quality of Service and optimizing the related costs for all the processes involved. + +This is very important for the overall O&M process where the performance of each constituent part is to be carefully handled in order to ensure efficiency and effectiveness of all resources (systems, personnel, internal organization, etc.) involved in the process. + +For example in the “maintenance” process the resources are represented by both the network and human resources. For the network the major components are: type and technological implementation of network elements (i.e. transmission and switching facilities, supervisory and measuring equipment). For human aspects the major components are: the staffing sufficiency and the skill levels. + +Thus for the O&M process it is necessary to: + +- 1) Manage the Network Performance (and then the QOS) level through the knowledge of the standards of different call connectivity and transmission quality parameters as measured utilizing one or a combination of the previous methods of network performance assessment as described in Clause 5. + +- 2) Manage the Operation and Maintenance performance through the knowledge of relevant appropriate parameters; for example the billing error ratio [11], the failure rate, the Mean Time to Repair (MTTR), the Service provisioning rate, the Directory response ratio, etc. [17], [18], [21]. +- 3) To define and utilize an overall index CDI (Context Difficulty Index) which represents the difficulty levels (i.e. the non-performance) for all processes/components involved in the O&M environment. An example of a CDI related to a particular “Transmission environment” is attached to this Recommendation as Annex A, where the most CDI significant components are defined and also its computations are shown. + +It is important to note that NP (QOS) varies inversely with CDI, e.g.: + +- when the environment is good (CDI low), NP (QOS) is high; +- when the environment is bad (CDI high), NP (QOS) is low. + +If the management capability of all components involved are comparable, the relationship of NP (QOS) and CDI is on the performance indifference curve as shown in Figure 2. However, there are some abnormal cases such as Group A and Group C. In Group A, the environment is bad (CDI high), but its NP (QOS) is high. This may be explained by the fact that the management capability of different components concerned is excellent. In Group C, the environment is good, but their NP (QOS) is low. Therefore, these components appear to have problems in the management procedures, or there could be other reasons for low performance. + +![Figure 2/M.1230: Management model for performance. A graph showing the relationship between Context Difficulty Index (CDI) on the x-axis and Quality of Service (QOS) or Non-Performance (NP) on the y-axis. A downward-sloping 'Performance indifference curve' represents the expected relationship. Four groups are plotted: Group A (high CDI, high QOS/NP), Group B (high CDI, low QOS/NP), Group C (low CDI, low QOS/NP), and Group D (low CDI, high QOS/NP). Arrows point from Groups A and C towards Group D, indicating a goal for management. Standard values QOS*, NP*, and CDI* are marked on the axes.](e6b5ee67ac260b0a3ed3e3c5ad7ea19c_img.jpg) + +H + ↑ + Group D + (+ +) + (+ +) + (+ +) + (+ +) + Group A + (+ +) + (+ +) + (+ +) + QOS\* or NP\* + ----- + (+) + (+) + (+) + Group C + (+) + (+) + (+) + L + ↓ + L CDI\* H + → + Group B + (+ +) + (+ +) + (+ +) + Performance indifference curve + T0405870-95/d02 + +QOS\* QOS standard value + NP\* NP standard value + CDI\* CDI standard value + +Figure 2/M.1230: Management model for performance. A graph showing the relationship between Context Difficulty Index (CDI) on the x-axis and Quality of Service (QOS) or Non-Performance (NP) on the y-axis. A downward-sloping 'Performance indifference curve' represents the expected relationship. Four groups are plotted: Group A (high CDI, high QOS/NP), Group B (high CDI, low QOS/NP), Group C (low CDI, low QOS/NP), and Group D (low CDI, high QOS/NP). Arrows point from Groups A and C towards Group D, indicating a goal for management. Standard values QOS\*, NP\*, and CDI\* are marked on the axes. + +FIGURE 2/M.1230 +Management model for performance + +It is clear that the best choice for TOs is to keep all the involved components in Group D, where the environment is good (CDI low) and NP (QOS) is high. + +As an example to achieve the aforesaid goals, the NP (QOS) and CDI relationship should be used to determine O&M budgets and relevant actions should be taken as follows: + +- 1) *Group A* – Even though the CDI is high, the NP (QOS) is high. Thus incentives should be given to the managers of these components, and O&M budgets should be assigned with high priority to improve their environment. With these relevant actions, it is possible to provide positive motivations to other components which have high CDI. +- 2) *Group B* – They are in the performance indifference curve, but below the NP (QOS) standard value NP\* (QOS\*). Therefore, additional budgets should be assigned to improve the NP (QOS) and CDI. With continuous supports, NP (QOS) and CDI should be improved above their standard values. +- 3) *Group C* – NP (QOS) is low even though the CDI is low. In this case relevant actions should be taken not by budget assignment but by management consulting to find reasons for low performance. Their NP (QOS) should be improved above standard value with proper activities. +- 4) *Group D* – These are ideal cases. With continuous support, it is essential to keep the NP (QOS) and CDI of these components above the standard values. + +## Annex A + +### Example of Context Difficulty Index (CDI) in an O&M environment where transmission aspects are predominant (This Annex forms an integral part of this Recommendation) + +In this “transmission environment” the following four significant factors are identified: + +- i) *Feeder cable ratio* – “Percentage of non-feeder cable to the percentage of feeder cable uninstalled area”. +- ii) *Cable buried ratio* – “Percentage of buried cable from the total cable”. +- iii) *Staffing insufficiency level* – The lack of personnel from its assigned number. +- iv) *Facility-obsolete level* – The level of obsolescence for key facilities. + +When the CDI value is high, it represents that the O&M environment is not good. + +These four factors can be selected, as they are important and common problems and their relevant data could be easily collected. CDI values can be calculated as reported in the following computation method. + +### Four CDI component index: + +- | | | | | | | +|----|----------------------------------------------------------------------------------------------------------|----|---|------------------------------|------------| +| 1) | Feeder cable ratio | X1 | → | Feeder cable index | Y1 = F(X1) | +| 2) | Cable buried ratio | X2 | → | Cable buried index | Y2 = F(X2) | +| 3) | Staffing insufficiency level | X3 | → | Staffing insufficiency index | Y3 = F(X3) | +| 4) | Facility obsolete level | X4 | → | Facility obsolete index | Y4 = F(X4) | +| F | Transform context difficulty component values into an index which has a range 4) from 1 to 5. | | | | | + +### CDI computation: + +$$CDI = (Y1 + Y2 + Y3 + Y4)/4$$ + +--- + +4) For each central office as involved in this example, values of context difficulty components were computed. Then central offices were classified into five different ranges according to these values. The offices with the best environment are assigned with index 1 and the poorest are assigned index 5. Thus, if CDI is high, their O&M environment is poor, if CDI is low, their O&M environment is good. + +## References + +- [1] CCITT Recommendation E.420 (1988), *Checking the quality of the international telephone service – General considerations.* +- [2] CCITT Recommendation E.421 (1988), *Service quality observations on a statistical basis.* +- [3] ITU-T Recommendation E.422 (1996), *Observations on international outgoing telephone calls for Quality of Service.* +- [4] CCITT Recommendation E.423 (1988), *Observations on traffic set up by operators.* +- [5] CCITT Recommendation E.424 (1992), *Test calls.* +- [6] CCITT Recommendation E.425 (1992), *Internal automatic observations.* +- [7] CCITT Recommendation E.426 (1992), *General guide to the percentage of effective attempts which should be observed for international telephone calls.* +- [8] CCITT Recommendation E.428 (1992), *Connection retention.* +- [9] CCITT Recommendation E.431 (1992), *Service quality assessment for connection set-up and release delays.* +- [10] CCITT Recommendation E.432 (1992), *Connection quality.* +- [11] CCITT Recommendation E.433 (1992), *Billing integrity.* +- [12] CCITT Recommendation E.434 (1992), *Subscriber-to-subscriber measurement of public switched telephone network* +- [13] ITU-T Recommendation E.440 (1996), *Customer satisfaction point.* +- [14] ITU-T Recommendation E.801 (1996), *Framework for Service Quality Agreement (SQA).* +- [15] ITU-T Recommendation E.600 (1993), *Terms and definitions of traffic engineering.* +- [16] ITU-T Recommendation E.800 (1994), *Terms and definitions related to Quality of Service and network performance including dependability.* +- [17] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [18] CCITT Recommendation M.21 (1992), *Maintenance philosophy for telecommunication services.* +- [19] CCITT Recommendation M.730 (1988), *Maintenance methods.* +- [20] CCITT Recommendation M.1235 (1988), *Use of automatically generated test calls for assessment of network performance.* +- [21] CCITT Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks.* + +## ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Telephone network and ISDN | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media | +| Series H | Transmission of non-telephone signals | +| Series I | Integrated services digital network | +| Series J | Transmission of sound-programme and television signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound-programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminal equipments and protocols for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.1235-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1235-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.1235-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.125-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg b/marked/M/T-REC-M.125-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e43dc7c8f4d7f9455b57fa79a68e18ac690a147a --- /dev/null +++ b/marked/M/T-REC-M.125-198811-I_PDF-E/191a4a245a7d36d03be9a990d0f758f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5dca9932c83f929d79b34c4b75e7b5023ac37957a54e21c84839de450e1c40d +size 155548 diff --git a/marked/M/T-REC-M.125-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.125-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.125-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.125-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/M/T-REC-M.125-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0b2a46c692facd73c1a8ecbd6af0800c174778 --- /dev/null +++ b/marked/M/T-REC-M.125-198811-I_PDF-E/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c3043fa3d527d11442e1e27c7c1174ac20b3bc6c1e6ec0a1c71a6a7b1cff78e +size 19554 diff --git a/marked/M/T-REC-M.125-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/M/T-REC-M.125-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eebc5c30db7cdd12114b8411bb38e4c191eb4bff --- /dev/null +++ b/marked/M/T-REC-M.125-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:070608865d8c4a41c043fa9a70b2e43fe52bfff12afd9996ef13c29c1d089ce1 +size 72774 diff --git a/marked/M/T-REC-M.125-198811-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg b/marked/M/T-REC-M.125-198811-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d151f71858f70c51bdbeb8b1382055d2d88361d --- /dev/null +++ b/marked/M/T-REC-M.125-198811-I_PDF-E/d980a3f9608055996a07f31788baf827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb97c425e0d6854749826f5f3b9efb133b6ee22ce1f9885314883a2c5ffb31dd +size 16129 diff --git a/marked/M/T-REC-M.125-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.125-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..142f499a00423a9197606b8f87dece6bfd153f98 --- /dev/null +++ b/marked/M/T-REC-M.125-198811-I_PDF-E/raw.md @@ -0,0 +1,203 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.125** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTRODUCTION AND GENERAL PRINCIPLES** + +--- + +**DIGITAL LOOPBACK MECHANISMS** + +**ITU-T Recommendation M.125** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.125 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# DIGITAL LOOPBACK MECHANISMS + +## 1 General + +Loopback can be one of the mechanisms which may be applied to fault localization and failure detection. This Recommendation provides digital loopback definitions and describes loopback applications related to the maintenance phases of Recommendation M.20. + +## 2 Digital loopback definitions + +A **digital loopback** is a mechanism incorporated into a piece of equipment whereby a bidirectional communication path may be connected back upon itself so that some or all of the information contained in the bit stream sent on the transmit path is returned on the receive path. + +The **loopback point** is the location of the loopback. + +The **loopback control mechanism** is the means by which the loopback is operated and released from the loopback control point. + +The **loopback control point** is the point which has the ability to directly control loopbacks. + +The loopback control point may receive requests for loopback operation from several loopback requesting points. + +The **loopback requesting point** is the point which requests the loopback control point to operate loopbacks. + +*Note 1* – Loopback requests should be subject to identification and authorization. + +*Note 2* – Possible locations of loopback requesting points are: the network, or a telecommunications management network (TMN), or a maintenance service provider (MSP). + +The **loopback test pattern** is the test information transmitted during the operation of the loopback in the channel or channels which are to be redirected by the loopback. + +*Note 1* – The generation of the test pattern used over the loopback may or may not take place at the control point. + +The **loopback application** is the maintenance phase for which the loopback operation is used, as defined in Recommendation M.20. + +### 2.1 Loopback types + +The following three types of loopback mechanisms are defined: + +- a) **complete loopback** – A complete loopback is a physical layer [1] mechanism which operates on the full bit stream. At the loopback point, the received bit stream shall be transmitted back towards the transmitting station without modification. + +*Note* – The use of the term “complete loopback” is not related to implementation since such a loopback may be provided by means of active logic elements or controlled unbalance of hybrid transformer, etc. At the control point only the information channels may be available. + +- b) **partial loopback** – A partial loopback is a physical layer [1] mechanism which operates on one or more specified channels multiplexed within the full bit stream. At the loopback point, the received bit stream associated with the specified channel(s) shall be transmitted back towards the transmitting station without modification. +- c) **logical loopback** – A logical loopback acts selectively on certain information within a specified channel or channels and may result in some specified modification of the looped information. Logical loopbacks may be defined to apply at any layer [1], depending on the detailed maintenance procedures specified. + +For each of the above three types of loopback mechanisms, the loopback may be further categorized as either transparent or non-transparent: + +- i) A **transparent loopback** is one in which the signal transmitted beyond the loopback point (the forward signal) when the loopback is activated, is the same as the received signal at the loopback point. See Figure 1 a)/M.125. +- ii) A **non-transparent loopback** is one in which the signal transmitted beyond the loopback point (the forward signal) when the loopback is activated is not the same as the received signal at the loopback point. The forward signal may be defined signal or unspecified. See Figure 1 b)/M.125. + +*Note* – Whether or not a transparent loopback is used, the loopback should not be affected by facilities connected beyond the point at which the loop is provided, e.g., by the presence of short circuits, open circuits or foreign voltages. + +Annex A to this Recommendation shows some examples of loopbacks. + +![Diagrams of transparent and non-transparent loopback mechanisms.](d62e2e2281009c16f4ee61660e716cd9_img.jpg) + +The diagram consists of two parts, (a) and (b), illustrating different loopback mechanisms. Both diagrams show a signal path with a loopback point indicated by a vertical dashed line. In part (a), labeled 'a) Transparent loopback', the signal is looped back at the loopback point. A label 'Transparent, complete loopback' points to the loop, with a sub-note '(Complete loopback of full bit stream, transparent with regard to bit stream in forward direction.)'. In part (b), labeled 'b) Non-transparent loopback', the signal is looped back at the loopback point, but there is a device labeled 'L1' in the forward path before the loopback point. A label 'Non-transparent, complete loopback' points to the loop, with a sub-note '(Complete loopback of full bit stream, non-transparent with regard to bit stream in forward direction.)'. Both diagrams include an 'X' on the forward path before the loopback point, with a note 'X = Signal inhibited in order to avoid interference with looped signal'. A reference code 'T0401150-88' is present near the bottom of part (b). + +Loopback point + +Transparent, complete loopback +(Complete loopback of full bit stream, transparent with regard to bit stream in forward direction.) + +X = Signal inhibited in order to avoid interference with looped signal + +a) Transparent loopback + +Loopback point + +Non-transparent, complete loopback +(Complete loopback of full bit stream, non-transparent with regard to bit stream in forward direction.) + +T0401150-88 + +X = Signal inhibited in order to avoid interference with looped signal + +L1 = Device which changes or inhibits the transferred signal + +b) Non-transparent loopback + +d01-sc + +Diagrams of transparent and non-transparent loopback mechanisms. + +FIGURE 1/M.125 + +## 3 Loopback applications + +### 3.1 Failure detection + +In order to detect failures related to networks maintained by different maintenance organizations, loopbacks should be applied at the borderline separating the maintenance responsibilities. Loopbacks should be located in the maintenance entities (ME) adjacent to the borderline and as close as possible to the borderline. Part of the bit stream can be involved in failure detection. Figure 2/M.125 shows an example with failure detection originated in locations A and B. + +![Diagram of failure detection with loopbacks across two maintenance organizations.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +The diagram shows two maintenance organizations, A and B, separated by a vertical dashed borderline. Maintenance organization A has three Maintenance Entities (ME) in a row, and Maintenance organization B also has three MEs. A signal path goes from point A through the MEs of organization A, crosses the borderline, and continues through the MEs of organization B to point B. In the last ME of organization A (closest to the border), there is a loopback arrow pointing from the forward path back to the return path. Similarly, in the first ME of organization B (closest to the border), there is a loopback arrow pointing from the forward path back to the return path. Labels include 'Maintenance organization A', 'Maintenance organization B', 'A', 'B', 'ME', 'T0400940-87', and 'd02-sc'. + +Diagram of failure detection with loopbacks across two maintenance organizations. + +FIGURE 2/M.125 + +#### Failure detection with loopbacks + +### 3.2 Fault localization + +The localization of faults in networks consisting of $n$ maintenance entities requires at least $n + 1$ loopback mechanisms. The loopback point should be as close as possible to the in- and output ports of the ME in order to include as much as possible of the ME in the loopback mechanism. (See example in Figure 3/M.125.) Part of the bit stream or the complete bit stream can be involved in fault localization, originated in locations A or B. + +![Diagram of fault localization with loopback mechanisms.](d980a3f9608055996a07f31788baf827_img.jpg) + +The diagram shows two parallel paths of Maintenance Entities (ME). The top path starts at point A and consists of three MEs, each with a loopback arrow pointing from the input side to the output side. The bottom path consists of three MEs ending at point B, each also with a loopback arrow pointing from the input side to the output side. Labels include 'A', 'B', 'ME', 'T0400950-87', and 'd03-sc'. + +Diagram of fault localization with loopback mechanisms. + +FIGURE 3/M.125 + +#### Fault localization with loopback mechanisms + +### 3.3 Verification + +Verification can require performance tests and measurements of the complete bit stream. + +The same loopback location can be used as for fault localization. + +## 4 Loopback operation and release + +Loopbacks can be operated/released locally or remotely. Remote operation/release can be based on in-service addressing (e.g., layer 1 protocols) or it can require separate loopbacks addressing systems. + +## 5 Loopback examples (under study – see Annex A) + +## ANNEX A (to Recommendation M.125) + +![Diagram illustrating six types of loopbacks in a network element. Each type shows a signal path with devices L1 and L2, and inhibited signals marked with X. The types are: 1. Non-transparent, complete loopback; 2. Transparent, complete loopback; 3. Unlooped signal and Non-transparent, partial loopback; 4. Unlooped signal and Transparent partial loopback; 5. Unlooped signal and Non-transparent, logical loopback; 6. Unlooped signal and Transparent, logical loopback.](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +Loopback part + +Non-transparent, complete loopback +(Complete loopback of full bit stream, non-transparent with regard to bit stream in forward direction) + +Transparent, complete loopback +(Complete loopback of full bit stream, transparent with regard to bit stream in forward direction) + +Unlooped signal +Non-transparent, partial loopback +(Partial loopback of channel(s), non-transparent with regard to channel(s) in forward direction) + +Unlooped signal +Transparent partial loopback +(Partial loopback of channel(s), transparent with regard to channel(s) in forward direction) + +Unlooped signal +Non-transparent, logical loopback +(Logical loopback of part channel, non-transparent in respect to channel in forward direction) + +Unlooped signal +Transparent, logical loopback +(Logical loopback of part of channel, transparent in respect to channel in forward direction) + +L1 = Device which changes or inhibits the transferred signal +L2 = Device which changes the looped signal +X = (Part of) signal inhibited in order to avoid interference with looped signal. + +T0400960-87 d04-sc + +Diagram illustrating six types of loopbacks in a network element. Each type shows a signal path with devices L1 and L2, and inhibited signals marked with X. The types are: 1. Non-transparent, complete loopback; 2. Transparent, complete loopback; 3. Unlooped signal and Non-transparent, partial loopback; 4. Unlooped signal and Transparent partial loopback; 5. Unlooped signal and Non-transparent, logical loopback; 6. Unlooped signal and Transparent, logical loopback. + +FIGURE A-1/M.125 +Examples of loopbacks + +## Reference + +- [1] CCITT Recommendation *Reference model of open system interconnection for CCITT applications*, Vol. VIII, Recommendation X.200. \ No newline at end of file diff --git a/marked/M/T-REC-M.1300-199710-I_PDF-E/raw.md b/marked/M/T-REC-M.1300-199710-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3ce16977c19dca8e2dc8a9f820c97a3d9bc62b67 --- /dev/null +++ b/marked/M/T-REC-M.1300-199710-I_PDF-E/raw.md @@ -0,0 +1,460 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1300** + +(10/97) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**Maintenance of international data transmission +systems operating in the range 2.4 kbit/s to +140 Mbit/s** + +ITU-T Recommendation M.1300 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.1300** + +## **MAINTENANCE OF INTERNATIONAL DATA TRANSMISSION SYSTEMS OPERATING IN THE RANGE 2.4 kbit/s TO 140 Mbit/s** + +## **Summary** + +This Recommendation provides a general description of international data transmission systems with a PDH presentation to the renter and of the basic requirements for their effective operation. + +## **Source** + +ITU-T Recommendation M.1300 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 24th of October 1997. + +## **Keywords** + +International data transmission links, international data transmission systems, international leased circuits. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | | Page | +|----|---------------------------------------------------------------------|-------------| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Terminology and definitions ..... | 2 | +| 4 | Abbreviations ..... | 2 | +| 5 | Operational procedures..... | 3 | +| 6 | Performance limits ..... | 3 | +| 7 | General description of international data transmission systems..... | 3 | +| 8 | General description of international data transmission links ..... | 9 | +| 9 | Timing sources ..... | 11 | +| 10 | Control and sub-control stations ..... | 11 | +| 11 | Reserve arrangements..... | 11 | +| 12 | Designations ..... | 11 | + + + +## Recommendation M.1300 + +## MAINTENANCE OF INTERNATIONAL DATA TRANSMISSION SYSTEMS OPERATING IN THE RANGE 2.4 kbit/s TO 140 Mbit/s + +(Published 1984; revised 1988, 1992 and 1997) + +## 1 Scope + +This Recommendation defines international data transmission systems with a PDH presentation to the router. The international data transmission system is transported via an international data transmission link, which may typically be provided on a variety of transmission media using a number of network technologies. + +## 2 References + +The following ITU-T Recommendations contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation G.703 (1991), *Physical/electrical characteristics of hierarchical digital interfaces*. +- [2] ITU-T Recommendation G.704 (1995), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels*. +- [3] CCITT Recommendation G.732 (1988), *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s*. +- [4] ITU-T Recommendation G.736 (1993), *Characteristics of a synchronous digital multiplex equipment operating at 2048 kbit/s*. +- [5] CCITT Recommendation G.751 (1988), *Digital Multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 624 kbit/s and using positive justification*. +- [6] CCITT Recommendation G.752 (1980), *Characteristics of digital multiplex equipments based on a second order bit rate of 6312 kbit/s and using positive justification*. +- [7] ITU-T Recommendation G.803 (1997), *Architectures of transport networks based on the Synchronous Digital Hierarchy (SDH)*. +- [8] ITU-T Recommendation G.811 (1997), *Timing characteristics of primary reference clocks*. +- [9] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- [10] CCITT Recommendation M.1012 (1988), *Circuit control station for leased and special circuits*. +- [11] CCITT Recommendation M.1013 (1988), *Sub-control station for leased and special circuits*. + +- [12] ITU-T Recommendation M.1340 (1996), *Performance allocations and limits for international data transmission links and systems.* +- [13] ITU-T Recommendation M.1370 (1993), *Bringing-into-service of international data transmission systems.* +- [14] ITU-T Recommendation M.1375 (1996), *Maintenance of international data transmission system.* +- [15] ITU-T Recommendation M.1380 (1997), *Bringing-into-service of international leased circuits that are supported by international data transmission systems.* +- [16] ITU-T Recommendation M.1385 (1993), *Maintenance of international leased circuits that are supported by international data transmission systems.* +- [17] ITU-T Recommendation M.1400 (1997), *Designations for international networks.* +- [18] ITU-T Recommendation V.11 (1996), *Electrical characteristics for balanced double-current interchange circuits operating at data signalling rates up to 10 Mbit/s.* +- [19] ITU-T Recommendation V.24 (1996), *List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE).* +- [20] ITU-T Recommendation V.28 (1993), *Electrical characteristics for unbalanced double-current interchange circuits.* +- [21] CCITT Recommendation X.21 (1992), *Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for synchronous operation on public data networks.* +- [22] CCITT Recommendation X.50 (1988), *Fundamental parameters of a multiplexing scheme for the international interface between synchronous data networks.* + +## 3 Terminology and definitions + +Terminologies and definitions relating to this Recommendation are provided in Recommendation M.60 [9]. + +A data transmission system is a component of a digital transmission network, and is primarily used to support international leased circuits. These circuits can be used for a variety of services, including voice, data, video, etc. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations. + +| | | +|-----|----------------------------------| +| DNI | Digital Network Interface | +| FDM | Frequency Division Multiplexing | +| LTP | Link Terminating Point | +| MUX | Multiplexing Equipment | +| PDH | Plesiochronous Digital Hierarchy | +| RP | Renter's Premises | +| TDM | Time Division Multiplexing | +| TIC | Terminal International Centre | + +## 5 Operational procedures + +Recommendation M.1370 [13] covers the setting up and bringing-into-service of international data transmission systems. Maintenance issues are covered by Recommendation M.1375 [14]. + +The bringing-into-service and maintenance issues relating to international leased circuits with a digital presentation at renters' premises that are supported by international data transmission systems are covered by Recommendations M.1380 [15] and M.1385 [16], respectively. + +## 6 Performance limits + +Performance limits applicable to international data transmission systems and links are provided in Recommendation M.1340 [12]. + +## 7 General description of international data transmission systems + +An international data transmission system is comprised of an international data transmission link combined with multiplexing equipment1 at each end and is primarily used for the point-to-point transmission of international leased circuits (see Figure 1). Typical data rates of interest are: 2.4, 4.8, 7.2, 9.6, 14.4, 19.2, 48, 56, 64, $N \times 64$ ( $N = 2$ to 31), 1544, and 2048 kbit/s, 6, 8, 34, 45 and 140 Mbit/s. A system may be carried as a channel on a higher order system (see Figure 2a). + +The international data transmission link that supports the aggregate transmission from the terminal multiplexing equipment of the international data transmission system will be presented via a digital interface that is referred to as the Link Terminating Point (LTP). Where an international data transmission link incorporates an analogue transmission path, the associated modems required to derive the digital interface are considered to be part of the link2. + +In general, an international data transmission link can be divided into sectional components. The international link section is considered to exist between Terminal International Centres (TICs) and the national link section is considered to exist between a TIC and LTP, where the LTP could be located at numerous points, including Terminal National Centres (TNCs) or renters' premises3. Several typical configurations of an international data transmission system are shown in Figure 3. It should be noted that where an LTP exists at a TIC, no national link section will exist. + +Exceptionally, an international data transmission system may not be routed via any Network Operator's/Service Provider's premises. Figure 3 d) shows an international data transmission system routed directly between renters' premises, e.g. via satellite. + +An international data transmission system can support circuits with either analogue or digital presentations at the renter's premises. Typical uses include data, facsimile, voice, etc. (see Figure 4). + +--- + +1 The term multiplexing equipment, as defined in Recommendation M.60 [9], includes digital cross-connect equipment. + +2 Certain terminal equipment incorporates modem and multiplex functions and there may consequently be no physical LTP at which testing is possible. A similar situation can exist where a channel card in a primary multiplex equipment operates as a lower order multiplexing equipment in its own right (e.g. in accordance with Recommendation X.50 [22]). Where a physical LTP does not exist, Network Operators/Service Providers should bilaterally develop alternative testing arrangements. + +3 The renter's premises is a geographical location which is outside the Administration's domain. + +For data transmission systems operating within an aggregate data rate, it is recommended that the multiplexing equipment used should conform to Table 1. Alternative frame structures may be used by bilateral agreement. + +![Diagram of an international data transmission system showing national link sections, international link sections, and the overall international data transmission link and system.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +The diagram illustrates the structure of an international data transmission system. It features two main components at the ends, each represented by a box containing the letters 'M', 'U', and 'X'. These components are connected to a central horizontal line. The left component is connected via a point labeled 'LTP'. The right component is also connected via a point labeled 'LTP'. Between these two LTP points, there are two intermediate points labeled 'TIC'. The segments between the LTP points and the TIC points are labeled 'National link section'. The segment between the two TIC points is labeled 'International link section'. Below the main horizontal line, a long double-headed arrow spans the distance between the two LTP points and is labeled 'International data transmission link'. At the very bottom, another long double-headed arrow spans the entire distance from the leftmost vertical line to the rightmost vertical line and is labeled 'International data transmission system'. A small code 'T0402520-91' is located at the bottom right of the diagram. + +Diagram of an international data transmission system showing national link sections, international link sections, and the overall international data transmission link and system. + +NOTE – Where an LTP is located at a TIC, there will be no national link section at that end of the international data transmission link. + +**Figure 1/M.1300 – An international data transmission system** + +![Diagram of a typical international data transmission system (Figure 2a/M.1300). The diagram shows a complex network architecture with multiple layers of transmission. At the top, a hierarchy of arrows indicates nested systems: International data transmission system (64 kbit/s), International data transmission link (64 kbit/s), International data transmission system (2048 kbit/s), and International data transmission link (2048 kbit/s). Below this, a '64 kbit/s channel' is shown within a 'Digital leased circuit (e.g. 9.6 kbit/s)'. The physical components include Renter's Premises (RP) with MUX units, Terminal National Centres (TNC) also with MUX units, and Terminal International Centres (TIC) with larger MUX units. Link Terminating Points (LTP) are marked at various connection interfaces. The bottom half of the diagram uses dashed lines and triangular symbols to represent the logical flow through adaption and termination functions, starting and ending with pentagonal input/output symbols. Labels indicate bit rates like 64 kbit/s and 2048 kbit/s at different stages. The diagram is indexed as T0407300-97.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +International data transmission system (64 kbit/s) + +International data transmission link (64 kbit/s) + +International data transmission system (2048 kbit/s) + +TNC TNC + +MUX MUX LTP LTP MUX International data MUX LTP MUX + +RP transmission link RP + +MUX (2048 kbit/s) MUX + +LTP LTP LTP LTP + +TIC TIC + +64 kbit/s channel + +Digital leased circuit (e.g. 9.6 kbit/s) + +International data transmission system (64 kbit/s) + +International data transmission link (64 kbit/s) + +64 kbit/s International data 64 kbit/s T0407300-97 + +transmission + +system (2048 kbit/s) + +International data transmission + +link (2048 kbit/s) + +– Adaption function +– Termination function +– Input/output + +TIC Terminal International Centre +TNC Terminal National Centre +RP Renter's Premises +LTP Link Terminating Point +MUX Multiplexing Equipment (or Cross-connect system) + +Diagram of a typical international data transmission system (Figure 2a/M.1300). The diagram shows a complex network architecture with multiple layers of transmission. At the top, a hierarchy of arrows indicates nested systems: International data transmission system (64 kbit/s), International data transmission link (64 kbit/s), International data transmission system (2048 kbit/s), and International data transmission link (2048 kbit/s). Below this, a '64 kbit/s channel' is shown within a 'Digital leased circuit (e.g. 9.6 kbit/s)'. The physical components include Renter's Premises (RP) with MUX units, Terminal National Centres (TNC) also with MUX units, and Terminal International Centres (TIC) with larger MUX units. Link Terminating Points (LTP) are marked at various connection interfaces. The bottom half of the diagram uses dashed lines and triangular symbols to represent the logical flow through adaption and termination functions, starting and ending with pentagonal input/output symbols. Labels indicate bit rates like 64 kbit/s and 2048 kbit/s at different stages. The diagram is indexed as T0407300-97. + +**Figure 2a/M.1300 – A typical international data transmission system carried on a higher order system, comprising Multiplex equipment** + +![Diagram of a typical international data transmission system (Figure 2b/M.1300) showing the hierarchy of data rates and the placement of cross-connect equipment.](d4af765160d04ecef538e5066006dc77_img.jpg) + +TIC DXC + RP + 64 2 + 2 34 + 34 140 + 140 34 + 34 2 + 2 64 + National data transmission system (2048 kbit/s) + International data transmission link (2048 kbit/s) + International data transmission system (2048 kbit/s) + Cross-Connection at 64 kbit/s + 64 kbit/s + 2 Mbit/s + 8 Mbit/s + 34 Mbit/s + 140 Mbit/s + T0407310-97 + +▽ – Adaption function + – Termination function + ▱ – Input/output + ○ – Connection function + RP Renter's Premises + DXC Digital Cross-Connect + +Diagram of a typical international data transmission system (Figure 2b/M.1300) showing the hierarchy of data rates and the placement of cross-connect equipment. + +**Figure 2b/M.1300 – A typical international data transmission system carried on a higher order system, comprising cross-connect equipment** + +Figure 2b above shows the case where the terminal multiplexing equipment is replaced with digital cross-connect equipment. In this case the international data transmission system exists between the mid-points of the two cross-connects. It is therefore possible to define a "virtual point" at the centre of the cross-connect equipment, from where the testing of the international data transmission system is carried out. + +In a similar way, a national data transmission system can be defined which exists, in the case illustrated above, between the TIC and the renter's premises. + +![Diagram (a) showing Multiplex/Demultiplex equipment located at the TIC. It depicts an 'International data transmission system' between two TIC boxes. Inside each TIC box are components M, U, and X. A line labeled 'International data transmission link' connects the LTP (Link Terminating Point) of component X in one TIC box to the LTP of component X in the other TIC box. The U component in each TIC box is connected to this link via a circle.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Diagram (a) showing Multiplex/Demultiplex equipment located at the TIC. It depicts an 'International data transmission system' between two TIC boxes. Inside each TIC box are components M, U, and X. A line labeled 'International data transmission link' connects the LTP (Link Terminating Point) of component X in one TIC box to the LTP of component X in the other TIC box. The U component in each TIC box is connected to this link via a circle. + +**a) Multiplex/Demultiplex equipment located at the TIC** + +![Diagram (b) showing Multiplex/Demultiplex equipment located at the TNC. It depicts an 'International data transmission system' between two TNC boxes. The system is divided into three 'link sections': 'National link section', 'International link section', and 'National link section'. Inside each TNC box are components M, U, and X. The 'International data transmission link' connects the LTP of component X in one TNC box to the LTP of component X in the other TNC box. Along this link, there are circles representing connection points: one at each TNC box, and two within the 'International link section' labeled 'TIC'.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +Diagram (b) showing Multiplex/Demultiplex equipment located at the TNC. It depicts an 'International data transmission system' between two TNC boxes. The system is divided into three 'link sections': 'National link section', 'International link section', and 'National link section'. Inside each TNC box are components M, U, and X. The 'International data transmission link' connects the LTP of component X in one TNC box to the LTP of component X in the other TNC box. Along this link, there are circles representing connection points: one at each TNC box, and two within the 'International link section' labeled 'TIC'. + +**b) Multiplex/Demultiplex equipment located at the TNC** + +![Diagram (c) showing Multiplex/Demultiplex equipment located at the RP. It depicts an 'International data transmission system' between two RP boxes. The system is divided into three 'link sections': 'National link section', 'International link section', and 'National link section'. Inside each RP box are components M, U, and X. The 'International data transmission link' connects the LTP of component X in one RP box to the LTP of component X in the other RP box. Along this link, there are circles representing connection points: one at each RP box, two within the first 'National link section' labeled 'TNC', two within the 'International link section' labeled 'TIC', and two within the second 'National link section' labeled 'TNC'.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Diagram (c) showing Multiplex/Demultiplex equipment located at the RP. It depicts an 'International data transmission system' between two RP boxes. The system is divided into three 'link sections': 'National link section', 'International link section', and 'National link section'. Inside each RP box are components M, U, and X. The 'International data transmission link' connects the LTP of component X in one RP box to the LTP of component X in the other RP box. Along this link, there are circles representing connection points: one at each RP box, two within the first 'National link section' labeled 'TNC', two within the 'International link section' labeled 'TIC', and two within the second 'National link section' labeled 'TNC'. + +**c) Multiplex/Demultiplex equipment located at the RP** + +![Diagram (d) showing a data transmission system routed directly between RPs. It depicts an 'International data transmission system' between two RP boxes. A direct line labeled '(e.g. A direct satellite link)' connects the U component of component X in one RP box to the U component of component X in the other RP box. Below this, a line labeled 'International data transmission link' connects the LTP of component X in one RP box to the LTP of component X in the other RP box.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Diagram (d) showing a data transmission system routed directly between RPs. It depicts an 'International data transmission system' between two RP boxes. A direct line labeled '(e.g. A direct satellite link)' connects the U component of component X in one RP box to the U component of component X in the other RP box. Below this, a line labeled 'International data transmission link' connects the LTP of component X in one RP box to the LTP of component X in the other RP box. + +**d) A data transmission system routed directly between RPs** + +T0401740-90 + +LTP Link Terminating Point + RP Renters' premises + TIC Terminal International Centre + TNC Terminal National Centre + +**Figure 3/M.1300 – Typical configurations of an international data transmission system** + +![Diagram of an international data transmission system showing various presentations at renter's premises. It includes components like TDM, A/D and D/A converters, Link Terminating Points (LTP), IPSS centres, and spare channels. The diagram illustrates the flow of data from renter's premises through various conversion and multiplexing stages into a common international transmission system.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +The diagram illustrates an international data transmission system architecture. At the far left and far right, there are 'Renter's premises' (indicated by dashed boxes containing a triangle symbol). These premises connect to 'Analogue' inputs of 'A/D Converter' (left) and 'D/A Converter' (right) blocks. The 'Analogue' inputs are also connected to 'TDM' (Time Division Multiplexing) units. The 'A/D Converter' and 'D/A Converter' blocks have 'Digital' outputs that connect to 'Link Terminating Point' (LTP) units, each containing 'M' (Multiplexer), 'U' (User), and 'X' (Switch) components. The LTP units are connected to a central 'International 56 kbit/s data transmission link'. Below the LTP units, there are 'IPSS centre' (International Packet Switching Service) units, each containing an 'X' (Switch) symbol. The IPSS centres are connected to 'Spare channels' which lead into the 'International data transmission system'. The entire system is framed by a top horizontal line labeled 'International TDM telegraph system' and a middle horizontal line labeled 'International leased data circuits'. The bottom horizontal line is labeled 'International data transmission system'. The diagram is labeled 'T0402530-91' in the bottom right corner. + +Legend: + +- △ Renter's premises +- X IPSS International Packet Switching Service +- TDM Time Division Multiplexing +- LTP Link Terminating Point + +Diagram of an international data transmission system showing various presentations at renter's premises. It includes components like TDM, A/D and D/A converters, Link Terminating Points (LTP), IPSS centres, and spare channels. The diagram illustrates the flow of data from renter's premises through various conversion and multiplexing stages into a common international transmission system. + +Figure 4/M.1300 – An example of an international data transmission system with different presentations at renter's premises + +**Table 1/M.1300 – Recommended interfaces and frame structures for multiplexing equipment operating between 1544 kbit/s and 140 Mbit/s** + +| | ITU-T Recommendation | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|-------------------| +| | Electrical/physical interface characteristics | Framing structure | +| 1 544 kbit/s | Clause 2/G.703 [1] | 2.1/G.704 [2] | +| 2 048 kbit/s | Clause 6/G.703 [1] | 2.3/G.704 [2] | +| 6 312 kbit/s | Clause 3/G.703 [1] | 4.1/G.704 [2] | +| 8 448 kbit/s | Clause 7/G.703 [1] | 6.1/G.704 [2] | +| 34 368 kbit/s | Clause 8/G.703 [1] | 1.4/G.751 [5] | +| 44 736 kbit/s | Clause 5/G.703 [1] | 1.3/G.752 [6] | +| 139 264 kbit/s | Clause 9/G.703 [1] | 1.5/G.751 [5] | +| NOTE 1 – Channel associated signalling for 2048 kbit/s frame structures, where required, should conform to 5.1.3.2/G.704 [2], and 5.1/G.732 [3]. | | | +| NOTE 2 – 2048 kbit/s frame structures that provide common channel signalling should conform to clause 2/G.736 [4]. | | | +| NOTE 3 – Signalling arrangements for 1544 kbit/s frame structures, where required, are described in 3.1.3/G.704 [2]. | | | + +## 8 General description of international data transmission links + +International data transmission links may typically be provided on a variety of transmission media in various combinations: + +- paired copper cable; +- FDM carrier systems (group or supergroup) via symmetric pair or coaxial cable systems, microwave radio links, satellites; +- voice grade analogue or digital channels; +- digital links via coaxial or optical fibre cable systems, microwave radio links or satellite systems. + +Modems or interface adaptors can be used to derive appropriate signals for the transmission medium being used. The LTPs of an international data transmission link provide digital interface test points and should preferably operate as standard G.703 [1] interfaces, although other interfaces (such as Recommendations V.24 [19], V.28 [20], X.21 [21], V.11 [18], etc.) may be used. + +Figure 5 gives an overview of possible configurations for an international data transmission link. While hybrid combinations of link configurations are possible, it is preferable that the same interface type be presented at each end. It should be noted that certain multiplexing equipment will not interwork correctly if differing interface presentations are provided at each LTP. + +The international data transmission link should maintain the transparency of the data flow, which means that the transmission rate at all points of the link will be at or above the data rate of the LTP. + +For data transmission links routed via a mixture of transmission media (e.g. microwave, optical fibre or satellite, etc.) the term "section" is used to refer to a section of the overall link, or international or national link section, routed wholly on one type of transmission medium. + +![Four diagrams (a, b, c, d) showing different configurations of an international data transmission link between two MUX units. Each MUX unit contains M, U, and X components. Diagram a) shows a direct connection via an analogue network with two modems. Diagram b) shows a connection to a digital network via interface adaptors and DNI points. Diagram c) shows a direct connection to a digital network. Diagram d) shows a connection routed via a higher order international data transmission system with two interface adaptors. All diagrams include a double-headed arrow labeled 'International data transmission link'.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +**a) Direct connection via an analogue network** + +**b) Connection to a digital network via interface adaptors** + +**c) Direct connection to a digital network** + +**d) Routed via higher order international data transmission system** + +T0401760-90 + +Four diagrams (a, b, c, d) showing different configurations of an international data transmission link between two MUX units. Each MUX unit contains M, U, and X components. Diagram a) shows a direct connection via an analogue network with two modems. Diagram b) shows a connection to a digital network via interface adaptors and DNI points. Diagram c) shows a direct connection to a digital network. Diagram d) shows a connection routed via a higher order international data transmission system with two interface adaptors. All diagrams include a double-headed arrow labeled 'International data transmission link'. + +DNI Digital Network Interface + LTP Link Terminating Point (digital interface) + MUX Multiplexing/demultiplexing (or similar) equipment + +**Figure 5/M.1300 – Configuration of an international data transmission link** + +The "Digital Network" shown in Figures 5 b) and 5 c) signifies that the international data transmission system cannot be broken down to data rates of less than the aggregate transmission rate, but it does include the possibility of the international data transmission system being carried as a channel in a higher rate system. + +## **9 Timing sources** + +The timing feed at each end of an international data transmission system should be derived from a primary reference clock operating in accordance with clause 2/G.811 [8]. + +This will allow for correct plesiochronous operation between Network Operators/Service Providers. + +## **10 Control and sub-control stations** + +Network Operators/Service Providers may elect to assign control and sub-control status to the terminal stations of an international data transmission system in accordance with Recommendations M.1012 [10] and M.1013 [11]. However, in order to achieve the fastest possible response times for maintenance activities on behalf of users, it is acceptable for both terminal stations of an international data transmission system to assume control station status. It is however essential for the control stations involved to develop an effective mechanism for coordinating maintenance activity and that they inform each other of specific maintenance actions as rapidly as possible. + +## **11 Reserve arrangements** + +Since international data transmission links often carry international leased circuits, data systems, and/or TDM telegraph systems, some Network Operators/Service Providers find it useful to nominate a reserve link for restoration purposes in the event of failure of the normal link. This should be decided by bilateral agreement between the Network Operators/Service Providers at the time of planning the link. Such reserve links must be set up or lined up to meet the requirements of the normal data transmission link and, wherever possible, should follow a different route from the route of the normal link. + +## **12 Designations** + +The form of designations for international data transmission systems and international data transmission links is described in Recommendation M.1400 [17]. + + + +## ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression: definitions, symbols, classification +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Overall network operation, telephone service, service operation and human factors +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media, digital systems and networks +- Series H Audiovisual and multimedia systems +- Series I Integrated services digital network +- Series J Transmission of television, sound programme and other multimedia signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits** +- Series N Maintenance: international sound programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality, telephone installations, local line networks +- Series Q Switching and signalling +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminals for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communication +- Series Z Programming languages \ No newline at end of file diff --git a/marked/M/T-REC-M.1301-200101-I_PDF-E/raw.md b/marked/M/T-REC-M.1301-200101-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..168317403c179534504ee1c3159921082619acd8 --- /dev/null +++ b/marked/M/T-REC-M.1301-200101-I_PDF-E/raw.md @@ -0,0 +1,689 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1301** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(01/2001) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**General description and operational procedures +for international SDH leased circuits** + +ITU-T Recommendation M.1301 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **General description and operational procedures for international SDH leased circuits** + +## **Summary** + +This Recommendation provides a general description of international synchronous digital leased circuits with an SDH presentation to the Customer, and of the basic requirements for their effective operation. The case of mixed SDH/PDH leased circuits is also described. + +## **Source** + +ITU-T Recommendation M.1301 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. + +## **Keywords** + +Digital leased circuit, digital path, international synchronous digital leased circuit, network termination equipment, path OverHead (POH), path terminating equipment, path termination point, section OverHead (SOH), synchronous Digital Hierarchy (SDH), trail, trail Termination Point (TTP). + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +| | | Page | +|-------|--------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 4 | +| 4 | Abbreviations..... | 4 | +| 5 | General description of international synchronous digital leased circuits ..... | 6 | +| 5.1 | Leased circuit configuration ..... | 6 | +| 5.2 | Network interfaces..... | 8 | +| 5.3 | Timing and network synchronization ..... | 9 | +| 5.4 | Designations..... | 9 | +| 5.5 | Performance ..... | 9 | +| 6 | Operational procedures ..... | 9 | +| 6.1 | Control and sub-control stations ..... | 10 | +| 6.2 | BIS procedures..... | 10 | +| 6.2.1 | Section-by-section testing and In-Service Monitoring (ISM) ..... | 11 | +| 6.2.2 | National circuit portions ..... | 11 | +| 6.2.3 | International circuit portions ..... | 11 | +| 6.2.4 | BIS using an alternative international link ..... | 12 | +| 6.2.5 | End-to-end test..... | 12 | +| 6.2.6 | Alternative end-to-end test ..... | 12 | +| 6.3 | Maintenance procedures ..... | 13 | +| 6.3.1 | Performance monitoring and data collection..... | 13 | +| 6.3.2 | Performance history, thresholding and reporting ..... | 14 | +| 6.3.3 | Maintenance intervention tests ..... | 14 | +| 6.3.4 | Test configurations ..... | 15 | +| 6.3.5 | Test access at DCS equipment..... | 15 | +| 6.3.6 | Returning-to-service tests ..... | 15 | +| 6.3.7 | Planned maintenance ..... | 15 | +| 7 | Maintenance records ..... | 16 | +| 8 | Protection and reserve arrangements ..... | 16 | +| | Annex A – Fault management ..... | 16 | +| A.1 | Initial reception of a fault report ..... | 16 | +| A.2 | Fault information exchange ..... | 17 | +| A.3 | Fault localization..... | 18 | + +| | Page | +|-----------------------------------------------------------------------|-------------| +| A.4 Circuit restoration ..... | 19 | +| A.5 Temporary service restoration ..... | 19 | +| A.5.1 Mechanisms for implementing temporary service restoration ..... | 19 | +| A.5.2 Time to restore service ..... | 19 | +| A.5.3 Restoration procedure..... | 20 | +| A.5.4 Returning to normal routing ..... | 20 | +| A.5.5 Information that should be exchanged..... | 20 | +| A.6 Automatic rerouting of international SDH transmission links ..... | 20 | +| A.7 Precautions to be taken in the use of DCSs ..... | 20 | + +## **General description and operational procedures for international SDH leased circuits** + +# **1 Scope** + +This Recommendation defines international synchronous digital leased circuits with an SDH presentation to the Customer (hereafter called SDH leased circuits) which are transported via STM-N transmission links over a variety of transmission media using a number of network technologies. The case of mixed SDH/PDH leased circuits is also described. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T G.701 (1993), *Vocabulary of digital transmission and multiplexing and Pulse Code Modulation (PCM) terms.* +- [2] ITU-T G.703 (1998), *Physical/electrical characteristics of hierarchical digital interfaces.* +- [3] ITU-T G.707/Y.1322 (2000), *Network node interface for the synchronous digital hierarchy (SDH).* +- [4] ITU-T G.708 (1999), *Sub STM-0 network node interface for the synchronous digital hierarchy (SDH).* +- [5] ITU-T G.783 (2000), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks.* +- [6] ITU-T G.784 (1999), *Synchronous digital hierarchy (SDH) management.* +- [7] ITU-T G.803 (2000), *Architectures of transport networks based on the synchronous digital hierarchy (SDH).* +- [8] ITU-T G.811 (1997), *Timing characteristics of primary reference clocks.* +- [9] ITU-T G.812 (1998), *Timing requirements of slave clocks suitable for use as node clocks in synchronization networks.* +- [10] ITU-T G.822 (1988), *Controlled slip rate objectives on an international digital connection.* +- [11] ITU-T G.823 (2000), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy.* +- [12] ITU-T G.824 (2000), *The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy.* +- [13] ITU-T G.825 (2000), *The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH).* +- [14] ITU-T G.826 (1999), *Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate.* + +- [15] ITU-T G.827 (2000), *Availability parameters and objectives for path elements of international constant bit-rate digital paths at or above the primary rate.* +- [16] ITU-T G.828 (2000), *Error performance parameters and objectives for international constant bit rate synchronous digital paths.* +- [17] ITU-T G.841 (1998), *Types and characteristics of SDH network protection architectures.* +- [18] ITU-T G.842 (1997), *Interworking of SDH network protection architectures.* +- [19] ITU-T G.957 (1999), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy (SDH).* +- [20] ITU-T I.432.1 (1999), *B-ISDN user-network interface – Physical layer specification: General characteristics.* +- [21] ITU-T I.432.2 (1999), *B-ISDN user-network interface – Physical layer specification: 155 520 kbit/s and 622 080 kbit/s operation.* +- [22] ITU-T I.432.3 (1999), *B-ISDN user-network interface – Physical layer specification: 1544 kbit/s and 2048 kbit/s operation.* +- [23] ITU-T I.432.4 (1999), *B-ISDN user-network interface – Physical layer specification: 51 840 kbit/s operation.* +- [24] ITU-T I.432.5 (1997), *B-ISDN user-network interface – Physical layer specification: 25 600 kbit/s operation.* +- [25] ITU-T M.20 (1992), *Maintenance philosophy for telecommunication networks.* +- [26] ITU-T M.34 (1988), *Performance monitoring on international transmission systems and equipment.* +- [27] ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [28] ITU-T M.85 (1992), *Fault report points.* +- [29] ITU-T M.90 (1988), *Sub-control stations.* +- [30] ITU-T M.1012 (1988), *Circuit control station for leased and special circuits.* +- [31] ITU-T M.1013 (1988), *Sub-control station for leased and special circuits.* +- [32] ITU-T M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [33] ITU-T M.1340 (2000), *Performance objectives, allocations and limits for international PDH leased circuits and supporting data transmission links and systems.* +- [34] ITU-T M.1370 (1998), *Bringing-into-service of international data transmission systems.* +- [35] ITU-T M.1375 (1998), *Maintenance of international data transmission systems.* +- [36] ITU-T M.1380 (2000), *Bringing-into-service of international leased circuits that are supported by international data transmission systems.* +- [37] ITU-T M.1385 (2000), *Maintenance of international leased circuits that are supported by international data transmission systems.* +- [38] ITU-T M.1400 (2000), *Designations for inter-operator networks.* +- [39] ITU-T M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network.* +- [40] ITU-T M.1520 (1992), *Standardized information exchange between Administrations.* +- [41] ITU-T M.1530 (1999), *Network maintenance information.* + +- [42] ITU-T M.1532 (2000), *Network maintenance service performance agreement (MSPA)*. +- [43] ITU-T M.1535 (1996), *Principles for maintenance information to be exchanged at customer contact point (MICC)*. +- [44] ITU-T M.1537 (1997), *Definition of maintenance information to be exchanged at customer contact point (MICC)*. +- [45] ITU-T M.1539 (1999), *Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC)*. +- [46] ITU-T M.1540 (1994), *Exchange of information for planned outages of transmission systems*. +- [47] ITU-T M.1560 (1992), *Escalation procedure for international leased circuits*. +- [48] ITU-T M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH paths, sections and transmission systems*. +- [49] ITU-T M.2101 (2000), *Performance limits and objectives for bringing-into-service and maintenance of international SDH paths and multiplex sections*. +- [50] ITU-T M.2102 (2000), *Maintenance thresholds and procedures for recovery mechanisms (protection and restoration) of international SDH VC trails (paths) and multiplex section*. +- [51] ITU-T M.2110 (1997), *Bringing-into-service of international PDH paths, sections and transmission systems and SDH paths and multiplex sections*. +- [52] ITU-T M.2120 (2000), *PDH path, section and transmission system and SDH path and multiplex section fault detection and localization procedures*. +- [53] ITU-T M.2130 (2000), *Operational procedures for the maintenance of the transport network*. +- [54] ITU-T M.2140 (2000), *Transport network event correlation*. +- [55] ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [56] ITU-T M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*. +- [57] ITU-T M.3208.2 (1999), *TMN management services for dedicated and reconfigurable circuits network: Connection management of pre-provisioned service link connections to form a leased circuit service*. +- [58] ITU-T M.3208.3 (2000), *TMN management services for dedicated and reconfigurable circuits network: Virtual private network service*. +- [59] ITU-T M.3320 (1997), *Management requirements framework for the TMN X-interface*. +- [60] ITU-T M.3300 (1998), *TMN F-interface requirements*. +- [61] ITU-T M.3400 (2000), *TMN management functions*. +- [62] ITU-T O.172 (2001), *Jitter and wander measuring equipment for digital systems which are based on the synchronous digital hierarchy (SDH)*. +- [63] ITU-T O.181 (1996), *Equipment to assess error performance on STM-N interfaces*. +- [64] ITU-T V.54 (1988), *Loop test devices for modems*. +- [65] ITU-T X.150 (1988), *Principles of maintenance testing for public data networks using Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) test loops*. +- [66] ITU-T X.790 (1995), *Trouble management function for ITU-T applications*. + +[67] ITU-T M.2101.1 (1997), *Performance limits for bringing-into-service and maintenance of international SDH paths and multiplex sections*.1 + +# 3 Terms and definitions + +General terminology and definitions relating to this Recommendation are provided in ITU-T G.701 [1] and ITU-T M.60 [27]. For the purposes of this Recommendation, the following definitions also apply: + +**3.1 SDH digital path:** a subset of a Digital Trail carrying the SDH payload and associated Path OverHead (POH) through the layered transport network between the two Path Termination Points (PTPs) within the Path Terminating Equipment (PTE). The SDH digital path usually comprises both access network portions and core transport network portions. The network portions comprise one or more SDH regenerator and/or multiplex sections, each of which has an associated Section OverHead (SOH). An SDH digital path may be bidirectional or unidirectional and may comprise both Customer-owned portions and Network Operator (NO)-owned portions. + +**3.2 SDH digital trail:** the complete end-to-end connection carrying the SDH payload and associated POH through the layered transport network between the two Trail Termination Points (TTPs). + +**3.3 SDH leased circuit:** a subset of a SDH digital path between the two Network Terminating Equipments (NTEs). An SDH leased circuit may be bidirectional or unidirectional. The SDH leased circuit end points are at the boundaries between the NO(s), or between the NO and the End-user Customer. At this point, the SDH signal contains the SOH, the payload and the associated POH. However, it should be noted that due to regulatory and/or commercial conditions, access to the POH for In-Service Monitoring (ISM) purposes may not be possible at this point by the NO e.g. when the Customer owns the PTE. The Customer should use the standard POH defined in ITU-T G.707 [3]. This is an issue for further study. + +For the purposes of this Recommendation, the terms "path" and "trail" are assumed to be synonymous. + +**3.4 Service Level Agreement (SLA):** an SLA or Contract is a set of appropriate procedures and targets formally or informally agreed between Network Operators/Service Providers (NOs/SPs) or between NOs/SPs and Customers, in order to support ITU-T Recommendations, achieve and maintain specified Quality of Service (QoS). The SLA may be an integral part of the Contract. These procedures and targets are related to specific circuit/service availability, error performance, Ready For Service (RFS) date, Mean Time Between Failures (MTBF), Mean Time to Restore Service (MTRS), Mean Time To Repair (MTTR). + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|----------------------------| +| ADM | Add-Drop Multiplex | +| AIS | Alarm Indication Signal | +| API | Access Point Identifier | +| ATM | Asynchronous Transfer Mode | +| BBE | Background Block Error | + +--- + +1 Maintenance of SDH systems designed to meet the long-term error performance of ITU-T G.826 should be maintained to ITU-T M.2101.1. + +| | | +|--------|-----------------------------------------------| +| BIP-n | Bit Interleaved Parity – nth level | +| B-ISDN | Broadband-Integrated Services Digital Network | +| CP | Customer's Premises | +| CRC | Cyclic Redundancy Checksum | +| CSES | Consecutive Severely Errored Second | +| DCS | Digital Cross-connect System | +| EMS | Element Management System | +| ES | Errored Second | +| HO-TCM | Higher Order – Tandem Connection Monitoring | +| IG | International Gateway | +| IP | Internet Protocol | +| ISM | In-Service Monitoring | +| LAPD | Link Access Protocol for D-channel | +| LO-TCM | Lower Order – Tandem Connection Monitoring | +| MS | Multiplex Section | +| MTBF | Mean Time Between Failures | +| MTRS | Mean Time to Restore Service | +| MTTR | Mean Time To Repair | +| NE | Network Element | +| NMC | Network Management Centre | +| NMS | Network Management System | +| NNI | Network Node Interface | +| NO | Network Operator | +| NOC | Network Operations Centre | +| NTE | Network Terminating Equipment | +| OC-n | Optical Carrier – nth level | +| OS | Operations System | +| PDH | Plesiochronous Digital Hierarchy | +| POH | Path OverHead | +| PTE | Path Terminating Equipment | +| PTP | Path Termination Point | +| QoS | Quality of Service | +| RFS | Ready For Service | +| RS | Regenerator Section | +| SDH | Synchronous Digital Hierarchy | +| SES | Severely Errored Second | +| SLA | Service Level Agreement | + +| | | +|-------|------------------------------------------| +| SMS | Service Management System | +| SOH | Section OverHead | +| SP | Service Provider | +| STM-N | Synchronous Transport Module – Nth level | +| TCM | Tandem Connection Monitoring | +| TE | Terminal Equipment | +| TIC | Terminal International Centre | +| TM | Terminal Multiplexer | +| TMN | Telecommunication Management Network | +| TNC | Terminal National Centre | +| TTP | Trail Termination Point | +| UNI | User Network Interface | +| UTC | Universal Coordinated Time | +| VC-n | Virtual Container – nth level | + +# 5 General description of international synchronous digital leased circuits + +An international synchronous digital leased circuit with SDH presentation to the Customer is comprised of an SDH transmission trail between Network Terminating Equipments (NTEs). The NTEs may be simple connectors, intelligent loopback devices or more sophisticated equipment. Both the national and international portions of the leased circuit may be provided by more than one NO. + +The TTPs may be owned, operated and maintained by the NO/SP or the Customer. Where the Customer owns the TTPs, the POH shall be made available to the NO/SP for operation and maintenance purposes. The detailed use of the POH is for further study. The interface to the Customer may be an electrical interface as described in ITU-T G.703 [2] and ITU-T G.707 [3], or an optical interface as described in ITU-T G.707 [3] and ITU-T G.957 [19]. + +The SDH leased circuit shall employ the frame structures, POH and SOH defined in ITU-T G.707 [3] and is transported over an SDH network at varying STM-N levels of the SDH, or over a mixed SDH/PDH network. The SDH leased circuit may be provisioned manually or semi-automatically via TMN facilities as described in ITU-T M.3208.1 [56]. Before provisioning, the parties concerned shall agree on the payload structure at the interfaces and the use of the POH and SOH. DCEs connected to the leased circuit may have test loopback facilities as described in ITU-T V.54 [64] or ITU-T X.150 [65]. + +The path overhead for the leased circuit should be configured as specified in ITU-T G.707. In the case of a VC3, the signal label byte C2 should be set as specified in 9.3.1.3/G.707. In the case of a VC12, the V5 byte should be set as specified in 9.3.2.1/G.707. + +NOTE – Some aspects of the POH need further clarification e.g. the case of LO-TCM requires valid J2, N2 and V5 bytes. + +## 5.1 Leased circuit configuration + +Figure 1 shows the basic constituent parts of an international point-to-point leased circuit without showing the SDH equipments that support the leased circuit. + +![Figure 1/M.1301 – Constituent parts of an international leased circuit. The diagram shows a linear sequence of nodes: CP, TNC, TIC, TIC, TNC, CP. Horizontal double-headed arrows indicate three segments: 'National portion' between the first CP and the first TIC, 'International portion' between the two TICs, and 'National portion' between the second TIC and the second CP. A longer double-headed arrow labeled 'International link' and 'International leased circuit' spans between the two TNCs. A legend at the bottom left defines CP as Customer's Premises, TIC as Terminal International Centre, and TNC as Terminal National Centre. The code T0414760-00 is in the bottom right.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 1/M.1301 – Constituent parts of an international leased circuit. The diagram shows a linear sequence of nodes: CP, TNC, TIC, TIC, TNC, CP. Horizontal double-headed arrows indicate three segments: 'National portion' between the first CP and the first TIC, 'International portion' between the two TICs, and 'National portion' between the second TIC and the second CP. A longer double-headed arrow labeled 'International link' and 'International leased circuit' spans between the two TNCs. A legend at the bottom left defines CP as Customer's Premises, TIC as Terminal International Centre, and TNC as Terminal National Centre. The code T0414760-00 is in the bottom right. + +**Figure 1/M.1301 – Constituent parts of an international leased circuit** + +The national portions of the leased circuit may in fact cross more than one NO and the responsibility for providing the circuit may be a SP who owns only part or even none of the network equipment supporting the circuit. The SP will negotiate with NOs (providers) to assign network paths as required, and with the Customer regarding visits to their premises for any installation of terminal equipment and testing of the circuit. + +An expanded version of Figure 1 based on Figure III.1/G.826 [14] shows a leased circuit existing between two NTEs via various International Gateways (IGs) in a multi-operator network, but the end-to-end digital path existing between two Terminal Equipments (TEs) includes a private network(s) as shown below in Figure 2: + +![Figure 2/M.1301 – Constituent parts of an SDH leased circuit and digital path. The diagram shows a sequence of nodes: TE, NTE, IG, IG, IG, IG, NTE, TE. Horizontal double-headed arrows indicate: 'International portion' between the first NTE and the last NTE; 'Leased circuit' between the first IG and the last IG; and 'End-to-end digital path' between the two TEs. Vertical lines from the last NTE to the final TE are labeled 'National portion' and 'Private network'. A legend at the bottom left defines IG as International Gateway, NTE as Network Terminal Equipment, and TE as Terminal Equipment. The code T0414770-00 is in the bottom right.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Figure 2/M.1301 – Constituent parts of an SDH leased circuit and digital path. The diagram shows a sequence of nodes: TE, NTE, IG, IG, IG, IG, NTE, TE. Horizontal double-headed arrows indicate: 'International portion' between the first NTE and the last NTE; 'Leased circuit' between the first IG and the last IG; and 'End-to-end digital path' between the two TEs. Vertical lines from the last NTE to the final TE are labeled 'National portion' and 'Private network'. A legend at the bottom left defines IG as International Gateway, NTE as Network Terminal Equipment, and TE as Terminal Equipment. The code T0414770-00 is in the bottom right. + +**Figure 2/M.1301 – Constituent parts of an SDH leased circuit and digital path** + +The portion between the NTE and TE may be outside the NO's control, provided by a private network over which a public NO has no control. Thus in the case of SDH leased circuits, end-to-end performance objectives cover only the portion situated between the two NTEs. + +Five types of SDH leased circuits can be identified: + +- 1) NO to NO circuit, where the NOs terminate the POH. This includes mixed SDH/SONET interworking where the POH and SOH is terminated and rebuilt, e.g. VC-3 to STS-1; + +- 2) end-user Customer to end-user Customer circuit where the POH is terminated at the end-user Customer's premises, but there is a facility for communication between the end-user Customer's terminal equipment. In this case the NOs transporting the circuit act as transit operators; +- 3) end-user Customer to NO circuit where one NO hands off the leased circuit to another NO. This is a subset of type 2) where one NO is acting as a Customer of another NO, and again could involve SDH/SONET interworking; +- 4) mixed SDH/PDH leased circuit where the traffic is accepted/delivered at one end in a PDH interface and at the other end buried in a SDH interface e.g. 2 Mbit/s PDH to STM-1 where the Customer has access to 1920 kbit/s in PDH at one end and VC-12 in SDH at the other end; +- 5) PDH leased circuit with SDH presentation to the Customer. + +Other types of SDH leased circuits include point-to-multipoint circuits, dedicated semi-permanent or reconfigurable circuits (with time-of-day switching) as described in ITU-T M.3208.1 [56], and unidirectional circuits (e.g. video broadcast circuits). + +## 5.2 Network interfaces + +Most (if not all) SDH leased circuits will employ SDH equipment and transmission systems to provide a synchronous digital path between the end points of the circuit (apart from types 4) and 5) where PDH equipment will be at one or both ends of the circuit). This may include sitting an SDH Add-Drop Multiplexer (ADM) or Terminal Multiplexer (TM) on the CP at the end of the access network transport link. The location of the interface (NTE) to the Customer depends as much on regulatory constraints as it does on technical decisions. + +ITU-T G.707 [3] and ITU-T G.708 [4] define the Network Node Interfaces (NNIs) for SDH that apply to both electrical and optical interfaces. It is clear from existing equipment practice that both electrical and optical interfaces are being offered to Customers as desired. + +The User Network Interfaces (UNIs) already being offered to users cover a broad range from the so-called "ATM25" interface at 25.6 Mbit/s to STM-4 (OC-12) at 622 Mbit/s and even STM-16 (OC-48) at 2.4 Gbit/s. The main Recommendations covering these are summarized below: + +- I.432.1 [20] – General characteristics of B-ISDN User-Network Interfaces physical layer; +- I.432.2 [21] – 155 520 kbit/s and 622 080 kbit/s B-ISDN UNI operation; +- I.432.3 [22] – 1544 kbit/s and 2048 kbit/s B-ISDN UNI operation; +- I.432.4 [23] – 51 840 kbit/s B-ISDN UNI operation; +- I.432.5 [24] – 25 600 kbit/s B-ISDN UNI operation; +- G.703 [2] – Physical/electrical characteristics of hierarchical digital interfaces; +- G.707/Y.1322 [3] – Network Node Interface (NNI) for the SDH; +- G.708 [4] – Bit rates and multiplexing structures for sub-STM-0 interfaces; +- G.957 [19] – Optical interfaces for equipments and systems relating to the SDH. + +Concatenated versions of SDH bandwidths are also in use to provide very high bandwidth transmission "pipes" for ATM and IP. This concatenation may be contiguous within one SDH signal or virtual using a number of SDH signals. When using virtual concatenation, differential delays need to be carefully controlled and some kind of frame reference signal is required. + +## **5.3 Timing and network synchronization** + +The timing feed at each end of an international SDH leased circuit should be derived from a primary reference clock operating in accordance with ITU-T G.811 [8]. In general, the SDH leased circuit timing will be derived from the SDH network supporting it and not from the Customer's equipment. The network clock is normally used to drive the Customer's equipment. If the leased circuit is provided by multiple NOs, agreement must be reached on the source of the master clock or the provision of appropriate facilities to take account of timing differences. + +## **5.4 Designations** + +The form of designations for international SDH leased circuits will be described in ITU-T M.1400 [38]. The details of this are for further study. + +## **5.5 Performance** + +Three key areas of performance need to be checked when bringing-into-service or maintaining an SDH leased circuit. These are: + +- error performance; +- timing performance; +- availability performance. + +ITU-T M.2101 [49] defines the error performance limits and allocation of the SDH digital trails which support SDH leased circuits. ITU-T G.811 [8], ITU-T G.812 [9], ITU-T G.822 [10], ITU-T G.823 [11], ITU-T G.824 [12] and ITU-T G.825 [13] define the timing performance which should be maintained. Delay performance is for further study. ITU-T G.827 [15] defines the physical layer availability for a digital path. + +# **6 Operational procedures** + +ITU-T M.2110 [51] covers the setting up and Bringing-Into-Service (BIS) of international digital paths. Maintenance issues are covered in ITU-T M.2120 [52]. General operational procedures for locating and clearing transmission faults are covered in ITU-T M.2130 [53]. The performance limits for bringing-into-service and maintenance of international SDH paths and multiplex sections are defined in ITU-T M.2101 [49]. + +The BIS (provisioning) of SDH leased circuits is increasingly based on the TMN approach to network and service management since the SDH transmission equipment that supports the leased circuits consists of highly intelligent software-intensive Network Elements (NEs) that are managed by SDH Element Management Systems (EMSs) and higher level Network Management Systems (NMSs). This includes the exchange of information electronically across TMN Q and X interfaces for management purposes, both within one NO/SP, and between NO/SPs since these circuits will often cross a number of NO/SP jurisdictions. ITU-T M.3208.1 [56], ITU-T M.3208.2 [57] and ITU-T M.3208.3 [58] define TMN management services for configurable and reconfigurable leased circuits within a multi-operator environment. + +Also, the maintenance (fault reporting, localization and testing) of these SDH leased circuits will be increasingly based on remotely managed test resources from a Network Management Centre (NMC) or Network Operations Centre (NOC). These test resources may be a mixture of built-in capabilities within the network equipment (e.g. POH, SOH, TCM, etc.) or remote test heads attached at strategic network access points e.g. a Digital Cross-connect System (DCS) used to configure the circuits. The following subclauses outline the procedures for Fault, Configuration, Administration and Performance Management, which are four of the key TMN managed functional areas defined in ITU-T M.3010 [55] and ITU-T M.3400 [61]. A new Recommendation in the M.3208.x-series is being drafted on TMN test management. + +## 6.1 Control and sub-control stations + +A dual control or a control and sub-control relationship shall be agreed at the BIS stage. Where a control and sub-control relationship exists, responsibilities will be as described in ITU-T M.80 [28], ITU-T M.90 [29], ITU-T M.1012 [30] and ITU-T M.1013 [31]. However, in order to achieve the fastest possible response times for maintenance activities on behalf of Customers, it is acceptable for both terminal stations of an international SDH leased circuit to assume control station status. It is essential however for the control stations involved to develop effective mechanisms and procedures for coordinating maintenance activities, and that they inform each other of specific maintenance actions as rapidly as possible to avoid confusion. TMN management systems operating over X interfaces between NO/SPs can greatly facilitate this process. + +It is possible for a third-party centre to be designated as the control station. In this situation the leased circuit may not be routed via this centre, nor need this centre be situated in a terminal or transit country of the leased circuit. Clearly, close co-operation is required between the SP and the NOs providing the leased circuit. In some cases, the international SDH leased circuit may be provided by one NO/SP acting as a "one stop shop", i.e. a primary SP (sometimes called a "retailer") who sub-contracts other parts of the SDH leased circuit to another NO to carry on their behalf (sometimes called a "wholesaler"). One or more NOs involved with providing the SDH trail may use cooperating network/service management systems communicating via TMN X interfaces (see ITU-T M.3320 [59]) to provision and maintain the SDH leased circuit (see ITU-T M.3208.1 [56], ITU-T M.3208.2 [57] and ITU-T M.3208.3 [58]). + +## 6.2 BIS procedures + +The basic BIS procedures for SDH leased circuits should be similar to those defined in existing ITU-T M.1370 [34], ITU-T M.1380 [36] and ITU-T M.2110 [51]. These include the preliminary exchange of information about the leased circuit configuration and interfacing, designation and routing, bringing-into-service schedule and coordination between stations, contact personnel details, details of any special maintenance or fault reporting arrangements, performance limits and test equipment to be used, and measurements against limits (see ITU-T M.80 [28], ITU-T M.90 [29], ITU-T M.1012 [30], ITU-T M.1013 [31], ITU-T M.1045 [32], ITU-T M.1400 [38] and ITU-T M.1510 [39]). The test equipment used should conform to ITU-T O.172 [62] and ITU-T O.181 [63]. + +Checks of individual SDH network equipment comprising the circuit should be performed. This should include confirming the interworking of alarms, e.g. Alarm Indication Signal (AIS) and, ideally, simulated error transmissions to check other alarm operations at both local and distant ends. Specific checks of POH, SOH and payload structure should be made to verify the agreed format. Note that full end-to-end checks of POH cannot be made until the VC-n path is equipped. This may require the Customer to connect their CPE to the SDH interface. An unequipped VC-n path may create spurious alarms and inhibit protection switching actions. + +BIS tests should ideally include periods of normal industrial activity to be representative of typical network conditions. Performance limits of ES, SES and BBE counts should be met simultaneously for the test results to be considered acceptable. Typical performance objectives, allocations and limits are given in ITU-T M.2101 [49] for SDH digital paths and multiplex sections and in ITU-T M.1340 [33] for mixed PDH/SDH leased circuits, however routed. The possible development and application of performance objectives for other parameters such as transmission delay, timing jitter, etc., are for further study. All test results obtained during the BIS tests should be retained as a "fingerprint" of the SDH leased circuit for possible future reference during maintenance activities. + +In the past PDH world, to reflect operational requirements for out-of-service testing, test durations of 24 hours, of 1 hour and of 15 minutes were often used. In an all-SDH transport environment with inherent ISM capabilities, much shorter provisioning and BIS testing time-scales can be achieved. With regard to bringing-into-service testing, the 1-month evaluation period suggested in + +ITU-T G.826 [14] and ITU-T G.828 [16] is not realistic in an operational environment (see ITU-T M.2101). A shorter test duration is required, particularly with strong commercial pressures to put a leased circuit into service or restore it after repair. However, it must be recognized that test results obtained over 24 hours or less are inherently less reliable. + +It should be noted then that a 24-hour or less test duration can be expected to give a particularly reliable indication of transmission performance. National circuit portions and international circuit portions may be set up and tested simultaneously or consecutively. However, careful harmonization of these procedures is required to ensure overall end-to-end performance is acceptable. + +### **6.2.1 Section-by-section testing and In-Service Monitoring (ISM)** + +BIS procedures will increasingly use TMN and ISM techniques, but end-to-end tests of the overall leased circuit may require appropriate personnel to be present at the Customer's premises in the two end points. The cooperation of staff, e.g. at the TICs/IGs or Customer Care Centre may also be required to overcome language or technical difficulties where the leased circuit crosses NO/SP and/or international boundaries. It may be easier to perform BIS tests on a section-by-section basis although an overall end-to-end check must be performed. One of the major issues for SDH leased circuits is that the SDH transport network supporting them will often be optical fibre transmission systems and there may not be readily available test access points in transport network sections. New SDH leased circuits may be added to existing higher-order transport network bearers (see 6.2.3). The use of ISM capabilities built into the SDH NEs coupled to EMSs and NMSs can greatly assist. + +### **6.2.2 National circuit portions** + +Before setting up the national circuit portions, suitable performance limits for the national circuit portions should be developed and exchanged between the Network Operators/Service Providers involved, always ensuring that the overall end-to-end performance can be achieved. + +### **6.2.3 International circuit portions** + +Using the in-service performance monitoring available, and if the error performance of the supporting transport system is acceptable, all new circuits should be tested for 15 minutes. + +In the case where a number of circuits using the same higher-order transport system are brought into service at the same time, and in-service performance monitoring is not available, the first circuit should be tested for 24 hours, and the remaining circuits could be tested for 15 minutes each. Any portions of the circuit, which are not supported by the higher-order transport system, should be tested for 24 hours. + +The performance limits given in ITU-T M.1340 [33] should be met for any mixed PDH/SDH leased circuits. Performance limits for SDH leased circuits are given in ITU-T M.2101 [49]. Where there is little confidence regarding the capabilities of a particular international transport system, or where the short duration test objectives were not met, a 24-hour test should be performed using the limits given in ITU-T M.1340 [33] or ITU-T M.2101 [49] as appropriate. In the event that the 24-hour limits are not met, Network Operators/Service Providers should agree to an appropriate course of action. + +Where the international circuit portion extends significantly beyond the tributary interfaces of a particular international higher-order transport system (e.g. where a transit routing involves the interconnection of two international SDH systems) additional tests may be required. NOs/SPs should ensure that all parts of the international circuit portion are fully tested. Suitable additional limits should be agreed between the NOs/SPs involved. Consistency with ITU-T M.1340 [33] and ITU-T M.2101 [49] should be sought wherever possible. + +### **6.2.4 BIS using an alternative international link** + +If any portion of the link, which would normally be used to carry the international leased circuit, is restored onto an alternative route before BIS testing is commenced, or during BIS testing, then testing may proceed, or continue, if the following three criteria are met: + +- 1) The performance of the alternative link is known to be acceptable; +- 2) The alternative link uses the same transmission media as the original link; +- 3) The length of the alternative link is not substantially different from the original link. + +If these criteria are not met, then testing should be postponed, or halted, until the original link is returned to service. + +If a single unavailability event occurs during the BIS test, and the cause of this event is precisely known and not recurrent, then this event should be ignored in the test results. + +### **6.2.5 End-to-end test** + +It will normally be required to perform an end-to-end test to confirm overall integrity and stability. A 24-hour test duration is recommended. Test limits should include allowances for the international and the two national circuit portions. NOs/SPs should pay particular attention to highlighting any problems that may be associated with the interworking of separately timed networks, especially for the first circuit provision that uses a particular equipment configuration. In particular, the jitter/wander performance requirements of ITU-T G.823 [11], ITU-T G.824 [12] and ITU-T G.825 [13] should be respected as appropriate to the leased circuit and supporting transport network. + +Depending upon the loopback capabilities provided by the NTEs at the Customer's premises, it may be possible to perform end-to-end tests, combined with ISM, from intermediate points within the network (e.g. at TICs). + +Where loop tests are employed it is proposed that no special additional performance allowance is made (i.e. doubling of limits is not recommended). + +### **6.2.6 Alternative end-to-end test** + +If NOs/SPs agree, based upon experience of similar network conditions, and in-service performance monitoring is available on the entire international transport system, a 2-hour end-to-end monitoring test may be performed. In this case, the BIS procedure is as follows: + +- 1) The national circuit portion is brought into service according to existing national procedures; +- 2) No international circuit portion test is carried out, as this portion has already been tested according to the procedures of ITU-T M.1370 [34] or ITU-T M.2110 [51] and in-service performance monitoring is being used to ensure that the performance of the higher-order transport system is acceptable; +- 3) For wholly SDH-routed circuits using a continuous POH, an end-to-end monitoring test of two hours is performed to verify the cross-connection capabilities of any digital cross-connect equipment used to configure the leased circuit. This test may be performed to a loopback at one or both ends. The performance limits for this test are given in Table 1/M.1340 [33] for mixed SDH/PDH leased circuits and in ITU-T M.2101 [49] for SDH-only leased circuits. There should be no clock slips or periods of unavailability during this test. If these conditions cannot be met, then the 24-hour test, as described above, should be carried out. For mixed SDH/PDH transported circuits, it may not be possible to perform a full end-to-end test, especially in the case of CPE owned by the end-user. In this case, a partial end-to-end test combined with ISM should be performed. + +As mentioned in 6.2.5, Network Operators/Service Providers should pay particular attention to highlighting any problems that may be associated with the interworking of separately timed + +networks, as these may not be evident from a 2-hour test. Where the performance limits are not met, fault localization should be performed and the faults rectified. + +## **6.3 Maintenance procedures** + +The basic maintenance procedures for SDH leased circuits should be similar to those defined in existing ITU-T M.1375 [35], ITU-T M.1385 [37], ITU-T M.2120 [52] and ITU-T M.2130 [53]. These include fault reporting, sectionalization, localization and restoration procedures, with appropriate exchange of information between NOs/SPs and with Customers. ISM facilities should be used whenever possible for fault sectionalization, localization and diagnosis. Further information on fault management is contained in Annex A. + +It should be noted that, for more extensive measurements involving intrusive testing, the circuit will be interrupted and the service to the Customer affected. This in turn may impact the SLA/Contract and result in penalties or rebates. Maintenance tests should therefore be kept as short as possible to avoid significantly extending out-of-service time. As with BIS procedures, any test equipment used should conform to ITU-T O.172 [62] and ITU-T O.181 [63]. Maintenance performance thresholds and procedures for protection of SDH leased circuits should in general follow the same principles defined in ITU-T M.20 [25], ITU-T M.34 [26], ITU-T M.2100 [48], ITU-T M.2101 [49], ITU-T M.2102 [50], ITU-T M.2120 [52] and ITU-T M.2130 [53]. + +Round-the-clock "help-desks" and TMN modules enable test and monitoring to be centralized and activated, for improved Customer service. For example, prompt information to the Customer about the fault condition detected and countermeasures planned, direct intervention of suitable technical teams, etc. can be driven from a Service Management System (SMS) situated in a Customer Care Centre and/or NMS situated in a NOC or NMC. The aim is to always respect the SLA contractual commitments to the Customers. + +### **6.3.1 Performance monitoring and data collection** + +Performance data is normally collected in terms of event counts associated with the performance parameters indicated in ITU-T G.826 [14], ITU-T G.828 [16], ITU-T M.2100 [48] and ITU-T M.2101 [49] using ISM. The performance primitives (anomalies and defects) are processed by the SDH NEs into performance parameters and accumulated over 15-minute and 24-hour intervals. The current and historical performance data is time stamped and stored in performance registers which are then interrogated by the Operations System (OS) managing the NEs and reported upwards to the NMS and SMS managing the SDH leased circuit service supported by the SDH network. Performance events are collected and stored independently for each direction of transmission of the circuit. The SDH path is monitored using the BIP-8 code with even parity provided in the POH byte B3. Additional monitoring capability for high bit rate VC-4-Xc trails is under study. Performance event counts are inhibited during periods of unavailability as defined in ITU-T G.826 [14], ITU-T G.828 [16] and ITU-T G.827 [15]. Any change of availability state is also time stamped and recorded in the performance registers. Full details of performance monitoring by SDH NEs are given in ITU-T G.707 [3], ITU-T G.783 [5], ITU-T G.784 [6] and ITU-T M.2101 [49]. Further information on transport network event correlation and handling of performance data can be found in ITU-T M.2140 [54]. + +Where the SDH leased circuit crosses a number of SDH sections, performance monitoring may include Tandem Connection Monitoring (TCM) using the B3 bytes in the VC-n overhead of each of the higher-order VCs that make up the Tandem Connection (TC) as described in ITU-T G.707 [3]. The TC also has a 32 kbit/s data link provided by part of the N1 byte in the first VC-n of the TC, which uses a LAPD message protocol to convey trace, status and performance report information. + +As stated earlier, regardless of who owns the CPE, the SDH POH specified in ITU-T G.707 [3] shall be used by the SDH digital path and made available at suitable monitoring points along the route. In the case of an end-Customer or another operator owning the POH terminating equipment, it may not + +be possible for one operator to access the POH at the ends of the digital path. However, the POH provided includes remote anomaly and defect information seen by the POH terminating equipment and returned to the distant end. Thus it is possible to assess the end-to-end error performance of the complete bidirectional path from one access point within the path i.e. from the user's viewpoint. However, it should be noted that not all VC-n SDH paths contained within a higher layer SDH signal can be monitored simultaneously on some SDH equipment. + +### **6.3.2 Performance history, thresholding and reporting** + +Performance history data are necessary to assess the recent performance of SDH leased circuits and transmission systems. Such information can be used to sectionalize faults and locate sources of intermittent errors. Performance monitoring thresholds may be set in the SDH NEs by the OS and threshold crossings detected and notifications generated as described in ITU-T M.20 [25], ITU-T M.34 [26], ITU-T M.2101 [49], ITU-T M.2102 [50], ITU-T M.2120 [52] and ITU-T M.2140 [54]. These notifications are normally generated autonomously. + +When thresholds of unacceptable or degraded performance levels are reached, maintenance action should be initiated independently of the performance measurement. A degraded performance result can be used to generate a fault report (commonly known as a "trouble ticket") to alert maintenance staff that SLA/Contract guarantees are not being met and action needs to be taken. This may include alerting the service billing system that a Customer is due for a discount or rebate. Other thresholds may be used for maintenance and longer-term quality analysis. The OS will use real time processing to assign maintenance priorities to these threshold crossings and information, using the performance supervision process described in ITU-T M.20 [25]. + +In general, two types of thresholds are used depending on the accumulation period for anomalies and defects. 15-minute monitoring periods with thresholds of ES, SES and BBE counts are used to detect transitions to or from unacceptable performance. 24-hour monitoring periods with thresholds of ES, SES and BBE counts are used to detect transitions to degraded performance. The thresholds are usually programmable from the OS to suit specific operating requirements. This may vary with importance of the circuit(s) supported by the path, transport technology employed or SLA/Contract values agreed with a Customer. Further information on performance thresholding is given in ITU-T M.2101 [49], ITU-T M.2102 [50], ITU-T M.2120 [52] and ITU-T M.2140 [54]. + +### **6.3.3 Maintenance intervention tests** + +Maintenance intervention tests should be kept as short as possible to avoid significantly extending the out-of-service time, and should be of a duration appropriate to the nature of the fault report received. It is assumed that, for maintenance intervention tests, the circuit shall only be withdrawn from service with the Customer's agreement, unless the circuit has completely failed. Where the leased circuit uses only part of the SDH transmission equipment channels, it may be possible to connect test equipment to monitor the performance of spare capacity. The data from such tests may provide a useful indication of the overall performance of the SDH transport network supporting the leased circuit. + +The duration of maintenance intervention tests will be dependent upon the nature of the fault report that has been received. Where a fault report suggests that the leased circuit has failed completely, a short test of basic integrity should be performed. Such tests, which are interpreted on a simple pass or fail basis, should normally be limited to a duration of 15 minutes with no SESs being observed. + +Where a fault report suggests that there has been an overall degradation of service, but that the circuit has not failed completely, a longer duration test will be appropriate. Where a longer duration test is to be performed, NO/SPs should agree a suitable test date and time with the Customer. The Customer may wish to retain access to the circuit until a more convenient time when a substantial out-of-service period may be more tolerable. When a 24-hour test is performed, NO/SPs should use the same limits that were developed for the initial BIS tests. + +### **6.3.4 Test configurations** + +Several test measurement configurations are possible (see Figure 1/M.2110 [51] for guidance). Any loopback facilities that may be available should be used when appropriate. DCEs connected to the leased circuits may have test loopback facilities as described in ITU-T V.54 [64] and ITU-T X.150 [65]. Care must be taken to avoid the simultaneous operation of multiple loopbacks on a particular circuit. Once the need for a loopback no longer exists, then care should be taken to ensure that it is removed. + +For digital loops, the continuity of a digital leased circuit can be tested, even through to the distant Customer's installation, if the specifications are compatible between NO/SPs. However, this requires the agreement of the NO/SPs and, in any case, of the Customer, since their circuit cannot be used at that time. In some networks, control of these loopbacks may be carried out using the TMN management capabilities. The details of these loopbacks for SDH are for further study. + +### **6.3.5 Test access at DCS equipment** + +An increasing number of transmission systems and circuits are configured using DCS equipment within transmission stations. These equipments are used to switch faulty digital paths over to standby paths when necessary. They also often provide the capability to divert transmission systems and circuits to test ports to which test equipment can be connected and used to measure performance and diagnose faults. Furthermore, this test equipment may be remotely controlled, possibly by the same management system that controls the DCS equipment. In any event, control of the two must be carefully synchronized. In some cases, simultaneous multiple access to test equipment (a "remote test head") is possible by multiple operational staff as multiple user sessions, with scripted test sequences. + +It is desirable that DCS equipment is capable of providing monitoring of selected digital paths before taking the path out of service. This allows in-service performance assessment and/or confirmation that a fault exists before breaking the path. Most DCS equipment provides both a "monitor" and a "split and terminate" functionality on the test ports. While the digital path is being monitored in-service, no interruption is experienced. Once a fault has been confirmed, the faulty path is split and the fault diagnosed. SDH DCS equipment is now commonplace in SDH transport networks, but SDH ADMs may also be used for test access. DCS and ADM equipment itself may be a useful source of fault and performance information from the built-in ISM. + +### **6.3.6 Returning-to-service tests** + +Returning-to-service tests should be of a duration that is appropriate to the nature of fault that has been cleared and should include observation of any network alarm facilities that may be available. Where a fault has caused a general degradation of service, a returning-to-service test with a short duration (e.g. 15 minutes) may not be appropriate and a longer-term test (e.g. 1 hour or 24 hours) should be used. + +Following corrective maintenance, the Customer should be asked to confirm that their application is functioning correctly. Only then can the service be said to be restored. When a fault is cleared, appropriate clearance information should be passed to any control or sub-control stations or customer care centres that have been involved with initial fault reporting and localization. + +#### **6.3.7 Planned maintenance** + +In cases of planned maintenance on the NO/SP's installations – transmission equipment, power equipment, cabling, etc. – which would cause or risk some performance degradation or unavailability of the digital leased circuit, reference is to be made to ITU-T M.1540 [46] and the terms of the SLA/Contract with the Customer. + +# 7 Maintenance records + +NO/SPs should ensure that up-to-date information is held on file to assist maintenance activities. Clause 6/M.1370 [34] and clause 6/M.1380 [36] provide details of information that should be available for PDH supporting systems and leased circuits respectively. The same kind of information should be kept for SDH leased circuits and supporting transport systems, together with any POH-specific or SOH-specific information in use by the circuit. In addition, a record should be kept of any particular maintenance agreement with the Customer, including for example a SLA/Contract. See also ITU-T M.1510 [39], ITU-T M.1530 [41], ITU-T M.1532 [42], ITU-T M.1535 [43], ITU-T M.1537 [44] and ITU-T M.1539 [45] for further information. Maintenance staff should refer to such agreements when dealing with a fault reported by the Customer. During maintenance operations, reference should be made to previous test results that are applicable to the circuit under test. Original BIS test results should be available for all leased circuits. + +Existing maintenance records should provide details of test equipment, test access points, test patterns and performance limits that are to be used. Test results from previous maintenance actions on all portions of the leased circuit may provide a useful indication of the overall performance of the SDH transport network supporting the leased circuit. The obligations set out in the leased circuit maintenance contract with the Customer, for example the SLA will be registered, and maintenance staff involved will refer to them whenever they are called in following a fault report by the Customer. In a TMN environment, this information will normally be available on a technician's client terminal connected to the SMS and/or NMS. NOs/SPs should also keep a log of circuit interruptions, over an adequate period, with a view to meeting any claims from Customers. + +# 8 Protection and reserve arrangements + +SDH leased circuits will normally be routed via SDH transmission networks employing network and/or sub-network protection e.g. in SDH rings. In some cases, Customers may require or NOs/SPs may decide to also provide alternate routing either at a physical or at a logical level through the network. ITU-T G.841 [17], ITU-T G.842 [18], ITU-T M.2102 [50] and ITU-T M.2130 [53] describe SDH network protection and restoration procedures. + +Some NOs/SPs may find it useful to nominate one or more reserve SDH transmission links for restoration purposes. This should be decided by bilateral agreement when designing and provisioning the SDH leased circuit, taking into account its importance and contracted availability normally specified in the SLA. Such reserve links or circuits must be set up or lined up to meet the requirements of the normal SDH leased circuit and, wherever possible, should follow a different route from the normal route of the leased circuit. Further information is given in ITU-T M.2130 [53]. + +# ANNEX A + +## Fault management + +### A.1 Initial reception of a fault report + +In general, fault information relating to an SDH leased circuit can originate from four sources: + +- a Customer trouble report (due to the failure or poor performance of the SDH leased circuit); +- a lower-order system operator (due to the failure or poor performance of a lower-order system that is supported as a channel or VC-n by the SDH leased circuit); +- the SDH leased circuit itself (through network alarms or distant NO); +- a network or higher-order system operator (with notification of the failure or poor performance of the higher-order network that supports this SDH leased circuit or recognition of a transmit problem from this SDH leased circuit). + +Trouble reports from Customers and information sent to them may be transmitted over an X interface (see ITU-T M.3320 [59]) as a "trouble ticket" as defined in ITU-T X.790 [66]. This information may include performance reports on how a Customer's leased circuit is performing, and may be part of the SLA within the service contract agreed with the Customer. Note that the Customer may be another NO (wholesaler) providing part of the whole of the leased circuit to a SP (retailer) who in turn supplies the service to an end-user Customer. + +### A.2 Fault information exchange + +When a fault report is received (e.g. a trouble report from a Customer or a connecting NO) the following information should be obtained2: + +- name, title and contact details for the person reporting the fault; +- time of fault report, recorded in UTC; +- designation of the faulty circuit (see ITU-T M.1400 [38]); +- symptoms of the fault; +- the observed duration of the fault prior to a report being made; +- any associated information that may assist with fault clearance. + +It is assumed that the Customer has carried out all the requisite checks using their own application's monitoring and control system, so as to determine that the fault stems from the leased circuit for which the NO(s) are responsible. + +Standardized exchange of information procedures are described in the M.15xx-series Recommendations. ITU-T M.1520 [40] defines the standardized information exchange between NOs/SPs. It summarizes the relevant M-series and E-series Recommendations requiring information exchange between NOs/SPs. ITU-T M.1535 [43] defines the principles for maintenance information to be exchanged at the Customer contact point. ITU-T M.1537 [44] defines the basic maintenance information to be exchanged with a Customer. ITU-T M.1539 [45] contains information to be exchanged at the Customer contact point. ITU-T M.1532 [42] defines a network maintenance service performance agreement that may exist between a NO/SP and the Customer. + +Through enhanced TMN services, the Customer may keep constant track of the problems encountered on the NO/SP's network in respect of their circuits. This reduces the amount of investigations the Customer has to make in the event of problems with their application. The Customer may use a TMN F interface (see ITU-T M.3300 [60]) and workstation to view fault and performance information via an X interface into the NO/SP. ITU-T M.3320 [59] on requirements for the X interface and a new Recommendation on identification of information to be exchanged via the X interface attempt to define how this exchange of information can take place within a TMN environment in a speedy, more efficient manner than traditional methods. + +Note that, in all cases, this information exchange may include Fault, Configuration, Accounting, Performance and Security information – the so-called "FCAPS" TMN managed functional areas. + +The Customer wants a speedy restoration of their circuit. They may also wish to know: + +- where the fault is located; +- the nature of the fault; +- above all, when the circuit will be restored, either by fault rectification or changeover. + +--- + +2 Some NOs/SPs have introduced computerized documentation (e.g. a trouble ticketing system) and exchange of work orders and set up a Leased Circuits "help-desk", which considerably facilitates operations and fault management. + +Prior to undertaking corrective maintenance or loop-test activity, the Customer must be asked to give permission for the circuit to be withdrawn from service. + +### A.3 Fault localization + +Figure 1/M.1375 [35] gives a typical example of a systematic and coordinated procedure for efficient fault localization. Initial localization should aim to identify as quickly as possible whether the fault is due to the transport network supporting the leased circuit or any terminal equipment provided and maintained by the NO/SP or the Customer. Subsequent localization should aim to identify the specific link section or equipment that has failed. Where TMN techniques are used, automatic identification of the exact cause of problems may greatly simplify fault monitoring and localization. Where fault localization is not achieved in a reasonable time, NO/SPs shall invoke the agreed escalation procedure (see ITU-T M.1560 [47]) to assist progress. + +It may be useful to reference Figure 1/M.1375 [35] for guidance with fault localization and use TMN data where applicable. The latter may be available at various locations within the NO/SP. The SDH network supporting the SDH leased circuit will normally have alarm surveillance implemented. Alarm surveillance detects and reports relevant events and conditions that may occur within the SDH network. These may occur within the NEs themselves comprising the network or associated with the NEs, e.g., building and power alarms. Alarms are indications that are automatically generated by a NE as a result of certain events and conditions, e.g., loss of signal. A persistence check is applied before declaring a failure. The OS managing the NEs normally has the ability to define which events and conditions generate autonomous reports and which shall be reported on request. The NEs also normally have historical alarm data registers. All events are time stamped and recorded in these registers. Full details of fault monitoring and management of SDH NEs are given in ITU-T G.707 [3], ITU-T G.783 [5] and ITU-T G.784 [6] including multiplex section protection facilities. Further information on transport network event correlation is given in ITU-T M.2140 [54]. + +Initial fault localization should seek to establish whether a fault exists and to determine if it is located within the national circuit portion or elsewhere. The use of network alarm information (available as described above) and measurements of the characteristics of the physical access link up to the Customer connection point, i.e. up to the point where the NO/SP is responsible, may assist. In addition, the higher-order path trace byte J1, which contains a path Access Point Identifier (API) so that a path-receiving terminal can verify its continued connection to the intended transmitter, may assist in the fault location process. + +Further fault-finding aids are provided by the C2 signal label byte in the higher-order POH, which is coded to indicate the composition or the maintenance status of the VC-n path, and the G1 path status byte, which conveys the path status and performance back to a VC-n trail termination source as detected by a trail termination sink. This feature permits the status and performance of the complete duplex trail (bidirectional path, i.e., circuit) to be monitored at either end, or at any point along that trail. Full details of these functions are given in ITU-T G.707 [3] along with similar capability for lower-order paths carried by an SDH network. A further facility now being fitted to SDH network equipment is TCM. This can assist in determining if errors are entering a NO/SP's domain or being generated within it. + +Where a fault is found to exist outside of the national circuit portion (i.e., within the international portion or distant national portion) it should be referred to a fault reporting point that has responsibility for international maintenance activities. This will typically be the fault reporting point that has responsibility for the international SDH transmission system. When a fault is referred to another fault reporting point, the information given in A.2 should be exchanged. Further localization should seek to identify the faulty element as quickly as possible. Where fault localization (or confirmation of it) is not achieved in a time consistent with the time to remove the fault or restore the circuit as specified in the SLA/Contract, NOs/SPs shall invoke the agreed escalation procedure (see ITU-T M.1560 [47]) to assist progress. + +### **A.4 Circuit restoration** + +SDH leased circuit restoration will normally be achieved initially via protection switching in the SDH transport network. This may be via SDH ring architectures and various levels of path and section switch protection. In cases of catastrophic failure, this may not be achievable and alternate routing of the circuit may have to be performed manually, or the circuit and its supporting network repaired immediately. Temporary restoration will either use dedicated facilities or available spare capacity (see below). This restoration should only be used when it is clear that the normal international network restoration will not be achieved in reasonable time (see Annex D/M.1560 [47]). + +In any event, it has to be decided which option, repair or changeover, is the speedier and stabler way of restoring the leased circuit. NO/SPs should take into account the urgency for restoration for each particular SDH transmission system as mentioned in the preliminary exchange of information for its provision. Where time to restore the circuit is inconsistent with the SLA/Contract, NO/SPs shall invoke the agreed escalation procedure (see ITU-T M.1560 [47]). + +### **A.5 Temporary service restoration** + +Temporary service restoration may be used when a network failure is localized to the international network and this is affecting SDH leased circuits supported by a major international transmission link. Typical international network failures that may require the use of temporary service restoration include the loss of an undersea cable system or satellite system. Temporary service restoration should only be used when it is clear that normal international network restoration will not be achieved in a reasonable time (see Annex D/M.1560 [47]) using SDH protection switching. + +#### **A.5.1 Mechanisms for implementing temporary service restoration** + +Two basic mechanisms have been identified as follows: + +- 1) To use a dedicated temporary restoration facility which will typically be an international SDH transmission system. If both of the following criteria are met, the dedicated temporary restoration facility may be used: + - a) An international network failure has occurred and it is observed that normal restoration will not be achieved in a reasonable time; + - b) A dedicated temporary restoration facility is available. +- 2) To use available temporary restoration capacity, which would typically be found within other international SDH transmission systems that connect to the same destination, although probably following a different physical route within the international network. If each of the following criteria are met, the temporary restoration capacity may be used: + - a) An international network failure has occurred and it is observed that normal restoration will not be achieved in a reasonable time; + - b) Any dedicated temporary restoration facility that may have been provided is not available; + - c) Spare restoration capacity (at the channel or VC-n level) is available; + - d) The NO/SPs involved have the technical capability and operating procedures to support the temporary switching of channels between international transport systems. + +#### **A.5.2 Time to restore service** + +NO/SPs should take into account the urgency for restoration for each particular international SDH transmission system as mentioned in the preliminary exchange of information for its provision (see ITU-T M.1045 [32] and ITU-T M.1400 [38]). Where time to restore service seems to be unacceptable, NO/SPs shall invoke the agreed escalation procedure (see ITU-T M.1560 [47]). + +#### **A.5.3 Restoration procedure** + +The following outline procedure is for guidance only. Detailed operating procedures will need to be agreed between the NO/SPs involved taking account of the network infrastructure that is available. This may include the use of a TMN X interface. + +When an international SDH transmission system failure occurs and the basic restoration criteria have been met (see A.5.1), the NO/SPs involved will confirm that some form of temporary service restoration is to be used and will agree how this is to be achieved. Service can be restored using the following procedure: + +- a) confirm that the international SDH transmission link is faulty; +- b) implement restoration switching; +- c) confirm that the affected leased circuits have been successfully restored. + +#### **A.5.4 Returning to normal routing** + +When service can be restored via its normal route, this should be done as a planned outage (see ITU-T M.1540 [46]). + +#### **A.5.5 Information that should be exchanged** + +Depending upon the proposed restoration method that is to be used, NO/SPs should ensure that suitable preliminary information has been exchanged (e.g., designations and routings for any international SDH transmission systems that may be used for dedicated service restoration). + +### **A.6 Automatic rerouting of international SDH transmission links** + +For priority links such as those bearing SDH leased circuits, NO/SPs may agree to fit the links with automatic rerouting switches, through requisite monitoring systems. These may be 1+1 or n+1 rerouting systems. + +For leased circuits supported on such links, the number of consecutive severely errored seconds (CSES) due to changeover of the SDH transmission system should be minimized in order to fulfil the requirements of the supported services. + +### **A.7 Precautions to be taken in the use of DCSs** + +DCS equipment types vary. Some handle cross-connecting of low speed VC-n signals and have STM-1 digital access ports. Depending on the bit rate of the digital path to be monitored and tested, one or more VCs of the test port are used for the signal. Other types of DCS equipment are used for higher bit rate signals, for example, cross-connecting STM-1/VC-4 digital paths and fitted with STM-4 digital access ports. Many SDH DCSs have considerably more flexibility than PDH DCSs. For further information on SDH cross-connects, see ITU-T G.783 [5]. + +For an international SDH leased circuit, the DCS is typically the routing point, since it fulfils a switching function. The DCS must thus offer a very high degree of availability. If a serious fault should nevertheless occur on a DCS, the NO/SP should have available sufficient alternative arrangements to relieve the faulty unit. At changeover, the databases may have to be loaded and it should be checked whether the software version is compatible if the DCS is a backup for another. + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1320-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1320-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.1320-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.1320-198811-I_PDF-E/aec7150315249ac202a63cc0e32323b8_img.jpg b/marked/M/T-REC-M.1320-198811-I_PDF-E/aec7150315249ac202a63cc0e32323b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..306bd95f76de039f5a8de160dd765e7f38b045d3 --- /dev/null +++ b/marked/M/T-REC-M.1320-198811-I_PDF-E/aec7150315249ac202a63cc0e32323b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7692678b669c7a838dd0f5684dcbd2285c60cb32e5afd5ea0ab5421cc22c1034 +size 42626 diff --git a/marked/M/T-REC-M.1320-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.1320-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bb459c5b58a7569ff7ffac986b87d5256b03fef6 --- /dev/null +++ b/marked/M/T-REC-M.1320-198811-I_PDF-E/raw.md @@ -0,0 +1,91 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1320** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: INTERNATIONAL DATA +TRANSMISSION SYSTEMS** + +--- + +**NUMBERING OF CHANNELS IN DATA +TRANSMISSION SYSTEMS** + +**ITU-T Recommendation M.1320** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.1320 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# NUMBERING OF CHANNELS IN DATA TRANSMISSION SYSTEMS + +Using suitable modems and multiplexers it is possible to provide for a combination of data channels multiplexed together to form an aggregate bit rate for transmission purposes. + +The principle shown in Annex A and Figure 1/M.1320 may be applied to higher bit rates as modems, etc., are developed and deployed. + +The numbering of data channels is obtained by indicating the multiplex channel followed by the sub-channel data rate assigned number in accordance with the scheme contained in Table A-1/M.1320. + +As an example, Figure 1/M.1320 shows a data transmission system, London-Montreal 96H001, employing equipment providing for 2 channels at 2400 bit/s and one channel at 4800 bit/s forming an aggregate bit rate of 9600 bit/s. + +For this system the channel numbering would be: + +London-Montreal 96H001/A2 + +London-Montreal 96H001/B1 + +London-Montreal 96H001/C1 + +![Diagram of channel numbering scheme for data transmission systems. It shows two multiplexers connected by a central line. The left multiplexer has inputs labeled with bit rates and channel numbers: (4800 bit/s) A2, (2400 bit/s) B1, and (2400 bit/s) C1. The right multiplexer has outputs labeled similarly. Above the multiplexers, a bracket labeled 'London-Montreal 96H001' spans the entire system, and another bracket labeled 'London-Montreal D1' spans the central transmission line. The text 'CCITT - 48832' is at the bottom right.](aec7150315249ac202a63cc0e32323b8_img.jpg) + +The diagram illustrates a data transmission system between two points, London and Montreal. On the left, three data channels are shown entering a multiplexer: A2 at 4800 bit/s, B1 at 2400 bit/s, and C1 at 2400 bit/s. The multiplexer is labeled 'Multiplexer' and 'Modem' with a 'V.29' standard indicator. The output of this multiplexer connects to a second multiplexer on the right via a central transmission line. The second multiplexer is also labeled 'Modem' and 'Multiplexer' with a 'V.29' standard indicator. Its outputs are labeled A2 at 4800 bit/s, B1 at 2400 bit/s, and C1 at 2400 bit/s. Above the diagram, a horizontal double-headed arrow labeled 'London-Montreal 96H001' spans the entire width, while another horizontal double-headed arrow labeled 'London-Montreal D1' spans only the central transmission line. The text 'CCITT - 48832' is located at the bottom right of the diagram. + +Diagram of channel numbering scheme for data transmission systems. It shows two multiplexers connected by a central line. The left multiplexer has inputs labeled with bit rates and channel numbers: (4800 bit/s) A2, (2400 bit/s) B1, and (2400 bit/s) C1. The right multiplexer has outputs labeled similarly. Above the multiplexers, a bracket labeled 'London-Montreal 96H001' spans the entire system, and another bracket labeled 'London-Montreal D1' spans the central transmission line. The text 'CCITT - 48832' is at the bottom right. + +FIGURE 1/M.1320 +**Example of the channel numbering scheme for data transmission systems** + +## ANNEX A + +(to Recommendation M.1320) + +Table A-1/M.1320 shows the channel numbering scheme for data transmission systems operated at an aggregate data rate of 9600 bit/s. The table also shows the channel numbering scheme for systems using 9600 bit/s modems operated at reduced data rates of 7200 bit/s or 4800 bit/s. + +TABLE A-1/M.1320 + +**Channel numbering scheme for data transmission systems using 9600 bit/s data modems conforming to Recommendation V.29 [1]** + +| Sub-channel data rate | Assigned number | Aggregate data rate | Multiplex configuration | Sub-channel data rate | Multiplex channel | Channel number | +|-----------------------|-----------------|---------------------|-------------------------|------------------------------|-------------------|----------------------| +| 9600 | 4 | 9600 bit/s | 1 | 9600 | A | A4 | +| 7200 | 3 | | 2 | 7200
2400 | A
B | A3
B1 | +| 4800 | 2 | | 3 | 4800
4800 | A
B | A2
B2 | +| 2400 | 1 | | 4 | 4800
2400
2400 | A
B
C | A2
B1
C1 | +| | | | 5 | 2400
2400
2400
2400 | A
B
C
D | A1
B1
C1
D1 | +| | | 7200 bit/s | 6 | 7200 | A | A3 | +| | | | 7 | 4800
2400 | A
B | A2
B1 | +| | | | 8 | 2400
2400
2400 | A
B
C | A1
B1
C1 | +| | | 4800 bit/s | 9 | 4800 | A | A2 | +| | | | 10 | 2400
2400 | A
B | A1
B1 | + +## **Reference** + +- [1] CCITT Recommendation 9600 bits per second modem standardized for use on point-to-point 4-wire leased telephone-type circuits, Vol. VIII, Rec. V.29. \ No newline at end of file diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e7985e3991c9f4c23120132bb70246eb53304e0 --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3b354db2bf9c2387ad827c0c3aa804361b6a9970cd4fb88484e4e7ed99a44da +size 87302 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b18e5b07ba6a266813c0ce76e92f4e93c0d9fd4b --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a97195c2fd68ad39d82d19b808d1738dce3aa52e94325870a031b5a2ea7c01 +size 8275 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e668ab96729b0b34277bb163cfef7ddfe5b4ea14 --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acaefd5caf9105b12cc8a6e3411e5f5ba491f70b371521135c84a1afa504b400 +size 65311 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f71a80f19e6926bd2799be6f37d559acf0d85c27 --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8fc6fcbb2d20030c0fd28c7af1e898aea7aa28e6ad9509dae96d0ac62da7c76 +size 46503 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d40548af481e751f23279d4942f468da044014e --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1e5436986baad0fec010196b3baa99069af917f5afe69b59e21465ccd6887eb +size 73072 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c065707ce034b4ef4fc49841f934e948b5ff184 --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c6fdd773251fe8ceb0cd800dc55831f553cc5a33c5f2089b5e2568da0b56a5d +size 69020 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/M/T-REC-M.1340-200002-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fea8ecb37525dc4d08e054cf73988d569dd2cf86 --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a63b04b28fb9254ea40ba547189e05b6d951fd5ff50a3a5f0bac511b6d4ff78 +size 59265 diff --git a/marked/M/T-REC-M.1340-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.1340-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..36806648a15618c25c8dd26c6a664915dda385da --- /dev/null +++ b/marked/M/T-REC-M.1340-200002-I_PDF-E/raw.md @@ -0,0 +1,754 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1340** + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**Performance objectives, allocations and limits +for international PDH leased circuits and +supporting data transmission links and systems** + +ITU-T Recommendation M.1340 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **PERFORMANCE OBJECTIVES, ALLOCATIONS AND LIMITS FOR INTERNATIONAL PDH LEASED CIRCUITS AND SUPPORTING DATA TRANSMISSION LINKS AND SYSTEMS** + +## **Summary** + +This Recommendation is only applicable to international data transmission links and systems for PDH applications. The requirements described in this Recommendation should form the basis for all digital test measurements associated with these types of applications. The performance limits are also applicable to the international portions of international leased circuits that are supported by an international data transmission system and that have a PDH digital interface at the Customer's premises. Allocations of performance between international and national portions are covered, but those between Network Operators within the national portion require further study. + +Recommendations M.1370 and M.1375 describe the Bringing-Into-Service and Maintenance procedures respectively for international data transmission links and systems, while Recommendations M.1380 and M.1385 describe similar procedures for international PDH leased circuits supported by those systems. These Recommendations are to be applied in conjunction with the performance objectives, allocations and limits described in this Recommendation. + +This Recommendation addresses the performance of leased circuits with a PDH digital presentation at the Customer's premises. Another Recommendation is being developed for performance of SDH leased circuits. For leased circuits with an analogue presentation, the performance limits of Recommendations M.1020, M.1025 or M.1040 are applied as appropriate. + +## **Source** + +ITU-T Recommendation M.1340 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 4 February 2000. + +## **Keywords** + +In-service monitoring, international data transmission system, international leased circuit, international section, national section, performance objective, performance allocation, performance limits, performance parameters, test duration. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2000 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | | Page | +|-------|-------------------------------------------------------------------------------------------------------------------------------|------| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 3 | +| 4 | Abbreviations..... | 3 | +| 5 | Basic principles ..... | 4 | +| 5.1 | Operational procedures ..... | 4 | +| 5.2 | Performance events and parameters..... | 4 | +| 5.3 | Derivation of performance objectives, allocation and limits ..... | 4 | +| 5.3.1 | Data rates below primary rate ..... | 5 | +| 5.3.2 | Data rates at primary rate and above..... | 5 | +| 5.4 | Test duration and error phenomena ..... | 5 | +| 5.5 | Action on test failure..... | 5 | +| 6 | Error performance allocation principles and test limits ..... | 6 | +| 6.1 | Overall performance allocation (link terminating point-to-link terminating point) ... | 6 | +| 6.2 | Calculation of overall performance limits ..... | 7 | +| 6.3 | Portion performance allocation (between MPs) ..... | 8 | +| 6.4 | Calculation of portion performance limits..... | 8 | +| 7 | Short duration test objectives..... | 8 | +| 7.1 | Maintenance test limits ..... | 9 | +| 7.2 | BIS test limits..... | 9 | +| 8 | In-Service Monitoring (ISM) of performance..... | 9 | +| 9 | Tables under study ..... | 17 | +| | Appendix I – Guidelines for performance allocations of the national circuit portions of an international leased circuit ..... | 18 | +| I.1 | Scope..... | 18 | +| I.2 | Basic principles ..... | 18 | +| I.2.1 | Data rates below primary rate ..... | 18 | +| I.2.2 | Data rate at the primary rate and higher rates ..... | 18 | +| I.3 | Error performance allocation principles ..... | 20 | +| I.3.1 | Performance allocation ..... | 20 | +| I.3.2 | Portion performance allocation..... | 20 | +| I.4 | Short duration test objectives..... | 22 | +| I.5 | In-service performance monitoring..... | 22 | + + + +# **PERFORMANCE OBJECTIVES, ALLOCATIONS AND LIMITS FOR INTERNATIONAL PDH LEASED CIRCUITS AND SUPPORTING DATA TRANSMISSION LINKS AND SYSTEMS** + +*(Published 1993, revised in 1996 and 2000)* + +## **1 Scope** + +This Recommendation is only applicable to international data transmission links and systems for PDH applications. The requirements described in this Recommendation should form the basis for all digital test measurements associated with these types of applications. The performance limits are also applicable to the international portions of international leased circuits that are supported by an international data transmission system and that have a PDH digital interface at the Customer's premises. Allocations of performance between international and national portions are covered, but those between Network Operators/Service Providers within the national portion require further study. + +This Recommendation addresses the performance of leased circuits with a PDH digital presentation at the Customer's premises. Another Recommendation is being developed for performance of SDH leased circuits. For leased circuits with an analogue presentation, the procedures described in Recommendation M.1060 [11] and performance limits of Recommendations M.1020 [7], M.1025 [8] or M.1040 [9] are applied as appropriate. + +The limits described in this Recommendation represent a typical minimum level of performance and Network Operators/Service Providers should apply practical experience and negotiation to mutually agree more stringent limits whenever feasible. However, it should be recognized that the performance limits described may not be achieved by certain existing transmission equipment technologies. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.701 (1993), *Vocabulary of digital transmission and multiplexing, and pulse code modulation (PCM) terms.* +- [2] ITU-T Recommendation G.821 (1996), *Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an integrated services digital network.* +- [3] ITU-T Recommendation G.826 (1999) *Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate.* +- [4] CCITT Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks.* +- [5] CCITT Recommendation M.34 (1988), *Performance monitoring on international transmission systems and equipment.* + +- [6] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [7] ITU-T Recommendation M.1020 (1993), *Characteristics of special quality international leased circuits with special bandwidth conditioning.* +- [8] ITU-T Recommendation M.1025 (1993), *Characteristics of special quality international leased circuits with basic bandwidth conditioning.* +- [9] CCITT Recommendation M.1040 (1988), *Characteristics of ordinary quality international leased circuits.* +- [10] ITU-T Recommendation M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [11] CCITT Recommendation M.1060 (1988), *Maintenance of international leased circuits.* +- [12] ITU-T Recommendation M.1300 (1997), *Maintenance of international data transmission systems operating in the range 2.4 kbit/s to 140 Mbit/s.* +- [13] ITU-T Recommendation M.1370 (1998), *Bringing-into-service of international data transmission systems.* +- [14] ITU-T Recommendation M.1375 (1998), *Maintenance of international data transmission systems.* +- [15] ITU-T Recommendation M.1380 (2000), *Bringing-into-service of international leased circuits that are supported by international data transmission systems.* +- [16] ITU-T Recommendation M.1385 (2000), *Maintenance of international leased circuits that are supported by international data transmission systems.* +- [17] ITU-T Recommendation M.1400 (2000), *Designations for inter operator networks.* +- [18] CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network.* +- [19] ITU-T Recommendation M.1530 (1999), *Network maintenance information.* +- [20] ITU-T Recommendation M.1535 (1996), *Principles for maintenance information to be exchanged at the customer contact point (MICC).* +- [21] ITU-T Recommendation M.1537 (1997), *Definition of maintenance information to be exchanged at customer contact point (MICC).* +- [22] ITU-T Recommendation M.1539 (1999), *Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC).* +- [23] ITU-T Recommendation M.1540 (1994), *Exchange of information for planned outages of transmission systems.* +- [24] CCITT Recommendation M.1560 (1992), *Escalation procedure for international leased circuits.* +- [25] ITU-T Recommendation M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH paths, sections and transmission systems.* + +## 3 Terms and definitions + +Recommendation M.1300 [12] provides general descriptions of international data transmission systems. Terminology and definitions relating to this Recommendation are provided in Recommendations G.701 [1] and M.60 [6]. For the purposes of this Recommendation, the following definitions of an international digital leased circuit and Service Level Agreement (SLA)/Contract apply: + +**3.1 international digital leased circuit:** The digital path between two Network Terminating Equipments (NTEs). The digital leased circuit may be bidirectional or unidirectional and its end points are at the boundaries between the Network Operator/Service Provider and the Customer. The NTEs may be owned by the Network Operator/Service Provider or owned by the Customer. + +**3.2 SLA/Contract:** A set of appropriate procedures and targets formally or informally agreed between Network Operators/Service Providers or between Network Operators/Service Providers and Customers, in order to achieve and maintain specified Quality of Service (QoS) in accordance with ITU (ITU-T and ITU-R) Recommendations. The SLA may be an integral part of the Contract. These procedures and targets are related to specific circuit/service availability, error performance, Ready For Service (RFS) date, Mean Time Between Failures (MTBF), Mean Time to Restore Service (MTRS), Mean Time To Repair (MTTR). + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|-------------------------------------| +| BIS | Bringing-Into-Service | +| CSES | Consecutive Severely Errored Second | +| ES | Errored Second | +| FS | Frontier Station | +| HRX | Hypothetical Reference Connection | +| ISM | In-Service Monitoring | +| LTP | Link Terminating Point | +| MP | Measurement Point | +| MTBF | Mean Time Between Failures | +| MTRS | Mean Time to Restore Service | +| MTTR | Mean Time To Repair | +| NTE | Network Terminating Equipment | +| OOS | Out-Of-Service | +| PCM | Pulse Code Modulation | +| PDH | Plesiochronous Digital Hierarchy | +| QoS | Quality of Service | +| RFS | Ready For Service | +| RPO | Reference Performance Objective | +| SDH | Synchronous Digital Hierarchy | +| SEP | Severely Errored Period | +| SES | Severely Errored Second | + +| | | +|-----|---------------------------------------| +| SLA | Service Level Agreement | +| TIC | Terminal International Centre | +| TMN | Telecommunications Management Network | +| TNC | Terminal National Centre | +| UTC | Coordinated Universal Time | + +## 5 Basic principles + +## 5.1 Operational procedures + +Recommendation M.1370 [13] covers the setting up and Bringing-Into-Service (BIS) of international data transmission systems, while Maintenance procedures are covered by Recommendation M.1375 [14]. The BIS and Maintenance procedures relating to international leased circuits with a PDH digital presentation at the Customer's premises and that are supported by international data transmission systems are covered by Recommendations M.1380 [15] and M.1385 [16] respectively. International data transmission systems and leased circuits shall use M.1400 [17] designations. + +## 5.2 Performance events and parameters + +Error performance limits provided in this Recommendation are based on error performance events of Errored Seconds (ESs) and Severely Errored Seconds (SESs) and the corresponding parameters as defined in Recommendations G.821 [2], G.826 [3] and M.2100 [25]. Performance limits for timing and delay performance parameters are for further study. With developments in network technology, delay may be a problem for some user applications. + +Network Operators/Service Providers should be aware that periods of Consecutive Severely Errored Seconds (CSES) of between 3 and 9 seconds, known as a Severely Errored Period (SEP), can have a severe impact on some Customers' leased circuit applications. CSESs are critical for some Customers' leased circuit applications because they require the application to be completely restarted, since the installation's own recovery system is no longer sufficient to cover the circuit interruption time. + +Performance limits and objectives for SEPs are for further study. It should be recognized, however, that current PDH and some SDH transmission equipment designed to Recommendations G.821 [2] and G.826 [3] does not monitor and record these "short break" events. + +## 5.3 Derivation of performance objectives, allocation and limits + +The performance limit allocation principles described in this Recommendation are compatible with those presented in Recommendation M.2100 [25]. Table 2b/M.2100 [25] is used as the basis for deriving overall error performance allocations for this Recommendation. + +For greatly simplified operational performance measurements, this Recommendation uses the same ES and SES limits to cover all 24-hour Out-Of-Service (OOS) test requirements (e.g. BIS, maintenance intervention and returning to service after repair). These limits are given in Table 1. In addition, dual limits associated with a confidence window, as described in Recommendations M.34 [5] and M.2100 [25] are not used. While this overall approach is not directly compatible with Recommendation M.2100 [25], an international digital path set up in accordance with the performance requirements of Recommendation M.2100 [25] should be able to support an international data transmission link set up in accordance with the performance requirements of this Recommendation. + +#### 5.3.1 Data rates below primary rate + +The same performance limits will be applicable for all data rates below the primary rate (for the purpose of this Recommendation, this will include data rates from 600 bit/s). + +The ES performance limits used in this Recommendation have a mathematical basis and are derived from a 40% allowance of an end-to-end ES objective as described in Recommendation G.821 [2]. However, taking account of practical experience, the 8% ES objective proposed in Recommendation G.821 [2] is reduced to 4% (see Table 1a/M.2100 [25]). + +The SES performance limits used in this Recommendation are not directly related to the SES objectives described in Recommendation G.821 [2]. The limits have a mathematical basis, but have been modified significantly to reflect practical experience. + +### 5.3.2 Data rates at primary rate and above + +The end-to-end error performance objectives at or above the primary rate are based on those given in Table 1b/M.2100 [25]. The Reference Performance Objectives (RPOs) for ES used in this Recommendation are based on a maximum of 63% of a 2% (for primary rate), 2.5% (for secondary rate), 3.75% (for tertiary rate) and 8% (for quaternary rate) end-to-end RPO as derived from Recommendation G.826 [3], where 63% is the overall international portion error performance allocation. + +Recommendation G.826 [3] allocates a block allowance of 17.5% of the overall performance objectives to one national portion of a path. In addition, a length-dependent allowance of 1% per 500 km is allocated to this portion. Considering that a path comprises two national portions and assuming a maximum length of $2 \times 500$ km, the total allocation assigned to the national portion is: + +$$2 \times 17.5\% + 2 \times 1\% = 37\%$$ + +Because this part of the Recommendation only deals with the **international portion**, only + +$$100\% - 37\% = 63\%$$ + +can be assigned to this **international portion**. + +The SES performance limits used in this Recommendation are identical to those for data rates below primary rate. + +## 5.4 Test duration and error phenomena + +To reflect operational requirements for OOS testing, test durations of 24 hours, 2 hours, 1 hour, and 15 minutes are used in this Recommendation. While the one-month test duration suggested in Recommendations G.821 [2] and G.826 [3] is not realistic for most practical test requirements, it must be recognized that 24-hour (or less) test results are inherently less reliable, since the statistics of transmission media can have little significance over such short periods. The 2-hour, 1-hour, and 15-minute test objectives specified in this Recommendation are used to provide a basic check of operability and are not intended to give a reliable indication of transmission error performance. + +The performance limits used during BIS and Maintenance tests should be consistent. For short duration tests, the limits given in clause 6 and its associated tables are appropriate. For all performance tests described in this Recommendation, the ES and SES limits should be met simultaneously for the test result to be considered acceptable. + +## 5.5 Action on test failure + +A 24-hour test duration cannot be expected to give a particularly reliable indication of transmission error performance (a test duration of one month is suggested in Recommendations G.821 [2] and G.826 [3]), since the statistics of transmission media can have little significance over such short periods. When a performance limit is not met, Network Operators/Service Providers should use + +practical judgement to determine an agreed course of action. Except where performance is catastrophically bad and a fault is obviously present, it will often be advantageous to continue testing to increase the level of confidence in the result. However, to avoid unnecessary testing where a limit is exceeded by only a very small margin, following agreement between Network Operators/Service Providers involved, it may be appropriate to consider the result acceptable. See Recommendations M.1370 [13], M.1375 [14], M.1380 [15] and M.1385 [16] for further guidance. + +In addition, reference should be made to any particular maintenance agreement with the Customer, including for example, a Service Level Agreement (SLA)/Contract. This should have been included in the preliminary exchange of information for the provision of international leased circuits and international data transmission systems, defined in Recommendation M.1045 [10]. See also Recommendations M.1510 [18], M.1530 [19], M.1535 [20], M.1537 [21], M.1539 [22] and M.1540 [23] for further information. Maintenance staff should refer to such agreements when dealing with a fault reported by the Customer, and should follow the escalation procedures defined in Recommendation M.1560 [24] where necessary. + +## **6 Error performance allocation principles and test limits** + +## **6.1 Overall performance allocation (link terminating point-to-link terminating point)** + +Prior to attempting to determine an overall performance allocation, Network Operators/Service Providers should construct an agreed schematic routing diagram for the international data transmission link or system or international leased circuit under consideration. The diagram should locate Link Terminating Points (LTPs), earth stations, terrestrial Frontier Stations (FSs) and Terminal International Centres (TICs), showing distances in kilometres (except for any satellite sections). Figure 1 is a typical schematic diagram (see also Figures 2a/M.2100 [25] and 3/M.2100 [25]). A suitable routing diagram may have been agreed at the initial planning stage prior to BIS. This routing diagram is used to calculate the error performance block allowances for the overall transmission link or circuit and its constituent portions. The inclusion of intermediate Measurement Points (MPs) as shown in Figure 1 is not necessary for the derivation of overall performance limits. + +![Diagram of performance allocation for international data transmission links and systems. It shows a path from a Terminating country (LTP/TIC) through four Transit countries (each with MP and FS) to another Terminating country (LTP). Performance allocations are labeled w, x, y, a, b, c, d, e, f, and N. A legend indicates w+y for Terrestrial and x for Submarine. The diagram is labeled 'Overall performance allocation (LTP to LTP)' and 'Section performance allocations (between MPs)'.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Overall performance allocation (LTP to LTP) + +Terminating country      Transit country      Transit country      Transit country      Terminating country + +MP      MP      MP      MP      MP + +LTP      FS      FS      FS      FS      FS      FS      FS      LTP + +TIC      TIC + +w      x      y      a      b      c      d      e      f      N + +w + y: Terrestrial +x: Submarine      Terrestrial + +T0413710-99 + +Section performance allocations (between MPs) + +Diagram of performance allocation for international data transmission links and systems. It shows a path from a Terminating country (LTP/TIC) through four Transit countries (each with MP and FS) to another Terminating country (LTP). Performance allocations are labeled w, x, y, a, b, c, d, e, f, and N. A legend indicates w+y for Terrestrial and x for Submarine. The diagram is labeled 'Overall performance allocation (LTP to LTP)' and 'Section performance allocations (between MPs)'. + +FS      Frontier Station +LTP      Link Terminating Point +MP      Measurement Point +TIC      Terminal International Centre + +NOTE 1 – An overall performance allocation is derived using Table 2/M.2100 [25] and Table 1 and taking account of allocations for national portions, e.g. N. + +NOTE 2 – Individual international portion performance allocations are derived using Tables 1 and 2. + +NOTE 3 – Where an LTP is located at a TIC, there will be no national portion. + +**Figure 1/M.1340 – Performance allocation for international data transmission links and systems** + +Within international portions, percentage performance allocations attributable to terminating countries, transit countries, submarine cable systems, satellite systems and terrestrial border crossings are determined by reference to Tables 2a/M.2100 [25] and 2b/M.2100 [25] as appropriate. The percentage allocations are described as "% of end-to-end RPO" (Reference Performance Objectives) in these tables. + +Percentage performance allocations attributable to national portion components are the responsibility of the Network Operators/Service Providers concerned and are for further study. Where a national portion is provided over a high grade transmission path, an allocation consistent with the terrestrial components given in Table 2 is recommended. Appendix I gives guidelines for performance limits for the national portion of an international leased circuit routed via medium and/or local grade transmission paths. + +## 6.2 Calculation of overall performance limits + +The calculation of overall performance limits from a single overall percentage allocation is preferred. An overall allocation is derived by simple addition of the individual portion allocations. The overall percentage allocation should then be applied to the appropriate data rate in Table 1 to determine single 24-hour test limits for ES and SES. Where an overall percentage performance allocation of greater than 40% for data rates below primary rate and 63% for data rates at the primary rate and above is derived, Network Operators/Service Providers should determine suitable limits for ES and SES by bilateral agreement, taking account of the limits in Table 1. The linear addition of portion performance limits to derive overall performance limits is not recommended. The 24-hour performance limits derived are applicable to all OOS tests (e.g. BIS, maintenance + +intervention and returning to service after repair) of the overall international data transmission link (LTP-to-LTP) or system or international leased circuit. + +## **6.3 Portion performance allocation (between MPs)** + +For certain operational test requirements (e.g. during maintenance investigation and re-routing), it will be necessary to perform 24-hour tests of portion components of an international data transmission link or international leased circuit. Prior to attempting to determine performance allocations, Network Operators/Service Providers should construct an agreed schematic routing diagram for the international data transmission link or system or international leased circuit as described in 6.1 above. A suitable routing diagram may have been agreed at the planning stage prior to BIS. The air-route distance between link portion end points, as described in Recommendation M.2100 [25] as Path Core Elements (PCEs) should be multiplied by an appropriate routing factor. This routing factor is specified as follows: + +- If the air route distance is $< 1000$ km, the routing factor is 1.5. +- If the air route distance is $\geq 1000$ km and $< 1200$ km, the calculated route length is taken to be 1500 km. +- If the air route distance is $\geq 1200$ km, the routing factor is 1.25. + +The modified air route distance is compared with the actual route length, where this is known, and the smaller of these distances is then applied to Table 2 for the calculation of percentage performance allocation between points of interest. + +## **6.4 Calculation of portion performance limits** + +The portion components from the schematic routing diagram should be applied to Table 2 (this is a simplified version of Table 2b/M.2100 [25]) for the calculation of percentage performance allocations between points of interest. Network Operators/Service Providers must ensure that the sum total of performance allocations for individual portion components is consistent with the overall performance allocation described in 6.1 above. Where the overall performance allocation is exceeded, Network Operators/Service Providers should agree proportional reductions to portion performance allocations by negotiation. Agreed portion performance allocations should then be applied to the appropriate data rate in Table 1 to determine the single 24-hour test limits for ES and SES. These test limits may be used for all OOS test requirements between agreed MPs. + +## **7 Short duration test objectives** + +The application of short duration test limits to BIS and maintenance operations on international data transmission links and systems is described in Recommendations M.1370 [13] and M.1375 [14] respectively, and similarly for international leased circuits in Recommendations M.1380 [15] and M.1385 [16]. + +It must be recognized that short duration tests do not give a reliable indication of overall transmission error performance for the reasons stated earlier. Failure to meet a short duration test objective by a small margin (see Note 3 to Table 4) may not necessarily be indicative of a performance problem and Network Operators/Service Providers should use their practical judgement to determine an agreed course of action, taking account of operational requirements. Where a short duration test objective is not met by a significant margin, corrective action should be taken in accordance with Recommendations M.1370 [13], M.1375 [14], M.1380 [15] or M.1385 [16] as appropriate. + +## **7.1 Maintenance test limits** + +It is recognized that 24-hour test limits are not appropriate for all OOS test requirements, especially those associated with maintenance operations. Proposed 15-minute and 1-hour test limits for international data transmission links and systems are given in Table 4. These error performance limits are independent of the routing configuration that is used. If there is any doubt about the validity of a 15-minute or 1-hour test result, a longer duration test may be appropriate. + +## **7.2 BIS test limits** + +International leased circuits are often carried on higher speed data transmission systems and links, and are provisioned at a later date than the supporting transport network. Table 2 gives 2-hour error performance test limits that can be used for BIS tests, when the circuit is provided over a data transmission system that has already been tested over a 24-hour period and is in service. + +## **8 In-Service Monitoring (ISM) of performance** + +On some international data transmission systems, it may be possible to assess overall performance by using built-in In-Service Monitoring (ISM) facilities e.g. CRC within the frame alignment signal or by monitoring a dedicated service channel. Performance limits are defined for ES and SES resulting from ISM errors and each performance limit will have its own threshold. The general strategy for the use of performance monitoring information and thresholds is described in Recommendations M.20 [4] and M.34 [5]. Specific information is also given in Recommendation M.1375 [14] for international data transmission systems and Recommendation M.1385 [16] for international leased circuits. + +Unacceptable Performance Limit (UPL) threshold values for a 15-minute period and Degraded Performance Limit (DPL) threshold values for a 24-hour period are for further study. When UPL or DPL thresholds are exceeded, maintenance action should be initiated including escalation procedures if necessary (see Recommendation M.1560 [24]). Threshold violations may automatically generate alerts to a TMN management system if implemented. + +**Table 1/M.1340 – 24-hour Out-Of-Service test limits** + +| Allocation % | Event | 0.5 | 1.0 | 1.5 | 2.0 | 2.5 | 3.0 | 3.5 | 4.0 | 4.5 | 5.0 | 5.5 | 6.0 | 6.5 | 7.0 | 7.5 | 8.0 | 8.5 | 9.0 | 9.5 | 10.0 | 10.5 | 11.0 | 11.5 | 12.0 | 12.5 | 13.0 | +|-----------------|-------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|------|------|------|------|------|------|------| +| < Primary rate | ES | | 9 | 16 | 23 | 30 | 37 | 45 | 52 | 60 | 68 | 76 | 83 | 91 | 99 | 107 | 115 | 123 | 131 | 139 | 147 | 155 | 163 | 171 | 179 | 187 | 195 | +| | SES | | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 5 | 5 | 5 | 6 | 6 | 6 | 7 | 7 | 7 | 8 | +| Primary rate | ES | | 3 | 6 | 9 | 12 | 16 | 19 | 23 | 26 | 30 | 34 | 37 | 41 | 45 | 49 | 52 | 56 | 60 | 64 | 68 | 72 | 76 | 79 | 83 | 87 | 91 | +| | SES | | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 5 | 5 | 5 | 6 | 6 | 6 | 7 | 7 | 7 | 8 | +| Secondary rate | ES | | 4 | 8 | 12 | 17 | 21 | 26 | 30 | 35 | 39 | 44 | 49 | 53 | 58 | 63 | 68 | 73 | 77 | 82 | 87 | 92 | 97 | 102 | 107 | 112 | 117 | +| | SES | | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 5 | 5 | 5 | 6 | 6 | 6 | 7 | 7 | 7 | 8 | +| Tertiary rate | ES | | 8 | 14 | 21 | 28 | 35 | 42 | 49 | 56 | 63 | 70 | 77 | 85 | 92 | 99 | 107 | 114 | 122 | 129 | 137 | 144 | 152 | 159 | 167 | 174 | 182 | +| | SES | | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 5 | 5 | 5 | 6 | 6 | 6 | 7 | 7 | 7 | 8 | +| Quaternary rate | ES | | 23 | 37 | 52 | 68 | 83 | 99 | 115 | 131 | 147 | 163 | 179 | 195 | 211 | 227 | 243 | 259 | 276 | 292 | 308 | 325 | 341 | 358 | 374 | 390 | 407 | +| | SES | | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 5 | 5 | 5 | 6 | 6 | 6 | 7 | 7 | 7 | 8 | + +| Allocation % | Event | 13.5 | 14.0 | 14.5 | 15.0 | 15.5 | 16.0 | 16.5 | 17.0 | 17.5 | 18.0 | 18.5 | 19.0 | 19.5 | 20.0 | 20.5 | 21.0 | 21.5 | 22.0 | 22.5 | 23.0 | 23.5 | 24.0 | 24.5 | 25.0 | 25.5 | 26.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary Rate | ES | 203 | 211 | 219 | 227 | 235 | 243 | 251 | 259 | 268 | 276 | 284 | 292 | 300 | 308 | 317 | 325 | 333 | 341 | 349 | 358 | 366 | 374 | 382 | 390 | 399 | 407 | +| | SES | 8 | 8 | 8 | 9 | 9 | 9 | 10 | 10 | 10 | 10 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 13 | 14 | 14 | 14 | 15 | 15 | 15 | +| Primary Rate | ES | 95 | 99 | 103 | 107 | 111 | 115 | 119 | 123 | 127 | 131 | 135 | 139 | 143 | 147 | 151 | 155 | 159 | 163 | 167 | 171 | 175 | 179 | 183 | 187 | 191 | 195 | +| | SES | 8 | 8 | 8 | 9 | 9 | 9 | 10 | 10 | 10 | 10 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 13 | 14 | 14 | 14 | 15 | 15 | 15 | +| Secondary Rate | ES | 122 | 127 | 132 | 137 | 142 | 147 | 152 | 157 | 162 | 167 | 172 | 177 | 182 | 187 | 192 | 197 | 202 | 207 | 212 | 217 | 222 | 227 | 232 | 237 | 242 | 247 | +| | SES | 8 | 8 | 8 | 9 | 9 | 9 | 10 | 10 | 10 | 10 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 13 | 14 | 14 | 14 | 15 | 15 | 15 | +| Tertiary Rate | ES | 189 | 197 | 204 | 212 | 219 | 227 | 235 | 242 | 250 | 257 | 265 | 273 | 280 | 288 | 296 | 303 | 311 | 319 | 326 | 334 | 342 | 349 | 357 | 365 | 372 | 380 | +| | SES | 8 | 8 | 8 | 9 | 9 | 9 | 10 | 10 | 10 | 10 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 13 | 14 | 14 | 14 | 15 | 15 | 15 | +| Quaternary rate | ES | 423 | 440 | 456 | 473 | 489 | 506 | 522 | 539 | 556 | 572 | 589 | 605 | 622 | 639 | 655 | 672 | 689 | 705 | 722 | 738 | 755 | 772 | 789 | 805 | 822 | 839 | +| | SES | 8 | 8 | 8 | 9 | 9 | 9 | 10 | 10 | 10 | 10 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 13 | 14 | 14 | 14 | 15 | 15 | 15 | + +**Table 1/M.1340 – 24-hour Out-Of-Service test limits (continued)** + +| Allocation % | Event | 26.5 | 27.0 | 27.0 | 28.0 | 28.5 | 29.0 | 29.5 | 30.0 | 30.5 | 31.0 | 31.5 | 32.0 | 32.5 | 33.0 | 33.5 | 34.0 | 34.5 | 35.0 | 35.5 | 36.0 | 36.5 | 37.0 | 37.5 | 38.0 | 38.5 | 39.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary Rate | ES | 415 | 423 | 432 | 440 | 448 | 456 | 465 | 473 | 481 | 489 | 498 | 506 | 514 | 522 | 531 | 539 | 547 | 556 | 564 | 572 | 580 | 589 | 597 | 605 | 614 | 622 | +| | SES | 16 | 16 | 16 | 16 | 17 | 17 | 17 | 18 | 18 | 18 | 18 | 19 | 19 | 19 | 20 | 20 | 20 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 23 | 23 | +| Primary Rate | ES | 199 | 203 | 207 | 211 | 215 | 219 | 223 | 227 | 231 | 235 | 239 | 243 | 247 | 251 | 255 | 259 | 264 | 268 | 272 | 276 | 280 | 284 | 288 | 292 | 296 | 300 | +| | SES | 16 | 16 | 16 | 16 | 17 | 17 | 17 | 18 | 18 | 18 | 18 | 19 | 19 | 19 | 20 | 20 | 20 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 23 | 23 | +| Secondary Rate | ES | 252 | 257 | 263 | 268 | 273 | 278 | 283 | 288 | 293 | 298 | 303 | 308 | 314 | 319 | 324 | 329 | 334 | 339 | 344 | 349 | 354 | 360 | 365 | 370 | 375 | 380 | +| | SES | 16 | 16 | 16 | 16 | 17 | 17 | 17 | 18 | 18 | 18 | 18 | 19 | 19 | 19 | 20 | 20 | 20 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 23 | 23 | +| Tertiary Rate | ES | 388 | 396 | 403 | 411 | 419 | 426 | 434 | 442 | 450 | 457 | 465 | 473 | 481 | 488 | 496 | 504 | 512 | 519 | 527 | 535 | 543 | 550 | 558 | 566 | 574 | 582 | +| | SES | 16 | 16 | 16 | 16 | 17 | 17 | 17 | 18 | 18 | 18 | 18 | 19 | 19 | 19 | 20 | 20 | 20 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 23 | 23 | +| Quaternary Rate | ES | 855 | 872 | 889 | 905 | 922 | 939 | 956 | 972 | 989 | 1006 | 1023 | 1039 | 1056 | 1073 | 1090 | 1106 | 1123 | 1140 | 1157 | 1174 | 1190 | 1207 | 1224 | 1241 | 1258 | 1274 | +| | SES | 16 | 16 | 16 | 16 | 17 | 17 | 17 | 18 | 18 | 18 | 18 | 19 | 19 | 19 | 20 | 20 | 20 | 21 | 21 | 21 | 21 | 22 | 22 | 22 | 23 | 23 | + +| Allocation % | Event | 39.5 | 40.0 | 40.5 | 41.0 | 41.5 | 42.0 | 42.5 | 43.0 | 43.5 | 44.0 | 44.5 | 45.0 | 45.5 | 46.0 | 46.5 | 47.0 | 47.5 | 48.0 | 48.5 | 49.0 | 49.5 | 50.0 | 50.5 | 51.0 | 51.5 | 52.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary Rate | ES | 630 | 639 | | | | | | | | | | | | | | | | | | | | | | | | | +| | SES | 23 | 24 | | | | | | | | | | | | | | | | | | | | | | | | | +| Primary Rate | ES | 304 | 308 | 313 | 317 | 321 | 325 | 329 | 333 | 337 | 341 | 345 | 349 | 353 | 358 | 362 | 366 | 370 | 374 | 378 | 382 | 386 | 390 | 395 | 399 | 403 | 407 | +| | SES | 23 | 24 | 24 | 24 | 24 | 25 | 25 | 25 | 26 | 26 | 26 | 26 | 27 | 27 | 27 | 28 | 28 | 28 | 29 | 29 | 29 | 29 | 30 | 30 | 30 | 31 | +| Secondary Rate | ES | 385 | 390 | 396 | 401 | 406 | 411 | 416 | 421 | 426 | 432 | 437 | 442 | 447 | 452 | 457 | 463 | 468 | 473 | 478 | 483 | 488 | 494 | 499 | 504 | 509 | 514 | +| | SES | 23 | 24 | 24 | 24 | 24 | 25 | 25 | 25 | 26 | 26 | 26 | 26 | 27 | 27 | 27 | 28 | 28 | 28 | 29 | 29 | 29 | 29 | 30 | 30 | 30 | 31 | +| Tertiary Rate | ES | 589 | 597 | 605 | 613 | 620 | 628 | 636 | 644 | 652 | 659 | 667 | 675 | 683 | 691 | 698 | 706 | 714 | 722 | 730 | 737 | 745 | 753 | 761 | 769 | 777 | 784 | +| | SES | 23 | 24 | 24 | 24 | 24 | 25 | 25 | 25 | 26 | 26 | 26 | 26 | 27 | 27 | 27 | 28 | 28 | 28 | 29 | 29 | 29 | 29 | 30 | 30 | 30 | 31 | +| Quaternary Rate | ES | 1291 | 1308 | 1325 | 1342 | 1358 | 1375 | 1392 | 1409 | 1426 | 1443 | 1459 | 1476 | 1493 | 1510 | 1527 | 1544 | 1561 | 1577 | 1594 | 1611 | 1628 | 1645 | 1662 | 1679 | 1695 | 1712 | +| | SES | 23 | 24 | 24 | 24 | 24 | 25 | 25 | 25 | 26 | 26 | 26 | 26 | 27 | 27 | 27 | 28 | 28 | 28 | 29 | 29 | 29 | 29 | 30 | 30 | 30 | 31 | + +**Table 1/M.1340 – 24-hour Out-Of-Service test limits (concluded)** + +| Allocation % | Event | 52.5 | 53.0 | 53.5 | 54.0 | 54.5 | 55.0 | 55.5 | 56.0 | 56.5 | 57.0 | 57.5 | 58.0 | 58.5 | 59.0 | 59.5 | 60.0 | 60.5 | 61.0 | 61.5 | 62.0 | 62.5 | 63.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary Rate | ES | | | | | | | | | | | | | | | | | | | | | | | +| | SES | | | | | | | | | | | | | | | | | | | | | | | +| Primary Rate | ES | 411 | 415 | 419 | 423 | 427 | 432 | 436 | 440 | 444 | 448 | 452 | 456 | 460 | 465 | 469 | 473 | 477 | 481 | 485 | 489 | 494 | 498 | +| | SES | 31 | 31 | 32 | 32 | 32 | 32 | 33 | 33 | 33 | 34 | 34 | 34 | 34 | 35 | 35 | 35 | 36 | 36 | 36 | 37 | 37 | 37 | +| Secondary Rate | ES | 519 | 525 | 530 | 535 | 540 | 545 | 550 | 556 | 561 | 566 | 571 | 576 | 582 | 587 | 592 | 597 | 602 | 607 | 613 | 618 | 623 | 628 | +| | SES | 31 | 31 | 32 | 32 | 32 | 32 | 33 | 33 | 33 | 34 | 34 | 34 | 34 | 35 | 35 | 35 | 36 | 36 | 36 | 37 | 37 | 37 | +| Tertiary Rate | ES | 792 | 800 | 808 | 816 | 823 | 831 | 839 | 847 | 855 | 863 | 870 | 878 | 886 | 894 | 902 | 910 | 917 | 925 | 933 | 941 | 949 | 957 | +| | SES | 31 | 31 | 32 | 32 | 32 | 32 | 33 | 33 | 33 | 34 | 34 | 34 | 34 | 35 | 35 | 35 | 36 | 36 | 36 | 37 | 37 | 37 | +| Quaternary Rate | ES | 1729 | 1746 | 1763 | 1780 | 1797 | 1814 | 1830 | 1847 | 1864 | 1881 | 1898 | 1915 | 1932 | 1949 | 1966 | 1983 | 1999 | 2016 | 2033 | 2050 | 2067 | 2084 | +| | SES | 31 | 31 | 32 | 32 | 32 | 32 | 33 | 33 | 33 | 34 | 34 | 34 | 34 | 35 | 35 | 35 | 36 | 36 | 36 | 37 | 37 | 37 | + +ES Errored Seconds + +SES Severely Errored Seconds + +NOTE 1 – The % allocation relates to the proportion of the overall reference performance objective that is attributable to a particular routing configuration. + +NOTE 2 – The limits are applicable to discrete measurement periods of 24 hours. + +NOTE 3 – Where a test has a discrete period of more than 24 hours, it is recommended that the limits be applied to each discrete period without averaging. + +NOTE 4 – The maximum % allocation of 40% in this table is consistent with the allowance for the high-grade quality classification given in Recommendation G.821 [2]. + +NOTE 5 – The ES and SES performance limits relate to the maximum number of errored seconds or severely errored seconds that would be acceptable in the measurement period. + +NOTE 6 – Performance limits for unavailable time are left for negotiation between Network Operators/Service Providers. However, it should be appreciated that an availability of 100% would normally be achieved during a typical 24-hour period and that a transition to unavailable state would be inconsistent with SES limits for allocations below 16.5%. + +**Table 2/M.1340 – 2-hour BIS limits for circuits carried on a data transmission system +which has already been tested over 24 hours and is in service** + +| Allocation % | Event | 0.5 | 1.0 | 1.5 | 2.0 | 2.5 | 3.0 | 3.5 | 4.0 | 4.5 | 5.0 | 5.5 | 6.0 | 6.5 | 7.0 | 7.5 | 8.0 | 8.5 | 9.0 | 9.5 | 10.0 | 10.5 | 11.0 | 11.5 | 12.0 | 12.5 | 13.0 | +|----------------|-------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|------|------|------|------|------|------|------| +| < Primary rate | ES | | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 2 | 2 | 3 | 3 | 4 | 4 | 5 | 5 | 6 | 6 | 7 | 7 | 8 | 8 | 9 | 10 | 10 | +| | SES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| < Primary rate | ES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 3 | +| | SES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Secondary rate | ES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 4 | 5 | 5 | +| | SES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Tertiary rate | ES | | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 2 | 2 | 2 | 3 | 3 | 4 | 4 | 5 | 5 | 6 | 6 | 7 | 7 | 8 | 8 | 9 | 9 | +| | SES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Quaternary rat | ES | | 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 15 | 16 | 17 | 18 | 19 | 20 | 22 | 23 | 24 | 25 | +| | SES | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +| Allocation % | Event | 13.5 | 14.0 | 14.5 | 15.0 | 15.5 | 16.0 | 16.5 | 17.0 | 17.5 | 18.0 | 18.5 | 19.0 | 19.5 | 20.0 | 20.5 | 21.0 | 21.5 | 22.0 | 22.5 | 23.0 | 23.5 | 24.0 | 24.5 | 25.0 | 25.5 | 26.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary rate | ES | 11 | 11 | 12 | 12 | 13 | 13 | 14 | 15 | 15 | 16 | 16 | 17 | 17 | 18 | 19 | 19 | 20 | 20 | 21 | 22 | 22 | 23 | 23 | 24 | 25 | 25 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Primary rate | ES | 3 | 4 | 4 | 4 | 4 | 5 | 5 | 5 | 6 | 6 | 6 | 6 | 7 | 7 | 7 | 7 | 8 | 8 | 8 | 8 | 9 | 9 | 9 | 10 | 10 | 10 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Secondary rate | ES | 5 | 6 | 6 | 6 | 6 | 7 | 7 | 7 | 8 | 8 | 8 | 9 | 9 | 10 | 10 | 10 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 14 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Tertiary rate | ES | 10 | 10 | 11 | 11 | 12 | 12 | 13 | 13 | 14 | 14 | 15 | 16 | 16 | 17 | 17 | 18 | 18 | 19 | 19 | 20 | 20 | 21 | 22 | 22 | 23 | 23 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Quaternary rate | ES | 26 | 28 | 29 | 30 | 31 | 33 | 34 | 35 | 36 | 37 | 39 | 40 | 41 | 42 | 44 | 45 | 46 | 47 | 49 | 50 | 51 | 52 | 54 | 55 | 56 | 58 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +**Table 2/M.1340 – 2-hour BIS limits for circuits carried on a data transmission system which has already been tested over 24 hours and is in service (*continued*)** + +| Allocation % | Event | 26.5 | 27.0 | 27.5 | 28.0 | 28.5 | 29.0 | 29.5 | 30.0 | 30.5 | 31.0 | 31.5 | 32.0 | 32.5 | 33.0 | 33.5 | 34.0 | 34.5 | 35.0 | 35.5 | 36.0 | 36.5 | 37.0 | 37.5 | 38.0 | 38.5 | 39.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary rate | ES | 26 | 26 | 27 | 28 | 28 | 29 | 29 | 30 | 31 | 31 | 32 | 33 | 33 | 34 | 34 | 35 | 36 | 36 | 37 | 37 | 38 | 39 | 39 | 40 | 41 | 41 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Primary rate | ES | 10 | 11 | 11 | 11 | 11 | 12 | 12 | 12 | 13 | 13 | 13 | 13 | 14 | 14 | 14 | 15 | 15 | 15 | 15 | 16 | 16 | 16 | 17 | 17 | 17 | 17 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Secondary rate | ES | 14 | 14 | 15 | 15 | 16 | 16 | 16 | 17 | 17 | 17 | 18 | 18 | 18 | 19 | 19 | 20 | 20 | 20 | 21 | 21 | 21 | 22 | 22 | 23 | 23 | 23 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Tertiary rate | ES | 24 | 24 | 25 | 26 | 26 | 27 | 27 | 28 | 28 | 29 | 29 | 30 | 31 | 31 | 32 | 32 | 33 | 34 | 34 | 35 | 35 | 36 | 36 | 37 | 38 | 38 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Quaternary rate | ES | 59 | 60 | 61 | 63 | 64 | 65 | 67 | 68 | 69 | 70 | 72 | 73 | 74 | 76 | 77 | 78 | 79 | 81 | 82 | 83 | 85 | 86 | 87 | 89 | 90 | 91 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +| Allocation % | Event | 39.5 | 40.0 | 40.5 | 41.0 | 41.5 | 42.0 | 42.5 | 43.0 | 43.5 | 44.0 | 44.5 | 45.0 | 45.5 | 46.0 | 46.5 | 47.0 | 47.5 | 48.0 | 48.5 | 49.0 | 49.5 | 50.0 | 50.5 | 51.0 | 51.5 | 52.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| < Primary rate | ES | 42 | 42 | | | | | | | | | | | | | | | | | | | | | | | | | +| | SES | 0 | 0 | | | | | | | | | | | | | | | | | | | | | | | | | +| Primary rate | ES | 18 | 18 | 18 | 19 | 19 | 19 | 20 | 20 | 20 | 20 | 21 | 21 | 21 | 22 | 22 | 22 | 23 | 23 | 23 | 23 | 24 | 24 | 24 | 25 | 25 | 25 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Secondary rate | ES | 24 | 24 | 24 | 25 | 25 | 26 | 26 | 26 | 27 | 27 | 27 | 28 | 28 | 29 | 29 | 29 | 30 | 30 | 30 | 31 | 31 | 32 | 32 | 32 | 33 | 33 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Tertiary rate | ES | 39 | 39 | 40 | 40 | 41 | 42 | 42 | 43 | 43 | 44 | 45 | 45 | 46 | 46 | 47 | 48 | 48 | 49 | 49 | 50 | 50 | 51 | 52 | 52 | 53 | 53 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Quaternary rate | ES | 92 | 94 | 95 | 96 | 98 | 99 | 100 | 102 | 103 | 104 | 106 | 107 | 108 | 109 | 111 | 112 | 113 | 115 | 116 | 117 | 119 | 120 | 121 | 123 | 124 | 125 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +**Table 2/M.1340 – 2-hour BIS limits for circuits carried on a data transmission system which has already been tested over 24 hours and is in service (*concluded*)** + +| Allocation % | Event | 52.5 | 53.0 | 53.5 | 54.0 | 54.5 | 55.0 | 55.5 | 56.0 | 56.5 | 57.0 | 57.5 | 58.0 | 58.5 | 59.0 | 59.5 | 60.0 | 60.5 | 61.0 | 61.5 | 62.0 | 62.5 | 63.0 | +|-----------------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------|------| +| Primary rate | ES | 26 | 26 | 26 | 26 | 27 | 27 | 27 | 28 | 28 | 28 | 29 | 29 | 29 | 29 | 30 | 30 | 30 | 31 | 31 | 31 | 32 | 32 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Secondary rate | ES | 34 | 34 | 34 | 35 | 35 | 35 | 36 | 36 | 37 | 37 | 37 | 38 | 38 | 39 | 39 | 39 | 40 | 40 | 40 | 41 | 41 | 42 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Tertiary rate | ES | 54 | 55 | 55 | 56 | 56 | 57 | 58 | 58 | 59 | 59 | 60 | 61 | 61 | 62 | 62 | 63 | 64 | 64 | 65 | 65 | 66 | 67 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| Quaternary rate | ES | 127 | 128 | 129 | 131 | 132 | 133 | 135 | 136 | 137 | 139 | 140 | 141 | 143 | 144 | 145 | 147 | 148 | 149 | 151 | 152 | 153 | 155 | +| | SES | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +ES Errored Seconds + +SES Severely Errored Seconds + +NOTE 1 – The % allocation relates to the proportion of the overall reference performance objective that is attributable to a particular routing configuration. + +NOTE 2 – The limits are applicable to discrete measurement periods of 2 hours. The 2-hour limits are derived from Table C/M.2100 [25]. + +NOTE 3 – Where a test has a discrete period of more than 2 hours, it is recommended that the limits be applied to each discrete period without averaging. + +NOTE 4 – The maximum % allocation of 40% in this table is consistent with the allowance for the high-grade quality classification given in Recommendation G.821 [2]. + +NOTE 5 – The ES and SES performance limits relate to the maximum number of errored seconds or severely errored seconds that would be acceptable in the measurement period. + +NOTE 6 – Performance limits for unavailable time are left for negotiation between Network Operators/Service Provider. However, it should be appreciated that an availability of 100% would normally be achieved during a typical 24-hour period and that a transition to unavailable state would be inconsistent with SES limits for allocations below 16.5%. + +**Table 3/M.1340 – Performance allocations for the derivation of performance limits for the international portion routed via a high grade transmission path** + +| International link portion component | Distance "d" (km) | Allocation % per 100 km | +|----------------------------------------------------------------|----------------------|-------------------------| +| Terrestrial (including transit and non-optical undersea cable) | $d \leq 500$ | 0.4 | +| | $500 < d \leq 1000$ | 3 | +| | $1000 < d \leq 2500$ | 4 | +| | $2500 < d \leq 5000$ | 6 | +| | $5000 < d \leq 7500$ | 8 | +| | $d > 7500$ | 10 | +| | | | +| Optical undersea cable | $d \leq 500$ | 1 | +| | $d > 500$ | 2.5 | +| Satellite | – | 20 | + +NOTE 1 – By negotiation, where sectional testing incorporates a terrestrial border crossing, it may be acceptable to incorporate an additional performance allocation (see Notes 3 and 4 in Table 2b/M.2100 [25]); an allocation of 0.5% is suggested. + +NOTE 2 – The allocations given in this table are maximum values and may be reduced by agreement between Network Operators/Service Providers. + +**Table 4/M.1340 – Short duration out-of-service test limits** + +| Dest duration | Objectives | | +|---------------|------------|-----| +| | ES | SES | +| 15 minutes | 0 | 0 | +| 1 hour | 5 | 0 | + +NOTE 1 – The ES and SES performance limits relate to the maximum number of errored seconds or severely errored seconds that would be acceptable in the test period specified. + +NOTE 2 – Where a 15-minute limit is exceeded, it may be useful to reference Annex D/M.2100 [25] and Table D.1/M.2100 [25] for guidance. + +NOTE 3 – The acceptable tolerance applicable to the limits of this table is dependent upon the overall allocation as defined in 3.1. + +## 9 Tables under study + +Tables 4 and 5 of the 1996 version of this Recommendation dealing with "24-hour in-service degraded performance limit thresholds" and "15-minute in-service unacceptable performance limit thresholds" require further study and are not contained in this edition. + +## APPENDIX I + +## **Guidelines for performance allocations of the national circuit portions of an international leased circuit** + +### **I.1 Scope** + +This appendix gives some examples to produce the performance limits for all digital test measurements associated with national circuit portions of PDH international leased circuits that are supported by an international data transmission system and that have a PDH digital interface at the Customer's premises. + +Terminology, operational procedures, performance parameters and derivation of performance limits in this appendix are identical to those described in this Recommendation. + +### **I.2 Basic principles** + +#### **I.2.1 Data rates below primary rate** + +The ES performance limits used in this appendix have a mathematical basis and are derived from 15% for local grade and 15% for medium grade as a maximum allowance of the ES objective for terminal national portions of an international leased circuit inside a national territory as described in Recommendation G.821 [2]; see Figure I.1. However, taking account of practical experience, the 8% ES objective proposed in Recommendation G.821 [2] is reduced to 4% (see Table 1a/M.2100 [25]). + +#### **I.2.2 Data rate at the primary rate and higher rates** + +The end-to-end error reference performance objectives at or above the primary rate are those given in Table 1b/M.2100 [25]. The reference performance objective for ES used in this appendix is based on a maximum of 2% (primary rate), 2.5% (secondary rate), 3.75% (tertiary rate) and 8% (quaternary rate) end-to-end reference performance objective as derived from Recommendation G.826 [3], where 18.5% (comprised of 17.5 block allowance plus 1% per 500 km) is the performance allocation for one terminal national portion of an international leased circuit, where the maximum allocation is 9.5% for the local grade and 9% for the medium grade inside national territory (see Figure I.1). + +The SES performance limits are identical to those for data rates below the primary rate. + +![Figure I.1/M.1340: Example of a model for a transmission system based on the Hypothetical Reference Connection (HRX).](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Diagram illustrating a transmission system model based on the Hypothetical Reference Connection (HRX). The total length is 27 500 km, divided into three circuit portions: National circuit portion (1250 km), International circuit portion (25 000 km), and National circuit portion (1250 km). The nodes are LTP (Link Terminating Point or Customer Premises), TNC (Terminal National Centre or Local Exchange), and TIC (Terminal International Centre or International Gateway). The overall allocation for bit rates is shown below the nodes. + +| Grade | Local grade | Medium grade | High grade | Medium grade | Local grade | +|-----------------|-------------|--------------|------------|--------------|-------------| +| < Primary rate: | 15.0% | 15.0% | 40.0% | 15.0% | 15.0% | + +LTP Link Terminating Point or Customer Premises + TIC Terminal International Centre or International Gateway + TNC Terminal National Centre or Local Exchange + +T0413720-99 + +Figure I.1/M.1340: Example of a model for a transmission system based on the Hypothetical Reference Connection (HRX). + +**Figure I.1/M.1340 – Example of a model for a transmission system based on the Hypothetical Reference Connection (HRX) with the location of the boundary between the medium and the high grade portions of the HRX on TIC** + +![Figure I.2/M.1340: Example of a model for a transmission system based on the Hypothetical Reference Path.](366a77fdefb0097b3289b4a011911390_img.jpg) + +Diagram illustrating a transmission system model based on the Hypothetical Reference Path. The total length is 27 500 km, divided into three circuit portions: National circuit portion (500 km min), International circuit portion (26 500 km max), and National circuit portion (500 km min). The nodes are LTP (Link Terminating Point or Customer Premises), TNC (Terminal National Centre or Local Exchange), and TIC (Terminal International Centre or International Gateway). The overall allocation for bit rates is shown below the nodes. + +| Grade | Local grade | Medium grade | High grade | Medium grade | Local grade | +|----------------------------------|-------------|--------------|------------|--------------|-------------| +| Overall allocation for bit rates | 17.5% | +1% /500 Km | 63%
max | 17.5% | +1% /500 Km | + +LTP Link Terminating Point or Customer Premises + TIC Terminal International Centre or International Gateway + TNC Terminal National Centre or Local Exchange + +T0414190-99 + +Figure I.2/M.1340: Example of a model for a transmission system based on the Hypothetical Reference Path. + +**Figure I.2/M.1340 – Example of a model for a transmission system based on the Hypothetical Reference Path** + +The definition of "local grade" is the classification for transmission path between LTP or Customer Premises and the nearest TNC or local exchange. The definition of "medium grade" is the classification for transmission path between nearest TNC to LTP or Customer Premises and TIC or IG where the maximum distance is 1250 km. When the distance is greater than 1250 km, a part of the national circuit portion should be routed over a high-grade transmission path. + +### I.3 Error performance allocation principles + +#### I.3.1 Performance allocation + +Figure I.3 is a schematic diagram example of the possible regional networks within one national territory showing the LTPs, FSs, TNCs and TICs (see also Figures 2a/M.2100 [25] and 3/M.2100 [25]). For the national circuit portions, the percentage performance allocations attributable to terminating TNCs and TIC are determined by reference to Table 1. Where a national circuit portion is provided over a high grade transmission path, an allocation consistent with the terrestrial components given in Table 2 is recommended. + +![Figure I.3/M.1340 – Performance allocation for the national circuit portion of an international leased circuit. The diagram shows a circuit path across three network domains (A, B, and C) with various components (LTP, TNC, TIC, FS) and distance segments (a-g km).](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates a circuit path across three network domains: Network Operator/Domain A, Network Operator/Domain B, and Network Operator/Domain C. The path starts at an LTP (Link Terminating Point) and ends at an FS (Frontier Station). The path is divided into segments with distances: *a* km, *b* km, *c* km, *d* km, *e* km, *f* km, and *g* km. The components along the path are: LTP, TNC (Terminal National Centre or Local Exchange), TNC, TNC, TNC, TNC, TIC (Terminal International Centre or International Gateway), and FS. A horizontal line indicates a maximum distance of 1250 km from the LTP to the TIC. The path is further divided into three grades: Local grade (from LTP to the first TNC), Medium grade (from the first TNC to the TIC), and High grade (from the TIC to the FS). A legend at the bottom defines the components: FS (Frontier Station), LTP (Link Terminating Point or Customer Premises), TIC (Terminal International Centre or International Gateway), and TNC (Terminal National Centre or Local Exchange). The diagram is labeled T0413730-99. + +Figure I.3/M.1340 – Performance allocation for the national circuit portion of an international leased circuit. The diagram shows a circuit path across three network domains (A, B, and C) with various components (LTP, TNC, TIC, FS) and distance segments (a-g km). + +**Figure I.3/M.1340 – Performance allocation for the national circuit portion of an international leased circuit** + +The 24-hour performance limits derived are applicable to all out-of-service tests (e.g. BIS, maintenance intervention and return to service after repair) of the overall national data transmission link (LTP-to-TIC) or system. + +#### I.3.2 Portion performance allocation + +For certain operational test requirements (e.g. during maintenance investigation and routing re-arrangements), it could be necessary to perform 24-hour tests of component portions of a national data transmission link. The component portions should be measured according to Table 2. + +To evaluate the allocation in the national portion of a leased circuit operating at the primary rate or above in a multi-operator environment, the following model in Figure I.4 is proposed: + +![Figure I.4/M.1340 – Model for performance allocation in a multi-operator environment. The diagram shows a network path from a Local Terminal Point (LTP) to a Central Terminal Node (CTN), then through a 'Medium grade' section, and finally through another CTN to another LTP. The 'Local grade' sections at the ends have specific performance allocation rules: 9.5% for copper or radio, 1% for fibre optics, and an additional +3% if the LTP is in a rural area. The 'Medium grade' section has allocations of 1% for the first 100 km block and 0.5% for subsequent 100 km blocks. A reference code T0413740-99 is present.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +**Local grade:** + 9.5% (copper or radio) + 1% (fibre optics) + +3% if the LTP is located in a rural area + +**Medium grade:** + 1% for each 100 km block for the first 200 km; + 0.5% for each 100 km for the following 100-km blocks + +**Local grade:** + 9.5% (copper or radio) + 1% (fibre optics) + +3% if the LTP is located in a rural area + +T0413740-99 + +Figure I.4/M.1340 – Model for performance allocation in a multi-operator environment. The diagram shows a network path from a Local Terminal Point (LTP) to a Central Terminal Node (CTN), then through a 'Medium grade' section, and finally through another CTN to another LTP. The 'Local grade' sections at the ends have specific performance allocation rules: 9.5% for copper or radio, 1% for fibre optics, and an additional +3% if the LTP is in a rural area. The 'Medium grade' section has allocations of 1% for the first 100 km block and 0.5% for subsequent 100 km blocks. A reference code T0413740-99 is present. + +**Figure I.4/M.1340 – Model for performance allocation in a multi-operator environment** + +This model is recursively applied to each interconnection between Network Operators/Service Providers. + +Figure I.5 is an example of the national portion of an international circuit carried by a National Operator (A) and an International Operator [owner of the International Gateway (IG)]. + +![Figure I.5/M.1340 – Example of performance allocation in a multi-operator environment. This diagram shows a specific example of the model in Figure I.4. It starts with an LTP connected to a CTN (Op. A), followed by a 'Medium grade (100 km)' section, and then another CTN (Op. A) connected to an IG (Operator B). The allocations are: 'Copper Access Allocation = 9.5%' for the first local section, 'Medium grade (100 km) Allocation = 1%' for the middle section, and 'Local grade fibre optics Allocation = 1%' for the final local section. The total allocation in the national portion is stated as 11.5%. A reference code T0413750-99 is present.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +**Copper Access Allocation = 9.5%** + +**Medium grade (100 km) Allocation = 1%** + +**Local grade fibre optics Allocation = 1%** + +**Total allocation in the national portion = 11.5 %** + +T0413750-99 + +Figure I.5/M.1340 – Example of performance allocation in a multi-operator environment. This diagram shows a specific example of the model in Figure I.4. It starts with an LTP connected to a CTN (Op. A), followed by a 'Medium grade (100 km)' section, and then another CTN (Op. A) connected to an IG (Operator B). The allocations are: 'Copper Access Allocation = 9.5%' for the first local section, 'Medium grade (100 km) Allocation = 1%' for the middle section, and 'Local grade fibre optics Allocation = 1%' for the final local section. The total allocation in the national portion is stated as 11.5%. A reference code T0413750-99 is present. + +**Figure I.5/M.1340 – Example of performance allocation in a multi-operator environment** + +Network Operators/Service Providers must ensure that the sum total of allocations for individual component portions is consistent with the allocation principles described above. Where the overall allocation is exceeded, Network Operators/Service Providers should agree on proportional reductions to portion allocations by negotiation. + +Agreed portion allocations should be applied to the appropriate part of Table 1 for the determination of single 24-hour test limits for ES and SES. These test limits may be used for all out-of-service test requirements between agreed MPs. + +### **I.4 Short duration test objectives** + +See clause 7. + +### **I.5 In-service performance monitoring** + +See clause 8. + + + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Languages and general software aspects for telecommunication systems | + +\*18184\* \ No newline at end of file diff --git a/marked/M/T-REC-M.1350-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1350-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8967263e94cc020db44108f9f929ce89749730f2 --- /dev/null +++ b/marked/M/T-REC-M.1350-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b7751536cfb17e96fbeb670ae3c5fdc669ad3ff20c609514318fe5a8e838689 +size 7485 diff --git a/marked/M/T-REC-M.1355-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1355-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..953f50794048267c80273e09dfd065a72e63a66b --- /dev/null +++ b/marked/M/T-REC-M.1355-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d93a2984bd727a586cdd1473146f57aa0c7b6e50bc9fe2f8dc71c86a8b2d80f5 +size 7462 diff --git a/marked/M/T-REC-M.1370-199806-I_PDF-E/raw.md b/marked/M/T-REC-M.1370-199806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a1b36a2524d9c79496b764b855fe939bc3f7b4e6 --- /dev/null +++ b/marked/M/T-REC-M.1370-199806-I_PDF-E/raw.md @@ -0,0 +1,375 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1370** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(06/98) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**Bringing-into-service of international data +transmission systems** + +ITU-T Recommendation M.1370 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.1370** + +# **BRINGING-INTO-SERVICE OF INTERNATIONAL DATA TRANSMISSION SYSTEMS** + +## **Summary** + +This Recommendation describes bringing-into-service procedures for international data transmission systems with a PDH presentation. + +### **Source** + +ITU-T Recommendation M.1370 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of June 1998. + +### **Keywords** + +Bringing-into-service, exchange of information for bringing-into-service, international data transmission link, international data transmission system. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 References ..... | 1 | +| 3 Terminology and definitions ..... | 1 | +| 4 Abbreviations ..... | 2 | +| 5 Performance limits and objectives..... | 2 | +| 6 Preliminary exchange of information ..... | 2 | +| 7 Bringing-into-service procedures for an international data transmission link..... | 3 | +| 7.1 Setting up and lining up individual link sections ..... | 3 | +| 7.2 Setting up and testing procedures for national and international link sections ..... | 3 | +| 7.3 Setting up and testing procedures for an overall international data transmission link ..... | 3 | +| 8 Bringing-into-service procedures for an international data transmission system..... | 5 | +| 8.1 General..... | 5 | +| 8.2 Local multiplexing equipment tests ..... | 5 | +| 8.3 Multiplexing equipment interworking tests ..... | 5 | +| 8.4 System stability test..... | 5 | +| 8.5 System configuration tests ..... | 5 | +| 8.6 Introduction into service ..... | 6 | +| 9 System and link integration ..... | 6 | +| 10 Measurement configurations ..... | 6 | + + + +# BRINGING-INTO-SERVICE OF INTERNATIONAL DATA TRANSMISSION SYSTEMS + +(Published in 1984; revised in 1988, 1993 and 1998) + +# 1 Scope + +The requirements described in this Recommendation should ensure that an international data transmission system is fully tested in terms of performance and interworking of multiplexing equipment1 prior to introduction into service. + +The bringing-into-service tests described in this Recommendation should ideally include periods of normal industrial activity to be representative of typical network conditions. + +## 2 References + +The following ITU-T Recommendations contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation M.20 (1992), *Maintenance philosophy for telecommunications networks.* +- [2] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [3] ITU-T Recommendation M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [4] ITU-T Recommendation M.1300 (1997), *International data transmission systems operating in the range 2.4 kbit/s to 140 Mbit/s.* +- [5] ITU-T Recommendation M.1340 (1996), *Performance allocations and limits for international data transmission links and systems.* +- [6] ITU-T Recommendation M.1380 (1997), *Bringing-into-service of international leased circuits that are supported by international data transmission systems.* +- [7] ITU-T Recommendation M.1400 (1997), *Designations for international networks.* +- [8] ITU-T Recommendation M.2110 (1997), *Bringing-into-service of international digital paths, sections and transmission systems and SDH paths and multiplex sections.* +- [9] CCITT Recommendation O.151 (1992), *Error performance measuring equipment operating at the primary rate and above.* +- [10] CCITT Recommendation O.152 (1992), *Error performance measurement equipment for bit rates of 64 kbit/s and $N \times 64$ kbit/s.* +- [11] CCITT Recommendation O.153 (1992), *Basic parameters for the measurement of error performance at bit rates below the primary rate.* + +# 3 Terminology and definitions + +Recommendation M.1300 [4] provides general descriptions of international data transmission links and international data transmission systems. + +--- + +1 The term "multiplexing equipment", as defined in Recommendation M.60 [2], includes digital cross-connect equipment. + +Terminologies and definitions relating to this Recommendation are provided in Recommendation M.60 [2]. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|----------------------------------| +| DXC | Digital Cross-Connect | +| ES | Errored Second | +| LTP | Link Terminating Point | +| MUX | Multiplexing Equipment | +| PDH | Plesiochronous Digital Hierarchy | +| SES | Severely Errored Second | + +# 5 Performance limits and objectives + +Recommendation M.1340 [5] covers all performance limits and objectives associated with this Recommendation. For all performance tests described in this Recommendation, the Errored Second (ES) and Severely Errored Second (SES) limits should be met simultaneously for the test result to be considered acceptable. + +# 6 Preliminary exchange of information + +To assist in the setting-up and bringing-into-service of international data transmission systems, it is important that Network Operators/Service Providers exchange information (as detailed in Recommendation M.1045 [3]) and agree as necessary on the following: + +- i) Multiplexing equipment1 interfacing and data structuring specifications that can confirm the likelihood of compatible interworking. +- ii) An equipment configuration diagram showing connection arrangements and the location and interface types of test points. + +This diagram should include reference to the Link Terminating Point (LTP) and all channel test points. + +- iii) A schematic routing diagram that identifies the location of LTPs, earth stations, terrestrial frontier stations and terminal international centres showing approximate distances in kilometres (except for any satellite sections or national link sections). + +This diagram should be used to calculate performance limits in accordance with Recommendation M.1340 [5] (see 3.1/M.1340 and Figure 1/M.1340). + +- iv) Details of test equipment that will be used for normal provision and maintenance operations. Test equipment specifications should be compared to ensure a consistent interpretation of typical transmission error events. +- v) Pseudo-random test patterns to be used. These should be in accordance with Recommendations O.151 [9], O.152 [10] and O.153 [11] as appropriate. (More severe test patterns that are available on some test equipment may be used following bilateral agreement. However, it should be appreciated that certain pseudo-random test patterns may stress a transmission system beyond its original design specification.) +- vi) A bringing-into-service schedule taking account of the test requirements and sequence of clauses 7 and 8 below. Dependent upon resource constraints, Network Operators/Service Providers may need to schedule testing several weeks or even months in advance of the proposed bringing-into-service date. + +- vii) A designation in accordance with Recommendation M.1400 [7]. +- viii) Contact details for operational and planning personnel. +- ix) Network Operators/Service Providers should agree on a dual control or a control and sub-control relationship for the terminal stations of the international data transmission system (see clause 10/M.1300 [4]). + +The bringing-into-service information exchanged, as detailed above, should be retained for future reference. + +# **7 Bringing-into-service procedures for an international data transmission link** + +## **7.1 Setting up and lining up individual link sections** + +Individual link sections should be set up or lined up as separate entities in accordance with the Recommendations and procedures appropriate to the transmission medium involved. + +Where an individual link section exists wholly within the network of a single Network Operator/Service Provider, the internal practices of that Network Operator/Service Provider may be used for setting up or lining up, provided that the limits used are consistent with the overall performance requirements for an international data transmission link. + +Where an individual link section is wholly contained within an existing data transmission system that has already been extensively tested, Network Operators/Service Providers may agree to reduce this requirement to a short duration test of 15 minutes, with performance limits as given in Table 3/M.1340 [5]. + +## **7.2 Setting up and testing procedures for national and international link sections** + +When successfully tested, the individual link sections described in 7.1 above should be interconnected to form the national or international sections as appropriate. These should then be checked for data transmission performance using limits that are consistent with the requirements of Recommendation M.1340 [5]. A test duration of 24 hours is desirable; however, a shorter duration test, as described in 7.1, may be appropriate. + +## **7.3 Setting up and testing procedures for an overall international data transmission link** + +When the international and any national sections have been tested and found to be satisfactory (see 7.2 above), they should then be interconnected to form the overall international data transmission link. + +It should be confirmed that test access arrangements are such that no part of the overall international data transmission link can be excluded from test. In accordance with Recommendation M.1300 [4], the LTPs at either end of an international data transmission link should provide a digital interface. Any equipment necessary to provide this interface is considered to be part of the link. + +The international data transmission link should be tested for 24 hours using limits derived in accordance with Recommendation M.1340 [5]. However, a shorter duration test, as described in 7.1, may be appropriate. + +Where the 24-hour performance limits given in Recommendation M.1340 [5] are not met, Network Operators/Service Providers should investigate the reasons for the test failure and endeavour to rectify any problems identified. + +Any possible effects of network traffic loading on data tests are for further study. + +Figure 1 illustrates the bringing-into-service tests and procedures. + +### **i) International data transmission link** + +Stage 1: Setting-up and lining-up of individual link sections (see 7.1) + +![Diagram for Stage 1: Setting-up and lining-up of individual link sections. It shows a series of 10 test equipment (T) blocks connected in a chain by horizontal lines, representing individual link sections being tested one by one.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Diagram for Stage 1: Setting-up and lining-up of individual link sections. It shows a series of 10 test equipment (T) blocks connected in a chain by horizontal lines, representing individual link sections being tested one by one. + +Stage 2: Setting up and testing of national and international link sections (see 7.2) + +![Diagram for Stage 2: Setting up and testing of national and international link sections. It shows a sequence: LTP (Test equipment) - National link section - TIC (Terminal International Centre, containing two Test equipment blocks) - International link section - TIC (containing two Test equipment blocks) - National link section - LTP (Test equipment).](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Diagram for Stage 2: Setting up and testing of national and international link sections. It shows a sequence: LTP (Test equipment) - National link section - TIC (Terminal International Centre, containing two Test equipment blocks) - International link section - TIC (containing two Test equipment blocks) - National link section - LTP (Test equipment). + +Stage 3: Setting-up and testing of an overall international data transmission link (see 7.3) + +![Diagram for Stage 3: Setting-up and testing of an overall international data transmission link. It shows a single long horizontal line representing the overall link, terminated at both ends by LTP (Test equipment) blocks.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +Diagram for Stage 3: Setting-up and testing of an overall international data transmission link. It shows a single long horizontal line representing the overall link, terminated at both ends by LTP (Test equipment) blocks. + +### **ii) International data transmission system** + +Stage 1: Local multiplexing equipment tests (see 8.2) + +![Diagram for Stage 1: Local multiplexing equipment tests. A Test equipment (T) block is connected to a Multiplexer (MUX) block. The MUX has two additional input arrows on its top side labeled 'Alarms' and 'Synchronization'.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +Diagram for Stage 1: Local multiplexing equipment tests. A Test equipment (T) block is connected to a Multiplexer (MUX) block. The MUX has two additional input arrows on its top side labeled 'Alarms' and 'Synchronization'. + +Stage 2: Multiplexing equipment interworking tests (see 8.3) + +![Diagram for Stage 2: Multiplexing equipment interworking tests. Two Multiplexer (MUX) blocks are connected to each other via their LTP (Link Terminating Point) outputs. Each MUX is also connected to its own Test equipment (T) block.](b10763be31553f31cbb795653b731a43_img.jpg) + +Diagram for Stage 2: Multiplexing equipment interworking tests. Two Multiplexer (MUX) blocks are connected to each other via their LTP (Link Terminating Point) outputs. Each MUX is also connected to its own Test equipment (T) block. + +Stage 3: System test (see 8.4) + +![Diagram for Stage 3: System test. Two Multiplexer (MUX) blocks are connected to each other via their LTP outputs. The left MUX is connected to a Test equipment (T) block, and the right MUX is connected to another Test equipment (T) block.](4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg) + +Diagram for Stage 3: System test. Two Multiplexer (MUX) blocks are connected to each other via their LTP outputs. The left MUX is connected to a Test equipment (T) block, and the right MUX is connected to another Test equipment (T) block. + +Stage 4: System configuration tests (see 8.5) + +![Diagram for Stage 4: System configuration tests. Two Multiplexer (MUX) blocks are connected to each other via their LTP outputs. The left MUX is connected to a Test equipment (T) block with text 'e.g. 56 kbit/s N x 64 kbit/s'. The right MUX is connected to a Test equipment (T) block with the same text 'e.g. 56 kbit/s N x 64 kbit/s'.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +Diagram for Stage 4: System configuration tests. Two Multiplexer (MUX) blocks are connected to each other via their LTP outputs. The left MUX is connected to a Test equipment (T) block with text 'e.g. 56 kbit/s N x 64 kbit/s'. The right MUX is connected to a Test equipment (T) block with the same text 'e.g. 56 kbit/s N x 64 kbit/s'. + +T0408870-98/d01 + +![Legend icon: A square box containing the letter 'T'.](1d530397c18af61370c07ad00bb26011_img.jpg) + +Legend icon: A square box containing the letter 'T'. + +Test equipment + +![Legend icon: A square box containing the letters 'M', 'U', and 'X' stacked vertically.](535b37bd5617cb193bb7544cf84b44eb_img.jpg) + +Legend icon: A square box containing the letters 'M', 'U', and 'X' stacked vertically. + +Multiplexer or Digital Cross-connect + +LTP Link Terminating Point + +TIC Terminal International Centre + +**Figure 1/M.1370 – Bringing-into-service of an international data transmission system** + +# **8 Bringing-into-service procedures for an international data transmission system** + +## **8.1 General** + +These tests are intended to prove the error performance stability and correct operation of an international data transmission system. + +## **8.2 Local multiplexing equipment2 tests** + +Each Network Operator/Service Provider should check the operation of the multiplexing equipment2 that will be used to support the international data transmission system. This should include a check of peripheral equipment such as power supplies and connecting leads. These checks should be performed well in advance prior to actual connection to an international data transmission link. + +## **8.3 Multiplexing equipment2 interworking tests** + +With the multiplexing equipment2 connected to the international data transmission link, the interworking of alarms should be confirmed. The LTP receive and transmit connections should be disconnected at each end in turn and the alarm conditions detected should be recorded (e.g. Alarm Indication Signal – Recommendation M.20 [1]). + +On some occasions it may be possible to introduce simulated error transmissions. Where this is possible, errors should be injected in turn at each end of the international data transmission link at the LTPs. A check should be made to confirm that the appropriate alarm condition is observed at the distant end. + +## **8.4 System stability test** + +This test is intended to confirm the stable interworking of terminal multiplexing equipment and to provide further confirmation of the performance of the international data transmission link. Channel error performance tests are performed simultaneously in each direction of transmission. + +A system stability test, at one particular channel data rate, should be undertaken. The test duration and data rate used should be set by bilateral agreement taking account of past experience. To provide a reliable indication of overall system stability, a minimum test duration of 24 hours is recommended. However, there are two cases where a short duration test may be appropriate. The first is if system stability has been confirmed for an identical equipment configuration using the same transmission facility. The second is if in-service performance monitoring (described in clause 5/M.1340 [5]) is available and that the performance of the system is shown to be good. In both of these cases, agreement between the Network Operators/Service Providers is required. + +If the MUX in Figure 1 is in practice a Digital Cross-Connect (DXC), then the cross-connect function should be used to test at the channel rate. + +Where the performance limits derived in accordance with Recommendation M.1340 [5] are not met, reference should be made to the performance results achieved during tests of the international data transmission link. If these results are inconsistent, fault localization should be performed. + +## **8.5 System configuration tests** + +These tests are intended to confirm the ability of an international data transmission system to support the intended range of channel types. A 15-minute test duration is considered appropriate. Tests should be performed at all digital channel data rates to be offered on the particular system being set up. Recommendation M.1340 [5] (see Table 3/M.1340) provides short-duration test objectives that are appropriate for digital configuration testing. + +--- + +2 The term "multiplexing equipment", as defined in Recommendation M.60 [2], includes digital cross-connect equipment. + +If the MUX in Figure 1 is in practice a Digital Cross-Connect (DXC), then the cross-connect function should be used to test at the channel rate. Network Operators/Service Providers may agree to forego the system configuration tests if an identical equipment configuration has been previously tested. + +Provided that the system stability test was completed satisfactorily, a configuration test is unlikely to indicate a transmission quality problem. It may be appropriate to check the configuration of the multiplexing equipment that is being used, especially where the problem exists for only one channel type. + +## **8.6 Introduction into service** + +The Network Operators/Service Providers involved should jointly confirm that all testing has been satisfactorily completed prior to opening an international data transmission system for commercial service. + +# **9 System and link integration** + +Throughout the bringing-into-service procedures described above, Network Operators/Service Providers should pay particular attention to highlighting any problems associated with the interconnection of separately timed networks (see also Recommendation M.1380 [6]). + +# **10 Measurement configurations** + +Several test measurement configurations are possible (see Figure 1/M.2110 [8]). Where possible, bidirection test measurement configurations should be used. Where loop tests are employed, the M.1340 [5] performance limits applicable to one direction of transmission should be used (i.e. doubling of limits is not recommended). + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.1375-199806-I_PDF-E/raw.md b/marked/M/T-REC-M.1375-199806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ef04755a6c9177694c39cf5821d316034f6cde46 --- /dev/null +++ b/marked/M/T-REC-M.1375-199806-I_PDF-E/raw.md @@ -0,0 +1,521 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1375** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(06/98) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**Maintenance of international data transmission +systems** + +ITU-T Recommendation M.1375 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.1375** + +# **MAINTENANCE OF INTERNATIONAL DATA TRANSMISSION SYSTEMS** + +## **Summary** + +This Recommendation describes the procedures and tests for the maintenance of international data transmission systems with a PDH presentation. + +### **Source** + +ITU-T Recommendation M.1375 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of June 1998. + +### **Keywords** + +Fault information exchange, fault localization, fault reporting procedure, in-service monitoring, international data transmission link, international data transmission system, international leased circuit, maintenance, planned Maintenance. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +*Page* + +| | | | +|------|-------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Terminology and definitions ..... | 2 | +| 4 | Abbreviations ..... | 2 | +| 5 | Performance limits and objectives..... | 2 | +| 6 | Maintenance records..... | 3 | +| 7 | Fault reporting procedures..... | 3 | +| 7.1 | Control and sub-control status ..... | 3 | +| 7.2 | Fault information exchange..... | 3 | +| 8 | Fault localization ..... | 4 | +| 9 | Maintenance tests ..... | 4 | +| 9.1 | General..... | 4 | +| 9.2 | Maintenance intervention tests..... | 4 | +| 9.3 | Returning to service tests ..... | 4 | +| 9.4 | Loopback tests..... | 7 | +| 9.5 | Test access at Digital Cross-Connect (DXC) equipment ..... | 7 | +| 10 | In-service monitoring ..... | 7 | +| 11 | Temporary service restoration ..... | 8 | +| 11.1 | Mechanisms for implementing temporary service restoration ..... | 8 | +| 11.2 | Time to restore service ..... | 8 | +| 11.3 | Restoration procedure ..... | 9 | +| 11.4 | Returning to normal routing..... | 9 | +| 11.5 | Information that should be exchanged ..... | 9 | +| 12 | Automatic rerouting of international data transmission links..... | 9 | +| 13 | Precautions to be taken in the use of DXCs ..... | 9 | +| 14 | Planned maintenance ..... | 10 | + + + +# **MAINTENANCE OF INTERNATIONAL DATA TRANSMISSION SYSTEMS** + +*(Published in 1984; revised in 1988, 1993, 1996 and 1998)* + +## **1 Scope** + +The requirements of this Recommendation are intended to ensure effective maintenance of international data transmission systems. The aim of this Recommendation is to minimize the number and duration of any interruptions to the customer's international leased circuit. + +## **2 References** + +The following ITU-T Recommendations contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [2] CCITT Recommendation M.80 (1988), *Control stations.* +- [3] CCITT Recommendation M.90 (1988), *Sub-control stations.* +- [4] CCITT Recommendation M.1012 (1988), *Circuit control station for leased and special circuits.* +- [5] CCITT Recommendation M.1013 (1988), *Sub-control station for leased and special circuits.* +- [6] ITU-T Recommendation M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [7] ITU-T Recommendation M.1300 (1997), *Maintenance of international data transmission systems operating in the range 2.4 kbit/s to 140 Mbit/s.* +- [8] ITU-T Recommendation M.1340 (1996), *Performance allocations and limits for international data transmission links and systems.* +- [9] ITU-T Recommendation M.1370 (1993), *Bringing-into-service of international data transmission systems.* +- [10] ITU-T Recommendation M.1385 (1993), *Maintenance of international leased circuits that are supported by international data transmission systems.* +- [11] ITU-T Recommendation M.1400 (1997), *Designations for international network.* +- [12] ITU-T Recommendation M.1540 (1994), *Exchange of information for planned outages of transmission systems.* +- [13] CCITT Recommendation M.1560 (1992), *Escalation procedure for international leased circuits.* +- [14] ITU-T Recommendation M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH paths, sections and transmission systems.* +- [15] ITU-T Recommendation M.2110 (1997), *Bringing-into-service of international PDH paths, sections and transmission systems and SDH paths and multiplex sections.* + +- [16] ITU-T Recommendation M.2120 (1997), *PDH path, section and transmission system and SDH paths and multiplex section fault detection and localization procedures.* +- [17] ITU-T Recommendation G.701 (1993), *Vocabulary of digital transmission and multiplexing, and Pulse Code Modulation (PCM) terms.* +- [18] ITU-T Recommendation G.704 (1995), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels.* +- [19] CCITT Recommendation G.706 (1991), *Frame alignment and Cyclic Redundancy Check (CRC) procedures relating to basic frame structures defined in Recommendation G.704.* +- [20] ITU-T Recommendation G.736 (1993), *Characteristics of a synchronous digital multiplex equipment operating at 2048 kbit/s.* +- [21] ITU-T Recommendation G.783 (1997), *Characteristics of Synchronous Digital Hierarchy (SDH) equipment functional blocks.* +- [22] CCITT Recommendation G.796 (1992), *Characteristics of a 64 kbit/s cross-connect equipment with 2048 kbit/s access ports.* +- [23] CCITT Recommendation X.50 (1988), *Fundamental parameters of a multiplexing scheme for the international interface between synchronous data networks.* + +## 3 Terminology and definitions + +Recommendation M.1300 [7] provides general descriptions of international data transmission links and international data transmission systems. + +Terminologies and definitions relating to this Recommendation are provided in Recommendations M.60 [1] and G.701 [17]. + +For the purposes of this Recommendation the following definition applies: + +The term **"structured" (sometimes known as "framed")** indicates that a frame structure such as those defined in Recommendation G.704 [18] is used. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|---------------------------------------| +| CRC | Cyclic Redundancy Check | +| CSES | Consecutive Severely Errored Seconds | +| DXC | Digital Cross-Connect | +| ES | Errored Second | +| SDH | Synchronous Digital Hierarchy | +| SES | Severely Errored Second | +| TMN | Telecommunications Management Network | +| UTC | Coordinated Universal Time | + +## 5 Performance limits and objectives + +Recommendation M.1340 [8] covers all performance limits and objectives associated with this Recommendation. For all performance tests described in this Recommendation, the Errored Second (ES) and Severely Errored Second (SES) limits should be met simultaneously for the test result to be considered acceptable. + +Additionally, periods of Consecutive Severely Errored Seconds (CSES) should be avoided as these can cause a severe impact on some customers' applications that are supported by international data transmission systems, (see clause 5/M.1385 [10]). + +## 6 Maintenance records + +Network Operators/Service Providers should ensure that up-to-date information is held on file to assist with maintenance activities. In particular, Network Operators/Service Providers should aim to hold all information highlighted in clause 6/M.1370 [9]. + +## 7 Fault reporting procedures + +### 7.1 Control and sub-control status + +At the bringing-into-service stage, Network Operators/Service Providers will have agreed on a dual control or on a control and sub-control relationship for the terminal stations of an international data transmission system (see clause 10/M.1300 [7]). + +Where a control and sub-control relationship exists, responsibilities will be as described in Recommendations M.80 [2], M.90 [3], M.1012 [4] and M.1013 [5]. + +Where a dual control relationship has been established, Network Operators/Service Providers should have agreed an effective mechanism for coordinating maintenance activities. Under this arrangement, to avoid confusion, it is essential that the terminal stations inform each other of maintenance activities as rapidly as possible. + +### 7.2 Fault information exchange + +In general, fault information relating to an international data transmission system can originate from four sources: + +- a customer (due to the failure or poor performance of an international leased circuit); +- a lower order system1 operator (due to the failure or poor performance of a lower order system that is supported as a channel on this system); +- the system itself (through alarms or distant operator); +- a network or higher order system1 operator (with notification of the failure or poor performance of the higher order network that supports this system or recognition of a transmit problem from this system). + +Where fault information is received directly from a customer, reference should additionally be made to Recommendation M.1385 [10]. + +During fault localization and clearance, fault information exchange should be as indicated in Figure 1. + +Where a fault is passed from one operator to another, or between Network Operators/Service Providers, as much information as possible should be exchanged including: + +- the name, title and contact details for the person reporting the fault; +- time of fault report, recorded in UTC; +- designation of the faulty system (see Recommendation M.1400 [11]); +- symptoms of the fault; +- the observed duration of the fault prior to a report being made; +- fault reference numbers; +- any associated information that may assist with fault clearance. + +The above fault information may be exchanged electronically, for example, using a TMN X interface. + +--- + +1 The terminology covering lower order systems and higher order systems relates to the hierarchical transmission data rate of the terminal multiplexing equipments that are interconnected to support service. A typical lower and higher order system relationship would exist where a 64 kbit/s international data transmission system (see Recommendation X.50 [23]) is supported as a channel on a 2048 kbit/s international data transmission system (see Recommendation G.736 [20]). + +When a fault is cleared, appropriate clearance information should be passed to stations that had been involved with initial fault reporting and localization. + +## **8 Fault localization** + +Figure 1 provides a systematic and coordinated procedure for efficient fault localization. + +Initial localization should aim to identify as quickly as possible whether the fault is due to the international data transmission link or the terminal multiplexing equipment2. Subsequent localization should aim to identify the specific link section or equipment that has failed. + +Where the TMN methodology is used, automatic identification of the exact cause of problems may greatly simplify fault monitoring and localization. + +Where fault localization is not achieved in a reasonable time, Network Operators/Service Providers shall invoke the agreed escalation procedure (see Recommendation M.1560 [13]) to assist progress. + +## **9 Maintenance tests** + +### **9.1 General** + +Existing maintenance records should provide details of test equipment, test points, test patterns and performance limits that are to be used for the maintenance of specific international data transmission systems. Where information is incomplete or out of date, reference should be made to Recommendations M.1340 [8] and M.1370 [9] as appropriate. + +Maintenance tests should be kept as short as possible to avoid significantly extending out-of-service time. Care must be taken to avoid the use of loopbacks to localize system faults, as this may disrupt one or more customers' circuits on the same system. + +Where an international data transmission system has yet to be fully utilized, that is, where it has spare capacity, it may be possible to connect test equipment to monitor the performance of one channel. The data from such tests may provide a useful indication of the overall performance of the international data transmission system. + +### **9.2 Maintenance intervention tests** + +Several test measurement configurations are possible; see Figure 1/M.2110 [15] for guidance. Maintenance intervention testing should be of a duration that is appropriate to the nature of the fault report that has been received. + +Where a report suggests that a system has failed completely, a short test of basic integrity should be performed. Such tests, which are interpreted on a simple pass or fail basis, should normally be limited to a duration of 15 minutes with no Severely Errored Seconds (SES) being observed. + +Where a fault report suggests that there is an overall degradation of service, but that the system has not failed completely, longer duration tests (1 hour or 24 hours) should be performed as appropriate. It may be possible for some tests to be performed via protected monitoring points with the system still in service. This may be particularly useful when the fault is believed to be in the data receive direction. Where an out-of-service test is necessary, full account should be taken of the traffic that is being supported. On some occasions, it may be appropriate to defer testing until such time as it is most convenient for customers. + +### **9.3 Returning to service tests** + +Returning to service tests should be of a duration that is appropriate to the nature of the fault that has been cleared and should include observation of any network alarm facilities that may be available. Where a fault had caused a general degradation of performance, a returning to service test with a short duration (e.g. 15 minutes) may not be appropriate, and a longer-term test (e.g. 1 hour or 24 hours) should be used. + +--- + +2 The term "multiplexing equipment", as defined in Recommendation M.60 [1], includes digital cross-connect equipment. + +![Flowchart titled 'Actions on receipt of fault information' (Figure 1/M.1375). It details procedures based on fault origin: customer, lower order system control/sub-control station, this system/local/distant end, or network/higher order system control/sub-control station. The process involves decision points for fault level, alarm status, and system awareness, leading to various actions like notifications, repairs, or temporary restoration.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +graph TD + subgraph Origins + O1([Origin: customer]) + O2([Origin: lower order system control/sub-control station]) + O3([Origin: this system, local end or distant end e.g. alarms]) + O4([Origin: the network or higher order system control/sub-control station]) + end + + O1 --> R1[See Recommendation M.1385 [10]] + R1 --> D1{Suggested fault on this system or at a higher level?} + D1 -- No --> N1[Notification of a channel level fault for information only] + N1 --> E1([End: ensure that the distant control/sub-control station is aware of system status]) + D1 -- Yes --> D2{Any local equipment alarms?} + D2 -- Yes --> I1[Using information received (alarms, etc.) and basic tests (e.g. loops), confirm that a fault exists and ascertain whether the problem appears to be with: +- lower order channel/system; +- local system equipment; +- higher order distant equipment. +Notify and liaise with distant end] + D2 -- No --> I1 + I1 --> A((A)) + I1 --> B((B)) + I1 --> C((C)) + I1 --> D((D)) + I1 --> E((E)) + I1 --> F((F)) + O2 --> D1 + O3 --> D3{Does report originate from the distant system control/sub-control station?} + D3 -- Yes --> F + D3 -- No --> I1 + O4 --> D4{Suggested fault on this system?} + D4 -- Yes --> F + D4 -- No --> D5{Higher order fault?} + D5 -- Yes --> R2[Await restoration/repair and liaise as appropriate] + R2 --> D6{Fault cleared?} + D6 -- No --> R3[Request for temporary restoration if appropriate] + R3 --> D6 + D6 -- Yes --> E2([End: ensure that the distant control/sub-control station is aware of system status]) + D5 -- No --> N2[Notification only (e.g. restoration of a previous fault) noted as appropriate] + N2 --> E3([End: ensure that the distant control/sub-control station is aware of system status]) + +``` + +T0403620-92/d01 + +Flowchart titled 'Actions on receipt of fault information' (Figure 1/M.1375). It details procedures based on fault origin: customer, lower order system control/sub-control station, this system/local/distant end, or network/higher order system control/sub-control station. The process involves decision points for fault level, alarm status, and system awareness, leading to various actions like notifications, repairs, or temporary restoration. + +Figure 1/M.1375 – Actions on receipt of fault information + +![Flowchart titled 'Actions on receipt of fault information' with six entry points (A-F). It details procedures for fault clearance, including liaising with customers, performing repairs, and passing faults to higher-order system operators.](007b053fe94a8348f75128a584503fd0_img.jpg) + +``` + +graph TD + A((A)) --> A1[End: inform originator close fault and ensure that the distant control/sub-control station is aware of system status] + B((B)) --> B1[Liaise with customer or lower order system control/sub-control to test the local end up to and including the channel input of this system] + B1 --> B2{Fault found?} + B2 -- No --> C1 + B2 -- Yes --> B3[Perform or arrange for check/repair as appropriate] + B3 --> B4{Fault cleared?} + B4 -- No --> B5[Further repair/analysis of local system equipment] + B5 -.-> B6[Refer to appropriate technical support group] + B4 -- Yes --> B7[End: ensure that the distant control/sub-control station is aware of system status] + C((C)) --> C1[Replace and repair as appropriate, notify and liaise with distant control/sub-control station when appropriate, ideally within 15 minutes of receipt of fault report] + D((D)) --> C1 + E((E)) --> E1{Alarms on higher order?} + E1 -- No --> D1[Where an upstream failure indication is received, allow time for clearance. Liaise with distant system control/sub-control to perform tests as appropriate] + E1 -- Yes --> E2[Pass to local higher order system operator] + F((F)) --> F_sink[ ] + C1 --> C2{Fault cleared?} + C2 -- No --> C3[Continue fault clearance. Liaise with local lower and higher order control/sub-control stations if appropriate] + C3 -.-> C4[Refer to appropriate technical support group] + C2 -- Yes --> C5[End: ensure that the distant control/sub-control station is aware of system status] + D1 --> D2{Distant end system fault (e.g. equipment)?} + D2 -- No --> D3{Data link fault?} + D3 -- No --> F_sink + D3 -- Yes --> D4[Both ends to refer fault to higher order/network control or sub-control stations] + D2 -- Yes --> D5[Await restoration/repair] + D5 --> D6{Fault cleared?} + D6 -- No --> D7[Liaise and chase periodically as appropriate] + D6 -- Yes --> D8[End: ensure that the distant control/sub-control station is aware of system status] + E2 --> E3[Pass to distant system operator] + E3 --> D5 + D4 --> D8 + +``` + +Flowchart titled 'Actions on receipt of fault information' with six entry points (A-F). It details procedures for fault clearance, including liaising with customers, performing repairs, and passing faults to higher-order system operators. + +T0403630-92/d02 + +NOTE – The fault-finding procedure outlined should be followed, as far as is possible, by lower order system control/sub-control stations prior to passing faults onto higher order system control/sub-control stations. + +**Figure 1/M.1375 (concluded) – Actions on receipt of fault information** + +### 9.4 Loopback tests + +On certain occasions, it may be possible to perform a data transmission performance test by utilizing a loopback. However, it should be appreciated that the results of such tests are not directly comparable with any previous measurements made in a single direction of transmission. + +Care must be taken to avoid the simultaneous operation of loopbacks if the system configuration is such that erroneous results would occur. Once the need for a loopback no longer exists, then care should be taken to ensure that it is removed. + +### 9.5 Test access at Digital Cross-Connect (DXC) equipment + +An increasing number of international data transmission systems are configured using Digital Cross-Connect (DXC) equipment within transmission stations (e.g. see Recommendation G.796 [22]). These equipments are used to switch faulty digital paths over to standby paths when necessary. They also often provide the capability to divert data transmission systems and circuits to test ports to which test equipment can be connected and used to measure performance and diagnose faults. + +Furthermore, this test equipment may be remotely controlled, preferably by the same management system that controls the DXC equipment. In any event, control of the two must be carefully synchronized. In some cases, simultaneous multiple access to test equipment ("remote test head") is possible by multiple operators. + +It is desirable that DXC equipment is capable of providing monitoring of selected digital paths before taking the path out of service. This allows in-service performance assessment and/or confirmation that a fault exists before breaking the path. Most DXC equipment provides both a monitor and a split and terminate functionality on the test ports. While the digital path is being monitored in-service, no interruption is experienced. Once a fault has been confirmed, the faulty path is split and the fault diagnosed. + +## 10 In-service monitoring + +On some international data transmission systems, it may be possible to assess overall performance by implementing a cyclic redundancy check within certain nominally spare bits of a frame alignment signal (e.g. CRC4 and CRC6 – see Recommendation G.706 [19]) or by monitoring an additional dedicated service channel. The system is then referred to as "structured" (or "framed"). + +The criteria for the evaluation of the Errored Second (ES) and Severely Errored Second (SES) parameters in relation to in-service performance monitoring are given in Annex B/M.2100 [14]. Where in-service monitoring is using an additional dedicated service channel, the results obtained may not reflect the true performance experienced by the customer's traffic. However, it is likely that the SES performance results will be correct. + +There is a need for further study of many issues relating to the support of in-service performance monitoring for international data transmission systems. However, degraded and unacceptable performance limit thresholds have been derived and are presented in Recommendation M.1340 (see Tables 4/M.1340 and 5/M.1340) [8]. The degraded performance limit threshold relates to a 24-hour monitoring period and the unacceptable performance limit threshold to a 15-minute monitoring period. + +The action to be taken in the event that a threshold is exceeded remains for further study. However, in general, where the unacceptable performance limit threshold is exceeded, immediate corrective action should be taken (e.g. temporary service restoration). Where the degraded performance limit threshold is exceeded, immediate corrective action may not be appropriate. However, the performance of the affected international data transmission system should be reviewed on a regular basis to establish whether a fault exists. See also 2.3/M.2120 [16] for further guidance with respect to performance limit thresholds. + +Where an international data transmission link is comprised of a number of discrete monitored link sections, the degraded and unacceptable performance limit thresholds should apply to that part of the international data transmission link that is actually monitored. In this case, the allocation for a particular monitored path element will be less than the allocation for the overall international data transmission link. + +The use of DXC equipment enables in-service observation, in the receive direction, on structured data transmission systems. For loopback observations, the agreement and cooperation of the foreign DXC authority is required. In some countries, observations via DXCs may be centralized by the TMN. + +In cases of complaints relating to intermittent faults on a leased circuit supported by a data transmission system, it may often be advisable for Network Operators/Service Providers to compare records of interruptions on the link, at DXC level. + +Comparison of regular records among Network Operators/Service Providers also provides a means of evaluating routings and thus of detecting those prone to frequent ES and SES. + +In-service monitoring may not be possible where the circuit is deemed to be transparent. + +## **11 Temporary service restoration** + +Temporary service restoration may be utilized when a network failure is localized to the international network and this is affecting circuits supported by an international data transmission system. Typical international network failures that may require the use of temporary service restoration include the loss of an undersea cable system or satellite system. + +Temporary service restoration should only be used when it is clear that normal international network restoration or repair will not be achieved in a reasonable time (see Annex D/M.1560) [13]. + +### **11.1 Mechanisms for implementing temporary service restoration** + +Two basic mechanisms have been identified as follows: + +#### **1) To utilize a dedicated restoration facility** + +The dedicated restoration facility will typically be an international data transmission system which may follow a different physical route. If both of the following criteria are met, the dedicated temporary restoration facility may be utilized: + +- a) An international network failure has occurred and it is observed that normal restoration will not be achieved in a reasonable time. +- b) A dedicated restoration facility is available. + +#### **2) To utilize temporary restoration capacity** + +The temporary restoration capacity would typically be found within other international data transmission systems that connect to the same destination, which may follow a different physical route within the international network. If each of the following criteria are met, the temporary restoration capacity may be utilized: + +- a) An international network failure has occurred and it is observed that normal restoration will not be achieved in a reasonable time. +- b) Any dedicated restoration facility that may have been provided is not available. +- c) Spare restoration capacity is available. + +If the Network Operators/Service Providers involved have the technical capability and operating procedures to support the temporary switching of channels between international data transmission systems, reference should be made to clause 10/M.1385 [10]. + +### **11.2 Time to restore service** + +Network Operators/Service Providers should take into account the urgency for restoration for each particular international data transmission system as mentioned in the preliminary exchange of information for its provision (see Recommendations M.1045 [6] and M.1400 [11]). Where time to restore service seems to be unacceptable, Network Operators/Service Providers shall invoke the agreed escalation procedure (see Recommendation M.1560 [13]). + +### **11.3 Restoration procedure** + +The following outline procedure is for guidance only. Detailed operating procedures will need to be agreed between the Network Operators/Service Providers involved taking account of the network infrastructure that is available. This may include the use of a TMN X interface. + +When an international data transmission system failure occurs and the basic restoration criteria have been met (see 11.1 above), the Network Operators/Service Providers involved will confirm that some form of temporary service restoration is to be used and agree how this is to be achieved. Service can be restored using the following procedure: + +- a) Confirm that the international data transmission link is faulty. +- b) Confirm that both Network Operators/Service Providers agree that the normal restoration time is unreasonable. +- c) Implement restoration switching. +- d) Confirm that the affected international data transmission system has been successfully restored. + +### **11.4 Returning to normal routing** + +When service can be restored via its normal route, this should be done as soon as practically possible, or as a planned outage (see Recommendation M.1540 [12]). + +### **11.5 Information that should be exchanged** + +Dependent upon the proposed restoration method that is to be used, Network Operators/Service Providers should ensure that suitable preliminary information has been exchanged (e.g. designations and routings for any international data transmission systems that may be used for dedicated or temporary service restoration). + +## **12 Automatic rerouting of international data transmission links** + +For priority links, Network Operators/Service Providers may agree to fit the links with automatic rerouting switches, through requisite monitoring systems. These may be 1 + 1 or n + 1 rerouting systems. + +For leased circuits supported on such links, the number of Consecutive Severely Errored Seconds (CSES) due to changeover of the data transmission system should be minimized in order to fulfil the requirements of the supported services (see clause 5/M.1385 [10]). + +## **13 Precautions to be taken in the use of DXCs** + +DXC equipment types vary. Some handle cross-connecting of low-speed (below primary rate) signals and have primary rate digital access ports. These are sometimes called "1/0 DXCs". Depending on the bit rate of the digital path to be monitored and tested, one or more timeslots of the test port are used for the signal. Other types of DXC equipment are used for higher bit rate signals, for example, cross-connecting primary rate digital paths and fitted with third level digital access ports. These are sometimes called "3/1 DXCs". Many SDH DXCs have considerably more flexibility. For further information on cross-connects, see Recommendations G.796 [22] for PDH and G.783 [21] for SDH. + +For an international data transmission link, the DXC is typically the routing point, since it fulfils a switching function. The DXC must thus offer a very high degree of availability. + +If a serious fault should nevertheless occur on a DXC, the Network Operator/Service Provider should have available sufficient alternative arrangements to relieve the faulty unit. At changeover, the databases may have to be loaded and it should be checked whether the software version is compatible if the DXC is a back-up for another. + +## **14      Planned maintenance** + +In cases of planned maintenance on the Network Operator's/Service Provider's installations – transmission equipment, power equipment, cabling, etc. – which would cause or risk some performance degradation or unavailability of the international data transmission system, Recommendation M.1540 [12] procedures should be followed. + +![A diagram consisting of four dashed rectangular boxes arranged in a cross-like pattern.](ac852a162572ca8a8c8478c49b571af5_img.jpg) + +The image shows a diagram composed of four dashed rectangular boxes. Two boxes are positioned vertically in the center, one above the other. A third, wider box is positioned horizontally, centered vertically and overlapping the two vertical boxes. A fourth box is located in the central space between the top and bottom vertical boxes, also overlapping with the horizontal box. The overall shape resembles a cross or a stylized letter 'H' with dashed outlines. + +A diagram consisting of four dashed rectangular boxes arranged in a cross-like pattern. + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.1380-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.1380-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..03d8e21cf7ec349b6b66f3c98ecc4474b493fb13 --- /dev/null +++ b/marked/M/T-REC-M.1380-200002-I_PDF-E/raw.md @@ -0,0 +1,324 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking across it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1380** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**Bringing-into-service of international leased +circuits that are supported by international data +transmission systems** + +ITU-T Recommendation M.1380 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Bringing-into-service of international leased circuits that are supported by international data transmission systems** + +## **Summary** + +This ITU-T Recommendation is only applicable to international leased circuits that are supported by a data transmission system. The requirements described in this ITU-T Recommendation should ensure that an international leased circuit meets performance limits and is fully tested prior to introduction into service. + +The Bringing-Into-Service tests described in this ITU-T Recommendation should ideally include periods of normal industrial activity to be representative of typical network conditions. This ITU-T Recommendation has been developed to be consistent with ITU-T Recommendation M.1370 that describes the Bringing-Into-Service of international data transmission systems. + +ITU-T Recommendation M.1385 covers maintenance issues for international leased circuits that are supported by a data transmission system maintained in accordance with ITU-T Recommendation M.1375. + +This ITU-T Recommendation addresses the Bringing-Into-Service requirements of leased circuits with a PDH digital presentation at Customers' premises. Another ITU-T Recommendation is being developed for Bringing-Into-Service and Maintenance procedures for SDH leased circuits. + +For leased circuits with an analogue presentation, the Bringing-Into-Service procedures given in ITU-T Recommendation M.1050 apply, with performance achievement in accordance with ITU-T Recommendations M.1020, M.1025 or M.1040 as appropriate. + +## **Source** + +ITU-T Recommendation M.1380 was revised by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000. + +## **Keywords** + +Bringing-Into-Service, exchange of Information, in-service monitoring, international data transmission system, international leased circuit, testing of performance objectives. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|---------------------------------------------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 3 | +| 4 | Abbreviations..... | 4 | +| 5 | Performance limits and objectives..... | 4 | +| 6 | Preliminary exchange of information ..... | 4 | +| 7 | Bringing-Into-Service procedures..... | 5 | +| 7.1 | National circuit portions ..... | 5 | +| 7.2 | International circuit portions..... | 5 | +| 7.2.1 | Bringing-Into-Service using an alternative international link ..... | 6 | +| 7.3 | End-to-end test..... | 6 | +| 7.3.1 | Alternative end-to-end test ..... | 6 | + +# **Bringing-into-service of international leased circuits that are supported by international data transmission systems** + +# **1 Scope** + +This ITU-T Recommendation describes the Bringing-Into-Service (BIS) procedures1 for an international leased circuit that is supported by a data transmission system. The circuit will have a digital presentation, normally in the PDH domain, at the Customer's premises, but in some cases may be terminated in the SDH domain. This case of mixed PDH/SDH leased circuit needs further study. The provisions of this ITU-T Recommendation should be considered in conjunction with those of ITU-T Recommendation M.1370 [19] for international data transmission systems. + +This ITU-T Recommendation does not cover the BIS requirements of leased circuits with an analogue presentation at the Customer's premises. Such leased circuits are described in ITU-T Recommendation M.1050 [16]. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.701 (1993), *Vocabulary of digital transmission and multiplexing, and Pulse Code Modulation (PCM) terms.* +- [2] ITU-T Recommendation G.703 (1998), *Physical/electrical characteristics of hierarchical digital interfaces.* +- [3] CCITT Recommendation G.802 (1988), *Interworking between networks based on different digital hierarchies and speech encoding laws.* +- [4] ITU-T Recommendation G.823 (2000), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy.* +- [5] ITU-T Recommendation G.824 (2000), *The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy.* +- [6] ITU-T Recommendation G.825 (2000), *The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH).* +- [7] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [8] CCITT Recommendation M.80 (1988), *Control stations.* +- [9] CCITT Recommendation M.90 (1988), *Sub-control stations.* +- [10] CCITT Recommendation M.1012 (1988), *Circuit control stations for leased and special circuits.* + +--- + +1 The BIS procedures include the setting up of the leased circuit, the exchange of information, the setting of performance limits and the testing against those performance limits. + +- [11] CCITT Recommendation M.1013 (1988), *Sub-control station for leased and special circuits.* +- [12] ITU-T Recommendation M.1020 (1993), *Characteristics of special quality international leased circuits with special bandwidth conditioning.* +- [13] ITU-T Recommendation M.1025 (1993), *Characteristics of special quality international leased circuits with basic bandwidth conditioning.* +- [14] CCITT Recommendation M.1040 (1988), *Characteristics of ordinary quality international leased circuits.* +- [15] ITU-T Recommendation M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [16] ITU-T Recommendation M.1050 (1993), *Lining up an international point-to-point leased circuit.* +- [17] ITU-T Recommendation M.1300 (1997), *Maintenance of international data transmission systems operating in the range 2.4 kbit/s to 140 Mbit/s.* +- [18] ITU-T Recommendation M.1340 (1996), *Performance objectives, allocations and limits for international data transmission links and systems.* +- [19] ITU-T Recommendation M.1370 (1998), *Bringing-into-service of international data transmission systems.* +- [20] ITU-T Recommendation M.1375 (1998), *Maintenance of international data transmission systems.* +- [21] ITU-T Recommendation M.1385 (2000), *Maintenance of international leased circuits that are supported by international data transmission systems.* +- [22] ITU-T Recommendation M.1400 (1997), *Designations for international networks.* +- [23] CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network.* +- [24] ITU-T Recommendation M.1530 (1999), *Network maintenance information.* +- [25] ITU-T Recommendation M.1535 (1996), *Principles for maintenance information to be exchanged at customer contact point (MICC).* +- [26] ITU-T Recommendation M.1537 (1997), *Definition of maintenance information to be exchanged at customer contact point (MICC).* +- [27] ITU-T Recommendation M.1539 (1999), *Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC).* +- [28] ITU-T Recommendation M.1540 (1994), *Exchange of information for planned outages of transmission systems.* +- [29] CCITT Recommendation M.1560 (1992), *Escalation procedure for international leased circuits.* +- [30] ITU-T Recommendation M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: leased circuit services.* +- [31] ITU-T Recommendation V.10 (1993), *Electrical characteristics for unbalanced double-current interchange circuits operating at data signalling rates nominally up to 100 kbit/s (also numbered as X.26).* + +- [32] ITU-T Recommendation V.11 (1996), *Electrical characteristics for balanced double-current interchange circuits operating at data signalling rates up to 10 Mbit/s (also published as X.27)*. +- [33] ITU-T Recommendation V.12 (1995), *Electrical characteristics for balanced double-current interchange circuits for interfaces with data signalling rates up to 52 Mbit/s*. +- [34] ITU-T Recommendation V.24 (2000), *List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)*. +- [35] ITU-T Recommendation V.28 (1993), *Electrical characteristics for unbalanced double-current interchange circuits*. +- [36] ITU-T Recommendation V.38 (1996), *A 48/56/64 kbit/s data circuit-terminating equipment standardized for use on digital point-to-point leased circuits*. +- [37] ITU-T Recommendation V.110 (2000), *Support by an ISDN of data terminal equipments with V-series type interfaces*. +- [38] ITU-T Recommendation V.120 (1996), *Support by an ISDN of data terminal equipment with V-series type interfaces with provision for statistical multiplexing*. +- [39] ITU-T Recommendation V.300 (1999), *A 128 (144) kbit/s data circuit-terminating equipment standardized for use on digital point-to-point leased circuits*. +- [40] CCITT Recommendation X.21 (1992), *Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchronous operation on public data networks*. +- [41] CCITT Recommendation X.24 (1988), *List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) on public data networks*. + +# 3 Terms and definitions + +ITU-T Recommendation M.1300 [17] provides general descriptions of international data transmission systems relevant to this ITU-T Recommendation. Terminology and definitions relating to this ITU-T Recommendation are provided in ITU-T Recommendations G.701 [1] and M.60 [7]. For the purposes of this ITU-T Recommendation, the following definitions of an international digital leased circuit and Service Level Agreement (SLA)/Contract apply: + +**3.1 An international digital leased circuit:** Is the digital path between two Network Terminating Equipments (NTEs). The digital leased circuit may be bidirectional or unidirectional and its end points are at the boundaries between the Network Operator/Service Provider and the Customer. The NTEs may be owned by the Network Operator/Service Provider or owned by the Customer. + +**3.2 An SLA/Contract:** Is a set of appropriate procedures and targets formally or informally agreed between Network Operators/Service Providers or between Network Operators/Service Providers and Customers, in order to achieve and maintain specified Quality of Service (QoS) in accordance with ITU (ITU-T and ITU-R) Recommendations. The SLA may be an integral part of the Contract. These procedures and targets are related to specific circuit/service availability, error performance, Ready for Service (RFS) date, Mean Time Between Failures (MTBF), Mean Time to Restore Service (MTRS), Mean Time to Repair (MTTR). + +# 4 Abbreviations + +This ITU-T Recommendation uses the following abbreviations: + +| | | +|------|------------------------------------| +| BIS | Bringing-Into-Service | +| DCE | Data Circuit-terminating Equipment | +| DTE | Data Terminal Equipment | +| ES | Errored Second | +| MTBF | Mean Time Between Failures | +| MTRS | Mean Time to Restore Service | +| MTTR | Mean Time to Repair | +| NTE | Network Terminating Equipment | +| PDH | Plesiochronous Digital Hierarchy | +| QoS | Quality of Service | +| RFS | Ready for Service | +| SDH | Synchronous Digital Hierarchy | +| SES | Severely Errored Second | +| SLA | Service Level Agreement | + +# 5 Performance limits and objectives + +Performance limits for the international portion should be consistent with those given in ITU-T Recommendation M.1340 [18]. For all performance tests described in this ITU-T Recommendation, the Errored Second (ES) and Severely Errored Second (SES) limits should be met simultaneously for the test result to be considered acceptable. + +For the national circuit portions, limits will be set independently by the Network Operators/Service Providers involved taking account of national conditions and the need to preserve overall end-to-end performance. Performance achievement will be dependent upon the performance and topology of the local transmission facilities. To maintain consistency with ITU-T Recommendation M.1340 [18], Network Operators/Service Providers should use ES and SES events to measure performance achievement. + +The possible development and application of performance objectives for transmission availability, delay and jitter is left for further study. + +All test results obtained during BIS tests should be retained for possible future reference during maintenance activities. + +# 6 Preliminary exchange of information + +Consideration should be given to information that has already been exchanged for the international data transmission system that will support the service. See clause 2/M.1370 [19]. + +Circuit information should be exchanged in accordance with ITU-T Recommendation M.1045 [15]. In addition, Network Operators/Service Providers may find that it is advantageous to exchange the following information: + +- details of any special maintenance or fault reporting arrangements that have been requested (e.g. single end fault reporting, SLA/Contract details); + +- contact details for, and operational arrangements with, any additional Network Operators/Service Providers that are involved with the provision of service (e.g. Network Operators/Service Providers that provide a transit routing facility); +- precise details of the interface presentation and functionality at the Customer's premises (this should ideally be in accordance with existing ITU-T Recommendations, e.g. G.703 [2], V.10 [31], V.11 [32], V.12 [33], V.24 [34], V.28 [35], V.38 [36], V.110 [37], V.120 [38], V.300 [39], X.21 [40] and X.24 [41]); +- performance limits for the national circuit portions (see below) and for the overall circuit; +- confirmation of the data rate presented at the Customer interface where this is different to the data rate extended internationally (e.g. application of ITU-T Recommendation G.802 [3] for the support of 1544 kbit/s circuits within a 2048 kbit/s transmission hierarchy); +- details of any equipment loopback capabilities that may be available; +- details of escalation arrangements and contacts that may be used to overcome operational difficulties (see ITU-T Recommendations M.1535 [25], M.1537 [26], M.1539 [27] and M.1560 [29]). + +Network Operators/Service Providers should confirm that the information exchanged is consistent and that the circuit will be able to support the service. + +The information that has been exchanged, as detailed above, should be retained for future reference. + +# 7 Bringing-Into-Service procedures + +It should be noted that neither a 24-hour nor a 2-hour test duration can be expected to give a particularly reliable indication of transmission performance due to the statistics of transmission media over such a short period. See 5.4/M.1340 [18] for further guidance. National circuit portions and international circuit portions may be set up and tested simultaneously or consecutively. However, careful harmonization of these procedures is required to ensure overall end-to-end performance is acceptable. + +## 7.1 National circuit portions + +Before setting up the national circuit portions, suitable performance limits for the national circuit portions should be developed and exchanged between the Network Operators/Service Providers involved, always ensuring that the overall end-to-end performance can be achieved. + +## 7.2 International circuit portions + +If in-service performance monitoring is available, and the error performance of the supporting data transmission system is acceptable, all new circuits should be tested for 15 minutes. In the case where a number of circuits using the same data transmission system are brought into service at the same time, and in-service performance monitoring is not available, the first circuit should be tested for 24 hours, and the remaining circuits could be tested for 15 minutes each. Any portions of the circuit, which are not supported by the data transmission system, should be tested for 24 hours. + +The performance objectives given in clause 7/M.1340 [18] should be met. Where there is little confidence regarding the capabilities of a particular international data transmission system, or where the short duration test objectives were not met, a 24-hour test should be performed using the limits that were originally developed to test the international data transmission system (see clause 3/M.1370 [19]). + +In the event that the 24-hour limits are not met, Network Operators/Service Providers should agree to an appropriate course of action (see ITU-T Recommendation M.1375 [20] for guidance). + +Where the international circuit portion extends significantly beyond the channel interfaces of a particular international data transmission system (e.g. where a transit routing involves the interconnection of two international data transmission systems) additional tests may be required. Network Operators/Service Providers should ensure that all parts of the international circuit portion are fully tested. Suitable additional limits should be agreed between the Network Operators/Service Providers involved. Consistency with ITU-T Recommendation M.1340 [18] should be sought wherever possible. + +### **7.2.1 Bringing-Into-Service using an alternative international link** + +If any portion of the link, which would normally be used to carry the international leased circuit, is restored onto an alternative route before BIS testing is commenced, or during BIS testing, then testing may proceed, or continue, if the following three criteria are met: + +- 1) the performance of the alternative link is known to be acceptable; and +- 2) the alternative link uses the same transmission media as the original link; and +- 3) the length of the alternative link is not substantially different from the original link. + +If these criteria are not met, then testing should be postponed, or halted, until the original link is returned to service. + +If a single unavailability event occurs during the BIS test, and the cause of this event is precisely known and not recurrent, then this event should be ignored in the test results. + +## **7.3 End-to-end test** + +It will normally be advantageous to perform an end-to-end test to confirm overall integrity and stability. A 24-hour test duration is recommended. Test limits should include allowances for the international and two national circuit portions. Network Operators/Service Providers should pay particular attention to highlighting any problems that may be associated with the interworking of separately timed networks, especially for the first circuit provision that uses a particular equipment configuration. In particular, the jitter/wander performance requirements of ITU-T Recommendations G.823 [4], G.824 [5] and G.825 [6] should be respected as appropriate to the leased circuit and supporting transmission network. + +Dependent upon the loopback capabilities provided by the network terminating equipments at the Customer's premises, it may be possible to perform end-to-end tests from intermediate points within the network (e.g. at Terminal International Centres). + +Where loop tests are employed, it is proposed that no special additional performance allowance is made (i.e. doubling of limits is not recommended). + +### **7.3.1 Alternative end-to-end test** + +If Network Operators/Service Providers agree, based upon experience of similar network conditions, and in-service performance monitoring is available on the entire international data transmission system, a 2-hour end-to-end test may be performed. In this case, the BIS procedure is as follows: + +- 1) The national circuit portion is brought-into-service according to existing national procedures. +- 2) No international circuit portion test is carried out, as this portion has already been tested according to the procedures of ITU-T Recommendation M.1370 [19], and in-service performance monitoring is being used to ensure that the performance of the data transmission system is acceptable. + +- 3) An end-to-end test of two hours is performed to verify the cross-connection capabilities of the digital cross-connect equipment. This test may be performed to a loopback at one or both ends. The performance objective for this test is given in Table 2/M.1340 [18]. There should be no clock slips or periods of unavailability during this test. If these conditions cannot be met, then the 24-hour test, as described above, should be carried out. + +As mentioned above in 7.3, Network Operators/Service Providers should pay particular attention to highlighting any problems that may be associated with the interworking of separately timed networks, as these may not be evident from a 2-hour test. + +# **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1385-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.1385-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c3a48c2fff19f902923cad0641f43adee77daef5 --- /dev/null +++ b/marked/M/T-REC-M.1385-200002-I_PDF-E/raw.md @@ -0,0 +1,383 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1385** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International data transmission systems + +--- + +**Maintenance of international leased circuits that +are supported by international data +transmission systems** + +ITU-T Recommendation M.1385 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +### **Maintenance of international leased circuits that are supported by international data transmission systems** + +## **Summary** + +This ITU-T Recommendation is only applicable to international leased circuits that are supported by a data transmission system. The requirements described in this ITU-T Recommendation should ensure that an international leased circuit meets performance limits and is fully tested prior to restoration into service after a fault. + +The Maintenance tests described in this ITU-T Recommendation should ideally include periods of normal industrial activity to be representative of typical network conditions. This ITU-T Recommendation has been developed to be consistent with ITU-T Recommendation M.1375 that describes the Maintenance of international data transmission systems. + +ITU-T Recommendation M.1380 covers Bringing-Into-Service issues for international leased circuits that are supported by a data transmission system. + +This ITU-T Recommendation addresses the Maintenance requirements of leased circuits with a PDH digital presentation at the Customer's premises. Another ITU-T Recommendation is being developed for Bringing-Into-Service and Maintenance procedures for SDH leased circuits. + +For leased circuits with an analogue presentation, the Maintenance procedures given in ITU-T Recommendation M.1060 apply, with performance achievement in accordance with ITU-T Recommendations M.1020, M.1025 or M.1040 as appropriate. + +## **Source** + +ITU-T Recommendation M.1385 was revised by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000. + +## **Keywords** + +Exchange of information, fault localization, fault reporting procedure, in-service monitoring, international data transmission system, international leased circuit, maintenance records, maintenance tests, planned maintenance, restoration procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this publication, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the publication development process. + +As of the date of approval of this publication, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this publication. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|---------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Performance limits and objectives..... | 3 | +| 6 Maintenance records ..... | 3 | +| 7 Fault reporting procedures ..... | 4 | +| 7.1 Control and sub-control status ..... | 4 | +| 7.2 Initial reception of a fault report ..... | 4 | +| 8 Fault localization..... | 5 | +| 9 Maintenance tests..... | 5 | +| 10 Temporary service restoration procedures..... | 6 | +| 10.1 Mechanisms for implementing temporary service restoration..... | 6 | +| 10.2 Time to restore service..... | 7 | +| 10.3 Restoration procedure ..... | 7 | +| 10.4 Returning to normal routing..... | 7 | +| 10.5 Information that should be exchanged ..... | 7 | +| 11 Planned maintenance ..... | 8 | + +## **Maintenance of international leased circuits that are supported by international data transmission systems** + +## **1 Scope** + +This ITU-T Recommendation describes the Maintenance procedures for an international leased circuit that is supported by a data transmission system. The circuit will have a digital presentation, normally in the PDH domain, at the Customer's premises, but in some cases may be terminated in the SDH domain. This case of mixed PDH/SDH leased circuit needs further study. The provisions of this ITU-T Recommendation should be considered in conjunction with those of ITU-T Recommendation M.1375 [12] for international data transmission systems + +This ITU-T Recommendation does not cover the Maintenance requirements of leased circuits with an analogue presentation at the Customer's premises. Such leased circuits are described in ITU-T Recommendation M.1060 [8]. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.701 (1993), *Vocabulary of digital transmission and multiplexing, and Pulse Code Modulation (PCM) terms.* +- [2] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [3] CCITT Recommendation M.80 (1988), *Control stations.* +- [4] CCITT Recommendation M.90 (1988), *Sub-control stations.* +- [5] CCITT Recommendation M.1012 (1988), *Circuit control stations for leased and special circuits.* +- [6] CCITT Recommendation M.1013 (1988), *Sub-control station for leased and special circuits.* +- [7] ITU-T Recommendation M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [8] CCITT Recommendation M.1060 (1988), *Maintenance of international leased circuits.* +- [9] ITU-T Recommendation M.1300 (1997), *Maintenance of International data transmission systems operating in the range 2.4 kbit/s to 140 Mbit/s.* +- [10] ITU-T Recommendation M.1340 (1996), *Performance objectives, allocations and limits for international data transmission links and systems.* +- [11] ITU-T Recommendation M.1370 (1998), *Bringing-into-service of international data transmission systems.* +- [12] ITU-T Recommendation M.1375 (1998), *Maintenance of international data transmission systems.* + +- [13] ITU-T Recommendation M.1380 (2000), *Bringing-into-service of international leased circuits that are supported by international data transmission systems.* +- [14] ITU-T Recommendation M.1400 (1997), *Designations for international networks.* +- [15] CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network.* +- [16] ITU-T Recommendation M.1530 (1999), *Network maintenance information.* +- [17] ITU-T Recommendation M.1535 (1996), *Principles for maintenance information to be exchanged at customer contact point (MICC).* +- [18] ITU-T Recommendation M.1537 (1997), *Definition of maintenance information to be exchanged at customer contact point (MICC).* +- [19] ITU-T Recommendation M.1539 (1999), *Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC).* +- [20] ITU-T Recommendation M.1540 (1994), *Exchange of information for planned outages of transmission systems.* +- [21] CCITT Recommendation M.1560 (1992), *Escalation procedure for international leased circuits.* + +## 3 Terms and definitions + +ITU-T Recommendation M.1300 [9] provides general descriptions of international data transmission systems. Terminology and definitions relating to this ITU-T Recommendation are provided in ITU-T Recommendations G.701 [1] and M.60 [2]. For the purposes of this ITU-T Recommendation, the following definitions of an international digital leased circuit and Service Level Agreement (SLA)/Contract apply: + +**3.1** An **international digital leased circuit**: Is the digital path between two Network Terminating Equipments (NTEs). The digital leased circuit may be bidirectional or unidirectional and its end points are at the boundaries between the Network Operator/Service Provider and the Customer. The NTEs may be owned by the Network Operator/Service Provider or owned by the Customer. + +**3.2** An **SLA/Contract**: Is a set of appropriate procedures and targets formally or informally agreed between Network Operators/Service Providers or between Network Operators/Service Providers and Customers, in order to achieve and maintain specified Quality of Service (QoS) in accordance with ITU (ITU-T and ITU-R Recommendations). The SLA may be an integral part of the Contract. These procedures and targets are related to specific circuit/service availability, error performance, Ready for Service (RFS) date, Mean Time Between Failures (MTBF), Mean Time to Restore Service (MTRS), Mean Time to Repair (MTTR). + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|-------------------------------------| +| BIS | Bringing-Into-Service | +| CSES | Consecutive Severely Errored Second | +| ES | Errored Second | +| ISM | In-Service Monitoring | +| MTBF | Mean Time Between Failures | + +| | | +|------|---------------------------------------| +| MTRS | Mean Time to Restore Service | +| MTTR | Mean Time To Repair | +| NTE | Network Terminating Equipment | +| PCM | Pulse Code Modulation | +| PDH | Plesiochronous Digital Hierarchy | +| RFS | Ready for Service | +| SDH | Synchronous Digital Hierarchy | +| SEP | Severely Errored Period | +| SES | Severely Errored Second | +| SLA | Service Level Agreement | +| TMN | Telecommunications Management Network | +| UTC | Co-ordinated Universal Time | + +## 5 Performance limits and objectives + +Performance limits should be consistent with those used during Bringing-Into-Service (see ITU-T Recommendation M.1380 [13]). For short duration tests the limits given in clause 7/M.1340 [10] are appropriate. For all performance tests described in this ITU-T Recommendation, the Errored Second (ES) and Severely Errored Second (SES) limits should be met simultaneously for the test result to be considered acceptable. + +Network Operators/Service Providers should be aware that periods of Consecutive Severely Errored Seconds (CSES), of between 3 and 9 seconds, called a "Severely Errored Period (SEP)", can have a severe impact on some Customers' leased circuit applications. CSESs are critical for some Customers' leased circuit applications because they require the application to be restarted completely, since the installation's own recovery system is no longer sufficient to cover the circuit interruption time. + +Performance limits and objectives for SEPs are for further study. + +## 6 Maintenance records + +Network Operators/Service Providers should ensure that up-to-date information is held on file to assist maintenance activities. Clause 6/M.1370 [11] and clause 6/M.1380 [13] provide details of information that should be available. In addition, a record should be kept of any particular maintenance agreement with the Customer, including for example SLA (Service Level Agreement). See also ITU-T Recommendations M.1510 [15], M.1530 [16], M.1535 [17], M.1537 [18] and M.1539 [19] for further information. Maintenance staff should refer to such agreements when dealing with a fault reported by the Customer. + +During maintenance operations, reference should be made to previous test results that are applicable to the circuit under test. Original BIS test results should be available for all leased circuits. + +Network Operators/Service Providers should also keep a log of circuit interruptions, over an adequate period, with a view to meeting any claims from Customers. + +## 7 Fault reporting procedures + +## 7.1 Control and sub-control status + +A dual control or a control and sub-control relationship will have been agreed at the BIS stage. See clause 10/M.1300 [9], item ix) of clause 6/M.1370 [11] and 7.1/M.1375 [12]. + +Where a control and sub-control relationship exists, responsibilities will be as described in ITU-T Recommendations M.80 [3], M.90 [4], M.1012 [5] and M.1013 [6]. + +Where a dual control relationship has been established, Network Operators/Service Providers should have agreed an effective mechanism for coordinating maintenance activities. Under this arrangement, to avoid confusion, it is essential that the terminal stations inform each other of maintenance activities as rapidly as possible, in accordance with the performance agreed within the SLA/Contract, (see also ITU-T Recommendations M.1510 [15], M.1530 [16], M.1535 [17], M.1537 [18] and M.1539 [19]). + +It is possible for a third-party centre to be designated as the control station. In this situation the leased circuit may not be routed via this centre, nor need this centre be situated in a terminal or transit country of the circuit. An example is when a "one-stop maintenance" type arrangement is set up. + +### 7.2 Initial reception of a fault report + +In general, fault information relating to an international leased circuit can originate from a number of sources: + +- a Customer (due to the failure or degraded performance of the circuit); +- the Network Operator providing the circuit (due to the failure or degraded performance of the network supporting the circuit); +- a connecting Network Operator providing part of the circuit (due to the failure or degraded performance of the network); +- a third-party centre, as described in 7.1 above. + +It is assumed that the Customer has carried out the following requisite checks to determine that the fault stems from the leased circuit for which the Network Operator/Service Provider is responsible: + +- results from the application's monitoring and control system; +- information from the Network Operator/Service Provider's TMN system, if available. + +When fault information is received (especially a fault report from a Customer), the following information should be obtained:1 + +- name, title and contact details for the person reporting the fault; +- the Customer identifier; +- time of fault report, recorded in UTC; +- international designation of the faulty circuit (see ITU-T Recommendation M.1400 [14]); +- symptoms of the fault and if possible, the probable cause; +- the time the fault was first observed, recorded in UTC; +- any associated information that may assist with fault clearance. + +--- + +1 Some Network Operator/Service Providers have introduced computerized documentation and exchange of work orders and set up a Leased Circuits "help-desk", which considerably facilitates operations. + +The Customer should be given a fault reference, which can be used in future communications. They may also wish to know: + +- where the fault is located; +- the nature of the fault; +- above all, when the circuit will be restored, either by fault rectification or by restoration. + +Prior to undertaking corrective maintenance (for example loop-tests), the Customer must be asked to give permission for the circuit to be withdrawn from service. + +Following corrective maintenance, the Customer should be asked to confirm that their application is functioning correctly. + +## **8 Fault localization** + +It may be useful to reference Figure 1/M.1375 [12] for guidance with fault localization. TMN data, which may be available at various locations within the Network Operator/Service Provider's network, may be used to assist with fault localization. + +Initial localization should seek to establish whether a fault exists and to determine if it is located within the Customer's premises, the national circuit portion or elsewhere. The use of the following information may assist: + +- whether the fault is intermittent or permanent; +- network alarm information; +- performance management information obtained from the network; +- results of the tests up to the Customer connection point, i.e. up to the point where the Network Operator/Service Provider is responsible. + +Where a fault is localized outside of the national circuit portion (i.e. within the international portion or distant national portion), it should be referred to a fault reporting point that has responsibility for international maintenance activities. This will typically be the fault reporting point that has responsibility for the international data transmission system. + +When a fault is referred to another fault reporting point, the information given in 7.2 above should be exchanged. Further localization should seek to identify the faulty element as quickly as possible. Where fault localization (or confirmation of it) is not achieved in a time consistent with the time to remove the fault or restore the circuit as specified in the SLA/Contract, Network Operators/Service Providers shall invoke the agreed escalation procedure (see ITU-T Recommendation M.1560 [21]) to assist progress. + +## **9 Maintenance tests** + +For maintenance intervention tests, the circuit shall only be withdrawn from service with the Customer's agreement, unless the circuit is completely interrupted. The use of In-Service Monitoring (ISM) is thus highly advisable. Maintenance tests should be kept as short as possible to avoid significantly extending the out-of-service time. + +Customer service may be improved by using 24-hour "help desks" and TMN facilities in order to schedule tests from a central location. Information about the fault condition detected, and the countermeasures planned, should be given promptly to the Customer, in order to respect any contractual commitments. + +Any loopback facilities that may be available should be used when appropriate. Care must be taken to avoid the simultaneous operation of multiple loopbacks on a particular circuit. Once the need for a loopback no longer exists, then care should be taken to ensure that it is removed. + +If both Network Operators have compatible equipment, then it may be possible to test the end-to-end continuity of a digital leased circuit. This may be possible using the TMN to apply a loopback condition. However this type of testing requires the agreement of the Customer, since their circuit cannot be used at that time. + +Where an ISM capability is available for in-service observation of the circuit signal, then it should be used to assist maintenance operations. It should be noted that, for more extensive measurements involving intrusive testing, the circuit will be interrupted. + +The duration of maintenance intervention tests will be dependent upon the nature of the fault report that has been received. + +- 1) Where the circuit has a failure, a short test of basic integrity should be performed. See clause 7/M.1340 [10] for suitable limits. +- 2) Where there has been an overall degradation of service, but that the circuit is not interrupted, a longer duration test will be appropriate. Network Operators/Service Providers should agree a suitable test date and time with the Customer. The Customer may wish to retain access to the circuit until a more convenient time when a substantial out-of-service period may be more tolerable. When a 24-hour test is performed, Network Operators/Service Providers should use the same limits that were developed for initial BIS tests (see ITU-T Recommendation M.1380 [13]). +- 3) For a repetitive fault, or a fault requiring special investigation, a longer duration test, as described above, should be used. Reference can also be made to the fault history, performance information from an ISM system, circuit topology, and the Customer's application to determine the cause of the repetitive fault. + +In all cases, returning-to-service tests should be of a duration that is appropriate to the nature of fault that has been cleared. Where a fault had caused a general degradation of service, a returning-to-service test with a short duration (e.g. 15 minutes) may not be appropriate and a longer-term test (e.g. 1 hour or 24 hours) should be used. + +## **10 Temporary service restoration procedures** + +Temporary service restoration may be used when a network failure is localized to either the national or the international network, and this is affecting circuits supported by a data transmission system. Typical international network failures that may require the use of temporary service restoration include the loss of an undersea cable system or satellite system. + +Temporary service restoration should only be used when it is clear that international network restoration or repair will not be achieved in a reasonable time (see Annex D/M.1560 [21]). + +### **10.1 Mechanisms for implementing temporary service restoration** + +Two basic mechanisms have been identified as follows: + +- 1) To use a dedicated restoration facility: + +The dedicated restoration facility for the circuit will typically be via a data transmission system which may follow a different physical route. If both of the following criteria are met, the dedicated restoration facility may be used: + +- a) a network failure has occurred and it is observed that restoration will not be achieved in a time consistent with the SLA/Contract; and +- b) a dedicated restoration facility is available. + +#### 2) To use temporary restoration capacity: + +The temporary restoration capacity would typically be found within other data transmission systems that connect to the same destination, which may follow a different physical route within the network. If each of the following criteria is met, the temporary restoration capacity may be used: + +- a) a network failure has occurred and it is observed that restoration will not be achieved in a time consistent with the SLA/Contract; and +- b) any dedicated restoration facility that may have been provided is not available; and +- c) spare restoration capacity (at the channel level) is available; +- d) the Network Operators/Service Providers involved have the technical capability and operating procedures to support the temporary switching of channels between data transmission systems. + +## **10.2 Time to restore service** + +Network Operators/Service Providers should take into account the urgency for restoration of leased circuits within each particular data transmission system as mentioned in the preliminary exchange of information for its provision (see ITU-T Recommendations M.1045 [7] and M.1400 [14]). Where time to restore service seems to be unacceptable in accordance with the SLA/Contract, Network Operators/Service Providers shall invoke the agreed escalation procedure (see ITU-T Recommendation M.1560 [21]). + +### **10.3 Restoration procedure** + +The following outline procedure is for guidance only. Detailed operating procedures will need to be agreed between the Network Operators/Service Providers involved, taking account of the network infrastructure that is available. This may include the use of a TMN X-interface. + +When a data transmission system failure occurs and the basic restoration criteria have been met (see 10.1 above), the Network Operators/Service Providers involved will confirm that some form of temporary service restoration is to be used and agree how this is to be achieved. Service can be restored using the following procedure: + +- a) confirm that the data transmission link is faulty; +- b) confirm that both Network Operators/Service Providers agree that the restoration time is inconsistent with the SLA/Contract; +- c) implement recovery mechanisms; +- d) confirm with the Customer that the affected leased circuits have been successfully restored and record the time of restoration in UTC. + +### **10.4 Returning to normal routing** + +When service can be restored via its normal route, this should be done as soon as practically possible, with agreement from the Customer in accordance with the terms of the SLA/Contract, or as a planned outage (see Recommendation ITU-T M.1540 [20]). + +### **10.5 Information that should be exchanged** + +Dependent upon the proposed restoration method that is to be used, Network Operators/Service Providers shall ensure that suitable preliminary information has been exchanged (e.g. designations and routings for any data transmission systems that may be used for dedicated service restoration). Additionally, records shall be kept of which circuits have been routed on the temporary restoration capacity. + +## **11      Planned maintenance** + +In cases of planned maintenance, either at the network or circuit level, impacting on the Network Operator/Service Provider's installations (transmission equipment, power equipment, cabling, etc.) which would cause or risk some performance degradation or unavailability of the digital leased circuit, reference is to be made to ITU-T Recommendation M.1540 [20] and the terms of the SLA/Contract with the Customer. + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1400-201504-I_PDF-E/raw.md b/marked/M/T-REC-M.1400-201504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2ecf1eb6e4964f898521b50ca23a90e3b34fd785 --- /dev/null +++ b/marked/M/T-REC-M.1400-201504-I_PDF-E/raw.md @@ -0,0 +1,6099 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1400** + +(04/2015) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Designations and information exchange + +--- + +**Designations for interconnections among +operators' networks** + +Recommendation ITU-T M.1400 + +**ITU-T** + +![ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'. + +# ITU-T M-SERIES RECOMMENDATIONS + +# TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T M.1400 + +# Designations for interconnections among operators' networks + +## Summary + +Recommendation ITU-T M.1400 covers the designations of interconnections among operators' networks of circuits, groups, group and line links, digital blocks, digital paths, data transmission systems, digital blocks created between digital circuit multiplication equipment (DCME), virtual containers and multiplex sections. + +The designation information is in two layers: + +- Layer 1: The unique information; the designation; +- Layer 2: Additional information; the related information. + +Guidance for the user is provided in a series of examples. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.14 | 1960-12-16 | | 11.1002/1000/7407 | +| 2.0 | ITU-T M.14 | 1964-06-26 | | 11.1002/1000/7406 | +| 3.0 | ITU-T M.14 | 1968-10-25 | | 11.1002/1000/7405 | +| 4.0 | ITU-T M.14 | 1972-12-15 | | 11.1002/1000/7404 | +| 5.0 | ITU-T M.140 | 1976-10-08 | | 11.1002/1000/7403 | +| 6.0 | ITU-T M.140 | 1980-11-21 | | 11.1002/1000/7402 | +| 7.0 | ITU-T M.140 | 1984-10-19 | | 11.1002/1000/5748 | +| 8.0 | ITU-T M.140 | 1988-11-25 | | 11.1002/1000/1488 | +| 9.0 | ITU-T M.1400 | 1992-10-05 | | 11.1002/1000/1489 | +| 10.0 | ITU-T M.1400 | 1997-04-19 | 4 | 11.1002/1000/4033 | +| 10.1 | ITU-T M.1400 (1997) Amd. 1 | 1998-06-26 | 4 | 11.1002/1000/4421 | +| 11.0 | ITU-T M.1400 | 2000-02-04 | 4 | 11.1002/1000/4861 | +| 12.0 | ITU-T M.1400 | 2001-10-14 | 4 | 11.1002/1000/5554 | +| 12.1 | ITU-T M.1400 (2001) Amd. 1 | 2002-05-29 | 4 | 11.1002/1000/6037 | +| 13.0 | ITU-T M.1400 | 2004-01-10 | 4 | 11.1002/1000/7092 | +| 14.0 | ITU-T M.1400 | 2006-07-14 | 4 | 11.1002/1000/8853 | +| 15.0 | ITU-T M.1400 | 2013-03-16 | 2 | 11.1002/1000/11903 | +| 16.0 | ITU-T M.1400 | 2015-04-29 | 2 | 11.1002/1000/12467 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2015 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# Table of Contents + +###### Page + +| | | | +|------|--------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 5 | +| 4 | Abbreviations and acronyms ..... | 7 | +| 5 | Conventions ..... | 8 | +| 6 | Framework..... | 9 | +| 6.1 | Layer 1 ..... | 9 | +| 6.2 | Layer 2..... | 11 | +| 6.3 | Implementation..... | 11 | +| 6.4 | Operator information ..... | 11 | +| 7 | Designations of public switched circuit interconnections ..... | 12 | +| 7.1 | General ..... | 12 | +| 7.2 | Telephone-type circuits ..... | 13 | +| 7.3 | Circuit used for switched telex and telegraph services ..... | 14 | +| 7.4 | Interconnecting circuits in the public switched data network ..... | 14 | +| 7.5 | Related information ..... | 14 | +| 8 | Related information for public switched circuit interconnections..... | 15 | +| 8.1 | Urgency for restoration [item 1]..... | 15 | +| 8.2 | Terminal countries [item 2] ..... | 15 | +| 8.3 | Names of network operators/service providers [item 3] ..... | 15 | +| 8.4 | Control station (sub-control station(s)) [item 4]..... | 16 | +| 8.5 | Fault report points [item 5]..... | 16 | +| 8.6 | Routing [item 6] ..... | 16 | +| 8.7 | Association [item 7] ..... | 17 | +| 8.8 | Equipment information [item 8]..... | 17 | +| 8.9 | Use [item 9] ..... | 18 | +| 8.10 | Transmission medium information [item 10]..... | 18 | +| 8.11 | Composition of the transmission [item 11] ..... | 19 | +| 8.12 | Bandwidth or bit rate [item 12] ..... | 19 | +| 8.13 | Signalling type [item 13] ..... | 19 | +| 9 | Designations of fixed (non-switched) circuit interconnections between operators..... | 20 | +| 9.1 | General ..... | 20 | +| 9.2 | Leased circuit interconnections ..... | 21 | +| 9.3 | Fixed (non-switched) public circuits ..... | 26 | +| 9.4 | Related information ..... | 29 | +| 10 | Related information for fixed circuit interconnections..... | 29 | +| 10.1 | Urgency for restoration [item 1]..... | 29 | + +| | Page | | +|-------|--------------------------------------------------------------------------------------------------|----| +| 10.2 | Terminal countries [item 2]..... | 30 | +| 10.3 | Names of network operators/service providers [item 3] ..... | 30 | +| 10.4 | Control station (sub-control station(s)) [item 4]..... | 30 | +| 10.5 | Fault report points [item 5]..... | 31 | +| 10.6 | Routing [item 6] ..... | 31 | +| 10.7 | Association [item 7] ..... | 32 | +| 10.8 | Equipment information [item 8]..... | 33 | +| 10.9 | Use [item 9] ..... | 33 | +| 10.10 | Transmission medium information [item 10]..... | 33 | +| 10.11 | Composition of the transmission [item 11] ..... | 34 | +| 10.12 | Bandwidth or bit rate [item 12] ..... | 34 | +| 10.13 | Signalling type [item 13] ..... | 35 | +| 10.14 | Applicable ITU-T Recommendations [item 14]..... | 35 | +| 11 | Designations of group, supergroup, etc. (bidirectional and unidirectional) interconnections..... | 35 | +| 11.1 | General ..... | 35 | +| 11.2 | Bidirectional groups, etc..... | 36 | +| 11.3 | Unidirectional groups and supergroups..... | 38 | +| 11.4 | Related information ..... | 39 | +| 12 | Designations of group link, supergroup link and line link interconnections ..... | 39 | +| 12.1 | Group and supergroup links ..... | 39 | +| 12.2 | Line links ..... | 40 | +| 12.3 | Related information ..... | 41 | +| 13 | Related information for group, group link and line link interconnections ..... | 41 | +| 13.1 | Urgency for restoration [item 1]..... | 42 | +| 13.2 | Terminal countries [item 2]..... | 42 | +| 13.3 | Names of network operators/service providers [item 3] ..... | 42 | +| 13.4 | Control station sub-control station(s) [item 4] ..... | 43 | +| 13.5 | Fault report points [item 5]..... | 43 | +| 13.6 | Routing [item 6] ..... | 44 | +| 13.7 | Association [item 7] ..... | 45 | +| 13.8 | Equipment information [item 8]..... | 45 | +| 13.9 | Use [item 9] ..... | 46 | +| 13.10 | Transmission medium information [item 10]..... | 46 | +| 13.11 | End-to-end information or operational agreement [item 11] ..... | 46 | +| 13.12 | Bandwidth [item 12]..... | 47 | +| 13.13 | Occupancy (for groups/supergroups, etc., and for line links) [item 13]..... | 47 | +| 14 | Designations of digital block (bidirectional and unidirectional) interconnections..... | 48 | +| 14.1 | General ..... | 48 | + +| | Page | | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 14.2 | Bidirectional digital blocks..... | 50 | +| 14.3 | Restoration digital blocks ..... | 50 | +| 14.4 | Multiple destination unidirectional digital blocks ..... | 50 | +| 14.5 | Single destination unidirectional digital blocks ..... | 51 | +| 14.6 | Related information ..... | 51 | +| 15 | Designation of digital path interconnections ..... | 51 | +| 15.1 | Conventional digital paths not connected to their terminal equipment..... | 51 | +| 15.2 | Restoration digital paths ..... | 52 | +| 15.3 | Digital line sections and digital radio sections ..... | 52 | +| 15.4 | Related information ..... | 52 | +| 16 | Designations of routes in the mixed analogue/digital transmission network ..... | 52 | +| 16.1 | Transmission routes with one analogue-to-digital conversion ..... | 53 | +| 16.2 | Transmission routes with two analogue-to-digital conversions ..... | 54 | +| 16.3 | Transmission routes with more than two analogue-to-digital conversions .... | 56 | +| 16.4 | Related information ..... | 56 | +| 17 | Designation of data transmission systems ..... | 56 | +| 17.1 | General ..... | 56 | +| 17.2 | Data transmission links..... | 59 | +| 17.3 | Related information ..... | 60 | +| 18 | Designations of digital block interconnections created by the interconnection of digital circuit multiplication equipments (DCMEs) ..... | 60 | +| 18.1 | General ..... | 60 | +| 18.2 | Multi-clique configuration of DCMEs ..... | 61 | +| 18.3 | Low-rate encoding equipment ..... | 62 | +| 18.4 | Related information ..... | 62 | +| 19 | Synchronous digital hierarchy (SDH) ..... | 63 | +| 19.1 | Designation of multiplex sections of the synchronous digital hierarchy (SDH) ..... | 63 | +| 19.2 | Designations of virtual container interconnections ..... | 64 | +| 19.3 | Concatenated virtual containers ..... | 66 | +| 19.4 | Leased circuits based on SDH ..... | 67 | +| 20 | Related information for digital block, path, data transmission system, block interconnections created by the interconnection of DCMEs, SDH multiplex sections and virtual containers..... | 68 | +| 20.1 | Urgency for restoration [item 1]..... | 68 | +| 20.2 | Terminal countries [item 2] ..... | 69 | +| 20.3 | Names of network operators/service providers [item 3] ..... | 69 | +| 20.4 | Control station [sub-control station(s)] [item 4]..... | 70 | +| 20.5 | Fault report points [item 5]..... | 70 | +| 20.6 | Routing [item 6] ..... | 71 | + +| | | | +|-------|-----------------------------------------------------------------------------------------------|----| +| 20.7 | Association [item 7] ..... | 72 | +| 20.8 | Equipment information [item 8]..... | 73 | +| 20.9 | Use [item 9] ..... | 74 | +| 20.10 | Transmission medium information [item 10]..... | 75 | +| 20.11 | End-to-end information or composition of transmission or operational agreement [item 11]..... | 75 | +| 20.12 | Bit rate (for blocks, paths and SDH multiplex sections) [item 12] ..... | 76 | +| 20.13 | Occupancy (except for paths) [item 13] ..... | 76 | +| 20.14 | Actual number of channels and access point identifier [item 14] ..... | 79 | +| 20.15 | Clocking information (for blocks only) [item 15]..... | 80 | +| 20.16 | Direction of transmission (for unidirectional blocks) [item 16]..... | 80 | +| 21 | Designation of connections for the asynchronous transfer mode (ATM) ..... | 81 | +| 21.1 | General ..... | 81 | +| 21.2 | Transport links..... | 81 | +| 21.3 | Virtual path..... | 82 | +| 21.4 | Virtual channels (VCAs) ..... | 83 | +| 21.5 | ATM Layer 2..... | 83 | +| 22 | Related information for the asynchronous transfer mode (ATM) ..... | 84 | +| 22.1 | Urgency for restoration [item 1]..... | 84 | +| 22.2 | Terminal countries [item 2] ..... | 84 | +| 22.3 | Names of network operators/service providers [item 3] ..... | 84 | +| 22.4 | Control and sub-control station(s) [item 4] ..... | 84 | +| 22.5 | Fault report points [item 5]..... | 84 | +| 22.6 | Routing [item 6] ..... | 84 | +| 22.7 | Association [item 7] ..... | 84 | +| 22.8 | Equipment information [item 8]..... | 84 | +| 22.9 | Use [item 9] ..... | 85 | +| 22.10 | Transmission medium information [item 10]..... | 85 | +| 22.11 | Operational agreement [item 11]..... | 85 | +| 22.12 | Unassigned item [item 12]..... | 85 | +| 22.13 | Occupancy [item 13] ..... | 85 | +| 22.14 | Direction of transmission (for unidirectional transit network services only) [item 14]..... | 85 | +| 22.15 | ATM transfer capability [item 15] ..... | 85 | +| 22.16 | Source traffic descriptor [item 16] ..... | 86 | +| 22.17 | Cell delay variation tolerance [item 17] ..... | 86 | +| 22.18 | Quality of service [item 18]..... | 86 | +| 23 | Transit network services ..... | 87 | +| 23.1 | General ..... | 87 | +| 23.2 | Transit digital transmission service ..... | 88 | + +| | Page | | +|---------|---------------------------------------------------------------------------------------------|-----| +| 23.3 | Transit dark fibre service..... | 89 | +| 23.4 | Related information ..... | 89 | +| 24 | Related information on transit network service..... | 90 | +| 24.1 | Urgency for restoration [item 1]..... | 90 | +| 24.2 | Terminal countries [item 2] ..... | 90 | +| 24.3 | Names of network operators/service providers [item 3] ..... | 90 | +| 24.4 | Control station [sub-control station(s)] [item 4]..... | 90 | +| 24.5 | Fault report points [item 5]..... | 90 | +| 24.6 | Routing [item 6] ..... | 90 | +| 24.7 | Association [item 7] ..... | 90 | +| 24.8 | Equipment information [item 8]..... | 90 | +| 24.9 | Use [item 9] ..... | 90 | +| 24.10 | Transmission medium information [item 10]..... | 90 | +| 24.11 | SLA [item 11]..... | 91 | +| 24.12 | Bit rate [item 12] ..... | 91 | +| 24.13 | Commercial identifier [item 13]..... | 91 | +| 24.14 | Unassigned item [item 14]..... | 91 | +| 24.15 | Clocking information [item 15]..... | 91 | +| 24.16 | Direction of transmission (for unidirectional transit network services only) [item 16]..... | 91 | +| 25 | Designations for wavelength division multiplexing (simple and dense)..... | 91 | +| 25.1 | General ..... | 91 | +| 25.2 | The equipment ..... | 92 | +| 25.3 | Configurations for the newly created transmission systems ..... | 93 | +| 25.4 | General format for the optical transmission systems ..... | 96 | +| 25.5 | Related information ..... | 99 | +| 26 | Related information on DWDM ..... | 99 | +| 27 | Designation of connections for the digital subscriber line (DSL) ..... | 101 | +| 27.1 | General ..... | 101 | +| 27.2 | Related information for the ADSL connections..... | 104 | +| 27.3 | Related information for the SDSL connection ..... | 105 | +| 27.4 | Examples ..... | 106 | +| 28 | Exceptional designations ..... | 107 | +| 28.1 | Exceptional designations with intelligence in the serial number ..... | 107 | +| 29 | Designation of optical transport networks..... | 107 | +| 29.1 | General ..... | 107 | +| 29.2 | Data transmission links..... | 109 | +| 29.3 | Related information ..... | 109 | +| Annex A | – Full examples for designation information..... | 111 | + +| | Page | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| A.1 | Full example for the designation information of a public switched telephone circuit ..... | 111 | +| A.2 | Full example for the designation information of a leased analogue circuit ... | 111 | +| A.3 | Full examples for the designation information of a group and a group link interconnection ..... | 112 | +| A.4 | Full examples for the designation information of a digital block, digital path, data transmission system, blocks created between DCMEs, virtual containers and SDH multiplex section interconnections..... | 114 | +| Annex B – | KLM addressing and its relationship to time slot numbering for virtual containers ..... | 123 | +| B.1 | KLM addressing relationship to time slot numbering..... | 123 | +| B.2 | KLM addressing of VC-4 occupancy..... | 124 | +| B.3 | Comparative notation of KLM addressing vs. time slot numbering ..... | 124 | +| Annex C – | Reference clause numbers for the various types of routes ..... | 127 | +| Annex D – | Numbering of channels in data transmission systems..... | 130 | +| Annex E – | Notification form for List of ITU Carrier Codes ..... | 132 | +| Annex F – | List of all ITU function codes..... | 133 | +| Bibliography..... | | 140 | + +# Introduction + +Designation of interconnecting routes is of great importance for identification and information. + +Technical developments, especially those due to digital technology, have brought a much greater variety of techniques and allow for a more efficient use of equipment. + +Information on the equipment and techniques used is of great interest to staff working in the field of maintenance and operation. Present operational conditions can be more complicated than those previously, e.g., as a consequence of greater competition in the field of telecommunication. Another consideration is automated file handling, which is often a necessity for network operators/service providers, and the standardization of designation is an important factor to facilitate this. + +The 2004 version of ITU-T M.1400 replaced every occurrence of "town" with "geographical area" on the basis of "geographical area" being more applicable for the termination of trails than "town". In addition, the 2004 revision aligned ITU-T M.1400 more closely with the ATIS Standard for location identification, which is not restricted to a town. + +The 2013 revised version of this Recommendation includes additional designations for Ethernet connections and optical transport networks (OTNs), and new Annex F – List of all ITU function codes. + +The 2015 revised version of this Recommendation includes additional designations for Ethernet connections, optical channel transport units (OTUk) and optical channel data units (ODUk). + + + +# Designations for interconnections among operators' networks + +# 1 Scope + +This Recommendation defines designations and additional information intended primarily for human-to-human communication between various operators, i.e., network operators or service providers. + +This Recommendation focuses on human needs for stable and recognizable data formats independent of the media through which they are communicated. Therefore, in order to support the human-to-human communication, the formats defined in this Recommendation will have to be provided at the corresponding human-to-computer interfaces as well. Hence, this Recommendation defines the presentation formats of data at human-to-computer interfaces, but does not define the data communication formats for interfaces between computer systems such as at the telecommunications management network (TMN) X interface, or non-TMN computer interfaces. However, it must be possible to automatically map the human-to-computer formats to the computer-to-computer formats and vice versa. The details of this mapping are for further study. + +This Recommendation extends the previous designation of international routes to also cover routes between national operators. However, use of this Recommendation inside national jurisdictions would be subject to national regulation and/or bilateral agreement between operators. Although compliance with all ITU-T Recommendations is voluntary, special mention is made for Recommendation ITU-T M.1400 due to the sensitivity of designations for interconnection from a regulatory and legal standpoint. This extension greatly increases the number of routes and nodes to be identified, and in this way extends the name spaces to be provided. + +This Recommendation defines both designations and additional information to be exchanged between two operators. However, this Recommendation focuses on information on network resources, operators and their addresses, and does not define order or transaction identification or additional information on the status or processing of these orders or transactions. + +The definition of information is independent of which function it supports. However, the selection of information defined in this Recommendation basically supports provisioning and network maintenance. In addition, this Recommendation may cover some information required for other TMNs or non-TMN functions, such as ordering and billing. + +This Recommendation aims at supporting communication between network operators, but may also support communication among network operators and service providers, brokers, retailers, customers and installation providers. + +This Recommendation aims at defining designations and additional information for technicians and file-support personnel at their terminals supporting the network, and serves as design information for developers of operational support systems. + +This Recommendation is presented in informal usual language, tables and figures. To support automatic interaction between computer systems of various operators, more formalization is needed. Also, the formalization may lead to redefinition of the scope of this Recommendation. These issues are for further study. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T E.164] Recommendation ITU-T E.164 (2010), *The international public telecommunication numbering plan*. +- [ITU-T E.171] Recommendation ITU-T E.171/Q.13 (1988), *International telephone routing plan*. +- [ITU-T F.162] Recommendation ITU-T F.162 (1996), *Service and operational requirements of store-and-forward facsimile service*. +- [ITU-T F.163] Recommendation ITU-T F.163 (1996), *Operational requirements of the interconnection of facsimile store-and-forward units*. +- [ITU-T G.113] Recommendation ITU-T G.113 (2007), *Transmission impairments due to speech processing*. +- [ITU-T G.692] Recommendation ITU-T G.692 (1998), *Optical interfaces for multichannel systems with optical amplifiers*. +- [ITU-T G.702] Recommendation ITU-T G.702 (1988), *Digital hierarchy bit rates*. +- [ITU-T G.707] Recommendation ITU-T G.707/Y.1322 (2007), *Network node interface for the synchronous digital hierarchy (SDH)*. +- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2012), *Interfaces for the optical transport network*. +- [ITU-T G.734] Recommendation ITU-T G.734 (1988), *Characteristics of synchronous digital multiplex equipment operating at 1544 kbit/s*. +- [ITU-T G.736] Recommendation ITU-T G.736 (1993), *Characteristics of a synchronous digital multiplex equipment operating at 2048 kbit/s*. +- [ITU-T G.742] Recommendation ITU-T G.742, (1988), *Second order digital multiplex equipment operating at 8448 kbit/s and using positive justification*. +- [ITU-T G.743] Recommendation ITU-T G.743 (1988), *Second order digital multiplex equipment operating at 6312 kbit/s and using positive justification*. +- [ITU-T G.745] Recommendation ITU-T G.745 (1988), *Second order digital multiplex equipment operating at 8448 kbit/s and using positive/zero/negative justification*. +- [ITU-T G.751] Recommendation ITU-T G.751 (1988), *Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 264 kbit/s and using positive justification*. +- [ITU-T G.752] Recommendation ITU-T G.752 (1988), *Characteristics of digital multiplex equipments based on a second order bit rate of 6312 kbit/s and using positive justification*. + +- [ITU-T G.753] Recommendation ITU-T G.753 (1988), *Third order digital multiplex equipment operating at 34 368 kbit/s and using positive/zero/negative justification.* +- [ITU-T G.754] Recommendation ITU-T G.754 (1988), *Fourth order digital multiplex equipment operating at 139 264 kbit/s and using positive/zero/negative justification.* +- [ITU-T G.803] Recommendation ITU-T G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy (SDH).* +- [ITU-T G.811] Recommendation ITU-T G.811 (1997), *Timing characteristics of primary reference clocks.* +- [ITU-T G.831] Recommendation ITU-T G.831 (2000), *Management capabilities of transport networks based on the synchronous digital hierarchy (SDH).* +- [ITU-T G.872] Recommendation ITU-T G.872 (2012), *Architecture of optical transport networks.* +- [ITU-T G.991.1] Recommendation ITU-T G.991.1 (1998), *High bit rate digital subscriber line (HDSL) transceivers.* +- [ITU-T G.992.1] Recommendation ITU-T G.992.1 (1999), *Asymmetric digital subscriber line (ADSL) transceivers.* +- [ITU-T G.992.2] Recommendation ITU-T G.992.2 (1999), *Splitterless asymmetric digital subscriber line (ADSL) transceivers.* +- [ITU-T G.994.1] Recommendation ITU-T G.994.1 (2012), *Handshake procedures for digital subscriber line transceivers.* +- [ITU-T G.996.1] Recommendation ITU-T G.996.1 (2001), *Test procedures for digital subscriber line (DSL) transceivers.* +- [ITU-T G.997.1] Recommendation ITU-T G.997.1 (2012), *Physical layer management for digital subscriber line transceivers.* +- [ITU-T I.121] Recommendation ITU-T I.121 (1991), *Broadband aspects of ISDN.* +- [ITU-T I.150] Recommendation ITU-T I.150 (1999), *B-ISDN asynchronous transfer mode functional characteristics.* +- [ITU-T I.211] Recommendation ITU-T I.211 (1993), *B-ISDN service aspects.* +- [ITU-T I.230] Recommendation ITU-T I.230 (1988), *Definition of bearer service categories.* +- [ITU-T I.231.1] Recommendation ITU-T I.231.1 (1988), *Circuit-mode 64 kbit/s unrestricted, 8 kHz structured bearer service.* +- [ITU-T I.231.2] Recommendation ITU-T I.231.2 (1988), *Circuit-mode 64 kbit/s, 8 kHz structured bearer service usable for speech transfer.* +- [ITU-T I.231.3] Recommendation ITU-T I.231.3 (1988), *Circuit-mode 64 kbit/s, 8 kHz structured bearer service usable for 3.1 kHz audio information transfer.* +- [ITU-T I.231.4] Recommendation ITU-T I.231.4 (1988), *Circuit-mode, alternate speech/64 kbit/s unrestricted, 8 kHz structured bearer service.* +- [ITU-T I.231.5] Recommendation ITU-T I.231.5 (1988), *Circuit-mode 2\*64 kbit/s unrestricted, 8 kHz structured bearer service.* +- [ITU-T I.231.6] Recommendation ITU-T I.231.6 (1996), *Circuit-mode 384 kbit/s unrestricted, 8 kHz structured bearer service.* + +- [ITU-T I.231.7] Recommendation ITU-T I.231.7 (1996), *Circuit-mode 1536 kbit/s unrestricted, 8 kHz structured bearer service.* +- [ITU-T I.231.8] Recommendation ITU-T I.231.8 (1996), *Circuit-mode 1920 kbit/s unrestricted, 8 kHz structured bearer service.* +- [ITU-T I.231.9] Recommendation ITU-T I.231.9 (1993), *Circuit-mode 64 kbit/s 8 kHz structured multi-use bearer service.* +- [ITU-T I.231.10] Recommendation ITU-T I.231.10 (1992), *Circuit-mode multiple rate unrestricted 8 kHz structured multi-use bearer service.* +- [ITU-T I.232.1] Recommendation ITU-T I.232.1 (1988), *Virtual call and permanent virtual circuit bearer service category.* +- [ITU-T I.232.2] Recommendation ITU-T I.232.2 (1988), *Connectionless bearer service category.* +- [ITU-T I.232.3] Recommendation ITU-T I.232.3 (1993), *User signalling bearer service category.* +- [ITU-T I.310] Recommendation ITU-T I.310 (1993), *ISDN – Network functional principles.* +- [ITU-T I.311] Recommendation ITU-T I.311 (1996), *B-ISDN general network aspects.* +- [ITU-T I.326] Recommendation ITU-T I.326 (2003), *Functional architecture of transport networks based on ATM.* +- [ITU-T I.365.1] Recommendation ITU-T I.365.1 (1993), *Frame relaying service specific convergence sublayer (FR-SSCS).* +- [ITU-T I.365.2] Recommendation ITU-T I.365.2 (1995), *Service-specific coordination function to provide the connection-oriented network service.* +- [ITU-T I.365.3] Recommendation ITU-T I.365.3 (1995), *Service-specific coordination function to provide the connection-oriented transport service.* +- [ITU-T I.365.4] Recommendation ITU-T I.365.4 (1996), *Service-specific convergence sublayer for HDLC applications.* +- [ITU-T I.432.1] Recommendation ITU-T I.432.1 (1999), *General characteristics.* +- [ITU-T I.432.2] Recommendation ITU-T I.432.2 (1999), *155 520 kbit/s and 622 080 kbit/s operation.* +- [ITU-T I.432.3] Recommendation ITU-T I.432.3 (1999), *1544 kbit/s and 2048 kbit/s operation.* +- [ITU-T I.432.4] Recommendation ITU-T I.432.4 (1999), *61 840 kbit/s operation.* +- [ITU-T I.432.5] Recommendation ITU-T I.432.5 (1997), *25 600 kbit/s operation.* +- [ITU-T M.20] Recommendation ITU-T M.20 (1992), *Maintenance philosophy for telecommunication networks.* +- [ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [ITU-T M.80] Recommendation ITU-T M.80 (1988), *Control stations.* +- [ITU-T M.90] Recommendation ITU-T M.90 (1988), *Sub-control stations.* +- [ITU-T M.1013] Recommendation ITU-T M.1013 (1988), *Sub-control station for leased and special circuits.* +- [ITU-T M.1020] Recommendation ITU-T M.1020 (1993), *Characteristics of special quality international leased circuits with special bandwidth conditioning.* + +- [ITU-T M.1045] Recommendation ITU-T M.1045 (1996), *Preliminary exchange of information for the provision of international leased circuits and international data transmission systems.* +- [ITU-T M.1055] Recommendation ITU-T M.1055 (1988), *Lining up an international multiterminal leased circuit.* +- [ITU-T M.1340] Recommendation ITU-T M.1340 (2000), *Performance objectives, allocations and limits for international PDH leased circuits and supporting data transmission links and systems.* +- [ITU-T M.1380] Recommendation ITU-T M.1380 (2000), *Bringing-into-service of international leased circuits that are supported by international data transmission systems.* +- [ITU-T M.1385] Recommendation ITU-T M.1385 (2000), *Maintenance of international leased circuits that are supported by international data transmission systems.* +- [ITU-T M.1510] Recommendation ITU-T M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network.* +- [ITU-T M.2130] Recommendation ITU-T M.2130 (2000), *Operational procedures for the maintenance of the transport network.* +- [ITU-T M.3208.1] Recommendations ITU-T M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services.* +- [ITU-T M.3320] Recommendations ITU-T M.3320 (1997), *Management requirements framework for the TMN X-Interface.* +- [ITU-T Q.8] Recommendation ITU-T Q.8 (1988), *Signalling systems to be used for international manual and automatic working on analogue leased circuits.* +- [ITU-T Q.9] Recommendation ITU-T Q.9 (1988), *Vocabulary of switching and signalling terms.* +- [ITU-T R.70] Recommendation ITU-T R.70 (1988), *Designation of international telegraph circuits.* +- [ITU-T V.29] Recommendation ITU-T V.29 (1988), *9600 bits per second modem standardized for use on point-to-point 4-wire leased telephone-type circuits.* +- [ISO 3166-1] ISO 3166-1 (2013), *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes.* +- [ITU-T Carrier] *ITU-T List of ITU Carrier Codes* +- NOTE –The list of ITU Carrier Codes is available at: . + +# 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 association:** Information about a route that identifies which other route(s) are related and what the type of relation is between them (e.g., diverse routing). +- 3.2 clocking information:** Information used to specify if an [ITU-T G.811] compliant clocking system or a master-slave clocking system is applied to the digital block. If a master-slave clocking system is applied, this information identifies the master and the slave. +- 3.3 composition of transmission:** Information about a circuit with respect to its applied routing, i.e., on analogue, digital or mixed transmission. + +**3.4 created digital block:** A digital block created by the interconnection of two digital circuit multiplication equipments (DCMEs). The bit rate for this kind of digital block is 1544 kbit/s or 2048 kbit/s. Its frame structure does not coincide with the multi-frame structure as defined in [ITU-T G.704] as the bit rate of each channel is one of the following: 64, 40, 32, 24, 16 kbit/s. The number of channels carried by a created digital block ranges from 30 to 240, in multiples of 30. + +**3.5 designation:** Information in a structured format that provides identification of a *route*. The designation consists of *traffic relation*, *function code* and *serial number*. + +**3.6 digital block:** A block which is part of the digital multiplex hierarchy and which is formatted according to [ITU-T G.734], [ITU-T G.736], [ITU-T G.742], [ITU-T G.743], [ITU-T G.745], [ITU-T G.751], [ITU-T G.752], [ITU-T G.753] and [ITU-T G.754]. + +**3.7 equipment information:** Information about the equipment used in the *route* when this equipment requires special maintenance attention. + +**3.8 function code:** A portion of a designation that identifies the type of route by a distinguishing characteristic, e.g., directionality, bit rate. + +**3.9 geographical area name:** The official name of a geographical area as identified in the country to which it belongs. + +**3.10 ITU Carrier Code (ICC):** A unique identifier of a network operator/service provider, listed and maintained in the "List of ITU Carrier Codes (according to ITU-T M.1400)". Its assignment may be delegated to a lower-level administration, e.g., province or state. + +**3.11 network operator:** An operator that manages a telecommunications network. A network operator may be a *service provider* and vice versa. A network operator may or may not provide particular telecommunications services. See clause 1.4.2.3 of [ITU-T M.3208.1], and clause 1.4.4 of [ITU-T M.3320]. + +**3.12 operator:** An organization responsible for identification and management of telecommunication resources. An operator must be legally recognized by the telecommunication administration of the country, or delegation thereof. An operator may or may not correspond to a trading partner. + +**3.13 related information:** A set of information about a route that it is necessary to know about at both terminations of that route. + +NOTE 1 – Related information is also referred to as Layer 2. + +NOTE 2 –The set is categorized by numbered items with specified formats. The items cover technical characteristics, e.g., routing and occupancy, as well as operational ones, e.g., control stations. + +**3.14 route:** All types of telecommunication connections: circuits, groups, blocks, etc. + +**3.15 serial number:** A portion of a designation that enumerates routes having the same *traffic relation* and *function code*. + +**3.16 service provider:** A general reference to an operator that provides telecommunication services to customers and other users, either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. See clause 1.4.6 of [ITU-T M.3320]. + +**3.17 suffix:** Information about the network node and network operator/service provider operating the node and that are associated with a *route* termination. + +**3.18 terminal country:** Information that identifies one of the countries in which a route is terminating. + +**3.19 transmission medium information:** Information about a route meant to give a warning about routing restrictions with respect to the transmission medium. + +**3.20 transport relation:** An ordered pair of *route* terminations. + +**3.21 use:** Information on the usage of the *route* when this usage is required by the operator. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|---------------------------------------------| +| ADPCM | Adaptive Differential Pulse Code Modulation | +| ADSL | Asymmetric Digital Subscriber Line | +| AP | Access Point | +| ATM | Asynchronous Transfer Mode | +| BC | Bearer Circuit | +| CDVT | Cell Delay Variation Tolerance | +| CIC | Circuit Identification Code | +| CO | Compandor | +| CPE | Customer Premises Equipment | +| CS | Control Station | +| CTE | Channel Translating Equipment | +| DC | Derived Circuit | +| DCME | Digital Circuit Multiplication Equipment | +| DSL | Digital Subscriber Line | +| DSLAM | Digital Subscriber Line Access Multiplexer | +| DWDM | Dense Wavelength Division Multiplexing | +| EC | Echo Canceller | +| EP | Even Position | +| ES | Echo Suppressor | +| GE | Gigabit Ethernet | +| GTE | Group Translating Equipment | +| IBT | Intrinsic Burst Tolerance | +| ICC | ITU Carrier Code | +| IDR | Intermediate Data Rate | +| LAN | Local Area Network | +| LRE | Low Rate Encoding | +| MU | Multiple destination Unidirectional | +| NO/SP | Network Operator/Service Provider | +| NTE | Network Terminating Equipment | +| OADM | Optical Add-Drop Multiplexer | +| OAS | Optical Amplifier Section | +| OC | Optical Channel | + +| | | +|--------------|---------------------------------------| +| OCh | Optical Channel | +| OMS | Optical Multiplex Section | +| OP | Odd Position | +| OTN | Optical Transport Network | +| PDH | Plesiochronous Digital Hierarchy | +| PHY | Physical layer | +| PLR | Part of a Longer Route | +| PTE | Path Terminating Equipment | +| QoS | Quality of Service | +| ORS | Optical Regenerator Section | +| SCR | Sustainable Cell Rate | +| SCS | Sub-Control Station | +| SDH | Synchronous Digital Hierarchy | +| SDSL | Symmetric Digital Subscriber Line | +| SGTE | Super Group Translating Equipment | +| SI | Speech Interpolation | +| SLA | Service Level Agreement | +| SONET | Synchronous Optical Network | +| SPC | Signalling Point Code | +| STD | Source Traffic Descriptor | +| STM | Synchronous Transport Module | +| TDM | Time Division Multiplex | +| TMN | Telecommunications Management Network | +| VBR | Variable Bit Rate | +| VC | Virtual Container | +| VC- n | Virtual Container- n | +| VCA | Virtual Channel | +| WAN | Wide Area Network | +| WDM | Wavelength Division Multiplexing | + +## 5 Conventions + +Data fields in the designation and related information shall consist of sequences of characters, each character being either alphabetic (A-Z) or numeric (0-9). Additional requirements for symbols are explicitly stated in format requirements for specific fields. It is recommended that alphabetic characters be represented with upper case letters, unless stated otherwise. + +# 6 Framework + +To cover the need for standardized designations which are easy to handle but which give precise information, the designation information is built up from two layers: + +- Layer 1 provides the unique identification: the designation. +- Layer 2 provides the necessary additional information which must be known at both terminations of the routes: the related information. + +## 6.1 Layer 1 + +The general format of Layer 1 for the designation of all types of interconnecting routes is shown in Table 1. + +**Table 1 – Layer 1 designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | / | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 6 | ≤ 4 | +| | | | | | | | | | | | | | | | | | ↑
No space | | + +The elements of the Layer 1 format are as follows: + +#### a) *Transport relation* + +An ordered pair of route termination identifiers: + +*Geographical Area A and Geographical Area B* refer to the names of the two geographical areas in which the origin and destination terminations of the interconnecting routes are located. The geographical area names (required: one to twelve characters or space) (see Note) in all types of designations should always take the official name of a geographical area as used in the country to which it belongs. Upper and lower case letters are permitted. Symbols that may be included in Geographical Area A and Geographical Area B are hyphen (–), underscore (\_), and space ( ). + +*Termination detail* is assigned by an operator to uniquely identify its route terminations within a geographical area. Termination detail is required and consists of one to six characters. Symbols that may be included in termination detail are hyphen (–), underscore (\_), and space ( ). + +*Operator ID* is the ICC that identifies the operator originating a route termination identification (one to six characters, each character being either alphabetic (i.e., A-Z) or numeric (i.e., 0-9) characters). For stability, it is required that this code not be changed for the life of the route termination identifier, regardless of any change in the operator responsible for maintaining the route termination identifier. Thus, Related Information Item 3 of Rec. ITU-T M.1400 Layer 2 must be referred to in determining the current responsible operator. + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (required: one to six alphabetic or numeric characters): + +Indicates the type of route. + +- c) *Serial number* (required: one to four numbers): + +Identifies the instance of the route (e.g., circuit, group, digital block, etc.) within the same transport relation and the same function code. The serial numbering starts anew if there is a difference in: + +- transport relation; +- function code. + +NOTE – If the name of the geographical area exceeds 12 characters, the responsible operator will supply an appropriate abbreviation, which should be unique. + +This Recommendation includes specifications for two route configurations: a route for end-to-end service between end-points A and B in Figure 1, and a route that includes a transit network service provided by Network Operator/Service Provider 2 (NO/SP 2). It is important to note that NO/SP 1 and NO/SP 3 in the transit network configuration may be the same, e.g., where NO/SP 1 is operating as a competitor in the country of NO/SP 2. In such a case, when NO/SP 2 provides transit service to NO/SP 1, NO/SP 2 does not need to know the origin and destination or other characteristics of the end-to-end service route for NO/SP 1. Transit route connections are specified using their origins and destinations, as opposed to using the origin and destination of the entire route. NO/SP 1 does not share the designation of the entire route with NO/SP 2. However, NO/SP 1 and NO/SP 2 do share the transit designations. + +![Diagram of a transit network showing three network operators (NO/SP 1, NO/SP 2, NO/SP 3) connected in series. End-points A and B are at the far left and far right respectively. NO/SP 1 is on the left, NO/SP 2 is in the middle, and NO/SP 3 is on the right. Each operator's network is represented by a box containing two grey rectangles. Solid lines connect the boxes. Dashed vertical lines separate the operators' domains. Below the boxes, arrows indicate 'Transit network connection' between NO/SP 1 and NO/SP 2, and between NO/SP 2 and NO/SP 3. A long double-headed arrow at the bottom spans from A to B and is labeled 'End-to-end service'. The diagram is labeled M.1400(13)_F01 in the bottom right corner.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +Diagram of a transit network showing three network operators (NO/SP 1, NO/SP 2, NO/SP 3) connected in series. End-points A and B are at the far left and far right respectively. NO/SP 1 is on the left, NO/SP 2 is in the middle, and NO/SP 3 is on the right. Each operator's network is represented by a box containing two grey rectangles. Solid lines connect the boxes. Dashed vertical lines separate the operators' domains. Below the boxes, arrows indicate 'Transit network connection' between NO/SP 1 and NO/SP 2, and between NO/SP 2 and NO/SP 3. A long double-headed arrow at the bottom spans from A to B and is labeled 'End-to-end service'. The diagram is labeled M.1400(13)\_F01 in the bottom right corner. + +**Figure 1 – Transit network** + +The use of transit networks reflects the new operating conditions due to liberalization of telecommunications and the consequent increased competition. To accommodate this approach, clause 23 covers transit networks. In addition, a note is provided in each clause where transit networks apply. + +If identical place names occur in different countries, and if confusion is likely to arise, the network operators/service providers concerned should agree to identify the country in the designation by adding after the place name a three-letter (alpha-3) country code as defined in [ISO 3166-1]. This country code must be included within the 12 characters of the geographical area name, if necessary by providing an abbreviation of the geographical area name. + +The serial number should be written without leading zeros. + +## 6.2 Layer 2 + +The general format for Layer 2 (related information) is as follows: + +- 1 . . . , . . . ; +- 2 . . . , . . . ; +- 3 . . . , . . . ; etc. + +The numbers identifying the fields in Layer 2 indicate the various items. Each item provides information on the route, e.g., *operational*: operating companies and control station, etc., or *technical*: analogue/digital, use of special equipment, etc. The items provide flexibility in designation information because they can be extended in the future if there is a need. + +## 6.3 Implementation + +Where designations do not comply with this Recommendation, e.g., due to outdated rules, it is recommended that operators change such designations. + +To facilitate the change, operators with control station responsibility should prepare proposals containing designations conforming to Layer 1 and propose the items of related information to be included in Layer 2. + +Agreement should then follow on the designation as well as an exchange of the agreed Layer 2 information. + +Operators will need to ensure that the Layer 2 related information is kept up to date and that other operators concerned are informed of any changes. + +## 6.4 Operator information + +Due to liberalization of telecommunications and increased competition in the telecommunications industry, there is a mandatory requirement that telecommunications operators that interoperate be identified. A centralized list of ITU Carrier Codes (ICCs) has been created, with TSB (ITU-T Secretariat) as the repository [ITU-T Carrier]. Instead of individual operators sending their ICCs to the TSB for registration, the national regulatory authorities are requested to provide the validated codes, and related information concerning international and domestic network operators, directly to the TSB by using the ICC notification form in Annex E. + +NOTE 1 – This form is also available online at . + +This list may be used to identify the operators while completing Layer 2 records, and related information, as explained in clauses 8.3, 13.3 and 20.3. + +Information and notification forms concerning ICC assignment should be directed to: + +Director of TSB +International Telecommunication Union +Place des Nations +1211 Geneva 20 +Switzerland + +Fax: +41 22 730 58 53 + +The ICC list identifies operators that are recognized by each Member State's Administration. + +NOTE 2 – Such a list is provided at . + +The ICCs may be used both for electronic commerce between operators and for designation of resources in their networks. Hence, ICCs can be assigned both to network operators and to service providers. + +It should be noted that ICCs can be assigned both to ITU-T and non-ITU-T Members, and that the referenced local ICC website may contain ICCs of operators of both kinds. + +The central ITU ICC website includes a page for ICC information, having one entry for each country. Each entry may have a reference to a local ICC website containing the appropriate information about ICCs in that country. Some Administrations may ask the TSB to maintain their list of ICCs at the central ITU ICC website, while others may choose to establish their own website directly, or through another organization, e.g., NECA1. All local ICC websites should be accessible free of charge. + +# 7 Designations of public switched circuit interconnections + +## 7.1 General + +The format of the designation of public switched circuits is shown in Table 2. + +**Table 2 – Public switched circuit designation format** + +| Format of designation | Geographical Area A | / | Exchange detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Exchange detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|-------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|-------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 1 or 2 | ≤ 4 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +### a) *Transport relation* + +Switched circuit termination A and switched circuit termination B refer to the names of the two exchanges in which the circuit terminates. The name of each exchange consists of the following elements: geographical area name, exchange detail, operator ID and country code. The order of the two exchanges is dependent on the operation of the circuit which will be indicated by the function code. + +*Geographical area*: the geographical area where the exchange is situated (required: one to twelve characters or space). + +*Exchange detail* shows the information that makes the exchange unique in the operator domain in that particular geographical area (see Note). Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the exchange identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +### b) *Function code* (format: one to two letters and/or digits): + +Indicates the type of circuit. + +1 National Exchange Carrier Association, Inc. (NECA) in North America. + +c) *Serial number* (required: one to four digits): + +Identifies the instance of the circuit. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +NOTE – In the example given in Figure 2, there may be only one exchange detail or three exchange details to be decided by the operator. + +![Figure 2 – Exchange configuration diagram](26d664119ad25250780f554633444e54_img.jpg) + +A circular diagram divided into three equal sectors by three lines meeting at the center. The top-left sector is labeled 'International exchange'. The top-right sector is labeled 'Electro-mechanic equipment'. The bottom sector is labeled 'Digital SPC'. Below the circle, the text 'M.1400(13)\_F02' is written. + +Figure 2 – Exchange configuration diagram + +Figure 2 – Exchange configuration + +## 7.2 Telephone-type circuits + +### 7.2.1 General + +Possible function codes are: + +- M manual telephone circuits; +- Z automatic and semi-automatic telephone circuits in one-way operation; +- B both-way telephone circuits. + +For the serial number, a special condition applies: by bilateral agreement, operators may wish to apply a serial number to telephone-type circuits on a geographical-area-to-geographical-area basis rather than on an exchange-to-exchange basis. + +### 7.2.2 Telephone circuits used in manual operation + +The circuit terminations are arranged in alphabetical order. + +The function code is: M. + +*Example:* + +The first telephone circuit for manual operation between London Keybridge of BT and the exchange Paris Bagnolet of France is designated: + +London/KB/BTPLC/GBR–Paris/BA/FRTE/FRA M1. + +### 7.2.3 One-way telephone circuits used for semi-automatic or automatic operation + +The circuit terminations are arranged in the order according to the direction of operation of the circuit. + +The function code is: Z. + +*Serial numbering:* Circuits operated in the direction corresponding to the alphabetical order of the terminations should have odd numbers: $(2n - 1)$ . Circuits operated in the direction corresponding to an inverse alphabetical order of the terminations should have even numbers: $(2n)$ . + +*Examples:* + +The eleventh circuit operated in the London Mollison exchange of BT to the Montreal 1TE exchange operated by Teleglobe Canada ULC with traffic in the direction from London to Montreal (alphabetical order of geographical areas) is designated: + +London/SM/BTPLC/GBR–Montreal/1TE/TGB/CAN Z21. + +The ninth circuit operated in the Montreal 1TE to London Mollison direction (inverse alphabetical order of geographical areas) is designated: + +Montreal/1TE/TGB/CAN–London/SM/BTPLC/GBR Z18. + +### **7.2.4 Both-way telephone circuits used for semi-automatic or automatic operation** + +The circuit terminations are arranged in alphabetical order. + +The function code is: B. + +*Example:* + +The first both-way circuit between the London Kelvin exchange of BT and the New York 24 exchange of MCI is designated: + +London/J/BTPLC/GBR–New York/24/MCI/USA B1. + +## **7.3 Circuit used for switched telex and telegraph services** + +See [ITU-T R.70]. + +## **7.4 Interconnecting circuits in the public switched data network** + +The terminations of the circuit are arranged in alphabetical order. + +The function code is: XD. + +*Example:* + +The first interconnection public switched data circuit between the Oslo A exchange of Telenor and the Stockholm HYX exchange of TeliaSonera AB is designated: + +Oslo/A/TELNOR/NOR–Stockholm/HYX/TELIA/SWE XD1. + +## **7.5 Related information** + +The additional information on public switched circuits is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) composition of transmission; +- 12) bandwidth or bit rate; +- 13) signalling type. + +The various items will be dealt with in clause 8. + +# 8 Related information for public switched circuit interconnections + +The following subclauses explain the items of related information concerned with public switched circuit interconnections. A full example for the designation information of a public switched telephone circuit interconnection is given in clause A.1. + +## 8.1 Urgency for restoration [item 1] + +This item supplies information on the urgency of restoration of the circuit, based upon bilateral agreement between the terminal network operators/service providers. + +*Format:* + +1. xxx . . . xx; (maximum ten characters) + +*Illustration:* + +- a) if the priority is top: 1; +if the priority is second: 2; +if the priority is third: 3; or +- b) if repair is required within, e.g., 24 hours: $\leq 24$ h; or +- c) if no urgency has to be indicated: –; + +## 8.2 Terminal countries [item 2] + +This item presents the countries in which the circuit is terminating. + +*Format:* + +2. XXX, YYY; (three characters for each) + +*Specification:* + +XXX: code for country of Geographical Area A + +YYY: code for country of Geographical Area B + +NOTE – The alpha-3 codes are according to [ISO 3166-1]. + +*Example:* + +For the circuit London/KB/BTPLC/GBR–Paris/BA/FRTE/FRA M1: + +2. UKM, FRA; + +## 8.3 Names of network operators/service providers [item 3] + +This item records the names of the network operators/service providers which operate the circuit. + +The applicable codes can be selected from the List of ITU Carrier Codes as described in clause 6.4. + +*Format:* + +3. YYYYYY, ZZZZZZ; (maximum six characters for each) + +*Specification:* + +YYYYYY: code for company operating in Geographical Area A + +ZZZZZ: code for company operating in Geographical Area B + +*Example:* + +For the circuit London/KB/BTPLC/GBR–Paris/BA/FRTE/FRA M1 operated by BT and FRTE: + +3. BT, FRTE; + +## 8.4 Control station (sub-control station(s)) [item 4] + +This item lists the appointed control station and sub-control stations (according to [ITU-T M.80] and [ITU-T M.90]). Further details about the stations can be found in the list of contact points [ITU-T M.1510]. + +*Format:* + +- 4. CS: designation of control station, +SCS1: designation of sub-control station, +SCS2: designation of sub-control station, +M M +SCSn: designation of sub-control station; + +*Specification:* + +- CS: designation of the control station, +SCS1: designation of the terminal sub-control station, +SCS2 to SCSn: if applicable, other sub-control stations have to be placed in the geographical order according to the traffic relation. + +*Example:* + +For the circuit New York/10/ATT/USA–Stockholm/HYX/TELIA/SWE XD1 where New York is the control station and sub-control stations are in London and Stockholm: + +- 4. CS: New York/10/ATT/USA, +SCS1: Stockholm/HYX/TELIA/SWE, +SCS2: London/KB/BTPLC/GBR; + +## 8.5 Fault report points [item 5] + +This item presents the names of both fault report points on the circuit. Further information about the fault report points can be found in the list of contact points [ITU-T M.1510]. + +*Format:* + +- 5. Designation of fault report point, designation of fault report point; + +*Specification:* + +The first report point is that of the country of Geographical Area A. + +The second fault report point is that of the country of Geographical Area B. + +*Example:* + +For the circuit London/M/BTPLC/GBR–Reims/IP/FRTE/FRA1 Z999 with fault report points in London M and Reims XRE: + +- 5. London/M/BTPLC/GBR, Reims/XRE/FRTE/FRA; + +## 8.6 Routing [item 6] + +This item shows the interconnecting primary group(s) or primary block(s) and channel number(s) which carry the circuit. If there is more than one, the groups or digital blocks appear in the geographical order from Geographical Area A to Geographical Area B. + +*Format:* + +6. Designation of an interconnecting primary group or primary block/channel number, designation of a primary group/channel number, ..., designation of a primary group/channel number; + +NOTE – Primary groups or digital blocks can be unidirectional as well. Two consecutive unidirectional groups or digital blocks are separated by a + sign instead of a comma. + +*Example:* + +For a circuit London/KB/BTPLC/GBR–Santiago/CTCMDO/CHL1 Z27: + +6. London/KB/BTPLC/GBR–Paris/IP/FRTE/FRA 1204/4, Paris/IP/FRTE/FRA–(MU) 1202/2+Santiago/CTCMDO/CHL–(MU) 1203/3; + +## **8.7 Association [item 7]** + +This item informs whether there are associated circuits and, if so, of which nature. + +*Format:* + +7. Association code: designation of associated circuit; + +*Specification:* + +If the circuit *has* a reserve circuit, the association code is: S followed by the function code and the serial number of the principal circuit. + +If the circuit *is* a reserve circuit, the association code is: function code followed by S and the serial number of the reserve circuit. + +*Example 1:* + +7. ZS13: Roma/AS1/TI/ITA–Zurich/SEL/CHEPTT/CHE T1; + +which indicates that the actual circuit Z13 is a reserve circuit for the circuit Roma/AS1/TI/ITA–Zurich/SEL/CHEPTT/CHE T1. + +If the circuit belongs to a group of circuits for which the time slot sequential order (end-to-end) must be guaranteed, the association code is: TSG. The designations of the associated circuits are abbreviated by taking the function code of the circuits followed by the lowest sequential number, a hyphen and the highest sequential number. + +*Example 2:* + +If the circuit Sherman Oaks/4ES/ATT/USA–Singapore/EST/ST/SGP B607 belongs to a group of 30 circuits for which the time slot sequential order must be guaranteed, the association is: + +7. TSG: B601-630; + +## **8.8 Equipment information [item 8]** + +This item records any equipment in the circuit which requires special maintenance attention. + +*Format:* + +8. XX, XX, XX, XX, XX; + +*Specification:* + +If the circuit has been routed via analogue circuit multiplication equipment: AM + +If the circuit has been routed via digital circuit multiplication equipment: + +- using reduced bit rate encoding: RB +- using speech interpolation: SI + +If the circuit has a compandor: CO + +If the circuit has an echo suppressor: ES + +If the circuit has an echo canceller: EC + +If the circuit has an echo suppressor in terminal country of Geographical Area A and an echo canceller in terminal country of Geographical Area B: ES, EC (any combination of EC and ES is possible). + +If the circuit is a bearer circuit: BC + +If the circuit is a derived circuit: DC + +NOTE 1 – If there is a need to record an additional special equipment, additional codes can be used by bilateral agreement between the network operators/service providers. The codes must be unique and shall have two characters. + +NOTE 2 – A bearer circuit refers to the circuit type that continues to be provided in the case of a breakdown of the circuit multiplication equipment. For a derived circuit, this is not the case. + +## 8.9 Use [item 9] + +This item supplies information on the usage of the circuit. It concerns the role of the circuit in the traffic (e.g., belonging to a final route) and the usage of the circuit made by the user. + +*Format:* + +9. XX, YYYY; (maximum seven characters) + +*Specification:* + +XX refers to the type of traffic carried by the circuit: + +- if it belongs to an overflow group of circuits: OF +- if it belongs to a transit group of circuits: TR +- if the information is not known: – + +YYYY refers to the use of the circuit: + +- in the case where a public telephone circuit is used for phototelegraphy or facsimile: F +- in the case where such a circuit is occasionally used for narrow-band sound programme transmission: RK. + +## 8.10 Transmission medium information [item 10] + +This item identifies whether a satellite is involved in the routing of the circuit. + +*Format:* + +10. ST; or –; + +*Specification:* + +If the circuit has been routed via satellite: ST + +If the circuit is not being routed via satellite: – + +*Example:* + +For the circuit Amsterdam/2H/TCOMNL/NLD–New York/24/ATT/USA Z33 routed partly via satellite: + +10. ST; + +## **8.11 Composition of the transmission [item 11]** + +This item shows the type of transmission on the circuit. + +*Format:* + +11. A; or N; or C; + +*Specification:* + +If the transmission is analogue: A + +If the transmission is digital: N + +If the transmission is mixed analogue/digital: C + +## **8.12 Bandwidth or bit rate [item 12]** + +This item shows the bandwidth (in the case of an analogue or mixed circuit) or the bit rate (in the case of a digital circuit). + +*Format:* + +12. xxxx.x Hz; or kHz; or MHz; bit/s; or kbit/s; or Mbit/s; + +Rule for the notation of the figures: + +Leading zeros may be omitted, and if the decimal is a zero, this decimal and the decimal point may also be omitted. + +If the figure is up to 999, use Hz, bit/s. + +If the figure is between 1000 and 9 999 999, use kHz, kbit/s. + +If the figure is 10 000 000 or more, use MHz, Mbit/s. + +*Specification:* + +If the circuit is analogue or mixed analogue/digital: the bandwidth in Hz, kHz, MHz. + +If the circuit is digital: the bit rate in bit/s, kbit/s, Mbit/s. + +## **8.13 Signalling type [item 13]** + +This item presents the signalling information that applies to the circuit. + +*Format:* + +13. xx . . . xx; (maximum 20 characters) + +*Specification:* + +If the signalling is of the type xxxx Hz/xx Hz: xxxx/xx + +If the ITU-T Signalling System R2 is applied: R2 + +If the ITU-T Signalling System R2-digital is applied: R2D + +If the ITU-T Signalling System No. 4 is applied: C4 + +If the ITU-T Signalling System No. 5 is applied: C5 + +If the ITU-T Signalling System No. 6 is applied: C6, xxx/yy where xxx/yy refers to band and circuit number respectively. + +If the ITU-T Signalling System No. 7 is applied: C7, xxxx, Y-YYY-Y, Z-ZZZ-Z where xxxx refers to the Circuit Identification Code (CIC). + +Y-YYY-Y refers to the Signalling Point Code (SPC) or National Signalling Point Code (NSPC) for Geographical Area A/exchange. + +Z-ZZZ-Z refers to the SPC or NSPC for Geographical Area B/exchange. + +*Example:* + +For a circuit with C6-signalling type and being the seventh circuit in band number 32: + +13. C6, 032/06; (circuit counting starts at 0) + +# 9 Designations of fixed (non-switched) circuit interconnections between operators + +## 9.1 General + +The designations of leased circuits and public fixed circuits are treated in clauses 9.2 and 9.3 respectively. The format of the designation of fixed circuits is shown in Table 3. + +**Table 3 – Leased circuit designation format** + +| Format of designation | Geographical Area A | / | Transmission station detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Transmission station detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|-----------------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|-----------------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 1 to 4 | ≤ 4 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +### a) *Transport relation* + +Non-switched circuit termination A and non-switched circuit termination B refer to the names of the two transmission stations in which the circuit is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is dependent on the operation of the circuit which will be indicated by the function code. + +*Geographical area:* the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +### b) *Function code* (format: one to four letters and/or digits): + +Indicates the type of circuit. + +c) *Serial number* (required: one to four digits): + +Identifies the instance of the circuit. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +The designations of the different categories of leased circuits are given below. In special cases in which ITU-T Recommendations do not apply, agreement should be reached between the terminal network operators/service providers. + +## 9.2 Leased circuit interconnections + +### 9.2.1 General + +Leased circuits are fixed circuits for private services or particular purposes. They are distinguished by the letter P. When a leased circuit route includes a transit network, clause 23 applies. + +The designation format for leased circuits is as stated in clause 9.1. Possible function codes are: + +- P for analogue leased circuits used wholly for telephony; +- TP for analogue leased circuits used for voice-frequency telegraphy; +- TDP for analogue leased circuits used for TDM-telegraphy; +- DP for analogue leased circuits used wholly for data transmission; +- FP for analogue leased circuits used wholly for phototelegraphy or facsimile; +- RP for analogue leased unidirectional sound-programme circuits; +- RRP for analogue leased reversible sound-programme circuits; +- VP for analogue leased unidirectional television-programme circuits; +- VVP for analogue leased reversible television-programme circuits; +- XP for analogue leased circuits used for multiple type transmissions; +- NP for digital leased circuits. + +NOTE 1 – In the case of leased circuits connecting three or more locations, the letter M should follow these function codes. + +NOTE 2 – Whether these circuits make use of analogue or digital transmission is not relevant for the above codes; the service is coded. + +NOTE 3 – For digital leased circuits, the actual use is not relevant; all are coded as NP. + +### 9.2.2 Analogue leased circuits used for telephony + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: P. + +*Example:* + +The first analogue leased circuit used for telephony between Paris (France) and Wellington (New Zealand) is designated: + +Paris/AB/FRTE/FRA–Wellington/E2/CLEAR/NZL P1. + +### 9.2.3 Analogue leased circuits used for telegraphy + +#### 9.2.3.1 Voice-frequency telegraphy + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: TP. + +*Example:* + +The first analogue leased circuit used for voice-frequency telegraphy between Bern 1RS and New York 1RC is designated: + +Bern/1RS/CHEPTT/CHE–New York/1RC/ATT/USA TP1. + +#### **9.2.3.2 TDM-telegraphy** + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: TDP. + +*Example:* + +The third analogue leased circuit used for TDM-telegraphy between London (Great Britain) and Montreal (Canada) is designated: + +London/XZ/BTPLC/GBR–Montreal/AB/TGB/CAN TDP3. + +### **9.2.4 Leased telegraph circuits** + +See [ITU-T R.70]. + +### **9.2.5 Analogue leased circuits used for data transmission** + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: DP. + +*Example:* + +The third analogue leased circuit used for data transmission between London and Paris is designated: + +London/AS3/BTPLC/GBR–Paris/HVE/FRTE/FRA DP3. + +### **9.2.6 Analogue leased circuits used for phototelegraphy or facsimile** + +The terminal points of the circuits are arranged in alphabetical order. + +If these circuits are different from P-circuits, the function code is: FP. + +*Example:* + +The second analogue leased circuit used for phototelegraphy between London and Paris is designated: + +London/AS3/BTPLC/GBR –Paris/HVE/FRTE/FRA FP2. + +If normal P-circuits are used, then these circuits are designated accordingly. + +### **9.2.7 Analogue leased circuits used for sound-programme transmission** + +#### **9.2.7.1 Analogue leased unidirectional sound-programme circuit** + +The terminal points of the circuits are arranged in the order corresponding to the direction of transmission (instead of alphabetically, if this is different). + +The function code for these circuits is: RP. + +*Serial numbering:* Circuits which transmit in the direction corresponding to the alphabetical order of the terminals should have odd serial numbers $(2n - 1)$ , circuits in the other direction even numbers $(2n)$ . + +*Examples:* + +The first leased sound-programme circuit transmitting in the direction Montreal to Wellington will be designated: + +Montreal/XX/TGB/CAN–Wellington/E2A/CLEAR/NZL RP1. + +The first leased sound-programme circuit transmitting in the direction Wellington to Montreal will be designated: + +Wellington/E2A/CLEAR/NZL–Montreal/XX/TGB/CAN RP2. + +#### **9.2.7.2 Analogue leased reversible sound-programme circuits** + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: RRP. + +*Example:* + +The first leased circuit with reversible sound-programme transmission between Montreal and Wellington is designated: + +Montreal/XX/TGB/CAN–Wellington/E2A/CLEAR/NZL RRP1. + +### **9.2.8 Analogue leased circuits used for television transmission** + +#### **9.2.8.1 Analogue leased unidirectional television-programme circuits** + +The terminal points of the circuit are arranged in the order corresponding to the direction of transmission (instead of alphabetically, if this is different). + +The function code is: VP. + +*Serial numbering:* Circuits which transmit in the direction corresponding to the alphabetical order of the terminals should have odd serial numbers $(2n - 1)$ , circuits in the other direction even numbers $(2n)$ . + +*Example:* + +The first leased television programme circuit transmitting in the direction Wellington (New Zealand) to Montreal (Canada) will be designated: + +Wellington/E2A/CLEAR/NZL–Montreal/XX/TGB/CAN VP2. + +#### **9.2.8.2 Analogue leased reversible television-programme circuits** + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: VVP. + +*Example:* + +The first circuit with reversible television transmission between Montreal (Canada) and Wellington (New Zealand) is designated: + +Montreal/XX/TGB/CAN–Wellington/E2A/CLEAR/NZL VVP1. + +### **9.2.9 Leased circuits used for digital video transmission** + +These circuits are designated as digital leased circuits (irrespective of the use); see clauses 9.2.15 and 9.2.16. + +### **9.2.10 Analogue leased circuits connecting circuit multiplication terminal equipment at renters' premises** + +These circuits are designated as normal leased circuits. The information indicating that these circuits connect circuit multiplication terminal equipment can be recorded under item 9 (Use) of related information (see clause 10.9). + +Circuits routed via circuit multiplication equipment are also designated as normal circuits. The multiplication equipment appears under item 8 (Equipment information) of related information (see clause 10.8). + +### **9.2.11 Analogue leased circuits used for transmission other than those designated above, or used for combinations of transmissions** + +In this category are circuits used for different transmissions at different times, or circuits in which the bandwidth is divided into two or more bands, thus providing two or more derived circuits which may be used for different transmissions. + +The terminal points of the circuits are arranged in alphabetical order. + +The function code is: XP. + +*Example:* + +Bruxelles/X2E/BGACOM/BEL–Paris/XYZ/FRTE/FRA XP8. + +### **9.2.12 Analogue leased circuits connecting three or more locations** + +Various types and configurations of multi-terminal circuits fall into this category. Each section of the circuit should have a unique designation. A section is any part of the circuit which connects a branching point to either a customer terminal or another branching point. + +Interconnecting sections should use the designation described below. + +The terminal geographical area points of each section are arranged in alphabetical order. + +The function code is formed by adding the letter M to the function codes recommended in clauses 9.2.2 to 9.2.11. This leads, in principle, to the function codes PM, TPM, TDPM, DPM, FPM, RPM, RRPM, VPM, VVPM and XPM. + +The association between sections should be recorded in the related information of each section under item 7 (Association) (see clause 10.7). + +Wholly national sections with national designations may be included if bilaterally agreed. + +*Example:* + +Let there be an interconnecting multiterminal leased circuit connecting Bruxelles (Belgium) and Paris (France) (seventh PM circuit between Bruxelles and Paris) with branches from Bruxelles to Edinburgh (first PM-circuit on this relation) and from Bruxelles to Muenchen (fourth PM-circuit) and with an extension from Paris to Marseille. + +The interconnecting sections are designated: + +Bruxelles/X2E/BGACOM/BEL–Edinburgh/EZC/BTPLC/GBR PM1 + +Muenchen/XFG/DTAG/DEU–Bruxelles/X2E/BGACOM/BEL PM4 + +Bruxelles/X2E/BGACOM/BEL–Paris/X34/FRTE/FRA PM7. + +### **9.2.13 Leased analogue groups, supergroups, etc.** + +These groups, supergroups, etc., will receive a circuit type designation. The additional information on the constitution of these leased groups, supergroups, etc., is to be recorded in related information under item 12 (Bandwidth or bit rate) (see clause 10.12) and under item 6 (Routing) (see clause 10.6). + +The function codes are according to the relevant codes for circuits. + +*Example:* + +A supergroup between renters' premises in London and Paris for data transmission, which is the 15th lease circuit for data transmission on this relation, is designated: + +London/SDE/BTPLC/GBR–Paris/XXC/FRTE/FRA DP15. + +### **9.2.14 Leased analogue group, supergroup links** + +These group and supergroup links will receive a circuit type designation. The additional information on the constitution of these leased group, supergroup links, etc., is to be recorded in related information under item 12 (Bandwidth or bit rate) (see clause 10.12) and under item 6 (Routing) (see clause 10.6). + +*Example:* + +A group link provided between renters' premises in London and Montreal devoted to data transmission, which is the tenth leased circuit for data transmission on this relation, is designated: + +London/SDE/BTPLC/GBR–Montreal/XNC/TGB/CAN DP10. + +### **9.2.15 Digital leased circuits connecting two locations** + +Designations given below also apply for leased digital blocks and paths. + +NOTE 1 – For digital leased circuits, the use of the circuit will no longer be taken into account for the designation: the use may change without notification to the network operator/service provider or may be unknown. + +The additional information concerning the bit rate is to be found in related information under item 12 (Bandwidth or bit rate) (see clause 10.12). + +The terminations of the circuit are placed in alphabetical order. + +The function code is: NP. + +*Example:* + +The fifth digital leased circuit between Birmingham and Toulouse is designated: + +Birmingham/X2E/BTPLC/GBR–Toulouse/TYU/FRTE/FRA NP5. + +NOTE 2 – It may happen that a digital leased circuit has been routed via one or more exchanges; in this case, they are designated as normal digital leased circuits. However, in such cases, an exchange suffix may replace the transmission station suffix. The information concerning the permanent switched mode is recorded in related information under item 8 (Equipment information) (see clause 10.8). + +*Example:* + +The twelfth digital leased circuit between users' premises in Athens and Reims, which is connected to transmission station TS2 in Athens and permanently switched in the exchange IP2 in Reims, is designated: + +Athinai/TS2/CDE/OTE/GRC–Reims/IP2/CCV/FRTE/FRA NP12. + +### **9.2.16 Digital leased circuits connecting three or more locations** + +Various types and configurations of multiterminal circuits fall into this category. Each section of the circuit should have a unique designation. A section is any part of the circuit which connects a branching point to either a customer terminal or another branching point. (See also [ITU-T M.1055].) + +Sections should use the designation described below. + +The terminal points of each section are arranged in alphabetical order. + +The function code is formed by adding the letter M to the function code recommended in clause 9.2.15, i.e., the function code is: NPM. + +The association between sections should be recorded in the related information of each section under item 7 (Association) (see clause 10.7). + +Wholly national sections with national designations may be included if bilaterally agreed. + +*Example:* + +In a digital multiterminal leased circuit connecting Oslo, London, Paris, Rome and Amsterdam, the section between Oslo and London (being the first NPM circuit on this relation) is designated: + +London/23R/BTPLC/GBR–OsloVPE/TELNOR/NOR NPM1. + +## **9.3 Fixed (non-switched) public circuits** + +### **9.3.1 General** + +The designation format is according to clause 9.1. When a fixed public circuit route includes a transit network, clause 18 applies. Possible function codes are: + +- R for a unidirectional sound-programme circuit; +- RR for a reversible sound-programme circuit; +- RK for telephone type circuits for narrow-band sound-programme transmission; +- V for a unidirectional television circuit; +- VV for a reversible television circuit; +- F for a phototelegraphy or facsimile circuit; +- T for circuits providing voice-frequency telegraph links; +- TD for circuits providing TDM-telegraph systems; +- D for data transmission circuits; +- DL for circuits providing transfer links for common channel signalling systems. + +NOTE – Information on whether a sound-programme circuit together with a second sound-programme circuit form a stereophonic pair will be recorded in the related information under the item 7 (Association) (see clause 10.7). + +### **9.3.2 Circuits used for sound-programme transmission** + +#### **9.3.2.1 Circuits used for unidirectional sound-programme transmission** + +The terminations of the circuit are arranged in the order corresponding to the direction of transmission (instead of alphabetically, if this is different). + +The function code is: R. + +*Serial numbering:* Circuits which transmit in the direction corresponding to the alphabetical order of the terminals should have odd serial numbers $(2n - 1)$ . Circuits which transmit in the direction corresponding to the inverse alphabetical order of the terminals should have even serial numbers $(2n)$ . + +*Example:* + +The first circuit transmitting in the direction Wellington to Montreal is designated: + +Wellington/FT3/CLEAR/NZL–Montreal/NT4/TGB/CAN R2. + +#### **9.3.2.2 Circuits used for reversible sound-programme transmission** + +The terminations of the circuit are arranged in alphabetical order. + +The function code is: RR. + +*Example:* + +The first circuit with reversible sound-programme transmission between Montreal and Wellington is designated: + +Montreal/NT4/TGB/CAN–Wellington/FT3/CLEAR/NZL RR1. + +#### **9.3.2.3 Telephone-type circuits used for narrow-band sound-programme transmission** + +In the traffic relation, the terminals of the circuit are arranged in the order corresponding to the direction of operation (instead of alphabetically, if this is different). + +The function code is: RK. + +*Serial numbering:* Circuits which transmit in the direction corresponding to the alphabetical order of the terminals should have odd serial numbers $(2n - 1)$ . Circuits which transmit in the direction corresponding to the inverse alphabetical order of the terminals should have even serial numbers $(2n)$ . + +*Example:* + +The first telephone-type circuit set up for the narrow-band sound-programme transmission in the direction from Milano to Madrid is designated: + +Milano/TY5/TI/ITA–Madrid/M2Z/TFCAES/ESP RK2. + +### **9.3.3 Circuits used for television transmission** + +#### **9.3.3.1 Circuits used for unidirectional television transmission** + +In the traffic relation, the terminations of the circuit are arranged in the order corresponding to the direction of transmission (instead of alphabetically, if this is different). + +The function code is: V. + +*Serial numbering:* Circuits which transmit in the direction corresponding to the alphabetical order of the terminals should have odd serial numbers $(2n - 1)$ . Circuits which transmit in the direction corresponding to the inverse alphabetical order of the terminals should have even serial numbers $(2n)$ . + +*Example:* + +The first unidirectional television circuit transmitting in the direction Paris to Helsinki is designated: +Paris/FRU/FRTE/FRA–Helsinki/2R5/SONERA/FIN V2. + +#### **9.3.3.2 Circuits used for reversible television transmission** + +The terminations of the circuit are arranged in alphabetical order. + +The function code is: VV. + +*Example:* + +The first reversible television transmission circuit between Tokyo TS1 and New Delhi is designated: +New Delhi/RT/VSNL/IND–Tokyo/TS1/UUE/NTT/JPN VV1. + +### **9.3.4 Circuits for digital audio and video transmission** + +These circuits are designated according to the data transmission system, see clause 17. + +### **9.3.5 Telephone-type circuits used for phototelegraphy or facsimile** + +Circuits used for phototelegraphy or facsimile which are different from normal telephone circuits will have the function code: F. + +The terminal points of the circuit are arranged in alphabetical order. + +If normal telephone circuits are used, they are designated accordingly. Information about the usage may be recorded in the related information under item 9 (Use) (see clause 10.9). + +*Example:* + +The first circuit for phototelegraphy between Koebenhavn and Tokyo: + +Koebenhavn/XCR/TD/DNK–Tokyo/4T5/NTT/JPN F1. + +### **9.3.6 Telephone-type circuits used to provide voice-frequency telegraph links** + +The terminal points of the circuit are arranged in alphabetical order. + +The function code is: T. + +*Example:* + +The first circuit to provide a voice-frequency telegraph link between Koebenhavn 1 and Montreal 1TE is designated: + +Koebenhavn/1/TD/DNK–Montreal/1TE/TGB/CAN T1. + +A reserve T-circuit is designated according to its present function. Information concerning the nature of the reserve T-circuit is found in the related information under item 7 (Association) (see clause 10.7). + +### **9.3.7 Telephone-type circuits used to provide time division multiplex (TDM) telegraph systems** + +The terminal points of the circuit are arranged in alphabetical order. + +The function code is: TD. + +*Example:* + +The first circuit to provide a TDM-telegraph system between London Keybridge and Montreal 1TE: + +London/KB/BTPLC/GBR–Montreal/1TE/TGB/CAN TD1. + +(Suffixes are optional.) + +A reserve TD-circuit is designated according to its present function. Information concerning the nature of the reserve TD-circuit is found in the related information under item 7 (Association) (see clause 10.7). + +### **9.3.8 Telephone-type circuits used for data transmission** + +The terminal points of the circuit are arranged in alphabetical order. + +The function code is: D. + +*Example:* + +The first circuit used for data transmission between Frankfurt 1 and Toronto 1TE is designated: + +Frankfurt/1/DTAG/DEU–Toronto/1TE/SCNM/CAN D1. + +### **9.3.9 Telephone-type circuits used as transfer links for common channel Signalling Systems No. 6 and No. 7** + +The terminal points of the circuit are arranged in alphabetical order. + +The function code is: DL. + +*Example:* + +The first data link used for common channel signalling between Sacramento 4ESS and Tokyo Shinjuku is designated: + +Sacramento/4ES/ATT/USA–Tokyo/SJK/NTT/JPN DL1. + +## 9.4 Related information + +The additional information on fixed circuits is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) composition of transmission; +- 12) bandwidth or bit rate; +- 13) signalling type; +- 14) applicable ITU-T Recommendations. + +The various items will be dealt with in clause 10. + +## 10 Related information for fixed circuit interconnections + +The following subclauses explain the items of related information concerned with fixed circuit interconnections. A full example for the designation information of an interconnecting leased analogue circuit is given in clause A.2. + +### 10.1 Urgency for restoration [item 1] + +This item supplies information on the urgency of restoration of the circuit based upon bilateral agreement between the terminal network operators/service providers. + +*Format:* + +1. xxx . . . xx; (maximum ten characters) + +*Illustration:* + +- a) if the priority is top: 1; +if the priority is second: 2; +if the priority is third: 3; or +- b) if repair is required within, e.g., 24 hours: $\leq 24$ h; or +- c) if no urgency has to be indicated: –; + +NOTE – In the case of a digital leased circuit, the priority or urgency may be decided upon by taking into account the bit rate of the circuit. + +## 10.2 Terminal countries [item 2] + +This item presents the countries in which the circuit is terminating. + +*Format:* + +2. XXX, YYY; (three characters for each) + +*Specification:* + +XXX: code for country of Geographical Area A + +YYY: code for country of Geographical Area B + +NOTE – The alpha-3 codes are according to [ISO 3166-1]. + +*Example:* + +For the circuit Paris/RE3/FRTE/FRA–Wellington/YBC/CLEAR/NZL P1: + +2. FRA, NZL; + +## 10.3 Names of network operators/service providers [item 3] + +This item records the names of the network operators/service providers which operate the circuit or, in the case of sound-programme and television circuits, the name of the broadcasting company. The applicable carrier codes can be selected from the ITU-T List of ITU Carrier Codes [ITU-T Carrier]. + +*Format:* + +3. YYYYYY, ZZZZZZ; (maximum six characters for each) + +*Specification:* + +YYYYYY: code for company operating in Geographical Area A + +ZZZZZZ: code for company operating in Geographical Area B + +*Example:* + +For the circuit Bern/IRS/CHEPTT/CHE–NewYork/1RC/MCI/USA TP1 operated by Radio Suisse and RCA: + +3. RS, MCI; + +## 10.4 Control station (sub-control station(s)) [item 4] + +This item lists the appointed control station and sub-control stations (according to [ITU-T M.80] and [ITU-T M.90] or [ITU-T M.1012] and [ITU-T M.1013] for leased circuits). Further details about the stations can be found in the list of contact points ([ITU-T M.1510]). + +*Format:* + +4. CS: designation of control station, +SCS1: designation of sub-control station, +SCS2: designation of sub-control station, +M M +SCSn: designation of sub-control station. + +*Specification:* + +- CS: designation of the control station, +SCS1: designation of the terminal sub-control station, + +SCS2 to SCSn: if applicable, other sub-control stations have to be placed in the geographical order according to the traffic relation. + +*Example:* + +For the circuit London/KB/BTPLC/GBR–Paris/ARC/FRTE/FRA RP1 where Paris Archives is the control station and London Keybridge is the sub-control station: + +4. CS: Paris/ARC/FRTE/FRA, +SCS1: London/KB/BTPLC/GBR. + +### 10.5 Fault report points [item 5] + +This item presents the names of both fault report points on the circuit. Further information about the fault report points can be found in the list of contact points [ITU-T M.1510]). + +*Format:* + +5. Designation of fault report point, designation of fault report point. + +*Specification:* + +The first fault report point is that of the country of Geographical Area A. + +The second fault report point is that of the country of Geographical Area B. + +*Example:* + +The fault report points for the circuit Athinai/NXQ/OTE/GRC–Roma DP3/TI/ITA: + +5. Athinai/TSB/OTE/GRC, Roma/TS1/TI/ITA. + +### 10.6 Routing [item 6] + +This item shows the interconnecting primary group(s) or primary block(s) and the channel number(s) which carry the circuit (see Notes 1 and 2). If there is more than one, the groups or blocks appear in the geographical order from Geographical Area A to Geographical Area B. + +*Format:* + +6. Designation of an interconnecting primary group (Note 1) or primary block/channel number, designation of a primary group or block/channel number, ..., designation of a primary group or block/channel number; + +*Example 1:* + +For the circuit from London Mollison to Paris Archives DP7: + +6. London/MOL/BTPLC/GBR–Paris/ARC/FRTE/FRA 1204/4; + +*Example 2:* + +For the wideband circuit Frankfurt–London DP5: + +6. Amsterdam/PR1/TCOMNL/NLD–Frankfurt/ABC/DTAG/DEU 6005/2, +Amsterdam/PR1/TCOMNL/NLD–London/XYZ/BTPLC/GBR 6002/3; + +NOTE 1 – In the case where a leased circuit consists of a group or block, the primary groups or blocks are to be replaced by the next higher groups or blocks. In this case, the channel numbers are to be replaced by the group numbers. + +NOTE 2 – Primary groups or blocks can be unidirectional as well. Two consecutive unidirectional groups or blocks are separated by a + sign instead of a comma. + +## 10.7 Association [item 7] + +This item informs whether there are associated circuits and, if so, of what nature. + +*Format:* + +7. Association code: Designation(s) of associated circuit(s); + +*Specification:* + +If the circuit *has* a reserve circuit, the association code is: S. This is followed by the function code and the serial number of the principal circuit. + +NOTE 1 – In this case, the designation of the associated circuit may be replaced by the designation of a free time slot or a free channel. + +If the circuit is a reserve circuit, the association code is: function code followed by S and this is the serial number of the reserve circuit. + +If a circuit must have diverse routing with respect to another circuit, the association code is: DVR. This is followed by the designation of the other circuit. + +If the circuit is one of a stereophonic pair, the other circuit will appear in this item. The association code is: H followed by a two-digit serial number indicating the number of the stereophonic pair. This is followed by the function code and the serial number of the actual circuit. + +If the circuit belongs to a multiterminal leased circuit, the association code is: PM, DPM, etc., (see clauses 9.2.12 and 9.2.16) and this is followed by the serial number of the circuit. + +*Example 1:* + +7. ST1: Roma/AS1/TI/ITA–Zurich/SEL/CHEPTT/CHE Z13; +which indicates that the reserve circuit for the principal circuit T1 is Roma/AS1/TI/ITA–Zurich/SEL/CHEPTT/CHE Z13. + +In the case of a free channel in the group Roma/AS1/TI/ITA–Zurich/SEL/CHEPTT/CHE 1205: + +7. ST1: Roma/AS1/TI/ITA–Zurich/SEL/CHEPTT/CHE 1205/6; + +*Example 2:* + +The two leased circuits Kolding/PTY/DTAG/DEU–Lausanne/CHEPTT/CHE DP and Geneve/RT1/CHEPTT/CHE–Koebenhavn/IVT/TD/DNK DP18 must have diverse routing. + +For the first circuit Kolding/PTY/DTAG/DEU–Lausanne/CHEPTT/CHE DP7: + +7. DVR: Geneve/RT1/CHEPTT/CHE–Koebenhavn/IVT/TD/DNK DP18; + +*Example 3:* + +If the circuit London/KB/BTPLC/GBR–Paris/ARC/FRTE/FRA R1 is bearing one channel of the second stereophonic pair from London to Paris, and + +London/KB/BTPLC/GBR–Paris/ARC/FRTE/FRA R5 is bearing the other channel of this pair: + +7. H02R1: London/KB/BTPLC/GBR–Paris/ARC/FRTE/FRA R5; +which indicates that circuit R1, being one of the stereophonic pair number 2, has as the other circuit of this pair: London/KB/BTPLC/GBR–Paris/ARC/FRTE/FRA R5. + +*Example 4:* + +If the circuit Bruxelles/Z5A/BGACOM/BEL–Edinburgh PM1/BTPLC/GBR is a part of an interconnecting multiterminal telephone circuit connecting Bruxelles and Paris (being the seventh PM-circuit on that relation) with branches from Bruxelles to Edinburgh and to Aachen (being the second PM-circuit on that relation) and with an extension from Paris to Marseille, then for the circuit Bruxelles/Z5A/BGACOM/BEL–Edinburgh PM1/BTPLC/GBR: + +7. PM1: Aachen/EB/DTAG/DEU–Bruxelles/Z5A/BGACOM/BEL PM2, +Bruxelles/Z5A/BGACOM/BEL–Paris/UV/FRTE/FRA PM7; + +NOTE 2 – The interconnecting branches may appear in any order. Intraconnecting branches may be added after bilateral agreement. + +## **10.8 Equipment information [item 8]** + +This item records any equipment in the circuit which requires special maintenance attention. + +*Format:* + +8. XX, XX, XX, XX, XX; + +*Specification:* + +If the circuit has been routed via digital circuit multiplication equipment: AM + +If the circuit has been routed via digital circuit multiplication equipment + +- using reduced bit rate encoding: RB +- using speech interpolation: SI + +If the circuit has a compandor: CO + +If the circuit consists of a semi-permanent switched connection: SP + +NOTE – If there is a need to record additional special equipment, additional codes can be used by bilateral agreement between the network operators/service providers. The codes must be unique and shall have two characters. + +## **10.9 Use [item 9]** + +This item identifies for what purpose the circuit is used (if this is known by the network operator/service provider and of use for maintenance). + +*Format:* + +9. XXX .. XX; (maximum seven characters) + +*Specification:* + +XX .. XX allows the record of the usage of the circuit. A comma may be included anywhere to separate two or more codes, in the case that the circuit has two or more simultaneous usages. + +If the circuit has been provided with circuit multiplication equipment at renters' premises with connection channels: CC. + +If the circuit is used for the COMFAX service: CFX. + +## **10.10 Transmission medium information [item 10]** + +This item identifies whether a particular transmission medium is required in the routing of the circuit. + +*Format:* + +10. ST: XX ... XX; or 10. NS: XX ... XX; or 10. –; (XX ... XX maximum ten characters) + +*Specification:* + +If the circuit has to be routed via satellite: ST followed by the designation of the satellite. + +If the circuit must not be routed via satellite: NS followed by the designation of the terrestrial transmission medium. + +If there is no transmission medium requirement: —. + +*Example:* + +For the circuit London/XYZ/BTPLC/GBR–Paris/ARC/FRTE/FRA DP3 that has to be routed via satellite Telecom 1: + +10. ST: Tel 1. + +### **10.11 Composition of the transmission [item 11]** + +This item shows the type of transmission on the circuit. + +*Format:* + +11. A; N; or C; + +*Specification:* + +If the transmission is analogue: A + +If the transmission is digital: N + +If the transmission is mixed analogue/digital: C + +### **10.12 Bandwidth or bit rate [item 12]** + +This item shows the bandwidth (in the case of an analogue circuit or mixed circuit) or the bit rate (in the case of a digital circuit). + +*Format:* + +12. xxxx.x Hz; or kHz; or MHz; bit/s; or kbit/s; or Mbit/s; + +Rules for the notation of the figures: + +Leading zeroes may be omitted, and if the decimal is a zero, this decimal and the decimal point may also be omitted. + +If the figure is up to 999, use Hz, bit/s. + +If the figure is between 1000 and 9 999 999, use kHz, kbit/s. + +If the figure is 10 000 000 or more, use MHz, Mbit/s. + +*Specification:* + +If the circuit is analogue or mixed analogue/digital: the bandwidth Hz, kHz, MHz. + +If the circuit is digital: the bit rate in bit/s, kbit/s, Mbit/s. + +*Example:* + +For the circuit Bordeaux/ZZ/FRTE/FRA–Darmstadt/RA/DTAG/DEU NP7 with a bit rate of 64 kbit/s: + +12. 64 kbit/s. + +### **10.13 Signalling type [item 13]** + +This item presents the signalling type that applies to the circuit (reference is made to [ITU-T M.1045] and [ITU-T Q.8]). + +*Format:* + +13. xxxxxx; (maximum seven characters) + +*Specification:* + +If the signalling is of the type xxxx Hz/xx Hz: xxxx/xx. Otherwise, the characters can be used on the basis of bilateral agreement between the two terminal network operators/service providers. + +*Example:* + +For a circuit with in-band signalling 1000 Hz/20 Hz: + +13. 1000/20. + +### **10.14 Applicable ITU-T Recommendations [item 14]** + +This item records the ITU-T Recommendation(s) applied as regards the parameters of the circuit. + +*Format:* + +14. Rec. ITU-T X.xxxx, Rec. ITU-T Y.yyyy; or 14. Rec. ITU-T X.xxxx; or 14. –; + +*Specification:* + +The number of Recommendations to be recorded (2, 1, or 0) is dependent on the need. + +*Example 1:* + +If the circuit is an analogue leased line: + +14. Rec. [ITU-T M.1020]; + +*Example 2:* + +If the circuit is used for the COMFAX (CFX) service: + +14. [ITU-T F.162], [ITU-T F.163]; + +## **11 Designations of group, supergroup, etc. (bidirectional and unidirectional) interconnections** + +### **11.1 General** + +The format of the designation of groups, etc., is shown in Table 4. When a group, supergroup, etc., route includes a transit network, clause 23 applies. + +**Table 4 – Group designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | / | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 1 to 6 | 2 to 3 | + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Group termination A and group termination B refer to the names of the two transmission stations in which the group, etc., is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. For multiple destination unidirectional groups, the name of Geographical Area B is replaced by (MU) (see clause 11.3.1). + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: ISO 3166-1 alpha-3 code. + +b) *Function code* (format: one to six letters and/or digits) + +This code consists of the nominal number of channels in the group (see Note). In the case of a unidirectional single destination group, the number is preceded by (U) (see clause 11.3.2). + +NOTE – Where group, supergroup, etc., links are directly interfaced by analogue to digital conversion equipment, the number of channels is followed by the letter C (see clause 16). + +c) *Serial number* (required: two to three digits) + +Identifies the instance of the group, etc. The serial numbering starts anew if there is a difference in transport relation and/or function code. The numbering of a group, supergroup, etc., is applied between the point where the group, etc., is assembled to the point where it is broken down, independently of the position it occupies in the band of line frequencies. + +If the number is less than 10, it is preceded by a zero. + +## 11.2 Bidirectional groups, etc. + +### 11.2.1 Group + +The function code is a number that indicates the nominal number of channels in the group, as follows: + +8 for 8-channel groups, +12 for 12-channel groups, +16 for 16-channel groups. + +*Example:* + +The third 12-channel group between Moskva and New York is designated: +Moskva/3RA/ROSTEL/RUS–New York/WXX/ATT/USA 1203. + +### **11.2.2 Supergroup** + +The function code is a number that indicates the nominal number of channels in the supergroup, as follows: + +60 for 60-channel supergroups. +80 for 80-channel supergroups. + +*Example:* + +The first 60-channel supergroup between London and Amsterdam is designated: +Amsterdam/PRR/TCOMNL/NLD–London/XXC/BTPLC/GBR 6001. + +### **11.2.3 Mastergroup** + +The function code is: 300. + +*Example:* + +The first mastergroup between Bruxelles and London is designated: +Bruxelles/XYZ/BGACOM/BEL–London/FGH/BTPLC/GBR 30001. + +### **11.2.4 Supermastergroup** + +The function code is: 900. + +*Example:* + +The tenth supergroup between Amsterdam and Paris is designated: +Amsterdam/EVR/TCOMNL/NLD–Paris/ARC/FRTE/FRA 90010. + +### **11.2.5 Use of the groups, etc.** + +This information will be contained in related information under item 9 (Use) (see clause 13.9). If groups are used for private purposes, see clause 9.2.13. + +### **11.2.6 Restoration groups and supergroups** + +Groups and supergroups set up on restoration groups and supergroups, or on spare groups and supergroups for restoration purposes, will receive a serial number from the 800 series, in descending order and starting from 899. + +Restoration groups: 8899, 8898, 8897, etc. +12899, 12898, 12897, etc., or +16899, 16898, 16897, etc., as appropriate. +Restoration supergroups: 60899, 60898, 60897, etc. + +*Example 1:* + +The second 12-channel restoration group between London and Sydney is designated: +London/CVB/BTPLC/GBR–Sydney/VRV/TELSTR/AUS 12898. + +*Example 2:* + +The first restoration supergroup between Amsterdam and Bruxelles is designated: +Amsterdam/EVT/TCOMNL/NLD–Bruxelles/1WZ/BGACOM/BEL 60899. + +### 11.3 Unidirectional groups and supergroups + +#### 11.3.1 Multiple destination unidirectional groups and supergroups + +The unidirectional route will be designated by the name of the sending terminal station (in the general format: Geographical Area A) followed by a hyphen, and the letters MU (multiple destination unidirectional) in parentheses replace Geographical Area B. This will be followed by the function code and serial number of the group or supergroup. + +*Example 1:* + +The first multiple destination unidirectional supergroup from London (to, for example, Bogota, Lusaka and Montreal) is designated: + +London/ERT/BTPLC/GBR–(MU) 6001. + +The next such supergroup from the same point of origin to any destination would take the next number in the series, e.g., the second supergroup from London is designated: + +London/ERT/BTPLC/GBR–(MU) 6002. + +This supergroup might go, for example, to Tokyo, Hawaii and Melbourne. + +*Example 2:* + +The first supergroup from Montreal (to, for example, London, Lusaka and Paris) is designated: + +Montreal/5TC/TGB/CAN–(MU) 6001. + +NOTE – Groups and supergroups routed via a multiple-access system may be provided for exclusive use between two terminal stations only, in which case the normal designations given above in this Recommendation will apply. + +#### 11.3.2 Single destination unidirectional groups and supergroups + +The unidirectional route will be designated by the name of the sending terminal station (in the general format: Geographical Area A) followed by a hyphen and the name of the receiving terminal station (Geographical Area B). The function code consists of the letter U (unidirectional) in parentheses and the nominal number of channels of the group or supergroup. + +*Example:* + +A unidirectional group transmitting in the direction from Paris to London, which, in the reverse direction of transmission, is assigned to a multiple destination unidirectional (MU) group from London to Paris and Rio de Janeiro, would be designated as: + +Paris/ARC/FRTE/FRA–London/VRT/BTPLC/GBR (U) 1201. + +The next group between these locations, Paris and London, if bidirectional, would be designated in the normal manner as: + +London/VRT/BTPLC/GBR–Paris 1202. + +NOTE – Groups and supergroups routed via a multiple-access system may be provided on a bidirectional basis for exclusive use between two terminal stations only, and in this case the normal designations given above in this Recommendation will apply. + +## 11.4 Related information + +The additional information on groups, etc., is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bandwidth; +- 13) occupancy. + +The various items will be dealt with in clause 13. + +## 12 Designations of group link, supergroup link and line link interconnections + +### 12.1 Group and supergroup links + +Group links and supergroup links are designated according to the general format for groups (see clause 11.1). In practice, it may be that terminal equipment is not connected to a group link or supergroup link. Nevertheless, for designation purposes, the link will be numbered as though terminal equipment were connected. + +#### 12.1.1 Conventional links not connected to their terminal equipment + +Such links are included in the normal numbering sequence of groups and supergroups and are not given a separate numbering sequence. + +When a group link or supergroup link is used only part time with terminal translating equipment (to provide a conventional group or supergroup), it will be designated in the normal way. The part time condition of the group link has to be indicated in related information under item 9 (Use) (see clause 13.9). + +*Example:* + +The group link between Amsterdam and London set up following 5 groups already in service, is designated: + +Amsterdam/VRT/TCOMNL/NLD–London/B1C/BTPLC/GBR 1206. + +### 12.1.2 Restoration links + +Group links and supergroup links nominated for restoration purposes will receive a serial number from the 800-series in ascending order and starting from 801. + +Restoration group links: 12801, 12802, 12803, etc. + +Restoration supergroup links: 60801, 60802, 60803, etc. + +*Example:* + +The second restoration group link between Hong Kong and Sydney is designated: + +Hong Kong/33R/CWHKTI/HKG–Sydney/12R/TELSTR/AUS 12802. + +NOTE – The first two digits (e.g., 12) in the designation of a restoration group link do not necessarily indicate the number of channels in the group which is set up via the link. For example, a restoration group link London/1VT/BTPLC/GBR–Montreal/RST/TGB/CAN 12801 might be used to restore the group London/1VT/BTPLC/GBR–Montreal/RST/TGB/CAN 1605. + +### 12.2 Line links + +The format of the designation of line links is shown in Table 5. + +**Table 5 – Line link designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | / | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 3 to 5 | 2 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Group termination A and group termination B refer to the names of the two transmission stations in which the group, etc., is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area:* the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: three to five letters and/or digits) + +This code consists of a number indicating the nominal telephone channel transmission capacity followed by the letter A. + +- c) *Serial number* (required: two digits) + +Identifies the instance of the group link, etc. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example 1:* + +The first 1840 telephone channel capacity line link between Beaver Harbour and Widemouth is designated: + +Beaver Harbo/23R/TGB/CAN–Widemouth/45T/BTPLC/GBR 1840A01. + +*Example 2:* + +The first 432 telephone channels capacity line link between London and Pleumeur-Bodou is designated: + +London/3ER/BTPLC/GBR–Pleumeur-Bod/DFC/FRTE/FRA 432A01. + +NOTE – Line links are sometimes characterized by having channel capacities not in accordance with normal group, supergroup, etc., alignments. Examples of these non-standard capacities may often be found in submarine cable or satellite line links. These links will be numbered in accordance with the nominal channel capacity of the link. + +### 12.3 Related information + +The additional information on group links, supergroup links and line links is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bandwidth; +- 13) occupancy (this item is not in use for group links and line links). + +The various items will be dealt with in clause 13. + +### 13 Related information for group, group link and line link interconnections + +The following subclauses explain the items of related information concerned with group, group link, line link, etc., interconnections. Full examples for the designation information of an interconnecting group and an interconnecting group link are given in clause A.3. + +### 13.1 Urgency for restoration [item 1] + +This item supplies information on the urgency of restoration of the group/group link based upon bilateral agreement between the terminal network operators/service providers. + +*Format:* + +1. xxx xx; (maximum ten characters) + +*Illustration:* + +- a) if the priority is top: 1; +if the priority is second: 2; +if the priority is third: 3; or +- b) if repair is required within, e.g., 24 hours: $\leq 24$ h; or +- c) if no urgency has to be indicated: –; + +*Example:* + +If the group Bonn/RFT/DTAG/DEU–Paris/ARC/FRTE/FRA 1201 needs top priority restoration: + +1. 1; + +### 13.2 Terminal countries [item 2] + +This item presents the countries in which the group/group link is terminating. + +*Format:* + +2. XXX, YYY; or XXX; (three characters for each) + +*Specification:* + +XXX: code for country of Geographical Area A + +YYY: code for country of Geographical Area B + +In the case of a multiple destination unidirectional group (MU), only XXX applies. + +*Example 1:* + +For the group Beograd/RED/YUGTEL/YUG–Roma/EDD/TI/ITA 1201: + +2. YUG, ITA; + +*Example 2:* + +For the multiple destination group Toronto/34R/TGB/CAN–(MU) 1202: + +2. CAN; + +*NOTE* – The alpha-3 codes are according to [ISO 3166-1]. + +### 13.3 Names of network operators/service providers [item 3] + +This item records the names of the carriers, etc., which operate the group/group link. The applicable carrier codes can be selected from the List of ITU Carrier Codes as described in clause 6.4. + +*Format:* + +3. XXXXXX, YYYYYY; or XXXXXX; (maximum six characters for each) + +*Specification:* + +XXXXXX: name of company in Geographical Area A + +YYYYYY: name of company in Geographical Area B + +In the case of a unidirectional multiple destination, only XXXXXX applies. + +*Example 1:* + +For the supergroup Amsterdam/E1R/TCOMNL/NLD–London/ERT/BTPLC/GBR 6002: + +3. TCOMNL, BTPLC; + +*Example 2:* + +For the multiple destination group Hong Kong/WXX/CWHKTI/HKG–(MU) 1201: + +3. CWHKTI. + +### **13.4 Control station sub-control station(s) [item 4]** + +This item lists the appointed control station and sub-control stations (according to [ITU-T M.80] and [ITU-T M.90]). Further details about the stations can be found in the list of contact point [ITU-T M.1510]). + +*Format:* + +4. CS: designation of control station, +SCS1: designation of sub-control station, +SCS2: designation of sub-control station, +M M +SCSn: designation of sub-control station. + +or in the case of a multiple destination unidirectional group: + +4. CS: designation of control station, + +*Specification:* + +- CS: designation of the control station, +SCS1: designation of the terminal sub-control station, +SCS2 to SCSn: if applicable, other sub-control stations have to be placed in the geographical order according to the traffic relation. + +In the case of a multiple destination unidirectional group, only CS applies. + +*Example 1:* + +For a group Helsinki/TM1/SONERA/FIN–Paris/ARC/FRTE/FRA 1201 where the control station is Helsinki TM1 and the sub-control station is Paris Archives: + +4. CS: Helsinki/TM1/SONERA/FIN, +SCS1: Paris/ARC/FRTE/FRA; + +*Example 2:* + +For the multiple destination unidirectional group Wien/ARS/RSLCOM/AUT–(MU) 1201: + +4. CS: Wien/ARS/RSLCOM/AUT; + +### **13.5 Fault report points [item 5]** + +This item presents the names of both fault report points on the group/group link (according to [ITU-T M.2130]). Further details about the fault report points can be found in the list of contact points [ITU-T M.1510]. + +*Format:* + +5. Designation of fault report point, designation of fault report point; +or +5. Designation of fault report point; + +*Specification:* + +The first fault report point is that of the country of Geographical Area A. The second fault report point is that of the country of Geographical Area B. In the case of a multiple destination unidirectional group, there is only one fault report point under item 5. + +*Example 1:* + +For the group Moskva/MNA/ROSTEL/RUS–Paris/ARC/FRTE/FRA 1201: + +5. Moskva/MNA/ROSTEL/RUS, Paris/ARC/FRTE/FRA; + +*Example 2:* + +For the multiple destination unidirectional group Caracas/TS1/CANTV/VEN–(MU) 1201: + +5. Caracas/TS1/CANTV/VEN; + +### **13.6 Routing [item 6]** + +This item records the next higher group within the multiplex hierarchy on which the group/group link has been routed and the position number, or in the case of the highest multiplex level, the transmission media on which the group/group link has been routed. + +*Format:* + +6. Designation of an interconnecting group/position number or designation of transmission medium, designation of an interconnecting group/position number or designation of transmission medium, ..., designation of an interconnecting group/position number or designation of transmission medium; + +NOTE – Two consecutive unidirectional groups are separated by a + sign instead of a comma. + +*Specification:* + +The designation of an interconnecting group refers to the next higher level in the multiplex hierarchy. If there is more than one, the groups are noted in geographical order from Geographical Area A to Geographical Area B. + +The designation of the transmission medium refers to the transmission medium leaving the country of Geographical Area A and to the transmission medium entering the country of Geographical Area B, respectively. + +As no ITU-T designations of transmission media are provided for the time being, the terminal countries should provide designations or agree on designations. + +If there is only one transmission medium, the designation of this medium applies. + +*Example 1:* + +A group Alger/5RT/PTT/DZA–London/34R/BTPLC/GBR 1201 has been routed between operators as follows: + +6. Alger/5RT/PTT/DZA–Paris/ARC/FRTE/FRA 6002/2, +London/34R/BTPLC/GBR–Paris/ARC/FRTE/FRA 6040/5; + +*Example 2:* + +A supermaster group Barcelona/WSX/TFCAES/ESP–Perpignan/EST/FRTE/FRA 90001 has been routed as follows: + +6. Gerona/EB2/TFCAES/ESP–Perpignan/EST/FRTE/FRA 1800A08; + +*Example 3:* + +A group Caracas/24E/CANTV/VEN–Paris/ARC/FRTE/FRA 1201 has been routed as follows: + +6. Caracas/24E/CANTV/VEN–Paris/ARC/FRTE/FRA 6001/2+Caracas–(MU) 6002/3; + +### 13.7 Association [item 7] + +This item informs whether there are associated group/group links and if so, of which nature. + +*Format:* + +7. Association code: designation(s) of the associated group(s) or group link(s); + +*Specification:* + +If the group *has* a reserve group, the association code is: S followed by the function code and the serial number of the group. + +If the group *is* a reserve group, the association code is: function code followed by S and the serial number of the reserve group. + +The same applies for group links. + +*Example:* + +If the normal group is Bruxelles/EDC/BGACOM/BEL–Luxembourg/EXX/LUXPT/LUX 1215 and if the group Bruxelles/EDC/BGACOM/BEL–Luxembourg/EXX/LUXPT/LUX 12899 serves as a restoration group for the group Bruxelles/EDC/BGACOM/BEL–Luxembourg/EXX/LUXPT/LUX 1215: + +7. S1215: Bruxelles/EDC/BGACOM/BEL–Luxembourg/EXX/LUXPT/LUX 12899; + +For the group Bruxelles–Luxembourg 12899 there has to be recorded under item 7: + +7. 12S899: Bruxelles/EDC/BGACOM/BEL–Luxembourg/EXX/LUXPT/LUX 1215; + +### 13.8 Equipment information [item 8] + +This item records information on equipment in the group/group link which requires special maintenance attention. + +*Format:* + +8. XX, XX, XX, XX; + +*Specification:* + +If the group is carrying companded circuits: CO + +If a group has been routed via TDMA: TD + +If there is no special equipment: – + +NOTE – If there is a need to record any additional equipment information, the free codeplaces are available for that purpose. The codes to be used must consist of two characters, be unique and can be chosen by bilateral agreement between network operators/service providers. + +*Example:* + +If a group Genève/DCV/CHEPTT/CHE–Mexico/N1M/TELMEX/MEX 1210 is carrying companded circuits: + +8. CO; + +### **13.9 Use [item 9]** + +This item identifies for what purpose the group/group link is used (if this is known by the network operator/service provider and of use for maintenance). + +*Format:* + +9. XXXXXX; (maximum six characters) + +*Specification:* + +XXXXXX refers to (among others) the designatory letters Z, B, D, X, DP, RP, VP, etc., as explained in clauses 7 and 9. If no other information is available, the sign – is used. + +*Example:* + +If the group London/45R/BTPLC/GBR–Melbourne/23E/TELSTR/AUS 1212 is dedicated to DP-circuits: + +9. DP. + +### **13.10 Transmission medium information [item 10]** + +This item identifies whether a satellite is involved in the routing. + +*Format:* + +10. ST; or –; + +*Specification:* + +If the group/group link has been routed via satellite: ST + +If the group/group link has not been routed via satellite: – + +*Example:* + +If the group Caracas/ECV/CANTV/VEN–Madrid/234/TFCAES/ESP 1203 has been routed via satellite: + +10. ST. + +### **13.11 End-to-end information or operational agreement [item 11]** + +#### **13.11.1 End-to-end information (for mixed analogue/digital routes only)** + +This item provides information on the destinations of the traffic carried by the group. + +*Format:* + +11. X ... X, Y ... Y; (maximum 12 characters each) or –; + +*Specification:* + +X ... X and Y ... Y are the names of a geographical area and refer to the destinations of the traffic in the group. The destinations are placed according to the order of geographical areas in the traffic relation. + + + +*Format in the case of a supergroup or higher level group:* + +13. Position number: designation of a group, of a leased circuit, or the sign –, +M M +Position number: designation of a group of a leased circuit, or the sign –; + +*Specification:* + +If the position number is occupied by a next lower group: designation of this group. + +If the position number is occupied by a leased circuit (with a bandwidth corresponding to the bandwidth of the next lower multiplex level, e.g., see clause 9.2.13): designation of this leased circuit. + +If the position number is not in use: – + +*Example:* + +For a supergroup Athinai/WED/OTE/GRC–Paris/ARC/FRTE/FRA 6002: + +13. 01: Beyrouth/3ED/BTPLC/GBR–Paris/ARC/FRTE/FRA 1209, +02: London/2WS/BTPLC/GBR–Sofia/3ED/FRTE/FRA 1202, +03: Athinai/3CC/OTE/GRC–Paris/ARC/FRTE/FRA 1205, +04: Athinai/3CC/OTE/GRC–Rotterdam/WSX/TCOMNL/NLD 1202, +05: Athinai/3CC/OTE/GRC–Paris/ARC/FRTE/FRA DP4; + +## 14 Designations of digital block (bidirectional and unidirectional) interconnections + +### 14.1 General + +This clause refers to blocks which are part of the digital multiplex hierarchy and which are formatted according to [ITU-T G.734], [ITU-T G.736], [ITU-T G.742], [ITU-T G.743], [ITU-T G.745], [ITU-T G.751], [ITU-T G.752], [ITU-T G.753] and [ITU-T G.754]. When a digital block route includes a transit network, clause 23 applies. The bit rates for these blocks, defined in [ITU-T G.702], are: 1544 kbit/s, 2048 kbit/s, 6312 kbit/s, 8448 kbit/s, 32 064 kbit/s, 34 368 kbit/s, 44 736 kbit/s, 97 728 kbit/s and 139 264 kbit/s. All other blocks are designated according to clause 17. + +An interconnecting digital block exists between two terminal points when it is possible to operate and monitor the digital block at both terminal points, without any other intermediate point where the original transmission structure ceases or is in some way modified. + +When in the interconnection route between two terminal transmission points an intermediate point is present where the digital transmission structure is demodulated, the route is split in two separate parts. Therefore, all present possible digital blocks exist only between the original route end points and that intermediate point and then have to be designated separately (according to the above rule). + +Basically, two different multiplex configurations apply: + +- Symmetrical: Both terminal points have the same multiplexing configuration. The digital blocks existing (i.e., those effectively operated and monitored) are designated as described in clause 14.2.1 (according to the above rule). +- Asymmetrical: One of the two terminal points has a different multiplexing configuration from the one used by the other point. The digital blocks existing (i.e., those effectively operated and monitored) are designated as described in clause 14.2.2. + +The format of the designation of digital blocks is shown in Table 6. + +**Table 6 – Digital block designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 3 to 6 | ≤ 4 | + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Digital block termination A and digital block termination B refer to the names of the two transmission stations in which the digital block is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). In the case of a multiple destination unidirectional digital block, Geographical Area B is replaced by (MU) (see clause 14.4). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: three to six letters and/or digits) + +This code consists of a number indicating the nominal number of channels in the digital block followed by the letter N. The function codes, for digital blocks formatted according to [ITU-T G.734], [ITU-T G.736], [ITU-T G.742], [ITU-T G.743], [ITU-T G.745], [ITU-T G.751], [ITU-T G.752], [ITU-T G.753] and [ITU-T G.754], are: 24N, 30N, 96N, 120N, 480N, 672N, 1440N and 1920N. + +For blocks in a mixed analogue/digital environment, see clause 16.1.2. (In this case, six characters or less are required.) + +c) *Serial number* (required: one to four digits) + +Identifies the instance of the digital block. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +## 14.2 Bidirectional digital blocks + +### 14.2.1 Symmetrical configuration + +As stated in clause 14.1, symmetric configuration means the same multiplexing configuration is present in both terminal transmission stations. The configuration in use defines the digital blocks to be designated. + +#### *Example 1:* + +In London and Paris, the same multiplexer configuration is being applied with a 34-Mbit/s supplying $4 \times 8$ -Mbit/s digital block. Then, an 8-Mbit/s block exists. The fourth secondary order block between London and Paris is designated: + +London/1L7/BTPLC/GBR–Paris/ARC/FRTE/FRA 120N4. + +#### *Example 2:* + +The tenth primary order block between New York and Tokyo is designated: + +New York/ERT/ATT/USA–Tokyo/MNM/NTT/JPN 24N10. + +### 14.2.2 Asymmetrical configuration + +As stated in clause 14.1, asymmetrical configuration means that different multiplexing configurations are present in the two terminal transmission stations. As the transmission station at one end has another multiplexer configuration than the one at the other end, only the digital blocks are deemed to exist that can be manipulated at both stations. + +#### *Example 1:* + +Lisbon and Rome are interconnected by a 34-Mbit/s line system. In Lisbon, a traditional multiplexer configuration is used (i.e., 34 Mbit/s $\leftrightarrow$ 8 Mbit/s $\leftrightarrow$ 2 Mbit/s). In Rome, an equipment with 34 Mbit/s $\leftrightarrow$ 2 Mbit/s multiplexer configuration is used, without the 8-Mbit/s modulation levels. In this case, the 8-Mbit/s blocks do not exist. Only the 34-Mbit/s and the 2-Mbit/s blocks exist between Lisbon and Rome. If only the first 2-Mbit/s block exists within the first 34 Mbit/s, the designation is: + +Lisboa/DFT/PT/PRT–Roma/VBB/TI/ITA 30N3. + +(See also the example in clause A.4.1.2.) + +## 14.3 Restoration digital blocks + +Digital blocks set up on restoration digital paths or spare digital paths for restoration purposes will receive a serial number from the 800-series, in descending order and starting from 899. + +#### *Example:* + +The first fourth order restoration block between Koebenhavn and Stockholm is designated: + +Koebenhavn/SST/TD/DNK–Stockholm/1BR/TELIA/SWE 1920N899. + +## 14.4 Multiple destination unidirectional digital blocks + +For these blocks, the traffic relation is composed of the name of the sending terminal station followed by a hyphen and the letters MU (multiple destination unidirectional) in parentheses. + +#### *Examples:* + +The first multiple destination unidirectional primary digital block from Bercenay (to, for example, London and Bruxelles) is designated: + +Bercenay/EVE/FRTE/FRA–(MU) 30N1. + +The next multiple destination unidirectional primary digital block from Bercenay (to, for example, Frankfurt and Roma) is designated: + +Bercenay/EVE/FRTE/FRA-(MU) 30N2. + +NOTE – Digital blocks routed via a multi-access system may be provided for exclusive use between two terminal stations only, in which case the normal designations given above in this Recommendation will apply. + +#### **14.5 Single destination unidirectional digital blocks** + +These blocks are designated as normal digital blocks and numbered in the same sequence. The unidirectional property as well as the direction of transmission has to be registered in Related information under item 16 (Direction of transmission) (see clause 20.16). + +*Example:* + +A unidirectional primary digital block transmitting in the direction Roma to London, which is the 21st primary digital block on that relation, is designated: + +London/CCD/BTPLC/GBR-Roma/DV1/TI/ITA 30N21. + +#### **14.6 Related information** + +The additional information on digital blocks is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bit rate; +- 13) occupancy; +- 14) actual number of channels (for primary blocks only); +- 15) clocking information; +- 16) direction of transmission (for unidirectional blocks only). + +The various items will be dealt with in clause 20. + +### **15 Designation of digital path interconnections** + +In practice, it may be that terminal equipment is not connected to a digital path. Nevertheless, for designation purposes, the digital path will be designated as though digital blocks had been set up (see clause 14.1). + +#### **15.1 Conventional digital paths not connected to their terminal equipment** + +Such digital paths are included in the normal serial numbering sequence of digital blocks and are not given a separate numbering sequence. When a digital path route includes a transit network, clause 23 applies. + +## 15.2 Restoration digital paths + +Digital paths nominated for restoration purposes are designated by serial numbers taken from the 800-series in ascending order and starting from 801. + +Restoration paths for first-order digital blocks: 30N801, 30N802, etc. + +Restoration paths for second-order digital blocks: 120N801, 120N802, etc. + +*Example 1:* + +The fourth second-order restoration digital path between London and Paris is designated: + +London/1N/BTPLC/GBR–Paris/ARC/FRTE/FRA 120N804. + +*Example 2:* + +The first third-order restoration digital path between Amsterdam and Paris is designated: + +Amsterdam/23T/TCOMNL/NLD–Paris/ARC/FRTE/FRA 480N801. + +## 15.3 Digital line sections and digital radio sections + +Designations of digital line sections and digital radio sections are under consideration. + +## 15.4 Related information + +The additional information on digital paths is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bit rate. + +The various items will be dealt with in clause 20. + +## 16 Designations of routes2 in the mixed analogue/digital transmission network + +Conforming to the philosophy for lining-up and maintaining a mixed analogue/digital transmission network [ITU-T M.20], the analogue and digital parts of the network are designated separately. To indicate that the end-to-end transmission relies on a mixture of analogue and digital transmission systems, the letter C is included in both the analogue and digital designations. The function code may, therefore, consist of a maximum of six characters. + +Transmultiplexer equipment is included in the designation of the analogue part of the route. + +--- + +2 This term is used provisionally in this context to designate various combinations of analogue and digital sections with appropriate intermediate equipment and usually also including terminal equipment, as illustrated in Figures 3 and 4. + +## **16.1 Transmission routes with one analogue-to-digital conversion** + +### **16.1.1 Groups and supergroups, etc., forming part of a mixed analogue/digital transmission route** + +Groups, supergroups, etc., which are converted into digital paths at some point, are designated in the same way as conventional groups or supergroups (see clause 11.1) but have a letter C included in the function code and placed after the nominal number of channels. + +*Examples:* + +Group: London/VEA/BTPLC/GBR–Riyadh/TYU/MOPTT/SAU 12C02 +Amsterdam/REV/TCOMNL/NLD–Koebenhavn/OOP/TD/DNK 12C899 +(restoration group) + +Supergroup: Paris/ARC/FRTE/FRA–Sydney/8UR/TELSTR/AUS 60C01 + +Mastergroup: Bruxelles/23E/BGACOM/BEL–London/ERT/BTPLC/GBR 300C03 + +Supermastergroup: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA 900C04 + +### **16.1.2 Digital blocks and paths forming part of a mixed analogue/digital transmission route** + +Digital blocks and paths which are converted into analogue groups, supergroups, etc., at some point, are designated in the same way as conventional digital blocks and paths, but have an additional letter C placed after the letter N. + +*Example:* + +Madrid/EEC/TFCAES/ESP–Roma/UE9/TI/ITA 480NC1. + +Figure 3 shows a typical analogue/digital arrangement and how it will be designated. + +![Figure 3: Example of a transmission route involving one analogue-to-digital conversion, showing how the various parts will be designated. The diagram shows a path from London to Frankfurt via Paris. In London, two Analogue IEs connect to CTEs, which then connect to a GTE and an SGTE. These are linked via a 'Mastergroup link' (Note 3) to another SGTE in Paris. In Paris, the SGTE connects to a 60 ch T/MUX. The output of the T/MUX goes through a digital multiplexing unit (marked with X and /) to an 8448 kbit/s path. This path continues through another digital multiplexing unit to a Digital IE in Frankfurt. Various circuit designations are shown: London-Paris 12C122, Frankfurt-Paris 30NC6, London-Paris 30002 (Note 1), Frankfurt-Paris 120N2 (Note 2), London-Paris 60C47, Frankfurt-Paris 30NC7, and London-Paris 12C123. The overall circuit designation is London-Frankfurt Z388. A legend at the bottom defines the symbols for CTE, GTE, SGTE, Digital multiplexing equipment, 60 ch T/MUX, Analogue switching, and Digital switching. Reference M.1400(13)_F03 is noted.](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +Figure 3: Example of a transmission route involving one analogue-to-digital conversion, showing how the various parts will be designated. The diagram shows a path from London to Frankfurt via Paris. In London, two Analogue IEs connect to CTEs, which then connect to a GTE and an SGTE. These are linked via a 'Mastergroup link' (Note 3) to another SGTE in Paris. In Paris, the SGTE connects to a 60 ch T/MUX. The output of the T/MUX goes through a digital multiplexing unit (marked with X and /) to an 8448 kbit/s path. This path continues through another digital multiplexing unit to a Digital IE in Frankfurt. Various circuit designations are shown: London-Paris 12C122, Frankfurt-Paris 30NC6, London-Paris 30002 (Note 1), Frankfurt-Paris 120N2 (Note 2), London-Paris 60C47, Frankfurt-Paris 30NC7, and London-Paris 12C123. The overall circuit designation is London-Frankfurt Z388. A legend at the bottom defines the symbols for CTE, GTE, SGTE, Digital multiplexing equipment, 60 ch T/MUX, Analogue switching, and Digital switching. Reference M.1400(13)\_F03 is noted. + +NOTE 1 – The conventional analogue designation is used. + +NOTE 2 – The conventional digital designation is used. + +NOTE 3 – Mastergroup link equipment is assumed and not shown here. + +**Figure 3 – Example of a transmission route involving one analogue-to-digital conversion, showing how the various parts will be designated** + +### 16.1.3 End-to-end designations + +This subject is covered by item 11 in related information for digital blocks (see clause 20.11). + +## 16.2 Transmission routes with two analogue-to-digital conversions + +### 16.2.1 End-to-end designations + +Where both ends of a route involving two analogue-to-digital conversions are analogue, an end-to-end designation using the analogue notation described in clause 16.1.1 should be agreed between the terminal network operators/service providers. + +Where both ends are digital, an end-to-end designation using the digital notation described in clause 16.1.2 should be agreed between the terminal network operators/service providers. + +By the above means, both terminal stations have available a common designation for the end-to-end transmission route, and are informed of its mixed analogue/digital nature. + +### 16.2.2 Intermediate section designation + +The intermediate part of the route is given a separate designation using the appropriate notation. The choice of this designation is the responsibility of the network operators/service providers providing the intermediate part of the route, and it is their responsibility to associate, in their records, this intermediate designation with the overall designation. + +Figure 4 shows two examples of routes involving two analogue-to-digital conversions and how they will be designated. + +![Figure 4: Examples of transmission routes involving two analogue-to-digital conversions. Part (a) shows a digital-analogue-digital route between Location A and Location D. Part (b) shows an analogue-digital-analogue route between Location A and Location D.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) + +**a) Digital-analogue-digital route** + +This diagram illustrates a transmission route between Location A and Location D. At Location A, a Digital IE connects to a 2048 kbit/s link (Note 1), which leads to a 60 ch T/MUX at Location B. A Supergroup link (Note 1) connects the T/MUX at Location B to another 60 ch T/MUX at Location C. From Location C, another 2048 kbit/s link (Note 1) leads to a Digital IE at Location D. Designations are provided for the full route (A-D Z427), the segment between A and D (A-D 30NC34 + A-D 30NC35), and the segment between B and C (B-C 60C47). + +**b) Analogue-digital-analogue route** + +This diagram illustrates a transmission route between Location A and Location D. At Location A, an Analogue IE connects to a CTE (ports 1 and 12), which in turn connects to a GTE (ports 5 and 12). A Supergroup link (Note 1) connects the GTE to a 60 ch T/MUX at Location B. A 2048 kbit/s link (Note 1) connects the T/MUX at Location B to another 60 ch T/MUX at Location C. A Supergroup link (Note 1) connects the T/MUX at Location C to a GTE (ports 5 and 12), which connects to a CTE (ports 1 and 12), which finally connects to an Analogue IE at Location D. Designations are provided for the full route (A-D Z125), and segments (A-D 12C94, A-D 60C46, and B-C 30NC146 + B-C 30NC7). + +Figure 4: Examples of transmission routes involving two analogue-to-digital conversions. Part (a) shows a digital-analogue-digital route between Location A and Location D. Part (b) shows an analogue-digital-analogue route between Location A and Location D. + +IE International exchange + +NOTE 1 – Higher-order groups and digital blocks would be designated in the conventional manner. + +NOTE 2 – Symbols are defined in Figure 3. + +**Figure 4 – Examples of transmission routes involving two analogue-to-digital conversions, showing how the various parts will be designated** + +### 16.3 Transmission routes with more than two analogue-to-digital conversions + +The transmission planning rules given in clause 3 of [ITU-T G.113] effectively restrict the number of unintegrated digital processes (e.g., analogue-to-digital conversions) permitted in the interconnection part of a telephone connection. Similarly, the routing plan given in [ITU-T E.171] restricts the number of interconnecting circuits in a connection to four. + +In view of these rules, it is desirable to limit the number of analogue-to-digital conversions in each direction between interconnecting centres to a maximum of two. Therefore, the detailed designation requirements of routes with more than two analogue-to-digital conversions are not considered. + +### 16.4 Related information + +The additional information on groups and blocks in the mixed analogue/digital network is covered by the same items as analogue groups and digital blocks respectively. However, item 11 "End-to-end information" is used in addition (see clauses 13.11 and 20.11). + +## 17 Designation of data transmission systems + +### 17.1 General + +This clause deals with data transmission systems provided between the premises of network operators/service providers. (Those between renters' premises are designated according to clause 9.2.15 concerning digital leased circuits connecting two locations.) Individual 56 or 64 kbit/s time slot interconnections (e.g., rented as single bearers in submarine cables) are considered as data transmission links and get a designation accordingly. For an example, see clause 17.2. When a data transmission system route includes a transit network, clause 23 applies. + +The designation scheme of these data transmission systems can only be used if they are non-hierarchical or not formatted according to [ITU-T G.734], [ITU-T G.736], [ITU-T G.742], [ITU-T G.743], [ITU-T G.745], [ITU-T G.751], [ITU-T G.752], [ITU-T G.753] and [ITU-T G.754]. This means that digital blocks from a digital multiplex hierarchy, with a format defined in [ITU-T G.702], cannot have a designation taken from this clause. They should be designated according to clause 14. The bit rates for these blocks, defined in [ITU-T G.702] are: 1544 kbit/s, 2048 kbit/s, 6312 kbit/s, 8448 kbit/s, 32 064 kbit/s, 34 368 kbit/s, 44 736 kbit/s, 97 728 kbit/s and 139 264 kbit/s. + +This clause also applies to single channel, optical transport network systems and their bit rates as defined in [ITU-T G.709], *Interface for the optical transport network*. + +These rates are: 2 666 057.143 kbit/s (2.666 Gb/s); 10 709 225.316 kbit/s (10.7 Gb/s); 43 018 413.559 kbit/s (43.0 Gb/s). + +Additionally, this clause applies for Ethernet connections at bit rates 1, 2.5 (but see Note 2), 10, 40 and 100 Gb/s. + +NOTE 1 – This clause deals with digital transmission only. Analogue data transmission systems and links are covered by the clauses treating circuits, groups and group links. + +NOTE 2 – 2.5 Gb/s is predominantly used in SONET/SDH networks. It is included in this clause (which applies only to Ethernet transmission) for possible future applications. Therefore, service providers should refer to clause 19 for function codes of 2.5 Gb/s in SDH. + +The format of designations of data transmission systems is shown in Table 7. + +**Table 7 – Data transmission system designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 3 to 5 | 1 to 3 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Data Transmission System Terminal Station A and Data Transmission System Terminal Station B refer to the names of the two transmission stations in which the data transmission system is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to the alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: three to six letters and/or digits) + +*General format* (excludes Gigabit Ethernet): The code consists of a two- to four-digit number which, together with a letter showing the multiplication factor, indicates the bit rate. Therefore, the full code is three to five characters in total. + +The letters to be used to indicate the multiplication factor are: + +Bit rate of system + +| Letter | Bit rate | +|--------|-----------------------------------| +| B | Up to 999 bit/s | +| H | 1000 to 9999 bit/s | +| K | 10 000 to 9 999 999 bit/s | +| M | 10 000 000 to 9 999 999 999 bit/s | + +Specific format for Gigabit Ethernet: This code consists of three to five alphanumeric characters which convey information about the rate of the signal for the digital transport system. + +Bit rate of system + +| Bit rate | Function code | Description | +|--------------------------|---------------|---------------------------------------| +| 1 Gb/s | GE1 | 1 Gigabit Ethernet (see Note 2) | +| 2.5 Gb/s | GE2X | 2.5 Gigabit Ethernet (see Note 3) | +| 10 Gb/s
(see Note 4) | 10GE | 10 Gigabit Ethernet (generic) | +| | GE10L | 10 Gigabit Ethernet LAN | +| | GE10W | 10 Gigabit Ethernet WAN | +| 40 Gb/s
(see Note 4) | 40GE | 40 Gigabit Ethernet (generic) | +| | GE40L | 40 Gigabit Ethernet LAN | +| | GE40W | 40 Gigabit Ethernet WAN | +| 100 Gb/s
(see Note 4) | 100GE | 100 Gigabit Ethernet (generic) | +| | GE100L | 100 Gigabit Ethernet LAN (see Note 5) | +| | GE100W | 100 Gigabit Ethernet WAN (see Note 5) | + +NOTE 1 – The leading or ending "GE" indicate Gigabit Ethernet. Numbers indicate bit rates in Gigabits per second. The suffix "L" indicates LAN at the physical layer. The suffix "W" indicates WAN at the physical layer. + +NOTE 2 – The "GE1" function code varies from the usual practice (in Rec. ITU-T M.1400) of using a letter as a separator at the end of the function code. Therefore, network operators/service providers, in particular, should take care to communicate clearly when referring to circuits using this code. Further, no future function codes ending with a digit will be created. + +NOTE 3 – The "GE2X" function code varies from the general format (see above) of using a letter showing the multiplication factor. In this case, the suffix "X" indicates a fraction of a Gigabit. + +NOTE 4 – When network operators/service providers agree to share separate Layer 2 information, including differentiation between LAN PHY and WAN PHY, the "10GE" (respectively, "40GE", "100GE") function code may be used. If Layer 2 information is not shared, or does not include differentiation between LAN PHY and WAN PHY, the specific function codes "GE10L" and "GE10W" (respectively, "GE40L" and "GE40W", "GE100L" and "GE100W") are used to differentiate between LAN PHY and WAN PHY at Layer 1. + +NOTE 5 – Although function codes "GE100L" and "GE100W" do not conform with the limitation to 5 characters in Table 7, they are kept for historical purposes. The 100 GE technology supports both LAN PHY and WAN PHY, and differentiation is not necessary. Therefore, 100 GE links should use function code "100GE" unless use of "GE100L" or "GE100W" is specifically required. + +c) *Serial number* (required: one to three digits) + +Identifies the instance of the transmission system. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +NOTE 3 – The use of the data transmission system (e.g., multiplex of digital leased circuits, broadcasting, video) will be recorded in Related information under Item 9 (Use) (see clause 20.9). + +*Example 1:* + +The first 9600 bit/s data transmission system between Lisbon RM1 and New York (for example, in use for a multiplex of 2400 bit/s and 7200 bit/s circuits): + +Lisboa/RM1/VCE/PT/PRT–New York/56H/ATT/USA 96H1. + +*Example 2:* + +The eleventh 2048 kbit/s data transmission system between London and Paris (used, for example, for a public video conference): + +London/MNM/BTPLC/GBR–Paris/ARC/FRTE/FRA 2048K11. + +*Example 3:* + +The first 512 kbit/s data transmission system (in use as an intermediate data rate (IDR) satellite carrier, rented from INTEL SAT) between Dubai and Montreal satellite earth stations (used, for example, for the public telephone service): + +Dubai/ERD/MOPTT/SAU–Montreal/TGB/CAN 512K1. + +*Example 4:* + +The third 100 Gigabit Ethernet LAN data transmission system between Milan and Rome, Italy: + +Milan/TI/ITA – Rome/TI/ITA GE100L3. + +![Diagram of a Gigabit Ethernet LAN showing three IEEE P802.3ba Edge devices connected to a central 100 Gbps Ethernet LAN bus.](02e16c8e8e61c2706b5c0129674884a8_img.jpg) + +The diagram illustrates a Gigabit Ethernet LAN. A central horizontal line represents the '100 Gbps Ethernet LAN'. Three 'IEEE P802.3ba Edge device' blocks are connected to this central line. Two blocks are positioned above the line, one on the left and one on the right, each connected via a vertical line. A third block is positioned below the line, also connected via a vertical line. Each block is divided into two sections: 'IEEE P802.3ba' and 'Edge device'. The label 'M.1400(15)\_F05' is located in the bottom right corner of the diagram area. + +Diagram of a Gigabit Ethernet LAN showing three IEEE P802.3ba Edge devices connected to a central 100 Gbps Ethernet LAN bus. + +**Figure 5 – Gigabit Ethernet LAN** + +## 17.2 Data transmission links + +Data transmission links are designated as data transmission systems. + +*Example:* + +In TAT-9, several single bearers between New York and London are in operation, being rented from the cable operating company by KPN Telecom in the Netherlands. The first single 64 kbit/s bearer gets the designation: + +London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K1. + +NOTE 1 – The suffix has to be agreed between the cable operating company and KPN Telecom, or simply by KPN. + +NOTE 2 – If the bearer is in use for the leased circuit Amsterdam/ERT/TCOMNL/NLD–New York/ABC/ATT/USA NP25, the occupancy is as follows: + +London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K1 + +1. Amsterdam/TCOMNL/NLD–New York/ABC/ATT/USA NP25 + +Should the bearer be idle, the occupancy is: 1. + +Reference is made to Annex B, which shows a more detailed example and the remaining part of routing from London to Amsterdam. + +### 17.3 Related information + +The additional information on data transmission systems is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) composition of transmission; +- 12) (unassigned item, use "-;"); +- 13) occupancy. + +The various items will be dealt with in clause 20. + +## 18 Designations of digital block interconnections created by the interconnection of digital circuit multiplication equipments (DCMEs) + +### 18.1 General + +The format of the designation of digital blocks created by the interconnection of digital circuit multiplication equipments (DCMEs) is shown in Table 8. + +**Table 8 – DCME designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 2 to 4 | ≤ 4 | +| | | | | | | | | | | | | | | | | | ↑
No space | | + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Digital block Terminal Point A and digital block Terminal Point B refer to the names of the two transmission stations in which the digital block is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: two to four letters and/or digits) + +This code consists of a number indicating the nominal maximum number of channels in the block followed by the letter Y. + +c) *Serial number* (required: one to four digits) + +Identifies the instance of the digital block. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example 1:* + +The second block created by the interconnection of DCMEs with a nominal maximum number of 240 channels between Frankfurt and Melbourne will be designated: + +Frankfurt/1WE/DTAG/DEU–Melbourne/34R/TELSTR/AUS 240Y2. + +*Example 2:* + +A block is created by the interconnection of DCMEs, and routed via a 512 kbit/s data transmission system. This data transmission system is an intermediate data rate (IDR) digital satellite carrier rented from INTELSAT (with $8 \times 64$ kbit/s bearer channels). Only one port will be used at both DCMEs. The first of such blocks to be established between Lisbon and Hong Kong will be designated: + +Hong Kong/4RT/CWHKTI/HKG–Lisboa/RFV/PT/PRT 30Y1. + +## 18.2 Multi-clique configuration of DCMEs + +If the created block is partly directed to destination B and partly to C (Figure 6) the designation of the blocks is: + +Geographical Area A/Transmission station detail/ICC/CC–Geographical Area B/Transmission station detail/ICC/CC $n_1n_1n_1$ Y xxxx + +Geographical Area A/Transmission station detail/ICC/CC–Geographical Area B/Transmission station detail/ICC/CC $n_2n_2n_2$ Y xxxx + +- $n_1n_1n_1$ , $n_2n_2n_2$ are the numbers of channels dedicated to that relation (multiples of 30); +- $n_1n_1n_1 + n_2n_2n_2$ = the capacity of the DCME. + +*Example:* + +London/EDC/BTPLC/GBR–New York/EV1/ATT/USA 120Y1 + +London/EDC/BTPLC/GBR–Pittsburgh/VBE/ATT/USA 120Y1 + +![Figure 6 – DCME configuration A: A diagram showing a central DCME unit labeled 'A' connected to two other DCME units labeled 'B' and 'C'. Unit 'A' has five input lines on its left side. It is connected to unit 'B' via a single line, and to unit 'C' via another single line. Unit 'B' has three output lines on its right side, and unit 'C' has three output lines on its right side. The label 'M.1400(15)_F06' is at the bottom right of the diagram.](29043c6ca27a7cfbc757a5d2eb029d33_img.jpg) + +Figure 6 – DCME configuration A: A diagram showing a central DCME unit labeled 'A' connected to two other DCME units labeled 'B' and 'C'. Unit 'A' has five input lines on its left side. It is connected to unit 'B' via a single line, and to unit 'C' via another single line. Unit 'B' has three output lines on its right side, and unit 'C' has three output lines on its right side. The label 'M.1400(15)\_F06' is at the bottom right of the diagram. + +**Figure 6 – DCME configuration A** + +The same designation applies to the configuration in Figure 7 ( $A_1 - B_1$ , $A_1 - B_2$ , $A_2 - B_1$ and $A_2 - B_2$ ). + +![Figure 7 – DCME configuration B: A diagram showing two DCME units labeled 'A1' and 'A2' on the left, and two DCME units labeled 'B1' and 'B2' on the right. Unit 'A1' is connected to both 'B1' and 'B2'. Unit 'A2' is also connected to both 'B1' and 'B2'. Each unit has three input lines on its left side and three output lines on its right side. The label 'M.1400(15)_F07' is at the bottom right of the diagram.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +Figure 7 – DCME configuration B: A diagram showing two DCME units labeled 'A1' and 'A2' on the left, and two DCME units labeled 'B1' and 'B2' on the right. Unit 'A1' is connected to both 'B1' and 'B2'. Unit 'A2' is also connected to both 'B1' and 'B2'. Each unit has three input lines on its left side and three output lines on its right side. The label 'M.1400(15)\_F07' is at the bottom right of the diagram. + +**Figure 7 – DCME configuration B** + +### 18.3 Low-rate encoding equipment + +Low-rate encoding equipment is considered as a special case of DCMEs. + +If two of these equipment components are linked, by using a 2-Mbit/s path, the designation 60Y (if multiplication factor = 2) should be applied. + +For low-rate encodings (LREs) linked by paths with other bit rates, the function code to be used is also dependent on the nominal maximum number of channels allowed by the configuration. + +*Example:* + +A block is created by the interconnection of LREs, and routed via a 512-kbit/s data transmission system. This data transmission system is an IDR digital satellite carrier rented from INTEL SAT (with $8 \times 64$ kbit/s bearer channels). The multiplication factor is 2. The first of such blocks to be established between Rome and Beijing will be designated: + +Beijing/11W/CT/CHN–Roma/ECB/TI/ITA 16Y1. + +### 18.4 Related information + +The additional information digital blocks created by the interconnection of DCMEs are covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; + +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bit rate; +- 13) occupancy. + +The various items will be dealt with in clause 20. + +## 19 Synchronous digital hierarchy (SDH) + +### 19.1 Designation of multiplex sections of the synchronous digital hierarchy (SDH) + +#### 19.1.1 General + +This clause deals with multiplex sections of the synchronous digital hierarchy (SDH) synchronous transport modules (STMs) as defined in [ITU-T G.707]. When a multiplex section route includes a transit network, clause 23 applies. + +The format of designation of multiplex sections is shown in Table 9: + +**Table 9 – Multiplex section designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 2 to 4 | 1 to 3 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Multiplex section Terminal Point A and multiplex section Terminal Point B refer to the names of the two transmission stations in which the multiplex section is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: two to four letters and/or digits) + +This code consists of a number (one to three digits) indicating the nominal number of VC-4s which can be carried by the multiplex section, followed by the letter S. + +NOTE – Network operators/service providers should refer to clause 17.1 for function codes of 2.5 Gb/s in Ethernet applications because 2.5 Gb/s is predominantly used in SONET/SDH networks. This clause 19 applies only to SDH transmission. + +- c) *Serial number* (required: one to three digits) + +Identifies the instance of the multiplex section. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example:* + +The eleventh multiplex section STM-16 (bit rate = $16 \times 155$ Mbit/s) between London and Paris is designated: + +London/22D/BTPLC/GBR–Paris/ARC/FRTE/FRA 16S11. + +### 19.1.2 Related information + +The additional information on multiplex sections is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bit rate; +- 13) occupancy; +- 14) access point identifiers. + +The various items will be dealt with in clause 20. + +## 19.2 Designations of virtual container interconnections + +### 19.2.1 General + +This clause refers to virtual containers (VCs) of the synchronous digital hierarchy as defined in [ITU-T G.707]. When a virtual container route includes a transit network, clause 23 applies. The format of the designation of virtual containers is shown in Table 10. + +**Table 10– Virtual container designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | – | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 4 to 5 | ≤ 4 | + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Data transmission system Terminal Point A and data transmission system Terminal Point B refer to the names of the two transmission stations in which the data transmission system is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: four to five letters and/or digits) + +This code is the following: + +VC11S for a VC-11 virtual container + +VC12S for a VC-12 virtual container + +VC2S for a VC-2 virtual container + +VC3S for a VC-3 virtual container + +VC4S for a VC-4 virtual container + +Function codes for concatenated virtual containers are covered by clause 19.3. + +c) *Serial number* (required: one to four digits) + +Identifies the instance of the virtual container. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example:* + +The tenth VC-4 virtual container between Barcelona and Toulouse is designated: + +Barcelona/ECT/TFCAES/ESP–Toulouse/CVB/FRTE/FRA VC4S10. + +### 19.2.2 Related information + +The additional information on virtual containers is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) (unassigned item, use: "-;"); +- 13) occupancy; +- 14) access point identifiers. + +The various items will be dealt with in clause 20. + +### 19.3 Concatenated virtual containers + +Concatenated virtual containers (VCs) are a group of virtual containers which are being concatenated. Such a concatenation configuration provides higher payload capability because the overhead in all but one virtual container is removed. The configuration therefore is a transport entity and receives a discrete designation. + +Concatenation can have two forms: contiguous and virtual. Contiguous refers to the configuration where the individual containers are in time slot order, whilst virtual concatenation refers to the configuration where the individual containers are spread over various time slots. The network management system keeps track of the actual configuration. + +The configurations are called in the operational field according to an expression using the letters VC followed by a hyphen followed by the VC level followed by a hyphen followed by the number of concatenated virtual containers followed by the letter v or c depending on the type of concatenation, so contiguous or virtual; example: VC-4-4c. + +This operational expression is used to explain the use of function codes for concatenated virtual containers. + +The function codes for concatenated virtual containers follows the scheme shown below: + +For contiguous concatenation and virtual concatenation respectively the function codes are: + +***mVpC*** and ***mVpV*** with, + +![Diagram showing the structure of function codes mVpC and mVpV. The code is composed of four parts: m, V, p, and C/V. m indicates the number of concatenated VCs (up to 256, max three digits). V defines it as a Virtual container. p indicates the VC level (2, 4, 11, 12, max two digits). C defines it as a Contiguous concatenated VC, or V defines it as a Virtual concatenated VC.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +*m* indicating the number of concatenated VCs up to 256 (maximum three digits) + +*V* defining that it is a Virtual container (one letter ) + +*p* indicating the VC level (2, 4, 11, 12) (maximum two digits) + +*C* defining that it is a Contiguous concatenated VC (one letter) +or *V* defining that it is a Virtual concatenated VC (one letter) + +Diagram showing the structure of function codes mVpC and mVpV. The code is composed of four parts: m, V, p, and C/V. m indicates the number of concatenated VCs (up to 256, max three digits). V defines it as a Virtual container. p indicates the VC level (2, 4, 11, 12, max two digits). C defines it as a Contiguous concatenated VC, or V defines it as a Virtual concatenated VC. + +Use of function codes for various payload types: + +| Payload type | | Function code | +|------------------------------------|-----------|---------------| +| 3 virtual concatenated VC-12's | VC-12-3v | 3V12V | +| 5 contiguous concatenated VC-2's | VC-2-5c | 5V2C | +| 4 contiguous concatenated VC-4's | VC-4-4c | 4V4C | +| 4 virtual concatenated VC-4's | VC-4-4v | 4V4V | +| 16 contiguous concatenated VC-4's | VC-4-16c | 16V4C | +| 256 contiguous concatenated VC-4's | VC-4-256c | 256V4C | + +*Example:* + +The third group of 16 contiguous concatenated VC-4's of payload type VC-4-16c, between Denver and Grenoble is designated: + +Denver/ABC/ATT/USA–Grenoble/EC1/FRTE/FRA 16V4C3. + +NOTE – Network operators/service providers should refer to clause 17.1 for function codes of 2.5 Gb/s in Ethernet applications because 2.5 Gb/s is predominantly used in SONET/SDH networks. This clause 19 applies only to SDH transmission. + +## 19.4 Leased circuits based on SDH + +### 19.4.1 General + +By placing SDH terminal equipment at users' premises, a leased circuit service can be offered to such users. This clause deals with these leased circuit types. When a leased circuit based on an SDH route includes a transit network, clause 23 applies. + +Various configurations apply: + +- terminal equipment at both sides is owned by a network operator/service provider (type A); or +- by the end user (type B); or +- on one side by the operator and on the other side by the user (type C). + +In case A, a fully managed leased circuit service is offered. The connection is a normal trail; namely, a virtual container. The use of the virtual container is expressed by a leased circuit service. + +In the case of type B and C at the side, where the terminal equipment is owned by the user, one has to identify a point where the connection is deemed to terminate and is handed over to the user; the role of such a point is expressed by the network terminating equipment (NTE). Because the + +connection is not terminating in the regular way, i.e., in the path terminating equipment (PTE), *this is not a trail* according to the definition of [ITU-T G.803]. Instead, this is a so-called *tandem connection*. In these cases no end-to-end managed connection is offered by the network operator/service provider to the user. The connection can only be partially managed. + +#### 19.4.2 Designations + +The designation format is according to clause 9. However, new function codes apply. To that end, a distinction is made between the fully managed and the partially managed types: + +- For partially managed SDH leased circuits, the function code is: HP; +- For fully managed SDH leased circuits, the function code is: MHP. + +#### 19.4.3 Application + +In case A, a virtual container is running from one user location to the other; it will receive a designation according to clause 19: so, for a VC12: Geographical Area A/termination detail/ICC/CC–Geographical Area B/termination detail/ICC/CC VC12S1 + +The leased circuit designation then will read: Geographical Area A/termination detail/ICC/CC-Geographical Area B/termination detail/ICC/CC MHP1 + +In the cases B and C, a tandem connection is running; a new function code applies: TCxxS where xx can take the values 12, 3 and 4. + +The tandem connection will receive a designation as follows: + +Geographical Area A/termination detail/ICC/CC–Geographical Area B/termination detail/ICC/CC TC12S1 and the leased circuit a designation: + +Geographical Area A/termination detail/ICC/CC–Geographical Area B/termination detail/ICC/CC HP1. + +It should be noted that function codes for leased circuits based on other network configurations, e.g., mixed PDH/SDH, require further study. + +#### 19.4.4 Related information + +This is left for further study. This will be organized within clause 20. + +### 20 Related information for digital block, path, data transmission system, block interconnections created by the interconnection of DCMEs, SDH multiplex sections and virtual containers + +The following subclauses explain the items of related information concerned with interconnecting digital blocks, paths, data transmission systems, blocks created by the interconnection of DCMEs, virtual containers and SDH multiplex sections. Full examples of the designation information of an interconnecting digital block, an interconnecting digital path, an interconnecting data transmission system, an interconnecting block created by the interconnection of DCMEs, an interconnecting virtual container and an interconnecting SDH multiplex section are given in clause A.4. + +#### 20.1 Urgency for restoration [item 1] + +This item supplies information on the urgency of restoration of the block, path, etc., based upon bilateral agreement between the terminal network operators/service providers. + +*Format:* + +1. xx ... xx; (maximum ten characters) + +*Illustration:* + +- a) If the priority is top: 1; +If the priority is second: 2; +If the priority is third: 3; or +- b) If repair is required within, e.g., 24 hours: $\leq 24$ h; or +- c) If no urgency has to be indicated: –; + +*Example:* + +If a block needs top priority in the case of restoration: + +- 1. 1; + +## **20.2 Terminal countries [item 2]** + +This item presents the countries in which the block, path, etc., is terminating. + +*Format:* + +- 2. XXX, YYY; (three characters for each) or two. XXX; + +*Specification:* + +XXX: code for country of Geographical Area A + +YYY: code for country of Geographical Area B + +In the case of multiple destination unidirectional block, only XXX applies. + +NOTE – The alpha-3 codes are according to [ISO 3166-1]. + +*Example:* + +For a digital block Bruxelles/ERY/BGACOM/BEL–Frankfurt/EVT/DTAG/DEU 120N1: + +- 2. BEL, DEU; + +## **20.3 Names of network operators/service providers [item 3]** + +This item records the names of the carriers, etc., which operate the block, path, etc. The applicable carrier codes can be selected from the List of ITU Carrier Codes as described in clause 6.4. + +*Format:* + +- 3. XXXXXX, YYYYYY; (maximum six characters for each) or three. XXXXXX; + +*Specification:* + +XXXXXX: name of company in Geographical Area A + +YYYYYY: name of company in Geographical Area B + +In the case of a multiple destination unidirectional block, only XXXXXX applies. + +*Example:* + +For a digital block Frankfurt/EVT/DTAG/DEU–London/CCB/BTPLC/GBR 30N1 operated by Deutsche Telekom and BT (British Telecom): + +- 3. DTAG, BTPLC; + +## 20.4 Control station [sub-control station(s)] [item 4] + +This item lists the appointed control station and sub-control stations (according to [ITU-T M.80] and [ITU-T M.90]). Further details about the stations can be found in the list of contact points in [ITU-T M.1510]. + +*Format:* + +- 4. CS: designation of control station, +SCS1: designation of sub-control station, +SCS2: designation of sub-control station, +M M +SCSn: designation of sub-control station, + +or, in the case of a multiple destination unidirectional block: + +- 4. CS: designation of control station. + +*Specification:* + +- CS: designation of the control station, +- SCS1: designation of the terminal sub-control station, +- SCS2 to SCSn: if applicable, other sub-control stations are to be placed in the geographical order according to the traffic relation. + +In the case of a multiple destination unidirectional block, only CS applies. + +*Example 1:* + +For the digital block Stockholm/ECC/TELIA/SWE–Venezia/XX1/TI/ITA 30N1 with control station Stockholm and sub-control stations Venezia and Paris: + +- 4. CS: Stockholm/HAM/TELIA/SWE; +SCS1: Venezia/CEN/TI/ITA; +SCS2: Paris/ARC/FRTE/FRA; + +*Example 2:* + +For the digital block Rio de Janei/E1X/EBTLBR/BRA–(MU) 30N1: + +- 4. CS: Rio de Janei/1/EBTLBR/BRA: + +## 20.5 Fault report points [item 5] + +This item presents the names of both fault report points on the block, path, etc., (according to [ITU-T M.2130]). Further details about the fault report points can be found in the list of contact points in [ITU-T M.1510]. + +*Format:* + +- 5. Designation of fault report point, Designation of fault report point +- or +- 5. Designation of fault report point; + +*Specification:* + +The first fault report point is that of the country of Geographical Area A. + +The second fault report point is that of the country of Geographical Area B. + +In the case of a multiple destination unidirectional block, the second station and the comma are omitted. + +*Example 1:* + +For the digital block Lisboa/EC1/PT/PRT–Zurich/CCB/CHEPTT/CHE 30N1: + +5. Lisboa/PCS/PT/PRT, Zurich/SEL/CHEPTT/CHE; + +*Example 2:* + +For the digital block Jakarta/2WS/INDSAT/IDN–(MU) 30N1: + +5. Jakarta/1/INDSAT/IDN; + +## **20.6 Routing [item 6]** + +This item records the next higher block within the multiplex hierarchy on which the block, path, virtual container, multiplex sections, etc., have been routed and the position number, or in the case of the highest multiplex level, the transmission media on which the block has been routed. + +*Format:* + +6. Designation of an interconnecting block/position number or designation of transmission medium, Designation of an interconnecting block/position number or designation of transmission medium, ..., Designation of an interconnecting block/position number or designation of transmission medium. + +NOTE 1 – For the case of a lower order virtual container (VC), the position number should be given using KLM addressing. KLM addressing is described in clause 7.3 of [ITU-T G.707]. Also, refer to Annex B for a description of how KLM addressing relates to time slot numbering. + +NOTE 2 – Two consecutive unidirectional blocks are separated by a + sign instead of a comma. + +NOTE 3 – For contiguous concatenation of lower order virtual containers the KLM-addressing applies as for normal virtual containers; for the concatenation of VC-4s and for virtual concatenation of all VC levels the time slot numbering must be applied. + +*Specification:* + +The designation of an interconnecting block refers to the next higher level in the digital multiplex hierarchy. If there is more than one, the blocks are noted in geographical order from Geographical Area A to Geographical Area B. + +The designation of the transmission medium refers to the transmission medium leaving the country of Geographical Area A and to the transmission medium entering the country of Geographical Area B respectively. + +As no ITU-T designations of transmission media, nor digital line or radio sections, are recommended for the time being, the terminal countries should provide designations or agree on designations. + +If there is only one transmission medium, the designation of this medium applies. + +*Example 1:* + +For the primary digital block Frankfurt/DCF/DTAG/DEU–Zurich/37T/CHEPTT/CHE 30N7: + +6. Frankfurt/DCF/DTAG/DEU–Zurich/37T/CHEPTT/CHE 120N1/3; + +*Example 2:* + +For the block Bruxelles/2WS/BGACOM/BEL–London/CBN/BTPLC/GBR 1920N1, with transmission medium corresponding to submarine cable: + +6. Bruxelles/2WS/BGACOM/BEL–London/CBN/BTPLC/GBR 5; + +## 20.7 Association [item 7] + +This item identifies whether there are associated blocks, paths, data transmission systems, digital blocks created between DCMEs, virtual containers and SDH multiplex sections, and if so, of what type. + +*Format:* + +7. Association code: designation(s) of the associated block(s), path(s), etc.; + +Further study is needed on the development of association codes for (shared) protection of SDH multiplex sections. + +### 20.7.1 Information on reserve blocks, paths, data transmission systems created digital blocks between DCMEs, virtual containers and multiplex sections + +*Specification:* + +If the block *has* a reserve block, the association code is: S followed by the function code and the serial number of the principal block. + +If the block *is* a reserve block, the association code is: function code followed by S and the serial number of the reserve block. + +The same applies for digital paths, data transmission systems, etc. + +*Example:* + +If the path Hongkong/11W/CWHKTI/HKG–Singapore/SSD/ST/SGP 30N801 is the restoration path for the normal block Hongkong/11W/CWHKTI/HKG–Singapore/SSD/ST/SGP 30N3, the Related information for the normal block under Association must show: + +7. S30N3: Hongkong/11W/CHKTI/HKG–Singapore/SSD/ST/SGP 30N801; + +### 20.7.2 Information on diverse routing + +*Specification:* + +If a block is required to be routed on a different route than other blocks, the association code is DVR followed by the designation of the other blocks. + +The same applies for digital paths, data transmission systems, etc. + +*Example:* + +If a block Amsterdam/CBN/TCOMNL/NLD–Paris/ARC/FRTE/FRA 30N7 is required to be routed on a different route than the blocks Amsterdam/CBN/TCOMNL/NLD–Bruxelles/VVC/BGACOM/BEL 30N12 and Bruxelles/VVC/BGACOM/BEL–Paris/ARC/FRTE/FRA 30N2, the related information for the block Amsterdam/CBN/TCOMNL/NLD–Paris/ARC/FRTE/FRA 30N7 under Association must show: + +7. DVR: Amsterdam/CBN/TCOMNL/NLD–Bruxelles/VVC/BGACOM/BEL 30N12, +Bruxelles/VVC/BGACOM/BEL–Paris/ARC/FRTE/FRA 30N2; + +NOTE – The codes listed in clauses 20.7.1 and 20.7.2 may both appear under Association. + +### 20.7.3 Information on consecutive routing + +*Specification:* + +If the time slots in a block carry traffic that is consecutively routed on single bearers, the block and the single bearers get an Association code, namely: + +PLR = part of a longer route. + +*Example:* + +If five single bearers (see the example in 12.2) are connected in London to five time slots in the interconnecting 2 Mbit/s digital block Amsterdam/PTT/TCOMNL/NLD–London/XYZ/BTPLC/GBR 30N1 the Association is as follows: + +Amsterdam/PTT/TCOMNL/NLD–London/XYZ/BTPLC/GBR 30N1 + +7. PLR: London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K1 +London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K2 +London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K3 +London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K4 +London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K5 + +Similar for each of the single bearers, e.g., for London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 64K1: + +7. PLR: London/XYZ/BTPLC/GBR–New York/ABC/ATT/USA 30N1 + +#### **20.7.4 Information on maintaining the sequential order of digital paths (concatenation)** + +*Specification:* + +If a couple of digital paths together support a service, it may be required to maintain the sequential order of the paths when multiplexed into a higher order block or container. In that case the designations of the paths get an Association code on concatenation, namely TSG = time slot sequential order must be guaranteed on an end-to-end basis; the format then is: 7. TSG followed by the function code and the sequential numbers of all concatenated digital paths including those of the path under consideration. + +*Example:* + +Three interconnecting 2-Mbit/s digital paths together support a video service, namely Lisboa/X1Y/PT/PRT–Milano/TI1/TI/ITA 30N21, Lisboa/X1Y/PT/PRT–Milano/TI1/TI/ITA 30N22, Lisboa/X1Y/PT/PRT–Milano/TI1/TI/ITA 30N23; + +They must stay concatenated when they are being multiplexed into a virtual container and therefore each of their designations gets the Association code TSG followed by function code and the sequential numbers of all three concatenated 2 Mbit/s digital paths: Lisboa/X1Y/PT/PRT–Milano/ TI1/TI/ITA 30N22 has under Related information item 7: + +7. TSG: 30N21-23 + +### **20.8 Equipment information [item 8]** + +**20.8.1** This item records information on equipment in the block, path, etc., which requires special maintenance attention. + +*Format:* + +8. XX, XX, XX, XX; + +*Specification:* + +If the block has been routed via TDMA: TD. + +If the block has been created by the interconnection of two transcoders (low-rate encoding equipment) using the A-law: AI or $\mu$ -law: MI. + +NOTE – If there is a need to record any additional equipment information, the next free codeplaces are available for that purpose. The codes to be used must consist of two characters, be unique and can be chosen by bilateral agreement between network operators/service providers. + +**20.8.2** For data transmission systems, this item supplies information about the multiplex configuration. + +*Format for data transmission systems only:* + +8.        XXXXXXYYYYZZZZ; + +*Specification:* + +XXXXXX refers to the Recommendation series, + +YYYY refers to the Recommendation number, + +ZZZZ refers to number of the clause, subclause, table, etc. + +*Example:* + +For a 9600-bit/s data transmission system with a multiplex configuration as defined in Table D.1, item 8 will present: + +8.        Rec. M.1400T12; + +**20.8.3** For blocks created by the interconnection of DCMEs, this item provides information on through-going channels (which are transmitted even if a DCME fails) and derived channels (which are not transmitted if a DCME fails). + +*Format:* + +8.        XXXXXX = Y; + +*Specification:* + +XXXXXX indicates a range of positions (e.g., 1-30), on all even positions (EP), on all odd positions (OP). + +Y indicates whether these positions are through-going (T) or derived (D). + +*Example 1:* + +If the 30 first channels of a 240Y block are through-going, item 8 will be: + +8.        1-30 = T; + +*Example 2:* + +If the even positions of a 60Y block created by the interconnection of two transcoders are derived, item 8 will be: + +8.        EP = D; + +## **20.9 Use [item 9]** + +This item identifies for what purpose the block, path, data transmission system is used (if this is known by the network operator/service provider and is of use for maintenance). + +*Format:* + +9.        XXXXXX; (maximum six characters) + +*Specification:* + +XXXXXX refers to (among others) the designatory letters Z, B, D, V, etc., to indicate the use of the block. If no information is available, the sign – is used. + +*Example:* + +If the digital block Frankfurt/SSD/DTAG/DEU–Luxembourg/ECC/LUXPT/LUX 30N1 is used for sound-programme transmission: + +9. R; + +## **20.10 Transmission medium information [item 10]** + +This item identifies whether a satellite is involved in the routing. + +*Format:* + +10. ST; or –; + +*Specification:* + +If the block has been routed via satellite: ST + +If the block has not been routed via satellite: –. + +*Example:* + +For the block Paris/ARC/FRTE/FRA–(MU) 30N1: + +10. ST; + +## **20.11 End-to-end information or composition of transmission or operational agreement [item 11]** + +### **20.11.1 End-to-end information (for blocks and paths on mixed analogue/digital routes only)** + +This item provides information on the destinations of the traffic carried by the block or path. + +*Format:* + +11. X ... X, Y ... Y; (maximum 12 characters each) or –; + +*Specification:* + +X ... X and Y ... Y are the names of a geographical area and refer to the destinations of the traffic on the block/path. The destinations are placed according to the order of geographical areas in the traffic relation. + +If the block has multiple destinations, the Geographical area name is replaced by the code: M. + +If the block is within a digital environment X ... X, Y ... Y is replaced by the sign –. + +*Example 1:* + +For primary digital block Frankfurt/MMN/DTAG/DEU–Paris/ARC/FRTE/FRA 30NC6 carrying from Frankfurt–London: + +11. Frankfurt, London; + +*Example 2:* + +For primary block Amsterdam/EC2/TCOMNL/NLD–Bruxelles/EXX/BGACOM/BEL 30NC146 carrying traffic from London to Luxembourg: + +11. London, Luxembourg; + +### **20.11.2 Composition of transmission (for data transmission systems)** + +This item shows the type of transmission on the data transmission system. + +*Format:* + +11. A; N; or C; + +*Specification:* + +If the transmission is analogue: A + + + + + +03: New York/24/ATT/USA–Paris/PT2/FRTE/FRA Z5, + 04: Paris/PT2/FRTE/FRA–New York/24/ATT/USA Z2, + 05: Paris/PT2/FRTE/FRA–New York/24/ATT/USA Z4, + 06: Paris/PT2/FRTE/FRA–New York/24/ATT/USA Z6, + 07: –, + 08: –, + 09: –, + 10: Orlando/TS1/ATT/USA–Toulouse/FER/FRTE/FRA 64K1, + 11: –, + 12: –, + 13: –, + 14: –, + 15: New York/TS1/ATT/USA–Paris/ARC/FRTE/FRA R1, + 16: New York/TS1/ATT/USA–Paris/ARC/FRTE/FRA R3, + 17: –, + 18: –, + 19: –, + 20: Paris/BEA/FRTE/FRA–Washington/TS1/ATT/USA NP1, + 21: –, + 22: –, + 23: –, + 24: –, + +*Example 3:* + +For the VC-4 Paris/ARC/FRTE/FRA–Roma/23T/TI/ITA VC4S12: + +13. 1,0,0: Napoli/EC/TI/ITA–Paris/ARC/FRTE/FRA VC3S15, + 2,1,0: Lille/WS/FRTE/FRA–Roma/23T/TI/ITA VC2S8, + 2,2,0: Lille/WS/FRTE/FRA–Roma/23T/TI/ITA VC2S121, + 2,3,0: –, + 2,4,1: London/113/BTPLC/GBR–Roma/23T/TI/ITA VC12S30, + 2,4,2: Paris/ARC/FRTE/FRA–Roma/23T/TI/ITA VC12S4, + 2,4,3: London/113/BTPLC/GBR–Roma/23T/TI/ITA VC12S31, + 2,5,0: London/113/BTPLC–Roma/23T/TI/ITA VC2S67, + 2,6,0: –, + 2,7,0: Paris/ARC/FRTE/FRA–Roma/23T/TI/ITA VC2S82, + 3,0,0: Napoli/EC/TI/ITA–Paris/ARC/FRTE/FRA VC3S16; + +*Example 4:* + +For the multiplex section London/113/BTPLC/GBR–Paris/ARC/FRTE/FRA 4S1: + +13. 1: Glasgow/24R/BTPLC/GBR–Paris/ARC/FRTE/FRA VC4S12, + 2: London/113/BTPLC/GBR–Paris/ARC/FRTE/FRA VC4S21, + 3: –, + +4: London/113/BTPLC/GBR–Toulouse/WSX/FRTE/FRA VC4S; + +## **20.14 Actual number of channels and access point identifier [item 14]** + +In the case of primary blocks, clause 20.14.1 applies; in the case of virtual containers and SDH multiplex sections, clause 20.14.2 applies. + +### **20.14.1 Actual number of channels (primary blocks only)** + +This item contains the actual number of channels on a primary digital block. + +*Format:* + +14.     xxx; + +*Specification:* + +xxx indicates the actual number of channels. + +For higher blocks xxx is replaced by the sign –. + +*Example 1:* + +For the digital block New York/WSX/ATT/USA–Paris/ARC/FRTE/FRA 30N5 dedicated to leased circuits: + +14.     31; + +*Example 2:* + +For the digital block London/23T/BTPLC/GBR–New York/3ED/ATT/USA 30N3 used for switched public telephone circuits with ADPCM, the information may be: + +14.     60; + +*Example 3:* + +For the digital block Honolulu/CCC/ATT/USA–Osaka/EDC/NTT/JPN 24N2 used for switched public telephone circuits: + +14.     24; + +### **20.14.2 Access point identifiers (virtual containers and SDH multiplex sections)** + +This item contains the access point identifiers associated with the trail terminations at the ends of the trail. For Geographical Area A in the designation of a virtual container or a multiplex section, the APId A applies. For Geographical Area B in the designation of a virtual container or a multiplex section, the APId B applies. + +*Format:* + +14.     APId A: xxx ... xx, (maximum 15 characters) +            APId B: xxx ... xx; (maximum 15 characters) + +The access point identifier consists of a maximum of 15 characters and begins with either: + +- a)     the three alphabetic character (alpha-3) country code as defined in [ISO 3166-1]; or +- b)     the country code as defined in [ITU-T E.164]. + +For further details, see [ITU-T G.831]. + +*Comments:* + +- 1)     the identifiers must be unique per layer, so identifiers may be the same if and only if they belong to different VC-layers; + +- 2) operators within a country may apply format a) or b), but must agree together with other users of that format on how to keep the remaining part of the code unique. + +*Application:* + +- 1) A VC-4 Access Point in the USA: USA12345ABC6789 where 12345ABC6789 is to be designated by the responsible operator in the USA. + +- 2) A VC-3 Access Point in the USA: USA12345ABC6789 + +*Comment:* This code may be the same as the one for the VC-4 Access Point, in accordance with Comment 1 above. + +- 3) A VC-4 Access Point in the UK: 449876543210123 where 9876543210123 is to be designated by the operator in the UK. + +- 4) A VC-12 Access Point in the Netherlands: NLDTCOMNL99ASD2; here the code TCOMNL99ASD2 was assigned by the operator KPN Telecom in the Netherlands. + +*Example:* + +For a VC-4 between Dallas in the USA and Manchester in the UK, item 14 is specified as: + +14. APId A: USA12345ABC6789, +APId B: 449876543210123; + +## **20.15 Clocking information (for blocks only) [item 15]** + +This item specifies whether network operators/service providers apply a clocking system according to [ITU-T G.811] or use a master/slave system. + +*Format:* + +15. XX ... XX; (maximum 30 characters) + +*Specification:* + +If clocking according to [ITU-T G.811] is applied: then use the information therein; + +If a master/slave clocking is applied: + +M = XX ... XX, S = XX ... XX; + +(Geographical area name for the master) (Geographical area name for the slave) + +*Example 1:* + +Clocking according to [ITU-T G.811]: + +15. Use the information therein; + +*Example 2:* + +Clocking according to master/slave system: + +15. M = London, S = Frankfurt; + +## **20.16 Direction of transmission (for unidirectional blocks) [item 16]** + +This item gives information on the direction of transmission of a unidirectional digital block. + +*Format:* + +16. I; or A; + +*Specification:* + +If the block is unidirectional and if it has a single destination: + +- if the direction of transmission is in alphabetical order A; +- if the direction of transmission is in inverse alphabetical order I. + +*Example:* + +For the unidirectional digital block London/23E/BTPLC/GBR–Roma/CCB/TI/ITA 30N1 transmitting in the direction Roma to London: + +16. I; + +## 21 Designation of connections for the asynchronous transfer mode (ATM) + +### 21.1 General + +This clause deals with semi-permanent or permanent connections for the ATM as defined in [ITU-T I.121], [ITU-T I.150], [ITU-T I.211], [ITU-T I.230], [ITU-T I.231.x], [ITU-T I.232.x], [ITU-T I.310], [ITU-T I.311], [ITU-T I.326], [ITU-T I.365.1], [ITU-T I.365.2], [ITU-T I.365.3], [ITU-T I.365.4], [ITU-T I.365.5], [ITU-T I.365.6] and [ITU-T I.432.x]. When an ATM connection includes a transit network, clause 23 applies. + +An ATM transport network can be supported by PDH and SDH through a number of transmission systems. ATM transport network nodes are connected by transport links (physical layer) and a virtual path (Function code VP). A VP's transmission capacity can be assigned to one or more virtual channels (Function code VCA). + +The designation format of ATM transport links, VP and VCA, is shown in Table 11: + +**Table 11 – ATM transport link, VP and VCA designation format** + +| Designation format | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 2 to 6 | 1 to 4 | + +↑ +No space + +### 21.2 Transport links + +Transport links are based upon either PDH digital paths or SDH virtual containers. So the links are not identical to the paths or containers, but do use them. The paths therefore act as a server and ATM transport link as the client. From a network model point of view, the PDH digital path and the SDH virtual container belong to the server layer and the ATM transport link to the client layer. This relation will be reflected in the routing of ATM transport links: they are being routed either on a PDH digital path or a virtual container. + +The elements of the Layer 1 format are as follows: + +- Transport relation* + +ATM transport link terminal station A and ATM transport link terminal station B refer to the names of the two transmission stations in which the ATM transport link is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: two to six letters and/or digits) + +This code is the following: + +| | | +|--------|-----------------------------------| +| A34M | for 34 Mbit/s ATM transport link | +| A45M | for 45 Mbit/s ATM transport link | +| A155M | for 155 Mbit/s ATM transport link | +| A622M | for 622 Mbit/s ATM transport link | +| A2500M | for 2.5 Gbit/s ATM transport link | +| A10G | for 10 Gbit/s ATM transport link | +| A40G | for 40 Gbit/s ATM transport link | + +- c) *Serial number* (required: one to four digits) + +Identifies the instance of the transport link. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example:* + +The first transport link at the speed of 34 Mbit/s between Lugano and Milan will be designated: + +Lugano/SUI/CHEPTT/CHE-Milano/M\*I/TI/ITA A34M1 + +## 21.3 Virtual path + +The elements of the Layer 1 format are as follows: + +- a) *Transport relation* + +ATM virtual path terminal station A and ATM virtual path terminal station B refer to the names of the two transmission stations in which the ATM virtual path is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: three letters) + +This code is VPA. + +- c) *Serial number* (required: one to four digits) + +Identifies the instance of the virtual path. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example:* + +The first ATM virtual path from Leeds to Koeln will be designated: + +Leeds/FGY/FRTE/FRA–Koeln/DG/DTAG/DEU VPA1 + +## 21.4 Virtual channels (VCAs) + +The elements of the Layer 1 format are as follows: + +- a) *Transport relation* + +ATM virtual channel (VCA) terminal station A and ATM VCA terminal station B refer to the names of the two transmission stations in which the ATM VCA is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +NOTE – The information about the virtual channel being bidirectional or unidirectional and, in this case, the information about its origin and destination points is crucial for maintenance, and will be addressed in the related information, which is open for further study. + +*Geographical area:* the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: three letters) + +This code is VCA. + +- c) *Serial number* (required: one to four digits) + +Identifies the instance of the VCA. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +## 21.5 ATM Layer 2 + +The related information on ATM is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; + +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) (unassigned item, use: "-;"); +- 13) occupancy; +- 14) direction of transmission (for unidirectional transit network services only); +- 15) ATM transfer capability; +- 16) source traffic descriptor; +- 17) cell delay variation tolerance; +- 18) quality of service. + +The various items will be dealt with in clause 22. + +## **22 Related information for the asynchronous transfer mode (ATM)** + +The following subclauses explain the items of Related information concerned with the asynchronous transfer mode: + +### **22.1 Urgency for restoration [item 1]** + +Normal assignment. + +### **22.2 Terminal countries [item 2]** + +Normal assignment. + +### **22.3 Names of network operators/service providers [item 3]** + +Normal assignment. + +### **22.4 Control and sub-control station(s) [item 4]** + +Normal assignment. + +### **22.5 Fault report points [item 5]** + +Normal assignment. + +### **22.6 Routing [item 6]** + +Normal assignment. + +### **22.7 Association [item 7]** + +Normal assignment. + +### **22.8 Equipment information [item 8]** + +Normal assignment. + +## **22.9 Use [item 9]** + +Normal assignment. + +## **22.10 Transmission medium information [item 10]** + +Normal assignment. + +## **22.11 Operational agreement [item 11]** + +Normal assignment. + +## **22.12 Unassigned item [item 12]** + +Not applicable. + +## **22.13 Occupancy [item 13]** + +Normal assignment. + +## **22.14 Direction of transmission (for unidirectional transit network services only) [item 14]** + +Normal assignment. + +## **22.15 ATM transfer capability [item 15]** + +An ATM transfer capability is intended to support an ATM layer service model and associated quality of service (QoS) through a set of ATM layer traffic parameters and procedures. An ATM transfer capability may include the specification of primitives to comply with, and of traffic control information to be exchanged through standardized interfaces. + +There may be more than one quality of service (QoS) class for a given ATM transfer capability (ATC) [ITU-T I.356]. Given that a user can commit to submitting cells in conformance to traffic descriptors in addition to the peak cell rate (PCR), the reason a user would choose a service based on an ATM transfer capability other than the deterministic bit rate transfer capability is the potential of incurring a lower cost from the network provider. + +It is mandatory that the ATM transfer capability used on a given ATM connection, among those that are made available by the network, be implicitly or explicitly declared at connection establishment. + +Once an ATM connection is established, the agreed-upon ATC is the same at all standardized interfaces along the connection. However, it is a network operator's choice on how to support a given ATM transfer capability, provided it is complying with specifications at standardized interfaces. + +A given ATM communication uses the same ATM transfer capability for both directions. Use of different transfer capabilities for the two connections of a communication raises issues relating, for example, to OAM and resource management cells, or to routing and is thus not currently specified in this Recommendation. This also applies to multicast connections. + +*Format:* + +15.    XXX;        (three characters) + +*Specifications:* + +DBR    Deterministic Bit Rate capability + +SBR    Statistical Bit Rate capability + +ABR    Available Bit Rate capability + +ABT    ATM Block Transfer capability + +*Example:* + +For an ATM-transport link Bruxelles/ZXC/BGACOM/BEL–Frankfurt/54T/DTAG/DEU A34M1 in which the ATM transfer capability is the deterministic bit rate capability: + +15. DBR; + +## **22.16 Source traffic descriptor [item 16]** + +This descriptor includes parameters that describe the traffic originated from the source. These parameters depend on the ATC. The source traffic descriptor (STD) and cell delay variation tolerance (CDVT) specified for each connection describe the traffic descriptor at the interface. + +Peak cell rate in the source traffic descriptor specifies an upper bound on the traffic that can be submitted on an ATM connection. + +Sustainable cell rate (SCR) together with a parameter characterizing the maximum burst size at the peak cell rate, i.e., intrinsic burst tolerance (IBT), are intended to describe variable bit rate (VBR) sources and allow for statistical multiplexing of traffic flows from such sources. SCR and IBT limit the medium frequency on which a connection can transmit cells. + +*Format:* + +16. XXXXXX, YYYYYY, ZZZZZ; (maximum six characters each) + +*Specifications:* + +XXXXXX Peak cell rate [cells/s] + +YYYYYY Sustainable cell rate [cells/s] + +ZZZZZ Intrinsic Burst Tolerance [cells] + +*Example:* + +For an ATM-transport link Bruxelles/XCV/BGACOM/BEL–Frankfurt/RTY/DTAG/DEU A34M1 in which the Peak cell rate = 32000 cell/s, Sustainable cell rate = not specified, intrinsic burst tolerance = not specified. + +16. 32000, , ; + +## **22.17 Cell delay variation tolerance [item 17]** + +This parameter specifies the maximum acceptable delay from the network, of the real arrival time of a cell at a UNI/INI interface compared to the theoretical arrival time of a cell at the UNI/INI interface at the same interface. + +*Format:* + +17. XXXXXX; (six characters) + +*Specifications:* + +XXXXXX Cell delay variation tolerance [s] + +*Example:* + +17. (For further study.) + +## **22.18 Quality of service [item 18]** + +These parameters characterize the quality of the connection. + +Cell error ratio is the ratio of total errored cells to the total of successfully transmitted cells. + +Cell loss ratio is the ratio of total lost cells to total transmitted cells in a population of interest. + +Cell transfer delay is the maximum delay for transferring a cell from the entry of the network to the exit of the network. + +Cell delay variation is the maximum variation of the cell transfer delay accepted between two points of the network. + +*Format:* + +18. XXXXXX,YYYYYY,ZZZZZZ,KKKKKK; (maximum six characters each) + +*Specifications:* + +XXXXXX Cell loss ratio + +YYYYYY Cell error ratio + +ZZZZZZ Cell transfer delay [s] + +KKKKKK Cell delay variation [s] + +*Example:* + +For an ATM-transport link Bruxelles/XCV/BGACOM/BEL–Frankfurt/45G/DTAG/DEU A34M1 in which are defined Cell Loss Ratio = $3 \times 10^{-7}$ , Cell Error Ratio = $3 \times 10^{-6}$ , Cell Transfer Delay = $400 \times 10^{-3}$ ms, Cell Delay Variation = $3 \times 10^{-3}$ + +18. $3 \times 10^{-7}, 3 \times 10^{-6}, 4 \times 10^{-1}, 3 \times 10^{-3};$ + +## 23 Transit network services + +### 23.1 General + +Up till now network operators/service providers (NOs/SPs) providing transit network service were aware of the terminations used by the other NOs/SPs. Presently, particularly in a multi-operator competitive environment (either domestic or international), this is no longer necessarily a desirable situation. Today's view is that the NO/SP that provides the transit network service does not need to know the actual terminations of the carried characteristic information. So, the NO(s)/SP(s) that provide(s) this kind of service does (do) not need to know the actual routing and destination inside the renter's domain. Figure 8 illustrates a transit network. + +![Diagram of a transit network showing three network operators (NO/SP 1, NO/SP 2, NO/SP 3) connected in series. Each operator's domain is represented by a box containing two grey rectangles (terminations). The connections between these rectangles are labeled 'Transit network connection'. The overall service from point A to point B is labeled 'End-to-end service'. The diagram is labeled M.1400(15)_F08.](009dd33575f64b406fa6cfed78b65248_img.jpg) + +The diagram illustrates a transit network architecture across three network domains, labeled NO/SP 1, NO/SP 2, and NO/SP 3. Each domain is enclosed in a rectangular box and contains two grey rectangular blocks representing network terminations. Within each domain, a horizontal line connects these two terminations. The connection between the second termination of one domain and the first termination of the next domain is labeled 'Transit network connection'. A long horizontal line at the bottom, spanning from point A (the first termination in NO/SP 1) to point B (the second termination in NO/SP 3), is labeled 'End-to-end service'. Vertical dashed lines separate the three domains. The diagram is identified by the text 'M.1400(15)\_F08' in the bottom right corner. + +Diagram of a transit network showing three network operators (NO/SP 1, NO/SP 2, NO/SP 3) connected in series. Each operator's domain is represented by a box containing two grey rectangles (terminations). The connections between these rectangles are labeled 'Transit network connection'. The overall service from point A to point B is labeled 'End-to-end service'. The diagram is labeled M.1400(15)\_F08. + +**Figure 8 – Transit network** + +The format for the designation of transit network services is shown in Table 12. + +**Table 12 – Format for designation of transit network services** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 2 or 3 | ≤ 4 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Transit network service terminal station A and transit network service terminal station B refer to the names of the two transmission stations in which the transit network service is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: two to three letters) + +The function code for transit network services may vary depending on the type. See clauses 23.2 and 23.3. + +c) *Serial number* (required: one to four digits) + +Identifies the instance of the transit network service. The serial numbering starts anew if there is a difference in transport relation and/or function code. For each traffic relation, the numbering of transit network services will begin from 1 and will increase by 1 for each new one. If a transit network service is deleted (i.e., it ceases to exist), its serial number can be reused without renumbering the other ones. + +## 23.2 Transit digital transmission service + +This clause deals with the transit network service consisting of a digital transmission route. This may be PDH or SDH transmission. The service is referred to as a circuit. In this case, the function code is DC. DC stands for digital circuit. + +*Example 1:* + +The first 2 Mbit/s PDH transit network service supplied by Telecom Italia connecting the WIND's building in Rome with France Telecom building in Reims (named Roma/taw and Reims/xmr respectively) will have the following designation: + +Roma/TAW/TI/ITA–Reims/XMR/FRTE/FRA DC1 + +*Example 2:* + +The first 155 Mbit/s SDH transit network service connecting the WIND's Main Site in Rome and the Telecom Italia International Exchange in Rome (named Roma/taw and Roma/tat respectively) will have the following designation: + +Roma/TAW/WIND–Roma/TAT/TI DC1 + +### **23.3 Transit dark fibre service** + +Optical fibres owned by one operator may be rented by another. This clause covers dark fibres: a bare optical fibre, i.e., without optical signals. This is referred to as "dark" because no light is turned on by the owner. Instead, providing the light is the responsibility of the renter. The dark fibre service may be built upon one single fibre or upon consecutive dark fibres in series. + +NOTE – If the fibres are offered in combination with a digital, optical or electrical interface, the previous clause applies. + +In this case, the function code is DFS. DFS stands for dark fibre service. + +*Example 1:* + +The first dark fibre service between Paris/FT1 and Strasbourg/FT1 owned by France Telecom (and possibly rented by KPN Telecom) is designated (by France Telecom): + +Paris/FT1/FRTE–Strasbourg/FT1/FRTE DFS1 + +*Example 2:* + +The third dark fibre service between Muenster and Osnabrueck in Germany owned by Deutsche Telekom (and possibly rented by Belgacom) is designated (by Deutsche Telekom): + +Muenster/DT1/DTAG–Osnabrueck/DT1/DTAG DFS3 + +### **23.4 Related information** + +The related information on transit network service is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) –; (unassigned item because no routing information applicable) +- 7) association; +- 8) equipment information; +- 9) –; (no information on use applicable) +- 10) transmission medium information; +- 11) SLA; + +- 12) bit rate; +- 13) commercial identifier; +- 14) –; (unassigned item) +- 15) clocking information; +- 16) direction of transmission (for unidirectional transit network services only). + +The various items will be dealt with in clause 24. + +## **24 Related information on transit network service** + +The following subclauses explain the items of Related information concerned with international or domestic transit network service. + +### **24.1 Urgency for restoration [item 1]** + +Normal assignment. + +### **24.2 Terminal countries [item 2]** + +Normal assignment. + +### **24.3 Names of network operators/service providers [item 3]** + +Normal assignment. + +### **24.4 Control station [sub-control station(s)] [item 4]** + +Normal assignment. + +### **24.5 Fault report points [item 5]** + +Normal assignment. + +### **24.6 Routing [item 6]** + +Not applicable. + +### **24.7 Association [item 7]** + +Normal assignment. + +### **24.8 Equipment information [item 8]** + +Normal assignment. + +### **24.9 Use [item 9]** + +Not applicable. + +### **24.10 Transmission medium information [item 10]** + +Normal assignment. + +## **24.11 SLA [item 11]** + +*Format:* + +SLA; + +*Specification:* + +It is an indicator that an SLA agreement exists between the renter operator and the leased operator(s). This reference has to be agreed bilaterally or multilaterally among the operators involved. SLA definitions and further details may be found in other ITU-T Recs, e.g., [ITU-T M.1340], [ITU-T M.1380] and [ITU-T M.1385]. + +## **24.12 Bit rate [item 12]** + +Normal assignment. + +## **24.13 Commercial identifier [item 13]** + +*Format:* + +xxx ... xx; (maximum 20 characters) + +*Specification:* + +It is a service identifier used to uniquely identify the contract between the renter operator and the leaser operator(s). This identifier has to be agreed bilaterally or multilaterally among the operators involved. + +## **24.14 Unassigned item [item 14]** + +Not applicable. + +## **24.15 Clocking information [item 15]** + +Normal assignment. + +## **24.16 Direction of transmission (for unidirectional transit network services only) [item 16]** + +Normal assignment. + +# **25 Designations for wavelength division multiplexing (simple and dense)** + +## **25.1 General** + +Wavelength division multiplexing (WDM) is an optical transport functionality that allows for the use of more than one wavelength on a fibre. The term WDM is applied if there are just two wavelengths to be combined and split by a passive element: the wave division (de)multiplexer. + +Dense wavelength division multiplexing (DWDM) is a species of WDM where combining and splitting of more than two channels with different wavelength. The actual numbers of channels may vary according to the equipment manufacturer and to the state of the technical art at given point in time; 4, 8, 16, 32 and even 64 channels are now typical figures. + +*Comment 1:* Though optical, the DWDM can use converters that convert an optical signal into an electrical one, process that signal and convert it back to optical. + +*Comment 2:* The interface is not yet a standard interface and varies per manufacturer. When [ITU-T G.692] comes into operation, this situation may change. + +*Comment 3:* The definitions for bidirectional systems (two directions in a single fibre) need further study. + +## 25.2 The equipment + +The equipment coding convention in this text is as follows: + +- WDM2: Simple wave division multiplexing using two wavelengths. +- DWDMnW. + +DWDM stands for dense wavelength division multiplexing and nW for the number of wavelengths which can be carried by the DWDM. + +This dense wavelength division multiplexer is made of three different parts: + +- The wavelength multiplexer which multiplexes the wavelengths. The abbreviation for this unit is: WMXn, (n is the number of wavelengths of the system). +- The wavelength adapter which converts the wavelength. The abbreviation for this unit is: WLAnn (nn is the number of the wavelength counted from 1 to n according to a numbering scheme for the allowed wavelengths). +- The optical (line) amplifier, which amplifies the multiplex signal. The abbreviation for this unit is: OAnW (n is the number of wavelengths and W stands for wavelength). + +Figure 9 shows an example of the scheme for a DWDM16W. + +![Diagram of a DWDM16W system showing 16 wavelength adapters (WLA) feeding into a DWDM16 unit, which then connects to an optical amplifier (OA16W).](da5a8f834706c8119a47c5eb732feabe_img.jpg) + +The diagram illustrates a DWDM16W system. On the left, there are 16 wavelength adapters (WLA) arranged in two groups of eight. Each group contains WLA1, WLA2, and WLA16. The first group is associated with the 1300 nm wavelength, and the second group with the 1550 nm wavelength. Each WLA outputs a signal at a specific wavelength (λ1, λ2, ..., λ16). These signals are multiplexed by a DWDM16 unit, specifically by its WMX16 component. The output of the WMX16 is a single stream containing all 16 wavelengths (λ1 to λ16). This stream is then amplified by an OA16W unit, which contains two optical amplifiers. The final output on the right is a 40 Gbit/s signal. The diagram is labeled 'M.1400(15)\_F09' at the bottom right. + +Diagram of a DWDM16W system showing 16 wavelength adapters (WLA) feeding into a DWDM16 unit, which then connects to an optical amplifier (OA16W). + +**Figure 9 – Example of the equipment on one side with 16 wavelengths** + +The optical regenerator: In the future it is possible to apply equipment that regenerates the optical DWDM signal. The equipment is called an optical regenerator. The abbreviation for this equipment is: OREGnW. OREG stands for optical regenerator and nW for the number of wavelengths which are regenerated. + +The optical add-drop multiplexer (OADM): It is possible now to add-drop in an optical DWDM system. The functionality of this equipment is an optical add – drop multiplexer. The abbreviation for this equipment is: OADMnW. OADM stands for optical add-drop multiplexer and nW for the number of wavelengths which can be carried by an OADM. Figure 10 shows an example of the scheme for an optical add-drop multiplexing. + +![Figure 10: Example of an optical add-drop multiplexer 16 wavelengths with 2 wavelengths extracted and inserted. The diagram shows three main components: a DWDM16W multiplexer on the left, an OADM16W add-drop multiplexer in the center, and another DWDM16W multiplexer on the right. The left DWDM16W has multiple input lines labeled λ1...λ16 and one output line labeled λ1...λ15. This output line connects to the OADM16W and is labeled 40 Gbit/s. The OADM16W has two additional input lines at the bottom labeled λ1 and λ16. The OADM16W has one output line labeled λ1...λ16, which connects to the right DWDM16W and is also labeled 40 Gbit/s. The right DWDM16W has one input line labeled λ1...λ16 and multiple output lines. A label M.1400(15)_F10 is at the bottom right.](bd33d5bc49161429f4c7da76529bcd18_img.jpg) + +Figure 10: Example of an optical add-drop multiplexer 16 wavelengths with 2 wavelengths extracted and inserted. The diagram shows three main components: a DWDM16W multiplexer on the left, an OADM16W add-drop multiplexer in the center, and another DWDM16W multiplexer on the right. The left DWDM16W has multiple input lines labeled λ1...λ16 and one output line labeled λ1...λ15. This output line connects to the OADM16W and is labeled 40 Gbit/s. The OADM16W has two additional input lines at the bottom labeled λ1 and λ16. The OADM16W has one output line labeled λ1...λ16, which connects to the right DWDM16W and is also labeled 40 Gbit/s. The right DWDM16W has one input line labeled λ1...λ16 and multiple output lines. A label M.1400(15)\_F10 is at the bottom right. + +**Figure 10 – Example of an optical add-drop multiplexer 16 wavelengths with 2 wavelengths extracted and inserted** + +A special case of OADM is the fixed optical add-drop multiplexer (FOADM); it is realized by two multiplexers in a back-to-back configuration. The dropped channels (wavelengths) are defined by optical cabling. This network element is referred to as FOADM $n$ where $n$ represents the number of wavelengths that is added/dropped at the location. + +Figure 11 shows an example of the detail scheme for an optical add-drop multiplexer. + +![Figure 11: Detail of the optical add-drop multiplexer 16 wavelengths with 2 wavelengths extracted and inserted. The diagram shows the internal structure of an OADM16W. It consists of two DWDM16W multiplexers connected back-to-back. The left DWDM16W has two optical amplifiers (OA 16W) on its left side, one pointing up and one pointing down. Its output side is connected to two wavelength line amplifiers (WLA). The first WLA has inputs λ1 and λ2, and its output is λ16. The second WLA has inputs λ1 and λ2, and its output is λ16. These two outputs are connected to the right DWDM16W. The right DWDM16W has two optical amplifiers (OA 16W) on its right side, one pointing up and one pointing down. Its input side is connected to two wavelength line amplifiers (WLA). The first WLA has an input λ16 and an output λ1. The second WLA has an input λ16 and an output λ1. The final outputs on the far right are labeled λ1-λ16. A label M.1400(15)_F11 is at the bottom right.](c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg) + +Figure 11: Detail of the optical add-drop multiplexer 16 wavelengths with 2 wavelengths extracted and inserted. The diagram shows the internal structure of an OADM16W. It consists of two DWDM16W multiplexers connected back-to-back. The left DWDM16W has two optical amplifiers (OA 16W) on its left side, one pointing up and one pointing down. Its output side is connected to two wavelength line amplifiers (WLA). The first WLA has inputs λ1 and λ2, and its output is λ16. The second WLA has inputs λ1 and λ2, and its output is λ16. These two outputs are connected to the right DWDM16W. The right DWDM16W has two optical amplifiers (OA 16W) on its right side, one pointing up and one pointing down. Its input side is connected to two wavelength line amplifiers (WLA). The first WLA has an input λ16 and an output λ1. The second WLA has an input λ16 and an output λ1. The final outputs on the far right are labeled λ1-λ16. A label M.1400(15)\_F11 is at the bottom right. + +**Figure 11 – Detail of the optical add-drop multiplexer 16 wavelengths with 2 wavelengths extracted and inserted** + +### 25.3 Configurations for the newly created transmission systems + +This clause deals with multiplex sections on the DWDM as defined in [ITU-T G.692] and [ITU-T G.872]. + +According to the terminology used throughout this Recommendation, the newly created higher-order multiplex section will be addressed as an optical multiplex section. It includes the multiplex equipment. The lower-order multiplex section will be called an *optical channel*. No multiplex equipment is involved on this level. If optical amplifiers are required, then *optical amplifier sections* are being created (not shown in the figures below) and if an optical regenerator is applied due to long distances or poor fibre performance before and after this regenerator, an *optical regenerator section* will be identified. + +There are three different configurations to use DWDM equipment and each deserves a distinct registration. + +*Configuration 1:* + +The use of wavelength adapters in both sides of the DWDM equipment. + +Figure 12 shows an example. + +![Schematic diagram of a DWDM system with wavelength adapters on both sides.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +The diagram illustrates a DWDM system configuration. At the top, a horizontal line labeled '4S' spans the entire width. Below it, on the left side, three input signals are shown: '1300 nm' entering an 'ADM4' block, '1550 nm' entering an 'ADM 16' block, and '1550 nm' entering a 'QDMX' block. Each of these blocks is connected to a 'WLA' block: 'WLA1', 'WLA2', and 'WLA16' respectively. The outputs of these WLA blocks are labeled $\lambda 1$ , $\lambda 2$ , and $\lambda \dots$ . These signals enter a 'WMX 16' block. The output of the 'WMX 16' block enters an 'OA16W' block. The output of the 'OA16W' block is labeled $\lambda 1 \dots 16$ and enters an 'OREG 16W' block. The output of the 'OREG 16W' block is also labeled $\lambda 1 \dots 16$ and enters another 'OA16W' block. The output of this 'OA16W' block enters a second 'WMX 16' block. The output of this 'WMX 16' block is labeled $\lambda 1$ , $\lambda 2$ , and $\lambda \dots$ . These signals enter 'WLA1', 'WLA2', and 'WLA16' blocks respectively. The outputs of these WLA blocks are labeled '1300 nm', '1300 nm', and '1300 nm'. These signals enter 'ADM4', 'ADM 16', and 'QDMX' blocks respectively. Below the main signal path, there are three nested horizontal lines with arrows indicating different sections: 'Optical regenerator' (spanning the OREG 16W block), 'Sections 1 and 2' (spanning the two OA16W blocks), 'Higher order multiplex section (optical block)' (spanning the two WMX 16 blocks), and 'Lower order multiplex section (optical line system)' (spanning the entire central part from the first WMX 16 to the second WMX 16). At the bottom, a horizontal line labeled '1920N' spans the entire width. In the bottom right corner, the text 'M.1400(15)\_F12' is present. + +Schematic diagram of a DWDM system with wavelength adapters on both sides. + +**Figure 12 – Example of the scheme for DWDM with wavelength adapters on both sides** + +*Configuration 2:* + +The use of wavelength adapters is only at the receive side of the DWDM equipment. The sending side does not have wavelength adapters and the PDH/SDH equipment has the possibility to recognize the DWDM wavelength. + +Figure 13 shows an example. + +![Schematic diagram of a DWDM system with wavelength adapters on one side. The diagram shows a bidirectional optical path. On the left (transmit side), multiple input signals (ADM4, ADM16 at 1550 nm, and QDMX) are connected to wavelength adapters (WLA1, WLA2, WLA16) which output specific wavelengths (λ1, λ2, λ...). These are multiplexed by a WMX unit. The signal then passes through an optical amplifier (OA16W), an optical regenerator (OREG 16W), and another optical amplifier (OA16W). On the right (receive side), the signal is demultiplexed by a WMX 16 unit into the same set of wavelengths (λ1, λ2, λ...), which are then received by the corresponding ADM4, ADM16, and QDMX units. The diagram is divided into three nested sections: 'Sections 1 and 2' (between the two OAs), 'Higher order multiplex section (optical multiplex section)' (between the WMX and WMX 16 units), and 'Lower order multiplex section (optical channel)' (between the WLA units and the WMX units). The total length is labeled '4S' at the top and '1920N' at the bottom. A label 'M.1400(15)_F13' is in the bottom right corner.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +Diagram illustrating the scheme for DWDM with wavelength adapters on one side. The system is divided into three main sections: Higher order multiplex section (optical multiplex section), Lower order multiplex section (optical channel), and Sections 1 and 2. The components shown include ADM4, WLA1, WLA2, QDMX, WMX, OA16W, OREG 16W, and WMX 16. The diagram shows multiple wavelengths (λ1, λ2, λ...) being transmitted and received. The total length of the system is indicated as 4S and 1920N. The label M.1400(15)\_F13 is present in the bottom right corner. + +Schematic diagram of a DWDM system with wavelength adapters on one side. The diagram shows a bidirectional optical path. On the left (transmit side), multiple input signals (ADM4, ADM16 at 1550 nm, and QDMX) are connected to wavelength adapters (WLA1, WLA2, WLA16) which output specific wavelengths (λ1, λ2, λ...). These are multiplexed by a WMX unit. The signal then passes through an optical amplifier (OA16W), an optical regenerator (OREG 16W), and another optical amplifier (OA16W). On the right (receive side), the signal is demultiplexed by a WMX 16 unit into the same set of wavelengths (λ1, λ2, λ...), which are then received by the corresponding ADM4, ADM16, and QDMX units. The diagram is divided into three nested sections: 'Sections 1 and 2' (between the two OAs), 'Higher order multiplex section (optical multiplex section)' (between the WMX and WMX 16 units), and 'Lower order multiplex section (optical channel)' (between the WLA units and the WMX units). The total length is labeled '4S' at the top and '1920N' at the bottom. A label 'M.1400(15)\_F13' is in the bottom right corner. + +**Figure 13 – Example of the scheme for DWDM with wavelength adapters on one side** + +*Configuration 3:* + +DWDM equipment without wavelength adapters. The sending and receive sides do not have these adapters and the PDH/SDH equipment has the possibility to transmit and recognize the DWDM wavelength. In this case the optical line systems do not exist. + +Figure 14 shows an example. + +![Figure 14: Example of the scheme for DWDM without wavelength adapters. The diagram shows a bidirectional optical transmission path. On the left, ADM4, ADM16, and QDMX units are connected to a WMX 16 unit via wavelengths λ1, λ2, and λ.... respectively. The WMX 16 unit is part of a 'Higher order multiplex section (optical multiplex section)'. The signal then enters an OA16W optical amplifier, followed by an OREG 16W optical regenerator, and then another OA16W optical amplifier. These three components are collectively labeled as an 'Optical regenerator'. The path continues through a second WMX 16 unit, which is part of 'Sections 1 and 2'. On the right side, the signals are split back to ADM4, ADM16, and QDMX units via wavelengths λ1, λ2, and λ.... respectively, with '...nm' indicating additional wavelengths. The entire assembly is labeled '4S' at the top and '1920N' at the bottom. The diagram is identified by 'M.1400(15)_F14' in the bottom right corner.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +Figure 14: Example of the scheme for DWDM without wavelength adapters. The diagram shows a bidirectional optical transmission path. On the left, ADM4, ADM16, and QDMX units are connected to a WMX 16 unit via wavelengths λ1, λ2, and λ.... respectively. The WMX 16 unit is part of a 'Higher order multiplex section (optical multiplex section)'. The signal then enters an OA16W optical amplifier, followed by an OREG 16W optical regenerator, and then another OA16W optical amplifier. These three components are collectively labeled as an 'Optical regenerator'. The path continues through a second WMX 16 unit, which is part of 'Sections 1 and 2'. On the right side, the signals are split back to ADM4, ADM16, and QDMX units via wavelengths λ1, λ2, and λ.... respectively, with '...nm' indicating additional wavelengths. The entire assembly is labeled '4S' at the top and '1920N' at the bottom. The diagram is identified by 'M.1400(15)\_F14' in the bottom right corner. + +**Figure 14 – Example of the scheme for DWDM without wavelength adapters** + +## 25.4 General format for the optical transmission systems + +The optical transmission systems are designated according to the general format. We recognize four system types to describe the coupling of the DWDM equipment: + +- the optical regenerator section; +- the optical amplifier section; +- the optical multiplex section (multiplex section at higher order); +- the optical channel (multiplex section at lower order between two wavelength adapters). + +These four system types have their own function codes; see clause 25.4.1. + +The format of designation of optical transmission systems in (D)WDM is shown in Table 13: + +**Table 13 – (D)WDM optical transmission system designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 2 to 3 | ≤ 4 | + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Optical transmission system terminal station A and Optical transmission system terminal station B refer to the names of the two transmission stations in which the optical transmission system is terminating. The name of each transmission station consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: two to three letters) + +This code identifies the type of optical transmission system; see clause 25.4.1. + +c) *Serial number* (required: one to four digits) + +Identifies the instance of the optical transmission system. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +#### 25.4.1 The function codes + +##### 25.4.1.1 The optical regenerator section (ORS) + +This clause applies in case where DWDM with an optical regenerator is used. + +A regenerator section is defined as being between the optical amplifier just next to the DWDMMultiplexer and an optical regenerator, or between two consecutive optical regenerators. The function code for the optical regenerator section is DWDMMultiplexer ORS. It should be noted that this code is independent of the number of channels carried. + +*Example 1:* + +A third optical regenerator section (between an amplifier in Bruxelles/KQ1 and a regenerator in Paris/KQ1) is designated as: + +Bruxelles/KQ1/BGACOM/BEL–Paris/KQ1/FRTE/FRA ORS3. + +#### **25.4.1.2 The optical amplifier section** + +An amplifier section is defined as being between a first multiplexer and a first amplifier, between two consecutive amplifiers and between a last amplifier in the route and a final multiplexer. The function code is OAS. + +*Example 2:* + +The second optical regenerator section between an amplifier in London/KQ1 and Lille/KQ1 is designated as: + +London/KQ1/BTPLC/GBR–Lille/KQ1/FRTE/FRA OAS2. + +#### **25.4.1.3 The optical multiplex section** + +Such a block is defined as being from one DWDMMultiplexer to another. The equipment components are a part of the block. The function code for the optical block is OMS. It should be noted that this code is independent of the number of channels carried. + +*Example 3:* + +The eleventh optical block (e.g., carrying 16 channels with 2.5 Gbit/s) between London/BT1 and Paris/FT1 is designated as: + +London/BT1/BTPLC/GBR–Paris/FT1/FRTE/FRA OMS11. + +#### **25.4.1.4 The optical channel (OC)** + +This clause applies when DWDM is used with wavelength adapters. + +Such a system is defined as being between two corresponding wavelength adapters. The function code for the optical line system is: OC. If the adapters are built into other equipment, the "OC" may not be registered as a separate resource. In this case, the use of OC is optional. + +*Example 4:* + +The fourth optical line system between Amsterdam/KP1 and Roma/TI1 is designated as: + +Amsterdam/KP1/TCOMNL/NLD–Roma/TI1/TI/ITA OC4. + +Figure 15 presents an example of the scheme with the function codes. + +![Figure 15: Example of the DWDM scheme with the function codes. The diagram shows a DWDM system with three main sections: Transmission station A, Station B, and Transmission station C. Station A contains ADM4, ADM 16, and QDMX units connected to WLA1, WLA2, and WLA16 units, which are then connected to a WMX unit. Station B contains OREG 16W and OA16W units. Station C contains WMX 16, WLA1, WLA2, and WLA16 units, which are then connected to ADM4, ADM 16, and QDMX units. Various optical paths are shown with labels like A-C 4S1, A-C OC1, A-B ORS1, B-C ORS1, A-C OB1, A-C OC16, and A-C 1920N1. Wavelengths are indicated as 1300 nm, 1550 nm, and λ1, λ2, λ....](68b20651884fcd557e865537f0803de5_img.jpg) + +Figure 15: Example of the DWDM scheme with the function codes. The diagram shows a DWDM system with three main sections: Transmission station A, Station B, and Transmission station C. Station A contains ADM4, ADM 16, and QDMX units connected to WLA1, WLA2, and WLA16 units, which are then connected to a WMX unit. Station B contains OREG 16W and OA16W units. Station C contains WMX 16, WLA1, WLA2, and WLA16 units, which are then connected to ADM4, ADM 16, and QDMX units. Various optical paths are shown with labels like A-C 4S1, A-C OC1, A-B ORS1, B-C ORS1, A-C OB1, A-C OC16, and A-C 1920N1. Wavelengths are indicated as 1300 nm, 1550 nm, and λ1, λ2, λ.... + +**Figure 15 – Example of the DWDM scheme with the function codes** + +## 25.5 Related information + +The related information on DWDM is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bit rate; +- 13) occupancy; +- 14) access point identifiers. + +The various items will be dealt with in clause 26. + +## 26 Related information on DWDM + +The related information on optical transmission in DWDM is indicated in Table 14: + +Further study is needed on the development of association codes for protection of WDM systems. + +**Table 14 – Information related to DWDM optical transmission systems** + +| Item | For optical multiplex section (OMS) | For optical regenerator section (ORS) | For optical amplifier section (OAS) | For optical channel (OC) | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| 1) Urgency for restoration | Normal assignment | Normal assignment | Normal assignment | Normal assignment | +| 2) Terminal countries | Normal assignment | Normal assignment | Normal assignment | Normal assignment | +| 3) Names of network operators/service providers | Normal assignment | Normal assignment | Normal assignment | Normal assignment | +| 4) Control and sub-control station(s) | Normal assignment | Normal assignment | Normal assignment | Normal assignment | +| 5) Fault report points | Normal assignment | Normal assignment | Normal assignment | Normal assignment | +| 6) Routing | OAS or ORS or the fibre | Pair of fibre | Pair of fibres | OMS | +| 7) Association | Not applicable | Not applicable | Not applicable | Set of OC on direction West and East respectively | +| 8) Equipment information | – Maximum number channels/wavelengths
– ITU-T G.692 if applicable or manufacturer type | – Maximum number of channels/wavelengths
– ITU-T G.692 if applicable or manufacturer type | – Maximum number of channels/wavelengths
– ITU-T G.692 if applicable or manufacturer type | ITU-T G.692 if applicable or manufacturer type | +| 9) Use | Not applicable | Not applicable | Not applicable | Not applicable | +| 10) Transmission medium information | SMF = single mode fibre
DSF = dispersion shift fibre
NZ DSF+ = non-zero DSF+
NZ DSF– = non-zero DSF–
Other | SMF = single mode fibre
DSF = dispersion shift fibre
NZ DSF+ = non-zero DSF+
NZ DSF– = non-zero DSF–
Other | SMF = single mode fibre
DSF = dispersion shift fibre
NZ DSF+ = non-zero DSF+
NZ DSF– = non-zero DSF–
other | No | +| 11) Operational agreement | Normal assignment | Normal assignment | Normal assignment | Normal assignment | +| 12) Bit rate | Normal assignment | No | No | No | +| 13) Occupancy | Position in the block:
designation of client | Designation of OMS carried | Designation of OMS carried | Designation of SDH or PDH system | +| 14) Access point identifiers | Not applicable | Not applicable | Not applicable | Not applicable | + +## 27 Designation of connections for the digital subscriber line (DSL) + +### 27.1 General + +This clause deals with connections for the digital subscriber line (DSL) as defined in the family of ITU-T Recommendations: [ITU-T G.991.1], [ITU-T G.992.1], [ITU-T G.992.2], [ITU-T G.994.1], [ITU-T G.996.1] and [ITU-T G.997.1]. + +Within the access network, some DSL connections can be created between two equipments: a customer premises equipment (CPE) on the customer side and a digital subscriber line access multiplexer (DSLAM) on the operator side. According to the type of cards contained in the DSLAM, the DSL connection will be symmetrical (SDSL connection) or asymmetrical (ADSL connection). + +In the following, an xDSL connection will represent either an ADSL connection or an SDSL connection. + +The format of designation of xDSL connections is shown in Table 15: + +**Table 15 – xDSL connection designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character Types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 2 to 6 | 1 to 4 | + +↑ +No space + +#### 27.1.1 ADSL connection + +ADSL connections are based upon bare copper connections. An ADSL connection uses one and only one bare copper connection. One bare copper connection can only be used once in the routing of an ADSL connection. From a network point of view, the bare copper connection belongs to the server layer and the ADSL connection to the client layer. + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +ADSL connection termination A and ADSL connection termination B refer to the names of the two extremities in which the ADSL connection is terminating. The name of each termination consists of the following elements: geographical area name, node detail, operator ID and country code. The order of the two terminations is arranged according to alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the terminal equipments are situated (required: one to twelve characters or space). + +*Termination detail* shows the information that makes the extremity of an ADSL connection unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the extremity identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: two to six letters and/or digits) + +This function code is **8448A** (8448 kbit/s being the maximum bit rate of an ADSL connection and the character "A" being set for ADSL). + +- c) *Serial number* (required: one to four digits) + +Identifies the instance of the ADSL connection. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example:* + +The second 64 kbit/s ADSL connection between two nodes in Toulouse, using France Telecom copper lines and a DSLAM belonging to Deutsche Telekom will be designed as: + +Toulouse/Matab/FRTE/FRA–Toulouse/Balma/DTAG/DEU 8448A2 + +### 27.1.2 ADSL Layer 2 + +The related information on ADSL is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) operational agreement; +- 12) bandwidth; +- 13) occupancy; +- 14) actual number of channel/access point identifiers; +- 15) clocking information; +- 16) direction of transmission; + +The various items will be dealt with in clause 27.2. + +### 27.1.3 Symmetric digital subscriber line (SDSL) connection + +Symmetric digital subscriber line (SDSL) connections are based upon bare copper connections. An SDSL connection uses one bare copper connection or several bare copper connections in parallel. One bare copper connection can only be used once in the routing of an SDSL connection. From a network point of view, the bare copper connection belongs to the server layer and the SDSL connection to the client layer. + +The elements of the Layer 1 format are as follows: + +- a) *Transport relation* + +SDSL connection termination A and SDSL connection termination B refer to the names of the two extremities in which the SDSL connection is terminating. The name of each termination consists of the following elements: Geographical area name, node detail, operator ID and country code. The order of the two terminations is arranged according to alphabetical order of the respective Geographical area names. + +*Geographical area*: the geographical area where the terminal equipments are situated (required: one to twelve characters or space). + +*Termination detail* shows the information that makes the extremity of an SDSL connection unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the extremity identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +- b) *Function code* (format: two to six letters and/or digits) + +This function code is built from: + +- A bit rate information that represents the maximum bit rate of the SDSL connection; +- A character "S" set for SDSL. + +*Format*: + +xxxxS where x is a numerical value from 0 to 9 + +*Examples*: + +8448S + +4224S + +- c) *Serial number* (required: one to four digits) + +Identifies the instance of SDSL connection. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +*Example*: + +The first 4 Mbit/s SDSL connection sold by France Telecom between two nodes in Paris will be designed as: + +Paris/Monp1 – Paris/Bertra 4224S1 + +#### 27.1.4 SDSL Layer 2 + +The related information on SDSL is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; + +- 11) operational agreement; +- 12) bandwidth; +- 13) occupancy; +- 14) actual number of channel/access point identifiers; +- 15) clocking information; +- 16) direction of transmission. + +The various items will be dealt with in clause 27.3. + +## **27.2 Related information for the ADSL connections** + +The following subclauses explain the items of Related information concerned with ADSL connections: + +### **27.2.1 Urgency for restoration [item 1]** + +Normal assignment. + +### **27.2.2 Terminal countries [item 2]** + +Normal assignment. + +### **27.2.3 Names of network operators/service providers [item 3]** + +Normal assignment. + +### **27.2.4 Control and sub-control station(s) [item 4]** + +Not applicable. + +### **27.2.5 Fault report points [item 5]** + +Normal assignment. + +### **27.2.6 Routing [item 6]** + +Normal assignment. + +### **27.2.7 Association [item 7]** + +Not applicable. + +### **27.2.8 Equipment information [item 8]** + +Normal assignment. + +### **27.2.9 Use [item 9]** + +Not applicable. + +### **27.2.10 Transmission medium information [item 10]** + +Normal assignment. + +### **27.2.11 Operational agreement [item 11]** + +Normal assignment. + +### **27.2.12 Bandwidth [item 12]** + +This item shows the real bit rate of the ADSL connection. + +*Format:* + +12. xxxx kbit/s or Mbit/s; + +Rules for the notation of the bandwidth figures: + +No leading zeros required. + +If the figure is between 0 and 9999, use kbit/s, else use Mbit/s. + +*Example:* + +A 64 kbit/s ADSL connection: + +Toulouse/Matab/FRTE–Toulouse/Balma/DTAG 8448A2 + +12. 64 kbit/s; + +### **27.2.13 Occupancy [item 13]** + +Normal assignment. + +### **27.2.14 Actual number of channel/access point identifiers [item 14]** + +Not applicable. + +### **27.2.15 Clocking information [item 15]** + +Normal assignment. + +### **27.2.16 Direction of transmission [item 16]** + +Normal assignment. + +## **27.3 Related information for the SDSL connection** + +The following subclauses explain the items of related information concerned with SDSL connections: + +### **27.3.1 Urgency for restoration [item 1]** + +Normal assignment. + +### **27.3.2 Terminal countries [item 2]** + +Normal assignment. + +### **27.3.3 Names of network operators/service providers [item 3]** + +Normal assignment. + +### **27.3.4 Control and sub-control station(s) [item 4]** + +Not applicable. + +### **27.3.5 Fault report points [item 5]** + +Normal assignment. + +### **27.3.6 Routing [item 6]** + +Normal assignment. + +### **27.3.7 Association [item 7]** + +Not applicable. + +### **27.3.8 Equipment information [item 8]** + +Normal assignment. + +### **27.3.9 Use [item 9]** + +Not applicable. + +### **27.3.10 Transmission medium information [item 10]** + +This item shows the number of pairs of copper lines used for the given SDSL connection. + +*Format:* + +10. xP where x is a numerical value from 0 to 9 + +*Example:* + +10. 2P + +### **27.3.11 Operational agreement [item 11]** + +Normal assignment. + +### **27.3.12 Bandwidth [item 12]** + +This item shows the real bit rate of the SDSL connection. + +*Format:* + +12. xxxx kbit/s or Mbit/s; + +Rules for the notation of the bandwidth figures: + +No leading zeros required. + +If the figure is between 0 and 9999, use kbit/s, else use Mbit/s. + +*Example:* + +A 64 kbit/s SDSL connection: + +Toulouse/Matab/FRTE/FRA–Toulouse/Balma/DTAG/DEU 8448A2 + +12. 64 kbit/s; + +### **27.3.13 Occupancy [item 13]** + +Normal assignment. + +### **27.3.14 Actual number of channel/access point identifiers [item 14]** + +Not applicable. + +### **27.3.15 Clocking information [item 15]** + +Normal assignment. + +### **27.3.16 Direction of transmission [item 16]** + +Normal assignment. + +## **27.4 Examples** + +The first 4 Mbit/s SDSL connection (using two pairs of copper lines) sold by France Telecom between two nodes in Paris will be designed as: + +Paris/Monp1–Paris/Bertra 4224S1 + +10. 2P +12. 4224 kbit/s + +The second 64 kbit/s ADSL connection between two nodes in Toulouse, using France Telecom copper lines and a DSLAM belonging to Deutsche Telekom will be designed as: + +Toulouse/Matab/FRTE/FRA–Toulouse/Balma/DTAG/DEU 8448A2 + +12. 64 kbit/s + +## 28 Exceptional designations + +This clause deals with designations that are temporarily tolerated until the Related information in this Recommendation is generally applied. These designations namely do not comply with the spirit of the Recommendation because they violate the regular use of traffic relation, function code or serial numbering. In the latter case, such an exceptional designation may contain information in the serial number. + +### 28.1 Exceptional designations with intelligence in the serial number + +#### Rationale + +Operational staff want to see as quickly as possible what spare routes are available in case a telecommunication system breaks down. This need may lead to the wish to recognize from the Layer 1 designation what dedicated restoration routes are available, and which dedicated restoration route is the back-up for the interrupted main route. This information can be supplied by the serial number as follows: + +The main route and the dedicated back-up route share the traffic relation and the function code; the serial number for the main route is as usual but the serial number of the dedicated back-up route is precisely 8000 higher; so if the serial number of the main route is xx, the serial number of the back-up route is 80xx. + +Therefore, in the case of dedicated restoration routes, the designations are: + +For the main route of the usual type: A-B Function code xx + +For the dedicated protection route a special type: A-B Function code 80xx + +Example: + +In the case of a Virtual Container-4 on a submarine cable between the United Kingdom and Spain, the main route may be designated as: + +Brighton-Valladolid VC4S1 with a dedicated restoration route: + +Brighton-Valladolid VC4S8001 + +#### Corresponding correct registration + +The correct designations according to the spirit of this Recommendation are (see clauses 19 and 20): + +For the main route: A-B Function code serial number and + +For the restoration route: A-B Function code another serial number + +in combination with the item Association from the Related information as follows: + +For the main route, e.g., a VC-4: A-B VC4S1: + +Item 7 Association: 7. S1: A-B VC4S2 + +And for the restoration route A-B VC4S2: + +Item 7 Association: 7. S2: A-B VC4S1 + +## 29 Designation of optical transport networks + +### 29.1 General + +This clause applies to optical channel transport units, optical channel data units, and their bit rates as defined in [ITU-T G.709] and [b-ITU-T G.Suppl. 43]. + +The format of designations of optical channel transport units and data units is shown in Table 16. + +**Table 16 –Optical transport network designation format** + +| Format of designation | Geographical Area A | / | Termination detail | / | Operator ID | / | Country code | - | Geographical Area B | / | Termination detail | / | Operator ID | / | Country code | | Function code | Serial number | +|-----------------------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|--------|---------------------|-------|--------------------|-------|-------------------|-------|--------------|-------|-------------------|---------------| +| Character types | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Hyphen | Letters or space | Slash | Letters or digits | Slash | Letters or digits | Slash | Letters | Space | Letters or digits | Digits | +| Number of characters | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | ≤ 12 | 1 | ≤ 6 | 1 | ≤ 6 | 1 | 3 | 1 | 3 to 5 | 1 to 3 | + +↑ +No space + +The elements of the Layer 1 format are as follows: + +a) *Transport relation* + +Data Transmission System Terminal Station A and Data Transmission System Terminal Station B refer to the names of the two transmission stations or optical channel data units in which the data transmission system is terminating. The name of each transmission station or optical channel data unit consists of the following elements: geographical area name, transmission station detail, operator ID and country code. The order of the two transmission stations or optical channel data units is arranged according to the alphabetical order of the respective geographical area names. + +*Geographical area*: the geographical area where the transmission station is situated (required: one to twelve characters or space). + +*Transmission station detail* shows the information that makes the transmission station unique in the operator domain in that particular geographical area. Format: one to six letters and/or digits. + +*Operator ID* is the identification of the operator that created the transmission station identification. Format: ICC (consisting of one to six letters and/or digits). + +*Country code* identifies the country in which the geographical area is located. Format: [ISO 3166-1] alpha-3 code. + +b) *Function code* (format: three to five letters and/or digits) + +The following function codes are defined for optical channel transport units (OTUs): + +| Function code | Bit rate | +|---------------|----------------------------------------------------------------------------------------------------------------------------------| +| OTU1S | 2.666 Gb/s [ITU-T G.709] | +| OTU2S | 10.709 Gb/s (OTU2) [ITU-T G.709]
or 11.09 Gb/s (OTU2e) [b-ITU-T G.Suppl. 43] | +| OTU3S | 43.018 Gb/s (OTU3) [ITU-T G.709]
or 44.57 Gb/s (OTU3e1) [b-ITU-T G.Suppl. 43]
or 44.58 Gb/s (OTU3e2) [b-ITU-T G.Suppl. 43] | +| OTU4S | 111.809 Gb/s [ITU-T G.709] | + +NOTE 1 – The letter "S" separates number representing the bit rate in the function code from the serial number that follows it (as shown in Example 1 below). + +The following function codes are defined for optical channel data units (ODUs): + +| Function code | Bit rate | +|---------------|----------------------------------------------------------------------------------| +| ODUF | ODUflex [ITU-T G.709] | +| ODU0S | 1.25 Gb/s [ITU-T G.709] | +| ODU1S | 2.5 Gb/s [ITU-T G.709] | +| ODU2S | 10.037 Gb/s (ODU2) [ITU-T G.709]
or 10.399 Gb/s (ODU2e) [ITU-T G.709] | +| ODU3S | 40.319 Gb/s (ODU3) [ITU-T G.709]
or 44.57 Gb/s (ODU3e1) [b-ITU-T G.Suppl. 43] | +| ODU4S | 104.79 Gb/s (ODU4) [ITU-T G.709] | + +NOTE 2 – Except for function code "ODUF", the letter "S" separates the number representing the bit rate in the function code from the serial number that follows it (as shown in Example 2 below). + +c) *Serial number* (required: one to three digits) + +Identifies the instance of the transmission system. The serial numbering starts anew if there is a difference in transport relation and/or function code. + +NOTE 3 – The use of the data transmission system (e.g., multiplex of digital leased circuits, broadcasting, video) will be recorded in Related information under Item 9 (Use) (see clause 20.9). + +## 29.2 Data transmission links + +Data transmission links are designated as data transmission systems. + +*Example 1:* + +The first 10.7 Gigabit optical transmission network (OTN) data transmission system between Dubai and Montreal: + +Dubai/ERD/MOPPT/SAU–Montreal/TGB/CAN OTU2S1. + +![Diagram of a single optical channel (OCh) with reduced functionality. It shows two ITU-T G.709 boxes connected by a thick line to a central oval labeled 'Proprietary wave division multiplex (WDM) system'. A dashed line runs through the center of the oval. A double-headed arrow at the bottom spans from the left ITU-T G.709 box to the right one, with the label 'M.1400(15)_F16' at the bottom right.](87f79156de933ff5c41b6698ee88e5bc_img.jpg) + +Diagram of a single optical channel (OCh) with reduced functionality. It shows two ITU-T G.709 boxes connected by a thick line to a central oval labeled 'Proprietary wave division multiplex (WDM) system'. A dashed line runs through the center of the oval. A double-headed arrow at the bottom spans from the left ITU-T G.709 box to the right one, with the label 'M.1400(15)\_F16' at the bottom right. + +**Figure 16 – Single optical channel (OCh) with reduced functionality** + +*Example 2:* + +The first 10 Gigabit optical data unit (ODU) between Dubai and Montreal: + +Dubai/ERD/MOPPT/SAU–Montreal/TGB/CAN ODU2S1. + +## 29.3 Related information + +The additional information on data transmission systems is covered by the following items: + +- 1) urgency for restoration; +- 2) terminal countries; + +- 3) names of network operators/service providers; +- 4) control and sub-control station(s); +- 5) fault report points; +- 6) routing; +- 7) association; +- 8) equipment information; +- 9) use; +- 10) transmission medium information; +- 11) composition of transmission; +- 12) (unassigned item, use: "-;"); +- 13) occupancy. + +The various items are dealt with in clause 20. + +## Annex A + +### Full examples for designation information + +(This annex forms an integral part of this Recommendation.) + +#### A.1 Full example for the designation information of a public switched telephone circuit + +The circuit is the 604th both-way telephone circuit between Sherman Oaks 4ES and Tokyo Shinjuku, operated by AT&T and KDDI. The signalling type is ITU-T No. 6 with band/circuit number assigned as 000/03. The control station and sub-control station of the circuit are Sherman Oaks-transmission station 1 and Tokyo-transmission station 1 respectively. Both stations are also the fault report points of the circuit. The circuit has been routed on the fourth channel of the first group between Sherman Oaks and Ibaraki which is routed via satellite and has been connected to digital blocks in domestic networks. + +*Designation:* + +Sherman Oaks/4ES/ATT/USA–Tokyo/SJK/KDDI/JPN B604 + +*Related information:* + +1. 2; +2. USA, JPN; +3. ATT, KDDI; +4. CS: Sherman Oaks/TS1/ATT/USA, +SCS1: Tokyo/TS1/KDDI/JPN; +5. Sherman Oaks/TS1/ATT/USA, Tokyo/TS1/KDDI/JPN; +6. Ibaraki/2SD/KDDI/JPN–Sherman Oaks/EC/ATT/USA 12C01/4; +7. –; +8. –; +9. –; +10. ST; +11. C; +12. 3.4 kHz; +13. C6, 000/03. + +#### A.2 Full example for the designation information of a leased analogue circuit + +The circuit is the first analogue leased circuit used for data transmission between London and Frankfurt, operated by British Telecom International and the Deutsche Telekom. The signalling type is 500 Hz/20 Hz. The control station and sub-control station of the circuit are London Mollison and Frankfurt 0 respectively. Both stations are also the fault report points of the circuit. The circuit is routed on the third channel of the first group between Frankfurt and London. As regards the parameters of the circuit, [ITU-T M.1020] is applied. The maintenance contract between network operators/service providers and customer is repair within 24 hours. + +*Designation:* + +Frankfurt/ERT/DTAG/DEU–London/EVC/BTPLC/GBR DP1 + +*Related information:* + +1. $\leq 24$ h; +2. DEU, GBR; +3. DTAG, BTPLC; +4. CS: London/SM/BTPLC/GBR, +SCS1: Frankfurt/0/DTAG/DEU; +5. Frankfurt/0/DTAG/DEU, London/SM/BTPLC/GBR; +6. Frankfurt/ERT/DTAG/DEU–London/EVC/BTPLC/GBR 1201/3; +7. –; +8. –; +9. D; +10. –; +11. A; +12. 3.4 kHz; +13. 500/20; +14. Rec. ITU-T M.1020. + +### **A.3 Full examples for the designation information of a group and a group link interconnection** + +#### **A.3.1 Full example for the designation information of a group interconnection** + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +The interconnecting group is the fifth group between Amsterdam and Paris. The urgency for restoration (1) is third priority, the terminal countries (2) are the Netherlands and France, the network operators/service providers involved (3) are the Netherlands KPN Telecom and France Telecom, the control station and sub-control station (4) are Paris Archives and Amsterdam 1 respectively, the fault report points (5) are Amsterdam 2 and Paris Archives, the routing (6) of the group is in the supergroup Amsterdam–Bruxelles 6011 on position 1 and in the supergroup Bruxelles–Paris 6002 on position 3, there is an associated group (7) carrying traffic but indicated for restoration, namely Amsterdam–Paris 1209, there is special equipment involved (8) because the group is carrying companded circuits, the use (9) is: Z-circuits and a DP circuit, no satellite (10) is involved, no end-to-end information (11) is to be recorded, the bandwidth (12) is 48 kHz and the occupancy (13) is to be seen from the example. + +*Designation:* + +Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA 1205 + +*Related information:* + +1. 3; +2. NLD, FRA; +3. TCOMNL, FRTE; +4. CS: Paris/ARC/FRTE/FRA, +SCS1: Amsterdam/1/TCOMNL/NLD; +5. Amsterdam/2/TCOMNL/NLD, Paris/ARC/FRTE/FRA; +6. Amsterdam/EDC/TCOMNL/NLD–Bruxelles/ZZC/BGACOM/BEL 6011/1, +Bruxelles/ZZC/BGACOM/BEL–Paris/ARC/FRTE/FRA 6002/3; +7. S1205: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA 1209; + +8. CO; +9. Z, DP; +10. –; +11. –; +12. 48 kHz; +13. 01: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA Z111, +02: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA Z113, +03: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA Z115, +04: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA Z117, +05: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA Z119, +06: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA Z121, +07: Paris/ARC/FRTE/FRA–Amsterdam/EDC/TCOMNL/NLD Z120, +08: Paris/ARC/FRTE/FRA–Amsterdam/EDC/TCOMNL/NLD Z122, +09: Paris/ARC/FRTE/FRA–Amsterdam/EDC/TCOMNL/NLD Z124, +10: Paris/ARC/FRTE/FRA–Amsterdam/EDC/TCOMNL/NLD Z126, +11: Paris/ARC/FRTE/FRA–Amsterdam/EDC/TCOMNL/NLD Z128, +12: Amsterdam/EDC/TCOMNL/NLD–Paris/ARC/FRTE/FRA DP5. + +### A.3.2 Full example for the designation information of a group link interconnection + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +The link is the first restoration group link between Paris and Genève. The urgency for restoration (1) is third priority, the terminal countries (2) are Switzerland and France, the network operators/service providers (3) are Swisscom and France Telecom, the control and sub-control stations (4) are Genève Monthoux and Paris Archives respectively, the fault report points (5) are the same stations, the routing (6) is in the second supergroup between Genève and Annemasse on position 1, there is no information to be recorded about association (7), special equipment (8), use (9), there is no satellite involved (10), no end-to-end information (11) is required, the bandwidth (12) is 48 kHz. + +*Designation:* + +Genève/MON/CHEPTT/CHE–Paris/ARC/FRTE/FRA 12801 + +*Related information:* + +1. 3; +2. CHE, FRA; +3. CHEPTT, FRTE; +4. CS: Genève/MON/CHEPTT/CHE, +SCS1: Paris/ARC/FRTE/FRA; +5. Genève/MON/CHEPTT/CHE, Paris/ARC/FRTE/FRA; +6. Annemasse/WSX/FRTE/FRA–Genève/11W/CHEPTT/CHE 6002/1; +7. –; +8. –; +9. –; +10. –; +11. –; + +12. 48 kHz; + +#### **A.4 Full examples for the designation information of a digital block, digital path, data transmission system, blocks created between DCMEs, virtual containers and SDH multiplex section interconnections** + +##### **A.4.1 Full example for the designation information of a digital block (bidirectional) interconnection** + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +###### **A.4.1.1 Full example for the designation information of a digital block (bidirectional symmetrical configuration) interconnection** + +The interconnecting digital block is the 12th primary digital block between Roma and Paris. The urgency for restoration (1) is 2, the terminal countries (2) are France and Italy, the network operators/service providers involved (3) are France Telecom and Telecom Italia, control station (4) is Roma 1 and sub-control station is Paris Archives, the fault report points (5) are the same stations, the block has been routed (6) in the secondary digital block Paris–Roma 120N2 on position number 3, it has an associated block (7) indicated for restoration: Paris–Roma 30N5, no special equipment (8) is involved, the use of the block (9) is DP- and NP-circuits, no satellite is involved (10), no end-to-end information (11) is required, the bit rate (12) is 2048 Mbit/s, the occupancy (13) is seen in the example, the actual number of channels (14) is 31, the clocking system (15) is a master/slave system with the master in Paris and the slave in Roma. + +###### *Designation:* + +Paris/ARC/FRTE/FRA–Roma/TI/ITA 30N12 + +###### *Related information:* + +1. 2; +2. FRA, ITA; +3. FRTE, TI; +4. CS: Roma/1/TI/ITA, +SCS1: Paris/ARC/FRTE/FRA; +5. Paris/ARC/FRTE/FRA, Roma/1/TI/ITA; +6. Paris/ARC/FRTE/FRA–Roma1/TI/ITA 120N2/3; +7. S30N12: Paris/ARC/FRTE/FRA–Roma/1/TI/ITA 30N5; +8. –; +9. DP, NP; +10. –; +11. –; +12. 2048 kbit/s; +13. 01: London/22/BTPLCL/GBR–Roma/1/TI/ITA DP12, +02: Paris/ARC/FRTE/FRA–Roma/1/TI/ITA DP2, +03: Napoli/34/TI/ITA–Rouen/CDD/FRTE/FRA NP1, +04: Paris/ARC/FRTE/FRA–Roma/1/TI/ITA NP3, +05: Paris/ARC/FRTE/FRA–Roma/1/TI/ITA NP4, +06: Paris/ARC/FRTE/FRA–Roma/1/TI/ITA NP5, +07: –, + +08: -, +09: -, +10: Lille/XVC/FRTE/FRA-Roma/1/TI/ITA DP1, +11: Paris/ARC/FRTE/FRA-Roma/1/TI/ITA DP5, +12: -, +13: -, +14: -, +15: -, +16: Bruxelles/DCC/BGACOM/BEL-Roma/1/TI/ITA DPM4, +17: Paris/ARC/FRTE/FRA-Roma/1/TI/ITA DPM1, +18: -, +19: -, +20: -, +21: -, +22: -, +23: -, +24: -, +25: -, +26: -, +27: -, +28: -, +29: -, +30: -, +31: -; + +14. 31; +15. M = Paris, S = Roma. + +#### A.4.1.2 Full example for the designation information of a digital block – Bidirectional asymmetrical configuration interconnection + +In the asymmetrical configuration, one transmission station has less modulation levels than the other one. In Figure A.1, the transmission station on the left (Palermo) uses a 2-Mbit/s $\leftrightarrow$ 140-Mbit/s multiplexer without intermediate modulation levels. The transmission station on the right (Marseille) uses an equipment with three possible modulation schemes: 2 Mbit/s $\leftrightarrow$ 140 Mbit/s, 2 Mbit/s $\leftrightarrow$ 34 Mbit/s $\leftrightarrow$ 140 Mbit/s and the traditional 2 Mbit/s $\leftrightarrow$ 8 Mbit/s $\leftrightarrow$ 34 Mbit/s $\leftrightarrow$ 140 Mbit/s. + +![Figure A.1 – Digital block bidirectional asymmetrical configuration](2d8e8a86768f5861aef582d938c0597d_img.jpg) + +The diagram illustrates a bidirectional asymmetrical digital block configuration between Palermo and Marseille. +- \*\*Palermo side\*\*: Shows 64 input lines (64x) entering a multiplexer block labeled '140/2'. +- \*\*Interconnection\*\*: A '140 Mbit/s block' connects Palermo and Marseille. Below this, a '2 Mbit/s blocks' span is indicated. +- \*\*Marseille side\*\*: The 140 Mbit/s block enters a complex multiplexing structure. + - A primary block is labeled '140/34 + 140/2'. + - From the '140/34' portion, it branches to a '34/8' block and a '34/2' block. + - The '34/8' block connects to an '8/2' block, which outputs 4x lines. + - The '34/2' block outputs 16x lines. + - The '140/2' portion outputs 32x lines. +- \*\*Internal blocks\*\*: An '8 Mbit/s block' is indicated between the 34/8 and 8/2 units. A '34 Mbit/s block' is indicated between the 140/34 and the 34/8 and 34/2 units. +- \*\*Reference\*\*: M.1400(13)\_FA.1 + +Figure A.1 – Digital block bidirectional asymmetrical configuration + +**Figure A.1 – Digital block bidirectional asymmetrical configuration** + +In this case, only the 2-Mbit/s and 140-Mbit/s blocks exist between Palermo and Marseille. The 8-Mbit/s and 34-Mbit/s blocks exist only between the multiplexing equipment components in the transmission station at the right (Marseille). The 8-Mbit/s and 34-Mbit/s blocks do not exist between operators. Therefore no interconnecting designation is needed. + +*Example 1:* + +The interconnecting digital block is the second 140 Mbit/s digital block between Palermo and Marseille. The urgency for restoration (1) is not indicated, the terminal countries (2) are France and Italy, the network operators/service providers involved (3) are France Telecom and Telecom Italia, control station (4) is Marseille/KND and sub-control station is Palermo/L\*I, the fault report points (5) are the same stations, the block has been routed (6) in the optical fibre systems Marseille-Ajaccio F01, Ajaccio-Golfo Aranci F02, Golfo Aranci–Palermo/L\*I F02, it has no associated block (7) indicated for restoration, no special equipment (8) is involved, the use of the block (9) is not specified, no satellite is involved (10), no end-to-end information (11) is required, the bit rate (12) is 139 264 kbit/s, the occupancy (13) is seen in the example, the actual number of channels (14) is 64, the clocking system (15) is a master/slave system with the master in Marseille and the slave in Palermo. + +*Designation:* + +Marseille/KND/FRTE/FRA–Palermo/L\*I/TI/ITA 1920N2 + +*Related information:* + +1. –; +2. FRA, ITA; +3. FRTE, TI; +4. CS: Marseille/KND/FRTE/FRA +SCS1: Palermo/L\*I/TI/ITA; +5. Marseille/KND/FRTE/FRA, Palermo/L\*I/TI/ITA; +6. Marseille/KND/FRTE/FRA–Ajaccio/34F/TI/ITA F01, +Ajaccio/34F/TI/ITA–Golfo Aranci/VBN/TI/ITA F02, +Golfo Aranci/VBN/TI/ITA–Palermo/L\*I/TI/ITA F02; +7. –; +8. –; +9. –; +10. –; +11. –; +12. 139 264 kbit/s; +13. 01: Athinai/CCB/OTE/GRC–Bracknell/NMN/BTPLC/GBR 30N1, +02: Athinai/CCB/OTE/GRC–Bracknell/NMN/BTPLC/GBR 30N2, +03: Dublin/RRT/EIRCOM/IRL–Tel Aviv/BARAK/ISR 30N1, +04: Athinai/CCB/OTE/GRC–Linda Velha/WX/ROMTL/ROM 30N1, +05: Marseille/KND/FRTE/FRA–Palermo/L\*I/TI/ITA 30N1, +. +. +35 –, +36: –, +37: New York/MLT/ATT/USA–Whitehill/MCL/BTPLC/GBR 30N1, +38: New York/MLT/ATT/USA–Bruxelles/ZZD/BGACOM/BEL 30N1 +. +. +. +62: Athinai/CCB/OTE/GRC–White Plains/ZXC/ATT/USA 30N5, +63: Istanbul/3DF/TT/TUR–Vauxhall/2/BTPLC/GBR 30N4, +64: –; +14. 64; +15. M = Marseille, S = Palermo. + +*Example 2:* + +Routing of a 2 Mbit/s digital block between Marseille and Palermo routed on the fifth time slot of the Marseille/KND/FRTE/FRA–Palermo/L\*I/TI/ITA 1920N2 + +*Designation:* + +Marseille/KND/FRTE/FRA–Palermo/L\*I/TI/ITA 30N1 + +*Related information:* + +6. Marseille/KND/FRTE/FRA–Palermo/L\*I/IT/ITA 1920N2/5 + +NOTE – The related information does not describe the actual routing of the 2-Mbit/s digital block, but only its interconnecting portion. The country in which the multiplexer equipment components exist (in this example, France) will document the local routing, which is not the object of this Recommendation. + +#### **A.4.2 Full example for the designation information of a digital path interconnection** + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +The interconnecting digital path is the first restoration digital second order path between Paris and Bruxelles. The urgency for restoration (1) is 3, the terminal countries (2) are Belgium and France, the network operators/service providers involved (3) are Belgacom and France Telecom, control station (4) is Bruxelles BLA and sub-control station is Paris Archives, the fault report points (5) are the same stations, the path has been routed (6) in the first third order block Bruxelles–Paris on position number 1, there are no associated blocks (7), no special equipment (8), use (9) has not been indicated, no satellite is involved (10), no end-to-end information (11) is required, the bit rate (12) is 8448 Mbit/s. + +*Designation:* + +Bruxelles/BLA/BGACOM/BEL–Paris/ARC/FRTE/FRA 120N801 + +*Related information:* + +1. 3; +2. BEL, FRA; +3. BGACOM, FRTE; +4. CS: Bruxelles/BLA/BGACOM/BEL, +SCS1: Paris/ARC/FRTE/FRA; +5. Bruxelles/BLA/BGACOM/BEL–Paris/ARC/FRTE/FRA; +6. Bruxelles/BLA/BGACOM/BEL–Paris/ARC/FRTE/FRA 480N1/1; +7. –; +8. –; +9. –; +10. –; +11. –; +12. 8448 kbit/s. + +#### **A.4.3 Full example for the designation information of a data transmission system interconnection** + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +The data transmission system interconnection is the first 64-kbit/s data transmission system between London and Paris. The urgency for restoration (1) is 1, the terminal countries (2) are United Kingdom and France, the network operators/service providers involved (3) are British Telecom International and France Telecom, the control and sub-control stations (4) are London Mollison and Paris Archives respectively, the fault report points (5) are the same stations, the system has been routed (6) in the 12th primary block between Paris and London on timeslot number 3, there is no information to be recorded about association (7), equipment information (8) and use (9), there is no satellite involved (10), composition of transmission (11) is digital, item (12) does not apply, the occupancy (13) is seen in the example. + +*Designation:* + +London/SM/BTPLC/GBR–Paris/ARC/FRTE/FRA 64K1 + +*Related information:* + +1. 1; +2. GBR, FRA; +3. BTPLC, FRTE; +4. CS: London/SM/BTPLC/GBR, +SCS1: Paris/ARC/FRTE/FRA; +5. London/SM/BTPLC/GBR–Paris/ARC/FRTE/FRA; +6. London/113/BTPLC/GBR–Paris/EDC/FRTE/FRA 30N12/3; +7. –; +8. –; +9. –; +10. –; +11. N; +12. –; +13. A4: London/113/BTPLC/GBR–Paris/EDC/FRTE/FRA NP12, +B4: London/113/BTPLC/GBR–Toulouse/RRC/FRTE/FRA NP3, +C4: –; +D4: Dublin/45/BTE/IRL–Paris/EDC/FRTE/FRA NP6, +E4: London/113/BTPLC/GBR–Paris/EDC/FRTE/FRA NP11, +F4: London/113/BTPLC/GBR–Paris/EDC/FRTE/FRA NP14. + +#### **A.4.4 Full example for the designation information of a block created by the interconnection of DCMEs** + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +This block is the second block created by the interconnection of DCMEs with a maximal nominal number of 240 channels between Boston and Reims. The urgency for restoration (1) is 2, the terminal countries (2) are the United States and France, the network operators/service providers involved (3) are AT&T and France Telecom, control station is Boston (4) and sub-control station is Reims/CRE, the fault report points (5) are the same stations, the block has been routed (6) on the 22nd primary digital path between Reims and New York, it has no associated block (7), the first 30 channels are through-going (8), use (9) has not been indicated, a satellite is involved in transmission (10), items 11 and 12 do not apply and the occupancy (13) is seen in the example (only 90 channels are occupied with circuits). + +*Designation:* + +Boston/FRC/ATT/USA–Reims/CRE/FRTE/FRA 240Y2 + +*Related information:* + +1. 2; +2. USA, FRA; +3. ATT, FRTE; +4. CS: Boston/FRC/ATT/USA, + +SCS1: Reims/CRE/FRTE/FRA; + +5. Boston/FRC/ATT/USA, Reims/CRE/FRTE/FRA; +6. New York/45/ATT/USA–Reims/CRE/FRTE/FRA 30N22; +7. –; +8. 1-30 = T; +9. –; +10. ST; +11. –; +12. –; +13. 001: New York/24/ATT/USA–Paris/PT3/FRTE/FRA B1, +002: New York/24/ATT/USA–Paris/PT3/FRTE/FRA B2, +..... +090: New York/24/ATT/USA–Paris/PT3/FRTE/FRA B90. + +#### A.4.5 Full example for the designation of a virtual container interconnection + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +The virtual container (VC) interconnection is the 12th VC-4 between Roma and Paris. The urgency for restoration (1) is 2, the terminal countries (2) are France and Italy, the network operators/service providers involved (3) are France Telecom and Telecom Italia, control station (4) is Roma 1 and sub-control station is Paris Archives, the fault report points (5) are the same stations, the block has been routed (6) in the multiplex section Paris–Roma 4S2 on position number 3, it has no associated block (7), no special equipment (8) is involved, the use of the block (9) is unknown, no satellite is involved (10), no end-to-end information (11) is required, the bit rate (12) is 155 Mbit/s, the occupancy (13) is seen in the example and the access points (14) are shown there as well. + +*Designation:* + +Paris/35R/FRTE/FRA–Roma/VVB/TI/ITA VC4S12 + +*Related information:* + +1. 2; +2. FRA, ITA; +3. FRTE, TI; +4. CS: Roma/1/TI/ITA, +SCS1: Paris/ARC/FRTE/FRA; +5. Paris/ARC/FRTE/FRA, Roma/1/TI/ITA; +6. Paris/35R/FRTE/FRA–Roma/VVB/TI/ITA 4S2/3; +7. –; +8. –; +9. –; +10. –; +11. –; +12. –; + +13. 1,0,0: Napoli/55E/TI/ITA–Paris/35R/FRTE/FRA VC3S15, +2,1,0: Lille/CVB/FRTE/FRA–Roma/1/TI/ITA VC2S8, +2,2,0: Lille/CVB/FRTE/FRA–Roma/1/TI/ITA VC2S121, +2,3,0: –, +2,4,1: London/XXC/BTPLC/GBR–Roma/1/TI/ITA VC12S30, +2,4,2: Paris/35R/FRTE/FRA–Roma/VVB/TI/ITA VC12S4, +2,4,3: London/XXC/BTPLC/GBR–Roma/VVB/TI/ITA VC12S31, +2,5,0: London/XXC/BTPLC/GBR–Roma/VVB/TI/ITA VC2S67, +2,6,0: –, +2,7,0: Paris/35R/FRTE/FRA–Roma/VVB/TI/ITA VC2S82, +3,0,0: Napoli/55E/TI/ITA–Paris/35R/FRTE/FRA VC3S16; +14. APId A: FRAFRTE12345678, +APId B: ITATI987654321. + +#### **A.4.6 Full example for the designation information of a multiplex section interconnection** + +NOTE – The numbers between parentheses refer to the numbers of the items in the Related information. + +The multiplex section interconnection is the first STM-4 between London and Paris. The urgency for restoration (1) is 1, the terminal countries (2) are United Kingdom and France, the network operators/service providers involved (3) are British Telecom International and France Telecom, the control and sub-control stations (4) are London Mollison and Paris Archives respectively, the fault report points (5) are the same stations, the system has been routed (6) on the France–UK 4 submarine cable, there is no information to be recorded about association (7), equipment information (8) and use (9), there is no satellite involved (10), item (11) does not apply, the bit rate (12) is 620 Mbit/s, the occupancy (13) is seen in the example. + +*Designation:* + +London/SM/BTPLC/GBR–Paris/ARC/FRTE/FRA 4S1 + +*Related information:* + +1. 1; +2. GBR, FRA; +3. BTPLC, FRTE; +4. CS: London/SM/BTPLC/GBR, +SCS1: Paris/ARC/FRTE/FRA +5. London/SM/BTPLC/GBR, Paris/ARC/FRTE/FRA; +6. France–UK 4; +7. –; +8. –; +9. –; +10. –; +11. –; +12. 620 Mbit/s; + +13. + - 1: Glasgow/DDC/BTPLC/GBR–Paris/ARC/FRTE/FRA VC4S12, + - 2: London/SM/BTPLC/GBR–Paris/ARC/FRTE/FRA VC4S21, + - 3: –, + - 4: London/SM/BTPLC/GBR–Toulouse/EDR/FRTE/FRA VC4S2; +14. APId A: 441234567890123, +APId B: FRAFRTE87654321. + +## Annex B + +### KLM addressing and its relationship to time slot numbering for virtual containers + +(This annex forms an integral part of this Recommendation.) + +#### B.1 KLM addressing relationship to time slot numbering + +It is possible to relate VC-4 occupancy listing with time slot numbering or tributary numbering to an occupancy listing with KLM addressing by using the following process. + +- List the designations of all tributaries (irrespective of type) in order. This will consist of a possible combination of VC-12s, VC-2s and/or VC-3s. + +- *Assign a K number:* + +Every VC-*n* is contained in one of three TU3s (or TUG3s). Each VC-*n* tributary should be assigned a K number, from 1 to 3, corresponding to the position in which its TU3 (or TUG3) is contained within the VC-4, e.g., the VC-3 in the second TU3 has a K number of 2; any VC-12 in the third TU3 has a K number of 3, etc. + +- *Assign an L number:* + +For each VC-3, the L number is 0. + +Each VC-2 or VC-12 is contained within one of seven TU2s (or TUG2s) within a TUG3. Each VC-2 or VC-12 should be assigned an L number from 1 to 7, corresponding to the position in which its TU2 (or TUG2) is contained within its TU3, e.g., a VC-2 in the fifth TU2 within its TUG3 has an L number of 5; any VC-12 within the sixth TUG2 in a TUG3 has an L number of 6, etc. + +- *Assign an M number:* + +For each VC-3 and VC-2, the M number is 0. + +Each VC-12 is contained within one of three TU12s within a TUG2. Each VC-12 should be assigned an M number from 1 to 3, corresponding to the position in which its TU12 is contained within its TUG2, e.g., the VC-12 corresponding to the third TU12 within a TUG2 has an M number of 3. + +## B.2 KLM addressing of VC-4 occupancy + +Figure B.1 illustrates VC-3, VC-2 and VC-12 occupancy of a VC-4. + +![](3c0be9369e1f99f7f820fda3f9d676e6_img.jpg) + +**VC-4 organization** + +| | VC-3
(K) | VC-2
(L) | VC-12
(M) | +|---|---------------------|-------------|--------------| +| 1 | TUG3 | 1 | 1 | +| | | 2 | 2 | +| | | 3 | 3 | +| | | 4 | | +| | | 5 | | +| | | 6 | | +| | | 7 | | +| 2 | TUG3 | KLM = 2,1,0 | 0 | +| | | | 0 | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| 3 | TUG3
KLM = 3,0,0 | 0 | 0 | + +M.1400(06)\_FB.1 + +×3 + +(1,.,3) + +×7 + +(1,.,.,.,.,7) + +×3 + +(1,.,3) + +**Figure B.1 – VC-4 organization** + +## B.3 Comparative notation of KLM addressing vs. time slot numbering + +The following example shows the two alternative ways of presenting occupancy. List 1 shows an occupancy listing using KLM numbering. List 2 shows the corresponding occupancy using time slot numbering. Note that each KLM address is specified only once in list 1. Also note that in List 2 a VC-3 (*n*,0,0) is repeated at every third time slot; a VC-2, (*n*,*n*,0) is repeated at every 21st time slot: a VC-12 (*n*,*n*,*n*) is not repeated within the 63 time slots. + +| List 1 | List 2 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Using KLM addressing | Using time slot numbering | +| 1,0,0: Napoli/1/TI/ITA–Paris/2/FT/FRA VC3S15,
2,1,0: Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S8,
2,2,0: Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S66,
2,3,0: –,
2,4,1: London/5/BTPLC/GBR–Roma/4/TI/ITA VC12S30,
2,4,2: Paris/2/FRTE/FRA–Roma/4/TI/ITA VC12S44,
2,4,3: London/5/BTPLC/GBR–Roma/4/TI/ITA VC12S31,
2,5,0: Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S67,
2,6,0: –,
2,7,0: Paris/2/FRTE/FRA–Roma/4/TI/ITA VC2S82,
3,0,0: Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16; | 01:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
02:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S8,
03:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
04:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
05:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S66,

06:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
07:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
08:–,
09:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
10:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
11:London/5/BTPLC/GBR–Roma/4/TI/ITA VC12S30,

12:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
13:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
14:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S67,
15:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
16:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
17:–,
18:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
19:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
20:Paris/2/FRTE/FRA–Roma/4/TI/ITA VC2S82,
21:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
22:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
23:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S8,
24:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
25:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
26:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S66,
27:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
28:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
29:–,
30:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
31:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
32:Paris/2/FRTE/FRA–Roma/4/TI/ITA VC12S44,
33:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
34:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
35:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S67,
36:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
37:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
38:–,
39:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
40:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,

41:Paris/2/FRTE/FRA–Roma/4/TI/ITA VC2S82,
42:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
43:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
44:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S8,
45:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16, | + +| List 1 | List 2 | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Using KLM addressing | Using time slot numbering | +| | 46:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
47:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S66,
48:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
49:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
50:–,
51:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
52:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
53:London/5/BTPLC/GBR–Roma/4/TI/ITA
VC12S31,
54:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
55:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
56:Lille/3/FRTE/FRA–Roma/4/TI/ITA VC2S67,
57:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
58:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
59:–,
60:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16,
61:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S15,
62:Paris/2/FRTE/FRA–Roma/4/TI/ITA VC2S82,
63:Napoli/1/TI/ITA–Paris/2/FRTE/FRA VC3S16; | + +## Annex C + +### Reference clause numbers for the various types of routes + +(This annex forms an integral part of this Recommendation.) + +| Clause | Type of interconnecting route | +|---------------|----------------------------------------------------------------------------------------------------| +| 7.2.2 | Telephone circuits used in manual operation | +| 7.2.3 | One-way telephone circuits used for semi-automatic or automatic operation | +| 7.2.4 | Both-way telephone circuits used for semi-automatic or automatic operation | +| 7.3 | Circuits used for switched telex and telegraph service | +| 7.4 | Interconnecting circuits in the public switched data network | +| 9.2.2 | Analogue leased circuits used for telephony | +| 9.2.3.1 | Analogue circuits used for voice-frequency telegraphy | +| 9.2.3.2 | Analogue leased circuits used for TDM-telegraphy | +| 9.2.4 | Leased telegraph circuits | +| 9.2.5 | Analogue leased circuits used for data transmission | +| 9.2.6 | Analogue leased circuits used for phototelegraphy or facsimile | +| 9.2.7.1 | Analogue leased unidirectional sound-programme transmission circuits | +| 9.2.7.2 | Analogue leased reversible sound-programme transmission circuits | +| 9.2.8.1 | Analogue leased unidirectional television-programme circuits | +| 9.2.8.2 | Analogue leased reversible television-programme circuits | +| 9.2.9 | Leased circuits used for digital video transmission | +| 9.2.10 | Analogue leased circuits connecting circuit multiplication terminal equipment at renters' premises | +| 9.2.11 | Analogue leased circuits used for combinations of transmissions, etc. | +| 9.2.12 | Analogue leased circuits connecting three or more locations | +| 9.2.13 | Leased analogue groups, supergroups, etc. | +| 9.2.14 | Leased analogue group, supergroup links | +| 9.2.15 | Digital leased circuits connecting two locations | +| 9.2.16 | Digital leased circuits connecting three or more locations | +| 9.3.2.1 | Public circuits used for unidirectional sound-programme transmission | +| 9.3.2.2 | Public circuits used for reversible sound-programme transmission | +| 9.3.2.3 | Public circuits used for narrow-band sound-programme transmission | +| 9.3.3.1 | Public circuits used for unidirectional television transmission | +| 9.3.3.2 | Public circuits used for reversible television transmission | +| 9.3.4 | Public circuits for digital audio and video transmission | +| 9.3.5 | Public telephone-type circuits used for phototelegraphy or facsimile | +| 9.3.6 | Telephone-type circuits used to provide voice-frequency telegraph links | +| 9.3.7 | Telephone-type circuits used to provide time division multiplex telegraph systems | +| 9.3.8 | Telephone-type circuits used for data transmission | + +| | | +|----------|--------------------------------------------------------------------------------------------------| +| 9.3.9 | Telephone-type circuits used as transfer links for common channel Signalling Systems Nos 6 and 7 | +| 11.2.1 | Groups (bidirectional) | +| 11.2.2 | Supergroups (bidirectional) | +| 11.2.3 | Mastergroups (bidirectional) | +| 11.2.4 | Supermastergroup (bidirectional) | +| 11.2.6 | Restoration groups and supergroups (bidirectional) | +| 11.3.1 | Multiple destination unidirectional groups and supergroups | +| 11.3.2 | Single destination unidirectional groups and supergroups | +| 12.1.1 | Conventional group and supergroup links | +| 12.1.2 | Restoration links | +| 12.2 | Line links | +| 14.2 | Bidirectional digital blocks | +| 14.3 | Restoration digital blocks | +| 14.4 | Multiple destination unidirectional digital blocks | +| 14.5 | Single destination unidirectional digital blocks | +| 15.1 | Conventional digital paths not connected to their terminal equipment | +| 15.2 | Restoration digital paths | +| 16.1.1 | Groups and supergroups, etc., on a mixed analogue/digital transmission route | +| 16.1.2 | Digital blocks and paths on a mixed analogue/digital transmission route | +| 16.2 | Designation of routes with two analogue-to-digital conversions | +| 17 | Designation of data transmission systems | +| 17.2 | Data transmission links | +| 18 | Blocks created by interconnection of DCMEs | +| 18.2 | Multi-clique configuration of DCMEs | +| 18.3 | Low rate encoding equipment | +| 19.1 | SDH multiplex sections | +| 19.2 | Virtual containers | +| 19.3 | "Virtual STMs" consisting of concatenated virtual containers (VCs) | +| 19.4 | Leased circuits based on SDH | +| 21.2 | ATM transport links | +| 21.3 | ATM virtual paths | +| 21.4 | ATM virtual channels (VCAs) | +| 23.2 | Transit digital transmission service | +| 23.3 | Transit dark fibre service | +| 25.4.1.1 | Wavelength division multiplexing optical regenerator section | +| 25.4.1.2 | WDM optical amplifier section | +| 25.4.1.3 | WDM optical multiplex section | + +- 25.4.1.4 WDM optical channel +- 27.1.1 ADSL connection +- 27.1.3 SDSL connection +- 28.1 Exceptional designations with intelligence in the serial number + +## Annex D + +### Numbering of channels in data transmission systems + +(This annex forms an integral part of this Recommendation.) + +Using suitable modems and multiplexers, it is possible to provide for a combination of data channels multiplexed together to form an aggregate bit rate for data transmission purposes. + +The principle shown in Figure D.1 and Table D.1 may be applied to higher bit rates as modems, etc., are developed and deployed. + +The numbering of data channels is obtained by indicating the multiplex channel followed by the sub-channel data rate assigned number in accordance with the scheme contained in Table D.1. + +As an example, Figure D.1 shows a data transmission system, London/EVY/BTPLC/GBR–Montreal/CCN/TGB/CAN 96H001, employing equipment providing for 2 channels at 2400 bit/s and one channel at 4800 bit/s, forming an aggregate bit rate of 9600 bit/s. + +London/EVY/BTPLC/GBR–Montreal/CCN/TGB/CAN 96H001/A2 + +London/EVY/BTPLC/GBR–Montreal/CCN/TGB/CAN 96H001/B1 + +London/EVY/BTPLC/GBR–Montreal/CCN/TGB/CAN 96H001/C1 + +![Figure D.1: Example of the channel numbering scheme for data transmission systems. The diagram shows a data transmission path from London to Montreal. On the left, three input channels are shown: A2 (4800 bit/s), B1 (2400 bit/s), and C1 (2400 bit/s). These are multiplexed together and then passed through an ITU-T V.29 Modem. The output of the modem is labeled 'London-Montreal D1'. This signal is then passed through another ITU-T V.29 Modem on the receiving side. The output of the second modem is then demultiplexed back into three channels: A2 (4800 bit/s), B1 (2400 bit/s), and C1 (2400 bit/s). Above the diagram, three horizontal double-headed arrows indicate the channel numbering scheme: 'London-Montreal 96H001/A2,B1,C1' for the entire aggregate, 'London-Montreal 96H001' for the main multiplex channel, and 'London-Montreal D1' for the sub-channel data rate. The diagram is labeled 'M.1400(13)_FD.1' at the bottom right.](5de3d4570bdb30251a009a25795993e9_img.jpg) + +Figure D.1: Example of the channel numbering scheme for data transmission systems. The diagram shows a data transmission path from London to Montreal. On the left, three input channels are shown: A2 (4800 bit/s), B1 (2400 bit/s), and C1 (2400 bit/s). These are multiplexed together and then passed through an ITU-T V.29 Modem. The output of the modem is labeled 'London-Montreal D1'. This signal is then passed through another ITU-T V.29 Modem on the receiving side. The output of the second modem is then demultiplexed back into three channels: A2 (4800 bit/s), B1 (2400 bit/s), and C1 (2400 bit/s). Above the diagram, three horizontal double-headed arrows indicate the channel numbering scheme: 'London-Montreal 96H001/A2,B1,C1' for the entire aggregate, 'London-Montreal 96H001' for the main multiplex channel, and 'London-Montreal D1' for the sub-channel data rate. The diagram is labeled 'M.1400(13)\_FD.1' at the bottom right. + +**Figure D.1 – Example of the channel numbering scheme for data transmission systems** + +Table D.1 shows the channel numbering scheme for data transmission systems operated at an aggregate data rate of 9600 bit/s. The table also shows the channel numbering scheme for systems using 9600 bit/s modems operated at reduced rates of 7200 bit/s or 4800 bit/s. + +**Table D.1 – Channel numbering scheme for data transmission systems using 9600 bit/s data modems conforming to [ITU-T V.29]** + +| Aggregate data rate | Multiplex configuration | Sub-channel data rate | Multiplex channel | Channel number | +|---------------------|-------------------------|-----------------------|-------------------|----------------| +| 9600 bit/s | 1 | 9600 | A | A4 | +| | 2 | 7200
2400 | A
B | A3
B1 | +| | 3 | 4800
4800 | A
B | A2
B2 | + +**Table D.1 – Channel numbering scheme for data transmission systems using 9600 bit/s data modems conforming to [ITU-T V.29]** + +| Aggregate data rate | Multiplex configuration | Sub-channel data rate | Multiplex channel | Channel number | +|---------------------|-------------------------|-----------------------|-------------------|----------------| +| 7200 bit/s | 4 | 4800 | A | A2 | +| | | 2400 | B | B1 | +| | | 2400 | C | C1 | +| | 5 | 2400 | A | A1 | +| | | 2400 | B | B1 | +| | | 2400 | C | C1 | +| | | 2400 | D | D1 | +| | 6 | 7200 | A | A3 | +| 4800 bit/s | 7 | 4800 | A | A2 | +| | | 2400 | B | B1 | +| | 8 | 2400 | A | A1 | +| | | 2400 | B | B1 | +| | | 2400 | C | C1 | +| | 9 | 4800 | A | A2 | +| | 10 | 2400 | A | A1 | +| | | 2400 | B | B1 | + +| Sub-channel data rate | Assigned number | +|-----------------------|-----------------| +| 9600 | 4 | +| 7200 | 3 | +| 4800 | 2 | +| 2400 | 1 | + +## Annex E + +### Notification form for List of ITU Carrier Codes3 + +(This annex forms an integral part of this Recommendation.) + +Since 1 January 2004, it has become mandatory for operators utilizing Recommendation ITU-T M.1400 operator ID or ITU Carrier Code (ICC) in the revised Layer 1 structure, to identify route terminations. An ICC is mandatory for interconnections between operators in different countries and different operators in the same country. This code is used in ITU-T M.1400 Layer 1 records to uniquely identify route terminations. It is also used for the purpose of an operator registering its interconnecting operators. + +In order to develop a listing of ICCs that may be used to identify the interconnecting operators in ITU-T M.1400 records, as explained in Recommendation ITU-T M.1400, national regulatory authorities are requested to complete the present Notification Form indicating the validated codes and related information for both international and domestic operators. On completion, this Notification Form should be sent directly to TSB at the following address: + +Director of TSB +International Telecommunication Union +Place des Nations +1211 Geneva 20 +Switzerland +Fax: +41 22 730 58 53 + +1. **Company full name:** +(name of operator) +- | | | | | | | +|--|--|--|--|--|--| +| | | | | | | +|--|--|--|--|--|--| +2. **Company Code:** + +(The code by which the operator wishes to identify itself. This code shall be alphabetic or alphanumeric (A to Z):(0 to 9), up to six characters and/or digits long, and shall be a unique identifier of a network operator/service provider within each country. This code may be one that is in use today, provided it fits the definition.) + +3. **Company official address:** +4. **Contact:** + +Tel.: + +Fax: + +E-mail: + +Date: + +3 + +## Annex F + +### List of all ITU function codes + +(This annex forms an integral part of this Recommendation.) + +This annex provides an overview of all ITU function codes specified within this Recommendation. + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|----------------------------------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------|---------------| +| 8 | 8-channel groups | Bidirectional and unidirectional groups | Clause 11.2.1 | +| 12 | 12-channel groups | Bidirectional and unidirectional groups | Clause 11.2.1 | +| 16 | 16-channel groups | Bidirectional and unidirectional groups | Clause 11.2.1 | +| 60 | 60-channel groups | Bidirectional and unidirectional groups | Clause 11.2.2 | +| 80 | 80-channel groups | Bidirectional and unidirectional groups | Clause 11.2.2 | +| 300 | Mastergroup | Bidirectional and unidirectional groups | Clause 11.2.3 | +| 900 | Supermastergroup | Bidirectional and unidirectional groups | Clause 11.2.4 | +| 8899, 8898, 8897, etc.
12899, 12898, 12897, etc.
16899, 16898, 16897, etc. | Restoration groups | Bidirectional and unidirectional groups | Clause 11.2.6 | +| 60899, 60898, 60897, etc. | Restoration supergroups | Bidirectional and unidirectional groups | Clause 11.2.6 | +| 12801, 12802, 12803, etc. | Restoration group links | Bidirectional and unidirectional groups | Clause 12.1.2 | +| 60801, 60802, 60803, etc. | Restoration supergroup links | Bidirectional and unidirectional groups | Clause 12.1.2 | +| 30N801, 30N802, etc. | First order digital block Restoration | Bidirectional and unidirectional groups | Clause 15.2 | +| 120N801, 120N802, etc. | Second order digital block Restoration | Bidirectional and unidirectional groups | Clause 15.2 | +| 24N | Indicates nominal number of channels (24) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 30N | Indicates nominal number of channels (30) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|---------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|-------------| +| 96N | Indicates nominal number of channels (96) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 120N | Indicates nominal number of channels 120) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 480N | Indicates nominal number of channels (480) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 672N | Indicates nominal number of channels (672) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 1440N | Indicates nominal number of channels (1440) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 1920N | Indicates nominal number of channels (1920) in the digital block (N) | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 14.1 | +| 10GE | 10 Gigabit Ethernet (generic) – 10 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| 40GE | 40 Gigabit Ethernet (generic) – 40 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| 100GE | 100 Gigabit Ethernet (generic) – 100 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| 3V12V | 3 Virtual concatenated VC-12's | Designation of virtual container interconnection | Clause 19.3 | +| 5V2C | 5 Contiguous concatenated VC-2's | Designation of virtual container interconnection | Clause 19.3 | +| 4V4C | 4 Contiguous concatenated VC-4's | Designation of virtual container interconnection | Clause 19.3 | +| 4V4V | 4 Virtual concatenated VC-4's | Designation of virtual container interconnection | Clause 19.3 | +| 16V4C | 16 Contiguous concatenated VC-4's | Designation of virtual container interconnection | Clause 19.3 | +| 256V4C | 256 Contiguous concatenated VC-4's | Designation of virtual container interconnection | Clause 19.3 | +| A* | This code consists of a number indicating the nominal telephone channel transmission capacity followed by the letter A | Bidirectional and unidirectional groups | Clause 12.2 | +| A10G | For 10 Gbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|---------------|----------------------------------------------------------------------------|-----------------------------------------------------------------|----------------------------------------| +| A34M | For 34 Mbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | +| A45M | For 45 Mbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | +| A40G | For 40 Gbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | +| A155M | For 155 Mbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | +| A622M | For 622 Mbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | +| A2500M | For 2.5 Gbit/s ATM transport link | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.2 | +| ABR | Available Bit Rate Capability | Designation of connections for asynchronous transfer mode (ATM) | Clause 22.15 | +| ABT | ATM Block Transfer Capabilities | Designation of connections for asynchronous transfer mode (ATM) | Clause 22.15 | +| B | Both-way telephone circuits | Telephone-type circuits | Clause 7.2 | +| C | Defined that it is a Contiguous concatenated VC (one letter); or | Concatenated virtual containers mVpC and mVpV* | Clause 19.3 | +| C* | If the transmission is mixed analogue/digital | Bidirectional and unidirectional groups | Clauses 8.11, 10.11, 16.1.1 and 16.1.2 | +| D | For data transmission circuits; | Fixed (non-switched) public circuits | Clause 9.3.1 | +| DC | Digital Circuit | Transit network services | Clause 23.2 | +| DBR | Deterministic Bit Rate Capability | Designation of connections for asynchronous transfer mode (ATM) | Clause 22.15 | +| DFS | Dark Fibre Service | Transit network services | Clause 23.3 | +| DL | For circuits providing transfer link for common channel signalling systems | Fixed (non-switched) public circuits | Clause 9.3.1 | +| DP | For analogue leased circuits used wholly for data transmission | Telephone-type circuits | Clause 9.2.1 | +| F | For a phototelegraphy or facsimile circuit | Fixed (non-switched) public circuits | Clause 9.3.1 | + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------------------------| +| FP | For analogue leased circuits used wholly for phototelegraphy or facsimile | Telephone-type circuits | Clause 9.2.1 | +| GE1 | 1Gigabit Ethernet – 1 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE2X | 2.5 Gigabit Ethernet – 2.5 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE10L | 10 Gigabit Ethernet LAN – 10 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE10W | 10 Gigabit Ethernet WAN – 10 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE40L | 40 Gigabit Ethernet LAN – 40 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE40W | 40 Gigabit Ethernet WAN – 40 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE100L | 100 Gigabit Ethernet LAN – 100 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| GE100W | 100 Gigabit Ethernet WAN- 100 Gbit/s | Gigabit Ethernet | Clause 17.1 | +| HP | Partially managed SDH leased circuits | Concatenated virtual containers mVpC and mVpV* | Clause 19.4.1 | +| m | Indicates the number of concatenated VCs up to 256 (max. three digits) | Concatenated virtual containers mVpC and mVpV* | Clause 19.3 | +| M | Manual telephone circuits; | Telephone-type circuits | Clause 7.2 | +| M* | Appended to function codes recommended in clauses 9.2.2 to 9.2.11 | Telephone-type circuits | Clause 9.2.12 | +| MHP | Fully managed SDH leased circuits | Concatenated virtual containers mVpC and mVpV* | Clause 19.4.1 | +| MI | If the block has been created by the interconnection of two transcoders (low-rate encoding equipment) using the A-law: AI or -law | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 20.8.1 | +| N | If the transmission is digital | Designation of digital block (bidirectional/unidirectional) interconnections | Clauses 8.11, 10.11 and 16.1.2 | +| NP | For ALL digital leased circuits. | Telephone-type circuits | Clause 9.2.1 | +| OAS | Optical Amplifier Section | Designation for wavelength division multiplexing (simple and dense) clause 25 | Clause 25.4.1.2 | +| OC | Optical Channel | Designation for wavelength division multiplexing (simple and dense) clause 25 | Clause 25.4.1.4 | + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|---------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------| +| ODUF | Optical channel Data Unit flexible | Optical transport network (OTN) | Clause 29.1 | +| ODU0S | Optical channel Data Unit at 1.25 Gbit/s (ODU0) | Optical transport network (OTN) | Clause 29.1 | +| ODU1S | Optical channel Data Unit at 2.5 Gb/s (ODU1) | Optical transport network (OTN) | Clause 29.1 | +| ODU2S | Optical channel Data Units at 10.037 Gb/s (ODU2) or 10.399 Gb/s (ODU2e) | Optical transport network (OTN) | Clause 29.1 | +| ODU3S | Optical channel Data Units at 40.319 Gb/s (ODU3) or 44.57 Gb/s (ODU3e1) | Optical transport network (OTN) | Clause 29.1 | +| ODU4S | Optical channel Data Unit at 104.79 Gb/s (ODU4) | Optical transport network (OTN) | Clause 29.1 | +| OMS | Optical Multiplex Section | Designation for wavelength division multiplexing (simple and dense) clause 25 | Clause 25.4.1.3 | +| ORS | Optical Regenerator Section | Designation for wavelength division multiplexing (simple and dense) clause 25 | Clause 25.4.1.1 | +| OTU1S | Optical channel Transport Units at 2.666 Gbit/s | Optical transport network (OTN) | Clause 29.1 | +| OTU2S | Optical channel Transport Units at 10.709 Gbit/s (OTU2) or 11.09 Gb/s (OTU2e) | Optical transport network (OTN) | Clause 29.1 | +| OTU3S | Optical channel Transport Units at 43.018 Gbit/s (OTU3) or 44.57 Gb/s (OUT 3e1) or 44.58 Gb/s (OTU3e2) | Optical transport network (OTN) | Clause 29.1 | +| OTU4S | 111.809 Gb/s | Optical transport network (OTN) | Clause 29.1 | +| p | Indicates the virtual container (VC) level (2, 4, 11, 12) (max. two digits) | Concatenated virtual containers mVpC and mVpV* | Clause 19.3 | +| P | For analogue leased circuits used wholly for telephony | Telephone-type circuits | Clause 9.2.1 | +| R | For a unidirectional sound-programme circuit | Fixed (non-switched) public circuits | Clause 9.3.1 | +| RK | For telephone type circuits for narrow-band sound-programme transmission | Fixed (non-switched) public circuits | Clause 9.3.1 | +| RP | For analogue leased unidirectional sound-programme circuits | Telephone-type circuits | Clause 9.2.1 | +| RR | For a reversible sound-programme circuit | Fixed (non-switched) public circuits | Clause 9.3.1 | + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|---------------|------------------------------------------------------------------|-----------------------------------------------------------------|---------------| +| RRP | For analogue leased reversible sound-programme circuits | Telephone-type circuits | Clause 9.2.1 | +| SBR | Statistical bit rate capability | Designation of connections for asynchronous transfer mode (ATM) | Clause 22.15 | +| T | For circuits providing voice-frequency telegraph links | Fixed (non-switched) public circuits | Clause 9.3.1 | +| TD | For circuits providing TDM-telegraph systems | Fixed (non-switched) public circuits | Clause 9.3.1 | +| TP | For analogue leased circuits used for voice-frequency telegraphy | Telephone-type circuits | Clause 9.2.1 | +| TPD | For analogue leased circuits used for TDM-telegraphy | Telephone-type circuits | Clause 9.2.1 | +| V | For a unidirectional television circuit | Fixed (non-switched) public circuits | Clause 9.3.1 | +| V | Defines that it is a virtual container (one letter ) | Concatenated virtual containers mVpC and mVpV* | Clause 19.3 | +| V* | Defines that it is a virtual concatenated VC (one letter) | Concatenated virtual containers mVpC and mVpV* | Clause 19.3 | +| VC1 1S | For a VC-11 virtual container | Designation of virtual container interconnection | Clause 19.2.1 | +| VC12S | For a VC-12 virtual container | Designation of virtual container interconnection | Clause 19.2.1 | +| VC2S | For a VC-2 virtual container | Designation of virtual container interconnection | Clause 19.2.1 | +| VC3S | For a VC-3 virtual container | Designation of virtual container interconnection | Clause 19.2.1 | +| VC4S | For a VC-4 virtual container | Designation of virtual container interconnection | Clause 19.2.1 | +| VCA | Virtual channel | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.4 | +| VP | For analogue leased unidirectional television-programme circuits | Telephone-type circuits | Clause 9.2.1 | +| VPA | Virtual path | Designation of connections for asynchronous transfer mode (ATM) | Clause 21.3 | +| VV | For a reversible television circuit | Fixed (non-switched) public circuits | Clause 9.3.1 | +| VVP | For analogue leased reversible television-programme circuits | Telephone-type circuits | Clause 9.2.1 | + +**Table F.1 – Function codes by designation and alphabetical order** + +| Function code | Description | Technology | Clause | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|----------------| +| x xxxxA
(bit rate + A) | A = ADSL – maximum bit rate for an ADSL connection, x numerical value from 0-9 | Designation of connection for the digital subscriber line (ADSL/SDSL) | Clause 27.1.1 | +| x xxxxS
(bit rate + S) | S = SDSL – maximum bit rate for an ADSL connection, x numerical value from 0-9 | Designation of connection for the digital subscriber line (ADSL/SDSL) | Clause 27.1.3 | +| x P | Number of copper pairs used for a given SDSL connection. x numerical value from 0 to 9 | Designation of connection for the digital subscriber line (ADSL/SDSL) | Clause 27.3.10 | +| XD | Interconnecting circuits in the public switched data network | Telephone-type circuits | Clause 7.4 | +| XP | For analogue leased circuits used for multiple type transmissions | Telephone-type circuits | Clause 9.2.1 | +| Y* | This code consists of a number indicating the nominal maximum number of channels in the block followed by the letter Y | Designation of digital block (bidirectional/unidirectional) interconnections | Clause 18.1 | +| Z | Automatic and semi-automatic telephone circuits in one-way operation | Telephone-type circuits | Clause 7.2 | + +A\* – The function code is formed by adding the A after the number of nominal maximum channels in the block. + +C\* – Letter C included in the function code and placed after the nominal number of channels indicate groups, supergroups, etc., are converted to digital paths. Also, an additional C after the N indicates digital blocks and paths are converted to analogue groups, supergroups, etc. (see clauses 16.1.1 and 16.1.2). + +M\* – In the case of leased circuits connecting three or more locations, the letter M should follow these function codes (see clause 9.2.12). + +(U) – In the case of a unidirectional single destination group, the number is preceded by the letter (U) in parentheses (see clause 11.3.2). + +(MU) – Multiple destination unidirectional (see clause 11.3.1). + +Y\* – The function code is formed by adding the Y after the number of nominal maximum channels in the block. + +## Bibliography + +- [b-ATIS-0300097] ATIS Specification ATIS-0300097 (2008), *Structure for the Identification of Telecommunications Connections for Interconnection Exchange*. +- [b-ITU-T G.Suppl. 43] Supplement 43 to ITU-T G-series Recommendations (2011), Transport of IEEE 10GBASE-R in optical transport networks (OTN). + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1401-200607-I_PDF-E/raw.md b/marked/M/T-REC-M.1401-200607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..64ac350d022ddff48b380d2f883675798a3c43ad --- /dev/null +++ b/marked/M/T-REC-M.1401-200607-I_PDF-E/raw.md @@ -0,0 +1,1495 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1401** + +(07/2006) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Designations and information exchange + +--- + +**Formalization of interconnection designations +among operators' telecommunication networks** + +ITU-T Recommendation M.1401 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.1401** + +## **Formalization of interconnection designations among operators' telecommunication networks** + +## **Summary** + +This Recommendation defines designations and additional information intended primarily for human-to-human communication between various Operators, i.e., network operators or service providers. + +This Recommendation contains data definitions for designations of interconnections and other information about network resources that are required to be communicated between operators. + +This Recommendation is developed in order to facilitate computerized interoperation between telecommunication operators. For this use a more formal approach than M.1400 is required. See Appendix III. + +Note that since ITU-T Rec. M.1400 does not formally specify data structures, backward compatibility with existing implementations may not be ensured, but this Recommendation is based on ITU-T Rec. M.1400. For further details, see Appendix II. + +## **Source** + +ITU-T Recommendation M.1401 was approved on 14 July 2006 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Data definitions, designations, domestic, interconnection, international, operator, terminology, X interface. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|---|--------------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Application schema ..... | 3 | +| 7 | Appendices ..... | 18 | +| | Appendix I – Registration of ICCs ..... | 18 | +| | I.1    Introduction ..... | 18 | +| | I.2    ITU ICC procedure..... | 18 | +| | I.3    Distributed ICC web..... | 19 | +| | Appendix II – Remarks ..... | 20 | +| | Appendix III – Data-oriented human-machine interface specification technique –
Formalism..... | 21 | +| | III.1  Introduction ..... | 21 | +| | III.2  Scope ..... | 22 | +| | III.3  References ..... | 22 | +| | III.4  General ..... | 22 | +| | III.5  Objects..... | 22 | +| | III.6  References ..... | 22 | +| | III.7  Attributes ..... | 23 | +| | III.8  Values ..... | 23 | +| | III.9  Functions ..... | 23 | +| | III.10 Schema-Population references ..... | 23 | +| | III.11 Denotations..... | 24 | +| | III.12 Documentation ..... | 24 | +| | III.13 Graphical notation ..... | 25 | +| | III.14 Textual notation..... | 25 | +| | Appendix IV – Example transit network registration ..... | 26 | +| | IV.1  Example..... | 26 | +| | IV.2  Representation ..... | 26 | +| | BIBLIOGRAPHY ..... | 32 | + +# Introduction + +This Recommendation defines designations and additional information intended primarily for human-to-human communication between various Operators, i.e., network operators or service providers. + +The area of interest is the communication between operators about network interconnections and network services. The objects of communication are network interconnection points, places, stations, nodes, interconnection links, and terminating and originating connections and transit connections, etc. Correct terms for these are provided by the application schema defined in this Recommendation. + +This Recommendation focuses on human needs for stable and recognizable data formats independently of what media they are communicated over. Therefore, in order to support the human-to-human communication, the formats defined in this Recommendation are required to be provided at the corresponding human-to-computer interfaces, as well. Hence, this Recommendation defines the presentation formats of data at human-to-computer interfaces, but does not define the data communication formats for interfaces between computer systems, such as at the TMN X interface or non-TMN computer interfaces. However, it should be possible in the future to automatically map the human-to-computer formats to the computer-to-computer formats and vice versa. The details of this mapping are for further study. + +Use of this Recommendation within national jurisdictions may be imposed by the national regulator or may be the result of bilateral negotiation between the operators and/or national regulatory authorities, in accordance with national laws and regulations. + +The Recommendation defines both designations and additional information to be exchanged between two Operators. However, this Recommendation focuses on information on Operators, network resources and their addresses, and does not define order or transaction identification or additional information on the status or processing of these orders or transactions. + +The definition of information is common for the functions it supports. However, the selection of information defined in this Recommendation basically supports provisioning and network maintenance. In addition, this Recommendation may cover some information required for other TMN or non-TMN functions, such as ordering and billing. + +This Recommendation aims at supporting communication between network operators, but may also support communication between network operators and service providers, brokers, retailers, customers and installation providers. + +This Recommendation aims at defining designations and additional information for technicians and file support personnel at their terminals supporting the network, and serves as design information for developers of operational support systems. + +This revision to ITU-T Rec. M.1401 (05/2005) replaces every occurrence of 'Town' with 'Geographical Area' on the basis of 'Geographical Area' being more applicable for the termination of routes than 'Town'. In addition, this revision aligns ITU-T Rec. M.1401 more closely with the ATIS Standard for location identification, which is not restricted to a town. + +Also, text for several data items is repositioned in keeping with the alphabetical sequence of attribute groups and attributes as stated in Clause 5, Conventions. + +## ITU-T Recommendation M.1401 + +## Formalization of interconnection designations among operators' telecommunication networks + +# 1 Scope + +The area of interest is the communication between operators about network interconnections. The objects of communication are network interconnection points, places, stations, nodes, interconnection links, and terminating and originating connections and transit connections, etc. This Recommendation contains definitions of those terms in the application schema. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation M.1400 (2006), *Designations for interconnections among operators' networks*. +- [2] ITU-T Recommendation T.50 (1992), *International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) – Information technology – 7-bit coded character set for information interchange*. +- [3] ITU-T Recommendation T.51 (1992), *Latin based coded character sets for telematic services*. +- [4] ITU-T Recommendation T.52 (1993), *Non-latin coded character sets for telematic services*. +- [5] ISO 3166-1:1997, *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes*. + +# 3 Definitions + +This Recommendation is comprised of structured definitions in the context of an application schema graph. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +- ICC ITU Carrier Code +- SDH Synchronous Digital Hierarchy +- TMN Telecommunication Management Network + +# 5 Conventions + +Figure 1 shows boxes containing object class labels to indicate object classes. Lines supported with a reversed arrowhead indicate subordinate object classes. Lines with two-way arrows indicate references between object classes. A dashed one-way arrow with an S at the arrowhead indicates a schema reference and is here used for stating recursion. + +The text that follows Figure 1 includes a label and explanation for each class in the schema. A class can be an object class, an attribute class, or a reference class. The level of each class is depicted in the text by indentations (5 mm) of the class label, supported with dashes, where the number of indentations and dashes indicates the level of a given class within the schema. Therefore, each class label has a given indentation based on the Figure 1 schema graph. + +Labels of data items that are subordinate to or referenced from a given object class are presented in the following sequence: + +- 1) alphabetized object class attributes; +- 2) alphabetized object class references; and +- 3) alphabetized object classes that are contained within the given object class at the next lower level. + +Textual definitions and explanations of object classes, attributes and references are provided in paragraphs that are adjusted 5 mm further to the right of their respective labels. + +Object class labels are underlined; attribute group and attribute labels are not underlined. Object class references are written in blue, italics and underlined. + +The formalism used in this Recommendation is introduced in Appendix III. + +Data attributes other than Local identifiers consist of sequences of characters taken from Table 1/T.50, each character being either alphabetic (A-Z) or numeric (0-9). Local identifiers consist of sequences of characters which may include characters from other character sets (for example, the non-Latin characters in ITU-T Rec. T.52), on the basis of appropriate bilateral and/or multilateral agreements. Additional requirements for symbols are explicitly stated in format requirements for specific attributes. It is recommended that alphabetic characters be represented with upper-case letters unless stated otherwise. + +# 6 Application schema + +![Figure 1/M.1401 – Application schema graph, depicting object classes (boxes), containment (reversed arrowheads) and references (two-way arrows).](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The diagram illustrates the application schema graph for M.1401. It shows various object classes represented by boxes, connected by containment (reversed arrowheads) and references (two-way arrows). The classes include Country, Operator, Address, Association, Multipoint trail, Geographical area, Cross-coupling site, Termination, Site relationship, Exchange, Location, Equipment identity, Equipment item, Trail, Physical link, Position, Component item, Trail multiplex channel, Physical link connection, Port item, and Trail section. A dashed line with an 'S' indicates a specific relationship between two Location classes. The diagram is labeled M.1401(07-06)\_F01 in the bottom right corner. + +Figure 1/M.1401 – Application schema graph, depicting object classes (boxes), containment (reversed arrowheads) and references (two-way arrows). + +**Figure 1/M.1401 – Application schema graph, depicting object classes (boxes), containment (reversed arrowheads) and references (two-way arrows)** + +### Address + +An Address identifies a geographic location, which may contain a Cross-coupling site. + +### ▪ Site + +An Address' subordinate Site is a role of a Cross-coupling site that is placed at the Address. An Address may have several Sites. + +### Association + +An Association defines an ordered or unordered relationship between a Trail and some other Trails. The ordering is indicated by the Superior trail reference. + +### ▪ Kind + +Kind is indicating the usage of the Association. Kind is a 2-character field, adjusted to the left. S indicates reserve. In this case, Superior trail indicates the main trail, and Trail indicates the reserve trail. + +### ▪ Superior trail + +An Association's subordinate Superior trail is a role of a Trail that controls the Association. In case of an ordered relationship, the Association will have one and only one Superior trail. In case of an unordered relationship, the Association will have no Superior trail. + +### ▪ Trail + +An Association's subordinate Trail is a role of a Trail being controlled by the Association. An Association must have one or more Trails. In case of an unordered relationship, the Association will have two or more Trails. + +### Country + +A Country with its Name and Country Code is defined in ISO 3166-1. + +Operators within a Country are recognized and identified by the national regulatory authorities within that Country. + +### ▪ Code + +The Country Code is a 3-character globally unique code that identifies each Country according to ISO 3166-1. + +### ▪ Name + +The Country Name identifies a Country, dependency, or other area of particular geopolitical interest. Countries are assigned a globally unique Name in ISO 3166-1. + +### ▪ Geographical area + +Geographical area defines a geographical or administrative area defined by the authorities of that Country. + +### ▪ ▪ Name + +Name of the Geographical area as spelled by the authorities in that Country, i.e., in a national language of that Country. Note that different spellings dependent on the user are not permissible. Geographical area Name has up to 12 characters. Upper- and lower-case letters are permitted. Symbols that may be included in Geographical area Name are hyphen (-), underscore (\_ ) and space ( ). In case the spelling given by the authorities exceeds 12 characters is not unique with 12 characters only, the Administration in that Country is responsible for assigning a unique identifier. + +### ▪ ▪ Site + +A Geographical area's subordinate Site is a role of a Cross-coupling site subordinate to Operator. + +This referenced Cross-coupling site's Identifier contains the Geographical area Name. + +### ▪ Operator + +For this Recommendation, an Operator is an organization responsible for identification and management of telecommunication resources. The Operator must be legally recognized by the telecommunication Administration of the Country, or delegation thereof. An Operator may or may not correspond to a trading partner. + +For this Recommendation, an Operator can be a network operator or service provider. + +Both the national authority and the Operators should note that each Operator would be registered as a separate entity in each Country in which it operates, and is required to report country-specific information to each national authority. This may or may not imply a need for a multinational Operator to use different ICCs in each Country. Multinational Operators are encouraged to ensure that they are registered in each Country in which they operate. + +### ▪ ▪ ICC + +The ITU Carrier Code provides a unique identifier of an Operator within a Country. The assignment of ICCs may be delegated to a lower-level regional administration (for example, a province). + +The ICC is used as an indispensable part in the assignment of identifiers for interworking between Operators. It is permissible that an operator uses one ICC for assignment of identifiers, while other operator codes are used for ordering, billing, etc. + +ICC is a 1- to 6-character alphanumeric field. + +See Appendix I on registration of ICCs. + +### - ▪ Controlled site + +An Operator's subordinate Controlled site is a role of a Cross-coupling site that is currently owned by the Operator, but not identified locally to this Operator. If the Operator owns Cross-coupling sites that are not identified locally to this Operator, this reference has to be explicitly provided. + +### - ▪ Controlled trail + +An Operator's subordinate Controlled trail is a role of a Trail being controlled by the Operator. An Operator may have many Controlled trails. Note that Controlled trail indicates responsibility for maintenance and not ownership. + +### - ▪ Cross-coupling site + +The Cross-coupling site allows termination of a Trail, e.g., in an exchange, at a subscriber's premises or other. In case of termination of the Trail, e.g., at the subscriber's premises or in an international transmission centre, the Operator's network is considered to exist at one side of the Cross-coupling site only, i.e., the Operator's network may not include the connection between the Cross-coupling site and the customer's equipment. + +The Cross-coupling site allows cross-couplings to route a Trail through that node, and the Cross-coupling site allows cross-couplings between Trails within that Cross-coupling site. The cross-coupling may use internal equipment, termination points and internal Trails which are associated to the routed Trail. + +The cross-couplings may be provided by automated management, e.g., in digital cross-connect or SDH network matrixes, or the cross-connect can be made manually as in a fibre matrix. However, a Cross-coupling site typically may contain more than a single piece of such Equipment items, and the individual Equipment item should not be registered as a Cross-coupling site. + +A Cross-coupling site can be a transmission station, a radio station, a base station, an earth station, a distribution frame, or a junction box, which as a special case can be an end junction box. + +A control station or sub-control station can be registered as a Cross-coupling site even if it may not provide for cross-couplings within that site. + +A Cross-coupling site cannot be geographically distributed over more than one building. However, it is also permissible to define several Cross-coupling sites at the same Address. In this case, separate Trails and other resources shall be defined to route Trails between these Cross-coupling sites at the same Address. + +A cross-coupling within a Cross-coupling site is typically made on the basis of a cross-coupling or routing order. Hence, the cross-couplings are considered to be semi-permanent. Junctions which contain permanent cross-couplings or permanently installed equipment, are not Cross-coupling sites. Note that this permanently installed equipment outside Cross-coupling sites may still be subject to automatic surveillance by management functions. + +A Cross-coupling site may contain one or more Exchanges, concentrators, routers and other equipment. + +### ▪ ▪ ▪ Identifier + +The Identifier uniquely identifies the Cross-coupling site within the scope of an Operator. Cross-coupling sites of different Operators, e.g., in the same room, shall be defined as separate Cross-coupling sites. However, if the place is managed by one Operator only, the place should be defined as one Cross-coupling site locally to that Operator. The other Operator's Equipment items, Exchanges and Locations shall then be identified locally to this Operator's Cross-coupling site. Hence, registration of ownership of Equipment items is distinguished from naming of the Equipment items within the Cross-coupling site. + +Aliases of Cross-coupling site Identifiers are not permitted for communication between Operators of different Countries. However, Operators may exchange Local identifiers that are local to a specific Operator, country or region. + +Note that some Operators may use the name of the Geographical area, or an abbreviation for this, as a part of the Cross-coupling site Identifier or for some of their Cross-coupling site Identifiers, while other Operators may not. The name of the Geographical area, if any, will additionally be provided in the Cross-coupling site's subordinate Address. + +### ▪ ▪ ▪ ▪ Geographical area + +The Name of the Geographical area being referenced in the Cross-coupling site's subordinate Geographical area. See field length and use of characters in this Name. + +### ▪ ▪ ▪ ▪ Site detail + +An identifier of the Cross-coupling site that is at least unique within a Geographical area and an Operator. This requirement does not prohibit that someone choose to make the identifier independent of Geographical area or Operator. The identifier has up to six characters. Symbols that may be included are hyphen (-), underscore (\_ ) and space ( ). + +### ▪ ▪ ▪ Local identifier + +An identifier of the Cross-coupling site that is unique within an Operator, having up to 18 alphabetic and/or numeric characters. A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in ITU-T Rec. M.1400. + +### ▪ ▪ ▪ Address + +A Cross-coupling site's subordinate Address is a role of an Address denoting a geographical location. A Cross-coupling site has one Address only, which is the physical location address of the Cross-coupling site. + +Note that the Cross-coupling site's subordinate Exchanges, Locations and Equipment items do not have separate references to Addresses, but their detailed addresses may be provided in address notes. + +### ▪ ▪ ▪ A-end site relationship + +A Cross-coupling site's A-end site relationship is a role of a Site relationship, of which the Cross-coupling site is referenced as an A-end site. A Cross-coupling site may have multiple A-end site relationships. + +### ▪ ▪ ▪ B-end site relationship + +A Cross-coupling site's B-end site relationship is a role of a Site relationship, of which the Cross-coupling site is referenced as a B-end site. A Cross-coupling site may have multiple B-end site relationships. + +### - ▪ ▪ Current operator + +A Cross-coupling site's subordinate Current operator is a role of an Operator who is currently responsible for the Cross-coupling site. A Cross-coupling site may have one Current operator only. If the Current operator deviates from the superior Operator of the Cross-coupling site, it has to be explicitly provided. + +### - ▪ ▪ Geographical area + +A Cross-coupling site's subordinate Geographical area is a role of a Geographical area subordinate to Country. The Name of this Geographical area is used as a part of the Cross-coupling site Identifier. + +### - ▪ ▪ Termination + +A Cross-coupling site's subordinate Termination is a role of a Trail's subordinate Termination. A Trail may have two Terminations, and a Cross-coupling site may have one or two Terminations for each Trail. + +### - ▪ ▪ Equipment item + +An Equipment item provides a collection of functions and is considered as a unit from a placement point of view in a Location. + +An Equipment item may be an Exchange, taking up a whole room, and it may be an individual circuit card. + +### - ▪ ▪ ▪ Identifier + +An Equipment item is assigned a unique Identifier within the scope of its superior Cross-coupling site. Room identification may or may not be a part of the Equipment item Identifier. The Operator of the Cross-coupling site assigns the Equipment item Identifier, and different pieces of Equipment items within a Cross-coupling site may be owned or used by different entities. + +Aliases of Equipment item Identifiers are not permitted for communication between Operators. However, Operators may exchange additional Equipment item identifiers that are local to a specific Operator. + +### - ▪ ▪ ▪ Unique item identification + +The manufacturer may assign a Unique item identification (UID) to an Equipment item. + +### - ▪ ▪ ▪ Equipment identity + +An Equipment item's subordinate Equipment identity is a role of an Equipment identity to which the Equipment item belongs. + +### - ▪ ▪ ▪ Exchange + +An Equipment item's subordinate Exchange is a role of an Exchange that is implemented by the Equipment item. + +### - ▪ ▪ ▪ Location + +An Equipment item's subordinate Location is a role of a Location subordinate to the superior Cross-coupling site or a recursively subordinate Location. Each Equipment item shall be assigned exactly one Location placement where the Equipment item can be found. + +### - ▪ ▪ ▪ Component item + +A Component item is a separate unit, e.g., a circuit card, within an Equipment item. A Component item has a specified Location, and a Component item has one or more Port items, which may provide inputs, outputs or both. + +- ▪ ▪ ▪ ▪ Identifier + +A Component item is assigned a unique Identifier within the scope of the superior Equipment item. + +- ▪ ▪ ▪ ▪ Unique item identification + +The manufacturer may assign a Unique item identification (UID) to a Component item. + +- ▪ ▪ ▪ ▪ Equipment identity + +A Component item's subordinate Equipment identity is a role of an Equipment identity to which the Component item belongs. + +- ▪ ▪ ▪ ▪ Location + +A Component item's subordinate Location is a role of a Location subordinate to the Location of the Equipment item containing the Component item. Each Component item shall be assigned exactly one Location placement where the Component item can be found. + +- ▪ ▪ ▪ ▪ Port item + +A Port item defines a functional unit of a Component item of an Equipment item. The Port item can be sender, receiver, or bidirectional. It may also be possible to modify the function of a Port item. + +- ▪ ▪ ▪ ▪ Identifier + +A Port item is assigned a unique Identifier within the scope of its superior Component item. + +- ▪ ▪ ▪ ▪ Equipment identity + +A Port item's subordinate Equipment identity is a role of an Equipment identity to which the Port item belongs. + +- ▪ ▪ ▪ ▪ Position + +A Port item's subordinate Position is a role of a Position that terminates the Port item. + +- ▪ ▪ ▪ ▪ Trail section + +A Port item's subordinate Trail section is a role of a Trail section in a Trail. + +- ▪ ▪ Exchange + +An Exchange is an entity that directs individual calls, packages or cells. + +Exchanges can be switches, concentrators or routers. Exchanges can be customer exchanges or transit exchanges. Intelligent Network servers and Operation Support System servers are not Exchanges and are not Cross-coupling sites. A Cross-coupling site may contain several Exchanges of various types. + +- ▪ ▪ ▪ No + +The number No uniquely identifies an Exchange within the scope of a Cross-coupling site. The managing Operator of the superior Cross-coupling site decides the numbering. + +Note that it is permissible to define a Cross-coupling site for each Exchange or a set of Exchanges at the same Address. In this case, separate Trails and other resources are required to route Trails between these Cross-coupling sites at the same Address. See also under Cross-coupling site. + +### - ▪ ▪ ▪ Equipment item + +An Exchange's subordinate Equipment item is a role of an Equipment item subordinate to a Cross-coupling site. The Exchange object class role is provided due to the specific identification of Exchanges different from identification of Equipment item in general. The reference via Equipment item provides a reference to the placement of the Exchange in a specific Location, e.g., in a room. + +### - ▪ ▪ Location + +A Location is a subdivision of a Cross-coupling site. It is an object in which resources, such as Exchanges, Equipment items and termination points, are placed. It should be noted that the term "Location" is here given a particular meaning local to Cross-coupling site, and that this definition may not apply for the generic term location. + +A Location can be a room, a frame, a rack, a block, a shelf or a slot in a shelf, and these may contain subordinate Locations recursively. + +### - ▪ ▪ ▪ Identifier + +The Identifier of a Location uniquely identifies a Location within a superior Location or Cross-coupling site. The Identifier may consist of both digits and letters. The Location Identifier is assigned by the Operator of the Cross-coupling site. + +### - ▪ ▪ ▪ Unique item identification + +The manufacturer may assign a Unique item identification (UID) to a Location + +### - ▪ ▪ ▪ Component item + +A Location's subordinate Component item is a role of a Component item of an Equipment item in this Location. + +#### - ▪ ▪ ▪ Equipment identity + +A Location's subordinate Equipment identity is a role of an Equipment identity to which the Location belongs. + +#### - ▪ ▪ ▪ Equipment item + +A Location's subordinate Equipment item is a role of an Equipment item being placed in this Location. + +### - ▪ ▪ ▪ Location + +A Location may contain Locations recursively. + +### - ▪ ▪ ▪ ▪ $S \leftrightarrow 'Location' Location$ + +The recursion is indicated by the subordinate Location class inheriting properties by the S(chema) reference to its superior Location class. + +### - ▪ ▪ ▪ Position + +A Position is a unit that is used to enter terminations and cross-couplings. The Position can be an individual pin, a pair of pins or a group of pins, depending on the design, planned or actual use of the Position. + +### - ▪ ▪ ▪ ▪ Identifier + +A Position is assigned a unique Identifier within the scope of its superior Location. The Identifier may, e.g., indicate a group of pins (3), or an individual pin (3a). + +### - ▪ ▪ ▪ ▪ Physical link connection + +A Position's subordinate Physical link connection is a role of a Physical link connection being terminated on this Position. + +### ▪ ▪ ▪ ▪ ▪ Port item + +A Position's subordinate Port item is a role of a Port item being terminated on this Position. + +Note that the Position can be on the slot of the shelf. This allows cables to be terminated on the slot of the shelf and not on the card, and thus allows the card to be easily replaceable. + +### ▪ ▪ ▪ ▪ ▪ Position + +A Position's subordinate Position is a role of another Position that is connected by cross-coupling or termination to this Position. + +Note that the cross-coupling or termination is assigned no direction. This means, e.g., that if the termination is from a position (i.e., a connector) on a slot in a shelf to a pin group on a block, only the names of the two Positions indicate the direction. + +### ▪ ▪ ▪ ▪ ▪ Trail + +A Position's subordinate Trail is a role of a Trail being terminated on this Position. + +### ▪ ▪ ▪ ▪ ▪ Trail multiplex channel + +A Position's subordinate Trail multiplex channel is a role of a Trail multiplex channel being terminated on this Position. + +### ▪ ▪ ▪ ▪ ▪ Trail section + +A Position's subordinate Trail section is a role of a Trail section in a Trail. + +### ▪ ▪ Multipoint trail + +A Multipoint trail is a connected set of Trails that are connecting three or more endpoints. A Multipoint trail can reside within one Cross-coupling site, or it may connect two or more Cross-coupling sites. + +### ▪ ▪ ▪ Identifier + +The Identifier uniquely identifies the Multipoint trail within the scope of an Operator. This means that if the resources of a Multipoint trail are shared between Operators, each Operator may assign its local Identifier to the Multipoint trail. This scheme is different from Identifiers of Trails within the Multipoint trail, as they are identified locally to Site relations. + +### ▪ ▪ ▪ Local identifier + +An identifier of a Multipoint trail that is unique within an Operator, having up to 26 alphabetic and/or numeric characters. A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in ITU-T Rec. M.1400. + +### ▪ ▪ ▪ Trail + +A Multipoint trail's subordinate Trail is a role of a Trail that is contained in the Multipoint trail. + +### Equipment identity + +A category of equipment instances that may be characterized by a combination of: + +- manufacturer name; +- manufacturer part number; +- manufacturer equipment version number; +- equipment category number; +- substitutability (upward/downward compatible replacement). + +An Equipment identity may categorize a set of Equipment items, Component items, Port items, or Locations, but an Equipment identity cannot categorize items belonging to more than one of these classes simultaneously. + +### ▪ Identifier + +A code that uniquely identifies a type of manufactured telecommunications network equipment or an assignable entity within a type of equipment. This code is assigned on behalf of the manufacturer. + +### ▪ Component item + +An Equipment identity's subordinate Component item is a role of a Component item belonging to the Equipment identity. An Equipment identity may relate to several Component items, and one Component item may relate to only one Equipment identity. + +### ▪ Equipment item + +An Equipment identity's subordinate Equipment item is a role of an Equipment item belonging to the Equipment identity. An Equipment identity may relate to several equipment items, and one Equipment item may relate to only one Equipment identity. + +### ▪ Location + +An Equipment identity's subordinate Location is a role of a Location belonging to the Equipment identity. An Equipment identity may relate to several Locations, and one Location may relate to only one Equipment identity. + +### ▪ Port item + +An Equipment identity's subordinate Port item is a role of a Port item belonging to the Equipment identity. An Equipment identity may relate to several Port items, and one Port item may relate to only one Equipment identity. + +### Site relationship + +A Site relationship is a combination of exactly two Cross-coupling sites. The two Cross-coupling sites may be different or the same. The last case is used in case of identification of internal Trails within a Cross-coupling site. + +### ▪ Identifier + +An Identifier of a Site relationship is an attribute group that uniquely identifies the Site relationship. The scope of the identification may be global in case of international Trails, which means that all fields are required to be filled in. The scope may be a Country in case of inter-operator Trails within that Country, which means that the two Country Codes may be left out. The scope may be the Operator in case of intra-operator Trails, which means that the two ICCs may be left out, and only the two Cross-coupling site Identifiers are filled in. This last case is outside the scope of this Recommendation. + +- ▪ A-end + + +The A-end of the Identifier is an attribute group uniquely identifying the Site relationship's subordinate A-end site. +- ▪ ▪ Country Code + + +Country Code identifies (recursively superior) Country of the Site relationship's A-end site. +- ▪ ▪ ICC + + +ICC identifies the (superior) Operator of the Site relationship's A-end site. +- ▪ ▪ Site + + +Site contains the Identifier of the Cross-coupling site referenced by the Site relationship's A-end site. +- ▪ B-end + + +The B-end of the Identifier is uniquely identifying the Site relationship's subordinate B-end site. +- ▪ ▪ Country Code + + +Country Code identifies (recursively superior) Country of the Site relationship's B-end site. +- ▪ ▪ ICC + + +ICC identifies the (superior) Operator of the Site relationship's B-end site. +- ▪ ▪ Site + + +Site contains the Identifier of the Cross-coupling site referenced by the Site relationship's B-end site. +- Local identifier + + +The Local identifier of a Site relationship is an attribute group that uniquely identifies the Site relationship. + +A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in ITU-T Rec. M.1400. + +Aliases of Cross-coupling site Identifiers are not permitted for communication between Operators of different Countries. However, Operators may exchange Local identifiers that are local to a specific Operator, country or region. +- ▪ A-end + + +The A-end of the Local identifier uniquely identifies the Site relationship's subordinate A-end site, using its Local identifier. +- ▪ B-end + + +The B-end of the Local identifier uniquely identifies the Site relationship's subordinate B-end site, using its Local identifier. +- [\*A-end site\*](#) + +The A-end site is a role of the Cross-coupling site having the distinguished name that comes first in the alphabet. The distinguished name consists of Country Code, ICC and Cross-coupling site Identifier, in that sequence. + +### - B-end site + +The B-end site is a role of the Cross-coupling site having the distinguished name that comes last in the alphabet. The distinguished name consists of Country Code, ICC and Cross-coupling site Identifier, in that sequence. + +### - Physical link + +A Physical link represents a set of parallel physical transport resources between two Cross-coupling sites. The physical transport resources are called Physical link connections. All Physical link connections in a Physical link shall be routed in the same cable branches. A cable branch connects either two Cross-coupling sites or two junctions where the pairs of the cable branch are split into pairs of cable branches leading to two or more different Cross-coupling sites. Cable branches represent one layer of the physical network, and Physical links represent the layer at which resources are allocated to route Trails of multiplex groups or other usages. + +A Physical link is terminated in exactly two Cross-coupling sites, which allow for termination of cross-couplings between Physical link connections. A Physical link cannot terminate in a junction that requires construction work to provide the couplings. + +Note that attributes of physical resources are different from attributes of logical resources and trail notions. + +### - ▪ Identifier + +The Identifier of a Physical link uniquely identifies the Physical link within the Site relationship. Note that Physical links are identified independently from Trail Identifiers within the same Site relationship. This allows cable and radio resources to be identified independently from Trails and the concerns of customers in the use of Trail Identifiers. + +### - ▪ Physical link connection + +A Physical link connection represents a physical resource between two Cross-coupling sites and can be allocated to a single Trail. The resource may represent a single fibre, a pair, a set of two pairs or other, which is planned to be used as a section of a Trail. + +### - ▪ ▪ Identifier + +The Identifier of a Physical link connection uniquely identifies the Physical link connection within the Physical link. The syntax of the Identifier may indicate that it represents a single branch (e.g., 3a), a pair (3), a set of two pairs (3-) or other. + +### - ▪ ▪ Position + +A Physical link connection's subordinate Position is a role of a Position on which the Physical link connection is terminated. + +### - ▪ ▪ Trail section + +A Physical link connection's subordinate Trail section is a role of a Trail section in a Trail. + +### - Trail + +A Trail provides a transport of signals between two Cross-coupling sites. The Cross-coupling site Positions may be located in Cross-coupling sites within different Countries, by different Operators, the same Operator, or within one and the same Cross-coupling site – in case of internal Trails. Also, the Trail may be terminated at the customer premises, i.e., outside the Cross-coupling site. Trails being terminated by the same Operator are outside the scope of this Recommendation. + +The Trail may be routed via several connected Cross-coupling sites. The routing and involved cross-couplings of the Trail are established on a semi-permanent basis based on a coupling order. However, switching to alternate Trails may be provided dynamically. + +A Trail may be routed on other Trails, e.g., each Operator may define a separate Trail Identifier for the routing within its domain, while a common inter-operator Trail is defined for the total routing. Also, the detailed routing within a Cross-coupling site may be defined in a separate internal Trail. + +A Trail may be involved as a part of a multipoint Trail, e.g., a ring. In this case, no Trail should be defined to pass the branching points. However, Trails routed on subordinate Trail multiplex channels may be routed through the branching points. + +The Trail may be established as a means to configure the Operator's network or be established to provide a service or product to a customer. + +The Trail may provide: + +- a transmission system functionality, e.g., a coax system between two pieces of line termination equipments; +- a multiplex group capacity, e.g., an SDH link; +- a reserve functionality, e.g., an alternate routing for a multiplex group; +- a traffic capacity, e.g., for routing of traffic between two (neighbouring) Exchanges; +- a user functionality, e.g., a leased line between two customers. + +Note that Trails are semi-permanent, which means that Trails do not comprise temporary dialled circuits, which directs traffic over a series of Trails. Also, Trails are not permanent cable resources between two (neighbouring) junction boxes. Dialled circuits are switched dynamically, and cable resources are installed permanently. Dialled circuits are established on the basis of a call attempt per call, per file transfer or per packet and are not established based on a coupling order. Cable resources are established based on construction plans and not on coupling orders. + +### - ▪ Bandwidth + +This attribute group defines the capacity of the medium. + +### - ▪ ▪ Actual + +This attribute group defines the actual capacity being allocated to the Trail. + +### - ▪ ▪ ▪ Size + +This attribute defines the Size of the Actual bandwidth as a multiple of the unit being given in the Unit attribute. This is a 5-character field of decimal digits adjusted to the right without leading zeros. + +### - ▪ ▪ ▪ Unit + +This attribute defines the unit being used to give the Size of the Actual bandwidth. The Unit is given in an alphanumeric 4-character field and is adjusted to the left. + +NOTE – This field must be provided if Size is provided, or Size may be a multiple of a default unit. + +### - ▪ ▪ Maximum + +This attribute group defines the maximum available capacity of the medium. + +### - ▪ ▪ ▪ Size + +This attribute defines the Size of the Bandwidth as a multiple of the unit being given in the Unit attribute. This is a 5-character field of decimal digits adjusted to the right without leading zeros. + +### - ▪ ▪ ▪ Unit + +This attribute defines the unit being used to give the Size of the Bandwidth. The Unit is given in an alphanumeric 4-character field and is adjusted to the left. + +NOTE – This field must be provided if Size is provided, or Size may be a multiple of a default unit. + +### - ▪ Identifier + +The Identifier of a Trail uniquely identifies the Trail within the Site relationship. + +Note that the Identifier of the Trail's superior Site relationship is independent of the identifiers of the Exchanges, Locations or Equipments in which the Trail is terminated. + +Note also that the Identifier of the superior Site relationship is independent of traffic or transmission direction of the Trail. + +### - ▪ Local identifier + +An identifier of a Trail that is unique within an Operator, having up to 26 alphabetic and/or numeric characters. A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in ITU-T Rec. M.1400. + +### - ▪ Signalling + +This attribute indicates the signalling system or signalling type being used on the Trail. + +The attribute is a 20-character alphanumeric field adjusted to the left. The permissible values are for further study. + +### - ▪ Urgency + +Urgency defines priority of restoration and may define a deadline for the restoration. + +### - ▪ ▪ Deadline + +Deadline defines date and hour for completion of the restoration. + +When transferred between time zones, the Deadline shall be given in standard GMT. + +When communicating within a time zone, two operators may agree to use local time. + +Each of the four fields is given by 2 decimal numbers with leading zeros. Either all fields are filled in or all are left blank. + +The fields may be calculated automatically from Limit and entering time when entered, be transformed to GMT when transferred and recalculated to local time at the receiving end if the communicating users are made aware of this conversion. + +The attribute has the substructure given below, and the fields may be separated by punctuation marks (.). + +### - ▪ ▪ ▪ Date + +### - ▪ ▪ ▪ ▪ Day + +### - ▪ ▪ ▪ ▪ Month + +### - ▪ ▪ ▪ ▪ Year + +### - ▪ ▪ ▪ Time + +#### - ▪ ▪ ▪ ▪ Hour + +### - ▪ ▪ Limit + +Limit defines number of hours for the restoration to be completed. The hours are counted from the moment when the Limit is given. The field length is 2 decimal digits, with leading zeros, or the field may be left blank. + +### - ▪ ▪ **Priority** + +Priority defines priority classes for restoration. The field length is 1 character, and the permissible values are 1, 2 and 3, or the field may be left blank. + +### - ▪ *Association* + +A Trail's subordinate Association is a role of an Association. A Trail may be involved in several Associations. + +### - ▪ *Controller* + +A Trail's subordinate Controller is a role of an Operator. A Trail may have several Controllers listed in falling priority. Note that Controller indicates responsibility for maintenance and not ownership. + +### - ▪ *Multipoint trail* + +A Trail's subordinate Multipoint trail is a role of a Multipoint trail that is supported by the Trail. + +### - ▪ *Position* + +A Trail's subordinate Position is a role of a Position that terminates the Trail. + +### - ▪ *Routing trail section* + +A Trail's subordinate Routing trail section is a role of a Trail section in the routing of another Trail, which is routed on the current Trail. + +### - ▪ *Subordinate association* + +A Trail's subordinate Subordinate association is a role of an Association. A Trail may have several Subordinate associations. + +### - ▪ *Termination* + +A Trail's subordinate Termination indicates termination in a Cross-coupling site. A Trail will normally have two Terminations. + +### - ▪ ▪ **Direction** + +A Termination's Direction indicates transmission direction of the Trail. The Direction can be S(ender), R(eceiver) or T(wo-way). If the Direction is S(ender), then the Direction of the other Termination is R(eceiver) and vice versa. If the D(irection) is T(wo-way), then the Direction of the other Termination is T(wo-way), as well. + +#### - ▪ ▪ *Cross-coupling site* + +A Termination's subordinate Cross-coupling site is a role of a Cross-coupling site. A Termination has just one Cross-coupling site, and a Cross-coupling site may have one or two Terminations for a Trail. + +#### - ▪ *Trail multiplex channel* + +A Trail may be split into several parallel Trail multiplex channels. The Trail multiplex channels in a Trail may have different capacities. All Trail multiplex channels in a Trail have the same routing, as the routing is assigned to Trails only, and not to Trail multiplex channels. + +Each Trail multiplex channel is terminated in the same multiplex Equipment item as the superior Trail. The Trail may be terminated at the higher capacity side of the Equipment item, while the Trail multiplex channels are terminated at the lower capacity side. Also, Trail multiplex channels and Trails may be terminated at Connection termination points or Trail termination points inside the Equipment item, as may be the case in SDH network matrixes. + +Trail multiplex channels may be implemented by different technologies, like frequency multiplexing, pulse code multiplexing, etc. + +- ▪ ▪ Number + +Trail multiplex channels are numbered within their superior Trail. + +Note that this naming scheme is different from naming of linkConnections within links within layerNetworkDomains. However, the scheme does not prohibit definition of a Trail for each link, as long as all linkConnections have the same routing. + +- ▪ ▪ Position + +A Trail multiplex channel's subordinate Position is a role of a Position on which the Trail multiplex channel is terminated. + +- ▪ ▪ Trail section + +A Trail multiplex channel's subordinate Trail section is a role of a Trail section in the routing of the Trail. + +- ▪ Trail section + +A Trail section is any element that makes up the routing of a Trail. + +Normally, Trail sections are connected in series to define the routing. + +However, Trail section may also define parallel elements. + +Example of a two-pair circuit: The Trail is defined as a series of Trail sections, each of these Trail sections is split in two parallel Trail sections, representing individual cable pair. + +Example of diverse routing of a two-pair circuit: The Trail is split in two parallel Trail sections representing a circuit pair, each Trail section is defined as a series of Trail sections, representing individual cable pairs. A more comprehensive registration can be obtained by letting the two parallel Trail sections represent one individual Trail each, with separate Identifiers, each of these Trails is defined as a series of Trail sections, representing individual cable pairs. + +There is no defined hierarchy between Trail sections by containment or references. However, the subordinate Trail sections are immediately following their superior Trail section, and information in each Trail section indicates if they represent an individual fibre, a pair, or a set of pairs. + +Users may do both selection and projection of Trail sections within a Trail. Selection means that only Trail sections within a geographical area may be listed. Projection means that only Trail sections connecting different Cross-coupling sites may be listed, etc. + +- ▪ ▪ Identifier + +A Trail section may have an Identifier that uniquely identifies the Trail section within the Trail. + +- ▪ ▪ Physical link connection + +A Trail section's subordinate Physical link connection is a role of a Physical link connection that is included in the routing of the Trail. + +- ▪ ▪ Port item + +A Trail section's subordinate Port item is a role of a Port item that is included in the routing of the Trail. + +- ▪ ▪ Position + +A Trail section's subordinate Position is a role of a Position that is included in the routing of the Trail. + +- ▪ ▪ Trail + +A Trail section's subordinate Trail is a role of a Trail that is included in the routing of the Trail. + +- ▪ ▪ Trail multiplex channel + +A Trail section's subordinate Trail multiplex channel is a role of a Trail multiplex channel that is included in the routing of the Trail. + +# 7 Appendices + +This Recommendation contains four appendices containing additional information, and a bibliography. Appendix I contains procedures for registration of ICCs on the basis of information provided by national authorities. Appendix II contains some notes on work for further study. Appendix III presents notions of the formalism used in this Recommendation for the specification of end-user terminology. Appendix IV provides an example transit network registration. + +## Appendix I + +### Registration of ICCs + +### I.1 Introduction + +There are two procedures for registering ICCs: + +- ITU ICC procedure; +- Distributed ICC web. + +### I.2 ITU ICC procedure + +ICCs are registered by ITU-TSB. Instead of individual Operators sending their ICCs to the TSB for registration, the national regulatory authorities are requested to provide the validated codes and related information of domestic Operators directly to the ITU-TSB. + +NOTE – ITU-TSB is the International Telecommunication Union – Telecommunication Standardization Bureau. + +The national authority in each Country is requested to: + +- collect the filled-in form from each Operator in that Country; +- ensure that the ICCs are unique within that Country; +- ensure that all information on the ICC Notification Form is provided; and +- to submit the information to the TSB Director. + +The national authority should inform operators in that Country on the need of using the ICCs for designations to be used in inter-operator communication. + +The national authority should collect and submit the required information whenever new Operators appear in that Country. Incremental changes to the information on operators in each Country should be reviewed and submitted to the TSB at least once a year. + +Only in case that the national authority cannot take the described responsibility may the Operator itself contact the TSB directly to obtain an ICC. The TSB will reject applications for ICCs which are already in use in that Country. + +Information on the ICCs in use together with the contact information will be found on the ITU web at [www.itu.int/ITU-T/inr/icc/index.html](http://www.itu.int/ITU-T/inr/icc/index.html). + +### **I.3      Distributed ICC web** + +Administrations may choose to maintain their own website and be referenced from the central ITU ICC website. The central ITU ICC website together with referenced websites from the central ITU ICC website is referred to as the ITU distributed ICC web. Note that only Administration's websites or websites established on behalf of Administrations can be incorporated into the ITU-distributed ICC web. One organization, e.g., NECA, may manage local ICC websites for several Administrations. + +NOTE – NECA is the National Exchange Carrier Association, Inc. in North America. + +The central ITU ICC website may include a page for ICC information, having one entry for each country. Each entry may have a reference to a local ICC website containing the appropriate information about ICCs in that country. Some Administrations may ask the TSB to maintain their list of ICCs at the central ITU ICC website, while others may choose to establish their own website, e.g., through NECA. + +Administrations that choose to incorporate a website into the ITU-distributed ICC web shall fill in a form that remains to be created by the TSB and return it to the TSB. + +The local ICC website to be referenced shall in a direct way provide: + +- 1)      the same kind of information as on the central ITU ICC website, as provided through TSB Circular 253; +- 2)      name of country and country code for that country; +- 3)      name of Administration and address of this Administration; +- 4)      name of organization providing the local ICC website and contact address to a person responsible for the local ICC website; +- 5)      reference to the central ITU ICC website. + +It should be noted that ICCs can be assigned both to ITU-T and non-ITU-T members, and the referenced local ICC website may contain ICCs of operators of both kinds. + +All local ICC websites should be accessible free of charge. It is up to each Administration to charge operators for being registered and for the ITU-T to charge Administrations for registration of references to their local website or operator information maintained on behalf of that Administration. One method of cost recovery is for assessing an annual fee to each operator for maintaining and updating the operator's data in the registry. + +Each local ICC website page may contain references to information on other pages that is not publicly available or free of charge. + +The local ICC website page must support the same data formats as on the central ITU ICC website page, but may provide more restricted variants of these formats, e.g., shorter field lengths, restrictions on character sets, etc. + +The local ICC website page(s) should not contain additional information that makes it difficult to select the same kind of information as on the central ITU ICC website pages. + +The local website pages(s) shall in particular not provide advertising information, but can provide simple logos and names that refer to other websites that have such information. + +The local website page(s) may use other layouts than that of the central ITU ICC website, but organizations are encouraged to use the central ITU ICC website pages as a model for their design. + +Registration procedures for each local ITU ICC website may be developed by each Administration. + +## Appendix II + +### Remarks + +Decomposition of Address information is for further study. + +Definition and identification of ring is for further study. + +Mappings to TMN are for further study. + +Definition and explanation of architecture, notations and methods are for further study. + +The physical cable network may contain additional object classes that are not used for routing purposes, e.g.: + +- Junction, which is a site that is used for cable splitting (splice junction), cable junctions, regenerators, repeaters, etc. Junctions require construction work and do not allow for cross-couplings. Cross-coupling is restricted to Cross-coupling sites; +- Cable section, connecting two adjacent junctions; +- Cable series providing a series of one or more Cable sections; +- Cable branch, between two junctions where the cable is split in two or more Cable branches leading to different Cross-coupling sites; thus, a Cable branch may contain Cable series both in sequence and in parallel; +- Multipoint physical link, containing all Cable branches which can be reached by passing junctions without crossing Cross-coupling sites; +- Cable section connection, a fibre or pair of parallel physical resources within the Cable section; +- Cable series connection, a series of Cable section connections; +- Cable branch connection, a fibre or pair of parallel physical resources within Cable branch; a series of Cable branch connections makes up a Physical link connection; a Cable branch connection is a series of Cable series connections; +- Multipoint physical link connection; a set of connected Cable branch connections having three or more endpoints. + +In addition to the above, comes a set of object classes to define sites, manholes, ducts, cable beds, placements, geography, distances, etc. + +Note that Logical links are not provided. Trail is used as a substitute, as this allows routing of the entire Trail and does not require routing of each of its individual channels. + +Note that Links in TMN are identified locally to layer network domain, while Physical link is here identified locally to Site relationship. The same goes for Trails. + +Note that hierarchical recursive decomposition of circuit packs is not provided; only hierarchical recursive decomposition of Locations is supported. + +Note that this Recommendation addresses the physical equipment and not the contained network elements and their internal Connection termination points and Trail termination points, which are the focus of network element management in TMN. + +Termination of Physical link, e.g., with assignment of direction within the access network, is for further study. + +Termination of Trail in Exchanges and assignment of traffic direction is for further study. + +This Recommendation covers routing on Equipment within Sites; customer equipment at the customer premises is not covered. + +This Recommendation treats physical resources within the Operator's network; products as sold to the customer are not covered. + +Attributes of Trail sections are for further study. + +Treatment of cross-couplings as individual Trail sections is for further study. + +Subclasses of Trail sections are for further study. + +External transmission media, clouds or sub-networks that are used to represent incomplete routing, informal routing or routing outside the scope of the current listing are not provided. + +Multipoint Physical links, multipoint physical link connections, multipoint trail multiplex channels and rings are not provided. + +In a Multipoint trail, a distinction can be made between Trail branches, connecting two branching points and/or end-points, and Trails, between endpoints only. If this distinction is made, then some Trails will be routed on the same resources, i.e., there will be several Trail sections for a given resource. A discussion on the needs of this distinction should be undertaken before the scope of the Recommendation is expanded on this point. + +Use is for further study. + +Transmission medium information is for further study. + +Also, other attributes are for further study. + +Local identifier of Cross-coupling site is introduced to allow mappings to North American T1 standards1 and other regional or national standards. + +## Appendix III + +### Data-oriented human-machine interface specification technique – Formalism + +### III.1 Introduction + +This appendix presents notions for the specification of end-user terminology and grammar of an application area. This specification may be provided in a separate External Terminology Schema. This schema provides a sub-layer of the Application Schema of a computer application system. See ITU-T Recs M.3300, Z.351 and Z.352. + +In the end-user terminology, both class and instance data labels may be local to other data labels. This provides data management and definitions within contexts. + +Also, both classes and instances may use significant duplicates within ordered lists; hence, strict naming may not be required. See the description of Identifiers under the Attributes clause. + +End-users may request access to both class and instance data; hence, a homomorphic mapping from instances to classes is required to allow easy navigation between these. See the Schema-Population References section. + +Finally, this appendix introduces the syntax of the formalism and does not emphasize modelling/semantics; however, a means for stating Denotation mappings is provided. See the Denotations clause. + +--- + +1 T1 standards are maintained since November 2003 by ATIS. + +### III.2 Scope + +The area of interest is the communication between end users, human-computer designers, implementers and computers about the terminology and grammar of data at the human-computer interface. The objects of communication are the terminology and grammar of both class data, such as headings, and instance data, such as values, at the human-computer interface. + +This appendix focuses on specification of data that appear in forms and graphics, and does not target natural language and stream interfaces. Hence, this appendix provides key notions for the specification of human-computer interfaces to Operations Support Systems (OSSs). + +### III.3 References + +- [1] ITU-T Recommendation Z.351 (1993), *Data oriented human-machine interface specification technique – Introduction*. +- [2] ITU-T Recommendation Z.352 (1993), *Data oriented human-machine interface specification technique – Scope, approach and reference model*. + +### III.4 General + +Data are arranged in a data tree, with references between the nodes in the tree. + +The data nodes may be categorized as Objects, References, Attribute groups, Attributes or Values. This categorization is permitted for the convenience of the designers and users of the specification. The categorization depends on the specification designer's understanding of the application area. + +However, once a choice has been made, this can have implications for the further choices. + +Schema nodes are introduced to prescribe the form and behaviour of data in its Population node(s). A Schema is considered to contain the rules of the instantiated data found in the corresponding Population. The data in the Schema are referred to as classes relative to their instances in the Population. The Schema data are also collectively called specifications relative to the Population data. + +Functions are introduced to further express constraints on and derivations of data. Schema-Population references are introduced to enforce constraints and derivations on instance data. + +### III.5 Objects + +An Object class can either be the root of the data tree in a Schema or be immediately subordinate to some other Object class in the Schema. All instantiated data of an Object class are Object instances. Every Object instance is of one Object class only. + +Both Object classes and Object instances are called Objects. If something is an Object, then its superior node in the data tree is an Object, as well. This implies that every recursively superior node of an Object is an Object. + +### III.6 References + +The existence of a subordinate Object x of some Object y may be made dependent on the existence of another Object z. This other Object z is called a Referenced object of the Object y. The Object x providing the reference can be considered a Role of the Referenced object z. The Object x can be considered a Reference object, or just a reference, of its superior Object y. + +Often references are made two-way, such that Object z has a subordinate Object u, which refers back to Object y. + +### III.7 Attributes + +Subordinate data nodes to Object classes and which are not themselves Object classes are Attribute group classes or Attribute classes. + +An Attribute group class is subordinate to an Object class or another Attribute group class. An Attribute class is subordinate to an Object class or an Attribute group class. + +All instantiated data of an Attribute group class are themselves Attribute groups. All instantiated data of an Attribute class are themselves Attributes. If their prescriptive role is not considered, Attribute group classes may be considered being Attribute groups, and Attribute classes may be considered being Attributes. + +Attribute groups are used to collect Attributes that appear together. + +Some of the Attribute groups and/or Attributes of an Object can be defined to be Identifier attributes. An Identifier uniquely identifies the Object within the scope of its superior Object. + +Each of the alternative Identifiers of the Object together with the Identifiers of the recursively superior Objects uniquely identifies the Object uniquely within the Population. An Object may or may not have an Identifier. + +### III.8 Values + +The data nodes which are subordinate to an Attribute class are Value classes. All instantiated data of Value classes are Values. If their prescriptive role is not considered, Value classes may be considered being Values. The notion of Value types is not considered in this text, but the Schema-Population references indicate how this can be provided. A Value may have recursively subordinate nodes, which provide the syntax of the Value. + +Some Attributes may be Single valued, others may be Multi-valued. + +### III.9 Functions + +Function classes may be subordinate to any node of the data tree. All instantiated nodes of a Function class are Functions. If their prescriptive role is not considered, Function classes may be considered being Functions. + +Functions express constraints and derivations. Each Function takes one or several Inputs and provides one Output. The Function provides references to its Inputs and Output. + +A Function cannot remember states from one invocation to the next. Functions may provide recursion. + +Cardinality is a special case of a Function. Cardinality can be stated for each node in the data tree. The Cardinality for a class node states the minimum and maximum number of instances of the class relative to the superior instance node in the data tree. If no Cardinality is stated, then any number of instances is permitted. + +### III.10 Schema-Population references + +A Schema is a data node containing subordinate nodes that prescribe the form and behaviour of data subordinate to the Population node. S is a Role of the Schema, and P is a Role of the Population. S and P are used to express schema-population references between two nodes, as no node is a Schema or Population in an absolute sense. Hence, S and P are reserved words, but Schema, Population and Class are not. + +Any node y in the data tree may contain one or more particular nodes S, which each refers to another data node z. The recursively subordinate nodes of the other node z are considered to contain the classes of the Population node y. + +The node *z* may contain one or more subordinate particular nodes *P*, each of which refers back to the node *y*. The recursively subordinate nodes of the node *y* are considered to contain the instances of the Population node *y* relative to the Schema node *z*. + +Each instance in a Population is an instance of exactly one class in a Schema of that Population, and each class may have several instances in each of the Populations of its Schema. + +The mapping from instances to classes is homomorphic, meaning that the mapping is many-to-one to classes in one particular Schema. For every instance there is exactly one corresponding class in a particular Schema. If two instances are connected in a particular way – by subordination or references – the corresponding classes are connected in the same way. + +Schema references may be recursive. This means that a Schema may contain nodes that have S references to other nodes within or outside the scope of the Schema. Also, an S reference can be made to a superior node, implying that the instances may make up a tree of many levels. + +Note that some classes may have no instances in some Populations of their Schemata. + +Note that since a Population may have several Schemata, the class of a particular instance may be found in any of its recursively referenced Schemata. + +### III.11 Denotations + +A data node is a term that may denote a phenomenon. The phenomena are considered to be inside some observer and hence be data themselves. An observer may be an individual or a collective of individuals. + +Mappings between terms and their phenomena are stated by using source mappings, O. Synonymity mappings, Y, provide the reverse mappings from phenomena to terms. + +The source mapping is stated by an O reference from a node *y* to a node *z*. The reference back from *z* to *y* is made by a Y reference. + +The denotation mapping is isomorphic, meaning that it is one-to-one, and if two phenomena are connected in a particular way – by subordination or references – the corresponding terms are connected in the same way. + +However, we accept that some data may not denote any phenomenon, and some phenomena may not have any notation. Therefore, this mapping is partial. For example, while a Value may denote a phenomenon, the "syntactical sugar" of the Value may denote no phenomenon. + +Most often, denotation references are not stated; therefore, most data denote/model nothing in a formal way. Also, many data nodes are introduced to provide overview of other data nodes, and it may not be convenient to consider each node to denote something. The object class Site relationship (between Cross-coupling sites) may provide such an example; it provides both overview of other data and an identification scheme of other data, and it may denote no concrete phenomenon in the observed universe. This lack of denotation does not preclude that study of the observed universe is essential to the design of data for managing phenomena within this universe. But study of the management itself is also needed to provide an efficient design of data. + +### III.12 Documentation + +The documentation of an application area shall contain: + +- Application area – textual definition and delimitation; +- Application Schema Graph – using the graphical notation; +- Textual Documentation – using the textual notation; +- Remarks – on needs for further study, etc. + +### III.13 Graphical notation + +![Figure III.1/M.1401 – Subset of graphical notation. The diagram shows four examples of graphical notation: 1. A rectangle labeled 'Country' with a double line at the bottom. 2. A rectangle labeled 'Country' containing a rectangle labeled 'Operator' via a line with a reversed arrowhead. 3. Two rectangles, 'Cross-coupling site' and 'Geographical area', connected by a double-headed arrow. 4. A rectangle labeled 'Schema' connected to a rectangle labeled 'Population' by a dashed line with an arrowhead pointing to 'Schema' and labeled 'S'.](5d3455c6c2a37cb3aff761fedeb8644e_img.jpg) + +Objects are depicted by a rectangle containing the object class label adjusted to the left and followed by a dividing line beneath the label. + +Containment is depicted with a line having a reversed arrowhead by the subordinate data. + +References are shown by arrows pointing at the referenced data; references may be one-way or two-way. + +Schema references are supported by dashed lines and the role label S. + +M.1401(07-06)\_FIII.1 + +Figure III.1/M.1401 – Subset of graphical notation. The diagram shows four examples of graphical notation: 1. A rectangle labeled 'Country' with a double line at the bottom. 2. A rectangle labeled 'Country' containing a rectangle labeled 'Operator' via a line with a reversed arrowhead. 3. Two rectangles, 'Cross-coupling site' and 'Geographical area', connected by a double-headed arrow. 4. A rectangle labeled 'Schema' connected to a rectangle labeled 'Population' by a dashed line with an arrowhead pointing to 'Schema' and labeled 'S'. + +**Figure III.1/M.1401 – Subset of graphical notation** + +### III.14 Textual notation + +##### Country + +Natural language texts are indented. + +- Name + +Levels of the data tree are shown by indentations. + +- Geographical area + +Object classes are underlined. + +- ▪ Name + +Attributes and other data have no underlining. + +- ▪ *Site* + +References are written with blue fonts and italics; the underlining indicates that the reference is an Object; the text tells how navigation is made to the referenced Object and indicates cardinalities. + +- Operator + +**Figure III.2/M.1401 – Subset of textual notation** + +## Appendix IV + +### Example transit network registration + +### IV.1 Example + +The end-to-end trail in Figure IV.1 is routed via three Network Operators/Service Providers. + +![Figure IV.1/M.1401 – Transit network diagram showing three Network Operators/Service Providers (NO/SP 1, NO/SP 2, NO/SP 3) connected in series. Each NO/SP contains two junction boxes. The trail starts at point A in NO/SP 1 and ends at point B in NO/SP 3. The connections between NO/SP 1 and NO/SP 2, and between NO/SP 2 and NO/SP 3, are labeled 'Transit network connection'. The overall connection from A to B is labeled 'End-to-end service'. The diagram is labeled M.1401(07-06)_FIV.1.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +Figure IV.1/M.1401 – Transit network diagram showing three Network Operators/Service Providers (NO/SP 1, NO/SP 2, NO/SP 3) connected in series. Each NO/SP contains two junction boxes. The trail starts at point A in NO/SP 1 and ends at point B in NO/SP 3. The connections between NO/SP 1 and NO/SP 2, and between NO/SP 2 and NO/SP 3, are labeled 'Transit network connection'. The overall connection from A to B is labeled 'End-to-end service'. The diagram is labeled M.1401(07-06)\_FIV.1. + +Figure IV.1/M.1401 – Transit network + +### IV.2 Representation + +The network in Figure IV.1 may be represented as depicted in Figure IV.2. + +![Figure IV.2/M.1401 – Population diagram showing a hierarchical representation of the network. The diagram is divided into seven levels: Site relationship, Trail, Trail section, Trail, Site relationship, Cross-coupling site, Operator, and Country. The top level shows a single Site relationship box. Below it, a Trail box is connected to the Site relationship. The Trail section level contains five boxes, each connected to the Trail box above. The Trail level contains five shaded boxes, each connected to a Trail section box. The Site relationship level contains five boxes, each connected to a Trail box. The Cross-coupling site level contains five boxes, each connected to a Site relationship box. The Operator level contains three boxes, each connected to a Cross-coupling site box. The bottom level shows Country boxes connected to Operator boxes. The diagram is labeled M.1401(07-06)_FIV.2.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +Figure IV.2/M.1401 – Population diagram showing a hierarchical representation of the network. The diagram is divided into seven levels: Site relationship, Trail, Trail section, Trail, Site relationship, Cross-coupling site, Operator, and Country. The top level shows a single Site relationship box. Below it, a Trail box is connected to the Site relationship. The Trail section level contains five boxes, each connected to the Trail box above. The Trail level contains five shaded boxes, each connected to a Trail section box. The Site relationship level contains five boxes, each connected to a Trail box. The Cross-coupling site level contains five boxes, each connected to a Site relationship box. The Operator level contains three boxes, each connected to a Cross-coupling site box. The bottom level shows Country boxes connected to Operator boxes. The diagram is labeled M.1401(07-06)\_FIV.2. + +Figure IV.2/M.1401 – Population diagram + +In this case, one Trail is routed on five other Trails. The Trails are indicated by shaded boxes. + +Note that the end-to-end Trail has only a Site relationship to the main transmission centres (i.e., Cross-coupling node) of the terminating Operators, and not to the terminating junction boxes (i.e., Cross-coupling node) of these Operators. + +Each Operator may only know parts of the routing. The routing known to the leftmost Operator is depicted in Figure IV.3. + +![Figure IV.3/M.1401 – View of data. A hierarchical diagram showing the relationship between Site relationships, Trails, Trail sections, Cross-coupling sites, Operators, and Countries. The diagram is a tree structure with nodes represented by rectangles. Some nodes are shaded grey. Arrows indicate relationships between nodes. The leftmost Operator's view is highlighted by a shaded path.](c76da2d73c064464051d1583fd80bb6b_img.jpg) + +The diagram illustrates a hierarchical data structure. At the top level is 'Site relationship'. Below it is 'Trail'. Below that is 'Trail section'. Below that is 'Trail'. Below that is 'Site relationship'. Below that is 'Cross-coupling site'. Below that is 'Operator'. Below that is 'Country'. The diagram shows a tree structure with nodes represented by rectangles. Some nodes are shaded grey. Arrows indicate relationships between nodes. The leftmost Operator's view is highlighted by a shaded path. + +Figure IV.3/M.1401 – View of data. A hierarchical diagram showing the relationship between Site relationships, Trails, Trail sections, Cross-coupling sites, Operators, and Countries. The diagram is a tree structure with nodes represented by rectangles. Some nodes are shaded grey. Arrows indicate relationships between nodes. The leftmost Operator's view is highlighted by a shaded path. + +Figure IV.3/M.1401 – View of data + +The identifiers of Figure IV.2 are shown in alphanumerical notation in Figure IV.4. Non-identifier attributes and references are not shown. + +First, the Countries with their Operators and respective Cross-coupling sites are listed. Then come the Site relationships with their example Trails. + +Note that the contents of the A-end and B-end Sites are only indicated informally in this Recommendation. In the example, their Identifiers with Geographical area and Site detail are copied in. + +The routing of the end-to-end Trail is indicated by Trail sections only, and not by references to their respective resources, which happen to be Trails, as well. However, these Trails are listed separately, in the appropriate sequence, under their Site relationships. + +Figure IV.4/M.1401 – Data values in Example Population (start) + +##### Country + +- Name + - ITALY** +- Code + - ITA** +- Operator + - ICC + - WIND** + - Cross-coupling site + - Identifier + - Geographical area + - ROMA** + - Site detail + - TAW-1** + - Cross-coupling site + - Identifier + - Geographical area + - ROMA** + - Site detail + - TAW** + +- Operator +- ▪ ICC + - **TI** + - ▪ Cross-coupling site + - ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - **MILANO** + - ▪ ▪ ▪ Site detail + - **MIL** + - ▪ Cross-coupling site + - ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - **MILANO** + - ▪ ▪ ▪ Site detail + - **MIL-1** +- Country +- Name + - **FRANCE** +- Code + - **FRA** +- Operator +- ▪ ICC + - **FRTE** + - ▪ Cross-coupling site + - ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - **REIMS** + - ▪ ▪ ▪ Site detail + - **RE1** + - ▪ Cross-coupling site + - ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - **REIMS** + - ▪ ▪ ▪ Site detail + - **REI-1** +- Site relationship +- Identifier +- ▪ A-end +- ▪ ▪ Country Code + - **FRA** +- ▪ ▪ ICC + - **FRTE** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area + - **REIMS** +- ▪ ▪ ▪ ▪ Site detail + - **REI** +- ▪ B-end +- ▪ ▪ Country Code + - **ITA** +- ▪ ▪ ICC + - **TI** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area + - **ROMA** +- ▪ ▪ ▪ ▪ Site detail + - **TAW** +- Trail +- ▪ Identifier + - **DC1** +- ▪ Trail section +- ▪ ▪ Identifier + - **1** + - **2** + - **3** + - **4** + - **5** + +##### Site relationship + +- Identifier +- ▪ A-end +- ▪ ▪ Country Code +**ITA** +- ▪ ▪ ICC +**WIND** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area +**ROMA** +- ▪ ▪ ▪ ▪ Site detail +**TAW** +- ▪ B-end +- ▪ ▪ Country Code +**ITA** +- ▪ ▪ ICC +**WIND** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area +**ROMA** +- ▪ ▪ ▪ ▪ Site detail +**TAW-1** +- Trail +- ▪ Identifier +**DC1** + +##### Site relationship + +- Identifier +- ▪ A-end +- ▪ ▪ Country Code +**ITA** +- ▪ ▪ ICC +**TI** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area +**MILANO** +- ▪ ▪ ▪ ▪ Site detail +**MIL** +- ▪ B-end +- ▪ ▪ Country Code +**ITA** +- ▪ ▪ ICC +**WIND** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area +**ROMA** +- ▪ ▪ ▪ ▪ Site detail +**TAW** +- Trail +- ▪ Identifier +**DC1** + +##### Site relationship + +- Identifier +- ▪ A-end +- ▪ ▪ Country Code +**ITA** +- ▪ ▪ ICC +**TI** +- ▪ ▪ Site +- ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ Geographical area +**MILANO** +- ▪ ▪ ▪ ▪ Site detail +**MIL** +- ▪ B-end +- ▪ ▪ Country Code +**ITA** + +- ▪ ▪ ICC + - TI** +- ▪ ▪ Site + - ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - MILANO** + - ▪ ▪ ▪ ▪ Site detail + - MIL-1** +- Trail + - ▪ Identifier + - DC1** +- Site relationship + - Identifier + - ▪ A-end + - ▪ ▪ Country Code + - FRA** + - ▪ ▪ ICC + - FRTE** + - ▪ ▪ Site + - ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - REIMS** + - ▪ ▪ ▪ ▪ Site detail + - REI** + - ▪ B-end + - ▪ ▪ Country Code + - ITA** + - ▪ ▪ ICC + - TI** + - ▪ ▪ Site + - ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - MILANO** + - ▪ ▪ ▪ ▪ Site detail + - MIL-1** +- Trail + - ▪ Identifier + - DC1** +- Site relationship + - Identifier + - ▪ A-end + - ▪ ▪ Country Code + - FRA** + - ▪ ▪ ICC + - FRTE** + - ▪ ▪ Site + - ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - REIMS** + - ▪ ▪ ▪ ▪ Site detail + - REI** + - ▪ B-end + - ▪ ▪ Country Code + - FRA** + - ▪ ▪ ICC + - FRTE** + - ▪ ▪ Site + - ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ Geographical area + - REIMS** + - ▪ ▪ ▪ ▪ Site detail + - REI-1** +- Trail + - ▪ Identifier + - DC1** + +**Figure IV.4/M.1401 – Data values in Example Population *(end)*** + +30 **ITU-T Rec. M.1401 (07/2006)** + +If France Telecom were operating in Italy, this would require a separate ICC, which may or may not be identical to the identifier used within France, but different from other ICCs in Italy. + +Note that the information within the Site relationship Identifiers are given in alphabetic sequence. In this example all Trails have the local Identifier DC1 within their respective Site relationship. The serial number 1 depends on what other Trails have been established within this Site relationship. The permissible Function codes, like DC, will be prescribed in the data type of the data class Trail Identifier; data types are not yet covered by this Recommendation. + +# BIBLIOGRAPHY + +Attempts have been made to map M.1401 to other Recommendations and standards. Some compliance has been reached; however, no guarantee can be given as to full compliance between these standards. + +Therefore, the following Recommendations and standards provide additional and not normative information to the provisions of this Recommendation. + +- ITU-T Recommendation G.853.1 (1999), *Common elements of the information viewpoint for the management of a transport network*. +- ITU-T Recommendation M.3100 (2005), *Generic network information model*. +- ANSI T1.251-2001 (Version 2), *Identification of Telecommunications Service Provider Codes for the North American Telecommunications System*.\* +- ATIS 0325300-2005, *Identification of Location Entities for Information Exchange*. +- ATIS 0300007-2005, *Identification of Physical Network Resources*. +- ETSI TS 102 209 V1.2.1 (2004-02), *Telecommunications and Internet converged Services and Protocols for Advancing Networks (TISPAN); Telecommunication Equipment Identification*. +- ETSI TS 102 359 V1.2.1 (2005-09), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Equipment Information in the Management Information Base (MIB)*. + +--- + +\* T1 standards are maintained since November 2003 by ATIS. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1402-201205-I_PDF-E/raw.md b/marked/M/T-REC-M.1402-201205-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d3c3dc4020a8d533820b067c28bc7d743a3086b8 --- /dev/null +++ b/marked/M/T-REC-M.1402-201205-I_PDF-E/raw.md @@ -0,0 +1,1276 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1402** + +(05/2012) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Designations and information exchange + +--- + +**Formalization of data for service management** + +Recommendation ITU-T M.1402 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. The letters "ITU" are written in blue below the globe. To the right of the logo, the text "International Telecommunication Union" is written in blue. + +ITU logo + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T M.1402 + +## Formalization of data for service management + +## Summary + +Recommendation ITU-T M.1402 contains definitions of data for service management. The data are defined in the way they are presented to the end users at their terminals, and conceptual or internal data structures are not defined. Therefore, this Recommendation defines an external terminology schema for the given application domain. + +This Recommendation focuses on defining data for products, customers, accounts, contracts, deals, addresses, prices, various segments and relationships between all these. Some attributes that are essential for identifying objects and associations between them are defined, as well. + +Order data and detailed mappings to network elements are not covered. Also, billing, marketing, sales, retailer, distributor, number management, device management, location management, logistics and finance are not covered. Finally, alarms, trouble tickets, call records and other call centre information are missing. + +As the data defined in this Recommendation are designed for human usage, they are independent of the functions in which they are used. Hence, the data may be applied in any functions, e.g., in customer requests, call centres, billing, service platforms, etc. + +This Recommendation uses the notation and conventions found in Recommendation ITU-T M.1401, "Formalization of interconnection designations among operators' telecommunication networks". + +Appendix I explains the creation of product and customer service databases. + +Appendix II explains the creation of interfaces to service platforms. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.1402 | 2007-08-06 | 4 | +| 2.0 | ITU-T M.1402 | 2012-05-14 | 2 | + +## Keywords + +CRM, customer, data, definitions, product. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2012 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 External terminology schema ..... | 4 | +| Appendix I – Product and customer service databases ..... | 24 | +| Appendix II – Interface to a service platform ..... | 27 | + +## Introduction + +This Recommendation defines data as they are presented to the end users at their terminals. The data are defined in an external terminology schema that provides the glossary and grammar of all permissible data to the end user. + +The external terminology schema defines elementary sentence types only, which prescribe elementary sentences like "Contract 1 contains Product instance 12345678". The schema does not prescribe compound sentences, like "Contract 1 contains Product instance 12345678, which has Installation address Storgata 6", as is required at the end-user interfaces. Note that the relative pronoun "which" is not used in external terminology schemata, but may be used in the "Contents schema" for each screen or report. + +The proposed external terminology schema is intended for harmonization of data across all sub-domains within service management and all channels to this application domain. + +The external terminology schema focuses on end users' need for harmonized data and not on needs for storage or communication formats. + +## Recommendation ITU-T M.1402 + +## Formalization of data for service management + +## 1 Scope + +Service management is the universe of discourse (UoD) of this Recommendation. This UoD comprises products, customers, accounts, contracts, deals, addresses, prices and various segments and relationships between these. + +The focus of this Recommendation is on end-user terminology as defined in an external terminology schema and which puts requirements on other schemata and implementations. As such, this Recommendation focuses on the definition of object and reference classes, and provides most identifiers and name bindings (i.e., subordinate object indicated by reversed arrowheads) for these. It also provides some attribute groups and attributes which are essential to define the data structure. Other attributes, e.g., to indicate entity history, are not covered. Also data structures for orders are not covered. + +The data definitions are meant to cover the needs for customer inquiries and customer sales about the customer, their services and relations to the operator, but the definitions do not provide background information for sales people and account managers who provide offers and contracts to large customers. These may need processed information about turnover and plans for a customer/cooperation. The data structure may apply for these needs as well, but additional attributes are required. The data structure lacks the means to provide overviews for market analyses. Also, a network view for answering customer inquiries and service delivery is missing. + +The data definitions cover product types as they are defined in product catalogues and cover product instances in customer databases. A subset of these product types and product instances may be implemented as telecommunication services, e.g., in a service platform. The broader context of product catalogues and customer databases is essential for definition and harmonization of service types and instances. The object class service is not defined in this Recommendation. However, the data structure defines the scope of service management. + +It should be noted that product types within product catalogues are in this Recommendation defined as classes of product instances within contracts. This means that the product types may contain data that are not needed in a pure enterprise product catalogue, but these data are needed for the product catalogue to serve the role of being a schema. One contract instance may have several product catalogue instances as its schemata. One product instance in a contract is, however, only generated from one product type within a product catalogue. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.1401] Recommendation ITU-T M.1401 (2006), *Formalization of interconnection designations among operators' telecommunication networks*. + +## **3 Terms and Definitions** + +### **3.1 Terms defined elsewhere** + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 Attribute [ITU-T M.1401]** +- 3.1.2 Attribute class [ITU-T M.1401]** +- 3.1.3 Attribute group [ITU-T M.1401]** +- 3.1.4 Identifier attribute [ITU-T M.1401]** +- 3.1.5 Object [ITU-T M.1401]** +- 3.1.6 Object class [ITU-T M.1401]** +- 3.1.7 Population [ITU-T M.1401]** +- 3.1.8 Reference [ITU-T M.1401]** +- 3.1.9 Reference class [ITU-T M.1401]** +- 3.1.10 Schema [ITU-T M.1401]** +- 3.1.11 Subordinate object [ITU-T M.1401]** +- 3.1.12 Subordinate object class [ITU-T M.1401]** + +### **3.2 Terms defined in this Recommendation** + +None. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +- CC Country Code +- CRM Customer Relationship Management +- ICC ITU Carrier Code +- KID Customer Identifier +- LID Local Identifier +- SMS Short Message Service +- UoD Universe of Discourse + +## **5 Conventions** + +This Recommendation uses 5 mm bulleted indentations to indicate subordinate data. + +Textual definitions and explanations are provided in paragraphs that are indented 5 more mm to the right. + +Object classes are underlined; attribute group and attribute classes are not. + +References to other object classes are written in blue fonts, in italics and underlined. + +The figures use rectangles to indicate object classes. + +Lines with reversed arrowheads indicate subordinate object class. + +Two-way arrows indicate references between object classes. + +A dashed one-way arrow supported with an S at the arrowhead indicates a schema reference from a population. Each element subordinate to a schema may be instantiated to several elements subordinate to the population. And, the schema reference may itself be instantiated, like any other reference. + +A dashed one-way arrow supported with a colon (:) at the arrowhead indicates a data type. This is analogous to super-class references in object-oriented languages, where properties of the subordinate class are inherited from the data type. + +A reference one level up in the data tree is indicated by a ('). + +A recursive use of any number of dashes is indicated by (&). + +An existential condition is stated by (<>). A data node on the left-hand side of the condition can only exist if the node referenced on the right-hand side exists. + +A reference to a data node without referencing its label is stated by a parenthesis ( ), e.g., (Operator) refers to a superior node of Operator, i.e., the Corporation in the graph. However, by not referring to the Corporation, we can reference any node corresponding to the Corporation, i.e., one of its Populations. + +Red (combined dashed and dotted) lines indicate derived references. + +## 6 External terminology schema + +![External terminology schema graph for service management. The diagram shows a complex web of classes and their relationships. Key classes include Employee, Corporation, Country, Market, Operator, Customer, Structure, Type, Address, Role, Contract, Catalogue, Channel, Account, Membership, Deal, Product, Price, Price component, Price rule, Event, Term, Quality level, Quality parameter, Product characteristics, Association, Installation, and Use. Relationships are shown as solid lines with arrows, and some are dashed red lines with 'S' labels indicating schema references. A 'Sales channel' label is also present near the Channel class.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +The diagram illustrates the external terminology schema graph for service management. It features a variety of classes represented by rectangular boxes, interconnected by lines representing relationships. + + +- Employee** is connected to **Corporation**. +- Corporation** is connected to **Country** and **Market**. +- Country** is connected to **Operator** and **Customer**. +- Market** is connected to **Operator**. +- Operator** is connected to **Contract**, **Catalogue**, and **Channel**. +- Customer** is connected to **Structure**, **Role**, and **Contract**. +- Structure** and **Type** are connected to **Address**. +- Address** is connected to another **Type** class, which is in turn connected to **Account**. +- Account** is connected to **Membership** and **Deal**. +- Membership** is connected to **Deal**. +- Deal** is connected to **Product**. +- Product** is connected to **Price**, **Event**, **Quality level**, **Association**, **Installation**, and **Use**. +- Price** is connected to **Price component**. +- Price component** is connected to **Price rule**. +- Event** is connected to **Term**. +- Quality level** is connected to **Quality parameter**. +- Quality parameter** is connected to **Product characteristics**. +- Association**, **Installation**, and **Use** are all connected to **Product**. +- Catalogue** is connected to **Product** and **Channel**. +- Channel** is connected to **Product** and has a label 'Sales channel'. +- Dashed red lines with 'S' labels indicate schema references from **Contract**, **Product**, and **Deal** back to **Customer**, **Structure**, and **Type**. + +External terminology schema graph for service management. The diagram shows a complex web of classes and their relationships. Key classes include Employee, Corporation, Country, Market, Operator, Customer, Structure, Type, Address, Role, Contract, Catalogue, Channel, Account, Membership, Deal, Product, Price, Price component, Price rule, Event, Term, Quality level, Quality parameter, Product characteristics, Association, Installation, and Use. Relationships are shown as solid lines with arrows, and some are dashed red lines with 'S' labels indicating schema references. A 'Sales channel' label is also present near the Channel class. + +M.1402(12)\_F01 + +**Figure 1 – External terminology schema graph for service management** + +### Corporation + +This Recommendation defines a schema of a system of a Corporation. The schema is called Corporation. + +The schema contains data classes of the system. Each class acts as an original/prototype that can be copied into (several) instances subordinate to each of the populations of the schema. The S reference from a population to another data item makes the other item act as a schema relative to the population item. + +Overlapping subsets of a schema may be implemented as separate systems. + +#### - Country + +A Country may be an independent state or a state within a union. + +Operators are identified with a unique International Carrier Code within a Country. This means that a corporation must be defined with (minimum) one Operator within each Country. + +#### - CC + +Country Code is a three-character value according to ISO 3166-1. + +#### - ▪ Name + +The Country Name identifies a Country, dependency, or other area of particular geopolitical interest. Countries are assigned a globally unique Name in ISO 3166-1. + +#### - ▪ Address + +An Address identifies a geographical place. The identifier is independent from application domain, vendor or market segment of its use. + +The Address notion does not cover bank accounts and the like. However, the post box notion is covered by the identifiers. Also, postal addresses given by place and postal code/post area are covered by the identifiers. + +In this Recommendation, Address is treated as one object class only; this requires further study, e.g., separate object classes for streets, local areas, etc. + +#### - ▪ ▪ Installation + +An Address may have one or more subordinate Installations, which each defines a role of an Installation in this Address. + +#### - ▪ ▪ Type + +An Address may have one or more subordinate Types, which each indicates a role of a Type of an Account. + +#### - ▪ ▪ Type + +An Address may have one or more subordinate Types, which indicates a role of a Type of a Customer. + +#### - ▪ Customer + +Customer indicates a legal person whom the Operator relates to. This legal person may have one or more roles to Accounts, Contracts, Product instances, Deals or Employees in or from the Operator. The Role notions allow the Operator to register the Customer relative to these legal notions and not to register the Customer's internal organization structure, which may change without the Operator's knowledge. + +A Customer may be a private person or a legal organization. The Customer's internal organization may indicate family, cohabitant and friendship relations, or indicate organization of geographically distributed companies and collaborative relations. The Operator may not want or be able to record this internal organization of the Customer. + +#### - ▪ ▪ KID + +Each Customer of the corporation's Operators shall be assigned a customer identifier (KID) that is unique within the corporation in a Country and is not specific for each business unit/Operator. It shall be possible to undertake credit control of the Customer based on the customer identifier (KID). + +#### - ▪ ▪ Name + +Each Customer shall have a Name within a Country. Several Customers may have identical Names. Customers may be distinguished by Address or other information. + +#### - ▪ ▪ Business role + +This attribute may have the following value set: + +A – Employee in the corporation + +F – Retailer of the corporation + +D – Distributor of the corporation + +L – Operator in the corporation + +K – Competitor of the corporation + +Sources for this information are not identified and responsibility for updating is not assigned in this Recommendation. + +#### - ▪ ▪ Customer status + +Customer status is provided by the business register within the Country. + +K – valid customer + +UK – (terminated) bankrupt + +UF – (terminated) wrong registration + +US – (terminated) merged + +UO – (terminated) closed + +UT – (terminated) legal action + +For persons, the following states are used: + +K – customer + +KU – customer emigrated + +KF – customer disappeared + +#### - ▪ ▪ Importance + +This attribute indicates that the Customer is a Very Important Person in his relationships to the corporation. + +V – Very Important Person + +This Recommendation does not prescribe how this attribute will be maintained, but the attribute may become updated if the Customer gets a Role as Very Important Person to an Account or Contract, and be deleted if the Role as Very Important Person is deleted. + +#### - ▪ ▪ Employee + +A Customer may have one or more subordinate Employees that each is a role of an Employee. This way, it is possible to state that the "customer" is employed by some Operator of some Product instances. However, only employment in the corporation is registered and not by each Operator. + +Normally, there is a one-to-one correspondence between Customer and Employee, but in some cases there may be several Employee roles per Customer. This relationship shall not be used to register that an Employee has responsibility for a set of Customers. This information is registered by letting the employee Customer have Roles to several Accounts or Contracts. + +#### - ▪ ▪ Membership + +A Customer may have several subordinate Memberships, which each indicates a role of a Membership, which has a subordinate Deal, which is a role of a Deal. + +#### - ▪ ▪ Role + +A Customer may have several subordinate Roles, which each indicates a role of a Contract's subordinate Role. + +#### - ▪ ▪ Role + +A Customer may have several Roles, which each indicates a role of an Account's subordinate Role. + +#### - ▪ ▪ Subordinate structure + +A Customer may have several Subordinate structures, which each indicates a role of a Structure object, used to define the Customer's internal organization structure. + +For a corporate Customer, the Subordinate structure's Subordinate customer indicates an organization unit within the corporation. + +For a private person Customer, the Subordinate structure's Subordinate customer indicates a family member, etc. + +Sometimes the Subordinate structure is not explicitly registered, but is derived from geographic addresses and relationships to Accounts, Contracts or Product instances, e.g.: + +- When looking upon a Customer, list all subordinate Accounts and Contracts which have usage address at a given address. +- The terminal user assumes that the Customer with the Role Type Owner has a subordinate unit at the given address. + +#### - ▪ ▪ Superior structure + +A Customer may have a subordinate Superior structure, which indicates a role of a Structure indicating the Customer's organizational association. The Customer's subordinate Superior structure's Superior customer indicates this relationship. + +#### - ▪ ▪ Type + +A Customer may have several subordinate Types, which each indicates a role to a Type (of Address), which has a subordinate Address, which is a role of an Address. + +#### - ▪ ▪ Use + +A Customer may have several subordinate Uses, which each indicates a role of a Use, which has a subordinate Product, which indicates a role of a Product instance. + +### - ▪ Operator + +An Operator – i.e., an instance of the data class Operator – defines a business unit for sales and delivery of telecommunication services. + +An Operator must always be defined locally to a Country. + +The definition of Operators may reflect the organization structure of the corporation. + +For more information on Operator, see [ITU-T M.1401]. + +### - ▪ ▪ ICC + +An Operator is assigned an ITU Carrier Code by the Administration/Regulator in each Country. + +For more information on Operator, see [ITU-T M.1401]. + +### - ▪ ▪ LID + +Every Operator in the corporation may be assigned a unique Local identifier (LID) within the corporation. + +### - ▪ ▪ Billing system + +This attribute provides the identification of default Billing system for all Accounts under this Operator. + +#### - ▪ ▪ Rating system + +This attribute provides the identification of default Rating system for all Contracts under this Operator. + +#### - ▪ ▪ Account + +An Account provides information on agreed and delivered payments from a Customer. + +#### - ▪ ▪ ▪ Account number + +The Account number is a unique identifier of an Account within an Operator. + +### ▪ ▪ ▪ ▪ Payment form + +E – prepaid + +O – postpaid + +#### ▪ ▪ ▪ ▪ Role + +An Account may have several subordinate Roles, which each indicates a relationship to a Customer. + +#### ▪ ▪ ▪ ▪ ▪ Category + +The Category indicates which role a Customer plays to an Account. The Category is an attribute group that consists of attributes. + +If the value of the Type attribute is updated by the terminal user, then the value of the Update attribute is set to manual (M). If the role is created by the system itself, then the value of the Update attribute is set to derived (B). Only roles that are updated manually need to be stored. + +### ▪ ▪ ▪ ▪ ▪ Type + +A Role's subordinate Type may have one of the following values: + +E – owner + +B – payer + +F – billing address + +Y – authorized + +K – contact + +V – very important person + +U – user + +A – provider agent + +R – responsible employee + +An Account may only have one Role of Type owner (E), payer (B), user (U) or provider agent (A), but may have several Roles of Type contact (K) and very important person (V). + +If some Roles are not explicitly provided for an Account, and the Account has one Contract only, then the Roles of the Account are copied from the Roles of the Contract. + +If owner (E) is provided, and payer (B) is missing, then the payer is equal to the owner. + +If owner (E) is provided, and billing address (F) is missing, then the billing address is equal to the owner. + +If owner (E) is provided, and user (U) is missing, the user is equal to the owner. + +If payer (B) is provided, and owner (E) is missing, the owner is equal to payer. + +If payer (B) is provided, and user (U) is missing, the user is equal to payer. + +If user (U) is provided, and owner (E) is missing, the owner is equal to user. + +If user (U) is provided, and payer (B) is missing, the payer is equal to user. + +If some Roles are not provided for a related Contract, then the Roles of the Contract are equal to those of the Account. + +Derived Types may be indicated by a separate colour at the user interface, or they may be hidden. + +### - ▪ ▪ ▪ ▪ ▪ Update + +The Type of a Role may be updated + +M – manually + +B – automatic + +### - ▪ ▪ ▪ ▪ Customer + +A Role must have a subordinate Customer that is a role of a Customer. + +#### - ▪ ▪ ▪ ▪ Address type + +An Account may have a subordinate Address type, which indicates a role to a Type of an Address. + +### - ▪ ▪ ▪ ▪ Contract + +An Account may have a subordinate Contract, which is a role of a Contract, which is billed by this Account. + +Note that the Account may be owned by an employee and have a reference to the Contract of this employee. The company in which the person is employed may have an Account that refers to the same Contract. The company Account may have references to a Contract of each employee. + +#### - ▪ ▪ ▪ ▪ Deal + +An Account may have a subordinate Deal, which is a role of a Deal, which is billed by this Account. + +This reference is typically established when the Deal is settled between an organization Customer and the Operator. The Deal refers to Price of a Product in a product Catalogue of an Operator. When a member of the organization uses the Deal, the Price is instantiated to a Product instance under a Contract that has a reference to one or more Accounts. One of the Accounts may be the Account that has the reference to the Deal. + +#### - ▪ ▪ ▪ ▪ Subordinate account + +An Account may have several Subordinate accounts, which each indicates a role of another Account. The Subordinate account provides information on parts of the Superior account. The account structure indicates how the Customer wants his payment information to be structured and split. Figures from the current Account may then be calculated to all Superior accounts. Therefore, the account structure may have several top nodes, but one Account cannot be contained (recursively) via different paths within the same node. An attribute indicates if the Account shall result in a bill or not. One Customer may receive several bills on the same Product instance and the same period, e.g., partly prepaid and postpaid. + +#### - ▪ ▪ ▪ ▪ Superior account + +An Account may have a Superior account, which indicates a role of another Account. In this case, the current Account provides information on parts of the Superior account. An Account may have several Superior accounts. Figures from the current Account may then be calculated to all Superior accounts. Therefore, the account structure may have several top nodes, but one Account cannot be contained (recursively) via different paths within the same node. An attribute indicates if the Account shall result in a bill or not. One Customer may receive several bills on the same Product instance and the same period, e.g., partly prepaid and postpaid. + +#### - ▪ ▪ Catalogue + +A Catalogue contains an overview of all Products, i.e., Product types, available from the superior Operator of the Catalogue. Due to needs to manage several versions of offers, an Operator may have several Catalogues. Also, separate Catalogues may be defined for technical products and Product types which are inherited, or by other means are used to construct products for sale. A Product from one Catalogue may be inherited or composed of Products from other Catalogues. + +#### - ▪ ▪ ▪ Identifier + +A Catalogue has a unique identifier within the superior Operator. If there are several versions for a product Catalogue, version information should be contained in the identifier. + +#### - ▪ ▪ ▪ Valid Period + +The period during which the catalogue is applicable. + +#### - ▪ ▪ ▪ Product + +### *Product type* + +A Product type (under a Catalogue) is a type of service with a predefined functionality. + +Note that a Product type is an instance of Product class (under Catalogue). Product types are normally for sale, and these only are visible in the customer channels. Separate Product types may be defined as technical products, which are used to implement products for sale. Also, particular Product types may be defined for inheritance of definitions. See the Association Type I. + +The Product type may be defined as a market product or a technical product. This allows one Operator A to deliver a Product type to another Operator B. The delivered Product type may be a technical product from A that is used to deliver a bundled market product from B, and the market product only is visible to the Customers of B. This way, products may be bundled in several steps. + +Due to the bundling mechanisms indicated above, there is no distinction between Product, service and resource. Products may have service attributes, and Products may have attributes that refer to resources. + +Note that a service may be defined to be a Product that is delivered from a service platform to a user. However, this notion is outside the scope of this Recommendation. See Appendix I. + +As only Products may have Prices, if the parameters of the resources imply different pricing, a separate Product must be defined for each of these parameter values. This means that if the service platform has a parameter for bandwidth and the different bandwidths have different Prices, then a separate Product may be defined for each bandwidth. + +The Product type may be an individual Product type or be bundled as a predefined set of other Product types, see Association Type B. + +A Product type may have a set of permissible additional Product types, see Association Type M, and the Product type may exclude use of other Product types, see Association Type I. + +The topmost node in the Product type hierarchy, by bundling or inheritance, i.e., Association Type B or I, shall itself be an ordinary Product type (for sale), and the hierarchy shall not be used for categorization of Products, shall not indicate organization, deals or other information. + +A Product type may inherit properties or subordinate structures from several other Product types. + +Each Product type will have a Type (identifier) that is unique within the superior Catalogue. + +In addition, a Product type may have a Resource type identifier, provided by the Operator, and which tells that an instance of this Resource type may be replaced by another instance of the same type. + +### *Product instance* + +A Product instance is an instance of exactly one Product type, and there may be several instances of the same type. This is accomplished by the S(chema) reference from Contract to Catalogue. This specifies that: + +- All data classes subordinate to Catalogue are considered to be subordinate to Contract, as well; +- The S(chema) reference itself may be instantiated to refer from a specific Contract instance to one or more specific Catalogue instances; +- The data instances in the tree subordinate to a Contract are instances of the data, i.e., Product types, under the referenced Catalogues. + +A Product instance may be contained in a Product instance bundle, may have additional Product instances and exclude use of others according to the prescriptions in its Product types. + +Note that a Product instance may only be contained in one superior product bundle, while a Product type may be contained in several superior product bundle types. + +The Product instance has an Identifier. This Identifier is made up of a Catalogue, a Type and a Number. The Catalogue attribute indicates from which Catalogue the Product type is taken to generate this Product instance. Also, the Catalogue makes the identifier unique within an Operator. The Number may be a telephone number, circuit number or a similar resource identifier. In addition, the Product instance may have a Resource type attribute. + +Note that generalization of Number to an alphanumeric field is for further study. + +#### ▪ ▪ ▪ ▪ ▪ Identifier + +A Product has a unique identifier within the superior Catalogue or Contract. + +The Type is unique within its Catalogue, while the combination of Catalogue, Type and Number is unique within the Contract. + +#### ▪ ▪ ▪ ▪ ▪ Catalogue + +The Catalogue attribute identifies the Catalogue instance from which the Product instance is generated. The Catalogue attribute is strictly needed only for Product instances. + +#### ▪ ▪ ▪ ▪ ▪ Type + +Each Product type will have a unique Type within its superior Catalogue. + +Each Product instance under a Contract instance will be assigned the Type of the Product type from which it is generated. The Type must be filled in both for Product types and Product instances. + +### ▪ ▪ ▪ ▪ ▪ Number + +Product instances within a Contract instance will have a Number which is unique together with the Catalogue and Type within the Product's superior Contract. + +However, for some Types, e.g., TLF, the Number may be globally unique, such that one may look up a product instance directly, based on the Number only. + +The Number attribute is strictly needed only for product instances. + +- ▪ ▪ ▪ ▪ Name + +A word, term, or phrase by which the Product is known and distinguished from other Products. The Name attribute is applicable for both Product types and Product instances. +- ▪ ▪ ▪ ▪ Description + +An explanation of what the Product is. The Description attribute is applicable for both Product types and Product instances. +- ▪ ▪ ▪ ▪ Technology type + +The technology type of the Product, such as fixed phone, wireless, data communication, etc. This attribute is only applicable for Product types. +- ▪ ▪ ▪ ▪ Customer base type + +The industry or customer base the Product is designed for, such as government, education, finance, family, etc. This attribute is only applicable for Product types. +- ▪ ▪ ▪ ▪ Valid period + +The period during which the Product is applicable. This attribute is applicable for both Product types and Product instances. +- ▪ ▪ ▪ ▪ Status + +The condition in which the Product exists. This attribute is applicable for both Product types and Product instances. However, Product type and Product instance may have different status values. For example, Product type may take such values as planned, obsolete, active, while Product instance may take such values as planned, designed, activated, disconnected. +- ▪ ▪ ▪ ▪ Product characteristic + +Product characteristic specifies characteristic quality or distinctive features of a Product and the values assigned to the characteristics. The characteristic can either take on a discrete value, such as colour, or take on a range of values (for example, sensitivity of 100-240 mV). Product characteristic is applicable for both Product types and Product instances. +- ▪ ▪ ▪ ▪ ▪ Identifier + +The local unique identifier for the Product characteristic within the Product. +- ▪ ▪ ▪ ▪ ▪ Name + +A word, term, or phrase by which the characteristic is known and distinguished from other characteristics. +- ▪ ▪ ▪ ▪ ▪ Description + +A narrative that explains the characteristic. +- ▪ ▪ ▪ ▪ ▪ Value unit + +This indicates the unit that is used by this characteristic. When no unit is used for this characteristic (such as a ratio), this field is filled with "--", indicating "not applicable". This attribute is optional. + +- ▪ ▪ ▪ ▪ ▪ Configurable +A boolean value determines if a characteristic value can be assigned for Product types by the provider or configured for Product instances by the customers. +- ▪ ▪ ▪ ▪ ▪ Value +Values that the characteristic can take on. The value may be a discrete value or a value range. This attribute is optional. +- ▪ ▪ ▪ ▪ ▪ Valid period +The period of time for which a characteristic and its value are applicable. +- ▪ ▪ ▪ ▪ ▪ Sales channel +A Product's subordinate Sales channel refers to a Channel subordinate to an Operator. +A Product may have a variety of Sales channels, such as online purchase, SMS purchase, hotline purchase, business hall purchase, and so on. Alternative Sales channels may exist for a Product type, while a Product instance is sold through a particular Sales channel. +- ▪ ▪ ▪ ▪ ▪ Term +Term specifies a condition under which the Product is made available to customers. The Term includes financial terms, such as acceptable methods of payment, shipment terms and service terms. Term is only applicable for Product types. +- ▪ ▪ ▪ ▪ ▪ Identifier +The local unique identifier of the Term within the Product. +- ▪ ▪ ▪ ▪ ▪ Type +The type of the Term, such as financial terms, shipment terms, service terms, and so on. +- ▪ ▪ ▪ ▪ ▪ Term information +The detailed information of the specific Term. +- ▪ ▪ ▪ ▪ ▪ Quality level +The information about different quality level options to be chosen or agreed for the Product type, or a quality level that is chosen by a customer for a particular Product instance. +- ▪ ▪ ▪ ▪ ▪ Service class +This attribute is used to identify the Quality level of the Product, such as "platinum", "gold", "silver" and so on. The Service class is unique within the Product. +- ▪ ▪ ▪ ▪ ▪ Description +Explanation of the specific Service class. +- ▪ ▪ ▪ ▪ ▪ Quality parameter +Quality parameter specifies the detailed information of each quality parameter of the Product. + +- ▪ ▪ ▪ ▪ ▪ ▪ Identifier +The unique identifier assigned for the parameter for reference and identification purpose. The Identifier is unique within the Quality level. +- ▪ ▪ ▪ ▪ ▪ ▪ Name +This attribute is used to specify the full name or the abbreviation of the specified Quality parameter. +- ▪ ▪ ▪ ▪ ▪ ▪ Value unit +This indicates the unit that is used by this Quality parameter. When no unit is used for this Quality parameter (such as a ratio), this field is filled with "--", indicating "not applicable". +- ▪ ▪ ▪ ▪ ▪ ▪ Value +Values that the Quality parameter can take, indicating the possible value range within which the Quality parameter should be to comply to the service level. The value may be a discrete value or a value range. +- ▪ ▪ ▪ ▪ ▪ ▪ Description +This attribute explains the meaning of the Quality parameter. +- ▪ ▪ ▪ ▪ ▪ ▪ Parameter area +This attribute indicates which area this Quality parameter is dealing with. For example, the areas could be Network Performance, Traffic or Service. +- ▪ ▪ ▪ ▪ Association +A Product's subordinate Association indicates a role to one or more other Products relative to the first Product. +- ▪ ▪ ▪ ▪ ▪ Type +A Product's Association to one or more other Products may be of the following Types: + - B – Bundle, where the other Products are components + - M – Main product, where the other Products are additional products + - C – Constrained product, where the other Products are excluded products + - I – Product instance, where the other Product is the Product type of the current Product + - N – Next service; if the user is not present at the current service, try the next +- ▪ ▪ ▪ ▪ ▪ Contained product +An Association's subordinate Contained product is a Product that is referenced in the Association. +- ▪ ▪ ▪ ▪ Installation +A Product's subordinate Installation indicates a role of an Installation. +- ▪ ▪ ▪ ▪ Superior association +A Product's subordinate Superior association is an Association that references the Product. +The recursive references on the Product types under a Catalogue put constraints on the Product instances under Contracts. + +A Product instance must contain exactly the Association Type Bundle, which are prescribed by the Product type. + +A Product instance may only have a subset of the Association Type Main Product that are given for the Product type. + +A Product instance may not contain or be part of a Product that is associated by the Association Type Constrained product of the Product type. + +A Product instance can only have the Association Type Next to Products of Product types having this association from the Product type of the Product instance. + +A Product instance obeys all rules that are prescribed for its Product type, as well as the type's recursively superior types. + +A Product type or Product instance may have an Association Type I to another Product type. When this Association is between two Product types, it is used to inherit properties. When it is between an instance and a type, it is used for instantiation. Inheritance may be seen as a constrained form of instantiation. Note that the Association from instance to type may or may not be explicitly stored. Also, the Type of the instance Identifier will tell about this Association. + +Note that specialized associations may be derived from the various Association Types, e.g., a S(chema) reference from the Association Type I. Such derived associations are not covered by this Recommendation. + +### - ▪ ▪ ▪ ▪ Event + +A special set of circumstances under which a service management policy would be triggered. + +Normally, only service Products may have Events. + +### - ▪ ▪ ▪ ▪ Identifier + +A globally unique identifier of the Event. The identifier may consist of a prefix indicating the environment, e.g. Service platform, of the identifier, followed by the unique identifier within that environment. + +#### - ▪ ▪ ▪ ▪ ▪ Environment + +A globally unique identification of the hardware or software environment in which Events are identified. + +### - ▪ ▪ ▪ ▪ ▪ Event-identifier + +A unique identifier of the Event within its Environment. + +### - ▪ ▪ ▪ ▪ ▪ Price component + +An Event's subordinate Price component refers to a Price component subordinate to a Price of the same or a recursively superior Product. + +### - ▪ ▪ ▪ ▪ Price + +A Product type may have several Prices. A Product instance has only one Price. + +The Price of a Product instance may depend on Deal and Market. The same Price may apply for several Deals or Markets, or may be different for alternative Deals and Markets. + +### - ▪ ▪ ▪ ▪ ▪ Price component + +A Price is made up of a set of Price components. Normally, Price components are added up to make up the Price. However, the Price type may indicate subtraction, multiplication or other operators. + +- ▪ ▪ ▪ ▪ ▪ ▪ Price type + - A category that describes the price, such as recurring, discount, allowance, penalty, and so forth. +- ▪ ▪ ▪ ▪ ▪ ▪ Unit + - The unit used for this Price component. The unit may be given in a certain currency, minutes, SMSes or other. +- ▪ ▪ ▪ ▪ ▪ ▪ Amount + - The amount in which this Price is defined. +- ▪ ▪ ▪ ▪ ▪ ▪ Description + - A narrative that explains in detail the semantics of this Price component. +- ▪ ▪ ▪ ▪ ▪ ▪ Valid period + - The period for which the pricing is valid. +- ▪ ▪ ▪ ▪ ▪ ▪ Event + - A Price component's subordinate Event refers to an Event subordinate to a service Product. +- ▪ ▪ ▪ ▪ ▪ ▪ Price rule + - A Price component is governed by Price rules. All Price rules consist of three types of components, which define the semantics of the rule. +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Event + - A Price rule may refer to the Price component's subordinate Event which may trigger the evaluation of the Price rule. +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Price condition + - Part of a Price rule representing constraints that define the assessment of the Price rule. +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Price action + - The action to be taken when the Price condition is satisfied. +- ▪ ▪ ▪ ▪ ▪ ▪ Deal + - A Price's subordinate Deal indicates a role of a Deal subordinate to the Price. +- ▪ ▪ ▪ ▪ ▪ ▪ Market + - A Price's subordinate Market indicates a role of a Market. The Market indicates the market segment for which this Price applies. +- ▪ ▪ ▪ ▪ Use + - A Product instance may have a Use, which is a role of a Use. Use refers to a Customer and his relationship to the Product instance. +- ▪ ▪ Market + - An Operator may have several subordinate Markets, which each indicates a role of a Market of this Operator. +- ▪ ▪ Channel + - A medium or organization through which Products may be distributed or sold. +- ▪ ▪ ▪ Identifier + - A unique identifier of the Channel within the Operator. + +- ▪ ▪ ▪ Name +The name of the Channel. +- ▪ ▪ ▪ Channel information +The detailed information of the Channel. +- ▪ ▪ ▪ Product +A Channel's subordinate Products refer to the Products that may use this sales or distribution Channel +- ▪ ▪ Contract +A Contract is a contract with a Customer on delivery of services, which are called Product instances in this data structure. +Permissible Product types for sale can be found in two ways: + - By the schema reference (S) to Catalogues, which are explicitly referred to from the Contract; + - If no explicit schema reference is provided, the permissible Product types are found under the latest Catalogue under the Contract's superior Operator. + Note that older Product types under the current Contract may come from older Catalogues under the current Operator. +A Customer may have one or more Contracts. Sometimes it may be convenient to have one Contract per Account. +- ▪ ▪ ▪ Contract number +A Contract's subordinate Contract number is a unique identifier of a Contract within the Operator. +A Contract number may by default be identical to a phone number used to identify a Product instance subordinate to the Contract. If a Contract number is assigned this way, one must avoid that this number comes in conflict with numbers assigned differently. +The customer may not always be informed about the Contract number, and the Operator may not expect that the Customer is able to inform about his Contract number. Rather, the Customer may inform about a Number of a Product instance, e.g., a phone number. +- ▪ ▪ ▪ Amount +A Contract's subordinate Amount indicates the available amount for usage under this Contract. +- ▪ ▪ ▪ ▪ Prepaid amount +An Amount's subordinate Prepaid amount indicates the set amount for usage from the Prepaid date under this Contract. +The Prepaid amount is the Prepaid amount minus the Spent amount before the Prepaid date plus the additional amount paid at this date. +- ▪ ▪ ▪ ▪ Prepaid date +The Prepaid date gives the last date when the Prepaid amount under this Contract was updated. +- ▪ ▪ ▪ ▪ Spent amount +An Amount's subordinate Spent amount indicates the used amount under this Contract since the Prepaid date. The available amount for usage is Prepaid amount $\div$ Spent amount. + +NOTE – More attributes, e.g., for Available amount, Last usage update, etc., could be defined, if needed. + +#### - ▪ ▪ ▪ Internet address + +A Contract's subordinate Internet address indicates the Customer's contact address. A Customer may have more Internet addresses, and each Internet address is recorded as a Product instance. + +### - ▪ ▪ ▪ Account + +A Contract may have one or more subordinate Accounts, which each is a role of an Account. Normally a Contract has one Account only, but use of multiple Accounts allows for split bills. Rules given for each Account specifies which costs go where, e.g., before 17.00 hours to the company customer and after 17.00 hours to the private customer. Also, the Account hierarchy may help to accomplish this split. + +#### - ▪ ▪ ▪ Role + +A Contract's subordinate Role indicates the Customer's relationship to this Contract. + +#### - ▪ ▪ ▪ ▪ Category + +The Category indicates which role a Customer plays relative to a Contract. The Category is an attribute group that consists of attributes. + +If the value of the Type attribute is updated by the terminal user, then the value of the Update attribute is set to manual (M). If the role is created by the system itself, then the value of the Update attribute is set to derived (B). Only roles that are updated manually need to be stored. + +#### - ▪ ▪ ▪ ▪ ▪ Type + +A Role's subordinate Type may have one of the following values: + +- E – owner +- B – payer +- Y – authorized +- K – contact +- V – very important person +- U – user +- A – provider agent +- R – responsible employee + +A Contract may only have one Role of Type owner (E), payer (B), user (U) or provider agent (A), but may have several Roles of Type contact (K) and very important person (V). + +If some Roles are not explicitly provided for a Contract, and the Contract has one Account only, then the Roles of the Contract are copied from the Roles of the Account. + +If the Role of Type user (U) is not indicated for the Contract, but is the same for several subordinate Product instances, then this role is copied to the Contract. + +If owner (E) is provided, and payer (B) is missing, then the payer is equal to the owner. + +If owner (E) is provided, and user (U) is missing, the user is equal to the owner. + +If payer (B) is provided, and owner (E) is missing, the owner is equal to payer. + +If payer (B) is provided, and user (U) is missing, the user is equal to payer. + +If user (U) is provided, and owner (E) is missing, the owner is equal to user. + +If user (U) is provided, and payer (B) is missing, the payer is equal to user. + +If Use is not provided for some subordinate Product instances, then these are copied from the user (U) Type of the Contract. + +If some Roles are not provided for a related Account, and this Account has only this Contract, then the Roles of the Account are equal to those of the Contract. + +Derived Types may, e.g., be indicated by a separate colour at the user interface, or they may be hidden. + +#### ▪ ▪ ▪ ▪ ▪ ▪ Update + +The Type of a Role may be updated + +M – manually + +B – automatic + +#### ▪ ▪ ▪ ▪ ▪ Customer + +A Role must have a subordinate Customer that is a role of a Customer. + +### ▪ ▪ ▪ ▪ *S <> '& (Corporation ( Country ( Operator ( Catalogue* + +A Contract's superior Operator's first subordinate Catalogue is a S(chema) for the Product instances subordinate to the Contract. + +Note that the reference may go all the way up to the object Corporation via wild card (&) down to some other Operator than the directly superior Operator. If this option is used, the value of the Catalogue attribute of the Product instance must be made unique across the Operators. + +If no explicit S(chema) reference is provided, the latest Catalogue of the directly superior Operator is used. + +Note that the S(chema) reference may itself be instantiated. Then the reference goes via the Population of the Schema. + +The Product instances subordinate to the Contract are instances of the Product types subordinate to the S(chema) referenced Catalogue. + +The recursive references on the Product types put restrictions on the Product instances subordinate to the Contract: + +- A Product instance must contain exactly the Associations with the Type Bundle that are prescribed for its Product type; +- A Product instance may only contain a subset of the Associations with the Type Main product that are allowed for its Product types; +- A Product instance must not contain Associations with the Type Constrained that are prescribed for its Product types; +- A Product instance must obey all constraints that are defined for its Product types as well as its recursively superior Product types, indicated by the Association Type I. + +### - ▪ ▪ Deal + +A Deal defines a relationship from an Operator via a Membership to a Customer on one or more product instance prices of given Product types. A Deal is valid for a limited time period, with a defined start and stop. + +A Deal may be a campaign for a product type or a result of a campaign for a product instance. + +Note that a Product instance may be related via Price to several Deals, and Deals may become terminated, while a Product instance is contained in a Contract that cannot be removed without removing its Product instances, as well. + +#### - ▪ ▪ ▪ Account + +A Deal may have a subordinate Account, which is a role of an Account, which is the billing Account for this Deal. + +#### - ▪ ▪ ▪ Membership + +A Deal may have subordinate Memberships, which each is a role of a Membership. + +### - ▪ ▪ ▪ Price + +A Deal may have several subordinate Prices, which each is a role of a Price. The Prices may be both types (under Product in a Catalogue) and instances (under Product in a Contract). + +### - Employee + +Employee is an employee of an Operator of Product instances to Customers. + +#### - ▪ Employee number + +Employee number is a unique identifier of an Employee of an Operator of Product instances. Some employees may have several Employee numbers. In this case, several Employees are related to the same Customer, who plays the role of being the person that is employed. + +Note that Employee number is unique across all Operators of a corporation. + +### - ▪ Customer + +An Employee may have a subordinate Customer, who indicates a role of the employee as a Customer. + +Note that the employee's role to other Customers is registered from his Customer role to the other Customers. + +### - Installation + +Installation indicates a reference to the installation address of a Product instance. + +#### - ▪ Change + +Change indicates state and time interval for the installation. + +### - ▪ ▪ State + +State indicates + +H – historic + +I – installed + +### - ▪ ▪ Time interval + +Time interval indicates the time period for the establishment or termination of an installation. + +### - Installation address + +An Installation must have a subordinate Installation address that indicates the Address where the Product instance is installed. + +### - Product + +An Installation must have a subordinate Product, which indicates the Product instance that is installed at the Address. + +### - Market + +A Market defines a market segment, which the Operator chooses to handle in a harmonized manner. + +A Market may be defined by customer groupings, channel groupings or by other means. + +### - Operator + +A Market may have a subordinate Operator, which is a role of an Operator for whom the given Prices apply. + +### - Price + +A Market may have subordinate Prices, which each indicates a role of a Price of a Product (type or instance). + +### - Membership + +A Membership indicates an association between a Customer and a Deal of an Operator. + +### - Category + +A Category indicates a role that a Customer plays in a Deal. Category is an attribute group, which contains two attributes. + +If Type is updated manually by the terminal user, the Update attribute value is set to manual (M). If the Type is updated by the system itself, the Update attribute value is set to derived (B). Only manual updates need to be stored. + +### - Type + +The Type of a Membership may have one of the following values: + +K – contact + +M – member + +E – owner + +Note that often the members will only be registered by a reference to their phone numbers, i.e., Number within a Product instance. In this case, the memberships will be derived automatically from Product instances via Use to Customer. + +### - Update + +Types may be updated + +M – manually + +B – derived + +### - Customer + +A Membership may have a subordinate Customer that is a role of a Customer of the corporation. + +### - Deal + +A Membership may have a subordinate Deal, which indicates a role of a Deal subordinate to Operator. + +### - Structure + +A Structure indicates the organization of the Customer. + +The Operator will normally not register this Structure, but sometimes the implied organization of a corporation into its constituent business units may be derived from the geographical locations, or of families from their relationships to common account numbers and addresses. + +The Operator will normally only register the Customer's associations to Accounts, Contracts and Products, which indicates agreed relationships between the Customer and Operator. + +#### - ▪ Type + +Type indicates which role a Subordinate customer plays to a Superior customer. + +V – indicates subordinate business unit + +M – indicates Member of a family + +U – indicates subordinate Unspecified membership + +H – indicates historical entity of the current entity + +#### - ▪ Subordinate customer + +A Structure's Subordinate customer indicates a role of a Customer that is superior to this Structure. + +#### - ▪ Superior customer + +A Structure's Superior customer indicates a role of a Customer that is subordinate to this Structure. + +#### - Type + +A Type indicates the type of Address of the Customer. + +#### - ▪ Type + +Type indicates the role of the referenced Address relative to the Customer. + +S – location + +P – postal address + +#### - ▪ Address + +A Type must have a subordinate Address, which indicates a role of an Address. + +#### - ▪ Customer + +A Type must have a subordinate Customer that indicates a role of a Customer. + +#### - Type + +A Type indicates the type of Address of the Account. + +#### - ▪ Type + +Type indicates the role of the referenced Address relative to the Account. + +A – address of responsible person + +B – billing address + +A company customer may have several Accounts, which each may have different responsible persons. + +#### - ▪ Account + +A Type must have a subordinate Account, which indicates a role of an Account. + +#### - ▪ Address + +A Type must have a subordinate Address, which indicates a role of an Address. + +### - Use + +Use indicates a role between a Product instance and a Customer. The role is defined in the attribute group Category. Use is not relevant for Product types within a Catalogue. + +#### - ▪ Category + +Category indicates the role that a Customer has to be a Product instance. Category is an attribute group which consists of two attributes. + +If the attribute Type is updated by the terminal user, the Update attribute is assigned the value Manual (M). If the role is established by the system itself, the Update attribute is assigned the value automatic (B). Only roles that are updated manually need to be stored. + +#### - ▪ ▪ Date + +Date for establishment of a certain Type of Use. + +#### - ▪ ▪ Type + +The subordinate Type of a Use may have one of the following values: + +K – contact person + +U – user + +A Product may have one user (U) only, but may have several contacts (K). + +If a particular Role is not provided for the superior Contract, and this role is given for the current Product instance in the Contract, then the Role of the Contract is derived automatically from the role of the Product instance. + +If Use is not given for a Product instance, this is derived automatically from the Role of the Contract. + +From the above, if a role is given for a particular Product instance only, then this role is inherited to all Product instances within the Contract. However, the inherited roles may be overridden by manual insertion of particular roles for a Product instance, Contract or Account. + +Derived Types may be indicated by use of a separate colour in the end-user dialogue, or they may be hidden. + +#### - ▪ ▪ Update + +The Type of a Use may be updated + +M – manual(ly) + +B – automatic + +#### - ▪ Customer + +A Use must have a subordinate Customer, who is a role of a Customer. + +#### - ▪ Product + +A Use must have a subordinate Product, which is a role of a Product instance. + +## Appendix I + +### Product and customer service databases + +(This appendix does not form an integral part of this Recommendation.) + +Products in a Catalogue may be instantiated into Products in a Contract. This is illustrated in Figure I.1, which depicts how classes within the Catalogue class apply within any Contract. The Contract plays the role of being a P(opulation) of the Catalogue, which acts as a S(chema) of the Contract. + +![Figure I.1: Example inheritance by instantiation from the product Catalogue. The diagram shows a hierarchy of classes: Corporation at the top, connected to Country, which is connected to Operator. Operator is connected to Contract. Contract is connected to Product. Product is connected to Association, which is connected to Catalogue. A dashed line labeled 'S' points from Contract to Catalogue. The diagram is labeled M.1402(07)_FI.1.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` +graph TD; Corporation --> Country; Country --> Operator; Operator --> Contract; Contract --> Product; Product --> Association; Association --> Catalogue; Contract -.->|S| Catalogue; +``` + +Figure I.1: Example inheritance by instantiation from the product Catalogue. The diagram shows a hierarchy of classes: Corporation at the top, connected to Country, which is connected to Operator. Operator is connected to Contract. Contract is connected to Product. Product is connected to Association, which is connected to Catalogue. A dashed line labeled 'S' points from Contract to Catalogue. The diagram is labeled M.1402(07)\_FI.1. + +**Figure I.1 – Example inheritance by instantiation from the product Catalogue** + +NOTE 1 – The Schema reference from Contract to Catalogue in Figure I.1 allows for an n:1 mapping from Product under Contract to Product under Catalogue. Only a 1:1 mapping is depicted. The purpose is to show that the same classes apply under Contract as of under Catalogue. This is right, but in practice, the instantiation is more complicated: Contract is instantiated, Catalogue is instantiated, and Schema references are stated between the Contract instances and Catalogue instances. Product instances under Contract instances are instantiated from Product type instances under Catalogue instances. + +NOTE 2 – The term inheritance is used in many object oriented notations, but not in the notation used in the ITU-T M.1400 series, as the ITU-T M.1400 series prescribe syntax, not concepts. The purpose of Figure I.1 and the accompanying text is to show that something similar to inheritance, but more complex, can be stated. Most object-oriented notations apply only between classes. In the current approach, the same notation applies between instances. + +The Product class and its subordinate classes, such as Price, may be instantiated into a product database. An example instantiation is shown in Figure I.2. + +![A hierarchical diagram showing database instances. At the top is 'Population', followed by 'Country: S', 'Operator: SV', and 'Catalogue: 1'. Below 'Catalogue: 1' are three product instances: 'Product: IPCEN', 'Product: TEL', and 'Product: EMAIL'. To the left of these products are association types: 'A: B' is associated with 'Product: IPCEN'; 'A: T' is associated with 'Product: TEL'; and another 'A: T' is associated with 'Product: EMAIL'. A small label 'M.1402(07)_FI.2' is at the bottom right of the diagram.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +graph TD + Population[Population] --> CountryS[Country: S] + CountryS --> OperatorSV[Operator: SV] + OperatorSV --> Catalogue1[Catalogue: 1] + Catalogue1 --> ProductIPCEN[Product: IPCEN] + Catalogue1 --> ProductTEL[Product: TEL] + Catalogue1 --> ProductEMAIL[Product: EMAIL] + AB[A: B] --> ProductIPCEN + AT1[A: T] --> ProductTEL + AT2[A: T] --> ProductEMAIL + +``` + +M.1402(07)\_FI.2 + +A hierarchical diagram showing database instances. At the top is 'Population', followed by 'Country: S', 'Operator: SV', and 'Catalogue: 1'. Below 'Catalogue: 1' are three product instances: 'Product: IPCEN', 'Product: TEL', and 'Product: EMAIL'. To the left of these products are association types: 'A: B' is associated with 'Product: IPCEN'; 'A: T' is associated with 'Product: TEL'; and another 'A: T' is associated with 'Product: EMAIL'. A small label 'M.1402(07)\_FI.2' is at the bottom right of the diagram. + +**Figure I.2 – Example instances in a product database** + +Note that the labels used in Figure I.2 are incomplete, due to lack of space inside the boxes. For example A: B means Association Type B. Product: IPCEN means a Product of Type IPCEN. Population is the name of the product database. + +The instances in a product database may act as classes of Product instances in a customer service database. This is illustrated in Figure I.3. + +![A hierarchical diagram showing instances in a customer service database. At the top is 'Population', which points to 'Country: S'. 'Country: S' points to 'Operator: SV'. 'Operator: SV' points to 'Catalogue: 1' and 'Contract 1'. 'Catalogue: 1' has a dashed arrow labeled 'S' pointing to 'Contract 1'. 'Contract 1' points to four product instances: 'Product: IPCEN-1', 'Product: TEL-1', 'Product: EMAIL-1', and 'Product: TEL-2'. 'Product: IPCEN-1' points to 'A: B'. 'Product: TEL-1' points to 'A: T'. 'Product: EMAIL-1' points to 'A: T'. 'Product: TEL-2' points to 'A: T'. A small label 'M.1402(07)_FI.3' is at the bottom right.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +graph TD + Population[Population] --> CountryS[Country: S] + CountryS --> OperatorSV[Operator: SV] + OperatorSV --> Catalogue1[Catalogue: 1] + OperatorSV --> Contract1[Contract 1] + Catalogue1 -.->|S| Contract1 + Contract1 --> IPCEN1[Product: IPCEN-1] + Contract1 --> TEL1[Product: TEL-1] + Contract1 --> EMAIL1[Product: EMAIL-1] + Contract1 --> TEL2[Product: TEL-2] + IPCEN1 --> AB[A: B] + TEL1 --> AT1[A: T] + EMAIL1 --> AT2[A: T] + TEL2 --> AT3[A: T] + +``` + +A hierarchical diagram showing instances in a customer service database. At the top is 'Population', which points to 'Country: S'. 'Country: S' points to 'Operator: SV'. 'Operator: SV' points to 'Catalogue: 1' and 'Contract 1'. 'Catalogue: 1' has a dashed arrow labeled 'S' pointing to 'Contract 1'. 'Contract 1' points to four product instances: 'Product: IPCEN-1', 'Product: TEL-1', 'Product: EMAIL-1', and 'Product: TEL-2'. 'Product: IPCEN-1' points to 'A: B'. 'Product: TEL-1' points to 'A: T'. 'Product: EMAIL-1' points to 'A: T'. 'Product: TEL-2' points to 'A: T'. A small label 'M.1402(07)\_FI.3' is at the bottom right. + +**Figure I.3 – Example instances in a customer service database** + +Note that there is a homomorphic mapping from instances to their classes, i.e., there is a many-to-one mapping from instances to classes, and for each box, line or label among the instances there is an identical box, line or label among their classes. The Catalogue attribute of the Product instances is not indicated. + +## Appendix II + +### Interface to a service platform + +(This appendix does not form an integral part of this Recommendation.) + +Some of the Product instances in the customer service database may be implemented as services within a service platform. Hence, information of the subset of Product types and Product instances need to be communicated over the interface to the service platform. Figure II.1 depicts the basic data structure needed for communicating instance data to and from the service platform. + +![Figure II.1: Example data structure for interface specification. The diagram shows a hierarchy of entities: Corporation, Country, Operator, Contract, Association, and Product. Corporation is connected to Country, which is connected to Operator. Operator is connected to Contract. Contract is connected to Product. Association is connected to Product and has a bidirectional relationship with Contract.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` +graph TD; Corporation[Corporation] --> Country[Country]; Country --> Operator[Operator]; Operator --> Contract[Contract]; Contract --> Product[Product]; Association[Association] --> Product; Contract <--> Association; +``` + +M.1402(07)\_FII.1 + +Figure II.1: Example data structure for interface specification. The diagram shows a hierarchy of entities: Corporation, Country, Operator, Contract, Association, and Product. Corporation is connected to Country, which is connected to Operator. Operator is connected to Contract. Contract is connected to Product. Association is connected to Product and has a bidirectional relationship with Contract. + +**Figure II.1 – Example data structure for interface specification** + +The interface specification towards the service platform is designed to be simple. + +The interface is anticipated to be implemented as a replication of a subset, i.e., horizontal partition, of the customer service database. + +Alternatively, the interface may be designed as an exchange of service orders; this alternative is not shown in this Recommendation. + +For pricing information, both Price and Deal may be added to the shown data structure. + +Note that what appears as a networked data structure (in the Application layer of the Data Architecture) may be turned into a tree (defined in a Distribution Schema) when being communicated over the interface to the service platform. + +Note that the data structure provides multi-operator support on one and the same service platform. + +## Bibliography + +- [b-TMF GB922A3] TM Forum GB922 (2010), *Shared Information/Data (SID) Model. Addendum 3 – Product Business Entity Definitions, Release 9.0.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1403-200708-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/M/T-REC-M.1403-200708-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d171bcb671715e39c0b5bca50d4b1d2ff646b359 --- /dev/null +++ b/marked/M/T-REC-M.1403-200708-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46248b9f1de143bca9c6af2afb874096a5ba4e77507df11063da063b02fd5c89 +size 7378 diff --git a/marked/M/T-REC-M.1403-200708-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.1403-200708-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.1403-200708-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.1403-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/M/T-REC-M.1403-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59aa0b0f05429a57e917364469ceb50188c73996 --- /dev/null +++ b/marked/M/T-REC-M.1403-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1569a20f2dc31687786b9d5b2345a5eb3cbacd2e4c9382c4de231aa997a8266e +size 39897 diff --git a/marked/M/T-REC-M.1403-200708-I_PDF-E/raw.md b/marked/M/T-REC-M.1403-200708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ee7e37eb065e23e2db91a592a5f7b9b88fb884c0 --- /dev/null +++ b/marked/M/T-REC-M.1403-200708-I_PDF-E/raw.md @@ -0,0 +1,413 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1403** + +(08/2007) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Designations and information exchange + +# --- Formalization of generic orders + +ITU-T Recommendation M.1403 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.1403** + +# **Formalization of generic orders** + +## **Summary** + +ITU-T Recommendation M.1403 defines orders and additional information intended primarily for human-to-human communication between various operators, i.e., network operators or service providers. + +The orders contain data for designations of interconnections and other information about services and network resources that are required to be communicated between operators. + +This Recommendation provides a skeleton that can be extended with any contents and allow for any use of the orders. + +This Recommendation is developed in order to facilitate computerized interoperation between telecommunication operators. + +As the data defined in this Recommendation are designed for human usage, they are independent of the functions in which they are used. Hence, the data may be applied in any functions, e.g., in customer requests, call centres, billing, service platforms, etc. + +## **Source** + +ITU-T Recommendation M.1403 was approved on 6 August 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Data definitions, designations, domestic, interconnection, international, messages, operator, orders, terminology, X interface. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 Normative references..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Conventions ..... | 2 | +| 6 External terminology schema ..... | 3 | +| Appendix I – Theory of orders..... | 6 | +| I.1 Introduction ..... | 6 | +| I.2 Statements in messages ..... | 6 | +| Appendix II – Simplifications relative to Ogden's triangle ..... | 8 | +| II.1 Introduction ..... | 8 | +| II.2 Denotations from messages ..... | 8 | +| Appendix III – Harmonization issues ..... | 9 | + +# Introduction + +This Recommendation defines order designations and additional information intended primarily for human-to-human communication between various operators, i.e., network operators or service providers within the context of an external terminology schema in end user terminology. + +This Recommendation on generic orders provides common terms for any order, e.g., network orders and service orders. + +The area of interest is the communication of orders between operators about network interconnections and telecommunication services. The objects of communication are telecommunication services and network resources. + +This Recommendation focuses on human needs for stable and recognizable data formats independently of the media they are communicated over. Therefore, in order to support the human-to-human communication, the formats defined in this Recommendation are required to be provided at the corresponding human-to-computer interfaces, as well. Hence, this Recommendation defines the formats of data at human-to-computer interfaces, but does not define the data communication formats for interfaces between computer systems, such as at the TMN X interface or non-TMN computer interfaces. However, it must be possible to automatically map the human-to-computer formats to the computer-to-computer formats and vice versa. The details of this mapping are for further study. + +Use of this Recommendation inside national jurisdictions will be the result of bilateral negotiation between the operators and/or national regulatory activity. Although compliance with all ITU-T Recommendations is voluntary, special mention is made for ITU-T Rec. M.1403 due to the sensitivity of designations for interconnection from a regulatory and legal standpoint. This extension greatly increases the number of routes and nodes to be identified, and in this way extends the name spaces to be provided. + +This Recommendation defines orders and additional information to be exchanged between two operators. While it defines order and message identification, it does not define data on the status or processing of these orders or messages. In that regard, this Recommendation can be considered as an adaptation or extension of ICT industry standards, e.g., OASIS UBL. ICT industry standards for such data may impose additional requirements on human-to-computer interfaces. + +The definition of information is common for the functions it supports. + +This Recommendation aims at supporting communication among service providers and network operators, but may also support communication between brokers, retailers, customers and installation providers. + +This Recommendation aims at defining designations of orders and additional information for service personnel, technicians and file support personnel at their terminals supporting the services and network, and serves as design information for developers of operational support systems. + +In addition to the definition of orders and messages in the main body of this Recommendation, Appendix I provides an explanation of the contents of messages. + +Appendix II presents order information in context of Ogden's triangle and discusses simplified designs. + +## Formalization of generic orders + +# 1 Scope + +The area of interest is the communication of orders between operators about telecommunication services and network interconnections. The contents of the orders are defined in other Recommendations. + +The focus of this Recommendation is on end user terminology as defined in an external terminology schema and which puts requirements on other schemata and implementations. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.1400] ITU-T Recommendation M.1400 (2006), *Designations for interconnections among operators' networks*. + +[ITU-T M.1401] ITU-T Recommendation M.1401 (2006), *Formalization of interconnection designations among operators' telecommunication networks*. + +[ISO 3166-1] ISO 3166-1:2006, *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes*. + +## 3 Definitions + +This Recommendation is comprised of structured definitions in the context of an external terminology schema graph. + +This Recommendation uses all definitions in [ITU-T M.1401], provides an additional order structure to these definitions, and provides correspondences between the two structures. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +ICC ITU Carrier Code + +ICT Information and Communications Technology + +OASIS Organization for the Advancement of Structured Information Standards + +UBL Universal Business Language + +## 5 Conventions + +Figure 1 shows boxes containing object class labels to indicate object classes. Lines supported with a reversed arrowhead indicate subordinate object classes. Lines with two-way arrows indicate references between object classes. A dashed one-way arrow with an S at the arrowhead indicates a schema reference and is here used to state instance-class correspondences between Messages. " ' & " states recursively superior node, while "(" states subordinate node. Hence, the used expression states a schema reference from any to any Message. Ellipses are used to indicate any data structure. + +The text that follows Figure 1 includes a label and explanation for each class in the schema. A class can be an object class, an attribute class, or a reference class. The level of each class is depicted in the text by indentations (5 mm) of the class label, supported with dashes, where the number of indentations and dashes indicates the level of a given class within the schema. Therefore, each class label has a given indentation based on the Figure 1 schema graph. + +Labels of data items that are subordinate to or referenced from a given object class are presented in the following sequence: + +- 1) alphabetized object class attributes; +- 2) alphabetized object class references; and +- 3) alphabetized object classes that are contained within the given object class at the next lower level. + +Textual definitions and explanations of object classes, attributes and references are provided in paragraphs that are adjusted 5 mm further to the right of their respective labels. + +Object class labels are underlined; attribute group and attribute labels are not underlined. Object class references are written in blue, italics and underlined. + +The formalism used in this Recommendation is introduced in Appendix III of [ITU-T M.1401]. + +Data attributes shall consist of sequences of characters, each character being either alphabetic (A-Z) or numeric (0-9). Additional requirements for symbols are explicitly stated in format requirements for specific attributes. It is recommended that alphabetic characters be represented with upper case letters unless stated otherwise. + +Brown dotted lines indicate references between the main register part and the order register part. Brown textual references indicate references between the main register part and the order register part. + +## 6 External terminology schema + +![Figure 1 – External terminology schema graph. The diagram shows two main registers. The 'Main register' on the left contains 'Country', 'Operator', and 'Part of main register'. The 'Order register' on the right contains 'Order', 'Message', and 'Part of order register'. 'Country' and 'Operator' are connected by a reversed arrow (containment). 'Operator' and 'Part of main register' are connected by a two-way arrow (reference). 'Order' and 'Message' are connected by a reversed arrow. 'Message' and 'Part of order register' are connected by a two-way arrow. A brown dashed arrow points from 'Part of order register' to 'Part of main register'. A solid line connects 'Operator' to 'Order'. A small 'S' is next to the 'Message' box. The label 'M.1403(07)_F01' is at the bottom right.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +Figure 1 – External terminology schema graph. The diagram shows two main registers. The 'Main register' on the left contains 'Country', 'Operator', and 'Part of main register'. The 'Order register' on the right contains 'Order', 'Message', and 'Part of order register'. 'Country' and 'Operator' are connected by a reversed arrow (containment). 'Operator' and 'Part of main register' are connected by a two-way arrow (reference). 'Order' and 'Message' are connected by a reversed arrow. 'Message' and 'Part of order register' are connected by a two-way arrow. A brown dashed arrow points from 'Part of order register' to 'Part of main register'. A solid line connects 'Operator' to 'Order'. A small 'S' is next to the 'Message' box. The label 'M.1403(07)\_F01' is at the bottom right. + +NOTE – Except for Order and Message and their references, the right-hand part is a copy of the left-hand part. The brown arrow shows the correspondences. Country may be contained in Corporation; this is not elaborated in this Recommendation. + +**Figure 1 – External terminology schema graph, depicting object classes (boxes), containment (reversed arrowheads) and references (two-way arrows)** + +### Country + +See [ITU-T M.1401]. + +#### - Country + +See [ITU-T M.1401]. + +### - Name + +See [ITU-T M.1401]. + +### - Code + +See [ITU-T M.1401]. + +### - Operator + +See [ITU-T M.1401]. + +#### - ▪ Operator + +See [ITU-T M.1401]. + +### - ▪ ICC + +See [ITU-T M.1401]. + +#### - ▪ Order + +An Order identifies a transaction relative to an organization, a part of an organization or a collaboration of organizations. This organization is typically an Operator, but may involve Customers, installation companies, etc. + +An Order comprises a set of Messages that are linked via the common Order. + +An Order can be of one or several types, like customer order, installation order, activation order, billing order or other. This is prescribed by the Type of each Message contained in the Order. + +#### - ▪ ▪ **Number** + +The Order Number uniquely identifies the Order within an Operator. The Order Number is used to retrieve and follow up information on events that are described in the Message instances. Assignment of Order Numbers and management of order series are outside the scope of this Recommendation. + +The same Order Number may be used for a Request, Work order, etc., but different Numbers that are related by Derived orders may be used, as well. The Derived order may belong to another Operator. + +#### - ▪ ▪ Derived order + +An Order may have several subordinate Derived orders, which each is a role of another Order. Dependent on the current Order, Derived orders may be generated automatically. For example, the current Order may be a customer order/order request, while the Derived order may be an installation order. + +#### - ▪ ▪ Served order + +An Order may have several subordinate Served orders, which each is a role of another Order. The current Order may be a construction order, which must be executed before several installation orders can be executed. + +#### - ▪ ▪ Message + +A Message is a statement or a compound set of statements. A statement is the carrier of information between people and between systems. + +### *Message type* + +A message instance is of a message type. A message type provides a template for a message instance. + +Many message instances can refer to the same message class by the S(chema reference), and message classes can refer to other message classes recursively. + +The message type contains all the data classes for the data instances in the corresponding message instance. There may be several data instances of one data class in one message. + +### *Message instance* + +A message instance is treated as a unit of communication between persons or between systems. Due to the typing mechanism, provided by the S(chema) references between messages or by the Message Type attribute, a message instance will contain data according to a subset of the data classes provided subordinate to Message (class) in the data structure graph. + +For each of the object classes (recursively) contained in Message, there is a reference to the corresponding object class in the main register. Instances of this reference provide a source for more information on the actual status of the object instance. Typically, the Message instances contain information on what is the planned status of an object instance some time into the future, what has happened in the outside world (UoD), or what has been the (planned) status in the past. + +Seen from an object instance in the main register, the references to object instances in the order/transaction register (part) provide information on statements about the history and future of the entity. + +#### ▪ ▪ ▪ ▪ Type + +Each message instance is of one named message Type only. However, message types may inherit from other message types without inheriting the Type value. + +The typing mechanism constrains the data in the message instance to be of its message type (and recursively superior message classes) only. + +#### ▪ ▪ ▪ ▪ *S <> ' & ( ( Order ( Message* + +A Message's subordinate S(chema) is a role of another Message, which provides the message class for the (first) message instance. + +The S(chema) reference may be explicitly given for each Message, as will by the case between different message classes. + +Normally, a message instance will contain the Type attribute only, which provides an indirect schema reference to the appropriate message class. + +## Appendix I + +## Theory of orders + +(This appendix does not form an integral part of this Recommendation) + +### I.1 Introduction + +The fundamentals about orders are found in the definitions of Order and Message in the main body of this Recommendation. + +### I.2 Statements in messages + +In this Recommendation, a Message is treated as a set of statements in one sentence. The statements are elementary and correspond to predicates in predicate calculus. An example statement is "Customer abc has Role Owner to Account 123", or in predicate calculus "Role(abc, Owner, 123)". In the corresponding Message type, we find the template "Customer x has Role y to Account z", i.e., "Role(x, y, z)". + +The main register consists of a set of elementary statements, and so does the order register. In the main register, the schema of the data classes is instantiated into a population of data instances. In the order register, the message types are instantiated into message instances. A message type may contain most of the data definitions that are contained in the schema of the main register, and a message instance may contain some of the data instances that are contained in the population of the main register. + +In this Recommendation, data classes in the main register are considered to be first class citizens of the order register, as well. This means that this Recommendation does not address additional information, like process information, work flow, deals with installation companies, dates with customers, contacts, comments, etc. + +The elementary statements of the External Terminology Layer of both registers may be considered combined by conjunctions, e.g., "Role(abc, Owner, 123) AND AddressType(123, bill, Kings road 16) AND Role(bcd, Owner, 234) etc.". + +The Contents Layer for both registers uses reflexive pronouns rather than conjunctions, e.g., "Customer abc, (WHICH has) RoleOwner 123, (WHICH has) TypeAddress Kings road 16 etc.". + +The effect of the above is that the terminology and grammar of the order register is identical to that of the main register. This is a fundamental issue, and provides harmonization and great simplifications for users who have to use both registers. + +The references between the two registers provide a history of all statements about each entity in the main register. These history statements may be about past or future events. Here we give no recommendation on how much of this information should be recorded in one system or how the schema and population data should be partitioned into several systems, e.g., about past, current or future events. + +If we want to assign actions to what should happen to the entities outside the register(s), this then will have to be provided in attributes of the entities. The form of these attributes should be coordinated across all entities. Also, the actions relate to the status of the entities in the main register. Hence, a generic Status attribute may replace the need for action attributes. This is for further study. + +Note that we have provided no means to nest or group Messages within an Order. Such associations may relate to work flow and work sequences, and these issues are not addressed in this Recommendation. Also, there is no means to reference between objects within two Messages, + +except that the same object may be mentioned within several Messages. This means that we may state that a relationship to an object has to be removed and another relationship to the same object has to be established within the same or different Messages, but cannot state which should be treated first. We may, however, assign timing to each event, but relative timing between events is for further study. + +The reader should note the extensive use of local naming in orders as well as in the main register. Order (Number)s are defined locally to Operator. This means that the full identifier of the Order is Operator Identifier plus Order Number. However, within the scope of the Operator who issues this particular Order Number, i.e., the Operator who originates the Order, only the Order Number is needed. Only when communicating with other Operators, need the full identifier be used. + +Within a Message of an Order we may also have Operators. The purpose of this mentioning is to be able to talk about any Operator inside the Message. One of these Operators may be the same as the one who originated the Order. + +Since the contents of a Message class is identical to that of the Schema of the main register, the contents could have been defined by inheritance. To this must be added the two-way references between corresponding classes of the two registers. + +## Appendix II + +## Simplifications relative to Ogden's triangle + +(This appendix does not form an integral part of this Recommendation) + +### II.1 Introduction + +This appendix introduces Ogden's triangle and explains the role of Messages in context of this triangle. + +The linguist Charles Kay Ogden (1889-1957) distinguished between terms, concepts and phenomena as shown in Figure II.1. Note that different labels of these notions may be used, like names, ideas and things. The discussion of different world views dependent on or indicated by the various choices of labels is outside the scope of this appendix. + +![Figure II.1 – Ogden's triangle. A diagram showing three nodes: 'term' (top left), 'concept' (top right), and 'phenomenon' (bottom center), connected by lines forming a triangle. The text 'M.1403(07)_FII-1' is visible near the bottom right node.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` +graph TD; term((term)) --- concept((concept)); term --- phenomenon((phenomenon)); concept --- phenomenon; M140307_FII-1[M.1403(07)_FII-1] +``` + +Figure II.1 – Ogden's triangle. A diagram showing three nodes: 'term' (top left), 'concept' (top right), and 'phenomenon' (bottom center), connected by lines forming a triangle. The text 'M.1403(07)\_FII-1' is visible near the bottom right node. + +**Figure II.1 – Ogden's triangle** + +The relation from terms to concepts may be labelled tcDenote, the relation from terms to phenomena may be labelled tpDenote, and from concepts to phenomena may be labelled cpDenote. + +### II.2 Denotations from messages + +Terms may correspond to objects, attributes and values within the contents of Messages within Orders. Concepts may correspond to objects, attributes and values within the main register. Hence, the relation from data in the order register to data in the main register may correspond to tcDenote. And the concepts are data. + +Note that there may be order data without corresponding data (yet) in the main register, and there may be main register data without corresponding data in the order register. However, when there is a mapping between the two registers, the mapping between the contents of each Message and the main register is isomorphic. The mapping between the contents of a set of Messages and the main register is homomorphic. + +Both the order data and the main register data may be within the External terminology layer of the data architecture. Both sets of data may map to the Concept layer. This mapping is the tcDenote relation. + +The Internal terminology layer may be considered to contain the phenomena of an IT system. The mapping from the Concept layer to the Internal terminology layer is the cpDenote relation. + +The architecture may be considerably simplified if the Concept layer and the mappings to and from it can be discarded. In this case, only the tpDenote relation from the External terminology layer to the Internal terminology layer is used. In many cases, also the Internal terminology layer may be bypassed. + +Further simplification may be achieved by discarding the Order notion. Orders are introduced for handling long transactions among organizations and systems. Hence, the orders may be discarded if everything is treated within one system, and/or with synchronous communication to other systems. + +## Appendix III + +## Harmonization issues + +(This appendix does not form an integral part of this Recommendation) + +The HCI data defined in this Recommendation are considered to provide requirements on information models in other Recommendations. Also, the information models may provide feedback on HCI data. + +In particular, four issues in regard to harmonization of this Recommendation with TeleManagement Forum's Shared Data/Information (SID) Model have been identified for further study. + +The current SID Model provides a UML-based information reference model and a common information vocabulary from a business entity perspective. This business view model categorizes the business entities in a layered structure, with each layer identifying in more detail the entities associated with the immediate parent layer. + +Issues identified for further study follow. + +- 1) Name binding of Order within Operator: The SID Model associates "party" with "party role" which is associated with "order". Introduce the concept of "business role" between "Organization (Operator)" and "Order" in ITU-T Rec. M.1403. +- 2) Name binding of Message to Order: Align the association between Message and Order with "interaction/service order/resource order" as in the SID Model. +- 3) Different types of orders: ITU-T Rec. M.1403 makes no distinction between service order and derived order. Include roles of orders in ITU-T Rec. M.1403 with the SID Model, and align ITU-T Rec. M.1403 with pre-conditions and context as modelled in the SID, to determine the type of order. +- 4) Unique numbering of Order within Operator: The same Order number may be assigned by an Operator in different order management systems. The M.1403 name binding of Order within Operator does not allow for this. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1404-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.1404-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/M/T-REC-M.1404-200708-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/M/T-REC-M.1404-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/M/T-REC-M.1404-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6e616fb6452ce3d74d6f29cea4a1dcc000e7edb --- /dev/null +++ b/marked/M/T-REC-M.1404-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00decc55341be8746c9d5f11afc8e85dae28f856fe296a453ee70a68bb71a1a7 +size 230547 diff --git a/marked/M/T-REC-M.1404-200708-I_PDF-E/raw.md b/marked/M/T-REC-M.1404-200708-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2320e917574b2666db0df0cf94e2ca3006ec4c0b --- /dev/null +++ b/marked/M/T-REC-M.1404-200708-I_PDF-E/raw.md @@ -0,0 +1,564 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1404** + +(08/2007) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Designations and information exchange + +# --- **Formalization of orders for interconnections among operators' networks** + +ITU-T Recommendation M.1404 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.1404** + +# **Formalization of orders for interconnections among operators' networks** + +## **Summary** + +ITU-T Recommendation M.1404 defines orders and additional information intended primarily for human-to-human communication between various operators, i.e., network operators or service providers. + +The orders contain data for designations of interconnections and other information about network resources that are required to be communicated between operators. + +This Recommendation extends ITU-T Recommendation M.1401 and ensures use of M.1401 in orders containing designations of interconnections among operators' networks. + +This Recommendation is developed in order to facilitate computerized interoperation between telecommunication operators. + +## **Source** + +ITU-T Recommendation M.1404 was approved on 6 August 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Data definitions, designations, domestic, interconnection, international, operator, orders, terminology, X interface. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations..... | 1 | +| 5 Conventions ..... | 2 | +| 6 External terminology schema ..... | 3 | + +# Introduction + +This Recommendation defines order designations and additional information intended primarily for human-to-human communication between various operators, e.g., network operators, within the context of an external terminology schema in end-user terminology. + +The area of interest is the communication of orders between operators about network interconnections and network services. These orders may also be relevant for network planning and installation companies and other entities. The objects of communication are network interconnection points, places, stations, nodes, etc., interconnection links, and terminating and originating connections and transit connections. These terms are defined in [ITU-T M.1400] and [ITU-T M.1401]. + +This Recommendation focuses on human needs for stable and recognizable data formats independently of the media they are communicated over. Therefore, in order to support the human-to-human communication, the formats defined in this Recommendation are required to be provided at the corresponding human-to-computer interfaces as well. Hence, this Recommendation defines the formats of data at human-to-computer interfaces, but does not define the data communication formats for interfaces between computer systems, such as at the TMN X interface or non-TMN computer interfaces. However, it must be possible to automatically map the human-to-computer formats to the computer-to-computer formats and vice versa. The details of this mapping are for further study. + +Use of this Recommendation inside national jurisdictions will be the result of bilateral negotiation between the operators and/or national regulatory activity. Although compliance with all ITU-T Recommendations is voluntary, special mention is made for [ITU-T M.1404] due to the sensitivity of designations for interconnection from a regulatory and legal standpoint. This extension greatly increases the number of routes and nodes to be identified, and in this way extends the name spaces to be provided. + +This Recommendation defines orders and additional information to be exchanged between two operators. While it defines order and message identification, it does not define data on the status or processing of these orders or messages. In this regard, this Recommendation can be considered as an adaptation or extension of ICT industry standards, e.g., OASIS UBL. ICT industry standards for such data may impose additional requirements on human-to-computer interfaces. + +The definition of information is common for the functions it supports. However, the selection of information defined in this Recommendation basically supports provisioning and network maintenance. + +This Recommendation aims at supporting communication between network operators, but may also support communication between network operators and service providers, brokers, retailers, customers and installation providers. + +This Recommendation aims at defining designations and additional information for technicians and file support personnel at their terminals supporting the network, and serves as design information for developers of operational support systems. + +## ITU-T Recommendation M.1404 + +# Formalization of orders for interconnections among operators' networks + +# 1 Scope + +The area of interest is the communication of orders between operators about network interconnections. The objects of communication are network interconnection points, places, stations, nodes, etc., interconnection links, and terminating and originating connections and transit connections. These terms are defined in [ITU-T M.1400] and [ITU-T M.1401]. + +The focus of this Recommendation is on end-user terminology, as defined in an external terminology schema, which puts requirements on other schemata and implementations. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.1400] ITU-T Recommendation M.1400 (2006), *Designations for interconnections among operators' networks*. +- [ITU-T M.1401] ITU-T Recommendation M.1401 (2006), *Formalization of interconnection designations among operators' telecommunication networks*. +- [ITU-T M.1403] ITU-T Recommendation M.1403 (2007), *Formalization of generic orders*. +- [ISO 3166-1] ISO 3166-1:2006, *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes*. + +## 3 Definitions + +This Recommendation is comprised of structured definitions in the context of an external terminology schema graph. + +This Recommendation uses all definitions in [ITU-T M.1401], provides an additional order structure to these definitions, and provides correspondences between the two structures. + +## 4 Abbreviations + +This Recommendation uses the following abbreviations: + +- ICC ITU Carrier Code +- ICT Information and Communication Technology +- OASIS Organization for the Advancement of Structured Information Standards +- TMN Telecommunication Management Network +- UBL Universal Business Language + +## 5 Conventions + +Figure 1 shows boxes containing object class labels to indicate object classes. Lines supported with a reversed arrowhead indicate subordinate object classes. Lines with two-way arrows indicate references between object classes. A dashed one-way arrow with an S at the arrowhead indicates a schema reference and is here used to state instance-class correspondences between Messages. "&" states recursively superior node, while "(" states subordinate node. Hence, the used expression states a schema reference from any to any Message. + +The text that follows Figure 1 includes a label and explanation for each class in the schema. A class can be an object class, an attribute class, or a reference class. The level of each class is depicted in the text by indentations (5 mm) of the class label, supported with dashes, where the number of indentations and dashes indicates the level of a given class within the schema. Therefore, each class label has a given indentation based on the Figure 1 schema graph. + +Labels of data items that are subordinate to or referenced from a given object class are presented in the following sequence: + +- 1) alphabetized object class attributes; +- 2) alphabetized object class references; and +- 3) alphabetized object classes that are contained within the given object class at the next lower level. + +Textual definitions and explanations of object classes, attributes and references are provided in paragraphs that are adjusted 5 mm further to the right of their respective labels. + +Object class labels are underlined; attribute group and attribute labels are not underlined. Object class references are written in [blue](#), italics and underlined. + +The formalism used in this Recommendation is introduced in Appendix III of [ITU-T M.1401]. + +Data attributes shall consist of sequences of characters, each character being either alphabetic (A-Z) or numeric (0-9). Additional requirements for symbols are explicitly stated in format requirements for specific attributes. It is recommended that alphabetic characters be represented with upper case letters unless stated otherwise. + +Brown dotted lines indicate references between the main register part and the order register part. Brown textual references indicate references between the main register part and the order register part. + +## 6 External terminology schema + +![External terminology schema graph showing object classes, containment, and references.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The diagram illustrates the external terminology schema graph, showing various object classes as boxes and their relationships as arrows. The graph is divided into two main parts by a vertical dashed line. The left part contains classes such as Country, Operator, Geographical, Cross-coupling, Termination, Association, Address, Multipoint trail, Exchange, Location, Equipment, Equipment item, Trail, Physical link, Position, Component item, Trail multi-, Port item, and Trail section. The right part contains classes such as Order, Message, Country, Operator, Address, Association, Multipoint trail, Geographical, Cross-coupling, Termination, Site relationship, Exchange, Location, Equipment, Equipment item, Trail, Physical link, Position, Location, Component item, Trail multi-, Port item, Trail section, and Physical link. Solid black arrows represent references between classes, while dashed brown arrows represent correspondences between the left and right parts of the graph. Reversed arrowheads indicate containment relationships. + +External terminology schema graph showing object classes, containment, and references. + +M.1404(07)F\_01 + +NOTE – The left-hand part is identical to [ITU-T M.1401]. Except for Order and Message and their references, the right-hand part is a copy of the same. The brown arrows show the correspondences. Country may be contained in Corporation; this is not elaborated in this Recommendation. + +**Figure 1 – External terminology schema graph, depicting object classes (boxes), containment (reversed arrowheads) and references (two-way arrows)** + +### Address + +- Address +- Site + +### Association + +- Kind +- Superior trail +- Trail + +### Country + +See [ITU-T M.1401]. + +- Country +- Name + - See [ITU-T M.1401]. +- Code + - See [ITU-T M.1401]. +- Operator + - See [ITU-T M.1401]. + - Operator + - ICC + - See [ITU-T M.1401]. + - Controlled site + - Controlled trail + - Cross-coupling site + - Cross-coupling site + - Identifier + - Geographical area + - Site detail + - Local identifier + - Address + - A-end site relationship + - B-end site relationship + - Current operator + - Termination + - Geographical area + - Equipment item + - Equipment item + - Identifier + +- ▪ ▪ ▪ Unique item identification +- ▪ ▪ ▪ *Equipment identity* +- ▪ ▪ ▪ *Exchange* +- ▪ ▪ ▪ *Location* +- ▪ ▪ ▪ Component item + - ▪ ▪ ▪ ▪ *Component item* + - ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ Unique item identification + - ▪ ▪ ▪ ▪ *Equipment identity* + - ▪ ▪ ▪ ▪ *Location* + - ▪ ▪ ▪ ▪ Port item + - ▪ ▪ ▪ ▪ ▪ *Port identity* + - ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ *Equipment identity* + - ▪ ▪ ▪ ▪ ▪ *Position* + - ▪ ▪ ▪ ▪ ▪ *Trail section* + - ▪ ▪ ▪ ▪ Exchange + - ▪ ▪ ▪ ▪ *Exchange* + - ▪ ▪ ▪ ▪ No + - ▪ ▪ ▪ ▪ *Equipment item* + - ▪ ▪ ▪ ▪ Location + - ▪ ▪ ▪ ▪ *Location* + - ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ Unique item identification + - ▪ ▪ ▪ ▪ *Component item* + - ▪ ▪ ▪ ▪ *Equipment item* + - ▪ ▪ ▪ ▪ Location + - ▪ ▪ ▪ ▪ ▪ *Location* + - ▪ ▪ ▪ ▪ ▪ *S<> 'Location' Location* + - ▪ ▪ ▪ ▪ Position + - ▪ ▪ ▪ ▪ ▪ *Position* + - ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ *Physical link connection* + - ▪ ▪ ▪ ▪ ▪ *Port item* + - ▪ ▪ ▪ ▪ ▪ *Position* + - ▪ ▪ ▪ ▪ ▪ *Trail* + - ▪ ▪ ▪ ▪ ▪ *Trail multiplex channel* + +- ▪ ▪ ▪ ▪ [\*Trail section\*](#) +- ▪ Order + - See [ITU-T M.1403]. +- ▪ ▪ Number + - See [ITU-T M.1403]. +- ▪ ▪ [\*Derived order\*](#) + - See [ITU-T M.1403]. +- ▪ ▪ [\*Served order\*](#) + - See [ITU-T M.1403]. +- ▪ ▪ Message + - See [ITU-T M.1403]. +- ▪ ▪ ▪ Type + - See [ITU-T M.1403]. +- ▪ ▪ ▪ [\*S <> ' & \( \( \( Order \( Message\*](#) + - See [ITU-T M.1403]. +- ▪ ▪ ▪ Address +- ▪ ▪ ▪ ▪ [\*Address\*](#) +- ▪ ▪ ▪ ▪ [\*Site\*](#) +- ▪ ▪ ▪ Association +- ▪ ▪ ▪ ▪ Kind +- ▪ ▪ ▪ ▪ [\*Superior trail\*](#) +- ▪ ▪ ▪ ▪ [\*Trail\*](#) +- ▪ ▪ ▪ Country +- ▪ ▪ ▪ ▪ [\*Country\*](#) +- ▪ ▪ ▪ ▪ Name +- ▪ ▪ ▪ ▪ Code +- ▪ ▪ ▪ ▪ Operator +- ▪ ▪ ▪ ▪ ▪ [\*Operator\*](#) +- ▪ ▪ ▪ ▪ ▪ ICC +- ▪ ▪ ▪ ▪ ▪ [\*Controlled site\*](#) +- ▪ ▪ ▪ ▪ ▪ [\*Controlled trail\*](#) +- ▪ ▪ ▪ ▪ Cross-coupling site +- ▪ ▪ ▪ ▪ ▪ ▪ [\*Cross-coupling site\*](#) +- ▪ ▪ ▪ ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Geographical area +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Site detail +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Local identifier + +- ▪ ▪ ▪ ▪ ▪ ▪ *Address* +- ▪ ▪ ▪ ▪ ▪ ▪ *A-end site relationship* +- ▪ ▪ ▪ ▪ ▪ ▪ *B-end site relationship* +- ▪ ▪ ▪ ▪ ▪ ▪ *Current operator* +- ▪ ▪ ▪ ▪ ▪ ▪ *Termination* +- ▪ ▪ ▪ ▪ ▪ ▪ *Geographical area* +- ▪ ▪ ▪ ▪ ▪ ▪ Equipment item + - ▪ ▪ ▪ ▪ ▪ ▪ *Equipment item* + - ▪ ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ ▪ Unique item identification +- ▪ ▪ ▪ ▪ ▪ ▪ *Equipment identity* +- ▪ ▪ ▪ ▪ ▪ ▪ *Exchange* +- ▪ ▪ ▪ ▪ ▪ ▪ *Location* +- ▪ ▪ ▪ ▪ ▪ ▪ Component item + - ▪ ▪ ▪ ▪ ▪ ▪ *Component item* + - ▪ ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ ▪ Unique item identification +- ▪ ▪ ▪ ▪ ▪ ▪ *Equipment identity* +- ▪ ▪ ▪ ▪ ▪ ▪ *Location* +- ▪ ▪ ▪ ▪ ▪ ▪ Port item + - ▪ ▪ ▪ ▪ ▪ ▪ *Port item* + - ▪ ▪ ▪ ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ ▪ ▪ *Equipment identity* +- ▪ ▪ ▪ ▪ ▪ ▪ *Position* +- ▪ ▪ ▪ ▪ ▪ ▪ *Trail section* +- ▪ ▪ ▪ ▪ ▪ ▪ Exchange + - ▪ ▪ ▪ ▪ ▪ ▪ *Exchange* + - ▪ ▪ ▪ ▪ ▪ ▪ No +- ▪ ▪ ▪ ▪ ▪ ▪ *Equipment item* +- ▪ ▪ ▪ ▪ ▪ ▪ Location + - ▪ ▪ ▪ ▪ ▪ ▪ *Location* + - ▪ ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ ▪ Unique item identification +- ▪ ▪ ▪ ▪ ▪ ▪ *Component item* +- ▪ ▪ ▪ ▪ ▪ ▪ *Equipment item* +- ▪ ▪ ▪ ▪ ▪ ▪ Location + - ▪ ▪ ▪ ▪ ▪ ▪ *Location* + +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *S<> 'Location' Location* +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ Position + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Position* + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Physical link connection* +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Port item* +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Position* +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Trail* +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Trail multiplex channel* +- ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ *Trail section* +- ▪ ▪ ▪ ▪ ▪ Multipoint trail + - ▪ ▪ ▪ ▪ ▪ ▪ *Multipoint trail* + - ▪ ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ ▪ Local identifier + - ▪ ▪ ▪ ▪ ▪ ▪ *Trail* +- ▪ ▪ ▪ ▪ Geographical area + - ▪ ▪ ▪ ▪ ▪ *Geographical area* + - ▪ ▪ ▪ ▪ ▪ Name +- ▪ ▪ ▪ ▪ ▪ *Site* +- ▪ ▪ ▪ Equipment identity + - ▪ ▪ ▪ ▪ *Equipment identity* + - ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ *Component item* + - ▪ ▪ ▪ ▪ *Equipment item* + - ▪ ▪ ▪ ▪ *Location* + - ▪ ▪ ▪ ▪ *Port item* +- ▪ ▪ ▪ Site relationship + - ▪ ▪ ▪ ▪ *Site relationship* + - ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ A-end + - ▪ ▪ ▪ ▪ ▪ Country Code + - ▪ ▪ ▪ ▪ ▪ ICC + - ▪ ▪ ▪ ▪ ▪ Site + - ▪ ▪ ▪ ▪ ▪ B-end + - ▪ ▪ ▪ ▪ ▪ Country Code + - ▪ ▪ ▪ ▪ ▪ ICC + - ▪ ▪ ▪ ▪ ▪ Site + +- ▪ ▪ ▪ ▪ Local identifier + - ▪ ▪ ▪ ▪ ▪ A-end + - ▪ ▪ ▪ ▪ ▪ B-end + - ▪ ▪ ▪ ▪ A-end site + - ▪ ▪ ▪ ▪ B-end site + - ▪ ▪ ▪ ▪ Physical link + - ▪ ▪ ▪ ▪ ▪ Physical link + - ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ Physical link connection + - ▪ ▪ ▪ ▪ ▪ ▪ Physical link connection + - ▪ ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ Position + - ▪ ▪ ▪ ▪ ▪ Trail section + - ▪ ▪ ▪ ▪ Trail + - ▪ ▪ ▪ ▪ ▪ Trail + - ▪ ▪ ▪ ▪ ▪ Identifier + - ▪ ▪ ▪ ▪ ▪ Local identifier + - ▪ ▪ ▪ ▪ ▪ Bandwidth + - ▪ ▪ ▪ ▪ ▪ ▪ Maximum + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ Size + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ Unit + - ▪ ▪ ▪ ▪ ▪ ▪ Actual + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ Size + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ Unit + - ▪ ▪ ▪ ▪ ▪ Signalling + - ▪ ▪ ▪ ▪ ▪ Urgency + - ▪ ▪ ▪ ▪ ▪ ▪ Priority + - ▪ ▪ ▪ ▪ ▪ ▪ Limit + - ▪ ▪ ▪ ▪ ▪ ▪ Deadline + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ Date + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Day + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Month + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Year + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Time + - ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Hour + - ▪ ▪ ▪ ▪ Association + - ▪ ▪ ▪ ▪ Controller + +- ▪ ▪ ▪ ▪ ▪ Multipoint trail +- ▪ ▪ ▪ ▪ ▪ Position +- ▪ ▪ ▪ ▪ ▪ Routing trail section +- ▪ ▪ ▪ ▪ ▪ Subordinate association +- ▪ ▪ ▪ ▪ ▪ Termination +- ▪ ▪ ▪ ▪ ▪ Direction +- ▪ ▪ ▪ ▪ ▪ ▪ Cross-coupling site +- ▪ ▪ ▪ ▪ ▪ Trail multiplex channel +- ▪ ▪ ▪ ▪ ▪ ▪ Trail multiplex channel +- ▪ ▪ ▪ ▪ ▪ ▪ Number +- ▪ ▪ ▪ ▪ ▪ ▪ Position +- ▪ ▪ ▪ ▪ ▪ ▪ Trail section +- ▪ ▪ ▪ ▪ ▪ Trail section +- ▪ ▪ ▪ ▪ ▪ ▪ Trail section +- ▪ ▪ ▪ ▪ ▪ ▪ Identifier +- ▪ ▪ ▪ ▪ ▪ ▪ Physical link connection +- ▪ ▪ ▪ ▪ ▪ ▪ Port item +- ▪ ▪ ▪ ▪ ▪ ▪ Position +- ▪ ▪ ▪ ▪ ▪ ▪ Trail +- ▪ ▪ ▪ ▪ ▪ ▪ Trail multiplex channel +- ▪ Multipoint trail +- ▪ ▪ Multipoint trail +- ▪ ▪ Identifier +- ▪ ▪ Local identifier +- ▪ ▪ Trail +- Geographical area +- ▪ Geographical area +- ▪ Name +- ▪ Site + +### Equipment identity + +- Equipment identity +- Identifier +- Component item +- Equipment item +- Location +- Port item + +### Site relationship + +- Site relationship + - Identifier + - ▪ A-end + - ▪ ▪ Country Code + - ▪ ▪ ICC + - ▪ ▪ Site + - ▪ B-end + - ▪ ▪ Country Code + - ▪ ▪ ICC + - ▪ ▪ Site + - Local identifier + - ▪ A-end + - ▪ B-end +- A-end site +- B-end site +- Physical link + - ▪ Physical link + - ▪ Identifier + - ▪ Physical link connection + - ▪ ▪ Physical link connection + - ▪ ▪ Identifier + - ▪ ▪ Position + - ▪ ▪ Trail section +- Trail + - ▪ Trail + - ▪ Identifier + - ▪ Local identifier + - ▪ Bandwidth + - ▪ ▪ Maximum + - ▪ ▪ ▪ Size + - ▪ ▪ ▪ Unit + - ▪ ▪ Actual + - ▪ ▪ ▪ Size + - ▪ ▪ ▪ Unit + - ▪ Signalling + - ▪ Urgency + - ▪ ▪ Priority + +- ▪ ▪ Limit +- ▪ ▪ Deadline +- ▪ ▪ ▪ Date +- ▪ ▪ ▪ ▪ Day +- ▪ ▪ ▪ ▪ Month +- ▪ ▪ ▪ ▪ Year +- ▪ ▪ ▪ Time +- ▪ ▪ ▪ ▪ Hour +- ▪ *Association* +- ▪ *Controller* +- ▪ *Multipoint trail* +- ▪ *Position* +- ▪ *Routing trail section* +- ▪ *Subordinate association* +- ▪ Termination + - ▪ ▪ *Termination* + - ▪ ▪ Direction + - ▪ ▪ *Cross-coupling site* +- ▪ Trail multiplex channel + - ▪ ▪ *Trail multiplex channel* + - ▪ ▪ Number + - ▪ ▪ *Position* + - ▪ ▪ *Trail section* +- ▪ Trail section + - ▪ ▪ *Trail section* + - ▪ ▪ Identifier + - ▪ ▪ *Physical link connection* + - ▪ ▪ *Port item* + - ▪ ▪ *Position* + - ▪ ▪ *Trail* + - ▪ ▪ *Trail multiplex channel* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1405-200708-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.1405-200708-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.1405-200708-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.1405-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/M/T-REC-M.1405-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c6d6a6ee19d2bb973d38ecd093de4aa42ae6992 --- /dev/null +++ b/marked/M/T-REC-M.1405-200708-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77c34176bada5d75971d40f8f5a45fa55aad104ee7be0f3ec8393cea4126afd5 +size 139746 diff --git a/marked/M/T-REC-M.15-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.15-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3b6a0d0059a460eadf3698d91b294506e248d250 --- /dev/null +++ b/marked/M/T-REC-M.15-198811-I_PDF-E/raw.md @@ -0,0 +1,53 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.15** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: INTRODUCTION +AND GENERAL PRINCIPLES** + +--- + +**MAINTENANCE CONSIDERATIONS +FOR NEW SYSTEMS** + +**ITU-T Recommendation M.15** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.15 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **MAINTENANCE CONSIDERATIONS FOR NEW SYSTEMS** + +## **1 General** + +To ensure that new systems are implemented so as to permit compatible international operation and maintenance in the most effective manner, the following guiding principles are indicated. + +## **2 Principles** + +2.1 When a new system is being studied, early consideration should be given to operational and maintenance requirements. + +2.2 The maintenance organization and maintenance facilities (including test equipment) should be considered early enough to ensure their availability when the new system is introduced. + +2.3 In order to reduce total (lifetime) costs and to improve the efficiency of maintenance, new systems should be provided with internal supervision and fault localization functions. Such functions reduce the number and type of external test equipment to a minimum, and make it possible to omit most external routine tests. + +2.4 Where existing maintenance procedures, for example fault reporting, are not appropriate, alternative procedures should be considered early enough to ensure their application when the new system is introduced. However, any new procedures should consider established maintenance principles accepted by the CCITT. \ No newline at end of file diff --git a/marked/M/T-REC-M.1510-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1510-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2019efd5f4354ba10c416ab06862fb1337e9c42b --- /dev/null +++ b/marked/M/T-REC-M.1510-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:863fbab90e6121bc695abd9336f52f34bc433294cf4a592bb46cbad5ac93b554 +size 8307 diff --git a/marked/M/T-REC-M.1510-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.1510-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dc221045d408fa8e40ec1418a3f4a2292f3e0fa --- /dev/null +++ b/marked/M/T-REC-M.1510-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bd9b23afe9289bcb5c64b34a5ef4b58ff33edf36bdb97daf64ced7f6dca8981 +size 6543 diff --git a/marked/M/T-REC-M.1510-199210-I_PDF-E/raw.md b/marked/M/T-REC-M.1510-199210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..654a17fae6ddee6373dded1254fbe3dd8cdd9282 --- /dev/null +++ b/marked/M/T-REC-M.1510-199210-I_PDF-E/raw.md @@ -0,0 +1,339 @@ + + +![ITU logo: A globe with the letters ITU superimposed on it.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU superimposed on it. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**M.1510** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +(10/92) + +**MAINTENANCE: INFORMATION EXCHANGE** + +--- + +**EXCHANGE OF CONTACT POINT +INFORMATION FOR THE MAINTENANCE +OF INTERNATIONAL SERVICES AND +THE INTERNATIONAL NETWORK** + +![CCITT logo: A globe with the letters CCITT superimposed on it.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT superimposed on it. + +**Recommendation M.1510** + +--- + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation M.1510 was revised by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. + +# --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency. + +# Recommendation M.1510 + +# EXCHANGE OF CONTACT POINT INFORMATION FOR THE MAINTENANCE OF INTERNATIONAL SERVICES AND THE INTERNATIONAL NETWORK + +*(Published as M.93 in 1984, revised 1988; revised and renumbered in 1992)* + +## *Abstract* + +This Recommendation identifies contact points within a maintenance organization for the effective cooperation between Administrations; it lists services, and provides a guide of what information should be exchanged. Annexes A to E provide standard forms to be used in exchanging contact point information. + +## *Keywords* + +- contact point; +- distribution; +- exchange; +- information. + +## 1 General + +The attention of Administrations is drawn to the need for exchanging information about telephone numbers, telex numbers, staffing hours, etc., for units involved in the maintenance of international telecommunication services. The exchange of such information is of great assistance to international cooperation and has an important bearing on maintenance efficiency. + +This Recommendation lists services for which information should be exchanged. The list is not exhaustive and Administrations are asked to consider, when intending to introduce a new service, what contact point information will be required. + +## 2 Aspects to be covered by the exchange of information + +### 2.1 *Technical service* + +The general functions and responsibilities of the “technical service” are given in Recommendation M.75 [7]. + +Where technical service responsibility within an Administration has been divided on a functional basis, contact point information relating to each function (for example, maintenance of telephone circuits, provision of leased circuits, exchange of information for changes in national numbering plans and circuit order of selection) should be supplied. + +### 2.2 *Automatic and semi-automatic telephone service* + +For each international centre, contact point information for each of the maintenance elements in Recommendations M.715 to M.725 [8] should be exchanged. + +### 2.3 *Manual telephone circuits* + +For each international centre which has responsibility for manually operated international telephone circuits, appropriate maintenance contact point information should be exchanged. + +### 2.4 *Other international services* + +Contact point information, which should at least include information for fault reporting purposes, should be exchanged for the following international services: + +- Circuit-switched Public Data Communication service; +- Packet-switched Public Data Communication service; +- Public Telegram service; +- teletex service; +- telex service; +- Public Facsimile service (bureau and telefax); +- Store and Forward Facsimile Switching service; +- Phototelegraph service. + +### 2.5 *Common channel signalling systems* + +For each international centre where common channel signalling is employed, contact point information should be exchanged for the maintenance units which have responsibility for the following: + +- signalling system transfer link (Recommendations M.760 [9] and M.4100 [11]); +- signalling system administrative control (Recommendations M.762 [10] and M.4100 [11]). + +Where an Administration has subdivided the maintenance functions of the Common Channel Signalling System No. 6 transfer link (for example, into fault reporting, control station, etc.), appropriate contact point information should be supplied. + +### 2.6 *Leased and special circuits* + +For each international centre which has responsibility for leased and special circuits, contact point information should be exchanged for the following: + +- fault report point; +- testing point; + +- transmission maintenance point (international line) (Recommendation M.1014 [1]); +- circuit control/sub-control station (Recommendations M.1012 [2] and M.1013 [3]); +- restoration point for individual circuits; +- escalation points (Recommendation M.1560 [12]). + +### 2.7 *Sound programme and television* + +Contact point information for the following centres concerned with sound-programme and television should be exchanged: + +- international sound-programme centre (ISPC) (Recommendation N.1 [4]); +- international television centre (ITC) (Recommendation N.51 [5]); +- programme booking centre (PBC) (Recommendation D.180 [6]). + +### 2.8 *Groups, supergroups, etc., digital paths and blocks and transmission systems* + +For each international centre, contact point information should be exchanged for the following: + +- fault report point (Recommendation M.2130 [13]); +- testing point (for routines, functional tests and fault localization); +- control/sub-control station (Recommendations M.80 [14] and M.90 [15]); +- restoration control point (Recommendation M.725 [8]); +- restoration implementation point. + +### 2.9 *Setting-up and lining-up activities* + +Where staff, separate from those concerned with day-to-day maintenance, are used for setting-up and lining-up new or rearranged telephone circuits, leased circuits, groups, supergroups, etc., relevant contact point information should be exchanged. + +## 3 **Exchange and distribution of contact point information** + +Annexes A to E contain “forms” to be used for the purpose of exchanging contact point information. + +For convenience, the form in Annex B covers contact points for the automatic, semi-automatic and manual telephone service, and CCSS No. 6/No. 7. + +Each form provides for specific telephone numbers, telex numbers and answerback codes, and facsimile number together with the hours of staffing for each contact point and the name1) of the maintenance unit involved. The *remarks* columns on the forms should be used to supply other useful information, such as languages spoken, telephone number of the supervising officer of the maintenance unit. + +1) The name to be used is that by which the maintenance unit is known within the Administration and should ideally be the name used by maintenance staff when answering the telephone. + +Each contact point is afforded two horizontal lines. If the maintenance unit normally responsible for a particular contact point is staffed during restricted hours only, alternative contact point information should be supplied in the lower line for use outside those hours. + +In some situations a single telephone number, telex number, etc., will cover all contact points for several purposes, (e.g. leased and special circuits at an international centre). In other situations, each contact point may have its own number. The actual arrangements will depend upon the particular organization existing within the Administration concerned. + +Each Administration should distribute completed forms (see Annexes A to E) to all Administrations likely to have use of the contact point information involved. Furthermore, revised issues of the forms should be distributed as required, for example, to reflect organizational changes, because a new international centre has been put into service. + +Copies of contact point information distributed to, and received from, other Administrations should be made readily available to all staff at maintenance centres involved in international services or the international network. In this way, such staff are made aware of both their own functions and responsibilities and those of the maintenance organizations of other Administrations. + +## ANNEX A (to Recommendation M.1510) + +### **CONTACT POINTS FOR THE TECHNICAL SERVICE** + +COUNTRY: + +ADMINISTRATION OR PRIVATE OPERATING AGENCY: + +Contact point of the Technical Service: + +Postal address: + +Telephone No.: + +Telex No. and answerback: + +Facsimile No.: + +Office hours (UTC): + +International centres: + +Further information: + +(e.g. contact points common for more than one international centre, or principal contact points for certain traffic relations or where more than one technical service applies.) + +FIGURE A-1/M.1510 +**Form for contact points for the technical service** + +## ANNEX B (to Recommendation M.1510) + +### **CONTACT POINTS FOR INTERNATIONAL TELEPHONE SERVICE** + +COUNTRY: + +INTERNATIONAL CENTRE: + +DATE OF ISSUE: + +POSTAL ADDRESS: + +| Contact point | | Telephone No. | Telex No. answerback code | Facsimile No. | Service hours (UTC) | Name of unit responsible | Remarks a) | | +|------------------------------------------------|--------------------------------------------------------|---------------------------|---------------------------|---------------|---------------------|--------------------------|-----------------------|--| +| Automatic and semi-automatic telephone service | Fault report point (circuit) | | | | | | | | +| | Fault report point (network) | | | | | | | | +| | Testing point (transmission) | | | | | | | | +| | Testing point (line signalling) | | | | | | | | +| | Testing point (switching and interregister signalling) | | | | | | | | +| | Network analysis point | | | | | | | | +| | System availability information point | | | | | | | | +| | Network management | Planning + liaison point | | | | | | | +| | | Implement + control point | | | | | | | +| | | Development point | | | | | | | +| | Circuit control station subcontrol | | | | | | | | +| | Restoration control point | | | | | | | | +| Common channel signalling system (CCSS) | CCSS No. 6/No. 7 transfer link | | | | | | | | +| | CCSS No. 6/No. 7 administrative control | | | | | | | | +| Manual telephone service | Manual telephone circuits | | | | | | | | + +a) Language information may be included. + +FIGURE B-1/M.1510 + +**Form for the contact points for international telephone service** + +## ANNEX C + +(to Recommendation M.1510) + +### **CONTACT POINTS FOR INTERNATIONAL LEASED AND SPECIAL CIRCUIT MAINTENANCE** + +COUNTRY: + +INTERNATIONAL CENTRE: + +DATE OF ISSUE: + +POSTAL ADDRESS: + +CIRCUIT TYPE: + +THIS CENTRE DEALS WITH ALL ANALOGUE LEASED CIRCUIT FAULTS AND COOPERATION + +| Contact point | Telephone No. | Telex No. answerback | Facsimile No. | Service hours (UTC) | Name of unit responsible | Remarks | +|----------------------------------------------------------------|---------------|----------------------|---------------|---------------------|--------------------------|---------| +| Circuit Control/
sub-control station | | | | | | | +| | | | | | | | +| Transmission maintenance point-
international line (TMP-IL) | | | | | | | +| | | | | | | | +| Fault report point | | | | | | | +| | | | | | | | +| Testing point | | | | | | | +| Restoration of individual circuits | | | | | | | +| Setting-up and lining-up
of new and rearranged
circuits | | | | | | | +| | | | | | | | + +FIGURE C-1/M.1510 + +**Form for contact points for international leased and special circuits maintenance** + +## ANNEX D (to Recommendation M.1510) + +### **CONTACT POINTS FOR GROUP, SUPERGROUP, ETC., DIGITAL PATH, BLOCK, AND TRANSMISSION SYSTEM MAINTENANCE** + +COUNTRY: + +INTERNATIONAL REPEATER STATION (IRS): + +INTERNATIONAL CENTRES +SERVED BY THIS IRS: + +DATE OF ISSUE: + +POSTAL ADDRESS: + +| Contact point | Telephone No. | Telex No. and answerback code | Facsimile No. | Service hours (UTC) | Name of unit responsible | Remarks a) | +|----------------------------------------------------------|---------------|-------------------------------|---------------|---------------------|--------------------------|-----------------------| +| Fault report point | | | | | | | +| | | | | | | | +| Testing point | | | | | | | +| | | | | | | | +| Control/
sub-Control station | | | | | | | +| | | | | | | | +| Restoration implementation point | | | | | | | +| | | | | | | | +| Restoration control point
(Recommendation M.725 [17]) | | | | | | | +| | | | | | | | + +a) Language information may be included. + +FIGURE D -1/M.1510 + +**Form for the contact points for group, supergroup, etc., +digital path, block, and transmission system maintenance** + +## ANNEX E + +(to Recommendation M.1510) + +### **CONTACT POINTS FOR INTERNATIONAL SOUND-PROGRAMME AND TELEVISION TRANSMISSIONS** + +COUNTRY: + +DATE OF ISSUE: + +| Contact point | Telephone No. | Telex No. and answerback code | Facsimile No. | Service hours (UTC) | Postal address | Remarks a) | +|---------------|---------------|-------------------------------|---------------|---------------------|----------------|-----------------------| +| ISPC | | | | | | | +| | | | | | | | +| ITC | | | | | | | +| | | | | | | | +| PBC | | | | | | | +| | | | | | | | + +a) Language information may be included. + +FIGURE E-1/M.1510 + +**Form for the contact points for international sound-programme and television transmissions** + +## References + +- [1] CCITT Recommendation M.1014 *Transmission maintenance point international line (TMP-IL)*. +- [2] CCITT Recommendation M.1012 *Circuit control station for leased and special circuits*. +- [3] CCITT Recommendation M.1013 *Sub-control station for leased and special circuits*. +- [4] CCITT Recommendation N.1 *Definitions for application to international sound-programme transmissions*. +- [5] CCITT Recommendation N.51 *Definitions for application to international television transmissions*. +- [6] CCITT Recommendation D.180 *International sound- and television-programme transmissions*. +- [7] CCITT Recommendation M.75 *Technical Service*. +- [8] CCITT Recommendations M.715 to M.725 *Fault report point; testing point; network analysis point; network management point etc.* +- [9] CCITT Recommendation M.760 (will be M.4020 when revised) *Transfer link for Common Channel Signalling System No. 6*. +- [10] CCITT Recommendation M.762 (will be M.4040 when revised) *Maintenance of CCSS No. 6*. +- [11] CCITT Recommendation M.4100 *Maintenance of CCSS No. 7*. +- [12] CCITT Recommendation M.1560 *Escalation procedure for international leased circuits*. +- [13] CCITT Recommendation M.2130 *Operational procedures in locating and clearing transmission faults*. +- [14] CCITT Recommendation M.80 *Control stations*. +- [15] CCITT Recommendation M.90 *Sub-control stations*. +- [16] CCITT Recommendation M.4110 *Inter-administration agreements on CCSS No. 7*. +- [17] CCITT Recommendation M.725 *Restoration control point*. \ No newline at end of file diff --git a/marked/M/T-REC-M.1520-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1520-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..114ada82a155841895be88edabe3f0e44a987929 --- /dev/null +++ b/marked/M/T-REC-M.1520-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:568a956cd506c57e7ad41b63949aa3db1fabb2712aa3e4134d3c6c8f95742fb4 +size 8147 diff --git a/marked/M/T-REC-M.1520-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.1520-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93e1662bb0e0b41a8848e68e39e233331854118d --- /dev/null +++ b/marked/M/T-REC-M.1520-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca4b42feee4f06820a2bed23058d356f0d7e277106d819c8d1a45d208d5c51f5 +size 6844 diff --git a/marked/M/T-REC-M.1530-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1530-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/M/T-REC-M.1530-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/M/T-REC-M.1532-200002-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/marked/M/T-REC-M.1532-200002-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..334fe39425392c36c4f458ab5efff9c1440f1ff1 --- /dev/null +++ b/marked/M/T-REC-M.1532-200002-I_PDF-E/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d86b318f8f39f5a6cf263b65903f9bc91ecbbc099f486d1f22708b76dc5f93e9 +size 292928 diff --git a/marked/M/T-REC-M.1532-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1532-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/M/T-REC-M.1532-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/M/T-REC-M.1532-200002-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/M/T-REC-M.1532-200002-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e15615d636b2f164eb9d224271f04cd7af39919 --- /dev/null +++ b/marked/M/T-REC-M.1532-200002-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b11e064430a3b36f73de6261960239cd4be4f5161f54befbdd534c10f1947857 +size 15534 diff --git a/marked/M/T-REC-M.1532-200002-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg b/marked/M/T-REC-M.1532-200002-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b19f739578b5e19db6db5471e7c8d84e5b7be4d --- /dev/null +++ b/marked/M/T-REC-M.1532-200002-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9131bc734d30423f0345ff0394e33d6964c7f9bbbd70429d8bcd7c18962403 +size 148693 diff --git a/marked/M/T-REC-M.1532-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.1532-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2c2767aa72e6c618638793c4a1b1c843cec9dbb3 --- /dev/null +++ b/marked/M/T-REC-M.1532-200002-I_PDF-E/raw.md @@ -0,0 +1,794 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.1532** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Designations and information exchange + +--- + +**Network maintenance service performance +agreement (MSPA)** + +ITU-T Recommendation M.1532 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Network maintenance service performance agreement (MSPA) + +## Summary + +This ITU-T Recommendation, making reference to the basic principles of the management of the Grade Of network Maintenance Services (GOMS) at the Maintenance Service Customer Contact point (MSCC)1, provides to both a Maintenance Service Customer (MSC) and a Maintenance Service Provider (MSP) of any Maintenance Service (MS), specific guidelines to establish and manage the effectiveness of an appropriate network2 Maintenance Service Performance Agreement (MSPA). + +An MSPA is a set of appropriate procedures and targets related to specific performance parameters, action plans and relevant action points which are formally or informally agreed between an MSC and an MSP, in order to support ITU-T Recommendations and achieve and maintain the agreed GOMS under all possible operational circumstances. If both MSC and MSP wish to further improve the previously agreed GOMS, the MSPA guidelines may also be used. The MSPA may be an integral part of a contract or an informal agreement between the parties involved. + +## Source + +ITU-T Recommendation M.1532 was prepared by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000. + +## Keywords + +Action point, actions plan, grade3 of maintenance service, maintenance service4, maintenance service contract5, maintenance service customer contact point6, maintenance service customer4, maintenance service element(s)4, maintenance service informal agreement5, maintenance service performance agreement7, maintenance service performance agreement management, maintenance service performance agreement management difficulty index, maintenance service provider4, maintenance service unavailability4, management of the grade of maintenance service8, quality of service9. + +--- + +1 The GOMS concepts and its management are described in ITU-T Recommendation M.1539. + +2 The word network is used here to emphasize that the MSs are related to the entire telecommunication network and it will be avoided further within the text. + +3 For the purpose of this ITU-T Recommendation the terms: grade of service, service level, service performance are similar. + +4 The definition is reported in ITU-T Recommendation M.1539. + +5 The definition is reported in ITU-T Recommendation M.1537. + +6 For a generic service the term "Service Access Point (SAP)" is often used. + +7 Similar terms such as: "Service Level Agreement (SLA)", "Service Level Guarantee (SLG)" and "Service Quality Agreement (SQA)" are currently used in the area of telecommunications services. ITU-T Recommendation E.801, in particular, shows the main SQA concepts and the framework to be used by Network Operators/Providers and/or Service Providers for any switched or dedicated telecommunication service. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +--- + +8 The main concepts are reported in ITU-T Recommendation M.1539. + +9 In the area of concepts relating to "quality of service" and "network performance" a simple and consistent set of terms and definitions is reported in ITU-T Recommendation E.800. + +# CONTENTS + +| | Page | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Abbreviations and acronyms..... | 2 | +| 4 Terms and definitions ..... | 3 | +| 5 MSPA objectives and benefits..... | 3 | +| 6 MSPA for GOMS management..... | 4 | +| 7 MSPA overview..... | 5 | +| 7.1 MSPA Structure and basic process functions ..... | 5 | +| 7.2 MSPA implementation and operation..... | 5 | +| 7.3 MSPA Reference Model..... | 6 | +| 8 MSPA management ..... | 6 | +| 8.1 Objectives of MSPA management..... | 6 | +| 8.2 Brief overview of MSPA management..... | 6 | +| 8.3 Criteria to be used for MSPA management..... | 8 | +| 8.3.1 The MSPA Management Difficulty Index (MMDI)..... | 8 | +| 9 Examples of MSPA ..... | 10 | +| Annex A – Example of definition of MSPA Management Difficulty Index (MMDI) ..... | 10 | +| Appendix I – Examples of MSPA for Maintenance Services (MSs) related to specific
managed areas – Example of MSPA for MSs related to Leased Circuit
Service (LCS)..... | 13 | +| I.1 Introduction..... | 13 | +| I.2 MS Performance Monitoring..... | 13 | +| I.2.1 Maintenance Service Elements (MSEs) ..... | 13 | +| I.2.2 MSPA for the GOMS ..... | 13 | +| I.3 MS Performance and Fault Management..... | 14 | +| I.3.1 Maintenance Service Elements (MSEs) ..... | 14 | +| I.3.2 MSPA for GOMS ..... | 14 | +| I.4 MS Restoration ..... | 16 | +| I.4.1 Maintenance Service Elements (MSEs) ..... | 16 | +| I.4.2 MSPA for GOMS ..... | 16 | +| Appendix II – Examples of MSPA for Maintenance Services (MSs) related to specific
managed areas – Example of MSPA for MSs related to Videoconferencing service. | 16 | +| II.1 Introduction..... | 16 | +| II.2 Maintenance Service (MS) ..... | 16 | + +| | Page | | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| II.3 | Maintenance Services Elements (MSEs)..... | 16 | +| II.4 | MSPA for the GOMS ..... | 17 | +| II.4.1 | AP1: Videoconference quality improvement ..... | 17 | +| II.4.2 | AP2: Videoconferencing user training ..... | 17 | +| II.4.3 | AP3: Performance index value refreshing..... | 17 | +| Appendix III | – Examples of MSPA for Maintenance Services (MSs) related to specific
managed areas – Example of MSPA for MSs related to Internet services ..... | 17 | +| III.1 | Introduction..... | 17 | +| III.2 | Maintenance Service (MS) ..... | 17 | +| III.3 | Maintenance Services Elements (MSEs)..... | 17 | +| III.4 | MSPA for the GOMS ..... | 17 | +| III.4.1 | AP1: Performance improvement of trunk network ..... | 17 | +| III.4.2 | AP2: Performance improvement of access network..... | 18 | + +# Introduction + +In today's telecommunications environment, the provisioning of all features of any MS requires more and more an appropriate inter-operability between all the various maintenance organizations within different Network Operators/Service Providers and Customers which are involved in the MS domain concerned. In this multiple service providers situation, according to ITU-T Recommendation M.1539, in order to achieve the overall GOMS objective as agreed for any specific MS between an MSC and an MSP in a contract or in an informal agreement, it is necessary to properly manage the overall GOMS. Considering both MSC and MSP point of view, an efficient GOMS management is very important as it is strictly related to their individual business. At present, in particular, each MSP focuses to assure the "honouring at the operational level" of all contracts or informal agreements regarding any offered MS which are stipulated with every MSC. Nevertheless, in some cases, the GOMS agreed objective is very hard to attain or difficult to maintain. This is generally due to frequent instability, or sometimes to sudden drops of the performance values with respect to the specified limits/targets of one or more of the performance parameters/indices contributing to the overall GOMS. These parameters/indices are related to all procedures of each process pertaining to a particular Maintenance Service Element (MSE) within the adopted Operational Procedures Selection for the management, achievement and improvement of the agreed GOMS (OPSG). If these events of performance degradation or dropping are not analysed immediately, and their causes removed in a reasonable time, this will lead to a permanent condition of "unacceptable MS/GOMS". + +In this case, in order to achieve the overall agreed GOMS, it is necessary to review carefully all initial performance parameters regarding each procedure of involved processes and relevant performance indices, and also whether their assessments/measurements are still valid or whether they need to be revised, or completely changed with new ones. + +In the above context, the most suitable current way to manage all QoS aspects of any MS is to use an MSPA between an MSC and an MSP of the involved MS. The MSPA may be an integral part of the contract or the informal agreement between the parties concerned. An MSPA normally implies an appropriate set of procedures and targets, formally or informally agreed and signed between an MSC and an MSP in a specified actions plan, and relevant action points. Every actions plan has individual objectives and specified modalities to be carried out with a precise deadline for its completion or, when necessary, its revision or update. + +Another important issue to consider is the ever-increasing demand for an efficient MSPA management, either considering a simple situation of one MSPA or when, due to a great number of simultaneous MSPAs, to satisfy the pressure of MSPA requests, several MSPAs co-exist. To ensure an efficient management of any number of required MSPAs, it is necessary to find out suitable criteria such as the continuous evaluation of an appropriate index representing the difficulty level driven by all technical and commercial business aspects related to the MS/GOMS concerned. An efficient MSPA management may imply an increase of the operational cost above the values which were related to the previous contract or informal agreement as stipulated between the MSC and the MSP. + +It is to be noted that all concepts, methodologies, objectives and any possible target as described in an MSPA, may also be applied when more than one MSP is involved in the interested MS. That is, in particular, the case of the MS/GOMS agreed between an MSP and another MSP where, in practice, one acts as an MSC and the other as an MSP. Similar considerations apply when an MSPA is signed between Network Operators and/or between Network Operators and Service Providers. In both cases, one of the Network Operators or Service Providers plays the role of the MSP and the other the role of the MSC. + +## **Network maintenance service performance agreement (MSPA)** + +# **1 Scope** + +An MSPA provides guidelines to any MSC and MSP of the interested MS, in order to agree upon and carry out an appropriate actions plan, to ensure the effective achievement or, under specific requests, even the improvement of the GOMS. + +This ITU-T Recommendation specifies: + +- a) the MSPA general aspects to achieve the agreed GOMS based on QoS general requirements from both MSC and MSP; +- b) the MSPA structure associated with basic process functions that characterize the nature of MSPA and the MSPA reference model; +- c) MSPA management criteria and relevant objectives. + +This ITU-T Recommendation does not specify: + +- a) any value for overall GOMS or its relevant performance parameters/indices being agreed in an MSPA, or in an MSPA/contract or in an informal agreement between an MSC and an MSP; +- b) any particular action involved in an MSPA to establish and manage all types of OAM&P functions, processes and relevant procedures which in practice imply the specific implementation of an OPSG between an MSP and an MSC for the achievement of a particular GOMS; +- c) performance parameters/indices and relevant values for any specific MS. + +# **2 References** + +The following ITU-T Recommendations and other references, contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- [2] ITU-T Recommendation M.1230 (1996), *Method to improve the management of operations and maintenance processes in the International Telephone Network*. +- [3] ITU-T Recommendation M.1530 (1999), *Network maintenance information*. +- [4] ITU-T Recommendation M.1535 (1996), *Principles for maintenance information to be exchanged at customer contact point (MICC)*. +- [5] ITU-T Recommendation M.1537 (1997), *Definition of maintenance information to be exchanged at customer contact point (MICC)*. +- [6] ITU-T Recommendation M.1539 (1999), *Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC)*. +- [7] ITU-T Recommendation E.440 (1996), *Customer Satisfaction Point*. + +- [8] ITU-T Recommendation E.800 (1994), *Terms and definitions related to quality of service and network performance including dependability*. +- [9] ITU-T Recommendation E.801 (1996), *Framework for service quality agreement*. + +# 3 Abbreviations and acronyms + +This ITU-T Recommendation uses the following abbreviations and acronyms: + +| | | +|------------|------------------------------------------------------------------------------------------------------------| +| ACPL | ACTIONS PLAN | +| AP | Action Point | +| BC | Basic Characteristics of MSPA | +| FRP | Fault Report Point | +| GOMS | Grade Of Maintenance Service | +| LCS | Leased Circuit Service | +| MICC | Maintenance Information to be exchanged at the Customer Contact point 10 | +| MMDI | MSPA Management Difficulty Index | +| MS/GOMS | The GOMS related to a specific MS | +| MS | Maintenance Service | +| MSC | Maintenance Service Customer | +| MSCC | Maintenance Service Customer Contact point | +| MSE | Maintenance Service Element | +| MSP | Maintenance Service Provider | +| MSPA | Maintenance Service Performance Agreement | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OPSG | Operational Procedures Selection for the management, achievement and improvement of the GOMS 11 | +| QoS | Quality of Service | +| RFMS | Ready For Maintenance Service/GOMS date | +| RFS | Ready For Service date 12 | +| SC | Specific Characteristics of MSPA | +| $\mu$ TPMS | Mean Time to Provide a Maintenance Service/Grade Of Maintenance Service 13 | +| $\mu$ TRMS | Mean Time to Restore a Maintenance Service/Grade Of Maintenance Service 14 | + +10 The basic MICC concepts and related definitions are reported in ITU-T Recommendations M.1535 and M.1537. + +11 The OPSG concepts and relevant definition are reported in ITU-T Recommendation M.1539. + +12 This term and its abbreviation are normally used for a generic service. + +13 The concepts and definitions of Time to Provide an MS/GOMS (TPMS) and relevant indices, are reported in ITU-T Recommendation M.1539. + +14 The concepts and definitions of Time to Restore MS/GOMS (TRMS) and relevant indices, are reported in ITU-T Recommendation M.1539. + +# 4 Terms and definitions + +Terminology and definitions relating to this ITU-T Recommendation are provided in ITU-T Recommendations M.60, M.1230, M.1535, M.1537, M.1539, E.800 and E.801. This ITU-T Recommendation defines the following terms: + +**4.1 maintenance service performance agreement (MSPA):** For a specific MS, an MSPA is a particular agreement between an MSP and an MSC in order to support ITU-T Recommendations and to effectively achieve, maintain and/or also to improve, whenever it is required, the agreed GOMS as specified in the contract or in the informal agreement relating to this MS. An MSPA is a set of appropriate procedures and targets which are related to specific performance parameters/indices, action plans and relevant action points. The MSPA may be an integral part of the original contract or the informal agreement. + +**4.2 action point:** An "Action Point (AP)" is a set of appropriate sub-actions or functions, including all specifications and any necessary information belonging to a specified "actions plan", which is agreed between an MSC and an MSP in order to avoid, remove any situation of recurrent negative trend or hard to be reached for the agreed GOMS or to ensure its improvement whenever it is required. The type and/or particular characteristic of each selected AP depends on the specific conditions or events which may occur and cause to establish that the assessed/measured GOMS is not conforming to the value of the agreed GOMS objective. + +**4.3 actions plan:** An "Actions PLan" (ACPL) is a set of appropriate "Action Points (APs)" agreed for the MS/GOMS achievement or improvement purposes. It constitutes the carrying structure of an MSPA. Every ACPL has individual objectives, specified modalities to be carried out and precise dead-line when it must be considered completed or it is necessary to review it and/or to make its update. + +**4.4 MSPA management difficulty index (MMDI):** The MMDI is an index which represents a current difficulty level to manage efficiently at the MSCC one MSPA or several MSPAs which may co-exist simultaneously. When the MMDI is low, the MSPA is managed efficiently and when it is high the MSPA is managed inefficiently. + +# 5 MSPA objectives and benefits + +For any MS, the main objectives of an MSPA are: + +- 1) to allow the conformance achievement of the agreed GOMS. This permits, in particular, to the MSP to effectively "honour the contract at the operational level"; +- 2) to stabilize and regularly review the validity or real effectiveness of the OPSG used for the achievement of the agreed GOMS. This means that both the MSC and the MSP will be able to carry out a systematic update of any network and service resource, that is the implementation of any modification or additional procedure within the OPSG previously adopted; +- 3) to obtain, on the basis of the optimization as indicated in the aforesaid item 2), a significant cost-saving for both the MSC and the MSP; +- 4) to improve further the understanding and cooperation between an MSC and an MSP for any technical and commercial aspects of the MS concerned and particularly for the issues regarding the GOMS and its goals. + +The introduction of an MSPA provides to both an MSC and an MSP the following main benefits: + +- 1) the continuous optimization of the use of all their own resources employed in the involved MS; +- 2) the identification of an ever increasing positive influence for their MSs costs and specific business applications. + +# 6 MSPA for GOMS management + +For a specific MS/GOMS, an MSPA normally involves the establishment, carrying out, follow-up and administering of an appropriate ACPL. This ACPL must be applied in order to solve GOMS specific degradation or sudden drops which might imply that its agreed value/target may not be achieved. Whatever will be the choice of this ACPL, in all cases, it will help to solve misunderstanding or subsequent GOMS assessment/measurement problems both to MSC and MSP. + +It must be emphasized that even though the MSPA is mainly GOMS oriented, it has normally strict linkages to commercial conditions and also to business aspects of the MS contract for both MSC and MSP. + +Therefore, any information regarding the GOMS management and particularly the results of its continuous assessment and any stability problem must be collected, recorded, and reported15. Any type of impairment cause and its localization shall also be identified and stored for any future MSPA reference or statistical purpose. + +When it is ascertained a persistent GOMS instability or sudden drops of the performance values lasting for a significant time and this situation may impact the achievement of the agreed MS/GOMS. For the involved MS, both MSC and MSP should act as follows: + +- 1) If the MSPA already exists (i.e. it is already an integral part of the contract or the informal agreement), both MSC and MSP promptly and carefully check all procedures and performance parameters involved in the APs for which they are specifically responsible. When this activity is completed the GOMS instability causes should be clearly identified and removed. Suitable tests shall be carried out jointly by the MSC and the MSP to confirm GOMS instability was definitively removed. If the duration of this GOMS instability exceeds an agreed time as specified in the MSPA, the relevant operational managers in charge for the MSC and MSP respectively, shall request, according to the severity of the problem, either directly or using specified escalation procedures, an immediate and appropriate revision of the previous agreed ACPL and all relevant APs. This revision must be invoked, independently of the agreed time and relevant periodical update as scheduled in the MSPA. It is to be emphasized that any data/information regarding the monitoring, assessment or measurement of each performance index during GOMS instability, and all localization and clearance details of problems, must be collected, recorded and reported according to the specifications contained in the MSPA. +- 2) If the MSPA does not exist, both MSC and MSP will promptly evaluate the technical-economical convenience of its implementation. Should both parties confirm this convenience, a specific MSPA shall be agreed on and managed according to the same MS/GOMS instability checks and removal operational procedures as described at item 1) above. + +All principles contained in an MSPA are strictly related to the management of the agreed MS/GOMS. The structure and detailed procedures of an MSPA follow the general principles of the OPSG for the management of the GOMS. It is to be noted that the performance requirements of all parameters/indices in the MSPA for GOMS management are more stringent and require supplementary features compared to those at the time agreed/stipulated according to ITU-T Recommendation M.1539. + +--- + +15 A list of useful information, based on the different nature of the events and their priority in information exchange between maintenance involved people, including MSC, is shown in ITU-T Recommendation M.1530. For telecommunications services, examples of procedures for the exchange of information with the customer is reported in ITU-T Recommendation E.440. + +# 7 MSPA overview + +## 7.1 MSPA Structure and basic process functions + +The basic structure of an MSPA related to an MS usually consists of two parts. The first contains the general principles, scope, aspects related to its confidentiality and legal status, its reviewing periodicity, the signatures of responsible people within both MSC and MSP organizations and any further general information as needed (e.g. criteria to establish the contact points managing the MSPA, any possible escalation principles and relevant procedure). The second part contains the ACPL regarding the agreed MS performance parameters/indices to be monitored and verified at the MSCC within the involved OPSG. For example, some of these performance parameters/indices are: MS/GOMS Availability; Mean Time to Provide MS/GOMS ( $\mu$ TPMS); Mean Time to Restore MS/GOMS ( $\mu$ TRMS); Ready For MS/GOMS date (RFMS). The aforesaid ACPL normally includes: the definitions of all performance parameters/indices; the adopted monitoring and management criteria, including relevant data collection, recording and reporting procedures; performance measurements and any possible target value; additional information which is useful to easily operate and manage the MSPA (e.g. contact name details of people managing operational aspects of the MSPA, escalation points and relevant people, reference/historical data). + +Any identified operational problem of the performance parameters/indices while managing an MSPA, must be classified in a set of indices of different types (e.g. technical, commercial) related to the reason and nature of this problem. These reasons should be then analysed in-depth and correlated with a certain number of topics or specific measures to be carried out, monitored, followed-up, reported and reviewed periodically after their introduction or implementation within the revised contract or informal agreement. These constitute "Action Points (APs)". Each AP contains characteristics (i.e. sub-activities) which are "basic"(BC) and "specific"(SC). Each BC is described with the following information: the whole description, scope, objectives, duration of time to be carried out, responsible people interested in all sub-functions needed in the different phases of the MSPA, any possible value of performance parameters resulting from specific assessments and/or measurements and the time when the AP should be periodically reviewed. Any necessary further information to complete the AP is part of the SC. + +The following is some of the main important operational information: + +- 1) Responsibility for the AP: Name(s) of the people who are responsible for the AP, MSPA signature, its implementation, coordination and reviewing. This information should also include all necessary contact points/person details to manage the whole MSPA (e.g. postal mail, telephone, facsimile numbers, paging, e-mail of all APs managers involved). +- 2) Operative duration (or validity) of the AP: i.e. start and end dates and in some cases the time and hours when the AP is planned to be completely carried out or reviewed. +- 3) Priority for the completion of the AP if a certain number of APs should be carried out simultaneously. +- 4) Detailed description of the AP, including all criteria for the assessment or measurement of its effectiveness. +- 5) Operative status of the AP, completed/discharged or ongoing. +- 6) Date of AP implementation, its periodical reviewing and its completion. + +## 7.2 MSPA implementation and operation + +Two main phases can be identified for the lifecycle of an MSPA: + +- 1) Implementation phase: This phase, starts when either the MSC or the MSP present a formal request for the MSPA implementation and it ends when it is possible to start the MSPA operation. Therefore this phase produces a technical-commercial validation in order to + +ascertain the real benefits of activating the new MSPA for both the MSC and the MSP. Furthermore, this phase is characterized by BCs which are constituted by relevant process functions and their mutual interactions during various phases ending with the effective initialization of the MSPA. + +- 2) Operation phase: It represents the MSPA operational status, including either its "in operation" and "termination". It starts whenever the implementation phase is completed and it ends when both the MSC and the MSP agree to perform formally re-operations or terminations. During this operation phase, MSPA application of all rules, measures, ACPL reviewing and any other update of all involved criteria are carried out. This phase also implies the utilization of specified BCs during the various operations phases ending with the decommissioning of any involved ACPL, relevant APs and the formal termination of the MSPA itself. + +For both the implementation and operation phases, the main BCs are described in 7.1. + +## 7.3 MSPA Reference Model + +Figure 1 shows the MSPA Reference Model. With reference to a determined MSPA for a specific MS, any selected ACPL contains a certain number of APs. Each AP is related to a certain specific time duration and it is associated with a defined number of resources, relevant processes and procedures. APs are performed according to a certain list of BCs (e.g. from BC 1 to BC m) and SCs (e.g. from SC1 to SCn). This list is common to all APs of each ACPL (i.e. to "N " APs for ACPL 1). A similar situation exists after a certain period and a revised or new plan is put in place. When the MSPA is terminated all resources are released for any other APs when necessary. + +![Figure 1/M.1532 – Reference model of MSPA. The diagram shows a hierarchical structure starting with MSPA at the top. It branches into ACPL1 and ACPL_M. ACPL1 branches into AP11 and AP1N. AP11 branches into BC1 and SC11. AP1N branches into BC1 and SCN1. ACPL_M branches into BC1 and SCNw. The diagram is labeled T0411780-99.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` + +graph TD + MSPA[MSPA] --- ACPL1[ACPL1] + MSPA --- ACPL_M[ACPLM] + ACPL1 --- AP11[AP11] + ACPL1 --- AP1N[AP1N] + AP11 --- BC1_1[BC1] + AP11 --- SC11[SC11] + AP1N --- BC1_N[BC1] + AP1N --- SCN1[SCN1] + ACPL_M --- BC1_M[BC1] + ACPL_M --- SCNw[SCNw] + BC1_1 -.-> BCm_1[BCm] + SC11 -.-> SC1n[SC1n] + BC1_N -.-> BCm_N[BCm] + SCN1 -.-> SCNw + T0411780-99[T0411780-99] + +``` + +Figure 1/M.1532 – Reference model of MSPA. The diagram shows a hierarchical structure starting with MSPA at the top. It branches into ACPL1 and ACPL\_M. ACPL1 branches into AP11 and AP1N. AP11 branches into BC1 and SC11. AP1N branches into BC1 and SCN1. ACPL\_M branches into BC1 and SCNw. The diagram is labeled T0411780-99. + +Figure 1/M.1532 – Reference model of MSPA + +# 8 MSPA management + +## 8.1 Objectives of MSPA management + +Both an MSC and an MSP need to find out the most suitable way to assure an efficient MSPA management. The main objective of MSPA management is a continuous optimization of the total number of the MSPAs, their constituent ACPL(s) and relevant APs which may be simultaneously in place. + +## 8.2 Brief overview of MSPA management + +For any involved MS, once the relevant GOMS has been specified and agreed between an MSC and an MSP in a contract or in an informal agreement, it is provided by the MSP at the MSCC. In order to manage the agreed GOMS the adopted OPSG, together with a specified MSPA which is characterized by a particular ACPL, may or not be determined as integral part of the agreement. + +Each of these actions is univocally and clearly defined and also their own deadline must be established. Both MSP and MSC continuously apply by their own the agreed criteria, methods, performance parameters/indices and the relevant limits/thresholds in order to carry out the GOMS assessment (i.e. specific measurements and evaluation) and the verification of its conformance to the agreed value/level. Whenever a situation of high and persistent instability of the GOMS exists, both MSC and MSP carry out all APs for which they are respectively responsible described in the MSPA. + +At the completion of these actions both parties verify if the GOMS instability is still present or has been removed. If the GOMS stability is still critical, they must promptly agree further actions or, in some cases, agree quickly to a completely new ACPL through MSPA management. + +Furthermore, as illustrated in Figure 2, which shows the MSPA management cycle for MSs, the continuous assessment of the GOMS value/target, implies that the MSPA which originally started to be operative at the implementation time " $t_i$ " (i.e. $MSPA_{t_i}$ ) is subsequently different at any other revision time " $t_r$ " when it will be submitted to a verification to ascertain its validity and/or completion (i.e. $MSPA_{t_r}$ ). + +Referring to any MS, in order to identify univocally the functional block defining a specific MS/GOMS as agreed in a contract or in an informal agreement, it is necessary to define the following: + +- MS type and relevant characteristics; +- MSC type and relevant characteristics; +- MSP type and relevant characteristics; +- OAM&P resources performance statistics; +- GOMS performance parameters/indices and their objectives; +- GOMS contract or informal agreement limits/targets; +- MSEs performance statistics; +- MSPA establishment and initiation of its management at the same time or after the contract or the informal agreement is stipulated. + +When the MS/GOMS becomes effective, the MSPA at $t_i$ is referenced to achieve the agreed GOMS. According to the MS/GOMS, both the MSC and the MSP perform monitoring, measurements, assessments, reporting and storage to assure the agreed GOMS achievement, while MSPA management takes place to apply the MSPA at $t_i$ . Continuous activities taken by both MSC and MSP provide feedback to MSPA management on the validity of MSPA at $t_i$ . When the revision of MSPA at $t_i$ is requested by both the MSC and the MSP, a new MSPA at $t_r$ is constituted. After installing this new MSPA, the MSC and the MSP resume activities to assure the agreed GOMS achievement. + +Information that improved the MSPA is archived as "Recommended MSPA specifications" and it is applied to constitute or support MSPAs. + +![Figure 2/M.1532 – Overview of the MSPA management cycle for MSs](71ab4df17511d75261da8d462d643b1a_img.jpg) + +``` + +graph TD + subgraph Inputs + MSC_Char[MSC type and relevant characteristics] + MSP_Char[MSP type and relevant characteristics] + OAM_Res[OAM&P resources performance statistics] + MS_Char[MS type and relevant characteristics] + GOMS_Perf[GOMS performance parameters/indices and their Objectives] + GOMS_Cont[GOMS contract or informal agreement limits/targets] + MSE_Perf[MSEs performance statistics] + end + + Contract[MS/GOMS Contract or Informal Agreement] --> MSPA_ti[MSPA at t_i] + Inputs --> Contract + + MSPA_ti -- Apply --> MSC_Own[MSC own MS/GOMS Monitoring, Measurements, Assessments, Reporting and Storage] + MSPA_ti -- Apply --> MSP_Own[MSP own MS/GOMS Monitoring, Measurements, Assessments, Reporting and Storage] + + MSC_Own -- Feedback --> MSPA_Mgmt[MSPA Management Implementation and Follow-up of an ad hoc Actions Plan] + MSP_Own -- Feedback --> MSPA_Mgmt + MSPA_Mgmt -- Apply --> MSC_Own + MSPA_Mgmt -- Apply --> MSP_Own + + MSC_Own -- Feedback --> MSPA_tr[MSPA at t_r] + MSP_Own -- Feedback --> MSPA_tr + MSPA_Mgmt -- Apply --> MSPA_tr + + MSPA_tr -- Apply --> Cont_MSPA[Continued MSPA Implementation and follow-up of revised or new ad hoc Actions Plan] + + Cont_MSPA -- Feedback --> Rec_Specs[(Recommended MSPA Specifications)] + MSP_Own -- Feedback --> Rec_Specs + Rec_Specs -- Apply --> Cont_MSPA + Rec_Specs -- Feedback --> MSPA_ti + +``` + +**Figure 2/M.1532 – Overview of the MSPA management cycle for MSs** + +Figure 2/M.1532 – Overview of the MSPA management cycle for MSs + +### 8.3 Criteria to be used for MSPA management + +#### 8.3.1 The MSPA Management Difficulty Index (MMDI) + +For any MS and GOMS value objective as agreed between an MSC and an MSP in one or more MSPAs relevant to a specific amount of contracts and/or informal agreements, the associated MMDI16 represents an overall index which permits, with respect to a stated and measured level of difficulty, to evaluate the probability to efficiently manage the real technical and economical convenience for the retainability of each existing MSPA or the implementation of a new one. The use of MMDI also allows to monitor continuously the achievement of GOMS objectives or its stability status. It is important to note that the "MSPA management efficiency" varies inversely with MMDI, i.e. when: + +- "GOMS achievement (stability)" is good (MMDI low), "MSPA management efficiency" is high; +- "GOMS achievement (stability)" is bad (MMDI high), "MSPA management efficiency" is low. + +--- + +16 The definition and use of a similar "Difficulty Index" used for the optimization of the management of all network and human resources involved in the Maintenance domain, including the relevant processes and procedures, can be found in ITU-T Recommendation M.1230. + +8 **ITU-T M.1532 (02/2000)** + +At any time "t", it is possible to define the MMDI as a set of suitable factors which may be expressed and combined with a more or less simple mathematical law of variation. The definition of these factors, their values, range of variation and their combination for MMDI computation mainly depend on the particular MS type/characteristics and the effective level of network performance and QoS, i.e. the GOMS which, according to specific business purposes, is agreed upon by an MSP and an MSC in an appropriate MSPA itself. The most used formula for the aforesaid combination of factors is a simple normalized formula where each factor "Yi" is specified as a function "Fi" of a specific index "Xi" related to a correspondent characteristic agreed in the contract or in the informal agreement. In some cases, the involved functions "F" may be the same either for a set or the total, of the "X" indices interested. Namely, at a certain time "t": + +$$MMDI = \frac{\sum_{i=1}^n P_i Y_i}{\sum_{i=1}^n P_i}$$ + +where: + +- 1) $Y_i = F_i(X_i)$ ; +- 2) $P_i$ = weight of the "i" factor $Y_i$ . + +With reference to each type of MS, independently of the particular GOMS to be achieved and taking into consideration a generic average customer, a typical MSPA and relevant mean life-duration, the following are main technical and commercial factors which usually need to be considered for the MMDI definition and computation: + +- 1) The overall cost of one MSPA or its average value, when several MSPA co-exist, per MSC; +- 2) The total number of contracts and informal agreements per MSC; +- 3) The total number of contracts and informal agreements with an MSPA per MSC; +- 4) The different types and total number of GOMS involved in all MSPAs, per MSC. For this factor, it is quite common and useful to practically establish a precise classification and limited number of possible achievable values of GOMS (e.g. using different scale indices); +- 5) The different type, level/threshold of the "MSPA management efficiency" per MSC, taking into account any additional cost which MSPAs may imply with respect to the cost of normal MS contracts or informal agreements (e.g. using different scale indices). + +For a specific MS, one of the most simple and significant factor to assess, at any time, if both "GOMS achievement/stability" and "MSPA management efficiency" are good (MMDI low), is the current value of the "Percentage of MSPAs" over the total number of contracts or informal agreements which exist at that time for this MS. Namely: + +$$\text{Percentage of MSPAs} = \frac{(\text{Total number of MSPA})}{(\text{Total number of contracts + informal agreements})} \times 100$$ + +The following two main conditions may occur: + +- When this ratio is greater than a certain value or it has a positive trend towards 100% or it becomes equal to 100%, then GOMS values for all the MS contracts for each involved MSC are always quite unstable/critical to be achieved or there is a steady status where several MSCs are all requesting a contemporaneous GOMS improvement to the involved MSP. + +This condition corresponds to the highest probability to have a poor or bad MSPAs management efficiency. That represents the "worst case" to be avoided as much as possible, and which shall be promptly faced and removed because its permanence, will quickly lead to recurrent high new investments from the MSP in order to ensure continuous adequate adjustments of all involved MSEs, relevant processes and procedures of the selected OPSG. + +- When the value of this ratio becomes low or very close to zero, it will imply that almost all agreed GOMS in the existing contracts or informal agreements are quite stable and their agreed objective values may be achieved without any particular difficulty. The continuous use of the MMDI also permits both the MSC and the MSP, to estimate with a good level of confidence, the success probability to continue managing efficiently the total number of MSPAs. As a matter of fact, this number is continuously varying because additional MSPAs may be required at any time. Taking into consideration that all factors of MMDI are strictly dependent on both technical and commercial - business aspects, its overall value may have a continuous fluctuation. Therefore, it is fundamental to follow the MMDI value according to any MS/GOMS specific change or new requirement. + +# 9 Examples of MSPA + +An MSPA may, in general, be applied to all GOMS with different scale (from a best to a poorest) and relative to specific MSs. The ACPL, and relevant APs constituting an MSP, are usually selected taking into account the MSC requirement, the MS type and also the particular telecommunication service characteristic to which it is normally applied. Some MSPA examples for MSs related to specific managed areas are reported in the Appendices I, II and III. These deal respectively with Leased Circuit Service (LCS), Videoconferencing and Internet services. A summary description of some main MSEs and relevant APs is provided in each appendix. + +# ANNEX A + +## Example of definition of MSPA Management Difficulty Index (MMDI) + +This example refers to a case where an efficient MSPA management regarding a specific MS, can be made using a set of only four significant factors having the same weight (i.e. $p=p1=p2=p3=p4$ ) and also the possibility to use the same transform function $F$ of the relevant four involved $X$ indices is assumed (i.e. $F=F1=F2=F3=F4$ ) namely: + +### Four MMDI components: + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------| +| 1) MSPA ratio per total Agreements (contract + Informal Agreements) per MSC. | X1: MSPA existence index. | $Y1 = F (X1)$ | +| 2) MSPA to MS ratio per MSC. | X2: MSPA existence per MS index. | $Y2 = F (X2)$ | +| 3) MSPA to GOMS different scale ratio per MSC.
Ratio to be calculated for each five GOMS scale levels [from (1) to (5)]. | X3: MSPA existence per GOMS scale index. | $Y3 = F (X3)$ | +| 4) Mean additional cost for MSPA per GOMS different scale ratio per MSC, with respect to the similar mean cost without MSPA.
Ratio to be calculated for each five GOMS scale levels [from (1) to (5)]. | X4: MSPA cost index. | $Y4 = F (X4)$ | + +F transforms the four MMDI difficulty component values into an overall GOMS scale index which has a range from (1) to (5), that is: + +| GOMS scale index | Description | +|------------------|-------------------------| +| (1) | acceptable-excellent | +| (2) | acceptable-good | +| (3) | acceptable-sufficient | +| (4) | partially-unacceptable | +| (5) | completely-unacceptable | + +For each MSPA as involved, values of MMDI components can be computed. Then MSPAs (related to contracts and/or informal agreements) are classified into five different ranges according to these values. The MSPAs with the best MS/GOMS are assigned with the index (1) and the poorest are assigned with the index (5). In this way if MMDI is high, the MSPA management is inefficient, if MMDI is low, the MSPA management is efficient/good. + +**MMDI computation:** $MMDI = (Y1 + Y2 + Y3 + Y4)/4$ + +Figure A.1 shows a general diagram of the MSPA management using this example of MMDI based on four significant factors. The concepts are represented at two different instants, i.e. the initial time " $t_i$ ", when the total number of MSPA to be managed is $N_i$ and the revision time " $t_r$ " when the same number is equal to $N_r$ . In this case, as all four factors are also considered with the same weight, the MMDI can simply be expressed as their arithmetic mean. + +![General diagram of MSPA management using an MMDI based on four components. The diagram shows two parallel structures for time 't_i' and time 't_r'. Each structure includes a hierarchy of MSCs, MSs, and MSPs, leading to four components (Y1-Y4) that are averaged to find the MMDI. A legend at the bottom defines the abbreviations.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +The diagram illustrates the management of Maintenance Service Performance Agreements (MSPA) using a Maintenance Management Difficulty Index (MMDI). It is divided into two main sections representing different time points: $t_i$ (implementation time) and $t_r$ (revision time). + +**Structure at time $t_i$ :** + +- Top Level:** A hierarchy of Maintenance Service Customers (MSCs) labeled $MSC_A, MSC_j, MSC_Z$ . Each MSC is connected to a Maintenance Service (MS) labeled $MS_a, MS_i, MS_z$ . These are linked to 'Contract or Informal Agreement' blocks containing Grade Of Maintenance Service (GOMS) indices: $GOMS_{Ai}, GOMS_{Ji}, GOMS_{Zi}$ . +- MSP Management:** A dashed line labeled **MSCC** (Maintenance Service Customer Contact point) encircles the agreements, labeled 'Management of a number of $N_i$ MSPAs at " $t_i$ "' under a Maintenance Service Provider $MSP_T$ . +- Component Calculation:** Below the MSP management, four components are calculated: + - $Y1 = F(X1)$ → MSPA ratio per Total Agreements per MSC $(MSPA_{TOT} / MSC_{TOT})$ in percentage + - $Y2 = F(X2)$ → MSPA to MS per MSC $(MSPA_{TOT} / MS_{TOT})$ in percentage + - $Y3 = F(X3)$ → MSPA to GOMS different scale ratio per MSC $(MSPA_{TOT} / GOMS\ scale)$ in percentage + - $Y4 = F(X4)$ → Mean additional Cost × MSPA per GOMS different scale ratio per MSC with respect to the similar cost without MSPA +- MMDI Calculation:** The components are averaged to find the MMDI at $t_i$ : $MMDI = (Y1 + Y2 + Y3 + Y4)/4$ . + +**Structure at time $t_r$ :** This structure is identical to the one at $t_i$ , but with $N_r$ MSPAs at time $t_r$ . + +**Legend:** + +- MS: Maintenance Service (from a to z) +- MSC: Maintenance Service Customer (from A to Z) +- MSCC: Maintenance Service Customer Contact point +- MSP: Maintenance Service Provider (from K to T) +- MSPA: Maintenance Service Performance Agreement +- MMDI: MSPA Management Difficulty Index +- GOMS: Grade Of Maintenance Service +- $t_i$ : implementation time +- $t_r$ : revision time + +**Notes:** + +- total number = $N_i$ at the time " $t_i$ " and $N_r$ at the time " $t_r$ " +- at any time, an MMDI based on four components/factors is considered in this example +- for the involved service " $MS_i$ " and for each MSC, only five different scale indices are considered in this example + +time → +T0411800-99 + +General diagram of MSPA management using an MMDI based on four components. The diagram shows two parallel structures for time 't\_i' and time 't\_r'. Each structure includes a hierarchy of MSCs, MSs, and MSPs, leading to four components (Y1-Y4) that are averaged to find the MMDI. A legend at the bottom defines the abbreviations. + +Figure A.1/M.1532 – General diagram of MSPA management using an MMDI based on four components + +# APPENDIX I + +## **Examples of MSPA for Maintenance Services (MSs) related to specific managed areas** + +### **Example of MSPA for MSs related to Leased Circuit Service (LCS)** + +### **I.1 Introduction** + +LCS provide proprietary data transmission capability (i.e. different transmission capacity) from an MSP to private business customers (MSCs). Some of the most significant MSPA issues regarding "MS Performance Monitoring", "MS Performance and Fault Management" and "MS Restoration" which represent the main Maintenance Services (MSs) in this communication services domain are shown in this appendix. + +### **I.2 MS Performance Monitoring** + +#### **I.2.1 Maintenance Service Elements (MSEs)** + +The following main MSEs constitute this MS: + +- MSE1: To guarantee the availability of all network elements and any other equipment involved in normal conditions including all types of OAM&P functions and relevant procedures; +- MSE2: To ensure the availability of any redundant or spare part of the network elements including all OAM&P functions and relevant procedures; +- MSE3: To assure the capability of measuring any LCS performance parameters (e.g. US, ES, SES) including data collection, recording and storage for statistical purposes or any other subsequent action; +- MSE4: To monitor the correct operation of any centralized system (e.g. general main alarms for time synchronization failure). + +#### **I.2.2 MSPA for the GOMS** + +##### **I.2.2.1 AP1: 24 hour basis continuous monitoring** + +When performance degradation is reported from an MSC, this action is taken to obtain times and occurrences of any unavailability event of all parameters related to network elements (e.g. Digital Access Cross Connection System, ADM, ADPCM, DCME, Network Termination Unit). + +##### **I.2.2.2 AP2: Spare equipment restoration** + +When the number of spare equipment becomes lower than a specified threshold which may impact the expected/designed value associated with the agreed GOMS, this action is taken to avoid the shortage of spare equipment. + +##### **I.2.2.3 AP3: MSCC availability verification** + +When problems in accessing and operating at the MSCC are identified, this action is taken to check and verify times and occurrence of problem accessing and operating at the MSCC (e.g. maximum delay to transfer and retrieve information on MS/GOMS states and relevant LCS performance values). + +##### **I.2.2.4 AP4: Monitoring data exchange** + +When performance data are requested, this action is taken to exchange or report any monitoring data result, and particularly those regarding special days or events of high priority or importance at the MSCC, within a specified time. + +##### **I.2.2.5 AP5: Performance monitoring in general** + +This action consists of in-service techniques and alarm monitoring and diagnosis. This action is taken when needed. + +##### **I.2.2.6 AP6: Interval reporting** + +This action makes all measurements and reporting on a specified time interval basis in order to facilitate correlation analysis of any MSE component behaviour and the LCS performance. + +##### **I.2.2.7 AP7: Out of service testing** + +Out of service techniques for assessing the cause for MSE performance degradation composes this action. This action is taken with a formalized acceptance of the MSC or when the LCS has returned to its original performance (e.g. through an automatic restoration of a faulty network or sub-network component of MSE involved in original LCS network configuration.) + +##### **I.2.2.8 AP8: Remedies/penalties** + +This action is taken when the mean time and rate of its performance degradation exceeds a specified value. In all cases the LCS degradation events shall be clearly due to performance degradation state that is localized in one or more of the network components constituting the MSEs. + +##### **I.2.2.9 AP9: Escalation procedures** + +In all degradation circumstances of a specified LCS, in a certain operation period, this action is taken only when: + +- Specified thresholds of the absolute or average duration time of the LCS performance degradation time or its frequency, are exceeded. All LCS degradation events must be attributed to performance problems related to any component of the involved MSEs. +- Specified thresholds of the absolute or average duration time of the LCS performance degradation, or its rate, are identified without any reason or precise localization. All LCS degradation events must be attributed to performance problems related to any component of the involved MSEs. + +### **I.3 MS Performance and Fault Management** + +#### **I.3.1 Maintenance Service Elements (MSEs)** + +The main MSE of this MS is as follows: + +- MSE1: To guarantee the availability of all network elements and any other equipment involved in normal conditions, including the correct application of all OAM&P functions and relevant procedures used for the correct operation of LCS. + +#### **I.3.2 MSPA for GOMS** + +##### **I.3.2.1 AP1: Opening trouble ticket** + +When any performance index value is lower than the expected/designed value associated with the agreed GOMS, this action is taken to record the fault data and time of the event occurrence. + +##### **I.3.2.2 AP2: Trouble ticket management** + +Once the trouble ticket is opened, this action is taken. This action includes agreed procedures of Reception, Diagnostics, Undertake Repair and Clear-Close. + +##### **I.3.2.3 AP3: Fault report point establishment** + +When a fault occurs, this action is taken to establish a Fault Report Point (FRP) that provides 24 hours per day, 365 days per year, contact for operations entities of MSP and MSC. + +##### **I.3.2.4 AP4: Fault localization and restoration** + +When the FRP is established, this action is taken to initiate fault localization and restoration. + +##### **I.3.2.5 AP5: Fault reporting** + +When customer has a service fault, this action is taken by the customer to report about one of the following states: + +- 1) Permanent and complete loss of the service; +- 2) Intermittent loss or degradation of the service. + +##### **I.3.2.6 AP6: Fault information exchange** + +When a particular investigation is needed, this action is taken to exchange fault information on circuits. + +##### **I.3.2.7 AP7: Fault-related information recording** + +When an initial contact to the FRP is made by the MSC, this action is taken to record the following information: + +- a) Name or identifier code of customer's organization; +- b) Name of customer reporting the fault; +- c) Contact details of the customer reporting the fault (e.g. telephone, facsimile, e-mail numbers); +- d) Time of the fault report in UTC; +- e) Circuit designation of faulty circuit; +- f) Symptoms of fault; +- g) Duration of fault as observed before the fault was reported; +- h) Agreement with the customer that the circuit can be withdrawn from service. +- i) How and where the fault was first noticed; +- j) A fault reference number to be used in all future contacts. + +Even if the fault is suspected to be within a network of a specific Network Operator/Service Provider, all fault reports must be communicated to the relevant remote Control Center or FRP (e.g. via telephone, facsimile). + +### **I.4 MS Restoration** + +#### **I.4.1 Maintenance Service Elements (MSEs)** + +The main MSEs of this MS are: + +- MSE1: To provide additional restoration capability of all OAM&P resources (e.g. transmission capacity) used for the involved LCS in order to ensure the restoration to the original conditions whenever it is necessary; +- MSE2: To manage all operations required to restore the original MS capabilities and transmission capacity involved by the LCS. + +#### **I.4.2 MSPA for GOMS** + +##### **I.4.2.1 AP1: Restoration expedition** + +When restoration time of capability is critical, this action is taken to speed up the Fault clearance. The mean time to restore the capability to operate all the interested LCS within a specified limit is used to capture the level of restoration. In addition, all tests are coordinated between the FRP and customer. + +##### **I.4.2.2 AP2: Circuit restoration** + +When a circuit restoration is necessary, this action is taken. The circuit restoration can be made using agreed automatic and/or manual plans. A restoration plan is an appropriate set of pre-arranged actions which are performed in case of failures. + +##### **I.4.2.3 AP3: Spare LCS use** + +When the unavailable time needs to be minimized, this action is taken. In this action the FRP uses a spare LCS and an additional monitoring period (e.g. three months) in order to ensure that the problem found was the only one that caused the fault. + +## **APPENDIX II** + +## **Examples of MSPA for Maintenance Services (MSs) related to specific managed areas** + +### **Example of MSPA for MSs related to Videoconferencing service** + +### **II.1 Introduction** + +Videoconferencing service provides a multipoint videoconferencing capability from an MSP to registered customers (MSCs) on reservation basis. + +### **II.2 Maintenance Service (MS)** + +"Guaranteed multipoint videoconferencing service" is a potential MS. + +### **II.3 Maintenance Services Elements (MSEs)** + +The following MSEs and relevant performance indices constitute GOMS for this MS: + +- MSE1: To guarantee the conference start time with performance indices, conference start time delay and number of conference operation troubles; +- MSE2: To identify trouble at customer site with performance indices, test achievement ratio and customer's trouble number; + +- MSE3: To back-up customer conference site with performance indices, restored customer site ratio and additional resource allocation time. + +### **II.4 MSPA for the GOMS** + +#### **II.4.1 AP1: Videoconference quality improvement** + +When any performance index value is lower than the expected/designed value relating to the agreed GOMS, this action is taken to improve the service quality. + +#### **II.4.2 AP2: Videoconferencing user training** + +When the recovered customer ratio is degraded with respect to the value established to achieve the agreed GOMS, this action is taken to improve the customer ability to use videoconferencing facility. + +#### **II.4.3 AP3: Performance index value refreshing** + +When the average start time delay exceeds the agreed GOMS value and the quality improvement action is taken and confirmed, this action is performed to initialize evaluation process. + +## **APPENDIX III** + +## **Examples of MSPA for Maintenance Services (MSs) related to specific managed areas** + +### **Example of MSPA for MSs related to Internet services** + +### **III.1 Introduction** + +Internet services provide data transmission capability of using IP to customers. + +### **III.2 Maintenance Service (MS)** + +"Guaranteed data transmission service" is a potential MS. + +### **III.3 Maintenance Services Elements (MSEs)** + +The following MSEs and relevant performance indices constitute GOMS for this MS: + +- MSE1: To manage data transmission for a trunk network in terms of the lower bit-rate bound over a specified percent of specified duration, this MSE undertakes performance measurements including throughput and alarm monitoring of all resources involved in trunk network; +- MSE2: To manage data transmission for an access line network, this MSE undertakes performance measurement including throughput and alarm monitoring of access network. + +### **III.4 MSPA for the GOMS** + +#### **III.4.1 AP1: Performance improvement of trunk network** + +If the trunk network performance becomes lower than the expected/designed value relating to the agreed GOMS, this action is taken to improve the performance through cause analysis of low performance and appropriate actions such as network resource restoration. + +#### **III.4.2 AP2: Performance improvement of access network** + +If the access line network performance becomes lower than the expected/designed value associated with the agreed GOMS, this action is taken to improve the performance through cause analysis of low performance and appropriate actions such as network resource restoration. + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.1535-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1535-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a89ffc6680f0d7ee424068fe7300299b1c05fa4 --- /dev/null +++ b/marked/M/T-REC-M.1535-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:104e9f6b5b45fa1073a17e325004437e1c8e4314b9de4021d0c4fbcb847d42fe +size 8276 diff --git a/marked/M/T-REC-M.1535-199605-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/M/T-REC-M.1535-199605-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c64274d98333f6c3fb34e42c59e02eaa1bff46a9 --- /dev/null +++ b/marked/M/T-REC-M.1535-199605-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3d5637dc61e92c0c044defdb85c6ad8e52bad18827034d488ec914a9d49fcf6 +size 139214 diff --git a/marked/M/T-REC-M.1535-199605-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.1535-199605-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7224fa75a37e48f7c6174102aca9d7d548ef718 --- /dev/null +++ b/marked/M/T-REC-M.1535-199605-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a195c7e58beb7c891523a2304c7629be952166154fb01f040179d7b3f3651009 +size 90751 diff --git a/marked/M/T-REC-M.1537-199710-I_PDF-E/raw.md b/marked/M/T-REC-M.1537-199710-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f71d34d375f1b228191361de8f09d9594fd69bda --- /dev/null +++ b/marked/M/T-REC-M.1537-199710-I_PDF-E/raw.md @@ -0,0 +1,618 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt symbol.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt symbol. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.1537** + +(10/97) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Designations and information exchange + +--- + +**Definition of maintenance information to be +exchanged at customer contact point (MICC)** + +ITU-T Recommendation M.1537 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.1537** + +# **DEFINITION OF MAINTENANCE INFORMATION TO BE EXCHANGED AT CUSTOMER CONTACT POINT (MICC)** + +###### **Source** + +ITU-T Recommendation M.1537 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 24th of October 1997. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References ..... | 1 | +| 3 Terms and definitions..... | 2 | +| 3.1 Terminology ..... | 2 | +| 4 Abbreviations ..... | 2 | +| 5 Definition of maintenance information ..... | 2 | +| 5.1 Information basic structure..... | 2 | +| 5.2 Generic information part ..... | 3 | +| 5.3 Specific information part..... | 4 | +| 5.4 Reference information part..... | 6 | +| 6 Examples of maintenance processes ..... | 6 | +| 6.1 Bringing-into-service process..... | 6 | +| 6.2 Fault report process (customer to service provider)..... | 6 | +| 6.3 Network fault report process (service provider to customer)..... | 7 | +| 6.4 Fault localization process ..... | 7 | +| 6.5 Service restoration process..... | 7 | +| 6.6 Network repair process..... | 7 | +| 6.7 Fault follow-up process ..... | 7 | +| 6.8 Planned outage process ..... | 7 | +| 7 Information classification..... | 7 | +| 7.1 Utility value of information..... | 7 | +| 7.2 Timing of information ..... | 7 | +| 7.3 Standardization levels ..... | 8 | +| Annex A – Examples of maintenance process ..... | 8 | + + + +# **DEFINITION OF MAINTENANCE INFORMATION TO BE EXCHANGED AT CUSTOMER CONTACT POINT (MICC)** + +*(Geneva, 1997)* + +## **1 Scope** + +This Recommendation describes the definition for the maintenance information exchange between a customer and a service provider's customer care staff at customer contact point under the environment of multiple service providers. + +A customer contact point is a conceptual point at which a service provider can interact with any customer of the offered service for the purpose of maintaining communication services. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation E.440 (1996), *Customer satisfaction point*. +- ITU-T Recommendation E.800 (1994), *Terms and definition related to quality of service and network performance including dependability*. +- CCITT Recommendation M.21 (1992), *Maintenance philosophy for telecommunication services*. +- ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- ITU-T Recommendation M.1400 (1997), *Designations for international networks*. +- CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network*. +- CCITT Recommendation M.1520 (1992), *Standardized information exchange between Administrations*. +- CCITT Recommendation M.1530 (1992), *Network maintenance information*. +- ITU-T Recommendation M.1535 (1996), *Principles for Maintenance Information to be exchanged at Customer Contact point (MICC)*. +- ITU-T Recommendation M.1540 (1994), *Exchange of information for planned outages of transmission systems*. +- ITU-T Recommendation M.3010 (1996), *Principles for a Telecommunications Management Network*. +- ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. + +- ITU-T Recommendation X.160 (1996), *Architecture for customer network management service for public data networks.* +- ITU-T Recommendation X.161 (1995), *Definition of customer network management services for public data networks.* +- ITU-T Recommendation X.162 (1995), *Definition of management information for customer network management service for public data networks to be used with the CNMc Interface.* +- ITU-T Recommendation X.163 (1995), *Definition of management information for customer network management service for public data networks to be used with the CNMe Interface.* + +## **3 Terms and definitions** + +### **3.1 Terminology** + +Recommendation M.1535 provides principles for Maintenance Information to be exchanged at Customer Contact point (MICC). + +Terminology and definitions relating to this Recommendation are provided in Recommendation M.60. Further terms and definitions can be found in other ITU-T Recommendations (e.g. M.21, M.1400, M.1510, M.1520, M.1530, M.1540, M.3010, M.3200, E.800, E.440, X.160, X.161, X.162 and X.163). + +## **4 Abbreviations** + +This Recommendation uses the following abbreviations + +ISDN Integrated Services Digital Network + +MICC Maintenance Information to be exchanged at Customer Contact point + +TMN Telecommunications Management Network + +# **5 Definition of maintenance information** + +### **5.1 Information basic structure** + +Maintenance Information to be exchanged at Customer Contact point (MICC) consists of "Generic information part", "Specific information part" and "Reference information part". All this information contains items and/or sub-items of maintenance information (see Figure 1). + +![Diagram of MICC basic structure showing the flow from Customer to Service provider through Generic, Specific, and Reference information parts, with a detailed breakdown of items and sub-items.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +The diagram illustrates the basic structure of MICC (Maintenance Information and Control Circuit). At the top, a 'Customer' box on the left and a 'Service provider' box on the right (containing 'Customer care staff') are connected by a double-headed arrow labeled 'MICC'. Below this, a table shows three columns: 'Generic information part', 'Specific information part', and 'Reference information part'. + +The bottom part of the diagram is a hierarchical tree structure starting with 'MICC' on the left. It branches into three main categories: + + +- Generic information part**: This part further branches into 'item i' and 'item j'. 'item i' further branches into 'sub-item m' and 'sub-item n'. +- Specific information part**: This part branches into a list of information types: 'Bringing-into-service information', 'Fault Reporting information', 'Network fault Reporting information', 'Fault localization information', 'Service restoration information', 'Network repair information', 'Follow-up information', and 'Planned outage information'. 'Bringing-into-service information' branches into 'item p'. 'Fault Reporting information' branches into 'item q'. A vertical dashed line indicates that the remaining specific information types also have associated items. +- Reference information part**: This part branches into 'Contact information' and 'Service agreement information'. 'Contact information' branches into 'item r'. + +T0407320-97 + +Diagram of MICC basic structure showing the flow from Customer to Service provider through Generic, Specific, and Reference information parts, with a detailed breakdown of items and sub-items. + +**Figure 1/M.1537 – MICC basic structure** + +### 5.2 Generic information part + +Generic information part is independent from the maintenance sub-process type (see Recommendation M.1535), and it is normally used during a sequence of procedure in order to identify the circuit and event concerned. Generic information items are shown in Table 1. + +**Table 1/M.1537 – Generic information items** + +| Managed area

Information part | Telephone services
(Note 1) | Leased Circuit services | ISDN services | Data transmission services | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------|-----------------------------------| +| | Information items | | | | +| Generic information | – Contact time (Note 2)
– Customer identification
– Customer care staff identification
– Circuit identification (Note 3) | | | | +| NOTE 1 – For telephone services, the above information items are used for special telephone services only, for example sound-program transmission on fixed (non-switched) public circuits.
NOTE 2 – Contact time identifies the time whenever service provider's care staff is contacted by customer or vice versa, for example: planned outage.
NOTE 3 – For circuit identification, Recommendation M.1400 may be used. | | | | | + +### 5.3 Specific information part + +Specific information part is dependent on individual maintenance sub-process. Therefore, appropriate maintenance information items are used for each of the following eight maintenance sub-processes (see Recommendation M.1535): + +- bringing-into-service; +- fault report (customer to service provider); +- network fault report (service provider to customer); +- fault localization; +- service restoration ; +- network repair; +- fault follow-up; +- planned outage. + +Specific information items are shown in Table 2. + +**Table 2/M.1537 – Specific information items** + +| Managed area

Maintenance related process | Telephone services
(Note) | Leased Circuit services | ISDN services | Data transmission services | +|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------|-----------------------------------| +| | Information items | | | | +| Bringing-into-service |
  • – Transmission route
  • – Transmission media
  • – Ready for service date
  • – Testing date
  • – Circuit designation
  • – Reference to the appropriate ITU-T Recommendations
| | | | +| Fault report |
  • – Fault start time (based on fault occurrence and/or its detection)
  • – Fault status
  • – Permission for testing
  • – Fault related data log
| | | | +| Network fault report |
  • – Fault detection time
  • – Fault status
  • – Permission for testing
  • – Expected restoration time
  • – Cause(s)
  • – Fault related data log
| | | | +| Fault localization |
  • – Localization result by customer
  • – Localization result by service provider
| | | | +| Service restoration |
  • – Requirement/capability for service restoration
  • – Expected service restoration time
  • – Means for service restoration
  • – Confirmation of service restoration
| | | | +| Network repair |
  • – Expected network repair time
  • – Means for network repair
  • – Confirmation of network repair
| | | | +| Fault follow-up |
  • – Restoration schedule
  • – Progress
| | | | +| Planned outage |
  • – Planned outage schedule (start/end time)
  • – Reason
  • – Affected area
  • – Normality confirmation test result by both customer and service provider
| | | | + +NOTE – For telephone services, the above information items are used for special telephone services only, for example sound-program transmission on fixed (non-switched) public circuits. + +### 5.4 Reference information part + +Reference information part is used in case of necessity to proceed maintenance efficiently in collaboration with the customer, and it can be mainly classified into contract information (Note 1) and service agreement information (Note 2). Typical maintenance information items which are related to the maintenance service contract or maintenance service agreement are: + +- contract identifier (e.g. contract number); +- contact identifier (e.g. authentication identification and password); +- service starting date; +- service hours (for normal and particular days of the year); +- type of contract; +- access network type (e.g. mobile, ISDN, leased circuit); +- network configuration (e.g. transmission routes, transmission media, automatic restoration); +- traffic volume; +- fault status and occurrence; +- testing status; +- call connectivity quality; +- transmission quality; +- congestion status; +- service availability. + +NOTE 1 – A contract represents a formal business agreement between service provider and customer for its maintenance service. + +NOTE 2 – A maintenance service agreement may not be formal nor has a legal binding as maintenance service contract. + +It is to be noted that for this information part the maintenance information items depend on the managed area. + +# 6 Examples of maintenance processes + +An example of each maintenance process is described in Annex A to help understanding the "Generic part and the Specific part" of MICC based on maintenance process reference model (see Recommendation M.1535). + +### 6.1 Bringing-into-service process + +An example of bringing-into-service process is given in Figure A.1. + +### 6.2 Fault report process (customer to service provider) + +A customer detects malfunction in the service by receiving report from end-user or alarm report from its own communication facilities. Then he can confirm the status of this malfunction by notifying the end-user for the detail of test results and type of alarm on the facilities. + +The customer tries to specify where the cause of malfunction is located (at his own premises, customer side or at the service provider side). Then he accesses a customer contact point to report the malfunction to the service provider. An example of fault report process is given in Figure A.2. + +### **6.3 Network fault report process (service provider to customer)** + +An example of network fault report process is given in Figure A.3. + +### **6.4 Fault localization process** + +An example of fault localization process is given in Figure A.4. + +### **6.5 Service restoration process** + +An example of service restoration process is given in Figure A.5. + +### **6.6 Network repair process** + +An example of network repair process is given in Figure A.6. + +### **6.7 Fault follow-up process** + +An example of fault follow-up process is given in Figure A.7. + +### **6.8 Planned outage process** + +An example of planned outage process is given in Figure A.8. + +## **7 Information classification** + +### **7.1 Utility value of information** + +Maintenance information between customer and service provider can be classified in the following three types from the viewpoint of the utility value of information: + +- 1) Type A: information supplied to customers by which they can judge what kind of action is necessary for using telecommunications services; +- 2) Type B: information supplied to customers by which they can use network/services efficiently; +- 3) Type C: information supplied to customers which is useful for their business. + +### **7.2 Timing of information** + +Maintenance information between customer and service provider can be classified in the following three types from the viewpoint of the timing: + +- 1) Type 1: information provided to a customer when the customer claims or following specific request according to service and/or network fault; +- 2) Type 2: information provided to a customer spontaneously when the service provider detects service and/or network fault status; +- 3) Type 3: information provided to a customer according to the customer's special requirements (e.g. long-term traffic volume data). + +### 7.3 Standardization levels + +Standardization levels are classified in the following three levels made up of the matrix of the utility value of information and the timing of information: + +- 1) Basic (Mandatory): to provide the information is mandatory regardless of customer's demands. This information is included in the maintenance service contract between the service provider and customer; +- 2) Essential (Option level 1): to provide the information only when a customer demands the information; +- 3) Optional (Option level 2): whether or not the information is provided for a customer is a negotiated matter between customer and service provider. + +## ANNEX A + +## Examples of maintenance process + +![Diagram of the bringing-into-service process showing information exchange between Customer, Service provider, and Network provider.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +The diagram illustrates the flow of information during a maintenance process. It is divided into three main vertical sections: **Customer (Activity)**, **Service provider Customer care staff (Activity)**, and **(Network provider)**. + +- Customer (Activity):** Contains a rounded rectangle labeled "Service order production and acceptance". +- Service provider Customer care staff (Activity):** Contains a rounded rectangle with three items: "Service order reception", "Service order confirmation", and "Service order processing". +- (Network provider):** Contains a rounded rectangle labeled "Provisioning status and reporting". + +Information flow is indicated by arrows: + +- A "Service order" arrow points from the Customer's "Service order production and acceptance" to the Service provider's "Service order reception". +- A "Service order confirmation" arrow points from the Service provider's "Service order confirmation" back to the Customer's "Service order production and acceptance". +- A double-headed arrow connects the Service provider's "Service order confirmation" and the Network provider's "Provisioning status and reporting". + +Below the flow, a section titled **Maintenance Information to be exchanged at Customer Contact point (MICC)** is divided into two columns: + +| Generic information part | Specific information part | +|-----------------------------------------|------------------------------------------------------| +| – Contact time | – Ready for service date | +| – Customer identification 1) | – Testing date | +| – Customer care staff identification 2) | – Circuit designation | +| – Circuit identification | – Reference to the appropriate ITU-T Recommendations | +| | – Transmission route | +| | – Transmission media | + +Diagram of the bringing-into-service process showing information exchange between Customer, Service provider, and Network provider. + +T0408370-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.1/M.1537 – Example of bringing-into-service process** + +![Flowchart of the fault report process from customer to service provider, including information exchange details.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram illustrates the fault report process between a Customer (Activity), a Service provider Customer care staff (Activity), and a Network provider. The process involves fault detection, status confirmation, and information exchange. + +**Maintenance Information to be exchanged at Customer Contact point (MICC)** + +| Generic information part | Specific information part | +|-----------------------------------------|---------------------------------------------------------------------| +| – Contact time | – Fault start time (based on fault occurrence and/or its detection) | +| – Customer identification 1) | – Fault status | +| – Customer care staff identification 2) | – Permission for testing | +| – Circuit identification | – Fault related data log | + +**Process Flow:** + +- Customer (Activity):** Fault detection → Fault status confirmation → Verification of fault on customer's premises → Fault report production. +- Service provider Customer care staff (Activity):** Fault report reception → Fault status confirmation → Inquires more detailed information. +- Information Exchange:** + - Fault report (from Customer to Service provider) + - Other related information (from Service provider to Customer) +- Network provider:** Fault status confirmation (connected to Service provider). + +Flowchart of the fault report process from customer to service provider, including information exchange details. + +T0408380-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.2/M.1537 – Example of fault report (customer to service provider) process** + +![Diagram of network fault report process between Customer, Service provider, and Network provider. It includes a table for Maintenance Information (MICC) with Generic and Specific information parts.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The diagram illustrates the flow of information during a network fault report. It is divided into three main vertical sections: **Customer (Activity)**, **Maintenance Information to be exchanged at Customer Contact point (MICC)**, and **Service provider Customer care staff (Activity)**, with a fourth section for **(Network provider)**. + +- Customer (Activity):** Contains a box with "Network fault report reception", "Fault status confirmation", and "Verification of fault on customer's premises". +- Maintenance Information to be exchanged at Customer Contact point (MICC):** The central column. Arrows show "Network fault report" and "Other related information" being exchanged between the Customer and Service provider. +- Service provider Customer care staff (Activity):** Contains a box with "Grouping affected circuits into each customer", "Network fault report production", and "Inquires more detailed information". +- (Network provider):** Contains a box with "Network failure (i.e. Alarm detection)" pointing to "Fault status confirmation" and "Affected circuit identification". + +Below the main flow, the **Maintenance Information to be exchanged at Customer Contact point (MICC)** is detailed in a table: + +| Generic information part | Specific information part | +|-----------------------------------------|-----------------------------| +| – Contact time | – Fault detection time | +| – Customer identification 1) | – Fault status | +| – Customer care staff identification 2) | – Permission for testing | +| – Circuit identification | – Expected restoration time | +| | – Cause(s) | +| | – Fault related data log | + +Diagram of network fault report process between Customer, Service provider, and Network provider. It includes a table for Maintenance Information (MICC) with Generic and Specific information parts. + +T0408390-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.3/M.1537 – Example of network fault report (service provider to customer) process** + +![Diagram of fault localization process showing information exchange between Customer, Service provider, and Network provider. It includes a table for 'Maintenance Information to be exchanged at Customer Contact point (MICC)' with 'Generic information part' and 'Specific information part'.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +**Maintenance Information to be exchanged at Customer Contact point (MICC)** + +| Generic information part | Specific information part | +|-----------------------------------------|-------------------------------------------| +| – Contact time | – Localization result by customer | +| – Customer identification 1) | – Localization result by service provider | +| – Customer care staff identification 2) | | +| – Circuit identification | | + +Diagram of fault localization process showing information exchange between Customer, Service provider, and Network provider. It includes a table for 'Maintenance Information to be exchanged at Customer Contact point (MICC)' with 'Generic information part' and 'Specific information part'. + +T0408400-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.4/M.1537 – Example of fault localization process** + +![Diagram of service restoration process showing interactions between Customer, Service provider, and Network provider. The diagram includes a table for 'Generic information part' and 'Specific information part'.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +**Maintenance Information to be exchanged at Customer Contact point (MICC)** + +| Generic information part | Specific information part | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
  • - Contact time
  • - Customer identification 1)
  • - Customer care staff identification 2)
  • - Circuit identification
|
  • - Requirement/capability for service restoration
  • - Expected service restoration time
  • - Means for service restoration
  • - Confirmation result by both customer and service provider
| + +Diagram of service restoration process showing interactions between Customer, Service provider, and Network provider. The diagram includes a table for 'Generic information part' and 'Specific information part'. + +T0408410-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.5/M.1537 – Example of service restoration process** + +![Diagram of network repair process showing interactions between Customer, Service provider, and Network provider. It includes a table for 'Maintenance Information to be exchanged at Customer Contact point (MICC)' with 'Generic information part' and 'Specific information part'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +**Maintenance Information to be exchanged at Customer Contact point (MICC)** + +| Generic information part | Specific information part | +|-----------------------------------------|----------------------------------| +| - Contact time | - Expected network repair time | +| - Customer identification 1) | - Means for network repair | +| - Customer care staff identification 2) | - Confirmation of network repair | +| - Circuit identification | | + +\* Process in case of possibility of service restoration or of necessity for putting network configuration back to original one after service restoration + +Diagram of network repair process showing interactions between Customer, Service provider, and Network provider. It includes a table for 'Maintenance Information to be exchanged at Customer Contact point (MICC)' with 'Generic information part' and 'Specific information part'. + +T0408420-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.6/M.1537 – Example of network repair process** + +![Diagram of the fault follow-up process showing information exchange between Customer, Service provider, and Network provider. The diagram includes a 'Fault follow-up report' flow and a detailed 'Maintenance Information' table with 'Generic information part' and 'Specific information part'.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +**Maintenance Information to be exchanged at Customer Contact point (MICC)** + +The diagram illustrates the fault follow-up process involving three main entities: **Customer (Activity)**, **Service provider Customer care staff (Activity)**, and **(Network provider)**. + +- Customer (Activity)** includes: + - Fault follow-up report reception + - Fault status confirmation +- Service provider Customer care staff (Activity)** includes: + - Network operating tracking + - Fault follow-up process +- (Network provider)** includes: + - Fault identification + - Fault recovery or repair + - Confirmation test + +A **Fault follow-up report** is exchanged between the Customer and the Service provider. + +The **Maintenance Information to be exchanged at Customer Contact point (MICC)** is structured as follows: + +| Generic information part | Specific information part | +|-----------------------------------------|---------------------------| +| – Contact time | | +| – Customer identification 1) | – Restoration schedule | +| – Customer care staff identification 2) | – Progress | +| – Circuit identification | | + +Diagram of the fault follow-up process showing information exchange between Customer, Service provider, and Network provider. The diagram includes a 'Fault follow-up report' flow and a detailed 'Maintenance Information' table with 'Generic information part' and 'Specific information part'. + +T0408430-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.7/M.1537 – Example of fault follow-up process** + +![Diagram of the planned outage process showing information exchange between Customer, Service provider, and Network provider.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +**Customer +(Activity)** + +Planned outage +notification + + Service normality +confirmation + +**Maintenance Information +to be exchanged at +Customer Contact point +(MICC)** + +← +Planned outage report +← + +← +Other related information +← + +| Generic information part | Specific information part | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – Contact time

– Customer identification 1)

– Customer care staff
  identification 2)


– Circuit identification | – Planned outage schedule
  (start/end time)

– Reason
– Affected area
– Confirmation test result by both
  customer and service provider
| + +**Service provider +Customer care staff +(Activity)** + +Planned outage +reporting + + Service normality +confirmation + +(Network provider) + + +Planned outage +reporting + + Affected circuit +identification + + Performing test + + Confirmation test + +Diagram of the planned outage process showing information exchange between Customer, Service provider, and Network provider. + +T0408440-97 + +1) e.g. company name, contact person, address, tel., fax, telex, e-mail. + +2) e.g. service provider name, contact person, address, tel., fax, telex, e-mail. + +**Figure A.8/M.1537 – Example of planned outage process** + + + +# ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression: definitions, symbols, classification +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Overall network operation, telephone service, service operation and human factors +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media, digital systems and networks +- Series H Audiovisual and multimedia systems +- Series I Integrated services digital network +- Series J Transmission of television, sound programme and other multimedia signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits** +- Series N Maintenance: international sound programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality, telephone installations, local line networks +- Series Q Switching and signalling +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminals for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communication +- Series Z Programming languages \ No newline at end of file diff --git a/marked/M/T-REC-M.1540-199410-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.1540-199410-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da570fc3d3b68aff5fa5c3030e6a2a95359f9879 --- /dev/null +++ b/marked/M/T-REC-M.1540-199410-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f448e2b769ed40f9db061796df968febd9d49d5057233ca5650a5f2ff1a1fda +size 8298 diff --git a/marked/M/T-REC-M.1540-199410-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/M/T-REC-M.1540-199410-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdd7cf235a14fa528a59f53da48655e106a3d95d --- /dev/null +++ b/marked/M/T-REC-M.1540-199410-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50627770a1ead4263af263d537bf48fbc714577eac53583717064ce6c46dc000 +size 84040 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7f4f3d65f996a445387c6b006d27a18a55397fc --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19bceeb65fc892866678bd85d5353958a41411df78c98bd908bfe6bb117906f1 +size 23832 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9120522d5bb1853de9fe6247f24170ade8dd8686 --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fa26f18b6d8e7a4330161dc96b25cad3a85bfa27e8f53f9ba2ec0182986f4d7 +size 31608 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a6ca72e262ee12258abae74f54f29f9f4d196ff --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51463ba5d6e775e99e333a3246424963dfc0f170c989405e2d3360dddbcae4bc +size 16617 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aacccbf993c11f1ea548b1093c843329b59fea4f --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f697f1546aad9d346800deca8274f38076334cc49a493734fa1260d139ec9924 +size 30829 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c72431e15b11b57829c7438bb3308e5f538cdeed --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60102aad39f98175ad9947473c0184f23924d5f133b33d7afbe323ab801b6154 +size 21144 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba8edfe1c0c4c00c3d92754284b71cd04c994e45 --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99a66adf0f1be523d51d13cc69ea5f1b46708d36c38109062f6a7496d2a2f8f9 +size 27238 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62a2e98629da5a6328a0ac2bd6ddfe35692322ae --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:704894a92b416ba01d0084281c9f236cf8f10581b6beb515db7a33ac54f5b95d +size 6625 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e988f870368c18ecc900f79a6506987c202ad8a --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b41507953b6f0673016646ee9d3bbf6bf239152a62c34c97671f97b8c08fb858 +size 32355 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b07b7e328b65e186625ed49edfa4cc00131cd72 --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6428d0aebc8038b48812117f41b825c7fd7b5f83192b6a1ba7e8487d827406f9 +size 15508 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c367c837e93d16631f234edbb076efce44e881bc --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c8fac8c074ace3151ef1f72f5e7d41fb79e87ec48799e64dac4a46e6177b82d +size 31388 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ff60f84d6bf3a1d0a5ebd6876ce68ee87e209ff --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb673d04463a085c404d9fcd428e9e4fc79646844ac2b2b5be77f5ea69cf814 +size 22516 diff --git a/marked/M/T-REC-M.1541-201101-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/M/T-REC-M.1541-201101-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dd11a1ce5ce752e2225987633ee96372bc8b487 --- /dev/null +++ b/marked/M/T-REC-M.1541-201101-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd82183ae02d5792d981a78c7d2c9d120243904be13f8b3cf2db925563c14b21 +size 29568 diff --git a/marked/M/T-REC-M.1560-199210-I_PDF-E/raw.md b/marked/M/T-REC-M.1560-199210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c1a0659eace2ad4fe6331af1a5cab4f9666ccf5c --- /dev/null +++ b/marked/M/T-REC-M.1560-199210-I_PDF-E/raw.md @@ -0,0 +1,420 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**M.1560** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +(10/92) + +**MAINTENANCE: DESIGNATIONS +AND INFORMATION EXCHANGE** + +--- + +**ESCALATION PROCEDURE FOR +INTERNATIONAL LEASED CIRCUITS** + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +**Recommendation M.1560** + +--- + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation M.1560 was prepared by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency. + +# **ESCALATION PROCEDURE FOR INTERNATIONAL LEASED CIRCUITS** + +(1992) + +## *Abstract* + +This Recommendation defines an escalation procedure for the resolution of problems or difficulties in the provision or maintenance of international leased circuits where normal cooperation of maintenance elements does not. This procedure supplements the general escalation procedure given in Recommendation M.1550 [1]. + +## *Keywords* + +- escalation, +- fault restoration, +- leased circuit, +- maintenance, +- procedure. + +## **1 General** + +Customers using international leased circuits, have ever increasing demands for + +- faster installation times, and consequent need for cooperation between Administrations to achieve required in-service dates; +- higher availability of leased and special circuits, and hence faster resolution of faults or impairments, + +and have an expectation that Administrations should meet these demands in delivering quality services over the international network. + +Normally cooperation between maintenance elements in different Administrations will result in the efficient provision line-up, designation and restoration/repair of international leased circuits. There may be circumstances, however, where this escalation procedure needs to be used. Generally this will occur when: + +- timings for certain activities in the procedures for provision and line-up (setting of international circuit test appointments) are in jeopardy or exceeded (failed); +- service is not restored or is not likely to be restored within agreed time periods (based on experience of average restoration time) (e.g. mean time to restore service MTRS); +- the same fault recurs within short intervals; +- indications of network malfunction persist despite repeated fault investigations. + +This Recommendation supplements the procedure given in Recommendation M.1550 [1] in respect of the provision, line-up, designation and restoration/repair of international leased circuits. + +# **2 Escalation process** + +In order to improve the quality of service to customers, Administrations shall (bilaterally or multilaterally) agree to apply time targets in performing functions related to the provision, line-up, designation and restoration/repair of international leased circuits on an end-to-end basis. + +These agreements would normally be made by the technical service (see Recommendation M.75 [2]) between the Administrations concerned. + +The general concept of escalation and the definition of an escalation point are given in Recommendation M.1550 [1], however, as it applies to international leased circuits, the following shall prevail: + +- for provision of international leased circuits the time targets are usually applied during the normal working day; +- for maintenance of international leased circuits the time targets for restoration of service are to be applied on a 24 hours/day, 365 days/year end-to-end basis when customers require this level of performance. Administrations will need to agree on the level of performance bilaterally or multilaterally taking into consideration what organization they require to deliver this level of performance (see M.700-Series [3] and M.1000-Series [4] Recommendations). + +A fault can be the result of any type of failure (see Recommendation M.20, § 3.2 [5]) either as reported by a customer to an Administration, or as notified by the network through an alarm or monitoring functions. + +Administrations should encourage customers to normally contact escalation points within their own organization. Customers should only be encouraged, to contact the distant Administration if agreed by the Administrations involved. + +For further information on interworking, see Annex D. + +### 2.1 *Escalation levels/escalation points* + +A number of escalation levels should be established (this will depend upon the specific organization of an Administration) and is subject to bilateral agreement. If there is more than one escalation point, then these must not be vested in the same person/organization element. + +For example, in this Recommendation three levels of escalation have been used to demonstrate the principles to be used. At each level there will be an appointed “escalation point” which is an element of the general maintenance organization (see Recommendation M.85 [6]). The primary escalation point is the next level of management (supervision) within the organization of the Administration (see Recommendation M.75, § 2 [2]). + +The person/organization unit receiving the escalation request should have the required expertise and authority to deploy the required resources/expertise to resolve the problems. + +## 2.2 *Performance targets time interval* + +These are targets for particular actions or activities which should be achieved within a particular time interval, e.g. where in the case of a faulty international leased circuit it is agreed that the circuit should be restored/repairs within an agreed time period. + +A target is considered to be “in jeopardy” where a situation exists which will or may prevent the achievement of agreed target timings. Administrations should agree to advise each other when such situations arise. A target is considered to have been “exceeded”, or “failed”, when the agreed target has been missed, without the agreed action having taken place. + +The targets to be applied are given in the following sub-sections. + +### 2.2.1 *Provision and line-up* + +The prime objective is to ensure that Administrations are able to deliver the required type of circuit, working to specification, on the required date, to the customers. To do this the following targets should be set: + +- *Circuit routing proposal*: The date by which Administrations should have made a response to proposals (see Recommendation M.1045 [7]) received from the other Administration(s). +- *Line-up*: The date by which the line-up date is to be reviewed with the objective of ensuring that the agreed Ready for Service (RFS) date can be met. +- *National circuit section tests*: The date by which the national circuit section tests are to be performed, completed and advised to the partner Administration. + +- *International circuit section tests*: The date by which the international circuit section tests are performed, completed and advised to the partner Administration. +- *End-to-end tests*: The date by which the end-to-end tests are to be performed and completed. +- *Ready for service date*: The date by which the circuit is to be ready for customer service. + +### 2.2.2 *Maintenance (fault localization, repair and make good)* + +The prime objective is to ensure that Administrations are able to restore service to the customers/users within an agreed time period. To do this the following types of targets should be set: + +- *Service restoration*: The period within which fault localization and repair or make good, to restore service to the customer is achieved (see Recommendation M.1016 [8]). +- *Intermittent fault recurrence*: Where there are more than an agreed number of faults within an agreed period (e.g. $\geq x$ faults/y days). + +### 2.2.3 *Maintenance performance* + +Escalation will only occur for the following criteria if no identifiable reason can be established for the deterioration in performance, e.g. a major cable failure (which would be subject to escalation procedures in Recommendation M.1550 [1]). + +- *Fault rate*: Where the agreed fault rate of circuits (generally expressed as number of faults per 100 circuits per month) between Administrations is exceeded in a three month period. +- *Restoration time*: Where the agreed average restoration time (expressed as the mean hours/faults/month) between administrations is exceeded in a three month period. +- *% circuits restored in $x$ hours*: Where the performance (expressed as % of faulty circuits restored in $x$ hours/faults/month) drops below the agreed % in a three month period. + +Examples of escalation target criteria are given in Annex B. + +## 2.3 *Escalation steps* + +In general the following steps shall be taken to escalate a problem or situation in the provision, line-up, designation and restoration/repair of international leased circuits. The principle of the following three step escalation procedure (see also Figure 1/M.1560), aiming at a close and coordinated cooperation of Administrations is recommended in order to reduce the number and frequency of occasions of failure to meet targets. + +- *Step 1* – When the initial target ( $T_0$ ) is in jeopardy, or has been exceeded (failed), the organization element of one Administration informs its First Level Escalation Point which is then expected to assume the responsibility and control over all actions associated with the resolution of the target failure within step 1 period ( $T_1$ ). If the distant Administration's cooperation is required to resolve the problem, then the matter should also be escalated to the distant First Level Escalation Point of the equivalent organization element. +- *Step 2* – If step 1 fails a Second Level Escalation Point within the organization is to be advised of the situation and requested to initiate further actions suitable to resolve the reported problem within step 2 period ( $T_2$ ). Also information about the actions taken up to this time for clearing the reported problem can be given (when appropriate) to the customer/user concerned during step 2. If the distant Administration's cooperation is still required to resolve the problem, then the matter should be escalated to the distant Second Level Escalation Point by the First Level Escalation Point in the distant Administration. + +- *Step 3* – In the event that steps 1 and 2 fail the Third Level Escalation Point, within the organization which is not normally concerned with the day-to-day operation of international services, will be alerted by the Second Level Escalation Point mentioned in step 2 above. If the distant Administration's cooperation is still required to resolve the problem, then the matter should be escalated to the distant Third Level Escalation Point by the Second Level Escalation Point in the distant Administration. Step 3 period ( $T_3$ ) is initiated during which information can (when appropriate) also be given to the customer/user concerned. + +![A staircase diagram illustrating the escalation process. It starts at the bottom left with 'Period T0' and a horizontal arrow pointing right. Above this is 'Target missed' with an upward arrow. The next step is 'Step 1 Escalate to first level' with an upward arrow, followed by 'Period T1' with a horizontal arrow. The next step is 'Step 2 Escalate to second level' with an upward arrow, followed by 'Period T2' with a horizontal arrow. The final step is 'Step 3 Escalate to third level' with an upward arrow, followed by 'Period T3' with a horizontal arrow. The diagram shows a series of three steps, each consisting of an escalation action followed by a time period. The steps are labeled Step 1, Step 2, and Step 3, and the time periods are labeled Period T1, Period T2, and Period T3. The initial state is 'Target missed' and the initial time period is 'Period T0'. The diagram is labeled T0402560-91/d01 in the bottom right corner.](191a4a245a7d36d03be9a990d0f758f5_img.jpg) + +``` + +graph TD + T0[Period T0] --> TM[Target missed] + TM --> S1[Step 1 Escalate to first level] + S1 --> T1[Period T1] + T1 --> S2[Step 2 Escalate to second level] + S2 --> T2[Period T2] + T2 --> S3[Step 3 Escalate to third level] + S3 --> T3[Period T3] + +``` + +A staircase diagram illustrating the escalation process. It starts at the bottom left with 'Period T0' and a horizontal arrow pointing right. Above this is 'Target missed' with an upward arrow. The next step is 'Step 1 Escalate to first level' with an upward arrow, followed by 'Period T1' with a horizontal arrow. The next step is 'Step 2 Escalate to second level' with an upward arrow, followed by 'Period T2' with a horizontal arrow. The final step is 'Step 3 Escalate to third level' with an upward arrow, followed by 'Period T3' with a horizontal arrow. The diagram shows a series of three steps, each consisting of an escalation action followed by a time period. The steps are labeled Step 1, Step 2, and Step 3, and the time periods are labeled Period T1, Period T2, and Period T3. The initial state is 'Target missed' and the initial time period is 'Period T0'. The diagram is labeled T0402560-91/d01 in the bottom right corner. + +FIGURE 1/M.1560 +**Escalation steps** + +Where a problem or situation is escalated, an acknowledgement should be issued by the Escalation Point receiving the escalation to the contact point which is escalating the problem. + +Examples of escalation timings between escalation levels are given in Annex C. + +## 2.4 *Escalation communication* + +Escalation communications between Administrations should normally occur (horizontally in diagram below) between peer levels, e.g. escalation communications should only occur between the same escalation levels. However, in exceptional circumstances, communication can occur between Administrations between different escalation levels. + +In cases where language difficulties exist it is recommended that electronic text communication be used which can be translated by the receiving point if necessary. + +# 3 **Exchange of information** + +It is recommended that information be exchanged between Administrations in a standardized format to convey fault information, escalation points, and contact points. + +![Diagram of Escalation communication paths showing four levels: Operational, First, Second, and Third. The Operational level is represented by circles, while the others are squares. Vertical arrows show escalation from Operational up to Third level. Horizontal double-headed arrows show escalation communication between corresponding levels on two sides. A dashed horizontal arrow shows normal communication between Operational levels. A legend defines the symbols: solid double-headed arrow for Escalation communication, dashed double-headed arrow for Normal communication, square for Escalation point, and upward arrow for Escalation. Reference T0404130-93/d02 is noted.](fc46871d72c65d3381d9201646d23439_img.jpg) + +T0404130-93/d02 + +←→ Escalation communication      □ Escalation point + - - - → Normal communication    ↑ Escalation + +Diagram of Escalation communication paths showing four levels: Operational, First, Second, and Third. The Operational level is represented by circles, while the others are squares. Vertical arrows show escalation from Operational up to Third level. Horizontal double-headed arrows show escalation communication between corresponding levels on two sides. A dashed horizontal arrow shows normal communication between Operational levels. A legend defines the symbols: solid double-headed arrow for Escalation communication, dashed double-headed arrow for Normal communication, square for Escalation point, and upward arrow for Escalation. Reference T0404130-93/d02 is noted. + +FIGURE 2/M.1560 +**Escalation communication paths** + +In order to facilitate the communication between + +- provision liaison points; +- fault report points; +- escalation points; + +as covered in this Recommendation, standardized information must be provided updated and exchanged, as detailed in Annex A. + +# ANNEX A (to Recommendation M.1560) + +## **Information to be provided and exchanged** + +## A.1    *Maintenance information exchange* + +#### Part 1 – *Centre-to-centre information* + +- 1      Designation of fault report point (see Recommendation M.95 [6]) +- 2      Operating hours +- 3      Designation of the Administration +- 4      Telephone numbers (at least two) +- 5      Facsimile number +- 6      Telex number +- 7      Designation and responsibility of First Level Escalation Point +- 8      Relevant telephone, fax and telex numbers +- 9      Designation and responsibility of Second Level Escalation Point + +- 10 Relevant telephone, fax and telex numbers +- 11 Position and responsibility of Third Level Escalation Point +- 12 Relevant telephone, fax and telex numbers +- 13 Out of hours contact and escalation points if different from above +- 14 Designation of customer's organization +- 15 Operating hours of control and sub-control stations (see Recommendation M.1510 [9]) + +#### Part 2 – (variable) *Information concerning the circuit* + +- 1 Designation of the international leased circuit +- 2 Urgency of restoration +- 3-14 Other relevant information (according to Recommendation M.1400 [10]) +- 15 Information on whether circuit is permanent or temporary +- 16 Designation of customer's organization (Note) +- 17 Customer's telephone number (Note) + +#### Part 3 – (variable) *Information concerning the fault report* + +- 1 Time of fault reporting (UTC) +- 2 Time of fault incidence (UTC) +- 3 Name and position of person reporting the fault +- 4 Symptoms of the fault +- 5 Fault report number/code +- 6 Statement from customer that circuit can be used for testing and fault clearance and whether or not a loop-back is available +- 7 Statement by the Administration that customer will be kept informed of progress as regards fault clearance +- 8 Access times at renter's premises + +### A.2 *Provision information exchange* + +#### Part 1 – *Provision liaison point-to-point information* + +- 1 Designation of Provision Liaison Centre +- 2 Operating hours +- 3 Designation of the Administration +- 4 Telephone numbers (at least two) +- 5 Facsimile number +- 6 Telex number +- 7 Designation and responsibility of First Level Escalation Point +- 8 Relevant telephone, fax and telex numbers +- 9 Designation and responsibility of Second Level Escalation Point +- 10 Relevant telephone, fax and telex numbers +- 11 Designation and responsibility of Third Level Escalation Point + +- 12 Position and relevant telephone, fax and telex numbers +- 13 Out of hours contact and escalation points if different from above +- 14 Operating hours of provision control and sub-control stations + +#### Part 2 – (variable) *Information concerning the order* + +- 1 Intended designation of the international leased circuit (if available) +- 2 Customer required by date (date when customer wants service) +- 3-14 Other relevant information (according to Recommendation M.1045 [7]) + +#### Part 3 – (variable) *Information concerning the order problem* + +- 1 Customer required by date (date when customer wants service) +- 2 Proposed/agreed ready for service date +- 3 Name and position of person reporting the problem +- 4 Nature of the problem +- 5 Report number/code +- 6 Statement by the Administration that customer will be kept informed of progress as regards resolution of the problem +- 7 Access times at renter's premises +- 8 Designation of customer's organization (see Note) +- 9 Customer's telephone number (see Note) + +*Note* – This information is only to be exchanged where the support of the One-Stop-Shopping (OSS) arrangements is required (see Recommendation F.14 [11]). + +# ANNEX B + +(to Recommendation M.1560) + +## **Examples of escalation target criteria** + +The examples given as targets below are considered to be feasible, however, the exact nature of each of these targets should be subject to agreement between Administrations. Administrations may decide to agree on different targets for different circuit types (e.g. analogue and digital): + +## B.1 *Maintenance (fault localization, repair and make good)* + +- Service restoration: 2 hours; +- Intermittent fault recurrence (repeat faults): $\geq 2$ faults/60 days; + +## B.2 *Maintenance performance* + +- Fault rate: 25 faults/100 circuits/month; +- Mean time to restore service (over a 3 month period): 1.5 hours; +- % circuits restored in 3 hours in a 3 month period: 85%; +- % circuits restored in 24 hours in a 3 month period: 100%. + +# ANNEX C (to Recommendation M.1560) + +## **Examples of escalation timings between escalation levels** + +The escalation timings for leased and special circuits should be agreed bilaterally/multilaterally between Administrations. The example timings below are considered feasible but are for demonstration purposes only. + +## C.1 *Escalation timings* + +### C.1.1 *Provision and line-up* + +- Replies to information exchange (see Recommendation M.1045 [7]) + - T0 5 days after transmission + - T1 10 days after transmission + - T2 15 days after transmission +- Setting of international circuit test appointment + - T0 10 days before Ready For Service (RFS) + - T1 5 days (5 days before RFS) + - T2 2 days (3 days before RFS) +- International circuit section tests + - T0 5 days before RFS + - T1 3 days (2 days after RFS) + - T2 2 days (5 days after RFS) +- National circuit section end-to-end tests + - T0 10 days before RFS + - T1 5 days (5 days before RFS) + - T2 5 days (0 days before RFS) + +### C.1.2 *Maintenance (fault localization, repair and make good)* + +- Service restoration + - T0 2 hours after fault report + - T1 2 hours + - T2 2 hours + - T3 2 hours +- Intermittent fault recurrence (repeat faults) + - T0 $\geq 2$ faults/60 days + - T1 10 days + - T2 10 days + - T3 10 days + +#### C.1.3 *Maintenance performance* + +- Fault rate + - T0 1 month + - T1 1 month + - T2 1 month + - T3 1 month +- Restoration time + - T0 1 month + - T1 1 month + - T2 1 month + - T3 1 month +- % circuits restored in x hours + - T0 1 month + - T1 1 month + - T2 1 month + - T3 1 month + +# ANNEX D + +(to Recommendation M.1560) + +## **Examples of interworking** + +## D.1 *Maintenance (fault localization, repair and make good)* + +The following escalation procedure is recommended in order to reduce the number and frequency of occasions of failing/exceeding targets (see § 2.1). It is aimed at a close and coordinated cooperation both between Fault Report Points and with customers/users who have reported a faulty international leased circuit. + +#### D.1.1 *Fault restoration* + +- *Step 1* – When the time limit of the initial restoration target has been missed, the customer or one of the involved Fault Report Points informs a First Level Manager (supervisor of the fault report point) about the situation, who is then expected to assume the responsibility and control over all actions associated with the repair/restoration of the failed service within step 1 period (T1). If distant Administration cooperation is required to resolve the problem, then the matter should also be communicated by the First Level Manager to the distant First Level Manager. +- *Step 2* – If step 1 fails a Second Level Escalation Point is to be advised of the situation by the First Level Manager and requested to initiate further repair/restoration actions suitable to resolve the reported problem within step 2 period (T2). Information about the actions taken up to this time for clearing the reported fault can (where Administration's cooperation is still required to resolve the problem, then the matter should also be communicated by the Second Level Escalation Point to the distant Second Level Escalation Point. + +- *Step 3* – In the event that steps 1 and 2 fail the Third Level Escalation Point, not normally concerned with the day-to-day operation of international services, will be alerted by the Second Level Escalation Point mentioned in step 2 above. If distant Administration's cooperation is still required to resolve the problem, then the matter should also be communicated by the Third Level Escalation Point to the distant Third Level Escalation Point. Step 3 period ( $T_3$ ) is initiated during which information can (when appropriate) also be given to the customer/user concerned. + +Although the responsibility and control over all actions associated with the repair/restoration of the failed service is escalated to higher levels, the responsibility for day-to-day contact stays with the relevant Fault Report Point or Transmission Maintenance Point – International Line. + +If reported faults are due to known major failures, or satisfactory action is being taken to clear the fault, escalation steps 1 and 2 can be omitted. However, after 12 hours have elapsed a fault must be escalated to the Third Level Escalation Point by means of electronic text communication. + +It is further recognized that in order to achieve the restoration of service to customers, Administrations may need to agree to nominate reserve circuits on diverse routes. Such reserve circuits should be utilized to "make good" service to customers in fault restoration after an agreed time period (e.g. $T_2$ ) has elapsed; also such reserve circuits can be utilized to restore service on recurrent faults by agreement between Administrations. Further to this, reserve circuits should not be overly used for long term "make good" of circuits unless all avenues of investigation cannot lead to successful fault correction. + +#### D.1.2 *Intermittent faults* + +Where there are more than a pre-agreed number of faults on a circuit within a rolling period (e.g. $\geq 2$ faults/60 days), the occurrence of this should be escalated to the first level. The first level managers of each Administration should discuss and agree an action plan for the investigation of the problem with an agreed resolution date. The same procedure as defined in § 2.3 can be followed with the examples of time periods given in Annex B. + +## D.2 *Maintenance performance* + +Information on maintenance shall be exchanged between nominated contact points in Administrations in order to: + +- agree what actual performance levels are being attained, through the matching of perceptions from each Administration's viewpoint; +- identify areas for continuous improvement in performance, within and between, the maintenance organizations (staffing, testing facilities, procedures etc.). + +Such information should form the basis for agreement of action plans for improvement, both in terms of delivery of service to the customer, and the efficiency and effectiveness of interworking between Administrations. + +Such information should be exchanged under terms of confidence between Administrations, and such exchanged information should not be published in any way to customers/users without the agreement of all Administrations involved. + +# References + +- [1] CCITT Recommendation M.1550 *Escalation procedure*. +- [2] CCITT Recommendation M.75 *Technical service*. +- [3] CCITT Recommendation M.700-Series *Maintenance organization; fault report point; testing point; circuit control station etc.* +- [4] CCITT Recommendation M.1000-Series *International leased circuits*. + +- [5] CCITT Recommendation M.20 *Maintenance philosophy for telecommunications networks.* +- [6] CCITT Recommendation M.85 *Fault report points.* +- [7] CCITT Recommendation M.1045 *Preliminary exchange of information for the provision of international leased circuits.* +- [8] CCITT Recommendation M.1016 *Assessment of service availability performance of international leased circuits.* +- [9] CCITT Recommendation M.1510 *Exchange of contact point information for the maintenance of international services and international network.* +- [10] CCITT Recommendation M.1400 *Designation of international network etc.* +- [11] CCITT Recommendation F.14 *General provisions for one-stop-shopping arrangements.* \ No newline at end of file diff --git a/marked/M/T-REC-M.160-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.160-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.160-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.160-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.160-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c98dc836e52e734a05daa22649501270ad395558 --- /dev/null +++ b/marked/M/T-REC-M.160-198811-I_PDF-E/raw.md @@ -0,0 +1,196 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.160** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTRODUCTION AND GENERAL PRINCIPLES** + +--- + +**STABILITY OF TRANSMISSION** + +**ITU-T Recommendation M.160** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.160 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **STABILITY OF TRANSMISSION1)** + +## **1 Variation of circuit overall loss with time2)** + +1.1 The objective is that the following values should not be exceeded: + +1.1.1 difference between the mean value and the nominal value of the overall transmission loss: + +0.5 dB for all circuits, + +1.1.2 standard deviation about the mean value of the variation of the overall transmission loss: + +1.0 dB for all circuits. + +However, in the case of circuits which are set up, wholly or in part, on older type equipment, and which are composed of two or more circuit sections, a standard deviation not exceeding 1.5 dB may be admitted. + +1.2 The method for achieving the above objective values is left to the discretion of Administrations (better maintenance, fitting of automatic regulators, etc.). + +## **2 Variation of pilot levels with time on group, supergroup, etc. links** + +2.1 The objective is that the following values of M and S should be met, where M represents the mean deviation of the pilot level from its nominal value and S represents the standard deviation of the variations of the pilot level: + +2.2 conditions concerning through-connection points of group, supergroup, etc. links: + +$$|M| \leq 0.5 \text{ dB}, \quad S \leq 1.3 \text{ dB}$$ + +2.3 conditions concerning the receiving end: + +2.3.1 group links: + +$$|M| \leq 0.3 \text{ dB}, \quad S \leq 0.6 \text{ dB}$$ + +2.3.2 supergroup links: + +$$|M| \leq 0.3 \text{ dB}, \quad S \leq 0.5 \text{ dB}$$ + +2.3.3 mastergroup links: + +$$|M| \leq 0.3 \text{ dB}, \quad S \leq 0.4 \text{ dB}$$ + +2.3.4 supermastergroup links: + +$$|M| \leq 0.3 \text{ dB}, \quad S \leq 0.3 \text{ dB}.$$ + +## **3 Practical application of limits** + +The assumption is made that the limits set out in §§ 1 and 2 above for the variation with time of: + +- the loss of each individual circuit, or +- the level of each individual group, supergroup, etc. pilot, + +may be used as limits for the results of measurements made on a set of circuits, groups, supergroups, etc. at a given time. Experience indicates that such a use has a practical validity and hence Administrations are encouraged to use this Recommendation as giving currently practical limits for sets of circuits, groups, supergroups, etc. This does not preclude the application of these limits to single circuits, groups, supergroups, etc. + +--- + +1) Recommendation G.214 [4] also concerns the subject of the stability of transmission. + +2) See [1] concerning questions of statistical theory. + +## 4 **Reline-up of circuits, groups, supergroups, etc.** + +When a circuit, group, supergroup, etc., has its routing or composition permanently changed over part or all of its length, it is essential to ensure that a complete line-up of the circuit, group, etc., is made in accordance with the relevant line-up Recommendations since the rerouting constitutes a re-establishment of the circuit, group, etc. + +This procedure is necessary in order to maintain the transmission performance and stability of the network. The pressing needs of the operating services should not be allowed to prevent these measurements from being properly carried out, since this could only result in a degradation of the stability and performance of the circuits in the network. Under all circumstances the circuit control station should be kept advised. + +## 5 **Basic factors for transmission stability** + +The CCITT recommends that the following basic factors should be taken into account for achieving a stable network: + +### 5.1 *Staff training* + +The importance of this factor cannot be over emphasized. + +The staff should understand why level variations are to be kept to a low value and should be made fully aware of the results of incorrect adjustments. It is important that adjustments should be made only when absolutely necessary and an adjustment should never be made to cover up a fault. + +The staff must realize the possible effects of a brief interruption on any type of circuit. + +### 5.2 *Design of installations* + +Installations should be such that sudden interruptions are avoided. For example, this may be achieved by: + +- the arrangement of transmission equipment to facilitate maintenance, patching out, the replacement of subassemblies; +- the design of carrier generators with a view to great reliability; +- the design of power supplies; attention is particularly drawn to the importance of the judicious choice and grading of protective devices (fuses, circuit-breakers) in the power feeds to repeater station racks. + +*Note – See in this connection Recommendation G.231 [2].* + +### 5.3 *Care in the organization of work in international exchanges, repeater stations, and on the transmission lines, cables and systems used in the international network* + +Experience has shown that operations carried out on exchange and repeater station equipment and on the external plants (underground cables, etc.) are a major cause of attenuation and phase variations and of interruptions to service in the international network. + +All work liable to cause interference should therefore be carried out, when possible, at times of light traffic. It must be recognized that for very long routes it will become increasingly difficult to find suitable periods of light traffic, bearing in mind the time differences which will exist between the terminal countries on such routes. This will require good coordination and cooperation between Administrations. In particular, the control stations should be consulted well in advance (see Recommendation M.490). + +### 5.4 *Care in the organization of maintenance* + +The same reasons for transferring working operations to times of light traffic apply to maintenance operations. + +It is desirable to avoid all equipment changeovers which are not absolutely necessary. + +It is also desirable to guard against maintenance operations which appear harmless but which may, however, result in short interruptions and which are all the more dangerous if they affect common units (e.g. changeover of master oscillators). + +### 5.5 *Power supplies* + +5.5.1 Too frequent changeover of power supplies for routine maintenance must be avoided. It should be possible to make partial tests to check that the standby motor-generator starts, without changing over the power supplies. + +5.5.2 The instruction or training of staff during the day on working power supplies should be forbidden. + +5.5.3 Changeover of power supplies should be carried out at times of light traffic and as far as possible at night. + +5.5.4 To ensure that circuits in the international network are not interrupted owing to the failure of public power supplies, repeater stations in the international network should have power-continuity arrangements which ensure that the transmission equipment continues to operate, *without any interruption*, in the event of a failure of the public power supply. + +### 5.6 *Care in the testing of new equipment* + +Equipment should not be put into service until after the most thorough inspection. It is necessary to ensure that the pressing needs of the operating services do not result in these tests being omitted or hastily done. + +Where the urgent requirements of the operating services resulted in equipment being put into service before it had been sufficiently tested, the equipment should be temporarily taken out of service and a thorough inspection made as soon as possible. + +### 5.7 *Vibration testing* + +Vibration tests, using the principles described in [3], help in improving transmission stability and in ensuring satisfactory operation of transmission equipment. They should be made, wherever applicable, when new equipment is put into service, under special circumstances for fault locating purposes or even as a routine measure for preventive maintenance, if the Administration concerned deems it necessary. + +### 5.8 *Automatic regulation by pilots (group pilots, supergroup pilots, etc.)* + +In carrier systems, the presence of pilots (line pilots, group pilots, supergroup pilots, etc.) makes it possible to supervise transmission, to keep track of short-duration phenomena where necessary and to give the alarm if there are large variations in level. + +Regulation by pilots and the way such regulation (manual or automatic) is carried out has a decisive effect on transmission stability. In addition to regulation by line pilots, with which wideband transmission systems are normally equipped, it may be necessary to regulate the group links themselves (group links, supergroup links, etc.), both to achieve adequate stability for the circuits formed from the groups and to reduce system overloading risks due to the existence of unduly high line levels. + +Automatic regulation of links is a convenient means to meet the requirements for the values of M and S of the pilot levels as stated under § 2 above. Therefore, automatic regulators should be fitted into a link when these limits cannot be achieved by other means. + +However, when setting up a link the need for fitting automatic regulators cannot be determined solely by these requirements. It is also necessary to take practical considerations into account such as those given in the Annex to this Recommendation. + +In the case of through-connection points of group, supergroup, etc. links, the insertion of automatic regulators prevents overloading of sections further down the line. If a link is through-connected several times and several regulators have to be inserted for the same direction of transmission to meet the conditions of § 2.2 above, the first insertion should be made at the first through-connection point requiring regulation in that direction of transmission. A regulator should be inserted at the through-connection point nearest the frontier (in the outgoing direction) when there are one or more other through-connection points before this point on the same link. This is to ensure that the level of the signals entering the next country is kept within the prescribed limits. + +# ANNEX A + +(to Recommendation M.160) + +## **Practical aspects to be considered when determining the need for regulators** + +When setting up a link the need for fitting regulators cannot be determined solely by the requirements of § 2 above of this Recommendation. It is necessary to take the following practical considerations into account. + +A.1 In order to establish that a link meets the stability requirements of this Recommendation it is either necessary to conduct long-term tests at the time of setting up the link or to accept measurements made on similar links, that is, to predict the performance. + +If the former method is adopted, then, in the case of a link passing in transit through the territory of a third Administration it is probable that transit charges will apply from the date the link is set up. In any event, the cooperation of the distant terminal Administration will be required and this may not be readily forthcoming. + +If the latter method is adopted and the stability requirements are not met, then the problem will arise of taking the link out of service to fit a regulator and to reline the link. This could entail a substantial loss of revenue and will require distant end cooperation. + +A.2 It is unusual for a supergroup to be provided with all five groups allocated from the outset and it cannot be assumed that these groups will end at the same point as the supergroup. In any case, if a group that ends at the same point is changed to a through-group, then, unless a supergroup regulator has already been fitted, it may be necessary to interrupt service to fit a regulator and reline the supergroup link. + +A.3 Consideration also has to be given to the restoration requirements when deciding to fit regulators to supergroup links. Lack of such regulators may seriously hamper restoration arrangements. + +A.4 Frequent rearrangements occur on international routes and are outside the control of the distant Administration. + +# **References** + +- [1] CCITT Supplement *Statistical theory requirements*, Green Book, Vol. IV.2, Supplement No. 1.6, ITU, Geneva, 1973. +- [2] CCITT Recommendation *Arrangement of carrier equipment*, Vol. III, Rec. G.231. +- [3] CCITT Supplement *Vibration testing*, Green Book, Vol. IV.2, Supplement No. 2.9, ITU, Geneva, 1973. +- [4] CCITT Recommendation *Line stability of cable systems*, Vol. III, Rec. G.214. \ No newline at end of file diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1d022ba4603d51bf8dabfa0cde2212fade5e13b --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a943ab4b666472d769ceb39464207819fde8936efdff7b3dff96acf3adab8041 +size 78403 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad351c53ff999099a9f7d7b00da3fd5ad247b0cc --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28b3cd903682d11ba7711d0e765b7c0d5360e54caaa40e21cfc47f7403ef39e7 +size 22961 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0cf64ab3a9dc22e4ff7e034939f8824c6864caa --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba640aeb533d841075855b134be113bb14ab40d3841d35806d7691948af57f25 +size 75647 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fad47a394a3f1918cfc12741e4980bd96553acb --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a4f3eed6518499d85adeccd31ec47f9470d3a3ad3ac83d358cf73fd4d9d8dc8 +size 8207 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3d8f4d85fdbab9e47867aa193a6bb1fb21bd406 --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a9c5d92260a30649c44ab79adc0159737e02096f034dd146c0a17962424cb0c +size 217158 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a257837fd3149b8fb183ee555e2054009a960be --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52d397f22b5f38920f855676e5540b10b6e2694338e7eb67c98d876a3b5c3acc +size 5988 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d4a7e0ae18d5c0f93671aa5e137dced2acaeb5 --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5923a9f3b6a915c732b5ade0cacaa4e21f86fde87dfaeb43318f7281aae6c6a +size 40475 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..764c6902582b800bd548cd62da95a327d192c18f --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/a738993919a50143787084ee7ce6e2f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:897b6e79865bb9d9cebf6b51cbdb1ff92a8ad87ee6c6f88dc39a9142485797ef +size 76022 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60060f3cdd90ef960b89d40600045331de3d0d88 --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d444d5899844ed0e06912ad8b55cbe5bc40668e7ac24f2fbf41c7d21c9de645 +size 43940 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d26e7aa49be6edef134404a7a52c6f03255c412 --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:022eb5fc381395c8fac22f19fc3a57ffc75366d28b65d19d516c5caf0e5b253c +size 49258 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/M/T-REC-M.20-199210-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fc2113b14e29e55ef879db083d8c2eea4ea5a9d --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02d6eb4dfcc9b901d8135c7fe31d13486dbadc76616215c4ef7c50cd248b4c73 +size 45138 diff --git a/marked/M/T-REC-M.20-199210-I_PDF-E/raw.md b/marked/M/T-REC-M.20-199210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4951a762b57695ab23a6583de70b746d72950c63 --- /dev/null +++ b/marked/M/T-REC-M.20-199210-I_PDF-E/raw.md @@ -0,0 +1,900 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +**M.20** + +(10/92) + +**MAINTENANCE: INTRODUCTION +AND GENERAL PRINCIPLES** + +--- + +**MAINTENANCE PHILOSOPHY FOR +TELECOMMUNICATION NETWORKS** + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +**Recommendation M.20** + +--- + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation M.20 was revised by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. + +# --- CCITT NOTES + +- 1) In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency. +- 2) A list of abbreviations used in this Recommendation can be found in Annex A. + +## Recommendation M.20 + +# MAINTENANCE PHILOSOPHY FOR TELECOMMUNICATIONS NETWORKS1) + +(revised 1992) + +# *Abstract* + +This Recommendation describes maintenance philosophy for telecommunications networks. It also defines network maintenance phases, network supervision capabilities, and bringing into service requirements. + +## *Keywords* + +- maintenance, +- maintenance entity, +- network. + +# 1 General + +1.1 Maintenance involves the whole of operations required for setting up and maintaining, within prescribed limits, any element entering into the setting-up of a connection (see Recommendation M.60)2). In order to properly plan and program the maintenance operations required to establish and maintain an analogue, digital or mixed network, the following general strategy is recommended. + +1.1.1 A maintenance organization should be established using the guiding principles set forth in Recommendations M.70 [11] and M.710 [12] for automatic circuits switched over analogue, digital and mixed networks. In addition, the concept of control and subcontrol stations found in Recommendations M.80 [13] and M.90 [14] for international circuits and transmission systems should be implemented. + +1.1.2 The strategy should include the following maintenance operations considerations: + +- a) It should consider the evolution of the network from the present highly analogue environment to the future almost wholly digital environment. In doing this, it must consider the new services and functions offered by the networks (e.g. CCITT Signalling System No. 7 and ISDN) and the maintenance tools and capabilities becoming available (e.g. performance monitoring). +- b) It should employ an overall maintenance philosophy that uses the maintenance entity concept, failure classification and network supervision process specified in § 3. +- c) It should provide for the maintenance of the network systems, equipment and circuits during the following activities: + - installation and acceptance testing (§ 4); + - bringing into service (§ 4); + - keeping the network operational (§ 5). +- d) It should support other maintenance activities (§ 6) associated with the administration of maintenance operations (e.g. data bases, spare parts, failure statistics, etc.) along with a detailed plan for preventive maintenance, where required, on the various telecommunication equipments (hardware and software). + +--- + +1) The principles described in Recommendation M.21 [15] should also be taken into account. + +2) It is recognized that for some Administrations, bringing into service is not considered to be part of maintenance. + +- e) It should have as a major aim to minimize both the occurrence and the impact of failures and to ensure that in cause of failure: + - the right personnel can be sent to; + - the right place with; + - the right equipment; + - the right information at; + - the right time to perform; + - the right actions; and + - the right notification. + +1.2 To apply this general strategy in a network, the following principles can be used: + +### *Preventive maintenance* + +The maintenance carried out at predetermined intervals or according to prescribed criteria and intended to reduce the probability of failure or the degradation of the functioning of an item. + +### *Corrective maintenance* + +The maintenance carried out after fault recognition and intended to restore an item to a state in which it can perform a required function. + +### *Controlled maintenance* + +A method of sustaining a desired technical performance by the systematic application of supervision, testing and performance sampling in order to minimize preventive maintenance and to reduce corrective maintenance. + +1.3 In general for all three types of network (analogue, digital and mixed), the use of controlled maintenance principles is recommended, i.e., the maintenance actions are determined on the basis of information generated in the maintained system or coming from auxiliary supervision systems. + +1.4 The advantages of the controlled maintenance approach are that it directs future maintenance activity to those areas where a known improvement in service to the customer will be achieved. The monitoring techniques which are inherent in controlled maintenance provide data which simplify the identification of hidden faults by using statistical analysis. + +1.5 The smaller the portion of the network which is affected by a failure, the more difficult and/or less economic it may be to detect it using controlled maintenance techniques. In these cases corrective and/or preventive maintenance techniques may have to be employed. + +1.6 In analogue and mixed networks a mixture of the above-mentioned principles are used, depending on the existing equipment included in the network (see Recommendations M.710, M.715 to M.725). + +1.7 The maintenance philosophy and fundamental principles are closely linked to + +- availability performance; +- network technical performance; +- network economics. + +# **2 Maintenance objectives** + +## **2.1 Purpose** + +The main purpose of a general maintenance philosophy for analogue, digital and mixed networks is to accomplish the aims defined in § 1.1. + +In addition the following objectives should be fulfilled: + +- for a defined level of service the total cost should be kept to a minimum by the use of appropriate methods (e.g. centralized operation and maintenance); +- the same maintenance philosophy should be applied to exchanges, transmission equipment, data equipment, subscriber terminals, etc., wherever possible. + +## 2.2 Economics + +New technology provides new possibilities for low cost maintenance not only for individual exchanges, but for the whole network. + +The operation and maintenance functions in a network should be planned in such a way that the life cost will be a minimum. For a defined level of service the total cost consists of + +- investment cost; +- operations cost; +- maintenance cost; +- cost for loss of traffic. + +## 2.3 *Transition from analogue to digital networks including ISDNs* + +The basic philosophy, as described in this Recommendation, is valid in principle for analogue, mixed and digital networks. However, many digital network parts are more suited to the implementation of controlled maintenance than are analogue network parts. Due to new technological developments, maintenance functions can be incorporated within digital equipment. Analogue equipment often requires additional external maintenance systems in order to permit controlled maintenance, e.g. ATME No. 2 (see Recommendation O.22 [1]). + +## 2.4 *Centralized maintenance operations* + +The introduction of digital telecommunications equipment with enhanced maintenance operations functions, including the facility for remote reporting and control, provides new opportunities for centralization. Supplement No. 6.2 [2] provides a description of a centralized maintenance organization. There are many benefits that can be gained from centralization. These include the ability to + +- be more flexible in the organization of maintenance operations and administration; +- utilize highly skilled human resources more efficiently; +- utilize more effectively data and data bases; +- improve maintenance effectiveness; +- decrease maintenance costs; +- increase the availability of transmission and switching systems; +- improve quality of service. + +*Note* – By the use of remote terminals, an Administration can choose how they allocate their technical staff between local and centralized locations. + +Because of these benefits, it is recommended that centralized maintenance and other operations capabilities be considered when specifying new telecommunications systems and equipment. The general principles for setting-up, operating and maintaining a Telecommunication Management Network (TMN) to support centralized maintenance and other operations are given in Recommendation M.3010 [16]. + +In addition, the introduction of open or standardized interfaces between Network Elements (NEs) and Operations Systems (OS) via TMN, including interfaces between TMNs will allow for enhancing maintenance, operations and testing procedures. These new enhanced procedures will be based upon remote capabilities to perform the following: + +- loopbacks; +- access to performance and test data; +- status change and control; +- switchovers; +- others. + +# 3 Overall maintenance philosophy + +## 3.1 Network components for maintenance + +### 3.1.1 Maintenance entity concepts + +In order to facilitate efficient maintenance, the telecommunication network (analogue and digital) is divided into parts called Maintenance Entities (MEs), Maintenance Entity Assemblies (MEAs) and Maintenance Sub-Entities (MSEs). Examples of MEs, MEAs and MSEs are given in Figures 1/M.20, 2/M.20 and 3/M.20. + +![Diagram of maintenance entity concept for digital transmission networks showing components like Digital switch, ET, DIG MUX, LT, and Two-way generator, with labels for ME, MSE, MEA, Digital line system, and Digital circuit.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +The diagram illustrates a digital transmission path with various network elements and their maintenance boundaries. From left to right, the components are: a Digital switch (represented by a box with an 'X'), an Exchange terminal (ET), a Digital muldex (DIG MUX), a Line terminal (LT), a Two-way generator (represented by a box with two triangles), another Line terminal (LT), another Digital muldex (DIG MUX), an Exchange terminal (ET), and a final Digital switch. Maintenance boundaries are indicated by double-headed arrows above the components: + + +- ME (Maintenance entity):** There are five individual ME segments. The first covers the first ET, the second covers the first DIG MUX, the third covers the first LT, the fourth covers the Two-way generator, and the fifth covers the second ET. +- MSE (Maintenance sub-entity):** There are three MSE segments. The first covers the first LT, the second covers the Two-way generator, and the third covers the second LT. +- MEA (Maintenance entity assembly):** A single long MEA segment covers the first DIG MUX, the first LT, the Two-way generator, the second LT, and the second DIG MUX. +- Digital line system:** A segment covering the first LT, the Two-way generator, and the second LT. +- Digital circuit:** The longest segment, covering the first ET, the first DIG MUX, the first LT, the Two-way generator, the second LT, the second DIG MUX, and the second ET. + + The diagram is labeled 'T0403690-93' at the bottom right. + +Legend: + +- X Digital switch +- △ +▽ Two-way generator +- ME Maintenance entity +- MSE Maintenance sub-entity +- ET Exchange terminal +- LT Line terminal +- DIG MUX Digital muldex +- MEA Maintenance entity assembly + +Diagram of maintenance entity concept for digital transmission networks showing components like Digital switch, ET, DIG MUX, LT, and Two-way generator, with labels for ME, MSE, MEA, Digital line system, and Digital circuit. + +FIGURE 1/M.20 +Maintenance entity concept for digital transmission networks + +![Maintenance entity concept for the ISDN subscriber network diagram](fc46871d72c65d3381d9201646d23439_img.jpg) + +This diagram illustrates the maintenance entity concept for an ISDN subscriber network. It shows a sequence of components from left to right: Terminal Equipment 1 (TE1), Terminal Equipment 2 (TE2) connected to a Terminal Adaptor (TA), a Network Terminal 2 (NT2), a Network Terminal 1 (NT1), a Line Terminal (LT), and an Exchange Terminal (ET). The components TE1, TE2, TA, and NT2 are grouped under the label 'Under study'. Vertical dashed lines labeled S, T, U, and V mark specific reference points. A 'Digital line system' is indicated between NT1 and LT. Maintenance Entities (ME) are shown as segments: one between NT2 and NT1, another between NT1 and LT, and a third between LT and ET. The diagram is labeled T0403700-93. + +ET Exchange terminal + LT Line terminal + ME Maintenance entity + NT Network terminal + TA Terminal adaptor + TE Terminal equipment + +Maintenance entity concept for the ISDN subscriber network diagram + +FIGURE 2/M.20 +Maintenance entity concept for the ISDN subscriber network + +![Maintenance entity concept for analogue networks diagram](a738993919a50143787084ee7ce6e2f2_img.jpg) + +This diagram illustrates the maintenance entity concept for analogue networks. It shows a sequence of components from left to right: Exchange, Channel Translation Equipment (CTE), Group Translation Equipment (GTE), Supergroup Translation Equipment (STE), Line Terminal (LT), a Two-way repeater (represented by two triangles), another Line Terminal (LT), STE, GTE, CTE, and another Exchange. The components between the two LTs are grouped under the label 'Analogue line system'. The entire sequence between the two Exchanges is labeled 'Analogue circuit'. Maintenance Entities (ME) are shown as segments: between Exchange and CTE, CTE and GTE, GTE and STE, STE and LT, between the two LTs (labeled MEA), LT and STE, STE and GTE, GTE and CTE, and CTE and Exchange. Maintenance Sub-entities (MSE) are shown between the LTs and the Two-way repeater. The diagram is labeled T0403710-93. + +CTE Channel translation equipment + GTE Group translation equipment + STE Supergroup translation equipment + MEA Maintenance entity assembly + MSE Maintenance sub entity + ME Maintenance entity + LT Line terminal + +Two-way repeater + +Maintenance entity concept for analogue networks diagram + +FIGURE 3/M.20 +Maintenance entity concept for analogue networks + +##### 3.1.1.1 *Definition of Maintenance Entity* + +Maintenance entities are defined by the following requirements: + +- The different equipment of a telecommunications network constituting the MEs are interconnected at consecutive and easily identifiable interface points.3) At these points the interface conditions defined for these equipment apply and they possess the means of detecting maintenance events and the means of restoration. +- If the telecommunication equipment supports bidirectional transmission, it normally consists of telecommunications equipment transmitting in both directions and then both directions are considered part of the same ME. +- When a failure occurs within a network, it is desirable that the maintenance alarm indication appears at the failed maintenance entity. When this is not practical, the indication should appear at the closest possible entity. +- Maintenance alarm information indications in an entity should not cause related alarm information indications at other entities. In the event that such indications are permitted to occur, they should clearly indicate that the failure has occurred upstream, and not in the other entities displaying the information. + +Meeting these four requirements ensures that the responsible maintenance personnel are called into action, and that usually no unnecessary maintenance activity is initiated elsewhere. + +In a digital network, for example, easily identifiable points may be provided by digital distribution frames. Even in a location where no digital distribution frame is provided, an equivalent point, where defined interface conditions apply, will normally be identifiable. The interface between the exchange terminals and the digital switch may be accessed on a virtual basis. + +##### 3.1.1.2 *Maintenance Entity interface* + +An ME has to perform a determined function between telecommunication interfaces (see Figure 4/M.20). The performance is checked by internal failure detection and conveyed to the maintenance interface either automatically after a failure occurrence, or after a request for maintenance information. + +![Diagram of a Maintenance Entity interface. A central box labeled 'Maintenance entity' is connected to 'Telecommunication interfaces' on both the left and right via double-headed arrows. Below the box, a dashed horizontal line represents the 'Maintenance interface'. Below this line, two arrows point to the maintenance interface: one labeled 'Maintenance information' and the other 'Request for maintenance'. The code 'T0403720-93' is shown to the right of the maintenance interface line.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +The diagram illustrates a central 'Maintenance entity' box. It has bidirectional connections to 'Telecommunication interfaces' on both its left and right sides. Below the box, a dashed horizontal line represents the 'Maintenance interface'. Two arrows point from below towards this interface: one labeled 'Maintenance information' and the other 'Request for maintenance'. The code 'T0403720-93' is positioned to the right of the maintenance interface line. + +Diagram of a Maintenance Entity interface. A central box labeled 'Maintenance entity' is connected to 'Telecommunication interfaces' on both the left and right via double-headed arrows. Below the box, a dashed horizontal line represents the 'Maintenance interface'. Below this line, two arrows point to the maintenance interface: one labeled 'Maintenance information' and the other 'Request for maintenance'. The code 'T0403720-93' is shown to the right of the maintenance interface line. + +FIGURE 4/M.20 +**Maintenance entity interface** + +In addition, other operations and administrative functions may be carried out by the maintenance interface. Several types of maintenance interfaces are described in Recommendation M.3010 [16] which covers the TMN. + +3) If an easily identifiable interface point is not available, the interface point may be replaced by a point permitting sectionalization with functions such as, e.g. looping-back or performance monitoring. + +##### 3.1.1.3 *Definition of Maintenance Entity Assembly* + +A maintenance entity assembly (MEA) is defined by the following requirements: + +- an MEA contains a group of MEs assembled for additional maintenance purposes; +- requirements that apply for MEs apply as well for MEAs; +- an MEA may detect failures and maintenance event information which can not be detected by MEs; +- an MEA may provide end-to-end maintenance alarm information which can not be provided by MEs. + +End-to-end information may be collected by using additional supervision means. + +##### 3.1.1.4 *Definition of Maintenance Sub-Entity (MSE)* + +A maintenance sub-entity is defined by the following principles: + +- the different parts of an MSE constituting the MEs are interconnected at consecutive and easily identifiable interface points; +- when a failure occurs within an MSE, it is desirable that the maintenance alarm information indication appears at the failed maintenance entity containing the MSE; +- a failed MSE should be identified as failed by the fault location process, but should lead only to the identification of the failed ME by the supervision process; +- an MSE generally corresponds to the item which is replaceable during routine operations in the event of a failure. + +##### 3.1.1.5 *Maintenance Entity choices* + +The choice of ME, MEA and MSE should be compatible with the maintenance organization of an Administration (Recommendations M.710 to M.725 [12]). + +#### 3.1.2 *Support Entity concept* + +The Support Entity functions (SEF) are fault localization, billing, protection switching, etc. They are not directly involved in the telecommunication process. A Support Entity (SE) can contain one or more SEFs. + +#### 3.1.3 *Network Element concept* + +The Network Element (NE) and the Network Element function (NEF) are defined in Recommendation M.3010 [16]. Essentially an NE is telecommunication equipment which may have associated or built-in capability for surveillance, reporting and/or control. + +#### 3.1.4 *Relationship between Maintenance Entities, Support Entities and Network Elements* + +Examples of parts of network elements and an example of digital switch with billing equipment are given in Figures 5/M.20 and 6/M.20. + +## 3.2 *Failure concepts* + +The following definitions and classifications are used in developing the concept of a failure. + +### 3.2.1 *Anomalies* + +An anomaly is a discrepancy between the actual and desired characteristics of an item. + +The desired characteristic may be expressed in the form of a specification. + +An anomaly may or may not affect the ability of an item to perform a required function. + +As an example, for a multiplexer one type of elementary information that can be detected is an error in the frame alignment word. This elementary information is an anomaly. More examples of anomalies are given in Recommendation M.2100 [17]. + +![Diagrams of Maintenance Entity (ME) and Support Entity (SE) interfaces.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram consists of two parts, (a) and (b), showing the interface structure of network elements. + +**a) Maintenance Entity (ME):** A central rectangular block labeled "ME" has multiple horizontal lines representing interfaces entering from the left and exiting to the right. Above the block, a vertical line connects to a horizontal line labeled "M, Q". Below the block, two vertical lines connect to horizontal lines labeled "T". + +**a) Support Entity (SE):** A central rectangular block labeled "SE" has a vertical line above it labeled "M, Q" and a horizontal line to its right labeled "TS". + +Below the diagrams is a legend: + +- T Telecommunications interface +- Q Qx, Q3, interfaces +- M (Non-standardized) maintenance interface +- TS Telecommunications support interface + +Diagrams of Maintenance Entity (ME) and Support Entity (SE) interfaces. + +FIGURE 5/M.20 +Parts of network elements + +![Diagram of network elements (Billing equipment, Switch support, Digital switch) and their interfaces.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +The diagram shows three network elements: "Billing equipment", "Switch support", and "Digital switch". + +- The "Billing equipment" and "Switch support" blocks are at the top, each connected to a "Q3" interface above it. +- Both "Billing equipment" and "Switch support" have a "TS" (Telecommunication support interface) on their left and right sides respectively. +- Below each of these two blocks is an "SE" (Support Entity) label, which is connected to an "M" (Non-standard maintenance interface) label. +- The "Digital switch" block is at the bottom, connected to the "M" interfaces from the "Billing equipment" and "Switch support" blocks. +- The "Digital switch" has "T" (Telecommunication interface) labels on its left and right sides. + +Below the diagram is a legend: + +- T Telecommunication interface +- TS Telecommunication support interface +- M Non-standard maintenance interface +- Q3 TMN Q3 interface + +Diagram of network elements (Billing equipment, Switch support, Digital switch) and their interfaces. + +FIGURE 6/M.20 +Example of Network Elements (NE) + +#### 3.2.2 Defects + +A defect is a limited interruption in the ability of an item to perform a required function. It may or may not lead to maintenance action depending on the results of additional analysis. + +Successive anomalies causing a decrease in the ability of an item to perform a required function are considered as a defect. + +As an example, the G.700-Series Recommendations [3] recommends that three consecutive errored frame alignment words will give a loss of frame alignment. This loss of frame alignment is a defect. More examples of defects are given in Recommendation M.2100 [17]. + +The process of using anomalies and defects is explained in § 3.3. + +#### 3.2.3 *Failures* + +A failure is the termination of the ability of an item to perform a required function. + +*Note* – After failure, the item has a fault. + +Analysis of successive anomalies or defects affecting the same item can lead to the item being considered as “failed”. + +##### 3.2.3.1 *Classification of failures* + +The severity of the failure depends on the failure effect. This effect can be related to + +- the network service performance requirements as experienced by the subscribers; +- the probability that multiple failures will occur, thus resulting in a deteriorating performance as seen by the customer; +- the probable loss of revenue to the Administration. + +The failures can be classified according to their importance and consequences to the quality of service provided to the subscribers and to the network technical performance: + +- Failures which result in complete interruption of service(s) for one or several subscribers. +- Failures which result in degradation of service(s) (e.g. degradation of transmission quality) to one or several subscribers. +- Failures which decrease the availability performance of the equipment and/or the network but do not affect the subscribers. +- Failures can result in either a permanent or intermittent conditions. +- The severity of a failure can be determined by measuring the down time, up time and failure rate of the ME. These items are defined in Supplement No. 6 to Fascicle II.3 [4]. + +#### 3.2.4 *Fault* + +A fault is the inability of an item to perform a required function, excluding that inability due to preventive maintenance, lack of external resources or planned actions. + +*Note* – A fault is often the result of a failure of the item itself, but may exist without prior failure. + +## 3.3 *Network supervision* + +Network supervision is a process in which the anomalies and defects detected by the maintenance entities ME or MEA are analysed and checked. This analysis may be internal or external to the entity. In the external case it can be accomplished either locally or on a centralized basis. + +For maintenance, this supervision process has to include the following actions: + +- a) Locating “failed” equipment, or the equipment in which a fault is suspected or a failure is believed to be imminent. It is generally carried out by analytical or statistical identification processes. The supervision process consists of three continuously running concurrent processes + - the supervisory process for anomalies (short period); + - the defect supervisory process (medium period); and + - the malfunction supervisory process (long period). + +Each process is interfaced by the characteristic data, e.g. accumulated anomaly data and accumulated defect data. The supervisory processes for anomalies and defects respectively, indicate that the anomaly or defect states have been reached. The malfunction supervisory process evaluates the performance level of the maintenance entity and judges it to be normal, degraded or unacceptable. These levels are determined from the anomalies and defects received and analyzed over a given time. The thresholds + +limiting degraded or unacceptable performance limits and the process period are defined for each defect and confirmed fault or group of anomalies and defects and also for each type of entity. Indications of degraded and unacceptable performance levels are generated each time the corresponding threshold is exceeded. This process is shown in Figure 7/M.20. + +![Flowchart of the supervision process for a maintenance entity. The process starts with MEF and SEF providing 'Elementary information' to the 'Anomalies supervision process' (Short period process). This leads to 'Accumulated anomaly data', which feeds into the 'Defect supervision process' (Medium period process). This leads to 'Accumulated defect data', which feeds into the 'Performance evaluation' (Long period process). The 'Performance evaluation' is part of the 'Malfunction supervision process' and leads to three outcomes: 'Unacceptable performance', 'Degraded performance', and 'Normal performance'. The first two lead to a box 'Malfunction or possibility of malfunction detected', which then leads to 'Maintenance phases'. A feedback loop from 'Accumulated defect data' also feeds into the 'Performance evaluation'.](007b053fe94a8348f75128a584503fd0_img.jpg) + +``` + +graph TD + MEF((MEF)) -- "Elementary information" --> ASP((Anomalies supervision process)) + SEF((SEF)) -- "Elementary information" --> ASP + ASP -- "Short period process" --> AAD[Accumulated anomaly data] + AAD --> DSP((Defect supervision process)) + DSP -- "Medium period process" --> ADD[Accumulated defect data] + ADD --> PE((Performance evaluation)) + ADD -- "Long period process" --> PE + subgraph MSP [Malfunction supervision process] + PE + UP[Unacceptable performance] + DP[Degraded performance] + NP[Normal performance] + MPD[Malfunction or possibility of malfunction detected] + PE --> UP + PE --> DP + PE --> NP + UP --> MPD + DP --> MPD + end + MPD --> MP[Maintenance phases] + T0403750-93[T0403750-93] + +``` + +Flowchart of the supervision process for a maintenance entity. The process starts with MEF and SEF providing 'Elementary information' to the 'Anomalies supervision process' (Short period process). This leads to 'Accumulated anomaly data', which feeds into the 'Defect supervision process' (Medium period process). This leads to 'Accumulated defect data', which feeds into the 'Performance evaluation' (Long period process). The 'Performance evaluation' is part of the 'Malfunction supervision process' and leads to three outcomes: 'Unacceptable performance', 'Degraded performance', and 'Normal performance'. The first two lead to a box 'Malfunction or possibility of malfunction detected', which then leads to 'Maintenance phases'. A feedback loop from 'Accumulated defect data' also feeds into the 'Performance evaluation'. + +MEF Maintenance entity function +SEF Support entity function + +FIGURE 7/M.20 +**Supervision process for a maintenance entity** + +- b) Reporting of failures and faults to maintenance personnel. +- c) Transmission of data to the maintenance personnel, relating to specific functional features of the network (traffic, state of equipment, particular malfunctions, etc.). This information can be transmitted systematically or on demand. +- d) Protecting the system by transmitting to all network equipment involved, the necessary information for automatic initialization of internal or external restoration mechanisms, e.g. reconfiguration, traffic rerouting, etc. +- e) Modify the supervision process due to + - the type of service being offered over a given portion of the network; + - the time of day. + +# 4 Bringing-into-service new international transmission systems and circuits + +## 4.1 *Installation and acceptance testing*4) + +For new systems, this work may include the necessary installation of new equipment. Once the new equipment is working, the Administration should make the necessary tests to ensure the new system meets required specifications. Acceptance testing of the new system or equipment should be based on policies established by the Administration. However, Administrations may wish to use the performance monitoring techniques found in Recommendation M.34 [18] to aid in their acceptance testing of new transmission systems. + +## 4.2 *Setting-up and lining-up* + +As soon as Administrations have decided to bring a new international transmission system and/or circuit into service, the necessary contacts are made between their technical service for the exchange of information. Those services jointly select the control and sub-control stations for the new system or circuit (see Recommendations M.80 [13] and M.90 [14]). + +The technical service of each Administration is responsible for the setting-up and lining-up of the line on circuit sections in its territory, and for arranging that the adjustments and tests required are made by the station staff concerned. + +## 4.3 *Detailed considerations* + +To set-up a line section or circuit which crosses a frontier, Administrations should arrive at bilateral agreements on the basis of CCITT Recommendations and, for radio-relay sections, the Recommendations of the CCIR. Administrations should refer to the following Recommendations for detailed considerations associated with bringing-into-service the following entities: + +### 4.3.1 *New transmission systems* + +Recommendations M.450 to M.475 [19] and M.34 [18]. + +### 4.3.2 *Telephone circuits* + +Recommendations M.570 to M.590 [20]. + +### 4.3.3 *Common channel signalling systems* + +Recommendations M.4030 [21] and M.4100 [24]. + +### 4.3.4 *Leased and special circuits* + +Recommendations M.1000-Series [26]. + +### 4.3.5 *International digital paths, sections and line sections* + +Recommendations M.2100 [17] and M.2110 [23]. + +## 4.4 *Other considerations* + +After the control station has determined from reports provided by the subcontrol station that appropriate tests and adjustments have been performed, the control station conducts overall tests of the system or circuit. The overall tests results are recorded, operations systems data bases are updated and synchronized between Administrations, and the system and/or circuits are placed in service. At this time the system and/or circuits are transferred to a performance measuring state (see § 5.1) to track and ensure their continuing proper operation. + +--- + +4) Installation and acceptance testing is generally not considered part of maintenance. + +# 5 Maintenance phases under normal and fault conditions + +Under normal conditions in the network, performance information should be gathered from MEs on a continuous or periodic basis. This data can be used to detect acute fault conditions which generate alarm reports. Further analysis may reveal subtle degradations which generate maintenance information reports. + +After the occurrence of a failure in the network, a number of maintenance phases are required to correct the fault and to protect, when possible, the traffic affected by the fault if it has been interrupted. + +As an example, Figure 8/M.20 lists the maintenance phases which are involved before and after a failure occurrence in a maintenance entity (ME). The parameters determining the different phases are indicated in the figure. It is intended to characterize different maintenance strategies with the aid of the maintenance phases. The mechanics used to implement the various maintenance processes should be defined in connection with each specific application in the relevant Recommendations. The maintenance phases are described below in more detail. + +## 5.1 *Performance measurement* + +Different types of performance measuring mechanisms can be used: + +- continuous checking; +- routine or periodic testing; +- checking of behavior in live traffic; +- checking of behavior in the absence of live traffic. + +The rules governing the measurement mechanisms are defined when conceiving the systems; no intervention of the maintenance personnel is necessary. Under some conditions, however, the personnel can control some operations which may prove necessary for periodic or casual checking, such as: + +- modifying the priority level of a checking process; +- modifying the nominal period in the case of periodic checking; +- carrying out some partial or recurrent checks (e.g. test on demand). + +The choice of a measurement mechanism depends on the requirements for the “quality of service” as seen by the subscribers, and on the technical network performance and the nature of the equipment. In addition, several mechanisms may be operated in the same item of equipment. + +Typical measurement mechanisms are listed below. + +### 5.1.1 *Continuous checking* + +All the time an item is active, it is being checked for good performance. If the item does not fulfill the test requirements, it is considered to have a fault. + +#### 5.1.2 *Routine or periodic testing* + +Items are tested periodically, initiated by either the system or the maintenance staff. + +The frequency of the test depends on the importance of the item, the failure rate and the number of items of that type present in the element. + +#### 5.1.3 *Checking in live traffic* + +Checking behavior in live traffic can be performed directly or statistically. + +This checking exists if the ME itself indicates a faulty performance or the continuous detection of anomalies or defects. + +All of the elementary information from the different detectors is either retransmitted by each entity to a processing unit or processed locally. + +Performance parameters are derived from this information. + +![](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +| Phase | Description | Process | Result | +|-------------------------------|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Performance measuring (§ 5.1) | Normal function of ME | By continuous or periodic (routine) checking of functions | Pass or maintenance event information | +| Failure detection (§ 5.2) | Malfunction or possibility of malfunction is detected | By continuous or periodic (routine) checking of functions | Prompt maintenance alarm
Deferred maintenance alarm
Maintenance event information | +| System restoration (§ 5.3) | Effect of failure of ME is minimized | Using blocking or changeover | Failed ME excluded from operation | +| Failure information (§ 5.4) | ME failure indication to other MEs
ME failure indication to maintenance interface | Alarm contact function or alarm message | Alarm indication signal
Service alarm
Upstream failure indication

Prompt maintenance alarm
Deferred maintenance alarm
Maintenance event information | +| Fault localization (§ 5.5) | Determination of faulty ME if fault information is insufficient | By internal test system or external test system – automatic or manual | Fault located or disappears | +| Logistic delay times (§ 5.6) | Determination of time and staff for maintenance interventions | Delay can be a few hours if initiated by DMA or PMA, or a few days if initiated by MEI | | +| Fault correction (§ 5.7) | Correction of faulty ME | By repair, changeover to spare or change of equipment | | +| Verification (§ 5.8) | Check of ME after fault correction | By internal test system or external test system automatic or manual | Pass or fail | +| Restoration (§ 5.9) | Attempt to restore normal function of ME | Unblocking or end of changeover | ME in service or in standby mode | + +T0403760-93 + +FIGURE 8/M.20 +Maintenance phases under normal and failure conditions + +##### 5.1.3.1 Processing of performance parameters + +Some performance parameters in use are Errored Seconds (ES) and Severely Errored Seconds (SES) (see Recommendation M.2100 [17]). + +Each of the performance parameters (e.g. ES, SES) is to be processed separately in order to evaluate the performance level of the entity's operation. + +##### 5.1.3.2 *Evaluation of unacceptable performance* + +Unacceptable performance is characterized by a significant and long-lasting degradation in quality. It can be associated with the faulty state (see Recommendation M.2100 [17]). + +It is ascertained by statistical analysis of each of the performance parameters individually, throughout a given time T1. + +As soon as the result of statistical analysis reaches a N1 threshold (defined for each entity individually), the entity is declared to be at an unacceptable level of performance. + +Elsewhere, for each defect corresponding to an interruption, lasting $x$ consecutive seconds, the entity is considered as having reached an unacceptable level. + +##### 5.1.3.3 *Evaluation of degraded performance* + +Each of the performance parameters is analysed statistically over a time T2 which can be a relatively long period. + +As soon as the result of statistical analysis reaches a N2 threshold (to be defined), the entity can be considered to be at degraded performance. The time T2 will depend on the entity in question. + +This checking leads to maintenance decisions on statistical grounds: + +- the number of times in which the item performs its function “normally” is compared with the number of times the performance of the item does not fulfill the requirements; +- the average time of functioning is compared with standard values; +- the number of times an item performs its function during a certain period is compared to normal values. + +If the degraded performance level is characterized by a gradual degradation in quality, the maintenance personnel should be informed before this decrease in performance becomes unacceptable to the user. + +#### 5.1.4 *Checking in the absence of live traffic (traffic is zero)* + +Checking of system internal functions is done once a process is over, or when a process has been initiated several times. Examples are operational checks which start when a customer initiates an action to use the network. + +### 5.2 *Failure detection* + +Failures should be discovered by the Administration independently of, and preferably before, the subscriber, i.e., the majority of failures are both detected and remedied without the subscriber having been aware of them. + +Failures are classified depending on their nature (see § 3.2) and may be categorized depending on their severity. Corresponding maintenance alarm information is then passed on to the appropriate entities. + +## 5.3 *System restoration* + +When a failure has occurred or performance has degraded, the following functions must be performed: + +- as a result of the medium and longer period supervision process a signal must be transmitted to all the concerned network equipment of any necessary information for automatic (preferred) initialization of internal or external restoration mechanisms, e.g., reconfiguration, traffic rerouting, etc.; +- decision on any necessary actions, e.g., putting an item “out of service” or “in testing condition”, changing to a configuration with minimal or degraded service. + +A specific protection method is recommended for transmission systems using manual or automatic restoration on a maintenance entity basis + +- a) If a failure occurs either in maintenance entities without automatic changeover capabilities or with automatic changeover capabilities but without an available stand-by, the following actions should be executed: + - 1) initiate maintenance alarm information identifying the maintenance entity containing the failed equipment; + - 2) transmit an alarm indication signal (AIS) in the direction affected (downstream direction) or give an upstream failure indication (UFI) at equipment which has not failed; + - 3) initiate a service alarm indication at the appropriate entities, e.g. primary PCM multiplex or digital switch interfaces. (As a consequence the circuits may be removed from service.) +- b) If a failure occurs in a maintenance entity having automatic changeover capability with a stand-by available, the following actions should be automatically executed: + - 1) changeover to the stand-by whether or not connections are released as a result of automatic changeover depends on the service performance objectives assigned to each maintenance entity; + - 2) initiate maintenance alarm information indicating the maintenance entity containing the failed equipment. + +### 5.4 *Failure or performance information* + +Information on failure, unacceptable performance or degraded performance will normally be transmitted to the maintenance staff. Other parts of the network are notified when appropriate. + +Information for the use of personnel is available either in the entity, when the processing of anomalies or defects is internal, or via a unit which provides processing, when external to the entity. + +#### 5.4.1 *Alarm information categories* + +The following maintenance alarm information may be associated with the information of failure or unacceptable or degraded performance: + +##### a) *Prompt maintenance alarm (PMA)* + +A PMA is generated in order to initiate maintenance activities (normally immediately) by maintenance personnel to remove defective equipment from service for the purpose of restoring good service and effecting repair of the failed equipment. + +##### b) *Deferred maintenance alarm (DMA)* + +A DMA is generated when immediate action is not required by maintenance personnel, e.g; + +- when performance falls below a set threshold but the effect does not warrant removal from service; +- when automatic changeover to stand-by equipment has been used to restore service. + +##### c) *Maintenance event information (MEI)* + +MEI is generated as a consequence of events when no immediate actions by the maintenance staff are required because the total performance is not endangered. The maintenance actions can be performed on a scheduled basis or after an accumulation of MEI indications. + +Starting with the malfunction supervisory process from Figure 7/M.20, Figure 9/M.20 shows the alarm information process for an ME. The actual PMA, DMA or MEI may or may not be generated in the ME. When generated outside the ME, the alarm information process may combine information from other sources (e.g. other MEs, time of day, traffic load, etc.) with the output from the malfunction supervisory process to decide if a PMA, DMA or MEI should be generated. When an AIS or UFI is received, an ME may be required to generate a Service Alarm (SA). + +Both the malfunction supervisory process and the alarm information process, including the use of PMAs, DMAs and MEIs, can also be applied to non-telecommunications equipment. + +![Flowchart of the alarm information process. Inputs include 'Malfunction supervisory process (Figure 7/M.20)', 'AIS or UFI', and 'Other sources'. The process generates 'SA', 'PMA', 'DMA', and 'MEI'. A bracket groups 'PMA', 'DMA', and 'MEI' as 'Maintenance alarm information'. A legend defines the abbreviations.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +``` + +graph TD + A([Malfunction supervisory process +(Figure 7/M.20)]) --> B([Alarm information process]) + C[AIS or UFI] --> B + D[Other sources] --> B + B --> E[SA] + B --> F[PMA] + B --> G[DMA] + B --> H[MEI] + F & G & H --> I[Maintenance alarm information] + I --> J(( )) + J --> B + K[T0403770-93] + +``` + +AIS Alarm indication signal + UFI Upstream failure indication + SA Service alarm + PMA Prompt maintenance alarm + DMA Deferred maintenance alarm + MEI Maintenance event information + +Flowchart of the alarm information process. Inputs include 'Malfunction supervisory process (Figure 7/M.20)', 'AIS or UFI', and 'Other sources'. The process generates 'SA', 'PMA', 'DMA', and 'MEI'. A bracket groups 'PMA', 'DMA', and 'MEI' as 'Maintenance alarm information'. A legend defines the abbreviations. + +FIGURE 9/M.20 +**Alarm information process** + +#### 5.4.2 Other fault and service indications + +In order to avoid unnecessary maintenance actions and to signal the unavailability of the service, the following fault indications are used: + +##### a) *Alarm indication signal (AIS)* + +An AIS is a signal associated with a defective maintenance entity and is, when possible, transmitted in the direction affected (downstream direction) as a substitute for the normal signal, indicating to other nondefective entities that a failure has been identified and that other maintenance alarms consequent to this failure should be inhibited. The binary equivalent of the AIS corresponds to an all 1s signal. + +*Note 1* – The AIS is different from the “alarm information to the remote end”; see § 5.4.4. + +*Note 2* – The AIS capability does not impose any restrictions on the binary content of signals which may be transmitted over the digital hierarchy at the primary multiplex and higher levels. The implications at the 64 kbit/s level and at lower bit rates are under study, since ambiguity arises between AIS and an all 1s information signal. + +*Note 3* – For a maintenance entity with multi-destination ends (e.g. in networks with TDMA/DSI satellite systems) alarm indication signals on a circuit basis may be useful. This subject is under study. + +*Note 4* – In the particular case of the 44 736 kbit/s hierarchical level, the AIS is defined as a signal + +- with a valid frame alignment signal, parity and justification control bits as defined in Table 2/G.752 [6]; +- with the tributary bits being set to a 1010 . . . sequence, starting with a binary one (“1”) after each frame alignment, multiframe alignment and justification control bit; +- and with all justification control bits being set to binary zero (“0”). + +Demultiplexers of the 44 736 kbit/s hierarchical level must produce the all 1s AIS at their tributary outputs when they receive the 44 736 kbit/s AIS at their high bit rate inputs. + +##### b) *Service alarm (SA)* + +An SA is generated at maintenance entities at which the service originates and/or terminates to indicate that the particular service is no longer available (e.g. when a primary block is no longer available for setting up connections, the PCM muldex will extend a service alarm indication to the exchange equipment). + +The service alarm should be generated when performance falls below a level specified for a particular service. This level may coincide with that for initiating also a prompt maintenance alarm. + +##### c) *Upstream failure indication (UFI)* + +The UFI given by a maintenance entity indicates that the signal arriving at that maintenance entity is defective. The UFI indicates that the failure has occurred upstream of this point, and no unnecessary maintenance activities are initiated. + +The appearance of an alarm indicates either a fault in the equipment generating the alarm or a failure of the incoming signal (an upstream failure). To distinguish between these two possibilities it is necessary to provide an independent test, either of the input signal, or of the equipment generating the alarm. The input signal can be checked for proper parity, for example, by a monitor included in the protection switching equipment. A defective input signal indicates an upstream failure. Alternatively, the equipment generating the alarm can be tested independently, (e.g. by looping), and if the equipment operates correctly, an upstream failure is indicated. + +#### 5.4.3 *Transmission and presentation of alarm information* + +The failure information at the alarm interface is used to determine the faulty ME or part of ME. The information can be presented either locally, or remotely via an alarm collection system. + +The alarms may be presented as + +- an indication at an alarm interface (e.g. contact function, d.c. signal); +- an alarm message on the man-machine interface. + +#### 5.4.4 *Alarm information to the remote end* + +Equipment which is a source of digital multiplex signals (i.e. multiplex equipment or exchanges) may, in case of a fault condition, transmit alarm information within a specified bit or specified bits of the pulse frame. This information is intended for evaluation at the remote terminal (at the end of the digital link). Examples: see Recommendations G.704, § 2.3.2 [7], G.732, § 4.2.3 [8] and G.733, § 4.2.4 [9]. + +## 5.5 *Fault localization* + +Where the initial failure information is insufficient for fault localization within a failing ME, it has to be augmented with information obtained by additional fault localization routines. The routines can employ ME internal or external test systems, initiated manually or automatically, at the local and/or remote end. + +A test system, serving one or more MEs could have the following functions: + +- alarm collection, e.g. by sampling of alarm interfaces and assembling of alarm messages; +- request for failure information, e.g. by addressing different MEs; +- test programs, e.g. for selection of essential alarms, editing, etc.; +- control of special devices, e.g. for looping measurement of electrical characteristics; +- display of results, e.g. for all MEs within a network region. + +It should be particularly noted that + +- the corrective maintenance action time and the activity of repair centres (these repair centres may receive unfailed items or sub-items) are strongly conditioned by the localization efficiency (not yet defined); +- if an ME can be subdivided into MSEs, the faulty MSE should be identified as failed in the fault localization process; +- for interchangeable items, the failed item must be identified uniquely. + +## 5.6 *Logistic delay* + +The logistic delay is the period of time between the fault localization and arrival of the maintenance staff on site. The logistic delay will depend on the type of failures and how they are reported, i.e. by PMA, DMA or MEI. + +Following a PMA or DMA alarm, fault correction will be performed normally in the course of a specific trip of the maintenance staff. The logistic delay may vary from a few hours in the case of PMA alarms, to a few days in the case of DMA alarms. + +Following an MEI, which indicates that no immediate actions are necessary, the maintenance action can be postponed until the next scheduled maintenance visit unless an accumulation of MEIs demands earlier action. + +## 5.7 *Fault correction* + +Fault correction normally requires change or repair of an ME, MSE or a part thereof. One or more fault corrections can be performed in the course of a maintenance visit. It is desirable that strategies be developed to accomplish fault correction satisfying overall maintenance objectives with a minimum number of visits, using the concept of logistic delay. + +Failed interchangeable items will be sent to a specialized repair centre, where appropriate test equipment is available (the system itself should not act as a test machine). + +Normally, cooperation between maintenance elements in different Administrations will result in the satisfactory identification and correction of faults. There may be circumstances, however, where the fault escalation procedures defined in Recommendations M.1550 [24] and M.1560 [25] may be required. + +## 5.8 *Verification* + +After the fault has been corrected, checks must be made to ensure the ME is working properly. The verification can be made locally or remotely. + +## 5.9 *Restoration* + +The repaired part of the ME or MSE is returned to service. Blocked MEs are unblocked. + +# 6 **Additional maintenance activities** + +In addition to the above-mentioned phases, the following activities may be required: + +## 6.1 *Maintenance support* + +Maintenance support covers the functions identified below: + +- management of information of network equipment in operation; +- management of operating data (routing data mainly); +- correction instruction for hardware and software; +- repairing of removable items; +- management of spare parts; +- network and equipment documentation. + +The quantity of spare parts held depends on + +- organization of maintenance entities; +- failure rate of an item; +- turn around time (actual repair time, transport); +- number of items in operation; +- risk that no spare part is available. + +## 6.2 *Failure statistics* + +If all failures are recorded, this information, after processing, can serve the following organizational functions: + +- management, e.g. evaluating system performance; +- organization of maintenance, e.g. use of test equipment, subscriber complaints versus test results, amount of spare parts; +- maintenance activities, e.g. identifying weak components where preventive maintenance actions are necessary. + +## 6.3 *Preventive maintenance actions* + +Mechanical parts (such as magnetic equipment heads) have to be cared for periodically. + +After analyzing failure statistics, decisions can be made to interchange items even before failures have occurred, if they seem to be weak items. + +# 7 **Other maintenance considerations** + +## 7.1 *Reference test frequency considerations* + +Under study. + +## 7.2 *Use of maintenance test lines and loop-backs* + +Under study. + +## 7.3 *Maintenance of common channel Signalling System No. 7 networks* + +Under study. + +# **References** + +- [1] CCITT Recommendation Q.22 *Specification for CCITT automatic transmission measuring and signalling testing equipment ATME No. 2.* +- [2] CCITT Supplement No. 6.2 *New operation and maintenance organization in the Milan Italcable Intercontinental telecommunication centre, Blue Book, Vol. IV.* + +- [3] CCITT Recommendations G.700 to G.956 *Digital networks.* +- [4] CCITT Supplement No. 6 *Terms and definitions for Quality of Service, network performance, dependability and trafficability studies, Blue Book, Fascicle II.3.* +- [5] CCITT Recommendation G.821 *Error performance on an international digital connection forming part of an integrated services digital network.* +- [6] CCITT Recommendation G.752 *Characteristics of digital multiplex equipment based on a second order bit rate of 6312 kbit/s and using positive justification.* +- [7] CCITT Recommendation G.704 *Functional characteristics of interfaces associated with network nodes.* +- [8] CCITT Recommendation G.732 *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s.* +- [9] CCITT Recommendation G.733 *Characteristics of primary PCM multiplex equipment operating at 1544 kbit/s.* +- [10] CCITT Recommendation M.60 *Maintenance terminology and definitions.* +- [11] CCITT Recommendation M.70 *Guiding principles on the general maintenance organization for telephone-type international circuits.* +- [12] CCITT Recommendation M.710 to M.725 *General maintenance organization for the international automatic and semi-automatic telephone service; fault report point; testing point; network analysis point; circuit control station; restoration control point.* +- [13] CCITT Recommendation M.80 *Control stations.* +- [14] CCITT Recommendation M.90 *Sub-control stations.* +- [15] CCITT Recommendation M.21 *Principles for maintenance philosophy and considerations for maintenance strategy for telecommunication services.* +- [16] CCITT Recommendation M.3010 *Principles for a telecommunications management network.* +- [17] CCITT Recommendation M.2100 *Performance limits for bringing-into-service and maintenance of international digital paths, sections and transmission systems.* +- [18] CCITT Recommendation M.34 *Performance monitoring on international transmission systems and equipment.* +- [19] CCITT Recommendations M.450 to M.475 *Bringing-into-service, setting up and lining up, etc.* +- [20] CCITT Recommendations M.570 to M.590 *Constitution of the circuit, setting up and lining up an international circuit, bringing-into-service an international digital circuit, etc.* +- [21] CCITT Recommendation M.4030 *Transmission characteristics for setting up and lining up a transfer link for CCSS No. 6.* +- [22] CCITT Recommendation M.4100 *Maintenance of CCSS No. 7.* +- [23] CCITT Recommendation M.2110 *Bringing digital paths, sections and transmission systems into service.* +- [24] CCITT Recommendation M.1550 *Escalation procedure.* +- [25] CCITT Recommendation M.1560 *Escalation procedure for international leased circuits.* +- [26] CCITT Recommendation M.1000-Series *International leased circuits.* + +# ANNEX A (to Recommendation M.20) + +## **Alphabetical list of abbreviations used in this Recommendation** + +| | | +|---------|--------------------------------------------| +| AIS | Alarm indication signal | +| ATME | Automatic transmission measuring equipment | +| CTE | Channel translation equipment | +| DIG MUX | Digital muldex | +| DMA | Deferred maintenance alarm | +| DSI | Digital speech interpolation | +| ES | Errored second | +| ET | Exchange terminal | +| GTE | Group translation equipment | +| ISDN | Integrated services digital network | +| LT | Line terminal | +| ME | Maintenance entity | +| MEA | Maintenance entity assembly | +| MEF | Maintenance entity function | +| MEI | Maintenance event information | +| MSE | Maintenance sub-entity | +| NE | Network element | +| NEF | Network element function | +| NT | Network terminal | +| OS | Operating system | +| PMA | Prompt maintenance alarm | +| SA | Service alarm | +| SEF | Support entity function | +| SES | Severely errored second | +| STE | Supergroup translation equipment | +| TA | Terminal adaptor | +| TDMA | Time division multiple access | +| TE | Terminal equipment | +| TMN | Telecommunication management network | +| UFI | Upstream failure indication | \ No newline at end of file diff --git a/marked/M/T-REC-M.21-199210-I_PDF-E/raw.md b/marked/M/T-REC-M.21-199210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d68a1330942774bcfedff2095de684727780cb05 --- /dev/null +++ b/marked/M/T-REC-M.21-199210-I_PDF-E/raw.md @@ -0,0 +1,195 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +**M.21** + +(10/92) + +**MAINTENANCE: INTRODUCTION AND GENERAL +PRINCIPLES OF MAINTENANCE AND +MAINTENANCE ORGANIZATION** + +--- + +**MAINTENANCE PHILOSOPHY FOR +TELECOMMUNICATION SERVICES** + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +**Recommendation M.21** + +--- + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation M.21 was revised by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency. + +## Recommendation M.21 + +# MAINTENANCE PHILOSOPHY FOR TELECOMMUNICATION SERVICES + +*(Melbourne 1988, revised 1992)* + +## *Abstract* + +This Recommendation describes the maintenance philosophy for telecommunication services. It also defines service maintenance phases, service supervision capabilities, and bringing into service requirements. + +## *Keywords* + +- service; +- maintenance; +- quality of service. + +# 1 General + +Service maintenance is the combination of all technical and corresponding administrative actions, including supervision actions, intended to retain a service in, or restore it to a state in which it can ensure meeting the applicable Quality Of Service (QOS) requirements. In order to properly plan and develop the maintenance operations required to establish and maintain a telecommunication service, the following general strategy is recommended. + +## 1.1 *Service maintenance objectives* + +### 1.1.1 *Purpose* + +Service maintenance objectives are to ensure that any deviations from defined Quality Of Service (QOS) factors and performance objectives will be corrected in timely fashion and to customer satisfaction. A concept of QOS is defined in Recommendation E.800 [1] as “the collective effect of service performances which determine the degree of satisfaction of a user of the service”. QOS comprises a number of factors or performances which are enumerated and defined in Recommendation E.800 [1]. For this purpose Administrations may designate units within the existing maintenance organization or may establish new service maintenance organization units responsible for all aspects of service maintenance. + +### 1.1.2 *Introduction of new services* + +When a new service is to be introduced, early consideration should be given to its operational and maintenance requirements. In practice, these will depend on its Quality Of Service objectives, and therefore, on performance parameters and objectives which are set for each item which is used for operating the service (e.g. equipment, network, etc.). Thus each item should be considered individually. If such an item is unique to a service, there will be new operational and maintenance requirements. If such an item is not unique to a service and it is already used in providing an existing service, consideration should be given to whether the existing operational and maintenance requirements need to be changed. This will depend on whether the performance parameter objectives are changed. + +### 1.1.3 *Interactive and coordinated maintenance activities* + +Considerable benefits may be obtained by close cooperation between the network maintenance organization and service maintenance organization units. In the provision and maintenance of a service consideration should also be given whether subject areas require inter-Administration agreements or the development of specific Recommendations. In such a case, operational and maintenance responsibilities should be negotiated and established among all involved service providers prior to the introduction of such a service. Technical service, as defined in Recommendation M.75 [4], may need to be involved in making the appropriate agreements. Service maintenance contact points should be exchanged as part of the general exchange of contact point information as specified in Recommendation M.1510 [5]. + +# 2 Overall service maintenance philosophy + +Service maintenance philosophy should encompass all components involved in service and their relationships. + +## 2.1 *Service supervision capabilities* + +Service supervision is a process in which anomalies and defects are detected, analysed and checked. This analysis may be internal or external to the entity. In the external case, it can be accomplished either locally or on a centralized basis. For maintenance, this supervision process has to include the following actions: + +- a) Locating the “failed” component, or the component in which a fault is suspected or a failure is believed to be affecting service operation. The service supervision process follows the network supervision process principles as defined in Recommendation M.20 [6]. However, the service supervision process is analysing anomaly and defect data related to service quality parameters and objectives. The thresholds of degraded or unacceptable performance limits and the process period, are defined for each defect, confirmed fault, or group of anomalies and defects, and also for each type of entity. Indications of degraded and unacceptable performance levels are generated each time the corresponding threshold is exceeded. +- b) Reporting of failures or service degradations to maintenance personnel. +- c) Protecting or restoring the service by automatic initialization of internal or external protection mechanisms, e.g. reconfiguration, traffic rerouting, etc. + +## 2.2 *Relationships to network failure concepts* + +Failure concepts specified in Recommendation M.20 [6] are applicable to service failure concepts, but they are not equal. Failure of a network equipment or capability may not cause service failure. This is because service function(s) may be automatically restored by using reconfiguration, rerouting capabilities, etc. However, such network equipment failures should be promptly repaired to ensure that subsequent failures will not cause service degradation or failure. The faults occurring in the telecommunication network are characterized by their impact on the service provided by the network. Three measures applicable to maintenance are specified in Recommendation E.862 [2]: + +- duration of the fault (mean down time); +- mean traffic intensity affected by the fault; +- mean probability of congestion during the fault. + +The seriousness of a fault also depends on how the customers experience the fault, and on the Administration's loss of revenue. + +# 3 Bringing into service + +## 3.1 *Verification of service from the network perspective* + +All service functions should be verified by the service provider before making the service available. This verification should include the verification of network resources and operation of the service. + +## 3.2 *Verification of service from the customer/user perspective* + +The pre-service verification should encompass the service features (as purchased by the customer) and related operations procedures. It is recommended that pre-service verification be successfully conducted before releasing the service to a customer. + +## 3.3 *Detailed considerations* + +Given that the fundamental objective is to provide service in an acceptable time frame, meeting or exceeding customer expectations, detailed bringing-into-service procedures should be developed and implemented. + +## 3.4 *Identification of responsibilities* + +In multi-Administrations services the information resources will be distributed across all involved telecommunications networks. In order to provide good and timely support, responsibilities of all the Administrations should be clearly defined. + +# 4 **Maintenance phases** + +## 4.1 *Performance/quality surveillance* + +The objectives of service surveillance are to detect anomalies, defects and faults affecting service quality. It is assumed that service performance criteria/parameters to be monitored (e.g. errored seconds for digital transmission, post-dialling delay for switched services) are known and established according to specific service requirements. This should also include the definition of normal, degraded and unacceptable values for these parameters. It should be noted that QOS parameters and target values for these parameters are defined in Recommendations which either define services or address specific implementation aspects; examples can be found in the E-Series, I-Series and Q-Series Recommendations. + +All types of performance measurement specified in Recommendation M.20 (§ 5.1) [6] are applicable. In addition, other methods of measuring QOS may be used. These include test calls (simulated traffic), customer complaints (see Recommendation E.420 [7]) and customer interviews for opinions of QOS. + +## 4.2 *Service degradation detection* + +Performance data should be analysed to determine service status (e.g. normal, degraded, failed, etc.). Information on failure, unacceptable performance or degraded performance should be transmitted to the maintenance staff, operations systems involved in service/network maintenance, and other parts of the network when appropriate, to initiate proper action (e.g. report degradation or failure, request reconfiguration, etc.). Customer(s) may need to be informed when appropriate. + +## 4.3 *Service restoration* + +The objective of service restoration is to restore the service to an agreed service performance level. To achieve this, it is necessary to define an alternative way to restore the service (e.g. network reconfiguration). This alternative should be performed based upon information on the type of failure, including such information as identification of the failed component/equipment, or failed transmission link. Criteria for service restoration, such as, type of service to be restored and priority scheme, may also be made available. To make service restoration possible, Administrations should provide sufficient spare capacity in the network and/or backup equipment. Upon successful verification of the alternative configuration the affected service should be routed over that configuration. + +## 4.4 *Service restoration time* + +It is desired that the time taken for service restoration be kept to a minimum so that impacts of failures are minimized. + +## 4.5 *Failure or performance information* + +The principles for use of failure and performance information defined in § 5.4 Recommendation M.20 [6] are also applicable to service maintenance. + +## 4.6 *Fault localization* + +If the fault description is not adequate, additional fault localization and/or diagnostics will need to be performed. Once the fault is localized the fault correction/repair activity should be initiated. + +## 4.7 *Fault recovery time* + +Fault recovery time is a part of the overall down time of network resources, and includes active repair time and logistic delay. This time is a function of network maintenance procedures, maintenance organization efficiency, testing capabilities, etc. Repair of network resources may be carried out while the service is performing all required functions under an alternative configuration. Supplement No. 6 to CCITT Blue Book Fascicle II.3 [3] defines terms associated with dependability and time concepts and should be applied here. + +## 4.8 *Fault correction* + +The objectives of fault correction are to promptly repair the failed component and make it available for service. Fault correction may require dispatching maintenance personnel to replace/repair the failed unit (in case of a hardware failure), or the fault may be remotely corrected (in the case of a software failure). + +## 4.9 *Verification* + +After the fault has been corrected, checks must be made to ensure the service is working properly. + +## 4.10 *Restoration* + +After correction and verification, the service is restored to the original configuration. The alternative configuration is then released. + +# 5 **Additional maintenance activities** + +## 5.1 *Maintenance support* + +The service providers' ability to efficiently deal with customer requests will rely heavily on their ability to communicate with all involved Administrations and on their ability to exchange in a timely manner: service, network operations and maintenance information which directly affects the customer. In order to meet this goal, efficient methods for information exchange between all involved Administrations are required (see Recommendation M.1520 [8]). + +## 5.2 *Failure statistics* + +For further study. + +## 5.3 *Preventive maintenance* + +For further study. + +# 6 **Other maintenance considerations** + +If the maintenance procedures do not successfully resolve the problem, an escalation procedure may be required (see Recommendations M.1550 [9] and M.1560 [10]). Service providers should also consider the unique aspects of international services such as time differences, language barriers, different technologies and standards, different network management methods and different market needs. + +# References + +- [1] CCITT Recommendation E.800 *Quality of service and dependability vocabulary.* +- [2] CCITT Recommendation E.862 *Dependability planning of telecommunication networks.* +- [3] CCITT Supplement No. 6 *Terms and definitions for quality of service, network performance, dependability and trafficability studies, Blue Book, Fascicle II.3.* +- [4] CCITT Recommendation M.75 *Technical Service.* +- [5] CCITT Recommendation M.1510 *Exchange of contact point information for the maintenance of international services and the international network.* +- [6] CCITT Recommendation M.20 *Maintenance philosophy for telecommunication network.* +- [7] CCITT Recommendation E.420 *Checking the quality of the international telephone service etc.* +- [8] CCITT Recommendation M.1520 *Standardized information exchange between Administrations.* +- [9] CCITT Recommendation M.1550 *Escalation procedure.* +- [10] CCITT Recommendation M.1560 *Escalation procedure for international leased circuits.* \ No newline at end of file diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..197a8d38ce1cbf51960fc86bed6f569918bca0d5 --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03ca09974324bb938ba25e9f919f4c702584d36eb05d029491efbf7485113fc4 +size 92631 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31c1f5820c21b121be4a0730f35b0a428c6c42e7 --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c2de884bd4926814a64ad482fc43ec1af29ff552d2eec7bc2fd176d81497848 +size 88561 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..869ee06fd1acf677c561ae354413b5bf812fb3ff --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c12154d1a60e1a29bf8a1b82865890dbecef3b52014b6001b126405fb303d4cc +size 15844 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec37cadb681487b1d9136bff05993d0bbbeac96 --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59b1c564fa629b6e59343de9a419ac5395d4a079540ec58b955c88f6c770bb1b +size 69567 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40b1e3c358160e7d3b3299d2d8f05aa8b90a38c3 --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80cef75dffc5e7ce195c4fdc13f4c0d5e752950f7604ca79e20e8083814e0d4e +size 39829 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d39e0fb8a05c7c8f167721a65c18f41903b3d6a --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:742c0eafb934c5bc22c16924e56dae352a9cb2beec27a60d43d8880b9ebf8a5b +size 93412 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/M/T-REC-M.2100-200304-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f8d5bd197c2ca75f949708043dd64f9f73bfc19 --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df7d12a670f43876bb57c4aebc742996de798e156bf64844b19993ffce1ae0a5 +size 114408 diff --git a/marked/M/T-REC-M.2100-200304-I_PDF-E/raw.md b/marked/M/T-REC-M.2100-200304-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7ac7a96b9b18e29c5295cd3318de77edb2e6378a --- /dev/null +++ b/marked/M/T-REC-M.2100-200304-I_PDF-E/raw.md @@ -0,0 +1,1970 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2100** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/2003) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +--- + +**Performance limits for bringing-into-service and +maintenance of international multi-operator PDH +paths and connections** + +ITU-T Recommendation M.2100 + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.2100** + +# **Performance limits for bringing-into-service and maintenance of international multi-operator PDH paths and connections** + +## **Summary** + +This Recommendation provides limits for bringing-into-service and maintenance of international multi-operator PDH paths which operate at or above the primary rate, and connections which operate below the primary rate. Error, timing and availability performance are considered. A method for deriving ES and SES from in-service measurement is given for all hierarchical levels. Sections are not covered by this Recommendation. BIS limits and maintenance procedures for radio sections are described in the relevant ITU-R Recommendations. + +## **Source** + +ITU-T Recommendation M.2100 (2003) was approved by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure on 13 April 2003. + +## **Keywords** + +Availability, bringing-into-service (BIS), digital path, digital connection, error performance parameter, errored second (ES), maintenance limit, performance allocation, performance objective (PO), severely errored second (SES), unavailability. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU [had/had not] received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2003 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|------|-------------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 4 | +| 4 | Abbreviations..... | 5 | +| 5 | Reference models..... | 5 | +| 5.1 | Hypothetical reference performance models for international 64 kbit/s connections ..... | 5 | +| 5.2 | Hypothetical reference performance model for international primary and higher order paths ..... | 6 | +| 6 | Performance objectives..... | 9 | +| 6.1 | Connections operating below the primary rate..... | 9 | +| 6.2 | Primary rate and higher bit rates ..... | 10 | +| 7 | Allocation principles..... | 10 | +| 8 | Evaluation of error performance events ..... | 13 | +| 8.1 | Evaluation of ES/SES events from in-service measurements ..... | 13 | +| 8.2 | Evaluation of ES/SES events from out-of-service measurements ..... | 14 | +| 8.3 | Definition of ratios ..... | 15 | +| 9 | Performance limits – General considerations ..... | 16 | +| 9.1 | Relationship between performance limits and objectives ..... | 16 | +| 9.2 | Type of limits ..... | 16 | +| 10 | Performance limits for bringing-into-service ..... | 17 | +| 10.1 | Calculation of the BIS limits ..... | 17 | +| 10.2 | BIS limits values..... | 18 | +| 11 | Performance limits for maintenance..... | 18 | +| 11.1 | Performance levels and limits ..... | 18 | +| 11.2 | Performance thresholds ..... | 19 | +| 12 | Long-term quality monitoring/measurement..... | 20 | +| 13 | Effects of timing impairments on error performance ..... | 20 | +| 14 | Availability and unavailability ..... | 20 | +| 14.1 | Definitions of available and unavailable states ..... | 20 | +| 14.2 | Consequences for error performance measurements..... | 21 | +| 14.3 | Inhibiting performance monitoring during unavailable time ..... | 21 | +| 14.4 | Unavailability limits ..... | 21 | + +###### **Page** + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Annex A – Example applications of PO allocation from Tables 2a and 2b ..... | 22 | +| Annex B – In-service ES and SES event evaluation criteria ..... | 23 | +| Annex C – Values for bringing-into-service limits for international digital paths ..... | 30 | +| Annex D – Default unacceptable performance level thresholds for international digital paths..... | 42 | + +# Performance limits for bringing-into-service and maintenance of international multi-operator PDH paths and connections + +# 1 Scope + +The purpose of this Recommendation is to provide limits for bringing-into-service and limits for maintenance of international multi-operator digital PDH paths which operate at or above the primary rate, and connections which operate below the primary rate, in order to achieve the performance objectives given for a multiservice environment. These objectives include error performance (ITU-T Recs G.821 and G.826), timing performance (ITU-T Rec. G.822) and availability. This Recommendation defines the parameters and their associated objectives in order to respect the principles given in ITU-T Recs M.20, M.32 and M.34. + +"International multi-operator" in this Recommendation refers to PDH paths and connections which cross international boundaries with a change in jurisdictional responsibility. + +The methods and procedures for applying these limits are described in ITU-T Rec. M.2110 for the bringing-into-service procedures and in ITU-T Rec. M.2120 for the maintenance procedures. + +This Recommendation uses certain principles which are the basis of the maintenance of a digital network: + +- it is desirable to do in-service, continuous measurements. In some cases (e.g., for bringing-into service), out-of-service measurements may be necessary; +- a single set of parameters must be used for maintenance of every level of the hierarchy (this principle does not apply to limits); +- error performance limits of transmission systems are dependent on the medium used; however, due to the many possible network structures, error performance limits on paths are independent of the medium. + +Since the performance limits are intended to satisfy the needs of the evolving digital network, it must be recognized that such limits might not be achieved by all of today's digital equipment and systems. + +Currently, this Recommendation covers the error performance limits for paths at every level of the PDH hierarchy and in-service parameter evaluation criteria up to the quarterternary layer and, for connections below the primary rate, down to 64 kbit/s. Sections are not covered. + +By bilateral agreement, ITU-R Rec. F.1330-1 may be used in conjunction with this Recommendation for radio-relay systems where applicable. + +Throughout this Recommendation the terms "path" and "connections" should be understood as digital. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-R Recommendation F.1330-1 (1999), *Performance limits for bringing-into-service of the parts of international plesiochronous digital hierarchy and synchronous digital hierarchy paths and sections implemented by digital radio-relay systems.* +- ITU-T Recommendation G.703 (2001), *Physical/electrical characteristics of hierarchical digital interfaces.* +- ITU-T Recommendation G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels.* +- ITU-T Recommendation G.706 (1991), *Frame alignment and cyclic redundancy check (CRC) procedures relating to basic frame structures defined in Recommendation G.704.* +- ITU-T Recommendation G.724 (1988), *Characteristics of a 48-channel low bit rate encoding primary multiplex operating at 1544 kbit/s.* +- ITU-T Recommendation G.732 (1988), *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s.* +- ITU-T Recommendation G.733 (1988), *Characteristics of primary PCM multiplex equipment operating at 1544 kbit/s.* +- ITU-T Recommendation G.734 (1988), *Characteristics of synchronous digital multiplex equipment operating at 1544 kbit/s.* +- ITU-T Recommendation G.735 (1988), *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s and offering synchronous digital access at 384 kbit/s and/or 64 kbit/s.* +- ITU-T Recommendation G.736 (1993), *Characteristics of a synchronous digital multiplex equipment operating at 2048 kbit/s.* +- ITU-T Recommendation G.737 (1988), *Characteristics of an external access equipment operating at 2048 kbit/s offering synchronous digital access at 384 kbit/s and/or 64 kbit/s.* +- ITU-T Recommendation G.738 (1988), *Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s and offering synchronous digital access at 320 kbit/s and/or 64 kbit/s.* +- ITU-T Recommendation G.739 (1988), *Characteristics of an external access equipment operating at 2048 kbit/s offering synchronous digital access at 320 kbit/s and/or 64 kbit/s.* +- ITU-T Recommendation G.742 (1988), *Second order digital multiplex equipment operating at 8448 kbit/s and using positive justification.* +- ITU-T Recommendation G.743 (1988), *Second order digital multiplex equipment operating at 6312 kbit/s and using positive justification.* +- ITU-T Recommendation G.745 (1988), *Second order digital multiplex equipment operating at 8448 kbit/s and using positive/zero/negative justification.* +- ITU-T Recommendation G.747 (1988), *Second order digital multiplex equipment operating at 6312 kbit/s and multiplexing three tributaries at 2048 kbit/s.* +- ITU-T Recommendation G.751 (1988), *Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 264 kbit/s and using positive justification.* +- ITU-T Recommendation G.752 (1988), *Characteristics of digital multiplex equipments based on a second order bit rate of 6312 kbit/s and using positive justification.* +- ITU-T Recommendation G.753 (1988), *Third order digital multiplex equipment operating at 34 368 kbit/s and using positive/zero/negative justification.* + +- ITU-T Recommendation G.754 (1988), *Fourth order digital multiplex equipment operating at 139 264 kbit/s and using positive/zero/negative justification.* +- ITU-T Recommendation G.755 (1988), *Digital multiplex equipment operating at 139 264 kbit/s and multiplexing three tributaries at 44 736 kbit/s.* +- ITU-T Recommendation G.761 (1988), *General characteristics of a 60-channel transcoder equipment.* +- ITU-T Recommendation G.762 (1988), *General characteristics of a 48-channel transcoder equipment.* +- ITU-T Recommendation G.775 (1998), *Loss of Signal (LOS) and Alarm Indication Signal (AIS) and Remote Defect Indication (RDI) defect detection and clearance criteria for PDH signals.* +- ITU-T Recommendation G.793 (1988), *Characteristics of 60-channel transmultiplexing equipments.* +- ITU-T Recommendation G.794 (1988), *Characteristics of a 24-channel transmultiplexing equipment.* +- ITU-T Recommendation G.821 (2002), *Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an Integrated Services Digital Network.* +- ITU-T Recommendation G.822 (1988), *Controlled slip rate objectives on an international digital connection.* +- ITU-T Recommendation G.823 (2000), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy.* +- ITU-T Recommendation G.824 (2000), *The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy.* +- ITU-T Recommendation G.826 (2002), *End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections.* +- ITU-T Recommendation H.221 (1999), *Frame structure for a 64 kbit/s to 1920 kbit/s channel in audiovisual teleservices.* +- ITU-T Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks.* +- ITU-T Recommendation M.32 (1988), *Principles for using alarm information for maintenance of international transmission systems and equipment.* +- ITU-T Recommendation M.34 (1988), *Performance monitoring on international transmission systems and equipment.* +- ITU-T Recommendation M.35 (1988), *Principles concerning line-up and maintenance limits.* +- ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- ITU-T Recommendation M.2110 (2002), *Bringing into service international multi-operator paths, sections and transmission systems.* +- ITU-T Recommendation M.2120 (2002), *International multi-operator paths, sections and transmission systems fault detection and localization procedures.* + +# 3 Terms and definitions + +General terms and definitions related to this Recommendation are provided in ITU-T Rec. M.60. In addition, this Recommendation defines the following terms: + +**3.1 Performance Objective (PO):** Performance objective for the international portion of the hypothetical reference path (see Figure 3/G.826) and the hypothetical reference connection (see Figure 1/G.821). + +**3.2 Allocated Performance Objective (APO):** Performance objective for a real path or connection calculated according to the allocation rules. + +**3.3 Bringing-Into-Service Performance Objective (BISPO):** Bringing-into-service performance objective for a real path or connection calculated from its APO. + +**3.4 international portion:** An international digital path can be subdivided into two national portions and one international portion. The boundary between these portions is defined to be at an International Gateway (IG), which corresponds to: + +- an International Switching Centre (ISC), on the international side, for 64 kbit/s paths between switches (IG = ISC = Path End Point (PEP)); +- an International Digital Transmission Centre (IDTC) for paths at 2 Mbit/s and above (IG = IDTC = PEP), carrying lower order paths providing paths between ISCs or leased lines. + +When the 2 Mbit/s paths are terminated inside an ISC (ISC = PEP), IG is located at the IDTC associated with the ISC. No national portion has to be considered since IDTC and ISC are situated in the same geographical area. + +The national portion is outside the scope of this Recommendation. + +**3.5 international boundary and border crossing points:** The International Boundary, the point at which control transfers from one international operator to the next international operator, normally exists within the Inter Country Path Core Element (ICPCE). Generally, this would be halfway along a submarine cable or terrestrial border crossing ICPCE. The Border Crossing Point may coincide with the International Boundary (for example, for a terrestrial border crossing ICPCE) or, in the case of a submarine cable (for example), there would be two border crossings, corresponding to the coastline of the operator's country, which would not coincide with the International Boundary. + +**3.6 Path Core Element (PCE):** An international digital path has been partitioned in geographical terms for the purpose of allocating the PO. These partitions have been titled Path Core Elements. + +Two types of PCEs are used: + +- an International Path Core Element (IPCE) is between an IG and a frontier station (FS) in a terminating country, or between frontier stations in a transit country; +- an ICPCE is between the adjacent frontier stations of the two countries involved. The ICPCE corresponds to the highest order digital path carried on a digital transmission system linking the two countries. An ICPCE may be transported on a terrestrial, satellite or undersea cable transmission system. + +There are two cases where a country may not contain an IPCE: + +- depending on the geographical situation and network topology, the IG may coincide with the FS in a terminating country; +- the path uses only one FS in a transit country. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|---------------------------------------------| +| AIS | Alarm Indication Signal | +| APO | Allocated Performance Objective | +| BER | Bit Error Ratio | +| BIS | Bringing-Into-Service | +| BISPO | Bringing-Into-Service Performance Objective | +| CRC | Cyclic Redundancy Check | +| DPL | Degraded Performance Level | +| ES | Errored Second | +| FAS | Frame Alignment Signal | +| FS | Frontier Station | +| IB | International Boundary | +| ICPCE | Inter-Country Path Core Element | +| IDTC | International Digital Transmission Centre | +| IG | International Gateway | +| IPCE | International Path Core Element | +| ISC | International Switching Centre | +| ISDN | Integrated Services Digital Network | +| LOF | Loss Of Frame | +| LOS | Loss Of Signal | +| PCE | Path Core Element | +| PDH | Plesiochronous Digital Hierarchy | +| PEP | Path End Point | +| PO | Performance Objective | +| PRBS | Pseudo-Random Binary Sequence | +| RDI | Remote Defect Indication | +| SES | Severely Errored Second | +| TMN | Telecommunications Management Network | +| TP | Test Period | +| UPL | Unacceptable Performance Level | + +# 5 Reference models + +## 5.1 Hypothetical reference performance models for international 64 kbit/s connections + +Two ITU-T Recommendations deal with performance of international digital connections operating below the primary rate: + +- ITU-T Rec. G.821 for connections using equipment designed before the adoption of ITU-T Rec. G.826 in November 2002; +- ITU-T Rec. G.826 for the other connections. + +So, two reference models are defined, one for connections designed to ITU-T Rec. G.821 and another one for connections designed to ITU-T Rec. G.826 (2002). + +### **5.1.1 Connections using equipment designed before the adoption of ITU-T Rec. G.826 (2002)** + +The physical relationship between international paths of the primary rate network layer and connections in the 64 kbit/s network layer is illustrated in Figure 1. + +Key points to note in Figure 1 are: + +- a) Paths of the primary rate network layer can serve either: + - peer-layer clients, e.g., an H12 channel in the case of 2048 kbit/s paths; or + - lower order clients, e.g., 64 kbits/s section of a path in the 64 kbit/s network layer. +- b) The international portion of the 64 kbit/s connection is given 40% of the end-to-end error PO. +- c) Some examples of international primary rate paths are given in Annex A. These examples also illustrate the breakdown of the international primary rate path into PCEs; the PCE APOs are given in Table 2b. +- d) Simple addition of the PCE APOs is assumed when determining the end-to-end APO (i.e., between primary rate – PEPs). Moreover, simple addition of tandemed international primary rate path APOs is assumed when considering the APO offered to the section of the 64 kbit/s network layer. +- e) Sensible engineering planning is required to ensure that tandemed international primary rate paths respect the 40% allocation to 64 kbit/s connections. + +### **5.1.2 Connections using equipment designed after the adoption of ITU-T Rec. G.826 (2002)** + +The physical relationship between connections and higher order paths is illustrated in Figure 2a. Key points to note in Figure 2a: + +- a) Allocation of the end-to-end connection is specified in ITU-T Rec. G.826. +- b) The international portion of connections is given a maximum of 63% of the end-to-end PO. + +## **5.2 Hypothetical reference performance model for international primary and higher order paths** + +The physical relationship between international primary and higher order paths is illustrated in Figure 2b. Key points to note in Figure 2b are: + +- a) Allocation of the end-to-end path is specified in ITU-T Rec. G.826. +- b) According to ITU-T Rec. G.826, the international portion of primary and higher order paths are given a maximum 63% of the end-to-end error PO. +- c) Sensible engineering planning is required to ensure that international "n" Mbit/s paths in tandem, above or equal to the primary rate respect the 63% allocation. +- d) Some examples of primary and higher order international paths are provided in Annex A. + +![Figure 1/M.2100 – HRP model for international primary rate path and 64 kbit/s path. The diagram shows a network architecture with four primary rate paths (W, X, Y, Z) and a 64 kbit/s path. It includes multiplexing and cross-connect functions, and various network elements like PEPs and sections. The diagram is labeled with 'M.2100_F01' in the bottom right corner.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the HRP model for international primary rate path and 64 kbit/s path. It shows a network architecture with four primary rate paths (W, X, Y, Z) and a 64 kbit/s path. The 64 kbit/s path is shown as a horizontal line at the bottom, passing through several nodes. The primary rate paths W, X, Y, and Z are shown as vertical lines at the top, each passing through a node. The nodes are represented by dashed boxes containing multiplexing and cross-connect functions. The diagram is labeled with 'M.2100\_F01' in the bottom right corner. + +Legend: + +- Multiplexing function (represented by a box with a diagonal line) +- Cross-connect function (represented by a box with an 'X') +- PEP Path End Point (represented by a box with a diagonal line and a cross-connect function) + +Figure 1/M.2100 – HRP model for international primary rate path and 64 kbit/s path. The diagram shows a network architecture with four primary rate paths (W, X, Y, Z) and a 64 kbit/s path. It includes multiplexing and cross-connect functions, and various network elements like PEPs and sections. The diagram is labeled with 'M.2100\_F01' in the bottom right corner. + +NOTE 1 – The international portion of 64 kbit/s path may be made up of up to 4 tandem primary rate paths W, X, Y and Z, where $W + X + Y + Z \leq 40\%$ of the total RPO. + +NOTE 2 – For a 64 kbit/s switched connection, this point has historically been referred to as an (International Switching Centre). For other network layers, the node of the network (e.g., digital distribution frames) is defined to exist at the International Digital Transmission Centre (IDTC). + +NOTE 3 – The primary rate PEPs logically terminate the primary rate transmission network layer. Physically, however, it might reside in a 64 kbit/s node, e.g., an International Switching Centre for International 64 kbit/s switched ISDN path. + +NOTE 4 – In the case of a 64 kbit/s ISDN path, further information on the partitioning of quality classes (e.g., high grade, medium grade and low grade) is given in Figure 1/G.821 [1]. + +**Figure 1/M.2100 – HRP model for international primary rate path and 64 kbit/s path** + +![Diagram of an international n Mbit/s path apportionment across multiple countries and network layers.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the apportionment of an international path across multiple countries and network layers. At the top, a sequence of nodes is shown: IDTC, FS, FS, FS, FS, FS, FS, FS, FS, IDTC. These are categorized into 'Terminating country' (IDTC), 'Submarine cable' (FS, FS), and three 'Transit country' segments. Each segment contains an 'IPCE' (IP Control Element) and an 'ICPCE' (ICP Control Element). Below this, a horizontal timeline shows percentages: a1%, a2%, a3%, a4%, a5%, a6%, a7%, a8%, a9%. Sub-segments b3.1%, c3.1%, c3.2%, b3.2% are shown under a3%, and b7.1%, b7.1% under a7%. Below a dashed line labeled 'Higher order layers', nodes A, B, C, D, E, and F are shown. Node A is labeled 'n Mbit/s Layer'. Below the nodes, a timeline shows 'n Mbit/s section' segments between nodes, and a longer 'n Mbit/s path' segment spanning from node A to node F. An 'International border' is indicated between nodes E and F. + +Diagram of an international n Mbit/s path apportionment across multiple countries and network layers. + +$a_i$ are given in Table 2b. Path allocation = $a_1 + a_2 + \dots + a_9 = \sum_{i=1}^n a_i (\%)$ + +M.2100\_F02a + +$b_i$ and $c_i$ values are the responsibility of the national network operators for country $i$ with the following constraints: $b_i \times n + c_i \times m \leq a_i$ for each PCE; where $n = 1, 2, \dots$ , and $m = 1, 2, \dots$ , etc. + +$c_i$ values must be communicated to each control station. + +**Figure 2a/M.2100 – Example of apportionment for an international n Mbit/s path, where n = 1.5, 2, 6, 8, ... , 140** + +![Figure 2b/M.2100 – Example of apportionment for a primary rate path showing the relationship with the higher bit rate paths which support it. The diagram illustrates a network path from IDTC to IDTC via FS, Submarine cable, and Transit country segments. It shows various bit rate layers (140 Mbit/s, 34 Mbit/s, 8 Mbit/s, 2 Mbit/s) and their relationship to the overall path capacity. The path is divided into segments with percentages a1% through a5%, and further sub-divided into b and c components. A legend at the bottom defines 'TERMINATING' and 'TRANSIT' segments.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram shows a network path from IDTC to IDTC via FS, Submarine cable, and Transit country segments. The path is divided into segments with percentages a1% through a5%, and further sub-divided into b and c components. A legend at the bottom defines 'TERMINATING' and 'TRANSIT' segments. + +Transmission system layer + +140 Mbit/s layer + +34 Mbit/s layer + +8 Mbit/s layer + +2 Mbit/s layer + +A B C D E F G H I J + +TERMINATING + +TRANSIT + +TERMINATING + +TERMINATING + +$b3.1 + b3.2 + c3.1 \leq a3$ + +$b5.1 + b5.2 + c5.1 \leq a5$ + +M.2100\_F02b + +Figure 2b/M.2100 – Example of apportionment for a primary rate path showing the relationship with the higher bit rate paths which support it. The diagram illustrates a network path from IDTC to IDTC via FS, Submarine cable, and Transit country segments. It shows various bit rate layers (140 Mbit/s, 34 Mbit/s, 8 Mbit/s, 2 Mbit/s) and their relationship to the overall path capacity. The path is divided into segments with percentages a1% through a5%, and further sub-divided into b and c components. A legend at the bottom defines 'TERMINATING' and 'TRANSIT' segments. + +**Figure 2b/M.2100 – Example of apportionment for a primary rate path showing the relationship with the higher bit rate paths which support it** + +# 6 Performance objectives + +In this Recommendation, ES and SES events are dealt with. Both performance events are considered essential for BIS and maintenance. + +## 6.1 Connections operating below the primary rate + +There are two types of connections, those using equipment designed before the approval of revised ITU-T Rec. G.826 (2002) and those using equipments designed according to ITU-T Rec. G.826 (2002). + +### 6.1.1 Connections using equipment designed before the adoption of revised ITU-T Rec. G.826 + +The ES performance objective (PO) will support the 8% end-to-end objective for services based on ITU-T Rec. G.821. The PO is based on empirical evidence of readily achievable primary rate path performance. It is 50% of the objective values for ES per ITU-T Rec. G.821 and the adopted value is 4%. + +The SES performance objective is based on 0.1% end-to-end PO taken directly from ITU-T Rec. G.821. However, since the periods used for BIS/maintenance are short compared to the one month evaluation period suggested in ITU-T Rec. G.821, the additional allowance for radio/satellite systems (per ITU-T Rec. G.821 ) has not been included. See Table 1a. + +### 6.1.2 Connections using equipment designed according to revised ITU-T Rec. G.826 + +The ES performance objective will support the 4% end-to-end objective for connections based on ITU-T Rec. G.826. It is 50% of the value for ES per ITU-T Rec. G.826 and the adopted value is 2%. The SES performance objective is based on the 0.1% end-to-end PO defined in ITU-T Rec. G.826. + +**Table 1a/M.2100 – End-to-end error performance objectives for connections** + +| Parameters (Note) | End-to-end PO for connections based on ITU-T Rec. G.821 (before revision of ITU-T Rec. G.826) | End-to-end PO for connections based on revised ITU-T Rec. G.826 | +|-----------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| Errored Second Ratio (ESR) | 0.04 | 0.02 | +| Severely Errored Second Ratio (SESR) | 0.001 | 0.001 | +| NOTE – ESR and SESR are defined in 8.3. | | | + +## 6.2 Primary rate and higher bit rates + +The values given in Table 1b for layers at or above the primary rate are selected to maintain alignment with ITU-T Rec. G.826, and are 50% of G.826 values. The APO for ES used in this Recommendation is based on a maximum of 63% of a 2% (primary level), 2.5% (secondary level), 3.75% (tertiary level) and 8% (quaternary level) end-to-end PO as derived from ITU-T Rec. G.826. + +The APO for SES is based on a maximum of 63% of a 0.1% (for every level) end-to-end PO as derived from ITU-T Rec. G.826. However, the basis for calculating ES and SES in ITU-T Rec. G.826, and in this Recommendation, are different and numbers cannot be compared directly. + +**Table 1b/M.2100 –End-to-end error performance objectives at or above the primary rate** + +| Network level | Errored Seconds Ratio (ESR) | Severely Errored Seconds Ratio (SESR) | +|-----------------------------------------|-----------------------------|---------------------------------------| +| Primary | 0.02 | 0.001 | +| Secondary | 0.025 | 0.001 | +| Tertiary | 0.0375 | 0.001 | +| Quaternary | 0.08 | 0.001 | +| NOTE – ESR and SESR are defined in 8.3. | | | + +# 7 Allocation principles + +This clause specifies the allocation of error performance objectives for the international portion of international digital paths, in terms of PCEs as shown in Figure 3. + +![Diagram of a primary rate path showing components: IG (International Gateway), FS (Frontier Station), IB (International Border), and IPCE (International Path Component). The path starts at an IG, passes through a series of FS and IB points, and is divided into seven IPCE segments. The fourth segment is labeled 'IPCE (Note 1)'. The diagram is labeled M.2100_F03.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +FS Frontier Station (see clause 2/M.2110) + IB International Border + IG International Gateway + +M.2100\_F03 + +Diagram of a primary rate path showing components: IG (International Gateway), FS (Frontier Station), IB (International Border), and IPCE (International Path Component). The path starts at an IG, passes through a series of FS and IB points, and is divided into seven IPCE segments. The fourth segment is labeled 'IPCE (Note 1)'. The diagram is labeled M.2100\_F03. + +NOTE –This ICPCE crosses two international border and is typically on a satellite or undersea cable transmission system + +**Figure 3/M.2100 – Example of the components of a primary rate path (such as W, X, Y or Z in Figure 1)** + +It is the responsibility of each operator to design its network in a way that is consistent with the country allocation for the international path. The allocation of each portion of the international path can be determined from the values given in Table 2b. The lengths referred to in this table are actual route lengths or air-route distances multiplied by an appropriate routing factor (rf), whichever is less. Values of rf are given in Table 2a. + +**Table 2a/M.2100 – Routing factor** + +| PCE air-route distance | Routing factor (rf) | Calculated PCE length | +|------------------------------------|---------------------|-----------------------| +| $d < 1000$ km | 1.5 | $1.5 \times d$ km | +| $1000 \text{ km} \leq d < 1200$ km | $1500/d$ | 1500 km | +| $d \geq 1200$ km | 1.25 | $1.25 \times d$ km | + +As shown in Figures 2a and 2b, it is possible that access to the bit stream for a given path may not coincide with the end of a PCE. In this case, or if a transit country has other access points within its network, it may be necessary to make a suballocation for maintenance purposes, e.g., fault localization as described in ITU-T Rec. M.2120. Such suballocations will be the responsibility of the network operator(s) of the country involved, with the following constraints: + +- the sum of suballocations may not exceed the allocation of Table 2b for the PCE in question; +- the values of the suballocations must be communicated to all maintenance centres involved before bringing the path into service and after any rearrangement which changes the values. + +**Table 2b/M.2100 – Allocation of POs to international and inter-country path core elements** + +| PCE classification (Note 2) | Allocation
(% of end-to-end POs)
(Note 5) | +|----------------------------------------------|-------------------------------------------------| +| IPCE | | +| Terminating/transit national networks | | +| $d \leq 500 \text{ km}$ | 2.0 | +| $500 \text{ km} < d \leq 1000 \text{ km}$ | 3.0 | +| $1000 \text{ km} < d \leq 2500 \text{ km}$ | 4.0 | +| $2500 \text{ km} < d \leq 5000 \text{ km}$ | 6.0 | +| $5000 \text{ km} < d \leq 7500 \text{ km}$ | 8.0 | +| $d > 7500 \text{ km}$ | 10.0 | +| ICPCE | | +| Non-optical undersea cable | | +| $d \leq 500 \text{ km}$ | | +| $500 \text{ km} < d \leq 1000 \text{ km}$ | 3.0 | +| $1000 \text{ km} < d \leq 2500 \text{ km}$ | 4.0 | +| $2500 \text{ km} < d \leq 5000 \text{ km}$ | 6.0 | +| $d > 5000 \text{ km}$ | 8.0 | +| Optical undersea cable | | +| $d \leq 500 \text{ km}$ | 1.0 | +| $d > 500 \text{ km}$ | 2.5 | +| Satellite | | +| Normal operation | 20.0 | +| Wideband cable restoration mode | (Note 1) | +| Terrestrial | | +| $d < 300 \text{ km}$ (Notes 3 and 4) | 0.5 | + +NOTE 1 – The allocated percentage of the POs for the satellite ICPCE will be the same as that for the particular cable restored, with a minimum value of 2.5%. This level of error performance, which is better than that provided by usual satellite portions of ISDN connections, can be achieved through the careful design of specialized wideband, high capacity, C-band carriers which use dedicated facilities. + +NOTE 2 – Examples of PCE allocations using Table 2b are given in Annex A. + +NOTE 3 – The terrestrial ICPCE is only intended for use in the calculation of end-to-end path BIS/maintenance thresholding applications. It is not intended to be used as the basis for setting maintenance thresholds for the terrestrial ICPCE itself. + +NOTE 4 – It is assumed that this length will be less than 300 km. In the case of an unusually long terrestrial ICPCE, the country could transfer a portion of the allocation of its adjacent IPCE to supplement the 0.5% allocation. + +NOTE 5 – The allocations of this table are maximum values and may be decreased by bilateral or multilateral agreement. For some very short paths, the M.2100 methodology sometimes gives a larger allocation than ITU-T Rec. G.826. In this case, the Administrations can by bilateral or multilateral agreement choose to lower the allocation given by this Recommendation to reflect the G.826 value, or to take M.2100 values, assuming that the end-to-end G.826 objectives are respected over the long term. + +**Table 2b/M.2100 – Allocation of POs to international and inter-country path core elements** + +NOTE 6 – Note that in the case of higher order terminating path supporting lower order transit path, the transit path may have a lower allocation than the sum of the terminating paths. Sensible engineering planning should result in all requirements being met. + +NOTE 7 – The 20% allocation is for primary rate links. Applicability to higher bit rates has yet to be validated. + +# **8 Evaluation of error performance events** + +This clause addresses the evaluation of the error performance events ES and SES from standardized signals using anomalies and defects. The concepts of anomaly and defect are defined in ITU-T Rec. M.20. + +In-service evaluation is considered in 8.1, and out-of-service evaluation is considered in 8.2. + +NOTE – Only standardized path signals are considered under in-service evaluation; transmission systems with proprietary overhead are not covered. However, both paths and systems can be considered under out-of-service evaluation. + +The treatment of the ES and SES counts during the unavailable state is explained in clause 14. + +## **8.1 Evaluation of ES/SES events from in-service measurements** + +### **8.1.1 General** + +Both the ES and SES events are evaluated from in-service anomalies (see 8.1.2) and in-service defects (see 8.1.3) relevant to the path terminating equipment at the network level of interest over a one-second integration period. + +### **8.1.2 In-service anomaly information** + +An "in-service anomaly" occurs on a path when there is an elemental change of the path overhead from its normal value without a change of state of the total path signal from its normal state, i.e., there is no in-service defect present. + +Examples of in-service anomalies are: + +- a FAS violation. It should be noted that, for a bunched FAS, an FAS violation occurs if one or more binary errors are present in a single occurrence of the FAS pattern; +- a CRC codeword violation (or its return equivalent, e.g., the "E" bits at 2.048 Mbit/s); +- a parity bit violation; +- an interface code violation (as in ITU-T Rec. G.703). It should be noted that this in-service anomaly is extra redundancy which is not part of the overhead of the binary path signal structure; however, it is required to adapt the binary path signal structure to a form more suited to the transmission media; +- a controlled slip. ITU-T Rec. G.822 gives the performance requirements for controlled slips on primary rate paths which terminate international clock boundaries (see also clause 13). + +### **8.1.3 In-service defect information** + +An "in-service defect" occurs on a path when there is a change of state of the total path signal from its normal state. A particular in-service defect is evaluated from the persistence (i.e., integration period) of the relevant in-service anomalies; exact details (including any associated consequent actions) are given in the Recommendations dealing with the path termination function for the particular in-service defect considered. + +Examples of in-service defects are: + +- LOF. ITU-T Rec. G.706 gives the LOF criteria for the basic frame structures (including the primary rate) defined in ITU-T Rec. G.704; +- LOS. ITU-T Rec. G.775 gives the integration criterion for the HDB3 interface code (per ITU-T Rec. G.703). The integration criterion for other interface codes is under study; +- AIS. ITU-T Rec. G.775 gives the integration criterion for 2048 kbit/s path signals structured as per ITU-T Recs G.704 and G.706. The integration criteria for other path signals are under study. + +NOTE – An AIS can be considered to cause an effective BER of 0.5 for its duration. If the AIS is of sufficient duration to cause a LOF event at the path level, then for the purposes of ES/SES parameter evaluation it should be considered as a LOF defect. However, a signal with all bits, except the frame alignment in the 1 state, should not be mistaken for an AIS. + +### 8.1.4 Return in-service defect information + +The majority of path signals have a facility whereby the detection of the in-service defect LOF at a path terminating equipment results in a remote alarm indication bit being set in the return path overhead. In order to give a degree of protection against transmission errors causing an incorrect decision regarding the status of the remote alarm indication bit, it should be evaluated over an integration period commensurate with its minimum set-state period in the path terminating equipment which originally detected the in-service defect LOF. + +### 8.1.5 ES and SES evaluation from in-service anomaly and defect information at path terminating equipment + +This clause shows how anomaly and defect event indicators may be processed into ES and SES events. Tables have been prepared for each network level, from 64 kbit/s subprimary rate to the 97 728/139 264 kbit/s quaternary rate (see Annex B). The tables are all of the same format, each table referring to one level as follows: + +- | | | | | +|---|------------|----------------------------|---------------------------------| +| – | Table B.1: | subprimary level | (64 kbit/s) | +| – | Table B.2: | primary level frame | (1544, 2048 kbit/s) | +| – | Table B.3: | primary level equipment | (1544, 2048 kbit/s) | +| – | Table B.4: | secondary level equipment | (6312, 8448 kbit/s) | +| – | Table B.5: | tertiary level equipment | (32 064, 34 368, 44 736 kbit/s) | +| – | Table B.6: | quaternary level equipment | (97 728, 139 264 kbit/s) | + +Each table provides guidance for mapping the wide variety of path overhead and the line signal anomaly and defect indicators into the standard ES and SES events. + +Where applicable, return in-service anomaly or defect information from a remote path terminating equipment is included in the tables. This allows, when required, a single-ended both-direction monitoring capability. + +## 8.2 Evaluation of ES/SES events from out-of-service measurements + +### 8.2.1 General + +The ES and SES events are evaluated from out-of-service anomalies and defects relevant to the test equipment at the network level of interest over the relevant integration period. + +### 8.2.2 Out-of-service anomaly information + +An out-of-service anomaly occurs when there is an elemental change of the test signal from its normal value without a change of state of the total test signal from its normal state, i.e., there is no defect. + +Out-of-service measurements usually employ a PRBS and, therefore, permit resolution to the bit level. Hence, the bit error is the most basic out-of-service anomaly which can be measured. However, since some test equipment uses PRBSs which are embedded in standardized path signals, it might also be possible to evaluate in-service anomalies (see 8.1.2). + +### 8.2.3 Out-of-service defect information + +An out-of-service defect occurs when there is a change of state of the test signal from its normal state. Since some out-of-service test equipment uses PRBSs which are embedded in standardized path signals, it might also be possible to evaluate in-service defects (see 8.1.3). + +NOTE – Some test equipment, which uses a PRBS that is not embedded in a standardized path signal, can experience a condition which is referred to as "Loss of Sequence Synchronization". + +Loss of sequence synchronization can occur as a consequence of: + +- long duration intense error burst; +- long duration AIS; +- uncontrolled bit slip; +- loss of signal. + +The criterion to declare "loss of sequence synchronization" is manufacturer-specific and can be highly variable between different manufacturers. The standardized criterion for loss of sequence synchronization in test equipment is given in the O-Series ITU-T Recommendations. + +### 8.2.4 ES and SES evaluation from out-of-service anomaly and defect information in test equipment + +Since there will generally be resolution to the bit, the predominant evaluation criteria for ES and SES parameters will be: + +- ES: a 1-second period with $\geq 1$ bit error or a defect. +- SES: a 1-second period with an integrated BER of $\geq 10^{-3}$ or a defect. + +If, in addition, the test equipment uses a PRBS that is embedded in a standardized path signal, then the further ES/SES evaluation criteria referred to in 8.1.5 for in-service anomaly and defect information, can also be utilized. + +However, if the test equipment uses a PRBS that is not embedded in a standardized path signal, then the only additional anomaly or defect conditions which can be taken into account are: + +- Anomalies: Interface code violations (per ITU-T Rec. G.703). +- Defects: AIS, LOS. + +In particular, a 1-second period with $\geq 1$ LOS should be considered to give rise to a SES (and an ES). + +NOTE – An AIS can be considered to cause an effective BER of 0.5 for its duration. If the AIS is of sufficient duration to cause a BER $\geq 10^{-3}$ in any 1-second period, then it should be considered as a SES (+ES) parameter event. However, a signal with all bits, except the frame alignment in the one state, should not be mistaken for an AIS. + +## 8.3 Definition of ratios + +The Errored Second Ratio (ESR) c.q. Severely Errored Second Ratio (SESR) is defined as the ratio of the number of Errored Seconds c.q. Severely Errored Seconds to the total number of seconds in available time in the test period. + +# **9 Performance limits – General considerations** + +Performance limits relative to Allocated Performance Objective from a long-term perspective are given in Table 3. + +## **9.1 Relationship between performance limits and objectives** + +The limits in this Recommendation are to be used to indicate the need for actions during maintenance and bringing-into-service. A network maintained to these limits should meet the performance objectives specified in ITU-T Recs G.821 and G.826. + +The particular parameters measured, the measurement duration, and the limits used for the procedure need not be identical to those used for specifying the performance objectives as long as they result in network performance which meets these objectives. For example, the error performance objectives refer to long periods, such as one month. However, practical considerations demand that maintenance and BIS limits be based on shorter measurement intervals. + +Statistical fluctuations in the occurrence of anomalies mean that one cannot be certain that the long-term objectives are met. The limits on the numbers of events, and the duration of measurements, attempt to ensure that systems, or paths, exhibiting unacceptable or degraded performance can be detected. The only way to ensure that a system, or path, meets network performance objectives is to do continuous measurement over a long period (months). + +## **9.2 Type of limits** + +Limits are needed for several maintenance functions as defined in ITU-T Rec. M.20. This Recommendation provides limits for three of these functions: + +- bringing-into-service (BIS); +- keeping the network operational (maintenance); +- system restoration. + +Limits for commissioning (installation and acceptance testing of transmission systems) are not provided in ITU-T Recommendations. + +### **9.2.1 BIS tests/limits** + +BIS tests are done by measurements using a PRBS between digital terminating points. When a particular path/section is brought into service, the collection of anomalies and defects for the BIS tests shall be done at the actual termination points of this path/section. See ITU-T Rec. M.2110 for further information. These should be long-term measurements for routes with new equipment and long-term (e.g., 24 hour) BIS tests should be used. However, for practical reasons (a new path on a route with many paths already in-service, rearrangements of the network, etc.), the measurements between PEPs may be reduced to a quick measurement and the assessment completed with performance monitoring equipment. + +Tests results should be compared to the BIS limits given in this Recommendation. + +### **9.2.2 Maintenance limits** + +Once entities have been placed into service, supervision of the network requires additional limits, as described in ITU-T Rec. M.20. This supervision is done on an in-service basis using performance monitoring equipment. The supervision process involves analyzing anomalies and defects detected by maintenance entities to determine if the performance level is normal, degraded, or unacceptable. Thus, degraded and unacceptable performance limits are required. In addition, a limit on performance after intervention (repair) is also required. It may be different from the BIS limit. + +### **9.2.3 System restoration limit** + +A limit on performance after intervention (repair) is required; it is equal to the BIS limit. + +# 10 Performance limits for bringing-into-service + +The BIS testing procedures, including how to deal with any period of unavailability during the test, is defined in ITU-T Rec. M.2110. This clause defines the methodology of calculation of BIS performance limits for international paths of every rate of the PDH. The derivation of the limits is a function of a given allocation and the measurement duration, and is based on a pragmatic rule. These limits depend on parameters and objectives from ITU-T Recs G.821 and G.826, and are derived from the values shown in Tables 1a and 1b. The Bringing-into-service Performance Objective (BISPO) is derived from the APO. + +The difference between the APO and the BISPO limits is called the ageing margin. This margin should be as large as possible to minimize maintenance interventions. The ageing factor for paths is 0.5. + +One limit S is derived from the BISPO for use in BIS testing. + +If performance is better than the limit S, the entity can be brought into service with some confidence. Corrective action is required if performance is worse than the limit S. + +Continuous in-service monitoring is required to provide sufficient confidence in the long-term performance. + +## 10.1 Calculation of the BIS limits + +The BISPO and S limits for each event (ES and SES) are calculated on the basis of the BIS objective, which is fixed at two times better than the APO. + +The following steps should be followed: + +### Step a: Identification of PO + +- 1) Identify the bit rate of the path. +- 2) Read the PO for the appropriate bit rate from Tables 1a and 1b for ES and SES: + $PO_{es} = x$ (ratio) + $PO_{ses} = y$ (ratio) + +### Step b: Calculation of allocation + +- 3) Identify all PCEs for the entire path, and set $N$ = the total number of PCEs. +- 4) Label the PCEs as $PCE_1$ to $PCE_N$ as shown in Figures 2a and 2b. +- 5) Identify the length, $d$ , of each $PCE_n$ . The length, $d$ , is either the actual path length or can be estimated by the great circle length between its endpoints multiplied by the appropriate routing factor from Table 2a. +- 6) Read the allocation, $a_n\%$ , (as a percentage of end-to-end PO) for $PCE_n$ from Table 2b. Note that the allocations in Table 2b are maximum values; more stringent values can be used by bilateral or multilateral agreement. +- 7) Calculate $A\%$ , the path allocation, where: $A\% = \sum a_n\%$ ; i.e., $a_1\% + a_2\% + \dots + a_N\%$ + +### Step c: Calculation of APO + +- 8) Determine the required Test Period, (TP) where TP = 15 min., 2 hours, or 24 hours. Express TP in seconds, e.g., TP = 900 seconds for a 15-minute test. + +- 9) Calculate the Allocated Performance Objective (APO) counts for ES and SES required from the information already obtained: + +$$APO_{es} = A \times PO_{es} \times TP \div 100 \text{ (convert A\% to ratio)}$$ + +$$APO_{ses} = A \times PO_{ses} \times TP \div 100 \text{ (convert A\% to ratio)}$$ + +### **Step d:** Calculation of BISPO and S values + +- 10) Calculate the BISPOs for the path: + +$$BISPO_{es} = \frac{APO_{es}}{2} \qquad BISPO_{ses} = \frac{APO_{ses}}{2}$$ + +- 11) Calculate S values: + +$$D_{es} = 2\sqrt{BISPO_{es}}$$ + +$$S_{es} = BISPO_{es} - D_{es}$$ + +$$D_{ses} = 2\sqrt{BISPO_{ses}}$$ + +$$S_{ses} = BISPO_{ses} - D_{ses}$$ + +Round all S values to the nearest integer value $\geq 0$ . + +## 10.2 BIS limits values + +By application of the methodology described above, the performance limits for BIS are calculated according to the path allocation and the testing duration. BIS tests described in ITU-T Rec. M.2110 are 15-minute, 2-hour and 24-hour tests. + +According to those durations, S values are defined as $S_{15}$ , $S_2$ and $S_{24}$ . Those S values can be read from the tables given in Annex C. + +# 11 Performance limits for maintenance + +Once entities have been placed into service, the supervision of the network requires additional limits, as described in ITU-T Rec. M.20. The supervision process involves analyzing anomalies and defects detected by maintenance entities to determine the performance level. The maintenance procedures are defined in ITU-T Rec. M.2120. + +## 11.1 Performance levels and limits + +According to ITU-T Rec. M.20, an entity can be in a limited number of predefined conditions depending on its performance. These conditions are called performance levels and are Unacceptable Performance Level (UPL), Degraded Performance Level (DPL) and Acceptable Performance Level. + +**Unacceptable performance level:** An unacceptable performance level is defined in ITU-T Rec. M.20. The unacceptable performance limit for a given entity is derived from an objective of at least 10 times the APO during a 15-minute period. + +**Degraded performance level:** A degraded performance level is defined in ITU-T Rec. M.20. The degraded performance limit for a given entity is derived from an objective on the order of 0.5 times the APO for transmission systems and 0.75 times the APO for paths. The monitoring duration is a fixed duration of 24 hours. + +**Performance limit after intervention (repair):** This performance limit is derived from an objective in the order of 0.125 times the APO for transmission systems and the same as the BIS limit for paths (see ITU-T Recs M.35 and M.2110). + +The boundaries between the performance levels are called performance limits. The performance limits are a function of the APO as follows: + +- UPL Limit $\geq 10 \times$ APO where TP = 900 seconds; +- DPL Limit = $0.75 \times$ APO (path) where TP = 86 400 seconds; +- DPL Limit = $0.50 \times$ APO (transmission system) where TP = 86 400 seconds. + +In the case of testing performance after repair, a special threshold, "Performance After Repair", is used (see ITU-T Recs M.34 and M.2110) where: + +- Performance After Repair = $0.125 \times$ APO (transmission system) for ES and BBE; +- Performance After Repair = $0.5 \times$ APO (path). + +Performance levels are bounded by UPL and DPL Limits. The "Performance After Repair" and BIS thresholds are included in the Acceptable range but are not boundaries between performance levels. + +## 11.2 Performance thresholds + +Performance limits are defined for ES and SES. Each performance level will have its own threshold to detect crossing of the limit and will require its own measurement duration. Examples of the above principles and objectives to derive limits are shown in Table 3. + +**Table 3/M.2100 – Performance limits (ES & SES) relative to APO from a long-term perspective (> 1 month)** + +| Transmission systems | | | Paths | | | +|----------------------------------------|--------|-----------------------|----------------------------------------|--------|-----------------------| +| Limit (relative number of impairments) | | Performance for staff | Limit (relative number of impairments) | | Performance for staff | +| Bringing-into-service | 0.1 | Acceptable | Bringing-into-service | 0.5 | Acceptable | +| Performance after repair | 0.125 | | Performance after repair | 0.5 | | +| Degraded | 0.5 | Degraded | Degraded | 0.75 | Degraded | +| Unacceptable | $> 10$ | Unacceptable | Unacceptable | $> 10$ | Unacceptable | + +### 11.2.1 Use of thresholds + +The general strategy for the use of performance monitoring information and thresholds is described in ITU-T Recs M.20 and M.34. These thresholds and information will be reported to operations systems via the TMN for both real time and longer term analysis. When thresholds of unacceptable or degraded performance levels are exceeded, maintenance action should be initiated independently of the performance measurement. Other thresholds may be used for longer term quality analysis. The operations systems will use real-time processing to assign maintenance priorities to these thresholds and information, using the performance supervision process described in ITU-T Rec. M.20. + +### 11.2.2 Types of thresholds + +There are two types of thresholds according to the monitoring duration T1 or T2. + +#### *Thresholds based on a T1 evaluation period* + +The monitoring duration T1 is 15-minutes and ES and SES are counted over this period. The T1 period is to assist in detection of transition to or from the unacceptable performance. + +A threshold report occurs when an ES or SES threshold is met or exceeded. The reset threshold report, which is an optional feature, occurs when the number of ES and SES is lower than, or equal to, the reset threshold. Those principles are explained in ITU-T Rec. M.2120. + +#### ***Thresholds based on a T2 evaluation period*** + +The monitoring duration T2 is fixed to a 24-hour value. The T2 period is to assist in detection of transition to the degraded performance. + +A threshold report occurs when an ES or SES threshold is met or exceeded over the period of time T2 as explained in ITU-T Rec. M.2120. + +### **11.2.3 Threshold values** + +Thresholds should be programmable (for both ES and SES) to suit specific operating requirements. In particular, the need for iterative adjustment (with operational experience) of threshold is seen as a likely requirement. + +The default unacceptable thresholds for the 15-minute evaluation period are given in Annex D for various allocations. + +The degraded performance thresholds for the 24-hour evaluation period are the responsibility of each network operator; $0.75 \times \text{APO}$ values are suggested for paths. + +# **12 Long-term quality monitoring/measurement** + +Performance monitoring history should be kept for at least one year (suggested value) by the management system. + +# **13 Effects of timing impairments on error performance** + +The following two types of timing impairments may affect the network performance: + +- The first one, called controlled slip, is caused by the long-term phase departure between two timing signals at the primary rate path terminating equipment. The number of controlled slips, which produces the loss or the duplication of an octet at the 64 kbit/s level, must fulfil the requirements of ITU-T Rec. G.822. +- The second one, called jitter and wander, is related to the fluctuations in the timing signal. Limits for jitter and wander are defined in ITU-T Recs G.823 and G.824. Those limits are fixed in such a way that a given level of jitter could be applied to the input of a network equipment without producing errors or excessive jitter at its output. + +Therefore, for maintenance purposes, the error performance requirements are sufficient to deal with those timing impairments. + +# **14 Availability and unavailability** + +## **14.1 Definitions of available and unavailable states** + +According to 4.2.2/G.821 and 4.7/G.826, the error performance of a path shall only be evaluated whilst the path is in the available state. The reason is that error performance is a parameter which characterizes the service provided by the path. When the service is not available, this characteristic is irrelevant. + +In line with this general principle, the evaluation of the error performance shall be based on the numbers of events which happened during available time. + +Annex A/G.821 and ITU-T Rec. G.826 further stipulate that a bidirectional service between A and B is only available if both of the two constituent unidirectional services (A to B, and B to A) are available. The reason is that a client is not very much interested in the detailed performance of one direction if the other direction is completely broken. + +This Recommendation has a different approach because it is dealing with BIS and maintenance. Maintenance consists of identifying, localizing and correcting failures which affect the performance of a path. In order to be able to carry out these tasks efficiently, the view of an operator working on failures affecting one direction of a bidirectional path should not be obscured by possible unavailability of the other direction. + +For this reason, this Recommendation uses only the criteria for a single direction, and not the criterion for a bidirectional path. + +The criteria for a single direction are: "A period of unavailable time begins at the onset of ten consecutive SES events. These ten seconds are considered to be part of unavailable time. A new period of available time begins at the onset of ten consecutive non-SES events. These ten seconds are considered to be part of available time." + +Hence, in order to evaluate the error performance of a transport entity against the objectives put forward in clause 10, each direction shall be evaluated while disregarding the behaviour of the other direction, and the counting of events for a direction shall only be inhibited when that direction is unavailable. + +## **14.2 Consequences for error performance measurements** + +To determine the entry into and exit from unavailability, it is necessary to collect SES and to determine unavailability for each direction of a two-way path or connection independently. It should be noted that, when only one direction is in the unavailable state, measurements made on the opposite direction should not be included in the performance assessment of the bidirectional path or connection. + +## **14.3 Inhibiting performance monitoring during unavailable time** + +During unavailable time, the count of performance events is inhibited. When only one direction of a bidirectional path is unavailable, the count of performance events is inhibited for this direction and continues for the other direction. + +Figure 4 illustrates the rules for determining the unavailable second parameter and for inhibiting other parameter counts. Reading down and left to right, the first row represents the error condition and shows momentary and persistent conditions. It indicates if an error condition exists (Y) or not (N). Error conditions include anomalies and defects as shown. Proceeding in a similar manner, the latter three rows show the procedures for calculating path unavailable seconds, real-time and adjusted real-time parameter counts. + +Figure 4 shows the correction to the unavailable counter, and the rules for deleting and adding increments in time in the unavailable second counter. It also shows the count of anomalies during the clearing time interval. + +Note that the signal condition transition, or declaration instant of a defect or anomaly condition, is independent of the performance monitoring clock one-second boundaries. + +## **14.4 Unavailability limits** + +For the time being, unavailability limits are left for negotiation. This subject is under consideration. In general, any transition to the unavailable state should be unacceptable for BIS. For radio and satellite systems, however, unavailable periods due to natural phenomena (e.g., rain fade) may be acceptable. + +![Timing diagram illustrating performance monitoring inhibiting during unavailable time. The diagram shows five horizontal timelines: Error condition (Y/N), Performance monitoring clock, Real-time parameter count (Y/N), Path unavailable seconds (Y/N), and Adjusted real-time parameter count (Y/N). The Error condition timeline shows pulses labeled (Note 1) and (Note 2). The Performance monitoring clock shows a series of vertical lines. The Real-time parameter count timeline shows a pulse that is inhibited (held low) when the path is unavailable. The Path unavailable seconds timeline shows a pulse that goes high when the path becomes unavailable and low when it becomes available. The Adjusted real-time parameter count timeline shows a pulse that is inhibited when the path is unavailable. Annotations include 'Momentary anomalies + defects', 'Defects', 'Momentary defects', '10 consecutive SES', 'No SES during 10 s', 'Declare unavailability', 'Add 10 s', 'Declare availability', 'Delete 10 s', 'Add anomaly observe during clear time', and 'Delete 10 ES & SES'. The diagram is labeled M.2100_F04.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +Timing diagram illustrating performance monitoring inhibiting during unavailable time. The diagram shows five horizontal timelines: Error condition (Y/N), Performance monitoring clock, Real-time parameter count (Y/N), Path unavailable seconds (Y/N), and Adjusted real-time parameter count (Y/N). The Error condition timeline shows pulses labeled (Note 1) and (Note 2). The Performance monitoring clock shows a series of vertical lines. The Real-time parameter count timeline shows a pulse that is inhibited (held low) when the path is unavailable. The Path unavailable seconds timeline shows a pulse that goes high when the path becomes unavailable and low when it becomes available. The Adjusted real-time parameter count timeline shows a pulse that is inhibited when the path is unavailable. Annotations include 'Momentary anomalies + defects', 'Defects', 'Momentary defects', '10 consecutive SES', 'No SES during 10 s', 'Declare unavailability', 'Add 10 s', 'Declare availability', 'Delete 10 s', 'Add anomaly observe during clear time', and 'Delete 10 ES & SES'. The diagram is labeled M.2100\_F04. + +NOTE 1 – Anomaly (or anomalies). + +NOTE 2 – Defect (or defects). + +**Figure 4/M.2100 – Illustration of performance monitoring inhibiting during unavailable time** + +## Annex A + +## Example applications of PO allocation from Tables 2a and 2b + +This annex provides two examples showing the application of PO Allocation Table described in clause 7. The first example is of a primary rate path which is extremely long and, as such, does not allow for additional tandem paths to further extend the 64 kbit/s connection. The second example is of a complex network where a 64 kbit/s connection is routed over three tandem primary rate paths. The purpose of these examples is to clearly show that the design of individual primary rate paths may result in a wide variation of performance limits. As a result, attention must be paid to this when designing a 64 kbit/s connection so that the high grade international allocation of 40% (if based on ITU-T Rec. G.821) is not exceeded. + +### Example 1 + +![Diagram of a primary rate path showing a sequence of nodes: T1, BC1, T2, BC2, T3, BC3, T4, SC1, T5, SC2, T6, SC3, T7, BC4, T8. The path starts at T1 (PEP) and ends at T8 (PEP). The nodes are connected in a linear sequence. The diagram is labeled M.2100_FA-1.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +Diagram of a primary rate path showing a sequence of nodes: T1, BC1, T2, BC2, T3, BC3, T4, SC1, T5, SC2, T6, SC3, T7, BC4, T8. The path starts at T1 (PEP) and ends at T8 (PEP). The nodes are connected in a linear sequence. The diagram is labeled M.2100\_FA-1. + +T Terminating or transit IPCE +BC Border Crossing ICPCE +SC Submarine Cable ICPCE + +| | | | | +|---------|---------------------------------|-----------------|---------------------------| +| T1-T8 | IPCE (Terminating) | 1000 km-2500 km | $2 \times 4.0\% = 8.0\%$ | +| T2-T5 | IPCE (Transit) | 500 km-1000 km | $4 \times 3.0\% = 12.0\%$ | +| T6 | IPCE (Transit) | <500 km | $1 \times 2.0\% = 2.0\%$ | +| T7 | IPCE (Transit) | >5000 km | $1 \times 8.0\% = 8.0\%$ | +| SC1-SC3 | ICPCE (Optical Submarine Cable) | <500 km | $3 \times 2.5\% = 7.5\%$ | +| BC1-BC4 | ICPCE (Terrestrial) | | $4 \times 0.5\% = 2.0\%$ | + +Total primary rate path allocation = 39.5% + +**Figure A.1/M.2100 – Example of PO allocation** + +This path is suitable for 64 kbit/s connections that do not require an additional international primary rate connection such as allowing message traffic to be switched through to another international destination. + +### Example 2 + +![Diagram showing three primary rate paths (X, Y, Z) between T1 and T8. Path X includes T1, SC1, SC2, and T2. Path Y includes T3, SC3, T4, and BC1. Path Z includes T5, T6, BC2, T7, BC3, and T8. PEP markers are shown below the path segments.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) + +Diagram illustrating the allocation of primary rate paths (Path X, Path Y, Path Z) between T1 and T8. The diagram shows the sequence of nodes: T1, SC1, SC2, T2, T3, SC3, T4, BC1, T5, T6, BC2, T7, BC3, T8. PEP (Primary Rate Equipment) markers are indicated below the path segments. + +Legend: + +- T Terminating or transit IPCE +- BC Border Crossing ICPCE +- SC Submarine Cable ICPCE + +Path X allocation: + +| | | | | +|---------|---------------------------------|----------------|--------------------------------------------| +| T1 | IPCE (Terminating) | 500 km-1000 km | $1 \times 3.0\% = 3.0\%$ | +| T2 | IPCE (Terminating) | >5000 km | $1 \times 8.0\% = 8.0\%$ | +| SC1-SC2 | ICPCE (Optical Submarine Cable) | >500 km | $2 \times 2.5\% = 5.0\%$ | +| | | | Total primary rate path allocation = 16.0% | + +Path Y allocation: + +| | | | | +|-------|---------------------------------|----------------|--------------------------------------------| +| T3,T5 | IPCE (Terminating) | <500 km | $2 \times 2.0\% = 4.0\%$ | +| T4 | IPCE (Transit) | 500 km-1000 km | $1 \times 3.0\% = 3.0\%$ | +| SC3 | ICPCE (Optical Submarine Cable) | >500 km | $1 \times 2.5\% = 2.5\%$ | +| BC1 | ICPCE (Terrestrial) | | $1 \times 0.5\% = 0.5\%$ | +| | | | Total primary rate path allocation = 10.0% | + +Path Z allocation: + +| | | | | +|---------|---------------------|-----------------|--------------------------------------------| +| T6 | IPCE (Terminating) | 500 km-1000 km | $1 \times 3.0\% = 3.0\%$ | +| T7 | IPCE (Transit) | 1000 km-2500 km | $1 \times 4.0\% = 4.0\%$ | +| T8 | IPCE(Terminating) | <500 km | $1 \times 2.0\% = 2.0\%$ | +| BC2-BC3 | ICPCE (Terrestrial) | | $2 \times 0.5\% = 1.0\%$ | +| | | | Total primary rate path allocation = 10.0% | + +International 64 kbit/s path allocation: $16.0\% + 10.0\% + 10.0\% = 36.0\%$ + +Diagram showing three primary rate paths (X, Y, Z) between T1 and T8. Path X includes T1, SC1, SC2, and T2. Path Y includes T3, SC3, T4, and BC1. Path Z includes T5, T6, BC2, T7, BC3, and T8. PEP markers are shown below the path segments. + +**Figure A.2/M.2100 – Example of PO allocation** + +The total international high grade allocation for a 64 kbits/s connection between terminating countries T1 and T8 is 36.0% which is within the objective of 40%. Since the lowest allocation possible for a primary rate path is 4.5% (two terminating IPCEs < 500 km and one terrestrial ICPCE) adding a fourth primary rate path would exceed the 40% objective. This will be possible if this connection is using equipments designed according to ITU-T Rec. G.826 (maximum of 63%). + +# Annex B + +## In-service ES and SES event evaluation criteria + +This annex is presented as explanatory text followed by tables. The explanatory text is split into six sections which refer to their respective columns. + +Each table contains six columns. + +### **Column 1: Equipment Recommendation and path level (kbit/s)** + +The left hand column indicates the path bit rate in kbit/s, as well as any relevant qualifying information for the equipment in question and a reference to any relevant equipment Recommendation + +### **Column 2: Path overhead available to derive anomaly and defect information** + +The second column indicates the path overhead available in the given frame structure suitable for the derivation of anomaly and defect events. The following path overhead functions may be available: + +- CRC-4/6 errored block indication; +- E-bits events: Bit 1 of frame 13 and 15 in multiframe – CRC-4 error indication; +- FAS events (binary errors in alignment word); +- Remote defect indication events; +- A-bits: Remote defect indication – Bit 3 in ITU-T Rec. G.704; +- Parity bits; +- S-bits: (multi)frame alignment signal for 1544 kbit/s signals. + +### **Column 3: Anomalies and defects in 1 second** + +The third column lists the anomaly and defect criteria for 1 second duration. The following techniques may be used: + +- LOF alignment; +- LOS: Equipment dependent; +- Errored FAS: Binary errors in any FAS bits/words during the 1 second duration; +- Frame bit-errors: If the equipment can detect binary errors in the FAS word, then an SES can be detected using the suggested value. If the equipment can only detect FAS word violations, then the same number of violated FAS words will lead to an SES; +- A-bits: Remote defect indication – Bit 3 in ITU-T Rec. G.704; +- Remote defect indication bits; +- Parity errors; +- E-bits: Return CRC-4 errored block indicator bits. + +In a number of rows, values are suggested when recommended values are not available. + +Controlled slips may be introduced at primary rate path end points which are also international clock boundaries (see ITU-T Rec. G.822). A controlled slip is a deterministic impairment which effectively removes or duplicates a single frame of payload at the primary rate path end point. It is classified as an anomaly (see 5.2.2) and should be interpreted as causing an ES (but not an SES). + +### **Column 4: Interpretation for receive direction** + +Column 4 demonstrates how to interpret anomalies and defects detected using the criteria specified in Column 3 for the path overhead in Column 2. Anomalies lead to ESs, defects lead to SESs and ESs. + +### **Column 5: Interpretation for send direction** + +Column 5 demonstrates how to interpret anomalies and defects detected by the techniques specified in Column 3. Anomalies lead to ESs; defects lead to SESs and ESs. + +### **Column 6: Remarks** + +This column provides further explanatory text. + +**Table B.1/M.2100 – In-service ES and SES event evaluation criteria for subprimary level** + +| Path level (kbit/s) | Path overhead available to derive anomaly/defect information | ES/SES event measurement criteria (anomalies and defects in 1 second) | | | Remarks | +|---------------------|--------------------------------------------------------------|-----------------------------------------------------------------------|--------------------------------------|-----------------------------------|---------------------------------------------------------------------------------| +| | | Anomalies/ and defects in 1 second | Interpretation for receive direction | Interpretation for send direction | | +| 64 (clear) | None | – | – | – | ITU-T Rec. G.821 gives reference performance. | +| 64 ITU-T Rec. H.221 | CRC-4 E-bits FAS RDI bit | Under study | Under study | Under study | See ITU-T Rec. H.221 for details. Parameter evaluation criteria is under study. | + +**Table B.2/M.2100 – In-service ES and SES event evaluation criteria for synchronous frame structures used at the primary level** + +| Path level (kbit/s) | Path overhead available to derive anomaly/ defect information | ES/SES event measurement criteria (anomalies and defects in 1 second) | | | Remarks | +|---------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Anomalies/ and defects in 1 second | Interpretation for receive direction | Interpretation for send direction | | +| 1544 (non CRC-6) | FAS S-bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 8$ frame bit errors | ES + SES
ES + SES
ES + SES
ES
ES + SES | –
–
–
–
– | Send ES resolution limited to part of SES population. | +| 1544 (CRC-6) | CRC-6 FAS LOF | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ CRC-6 block errors
$\geq 320$ CRC-6 block errors
$\geq 1$ LOF sequence | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population (real-time). Total send ES data could be obtained from remote end store via 4 kbit/s data link (method not detailed). | +| 2048 (non CRC-4) | FAS A-bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 28$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| 2048 (CRC-4) | CRC-4 E-bits FAS A-bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ CRC-4 block errors
$\geq 805$ CRC-4 block errors
$\geq 1$ E-bit
$\geq 805$ E-bits
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
–
–
– | –
–
–
–
–
ES
ES + SES
ES + SES | Both send and receive ES and SES resolution possible in real-time from single end. | + +**Table B.3/M.2100 – In-service ES and SES event evaluation criteria +for equipment which operates at the primary level** + +| Equipment and path level (kbit/s) | Path overhead available to derive anomaly/defect information | ES/SES event measurement criteria (anomalies and defects in 1 second) | | | Remarks | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------| +| | | Anomalies/ and defects in 1 second | Interpretation for receive direction | Interpretation for send direction | | +| ITU-T Rec. G.724
ITU-T Rec. G.733
ITU-T Rec. G.762
ITU-T Rec. G.794
1544 | | | | | Uses ITU-T Recs G.704 and G.706.
See appropriate entry in Table B.2. | +| ITU-T Rec. G.734
1544 | FAS
RDI bit | ≥ 1 LOF
≥ 1 LOS
≥ 1 AIS
≥ 1 errored FAS
≥ 8 frame bit errors
≥ 1 RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | | +| ITU-T Rec. G.732
ITU-T Rec. G.735
ITU-T Rec. G.736
ITU-T Rec. G.737
ITU-T Rec. G.738
ITU-T Rec. G.739
ITU-T Rec. G.761
ITU-T Rec. G.793
2048 | | | | | Uses ITU-T Recs G.704 and G.706.
See appropriate entry in Table B.2. | + +**Table B.4/M.2100 – In-service ES and SES event evaluation criteria +for equipment which operates at the secondary level** + +| Equipment and path level (kbit/s) | Path overhead available to derive anomaly/defect information | ES/SES event measurement criteria (anomalies and defects in 1 second) | | | Remarks | +|-----------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Anomalies/ and defects in 1 second | Interpretation for receive direction | Interpretation for send direction | | +| ITU-T Rec. G.743 6312 | FAS
RDI bit (if equipped) | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 21$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population (if RDI equipped). | +| ITU-T Rec. G.747 6312 | Parity bit
FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ Parity error, or
$\geq 1$ errored FAS
$\geq 2000$ Parity errors or
$\geq 28$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES
ES + SES
ES + SES
– | –
–
–
–
–
–
–
ES + SES | The method of using Parity and/or errored FAS for receive ES and SES evaluation is under study. Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.742 8448 | FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 41$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.745 8448 | FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 22$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | + +**Table B.5/M.2100 – In-service ES and SES event evaluation criteria +for equipment which operates at the tertiary level** + +| Equipment and path level (kbit/s) | Path overhead available to derive anomaly/ defect information | ES/SES event measurement criteria (anomalies and defects in 1 second) | | | Remarks | +|-----------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Anomalies/ and defects in 1 second | Interpretation for receive direction | Interpretation for send direction | | +| ITU-T Rec. G.752
32 064 | FAS
RDI bit | ≥ 1 LOF
≥ 1 LOS
≥ 1 AIS
≥ 1 errored FAS
≥ 31 frame bit errors
≥ 1 RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.751
34 368 | FAS
RDI bit | ≥ 1 LOF
≥ 1 LOS
≥ 1 AIS
≥ 1 errored FAS
≥ 52 frame bit errors
≥ 1 RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.753
34 368 | FAS
RDI bit | ≥ 1 LOF
≥ 1 LOS
≥ 1 AIS
≥ 1 errored FAS
≥ 32 frame bit errors
≥ 1 RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.752
44 736 | Parity bits
FAS
RDI bit
(if equiped) | ≥ 1 LOF
≥ 1 LOS
≥ 1 AIS
≥ 1 Parity error,
or
≥ 1 errored FAS
≥ 2444 Parity errors,
or
≥ 5 frame bit errors
≥ 1 RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | The method of using Parity and/or errored FAS for receive ES and SES evaluation is under study. Send ES resolution limited to part of SES population (if RDI equipped). | + +**Table B.6/M.2100 – In-service ES and SES event evaluation criteria +for equipment which operates at the quaternary level** + +| Equipment and path level (kbit/s) | Path overhead available to derive anomaly/defect information | ES/SES event measurement criteria (anomalies and defects in 1 second) | | | Remarks | +|-----------------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Anomalies/ and defects in 1 second | Interpretation for receive direction | Interpretation for send direction | | +| ITU-T Rec. G.752 97 728 | Parity bit
FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ Parity error, or
$\geq 1$ errored FAS
$\geq 21\,000$ Parity errors, or
$\geq 152$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES
ES + SES
ES + SES
– | –
–
–
–
–
–
–
ES + SES | The method of using Parity and/or errored FAS for receive ES and SES evaluation is under study. Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.751 139 264 | FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 69$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.754 139 264 | FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ errored FAS
$\geq 104$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES + SES
– | –
–
–
–
–
ES + SES | Send ES resolution limited to part of SES population. | +| ITU-T Rec. G.755 139 264 | Parity bit
FAS
RDI bit | $\geq 1$ LOF
$\geq 1$ LOS
$\geq 1$ AIS
$\geq 1$ Parity error, or
$\geq 1$ errored FAS
$\geq 43\,800$ Parity errors or
$\geq 655$ frame bit errors
$\geq 1$ RDI | ES + SES
ES + SES
ES + SES
ES
ES
ES + SES
ES + SES
– | –
–
–
–
–
–
–
ES + SES | The method of using Parity and/or errored FAS for receive ES and SES evaluation is under study. Send ES resolution limited to part of SES population. | + +# Annex C + +## Values for bringing-into-service limits for international digital paths + +Tables have been prepared for each network level from 64 kbit/s to 139 264 kbit/s. + +- Tables C.1: Subprimary level. + +Table C.1a is applicable to connections based on ITU-T Rec. G.821 (i.e., using equipment designed before the adoption of ITU-T Rec. G.826) and Table C.1b is applicable to connections based on ITU-T Rec. G.826. + +- Table C.2: Primary level. +- Table C.3: Secondary level. +- Table C.4: Tertiary level. +- Table C.5: Quaternary level. + +**Table C.1a/M.2100 – BIS performance limits for subprimary level based on ITU-T Rec. G.821** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 0.2% | 0 | 0 | 0 | 0 | 0 | 0 | +| 0.5% | 0 | 0 | 0 | 0 | 3 | 0 | +| 1.0% | 0 | 0 | 0 | 0 | 9 | 0 | +| 1.5% | 0 | 0 | 0 | 0 | 16 | 0 | +| 2.0% | 0 | 0 | 0 | 0 | 23 | 0 | +| 2.5% | 0 | 0 | 0 | 0 | 30 | 0 | +| 3.0% | 0 | 0 | 0 | 0 | 37 | 0 | +| 3.5% | 0 | 0 | 0 | 0 | 45 | 0 | +| 4.0% | 0 | 0 | 0 | 0 | 52 | 0 | +| 4.5% | 0 | 0 | 0 | 0 | 60 | 0 | +| 5.0% | 0 | 0 | 0 | 0 | 68 | 0 | +| 5.5% | 0 | 0 | 0 | 0 | 76 | 0 | +| 6.0% | 0 | 0 | 0 | 0 | 83 | 0 | +| 6.5% | 0 | 0 | 0 | 0 | 91 | 0 | +| 7.0% | 0 | 0 | 0 | 0 | 99 | 0 | +| 7.5% | 0 | 0 | 0 | 0 | 107 | 0 | +| 8.0% | 0 | 0 | 0 | 0 | 115 | 0 | +| 8.5% | 0 | 0 | 0 | 0 | 123 | 0 | +| 9.0% | 0 | 0 | 0 | 0 | 131 | 0 | +| 9.5% | 0 | 0 | 0 | 0 | 139 | 0 | +| 10.0% | 0 | 0 | 0 | 0 | 147 | 0 | +| 10.5% | 0 | 0 | 0 | 0 | 155 | 0 | +| 11.0% | 0 | 0 | 0 | 0 | 163 | 0 | +| 11.5% | 0 | 0 | 0 | 0 | 171 | 1 | +| 12.0% | 0 | 0 | 0 | 0 | 179 | 1 | +| 12.5% | 0 | 0 | 0 | 0 | 187 | 1 | +| 13.0% | 0 | 0 | 0 | 0 | 195 | 1 | +| 13.5% | 0 | 0 | 0 | 0 | 203 | 1 | +| 14.0% | 0 | 0 | 0 | 0 | 211 | 1 | +| 14.5% | 0 | 0 | 0 | 0 | 219 | 1 | +| 15.0% | 0 | 0 | 0 | 0 | 227 | 1 | +| 15.5% | 0 | 0 | 0 | 0 | 235 | 2 | +| 16.0% | 0 | 0 | 0 | 0 | 243 | 2 | +| 16.5% | 0 | 0 | 14 | 0 | 251 | 2 | +| 17.0% | 0 | 0 | 15 | 0 | 259 | 2 | +| 17.5% | 0 | 0 | 15 | 0 | 268 | 2 | +| 18.0% | 0 | 0 | 16 | 0 | 276 | 2 | +| 18.5% | 0 | 0 | 16 | 0 | 284 | 2 | +| 19.0% | 0 | 0 | 17 | 0 | 292 | 2 | +| 19.5% | 0 | 0 | 17 | 0 | 300 | 3 | +| 20.0% | 0 | 0 | 18 | 0 | 308 | 3 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 20.5% | 0 | 0 | 19 | 0 | 317 | 3 | +| 21.0% | 0 | 0 | 19 | 0 | 325 | 3 | +| 21.5% | 0 | 0 | 20 | 0 | 333 | 3 | +| 22.0% | 0 | 0 | 20 | 0 | 341 | 3 | +| 22.5% | 0 | 0 | 21 | 0 | 349 | 3 | +| 23.0% | 0 | 0 | 22 | 0 | 358 | 4 | +| 23.5% | 0 | 0 | 22 | 0 | 366 | 4 | +| 24.0% | 0 | 0 | 23 | 0 | 374 | 4 | +| 24.5% | 0 | 0 | 23 | 0 | 382 | 4 | +| 25.0% | 0 | 0 | 24 | 0 | 390 | 4 | +| 25.5% | 0 | 0 | 25 | 0 | 399 | 4 | +| 26.0% | 0 | 0 | 25 | 0 | 407 | 5 | +| 26.5% | 0 | 0 | 26 | 0 | 415 | 5 | +| 27.0% | 0 | 0 | 26 | 0 | 423 | 5 | +| 27.5% | 0 | 0 | 27 | 0 | 432 | 5 | +| 28.0% | 0 | 0 | 28 | 0 | 440 | 5 | +| 28.5% | 0 | 0 | 28 | 0 | 448 | 5 | +| 29.0% | 0 | 0 | 29 | 0 | 456 | 5 | +| 29.5% | 0 | 0 | 29 | 0 | 465 | 6 | +| 30.0% | 0 | 0 | 30 | 0 | 473 | 6 | +| 30.5% | 0 | 0 | 31 | 0 | 481 | 6 | +| 31.0% | 0 | 0 | 31 | 0 | 489 | 6 | +| 31.5% | 0 | 0 | 32 | 0 | 498 | 6 | +| 32.0% | 0 | 0 | 33 | 0 | 506 | 6 | +| 32.5% | 0 | 0 | 33 | 0 | 514 | 7 | +| 33.0% | 0 | 0 | 34 | 0 | 522 | 7 | +| 33.5% | 0 | 0 | 34 | 0 | 531 | 7 | +| 34.0% | 0 | 0 | 35 | 0 | 539 | 7 | +| 34.5% | 0 | 0 | 36 | 0 | 547 | 7 | +| 35.0% | 0 | 0 | 36 | 0 | 556 | 7 | +| 35.5% | 0 | 0 | 37 | 0 | 564 | 8 | +| 36.0% | 0 | 0 | 37 | 0 | 572 | 8 | +| 36.5% | 0 | 0 | 38 | 0 | 580 | 8 | +| 37.0% | 0 | 0 | 39 | 0 | 589 | 8 | +| 37.5% | 0 | 0 | 39 | 0 | 597 | 8 | +| 38.0% | 0 | 0 | 40 | 0 | 605 | 8 | +| 38.5% | 0 | 0 | 41 | 0 | 614 | 8 | +| 39.0% | 0 | 0 | 41 | 0 | 622 | 9 | +| 39.5% | 0 | 0 | 42 | 0 | 630 | 9 | +| 40.0% | 0 | 0 | 42 | 0 | 639 | 9 | + +**Table C.1b/M.2100 – BIS performance limits for subprimary level based on ITU-T Rec. G.826** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 0.2% | 0 | 0 | 0 | 0 | 0 | 0 | +| 0.5% | 0 | 0 | 0 | 0 | 0 | 0 | +| 1.0% | 0 | 0 | 0 | 0 | 3 | 0 | +| 1.5% | 0 | 0 | 0 | 0 | 6 | 0 | +| 2.0% | 0 | 0 | 0 | 0 | 9 | 0 | +| 2.5% | 0 | 0 | 0 | 0 | 12 | 0 | +| 3.0% | 0 | 0 | 0 | 0 | 16 | 0 | +| 3.5% | 0 | 0 | 0 | 0 | 19 | 0 | +| 4.0% | 0 | 0 | 0 | 0 | 23 | 0 | +| 4.5% | 0 | 0 | 0 | 0 | 26 | 0 | +| 5.0% | 0 | 0 | 0 | 0 | 30 | 0 | +| 5.5% | 0 | 0 | 0 | 0 | 34 | 0 | +| 6.0% | 0 | 0 | 0 | 0 | 37 | 0 | +| 6.5% | 0 | 0 | 0 | 0 | 41 | 0 | +| 7.0% | 0 | 0 | 1 | 0 | 45 | 0 | +| 7.5% | 0 | 0 | 1 | 0 | 49 | 0 | +| 8.0% | 0 | 0 | 1 | 0 | 52 | 0 | +| 8.5% | 0 | 0 | 1 | 0 | 56 | 0 | +| 9.0% | 0 | 0 | 1 | 0 | 60 | 0 | +| 9.5% | 0 | 0 | 2 | 0 | 64 | 0 | +| 10.0% | 0 | 0 | 2 | 0 | 68 | 0 | +| 10.5% | 0 | 0 | 2 | 0 | 72 | 0 | +| 11.0% | 0 | 0 | 2 | 0 | 76 | 0 | +| 11.5% | 0 | 0 | 3 | 0 | 79 | 1 | +| 12.0% | 0 | 0 | 3 | 0 | 83 | 1 | +| 12.5% | 0 | 0 | 3 | 0 | 87 | 1 | +| 13.0% | 0 | 0 | 3 | 0 | 91 | 1 | +| 13.5% | 0 | 0 | 3 | 0 | 95 | 1 | +| 14.0% | 0 | 0 | 4 | 0 | 99 | 1 | +| 14.5% | 0 | 0 | 4 | 0 | 103 | 1 | +| 15.0% | 0 | 0 | 4 | 0 | 107 | 1 | +| 15.5% | 0 | 0 | 4 | 0 | 111 | 2 | +| 16.0% | 0 | 0 | 5 | 0 | 115 | 2 | +| 16.5% | 0 | 0 | 5 | 0 | 119 | 2 | +| 17.0% | 0 | 0 | 5 | 0 | 123 | 2 | +| 17.5% | 0 | 0 | 6 | 0 | 127 | 2 | +| 18.0% | 0 | 0 | 6 | 0 | 131 | 2 | +| 18.5% | 0 | 0 | 6 | 0 | 135 | 2 | +| 19.0% | 0 | 0 | 6 | 0 | 139 | 2 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 19.5% | 0 | 0 | 7 | 0 | 143 | 3 | +| 20.0% | 0 | 0 | 7 | 0 | 147 | 3 | +| 20.5% | 0 | 0 | 7 | 0 | 151 | 3 | +| 21.0% | 0 | 0 | 7 | 0 | 155 | 3 | +| 21.5% | 0 | 0 | 8 | 0 | 159 | 3 | +| 22.0% | 0 | 0 | 8 | 0 | 163 | 3 | +| 22.5% | 0 | 0 | 8 | 0 | 167 | 3 | +| 23.0% | 0 | 0 | 8 | 0 | 171 | 4 | +| 23.5% | 0 | 0 | 9 | 0 | 175 | 4 | +| 24.0% | 0 | 0 | 9 | 0 | 179 | 4 | +| 24.5% | 0 | 0 | 9 | 0 | 183 | 4 | +| 25.0% | 0 | 0 | 10 | 0 | 187 | 4 | +| 25.5% | 0 | 0 | 10 | 0 | 191 | 4 | +| 26.0% | 0 | 0 | 10 | 0 | 195 | 5 | +| 26.5% | 0 | 0 | 10 | 0 | 199 | 5 | +| 27.0% | 0 | 0 | 11 | 0 | 203 | 5 | +| 27.5% | 0 | 0 | 11 | 0 | 207 | 5 | +| 28.0% | 0 | 0 | 11 | 0 | 211 | 5 | +| 28.5% | 0 | 0 | 11 | 0 | 215 | 5 | +| 29.0% | 0 | 0 | 12 | 0 | 219 | 5 | +| 29.5% | 0 | 0 | 12 | 0 | 223 | 6 | +| 30.0% | 0 | 0 | 12 | 0 | 227 | 6 | +| 30.5% | 0 | 0 | 13 | 0 | 231 | 6 | +| 31.0% | 0 | 0 | 13 | 0 | 235 | 6 | +| 31.5% | 0 | 0 | 13 | 0 | 239 | 6 | +| 32.0% | 0 | 0 | 13 | 0 | 243 | 6 | +| 32.5% | 0 | 0 | 14 | 0 | 247 | 7 | +| 33.0% | 0 | 0 | 14 | 0 | 251 | 7 | +| 33.5% | 0 | 0 | 14 | 0 | 255 | 7 | +| 34.0% | 0 | 0 | 15 | 0 | 259 | 7 | +| 34.5% | 0 | 0 | 15 | 0 | 264 | 7 | +| 35.0% | 0 | 0 | 15 | 0 | 268 | 7 | +| 35.5% | 0 | 0 | 15 | 0 | 272 | 8 | +| 36.0% | 0 | 0 | 16 | 0 | 276 | 8 | +| 36.5% | 0 | 0 | 16 | 0 | 280 | 8 | +| 37.0% | 0 | 0 | 16 | 0 | 284 | 8 | +| 37.5% | 0 | 0 | 17 | 0 | 288 | 8 | +| 38.0% | 0 | 0 | 17 | 0 | 292 | 8 | +| 38.5% | 0 | 0 | 17 | 0 | 296 | 8 | + +**Table C.1b/M.2100 – BIS performance limits for subprimary level based on ITU-T Rec. G.826** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 39.0% | 0 | 0 | 17 | 0 | 300 | 9 | +| 39.5% | 0 | 0 | 18 | 0 | 304 | 9 | +| 40.0% | 0 | 0 | 18 | 0 | 308 | 9 | +| 40.5% | 0 | 0 | 18 | 0 | 313 | 9 | +| 41.0% | 0 | 0 | 19 | 0 | 317 | 9 | +| 41.5% | 0 | 0 | 19 | 0 | 321 | 9 | +| 42.0% | 0 | 0 | 19 | 0 | 325 | 10 | +| 42.5% | 0 | 0 | 20 | 0 | 329 | 10 | +| 43.0% | 0 | 0 | 20 | 0 | 333 | 10 | +| 43.5% | 0 | 0 | 20 | 0 | 337 | 10 | +| 44.0% | 0 | 0 | 20 | 0 | 341 | 10 | +| 44.5% | 0 | 0 | 21 | 0 | 345 | 10 | +| 45.0% | 0 | 0 | 21 | 0 | 349 | 11 | +| 45.5% | 0 | 0 | 21 | 0 | 353 | 11 | +| 46.0% | 0 | 0 | 22 | 0 | 358 | 11 | +| 46.5% | 0 | 0 | 22 | 0 | 362 | 11 | +| 47.0% | 0 | 0 | 22 | 0 | 366 | 11 | +| 47.5% | 0 | 0 | 23 | 0 | 370 | 11 | +| 48.0% | 0 | 0 | 23 | 0 | 374 | 12 | +| 48.5% | 0 | 0 | 23 | 0 | 378 | 12 | +| 49.0% | 0 | 0 | 23 | 0 | 382 | 12 | +| 49.5% | 0 | 0 | 24 | 0 | 386 | 12 | +| 50.0% | 0 | 0 | 24 | 0 | 390 | 12 | +| 50.5% | 0 | 0 | 24 | 0 | 395 | 12 | +| 51.0% | 0 | 0 | 25 | 0 | 399 | 13 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 51.5% | 0 | 0 | 25 | 0 | 403 | 13 | +| 52.0% | 0 | 0 | 25 | 0 | 407 | 13 | +| 52.5% | 0 | 0 | 26 | 0 | 411 | 13 | +| 53.0% | 0 | 0 | 26 | 0 | 415 | 13 | +| 53.5% | 0 | 0 | 26 | 0 | 419 | 13 | +| 54.0% | 0 | 0 | 26 | 0 | 423 | 14 | +| 54.5% | 0 | 0 | 27 | 0 | 427 | 14 | +| 55.0% | 0 | 0 | 27 | 0 | 432 | 14 | +| 55.5% | 0 | 0 | 27 | 0 | 436 | 14 | +| 56.0% | 0 | 0 | 28 | 0 | 440 | 14 | +| 56.5% | 0 | 0 | 28 | 0 | 444 | 15 | +| 57.0% | 0 | 0 | 28 | 0 | 448 | 15 | +| 57.5% | 0 | 0 | 29 | 0 | 452 | 15 | +| 58.0% | 0 | 0 | 29 | 0 | 456 | 15 | +| 58.5% | 0 | 0 | 29 | 0 | 460 | 15 | +| 59.0% | 0 | 0 | 29 | 0 | 465 | 15 | +| 59.5% | 0 | 0 | 30 | 0 | 469 | 16 | +| 60.0% | 0 | 0 | 30 | 0 | 473 | 16 | +| 60.5% | 0 | 0 | 30 | 0 | 477 | 16 | +| 61.0% | 0 | 0 | 31 | 0 | 481 | 16 | +| 61.5% | 0 | 0 | 31 | 0 | 485 | 16 | +| 62.0% | 0 | 0 | 31 | 0 | 489 | 16 | +| 62.5% | 0 | 0 | 32 | 0 | 494 | 17 | +| 63.0% | 0 | 0 | 32 | 0 | 498 | 17 | + +**Table C.2/M.2100 – BIS performance limits for primary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 0.2% | 0 | 0 | 0 | 0 | 0 | 0 | +| 0.5% | 0 | 0 | 0 | 0 | 0 | 0 | +| 1.0% | 0 | 0 | 0 | 0 | 3 | 0 | +| 1.5% | 0 | 0 | 0 | 0 | 6 | 0 | +| 2.0% | 0 | 0 | 0 | 0 | 9 | 0 | +| 2.5% | 0 | 0 | 0 | 0 | 12 | 0 | +| 3.0% | 0 | 0 | 0 | 0 | 16 | 0 | +| 3.5% | 0 | 0 | 0 | 0 | 19 | 0 | +| 4.0% | 0 | 0 | 0 | 0 | 23 | 0 | +| 4.5% | 0 | 0 | 0 | 0 | 26 | 0 | +| 5.0% | 0 | 0 | 0 | 0 | 30 | 0 | +| 5.5% | 0 | 0 | 0 | 0 | 34 | 0 | +| 6.0% | 0 | 0 | 0 | 0 | 37 | 0 | +| 6.5% | 0 | 0 | 0 | 0 | 41 | 0 | +| 7.0% | 0 | 0 | 1 | 0 | 45 | 0 | +| 7.5% | 0 | 0 | 1 | 0 | 49 | 0 | +| 8.0% | 0 | 0 | 1 | 0 | 52 | 0 | +| 8.5% | 0 | 0 | 1 | 0 | 56 | 0 | +| 9.0% | 0 | 0 | 1 | 0 | 60 | 0 | +| 9.5% | 0 | 0 | 2 | 0 | 64 | 0 | +| 10.0% | 0 | 0 | 2 | 0 | 68 | 0 | +| 10.5% | 0 | 0 | 2 | 0 | 72 | 0 | +| 11.0% | 0 | 0 | 2 | 0 | 76 | 0 | +| 11.5% | 0 | 0 | 3 | 0 | 79 | 1 | +| 12.0% | 0 | 0 | 3 | 0 | 83 | 1 | +| 12.5% | 0 | 0 | 3 | 0 | 87 | 1 | +| 13.0% | 0 | 0 | 3 | 0 | 91 | 1 | +| 13.5% | 0 | 0 | 3 | 0 | 95 | 1 | +| 14.0% | 0 | 0 | 4 | 0 | 99 | 1 | +| 14.5% | 0 | 0 | 4 | 0 | 103 | 1 | +| 15.0% | 0 | 0 | 4 | 0 | 107 | 1 | +| 15.5% | 0 | 0 | 4 | 0 | 111 | 2 | +| 16.0% | 0 | 0 | 5 | 0 | 115 | 2 | +| 16.5% | 0 | 0 | 5 | 0 | 119 | 2 | +| 17.0% | 0 | 0 | 5 | 0 | 123 | 2 | +| 17.5% | 0 | 0 | 6 | 0 | 127 | 2 | +| 18.0% | 0 | 0 | 6 | 0 | 131 | 2 | +| 18.5% | 0 | 0 | 6 | 0 | 135 | 2 | +| 19.0% | 0 | 0 | 6 | 0 | 139 | 2 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 19.5% | 0 | 0 | 7 | 0 | 143 | 3 | +| 20.0% | 0 | 0 | 7 | 0 | 147 | 3 | +| 20.5% | 0 | 0 | 7 | 0 | 151 | 3 | +| 21.0% | 0 | 0 | 7 | 0 | 155 | 3 | +| 21.5% | 0 | 0 | 8 | 0 | 159 | 3 | +| 22.0% | 0 | 0 | 8 | 0 | 163 | 3 | +| 22.5% | 0 | 0 | 8 | 0 | 167 | 3 | +| 23.0% | 0 | 0 | 8 | 0 | 171 | 4 | +| 23.5% | 0 | 0 | 9 | 0 | 175 | 4 | +| 24.0% | 0 | 0 | 9 | 0 | 179 | 4 | +| 24.5% | 0 | 0 | 9 | 0 | 183 | 4 | +| 25.0% | 0 | 0 | 10 | 0 | 187 | 4 | +| 25.5% | 0 | 0 | 10 | 0 | 191 | 4 | +| 26.0% | 0 | 0 | 10 | 0 | 195 | 5 | +| 26.5% | 0 | 0 | 10 | 0 | 199 | 5 | +| 27.0% | 0 | 0 | 11 | 0 | 203 | 5 | +| 27.5% | 0 | 0 | 11 | 0 | 207 | 5 | +| 28.0% | 0 | 0 | 11 | 0 | 211 | 5 | +| 28.5% | 0 | 0 | 11 | 0 | 215 | 5 | +| 29.0% | 0 | 0 | 12 | 0 | 219 | 5 | +| 29.5% | 0 | 0 | 12 | 0 | 223 | 6 | +| 30.0% | 0 | 0 | 12 | 0 | 227 | 6 | +| 30.5% | 0 | 0 | 13 | 0 | 231 | 6 | +| 31.0% | 0 | 0 | 13 | 0 | 235 | 6 | +| 31.5% | 0 | 0 | 13 | 0 | 239 | 6 | +| 32.0% | 0 | 0 | 13 | 0 | 243 | 6 | +| 32.5% | 0 | 0 | 14 | 0 | 247 | 7 | +| 33.0% | 0 | 0 | 14 | 0 | 251 | 7 | +| 33.5% | 0 | 0 | 14 | 0 | 255 | 7 | +| 34.0% | 0 | 0 | 15 | 0 | 259 | 7 | +| 34.5% | 0 | 0 | 15 | 0 | 264 | 7 | +| 35.0% | 0 | 0 | 15 | 0 | 268 | 7 | +| 35.5% | 0 | 0 | 15 | 0 | 272 | 8 | +| 36.0% | 0 | 0 | 16 | 0 | 276 | 8 | +| 36.5% | 0 | 0 | 16 | 0 | 280 | 8 | +| 37.0% | 0 | 0 | 16 | 0 | 284 | 8 | +| 37.5% | 0 | 0 | 17 | 0 | 288 | 8 | +| 38.0% | 0 | 0 | 17 | 0 | 292 | 8 | +| 38.5% | 0 | 0 | 17 | 0 | 296 | 8 | + +**Table C.2/M.2100 – BIS performance limits for primary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 39.0% | 0 | 0 | 17 | 0 | 300 | 9 | +| 39.5% | 0 | 0 | 18 | 0 | 304 | 9 | +| 40.0% | 0 | 0 | 18 | 0 | 308 | 9 | +| 40.5% | 0 | 0 | 18 | 0 | 313 | 9 | +| 41.0% | 0 | 0 | 19 | 0 | 317 | 9 | +| 41.5% | 0 | 0 | 19 | 0 | 321 | 9 | +| 42.0% | 0 | 0 | 19 | 0 | 325 | 10 | +| 42.5% | 0 | 0 | 20 | 0 | 329 | 10 | +| 43.0% | 0 | 0 | 20 | 0 | 333 | 10 | +| 43.5% | 0 | 0 | 20 | 0 | 337 | 10 | +| 44.0% | 0 | 0 | 20 | 0 | 341 | 10 | +| 44.5% | 0 | 0 | 21 | 0 | 345 | 10 | +| 45.0% | 0 | 0 | 21 | 0 | 349 | 11 | +| 45.5% | 0 | 0 | 21 | 0 | 353 | 11 | +| 46.0% | 0 | 0 | 22 | 0 | 358 | 11 | +| 46.5% | 0 | 0 | 22 | 0 | 362 | 11 | +| 47.0% | 0 | 0 | 22 | 0 | 366 | 11 | +| 47.5% | 0 | 0 | 23 | 0 | 370 | 11 | +| 48.0% | 0 | 0 | 23 | 0 | 374 | 12 | +| 48.5% | 0 | 0 | 23 | 0 | 378 | 12 | +| 49.0% | 0 | 0 | 23 | 0 | 382 | 12 | +| 49.5% | 0 | 0 | 24 | 0 | 386 | 12 | +| 50.0% | 0 | 0 | 24 | 0 | 390 | 12 | +| 50.5% | 0 | 0 | 24 | 0 | 395 | 12 | +| 51.0% | 0 | 0 | 25 | 0 | 399 | 13 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 51.5% | 0 | 0 | 25 | 0 | 403 | 13 | +| 52.0% | 0 | 0 | 25 | 0 | 407 | 13 | +| 52.5% | 0 | 0 | 26 | 0 | 411 | 13 | +| 53.0% | 0 | 0 | 26 | 0 | 415 | 13 | +| 53.5% | 0 | 0 | 26 | 0 | 419 | 13 | +| 54.0% | 0 | 0 | 26 | 0 | 423 | 14 | +| 54.5% | 0 | 0 | 27 | 0 | 427 | 14 | +| 55.0% | 0 | 0 | 27 | 0 | 432 | 14 | +| 55.5% | 0 | 0 | 27 | 0 | 436 | 14 | +| 56.0% | 0 | 0 | 28 | 0 | 440 | 14 | +| 56.5% | 0 | 0 | 28 | 0 | 444 | 15 | +| 57.0% | 0 | 0 | 28 | 0 | 448 | 15 | +| 57.5% | 0 | 0 | 29 | 0 | 452 | 15 | +| 58.0% | 0 | 0 | 29 | 0 | 456 | 15 | +| 58.5% | 0 | 0 | 29 | 0 | 460 | 15 | +| 59.0% | 0 | 0 | 29 | 0 | 465 | 15 | +| 59.5% | 0 | 0 | 30 | 0 | 469 | 16 | +| 60.0% | 0 | 0 | 30 | 0 | 473 | 16 | +| 60.5% | 0 | 0 | 30 | 0 | 477 | 16 | +| 61.0% | 0 | 0 | 31 | 0 | 481 | 16 | +| 61.5% | 0 | 0 | 31 | 0 | 485 | 16 | +| 62.0% | 0 | 0 | 31 | 0 | 489 | 16 | +| 62.5% | 0 | 0 | 32 | 0 | 494 | 17 | +| 63.0% | 0 | 0 | 32 | 0 | 498 | 17 | + +**Table C.3/M.2100 – BIS performance limits for secondary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 0.2% | 0 | 0 | 0 | 0 | 0 | 0 | +| 0.5% | 0 | 0 | 0 | 0 | 1 | 0 | +| 1.0% | 0 | 0 | 0 | 0 | 4 | 0 | +| 1.5% | 0 | 0 | 0 | 0 | 8 | 0 | +| 2.0% | 0 | 0 | 0 | 0 | 12 | 0 | +| 2.5% | 0 | 0 | 0 | 0 | 17 | 0 | +| 3.0% | 0 | 0 | 0 | 0 | 21 | 0 | +| 3.5% | 0 | 0 | 0 | 0 | 26 | 0 | +| 4.0% | 0 | 0 | 0 | 0 | 30 | 0 | +| 4.5% | 0 | 0 | 0 | 0 | 35 | 0 | +| 5.0% | 0 | 0 | 0 | 0 | 39 | 0 | +| 5.5% | 0 | 0 | 1 | 0 | 44 | 0 | +| 6.0% | 0 | 0 | 1 | 0 | 49 | 0 | +| 6.5% | 0 | 0 | 1 | 0 | 53 | 0 | +| 7.0% | 0 | 0 | 1 | 0 | 58 | 0 | +| 7.5% | 0 | 0 | 2 | 0 | 63 | 0 | +| 8.0% | 0 | 0 | 2 | 0 | 68 | 0 | +| 8.5% | 0 | 0 | 2 | 0 | 73 | 0 | +| 9.0% | 0 | 0 | 2 | 0 | 77 | 0 | +| 9.5% | 0 | 0 | 3 | 0 | 82 | 0 | +| 10.0% | 0 | 0 | 3 | 0 | 87 | 0 | +| 10.5% | 0 | 0 | 3 | 0 | 92 | 0 | +| 11.0% | 0 | 0 | 4 | 0 | 97 | 0 | +| 11.5% | 0 | 0 | 4 | 0 | 102 | 1 | +| 12.0% | 0 | 0 | 4 | 0 | 107 | 1 | +| 12.5% | 0 | 0 | 5 | 0 | 112 | 1 | +| 13.0% | 0 | 0 | 5 | 0 | 117 | 1 | +| 13.5% | 0 | 0 | 5 | 0 | 122 | 1 | +| 14.0% | 0 | 0 | 6 | 0 | 127 | 1 | +| 14.5% | 0 | 0 | 6 | 0 | 132 | 1 | +| 15.0% | 0 | 0 | 6 | 0 | 137 | 1 | +| 15.5% | 0 | 0 | 6 | 0 | 142 | 2 | +| 16.0% | 0 | 0 | 7 | 0 | 147 | 2 | +| 16.5% | 0 | 0 | 7 | 0 | 152 | 2 | +| 17.0% | 0 | 0 | 7 | 0 | 157 | 2 | +| 17.5% | 0 | 0 | 8 | 0 | 162 | 2 | +| 18.0% | 0 | 0 | 8 | 0 | 167 | 2 | +| 18.5% | 0 | 0 | 8 | 0 | 172 | 2 | +| 19.0% | 0 | 0 | 9 | 0 | 177 | 2 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 19.5% | 0 | 0 | 9 | 0 | 182 | 3 | +| 20.0% | 0 | 0 | 10 | 0 | 187 | 3 | +| 20.5% | 0 | 0 | 10 | 0 | 192 | 3 | +| 21.0% | 0 | 0 | 10 | 0 | 197 | 3 | +| 21.5% | 0 | 0 | 11 | 0 | 202 | 3 | +| 22.0% | 0 | 0 | 11 | 0 | 207 | 3 | +| 22.5% | 0 | 0 | 11 | 0 | 212 | 3 | +| 23.0% | 0 | 0 | 12 | 0 | 217 | 4 | +| 23.5% | 0 | 0 | 12 | 0 | 222 | 4 | +| 24.0% | 0 | 0 | 12 | 0 | 227 | 4 | +| 24.5% | 0 | 0 | 13 | 0 | 232 | 4 | +| 25.0% | 0 | 0 | 13 | 0 | 237 | 4 | +| 25.5% | 0 | 0 | 13 | 0 | 242 | 4 | +| 26.0% | 0 | 0 | 14 | 0 | 247 | 5 | +| 26.5% | 0 | 0 | 14 | 0 | 252 | 5 | +| 27.0% | 0 | 0 | 14 | 0 | 257 | 5 | +| 27.5% | 0 | 0 | 15 | 0 | 263 | 5 | +| 28.0% | 0 | 0 | 15 | 0 | 268 | 5 | +| 28.5% | 0 | 0 | 16 | 0 | 273 | 5 | +| 29.0% | 0 | 0 | 16 | 0 | 278 | 5 | +| 29.5% | 0 | 0 | 16 | 0 | 283 | 6 | +| 30.0% | 0 | 0 | 17 | 0 | 288 | 6 | +| 30.5% | 0 | 0 | 17 | 0 | 293 | 6 | +| 31.0% | 0 | 0 | 17 | 0 | 298 | 6 | +| 31.5% | 0 | 0 | 18 | 0 | 303 | 6 | +| 32.0% | 0 | 0 | 18 | 0 | 308 | 6 | +| 32.5% | 0 | 0 | 18 | 0 | 314 | 7 | +| 33.0% | 0 | 0 | 19 | 0 | 319 | 7 | +| 33.5% | 0 | 0 | 19 | 0 | 324 | 7 | +| 34.0% | 0 | 0 | 20 | 0 | 329 | 7 | +| 34.5% | 0 | 0 | 20 | 0 | 334 | 7 | +| 35.0% | 0 | 0 | 20 | 0 | 339 | 7 | +| 35.5% | 0 | 0 | 21 | 0 | 344 | 8 | +| 36.0% | 0 | 0 | 21 | 0 | 349 | 8 | +| 36.5% | 0 | 0 | 21 | 0 | 354 | 8 | +| 37.0% | 0 | 0 | 22 | 0 | 360 | 8 | +| 37.5% | 0 | 0 | 22 | 0 | 365 | 8 | +| 38.0% | 0 | 0 | 23 | 0 | 370 | 8 | +| 38.5% | 0 | 0 | 23 | 0 | 375 | 8 | + +**Table C.3/M.2100 – BIS performance limits for secondary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 39.0% | 0 | 0 | 23 | 0 | 380 | 9 | +| 39.5% | 0 | 0 | 24 | 0 | 385 | 9 | +| 40.0% | 0 | 0 | 24 | 0 | 390 | 9 | +| 40.5% | 0 | 0 | 24 | 0 | 396 | 9 | +| 41.0% | 0 | 0 | 25 | 0 | 401 | 9 | +| 41.5% | 0 | 0 | 25 | 0 | 406 | 9 | +| 42.0% | 0 | 0 | 26 | 0 | 411 | 10 | +| 42.5% | 0 | 0 | 26 | 0 | 416 | 10 | +| 43.0% | 0 | 0 | 26 | 0 | 421 | 10 | +| 43.5% | 0 | 0 | 27 | 0 | 426 | 10 | +| 44.0% | 0 | 0 | 27 | 0 | 432 | 10 | +| 44.5% | 0 | 0 | 27 | 0 | 437 | 10 | +| 45.0% | 0 | 0 | 28 | 0 | 442 | 11 | +| 45.5% | 0 | 0 | 28 | 0 | 447 | 11 | +| 46.0% | 0 | 0 | 29 | 0 | 452 | 11 | +| 46.5% | 0 | 0 | 29 | 0 | 457 | 11 | +| 47.0% | 0 | 0 | 29 | 0 | 463 | 11 | +| 47.5% | 0 | 0 | 30 | 0 | 468 | 11 | +| 48.0% | 0 | 0 | 30 | 0 | 473 | 12 | +| 48.5% | 0 | 0 | 30 | 0 | 478 | 12 | +| 49.0% | 0 | 0 | 31 | 0 | 483 | 12 | +| 49.5% | 0 | 0 | 31 | 0 | 488 | 12 | +| 50.0% | 0 | 0 | 32 | 0 | 494 | 12 | +| 50.5% | 0 | 0 | 32 | 0 | 499 | 12 | +| 51.0% | 0 | 0 | 32 | 0 | 504 | 13 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 51.5% | 0 | 0 | 33 | 0 | 509 | 13 | +| 52.0% | 0 | 0 | 33 | 0 | 514 | 13 | +| 52.5% | 0 | 0 | 34 | 0 | 519 | 13 | +| 53.0% | 0 | 0 | 34 | 0 | 525 | 13 | +| 53.5% | 0 | 0 | 34 | 0 | 530 | 13 | +| 54.0% | 0 | 0 | 35 | 0 | 535 | 14 | +| 54.5% | 0 | 0 | 35 | 0 | 540 | 14 | +| 55.0% | 0 | 0 | 35 | 0 | 545 | 14 | +| 55.5% | 0 | 0 | 36 | 0 | 550 | 14 | +| 56.0% | 0 | 0 | 36 | 0 | 556 | 14 | +| 56.5% | 0 | 0 | 37 | 0 | 561 | 15 | +| 57.0% | 0 | 0 | 37 | 0 | 566 | 15 | +| 57.5% | 0 | 0 | 37 | 0 | 571 | 15 | +| 58.0% | 0 | 0 | 38 | 0 | 576 | 15 | +| 58.5% | 0 | 0 | 38 | 0 | 582 | 15 | +| 59.0% | 0 | 0 | 39 | 0 | 587 | 15 | +| 59.5% | 0 | 0 | 39 | 0 | 592 | 16 | +| 60.0% | 0 | 0 | 39 | 0 | 597 | 16 | +| 60.5% | 0 | 0 | 40 | 0 | 602 | 16 | +| 61.0% | 0 | 0 | 40 | 0 | 607 | 16 | +| 61.5% | 0 | 0 | 40 | 0 | 613 | 16 | +| 62.0% | 0 | 0 | 41 | 0 | 618 | 16 | +| 62.5% | 0 | 0 | 41 | 0 | 623 | 17 | +| 63.0% | 0 | 0 | 42 | 0 | 628 | 17 | + +**Table C.4/M.2100 – BIS performance limits for tertiary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 0.2% | 0 | 0 | 0 | 0 | 0 | 0 | +| 0.5% | 0 | 0 | 0 | 0 | 2 | 0 | +| 1.0% | 0 | 0 | 0 | 0 | 8 | 0 | +| 1.5% | 0 | 0 | 0 | 0 | 14 | 0 | +| 2.0% | 0 | 0 | 0 | 0 | 21 | 0 | +| 2.5% | 0 | 0 | 0 | 0 | 28 | 0 | +| 3.0% | 0 | 0 | 0 | 0 | 35 | 0 | +| 3.5% | 0 | 0 | 0 | 0 | 42 | 0 | +| 4.0% | 0 | 0 | 1 | 0 | 49 | 0 | +| 4.5% | 0 | 0 | 1 | 0 | 56 | 0 | +| 5.0% | 0 | 0 | 2 | 0 | 63 | 0 | +| 5.5% | 0 | 0 | 2 | 0 | 70 | 0 | +| 6.0% | 0 | 0 | 2 | 0 | 77 | 0 | +| 6.5% | 0 | 0 | 3 | 0 | 85 | 0 | +| 7.0% | 0 | 0 | 3 | 0 | 92 | 0 | +| 7.5% | 0 | 0 | 4 | 0 | 99 | 0 | +| 8.0% | 0 | 0 | 4 | 0 | 107 | 0 | +| 8.5% | 0 | 0 | 5 | 0 | 114 | 0 | +| 9.0% | 0 | 0 | 5 | 0 | 122 | 0 | +| 9.5% | 0 | 0 | 6 | 0 | 129 | 0 | +| 10.0% | 0 | 0 | 6 | 0 | 137 | 0 | +| 10.5% | 0 | 0 | 7 | 0 | 144 | 0 | +| 11.0% | 0 | 0 | 7 | 0 | 152 | 0 | +| 11.5% | 0 | 0 | 8 | 0 | 159 | 1 | +| 12.0% | 0 | 0 | 8 | 0 | 167 | 1 | +| 12.5% | 0 | 0 | 9 | 0 | 174 | 1 | +| 13.0% | 0 | 0 | 9 | 0 | 182 | 1 | +| 13.5% | 0 | 0 | 10 | 0 | 189 | 1 | +| 14.0% | 0 | 0 | 10 | 0 | 197 | 1 | +| 14.5% | 0 | 0 | 11 | 0 | 204 | 1 | +| 15.0% | 0 | 0 | 11 | 0 | 212 | 1 | +| 15.5% | 0 | 0 | 12 | 0 | 219 | 2 | +| 16.0% | 0 | 0 | 12 | 0 | 227 | 2 | +| 16.5% | 0 | 0 | 13 | 0 | 235 | 2 | +| 17.0% | 0 | 0 | 13 | 0 | 242 | 2 | +| 17.5% | 0 | 0 | 14 | 0 | 250 | 2 | +| 18.0% | 0 | 0 | 14 | 0 | 257 | 2 | +| 18.5% | 0 | 0 | 15 | 0 | 265 | 2 | +| 19.0% | 0 | 0 | 16 | 0 | 273 | 2 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 19.5% | 0 | 0 | 16 | 0 | 280 | 3 | +| 20.0% | 0 | 0 | 17 | 0 | 288 | 3 | +| 20.5% | 0 | 0 | 17 | 0 | 296 | 3 | +| 21.0% | 0 | 0 | 18 | 0 | 303 | 3 | +| 21.5% | 0 | 0 | 18 | 0 | 311 | 3 | +| 22.0% | 0 | 0 | 19 | 0 | 319 | 3 | +| 22.5% | 0 | 0 | 19 | 0 | 326 | 3 | +| 23.0% | 0 | 0 | 20 | 0 | 334 | 4 | +| 23.5% | 0 | 0 | 20 | 0 | 342 | 4 | +| 24.0% | 0 | 0 | 21 | 0 | 349 | 4 | +| 24.5% | 0 | 0 | 22 | 0 | 357 | 4 | +| 25.0% | 0 | 0 | 22 | 0 | 365 | 4 | +| 25.5% | 0 | 0 | 23 | 0 | 372 | 4 | +| 26.0% | 0 | 0 | 23 | 0 | 380 | 5 | +| 26.5% | 0 | 0 | 24 | 0 | 388 | 5 | +| 27.0% | 0 | 0 | 24 | 0 | 396 | 5 | +| 27.5% | 0 | 0 | 25 | 0 | 403 | 5 | +| 28.0% | 0 | 0 | 26 | 0 | 411 | 5 | +| 28.5% | 0 | 0 | 26 | 0 | 419 | 5 | +| 29.0% | 0 | 0 | 27 | 0 | 426 | 5 | +| 29.5% | 1 | 0 | 27 | 0 | 434 | 6 | +| 30.0% | 1 | 0 | 28 | 0 | 442 | 6 | +| 30.5% | 1 | 0 | 28 | 0 | 450 | 6 | +| 31.0% | 1 | 0 | 29 | 0 | 457 | 6 | +| 31.5% | 1 | 0 | 29 | 0 | 465 | 6 | +| 32.0% | 1 | 0 | 30 | 0 | 473 | 6 | +| 32.5% | 1 | 0 | 31 | 0 | 481 | 7 | +| 33.0% | 1 | 0 | 31 | 0 | 488 | 7 | +| 33.5% | 1 | 0 | 32 | 0 | 496 | 7 | +| 34.0% | 1 | 0 | 32 | 0 | 504 | 7 | +| 34.5% | 1 | 0 | 33 | 0 | 512 | 7 | +| 35.0% | 1 | 0 | 34 | 0 | 519 | 7 | +| 35.5% | 1 | 0 | 34 | 0 | 527 | 8 | +| 36.0% | 1 | 0 | 35 | 0 | 535 | 8 | +| 36.5% | 1 | 0 | 35 | 0 | 543 | 8 | +| 37.0% | 1 | 0 | 36 | 0 | 550 | 8 | +| 37.5% | 1 | 0 | 36 | 0 | 558 | 8 | +| 38.0% | 1 | 0 | 37 | 0 | 566 | 8 | +| 38.5% | 1 | 0 | 38 | 0 | 574 | 8 | + +**Table C.4/M.2100 – BIS performance limits for tertiary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 39.0% | 1 | 0 | 38 | 0 | 582 | 9 | +| 39.5% | 2 | 0 | 39 | 0 | 589 | 9 | +| 40.0% | 2 | 0 | 39 | 0 | 597 | 9 | +| 40.5% | 2 | 0 | 40 | 0 | 605 | 9 | +| 41.0% | 2 | 0 | 40 | 0 | 613 | 9 | +| 41.5% | 2 | 0 | 41 | 0 | 620 | 9 | +| 42.0% | 2 | 0 | 42 | 0 | 628 | 10 | +| 42.5% | 2 | 0 | 42 | 0 | 636 | 10 | +| 43.0% | 2 | 0 | 43 | 0 | 644 | 10 | +| 43.5% | 2 | 0 | 43 | 0 | 652 | 10 | +| 44.0% | 2 | 0 | 44 | 0 | 659 | 10 | +| 44.5% | 2 | 0 | 45 | 0 | 667 | 10 | +| 45.0% | 2 | 0 | 45 | 0 | 675 | 11 | +| 45.5% | 2 | 0 | 46 | 0 | 683 | 11 | +| 46.0% | 2 | 0 | 46 | 0 | 691 | 11 | +| 46.5% | 2 | 0 | 47 | 0 | 698 | 11 | +| 47.0% | 2 | 0 | 48 | 0 | 706 | 11 | +| 47.5% | 2 | 0 | 48 | 0 | 714 | 11 | +| 48.0% | 2 | 0 | 49 | 0 | 722 | 12 | +| 48.5% | 2 | 0 | 49 | 0 | 730 | 12 | +| 49.0% | 3 | 0 | 50 | 0 | 737 | 12 | +| 49.5% | 3 | 0 | 50 | 0 | 745 | 12 | +| 50.0% | 3 | 0 | 51 | 0 | 753 | 12 | +| 50.5% | 3 | 0 | 52 | 0 | 761 | 12 | +| 51.0% | 3 | 0 | 52 | 0 | 769 | 13 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 51.5% | 3 | 0 | 53 | 0 | 777 | 13 | +| 52.0% | 3 | 0 | 53 | 0 | 784 | 13 | +| 52.5% | 3 | 0 | 54 | 0 | 792 | 13 | +| 53.0% | 3 | 0 | 55 | 0 | 800 | 13 | +| 53.5% | 3 | 0 | 55 | 0 | 808 | 13 | +| 54.0% | 3 | 0 | 56 | 0 | 816 | 14 | +| 54.5% | 3 | 0 | 56 | 0 | 823 | 14 | +| 55.0% | 3 | 0 | 57 | 0 | 831 | 14 | +| 55.5% | 3 | 0 | 58 | 0 | 839 | 14 | +| 56.0% | 3 | 0 | 58 | 0 | 847 | 14 | +| 56.5% | 3 | 0 | 59 | 0 | 855 | 15 | +| 57.0% | 3 | 0 | 59 | 0 | 863 | 15 | +| 57.5% | 3 | 0 | 60 | 0 | 870 | 15 | +| 58.0% | 4 | 0 | 61 | 0 | 878 | 15 | +| 58.5% | 4 | 0 | 61 | 0 | 886 | 15 | +| 59.0% | 4 | 0 | 62 | 0 | 894 | 15 | +| 59.5% | 4 | 0 | 62 | 0 | 902 | 16 | +| 60.0% | 4 | 0 | 63 | 0 | 910 | 16 | +| 60.5% | 4 | 0 | 64 | 0 | 917 | 16 | +| 61.0% | 4 | 0 | 64 | 0 | 925 | 16 | +| 61.5% | 4 | 0 | 65 | 0 | 933 | 16 | +| 62.0% | 4 | 0 | 65 | 0 | 941 | 16 | +| 62.5% | 4 | 0 | 66 | 0 | 949 | 17 | +| 63.0% | 4 | 0 | 67 | 0 | 957 | 17 | + +**Table C.5/M.2100 – BIS performance limits for quaternary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 0.2% | 0 | 0 | 0 | 0 | 2 | 0 | +| 0.5% | 0 | 0 | 0 | 0 | 9 | 0 | +| 1.0% | 0 | 0 | 0 | 0 | 23 | 0 | +| 1.5% | 0 | 0 | 0 | 0 | 37 | 0 | +| 2.0% | 0 | 0 | 1 | 0 | 52 | 0 | +| 2.5% | 0 | 0 | 2 | 0 | 68 | 0 | +| 3.0% | 0 | 0 | 3 | 0 | 83 | 0 | +| 3.5% | 0 | 0 | 4 | 0 | 99 | 0 | +| 4.0% | 0 | 0 | 5 | 0 | 115 | 0 | +| 4.5% | 0 | 0 | 6 | 0 | 131 | 0 | +| 5.0% | 0 | 0 | 7 | 0 | 147 | 0 | +| 5.5% | 0 | 0 | 8 | 0 | 163 | 0 | +| 6.0% | 0 | 0 | 9 | 0 | 179 | 0 | +| 6.5% | 0 | 0 | 10 | 0 | 195 | 0 | +| 7.0% | 0 | 0 | 11 | 0 | 211 | 0 | +| 7.5% | 0 | 0 | 12 | 0 | 227 | 0 | +| 8.0% | 0 | 0 | 13 | 0 | 243 | 0 | +| 8.5% | 0 | 0 | 15 | 0 | 259 | 0 | +| 9.0% | 0 | 0 | 16 | 0 | 276 | 0 | +| 9.5% | 0 | 0 | 17 | 0 | 292 | 0 | +| 10.0% | 0 | 0 | 18 | 0 | 308 | 0 | +| 10.5% | 0 | 0 | 19 | 0 | 325 | 0 | +| 11.0% | 0 | 0 | 20 | 0 | 341 | 0 | +| 11.5% | 0 | 0 | 22 | 0 | 358 | 1 | +| 12.0% | 0 | 0 | 23 | 0 | 374 | 1 | +| 12.5% | 0 | 0 | 24 | 0 | 390 | 1 | +| 13.0% | 0 | 0 | 25 | 0 | 407 | 1 | +| 13.5% | 0 | 0 | 26 | 0 | 423 | 1 | +| 14.0% | 1 | 0 | 28 | 0 | 440 | 1 | +| 14.5% | 1 | 0 | 29 | 0 | 456 | 1 | +| 15.0% | 1 | 0 | 30 | 0 | 473 | 1 | +| 15.5% | 1 | 0 | 31 | 0 | 489 | 2 | +| 16.0% | 1 | 0 | 33 | 0 | 506 | 2 | +| 16.5% | 1 | 0 | 34 | 0 | 522 | 2 | +| 17.0% | 1 | 0 | 35 | 0 | 539 | 2 | +| 17.5% | 1 | 0 | 36 | 0 | 556 | 2 | +| 18.0% | 1 | 0 | 37 | 0 | 572 | 2 | +| 18.5% | 1 | 0 | 39 | 0 | 589 | 2 | +| 19.0% | 2 | 0 | 40 | 0 | 605 | 2 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 19.5% | 2 | 0 | 41 | 0 | 622 | 3 | +| 20.0% | 2 | 0 | 42 | 0 | 639 | 3 | +| 20.5% | 2 | 0 | 44 | 0 | 655 | 3 | +| 21.0% | 2 | 0 | 45 | 0 | 672 | 3 | +| 21.5% | 2 | 0 | 46 | 0 | 689 | 3 | +| 22.0% | 2 | 0 | 47 | 0 | 705 | 3 | +| 22.5% | 2 | 0 | 49 | 0 | 722 | 3 | +| 23.0% | 3 | 0 | 50 | 0 | 738 | 4 | +| 23.5% | 3 | 0 | 51 | 0 | 755 | 4 | +| 24.0% | 3 | 0 | 52 | 0 | 772 | 4 | +| 24.5% | 3 | 0 | 54 | 0 | 789 | 4 | +| 25.0% | 3 | 0 | 55 | 0 | 805 | 4 | +| 25.5% | 3 | 0 | 56 | 0 | 822 | 4 | +| 26.0% | 3 | 0 | 58 | 0 | 839 | 5 | +| 26.5% | 3 | 0 | 59 | 0 | 855 | 5 | +| 27.0% | 3 | 0 | 60 | 0 | 872 | 5 | +| 27.5% | 4 | 0 | 61 | 0 | 889 | 5 | +| 28.0% | 4 | 0 | 63 | 0 | 905 | 5 | +| 28.5% | 4 | 0 | 64 | 0 | 922 | 5 | +| 29.0% | 4 | 0 | 65 | 0 | 939 | 5 | +| 29.5% | 4 | 0 | 67 | 0 | 956 | 6 | +| 30.0% | 4 | 0 | 68 | 0 | 972 | 6 | +| 30.5% | 4 | 0 | 69 | 0 | 989 | 6 | +| 31.0% | 4 | 0 | 70 | 0 | 1006 | 6 | +| 31.5% | 5 | 0 | 72 | 0 | 1023 | 6 | +| 32.0% | 5 | 0 | 73 | 0 | 1039 | 6 | +| 32.5% | 5 | 0 | 74 | 0 | 1056 | 7 | +| 33.0% | 5 | 0 | 76 | 0 | 1073 | 7 | +| 33.5% | 5 | 0 | 77 | 0 | 1090 | 7 | +| 34.0% | 5 | 0 | 78 | 0 | 1106 | 7 | +| 34.5% | 5 | 0 | 79 | 0 | 1123 | 7 | +| 35.0% | 6 | 0 | 81 | 0 | 1140 | 7 | +| 35.5% | 6 | 0 | 82 | 0 | 1157 | 8 | +| 36.0% | 6 | 0 | 83 | 0 | 1174 | 8 | +| 36.5% | 6 | 0 | 85 | 0 | 1190 | 8 | +| 37.0% | 6 | 0 | 86 | 0 | 1207 | 8 | +| 37.5% | 6 | 0 | 87 | 0 | 1224 | 8 | +| 38.0% | 6 | 0 | 89 | 0 | 1241 | 8 | +| 38.5% | 6 | 0 | 90 | 0 | 1258 | 8 | + +**Table C.5/M.2100 – BIS performance limits for quaternary level** + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 39.0% | 7 | 0 | 91 | 0 | 1274 | 9 | +| 39.5% | 7 | 0 | 92 | 0 | 1291 | 9 | +| 40.0% | 7 | 0 | 94 | 0 | 1308 | 9 | +| 40.5% | 7 | 0 | 95 | 0 | 1325 | 9 | +| 41.0% | 7 | 0 | 96 | 0 | 1342 | 9 | +| 41.5% | 7 | 0 | 98 | 0 | 1358 | 9 | +| 42.0% | 7 | 0 | 99 | 0 | 1375 | 10 | +| 42.5% | 7 | 0 | 100 | 0 | 1392 | 10 | +| 43.0% | 8 | 0 | 102 | 0 | 1409 | 10 | +| 43.5% | 8 | 0 | 103 | 0 | 1426 | 10 | +| 44.0% | 8 | 0 | 104 | 0 | 1443 | 10 | +| 44.5% | 8 | 0 | 106 | 0 | 1459 | 10 | +| 45.0% | 8 | 0 | 107 | 0 | 1476 | 11 | +| 45.5% | 8 | 0 | 108 | 0 | 1493 | 11 | +| 46.0% | 8 | 0 | 109 | 0 | 1510 | 11 | +| 46.5% | 9 | 0 | 111 | 0 | 1527 | 11 | +| 47.0% | 9 | 0 | 112 | 0 | 1544 | 11 | +| 47.5% | 9 | 0 | 113 | 0 | 1561 | 11 | +| 48.0% | 9 | 0 | 115 | 0 | 1577 | 12 | +| 48.5% | 9 | 0 | 116 | 0 | 1594 | 12 | +| 49.0% | 9 | 0 | 117 | 0 | 1611 | 12 | +| 49.5% | 9 | 0 | 119 | 0 | 1628 | 12 | +| 50.0% | 10 | 0 | 120 | 0 | 1645 | 12 | +| 50.5% | 10 | 0 | 121 | 0 | 1662 | 12 | +| 51.0% | 10 | 0 | 123 | 0 | 1679 | 13 | + +| | 15mn | | 2 hours | | 24 hours | | +|-------------|------|-----|---------|-----|----------|-----| +| | ES | SES | ES | SES | ES | SES | +| Path Alloc. | S15 | S15 | S2 | S2 | S24 | S24 | +| 51.5% | 10 | 0 | 124 | 0 | 1695 | 13 | +| 52.0% | 10 | 0 | 125 | 0 | 1712 | 13 | +| 52.5% | 10 | 0 | 127 | 0 | 1729 | 13 | +| 53.0% | 10 | 0 | 128 | 0 | 1746 | 13 | +| 53.5% | 10 | 0 | 129 | 0 | 1763 | 13 | +| 54.0% | 11 | 0 | 131 | 0 | 1780 | 14 | +| 54.5% | 11 | 0 | 132 | 0 | 1797 | 14 | +| 55.0% | 11 | 0 | 133 | 0 | 1814 | 14 | +| 55.5% | 11 | 0 | 135 | 0 | 1830 | 14 | +| 56.0% | 11 | 0 | 136 | 0 | 1847 | 14 | +| 56.5% | 11 | 0 | 137 | 0 | 1864 | 15 | +| 57.0% | 11 | 0 | 139 | 0 | 1881 | 15 | +| 57.5% | 12 | 0 | 140 | 0 | 1898 | 15 | +| 58.0% | 12 | 0 | 141 | 0 | 1915 | 15 | +| 58.5% | 12 | 0 | 143 | 0 | 1932 | 15 | +| 59.0% | 12 | 0 | 144 | 0 | 1949 | 15 | +| 59.5% | 12 | 0 | 145 | 0 | 1966 | 16 | +| 60.0% | 12 | 0 | 147 | 0 | 1983 | 16 | +| 60.5% | 12 | 0 | 148 | 0 | 1999 | 16 | +| 61.0% | 13 | 0 | 149 | 0 | 2016 | 16 | +| 61.5% | 13 | 0 | 151 | 0 | 2033 | 16 | +| 62.0% | 13 | 0 | 152 | 0 | 2050 | 16 | +| 62.5% | 13 | 0 | 153 | 0 | 2067 | 17 | +| 63.0% | 13 | 0 | 155 | 0 | 2084 | 17 | + +# Annex D + +## Default unacceptable performance level thresholds for international digital paths + +Tables D.1 and D.2 provide the default unacceptable performance level set and reset thresholds for international digital paths. + +**Table D.1/M.2100 – Default unacceptable performance level +set thresholds for international digital paths** + +| Allocation
(%) | Primary level | | Secondary level | | Tertiary level | | Quaternary level | | +|-------------------|---------------|-----|-----------------|-----|----------------|-----|------------------|-----| +| | ES | SES | ES | SES | ES | SES | ES | SES | +| 0.2-34 | 80 | 10 | 80 | 10 | 100 | 10 | 120 | 10 | +| 35-63 | 120 | 15 | 120 | 15 | 150 | 15 | 180 | 15 | + +**Table D.2/M.2100 – Default unacceptable performance level +reset thresholds for international digital paths** + +| Allocation
(%) | Primary level | | Secondary level | | Tertiary level | | Quaternary level | | +|-------------------|---------------|-----|-----------------|-----|----------------|-----|------------------|-----| +| | ES | SES | ES | SES | ES | SES | ES | SES | +| 0.2-34 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | +| 35-63 | 2 | 0 | 2 | 0 | 3 | 0 | 4 | 0 | + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.2101-200306-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg b/marked/M/T-REC-M.2101-200306-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dd009ce3bae14710560bcdf01c3091623790593 --- /dev/null +++ b/marked/M/T-REC-M.2101-200306-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d83643b859805d0ba4d611be7554649859e9e9f3d0da6f3cb4792b755eb25de3 +size 94207 diff --git a/marked/M/T-REC-M.2101-200306-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.2101-200306-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/M/T-REC-M.2101-200306-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/M/T-REC-M.2101-200306-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.2101-200306-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37f16d6d08fb6422c5acdfb399d17053776a5446 --- /dev/null +++ b/marked/M/T-REC-M.2101-200306-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c1ae06bed6b10fb746467466419d3da5f17f80fe75ca559fbcb7d6aeb6a320 +size 31611 diff --git a/marked/M/T-REC-M.2101-200306-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/M/T-REC-M.2101-200306-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3865d006f33ad8216e8692fae61cc7f8d203c902 --- /dev/null +++ b/marked/M/T-REC-M.2101-200306-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d858751cde1d737f58aee5cb17681fac736d5b161b6400d76bdcab63f71630ba +size 8652 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cca38cbf2af19ae3868a81887097153096404bf --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55d485ba2c46ecf64670c4814eeb5c51d1abd96c8dbbf70c91bd4e9f4048385b +size 150441 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99b360fbf10139585a7319ed521f073fb9bd0ee3 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b670ac5fdb04a6dffacac28c4d2daf628e85e5b937bec4c74d536b453b76645a +size 40865 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..891631c5e7bd45f0fa8abb3d22f7eeb2af930e56 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deddd780f31e658a05c4d6cd50b2bfc38ece5c03e80bd3ea042a545bcab037a8 +size 38743 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0ec5c2ca7efa54d605b194ec7930904bb53f3fe --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:986b214aa36ff24ac94217f22a0c3eb569acf6439e70358aa90201922c5dd61b +size 42661 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbf2fd224abcb680fcf126b57ee681cf4cfd38c1 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae9bcfb33930986e465d7a6643c172dcddc79f4cfd4a414a19649ccd456df588 +size 44891 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..072ba72c60e40692aa366a5af912bcbf1fecc6b1 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7efc91024d7fc75029f65fcee3b1db32f68badbfb0776708879662ccdcc1b126 +size 41039 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2eb1fc62bf72514326cfcb59a9112fab26a4582 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d566af925f72767e5fa3c96f16c39039ef2864aa6d95eb0e6c766aa9d96d77fe +size 45299 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aeb4861ceb5e942926bf7d29f2446881c440035 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:875f16ad7add5a58e4889c5bccf4b0ed0bb1d03e316ff1b2afad3a7854ac3d44 +size 38034 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65b37d991801b603bf141d775887c7204fa27100 --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1314fb6bb998773e366c26c8a2a0be092856facaa43181f589ad185f0d5e94bc +size 45453 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3951e81f3477cdf64c0c7a29d9031b799a3c0c3f --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ba9dec9238e67b05c7f929d2dedec164867a6b2099985d34e32cd6ef614f746 +size 109026 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15c9635918fce272df6d3204a020630f38e404cf --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfbb4b1eba6a4349ccf2c8bae81dc6a7599e5be4440b329d0a3f9c4a8731775d +size 135966 diff --git a/marked/M/T-REC-M.2102-200002-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/M/T-REC-M.2102-200002-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63351974fc4e5d5dc8dcbf873ca0bced3c2d82bc --- /dev/null +++ b/marked/M/T-REC-M.2102-200002-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f6d7656d75bce661015908ccd199bddeb971ea0f44a60b2362a7acac1d69d9e +size 30886 diff --git a/marked/M/T-REC-M.2120-200207-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/M/T-REC-M.2120-200207-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70f061f1ae8ec19c31551539d7f1d99dc2ac9fcf --- /dev/null +++ b/marked/M/T-REC-M.2120-200207-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f0d6176dccd5fe4afd8ad0c3cb2d81dc146f960fa450013dbe7c47931314ce0 +size 86018 diff --git a/marked/M/T-REC-M.2120-200207-I_PDF-E/raw.md b/marked/M/T-REC-M.2120-200207-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a8f07a0e7d04f92d421c35db4fbc6cdd56fe3ac1 --- /dev/null +++ b/marked/M/T-REC-M.2120-200207-I_PDF-E/raw.md @@ -0,0 +1,513 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2120** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/2002) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +--- + +**International multi-operator paths, sections and +transmission systems fault detection and +localization procedures** + +ITU-T Recommendation M.2120 + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.2120** + +# **International multi-operator paths, sections and transmission systems fault detection and localization procedures** + +# **Summary** + +This Recommendation provides procedures for fault detection and localization with and without in-service monitoring for international multi-operator paths, sections, and transmission systems. Filtering and thresholding of performance information are described for reporting to the TMN. Returning into service and long-term trend analysis are considered. These procedures are applicable whatever the technology used. + +## **Source** + +ITU-T Recommendation M.2120 was revised by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 14 July 2002. + +## **Keywords** + +Fault detection, filtering, in-service monitoring, localization, long-term trend analysis, path, returning into service, section, thresholding, TMN, transmission system. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|------------------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Maintenance techniques with ISM ..... | 2 | +| 5.1 | Relationship with ITU-T Rec. M.20..... | 2 | +| 5.2 | Fault localization information ..... | 3 | +| 5.2.1 | Performance information..... | 3 | +| 5.2.2 | Performance level information ..... | 4 | +| 5.2.3 | Performance primitives information..... | 4 | +| 5.2.4 | Supplementary information ..... | 4 | +| 5.3 | Performance filtering, thresholding, reporting and historical storage ..... | 4 | +| 5.3.1 | Events ..... | 4 | +| 5.3.2 | Transmission states..... | 4 | +| 5.3.3 | Threshold reports..... | 4 | +| 5.3.4 | Filter types used for evaluating transmission states and threshold reports .... | 5 | +| 5.3.5 | Evaluation of transmission states and threshold reports..... | 5 | +| 5.3.6 | Performance history storage in network elements..... | 7 | +| 5.3.7 | Performance history reporting from network elements..... | 7 | +| 5.3.8 | Accuracy and resolution ..... | 8 | +| 5.3.9 | Single-ended monitoring capability ..... | 8 | +| 6 | Fault localization procedures on transmission systems and multiplex sections ..... | 8 | +| 6.1 | Fault localization in a pre-ISM environment..... | 8 | +| 6.2 | Fault localization in an ISM environment ..... | 8 | +| 7 | Fault localization procedures on paths ..... | 9 | +| 7.1 | Fault localization in a pre-ISM environment or using OOS means ..... | 9 | +| 7.2 | Fault localization in an ISM environment ..... | 10 | +| 8 | Returning a maintenance entity into service..... | 10 | +| 9 | Trend analysis and signatures..... | 11 | + + + +# International multi-operator paths, sections and transmission systems fault detection and localization procedures + +# 1 Scope + +The TMN, as described in ITU-T Rec. M.3010 [5], is being progressively implemented by many operators. The maintenance procedures described here cover both the case where full In-Service Monitoring (ISM) is available (as in the TMN) and the case where no ISM or partial ISM is available. The latter case is referred to as pre-ISM. Information processing will be more integrated or less integrated depending on the TMN's degree of development. + +ISM should be understood as a situation where a dedicated full-time performance monitor exists for a path and/or transmission system. This facilitates performance data collection and storage, scheduled periodic reporting of current and historic data, exception reporting, and setting of thresholds. A pre-ISM situation exists if any condition does not meet the definition of ISM (e.g. existence of time-shared monitoring, no monitoring at all). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.784 (1999), *Synchronous digital hierarchy (SDH) management.* +- [2] ITU-T Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks.* +- [3] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions.* +- [4] ITU-T Recommendation M.2110 (2002), *Bringing into service international multi-operator paths, sections and transmission systems.* +- [5] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network.* +- [6] ITU-T Recommendation O.150 (1996), *General requirements for instrumentation for performance measurements on digital transmission equipment.* +- [7] ITU-T Recommendation O.151 (1992), *Error performance measuring equipment operating at the primary rate and above.* +- [8] ITU-T Recommendation O.161 (1984), *In-service code violation monitors for digital systems.* +- [9] ITU-T Recommendation O.162 (1992), *Equipment to perform in-service monitoring on 2048, 8448, 34 368 and 139 264 kbit/s signals.* +- [10] ITU-T Recommendation O.163 (1988), *Equipment to perform in-service monitoring on 1544 kbit/s signals.* +- [11] ITU-T Recommendation O.181 (2002), *Equipment to assess error performance on STM-N interfaces.* + +# **3 Terms and definitions** + +General terms and definitions relating to this Recommendation are provided in ITU-T Rec. M.60 [3]. + +# **4 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-----|--------------------------------------| +| BBE | Background Block Error | +| BIS | Bringing-Into-Service | +| CRC | Cyclic Redundancy Check | +| DPL | Degraded Performance Limit | +| ES | Errored Second | +| ISM | In-Service Monitoring | +| ME | Maintenance Entity | +| NE | Network Element | +| OOS | Out-Of-Service | +| RTR | Reset Threshold Report | +| SDH | Synchronous Digital Hierarchy | +| SES | Severely Errored Second | +| STM | Synchronous Transport Module | +| TMN | Telecommunication Management Network | +| TR | Threshold Report | +| UPL | Unacceptable Performance Limit | +| VC | Virtual Channel | + +# **5 Maintenance techniques with ISM** + +## **5.1 Relationship with ITU-T Rec. M.20** + +ITU-T Rec. M.20 [2], *Maintenance philosophy for telecommunications networks*, provides guidance for maintenance operations. This clause expands on the principles given in ITU-T Rec. M.20 [2] with specific application to transmission systems and ISM. Figure 1 includes abridged versions of Figures 7/M.20 [2] and 9/M.20 [2]. + +![Flowchart of the process of elaboration of information used for maintenance. The diagram shows inputs from SEF, MEF, and Other sources leading to various processing steps (Supervision process for anomalies, Defect supervision process, Performance evaluation, Level of performance, Alarm information process) which then lead to the final Maintenance process. Some steps are grouped into boxes labeled Figure 7/M.20 [2] and Figure 9/M.20 [2].](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph TD + subgraph Figure7 [Figure 7/M.20 [2]] + SEF((SEF)) --> SPA(Supervision process for anomalies) + MEF((MEF)) --> SPA + end + OS((Other sources)) --> SI[Supplementary information] + SPA --> DSP(Defect supervision process) + SPA --> PE(Performance evaluation) + SPA --> LOP[Level of performance] + DSP --> SI + PE --> PI[Performance information] + LOP --> AIP(Alarm information process) + AIP --> MP((Maintenance process)) + PI --> MP + PP[Performance primitives] --> MP + SI --> MP + style Figure7 fill:none,stroke:none + style Figure9 fill:none,stroke:none + subgraph Figure9 [Figure 9/M.20 [2]] + LOP + AIP + end + style OS fill:none,stroke:none + style SI fill:none,stroke:none + style PI fill:none,stroke:none + style PP fill:none,stroke:none + style MP fill:none,stroke:none + style SEF fill:none,stroke:none + style MEF fill:none,stroke:none + style SPA fill:none,stroke:none + style DSP fill:none,stroke:none + style PE fill:none,stroke:none + style LOP fill:none,stroke:none + style AIP fill:none,stroke:none + +``` + +M.2120\_F01 + +Flowchart of the process of elaboration of information used for maintenance. The diagram shows inputs from SEF, MEF, and Other sources leading to various processing steps (Supervision process for anomalies, Defect supervision process, Performance evaluation, Level of performance, Alarm information process) which then lead to the final Maintenance process. Some steps are grouped into boxes labeled Figure 7/M.20 [2] and Figure 9/M.20 [2]. + +**Figure 1/M.2120 – Process of elaboration of information used for maintenance** + +## 5.2 Fault localization information + +Once an alarm indication is received, the fault localization process must begin. For this purpose several categories of information are required: + +- performance information; +- performance level information; +- performance primitives; +- supplementary information. + +### 5.2.1 Performance information + +Performance information is in terms of error performance events and is used to calculate the performance levels. Normally it will be time-stamped and stored for correlation analysis and for long-term trend analysis (see clause 9). Error performance events, and the set of them that applies to maintenance and their limits, are defined in specific technology Recommendations. + +### **5.2.2 Performance level information** + +Performance level information (unacceptable performance limit (UPL), degraded performance limit (DPL), normal performance level) is derived from performance information (or the equivalent performance primitives). It is the information which will start the alarm information process, as shown in Figure 1, when a performance limit is reached. The performance limits are also referred to as alarm thresholds. The alarm generated (i.e. prompt maintenance alarm, deferred maintenance alarm or maintenance event information) determines the urgency of subsequent actions. + +### **5.2.3 Performance primitives information** + +Performance primitives are the basic information in the form of anomalies and defects used to determine the event counts defined in the specific technology Recommendations. Performance primitives depend on the type of entity being monitored. + +### **5.2.4 Supplementary information** + +Supplementary information is information other than that obtained from monitoring. It includes derived information such as the identification of a faulty maintenance entity (ME) or subentity, or information from other MEs. It also includes administrative information such as the constitution of a path. Supplementary information also includes such information as direct transmission restoration (protection switching) counts. + +## **5.3 Performance filtering, thresholding, reporting and historical storage** + +The functions described in this clause can be performed inside or outside the network element (NE). + +### **5.3.1 Events** + +The evaluation of error performance and availability performance is based on the processing of the performance events. The derivation of these events from standardized signal information is given in specific technology Recommendations. + +### **5.3.2 Transmission states** + +A path can be in one of two transmission states: + +- unavailable state; +- available state. + +The transmission state is determined from filtered SES/non-SES data (see 5.3.4 and 5.3.5). + +### **5.3.3 Threshold reports** + +A Threshold Report (TR) is an unsolicited error performance report from a ME with respect to either a 15-minute or 24-hour evaluation period. TRs can only occur when the concerned direction is in the available state. Several TRs are defined based on filtered error performance events. + +#### **5.3.3.1 TRs based on a 15-minute evaluation period** + +There are one TR15 and one Reset TR15 (RTR15) for each performance event. TR15s occur as soon as the 15-minute threshold is reached or exceeded. RTR15s optionally occur at the end of a 15-minute period in which the count is less than or equal to the "reset" threshold and there has not been any unavailable time during that period. A RTR15 can only occur subsequent to a 15-minute period containing a TR15. Clause 5.3.5.3 gives precise details. + +#### **5.3.3.2 TRs based on a 24-hour evaluation period** + +There is one TR24 for each performance event. TR24s occur as soon as the 24-hour threshold is reached or exceeded. Clause 5.3.5.4 gives precise details. There is no RTR24 for the 24-hour + +evaluation period defined in this Recommendation, but RTR24 may be implemented in some equipment. + +### **5.3.4 Filter types used for evaluating transmission states and threshold reports** + +Care needs to be taken with the error performance event counters and the generation of TRs during changes in transmission states. Guidance on this issue is given in 5.3.5.5. + +#### **5.3.4.1 Unavailable state and available state filters** + +The unavailable state filter is a 10-second rectangular sliding window, with 1-second granularity of slide. The available state filter is also a 10-second rectangular sliding window, with 1-second granularity of slide. + +#### **5.3.4.2 TR15 and RTR15 filters** + +The TR15 and RTR15 filters are 15-minute rectangular fixed windows. The start and end time for the 15-minute rectangular fixed windows are the same for all performance events and must occur on the hour and at 15, 30, and 45 minutes after the hour. + +#### **5.3.4.3 TR24 filter** + +The TR24 filter is a 24-hour rectangular fixed window. The start and end time for the 24-hour rectangular fixed windows are the same for all performance events and must occur on a 15-minute window boundary. + +### **5.3.5 Evaluation of transmission states and threshold reports** + +#### **5.3.5.1 Evaluation of the unavailable and available states** + +The unavailable state is detected at the end of 10 consecutive SESs. Upon detection, a date/time-stamped unavailable state report should be sent to the performance management centre. The time/date stamp should relate to the first of the 10 consecutive SESs. + +The termination of the unavailable state (i.e. reentry to the available state) is detected at the end of 10 consecutive non-SESs. Upon detection, a date/time-stamped termination of unavailability report should be sent to the performance management centre. The date/time-stamp should relate to the first of the 10 consecutive non-SESs. + +The unavailable seconds count and the unavailability event count should be calculated either within the network element or within a performance management system. + +#### **5.3.5.2 Evaluation of performance levels** + +Three performance levels are defined: + +- The unacceptable performance limit (UPL), which is reached when there is a TR15 for at least one performance event or when there is an unavailable period. +- The degraded performance limit (DPL), which is reached when there is a TR24 for at least one performance event. +- The normal performance level, which corresponds to not being in UPL or DPL state. + +#### **5.3.5.3 Evaluation of TR15** + +The performance events are counted separately, second by second, over each 15-minute rectangular fixed window period. A threshold can be crossed at any second within the 15-minute rectangular fixed window. As soon as a threshold is crossed for one performance event, a TR15 as appropriate should be sent to the performance management centre together with a date/time-stamp. Moreover, performance events should continue to be counted to the end of the current 15-minute period, at which time the current performance event counts are stored in the historical registers and the current performance event registers are reset to zero. + +There are two methods for evaluation of TR15: the Transient Condition Method and the optional Standing Condition Method. + +##### 5.3.5.3.1 Transient Condition Method + +The Transient Condition Method treats each 15-minute measurement period separately. During each period, the value of the event counter is compared to the set threshold on a second-by-second basis and if the count is equal to or greater than the threshold, a TR15 is generated. For this method there is no reset threshold or RTR15 defined. + +##### 5.3.5.3.2 Standing Condition Method + +The Standing Condition Method raises a standing condition when the set threshold is crossed and clears the standing condition when the count at the end of a subsequent period is below or equal to the reset threshold, provided that there was no unavailable time during that period. For the Standing Condition Method, the ME can be in one of two states: acceptable or unacceptable. + +If the ME is in the acceptable state, the value of the event counter is compared to the set threshold on a second-by-second basis. If the event count is equal to or greater than the threshold, a TR15 is generated and the state changes to unacceptable. + +If the ME is in the unacceptable state, the value of the counter is compared to the reset threshold at the end of each period. If the count is less than or equal to the reset threshold, and there has been no unavailable time during that period, a RTR15 is generated and the state changes back to acceptable. If there has been unavailable time during the period, the ME remains in the unacceptable state and no RTR15 is generated at the end of the period. + +If the Standing Condition Method is used, then no more than one TR15 should be generated per direction of transmission until there has been an RTR15. The generation of a RTR15 is only permitted subsequent to its respective TR15 and, once generated, re-enables the TR15 capability for the relevant event counter and direction of transmission. + +##### 5.3.5.3.3 Threshold criteria + +There are several TR15s, one for each of the performance event counters. There are several RTR15s (for the Standing Condition Method only), one for each of the performance event counters. The threshold values for TR15s and RTR15s should be programmable for each Termination Point over the following ranges with default values: + +- 0 to 900 for all events with 1 second granularity e.g. ES and SES events; +- 0 to $2^{16} - 1$ for the BBE event in the case of VC-11 up to VC-4-16c paths (SDH only); +- 0 to $2^{24} - 1$ for the BBE event in the case of STM-1 up to STM-16 (SDH only, see Note). + +The minimum value for TR15 is 1 and the minimum value for RTR15 is 0. Default threshold values for TR15 and RTR15 are given in the specific technology Recommendations. + +NOTE – It is recognized that some NEs will be incapable of accommodating a threshold greater than $2^{16} - 1$ . + +#### 5.3.5.4 Evaluation of TR24 + +The performance events are counted separately over each 24-hour period. There are several TR24s, one for each performance event. The threshold values should be programmable for each Termination Point over the following ranges with default values: + +- 1 to 86 400 for all events with 1 second granularity e.g. ES and SES events (see Note 2); +- 1 to $2^{32} - 1$ for the BBE event in the case of VC-11 up to VC-4-16c paths (SDH only, see Notes 1 and 2); +- 1 to $2^{40} - 1$ for the BBE event in the case of STM-1 up to STM-16 (SDH only, see Notes 1 and 2); + +The cases of VC-4-64c and STM-64 are for further study. + +NOTE 1 – The maximum values for BBE events for VCs and STM-Ns are smaller than the maximum number of BBEs that could theoretically be detected in a 24-hour period. + +NOTE 2 – It is recognized that some NEs will be incapable of accommodating a threshold greater than $2^{16} - 1$ . + +The NE shall recognize a 24-hour threshold crossing within 15 minutes of its occurrence. The threshold crossing shall be given the date/time-stamp of the moment of recognition. A TR24 as appropriate should be sent to the performance management centre with the date/time-stamp. Moreover, performance events should continue to be counted to the end of the current 24-hour period, at which time the performance events counts are stored in the historical registers and the current performance events registers are reset to zero. + +For the evaluation of TR24, only the Transient Condition Method applies. There is no reset threshold or RTR defined for the 24-hour evaluation period. No more than one TR24 should be generated per event counter and per direction of transmission during any 24-hour rectangular fixed window. + +#### **5.3.5.5 Threshold report evaluation during transmission state changes** + +Care should be taken to ensure that threshold reports are correctly generated and performance events counters are correctly processed during changes in the transmission state. This implies that all threshold reports should be delayed by 10 seconds. + +### **5.3.6 Performance history storage in network elements** + +Requirements for ME performance history storage are: + +- Event counts to be stored are defined in the specific technology Recommendations. +- Where the unavailable second count and unavailable event count have been calculated by the NE, the NE must store these counts in addition to the ES, BBE and SES counts. +- There should be a current 15-minute register (which can also facilitate the TR15/RTR15 filter) plus a further $N$ 15-minute history registers for each event in each ME. The $N$ 15-minute history registers are used as a stack, i.e. the values held in each register are pushed down the stack one place at the end of each 15-minute period, and the oldest register values at the bottom of the stack are discarded. As an example, $N$ is greater than or equal to 16 for SDH (see ITU-T Rec. G.784 [1]). +- There should be a current 24-hour register (which can also facilitate the TR24 filter) plus one previous 24-hour register for each event. + +### **5.3.7 Performance history reporting from network elements** + +Performance data should be reportable to the performance management centre to suit various needs, for example: + +- on demand, by request from the performance management centre; +- in a limited and targeted unsolicited format in the case of unavailability/availability transmission state change reports and, when in the available state, TR15/RTR15 or TR24 error performance reports; +- periodically, as part of a network-wide data accumulation task, by the network management centre(s). This may then be used for applications such as preventive maintenance (e.g. longer-term trend analysis) and "poor performer" analysis (see clause 9). + +### **5.3.8 Accuracy and resolution** + +#### **5.3.8.1 Event counts** + +All event counts should be actual counts for the 15-minute filtering period. Although all event counts should (ideally) also be actual counts for the 24-hour filtering periods, it is recognized that it might be desirable to limit register sizes. In such cases, register overflow could occur. Should register overflow occur, the registers should hold at their maximum value for the event considered until the registers are read and reset at the end of the 24-hour period. An implementation involving setting and resetting an overflow bit may be used. + +#### **5.3.8.2 Date/time-stamping of reports** + +The date/time-stamping accuracy of reports, together with the method of maintaining the accuracy, is under study. The format for date/time-stamps is as follows: + +- 15-minute window will be stamped Day, Month, Year, Hour, Minute; +- 24-hour window will be stamped Day, Month, Year, Hour; +- unavailable time events will be stamped Day, Month, Year, Hour, Minute, Second; +- alarms will be stamped either at the declaration of the alarm by the equipment or at the exact time of the event (to be decided) with Day, Month, Year, Hour, Minute, Second. + +Equipment clock accuracy requirements are for further study. + +### **5.3.9 Single-ended monitoring capability** + +Situations are envisaged where it could be desirable to carry out error and availability performance processing of both directions of path transmission from a single end. The specific technology Recommendations detail standardized signal information, which could be used to facilitate this requirement. + +# **6 Fault localization procedures on transmission systems and multiplex sections** + +Fault localization largely depends on the fault localization means available to the ME. However, the guidelines in 6.1 and 6.2 can be used. + +## **6.1 Fault localization in a pre-ISM environment** + +In a pre-ISM environment, a transmission system or multiplex section may not yield standardized events and may not have the capability to record performance history. In this situation, the only opportunity is to monitor on a forward-going basis, probably using proprietary test equipment. + +Clearly, this strategy cannot guarantee identification of the source of the original performance problem, particularly if it is of a transient nature. + +## **6.2 Fault localization in an ISM environment** + +When an unacceptable or degraded performance level is reached, the following should be done: + +- immediately send a message to the control stations of the paths carried by the transmission system or the multiplex section; +- store the message for access by those control stations, which do not receive the message directly. The storage will normally be at the fault report point; +- initiate the ME's fault localization capability to find the faulty maintenance sub-entity. This should be done in a time frame appropriate to the prompt or deferred maintenance alarm levels. + +For example, the specific technology Recommendations give the UPL and DPL thresholds from the long-term perspective. + +# **7 Fault localization procedures on paths** + +The efficiency of the fault localization procedure is largely dependent on the type of information available at each bit rate (i.e. CRC information, parity bit, known frame word, etc.). + +## **7.1 Fault localization in a pre-ISM environment or using OOS means** + +In a pre-ISM environment, the fault localization process will usually start after a user complaint. In this situation, the only opportunity is to monitor after the event. This process cannot guarantee identification of the source of the original performance problem, particularly if it is of a transient nature. The control station responsible for the fault should: + +- determine path routing; +- sectionalize the path. If traffic is not totally interrupted, in-service measuring methods as described in ITU-T Recs. O.161 [8], O.162 [9] and O.163 [10] should be placed at various accessible points along the path to determine which part is faulty. These measurements are made at protected monitoring points (see Figure 2); +- coordinate the measurement process so that subcontrol and participating centres start and finish their measurements at the same time; +- centralize results, either at the control station or at the fault report point, and compare to determine the faulty section; +- ensure that there are no monitoring "blind spots" on the path. A "blind spot" is a portion of the path which exists between two monitored portions. For example, cross-connect equipment may not be covered by the monitors of the transmission systems connected to the input and output. Unless such a cross-connect has its own monitoring system, it may be overlooked. + +If several sections are faulty, fault localization will normally concentrate first on the most severely degraded section. Where additional maintenance effort is available, the total out-of-service time may be reduced by utilizing this additional effort on less degraded sections. However, control is needed so that the efforts of one technician (or group) do not mask a problem being worked on by another. + +If traffic is totally interrupted, or ISM instruments are not available, the same fault localization procedure as before will be used, but with a pseudo-random bit sequence injected (if possible, framed sequence – using a method as described in ITU-T Recs. O.150 [6], O.151 [7] or O.181 [11]). The points of injection and the monitoring locations should be chosen for efficiency of localization. This includes the possibility of loopback. + + + +# 9 Trend analysis and signatures + +In the interest of providing superior service to users, many operators use, or intend to use, a preventive approach to maintenance and fault localization. Preventive maintenance implies locating and correcting faults before a performance impairment reaches an unacceptable or degraded performance level. + +One of the tools of preventive maintenance is trend analysis. Information is gathered from many points in the network, date/time-stamped and stored. Continuing automatic comparisons of measurements from a particular point may indicate, by the trend of the measurements, that there is a potential fault. The results of the trend analysis may generate the equivalent of a low-level deferred maintenance alarm. Economics will determine at what point an operator may decide to take action. + +An indication, which may be useful in trend or comparison analysis, is error performance. A path or section which has poorer error performance than similar paths or sections, or which is showing a trend of increasing errors, may become the target of reinforced maintenance. + +Trend analysis of this type implies a well-developed TMN with wide deployment of ISM techniques. + +A manual technique, which may be useful for either preventive maintenance or fault localization, is the analysis of signatures. A signature is a set of characteristics obtained by measurement, which can be interpreted to indicate the source of a fault or a potential fault. For example, experience on a path transported by submarine cable has shown that a gradually increasing (over several days) number of ES in the absence of SES was indicative of a multiplexer fault, which was not serious enough to generate an alarm. This signature may not appear on other systems. + +As signatures may be equipment-dependent and configuration-dependent, and are often ambiguous, their development and use is a matter for consideration by local maintenance forces. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.2130-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.2130-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2f1992e9db7260dda06dab7fb5d64c7b181742e3 --- /dev/null +++ b/marked/M/T-REC-M.2130-200002-I_PDF-E/raw.md @@ -0,0 +1,616 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2130** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +--- + +**Operational procedures for the maintenance of +the transport network** + +ITU-T Recommendation M.2130 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Operational procedures for the maintenance of the transport network** + +## **Summary** + +This ITU-T Recommendation specifies the operational procedures that two international maintenance organizations have to follow in case of failure or degradation of the transport network: paths, section or synchronization. These procedures are required in order to: localize and clear the fault, permit protection/reversibility and facilitate restoration and return to the original configuration. The maintenance procedures in this ITU-T Recommendation defines reference points requiring information to be exchanged between maintenance organizations of involved Network Operators/Service Providers. + +## **Source** + +ITU-T Recommendation M.2130 was revised by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000. + +## **Keywords** + +Degradation, failure, fault, maintenance, path, procedure, protection, restoration, reversibility, section. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Reference cases ..... | 2 | +| 5.1 No recovery mechanisms ..... | 3 | +| 5.2 Automatic protection (revertive)..... | 3 | +| 5.2.1 The (revertive) protection succeeded..... | 3 | +| 5.2.2 The (revertive) protection failed..... | 4 | +| 5.3 Automatic protection (non-revertive) ..... | 4 | +| 5.3.1 The (non-revertive) protection succeeded ..... | 4 | +| 5.3.2 The (non-revertive) protection failed..... | 5 | +| 5.4 Manual protection ..... | 5 | +| 5.5 Restoration plans..... | 6 | +| 5.5.1 Automatic restoration ..... | 6 | +| 5.5.2 Manual restoration..... | 6 | +| 5.6 Extraneous events ..... | 7 | +| Annex A – Synchronization faults ..... | 14 | +| Appendix I – Bibliography..... | 14 | + +## **Introduction** + +This ITU-T Recommendation specifies the operational procedures to manage faults occurring without recovery mechanisms, with automatic protection (revertive and non-revertive) or manual protection. It also covers the operational procedure for restoration plan. + +## **Operational procedures for the maintenance of the transport network** + +# **1 Scope** + +This ITU-T Recommendation covers PDH and SDH international paths, sections and synchronization. + +A brief description of maintenance procedures is provided. These maintenance procedures follow the approach expressed in ITU-T Recommendations M.20 [2] and M.21 [3], the PDH and SDH paths and sections maintenance procedures expressed in ITU-T Recommendations M.2100 and M.2101 [7], the SDH paths and sections recovery procedures expressed in ITU-T Recommendation M.2102 [8], PDH and SDH maintenance procedures expressed in ITU-T Recommendation M.2120 [9]. + +Synchronization faults usually result in degradation rather than unavailability of the supported trails. The relevant maintenance procedure is detailed in Annex A. + +The following six cases are addressed: + +- 1) no recovery mechanisms; +- 2) automatic protection (revertive); +- 3) automatic protection (non revertive); +- 4) manual protection; +- 5) restoration plans (automatic restoration revertive, automatic restoration non revertive, manual restoration); +- 6) extraneous events. + +The relevant flow charts are provided. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation G.810 (1996), *Definitions and terminology for synchronization networks*. +- [2] CCITT Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks*. +- [3] CCITT Recommendation M.21 (1992), *Maintenance philosophy for telecommunication services*. +- [4] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- [5] ITU-T Recommendation M.1400 (1997), *Designations for international networks*. +- [6] ITU-T Recommendation M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH paths, sections and transmission systems*. + +- [7] ITU-T Recommendation M.2101 (2000), *Performance limits and objectives for bringing-into-service and maintenance of international SDH paths and multiplex sections.* +- [8] ITU-T Recommendation M.2102 (2000), *Maintenance thresholds and procedures for recovery mechanisms (protection and restoration) of international SDH VC trails (paths) and multiplex sections.* +- [9] ITU-T Recommendation M.2120 (2000), *PDH path, section and transmission system and SDH path and multiplex section fault detection and localization procedures.* + +# 3 Terms and definitions + +This ITU-T Recommendation uses terms defined in ITU-T Recommendations M.20 [2], M.60 [4], M.2100 [6], M.2101 [7] and M.2102 [8]. + +# 4 Abbreviations + +This ITU-T Recommendations uses the following abbreviations: + +| | | +|-------|-------------------------------------------| +| ACK | Acknowledgement | +| APS | Automatic Protection Switch | +| FS | Frontier Station | +| GPS | Global Positioning System | +| IB | International Border | +| ICPCE | Inter-country Path Core Element | +| IDTC | International Digital Transmission Centre | +| IG | International Gateway | +| IPCE | International Path Core Element | +| MTIE | Maximum Time Interval Error | +| NACK | Negative Acknowledgement | +| OS | Operations System | +| PCE | Path Core Element | +| PDH | Plesiochronous Digital Hierarchy | +| SASE | Stand Alone Synchronization Equipment | +| SDH | Synchronous Digital Hierarchy | +| SSU | Synchronization Supply Unit | +| TDEV | Time Deviation | + +# 5 Reference cases + +In all cases below, a path or section between two points under the jurisdiction of Control Stations A and B respectively is assumed. For the purposes of the following discussions, the direction of transmission from B to A is considered. A disturbance in this transmission has taken place. + +Synchronization faults usually result in degradation rather than unavailability of the supported trails. The relevant maintenance procedure is detailed in Annex A. + +A general description of mandatory information to be exchanged (e.g. ITU-T Recommendation M.1400 [5] designation of the path or section, other information (e.g.: equipment facility), APS event time stamp etc.) follows. + +### **5.1 No recovery mechanisms** + +The procedures to be applied are shown in Figures 1, 2, 3 and 4. The acceptable, degraded and unacceptable states and relevant thresholds are defined in ITU-T Recommendations M.2100 [6] and M.2101 [7]. In particular: + +- the degradation procedures normally involve the count of relevant events and the measurement of their duration. Additionally, taking into consideration that specific maintenance degradation processes also involve commercial aspects (e.g. extra costs for the possible withdrawal of the degraded path or section from service), their establishment is completely left to agreements among all involved Network Operators/Service Providers; +- in all Figures from 1 to 4, every reference to "acceptable performance" implies the use of the BIS Performance after Repair limits as defined in ITU-T Recommendations M.2100 [6] and M.2101 [7]. + +### **5.2 Automatic protection (revertive)** + +#### **5.2.1 The (revertive) protection succeeded** + +Control Station A acknowledges the activation of the protection and agrees with Control Station B to begin the process of fault diagnosis to understand the reason for the recovery initiation with the goal of returning to the original configuration. + +In this case Control Station A shall send, at least, the following information to Control Station B: + +- a) ITU-T Recommendation M.1400 [5] designation of the path or section; +- b) time1 of the recovery initiation; +- c) request for diagnosis. + +The fault shall be repaired in a fixed time window. If this window is exceeded, an escalation procedure, if it exists, shall be activated. Thus, it is necessary to discover the reason of the failure analysing the network configuration. In particular it is necessary to find out if the fault is located in the IPCE or in the ICPCE. If the faulty element is found in the IPCE the maintenance organization involved clears it and the control station responsible communicates to the other control station: + +- a) the cause of the fault; +- b) the date and time for returning to the original configuration. + +If the faulty element is located in the ICPCE, the two control stations cooperate to locate and repair the fault. + +Return to the original configuration will take place as specified in ITU-T Recommendation M.2102 [8]. + +If the return to the original configuration does not occur, then either the normal is non working, in which case the procedure described in this subclause should be restarted, or there is some other problem which needs investigation. + +--- + +1 Wherever, in this ITU-T Recommendation, date and time are referred, the time is intended to be UTC (Universal Coordinated Time). + +#### **5.2.2 The (revertive) protection failed** + +Control Station A detects the failure in the recovery mechanism and agrees with Control Station B to begin the process of fault diagnosis with the goal to recover the transmission capacity as soon as possible, by any means possible. + +In this case Control Station A shall send, at least, the following information to Control Station B: + +- a) ITU-T Recommendation M.1400 [5] designation of the path or section; +- b) request for diagnosis. + +The fault shall be repaired in a fixed time window. If this window is exceeded, an escalation procedure, if it exists, shall be activated. Thus, it is necessary to discover the reason of the failure analysing the network configuration. In particular it is necessary to find out if the fault is located in the IPCE or in the ICPCE. + +If the faulty element is found in the IPCE the maintenance organization involved clears it and the control station responsible communicates to the other control station: + +- a) the cause of the fault; +- b) the date and time for returning to the original configuration. + +If the faulty element is located in the ICPCE, the two control stations cooperate to locate and repair the fault. + +### **5.3 Automatic protection (non-revertive)** + +#### **5.3.1 The (non-revertive) protection succeeded** + +Control Station A acknowledges the activation of the protection and agrees with Control Station B to begin the process of fault diagnosis to understand the reason for the recovery initiation with the goal of returning to the original configuration. + +In this case Control Station A shall send, at least, the following information to Control Station B: + +- a) ITU-T Recommendation M.1400 [5] designation of the path or section; +- b) time of the recovery initiation; +- c) request for diagnosis. + +The fault shall be repaired in a fixed time window. If this window is exceeded, an escalation procedure, if it exists, shall be activated. Thus, it is necessary to discover the reason of the failure analysing the network configuration. In particular it is necessary to find out if the fault is located in the IPCE or in the ICPCE. If the faulty element is found in the IPCE the maintenance organization involved clears it and the Control Station responsible communicates to the other Control Station: + +- a) the cause of the fault; +- b) the date and time for returning to the original configuration. + +If the faulty element is located in the ICPCE, the two control stations cooperate to locate and repair the fault. + +Once the fault is repaired, the Control Station responsible for the repair communicates to the other the cause of the failure and the date and time of the fault clearing. Thereafter the two entities negotiate a BIS test according to ITU-T Recommendation M.2100 [6] or ITU-T Recommendation M.2101 [7] using the Performance after Repair limit. + +After the test, the Control Stations agree the date and time of returning to the original configuration and the kind of recovery initiation (forced switch to normal or manual switch to normal) to be performed. + +#### **5.3.2 The (non-revertive) protection failed** + +Control Station A detects the failure in the recovery mechanism and agrees with Control Station B to begin the process of fault diagnosis with the goal to recover the transmission capacity as soon as possible, by any means possible. + +In this case Control Station A shall send, at least, the following information to Control Station B: + +- a) ITU-T Recommendation M.1400 [5] designation of the path or section; +- b) request for diagnosis. + +The fault shall be repaired in a fixed time window. If this window is exceeded, an escalation procedure, if it exists, shall be activated. Thus, it is necessary to discover the reason of the failure analysing the network configuration. In particular it is necessary to find out if the fault is located in the IPCE or in the ICPCE. + +If the faulty element is found in the IPCE the maintenance organization involved clears it and the control station responsible communicates to the other control station: + +- a) the cause of the fault; +- b) the date and time for returning to the original configuration. + +If the faulty element is located in the ICPCE, the two control stations cooperate to locate and repair the fault. + +### **5.4 Manual protection** + +The case "Manual protection" may apply also if the automatic protection fails to operate. In this case Control Station A shall send, at least, the following information to control station B: + +- a) ITU-T Recommendation M.1400 [5] designation of the path or section; +- b) the date and time of the failure. + +Thus, both parties agree upon the time and the kind of recovery initiation to perform. Afterwards both parties verify if the service was restored and subsequently they cooperate to localize the faulty element. + +The fault shall be repaired in a fixed time window. If this window is exceeded, an escalation procedure, if it exists, shall be activated. Thereafter it is necessary to discover the reason of the failure analysing the routing and all the sections involved. In particular it is necessary to find out if the fault is located at the national or international level. If the faulty element is found in the national portion or in the IPCE the maintenance organization involved clears it and the control station responsible communicates to the other control station: + +- a) the fault cause; +- b) the date and time when the original configuration of the path or section will be available. + +If the faulty element is located in the ICPCE, the two control stations cooperate to locate and repair the failure. + +Once the fault is repaired, the control station responsible for the reparation communicates to the other the cause of the failure and the date and time of the new availability of the path or section. Thereafter the two control stations negotiate an acceptance test on the normal path or section whose characteristics (time, thresholds) depend on the type of the failure: degradation, interruption or card breakdown. + +If the test is OK, the control stations agree on the date and time for which the original path or section has to be brought again into operation and the kind of recovery initiation (forced switch to normal or manual switch to normal) to be performed. + +If the manual protection cannot be performed because the alternate path or section is not available, subclause 5.1 applies. + +### 5.5 Restoration plans + +A restoration plan is a set of prearranged actions to be carried out in case of failures involving paths or sections. Examples of restoration plans can be found in Appendix I, reference [B1]. The plan can be executed by an OS or manually. If the plan is carried out by an OS, the return to the original configuration can be performed by manual switch to normal (automatic restoration non-revertive) or, also, by automatic OS controlled switch to normal (automatic restoration revertive). In case of manual restoration, this can be performed either by manual switch to alternate or by manual patch to alternate. Consequently, the return to the original configuration can be carried out by forced switch to normal, manual switch to normal or manual patch to normal. + +The restoration plan (either automatic or manual) can be performed at the path level or at the section level. + +#### 5.5.1 Automatic restoration + +In this case, the restoration plan is automatically initiated by the OS. After an agreed time interval, the maintenance organization responsible for the path or the section shall check to see if the service has been restored. + +If the restoration is successful, Control Station A and Control Station B cooperate in the localization of the fault, determining if the fault is in the IPCE or in the ICPCE. + +In case of failure in the ICPCE, the two control stations work together to locate and repair the fault. + +Once the fault is repaired, the Control Stations involved in the repair specify the cause of the failure and the date and time for returning to the original configuration. Thereafter the two Control Stations negotiate a BIS test according to ITU-T Recommendation M.2100 [6] or ITU-T Recommendation M.2101 [7] using the Performance after Repair limit. + +After the test, the Control Stations agree on the date and time for returning to the original configuration and the kind of recovery initiation (automatic OS controlled switch to normal or manual switch to normal) to be performed. In case of automatic restoration non-revertive, only the manual switch to normal can be performed. + +If the plan cannot be executed by one or more parties, subclause 5.1 applies and the party that cannot execute its part of the plan informs the others of the reason (e.g. lack of spare network resources due to the activation of another restoration plan). + +#### 5.5.2 Manual restoration + +In this case Control Station A communicates to Control Station B: + +- a) ITU-T Recommendation M.1400 [5] designation of the path or section; +- b) the date and time of the failure. + +Then, both parties execute the part of the plan for which they are responsible and, when the plan is completed, check to see if the service has been restored. + +If the restoration is successful, Control Station A and Control Station B cooperate in the localization of the fault finding out if the fault is in the IPCE or in the ICPCE. + +In the case that the fault is in the IPCE for which Control Station B is responsible, Control Station B informs Control Station A about: + +- a) the fault cause; +- b) the date and time when the original configuration of the path or section will be available. + +Once the fault is repaired, the Control Stations involved in the repair specify the cause of the failure and the date and time for fault clearing. Thereafter the two control stations negotiate a BIS test according to ITU-T Recommendation M.2100 [6] or ITU-T Recommendation M.2101 [7] using the Performance after Repair limit. + +After the test, the Control Stations agree on the date and time for returning to the original configuration and the kind of recovery initiation (forced switch to normal, manual switch to normal or manual patch to normal) to be performed. + +In case of failure in the ICPCE, the two control stations work together to locate and repair the fault. + +If the plan cannot be executed by one or more parties, subclause 5.1 applies and the party that cannot execute its part of the plan informs the others of the reason (e.g. lack of spare network resources due to the activation of another restoration plan). + +### **5.6 Extraneous events** + +Events which do not last long enough to allow for restoration processing may be detected by a control station (for instance A) which cannot ascribe the event to an automatic switch between equipment under its responsibility. + +In this case, Control Station A shall record all information regarding these events (date and time of the occurrence, etc.) and report these to Control Station B according to bilateral or multilateral agreements, in order to get subsequent in-depth analysis and solve these problems to avoid their serious impact onto the carried services. + +This kind of event can be closed as: + +- self healing (when both parties acknowledge the event but they do not know the real cause); +- problem not found if one party does not acknowledge the event. + +![Flowchart for Figure 1/M.2130 showing fault detection and handling between nodes A and B. The process starts with 'Fault occurrence', followed by 'A detects a failure'. If 'No', it goes to 'Degradation Procedure'. If 'Yes', 'A reports the failure to B'. Then 'B acknowledges the failure'. If 'Yes', 'B sends ACK to A', leading to withdrawal and localization. If 'No', 'B sends NACK to A', leading to 'A confirms NACK'. If 'Yes', the event is closed and stored. If 'No', it leads to a common point. Further decisions on 'failure located in the IPCE' and 'B can make a restoration' lead to various outcomes (1, 2, 3, or End).](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph TD + Start([Fault occurrence]) --> A_detects{"A" detects +a failure} + A_detects -- No --> Degradation[Degradation +Procedure] + A_detects -- Yes --> A_reports["A" reports the failure to "B"] + A_reports --> B_ack{"B" acknowledges +the failure} + B_ack -- Yes --> B_ACK["B" sends ACK to "A"] + B_ACK --> Withdraw["A" and "B" withdraw the failed +path or section from service] + B_ack -- No --> B_NACK["B" sends NACK to "A"] + B_NACK --> A_confirms{"A" confirms +NACK} + A_confirms -- Yes --> Close["A" and "B" close the event as +failure self cleared"] + Close --> Store["A" and "B" store the event for +transmission performance +statistics"] + Store --> End([End]) + A_confirms -- No --> Withdraw + Withdraw --> Localize["A" and "B" cooperate in localizing +the failure exchanging tests +schedules and results"] + Localize --> Located{the failure is +located in the IPCE} + Located -- Yes --> Connector4((4)) + Located -- No --> Node1((1)) + Node1 --> SeeFig4[see Fig. 4/M.2130] + Connector4 --> SeeFig2_4[see Fig. 2/M.2130] + Connector4 --> Can_restore{"B" can make +a restoration} + Can_restore -- Yes --> Node3((3)) + Can_restore -- No --> Node2((2)) + Node3 --> SeeFig2_3[see Fig. 2/M.2130] + Node2 --> SeeCont[see continuation of +Fig. 1/M.2130] + +``` + +T0411480-99 + +Flowchart for Figure 1/M.2130 showing fault detection and handling between nodes A and B. The process starts with 'Fault occurrence', followed by 'A detects a failure'. If 'No', it goes to 'Degradation Procedure'. If 'Yes', 'A reports the failure to B'. Then 'B acknowledges the failure'. If 'Yes', 'B sends ACK to A', leading to withdrawal and localization. If 'No', 'B sends NACK to A', leading to 'A confirms NACK'. If 'Yes', the event is closed and stored. If 'No', it leads to a common point. Further decisions on 'failure located in the IPCE' and 'B can make a restoration' lead to various outcomes (1, 2, 3, or End). + +**Figure 1/M.2130** + +![Flowchart for Figure 1/M.2130 (continued) showing a repair process between nodes 'A' and 'B'. It starts at connector '2', proceeds through repair initiation, escalation checks, failure clearing, path verification, and final data storage.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph TD + Start((2)) --> Step1["\"B\" starts the repair process and reports to \"A\" the estimated time to clear the failure"] + Step1 --> Decision1{An escalation procedure exists} + Decision1 -- Yes --> Decision2{Escalation procedure criteria are met} + Decision1 -- No --> Step2["\"B\" clears the failure"] + Decision2 -- Yes --> Step3["\"A\" and \"B\" apply the Escalation Procedure"] + Decision2 -- No --> Step2 + Step3 --> Step2 + Step2 --> Step4["\"A\" and \"B\" make an overall transmission check of the path or"] + Step4 --> Decision3{"\"A\" and \"B\" verify that the end-to-end path or section has been restored to its acceptable performance"} + Decision3 -- No --> Start + Decision3 -- Yes --> Step5["\"A\" and \"B\" agree upon the restoration data details and store them for transmission performance statistics"] + Step5 --> End([End]) + +``` + +Flowchart for Figure 1/M.2130 (continued) showing a repair process between nodes 'A' and 'B'. It starts at connector '2', proceeds through repair initiation, escalation checks, failure clearing, path verification, and final data storage. + +T0411490-99 + +Figure 1/M.2130 (continued) + +![Flowchart for IPCE RESTORING PROCEDURE. It starts with connector 3, followed by the procedure name, then steps for restoration and notification. A decision diamond checks for acceptable performance. If 'No', it checks if an escalation procedure exists and if criteria are met. If 'Yes' to either, it applies the escalation procedure and goes to connector 4. If 'No' to both, it goes directly to connector 4. If 'Yes' to the first decision, it involves data storage and repair initiation, leading to connector 5.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph TD + 3((3)) --> P[IPCE RESTORING PROCEDURE] + P --> S1[""B" restores the failed path or section using facilities on its IPCE"] + S1 --> S2[""B" informs "A" that path or section restoration has been performed"] + S2 --> D1{""A" and "B" verify that the end-to-end path or section has been restored to its acceptable performance"} + D1 -- No --> D2{"Escalation Procedure exists"} + D2 -- No --> 4((4)) + D2 -- Yes --> D3{"Escalation Procedure Criteria are met"} + D3 -- No --> 4 + D3 -- Yes --> S3[""A" and "B" apply the Escalation Procedure"] + S3 --> 4 + D1 -- Yes --> S4[""A" and "B" agree upon the restoration data details and store them for transmission performance statistics"] + S4 --> S5[""B" starts the repair process and informs "A" of the estimated time to clear the failure"] + S5 --> 5((5)) + +``` + +see Fig. 1/M.2130 + +see Fig. 3/M.2130 + +T0411500-99 + +Flowchart for IPCE RESTORING PROCEDURE. It starts with connector 3, followed by the procedure name, then steps for restoration and notification. A decision diamond checks for acceptable performance. If 'No', it checks if an escalation procedure exists and if criteria are met. If 'Yes' to either, it applies the escalation procedure and goes to connector 4. If 'No' to both, it goes directly to connector 4. If 'Yes' to the first decision, it involves data storage and repair initiation, leading to connector 5. + +**Figure 2/M.2130** + +![Flowchart for Figure 3/M.2130 showing the process of failure clearing and return to original configuration. It starts with a connector '5', followed by 'Failure clearing and return to the original configuration', then a loop involving 'B' clearing failure, validation tests, and restoration steps until performance is acceptable.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +graph TD + 5((5)) --> FC[Failure clearing and return to the original configuration] + FC --> B1["B" clears the failure and makes validation test] + B1 --> VT{Validation test is passed} + VT -- No --> B1 + VT -- Yes --> B2["B" informs "A" that the failure has been cleared and declares that it is ready to return the path or section to its original configuration"] + B2 --> AB1["A" and "B" make an overall transmission check of the path or section] + AB1 --> EOP{The end-to-end path or section original configuration has been restored to its acceptable performance} + EOP -- No --> B1 + EOP -- Yes --> AB2["A" and "B" agree upon an appropriate work plan, including precise date and time, for the return to the original configuration"] + AB2 --> B3["B" restores the path or section to its original configuration"] + B3 --> AB3["A" and "B" agree upon the restore data details and store them for transmission performance statistics"] + AB3 --> End([End]) + +``` + +Flowchart for Figure 3/M.2130 showing the process of failure clearing and return to original configuration. It starts with a connector '5', followed by 'Failure clearing and return to the original configuration', then a loop involving 'B' clearing failure, validation tests, and restoration steps until performance is acceptable. + +T0411510-99 + +**Figure 3/M.2130** + +![Flowchart for fault handling in the ICPCE. It starts with a connector '1', leading to 'FAULT IN THE ICPCE'. A decision 'Mutual aid plan exists' follows. If 'No', it goes to 'Escalation Procedure can be applied' and then to 'A and B cooperate to clear the failure'. If 'Yes', it goes to 'A and B activate the mutual aid plan'. Both paths lead to a decision 'Agreed time is expired'. If 'Yes', it goes to 'Path or section has been restored'. If 'No', it loops back to 'Agreed time is expired'. If 'Yes', it goes to connector '6'. If 'No', it goes to 'A and B cooperate to clear the failure'. From 'A and B cooperate to clear the failure', it goes to 'A and B make an overall transmission check of the path/section', then to a decision 'A and B verify that the end-to-end path or section has been restored to its acceptable performance'. If 'Yes', it goes to 'A and B agree upon the repair data details and store them for transmission statistics performance', then to 'End'. If 'No', it loops back to 'A and B cooperate to clear the failure'. Connector '6' has a note 'see continuation of Fig. 4/M.2130' and the code 'T0411520-99'.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + 1((1)) --> F[FAULT IN THE ICPCE] + F --> D{Mutual aid plan exists} + D -- No --> E[Escalation Procedure can be applied] + D -- Yes --> A["A" and "B" activate the mutual aid plan] + E --> C["A" and "B" cooperate to clear the failure] + A --> B{Agreed time is expired} + B -- Yes --> C2{Path or section has been restored} + B -- No --> B + C2 -- Yes --> 6((6)) + C2 -- No --> C + C --> D2["A" and "B" make an overall transmission check of the path/section] + D2 --> D3{"A" and "B" verify that the end-to-end path or section has been restored to its acceptable performance} + D3 -- Yes --> E2["A" and "B" agree upon the repair data details and store them for transmission statistics performance] + D3 -- No --> C + E2 --> End([End]) + 6 -.-> Cont[see continuation of Fig. 4/M.2130] + T0411520-99 + +``` + +Flowchart for fault handling in the ICPCE. It starts with a connector '1', leading to 'FAULT IN THE ICPCE'. A decision 'Mutual aid plan exists' follows. If 'No', it goes to 'Escalation Procedure can be applied' and then to 'A and B cooperate to clear the failure'. If 'Yes', it goes to 'A and B activate the mutual aid plan'. Both paths lead to a decision 'Agreed time is expired'. If 'Yes', it goes to 'Path or section has been restored'. If 'No', it loops back to 'Agreed time is expired'. If 'Yes', it goes to connector '6'. If 'No', it goes to 'A and B cooperate to clear the failure'. From 'A and B cooperate to clear the failure', it goes to 'A and B make an overall transmission check of the path/section', then to a decision 'A and B verify that the end-to-end path or section has been restored to its acceptable performance'. If 'Yes', it goes to 'A and B agree upon the repair data details and store them for transmission statistics performance', then to 'End'. If 'No', it loops back to 'A and B cooperate to clear the failure'. Connector '6' has a note 'see continuation of Fig. 4/M.2130' and the code 'T0411520-99'. + +Figure 4/M.2130 + +![Flowchart for Figure 4/M.2130 (continued) showing a process for restoring data details and configuration. It starts at connector 6, proceeds through data storage, failure cause removal, transmission checks, and configuration restoration or escalation procedures.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +``` + +graph TD + 6((6)) --> P1[""A" and "B" agree upon the restoring data details and store them for transmission statistics performance"] + P1 --> P2[""A" and "B" cooperate to remove the cause of the failure on the original configuration of the path or section"] + P2 --> P3[""A" and "B" make an overall transmission check"] + P3 --> D1{The end-to-end original configuration has been restored to its acceptable performance} + D1 -- No --> D2{An escalation procedure exists} + D1 -- Yes --> P4[""A" and "B" return the path or section to its original configuration"] + P4 --> P5[""A" and "B" agree upon the repair data details and store them for transmission performance statistics"] + P5 --> End([End]) + D2 -- No --> P2 + D2 -- Yes --> D3{Escalation procedure criteria are met} + D3 -- No --> Left[ ] + D3 -- Yes --> P6[""A" and "B" apply the escalation procedure"] + P6 --> D2 + style Left fill:none,stroke:none + +``` + +Flowchart for Figure 4/M.2130 (continued) showing a process for restoring data details and configuration. It starts at connector 6, proceeds through data storage, failure cause removal, transmission checks, and configuration restoration or escalation procedures. + +T0411530-99 + +Figure 4/M.2130 (continued) + +## ANNEX A + +## **Synchronization faults** + +A synchronization fault exists whenever a fault event is detected in the active synchronization equipment2, causing a degradation in the availability performance of a clock source and the relevant accuracy of synchronization. + +If the level of synchronization degradation exceeds a limit, agreed between the Network Operators involved, the following procedure should be followed. + +If a synchronization fault is individually detected by one of the Control Stations involved, it should check the synchronization equipment, all digital clock distributors, and all synchronization bearers. + +Control Station A shall record all information regarding the event. In case of severe degradation that may have serious impact on the carried services, Control Station A shall also report all information regarding the event (e.g. date and start time of the fault) to Control Station B according to specific bilateral agreements. + +Once the synchronization fault has been cleared, Control Station A shall inform Control Station B on the causes and resolution (e.g. date and end time). Furthermore, Control Station A shall continue monitoring synchronization performance (e.g. MTIE, TDEV) for an agreed period of time to verify that the degraded or unacceptable conditions are definitively cleared. + +It is very important to manage all types of synchronization faults efficiently to avoid possible negative impact on services. The reporting of synchronization faults allows the operator to avoid some service affecting events entirely or, when services are impacted, reduce restoration time. + +## APPENDIX I + +## **Bibliography** + +[B1] URM Universal Restoration Manual (latest Edition). + +This document is distributed by co-owners on a system-by-system basis. + +--- + +2 The Synchronization equipment is normally called Stand Alone Synchronization Equipment (SASE) or Synchronization Supply Unit (SSU) (see ITU-T Recommendation G.810 [1]). It usually includes different synchronization sources for reliability purposes (e.g. synchronization bearers from high-level source, GPS source, local rubidium/quartz crystal oscillator). + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.2140-200002-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/M/T-REC-M.2140-200002-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65a88be9b5b951a1ef3cb1e05f5b5d52cb78ee7f --- /dev/null +++ b/marked/M/T-REC-M.2140-200002-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0719d775dfd582ae999fb7b70413061c7a285caff401a7ff03e95d677f439323 +size 145539 diff --git a/marked/M/T-REC-M.2140-200002-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/M/T-REC-M.2140-200002-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d37e4f093c3065e53e30578f8cc78d15e4f44fc5 --- /dev/null +++ b/marked/M/T-REC-M.2140-200002-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd92e36b1ad865f0c2946ebc9c71c91bf920941cb36fde7c21f94fae233c9041 +size 50554 diff --git a/marked/M/T-REC-M.2140-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.2140-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/M/T-REC-M.2140-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/M/T-REC-M.2140-200002-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/M/T-REC-M.2140-200002-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c556466484f1cb56997fc516b25e262f86f70f6 --- /dev/null +++ b/marked/M/T-REC-M.2140-200002-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3cca2c9630740a8111a410382f2ed353cabbf7e3b4738bcef8dbd8da153cb19 +size 57935 diff --git a/marked/M/T-REC-M.2140-200002-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/M/T-REC-M.2140-200002-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ac6f7ec2846e38e3ed32fe6d34e4c27ef3c5a7a --- /dev/null +++ b/marked/M/T-REC-M.2140-200002-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a573cf02b192c6e9d96b10a8eee3eea15a022fe08560d20a4240ebe6159383c +size 114243 diff --git a/marked/M/T-REC-M.2140-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.2140-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d9404db75054ef5453bd43c37736405e2bc7f358 --- /dev/null +++ b/marked/M/T-REC-M.2140-200002-I_PDF-E/raw.md @@ -0,0 +1,967 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2140** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +# --- **Transport network event correlation** + +ITU-T Recommendation M.2140 + +(Formerly CCITT Recommendation) + +--- + +## ITU-T M-SERIES RECOMMENDATIONS + +## **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Transport network event correlation** + +## **Summary** + +This ITU-T Recommendation is a functional description of the operations functions required to achieve Network Event Correlation in the surveillance of international transport networks. The capability described is to correlate notifications of faults and impairments from Network Elements and to reveal the nature, location and severity of the faults and impairments and their true effect on the network. + +This Recommendation is based on the TMN Functional Architecture as specified in ITU-T Recommendation M.3010. This Recommendation identifies the TMN Management Function Sets from ITU-T Recommendation M.3400 that are involved in Transport Network Event Correlation, provides functional descriptions of each Management Function Set, and illustrates how they interact to achieve Transport Network Event Correlation. + +## **Source** + +ITU-T Recommendation M.2140 was prepared by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000. + +### **Keywords** + +Alarm Correlation, Event Correlation, Fault Management, Functional Architecture, International Transmission Entities, Network Management, Performance Management, Surveillance, Telecommunications Management Network (TMN). + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-----------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 4 | Abbreviations..... | 2 | +| 5 | Principles ..... | 3 | +| 5.1 | Event correlation processes..... | 3 | +| 5.1.1 | Selection of events..... | 3 | +| 5.1.2 | Comparison of events ..... | 3 | +| 5.1.3 | Persistence analysis ..... | 4 | +| 5.1.4 | Dependencies..... | 5 | +| 5.1.5 | Patterning..... | 6 | +| 5.2 | Generic event correlation model..... | 6 | +| 5.2.1 | Stage 0 ..... | 7 | +| 5.2.2 | Stage 1 ..... | 7 | +| 5.2.3 | Stage 2 ..... | 7 | +| 5.2.4 | Stage 3 ..... | 7 | +| 5.2.5 | Stage 4 ..... | 7 | +| 5.3 | Surveillance operations flows..... | 8 | +| 5.4 | Implementation considerations ..... | 10 | +| 6 | The transport network event correlation MAF interaction diagram ..... | 10 | +| 7 | Performance management..... | 14 | +| 7.1 | Detection, counting, storage and reporting ..... | 15 | +| 7.2 | NE(s) performance characterization ..... | 15 | +| 7.3 | Performance monitoring data accumulation ..... | 15 | +| 7.4 | NE(s) trend analysis ..... | 16 | +| 7.5 | Data aggregation and trending ..... | 16 | +| 7.6 | NE(s) TCA processing..... | 16 | +| 7.6.1 | TCA correlation rules ..... | 17 | +| 7.6.2 | Persistence analysis ..... | 17 | +| 7.7 | Network performance monitoring event correlation and filtering ..... | 18 | +| 7.7.1 | Correlation of impairment indications along a trail..... | 18 | +| 7.7.2 | Correlation of impairment indications among related trails ..... | 18 | +| 7.7.3 | Correlation of trend indications with impairment indications..... | 18 | +| 8 | Fault management..... | 19 | +| 8.1 | Failure event detection and reporting..... | 19 | + +| | Page | +|----------------------------------------------------------------------------|-------------| +| 8.2 Alarm reporting..... | 19 | +| 8.2.1 Equipment faults..... | 20 | +| 8.2.2 Communication faults..... | 20 | +| 8.2.3 Environmental conditions..... | 20 | +| 8.3 Alarm correlation and filtering ..... | 20 | +| 8.3.1 Processing of equipment alarms ..... | 21 | +| 8.3.2 Processing of communication alarms ..... | 21 | +| 8.3.3 Processing of environmental alarms..... | 21 | +| 8.3.4 Processing of state changes ..... | 22 | +| 8.3.5 Correlation of alarms among related trails ..... | 22 | +| 8.3.6 Persistence analysis ..... | 22 | +| 8.3.7 Declaring fault indications..... | 23 | +| 8.4 Network fault event analysis, including correlation and filtering..... | 23 | +| 8.4.1 Correlation of fault indications along a trail..... | 23 | +| 8.4.2 Correlation of fault indications among related trails ..... | 23 | +| 8.5 Network fault localization ..... | 24 | +| 8.5.1 Patterning of indications..... | 24 | +| 8.5.2 Correlation of indications among related resources ..... | 25 | +| 9 Configuration management..... | 25 | +| 9.1 Notification of state changes by NEs..... | 25 | +| 9.2 NE(s) status and control..... | 25 | +| 9.2.1 Operational state changes ..... | 25 | +| 9.2.2 Administrative state changes ..... | 26 | + +## Introduction + +Planning, developing and supporting operations functions in Network Elements (NEs) and management systems, and linking them together via well-defined open interfaces, are critical steps to introducing new technologies and services into the network and providing network operations support across boundaries between network/service providers. + +One of the key areas for network/service providers to automate with management systems supporting open interfaces is the area of service assurance. Service assurance is increasingly driven by the ability of the network to detect and report service affecting conditions before the customer reports a trouble. The network provides a wealth of information about its performance and the occurrence of service affecting conditions. Existing Operations Systems can process this information to some degree, but not completely, and rarely across different layers of a layered network or across traditional operations centre boundaries. As a result, service assurance today requires significant manual effort to properly interpret the information reported by NEs. The key to driving cost out of service assurance and improving its response time is to further automate the interpretation and correlation of events in complex layered networks. + +The intended audience of this Recommendation includes: + +- network operators interested in deploying management systems that perform Network Event Correlation within a TMN (operations and maintenance planners, transport network maintenance staff); +- OS vendors interested in providing management systems that perform Network Event Correlation, including element management systems (systems engineers and software developers); +- NE suppliers needing to understand how notifications that NEs produce will be used by the TMN (systems engineers and software developers). + +## Background + +TMN emphasizes the use of open, standard interfaces among management systems as well as between management systems and NEs. TMN also provides a logical framework for describing the Management Application Functions (MAFs) associated with the management of the network and the management of services supported by the network. ITU-T Recommendation M.3400, *TMN Management Functions*, is a guide for planning and deploying the management systems necessary for timely and efficient management of networks and services. The Management Function Sets of M.3400 serve as atomic units of network management functionality. The Management Functions in each set cannot easily stand alone. The Management Function Sets can stand alone or they can be packaged together into management systems at the discretion of network/service providers. Each Management Function Set can be considered to be its own Management Application Function (MAF) as defined in ITU-T Recommendation M.3010. This Recommendation treats each Management Function Set as an MAF. + +The functional decomposition of operations functions into the MAFs that correspond to the Management Function Sets of ITU-T Recommendation M.3400 helps achieve consistency of functionality among Operations Systems from various suppliers used by different network/service providers managing various network technologies. This functional consistency along with TMN open, standard interfaces (defined in ITU-T Recommendation M.3010) allows interoperability between these Operations Systems and the rapid integration of new emerging technologies into a comprehensive Network Event Correlation capability. + + + +## Transport network event correlation + +# 1 Scope + +The purpose of this Recommendation is the use of the Telecommunications Management Network (TMN) to correlate notifications of conditions (faults and impairments) from Network Elements and to reveal the conditions themselves and their true effect on the network. This Recommendation is based on the TMN Functional Architecture as specified in ITU-T Recommendation M.3010 [3]. This Recommendation identifies the TMN Management Application Functions (MAFs) corresponding to the Management Function Sets of ITU-T Recommendation M.3400 [4] that are involved in Transport Network Event Correlation. It provides functional descriptions of each MAF, and illustrates how these MAFs interact to achieve Transport Network Event Correlation. This Recommendation also includes timing criteria for event correlation. + +Transport Network Event Correlation relies on current configuration information from Configuration Management MAFs. It also is controlled in the specifics of its operation by policies in Business Management Layer MAFs. These interactions are mentioned in appropriate places, but are outside of the scope of this Recommendation. + +This Recommendation does not require the exchange of any particular operator's information about its national network. + +Algorithms for event correlation are important to the successful implementation of the MAFs described in this Recommendation. Detailed specification of these algorithms is outside of its scope. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] CCITT Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks*. +- [2] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- [3] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [4] ITU-T Recommendation M.3400 (2000), *TMN management functions*. + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +- 3.1 active:** Not cleared. +- 3.2 clear:** The end of a fault; the termination of a standing condition. +- 3.3 data collection interval:** The period over which performance parameters are accumulated to compute each stored measurement and detect maintenance threshold crossings. +- 3.4 degradation:** The presence of anomalies or defects in the absence of a fault. + +**3.5 event:** An instantaneous occurrence that changes the global status of an object. This status change may be persistent or temporary, allowing for surveillance, monitoring and performance measurement functionality, etc. Events may or may not generate reports; they may be spontaneous or planned; they may trigger other events or may be triggered by one or more other events. (Recommendation M.60.) + +**3.6 event correlation process:** A process that accepts events as input, performs one or more event correlation subprocesses, and reports events as output. + +**3.7 event correlation subprocess:** A single step in an event correlation process (see 5.1 for the five types). + +**3.8 event report message:** A message sent from one physical system to another that contains information about an event. + +**3.9 event set:** The set of all events that are grouped by a selection process for direct comparison or patterning. + +**3.10 impairment:** A condition that causes anomalies and defects without causing a failure (degrades the performance of a resource without causing a failure). + +**3.11 indication:** An intermediate output of the event correlation process. A notification, indicating a persistent network detected trouble condition. The three types of indication are fault indication, impairment indication and trend indication. + +**3.12 independent event:** An event that is not currently superseded by another event. + +**3.13 notification:** Information emitted by a managed object relating to an event that has occurred within the managed object (Recommendations M.60, X.710; Information passed from one MAF to another regarding an event). + +**3.14 standing condition:** A condition that has duration, beginning with a failure and ending with a clear. + +**3.15 threshold crossing alert:** A transient condition declared when a performance monitoring parameter reaches or exceeds a preset threshold. + +**3.16 transient condition:** A condition that has no duration, a one time report. + +**3.17 trouble:** The perception of a fault or degradation that is judged to require maintenance attention. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|-------------------------------------------------| +| ISM | In-Service Monitoring | +| MAF | Management Application Function | +| MFA | Management Functional Area | +| NE | Network Element | +| OS | Operations System | +| PDH | Plesiochronous Digital Hierarchy | +| SDH | Synchronous Digital Hierarchy | +| TCA | Threshold Crossing Alert, also Threshold Report | +| TMN | Telecommunications Management Network | + +# **5 Principles** + +Telecommunications networks are highly complex systems that must be very reliable. Yet they are made up of millions of parts that can fail and they are subject to a wide variety of unpredictable stresses. The solution that the telecommunications industry has arrived at is to build into the network the ability to detect and report stresses, failures and performance statistics. These real-time reports should allow corrective action to begin quickly and proceed rapidly with the information supplied in the notifications from the network. + +Each Network Element (NE) has many ways in which it can fail, or be stressed, and it has the capability to report as many of these conditions as can be foreseen. The only difficulty is that one condition in the network may result in many notifications from multiple NEs for each trouble that needs to be fixed. The number of messages is increased further because the NEs have been designed to send notifications to each other and to both report the condition. This is done to allow limited automatic corrective action and just in case one of the NEs is cut off from the communications with the TMN. + +For example, a few troubles in a network can result in hundreds of notifications being generated. Transport Network Event Correlation serves the vital business need to process the hundreds of notifications in real-time and to distinguish each independent trouble. It must also provide the best information from all of the notifications about the nature, location and severity of each trouble. + +## **5.1 Event correlation processes** + +An event correlation process accepts notifications from Network Elements (or other Operations Systems) and eliminates redundant and symptomatic notifications. It also eliminates notifications of conditions that are not persistent or otherwise do not require maintenance action. It does this by sorting and comparing notifications, consulting databases about the layout and hierarchy of the network, and constantly updating its view of the state of the network. An event correlation process produces a single notification for each distinct condition with the best information from all of the notifications about the nature, location and severity of each condition. This single notification is often referred to as the root cause within the scope of the event correlation process. + +An event correlation process can be described as a combination of selecting notifications, comparing or patterning them, evaluating dependencies and checking to see that the condition that triggered the notifications is persistent. These five subprocesses can be linked up in a process flow to create sophisticated event correlation processes. Each of these subprocesses is described below. + +### **5.1.1 Selection of events** + +The event correlation process starts with a stream of incoming notifications. One of the fundamental event correlation tools is the selection of notifications. Related notifications are selected for direct comparison or patterning. This selection may be done based on any attributes of an event including the type of notification, the source of the notification, or the dependencies between the sources of notifications. + +The set of all events that are grouped by a selection process for direct comparison or patterning is called an event set. Event sets must be defined so that the event correlation rules can always produce a single event to characterize each underlying trouble condition, through filtering and combination of any possible members of the event set, that is meaningful and without losing valuable surveillance information. + +### **5.1.2 Comparison of events** + +An event comparison subprocess ensures that there is always at most one active, independent event for each underlying condition within the domain of the MAF. It does this by using event correlation rules that are specific to each stage of event correlation and often specific to the types of resources being monitored. + +An event is active if it has not been cleared and has not expired by falling outside of a correlation window. An event is independent if it has not been superseded by another event. + +The comparison of events occurs when a new event notification is received and selected into the same event set as another active, independent event. The attributes of the new event are compared with the attributes of the independent events already in the event set. Correlation rules are used to determine whether the new event supersedes or is superseded by the independent events already in the event set. If there is an independent event, related to the same underlying condition, that cannot supersede or be superseded by the new event, it will be combined with the new event. This combination is done to preserve relevant information from both events into a single synthesized event that supersedes both to become a new independent event within the event set. + +In some cases, events can be ordered by severity or by significance. This is often because the condition reported by one notification implies the condition reported by another. For example, a critical alarm of a given type and source supersedes a major alarm of the same type and source. An environmental alarm indicating high humidity is superseded by one indicating a flood. When one event is superseded by another it is filtered out when the persistence time is reached. If no persistence analysis is performed within the event correlation process, then superseded events are filtered out immediately. + +In other situations notifications are of equal severity and significance, but are clearly related. Examples of this are, two equipment alarms from the same equipment component or two environmental alarms of the same severity from equipment at the same location. In these situations two events must be combined into a single synthesized event with multiple cause codes. + +If there are unrelated notifications then they may be the result of independent underlying conditions in the network and so they are not correlated. All independent notifications are sent forward to the next subprocess of the event correlation process. + +The rules for comparing and combining notifications will differ slightly from one technology to another, but should be stable for each technology (set of managed resources), and should not require much administration. + +### **5.1.3 Persistence analysis** + +Persistence analysis looks at one or more types of notification, which can be an output of another event correlation subprocess, and correlates those types of notification over time. + +The purpose of persistence analysis is to distinguish between persistent conditions, which require further analysis and attention, and non-persistent conditions that should be ignored and filtered out. Non-persistent conditions are infrequent and of short duration. When a condition is not persistent there is no reason to believe that a subsequent condition will occur or that any intervention will improve the expected performance of the affected network component in the future. Non-persistent conditions usually have external causes such as human activity or adverse weather conditions. Persistent conditions are long duration or intermittent but frequent occurrences of the same condition. When a persistent condition is observed there is reason to believe that the condition will continue or recur, that some network component is at fault, and that the trouble can be found and corrected. + +There are two fundamentally different types of conditions for the purpose of persistence analysis. A standing condition, such as a fault or state value exists for the entire period from when it is raised (reported by an alarm or state change notification) to when it is cleared (reported by an alarm clear or state change notification). All types of indications defined in 5.1.3 are standing conditions. A transient condition, such as a threshold crossing [reported by a Threshold Crossing Alert (TCA)], carries information that applies only to a particular moment in time and does not have an associated clear event. + +For standing conditions, persistence analysis consists of measuring the length of time that passes after the event (a condition is raised or cleared or a state value changes) and after enough time has + +passed, declaring the event persistent. When the event is declared persistent, a notification is sent forward. If the event is reversed before enough time has passed, then it is filtered out and no notification is sent forward. + +![Figure 1/M.2140 – Persistence analysis for standing conditions. A state transition diagram showing the lifecycle of events. It starts with two entry points: 'Event received that supersedes all active events' leading to 'Active & Independent' state, and 'Event received that is superseded by one or more active events' leading to 'Active & Dependent' state. Transitions include 'All superseding events cleared' (Independent to Dependent), 'Superseding event received' (Dependent to Independent), 'Persistence time reached' (Independent to Persistent Event), and 'Clear message received' (both Independent and Dependent to Filtered Out). The 'Persistent Event' state leads to 'New event declared and sent to the next stage of the correlation process'. A small code 'T0411740-99' is in the bottom right.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Active_Independent : Event received that supersedes all active events + [*] --> Active_Dependent : Event received that is superseded by one or more active events + Active_Independent --> Active_Dependent : All superseding events cleared + Active_Dependent --> Active_Independent : Superseding event received + Active_Independent --> Persistent_Event : Persistence time reached + Active_Independent --> Filtered_Out : Clear message received + Active_Dependent --> Filtered_Out : Clear message received + Persistent_Event --> [*] : New event declared and sent to the next stage of the correlation process + +``` + +Figure 1/M.2140 – Persistence analysis for standing conditions. A state transition diagram showing the lifecycle of events. It starts with two entry points: 'Event received that supersedes all active events' leading to 'Active & Independent' state, and 'Event received that is superseded by one or more active events' leading to 'Active & Dependent' state. Transitions include 'All superseding events cleared' (Independent to Dependent), 'Superseding event received' (Dependent to Independent), 'Persistence time reached' (Independent to Persistent Event), and 'Clear message received' (both Independent and Dependent to Filtered Out). The 'Persistent Event' state leads to 'New event declared and sent to the next stage of the correlation process'. A small code 'T0411740-99' is in the bottom right. + +**Figure 1/M.2140 – Persistence analysis for standing conditions** + +In the case of an intermittent phenomenon, a standing condition may be raised and cleared repeatedly at the earliest stage of correlation. However, the generic event correlation model in 5.2 defines four stages of event correlation with each successive stage operating over longer time periods. This staging of the correlation process allows intermittent standing conditions can be declared persistent. + +For transient conditions, persistence analysis consists of measuring the frequency of events and when the frequency is high enough, declaring the condition persistent and sending an event notification forward. + +Persistence analysis is not appropriate for all types of conditions. If a certain condition type or state value is unlikely to be cleared or changed soon after it is reported, then persistence analysis can be bypassed, by setting the required persistence time for that condition type to zero. + +### 5.1.4 Dependencies + +Dependencies are relationships between equipment components and/or transmission media determined by the topology of the network and the way that trails are provisioned. These relationships can be used to determine where the failure or degradation of one resource will result in the failure or degradation of other dependent entities. Dependency relationships can also be used to determine where events detected at one resource indicate a condition present at another resource. For example a trail is dependent on the equipment that terminates the trail at either end and on any server trails that carry it. It is these dependency relationships that allow events detected at one resource to be correlated with events detected at dependent resources. + +Dependency information is created during the engineering process and the provisioning process by Configuration Management. It must be available to the appropriate Performance Management and Fault Management MAFs to enable Network Event Correlation. Interfaces between Configuration Management MAFs and Performance and Fault Management MAFs provide this dependency information. Fault Management MAFs need dependency information in real-time. Performance Management MAFs need dependency information in near real-time. Both require near real-time updates, when dependency information changes. The interfaces that provide dependency information must be automated. + +Dependencies are evaluated by following these steps: + +- 1) adding dependency relationship information to event information received in notifications; +- 2) then selecting all notifications for entities that support the same dependent resource; +- 3) performing an event comparison to filter out redundant notifications; +- 4) and combining related notifications of the same importance in light of the relationship information that was added. + +### 5.1.5 Patterning + +Patterning is the correlation of events across the many supported resources of a supporting resource to infer the occurrence of unreported events on the supporting resource. Patterning is done to compensate for potential loss of communication with NEs or other OSs in the TMN and the resulting loss of notifications for the supporting resource. This method can also be used to infer events affecting unmonitored, common resources in the network, such as cables, conduits, and power sources. + +When a pre-set fraction of all provisioned supported resources have indications of a given type logged against them, then an indication is generated on the supporting resource which may supersede the individual indications on the supported resources. + +Patterning requires a database of the dependency relationships between managed resources including unmonitored resources. Patterning may be done recursively to infer trouble with a resource such as a conduit or power supply from indications in many indirectly supported resources (as depicted in Figure 2). + +![Diagram illustrating the patterning of events. A central supporting resource (hatched circle) is connected to five supported resources (circles). The supported resources are connected to event notifications (black circles) or no event notifications (white circles). The diagram shows that if a certain number of supported resources have event notifications, an event is inferred on the supporting resource. A legend defines the symbols: a white circle for a supporting resource, a white circle for supported resources, a black circle for an event notification received, a white circle for no event notification received, and a hatched circle for an event inferred. The text 'T0411750-99' is visible in the bottom right corner of the diagram area.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +Diagram illustrating the patterning of events. A central supporting resource (hatched circle) is connected to five supported resources (circles). The supported resources are connected to event notifications (black circles) or no event notifications (white circles). The diagram shows that if a certain number of supported resources have event notifications, an event is inferred on the supporting resource. A legend defines the symbols: a white circle for a supporting resource, a white circle for supported resources, a black circle for an event notification received, a white circle for no event notification received, and a hatched circle for an event inferred. The text 'T0411750-99' is visible in the bottom right corner of the diagram area. + +**Figure 2/M.2140 – Patterning of events** + +## 5.2 Generic event correlation model + +To correlate events of diverse types from multiple technologies across a large managed network the event correlation processes described in 5.1 must be performed many times with the results of one process becoming the input to the next process. As correlation proceeds, dependency information is added to events and some event detail is removed resulting in increasing levels of abstraction. + +The following generic event correlation model defines four stages of event correlation processing. Figure 3 shows the correlation processes present at each stage. It also shows the data stored at each stage and the data passed upward from one stage to the next. + +### **5.2.1 Stage 0** + +At the lowest level, anomalies, defects, and State Changes are detected in monitored resources on the order of milliseconds and usually reported to the appropriate Stage 1 correlation process within one second or sooner. + +### **5.2.2 Stage 1** + +At the first stage, anomaly, defect, and state change information is received. Anomalies are accumulated. Defect detections and terminations may be subjected to a brief persistence analysis. Failures are declared and faults are cleared based on the persistence or persistent absence of defects. State Changes may also be subjected to a brief persistence analysis. Performance parameters are calculated based on the occurrence of anomalies and defects. Intermediate values of performance parameters, during the data collection interval, are compared to thresholds periodically as they are accumulated and TCAs are generated if the threshold is reached or exceeded. The Stage 1 correlation process generates the following sorts of events: + +- Failure declarations. +- Fault clears. +- State Changes. +- Performance parameter values. +- TCAs on performance parameters. + +### **5.2.3 Stage 2** + +At the second stage of the correlation process, events in the same category within a local domain are received and dependency information is added to them based on information stored in a database containing the dependency relationships between equipment components and in some cases local network connectivity. These events are then selected for comparison based on common dependencies (such as receiving power from the same immediate source or a payload signal from the same source) and correlated. A local persistence analysis is performed and transient or redundant events are filtered out. The result of the local correlation process is called an indication and should be stored, available to other processes, and reported automatically to the third stage of the correlation process. These indications provide a reliable abstraction of the nature of a persistent fault or impairment (degradation) within the local domain. Indications may also be exchanged between network operators to facilitate fault localization. + +### **5.2.4 Stage 3** + +At the third stage of the correlation process, indications in the same category are received from each local domain and dependency information is added to them based on information stored in a database containing the network-wide dependency relationships between NEs or subnetwork connections and end-to-end facilities or circuits. These indications are then selected for comparison based on common dependencies (such as receiving a payload signal from the same source) and correlated. Redundant indications are filtered out. No persistence analysis is required at Stage 3. Instead updated indications are sent when new information changes the root cause information for a fault or impairment. Indications that are not filtered out should be stored, available to other processes, and reported automatically to the fourth stage of the correlation process. These indications provide a reliable abstraction of the nature of a persistent fault or impairment (degradation) based on current information from a broad category of events. + +### **5.2.5 Stage 4** + +At the fourth and final stage of the correlation process, independent, non-redundant indications from all categories are received from the network-wide Stage 3 correlation processes. Dependency information is added to them based on information stored in a database containing the network-wide + +dependency relationships between end-to-end facilities or circuits and the physical resources, such as cables, conduits and rights-of-way. These indications are then selected for comparison based on common dependencies (such as common routing) and correlated. Trouble patterning is done to infer troubles on common resources that are not directly monitored, or on resources that may be unmonitored due to failures in the TMN. Real-time information input from external trouble reports and other relevant sources may be included in this final stage of event correlation. A final persistence analysis is performed and transient or redundant events are filtered out. Indications that are not filtered out should be stored, available to other processes, and reported automatically to the trouble ticket administration process. Additionally, if the trouble is localized to an external network operator then it should be reported automatically to the trouble report handling process of the external network operator. The indications that survive the Stage 4 correlation process provide a reliable and definitive statement of the nature of a persistent fault or impairment (degradation) based on current information from all sources. + +![](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +| Stage | Information Reported | Correlation Processes | Data Stored | +|---------|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| Stage 4 | Unique Work Item

Independent Indications
(network-wide non-redundant) | Persistence Analysis
Patterning
Selection
Add Dependency Information | Dependencies on unmonitored resources
precedence of indication types | +| Stage 3 | Indications
(locally non-redundant) | Comparison
Selection
Add Dependency Information | Facility hierarchy
Facility-to-circuit mapping | +| Stage 2 | Failures (Alarms)
Performance Parameter Values
Threshold Crossing Alerts | Persistence Analysis
Comparison
Selection
Add Dependency Information | Local trail hierarchy
Local topology
Equipment, communications alarm precedence | +| Stage 1 | Anomalies
Defects
State Changes | Persistence Analysis
Comparison
Selection
Add Dependency Information | Equipment relationships
Failure definitions
Performance parameter definitions | +| Stage 0 | | Reporting
Detection | Defect definitions
Anomaly definitions
Detection mechanisms | + +T0411760-99 + +**Figure 3/M.2140 – Generic event correlation model** + +## 5.3 Surveillance operations flows + +Information from NEs of interest to Transport Network Event Correlation can be classified into three categories. + +- 1) Failure declarations, fault clears and State Changes. +- 2) Threshold Crossing Alerts (TCAs). +- 3) Transport performance parameter values. + +These three categories of information are the source material for three surveillance operations flows. At Stage 2 each of these categories of data are received by different MAFs and correlated separately within each local domain. A local domain is the span of control of each Management System that + +performs that MAF. For each of the three flows, the Stage 2 MAFs correlate the notifications from Stage 1 in the local domain to produce an intermediate output, called an indication, for further correlation at Stage 3. + +The concept of an indication has been used for each Interaction between Stage 2 and Stage 3 MAFs and is consistent across the three surveillance operations flows. Table 1 introduces the indication terminology. + +**Table 1/M.2140 – Indication types** + +| Surveillance Flow | Indication Type | +|--------------------------|------------------------| +| Alarm Surveillance | Fault Indication | +| TCA Surveillance | Impairment Indication | +| Trend Analysis | Trend Indication | + +In each flow, the Stage 2 MAF will produce one indication for each underlying condition in the network. The indication will contain the best information about the nature, location and severity of the condition available from the notifications within the local domain. + +The definition of indications is crucial for the interoperation of local and network-wide systems. The indication is not just an NE notification that has made it through a filter at Stage 2. It is a statement by the applicable Stage 2 MAF that it has observed a significant condition in its domain. The information in the indication may be drawn directly from one or more NE notifications or it may be very indirectly related to the individual NE notifications. In either case, the Stage 3 recipient of the indication (whether a person or a machine) must be prepared to receive the indication and act on it appropriately. Without a common definition of indications, the job of Network Event Correlation cannot be divided between Stage 2 and Stage 3 and an efficient exchange of reliable information between network operators will not be possible. This Recommendation proposes a common definition for each of these indications, allowing a partitioning of Network Event Correlation MAFs into stages. + +At Stage 3 Indications of each category are received from multiple local domains. The indications are correlated based on all of the information available from all local domains. + +The three surveillance operations flows are brought together at Stage 4 that culminates in a single work item from Network Fault Localization. Table 2 presents suggested timing criteria for each of the three surveillance operations flows. These criteria specify bounds on the persistence times to be used at each stage of event correlation. The essential features of the suggested criteria are that each of the three flows occurs at different time-scales and that later stages have longer persistence times than earlier stages within each flow. + +**Table 2/M.2140 – Suggested event timing criteria** + +| Flow | Alarm Surveillance | TCA Surveillance | Trend Analysis | +|-------------|---------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------------------| +| Stage 0 | anomaly counts and defect detection < 1 second | anomaly counts and defect detection < 1 second | anomaly counts and defect detection < 1 second | +| Stage 1 | equipment < 3 seconds
communications 2-3 seconds
environmental < 3 seconds
fault clears < 20 seconds | 15-minute TCA < 1 minute | 15-min value 15 minutes
24-hour value 24 hours | +| Stage 2 | fault indication 10-30 seconds | impairment indication 1-3 hours | trend indication 2 hours – 30 days | +| Stage 3 | no persistence analysis | no persistence analysis | no persistence analysis | +| Stage 4 | work item 30-150 seconds | work item 1-5 hours | work item 2 hours – 30 days | + +## 5.4 Implementation considerations + +For large public networks, any implementation of event correlation must have the following characteristics: + +- Scalable: Some network troubles can cause the generation of thousands of event reports and these event reports can come from multiple Network Elements. This need implies also that the event correlation processes need to be both fast and use computing resources efficiently. +- Robust: Some event notifications that should be generated by a given trouble may not be generated or may not be received by a management system. False notifications may also be generated under some circumstances. The event correlation implementation must be robust enough to deal with missing or false event reports. +- Layered: TMN-compliant management system architectures depend on multiple systems such as element managers, domain managers and inter-domain managers. To reduce the volume of event notifications that must be processed by higher level and multi-domain management systems, domain-specific event correlation should take place at each stage of event correlation and only summarized results should be sent to higher level management systems. +- Flexible: Large public networks require constant reconfiguration. This activity may be caused by customer orders, network growth or technology changes. The event correlation process, which must have knowledge of the network configuration, must be able to accommodate these changes and keep up-to-date with the current network configuration. If maintenance activity, such as removal of transport links from service, would affect event correlation, then this information must be available to the event correlation process and must be utilized by that process. + +# 6 The transport network event correlation MAF interaction diagram + +The following diagram (Figure 4) is presented in the style of Appendix I/M.3400 [4]. Each object represents a single MAF. The first line of text in each object is the function group to which the MAF belongs. The number in each object is the number of the subclause pertaining to the MAF, the text following the number is the name of the MAF. Each arrow corresponds to the flow of information between MAFs. The numbers on the arrows correspond to numbered descriptions of each interaction that follow the diagram. The stages of event correlation are represented by the vertical alignment of the MAF objects. + +Following each interaction description is a list of Associated Data, which contains a list of the most important data items that are conveyed in each interaction. + +The Transport Network Event Correlation MAF Interaction Diagram shows the relationships among the MAFs for the purpose of event correlation. It includes all MAFs involved in event correlation for network surveillance and maintenance. It includes MAF from Performance Management, Fault Management, and Configuration Management to create a complete picture of Network Event Correlation. + +At Stage 0 there are three sources of events for correlation. Three distinct operations flows can be seen: + +- the Alarm Surveillance Flow: interactions 1, 2, 3, 4, 5, 6; +- the TCA Surveillance Flow: interactions 7, 8, 9, 14; +- the Trend Analysis Flow: interactions 10, 11, 12, 13, 14. + +These three flows come together in Stages 3 and 4. The Trend Analysis Flow is filtered by Data Aggregation and Trending and passed on to Network Performance Monitoring Event Correlation and Filtering where it is correlated with the TCA Surveillance Flow. All network degradation and failure information is correlated by Network Fault Localization. + +![Figure 4/M.2140 – Transport network event correlation interactions. A diagram showing five stages (Stage 0 to Stage 4) of event correlation across three management domains: Performance Management, Fault Management, and Configuration Management. Arrows indicate the flow of information between different Management Information Functions (MIFs) within and across these domains.](10781f43062bf3e9601a1e086710556c_img.jpg) + +The diagram illustrates the flow of event correlation across five stages (Stage 0 to Stage 4) and three management domains: Performance Management, Fault Management, and Configuration Management. + +- Stage 0:** + - Performance Management: Performance Monitoring 7.1 Detection, Storage, Counting, and Reporting + - Fault Management: Alarm Surveillance 8.1 Failure Event Detection and Reporting + - Configuration Management: Status and Control 9.1 Notification of State Changes by NEs +- Stage 1:** + - Performance Management: Performance Monitoring 7.3 Performance Monitoring Data Accumulation (receives from 7.1) + - Fault Management: Alarm Surveillance 8.2 Alarm Reporting (receives from 8.1) + - Configuration Management: Status and Control 9.2 NE(s) Status and Control (receives from 9.1) +- Stage 2:** + - Performance Management: Performance Monitoring 7.4 NE(s) Trend Analysis (receives from 7.3) + - Fault Management: Alarm Surveillance 8.3 Alarm Correlation and Filtering (receives from 8.2) + - Configuration Management: (No MAF listed) +- Stage 3:** + - Performance Management: Performance Monitoring 7.5 Data Aggregation and Trending (receives from 7.4) + - Fault Management: Alarm Surveillance 8.4 Network Fault Event Analysis Including Correlation and Filtering (receives from 8.3) + - Configuration Management: (No MAF listed) +- Stage 4:** + - Performance Management: Performance Monitoring 7.7 Network Performance Monitoring Event Correlation and Filtering (receives from 7.5 and 7.6) + - Fault Management: Fault Localization 8.5 Network Fault Localization (receives from 8.4) + - Configuration Management: (No MAF listed) + +Additional MAFs and interactions shown: + +- Performance Monitoring 7.2 NE(s) Performance Characterization (receives from 7.1, sends to 7.3 and 7.7) +- Performance Monitoring 7.6 NE(s) Threshold Crossing Alert Processing (receives from 7.2, sends to 7.7) +- Interactions 1-14 are indicated by numbered arrows between the various MAFs. + +Figure 4/M.2140 – Transport network event correlation interactions. A diagram showing five stages (Stage 0 to Stage 4) of event correlation across three management domains: Performance Management, Fault Management, and Configuration Management. Arrows indicate the flow of information between different Management Information Functions (MIFs) within and across these domains. + +Figure 4/M.2140 – Transport network event correlation interactions + +- 1) Defect detections and terminations are sent by Failure Event Detection and Reporting to Alarm Reporting. + +###### **Associated Data:** + +Managed Resource + +Defect Type + +Detection/Termination Indicator + +- 2) Alarms are sent by instances Alarm Reporting in one or multiple NEs to Alarm Correlation and Filtering. + +###### **Associated Data:** + +NE ID +Managed Resource +Event Type +Probable Cause +Time & Date Stamp + +- 3) State Change Notifications are sent to NE(s) Status and Control. + +###### **Associated Data:** + +NE ID +Managed Resource +Administrative State +Operational State + +- 4) State Changes of interest to Network Event Correlation are forwarded to Alarm Correlation and Filtering in Fault Management. + +###### **Associated Data:** + +NE ID +Managed Resource +Administrative State +Operational State + +- 5) Fault indications are sent from multiple instances of Alarm Correlation and Filtering to Network Fault Event Analysis Including Correlation and Filtering. + +###### **Associated Data:** + +NE ID +Managed Resource +Event Type +Service Affect +Probable Cause +Severity +Fault Location +Time & Date Stamp + +- 6) Independent, non-redundant fault indications are sent from Network Fault Event Analysis Including Correlation and Filtering to Network Fault Localization. + +###### **Associated Data:** + +NE ID +Managed Resource +Event Type +Service Affect +Probable Cause +Severity +Fault Location +Time & Date Stamp + +- 7) Performance anomaly and defect information is provided to NE(s) Performance Characterization within each NE. +**Associated Data:** +NE ID +Termination Point ID +Performance Anomaly +Performance Defect +Direction Of Transmission +- 8) Threshold Crossing Alerts are sent from multiple NEs to NE(s) Threshold Crossing Alert Processing. +**Associated Data:** +NE ID +Termination Point ID +PM Parameter Name +PM Parameter Value +Direction Of Transmission +- 9) Impairment indications are sent from multiple instances of NE(s) Threshold Crossing Alert Processing to Network Performance Monitoring Event Correlation and Filtering. +**Associated Data:** +NE ID +Termination Point ID +PM Parameter Name +Direction Of Transmission +Observed TCA Frequency +- 10) Performance parameter values are sent from multiple instances of NE(s) Performance Characterization in various NEs to Performance Monitoring Data Accumulation. +**Associated Data:** +NE ID +Termination Point ID +PM Parameter Name +Direction Of Transmission +Data Collection Interval End Time +PM Parameter Value +- 11) Performance Monitoring Data Accumulation sorts and organizes the performance parameter values and makes them available to NE(s) Trend Analysis. +**Associated Data:** +NE ID +Termination Point ID +PM Parameter Name +Direction Of Transmission +Data Collection Interval End Time +PM Parameter Value +- 12) Trend indications are sent from multiple instances of NE(s) Trend Analysis to Data Aggregation and Trending. +**Associated Data:** +NE ID +Termination Point ID +Pattern Code +Pattern Descriptors + +- 13) Independent, non-redundant trend indications are sent on to Network Performance Monitoring Event Correlation and Filtering + +###### **Associated Data:** + +NE ID +Termination Point ID +Pattern Code +Pattern Descriptors + +- 14) Independent, non-redundant impairment indications and trend indications that are not tied to redundant impairment indications are forwarded to Network Fault Localization. + +###### **Associated Data:** + +| | | | +|---------------------------|----|----------------------| +| NE ID | or | NE ID | +| Termination Point ID | | Termination Point ID | +| PM Parameter Name | | Pattern Code | +| Direction Of Transmission | | Pattern Descriptors | +| Observed TCA Frequency | | | + +# 7 Performance management + +Transport Performance Management uses transport performance monitoring data to detect degraded performance of transport facility resources that is either service affecting already, or that is potentially service affecting in the near future. When degraded performance is detected and persists, proactive maintenance is begun to fix the facility component that is causing the degraded performance. + +Proactive maintenance is triggered by one of the following occurrences in the performance monitoring measurements: + +- a level of degradation that directly impacts service performance; +- measurements that exceed performance quality guarantees or objectives; +- a change for the worse observed; +- a pattern indicates impending onset of more severe degradation or complete failure. + +Transport Performance Management deals with degradation that has not yet interrupted service completely and measurements may vary from one moment to the next. Frequently, when degraded performance is detected it quickly fades, caused by some temporary phenomena external to the network. Because of these characteristics of transport performance data, events are examined over a longer time than they are when service is interrupted. Evidence of degradation is withheld at each stage of event correlation until there is confidence that the true severity of the problem is known, that the degradation is persistent, or that the source of the problem is clear, before the next stage is notified. The philosophy is that delayed reliable information is preferable to immediate unreliable information. This is in contrast to the Alarm Surveillance philosophy stated in clause 8. + +There are two approaches to Transport Performance Management. The Trend Analysis approach looks at all of the performance parameter values. The TCA Surveillance approach only considers periods of exceptionally poor performance. The Trend Analysis approach is more complete, but is more costly. The TCA Surveillance approach is less costly, but less flexible, less sensitive and less sophisticated. Both have their place in different network contexts. Often times, the Trend Analysis approach is applied only for high signal rate facilities or premium services. In other cases, Trend Analysis may be triggered by the detection of exceptionally poor performance by the TCA Surveillance approach. Both approaches are covered in this clause. The TCA Surveillance Flow and the Trend Analysis Flow and their use of the MAFs defined in this clause are presented in this clause. + +## **7.1 Detection, counting, storage and reporting** + +Detection, Counting, Storage, and Reporting is a Stage 0 function that monitors the status and behaviour of resources within an NE for conditions that impact performance. For transport networks, this MAF monitors the incoming (and in some cases outgoing) signals at each port in a Network Element to detect and track anomalies and defects in the signal. Not all monitored trails must be terminated at the NE. + +An anomaly is a discrepancy between the actual and desired characteristics of an item. For this MAF the items are monitored signals. An anomaly may or may not affect the ability of an item to perform a required function. + +Examples of anomalies are: + +- bit error detection anomalies: line coding errors, parity or other error detection code errors; +- synchronization related anomalies: controlled slips for PDH paths and pointer justifications for SDH paths. + +A defect is a limited interruption in the ability of an item to perform a required function. It may or may not lead to maintenance action depending on the results of additional analysis. Successive anomalies causing a decrease in the ability of an item to perform a required function may result in the detection of a defect. Examples of defects are: + +- loss of information defects: Loss Of Signal (LOS), Loss Of Pointer (LOP), Alarm Indication Signal (AIS); +- framing defects: Out Of Frame (OOF), Severely Errored Frame (SEF) and Loss Of Frame (LOF); +- incorrect information defects: incorrect or invalid variable values in frame or cell overhead in successive frames or cells. + +## **7.2 NE(s) performance characterization** + +NE(s) Performance Characterization is a Stage 1 function that is usually performed by the NE. This MAF uses the anomalies and defects from Detection, Counting, Storage, and Reporting to compute various Performance Monitoring parameters such as Errored Seconds, Severely Errored Seconds and Unavailable Seconds. This is done for each monitored trail. NE(s) Performance Characterization accumulates each of the parameters over 15-minute intervals and separately over 24-hour intervals. These counts are updated at the end of each second based on the anomaly and defect information from Detection, Counting, Storage and Reporting. Once an interval ends, the total count of each parameter is stored temporarily as historical Performance Monitoring data. The NE can be instructed to report current or historical data on demand or on a scheduled basis. These performance parameter values are used by NE(s) Trend Analysis. + +For each parameter, thresholds are set. There is one for 15-minute intervals and one for 24-hour intervals. If a count reaches or exceeds its threshold, then a Threshold Crossing Alert is generated and sent to the NE(s) TCA Processing MAF. + +## **7.3 Performance monitoring data accumulation** + +Performance Monitoring Data Accumulation is a Stage 1 function that receives performance parameter values for each data collection interval, sorts them by monitoring point and stores it for use by other MAFs. This data is then used by NE(s) Trend Analysis as well as other MAFs (not included in Network Event Correlation) involved in characterizing long-term network performance and producing quality of service reports. + +## 7.4 NE(s) trend analysis + +NE(s) Trend Analysis is a Stage 2 function that analyses the raw performance monitoring data gathered from NEs to detect trends, or more generally, patterns of performance monitoring data that indicate the presence or impending onset of a service affecting impairment that requires maintenance action to correct. For most applications, 15-minute data is used to allow rapid detection of trends. + +NE(s) Trend Analysis concentrates on uncovering patterns in the performance parameter values that indicate the cause of the impairment in more detail than NE(s) TCA Processing can provide. For example, a certain pattern may indicate that a specific component of a repeater is going bad. It also concentrates on cases when the data values are not off-normal enough to trigger TCAs, but the pattern indicates that the problem will worsen. + +NE(s) Trend Analysis examines the performance parameter values from NEs with no reference to the particular trail that the monitoring point supports. The only information that is needed is the type of trail that the monitoring point supports. The data is analysed by one or more pattern recognition algorithms to search for matches to rules, profiles, or other criteria that indicate the presence or impending onset of a condition that requires maintenance action. When a match is made, a trend indication is issued. + +The trend indication will include the pattern code for the trend or pattern detected, parameters (not PM parameters) characterizing the pattern detected and measures of the goodness of fit to the pattern detected. The trend indication will apply only to a single monitoring point. No correlation across monitoring points is included in this MAF. + +## 7.5 Data aggregation and trending + +Data Aggregation and Trending is a Stage 3 correlation function that receives trend indications from multiple instances of NE(s) Trend Analysis in different local domains. Trending is done at Stage 2 by NE(s) Trend Analysis on data from individual monitoring points to find patterns in raw performance monitoring data that may have unique significance for a specific type of equipment or transmission technology. When an impairment occurs, performance monitoring data will be collected at multiple points along the impaired trail. One or more instances of NE(s) Trend Analysis will try to find a pattern in the data at each of these monitoring points. + +Data Aggregation and Trending determines what trail is affected by each trend indication that it receives. If it receives more than one for a given trail, it also performs correlation along a trail to arrive at the most descriptive and diagnostic trend information for each impairment on a trail. These trend indications are sent to Network Performance Monitoring Event Correlation and Filtering. + +No correlation among different trails is included in this MAF. + +## 7.6 NE(s) TCA processing + +NE(s) TCA Processing is a Stage 2 function that receives Threshold Crossing Alerts (TCAs), based on 15-minute interval performance monitoring data, from NE Performance Characterization at Stage 1. It correlates the TCAs across multiple monitoring points on a trail and over time. It filters out redundant or symptomatic TCAs and sectionalizes impairments. For each impairment, it forwards a single reliable impairment indication to Network Performance Monitoring Event Correlation and Filtering at Stage 3 for correlation on a network-wide basis. + +NE(s) TCA Processing correlates TCAs generated by NEs within a single period to filter out redundant or symptomatic TCAs related to a given trail. It also correlates TCAs from low order (lower rate) trails to the high order (higher rate) supporting trails within its local domain. It will suppress TCAs from a low order trail when a TCA from a higher order trail indicates an impairment that would cause the low order trail TCA as a symptom. For each 15-minute interval, NE(s) TCA Processing will allow only one root cause TCA to pass through its filter for each impairment. + +The root cause TCA for a given impairment should be the one that best indicates the cause, location, and severity of the impairment. Fortunately, for the vast majority of impairments, one TCA, out of the many that may be received, is clearly the best on all three criteria. + +TCAs apply to one of the two directions of a bidirectional service. The two directions can be impaired independently and NE(s) TCA Processing must distinguish the affected direction of transmission. The different types of TCA can be ordered by severity. Finally, TCAs can be generated at multiple points along a trail. For this reason, NE(s) TCA Processing must record where TCAs come from and construct a notion of upstream and downstream along a trail in one or the other direction of transmission. + +### 7.6.1 TCA correlation rules + +The following rules specify how TCAs are correlated within each 15-minute interval. + +- 1) Any TCA on a trail shall suppress downstream near-end TCAs and far-end TCAs relating to the same direction of transmission on lower order trails carried by that trail. +- 2) Among TCAs for the same trail, TCAs of greater severity shall suppress TCAs of lower severity relating to the same direction of transmission. +- 3) Among TCAs of the same type (parameter name) for the same trail, near-end TCAs shall suppress downstream near-end TCAs and all far-end TCAs relating to the same direction of transmission. +- 4) Among TCAs of the same type (parameter name) for the same trail and in the absence of near-end TCAs, the first received far-end TCA shall suppress subsequent far-end TCAs relating to the same direction of transmission. + +Far-end data for a given trail is read from the overhead, not directly observed. As a result, far-end data values for the same direction of transmission will be the same at the trail termination point and at all intermediate performance monitoring points along the trail. All far-end TCAs are equally valid but only one should be allowed to become a root cause TCA, and then only if there are no near-end TCAs for that direction of transmission on the trail and no TCAs on supporting higher order trails. + +### 7.6.2 Persistence analysis + +The purpose of persistence analysis is to distinguish between persistent impairments, which should result in maintenance action, and non-persistent impairments, which should be ignored. + +Non-persistent impairments are infrequent and of short duration (e.g. affecting only one or two 15-minute intervals). When an impairment is not persistent there is no reason to believe that a subsequent impairment will occur or that any repair action will improve the expected quality of the transmission system in the future. Non-persistent impairments are usually caused by external events such as human activity or adverse weather conditions. + +Persistent impairments are long duration or intermittent but frequent occurrences of the same impairment. When a persistent impairment is observed there is reason to believe that the impairment will continue or recur and that some component of the transmission system is at fault. + +NE(s) TCA Processing checks to see that an impairment is persistent by using a sliding window algorithm. It works by recording the presence of an impairment as represented by the root cause TCA in successive intervals and requiring the impairment to be present in three or more intervals within a 4 to 12 interval window before declaring an impairment indication. The window length and number of impaired intervals required can be set based on performance monitoring policy, but they should not vary from trail to trail. If greater or lesser sensitivity to the degree of impairment is desired, the threshold settings on the individual PM parameters in NE(s) Performance Characterization should be modified. The impairment indication is cleared again when the number of impaired intervals in the window falls below the number required. + +This persistence analysis turns many root cause TCAs into a single, reliable standing condition. The impairment indications and associated clears are sent to Network Performance Monitoring Event Correlation and Filtering. + +## **7.7 Network performance monitoring event correlation and filtering** + +Network Performance Monitoring Event Correlation and Filtering is a Stage 3 function that has two event inputs. It receives impairment indications from multiple instances of NE(s) TCA Processing. It receives trend indications from Data Aggregation and Trending. Network Performance Monitoring Event Correlation and Filtering has a larger span of control than NE(s) TCA Processing does. For this reason, it performs some similar correlation functions. + +This MAF does three types of event correlation. The first is correlation of impairment indications from different local domains relating to the same trail. The second is correlation of impairment indications from one trail to indications on another trail that carries it. The third is correlation of any trend indication that exists to the impairment indication for the trail that is determined to be the root cause of an impairment. + +The output of this MAF is root cause indications (either impairment indications or trend indications) that contain the best information about the severity, location and cause of degradation on a trail. These root cause indications are sent to Network Fault Event Analysis, Including Correlation and Filtering. + +### **7.7.1 Correlation of impairment indications along a trail** + +This is similar to the correlation of individual TCAs from different monitoring points (within a local domain) on the same trail that takes place in NE(s) TCA Processing. The difference is that Network Performance Monitoring Event Correlation and Filtering correlates impairment indications (which are a product of persistence analysis of many TCAs) and it correlates over a larger domain. The process, however, is the same. + +The two directions of transmission for a trail are treated separately. Impairment indications that are of a lower or equal severity than another, declared upstream, are superseded. If there are multiple impairment indications based on far-end data, then all but the first received are superseded. + +### **7.7.2 Correlation of impairment indications among related trails** + +Correlation of impairment indications among trails that have a carrying/carried relationship also has an analogous function in NE(s) TCA Processing. Just as in NE(s) TCA Processing, correlation along a trail and among related trails can be done simultaneously. + +Impairment indications on a lower order trail are superseded, if there is an impairment indication on a higher order trail that carries the lower order trail. + +The procedure for one impairment indication superseding another depends on the order in which the impairment indications are received and processed. If the superseding impairment indication is processed earlier, the subsequent superseded impairment indication will be filtered out and no message will be sent to Network Fault Event Analysis, Including Correlation and Filtering for the superseded impairment indication. If the superseding impairment indication is processed later, an updated impairment indication is set to Network Fault Event Analysis, Including Correlation and Filtering reflecting the information in the superseding impairment indication. + +### **7.7.3 Correlation of trend indications with impairment indications** + +In order to understand the recommended approach to the correlation of trend indications to impairment indications, it is important to consider that for a given impairment, it is possible to receive a trend indication by itself, an impairment indication by itself, or both. If both are triggered, then they may be triggered at widely different times. For this reason, no persistence analysis is + +recommended to hold on to one indication while waiting for another. Instead, the two kinds of indication will be reported separately. This may seem contrary to the spirit of correlation, but delaying either category of performance indication long enough to correlate them effectively would withhold the information too long to support proactive maintenance. Furthermore, trend indication information and impairment indication information are so different in structure and semantics that combination of the two would be an artificial packaging exercise. + +Even without persistence analysis, redundant trend indications can be filtered out by correlating them with superseded impairment indications. Network Performance Monitoring Event Correlation and Filtering gets trend indications from Data Aggregation and Trending. A trend indication is said to correspond to an impairment indication if it is from the same direction of transmission of the same trail as the impairment indication. There are three cases to consider when correlating trend indications with impairment indications. + +- 1) A trend indication arrives before any corresponding impairment indication. In this case the trend indication is forwarded to Network Fault Event Analysis, Including Correlation and Filtering. +- 2) A trend indication arrives and corresponds to a root cause impairment indication. In this case the trend indication is forwarded to Network Fault Event Analysis, Including Correlation and Filtering. +- 3) A trend indication arrives and corresponds only to one or more superseded impairment indications. In this case the trend indication is superseded. + +# **8 Fault management** + +Fault Management deals with failures that have interrupted service completely or adverse conditions that are immediate threats to service. These fault events often require prompt maintenance action. The Alarm Surveillance Flow is designed to operate quickly to provide near-real time information for the maintenance process. Persistence analysis, required to filter out redundant or non-persistent events, is kept to a minimum (in the order of one minute). It is likely that the alarms that contain the best root cause information and are most significant will be received first. The Alarm Surveillance Flow takes advantage of this. However, there are cases when one stage of event correlation will provide incomplete information to the next stage and then update that information when more complete information is available. The philosophy is that, when service continuity is lost or under threat, prompt incomplete information is preferable to delayed complete information. This in contrast to the Transport Performance Management philosophy stated in clause 7. + +## **8.1 Failure event detection and reporting** + +Failure Event Detection and Reporting is a Stage 0 function that monitors resources within an NE for defects. Monitored resources include equipment components, software, incoming signals, power and timing signals. Defects are reported as soon as possible after their detection, often within milliseconds and always within a second. The specific defects and their definitions are dependent on the technology being monitored. + +## **8.2 Alarm reporting** + +Alarm Reporting is a Stage 1 function that receives defect information for resources within an NE from Failure Event Detection and Reporting. Defects may be subjected to a brief persistence analysis. Failures are declared based on the persistence of defects. Faults are cleared based on the persistent absence of defects. + +When a failure is detected, it is reported, usually as an alarm to Alarm Correlation and Filtering at Stage 2. These failures may directly affect service if there is no backup resource to assume the affected resource's function. If there is a backup resource, service will continue without immediate + +manual intervention1. Alarm Reporting is responsible for indicating in the alarm message whether or not the failure is directly service affecting or not. It also provides other information such as the type of fault condition, its severity, its location, and other attributes. + +When a fault is cleared, it is reported with a clear message to Alarm Correlation and Filtering at Stage 2. + +Alarm Reporting may perform some filtering of alarms and other events. For example, when there is a Loss of Signal (LOS) failure on a high rate signal the NE may suppress the reporting of Loss of Signal (LOS) and Alarm Indication Signal (AIS) alarms on carried lower rate signals. + +There are three different types of monitoring and therefore three types of fault. + +### **8.2.1 Equipment faults** + +Equipment monitoring monitors the various components of the NE, indicating when a component has failed or been removed. Equipment faults are always detected by the affected NE and are almost always reported by the affected NE. The NE usually sends an equipment alarm immediately without performing any persistence analysis. + +### **8.2.2 Communication faults** + +Communication monitoring monitors the incoming (and in some cases outgoing) signals at each port in the Network Element to detect failure conditions. Some examples of communication faults are Loss of Signal (LOS), Loss of Frame (LOF) and Alarm Indication Signal (AIS). All communications faults are declared as the result of a persistence analysis performed by Alarm Reporting. For instance, a Loss of Signal is declared when there has been no valid signal for 2-3 seconds (the actual definition is quite precise and out of the scope of this Recommendation). Some failures are based on measurements detected directly, others are based on measurements made by the NE at the other end of the trail and reported in the overhead part of the signal in the reverse direction of transmission. + +Communication faults always indicate that the problem is somewhere else, either in the transmission media, in an equipment component in an upstream NE, or occasionally another component of the same NE performing an upstream function. + +### **8.2.3 Environmental conditions** + +Environmental monitoring monitors environmental conditions, such as temperature, humidity, and the presence of smoke and compares the levels of these measurements to limits for each measurement. If the limit is exceeded a notification (usually an alarm) is reported. These conditions are external threats to the proper functioning of the entire Network Element. Some of the conditions monitored by an NE are related to electrical power (either standard or battery backup). Other conditions relate to the physical security or data security of the NE. For the purposes of this Recommendation, these are considered part of environmental monitoring. + +Environmental alarms are triggered independently of the detection of any equipment or communication fault. The limits should be set to trigger an environmental alarm before an equipment or communication fault occurs. This allows environmental alarms to provide early warning of trouble, so that proactive maintenance can occur before service is affected. + +## **8.3 Alarm correlation and filtering** + +Alarm Correlation and Filtering is a Stage 2 function that receives alarms (and other fault notifications, including State Changes) from multiple NEs within a local domain. It may correlate alarms based on network topology and circuit layout information. It filters out redundant or + +--- + +1 If service restoration requires manual intervention, then the resources used do not fit the definition of a backup resource and the fault is considered service affecting. + +symptomatic alarms and any non-persistent alarms. Its output is one fault indication for each trouble in its local domain, which contains the best information from the alarms that indicate the location, severity and type of the failure. + +### **8.3.1 Processing of equipment alarms** + +Since equipment alarms report the exact component that is at fault, they are the most precise of all alarms. When many alarms are received, it is usually an equipment alarm that provides the best root cause information. + +Equipment alarms from different NEs are always independent even if the failed components support the same trail. This is true even if an environmental fault has caused both equipment faults, because the two equipment components still must both be fixed. If more than one equipment alarm is received from the same NE, then they may not be independent. NEs usually prevent multiple equipment alarms from being triggered by the same underlying condition, but in some cases Alarm Correlation and Filtering must correlate equipment alarms from the same NE. This is done based on the equipment dependency relationships among all of the NE's components (bays, shelves, power supplies, timing generators, line cards, etc.). + +Alarm Correlation and Filtering must have this equipment dependency information for all of the NEs that it monitors in its local domain. Included in this information should be trail termination points directly supported by each equipment resource and the physical location of each NE. The dependency relationships will be slightly different for each NE due to the differences in the components installed to meet different customer needs. + +### **8.3.2 Processing of communication alarms** + +Communication alarms are detected when there is a problem with an incoming signal. The problem can be caused by an equipment fault, which will trigger an equipment alarm for the failed equipment from the NE. The problem can also be caused by a fault in a fibre, cable, or other transmission medium, which will not cause anything but communication alarms. Given this understanding, communication alarms are only important when they occur without related equipment alarms. If an equipment alarm is received, all downstream communication alarms on that trail must be superseded. This includes far-end communication alarms that are a result of the equipment fault. + +If no equipment alarms related to the trail are received, but communication alarms are received, then the cause of the fault is either: + +- outside of the local domain; +- some unmonitored piece of equipment; +- the transmission medium that carries the trail between equipment. + +In any of these three cases, the most upstream communication alarm will stand as an independent fault and will be the best root cause information available within the local domain. The other communications alarms will be filtered out. + +### **8.3.3 Processing of environmental alarms** + +Environmental alarms relate to an entire NE or all NEs at a given location, so they relate to many equipment components and many trails. For this reason environmental alarms should be given high priority. However, most environmental alarms only detect a potential threat and not the immediate effect on individual components or trails. Environmental alarms do not imply that any equipment has failed or any service has been affected. Service may be affected, but the environmental alarm itself will not state that. Also, if an environmental condition is affecting network components, it may not affect all of them, and it is important to retain information about network components that are in trouble. Thus it is important to separate environmental alarms from other alarms and not to filter out equipment and communication alarms that may or may not be caused by the environmental condition. + +Alarm Correlation and Filtering must maintain environmental conditions as independent faults, however, equipment faults and communication faults will be related or linked to potentially related environmental conditions by Network Fault Localization at Stage 4. + +### **8.3.4 Processing of state changes** + +In addition to alarms from NEs, Alarm Correlation and Filtering also receives administrative and operational State Changes from NE(s) Status and Control, a Stage 1 Configuration Management MAF. State Changes may provide additional information about the root cause of a condition in the network. State Changes also can serve as a back-up method of detecting faults. Administrative and operational State Changes should be treated like equipment alarms, since they always indicate a change in the ability of a resource to fulfil its function. + +The fact that one or more resources have entered the "locked" or "shutting down" administrative state, which can only occur through maintenance intervention, should be recorded in any related fault indication. This will allow a technician to distinguish the activity of another technician, when the administrative State Change is the root cause of a condition, from a resource failure. + +Operational State Changes from "enabled" to "disabled" result from a failure condition and will usually be accompanied by an alarm. In some cases an operational state change message will contain additional status information that may be useful for fault isolation and that is not contained in the accompanying alarm notification. If so, this information should be combined with the alarm information in the fault indication that is generated for the condition. If no such useful information is present in an operational state change notification, the notification can be superseded in the presence of alarms that explain the change in operational state. + +### **8.3.5 Correlation of alarms among related trails** + +In addition to correlating alarms along a trail, Alarm Correlation and Filtering includes correlation of alarms among related trails wherever possible. The opportunity to correlate among related trails exists whenever an instance of the Alarm Correlation and Filtering MAF will monitor more than one type of trail. This is usually true. The other requirement is that the instance of this MAF has access to trail configuration data that reveals how trails are related. Alarms on a supported trail will be superseded when they are correlated to alarms on an upstream supporting trail. There are two types of correlation between facilities. + +Alarm Correlation and Filtering correlates alarms of any type with any downstream alarms of any type on supported (client) facilities. This is done to eliminate symptomatic alarms. If the alarm at the lower level is less severe, then it is superseded. If the alarm at the lower level is more severe, then it remains an independent alarm because it is not fully explained by the higher level alarm. Another underlying condition is the likely cause of the lower level alarm. + +### **8.3.6 Persistence analysis** + +Persistence analysis has two purposes. One is to filter out alarms that are quickly followed by a clear notification from the NE. The other is to filter out alarms that are quickly explained by another related alarm that contains better information on the root cause and severity of the underlying condition. Once an alarm state has persisted for the required time without being cleared or superseded by the arrival of a related alarm that explains it, a fault indication is declared and sent to Network Fault Event Analysis, Including Correlation and Filtering at Stage 3. + +The required persistence should be long enough to allow for the correlation, at Stage 2, of all of the alarms triggered by a fault condition within the local domain in most circumstances and yet short enough to provide timely reporting to Stage 3. The range of 10 seconds to 10 minutes should allow enough flexibility, but should not be taken as a requirement. The trade-off between maximizing correlation and minimizing delay will be different depending on the number of affected customers or + +affected transmission capacity. The required persistence can be made shorter for faults that affect more capacity and longer for faults that affect less capacity. + +### **8.3.7 Declaring fault indications** + +Alarms that survive the persistence analysis are ready to be reported out of the Alarm Correlation and Filtering MAF to Network Fault Event Analysis, Including Correlation and Filtering at Stage 3. Alarm Correlation and Filtering generates a fault indication for each independent persistent alarm. If multiple related alarms were received that have the same severity or otherwise could not be filtered out then they are combined into a single fault indication. Specifically, when the first of the multiple alarms achieves the required persistence, all related, active alarms that have not been superseded will be combined into a single fault indication. + +The idea behind this approach is that as long as one of the alarms has persisted, then the underlying condition is persistent and requires prompt maintenance attention. The other related alarms that are active (not cleared) and independent (not superseded) provide additional information about the persistent underlying condition and should be included in the fault indication along with the first alarm that persists. This reduces the message traffic between Stage 2 and Stage 3 and reduces the processing load for Network Fault Event Analysis, Including Correlation and Filtering. + +## **8.4 Network fault event analysis, including correlation and filtering** + +Network Fault Event Analysis, Including Correlation and Filtering is a Stage 3 function. It receives fault indications from multiple instances of Alarm Correlation and Filtering for different local domains. Fault indications are correlated across the trail from end-to-end and among related trails. + +There is no persistence analysis subprocess in Network Fault Event Analysis, Including Correlation and Filtering. This is consistent with the Alarm Surveillance philosophy, stated in the first paragraph of clause 8, that when service continuity is lost or under threat, prompt incomplete information is preferable to delayed complete information. + +### **8.4.1 Correlation of fault indications along a trail** + +Any fault indication to reach Network Fault Event Analysis, Including Correlation and Filtering that is not related to an active indication already received, triggers a report to Network Fault Localization. Subsequent related indications will be superseded and filtered out if they are downstream on the same trail and of equal or lower severity. Subsequent related fault indications that are upstream on the same trail and of greater severity will supersede the previous fault indication and trigger an updated fault indication to be reported to Network Fault Localization. Subsequent related fault indications that are upstream on the same trail but of lower severity or downstream on the same trail, but of greater severity will remain independent and will trigger separate reports to Network Fault Localization. + +Note that fault indications based on far-end data read from the overhead in the signal in one direction of transmission must be correlated with the other (near-end) fault indications related to the opposite direction of transmission. Fault indications based on far-end data are considered to be downstream of all fault indications based on near-end data, because far-end data reflects conditions detected at the terminating equipment for the opposite direction of transmission. + +Clears to active independent fault indications are also passed through to Network Fault Localization. Clears to fault indications that have been filtered out in Network Fault Event Analysis, Including Correlation and Filtering will be filtered out and not forwarded to Network Fault Localization. + +### **8.4.2 Correlation of fault indications among related trails** + +In addition to correlation along a trail, Network Fault Event Analysis, Including Correlation and Filtering correlates fault indications among trails (circuits, facilities). + +A fault indication on a supporting trail supersedes downstream fault indications on supported (client) facilities. This is done to eliminate symptomatic fault indications from other local domains. If the fault indication at the lower level is less severe, then it is superseded. If the fault indication at the lower level is more severe, then it remains an independent fault indication, but the two indications are linked. Linking means that each indication is augmented with a pointer to the other as a related indication. + +The procedure for one fault indication superseding another depends on the order in which the fault indications are received and processed. If the superseding fault indication is processed earlier, the subsequent superseded fault indication will be filtered out and no message will be sent to Network Fault Localization for the superseded fault indication. If the superseding fault indication is processed later, an updated fault indication is set to Network Fault Localization reflecting the information in the superseding fault indication. + +## **8.5 Network fault localization** + +Network Fault Localization is a Stage 4 function. This is where all surveillance information comes together. Network Fault Localization receives fault indications from Network Fault Event Analysis, Including Correlation and Filtering. It receives impairment indications and trend indications from Network Performance Monitoring Event Correlation and Filtering. Real-time information input from external trouble reports and other relevant sources may be included in this final stage of event correlation. + +All three types of indication are correlated together. Any indication supersedes others that are downstream on the same or supported trail and of equal or less significance. Fault indications are the most significant indications followed by impairment indications and trend indications. + +If there is an active fault indication for a given trail, then related impairment indications and trend indications are superseded and prevented from generating independent trouble work items and are associated with the fault indication as detail information. If there is no fault indication for a trail, then the most severe and upstream impairment indication will stand as an independent indication with any corresponding trend indication information associated as detail information. If there is no impairment indication or fault indication, then a trend indication will stand as an independent indication. + +### **8.5.1 Patterning of indications** + +Patterning is the correlation of indications across the many supported (client) resources of a supporting resource to infer the occurrence of unreported events on the supporting resource. Patterning is done to compensate for potential loss of communication with NEs or other OSs in the TMN and the resulting loss of notifications for the supporting resource. This method can also be used to infer events affecting unmonitored, common resources in the network, such as cables, conduits, and power sources. When a pre-set fraction of all provisioned supported resources have indications of a given type logged against them, then an indication is generated on the supporting resource and the individual indications on the supported resources are superseded (except in the case of environmental conditions, see 8.5.2). Indications generated as a result of patterning should be distinctively labelled. + +An indication generated as a result of patterning is cleared, when enough of the contributing indications are cleared that the number of active contributing indications no longer meets or exceeds the pre-set fraction of all provisioned supported resources required to generate a pattern. An indication generated as a result of patterning is also cleared when a clear is received explicitly for the supported resource, following the recovery of a failed TMN communications link. + +Patterning requires a database of the dependency relationships between managed resources including unmonitored resources. Patterning may be done recursively to infer trouble with a resource such as a + +conduit or power supply from indications in many indirectly supported resources (as depicted in Figure 2 located in 5.1.5). + +### **8.5.2 Correlation of indications among related resources** + +In addition to correlation along and among trails, Network Fault Localization uses patterning to correlate indications on trails and other resources supported by the same unmonitored resource. This allows the generation of a single work item (trouble ticket) for a cable, or other unmonitored equipment or communications resource and the suppression of work items for each affected supported resource. + +Indications reporting environmental conditions are treated differently from indications reporting an equipment or communications condition, because the environmental condition may or may not actually affect the dependent resources. When an indication reporting an environmental condition is correlated to an indication on a dependent resource, the two indications are linked. Each indication remains independent but with a pointer to the other added prominently as additional information. + +Locations where NEs are housed can be treated as supporting the NEs and indirectly supporting facilities monitored by NEs. Equipment faults can be marked as related to environmental conditions existing at the location or NE that houses the reporting equipment component. Communication faults can be marked as related to any environmental condition existing at any location or NE that houses equipment that supports the facility impacted by the communications alarm. + +# **9 Configuration management** + +Status and Control is the group of MAFs in Configuration Management that relate to the tracking of the status of the network and its components. The two MAFs from this group that are important to Network Event Correlation are described below. These two MAFs are considered part of the Alarm Surveillance Flow because the state change information that they provide may indicate that a resource is completely inoperable and these State Changes are correlated with alarms at Stage 2. + +## **9.1 Notification of state changes by NEs** + +Notification of State Changes by NEs is a Stage 0 function that tracks state attributes of resources within a Network Element. When one of these states changes, this MAF sends a state change notification to NE(s) Status and Control at Stage 1. + +## **9.2 NE(s) status and control** + +NE(s) Status and Control is a Stage 1 function that tracks the states of resources within a local domain. Administrative and operational State Changes are of interest to Network Event Correlation; other State Changes are not. When NE(s) Status and Control is notified of an operational or administrative State Change, this MAF sends a notification to Alarm Correlation and Filtering in Fault Management for correlation with alarms. + +### **9.2.1 Operational state changes** + +A resource's operational State Changes from "enabled" to "disabled" when a condition occurs that renders the resource completely inoperable. Conditions that cause operational State Changes will almost always also trigger alarms for the same resource in Failure Event Detection and Reporting that will also be sent to Alarm Correlation and Filtering. Thus operational state change notifications will almost always be redundant with alarms. Yet State Changes enhance the robustness of Network Event Correlation by providing another backup method of detecting failures. Also there are cases when State Changes can provide additional useful information about a condition in the network. + +### **9.2.2 Administrative state changes** + +Administrative State Changes can only occur due to maintenance action. When the administrative state for a resource changes from "unlocked" or "shutting down" to "locked", the resource will cease to perform its function. Thus an administrative State Change can be service affecting. The locking of one resource may impact other resources that are dependent or downstream of the locked resource. When used properly, the administrative state for dependent and downstream entities are locked first to prevent alarms from being generated. When used improperly, the impacted resources become disabled while remaining in the unlocked administrative state and alarms are triggered in Failure Event Detection and Reporting. It is important to send administrative State Changes to Alarm Correlation and Filtering so that maintenance activity can be identified as the root cause of resulting conditions. + +The correlation of administrative State Changes with alarms will allow a technician to distinguish the activity of another technician from a resource failure in some situations. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c +size 8232 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7948bc3993a6ffaa0314f434c4bd5f256cae4215 --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:044b3436ae167802393bcbf2529a7fbd06d267c35a4ec1a14653b20a8ad12471 +size 95643 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9118f2189a4a76ce77236e6e8c29b14a7ddee80e --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ef73161e9d27330a49b7c79490eacd4f40fe8e49056052d47554061dc77b812 +size 73109 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db55923b06ae93e9c1aa4f79683b83f64feff90 --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab8c69418ef04a09b9ef5c7dc257d6c3e2645310d04d093faceb2f8f64ebd8cd +size 77734 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91b4c96b744adaa4dcdfc46d8017c688fa9a46ac --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a64b70fbd3b9dcbc057476654b99180446fd43c19ed2095f54f2e57a462c44c +size 83488 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b89c40432b5265375ab842cf5b73dc9ff6226c6 --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2486d2eb72b72bb4041f8b30d727bf98c217bf282aaf1c16dff3c5f4dd7a5510 +size 108312 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.2201-200103-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f06482db169d102fba98447e463ea4359251f135 --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bb1c15e96fabe1253813dcf17747094193b0267f95c4f0464f50d5b5cff878d +size 104034 diff --git a/marked/M/T-REC-M.2201-200103-I_PDF-E/raw.md b/marked/M/T-REC-M.2201-200103-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b8524dcbf7fd09e382f3e4aa79c173cfdc46037e --- /dev/null +++ b/marked/M/T-REC-M.2201-200103-I_PDF-E/raw.md @@ -0,0 +1,736 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2201** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/2001) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +--- + +**Performance objectives, allocations and limits +for bringing-into-service and maintenance of +international ATM virtual path and virtual +channel connections** + +ITU-T Recommendation M.2201 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Performance objectives, allocations and limits for bringing-into-service and maintenance of international ATM virtual path and virtual channel connections** + +## **Summary** + +This Recommendation provides performance objectives, allocations and limits, and measurement procedures for bringing-into-service and maintenance of international end-to-end permanent and semi-permanent ATM Virtual Path Connections (VPCs), Virtual Channel Connections (VCCs), and connection portions that form part of an international ATM VPC or VCC. Error, delay and availability performance aspects are addressed. Some of the performance objectives depend on the user's selection of Quality of Service (QoS) class, definitions of which are given in ITU-T I.356 and ITU-T I.371. + +## **Source** + +ITU-T Recommendation M.2201 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 15 March 2001. + +## **Keywords** + +Availability, bringing-into-service, degraded performance limit, errored second, in-service monitoring, performance allocation, performance limits, severely errored second, unacceptable performance limit. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +## CONTENTS + +| | Page | | +|-------|---------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Abbreviations..... | 4 | +| 5 | Hypothetical reference model..... | 6 | +| 5.1 | General model..... | 6 | +| 5.1.1 | Country-based model..... | 6 | +| 5.1.2 | Operator-based model..... | 8 | +| 5.2 | Relationship of ATM virtual paths to physical paths ..... | 8 | +| 5.3 | Testing arrangement ..... | 9 | +| 6 | Performance objectives..... | 10 | +| 6.1 | Reference performance events, performance parameters and performance objectives ..... | 10 | +| 6.2 | Allocation principles for end-to-end VPCs/VCCs..... | 11 | +| 7 | Performance measurements ..... | 14 | +| 7.1 | BIS performance measurements ..... | 14 | +| 7.2 | Maintenance performance measurements..... | 15 | +| 7.3 | Availability ..... | 16 | +| 7.4 | Evaluation of performance objectives ..... | 17 | +| 8 | Role within the TMN..... | 17 | +| 9 | Performance limits..... | 18 | +| 9.1 | Relationship between performance limits and objectives..... | 18 | +| 9.2 | Types of limits ..... | 18 | +| 9.3 | Process for calculation of ATM connection performance objectives and limits..... | 18 | +| 9.4 | Long-term quality monitoring/measurement..... | 19 | + +# Introduction + +This Recommendation describes the operational procedures and performance of ATM VPCs that are designed and engineered according to the relevant I-series Recommendations, and are used to support ATM VCCs. It relies heavily on the use of in-service monitoring facilities built into ATM equipment, and focuses on the F4 and F5 Operation, Administration and Maintenance (OAM) information flows specified in ITU-T I.610. However, these OAM facilities are not present in all types of ATM equipment. Therefore, Out-Of-Service (OOS) tests will also be required to ensure operational performance limits are met during Bringing-Into-Service (BIS) and maintenance activities. + +The long-term (one month) cell transfer and availability performance objectives for ATM networks are defined in ITU-T I.356 and ITU-T I.357 respectively. Short-term cell transfer and availability performance requirements from an operation and maintenance perspective are covered in this Recommendation. + +ITU-T I.356 and ITU-T M.2201 apply end-to-end from terminal measuring point MPT to MPT. This Recommendation enables the derivation of the performance objectives for real connections according to ITU-T I.356 (which has a country-based model); the performance allocation to a single operator is not specifically addressed. In cases where multiple operators operate one or more connections/portions, the subdivision of the objectives between them is subject to further study. + +This Recommendation is part of the M.22xx series that address the operation and maintenance of the ATM layer (i.e. above the physical layer). It does not address the ATM Adaptation Layer (AAL) services or consider provisioning and commissioning of ATM equipment into the network. Recommendations in the M.21xx series provide performance objectives, allocations and limits for the physical layer network supporting the ATM layer. The built-in monitoring used by these Recommendations is the OAM information flows defined in ITU-T I.610 as F1, F2 and F3. + +## **Performance objectives, allocations and limits for bringing-into-service and maintenance of international ATM virtual path and virtual channel connections** + +# 1 Scope + +This Recommendation provides performance objectives, allocations and limits, and measurement procedures for bringing-into-service and maintenance of international, permanent or semi-permanent end-to-end ATM Virtual Path Connections (VPCs), Virtual Channel Connections (VCCs), and connection portions that form part of an international ATM VPC or VCC. Error, delay and availability performance aspects are addressed. + +This Recommendation provides performance objectives, allocations and limits for Bringing-Into-Service (BIS) and maintaining international ATM permanent and semi-permanent VPCs that are transported over PDH, SDH or optical fibre networks, referring to the Operations, Administration and Maintenance (OAM) information flows F1-F5 (see Figure 3/I.610 [7]). This Recommendation is part of the M.22xx series, which address flows F4 and F5 (i.e. above the physical level); the M.21xx series address flows F1-F3. This Recommendation does not address the ATM Adaptation Layer (AAL) services or consider provisioning and commissioning of ATM equipment into the network. + +Because BIS and maintenance requirements differ according to cell priority level, different limits are provided based on Cell Loss Priorities CLP = 0, and CLP = 0 + 1. Performance parameters and limits are also given for triggering maintenance activity (e.g. fault localization, repair, etc.). Automatic re-routing of cells in the case of a fault is assumed in the determination of limits. The limits are designed to support the long-term performance objectives in ITU-T I.356 [4]. + +This Recommendation assumes the ATM cell format and structure described in ITU-T I.150 [1] and the use of ITU-T I.610 [7] B-ISDN OAM principles and functions. Methods of deriving performance information from OAM cells and other path information are given. + +This Recommendation enables the derivation of the performance objectives for real connections according to ITU-T I.356 [4] (which has a country-based model); the performance allocation to a single operator is not specifically addressed. In cases where multiple operators operate one or more connections/portions, the subdivision of the objectives between them is subject to further study. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is published regularly. + +- [1] ITU-T I.150 (1999), *B-ISDN asynchronous transfer mode functional characteristics*. +- [2] ITU-T I.326 (1995), *Functional architecture of transport networks based on ATM*. +- [3] ITU-T I.353 (1996), *Reference events for defining ISDN and B-ISDN performance parameters*. +- [4] ITU-T I.356 (2000), *B-ISDN ATM layer cell transfer performance*. +- [5] ITU-T I.357 (2000), *B-ISDN semi-permanent connection availability*. + +- [6] ITU-T I.371 (2000), *Traffic control and congestion control in B-ISDN.* +- [7] ITU-T I.610 (1999), *B-ISDN operation and maintenance principles and functions.* +- [8] ITU-T M.20 (1992), *Maintenance philosophy for telecommunication networks.* +- [9] ITU-T M.34 (1988), *Performance monitoring on international transmission systems and equipment.* +- [10] ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [11] ITU-T M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH paths, sections and transmission systems.* +- [12] ITU-T M.2101 (2000), *Performance limits and objectives for bringing-into-service and maintenance of international SDH paths and multiplex sections.* +- [13] ITU-T M.2140 (2000), *Transport network event correlation.* +- [14] ITU-T M.3010 (2000), *Principles for a telecommunications management network.* +- [15] ITU-T M.3200 (1997), *TMN management services and telecommunications managed areas: overview.* +- [16] ITU-T M.3207.1 (1996), *TMN management service: maintenance aspects of B-ISDN management.* +- [17] ITU-T M.3400 (2000), *TMN Management Functions.* +- [18] ITU-T M.3600 (1992), *Principles for the management of ISDNs.* +- [19] ITU-T M.3610 (1996), *Principles for applying the TMN concept to the management of B-ISDN.* +- [20] ITU-T M.3611 (1997), *Test management of the B-ISDN ATM layer using the TMN.* +- [21] ITU-T O.191 (2000), *Equipment to measure the cell transfer performance of ATM connections.* + +# 3 Terms and definitions + +General terms and definitions relating to this Recommendation are provided in ITU-T Recommendations I.326 [2], I.353 [3], I.356 [4], I.357 [5], I.371 [6], I.610 [7], M.20 [8], M.34 [9], M.60 [10], M.2100 [11] and M.2101 [12]. For the purpose of this Recommendation, the following definitions also apply: + +**3.1 Allocated Performance Objective (APO):** An APO is the PO for a real connection calculated according to the allocation rules defined in this Recommendation. + +**3.2 Bringing-Into-Service Performance Objective (BISPO):** A BISPO is the PO for a real connection or connection portion calculated from its APO and used for BIS testing. + +**3.3 Connection Point (CP):** A CP is a reference point where the output of a trail termination source or a connection is bound to the input of another connection, or where the output of a connection is bound to the input of a trail termination sink or another connection. + +**3.4 End-to-end VPC or VCC:** An end-to-end VPC or VCC is the VPC or VCC existing between two MPTs and may traverse a number of ATM switching/cross-connect nodes. + +**3.5 Measurement Point (MP):** A MP is located at an interface that separates either Customer Equipment (CEQ)/customer network or a Switching/Signalling Node (SSN) from an attached transmission system at which ITU-recommended protocols can be observed. + +NOTE 1 – The term SSN collectively denotes any equipment that accesses the ATM layer in the transport network under consideration. + +NOTE 2 – As defined, MPs exist at many physical interfaces in a connection. It is not the intention in this Recommendation to specify performance between arbitrary pairs of MPs. + +NOTE 3 – For B-ISDN, the MPs are located at interfaces where the ATM is accessible. The exact location within the protocol stack depends on whether the connection is a VPC or a VCC. + +**3.6 Measurement Point O (MPO):** A MPO is located at an interface that terminates a transmission system, for example, at an operator's boundary (Point Of Presence (POP)) or an International Switching Centre (ISC). MPTs and individual associated MPOs delimit portions of an end-to-end connection for which performance objectives are specified. + +**3.7 Measurement Point T (MPT):** A MPT is located at an interface associated with a T reference point. This interface separates CEQ from an attached digital section. The T (or $T_B$ in the case of B-ISDN) may be different from the ideal location and difficult to access. Two practical methods for measuring at the B-ISDN MPT are: + +- locating a physical test set at the MPT and replicating the ATM protocol functions outside of the CEQ, or +- approximating the performance at the MPT by observations made within the network at the first point where the ATM layer is observable. + +**3.8 OAM Flow:** Information flow transferred through the network by the means of a dedicated channel supported by specific bytes or bits of the transmission systems for the physical layer and by specific ATM cells referred to as OAM cells for the ATM layer. + +**3.9 Performance Objective (PO):** A PO is the target performance to be achieved over the end-to-end reference connection specified in this Recommendation (see Figure 1 for example), assuming a maximum length of 27 500 km. + +**3.10 Permanent Virtual Path Connection (VPC) or Virtual Channel Connection (VCC):** A permanent VPC or VCC is the ATM layer connection which exists between two MPTs or two ATM switches/cross-connect nodes that is permanently set up and configured for transporting ATM information between those two points. Each VPC is considered to be a unidirectional transport entity and may contain one or more VCCs. For a bidirectional VPC or VCC, all performance objectives, limits, etc. shall be applied to each direction independently of the other direction. However, note that use of ITU-T I.610 [7] OAM functionality requires the provision of a reverse channel to carry OAM information. + +**3.11 segment:** Portion of a VPC or a VCC delimited by two CPs referred to respectively as the segment source CP and segment sink CP. + +**3.12 semi-permanent VPC or VCC:** A semi-permanent VPC or VCC is the ATM layer connection which exists between two MPTs or two ATM switches/cross-connect nodes that is set up and configured for a limited time to transport ATM information between those two points. Each VPC is considered to be a unidirectional transport entity and may contain one or more VCCs. For a bidirectional VPC or VCC, all performance objectives, limits etc. shall be applied to each direction independently of the other direction. + +**3.13 sink:** Term used to indicate that OAM information is removed (e.g. at the sink trail termination function) from the incoming signal for further processing. + +**3.14 Source:** Term used to indicate that OAM information is added (e.g. at the source trail termination function) to the outgoing signal for further processing downstream (e.g. at the sink trail termination function). + +**3.15 Termination Connection Point (TCP):** A TCP is a special case of a CP where a trail termination function is bound to an adaptation function or a connection function. In the information model, the termination connection point is called Trail Termination Point (TTP). + +**3.16 VPC/VCC End-to-end Maintenance Entity (ME):** Maintenance entity delimited by the connection end points, which are: + +- i) the source TCP; and +- ii) the sink TCP. + +This ME is a bidirectional entity in the sense that the source TCP for a given direction and the sink TCP for the opposite direction are paired at each end of the ME (the VP/VC trail termination functions are located at those TCPs). This ME is created (or deleted) when the VPC/VCC is set up (or released). + +**3.17 VPC/VCC Segment Maintenance Entity (ME):** Maintenance entity delimited by the segment end points, which are: + +- i) the segment source CP; and +- ii) the segment sink CP. + +This ME is a bidirectional entity in the sense that the segment source CP for a given direction and the segment sink CP for the opposite direction are paired at each end of the ME (the VP/VC sub-layer trail termination functions are located at those CPs). This ME is a flexible ME which can be created or deleted following a TMN action. It should be noted that the segment source/sink CP may be adjacent to the source/sink TCP and that segment MEs can be nested inside end-to-end MEs. Thus there can be end-to-end OAM flows and segment OAM flows on the same connection. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|--------|-------------------------------------| +| AAL | ATM Adaptation Layer | +| AIS | Alarm Indication Signal | +| APO | Allocated Performance Objective | +| APS | ATM Protection Switching | +| ATC | ATM Transfer Capability | +| ATM | Asynchronous Transfer Mode | +| BIS | Bringing-Into-Service | +| B-ISDN | Broadband ISDN | +| BISPO | BIS Performance Objective | +| BR | Backward Reporting | +| CBR | Constant Bit Rate | +| CC | Continuity Check | +| CDV | Cell Delay Variation | +| CDVT | Cell Delay Variation Tolerance | +| CEQ | Customer Equipment/Customer network | +| CER | Cell Error Ratio | +| CL | Cell Loss | + +| | | +|------|-------------------------------------------| +| CLP | Cell Loss Priority | +| CLR | Cell Loss Ratio | +| CM | Cell Misinsertion | +| CMR | Cell Misinsertion Rate | +| CP | Connection Point | +| CRC | Cyclic Redundancy Checksum | +| CTD | Cell Transfer Delay | +| DPL | Degraded Performance Limit | +| ECB | Errored Cell Block | +| ES | Errored Second | +| FPM | Forward Performance Monitoring | +| FS | Frontier Station | +| IIP | International Inter-operator Portion | +| IoP | Inter-operator Portion | +| IS | In-Service | +| ISDN | Integrated Services Digital Network | +| ISM | In-Service Monitoring | +| ITP | International Transit Portion | +| LB | LoopBack | +| LCD | Loss of Cell Delineation | +| LOC | Loss Of Continuity | +| LOS | Loss Of Signal | +| MBS | Maximum Burst Size | +| MCTD | Mean Cell Transfer Delay | +| ME | Maintenance Entity | +| MP | Measurement Point | +| MPI | Measurement Point International boundary | +| MPO | Measurement Point Operator boundary | +| MPT | Measurement Point at T B | +| NE | Network Element | +| NP | Network Performance | +| NPC | Network Parameter Control | +| NPP | Network Performance Parameter | +| OAM | Operation, Administration and Maintenance | +| OOS | Out-Of-Service | +| OS | Operations System | +| PCR | Peak Cell Rate | + +| | | +|-------|--------------------------------------| +| PDH | Plesiochronous Digital Hierarchy | +| PM | Performance Monitoring | +| PO | Performance Objective | +| POH | Path OverHead | +| PTI | Payload Type Indicator | +| QoS | Quality of Service | +| RDI | Remote Defect Indication | +| SCR | Sustainable Cell Rate | +| SDH | Synchronous Digital Hierarchy | +| SECB | Severely Errored Cell Block | +| SECBR | Severely Errored Cell Block Ratio | +| SES | Severely Errored Second | +| SSN | Switching/Signalling Node | +| TCP | Termination Connection Point | +| TMN | Telecommunication Management Network | +| UAS | UnAvailable Second | +| UNI | User-Network Interface | +| UPC | Usage Parameter Control | +| UPL | Unacceptable Performance Limit | +| VC | Virtual Container | +| VCC | Virtual Channel Connection | +| VCI | Virtual Channel Identifier | +| VP | Virtual Path | +| VPC | Virtual Path Connection | +| VPI | Virtual Path Identifier | + +# 5 Hypothetical reference model + +## 5.1 General model + +### 5.1.1 Country-based model + +ATM cell transfer performance is measured by observing the reference events created as ATM cells cross MPs. ITU-T I.353 [3] defines the MPs and the associated reference events that provide the basis for ISDN and B-ISDN performance description. + +According to ITU-T I.353 [3], the only cells that create reference events are those with a payload type field indicating a user information cell. Thus, the performance recommendations of ITU-T I.356 [4], and consequently this Recommendation, only apply to the transfer of user information cells. + +![Figure 1a/M.2201 – Example of a VPC and its connection portions. The diagram illustrates a network path spanning an Originating Country, three Transit Countries, and a Terminating Country. It is divided into National Portions at each end and an International Portion in the middle. The path consists of Connection Points (CP) represented by blue circles. Measurement points include MPT at the customer network ends and MPI at country boundaries. The International Portion is subdivided into International Transit Portions (ITP) within countries and International Inter-operator Portions (IIP) between countries. A legend defines symbols for CPE/CEQ/Customer network (VP source/sink) as light blue rectangles and Connection Point – VP switching/signalling node (DXC or SSN) as blue circles with 'CP' text.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 1a/M.2201 – Example of a VPC and its connection portions. The diagram illustrates a network path spanning an Originating Country, three Transit Countries, and a Terminating Country. It is divided into National Portions at each end and an International Portion in the middle. The path consists of Connection Points (CP) represented by blue circles. Measurement points include MPT at the customer network ends and MPI at country boundaries. The International Portion is subdivided into International Transit Portions (ITP) within countries and International Inter-operator Portions (IIP) between countries. A legend defines symbols for CPE/CEQ/Customer network (VP source/sink) as light blue rectangles and Connection Point – VP switching/signalling node (DXC or SSN) as blue circles with 'CP' text. + +**Figure 1a/M.2201 – Example of a VPC and its connection portions** + +Figure 1a shows an example of a VPC crossing three transit countries. In general, the international portion of such a connection can be partitioned into several International Transit Portions (ITPs) and International Inter-operator Portions (IIPs). An ITP is a connection portion between two MPIs in a single transit country. An IIP is a connection portion between two MPIs in different countries. + +The convention IIP(n) is used to indicate the number "n" of intervening transit countries in each IIP. + +It should be noted that, in the case of a VPC: + +- the number of IIPs is equal to one more than the number of transit countries; +- all IIPs are of the type IIP(0); +- all transit countries have at least one MPI. + +![Figure 1b/M.2201 – Example of a VCC and its connection portions. This diagram is similar to Figure 1a but represents a Virtual Channel Connection (VCC). It shows the same country structure (Originating, three Transit, Terminating). It introduces green circles for Connection Point – VC switching/signalling node (DXC or SSN). The diagram highlights specific IIP types, such as IIP(0) and IIP(2), indicating the number of transit countries bypassed. The legend is expanded to include the green CP symbol for VC switching nodes.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 1b/M.2201 – Example of a VCC and its connection portions. This diagram is similar to Figure 1a but represents a Virtual Channel Connection (VCC). It shows the same country structure (Originating, three Transit, Terminating). It introduces green circles for Connection Point – VC switching/signalling node (DXC or SSN). The diagram highlights specific IIP types, such as IIP(0) and IIP(2), indicating the number of transit countries bypassed. The legend is expanded to include the green CP symbol for VC switching nodes. + +**Figure 1b/M.2201 – Example of a VCC and its connection portions** + +Figure 1b shows an example of a VCC crossing three transit countries. As stated in ITU-T I.353 [3], MPTs are measurement points at or near $T_B$ reference points and thus are at or near customer equipment (CEQ)/customer networks. + +It should be noted that, in the case of a VPC: + +- the number of IIPs depends on the position of VCC SSNs; +- several kinds of IIP can be present in a connection; +- not all transit countries have a MPI. + +### 5.1.2 Operator-based model + +The model used in 5.1.1 does not take into account a multi-operator environment. This case can be better described by means of the model shown in Figure 1c, applied to a VPC. + +![Diagram of a VPC in a multi-operator environment showing Operator A and Operator B portions connected via transit operators.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +The diagram illustrates a Virtual Path Connection (VPC) across multiple operator domains. It is divided into three main segments: + + +- Operator A Portion:** Contains the 'Originating Operator' (oval). It starts at an 'MPT' (Measurement Point) connected to a 'CPE (VP source/sink)' (square), followed by three 'CP' (Connection Point) nodes. +- Transit Portion:** Consists of three 'Transit Operator' (yellow oval) domains. Each domain contains 'CP' nodes and 'MPO' (Measurement Point) nodes. The segments between Operator A and the first Transit Operator, and between subsequent Transit Operators, are labeled 'IoP' (Inter-operator Portion). The segments within each Transit Operator's domain are labeled 'ITP' (Intra-operator Transit Portion). +- Operator B Portion:** Contains the 'Terminating Operator' (oval). It ends at an 'MPT' connected to a 'CPE (VP source/sink)' (square), with two 'CP' nodes in between. + + A legend at the bottom left defines the symbols: a square for 'CPE (VP source/sink)' and a circle with 'CP' for 'Connection Point (DXC or SSN)'. A small code 'T0415220-01' is in the bottom right. + +Diagram of a VPC in a multi-operator environment showing Operator A and Operator B portions connected via transit operators. + +**Figure 1c/M.2201 – Example of VPC and its connection portions in a multi-operator environment** + +In this clause, MPOs are measurement points established at the switching/signalling nodes (SSN) before and after the connection crosses the operator's boundary. + +For the purpose of performance management in this environment, ATM connections are divided into the following types of connection portions: + +- Connection portions between the MPT and the MPO both within the originating or terminating operator. +- Intra-operator Transit Portions (ITPs) between two MPOs in a single transit operator's domain. For VP, the ITP will consist of at least one VP SSN. +- Inter-operator Portions (IoPs): connection portions between two MPOs in different operator domains. For VP there are no ATM switching or cross-connect elements between these two MPOs. +- Private ATM networks may connect the end users to this public network model at one or both MPTs. The quantitative impact of such networks on the end-to-end QoS is an issue for further study and is not currently addressed in this Recommendation. + +## 5.2 Relationship of ATM virtual paths to physical paths + +Virtual paths originate and terminate in ATM switches or cross-connects that need not be coincident with the physical layer paths or other VP, as shown in Figure 2. + +![Diagram showing OAM hierarchical levels and relationship to network layers. The diagram is divided into two main sections: ATM Layer and Physical Layer, separated by a dashed line. The ATM Layer contains two levels: F5 - Virtual Channel Level and F4 - Virtual Path Level. The F5 level shows a 'Virtual Channel Network Connection' spanning three segments, each labeled 'VCLC'. The F4 level shows a 'Virtual Path Network Connection' spanning the same three segments, each labeled 'VPLC'. The Physical Layer contains three levels: F3 - Transmission Path Level, F2 - Multiplex Section Level, and F1 - Regenerator Section Level. The F3 level shows a 'Transmission Network Path' spanning three segments. The F2 level shows a 'Digital Network Section' spanning two segments. The F1 level shows a 'Digital Regenerator Section' spanning one segment. Nodes are represented by green squares at the ends and green circles at the intermediate points. Arrows indicate the flow of OAM information between these points.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Diagram showing OAM hierarchical levels and relationship to network layers. The diagram is divided into two main sections: ATM Layer and Physical Layer, separated by a dashed line. The ATM Layer contains two levels: F5 - Virtual Channel Level and F4 - Virtual Path Level. The F5 level shows a 'Virtual Channel Network Connection' spanning three segments, each labeled 'VCLC'. The F4 level shows a 'Virtual Path Network Connection' spanning the same three segments, each labeled 'VPLC'. The Physical Layer contains three levels: F3 - Transmission Path Level, F2 - Multiplex Section Level, and F1 - Regenerator Section Level. The F3 level shows a 'Transmission Network Path' spanning three segments. The F2 level shows a 'Digital Network Section' spanning two segments. The F1 level shows a 'Digital Regenerator Section' spanning one segment. Nodes are represented by green squares at the ends and green circles at the intermediate points. Arrows indicate the flow of OAM information between these points. + +VCLC Virtual Channel Link Connection + VPLC Virtual Path Link Connection + +T0415230-01 + +**Figure 2/M.2201 – OAM hierarchical levels and relationship to network layers** + +## 5.3 Testing arrangement + +Since performance is specified from MPT to MPT, BIS testing will use an OOS information flow transported between measuring instruments conforming to ITU-T O.191 [21] applied at the MPTs (or MPIs, MPOs for a connection portion). ISM OAM flow can be used between the connection portions as shown in Figure 3. + +![Figure 3/M.2201 – Test arrangement for ATM connection portions. The diagram shows a network path from an Originating Operator to a Terminating Operator through three Transit Operators. The path includes various components: CPE (VP source/sink), Connection Points (CP), ISM (Interconnection Switching Module), and OOS (Out-of-Service) points. The diagram is labeled with MPT, MPO, IoP, and ITP. Two O.191 Testers are shown at the ends of the path. A legend at the bottom left defines the symbols: a blue square for CPE (VP source/sink), a circle with 'CP' for Connection Point (DXC or SSN), a green curved arrow for ISM, and a black curved arrow for OOS. The text 'T0415240-01' is in the bottom right corner.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 3/M.2201 – Test arrangement for ATM connection portions. The diagram shows a network path from an Originating Operator to a Terminating Operator through three Transit Operators. The path includes various components: CPE (VP source/sink), Connection Points (CP), ISM (Interconnection Switching Module), and OOS (Out-of-Service) points. The diagram is labeled with MPT, MPO, IoP, and ITP. Two O.191 Testers are shown at the ends of the path. A legend at the bottom left defines the symbols: a blue square for CPE (VP source/sink), a circle with 'CP' for Connection Point (DXC or SSN), a green curved arrow for ISM, and a black curved arrow for OOS. The text 'T0415240-01' is in the bottom right corner. + +**Figure 3/M.2201 – Test arrangement for ATM connection portions** + +# 6 Performance objectives + +## 6.1 Reference performance events, performance parameters and performance objectives + +ITU-T I.353 [3] and ITU-T I.356 [4] define ATM cell reference events and ATM cell transfer outcomes between two MPs. These are used to determine ATM Network Performance Parameters (NPPs) and resulting Quality of Service (QoS) provided by the VPC or VCC. The NPPs are related to both connection distance and connection complexity, and include: + +- Cell Error Ratio (CER); +- Cell Loss Ratio (CLR) for all three CLP flows; +- Cell Misinsertion Rate (CMR)1; +- Severely Errored Cell Block Ratio (SECBR); +- Cell Transfer Delay (CTD); +- Mean Cell Transfer Delay (MCTD); +- Cell Delay Variation (CDV), both 1-pt CDV and 2-pt CDV; +- Availability. + +Table 1 shows the typical reference performance objectives in terms of NPPs for different QoS classes. These practical operational performance objectives apply to each direction over 24 hours, as opposed to the long-term (one month) objectives specified in ITU-T I.356 [4] and ITU-T I.357 [5]. + +1 CMR performance objective may not be relevant or practical to measure during BIS (e.g. < 1 misinserted cell per day), but monitoring for misinserted cells should still be done during maintenance. + +**Table 1/M.2201 – ATM VPC/VCC reference performance objectives** + +| QoS Class | CER | CLR 0+1 | CLR 0 | CMR | SECBR | UAT | CTD (ms) | CTD (ms) | 2-pt CDV (ms) | +|-----------|--------------------|----------------------|----------------------|-------|--------------------|-----|--------------------|------------------|---------------| +| | | | | | | | Terrestrial | Satellite | | +| 1 | $2 \times 10^{-6}$ | $1.5 \times 10^{-7}$ | X | 0 | $5 \times 10^{-5}$ | 0 | 400 | 700 | 1.5 | +| 2 | $2 \times 10^{-6}$ | $5 \times 10^{-6}$ | X | 1/day | $5 \times 10^{-5}$ | 0 | X | X | X | +| 3 | $2 \times 10^{-6}$ | X | $5 \times 10^{-6}$ | 1/day | $5 \times 10^{-5}$ | 0 | X | X | X | +| 5 | $2 \times 10^{-6}$ | X | $1.5 \times 10^{-7}$ | 1/day | $5 \times 10^{-5}$ | 0 | 400 | 700 | 3 | +| U | X | X | X | X | X | X | X | X | X | + +NOTE – The need for different tests to assess QoS is under study. +X = no commitment + +The methods for detecting the unavailable state are specified in ITU-T I.357 [5]. One method uses a 10-second consecutive SESATM event counter with hysteresis. However, no SESATM event count limit or PO for availability is currently specified. Further information on availability performance is given in 7.3. + +## 6.2 Allocation principles for end-to-end VPCs/VCCs + +This clause specifies the allocation principles of performance objectives for the end-to-end ATM VPCs or VCCs, in terms of the connection portions as shown in Figures 1a and 1b. + +It is the responsibility of each operator to design its network in a way that is consistent with its connection portion allocation for the VPC or VCC. The allocation of each portion of the VPC or VCC, as a percentage of the overall end-to-end PO, can be determined from the values given in Table 2 and Table 3 respectively. These allocation figures are based on I.356 [4]. + +**Table 2/M.2201 – Maximum allocation of PO to terrestrial VPC portions** + +| | Parameter | Units | Block Allowance | | Distance allocation | Complexity | +|--------------------|-----------------|-------|------------------------------|---------------------------|-----------------------------|---------------------| +| | | | International portion | National portion (Note 2) | | | +| Error Perf. | CER/SECBR | Ratio | $1\% + (N_{TC} \times 3)\%$ | 17.5% | 1% per 500 km | – | +| | CLR class 1 & 5 | Ratio | $1\% + (N_{TC} \times 8)\%$ | 23.0% | 1% per 1000 km | – | +| | CLR class 2 & 3 | Ratio | $1\% + (N_{TC} \times 10)\%$ | 34.5% | – | – | +| Delay Perf. | CTD class 1 & 5 | μs | – | – | $\leq (R_{km} \times 6.25)$ | $N_{sw} \times 300$ | +| | CDV class 1 | ms | $N_{TC} \times 0.7$ | 1.5 | – | – | +| | CDV class 5 | ms | $N_{TC} \times 1.5$ | 3.0 | – | – | + +NOTE 1 – $N_{TC}$ = number of transit countries, $R$ = route length (in km), $N_{sw}$ = number of SSNs. +NOTE 2 – For each end-to-end connection, there will be an originating country national portion and a terminating country national portion. + +**Table 3/M.2201 – Maximum allocation of PO to terrestrial VCC portions** + +| | Parameter | Units | Block Allowance | | | Distance allocation | Complexity | +|--------------------------|----------------------|-------|------------------------------|---------------------------|---------------------------|-----------------------------|---------------------| +| | | | International portion IIP(n) | International portion ITP | National portion (Note 2) | | | +| Error Perf. | CER/SECBR | Ratio | $1\% + (n \times 3)\%$ | 2% | 17.5% | 1% per 500 km | – | +| | CLR class 1 & 5 | Ratio | $1\% + (n \times 8)\%$ | 7% | 23.0% | 1% per 1000 km | – | +| | CLR class 2 & 3 | Ratio | $1\% + (n \times 10)\%$ | 9% | 34.5% | – | – | +| Delay Performance | CTD class 1 & 5 | μs | – | | – | $\leq (R_{km} \times 6.25)$ | $N_{sw} \times 300$ | +| | CDV class 1 (Note 3) | ms | $0.7 + 0.2 \times (n-1)$ | 0.7 | 1.5 | – | – | +| | CDV class 5 (Note 3) | ms | $1.5 + 0.5 \times (n-1)$ | 1.5 | 3.0 | – | – | + +NOTE 1 – R = route length (in km), NSW = number of SSNs. + +NOTE 2 – For each end-to-end connection, there will be an originating country national portion and a terminating country national portion. + +NOTE 3 – For CDV, the block allowance in the IIP is calculated only for the case $n > 0$ ; for the case $n = 0$ , there is no IIP block allowance. + +CER and SECBR are mainly distance related. Practical measurements show that CLR is distance and complexity related for QoS class 1, and complexity dominated for QoS class 2 and QoS class 3. However, the complexity is taken into account in the block allowance shown in Table 2 and Table 3 and there is no distance allowance for CLR in QoS classes 2 & 3. + +CTD and mean CTD are mainly distance related, but also depend on the connection complexity or number of SSNs. CDV is independent of distance and depends on the number of SSNs. However, the block allowance takes complexity into account in this case. + +Distances referred to in Table 2 and Table 3 are actual distances or, in the case where the actual distance is not known, calculated according to Table 5. If any connection portion is carried over satellite, the following allocations should be used: + +**Table 4/M.2201 – Maximum allocation of PO to satellite VPC portions** + +| | Parameter | Units | National portion | International portion | | +|------------------------|-----------------|-------|------------------|-----------------------|-----| +| | | | | IIP(n) | ITP | +| Error
Perf.
| CER/SECBR | Ratio | 42% | $35 + (4 \times n)\%$ | 36% | +| | CLR class 1 & 5 | Ratio | 35% | $25 + (5 \times n)\%$ | 30% | +| | CLR class 2 & 3 | Ratio | – | – | – | +| Delay
Perf.
| CTD class 1 & 5 | ms | 320 | 320 | 320 | + +**Table 5/M.2201 – Calculated terrestrial connection distance** + +| Air route distance d | Calculated Distance | +|-------------------------|---------------------| +| $d < 1000$ km | $d \times 1.5$ | +| $1000 \leq d < 1200$ km | 1500 km | +| $d \geq 1200$ km | $d \times 1.25$ | + +It is possible that access to the bit stream for a given VPC or VCC may not coincide with the end of a connection portion. In this case, or if a transit operator has other access points within its network, it may be necessary to make a sub-allocation for maintenance purposes, e.g. fault localization. Such sub-allocations will be the responsibility of the Network Operator(s) involved, with the following constraints: + +- the sum of sub-allocations may not exceed the allocation of Tables 2 or 3 for the connection portion in question; +- the values of the sub-allocations must be communicated to all maintenance centres involved before bringing the path into service and after any rearrangement, which changes the values. + +Two examples follow of how to calculate the performance allocations. + +#### **Example 1: Calculation of SECBR and CER for VPC in Figure 1a** + +The connection consists of: + +- one NP with air-route distance between its MPT and MPI equal to 1000 km; the calculated route length is 1500 km; +- four IIP(0)s with air-route distance between its MPIs equal to 500 km; the calculated route length is 750 km; +- three ITPs with air-route distance between its MPIs equal to 500 km; the calculated route length is 750 km; +- one NP with air-route distance between its MPI and MPT equal to 1000 km; the calculated route length is 1500 km. + +SECBR and CER allocation: + +$$NP = 2 \times (17.5 + 3) = 41\%;$$ + +$$IIP + ITP \text{ (block allowance)} = 1 + (3 \times 3) = 10\%;$$ + +$$IIP + ITP \text{ distance} = (4 \times 750) + (3 \times 750) = 5250 \text{ km (rounded up to 5500)} \Rightarrow 11\%;$$ + +$$\text{Global allocation} = 41 + 10 + 11 = 62\%.$$ + +### Example 2: Calculation of SECBR, CER and CDV class 1 for VCC in Figure 1b + +The connection consists of: + +- one NP with air-route distance between its MPT and MPI equal to 1000 km; the calculated route length is 1500 km; +- one IIP(0) with air-route distance between its MPIs equal to 500 km; the calculated route length is 750 km; +- one IIP(2) with actual distance between its MPIs equal to 3000 km; +- one ITP with air-route distance between its MPIs equal to 500 km; the calculated route length is 750 km; +- one NP with air-route distance between its MPI and MPT equal to 1000 km; the calculated route length is 1500 km. + +SECBR and CER allocation: + +$$\text{NP} = 2 \times (17.5 + 3) = 41\%;$$ + +$$\text{IIP}(0) \text{ (block allowance)} = 1\%;$$ + +$$\text{IIP}(2) \text{ (block allowance)} = 1 + (2 \times 3) = 7\%;$$ + +$$\text{ITP} \text{ (block allowance)} = 2\%;$$ + +$$\text{IIP} + \text{ITP distance} = 750 + 750 + 3000 = 4500 \text{ km} \Rightarrow 9\%;$$ + +$$\text{Global allocation} = 41 + 1 + 7 + 2 + 9 = 60\%.$$ + +CDV class 1 calculation: + +$$\text{NP} = 2 \times (1.5) = 3 \text{ ms};$$ + +$$\text{IIP}(0) \text{ (block allowance)} = 0;$$ + +$$\text{IIP}(2) \text{ (block allowance)} = 0.7 + 0.2 = 0.9 \text{ ms};$$ + +$$\text{ITP} \text{ (block allowance)} = 0.7 \text{ ms};$$ + +$$\text{Global allocation} = 3 + 0.9 + 0.7 = 4.6 \text{ ms}.$$ + +# 7 Performance measurements + +BIS measurements are to be made in an OOS state, and the performance parameters to be measured are described in 7.1. However, it should be noted that the results will be dependent on the traffic loading of the network, which is a shared resource, unlike the circuit-switched connection-oriented SDH network. Maintenance measurements are to be made in-service (if possible), and the technique and performance parameters to be measured are described in 7.2. + +## 7.1 BIS performance measurements + +BIS performance is normally measured OOS using test equipment conforming to ITU-T O.191 [21]. For new VPCs, a 24-hour test duration is recommended. For VCCs being added to an existing VPC, a shorter test duration e.g. 2 hours is acceptable. However, if during this shorter test, the BIS test limit is exceeded, a longer test should be carried out. + +However, not all NPPs may be specified or required for a given ATM VPC or VCC, and will depend on what OAM facilities are available and activated in network equipment. Not all of these NPPs may be practical to measure during BIS. For example, CMR performance may not be relevant or practical to measure during BIS, but monitoring for misinserted cells should still be done during maintenance. + +In addition, it should be noted that accurate CTD measurements require the two test sets to be synchronized in frequency and phase, and accurate 2-point CDV measurements require them at least to be synchronized in frequency. Synchronization methods are under study. A method of estimating + +2-point CDV from 1-point CDV measurements is suggested in Annex C/I.356 [4], although this method has some accuracy constraints. Further details are given in ITU-T O.191 [21]. + +ITU-T I.371 [6] defines traffic profile parameters used to specify traffic contracts for VPCs and VCCs, whether switched or non-switched. These traffic parameters are related to the ATM Transfer Capabilities (ATCs) offered by the VPCs or VCCs and are controlled via the Usage Parameter Control (UPC) or Network Parameter Control (NPC) function in ATM network equipment. These traffic profile parameters include: + +- Cell Delay Variation Tolerance (CDVT); +- Maximum Burst Size (MBS); +- Peak Cell Rate (PCR); +- Peak Emission Interval (PEI); +- Sustainable Cell Rate (SCR). + +For details on classes of service and QoS commitments, refer to ITU-T I.371 [6]. + +BIS performance measurements may include checks of UPC/NPC operation in order to determine the correct functioning of the UPC/NPC mechanism and/or the ability of the VPC or VCC to support its contracted traffic parameters (see also ITU-T I.356 [4] and ITU-T I.371 [6]). Test equipment conforming to ITU-T O.191 [21] may be used for this purpose and can provide user-programmable settings of UPC/NPC traffic profiles in terms of CDVT, MBS, PCR, PEI, SCR etc. BIS tests must include busy hour traffic periods because of the effect of traffic congestion on the result, especially delay parameters. + +## 7.2 Maintenance performance measurements + +ATM network equipment with built-in OAM facilities defined in ITU-T I.610 [7] can provide ISM of performance and fault events, and control of various other functions such as activation/deactivation of Performance Monitoring (PM) and/or Continuity Check (CC), protection switching, system management, etc. These can be used in conjunction with TMN facilities (see ITU-T Recommendations M.3010 [14], M.3200 [15], M.3207.1 [16], M.3400 [17], M.3600 [18], M.3610 [19] and M.3611 [20]) to provide integrated performance and fault management of ATM VPCs and VCCs. + +OAM functions in the network are performed on five OAM hierarchical levels associated with the ATM and physical layers of the protocol reference model (see Figure 1). The functions result in corresponding bidirectional information flows F1, F2, F3, F4 and F5 referred to as OAM flows. The physical layer contains the three lowest OAM flows as follows: + +- F1: regenerator section level; +- F2: multiplex section level; +- F3: transmission path level. + +The ATM layer contains the two higher OAM levels, F4 at the virtual path level and F5 at the virtual channel level. These OAM flows are related to bidirectional Maintenance Entities (MEs) corresponding to either the entire end-to-end ATM VPC/VCC, referred to as the VPC/VCC ME, or to a portion of this connection referred to as a VPC/VCC segment ME. + +For maintenance purposes, F4 and F5 OAM flows are defined at the ATM layer covering the VPC and VCC levels respectively. Both flows are bidirectional and follow the same physical route as the user-data cells, thus constituting an in-band maintenance flow. OAM cells of the F4 flow have the same VPI value in the ATM header as the user cells of the VPC. Both end-to-end F4 flow and segment F4 flow can exist simultaneously in a VPC. When allocating bandwidth to a VPC/VCC, it is necessary to allocate sufficient bandwidth for the OAM cells in that connection as described in ITU-T I.371 [6]. The ISM maintenance method is illustrated in Figure 4 below. + +![Diagram illustrating Maintenance in-service monitoring OAM flows across ATM layers (VCC, VP, VC) and Physical layer. The diagram shows the flow of OAM cells (F4, F5) through various network elements including VCC end points, VP cross-connects, and VC switches. The ATM layer is divided into VCC (VCI 1), VP (VPI 1, VPI 2), and VC (VCI 2, VCI 3) levels. The Physical layer shows transmission paths F3 and sections F2, F1.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +The diagram illustrates the maintenance in-service monitoring OAM flows across different layers of an ATM network. At the top, two VCC end points are shown, each with AAL, ATM, and PL layers. These are connected via a Physical layer connect (PL, PL) to a VP cross-connect (ATM, PL) and a VC switch (ATM, PL). The ATM layer is shown in three levels: VCC (VCI 1), VP (VPI 1, VPI 2), and VC (VCI 2, VCI 3). The VCC level shows a 'Virtual channel connection OAM cell indicated by PT Identifier F5'. The VP level shows a 'Virtual path connection VCI for OAM F4'. The VC level shows 'VPC-OAM F4'. The Physical layer shows 'Transmission path F3' and 'Section F2, F1'. A small text 'T0415250-01' is visible in the bottom right corner of the diagram area. + +Diagram illustrating Maintenance in-service monitoring OAM flows across ATM layers (VCC, VP, VC) and Physical layer. The diagram shows the flow of OAM cells (F4, F5) through various network elements including VCC end points, VP cross-connects, and VC switches. The ATM layer is divided into VCC (VCI 1), VP (VPI 1, VPI 2), and VC (VCI 2, VCI 3) levels. The Physical layer shows transmission paths F3 and sections F2, F1. + +**Figure 4/M.2201 – Maintenance in-service monitoring OAM flows** + +In-service performance monitoring is provided by the ATM network operator applying a flow of Performance Monitoring (PM) OAM cells that are inserted into the traffic stream to divide the user cell flow into cell blocks of a nominal size N. This procedure is described in ITU-T I.610 [7]. Only user cells are monitored by PM flows: if no user cells are inserted for a period of time (e.g. in the case of VBR connections), then no PM cells are inserted. The added OAM cells can be used to monitor path segments (segment flow) or the entire virtual connection (end-to-end flow). Dedicated OAM cells with pre-assigned VCI and PTI values are used to implement F4 and F5 flows respectively at segment or end-to-end levels. Further details are given in ITU-T I.610 [7]. The different OAM cell types can be summarized under the following categories: + +- Fault management using AIS, RDI, CC and LB cells; +- Performance management using FPM and BR cells; +- Activation/deactivation of PM and/or CC using activation/deactivation cells; +- Protection switching at the ATM layer using APS cells; +- System management cells for use by end-systems only. + +Anomalies and defects are detected via the OAM cells by the ATM network equipment and can be used in a similar way as that for the physical layer to determine performance parameters. Anomalies include Errored Cell Block (ECB), Cell Loss (CL) and Cell Misinsertion. Defects include Alarm Indication Signal (AIS), Remote Defect Indication (RDI), Loss Of Signal (LOS), Loss Of Continuity (LOC), and Loss of Cell Delineation (LCD). Persisting defects result in a failure state. Methods of detecting OAM procedure failures are for further study. + +ECBs and CLs can be counted and processed into performance parameters such as ESATM, SESATM and UASATM. These can provide a means to correlate VPC performance degradations with physical layer degradations. Detailed definitions, measurement and accumulation methods are for further study. + +## 7.3 Availability + +Two methods of detecting and declaring the unavailable state at the ATM layer are specified in ITU-T I.357 [5]. The main part of ITU-T I.357 [5] defines the availability criteria for ATM + +connections based on the SESATM event. This method uses a 10-second consecutive SESATM counter with hysteresis analogous to the 10-second consecutive SES counter approach used at the SDH and PDH layers. The means by which this SESATM event is estimated in-service and its accuracy depends on which OAM flows are activated on the connection. Only option 2 of the CC cell (i.e. one CC cell sent nominally every second independently of user cells) is used for in-service estimation of availability. However, there is a potential problem in the declaration of unavailability at the ATM layer using this method. If there is an error in the time at which unavailability is declared, e.g. 1 second late, there could be a large number of cells erroneously declared as lost. This could result in the declared cell loss exceeding the ITU-T I.356 [4] limit for one year. + +An alternative bidirectional method for estimating availability is specified in Annex A.1.2/I.357 [5] based on declaring unavailable state on the detection of AIS or RDI. This estimation is based on the fault management defined in ITU-T I.610 [7] for detecting an outage of a connection. The method is not tied to the 10-second entry and exit criteria for unavailability and does not capture all periods of unavailability, but may result in declaring unavailable state faster than the conventional method. Further information is given in ITU-T I.357 [5] and ITU-T I.610 [7]. + +It should be noted that ATM equipment using different methods of availability estimation on the same connection could lead to inter-operability problems and uncertainty in the performance results obtained. Therefore, it is advisable that the interconnected ATM equipments should use the same method. Furthermore, use of the alternative estimation method in Annex A.1.2/I.357 [5] may result in problems reaching the long-term availability performance objective of ITU-T I.356 [4] since the declaration of unavailable state may occur faster. However, this may be counter-balanced by some improvement in the CER and CLR results taken over available time. In general, the results may favour the connection user at the expense of the Service Provider and care should be taken when estimating availability this way against an SLA. + +## 7.4 Evaluation of performance objectives + +Practical operational measurements will be carried out in as short a time as possible. In all cases, the aim should be to meet the long-term end-to-end ATM cell transfer performance objectives specified in ITU-T I.356 [4] and ITU-T I.357 [5]. + +Any BIS test duration should be 24 hours because: + +- CMR is specified over 24 hours in ITU-T I.356 [4] (unless it is deemed acceptable to only detect cell misinsertions). +- CER and CLR will be dependent on server layer performance, which varies over long-term periods. +- Traffic busy hours vary by location/destination. +- Server layer BIS tests may have taken place several months or years prior to the ATM BIS process. + +# 8 Role within the TMN + +The network configuration for maintenance activities is described in ITU-T M.3600 [18]. This configuration is also applicable to the B-ISDN carrying ATM traffic. The B-ISDN OAM principles described in ITU-T I.610 [7] and used in this Recommendation are intended to be consistent with the TMN principles described in ITU-T M.3010 [14]. OAM information is processed by the management function within the ATM Network Elements (NEs) and passed to the TMN Operations Systems (OSs) at NE management level, network management level and service management level. This includes correlation of events occurring simultaneously at multiple layers of the network so as to avoid a large number of events being recorded when a "parent" event causes multiple performance + +impairment indications at different layers. Further details are given in ITU-T I.610 [7], ITU-T M.2140 [13] and in the other TMN Recommendations. + +# 9 Performance limits + +## 9.1 Relationship between performance limits and objectives + +The limits in this Recommendation are to be used to indicate the need for actions during maintenance and bringing-into-service. A network maintained to these limits should meet the performance objectives specified in ITU-T I.356 [4]. + +The particular parameters measured, the measurement duration, and the limits used for the procedure need not be identical to those used for specifying the performance objectives as long as they result in network performance which meets these objectives. For example, the long-term performance objectives refer to long periods, such as one month. However, practical considerations demand that maintenance and BIS limits be based on shorter measurement intervals. + +Statistical fluctuations in the occurrence of anomalies and defects mean that one cannot be certain that the long-term objectives are met. The limits on the numbers of events and the duration of measurements attempt to ensure that connections exhibiting unacceptable or degraded performance can be detected. The only way to ensure that a connection meets network performance objectives is to evaluate continuous measurement over a long period (i.e. months). + +## 9.2 Types of limits + +Limits are needed for several maintenance functions as defined in ITU-T M.20 [8]. This Recommendation provides connection limits for three of these functions: + +- Bringing-Into-Service (BIS); +- keeping the network operational (maintenance); +- restoration. + +The limits for BIS and restoration are the same. Limits for commissioning (installation and acceptance) of ATM equipment are not provided in ITU-T Recommendations. + +Once entities have been placed into service, supervision of the network requires additional limits, as described in ITU-T M.20 [8]. This supervision is done by in-service performance monitoring. The supervision process involves analysing anomalies and defects detected by maintenance entities to determine if the performance level is normal, degraded or unacceptable. Thus, Degraded Performance Limit (DPL) thresholds and Unacceptable Performance Limit (UPL) thresholds are required. In addition, a limit on performance after intervention (repair) is also required. + +## 9.3 Process for calculation of ATM connection performance objectives and limits + +The following steps shall be followed to obtain ATM connection performance limits: + +- Calculate the APO from $APO = PO \times Allocation \times Test\ duration$ . +- Calculate the BISPO from $BISPO = APO/2$ . +- Set the BIS limit = BISPO. +- Set the Maintenance UPL $\geq APO \times 10$ when measured over 15 minutes. +- Set the Maintenance DPL = $APO \times 0.75$ when measured over 24 hours. + +The UPL and DPL are used as maintenance thresholds that, when exceeded, trigger threshold exception reports to TMN management systems (see ITU-T M.34 [9]). + +## **9.4 Long-term quality monitoring/measurement** + +Performance monitoring history should be kept for at least one year (suggested) by the management system. + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.2301-200207-I_PDF-E/raw.md b/marked/M/T-REC-M.2301-200207-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d5ac931c19906c3a226f849bffd62a13564e385e --- /dev/null +++ b/marked/M/T-REC-M.2301-200207-I_PDF-E/raw.md @@ -0,0 +1,712 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2301** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/2002) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +--- + +**Performance objectives and procedures for +provisioning and maintenance of IP-based +networks** + +ITU-T Recommendation M.2301 + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.2301** + +# **Performance objectives and procedures for provisioning and maintenance of IP-based networks** + +## **Summary** + +This Recommendation provides performance objectives and procedures for provisioning and maintenance of IP-based networks. It focuses attention on parameters that significantly affect the quality of service perceived by the customer, and the methods of measuring those parameters. These include those parameters that affect delay performance at the application layer. Performance limits for temporary dial-up access links, end-customer owned portions and MPLS networks are not covered by this Recommendation and are for further study. However, the performance of fixed access links, whose routing does not change, is covered. + +## **Source** + +ITU-T Recommendation M.2301 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 14 July 2002. + +## **Keywords** + +Autonomous system, Border gateway protocol, Border gateway router, Bringing-into-service procedure, Intrusive measurements, IP operator domain, Maintenance procedure, Management information base, MIB monitoring, Non-intrusive measurements, Operator border gateway router, Performance objectives, Provisioning, Quality of service, Reference network. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2002 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Reference network and procedures..... | 4 | +| 5.1 | Definitions of availability ..... | 5 | +| 5.2 | Virtual private networks ..... | 5 | +| 5.3 | Bringing-into-service procedure..... | 5 | +| 5.4 | Maintenance procedure ..... | 6 | +| 6 | Measurement methods ..... | 6 | +| 6.1 | Intrusive performance measurement (using test packets) ..... | 6 | +| 6.2 | Non-intrusive performance measurement (using MIB monitoring)..... | 7 | +| 7 | Intrusive performance measurement..... | 7 | +| 7.1 | One-way IP Packet Transfer Delay (IPTD)..... | 7 | +| 7.2 | One-way IP Packet Delay Variation (IPDV)..... | 8 | +| 7.3 | IP Packet Loss Ratio (IPLR) ..... | 8 | +| 7.4 | IP Packet Error Ratio (IPER) ..... | 8 | +| 8 | Non-intrusive performance measurement using MIB monitoring..... | 8 | +| 8.1 | IP performance events ..... | 9 | +| 8.1.1 | Total IP packets received..... | 9 | +| 8.1.2 | Total IP packets transmitted ..... | 10 | +| 8.1.3 | IP Packet Error Ratio (IPER) ..... | 10 | +| 8.1.4 | IP Packet Loss Ratio (IPLR) ..... | 11 | +| 8.1.5 | IP Packet Discard Ratio (IPDR)..... | 11 | +| 9 | Performance objectives for IP networks..... | 11 | +| 9.1 | End-to-end IP flow ..... | 12 | +| 9.2 | IP flow across a single IPOD..... | 12 | +| 9.3 | Single link between two adjacent IPODs ..... | 13 | +| 9.4 | Access Links..... | 14 | +| 9.5 | Calculation of route distance ..... | 15 | +| | Annex A – Procedures for reading router MIB registers ..... | 16 | +| | Appendix I – Performance within an IPOD..... | 17 | +| I.1 | Single link between two adjacent routers..... | 17 | + +# Introduction + +This Recommendation provides performance objectives and procedures for provisioning and maintenance of IP-based networks owned by different operators. This is regardless of the transport technology supporting the IP network and the higher layers to be implemented over IP. These objectives include error performance, delay performance and availability. This Recommendation defines the parameters and their associated objectives based on the principles in ITU-T Rec. Y.1540. This Recommendation uses a reference model based on the concept of IP Operator Domains (IPODs) and their interconnecting links. An IPOD consists of one or more Autonomous Systems (ASs) and their interconnecting links. The interconnecting links between IPODs involve a change in jurisdictional responsibility. + +This Recommendation also provides, in an appendix, guidance on the performance objectives and limits for IP network resources (e.g. routers, subnetworks etc.), which are owned and managed by a single operator. However, the allocation of performance inside an IP network operator's domain or network portion, is the responsibility of each operator to ensure the end-to-end performance over their domain or network portion meets the limits given in this Recommendation. + +ITU-T Rec. Y.1540 provides a general framework for applying these limits. Guidance on the methods and procedures for applying these limits in provisioning and maintenance are given in this Recommendation. + +This Recommendation uses certain principles that are the basis of the maintenance of a digital network: + +- it is desirable to do in-service, continuous measurements. In some cases, out-of-service measurements may be necessary; +- performance limits of IP flows are independent of the supporting transport, but the allocation to network sections may be dependent on the transport medium used. + +# Performance objectives and procedures for provisioning and maintenance of IP-based networks + +# 1 Scope + +This Recommendation provides performance objectives and procedures for provisioning and maintenance of IP-based networks owned by different operators. This is regardless of the transport technology supporting the IP network and the higher layers to be implemented over IP. These objectives include error performance, delay performance and availability. This Recommendation also provides guidance, in an appendix, on the performance objectives and limits for IP network resources (e.g. routers, subnetworks etc.), which are owned and managed by a single operator. Performance limits for temporary dial-up access links, end-customer owned portions and MPLS networks are not covered by this Recommendation and are for further study. However, the performance of fixed access links, whose routing does not change, is covered. + +This Recommendation provides the network QoS classes needed to support user-oriented QoS categories. Accordingly, this Recommendation is consistent with the general framework for defining quality of communication services in ITU-T Rec. G.1000 [1], and with the end-user multimedia QoS categories needed to support user applications given in ITU-T Rec. G.1010 [2]. + +NOTE – This Recommendation uses parameters defined in ITU-T Rec. Y.1540 [4] that can be used to characterise IP network performance provided using IPv4. Applicability or extension to other protocols (e.g. IPv6) is for further study. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation G.1000 (2001), *Communications Quality of Service: A Framework and Definitions*. +- [2] ITU-T Recommendation G.1010 (2001), *End-user multimedia QoS categories*. +- [3] ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- [4] ITU-T Recommendation Y.1540 (1999), *Internet protocol data communication service – IP packet transfer and availability performance parameters*. +- [5] ITU-T Recommendation Y.1541 (2002), *Network performance objectives of IP-based services*. +- [6] IETF RFC 1213 (1991), *Management Information Base for Network Management of TCP/IP-based internets: MIB-II*. +- [7] IETF RFC 1267 (1991), *A Border Gateway Protocol 3 (BGP-3)*. +- [8] IETF RFC 2011 (1996), *SNMPv2 Management Information Base for the Internet Protocol using SMIPv2*. +- [9] IETF RFC 2012 (1996), *SNMPv2 Management Information Base for the Transmission Control Protocol using SMIPv2*. + +[10] IETF RFC 2013 (1996), *SNMPv2 Management Information Base for the User Datagram Protocol using SMIPv2*. + +# 3 Terms and definitions + +General terms and definitions related to maintenance are provided in ITU-T Rec. M.60 [3] and for IP performance are given in ITU-T Rec. Y.1540 [4]. This Recommendation defines the following terms: + +**3.1 Access Gateway (AG):** The IP network equipment that provides access to the AS and terminates the access protocol from the user. + +**3.2 Autonomous System (AS):** An IP network controlled and managed by a single authority and identified by a specific AS number in the whole Internet. An IP network operator may own and manage one or more ASs. + +**3.3 Border Gateway Protocol (BGP):** The Inter-Autonomous System routing protocol defined in RFC 1267 [7] that allows an AS to exchange routing information with other ASs. + +**3.4 Border Gateway Router (BGR):** A router, belonging to an AS, that exchanges network reachability information with the neighboured ASs. + +**3.5 connectivity:** The ability of an AS to provide a number of routes to its customers' traffic. An AS achieves whole Internet connectivity from its interconnection with other ASs. + +**3.6 Customer Premises Equipment (CPE):** Any network equipment sited on the customer's premises used to connect with an AS. This may include simple modems e.g. DSL, multiplexers, routers, switches or complete customer local area networks. + +**3.7 IP Operator Domain (IPOD):** Any connected subset of ASs together with all the links that interconnect them, which are under a single jurisdiction. The term IPOD can be used to refer to a single AS or any number of ASs and their interconnecting links. It can also be used to represent an entire single operator IP network and is defined between two OBGRs. + +**3.8 Management Information Base (MIB):** The database in a network element that contains configuration, event and performance data that is accessible by a management system. + +**3.9 Measurement Point (MP):** The physical or logical point at which measurements can be made and to which the data obtained is related. In the context of this Recommendation, this is typically at an OBGR. + +**3.10 Network Interface (NI):** The interface between the access network and the customer installation. + +**3.11 Operator Border Gateway Router (OBGR):** A router, belonging to an IPOD, that exchanges network reachability information with the neighboured IPOD. It is situated at the edge of an IPOD. + +**3.12 provisioning:** The installation, assignment and commissioning (including bringing-into-service testing) of network resources. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +AG Access Gateway + +AL Access Line + +AS Autonomous System + +BGP Border Gateway Protocol + +| | | +|------|--------------------------------------| +| BGR | Border Gateway Router | +| CPE | Customer Premises Equipment | +| DSL | Digital Subscriber Line | +| EGP | Edge Gateway Protocol | +| GbE | Gigabit Ethernet | +| ICMP | Internet Control Management Protocol | +| IP | Internet Protocol | +| IPDR | IP Packet Discard Rate | +| IPDV | IP Packet Delay Variation | +| IPER | IP Packet Error Ratio | +| IPLR | IP Packet Loss Ratio | +| IPOD | IP Operator Domain | +| IPTD | IP Packet Transfer Delay | +| MIB | Management Information Base | +| MP | Measurement Point | +| MPEG | Motion Picture Experts Group | +| MPLS | Multi-Protocol Label Switching | +| NI | Network Interface | +| OBGR | Operator Border Gateway Router | +| OC | Optical Channel | +| PO | Performance Objective | +| QoS | Quality of Service | +| R | Router | +| RFC | Request For Comment | +| SNMP | Simple Network Management Protocol | +| STM | Synchronous Transport Module | +| STS | Synchronous Transport Signal | +| TCP | Transmission Control Protocol | +| TMN | Telecommunication Management Network | +| VPN | Virtual Private Network | + +# 5 Reference network and procedures + +Figure 1 shows a typical flow of an IP customer's traffic, through an IP network across a number of IPODs to the distant end. + +![Figure 1/M.2301 – Example of an end-to-end IP flow. This diagram illustrates a network architecture where a Customer Premises Equipment (CPE) is connected to an operator's IP network via a Network Interface (NI). The CPE is part of a 'Customer installation' which includes an 'Access network'. The IP network itself is composed of multiple IP Operation Domains (IPODs), labeled IPOD 1, IPOD 2, and IPOD n. Each IPOD contains an Access Gateway (AG) and an Operator Border Gateway Router (OBGR). The IPODs are interconnected by dashed lines representing links between OBGRs. The entire IP network segment is labeled 'End-to-end network'. The connection between the two CPEs through the network is labeled 'User-to-user connection'. A label 'M.2301_F01' is present in the bottom right corner.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Figure 1/M.2301 – Example of an end-to-end IP flow. This diagram illustrates a network architecture where a Customer Premises Equipment (CPE) is connected to an operator's IP network via a Network Interface (NI). The CPE is part of a 'Customer installation' which includes an 'Access network'. The IP network itself is composed of multiple IP Operation Domains (IPODs), labeled IPOD 1, IPOD 2, and IPOD n. Each IPOD contains an Access Gateway (AG) and an Operator Border Gateway Router (OBGR). The IPODs are interconnected by dashed lines representing links between OBGRs. The entire IP network segment is labeled 'End-to-end network'. The connection between the two CPEs through the network is labeled 'User-to-user connection'. A label 'M.2301\_F01' is present in the bottom right corner. + +**Figure 1/M.2301 – Example of an end-to-end IP flow** + +The CPE is connected to the operator's IP network through, for example, a leased line. + +NOTE – The CPE may or may not contain a router, and the NI may be co-located with a router or not, depending on the connecting operators' agreement. Depending on the nature of the access link technology in use, the performance allocation given to this link may need to be greater than that for other links. Note that the IPOD may or may not include the access network portion. + +From that point on (Access Gateway), the routing is delegated to the routing policies of the operator. The NI is normally the physical point at which the jurisdiction boundary is located. It may be difficult to perform measurements at the NI. + +Figure 2 shows how an IPOD may contain more than one AS and the position of the OBGRs relative to the BGRs between ASs. + +![Figure 2/M.2301 – Example showing the make up of an IPOD. This diagram shows the internal structure of an IP Operation Domain (IPOD). On the left, a CPE connects to an AG via an NI. The AG is connected to a network of Autonomous Systems (ASes), represented by circles. These ASes are interconnected by Border Gateway Routers (BGRs), represented by squares with an 'X'. Some ASes also contain Operator Border Gateway Routers (OBGRs), represented by green diamonds. This group of ASes is labeled 'IPOD Operator A'. On the right, another IPOD, 'IPOD Operator B', is shown, also containing ASes and BGRs. The two IPODs are connected at their boundary by OBGRs. A legend at the bottom left identifies the symbols for BGR and OBGR. A label 'M.2301_F02' is present in the bottom right corner.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +Figure 2/M.2301 – Example showing the make up of an IPOD. This diagram shows the internal structure of an IP Operation Domain (IPOD). On the left, a CPE connects to an AG via an NI. The AG is connected to a network of Autonomous Systems (ASes), represented by circles. These ASes are interconnected by Border Gateway Routers (BGRs), represented by squares with an 'X'. Some ASes also contain Operator Border Gateway Routers (OBGRs), represented by green diamonds. This group of ASes is labeled 'IPOD Operator A'. On the right, another IPOD, 'IPOD Operator B', is shown, also containing ASes and BGRs. The two IPODs are connected at their boundary by OBGRs. A legend at the bottom left identifies the symbols for BGR and OBGR. A label 'M.2301\_F02' is present in the bottom right corner. + +**Figure 2/M.2301 – Example showing the make up of an IPOD** + +Figure 3 expands Figure 2 to show more detail of the reference network with indication of the network portions and Measurement Points (MPs). It shows how the neighbouring ASs connect together and each contains a number of interconnected routers and BGRs. + +![Figure 3/M.2301 – Example of a network topology for a typical IP customer. The diagram shows a network topology starting with a CPE (Intranet) connected to a BGR, which is connected to an Access network. The Access network is connected to an AG, which is part of an AS (Autonomous System) containing several R (Routers). The AS is connected to a BGR, which is connected to a Transport network. The Transport network is connected to another BGR, which is connected to Neighbouring ASs. The entire network structure is enclosed within an IPOD (IP Customer Domain).](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +Figure 3/M.2301 – Example of a network topology for a typical IP customer. The diagram shows a network topology starting with a CPE (Intranet) connected to a BGR, which is connected to an Access network. The Access network is connected to an AG, which is part of an AS (Autonomous System) containing several R (Routers). The AS is connected to a BGR, which is connected to a Transport network. The Transport network is connected to another BGR, which is connected to Neighbouring ASs. The entire network structure is enclosed within an IPOD (IP Customer Domain). + +**Figure 3/M.2301 – Example of a network topology for a typical IP customer** + +The hypothetical reference model used in this Recommendation is a network consisting of two access links and eight IPODs. For the more stringent QoS classes (QoS classes 0 and 2), the number of IPODs is reduced to three. Further details are given in clause 9. + +## 5.1 Definitions of availability + +The measurements defined in this Recommendation should only be performed on a network, or part of a network, during periods of availability. The definition and criteria of availability are under study and may depend on the application being supported by the IP network. For further information, see ITU-T Rec. Y.1540 [4]. + +In the case when test traffic is needed to check availability, the traffic generated specifically to test the availability state should be limited so that it does not cause congestion. This congestion could affect other traffic and/or could significantly increase the probability that the outage criteria will be exceeded. However, it should be noted that this test may not indicate the true availability for higher volumes of customers' traffic. The specification of the test packet stream is under study. + +## 5.2 Virtual private networks + +Each of the IPODs that support a Virtual Private Network (VPN) shall have been tested and be compliant with the figures in Table 3. End-to-end tests carried out on the VPN shall comply with the figures in Table 2. Performance limits for VPNs may be different (e.g. more stringent) dependent on Service Level Agreements between Service Provider and Customer. + +## 5.3 Bringing-into-service procedure + +When a new AS or new network resources are brought into service, the following procedure shall be adopted in order to check that the performance across an IPOD still meets the limits in this Recommendation. + +End-to-end flow tests should be carried out as described in clause 7 between each pair combination of OBGRs. Each test pair should meet the performance objectives of Table 3. Upon successful completion of this test the AS or network resources can be brought into service. + +The tests described in clause 7 should be repeated 24 hours after the AS or network resources have been brought into service in order to check that the introduction of them has not impaired the end-to-end performance. + +If either the initial test or the repeat test fails, appropriate fault management procedures should be initiated. + +Similarly, when a new link between two IPODs (pairs of OBGRs) is brought into service, the same procedure should apply and the limits in Table 4 should be met. Access links should meet the limits in Table 5. + +## 5.4 Maintenance procedure + +It is desirable that performance monitoring of an IPOD and links between IPODs is performed on a regular basis to check that performance is not degraded, and to indicate possible congestion or fault conditions. The overall set of measurements specified in clauses 7 and 8, or a subset of them, can be used for this purpose. This procedure may include the application of maintenance thresholds to one or more performance parameters. If these are exceeded, corrective maintenance actions should be initiated. The limits given in Tables 3, 4 and 5 should also be used for maintenance. + +After maintenance work on an AS, the network resources that have been repaired (routers or transmission links) should be tested to ensure the end-to-end performance can still be met. Further guidance on testing of individual routers and links is given in Appendix I. + +# 6 Measurement methods + +There are two basic approaches to performance measurement defined in this Recommendation. These are "intrusive" and "non-intrusive" which equate to the terms "active" and "passive" used by the IETF. Some performance parameters can be measured only intrusively, others only non-intrusively, and some both intrusively and non-intrusively as illustrated, for example using MIB monitoring1, in Table 1. + +**Table 1/M.2301 – Intrusive and non-intrusive measurement of performance parameters** + +| Parameter | Intrusive | Non-intrusive | +|-----------|-----------|---------------| +| IPTD | √ | | +| IPDV | √ | | +| IPER | √ | √ | +| IPLR | √ | √ | +| IPDR | | √ | + +## 6.1 Intrusive performance measurement (using test packets) + +Intrusive performance measurements are made by inserting test packets interleaved with the normal traffic flows between two MPs. This kind of measurement allows more detailed investigation of specific performance parameters e.g. one-way delay using time stamped packets, effect of packet size and number of packets on performance. + +It should be noted that intrusive performance measurement causes additional traffic through the network so care must be taken to ensure that the use of this test does not cause congestion and the subsequent loss of customer's packets. It is also important that the test is not carried out when customer traffic is so low that the results of the test are invalid. + +1 Note that other methods of non-intrusive measurement are possible. + +The test packet stream and the measurement period should be appropriate to the application service to be supported. The packet length and characteristics, and the intervals between measurement periods are for further study. + +## **6.2 Non-intrusive performance measurement (using MIB monitoring)** + +The performance can be assessed by interrogating all the routers for performance statistics and thus obtaining a real time view of the effect of the network on the traffic passing through that network. The data available are listed in RFC 1213 [6] and RFC 2011 [8]. RFC 1213 [6] has been updated by RFCs 2011 [8], 2012 [9] and 2013 [10] but only RFC 2011 [8] is applicable to this Recommendation. RFCs 1213 [6] and 2011 [8] include interface statistics, IP statistics, ICMP statistics, TCP statistics, EGP statistics and SNMP statistics. Only interface statistics and IP statistics should be used for performance measurement. This is because they will cover all traffic of all types and they will not be affected by the differences between the different protocols (e.g. the re-transmission of packets by TCP). + +This kind of measurement has the advantages of minimising impact on customer's traffic and testing every route through the network. Problems on links or routers can also be quickly identified. It should be noted, however, that non-intrusive measurements can realistically be done only within one IPOD since it may be difficult or undesirable for one operator to access the routers in another's IPOD. Results of non-intrusive measurements might be exchanged between connecting operators over a TMN X-interface. + +The application of MIB monitoring inside an IPOD is described in Appendix I. + +The measurements have to be made in pairs, which should be done 15 minutes apart except for those interfaces that are running at 1 Gbit/s or above. In the latter case, the readings should be separated by the time given in Table A.1 or less. + +# **7 Intrusive performance measurement** + +Intrusive measurement techniques are used when it is difficult or impossible to use non-intrusive measurements. One example could be one-way IP packet transfer delay (IPTD) and IP packet delay variation (IPDV). IPTD measurements require high resolution clocks accurate in frequency and phase. Another example is during the provisioning and turn-up process before applying live traffic to the network resources concerned. Intrusive measurements may also be used to evaluate error performance e.g. IP packet error ratio (IPER) and IP packet loss ratio (IPLR). It is not possible to measure packet discard ratio by this technique, as discarded packets cannot be identified separately from lost packets. For this reason the IPLR performance objectives in Table 3 have been increased to cover those packets discarded by the routers. Intrusive measurements are usually restricted to BGRs and OBGRs because of the practical problems of making such measurements at every router. + +## **7.1 One-way IP Packet Transfer Delay (IPTD)** + +This test is carried out between all pair combinations of OBGRs within an IPOD. All OBGR pairs should produce IPTD results within the performance objectives specified in Table 3. The test consists of sending a stream of time-stamped packets, distributed throughout the traffic, from one OBGR to the other. The time each packet is received is recorded. The time each packet was transmitted is subtracted from the received time to produce the one-way delay result for that packet. The worst case IPTD should be recorded and the number of test packets used should be sufficient to give a 95% confidence in this result. The same test should also be carried out on the connecting link between the OBGRs of neighbouring IPODs and end-to-end. The results for these two cases should be within the limits of Table 4 and Table 2 respectively. + +## 7.2 One-way IP Packet Delay Variation (IPDV) + +This test is carried out between all pair combinations of OBGRs within an IPOD using a similar test packet stream as for IPTD. All the OBGR pairs should produce an IPDV within the performance objectives specified in Table 3. One sequence of test packets is transmitted from one OBGR to the other. The one-way delay is calculated as above. The smallest IPTD figure is subtracted from the greatest to produce the delay variation and the number of test packets used should be sufficient to give a 95% confidence in this result (i.e. less than 5% of the population of IPTD values are not captured). The result should be within the limits specified in Table 3. The same test should also be carried out on the connecting link between the OBGRs of neighbouring IPODs and end-to-end. The results for these two cases should be within the limits of Table 4 and Table 2 respectively. + +## 7.3 IP Packet Loss Ratio (IPLR) + +This test is carried out between all pair combinations of OBGRs within an IPOD. All OBGR pairs should produce IPLR results within the performance objectives specified in Table 3. The test consists of sending a stream of numbered packets, distributed throughout the traffic, from one OBGR to the other. At the receiving OBGR the packets are checked to see if any are missing. The total number of missing packets is recorded, together with the total number of packets sent. The ratio between the two figures is the IPLR. The number of test packets used should be sufficient to give a 95% confidence in this result. The same test should also be carried out on the connecting link between the OBGRs of neighbouring IPODs and end-to-end. The results for these two cases should be within the limits of Table 4 and Table 2 respectively. + +## 7.4 IP Packet Error Ratio (IPER) + +This test is carried out between all pair combinations of OBGRs within an IPOD. All OBGR pairs should produce IPER results within the performance objectives specified in Table 3. The test consists of sending a stream of packets, distributed throughout the traffic, from one OBGR to the other. Each packet contains error checking bits. At the receiving OBGR each packet is checked for errors. The total number of errored packets is recorded, together with the total number of packets received. The ratio between the two figures is the IPER. The number of test packets used should be sufficient to give a 95% confidence in this result. The same test should also be carried out on the connecting link between the OBGRs of neighbouring IPODs and end-to-end. The results for these two cases should be within the limits of Table 4 and Table 2 respectively. + +# 8 Non-intrusive performance measurement using MIB monitoring + +As described earlier, the performance of an IPOD (including an individual AS) can be assessed by interrogating all the routers in that system for performance data and thus obtaining a real time view of the effect of the network on the traffic passing through that network. For any given link between any two routers, IPER and IPLR can be measured. + +The measurements can be made for every link in the IPOD or for specified links. Those links, which are chosen for any particular measurement, shall be known as a 'population of interest'. The MIB of an OBGR can be interrogated for comparison with the MIB of the neighbouring OBGR in order to obtain the performance of the connecting link between the neighbouring IPODs. + +The MIB in each router should be interrogated for the required counts. Those needed include: + +- ifInUcastPkts; +- ifInNUcastPkts; +- ifInDiscards; +- ifInErrors; +- ifInUnknownProtos; + +- ifOutUcastPkts; +- ifOutNUcastPkts; +- ifOutDiscards; +- ifOutErrors. + +For definitions of these counts, see RFC 1213 [6]. These readings should be made twice, separated by a specified time interval. This time interval between readings will depend on the data rate of the interface whose statistics are being collected. The time interval for each bit rate and procedures for dealing with counter roll-over are shown in Annex A. + +Figure 4 shows the passage of packets from one router to the next and the three points at which packet loss or packet errors can occur and be detected by MIB monitoring. + +![Diagram illustrating packet flow between a Source router and a Destination router across a Link under measurement. The Source router contains 'Higher layers' and an 'Interface'. Arrows from 'Higher layers' to 'Interface' are labeled 'Successful packets' and 'Errors & discards'. The 'Interface' connects to the 'Link under measurement'. Arrows from the 'Link' to the 'Destination router's 'Interface' are labeled 'Transmission losses' and 'Transmission errors'. The 'Destination router' also contains 'Higher layers' and an 'Interface'. Arrows from 'Interface' to 'Higher layers' are labeled 'Successful packets' and 'Errors & discards'. The diagram is labeled M.2301_F04.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Diagram illustrating packet flow between a Source router and a Destination router across a Link under measurement. The Source router contains 'Higher layers' and an 'Interface'. Arrows from 'Higher layers' to 'Interface' are labeled 'Successful packets' and 'Errors & discards'. The 'Interface' connects to the 'Link under measurement'. Arrows from the 'Link' to the 'Destination router's 'Interface' are labeled 'Transmission losses' and 'Transmission errors'. The 'Destination router' also contains 'Higher layers' and an 'Interface'. Arrows from 'Interface' to 'Higher layers' are labeled 'Successful packets' and 'Errors & discards'. The diagram is labeled M.2301\_F04. + +**Figure 4/M.2301 – The points at which packet loss and errors can occur** + +## 8.1 IP performance events + +### 8.1.1 Total IP packets received + +Total IP packets received is a count of the number of packets received at an interface. + +The total number of packet received across an interface is given by the sum of: + +- ifInUcastPkts; +- ifInNUcastPkts; +- ifInDiscards; +- ifInErrors; +- ifInUnknownProtos. + +Let this be known as ifInTotal. + +The number successfully delivered to a higher-layer protocol is given by the sum of: + +- ifInUcastPkts; +- ifInNUcastPkts. + +Let this be known as ifInOk. + +Alternatively this can be defined mathematically as follows: + +Define: + +$$\text{ifInTotal} = \text{ifInUcastPkts} + \text{ifInNUcastPkts} + \text{ifInDiscards} + \text{ifInErrors} + \text{ifInUnknownProtos}$$ + +$$\text{ifInOK} = \text{ifInUcastPkts} + \text{ifInNUcastPkts}$$ + +Define: + +$$\text{ifInErrored} = \text{ifInErrors} + \text{ifInUnknownProtos}$$ + +### 8.1.2 Total IP packets transmitted + +Total IP packets transmitted is a count of the number of packets submitted to an interface for onward transmission. + +The total number of packets submitted to an interface is given by the sum of: + +- $\text{ifOutUcastPkts}$ ; +- $\text{ifOutNUcastPkts}$ . + +Let this be known as $\text{ifOutTotal}$ . + +The number successfully transmitted over the link is given by the sum of: + +- $\text{ifOutUcastPkts}$ ; +- $\text{ifOutNUcastPkts}$ ; + +minus the sum of: + +- $\text{ifOutDiscards}$ ; +- $\text{ifOutErrors}$ . + +Let this be known as $\text{ifOutOk}$ . + +Or expressed mathematically: + +$$\text{ifOutTotal} = \text{ifOutUcastPkts} + \text{ifOutNUcastPkts}.$$ + +Then: + +$$\text{ifOutOK} = \text{ifOutTotal} - (\text{ifOutDiscards} + \text{ifOutErrors}).$$ + +### 8.1.3 IP Packet Error Ratio (IPER) + +IP packet error ratio is the ratio of total errored IP packet outcomes to the total of successful IP packet transfer outcomes, plus errored IP packet outcomes, in a population of interest. + +The number of packets received, which are errored, is given by the sum of: + +- $\text{ifInErrors}$ ; +- $\text{ifInUnknownProtos}$ . + +Let this be known as $\text{ifInErrored}$ . + +The packet error ratio is the ratio of $\text{ifInErrored}$ to $\text{ifInTotal}$ . + +Or expressed mathematically: + +$$\text{IPER} = (\text{ifInErrors} + \text{ifInUnknownProtos}) / \text{ifInTotal}.$$ + +### 8.1.4 IP Packet Loss Ratio (IPLR) + +IP packet loss ratio is the ratio of total lost IP packet outcomes to total transmitted IP packets in a population of interest. + +The packet loss ratio is the ratio of packets received and delivered to the higher layer to the number of packets submitted for transmission i.e. ifInOk to ifOutTotal. + +Or expressed mathematically: + +$$\text{IPLR} = (\text{ifInUcastPkts} + \text{ifInNUcastPkts}) / \text{ifOutTotal}.$$ + +### 8.1.5 IP Packet Discard Ratio (IPDR) + +IP packet discard ratio is the ratio of total discarded IP packet outcomes to total transmitted IP packets in a population of interest. Discarded packets are those packets which are deliberately lost although they are without error. Packets are usually discarded because there is insufficient buffer space to store the packets while they await processing. Thus IP packet discard ratio is a measurement of network congestion. + +The number of packets discarded is given by the sum of: + +- ifInDiscards; +- ifOutDiscards. + +Let this be known as ifDiscardTotal. + +The packet discard ratio is the ratio of ifDiscardTotal to ifOutTotal. + +Expressing this mathematically gives: + +$$\text{IPDR} = (\text{ifInDiscards} + \text{ifOutDiscards}) / \text{ifOutTotal}.$$ + +# 9 Performance objectives for IP networks + +The figures given in the following tables are based on a hypothetical reference model consisting of two access links and eight IPODs connected by seven OBGR-to-OBGR connecting links, for a total length of 27,500 km. Since the stringent IPTD objectives of QoS classes 0 and 2 cannot be guaranteed on such long distances, a reduced reference model consisting of two access links and three IPODs connected by two OBGR-to-OBGR connecting links, for a total length of 10,000 km has been used for these QoS classes. + +The IPODs have been allocated two thirds of the overall end-to-end performance objective and the connecting links one third. The access links have *each* been allocated 17.5% of the total connecting link allocation (i.e. 5.83% of the total end-to-end performance objective). The performance objectives for a single IPOD or connecting link between adjacent IPODs are derived by apportioning the end-to-end performance objectives. In the case of IPER, this can produce a slightly pessimistic view of the error ratio, especially for increasing values of IPER. This depends on the error statistics and their relationship to the packet length statistics. + +## 9.1 End-to-end IP flow + +The following performance objectives are specified for an end-to-end IP flow through two or more IPODs: + +**Table 2/M.2301 – IP QoS class definitions and network performance objectives for an end-to-end IP flow** + +| Parameter
QoS Class | IPTD | IPDV | IPLR | IPER | IPDR | +|------------------------|--------|-------|-----------------------------|--------------------|--------------------| +| Class 0 | 100 ms | 50 ms | $5 \times 10^{-4}$ (Note 1) | $5 \times 10^{-5}$ | $5 \times 10^{-4}$ | +| Class 1 | 400 ms | 50 ms | $5 \times 10^{-4}$ (Note 1) | $5 \times 10^{-5}$ | $5 \times 10^{-4}$ | +| Class 2 | 100 ms | U | $5 \times 10^{-4}$ | $5 \times 10^{-5}$ | $5 \times 10^{-4}$ | +| Class 3 | 400 ms | U | $5 \times 10^{-4}$ | $5 \times 10^{-5}$ | $5 \times 10^{-4}$ | +| Class 4 | 1 s | U | $5 \times 10^{-4}$ | $5 \times 10^{-5}$ | $5 \times 10^{-4}$ | +| Class 5 | U | U | U | U | U | + +NOTE 1 – Some applications (e.g. MPEG-2) may require $IPLR < 5 \times 10^{-5}$ . + +NOTE 2 – "U" means "unspecified" or "unbounded". When the performance relative to a particular parameter is identified as being "U" the ITU-T establishes no objective for this parameter and any default Y.1541 [5] objective can be ignored. When the objective for a parameter is set to "U", performance with respect to that parameter may, at times, be arbitrarily poor. + +## 9.2 IP flow across a single IPOD + +The following performance objectives are specified for an IP flow across a single IPOD. There are 8 IPODs in the reference model, and therefore the performance objective for one IPOD is given by the formulae: + +Single IPOD objective = End-to-end objective $\times 2/3 \times 1/8$ (for QoS classes 1, 3, 4 and 5). + +Single IPOD objective = End-to-end objective $\times 2/3 \times 1/3$ (for QoS classes 0 and 2). + +**Table 3/M.2301 – IP QoS class definitions and network performance objectives for an IP flow across a single IPOD** + +| Parameter
QoS Class | IPTD | IPDV | IPLR | IPER | IPDR | +|------------------------|-----------------------|------|----------------------------------|----------------------|----------------------------------| +| Class 0 | 11 + P ms
(Note 3) | FFS | $1.1 \times 10^{-4}$
(Note 1) | $1.1 \times 10^{-5}$ | $1.1 \times 10^{-4}$
(Note 1) | +| Class 1 | 22 + P ms
(Note 3) | FFS | $4.2 \times 10^{-5}$
(Note 1) | $4.2 \times 10^{-6}$ | $4.2 \times 10^{-5}$
(Note 1) | +| Class 2 | 11 + P ms
(Note 3) | U | $1.1 \times 10^{-4}$ | $1.1 \times 10^{-5}$ | $1.1 \times 10^{-4}$ | +| Class 3 | 22 + P ms
(Note 3) | U | $4.2 \times 10^{-5}$ | $4.2 \times 10^{-6}$ | $4.2 \times 10^{-5}$ | +| Class 4 | 72 + P ms
(Note 3) | U | $4.2 \times 10^{-5}$ | $4.2 \times 10^{-6}$ | $4.2 \times 10^{-5}$ | +| Class 5 | U | U | U | U | U | + +NOTE 1 – Some applications (e.g. MPEG-2) may require more stringent IPLR. + +NOTE 2 – "U" means "unspecified" or "unbounded". When the performance relative to a particular parameter is identified as being "U" the ITU-T establishes no objective for this parameter and any default Y.1541 [5] objective can be ignored. When the objective for a parameter is set to "U", performance with respect to that parameter may, at times, be arbitrarily poor. + +NOTE 3 – If the route distance between OBGRs across the IPOD exceeds 200 km then a propagation delay term, P, is added. This is calculated by multiplying the route distance (in km) by 5, dividing by 1000 and rounding down to an integer. This effectively allows 1 ms for each integer multiple of 200 km. See Table 6 for calculation of route distance when only air distance is known. + +NOTE 4 – The delay performance limits are derived from the formulae above the table after having removed, from the overall end-to-end IPTD, the delay resulting from the network length (137 ms for QoS classes 1, 3, 4 and 5; 50 ms for QoS classes 0 and 2). The distance-dependent factor, P, might result in the overall end-to-end flow performance objectives not being met for the case of large IPODs. For example, in some extreme geographical cases, or with a satellite hop, it may not be possible to meet the overall end-to-end delay performance limits. As a result, some highly interactive IP-based services may not be viable. + +## 9.3 Single link between two adjacent IPODs + +The following performance objectives are specified for the single link between the two OBGRs across the boundary between two IPODs. There are 8 IPODs in the reference model, and therefore the performance objective for one connecting link between adjacent IPODs is given by the formulae: + +Single link objective = End-to-end objective $\times 1/3 \times 0.65 \times 1/7$ (for QoS classes 1, 3, 4, 5). + +Single link objective = End-to-end objective $\times 1/3 \times 0.65 \times 1/2$ (for QoS classes 0 and 2). + +**Table 4/M.2301 – IP QoS class definitions and network performance objectives for a single link between OBGRs** + +| Parameter
QoS Class | IPTD | IPDV | IPLR | IPER | IPDR | +|------------------------|-----------------------|------|----------------------|----------------------|----------------------| +| Class 0 | 5 + P ms
(Note 1) | FFS | $5.4 \times 10^{-5}$ | $5.4 \times 10^{-6}$ | $5.4 \times 10^{-5}$ | +| Class 1 | 8 + P ms
(Note 1) | FFS | $1.5 \times 10^{-5}$ | $1.5 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 2 | 5 + P ms
(Note 1) | U | $5.4 \times 10^{-5}$ | $5.4 \times 10^{-6}$ | $5.4 \times 10^{-5}$ | +| Class 3 | 8 + P ms
(Note 1) | U | $1.5 \times 10^{-5}$ | $1.5 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 4 | 27 + P ms
(Note 1) | U | $1.5 \times 10^{-5}$ | $1.5 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 5 | U | U | U | U | U | + +NOTE 1 – If the route distance between OBGRs of adjacent IPODs exceeds 200 km, then a propagation delay term, P, is added. This is calculated by multiplying the route distance (in km) by 5, dividing by 1000 and rounding down to an integer. This effectively allows 1 ms for each integer multiple of 200 km. See Table 6 for calculation of route distance when only air distance is known. + +NOTE 2 – The delay performance limits are derived from the formulae above the table after having removed, from the overall end-to-end IPTD, the delay resulting from the network length (137 ms for QoS classes 1, 3, 4 and 5; 50 ms for QoS classes 0 and 2). The distance-dependent factor, P, might result in the overall end-to-end flow performance objectives not being met for the case of large distances between IPODs. For example, in some extreme geographical cases, or with a satellite hop, it may not be possible to meet the overall end-to-end delay performance limits. As a result, some highly interactive IP-based services may not be viable. + +## 9.4 Access Links + +The following performance objectives are specified for the access link between the NI and the AG. The performance objective for one access link is given by the formula: + +$$\text{Access link objective} = \text{End-to-end objective} \times 1/3 \times 0.175$$ + +**Table 5/M.2301 – IP QoS class definitions and network performance objectives for a single access link** + +| Parameter
QoS Class | IPTD | IPDV | IPLR | IPER | IPDR | +|------------------------|-----------------------|------|--------------------|--------------------|--------------------| +| Class 0 | 3 + P ms
(Note 1) | FFS | $3 \times 10^{-5}$ | $3 \times 10^{-6}$ | $3 \times 10^{-5}$ | +| Class 1 | 15 + P ms
(Note 1) | FFS | $3 \times 10^{-5}$ | $3 \times 10^{-6}$ | $3 \times 10^{-5}$ | +| Class 2 | 3 + P ms
(Note 1) | U | $3 \times 10^{-5}$ | $3 \times 10^{-6}$ | $3 \times 10^{-5}$ | +| Class 3 | 15 + P ms
(Note 1) | U | $3 \times 10^{-5}$ | $3 \times 10^{-6}$ | $3 \times 10^{-5}$ | +| Class 4 | 50 + P ms
(Note 1) | U | $3 \times 10^{-5}$ | $3 \times 10^{-6}$ | $3 \times 10^{-5}$ | +| Class 5 | U | U | U | U | U | + +NOTE 1 – If the route distance of an access link exceeds 200 km, then a propagation delay term, P, is added. This is calculated by multiplying the route distance (in km) by 5, dividing by 1000 and rounding down to an integer. This effectively allows 1 ms for each integer multiple of 200 km. See Table 6 for calculation of route distance when only air distance is known. + +NOTE 2 – The delay performance limits are derived from the formula above the table after having removed, from the overall end-to-end IPTD, the delay resulting from the network length (137 ms for QoS classes 1, 3, 4 and 5; 50 ms for QoS classes 0 and 2). The distance-dependent factor, P, might result in the overall end-to-end flow performance objectives not being met for the case of long access links. For example, in some extreme geographical cases, or with a satellite hop, it may not be possible to meet the overall end-to-end delay performance limits. As a result, some highly interactive IP-based services may not be viable. + +## 9.5 Calculation of route distance + +Table 6 contains the formulae for calculating the route distance when only air distance is known. + +**Table 6/M.2301 – Calculated route distance** + +| Air route distance d | Calculated route distance | +|-------------------------|---------------------------| +| $d < 1000$ km | $d \times 1.5$ km | +| $1000 \leq d < 1200$ km | 1500 km | +| $d \geq 1200$ km | $d \times 1.25$ km | + +# Annex A + +## Procedures for reading router MIB registers + +This annex contains procedures for reading router MIB registers. Table A.1 contains the elapsed time required between readings of the MIB values depending on the interface bit rate. + +**Table A.1/M.2301 – Elapsed time between readings of MIB values** + +| ITU Designation | ATIS T1 Designation | Data rate (Mbit/s) | Elapsed time | +|----------------------|----------------------|--------------------|--------------| +| IEEE 802.2 Ethernet | IEEE 802.2 Ethernet | 10 | 24 hrs | +| E3 | | 34 | 12 hrs | +| | DS3 | 45 | 12 hrs | +| IEEE 802.3u Ethernet | IEEE 802.3u Ethernet | 100 | 140 mins | +| STM-1 | STS-3/OC-3 | 155 | 3 hrs | +| STM-4 | STS-12/OC-12 | 622 | 50 mins | +| IEEE 802.3z GbE | IEEE 802.3z GbE | 1000 | 14 mins | +| STM-16 | STS-48/OC-48 | 2488 | 10 mins | +| IEEE 802.3ae GbE | IEEE 802.3ae GbE | 10 000 | 1 min | + +When making non-intrusive measurements, the MIB in each router is read twice, once at the start of the measurement period and once at the end. The end reading will generally be greater than the start. In that case, the start is subtracted from the end to produce the value for the parameter being measured. On some occasions the counter will 'roll-over' (that is, reach maximum count and start again at zero). The values in Table A.1 have been so chosen that this will not happen twice during one measurement period. + +When roll-over happens, the end reading will be less than the start. Before the correct value can be calculated it is necessary to determine whether the counter is 32 bit or 64 bit. All MIBs accessed by SNMP v1 use 32 bit counters, as v1 does not support 64 bit counters. If SNMP v2c or v3 is being used it is possible that some of the counters are 64 bit. The 64 bit counters have the letter 'HC' (meaning High Capacity) in the counter name. For example, the counter ifHCInUcastPkts has 64 bits whereas ifInUcastPkts has 32 bits. + +Now consult Figure A.1 to find out how to calculate value from the two counter readings. + +![Flowchart to determine MIB counter values. The process starts with 'Start', followed by 'Take two readings of counter'. A decision diamond 'Is End > Start?' has a 'Yes' path leading to 'Subtract Start from End' and a 'No' path leading to another decision diamond 'Is counter 64 bit?'. The 'Is counter 64 bit?' diamond has a 'Yes' path leading to 'Add 18446744073709551616 to End' and a 'No' path leading to 'Add 4294967296 to End'. Both 'Add' boxes lead to 'Subtract Start from End', which then leads to 'Finish'. The label 'M.2301_FA.1' is present near the bottom right of the flowchart.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +``` +graph TD; Start([Start]) --> A[Take two readings of counter]; A --> B{Is End > Start?}; B -- Yes --> E[Subtract Start from End]; B -- No --> C{Is counter 64 bit?}; C -- Yes --> D[Add 18446744073709551616 to End]; C -- No --> F[Add 4294967296 to End]; D --> E; F --> E; E --> G([Finish]); +``` + +M.2301\_FA.1 + +Flowchart to determine MIB counter values. The process starts with 'Start', followed by 'Take two readings of counter'. A decision diamond 'Is End > Start?' has a 'Yes' path leading to 'Subtract Start from End' and a 'No' path leading to another decision diamond 'Is counter 64 bit?'. The 'Is counter 64 bit?' diamond has a 'Yes' path leading to 'Add 18446744073709551616 to End' and a 'No' path leading to 'Add 4294967296 to End'. Both 'Add' boxes lead to 'Subtract Start from End', which then leads to 'Finish'. The label 'M.2301\_FA.1' is present near the bottom right of the flowchart. + +**Figure A.1/M.2301 – Flowchart to determine MIB counter values** + +It should be noted that most IP network equipment uses a SNMP management interface, but other types of protocol are not precluded. + +# **Appendix I** + +## **Performance within an IPOD** + +## **I.1 Single link between two adjacent routers** + +When an individual link or router is added to an existing AS, it could be tested by the methods defined in this Recommendation. An operator of IP networks may wish to use the non-intrusive performance measurement technique, defined in clause 8, to monitor its network on a regular basis. This will enable links and routers with a poor performance to be quickly identified and will also give early warning of a need to re-engineer the network to cope with increasing traffic. Trouble spots can be identified and dealt with before user traffic is badly affected. + +The performance objectives for a connecting link between routers are derived by apportioning the end-to-end performance objectives. In the case of IPER, this can produce a slightly pessimistic view of the error ratio, especially for increasing values of IPER. This depends on the error statistics and their relationship to the packet length statistics. + +Table I.1 specifies the performance objectives for each link between adjacent routers within the same AS: + +**Table I.1/M.2301 – IP QoS class definitions and network performance objectives for a single link between routers** + +| Parameter
QoS Class | IPTD | IPDV | IPLR | IPER | IPDR | +|------------------------|-----------------------|------|----------------------|----------------------|----------------------| +| Class 0 | 5 + P ms
(Note 1) | FFS | $5.4 \times 10^{-5}$ | $5.4 \times 10^{-6}$ | $5.4 \times 10^{-5}$ | +| Class 1 | 8 + P ms
(Note 1) | FFS | $1.5 \times 10^{-5}$ | $1.5 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 2 | 5 + P ms
(Note 1) | U | $5.4 \times 10^{-5}$ | $5.4 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 3 | 8 + P ms
(Note 1) | U | $1.5 \times 10^{-5}$ | $1.5 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 4 | 27 + P ms
(Note 1) | U | $1.5 \times 10^{-5}$ | $1.5 \times 10^{-6}$ | $1.5 \times 10^{-5}$ | +| Class 5 | U | U | U | U | U | + +NOTE 1 – If the route distance between routers exceeds 200 km, then a propagation delay term, P, is added. This is calculated by multiplying the route distance (in km) by 5, dividing by 1000 and rounding down to an integer. See Table 6 for calculation of route distance when only air distance is known. + +NOTE 2 – The distance-dependent factor, P, might result in the overall end-to-end flow performance objectives not being met for the case of large IPODs. For example, in some extreme geographical cases, or with a satellite hop, it may not be possible to meet the overall end-to-end delay performance limits. As a result, some highly interactive IP-based services may not be viable. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.2401-200312-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.2401-200312-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/M/T-REC-M.2401-200312-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/M/T-REC-M.2401-200312-I_PDF-E/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/M/T-REC-M.2401-200312-I_PDF-E/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b8ebd5d7d52ebe5af67e46d2c1a1b475e990b8 --- /dev/null +++ b/marked/M/T-REC-M.2401-200312-I_PDF-E/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9fd53bb4ad0d21e52f9fbb4d47c1f8e474e3d234b95e48025efe20a89bbdc0f +size 51075 diff --git a/marked/M/T-REC-M.2401-200312-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/M/T-REC-M.2401-200312-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a06cb25052ccf3628b223a543a834ebedfaf29ee --- /dev/null +++ b/marked/M/T-REC-M.2401-200312-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8d2347b98c83eb81a8be1b193373019d58d3cda070c23692b0711fa0d1a6300 +size 50208 diff --git a/marked/M/T-REC-M.2401-200312-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/M/T-REC-M.2401-200312-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b9b350ba5fd88b8028c5ab25e5f46d8b75595c7 --- /dev/null +++ b/marked/M/T-REC-M.2401-200312-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e611f5ca1e32b1445f837e2965cfae8381f4ba4384c6a82480ea40a919b99fe2 +size 60774 diff --git a/marked/M/T-REC-M.2401-200312-I_PDF-E/raw.md b/marked/M/T-REC-M.2401-200312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0385cc7a45a782ea4e94db406c8a7b5c34f62fdb --- /dev/null +++ b/marked/M/T-REC-M.2401-200312-I_PDF-E/raw.md @@ -0,0 +1,552 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.2401** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(12/2003) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +International transport network + +--- + +**Error performance limits and procedures for +bringing-into-service and maintenance of +multi-operator international paths and sections +within an optical transport network** + +ITU-T Recommendation M.2401 + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.2401** + +# **Error performance limits and procedures for bringing-into-service and maintenance of multi-operator international paths and sections within an optical transport network** + +## **Summary** + +This Recommendation gives error performance objectives, limits and procedures for bringing-into-service (BIS) and maintenance of multi-operator international ODUK Paths and OTUK Sections in an Optical Transport Network (OTN). + +## **Source** + +ITU-T Recommendation M.2401 was approved by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure on 14 December 2003. + +## **Keywords** + +Background block error, bringing-into-service, error detection code, error performance objectives, error performance parameters, forward error correction, in-service measurements, ODUK path monitoring, optical transport network, OTN maintenance, severely errored second. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +###### Page + +| | | | +|------|--------------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 1 | +| 4 | Abbreviations..... | 2 | +| 5 | Transport entities in the OTN..... | 3 | +| 5.1 | General introduction..... | 3 | +| 5.2 | Bidirectional transport entities and uni-directional monitoring ..... | 4 | +| 6 | Performance monitoring capabilities in the OTN..... | 4 | +| 6.1 | Optical impairments and digital error performance ..... | 4 | +| 6.2 | Monitored layer signals ..... | 5 | +| 6.3 | ODUk and OTUk overhead..... | 5 | +| 6.4 | In-Service Monitoring and Out-of-Service Measurement..... | 6 | +| 7 | Error performance events and parameters ..... | 6 | +| 7.1 | Severely Errored Seconds and Background Block Errors..... | 6 | +| 7.2 | FEC Corrected Errors ..... | 7 | +| 8 | Availability ..... | 7 | +| 9 | Network reference model ..... | 7 | +| 10 | Error performance objectives ..... | 8 | +| 10.1 | Error performance objectives for the HROP ..... | 8 | +| 10.2 | Error performance objectives for the domains of a real path ..... | 8 | +| 10.3 | Error performance objectives for the section ..... | 8 | +| 11 | Performance limits – General considerations ..... | 9 | +| 11.1 | Relationship between performance limits and performance objectives ..... | 9 | +| 11.2 | Types of limits..... | 9 | +| 12 | Bringing-Into-Service procedures and limits..... | 10 | +| 12.1 | Calculation of the BIS limits ..... | 10 | +| 13 | Performance levels and limits for maintenance..... | 11 | +| 13.1 | Calculation of limits for maintenance ..... | 11 | + + + +# Error performance limits and procedures for bringing-into-service and maintenance of multi-operator international paths and sections within an optical transport network + +# 1 Scope + +This Recommendation gives error performance objectives, limits and procedures for bringing-into-service (BIS) and maintenance of multi-operator international ODUk paths and OTUk sections in an Optical Transport Network (OTN). + +Note that possible consequences for the BIS and maintenance following from the use of an OTN as a server network for analog client signals is outside the scope of this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation G.709/Y.1331 (2003), *Interfaces for the Optical Transport Network (OTN)*. +- ITU-T Recommendation G.798 (2002), *Characteristics of optical transport network hierarchy equipment functional blocks*. +- ITU-T Recommendation G.874 (2001), *Management aspects of the optical transport network element*. +- ITU-T Recommendation G.7710/Y.1701 (2001), *Common equipment management function requirements*. +- ITU-T Recommendation G.8201 (2003), *Error performance parameters and objectives for multi-operator international paths within the Optical Transport Network (OTN)*. +- ITU-T Recommendation M.20 (1992), *Maintenance philosophy for telecommunication networks*. +- ITU-T Recommendation M.60 (1993), *Maintenance terminology and definitions*. +- ITU-T Recommendation M.2110 (2002), *Bringing into service international multi-operator paths, sections and transmission systems*. +- ITU-T Recommendation M.2120 (2002), *International multi-operator paths, sections and transmission systems fault detection and localization procedures*. + +# 3 Terms and definitions + +General terms and definitions related to maintenance are provided in ITU-T Recs M.20 and M.60. Terms and definitions related to OTN performance assessment are given in ITU-T Rec. G.8201. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|---------------------------------------------| +| 3R | Reamplification, Reshaping and Retiming | +| APO | Allocated Performance Objective | +| BBE | Background Block Error | +| BBER | Background Block Error Ratio | +| BDI | Backward Defect Indication | +| BEI | Backward Error Indication | +| BIP | Bit Interleaved Parity | +| BIS | Bringing-Into-Service | +| BISPO | Bringing-Into-Service Performance Objective | +| BOD | Backbone Operator Domain | +| DPL | Degraded Performance Level | +| DXC | Digital Crossconnect | +| EDC | Error Detection Code | +| EMF | Equipment Management Function | +| ES | Errored Second | +| ESR | Errored Second Ratio | +| FCE | FEC Corrected Errors | +| FEC | Forward Error Correction | +| HROP | Hypothetical Reference Optical Path | +| IOD | Inter-Operator Domain | +| ISM | In-Service Monitoring | +| LOD | Local Operator Domain | +| LT | Line Terminal | +| OCADM | Optical Add/Drop Multiplexer | +| OCh | Optical Channel | +| OCXC | Optical Crossconnect | +| OD | Operator Domains | +| ODUk | Optical Data Unit k, where k = 1, 2, 3 | +| OG | Operator Gateway | +| OH | Overhead | +| OMS | Optical Multiplex Section | +| OPUk | Optical Payload Unit k, where k = 1, 2, 3 | +| OS | Optical Section | +| OSM | Out-of-Service Measurement | +| OTN | Optical Transport Network | + +| | | +|------|---------------------------------------------| +| OTUk | Optical Transport Unit k, where k = 1, 2, 3 | +| PO | Performance Objective | +| PRBS | Pseudo-Random Binary Sequence | +| ROD | Regional Operator Domain | +| SES | Severely Errored Second | +| SESR | Severely Errored Second Ratio | +| SLA | Service Level Agreement | +| STM | Synchronous Transport Module | +| TP | Test Period | +| UPL | Unacceptable Performance Level | + +# 5 Transport entities in the OTN + +## 5.1 General introduction + +Figure 1 provides a simplified view of the OTN information structure hierarchy. The client signal, together with associated overhead, is mapped into the payload area of an Optical Payload Unit k (OPUk). The OPUk, together with its overhead, is mapped into the payload area of an Optical Data Unit k (ODUk). The ODUk, together with its overhead, is mapped into the payload area of an Optical Transport Unit k (OTUk). The OTUk is transported over the optical carrier network by inserting it in an Optical Channel (OCh). This picture does not show the various layers of the optical carrier network as their details are not relevant for the purpose of this Recommendation. + +![Diagram of OTN signal structure hierarchy showing the mapping of client signals into OTUk for transport over an optical carrier network.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +The diagram illustrates the hierarchical mapping of signals in OTN. At the top, a 'Client signal' is shown. Below it, the signal is mapped into an 'OCh Payload unit' consisting of an 'OH' (Overhead) section and a 'Payload' section. This is then mapped into an 'OCh Data unit k' consisting of an 'OH' section and an 'OPUk' section. Next, it is mapped into an 'OCh Transport unit k' consisting of an 'OH' section, an 'ODUk' section, and an 'FEC' (Forward Error Correction) section. The 'ODUk' section is further shown as being mapped into an 'OTUk' section. Finally, the 'OTUk' section is shown being transported over the 'Optical carrier network'. The diagram is labeled 'M.2401\_F01' at the bottom right. + +Diagram of OTN signal structure hierarchy showing the mapping of client signals into OTUk for transport over an optical carrier network. + +Figure 1/M.2401 – OTN signal structure + +The ODUk and OTUk overhead (OH) bytes contain information used to check and to control the behaviour of the transport network. For the purpose of error performance monitoring, the Path Monitoring bytes in the ODUk OH and the Section Monitoring bytes in the OTUk OH are relevant: they contain amongst others Bit Interleaved Parity (BIP), Backward Error Indication (BEI) and Backward Defect Indication (BDI) information. + +Note that the OPUk OH bytes do not contain error performance monitoring-related information. + +The Forward Error Correction (FEC) bytes, which are part of the OTUk, serve the purpose of improving the error performance of the payload (in this case the ODUk together with its OH) under given optical transport conditions. + +Figure 2 shows how these transport entities may be used in an example OTN. In this example, the client signal transported between the terminating Digital Crossconnects (DXCs) is an STM-N. This STM-N is carried on the concatenation of an SDH section (OSn) and the end-to-end connection in the OTN, the ODUk. The ODUk is carried on a concatenation of OTUks, each delimited by a 3R regeneration point. Each OTUk is associated with an optical wavelength by means of the OCh. A number of OChs are multiplexed into an Optical Multiplex Section n (OMSn), which spans the distance between the line-terminating equipment: LTs, OCADMs, OCXCs. + +![Diagram illustrating the usage of transport entities in the OTN. The diagram shows a path from a Client (DXC) through various optical transport components. The path starts with an STM-N signal, which is carried on an ODUk. The ODUk is carried on an OTUk, which is associated with an OCh. The OCh is multiplexed into an OMSn. The OMSn is carried on an OTSn. The OTSn is carried on an OSn. The path includes a 3R (Reamplification, Reshaping and Retiming) point, an OCADM (Optical Add/Drop Multiplexer), an OCXC (Optical Crossconnect), and another 3R point. The path ends at another Client (DXC). The diagram is labeled with various transport entities: STM-N, ODUk, OCh, OTUk, OMSn, OTSn, OSn, 3R, DXC, Client, OCADM, OCXC, OTM-0, OTM-n, R, and M.2401_F02.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Diagram illustrating the usage of transport entities in the OTN. The diagram shows a path from a Client (DXC) through various optical transport components. The path starts with an STM-N signal, which is carried on an ODUk. The ODUk is carried on an OTUk, which is associated with an OCh. The OCh is multiplexed into an OMSn. The OMSn is carried on an OTSn. The OTSn is carried on an OSn. The path includes a 3R (Reamplification, Reshaping and Retiming) point, an OCADM (Optical Add/Drop Multiplexer), an OCXC (Optical Crossconnect), and another 3R point. The path ends at another Client (DXC). The diagram is labeled with various transport entities: STM-N, ODUk, OCh, OTUk, OMSn, OTSn, OSn, 3R, DXC, Client, OCADM, OCXC, OTM-0, OTM-n, R, and M.2401\_F02. + +| | | | | +|-------|-----------------------------------------|-------|--------------------------------| +| 3R | Reamplification, Reshaping and Retiming | OSn | Optical Section Layer, level n | +| DXC | Digital Crossconnect | OTM-0 | Optical Transport Module 0 | +| OCADM | Optical Add/Drop Multiplexer | OTM-n | Optical Transport Module n | +| OCh | Optical Channel | OTSn | Optical Transport Section n | +| OCXC | Optical Crossconnect | OTUk | Optical Transport Unit k | +| ODUk | Optical Data Unit k | R | Repeater | +| OMSn | Optical Multiplex Section n | STM-N | Synchronous Transport Module N | +| OPS0 | Optical Physical Section 0 | | | + +Figure 2/M.2401 – Usage of transport entities in the OTN + +## 5.2 Bidirectional transport entities and unidirectional monitoring + +ITU-T Rec. G.709/Y.1331 defines the ODUk and the OTUk as bidirectional transport entities. ITU-T Rec. G.821 defines error performance objectives for bidirectional ODUks. However, for the purposes of BIS and maintenance, both directions are treated as independent entities and all objectives set forth in this Recommendation shall be met by each direction independently of the condition of the other direction. Clause 8 provides further clarification on this issue. + +# 6 Performance monitoring capabilities in the OTN + +## 6.1 Optical impairments and digital error performance + +While traversing an optical fibre or an optically transparent network element, an optical signal is subject to a number of physical phenomena which impair the quality of the signal. Typical examples are attenuation, polarization mode dispersion, chromatic dispersion, four-wave mixing and various scattering phenomena. This Recommendation does not elaborate on the details of these phenomena and the mechanisms through which they might affect the quality of the transport services provided by the optical signal. From the perspective of a client, it is sufficient to recognize that such impact may exist. The way in which this impact may be perceived, detected and quantified depends on the nature of the client signal. As the scope of this Recommendation is limited to digital + +client signals as standardized in ITU-T Rec. G.709/Y.1331, it uses the digital error performance of the ODUk and OTUk layer signals as a means to assess the quality of the transport services provided by an OTN. + +## 6.2 Monitored layer signals + +This Recommendation sets objectives and limits for the path (ODUk) and the section (OTUk). The rationale is: + +- The ODUk is the end-to-end connection in the OTN. Monitoring is needed because its performance is the performance of the OTN as perceived by the client. +- The OTUk is the connection between two 3R regeneration points in the network. 3R regeneration is needed because the current state of technology does not permit the construction of a worldwide transparent optical transport network. At a 3R regeneration point the optical signal is converted to an electrical signal, subsequently it is reshaped and retimed such that it conforms to the applicable pulse mask and jitter requirements, and converted again to optical format (O-E-O conversion). Monitoring is needed to support maintenance of the optical connections formed by 3R regeneration spans. + +ODUk Tandem Connection (ODUkT): + +- The ODUkT is specifically created to enable the monitoring of the performance of a part of a path without affecting the end-to-end monitoring of that path. Applications are: monitoring of an Operator Domain (see clause 9), and monitoring of a transport service provided by a subcontractor within an Operator Domain. Such monitoring might be needed to verify compliance with the applicable Service Level Agreement (SLA). + +## 6.3 ODUk and OTUk overhead + +In order to be able to assess the error performance of the transport service provided by the OTN without being dependent on *a priori* knowledge of the client signal, the ODUk and OTUk layers provide error performance information themselves. This is accomplished by means of an error detection code (EDC) scheme. In the OTN, the EDC is a BIP-8 code. + +At the transmit end, the parity information over the payload signal is calculated. This information is transmitted together with the payload signal, in the applicable OH bytes. At the receive end, the parity information is extracted. Simultaneously, at the receive end, the parity information over the payload signal is recalculated. The received parity information and the recalculated parity information are compared. Any errors incurred during the transport, be it in the payload signal or in the parity information, will be detected by a difference between the received and the calculated parity information. The nature of the used parity scheme does not allow all possible error patterns to be detected; however, for the purpose of assessing the quality of the transport the detecting capability is adequate. + +For the ODUk, the following OH information is available to assess its performance: + +- BIP-8: This is a one byte Error Detection Code (EDC) signal. Each ODUk BIP-8 is computed over the bits in the OPUk area of ODUk frame $i$ (the block), and inserted in the ODUk Path Monitoring BIP-8 overhead location in the ODUk frame $i + 2$ . +- BDI: This is a single bit Backward Defect Indication (BDI) signal. It conveys in the upstream direction the signal fail status detected in the path termination sink function. +- BEI: This is a four-bit Backward Error Indication (BEI) signal. It conveys in the upstream direction the count of interleaved-bit blocks that have been detected in error by the corresponding ODUk path monitoring sink using the BIP-8 EDC. This count has nine legal values, namely 0-8. + +For the ODUkT and the OTUk, similar OH information is available. + +Further details about these OH signals, like their locations in the OH bytes area are given in ITU-T Rec. G.709/Y.1331. + +In order to improve the error performance of an OTUk signal under given optical transport conditions, ITU-T Rec. G.709/Y.1331 defines Forward Error Correction (FEC) schemes. The use of a FEC is not mandatory; however, when it is used, the FEC decoder provides additional error information in the form of FEC Corrected Errors (FCE). + +## **6.4 In-Service Monitoring and Out-of-Service Measurement** + +The use of the OH as described in 6.3 enables the assessment of the error performance of a transport service without affecting the client signal, i.e., simultaneously with the performance assessment the service may be used for live traffic. This method is called In-Service Monitoring (ISM). It may be clear that this method can be used only if one has access to the error performance information from the equipment providing the transport service. + +If this is not possible, or not preferred, the performance of a transport service may be assessed by using a known test pattern, e.g., a Pseudo-Random Binary Sequence (PRBS) of known properties as the client signal, and performing a bit-by-bit check of this signal at the receiving end. This method is called Out-of-Service Measurement (OSM). + +# **7 Error performance events and parameters** + +## **7.1 Severely Errored Seconds and Background Block Errors** + +If the transport is not error free, this will be detected through the occurrence of a difference between the received and the calculated BIP-8 parity information. In such case, the transport atomic function which is responsible for the comparison will indicate that a block error occurred. While also taking into account the defect status of the signal of interest, these block errors will be processed further in the Equipment Management Function (EMF), leading to the detection of Severely Errored Second (SES) and Background Block Error (BBE) performance events, which are considered to be essential for BIS and maintenance. + +In general, the detection criteria for these events are: + +- a SES occurs when in a second more than 15% of the blocks is errored or a defect is detected; +- a BBE occurs when an errored block is detected in a second which is not a SES. + +The detection criteria are formally defined in clause 7/G.8201. + +ITU-T Recs G.7710/Y.1701 and G.874 provide details on the processing inside the EMF. + +From the events, the following performance parameters are derived: + +- Severely Errored Second Ratio (SESR): The ratio of the number of SESs to the total number of seconds in the observation interval in available time. +- Background Block Error Ratio (BBER): The ratio of the number of BBEs to the total number of blocks in the observation interval in available time. + +The Errored Second (ES) event, and the related parameter Errored Second Ratio (ESR), which are used for PDH and SDH transport error performance characterization, are not considered to be useful for performance assessment in the OTN. Due to the high bit rate transport and the physical properties of the optical transport, almost every second might exhibit at least one error before correction by the FEC. After the correction by FEC, there will be either no ESs, or so many that counting them does not provide information which is useful for BIS or maintenance purposes. + +## 7.2 FEC Corrected Errors + +An OTN system, which uses a Forward Error Correction method to improve the error performance behaviour under given optical transport conditions, may provide an additional parameter: the number of FEC Corrected Errors (FCE) in each second. This parameter is only available for OTUk sections, not for ODUk paths. + +# 8 Availability + +According to 4.5/G.8201, the error performance of a path shall only be evaluated whilst the path is in the available state. The reason is that error performance is a parameter which characterizes the service provided by the path. When the service is not available, this characteristic is irrelevant. + +In line with this general principle, the evaluation of the error performance shall be based on the numbers of events which happened during available time. + +Annex A/G.8201 further stipulates that a bidirectional service between A and B is only available if both of the two constituent unidirectional services (A to B, and B to A) are available. The reason is that a client is not very much interested in the detailed performance of one direction if the other direction is completely broken. + +This Recommendation has a different approach because it is dealing with BIS and maintenance. Maintenance consists of identifying, localizing and correcting failures which affect the performance of a path. In order to be able to carry out these tasks efficiently, the view of an operator working on failures affecting one direction of a bidirectional path should not be obscured by possible unavailability of the other direction. + +For this reason, this Recommendation uses only the criteria for a single direction from ITU-T Rec. G.8201, and not the criterion for a bidirectional path. + +The criteria for a single direction are: "A period of unavailable time begins at the onset of ten consecutive SES events. These ten seconds are considered to be part of unavailable time. A new period of available time begins at the onset of ten consecutive non-SES events. These ten seconds are considered to be part of available time." + +Hence, in order to evaluate the error performance of a transport entity against the objectives put forward in clause 10, each direction shall be evaluated while disregarding the behaviour of the other direction, and the counting of events for a direction shall only be inhibited when that direction is unavailable. + +# 9 Network reference model + +This clause introduces the notion of the ODUk Hypothetical Reference Optical Path (HROP). This is a 27 500 km long path, spanning a total of at most eight operator domains as depicted in Figure 3. + +![Diagram of the hypothetical reference optical path (HROP) showing a 27 500 km long path spanning multiple operator domains.](5dfc130b129ace4df375839020a5700d_img.jpg) + +The diagram illustrates the Hypothetical Reference Optical Path (HROP) as a 27 500 km long sequence of operator domains. It starts at a Path End Point (PEP) on the left and ends at another PEP on the right. The path consists of alternating Local Operator Domains (LOD), Regional Operator Domains (ROD), and Backbone Operator Domains (BOD). Each domain is represented by a cloud-like shape. Between these domains are Operator Gateways (OG) and Inter-Operator Domains (IOD). A bracket above the central part of the path indicates that there are at most four Backbone Operator Domains (BOD) in the entire 27 500 km path. The total length of the path is labeled as 27 500 km. The diagram is labeled M.2401\_F03. + +| | | | | +|-----|--------------------------|-----|--------------------------| +| BOD | Backbone Operator Domain | OG | Operator Gateway | +| IOD | Inter-Operator Domain | PEP | Path End Point | +| LOD | Local Operator Domain | ROD | Regional Operator Domain | + +Diagram of the hypothetical reference optical path (HROP) showing a 27 500 km long path spanning multiple operator domains. + +Figure 3/M.2401 – The hypothetical reference optical path + +From this model, four types of domains can be distinguished: the Local Operator Domain (LOD), the Regional Operator Domain (ROD), the Backbone Operator Domain (BOD), and the Inter-Operator Domain (IOD). The boundary between the domains is called an Operator Gateway (OG). Four BODs and two pairs of LOD-ROD are used for a total of at most eight operator domains. + +# 10 Error performance objectives + +## 10.1 Error performance objectives for the HROP + +The end-to-end performance objectives for the ODUk HROP, and the rules to derive from it the objectives for a real path, are chosen such that a path, brought into service and maintained in accordance with this Recommendation, will meet the long-term performance objectives of ITU-T Rec. G.8201. Table 1 gives end-to-end performance objectives for the ODUk HROP. The SESR and BBER values are 50% of the G.8201 values in order to provide some marging for maintenance purposes. + +**Table 1/M.2401 – Performance objectives for the ODUk HROP** + +| Path type | Bit rate | Number of blocks per second | SESR | BBER | +|-----------|------------|-----------------------------|-----------|-----------------------| +| ODU1 | 2.5 Gbit/s | 20 420 | $10^{-3}$ | $2 \times 10^{-5}$ | +| ODU2 | 10 Gbit/s | 82 025 | $10^{-3}$ | $5 \times 10^{-6}$ | +| ODU3 | 40 Gbit/s | 329 492 | $10^{-3}$ | $1.25 \times 10^{-6}$ | + +## 10.2 Error performance objectives for the domains of a real path + +For the four types of domains, the following block allocations, expressed as a percentage of the performance objective for the HROP, apply: + +- a block allocation of 5% for a BOD; +- a block allocation of 5% for a ROD; +- a block allocation of 7.5% for a LOD; +- a block allocation of 0.1% for an IOD. + +An additional distance-based allocation is also given to each domain, except for the IOD. This distance-based allocation is 0.2% per 100 km based on the real length. If the real length is not known, the product of the air route distance and a routing factor has to be used. + +The routing factor is specified as follows for each operator domain (between OGs): + +- if the air route distance between two OGs is <1000 km, the routing factor is 1.5; +- if the air route distance is $\geq 1000$ km and <1200 km, the calculated route length is taken to be 1500 km; +- if the air route distance between two OGs is $\geq 1200$ km, the routing factor is 1.25. + +The distance-based allocation is added to the block allocation to yield the total allocation for an operator domain, the so-called Path Allocation. + +NOTE – A single operator may span several domains, such as one LOD, one ROD and one BOD. In this case, the allocation to the operator is the sum of the various domain allocations. + +## 10.3 Error performance objectives for the section + +Table 2 gives performance objectives for the OTUk section. + +**Table 2/M.2401 – Performance objectives for the OTUk section** + +| Path type | Bit rate | Number of blocks per second | SESR | BBER | +|--------------------------------|------------|-----------------------------|------|------| +| OTU1 | 2.5 Gbit/s | 20 420 | FFS | FFS | +| OTU2 | 10 Gbit/s | 82 025 | FFS | FFS | +| OTU3 | 40 Gbit/s | 329 492 | FFS | FFS | +| NOTE – FFS: For further study. | | | | | + +Note that the FCE parameter might be useful for maintenance of OTUk sections. However, due to the implementation specific behaviour of this parameter, no objectives or limits are specified. + +# 11 Performance limits – General considerations + +## 11.1 Relationship between performance limits and performance objectives + +The limits in this Recommendation are to be used to indicate the need for actions during bringing-into-service and maintenance. A network maintained to these limits should meet the performance objectives specified in ITU-T Rec. G.8201. + +The particular parameters measured, the measurement duration, and the limits used for the procedures need not be identical to those used in the specification of these performance objectives as long as they result in network performance which meets these objectives. For example, the error performance objectives refer to long periods, such as one month. However, practical considerations demand that maintenance and BIS limits be based on shorter measurement intervals. + +Statistical fluctuations in the occurrence of anomalies and defects mean that one cannot be certain that the long-term objectives are met. The limits on the numbers of events and the duration of measurements attempt to ensure that OTN sections or paths exhibiting unacceptable or degraded performance can be detected. The only way to ensure that an OTN section or path meets network performance objectives is to evaluate continuous measurement over a long period (i.e., months). + +## 11.2 Types of limits + +Limits are needed for several maintenance functions as defined in ITU-T Rec. M.20. This Recommendation provides methods for calculation of path limits for three of these functions: + +- bringing-into-service; +- keeping the network operational (maintenance); +- system restoration. + +Limits for commissioning (installation and acceptance) of OTN sections are not provided in ITU-T Recommendations. + +### 11.2.1 BIS tests/limits + +BIS tests are done by measurements using a PRBS between digital terminating points. When a particular path/section is brought into service, the collection of anomalies and defects for the BIS tests shall be done at the actual termination points of this path/section. See ITU-T Rec. M.2110 for further information. + +Tests results should be compared to the BIS limits, calculated according to the method given in this Recommendation. + +### 11.2.2 Maintenance limits + +Once entities have been placed into service, supervision of the network requires additional limits, as described in ITU-T Rec. M.20. This supervision is done by in-service performance monitoring. The supervision process involves analysing anomalies and defects detected by maintenance entities to determine if the performance level is normal, degraded, or unacceptable. Thus, degraded and unacceptable performance limits are required. + +### 11.2.3 System restoration limit + +The limits used after intervention (repair) are equal to the BIS limits. + +# 12 Bringing-into-service procedures and limits + +The BIS testing procedures, including how to deal with any period of unavailability during the tests, are defined in ITU-T Rec. M.2110. These procedures use limits, called $S_{15}$ , $S_2$ , and $S_{24}$ , according to the duration of the tests (15 minutes, 2 hours, or 24 hours). + +These limits are derived from the PO given in Table 1 by means of calculating the Allocated Performance Objective (APO), taking into account the measurement period and the allocation according to 10.2. The Bringing-Into-Service Performance Objective (BISPO) is derived from the APO. This BISPO is chosen to be a factor $2^1$ more stringent than the APO. This factor is called the ageing marging. Subsequently, the BISPO is used to calculate the limits. + +## 12.1 Calculation of the BIS limits + +This clause defines the method for the calculation of the BIS limits. + +**Step a:** Identification of the PO: + +- 1) Identify the bit rate of the path. +- 2) Read the PO for BBE and SES for the appropriate bit rate from Table 1, denote these as $PO_{bbe}$ and $PO_{ses}$ (note that these are expressed as ratios). + +**Step b:** Calculation of path allocation: + +- 3) Identify all domains for the entire path; let $N$ be the number of Operator Domains (OD). +- 4) Label the ODs as $OD_1$ to $OD_N$ . +- 5) Identify the length, $d$ , of each $OD_n$ . The length, $d$ , is either the actual path length or, if not known, calculated according to the rules in 10.2. +- 6) Read the allocation, $a_n\%$ , (as a percentage of end-to-end PO) for $OD_n$ from 10.2. Note that these allocations are maximum values; more stringent values can be used by bilateral or multilateral agreement. +- 7) Calculate the allocation for the Inter-Operator Domains: $a_{IOD} = (N - 1) \times 0.1\%$ . +- 8) Calculate $A$ , the path allocation: $A = a_1 + a_2 + \dots + a_n + a_{IOD}$ (note that $A$ is a percentage). + +**Step c:** Calculation of APO: + +- 9) Determine the required Test Period, (TP) where TP is 15 minutes, 2 hours or 24 hours. Express TP in seconds, e.g., TP = 900 seconds for a 15-minute test. +- 10) Calculate the APO count for SES, converting percentage to ratio: +$$APO_{ses} = (A \div 100) \times PO_{ses} \times TP$$ + +--- + +1 This is a preliminary value; it might need revision when more error performance data, related to the operation of OTNs, becomes available. + +- 11) Calculate the APO count for BBE, converting percentage to ratio ( $N_b$ is the number of blocks per second as given in Table 2): + +$$APO_{bbe} = (A \div 100) \times PO_{bbe} \times TP \times N_b$$ + +**Step d:** Calculation of BISPO and S values: + +- 12) Calculate the BISPO counts: + +$$BISPO_{ses} = \frac{APO_{ses}}{2} ; \quad BISPO_{bbe} = \frac{APO_{bbe}}{2}$$ + +- 13) Calculate S values: + +$$D_{ses} = 2\sqrt{BISPO_{ses}}$$ + +$$S_{ses} = BISPO_{ses} - D_{ses}$$ + +$$D_{bbe} = 2\sqrt{BISPO_{bbe}}$$ + +$$S_{bbe} = BISPO_{bbe} - D_{bbe}$$ + +- 14) Round all S values to the nearest integer value $\geq 0$ . + +# 13 Performance levels and limits for maintenance + +Once entities have been placed into service, they will be subject to the supervision processes, as described in ITU-T Rec. M.20. According to this Recommendation, an entity can be in a limited number of predefined conditions depending on its performance. These conditions are called performance levels, and are the Unacceptable Performance Level (UPL), the Degraded Performance Level (DPL) and the Acceptable Performance Level. The boundaries between the performance levels are called performance limits. Refer to ITU-T Rec. M.2120 for further information on the use of these limits. + +## 13.1 Calculation of limits for maintenance + +The maintenance performance limits are a function of the APO and the applicable measurement period and are calculated as follows: + +- UP limit $\geq 10 \times APO$ where TP = 900 seconds; +- DP limit $= 0.75 \times APO$ where TP = 86 400 seconds. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/M/T-REC-M.3000-200002-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..436e84b6b2242295d6df4cc26fcfbfc7fd06b03a --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17b8c98a11d56d0b2a6b845b2b2751eeb1e318c67201ca490a30720c5a5dbdf +size 54852 diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3000-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b18e5b07ba6a266813c0ce76e92f4e93c0d9fd4b --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a97195c2fd68ad39d82d19b808d1738dce3aa52e94325870a031b5a2ea7c01 +size 8275 diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/M/T-REC-M.3000-200002-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efb2b625c134ffcf9e7d563f41996d022eed075e --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb3f393ed709faa7aaec16bcf4339931a083c5d2b42a9c5f6235d525c3b59a50 +size 210793 diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.3000-200002-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e5e237ba1fc3e9d6248a28d3dd433372961e2e6 --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fe352a646f45af589701480b90e42c6a259c0c894f09e68168d7d30ebc411f0 +size 60366 diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3000-200002-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91bb974e6760f35aaf2668679d98e36b0db0b329 --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbd49d84919c16bdd2c035debeb8a9777b8469a81aabf9afbc68e36c1a5b53ee +size 41835 diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/M/T-REC-M.3000-200002-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1befe38d4dcdca915c19da8d48dff9d9b5e26679 --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9f0180cde42a7ad49d6f65499bc9f6f54b8b8bbea018e647d47e61bf2b4d029 +size 49239 diff --git a/marked/M/T-REC-M.3000-200002-I_PDF-E/raw.md b/marked/M/T-REC-M.3000-200002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e0f2bb24bd3a1bb67a0c8819bf837a7819fbdd65 --- /dev/null +++ b/marked/M/T-REC-M.3000-200002-I_PDF-E/raw.md @@ -0,0 +1,1261 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3000** + +(02/2000) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +# --- **Overview of TMN Recommendations** + +ITU-T Recommendation M.3000 + +(Formerly CCITT Recommendation) + +--- + +## ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **OVERVIEW OF TMN RECOMMENDATIONS** + +## **Summary** + +This overview of TMN Recommendations describes the aim, subject areas and the range of TMN-related Recommendations developed or to be developed within the ITU-T. Annexes A and B contain the current lists of TMN-related Recommendations. + +## **Source** + +ITU-T Recommendation M.3000 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 4 February 2000. + +## **Keywords** + +List of TMN Recommendations, overview of TMN Recommendations, subject areas of TMN Recommendations, Telecommunications Management Network (TMN), TMN-referenced Recommendations. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|--------|----------------------------------------------------------|---| +| 1 | Scope..... | 1 | +| 2 | Fields of application..... | 1 | +| 3 | Abbreviations..... | 1 | +| 4 | Definitions ..... | 3 | +| 5 | Subject areas of TMN Recommendations ..... | 3 | +| 5.1 | Evolution of TMN ..... | 3 | +| 5.2 | TMN subject areas ..... | 4 | +| 5.2.1 | Architecture ..... | 4 | +| 5.2.2 | Interface specification methodology..... | 6 | +| 5.2.3 | TMN management services ..... | 6 | +| 5.2.4 | TMN management functions ..... | 6 | +| 5.2.5 | Management information models and catalogue ..... | 6 | +| 5.2.6 | Management information registration ..... | 6 | +| 5.2.7 | Communication protocols..... | 6 | +| 5.2.8 | Systems management services and management messages..... | 7 | +| 5.2.9 | Conformance ..... | 7 | +| 5.2.10 | International standardized profiles ..... | 7 | +| 5.2.11 | Terminology ..... | 7 | +| 5.2.12 | Security ..... | 7 | +| 5.3 | Referenced areas ..... | 7 | +| 5.3.1 | Telecommunication services ..... | 7 | +| 5.3.2 | Telecommunication network architecture ..... | 7 | +| 5.3.3 | Telecommunication network management for traffic ..... | 7 | +| 5.3.4 | Telecommunication network maintenance ..... | 7 | +| 5.3.5 | Telecommunication network security..... | 8 | +| 5.3.6 | Telecommunication network components ..... | 8 | +| 5.3.7 | Telecommunication network provisioning ..... | 8 | +| 5.3.8 | Communication protocols..... | 8 | +| 5.3.9 | OSI systems management services ..... | 8 | +| 5.3.10 | OSI layer management functions..... | 8 | +| 5.3.11 | ISP and implementation requirements..... | 8 | +| 5.3.12 | Managed object naming and addressing ..... | 8 | +| 6 | Range of Recommendations ..... | 8 | +| 6.1 | TMN Recommendations ..... | 8 | +| 6.2 | TMN-referenced Recommendations..... | 9 | + +| | Page | +|----------------------------------------------------|-------------| +| Annex A – List of TMN Recommendations..... | 10 | +| Annex B – List of TMN-related Recommendations..... | 22 | + +# **Introduction** + +The study of TMN requires various expertise and TMN-related Recommendations are being developed in various Study Groups within ITU-T. This Recommendation has been developed to present a stable framework in the form of an umbrella Recommendation as a guide to all relevant development activities. + + + +# **OVERVIEW OF TMN RECOMMENDATIONS** + +# **1 Scope** + +The purpose of this Recommendation is to serve as an umbrella Recommendation for the development and use of TMN Recommendations within ITU-T. TMN Recommendations describe principles, architecture, definitions and specifications necessary to implement all types of TMNs. + +The contents of this Recommendation are the fields of application of TMN, areas to be studied (subject areas) in TMN Recommendations and areas of Recommendations that are referenced by TMN Recommendations (TMN-referenced Recommendations). + +Annexes A and B list the current TMN-related Recommendations. + +The users of this Recommendation are expected to be the experts who develop individual TMN-related Recommendations, those who utilize TMNs to manage telecommunication networks, and vendors and suppliers who implement TMNs. + +# **2 Fields of application** + +TMNs provide the means used to transport, store and process information used to support the management of telecommunication networks and services. + +TMNs can be used for the management of telecommunication networks operated by Administrations, ROAs, customers, or other organizations and individuals. When these telecommunication networks are connected with each other, their TMNs provide the means of exchanging information required to manage end-to-end telecommunication services. + +All types of telecommunication networks and network elements – such as analogue networks, digital networks, public networks, private networks, switching systems, transmission systems, telecommunication software, and logical resources of the network (such as a circuit, path, or telecommunication services supported by these resources) are candidates for management by a TMN. + +There is in principle no limit to the fields of application. Since TMN Recommendations are still being developed, however, there is currently a practical limit to the variety of application fields that can be implemented. + +# **3 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|--------|-----------------------------------------------| +| ACSE | Association Control Service Element | +| AN | Access Network | +| AOM | Application OSI Management (profile) | +| ASN.1 | Abstract Syntax Notation One | +| ATM | Asynchronous Transfer Mode | +| B-ISDN | Broadband Integrated Services Digital Network | +| CMIP | Common Management Information Protocol | + +| | | +|--------|--------------------------------------------------------| +| CMISE | Common Management Information Service Element | +| CNM | Customer Network Management | +| CORBA | Common Object Request Broker Architecture | +| DCN | Data Communication Network | +| EDI | Electronic Data Interchange | +| ET | Exchange Termination | +| FTAM | File Transfer, Access and Management | +| GIOP | General Inter-ORB Protocol | +| ICS | Implementation Conformance Statement | +| IIOP | Internet Inter-ORB Protocol | +| IN | Intelligent Network | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| ISO | International Organization for Standardization | +| ISP | International Standardized Profile | +| LE | Local Exchange | +| MCS | Management Conformance Statement | +| MOCS | Managed Object Conformance Statement | +| MRCS | Management Relationship Conformance Statement | +| MS | Management Service | +| NE | Network Element | +| NSAP | Network Service Access Point | +| OAM&P | Operations, Administration, Maintenance & Provisioning | +| ODMA | Open Distributed Management Architecture | +| OS | Operations System | +| OSI | Open Systems Interconnection | +| PDU | Protocol Data Unit | +| PICS | Protocol Implementation Conformance Statement | +| RM-ODP | Reference Model for Open Distributed Processing | +| ROA | Recognized Operating Agency | +| ROSE | Remote Operation Service Element | +| SDH | Synchronous Digital Hierarchy | +| SG/WP | Study Group/Working Party | +| SN | Service Node | +| STASE | Security Transformations Application Service Element | +| TCP/IP | Transmission Control Protocol/Internet Protocol | +| TIB | Task Information Base | + +| | | +|-----|---------------------------------------| +| TMN | Telecommunications Management Network | +| UML | Unified Modelling Language | + +# 4 Definitions + +TMN-specific technical terms are defined in each TMN Recommendation as well as clause 2/M.60 or in Recommendations dedicated to specific areas of technology. + +# 5 Subject areas of TMN Recommendations + +## 5.1 Evolution of TMN + +The study of TMN within ITU-T originated in the definition of interfaces and the specification of interface protocols between OSs and transmission terminals. The concept of TMN was soon established to include the development of Recommendations for the information network operating in support of the management of all telecommunication networks and services. + +TMN Recommendations are thus expected to be developed over a long period, to suit the growing demands resulting from continuously evolving telecommunication networks and services. + +To avoid inconsistency and duplication in different telecommunication domains, TMN Recommendations are developed in a planned order and with an organized structure. The subject areas of TMN Recommendations are introduced to help understand the purpose of individual Recommendations and to make the assessment of Recommendations easier from the viewpoint of avoiding inconsistencies and duplications. + +*Identified TMN subject areas are:* + +- Architecture; +- Interface specification methodology; +- Management services; +- Management functions (protocol independent); +- Management information models and catalogue; +- Management information registration; +- Communication protocols; +- Systems management services and management messages (protocol specific); +- Conformance requirements; +- International standard profiles; +- Terminology; +- Security. + +To derive TMN requirements or introduce specifications as a tool to develop a TMN, TMN Recommendations reference other Recommendations and/or Standards. The areas of TMN-referenced Recommendations/Standards are: + +*Referenced areas:* + +- Telecommunication services; +- Telecommunication network architecture; +- Telecommunication network management for traffic; +- Telecommunication network maintenance; + +- Telecommunication network security; +- Telecommunication network components; +- Telecommunication network provisioning; +- Communication protocols; +- OSI systems management services; +- OSI layer management functions; +- ISPs or implementation requirements; +- Managed object naming and addressing. + +The relationships between TMN subject areas as well as TMN and referenced areas are shown in Figure 1. + +When an individual TMN Recommendation is developed, the subject area(s) to which it contributes is/are identified, and to avoid overlap the contents of the Recommendation are compared with those of other Recommendations concerned with the same area(s). Depending on the users' convenience, the documentation of TMN Recommendations may or may not follow the classification of subject areas. + +## **5.2 TMN subject areas** + +TMN subject areas are explained in this clause as a guide for the further development of TMN Recommendations. + +### **5.2.1 Architecture** + +The TMN architecture is described in Recommendation M.3010, "Principles for a Telecommunications Management Network". Three basic aspects are included in the TMN architecture. + +These are: + +- the TMN functional architecture; +- the TMN information architecture; and +- the TMN physical architecture. + +![Diagram a) Subject areas of TMN Recommendations. It shows a flow from 'Management services and functions' at the top, branching down to 'Management information models and catalogues' (Definition, Registration, Library) and 'Communication services, messages and ISPs'. Both of these lead to 'Conformance requirements' at the bottom.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Architecture, methodology, security and terminology + +``` + +graph TD + A[Management services and functions] --> B["Management information models and catalogues +- Definition +- Registration +- Library"] + A --> C["Communication services, messages and ISPs"] + B --> D[Conformance requirements] + C --> D + +``` + +Diagram a) Subject areas of TMN Recommendations. It shows a flow from 'Management services and functions' at the top, branching down to 'Management information models and catalogues' (Definition, Registration, Library) and 'Communication services, messages and ISPs'. Both of these lead to 'Conformance requirements' at the bottom. + +**a) Subject areas of TMN Recommendations** + +![Diagram b) Areas of TMN-referenced Recommendations. It shows 'Telecommunication services' at the top, with arrows pointing down to four boxes: 'Telecommunication network architecture and components', 'Telecommunication network management for traffic, maintenance, provisioning and security', 'Communication protocols, services and messages. OSI, ISDN, CORBA, etc.', and 'ISPs, managed object naming and addressing'. All four boxes point to a central 'TMN' box at the bottom. The code 'T0412970-99' is in the bottom right.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +``` + +graph TD + TS[Telecommunication services] --> TNA[Telecommunication network architecture and components] + TS --> TNM["Telecommunication network management for traffic, maintenance, provisioning and security"] + TS --> CPS["Communication protocols, services and messages. +OSI, ISDN, CORBA, etc."] + TS --> IMOA["ISPs, managed object naming and addressing"] + TNA --> TMN[TMN] + TNM --> TMN + CPS --> TMN + IMOA --> TMN + +``` + +T0412970-99 + +Diagram b) Areas of TMN-referenced Recommendations. It shows 'Telecommunication services' at the top, with arrows pointing down to four boxes: 'Telecommunication network architecture and components', 'Telecommunication network management for traffic, maintenance, provisioning and security', 'Communication protocols, services and messages. OSI, ISDN, CORBA, etc.', and 'ISPs, managed object naming and addressing'. All four boxes point to a central 'TMN' box at the bottom. The code 'T0412970-99' is in the bottom right. + +**b) Areas of TMN-referenced Recommendations** + +**Figure 1/M.3000** + +The TMN functional architecture describes the appropriate distribution of functionality within the TMN, appropriate in the sense of allowing for the creation of function blocks from which a TMN of any complexity can be implemented. The definition of function blocks and reference points between them leads to the requirements for the TMN-recommended interface specifications. + +The TMN information architecture is based on standardized open management paradigms that support the standardized modelling of the information to be communicated. TMN standardization activities will not develop a specific management paradigm but build upon industry recognized solutions, focusing primarily on object-oriented techniques. Specific management paradigms may be used in TMN standards when judged to be adequate. + +The TMN physical architecture describes interfaces that can actually be implemented and examples of physical components that make up the TMN. + +### **5.2.2 Interface specification methodology** + +This methodology is described in Recommendation M.3020 and shows the precise steps in determining the individual items needed for the complete specification of TMN interfaces. Definitions and specifications made at each step are important in maximizing the multiple use of the individual items of Recommendations. The TMN methodology shall therefore be followed when ITU-T Study Groups develop TMN Recommendations. + +### **5.2.3 TMN management services** + +Described from the user's viewpoint of Operation, Administration, Maintenance and Provisioning (OAM&P) requirements, the TMN management service addresses an area of management activity that provides for the support of an aspect of OAM&P of a telecommunication network. + +The management services are used as a mechanism to capture the management requirements and document them in a uniform way. The management services are the subject of Recommendations M.32xx. + +### **5.2.4 TMN management functions** + +TMN management functions are used by the TMN management service to implement their functionality when communicating with other functional entities across the TMN interfaces. TMN management functions that logically belong together are grouped to increase their usability. + +TMN management functions are the collection of the functional requirements for the TMN interface specifications. These functions are also described from the user's perspective and are protocol independent. The management functions are the subject of Recommendation M.3400. + +### **5.2.5 Management information models and catalogue** + +TMN information models that are abstractions of managed telecommunication resources include: + +- a) generic network information model; +- b) technology-specific models, e.g. for SDH. + +Support information models are defined as abstractions of processes by which specific functional aspects of management are achieved. Examples of the latter are included in the Q.820-series Recommendations. + +Management is carried out across the TMN standards interfaces using standard communication protocols and management-aspect protocols, the latter transporting management information defined in TMN management information models. + +### **5.2.6 Management information registration** + +The assignment of object identifiers for TMN management information is structured in a fashion similar to the assignment of identifiers to OSI systems management information and is described in Recommendation X.722. Properly defined management information is given a globally unique object identifier and, with the approval of the defining Recommendation, is registered automatically. + +The development of a computerized database library of TMN management information is under study within the ITU-T. + +### **5.2.7 Communication protocols** + +Communication and management-aspect protocols in ITU-T Recommendations and ISO Standards are selected for the transfer of management information across TMN interfaces. Communication transport protocols include OSI, ISDN, Signalling System No.7, and TCP/IP. Management-specific protocols include OSI's CMIP, FTAM, X.500, EDI and CORBA's GIOP transported over IP (IIOP). Selected protocols are organized into protocol suites or profiles for specific TMN interfaces. The transfer syntax employed is described in the binary encoding rules (see Recommendation X.690). + +### **5.2.8 Systems management services and management messages** + +TMN utilizes the OSI systems management services defined in the X.730-series Recommendations and also provides additional management application functionality by means of TMN management messages in Q.820-series Recommendations. This management functionality is made available for use across TMN interfaces by including it in a TMN-defined systems management application service element. + +### **5.2.9 Conformance** + +TMN conformance requirements are a set of statements for protocols and information models to which TMN implementations must conform. These conformance statements are the basis upon which conformance testing tools for TMN are developed and then applied to products claiming conformance to TMN Recommendations. + +### **5.2.10 International standardized profiles** + +The need for TMN ISPs has been recognized and will be addressed in the future. + +### **5.2.11 Terminology** + +Most of the TMN specific terms are defined and described in clause 2/M.60 and 3/M.3010 which is dedicated to the terminology used in the management of telecommunication network. + +### **5.2.12 Security** + +For a practical TMN implementation, security requirements associated with the TMN management services should be precisely defined, thus general aspects and guidelines on TMN security services are provided within the scope of TMN Recommendations. + +## **5.3 Referenced areas** + +The areas of TMN-referenced Recommendations are explained here as a guide to selecting the Recommendations to be referenced. + +### **5.3.1 Telecommunication services** + +Telecommunication services are defined in ITU-T Recommendations and TMN Recommendations will reference those Recommendations as basis for developing TMN Recommendations that deal with management of telecommunication services. + +### **5.3.2 Telecommunication network architecture** + +Telecommunication network architecture gives the fundamental structure of a telecommunication network. A typical example is the SDH network architecture described in Recommendation G.803. The telecommunication network architecture may mainly be referenced by Recommendations covering the area of network management information modelling in order to give the fundamental idea of the abstraction of the telecommunication network. + +### **5.3.3 Telecommunication network management for traffic** + +Traffic management of telecommunication network is one of the important application areas of TMN, and Recommendations dealing with traffic management will be referenced by TMN requirements Recommendations. + +### **5.3.4 Telecommunication network maintenance** + +Maintenance is one of the main categories of TMN management services, and Recommendations concerning this subject will be referenced while developing TMN management requirements Recommendations. + +### **5.3.5 Telecommunication network security** + +There are two aspects for security, i.e. security of management and management of security. Recommendations concerning network security will be taken into account when TMN security is studied. Those Recommendations will also be referenced when TMN requirements Recommendations are developed for management of telecommunication network security. + +### **5.3.6 Telecommunication network components** + +Telecommunication network components Recommendations, such as transmission systems and switching systems, describe the functions of components that provide a basis for developing network or components management information models. + +### **5.3.7 Telecommunication network provisioning** + +Recommendations concerning telecommunication network provisioning describe the mechanisms to provide telecommunication network services to the customer. TMN Recommendations will reference Recommendations of this area when developing TMN management requirements Recommendations. + +### **5.3.8 Communication protocols** + +TMN interface protocols are selected from communication protocol Recommendations such as those described in 5.2.7. + +### **5.3.9 OSI systems management services** + +OSI systems management services defined in the X.730/X.740-series Recommendations are referenced by TMN Recommendations (see 5.2.8). + +### **5.3.10 OSI layer management functions** + +Functions related to the management of the OSI layers such as activation and error control are described in the X.28x-series Recommendations. + +### **5.3.11 ISP and implementation requirements** + +A profile specifies a set of protocols, including available PICS, or managed objects, including available MOCS, combined to provide a specific functionality while minimizing optionality. Internationally recognized profiles are organized into ISPs which may add additional conformance statements. ISPs form the basis for the preparation of conformance testing. + +### **5.3.12 Managed object naming and addressing** + +To define the TMN managed object, TMN management information Recommendations will reference Recommendations concerning managed object naming and addressing. + +# **6 Range of Recommendations** + +TMN-related Recommendations are being developed within ITU-T. Some examples were mapped on the TMN subject areas as shown in Figure 2. + +## **6.1 TMN Recommendations** + +Recommendations that cover subject area(s) described in 5.2 are classified into the category of TMN Recommendations, which are listed in Annex A. + +![Flowchart showing the mapping of TMN Recommendations. At the top is a box for 'Architecture M.3010, M.3013; Methodology M.3020; Security M.3016; Terminology M.60'. Below it is 'Management services and functions M.3200-series, M.3300, M.3320, M.3400'. Arrows point down to two boxes: 'Management information models and catalogues M.3100, M.3101, M.3108.x, M.3180, G.774, G.85x-series, I.751' and 'Communication services, messages and ISPs Q.81x-series, Q.82x-series, G.773, Q.94x-series'. Both point down to a final box 'Conformance requirements'.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Architecture, methodology, security and terminology + +``` + +graph TD + A["Architecture M.3010, M.3013; Methodology M.3020; +Security M.3016; Terminology M.60"] --> B["Management services and functions +M.3200-series, M.3300, M.3320, M.3400"] + B --> C["Management information models and catalogues +M.3100, M.3101, M.3108.x, +M.3180, G.774, G.85x-series, +I.751"] + B --> D["Communication services, messages and ISPs +Q.81x-series, Q.82x-series, +G.773, Q.94x-series"] + C --> E["Conformance requirements"] + D --> E + +``` + +Flowchart showing the mapping of TMN Recommendations. At the top is a box for 'Architecture M.3010, M.3013; Methodology M.3020; Security M.3016; Terminology M.60'. Below it is 'Management services and functions M.3200-series, M.3300, M.3320, M.3400'. Arrows point down to two boxes: 'Management information models and catalogues M.3100, M.3101, M.3108.x, M.3180, G.774, G.85x-series, I.751' and 'Communication services, messages and ISPs Q.81x-series, Q.82x-series, G.773, Q.94x-series'. Both point down to a final box 'Conformance requirements'. + +a) Mapping of TMN Recommendations + +![Flowchart showing the mapping of TMN-referenced Recommendations. At the top is 'Telecommunication services F-series Recs.'. Below it are four boxes: 'Telecommunication network architecture and components. I/Q/G-series Recs.', 'Communication protocols, services and messages. I/Q/X-series Recs.', 'Telecommunication network management for traffic, maintenance provisioning and security. E/M-series Recs.', and 'ISPs, managed object naming and addressing. X-series Recs.'. Arrows from these four boxes point to a central box labeled 'TMN'. A reference code 'T0412980-99' is at the bottom right.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +``` + +graph TD + A["Telecommunication services F-series Recs."] --> TMN["TMN"] + B["Telecommunication network architecture and components. +I/Q/G-series Recs."] --> TMN + C["Communication protocols, services and messages. +I/Q/X-series Recs."] --> TMN + D["Telecommunication network management for traffic, maintenance provisioning and security. +E/M-series Recs."] --> TMN + E["ISPs, managed object naming and addressing. +X-series Recs."] --> TMN + +``` + +T0412980-99 + +Flowchart showing the mapping of TMN-referenced Recommendations. At the top is 'Telecommunication services F-series Recs.'. Below it are four boxes: 'Telecommunication network architecture and components. I/Q/G-series Recs.', 'Communication protocols, services and messages. I/Q/X-series Recs.', 'Telecommunication network management for traffic, maintenance provisioning and security. E/M-series Recs.', and 'ISPs, managed object naming and addressing. X-series Recs.'. Arrows from these four boxes point to a central box labeled 'TMN'. A reference code 'T0412980-99' is at the bottom right. + +b) Mapping of TMN-referenced Recommendations + +**Figure 2/M.3000** + +## 6.2 TMN-referenced Recommendations + +Recommendations that are referenced by TMN Recommendations are classified as TMN-referenced Recommendations. + +Typical TMN-referenced Recommendations are those of communication protocols used in the TMN protocol suites. Some Recommendations concerning telecommunication network architecture, telecommunication network management, telecommunication network maintenance, etc., may be referenced implicitly. Some main Recommendations referenced explicitly will be listed in Annex B. + +Annexes A and B contain the lists of some main TMN-related Recommendations developed within ITU-T. Recommendations are interdependent. Figure A.1 shows some examples of the dependencies among TMN-related Recommendations. These relations need to be taken into account when developing Recommendations. + +# ANNEX A + +## List of TMN Recommendations + +TMN Recommendations developed within ITU-T are listed here. + +The TMN subject areas are denoted as follows: + +- SA-1 Architecture +- SA-2 Interface specification methodology +- SA-3 Management services +- SA-4 Management functions +- SA-5 Management information models and catalogue +- SA-6 Management information registration +- SA-7 Communication protocols +- SA-8 Systems management services and management messages +- SA-9 International standardized profiles +- SA-10 Conformance +- SA-11 Terminology +- SA-12 Security + +Some Recommendations provide contributions to more than one area. For these, all significant areas of contribution are shown in order of that contribution. + +### **M-series** + +REC/STD: M.3000 + +TITLE: Overview of TMN Recommendations (present Recommendation) + +REC/STD: M.3010 + +TITLE: Principles for a TMN + +ABSTRACT: The TMN supports management activities associated with telecommunication networks. This Recommendation introduces the TMN concept, defines its scope, describes the functional and information architecture, and gives examples of physical architecture. It also provides a functional reference model and identifies concepts necessary for supporting the TMN architecture. + +KEYWORDS: TMN/Architecture/Reference Model/Telecommunications Management Network/Interfaces/ Principles. + +QUESTION: 13/4 + +SUBJECT AREA(S): SA-1 + +AVAILABILITY: Available + +REC/STD: M.3013 + +TITLE: Considerations for a telecommunications management network + +ABSTRACT: The Telecommunications Management Network (TMN) supports management activities associated with telecommunication networks. This Recommendation introduces the + +essential considerations needed to support the installation and operation of a TMN based on the TMN principles, concepts and architecture described in Recommendation M.3010. + +**KEYWORDS:** TMN/Architecture/Telecommunications Management Network. + +**QUESTION:** 13/4 + +**SUBJECT AREA(S):** SA-1 + +**AVAILABILITY:** Available + +**REC/STD:** M.3016 + +**TITLE:** TMN security overview + +**ABSTRACT:** This Recommendation provides an overview and framework that identifies security threats to a TMN and outlines how available security services can be applied within the context of the TMN functional architecture, as described in Recommendation M.3010. This Recommendation is generic in nature and does not identify or address the requirements for a specific TMN interface. This Recommendation does not seek to define new security services but uses existing security services defined in other ITU-T Recommendations and ISO Standards. It is envisaged that this Recommendation, along with Recommendation M.3400, will provide a basis for future standardization of TMN security services in the ITU-T. + +**QUESTION:** 13/4 + +**SUBJECT AREA(S):** SA-12 + +**AVAILABILITY:** Available + +**REC/STD:** M.3020 + +**TITLE:** TMN interface specification methodology + +**ABSTRACT:** This Recommendation provides a methodology for describing functional specifications and protocol specifications for TMN interfaces. Emphasis is placed on multiple applications of the methodology and on building specifications by reusing previous results. + +**KEYWORDS:** User requirements/Management Services/Management Functions/Information Model/Managed Objects/Messages/Protocols/Tasks/Task Information Base. + +**QUESTION:** 12/4 + +**SUBJECT AREA(S):** SA-2 + +**AVAILABILITY:** Available + +**REC/STD:** M.3100 + +**TITLE:** Generic network information model + +**ABSTRACT:** This Recommendation provides a generic information model. The model describes managed object classes and their properties that are generic and useful in describing information exchanged across all interfaces defined in M.3010 TMN architecture. These generic managed object classes are intended to be applicable across different technologies, architectures and services. The managed object classes in this Recommendation may be specialized to support the management of various telecommunications networks. + +**KEYWORDS:** Generic Network Information Model/Managed Object Class/Attributes/Notifications/Actions. + +**QUESTION:** 15/4 + +SUBJECT AREA(S): SA-5 + +AVAILABILITY: Available + +REC/STD: M.3101 + +TITLE: Managed object conformance statements for the generic network information model + +ABSTRACT: This Recommendation provides implementation conformance statement proformas for management information defined in ITU-T Recommendation M.3100. + +KEYWORDS: Conformance/MRCS/MOCS/MCS. + +QUESTION: 15/4 + +SUBJECT AREA(S): SA-10, SA-5 + +AVAILABILITY: Available + +REC/STD: M.3108.x + +TITLE: TMN management services for dedicated and reconfigurable circuits network: Information model + +ABSTRACT: This series of Recommendations provides a GDMO-based information model to cope with the management services defined in the series of Recommendations M.3208.x. This Recommendation provides Managed Objects and a Unified Modelling Language (UML) view of the GDMO-based information model. + +KEYWORDS: GDMO. + +QUESTION: 15/4 + +SUBJECT AREA(S): SA-10, SA-5 + +AVAILABILITY: Available + +REC/STD: M.3180 + +TITLE: Catalogue of TMN management information + +ABSTRACT: This Recommendation defines the scope of TMN management information, identifies specification techniques, describes the relationships between ITU-T documents defining management information and references definitions of currently available management information. + +KEYWORDS: Catalogue/managed object/resources/models/fragments/OSI Systems Management. + +QUESTION: 14/4 + +SUBJECT AREA(S): SA-5 + +AVAILABILITY: Available + +REC/STD: M.3200 + +TITLE: TMN management services and telecommunications managed areas: Overview + +ABSTRACT: This Recommendation contains information resulting from task information bases (TIBs) A and B of the ITU-T Recommendation M.3020. The information will be used by the object modelling teams to provide a basis to the ITU-T Recommendation M.3100 and specific network models. It therefore provides a link between the TMN Methodology and TMN Management Information Models. This information may also provide a basis on which an Administration compiles its own telecommunications management services. + +**KEYWORDS:** Telecommunications Management Network/Management Service/Object Modelling/Task Information Base/Mediation Device. + +**QUESTION:** 15/4 + +**SUBJECT AREA(S):** SA-3 + +**AVAILABILITY:** Available + +**REC/STD:** M.3207.x + +**TITLE:** TMN management service: Maintenance aspects of B-ISDN management + +**ABSTRACT:** This series of Recommendations describes the TMN management service for the maintenance aspect of B-ISDN management with using GDMS (Guideline for the Definition of TMN Management Service). + +**KEYWORDS:** Telecommunications Management Network/TMN Management Service. + +**QUESTION:** 15/4 + +**SUBJECT AREA(S):** SA-3 + +**AVAILABILITY:** Available + +**REC/STD:** M.3208.x + +**TITLE:** TMN management services for dedicated and reconfigurable circuits network + +**ABSTRACT:** This Recommendation is one of the M.3200-series TMN management service Recommendations that provide descriptions of management services, goals and context for the Dedicated and Reconfigurable Circuits Network. + +**KEYWORDS:** Dedicated and Reconfigurable Circuits Network/Leased Circuits/Leased Circuit Services/Telecommunications Management Network (TMN)/TMN Management Service. + +**QUESTION:** 15/4 + +**SUBJECT AREA(S):** SA-3 + +**AVAILABILITY:** Available + +**REC/STD:** M.3211.x + +**TITLE:** TMN management service: Fault and performance management of the ISDN access + +**ABSTRACT:** This series of Recommendations describes the TMN management service for the maintenance of ISDN access. These management services provide both the generic and specialized functionalities needed for the fault and performance management of the ISDN access. + +**KEYWORDS:** Exchange Termination (ET)/ISDN access/Management Service (MS)/Telecommunications Management Network (TMN). + +**QUESTION:** 15/4 + +**SUBJECT AREA(S):** SA-3 + +**AVAILABILITY:** Available + +REC/STD: M.3300 + +TITLE: TMN F interface requirements + +ABSTRACT: This Recommendation provides an overview of the TMN management capabilities presented for human information or intervention or both. This Recommendation describes the human-machine supporting functions in the five OSI functional areas and the management capabilities from the perspective of TMN application services. + +KEYWORDS: TMN/Management Capabilities/Human-machine interaction/Interface. + +QUESTION: 16/4 + +SUBJECT AREA(S): SA-3 + +AVAILABILITY: Available + +REC/STD: M.3320 + +TITLE: Management requirements framework for the TMN X-interface + +ABSTRACT: This Recommendation is part of a series dealing with the transfer of information for the management of telecommunication networks and services. The purpose of this Recommendation is to define a requirements framework for all functional, service and network-level requirements for the TMN exchange of information between Administrations. This Recommendation also provides for the general framework of using the TMN X-Interface for the exchange of information between Administrations, Recognized Operating Agencies, other Network Operators, Service Providers, Customers and other entities. + +KEYWORDS: International Aspects/Management Information Exchange/Security consideration/TMN X-interface. + +QUESTION: 17/4 + +SUBJECT AREA(S): SA-3 + +AVAILABILITY: Available + +REC/STD: M.3400 + +TITLE: TMN management functions + +ABSTRACT: A TMN management function is the smallest part of the TMN management service as perceived by the user of the service. In reality it will generally consist of a sequence of actions on a defined managed object or objects. The TMN Management Functions specified in this Recommendation provide the generic and specialized functionalities needed for all telecommunications activities (identified at this time) such as circuit testing, alarm surveillance, traffic management, etc. + +KEYWORDS: TMN Management Function/OSI Systems Management Function. + +QUESTION: 2/4 + +SUBJECT AREA(S): SA-4, SA-5 + +AVAILABILITY: Available + +REC/STD: M.36xx + +TITLE: Management of ISDNs + +ABSTRACT: This series of Recommendations covers ISDNs (ISDN and B-ISDN) management and the relationship with TMN as follows: + +- M.3600: Principle for the management of ISDNs. +- M.3602: Application of maintenance principles to ISDN subscriber installations. +- M.3603: Application of maintenance principles to ISDN basic rate access. +- M.3604: Application of maintenance principles to ISDN primary rate access. +- M.3605: Application of maintenance principles to static multiplexed ISDN basic rate access. +- M.3610: Principles for applying the TMN concept to the management of B-ISDN. +- M.3611: Test management of the B-ISDN ATM layer using the TMN. +- M.3620: Principles for the use of ISDN test calls, systems and responders. +- M.3621: Integrated management of the ISDN customer access. +- M.3640: Management of the D-channel – Data link layer and network layer. +- M.3641: Management information model for the management of the data link and network layer of the ISDN D-channel. +- M.3650: Network performance measurements of ISDN calls. +- M.3660: ISDN interface management services. + +KEYWORDS: ISDN management architecture/ISDN management principles/ISDN management/management service provider/OAM-centre/subscriber access/subscriber installation. + +QUESTION: 20/4 + +SUBJECT AREA(S): SA-4, SA-5 + +AVAILABILITY: Available + +### **G-series** + +REC/STD: G.773 + +TITLE: Protocol suites for Q-interfaces for management of transmission systems + +ABSTRACT: This Recommendation defines the characteristics of protocol suites for Q-interfaces, used to connect transmission systems/equipment, defined in Recommendation M.3010. Protocol suites for the Q-interfaces of other systems/equipment will be specified in other Recommendations. The interfaces will support bidirectional data transfer for the management of telecommunications systems. + +This Recommendation defines: + +- the layer services; +- the layer protocols; +- the application service elements and protocols; +- the conformance requirements to be met by an implementation of these interfaces. + +KEYWORDS: Not provided. + +QUESTION: 13/15 + +SUBJECT AREA(S): SA-7 + +AVAILABILITY: Available + +REC/STD: G.774.1 + +TITLE: Synchronous Digital Hierarchy (SDH) performance monitoring for the network element view + +ABSTRACT: This Recommendation provides an information model for the Synchronous Digital Hierarchy (SDH). This model describes the managed object classes and their properties that are useful to describe information exchanged across the interfaces defined in the TMN architecture in Recommendation M.3010. This Recommendation specializes the generic object classes of Recommendation M.3100 to provide management information specifically for the SDH. + +KEYWORDS: Synchronous Digital Hierarchy/Information Model/Managed Object Class/Attribute/Notification/Action/ GDMO/ASN.1. + +QUESTION: 14/15 + +SUBJECT AREA(S): SA-5 + +AVAILABILITY: Available + +REC/STD: G.85x + +TITLE: Management of the transport network + +ABSTRACT: This series of Recommendations provides an information model for the Transport Network. The definition and specification is described based on RM-ODP "Reference of Open Distributed Processing" methodology. + +KEYWORDS: Transport Network/RM-ODP. + +QUESTION: 18/4 + +SUBJECT AREA(S): SA-5 + +AVAILABILITY: Available + +### **Q-series** + +REC/STD: Q.811 + +TITLE: Lower layer protocol profiles for the Q3 and X interfaces + +ABSTRACT: This Recommendation provides the lower-layer protocol profiles for the Q3 and X-interfaces defined in Recommendation M.3010. It also provides a method for interworking. + +KEYWORDS: Q3-Interface/TMN/Protocol Profiles/DCN/ISDN/X.25/NSAP/Interworking. + +QUESTION: 19/4 + +SUBJECT AREA(S): SA-7 + +AVAILABILITY: Available + +REC/STD: Q.812 + +TITLE: Upper layer protocol profiles for the Q3 and X interfaces + +ABSTRACT: This Recommendation provides the upper-layer (5-7) protocol profiles for the Q3 and X-interfaces defined in Recommendation M.3010. + +KEYWORDS: Q3-Interface/TMN/Protocol Profiles/CMISE/FTAM/ACSE/ASN.1/EDI/X.500/CORBA/GIOP/IIOP. + +QUESTION: 19/4 + +SUBJECT AREA(S): SA-7 + +AVAILABILITY: Available + +REC/STD: Q.813 + +TITLE: Security Transformations Application Service Element for Remote Operations Service Element (STASE-ROSE) + +ABSTRACT: This Recommendation provides specifications to support security transformations, such as encryption, hashing, sealing and signing, focusing on whole Remote Operations Service Element (ROSE) Protocol Data Units (PDUs). Security transformations are used to provide various security services such as authentication, confidentiality, integrity and non-repudiation. This Recommendation describes an approach to the provisioning of security transformations that is implemented in the application layer and requires no security-specific functionality in any of the underlying OSI stack layers. + +QUESTION: 19/4 + +SUBJECT AREA(S): SA-12 + +AVAILABILITY: Available + +REC/STD: Q.821 + +TITLE: Stage 2 and stage 3 description for the Q3 interface – Alarm surveillance + +ABSTRACT: This Recommendation provides Stage 2 and Stage 3 Descriptions for the Q3-Interface in a TMN. Its focus is on Alarm Surveillance. Included in this Description are specifications of the functions, management information, services, functional units and protocols related to Alarm Surveillance. Significant reuse of OSI Systems Management specifications in the X.700-series Recommendations are described. Because of the desirability of providing common TMN solutions, this Recommendation is expected to be applicable to other TMN interfaces and TMN-related interfaces. + +KEYWORDS: Performance Management/Performance monitoring/Function/Objectclass/Attribute/Parameter/Service/ Functional unit/Protocol/ASN.1. + +QUESTION: 20/4 + +SUBJECT AREA(S): SA-8 + +AVAILABILITY: Available + +REC/STD: Q.822 + +TITLE: Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management + +ABSTRACT: This Recommendation provides Stage 1, Stage 2 and Stage 3 Descriptions for the Q3-Interface in a Telecommunications Management Network. Its focus is on the parameter collection and storage aspects and the thresholding aspects of Performance Management as they apply to the areas of performance monitoring, traffic management, and quality of service. Included in this Description are specifications of the functions, management information services, functional units and protocols related to Performance Management. Significant reuse of OSI Management protocols in the X.700-series Recommendations is described. + +Because of the desirability of providing common TMN solutions, this Recommendation is expected to be applicable to other TMN interfaces and TMN-related interfaces. + +**KEYWORDS:** Performance Management/Performance monitoring/Function/Objectclass/Attribute/Parameter/Service/ Functional unit/Protocol/ASN.1. + +**QUESTION:** 20/4 + +**SUBJECT AREA(S):** SA-8 + +**AVAILABILITY:** Available + +**REC/STD:** Q.823 + +**TITLE:** Stage 2 and stage 3 functional specifications for traffic management + +**ABSTRACT:** The scope of this Recommendation is to provide an information model which covers the management aspects of the traffic management service functions in an exchange. The scope is limited only to circuit switched networks using hierarchical routing. This Recommendation focuses on the Stage 2 and Stage 3 descriptions of the Q3-interface between Network Elements (NEs) and Operations Systems (OSs). The Stage 1 description is provided in the E.410-series Recommendations and in Recommendation E.502. + +**KEYWORDS:** + +**QUESTION:** 20/4 + +**SUBJECT AREA(S):** SA-8 + +**AVAILABILITY:** Available + +**REC/STD:** Q.824x + +**TITLE:** Stages 2 and 3 description for the Q3 interface – Customer administration + +**ABSTRACT:** The purpose of this series of Recommendations is to provide the common Stages 2 and 3 descriptions of the Q3-interface between a local exchange and the Telecommunications Management Network (TMN) for the support of configuration management functions in support of customer administration. Customer administration is a management activity that the network operator performs in order to exchange with the customer all the customer related management data and functions required to offer a telecommunications service, and to exchange with the network all the customer related management data and functions necessary for the network to produce that telecommunications service. These Recommendations support the administration of the customer configuration in the local exchange by the TMN. In these Recommendations the common non-technology specific managed objects are defined. + +**KEYWORDS:** + +**QUESTION:** 20/4 + +**SUBJECT AREA(S):** SA-5 + +**AVAILABILITY:** Available + +**REC/STD:** Q.825 + +**TITLE:** Specification of TMN applications at the Q3 interface: Call detail recording + +**ABSTRACT:** This Recommendation specifies the management functionality and the management information model required to support the management aspects of the Call Detail Recording function. The model applies to the Operation System to Network Elements (OS/NE) interface. The scope of the Recommendation is to support: + +- Data collection requirements for the analogue, digital and Integrated Services Digital Network (ISDN) subscribers. +- Data collection requirements in connection with Intelligent Network (IN). + +**KEYWORDS:** + +**QUESTION:** 20/4 + +**SUBJECT AREA(S):** SA-5 + +**AVAILABILITY:** Available + +**REC/STD:** Q.831 + +**TITLE:** Fault and performance management of V5 interface environments and associated customer profiles + +**ABSTRACT:** The purpose of this Recommendation is to define the Q3-interface between a Local Exchange (LE) and an Access Network (AN) and the Telecommunications Management Network (TMN) related to fault and performance management functions for V5 interfaces, as described in Recommendations G.964 and G.965, and their associated user ports. + +**KEYWORDS:** Access Network (AN)/ Fault Management/Performance Management/Information Model/Local Exchange/Line and Circuit Test Management/Q3-Interface/TMN/V5 Interface. + +**QUESTION:** 20/4 + +**SUBJECT AREA(S):** SA-5 + +**AVAILABILITY:** Available + +**REC/STD:** Q.832.1 + +**TITLE:** VB5.1 Management + +**ABSTRACT:** This Recommendation specifies the Q3-interfaces between a Service Node (SN) and the Telecommunications Management Network and between an Access Network (AN) and the TMN for the management associated with VB5.1 interfaces. + +**KEYWORDS:** Access Network (AN)/Fault Management/Performance Management/Information Model/Local Exchange/Line and Circuit Test Management/Q3-Interface/TMN/VB5.1 Interface. + +**QUESTION:** 21/4 + +**SUBJECT AREA(S):** SA-5 + +**AVAILABILITY:** Available + +**REC/STD:** Q.832.2 + +**TITLE:** VB5.2 Management + +**ABSTRACT:** This Recommendation specifies the Q3-interfaces between a Service Node (SN) and the Telecommunications Management Network and between an Access Network (AN) and the TMN for the management associated with VB5.2 interfaces. The managed object classes needed in addition to those defined for VB5.1 (Rec. Q.832.1) are defined. + +**KEYWORDS:** Access Network (AN)/Fault Management/Performance Management/Information Model/Local Exchange/Line and Circuit Test Management/Q3-Interface/TMN/VB5.2 Interface. + +QUESTION: 21/4 + +SUBJECT AREA(S): SA-5 + +AVAILABILITY: Available + +### **I-series** + +REC/STD: I.751 + +TITLE: Asynchronous transfer mode management of the network element view + +ABSTRACT: This Recommendation provides management requirements and an information model which pertain to the plane management of the ATM network element. The information model describes the managed object classes and their properties that are used to describe the information exchanged across management interfaces defined in Recommendation M.3010, Telecommunications Management Network (TMN) architecture. This Recommendation specializes the generic object classes of Recommendations M.3100, Q.821 and Q.822 to provide the information model specific to the ATM network element. + +KEYWORDS: Action/ASN.1/Asynchronous Transfer Mode/Attribute/DMO/Information Model/Managed Object Class/Notification. + +QUESTION: 15/4 + +SUBJECT AREA(s): SA-5 + +AVAILABILITY: Available + +![A hierarchical flow diagram illustrating the relationships between TMN-related Recommendations. At the top, 'Principles for a TMN (SG 4 M.3010)' is central, receiving input from 'SG 4 X.700 X.701' and 'Overview of TMN Recommendations (SG 4 M.3000)'. It links to 'TMN terminology and definitions (SG 4 clause 2/M.60)' and 'Considerations for a TMN (SG 4 M.3013)'. 'Considerations for a TMN' leads to 'TMN interface specification methodology (SG 4 M.3020)', which also links to 'TMN security overview (SG 4 M.3016)'. From 'TMN interface specification methodology', the diagram branches into three main areas: 'Generic network information model for TMN (SG 4 M.3100)', 'TMN management services and managed area (SG 4 M.3200)', and 'TMN management capabilities at F-interface (SG 4 M.3300)'. The 'Generic network information model' further branches into 'Managed object conformance statement (SG 4 M.3101)', 'Information model for a TMN management service (SG 4 M.310x.x)', and 'Catalogue of TMN management information (SG 4 M.3180)'. 'Information model for a TMN management service' connects to 'A TMN management service (SG 4 M.32xx.x-series)', which then leads to 'TMN management functions (SG 4 M.3400)'. 'TMN management functions' connects to several specific management areas: 'Management of ISDN/B-ISDN (SG 4 M.36xx-series)', 'Management of transport network (SG 15 G.774-series, SG 4 G.85x-series, SG 4 I.751)', 'Management of V5 interfaces (SG 4 Q.83x)', and 'Stages 1, 2 and 3 descriptions for Q-interface (SG 4 Q.82x)'. The 'Stages 1, 2 and 3 descriptions' node is also linked to 'Protocol profiles for the Q3-interface (SG 4 Q.81x)', which in turn links to 'Requirement framework for the TMN X-interface (SG 4 M.3320)'. External references like 'SG 4 X.72x-series SG 15 G.803', 'SG 4 X.71x-series', and 'SG 4 X.730/X.740-series' are shown with dashed arrows. A legend at the bottom explains that dashed arrows represent referenced recommendations, white boxes represent approved recommendations, and shaded boxes represent recommendations under study or planned.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +SG 4 +X.700 +X.701 + +Overview of TMN Recommendations +SG 4 M.3000 + +Principles for a TMN +SG 4 M.3010 + +TMN terminology and definitions +SG 4 clause 2/M.60 + +Considerations for a TMN +SG 4 M.3013 + +TMN security overview +SG 4 M.3016 + +TMN interface specification methodology +SG 4 M.3020 + +SG 4 +X.72x-series +SG 15 G.803 + +Generic network information model for TMN +SG 4 M.3100 + +TMN management services and managed area +SG 4 M.3200 + +TMN management capabilities at F-interface +SG 4 M.3300 + +Managed object conformance statement +SG 4 M.3101 + +Information model for a TMN management service +SG 4 M.310x.x + +A TMN management service SG 4 +M.32xx.x-series + +Requirement framework for the TMN X-interface +SG 4 M.3320 + +Catalogue of TMN management information +SG 4 M.3180 + +TMN management functions +SG 4 M.3400 + +Protocol profiles for the Q3-interface +SG 4 Q.81x + +SG 4 +X.71x-series + +SG 4 +X.730/X.740-series + +Management of ISDN/B-ISDN +SG 4 M.36xx-series + +Management of transport network +SG 15 G.774-series +SG 4 G.85x-series +SG 4 I.751 + +Management of V5 interfaces +SG 4 Q.83x + +Stages 1, 2 and 3 descriptions for Q-interface SG 4 +Q.82x + +Referenced Recommendations and responsible Study Groups + +(Draft) Rec. approved or under approval + +Recommendation under study or planned + +T0413130-99 + +A hierarchical flow diagram illustrating the relationships between TMN-related Recommendations. At the top, 'Principles for a TMN (SG 4 M.3010)' is central, receiving input from 'SG 4 X.700 X.701' and 'Overview of TMN Recommendations (SG 4 M.3000)'. It links to 'TMN terminology and definitions (SG 4 clause 2/M.60)' and 'Considerations for a TMN (SG 4 M.3013)'. 'Considerations for a TMN' leads to 'TMN interface specification methodology (SG 4 M.3020)', which also links to 'TMN security overview (SG 4 M.3016)'. From 'TMN interface specification methodology', the diagram branches into three main areas: 'Generic network information model for TMN (SG 4 M.3100)', 'TMN management services and managed area (SG 4 M.3200)', and 'TMN management capabilities at F-interface (SG 4 M.3300)'. The 'Generic network information model' further branches into 'Managed object conformance statement (SG 4 M.3101)', 'Information model for a TMN management service (SG 4 M.310x.x)', and 'Catalogue of TMN management information (SG 4 M.3180)'. 'Information model for a TMN management service' connects to 'A TMN management service (SG 4 M.32xx.x-series)', which then leads to 'TMN management functions (SG 4 M.3400)'. 'TMN management functions' connects to several specific management areas: 'Management of ISDN/B-ISDN (SG 4 M.36xx-series)', 'Management of transport network (SG 15 G.774-series, SG 4 G.85x-series, SG 4 I.751)', 'Management of V5 interfaces (SG 4 Q.83x)', and 'Stages 1, 2 and 3 descriptions for Q-interface (SG 4 Q.82x)'. The 'Stages 1, 2 and 3 descriptions' node is also linked to 'Protocol profiles for the Q3-interface (SG 4 Q.81x)', which in turn links to 'Requirement framework for the TMN X-interface (SG 4 M.3320)'. External references like 'SG 4 X.72x-series SG 15 G.803', 'SG 4 X.71x-series', and 'SG 4 X.730/X.740-series' are shown with dashed arrows. A legend at the bottom explains that dashed arrows represent referenced recommendations, white boxes represent approved recommendations, and shaded boxes represent recommendations under study or planned. + +**Figure A.1/M.3000 – Example of relation between TMN-related Recommendations** + +# ANNEX B + +## List of TMN-related Recommendations + +Some main Recommendations that are referenced by TMN Recommendations are listed here. + +### **Telecommunication network architecture area** + +REC/STD: G.803 + +TITLE: Architecture of transport networks based on the synchronous digital hierarchy (SDH) + +REC/STD: G.805 + +TITLE: Generic functional architecture of transport networks + +REC/STD: I.326 + +TITLE: Functional architecture of transport networks based on ATM + +These Recommendations are referenced by Recommendations M.3100, G.85x, I.751 and G.774 to develop TMN Network Information Models. + +#### **OSI Management** + +The following list of Data Network and OSI System Communication Recommendations is referenced to develop and maintain relevant TMN Management Recommendations. + +#### **Maintenance** + +- X.160            Architecture for customer network management service for public data networks +- X.161            Definition of customer network management services for public data networks +- X.162            Definition of management information for customer network management service for public data networks to be used with the CNMc interface +- X.162 Amd.1    Implementation Conformance Statement (ICS) proformas +- X.163            Definition of management information for customer network management service for public data networks to be used with the CNMe interface +- X.170            Network-to-network management architecture for data networks +- X.171            Network-to-network management services for data networks + +#### **Layer Managed Objects** + +- X.281            Information technology – Elements of management information related to the OSI Physical Layer +- X.282            Elements of management information related to the OSI data link layer +- X.282 Amd.1    Implementation Conformance Statement proformas +- X.283            Information technology – Elements of management information related to the OSI Network Layer +- X.284            Information technology – Elements of management information related to the OSI Transport Layer + +#### **Systems Management Framework and Architecture** + +- X.700 Management framework for Open Systems Interconnection (OSI) for CCITT applications +- X.701 Information technology – Open Systems Interconnection – Systems management overview +- X.702 Information technology – Open Systems Interconnection – Application context for systems management with transaction processing +- X.703 Information technology – Open Distributed Management Architecture +- X.703 Amd.1 Support using common object Request Broker Architecture (CORBA) + +#### **Management Communication Service and Protocol** + +- X.710 Information technology – Open systems Interconnection – Common management information service +- X.711 Information technology – Open systems Interconnection – Common management information protocol: Specification +- X.712 Information technology – Open Systems Interconnection – Common management information protocol: Protocol Implementation Conformance Statement (PICS) proforma + +#### **Structure of Management Information** + +- X.720 Information technology – Open Systems Interconnection – Structure of management information: Management information model +- X.720 Amd.1 Generalization of terms +- X.721 Information technology – Open Systems Interconnection – Structure of management information: Definition of management information +- X.721 Amd.1 Enhanced event control +- X.722 Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects +- X.722 Amd.1 Set by create and component registration +- X.722 Amd.2 Addition of the NO-MODIFY syntax element and guidelines extension +- X.722 Amd.3 Guidelines for the use of Z in formalizing the behaviour of managed objects +- X.723 Information technology – Open Systems Interconnection – Structure of management information: Generic management information +- X.724 Information technology – Open Systems Interconnection – Structure of management information: Requirements and guidelines for implementation conformance statement proformas associated with OSI management +- X.725 Information technology – Open Systems Interconnection – Structure of management information: General relationship model +- X.727 Information technology – Open Systems Interconnection – Structure of management information: Systems management application layer managed objects + +#### **Management functions and ODMA functions** + +- X.730 Information technology – Open Systems Interconnection – Systems Management: Object management function +- X.730 Amd.1 Implementation Conformance Statement proformas +- X.731 Information technology – Open Systems Interconnection – Systems Management: State management function +- X.731 Amd.1 Implementation Conformance Statement proformas +- X.732 Information technology – Open Systems Interconnection – Systems Management: Attributes for representing relationships +- X.732 Amd.1 Implementation Conformance Statement proformas +- X.733 Information technology – Open Systems Interconnection –Systems Management: Alarm reporting function +- X.733 Amd.1 Implementation Conformance Statement proformas +- X.734 Information technology – Open Systems Interconnection – Systems Management: Event Report Management Function +- X.734 Amd.1 Implementation Conformance Statement proformas +- X.735 Information technology – Open Systems Interconnection – Systems Management: Log control function +- X.735 Amd.1 Implementation Conformance Statement proformas +- X.736 Information technology – Open Systems Interconnection – Systems Management: Security alarm reporting function +- X.736 Amd.1 Implementation Conformance Statement proformas +- X.737 Information technology – Open Systems Interconnection – Systems Management: Confidence and diagnostic test categories +- X.738 Information technology – Open Systems Interconnection – Systems Management: Summarization function +- X.738 Amd.1 Implementation Conformance Statement proformas +- X.739 Information technology – Open Systems Interconnection – Systems Management: Metric objects and attributes +- X.739 Amd.1 Implementation Conformance Statement proformas +- X.740 Information technology – Open Systems Interconnection – Systems Management: Security audit trail function +- X.741 Information technology – Open Systems Interconnection – Systems management: Objects and attributes for access control +- X.742 Information technology – Open Systems Interconnection – Systems management: Usage metering function for accounting purposes +- X.742 Amd.1 Implementation Conformance Statement proformas +- X.743 Information technology – Open Systems Interconnection – Systems Management: Time management function +- X.744 Information technology – Open Systems Interconnection – Systems Management: Software management function + +- X.745 Information technology – Open Systems Interconnection – Systems Management: Test management function +- X.746 Information technology – Open Systems Interconnection – Systems Management: Scheduling function +- X.748 Information technology – Open Systems Interconnection – Systems Management: Response time monitoring function +- X.749 Information technology – Open Systems Interconnection – Systems Management: Management domain and management policy management function +- X.750 Information technology – Open Systems Interconnection – Systems Management: Management knowledge management function +- X.750 Amd.1 Relationship knowledge +- X.751 Information technology – Open Systems Interconnection – Systems Management: Changeover function +- X.753 Information technology – Open Systems Interconnection – Systems Management: Command sequencer for systems management +- X.770 Open Distributed Management Architecture (ODMA) functions: Notifications, selection and dispatch function +- X.790 Trouble management function for ITU-T applications +- X.790 Amd.1 Implementation Conformance Statement proformas +- X.791 Profile for trouble management function for ITU-T applications +- X.792 Configuration audit support function for ITU-T applications + +### **ISP and implementation requirements area** + +REC/STD: ISO/IEC ISP 11183 + +DESCRIPTION: This three-part standard specifies two network management profiles. ISP 11183 Part 1 identifies the requirements (including values in some cases) of parameters in session, presentations and ACSE protocol data units and functional units. ISP 11183 Part 2 specifies requirements on ROSE and CMIP with all the functional units of CMIP except the extended functional unit. ISP 11183 Parts 1 and 2 are referred to as the AOM 12 profile. ISP 11183 Part 3 specifies the requirements on ROSE and CMIP with only the CMIP kernel functional unit. ISP 11183 Parts 1 and 3 are referred to as the AOM 11 profile. + + + + + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | + +\*18601\* \ No newline at end of file diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e60c7cd2b5c00ce83de245aa7b03a65987722a99 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7f60e7fda98331616373ebc7d7fcfc5c7ae55ab46c486c49cf74278dfb0b5f4 +size 59107 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b18e5b07ba6a266813c0ce76e92f4e93c0d9fd4b --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a97195c2fd68ad39d82d19b808d1738dce3aa52e94325870a031b5a2ea7c01 +size 8275 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9827cba31632801ecc0e40b97ba7f9ceedbb3f20 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7983679dd58fa5383fd4b71da9c9092fbd82946bafeb0fd07f126da7bc3e94b2 +size 21679 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9bfd76f41ec44c599b5774f1ddbaa39e5c6deb4 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe7af190588ceab9a6e5183ebd2ab079734d0288bfe26d3bb6d3e95bbc1f5d86 +size 113718 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d513aad1bd73205c393154293241b2b393f260a --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cf318e3c8aec4d2f822ba559c78c746aa27ffc9eb13eb0a7760ab42307cad48 +size 50431 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e2457c8391154cd4c74774882473f92503cab8d --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87cdc3232b4ecf53a3120e718b6ebe538a9a3922d8bd882c082fbd7081be1731 +size 62013 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8072d9f9e4412eb44de3f91c4e0b9290c60981cb --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c4edaa678a9eb8c4538150110f322172613e1e8c19ea5967a828f0f4952f4db +size 114096 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b241aeb62460ccb81a73e122d84280cf217e6306 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:982782a193f2eacb39001c5d15e4fd5b6f8edb5b4b0401f2969dbff688a9dbb7 +size 77293 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a274702928d5957156befd80bca3f3f46683459 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa9a9224f8cc47cff231c1944047505db4f1dd244e6334e0479514fa752be5c9 +size 60025 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4734269ca73dad8f6cc50e28dc266f696f03b394 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3647b6e736b4d682261f82cfb9c79c57307a8f2aa0ce7ea6298faf4e6a381ae9 +size 89908 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76ad98f9a00a8a3cf97dc70f80a5f487f180469e --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7870f9f9526550f6d0a6fd36af7986ce40291c3b139479a068d2fe23983b40dd +size 12916 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ed718ff6c113fafca6c07f7b3799e174bbf43a1 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:681dd8ba672d31641e5a1ae9509f5e1650f94359955b9c97e7221753fea3ffa3 +size 9199 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..654800eff655d792398d08b33ce2620c2c68b6c1 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2c6541f8af10afd83fe7995f7352b3de4d03b235f312ab0087ceaaf61339645 +size 80776 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..180a188cbe17997da0c35bc6e71d514f8f344feb --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9c02e53a598b6dd6157961508164956ff72532d66cbe80317b666219d044142 +size 52039 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fab6cb868d29342b5e62447a74ba5c48232c5e26 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd73ce94ae2f2dd944e53a2a68364dbcdfedcbe87b77888dc8967f97d676b6b7 +size 105008 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a777d3bc7b7231b42c7f0c32b2eb6472f0dfeebd --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:875cebbfeddb870b9364ccd4e31be0f3fa477cf4fceab997a74ce5bc85a23e57 +size 75058 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b87bb94b8ec90b898cff02f452f0c6f2c1b23e7d --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7d932d839cadb33220500fd416ab84d01a1821a509be3dbf8c0613b973cc411 +size 37024 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bb5bfeebf0bb51c1df987e35ea1d35d351d1987 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:842381a115731d3ed3dcb31d751bc7b07f99e58fffbd4ad60d6206085f50733b +size 19591 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f3aa135170fdb3dfd61da2ee209618248e0f957 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:881a7dab7acc29002ae3e0c7d62bdbdd3f2f48a5f6ebdb07e6ee6e77b2182550 +size 103805 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce998b57b3cdc9ca83dc8ee1032ae08cd3b43a6f --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:329c3baae63df4a724aa56332246d58bc3d8d1b291e2fa48454a500f2fb42000 +size 57181 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce7e345c14ced004284b0349e66665c63e24f1f9 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:201b9275d3d9459aa363ff414843eae30af5e1537775c5877970f00ea45dac18 +size 12564 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23df0e0f0be2707d2eb9d22342c9172ddc08dcd4 --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7bcf57bd8f80ab8bc0b0b7c97600009ed9cd6194a28bb03100e8365d3c385e5 +size 84548 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6922a2dd39f6992a2af042cb9834bdc3ea24af7d --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de692958b08aed7667b2c5635a81810ba8d9c16fc1b8c4876847050ab369927c +size 39781 diff --git a/marked/M/T-REC-M.3013-200002-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/M/T-REC-M.3013-200002-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12a769a46322452112cd6b8e31b8e88164af2bcf --- /dev/null +++ b/marked/M/T-REC-M.3013-200002-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85d9e045c0178b2090183eaa796dccf532f858494a5edee67fa3db0855953b79 +size 19208 diff --git a/marked/M/T-REC-M.3016.0-200505-I_PDF-E/raw.md b/marked/M/T-REC-M.3016.0-200505-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e2433fca21e2ad3017706ecf7c4a801b10b327fc --- /dev/null +++ b/marked/M/T-REC-M.3016.0-200505-I_PDF-E/raw.md @@ -0,0 +1,793 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3016.0** + +(05/2005) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Security for the management plane: Overview** + +ITU-T Recommendation M.3016.0 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3016.0** + +# **Security for the management plane: Overview** + +## **Summary** + +This Recommendation provides an overview and framework that identifies security threats to a TMN and outlines how available security services can be applied within the context of the TMN functional architecture. + +## **Source** + +ITU-T Recommendation M.3016.0 was approved on 22 May 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Rationale ..... | 3 | +| 6 System description..... | 3 | +| 6.1 Actors and roles..... | 4 | +| 6.2 Security domains ..... | 5 | +| 7 Generic security objectives for TMN ..... | 5 | +| 8 Legislation issues..... | 6 | +| 9 Threats and risks ..... | 6 | +| 10 Security requirements and services ..... | 7 | +| 10.1 Security requirements and corresponding services ..... | 8 | +| 10.2 Requirements on the management of security..... | 12 | +| 10.3 Architectural requirements ..... | 13 | +| 10.4 Security services and OSI layers ..... | 13 | +| 10.5 Security management ..... | 15 | +| Appendix I – Functional classes and security subprofiles ..... | 16 | +| I.1 Grouping of security measures..... | 16 | +| I.2 Functional classes..... | 16 | +| I.3 Security profiles..... | 18 | + + + +# Security for the management plane: Overview + +# 1 Scope + +This Recommendation provides an overview and framework that identifies security threats to a TMN and outlines how available security services can be applied within the context of the TMN functional architecture, as described in ITU-T Rec. M.3010. + +This Recommendation is generic in nature and does not identify or address the requirements for a specific TMN interface. + +This Recommendation does not seek to define new security services but uses existing security services defined in other ITU-T Recommendations and ISO Standards. + +This Recommendation is part of the M.3016.x series of ITU-T Recommendations intended to provide guidance and recommendations for securing the management plane of evolving networks: + +ITU-T Rec. M.3016.0 – *Security for the management plane: Overview.* + +ITU-T Rec. M.3016.1 – *Security for the management plane: Security requirements.* + +ITU-T Rec. M.3016.2 – *Security for the management plane: Security services.* + +ITU-T Rec. M.3016.3 – *Security for the management plane: Security mechanism.* + +ITU-T Rec. M.3016.4 – *Security for the management plane: Profile proforma.* + +ITU-T Recs M.3016.1, M.3016.2 and M.3016.3 specify a set of requirements, services and mechanisms for the appropriate security of the management functions necessary to support the telecommunications infrastructure. Because different administrations and organizations require varying levels of security support, ITU-T Recs M.3016.1, M.3016.2 and M.3016.3 do not specify whether a requirement/service/mechanism is mandatory or optional. + +The proforma defined in ITU-T Rec. M.3016.4 is provided to assist organizations, administrations and other national/international organizations, to specify the mandatory and optional support of the requirements as well as value ranges, values, etc. to help implement their security policies. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation E.408 (2004), *Telecommunication networks security requirements.* +- ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network.* +- ITU-T Recommendation M.3400 (2000), *TMN management functions.* +- ITU-T Recommendation X.509 (2000), *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks.* + +- ITU-T Recommendation X.741 (1995), *Information technology – Open Systems Interconnection – Systems management: Objects and attributes for access control.* +- ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications.* +- ITU-T Recommendation X.802 (1995), *Information technology – Lower layers security model.* +- ITU-T Recommendation X.803 (1994), *Information technology – Open Systems Interconnection – Upper layers security model.* +- ITU-T Recommendation X.810 (1995), *Information technology – Open Systems Interconnection – Security frameworks for open systems: Overview.* +- ITU-T Recommendation X.812 (1995), *Information technology – Open Systems Interconnection – Security frameworks for open systems: Access control framework.* +- ITU-T Recommendation X.813 (1996), *Information technology – Open Systems Interconnection – Security frameworks for open systems: Non-repudiation framework.* +- ITU-T Recommendation X.814 (1995), *Information technology – Open Systems Interconnection – Security frameworks for open systems: Confidentiality framework.* +- ITU-T Recommendation X.815 (1995), *Information technology – Open Systems Interconnection – Security frameworks for open systems: Integrity framework.* +- ITU-T Recommendation X.816 (1995), *Information technology – Open Systems Interconnection – Security frameworks for open systems: Security audit and alarms framework.* +- ISO/IEC 9979:1999, *Information technology – Security techniques – Procedures for the registration of cryptographic algorithms.* + +# 3 Definitions + +This Recommendation does not define any new terms. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| CCITT | International Telegraph and Telephone Consultative Committee | +| DCN | Data Communication Network | +| FC | Functional classes | +| ISO | International Organization for Standardization | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| LLA | Logical Layered Architecture | +| MF | Mediation Function | +| NEF | Network Element Function | +| OSF | Operation System Function | +| OSI | Open System Interconnection | +| PIN | Personal Identification Number | +| TF | Transformation Function | + +| | | +|-----|---------------------------------------| +| TMN | Telecommunications Management Network | +| TTP | Trusted Third Party | +| WSF | WorkStation Function | + +# 5 Rationale + +The requirement for security in TMN has originated from different sources: + +- **Customers/subscribers** need confidence in the network and the services offered, including correct billing. +- **The Public Community/Authorities** demand security by Directives and Legislation, in order to ensure availability of services and privacy protection. +- **Network Operators/Service Providers** themselves need security to safeguard their operation and business interests, and to meet their obligations to the customers and the public. + +A TMN is intended to manage the underlying telecommunications network; therefore, the security of the TMN is essential to the proper functioning of the telecommunications network. Furthermore, the telecommunications network may incorporate security features that need to be managed by the TMN. ITU-T Rec. M.3400 enumerates those security management functions. + +TMN Security Standards should preferably be based upon internationally agreed security standards as it is beneficial to reuse rather than create new ones. The provisioning and usage of security services and mechanisms can be quite expensive relative to the value of the transactions being protected. It is, therefore, important to be able to customize the security provided to the TMN transactions being protected. The security services and mechanisms that are used for securing TMN transactions should be provided in a way that allows such customization. Due to the large number of possible combinations of security features, it is desirable to have **security profiles** (see Appendix I) that cover a broad range of TMN security applications. + +Standardization will facilitate **reuse of solutions and products**, meaning that security can be introduced faster and at lower cost. + +Important benefits of standardized solutions for vendors and users of the systems alike are the economy of scale in product development and component interoperation within a TMN system with regard to security. + +It is necessary to provide security services and mechanisms to protect TMN transactions among TMN entities (as defined in ITU-T Rec. M.3010) against malicious attacks such as eavesdropping, spoofing, tampering with messages (modification, delay, deletion, insertion, replay, re-routing, misrouting, or re-ordering of messages), repudiation or forgery. Protection includes prevention, detection and recovery from attacks, as well as management of security-related information. Standards should cover both intra-domain (Q and F) and inter-domain (X) interfaces. + +# 6 System description + +The objective of this Recommendation is an abstraction which makes it possible to avoid the many implementation details and to agree upon results that may be useful when later mapped on to specific implementations. + +The TMN is described in terms of a functional architecture, an information architecture and a physical architecture (ITU-T Rec. M.3010). + +It is recognized in ITU-T Rec. M.3010 that TMN building blocks may support other interfaces in addition to those of Q, X and F. Similarly, the physical equipment may have other functionality in addition to that associated with information received via Q, X and F. These additional interfaces + +and related functionality are outside the scope of the TMN and, therefore, outside the scope of TMN security standardization. + +![Figure 1/M.3016.0 – TMN functional architecture diagram. The diagram shows two TMN (Telecommunications Management Network) domains, each enclosed in a dashed box. The left TMN contains three functional blocks: WSF (Work Station Function) at the top, OSF (Operation System Function) in the middle, and NEF (Network Element Function) at the bottom. WSF is connected to an external point 'g' and to OSF via a vertical line labeled 'f'. OSF is connected to NEF via a line labeled 'q' and has an external connection point 'q' on its left. The right TMN contains four functional blocks: WSF at the top, OSF in the middle, TF (Translation Function) at the bottom left, and NEF at the bottom right. WSF is connected to an external point 'g' and to OSF via a vertical line labeled 'f'. OSF is connected to both TF and NEF via lines labeled 'q'. TF is connected to an external point 'm'. A horizontal line connects the OSF of the left TMN to the OSF of the right TMN, with a point 'x' marked on this line. The label 'M.3016.0_F6.1' is in the bottom right corner.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +Figure 1/M.3016.0 – TMN functional architecture diagram. The diagram shows two TMN (Telecommunications Management Network) domains, each enclosed in a dashed box. The left TMN contains three functional blocks: WSF (Work Station Function) at the top, OSF (Operation System Function) in the middle, and NEF (Network Element Function) at the bottom. WSF is connected to an external point 'g' and to OSF via a vertical line labeled 'f'. OSF is connected to NEF via a line labeled 'q' and has an external connection point 'q' on its left. The right TMN contains four functional blocks: WSF at the top, OSF in the middle, TF (Translation Function) at the bottom left, and NEF at the bottom right. WSF is connected to an external point 'g' and to OSF via a vertical line labeled 'f'. OSF is connected to both TF and NEF via lines labeled 'q'. TF is connected to an external point 'm'. A horizontal line connects the OSF of the left TMN to the OSF of the right TMN, with a point 'x' marked on this line. The label 'M.3016.0\_F6.1' is in the bottom right corner. + +**Figure 1/M.3016.0 – TMN functional architecture** + +## 6.1 Actors and roles + +For the purpose of TMN security standardization, only technical security will be considered, which means that the relevant actors to consider are *TMN users*. A TMN user is a person or process applying TMN Management Services for the purpose of fulfilling management operations. TMN users can further be categorized dependent on whether they belong to the organization running the TMN (internal users) or whether they access the TMN as external users. + +Each time a TMN user accesses a Management Service, the TMN user will take on a role. In some cases there will be a one-to-one relationship between a TMN user and a role, i.e., the TMN user will always stay in the same role. In other cases, there will be a one-to-many relationship between a specific TMN user and the possible roles the TMN user can play. + +The following gives a high-level classification of some common roles: + +- Network Operators (*private or public*); +- Service Providers (*Bearer Service Providers or Value Added Service Providers*); +- Service Subscribers/Service Customers; +- Service End Users; +- Equipment/Software Vendors; +- Trusted Third Party (that is, a third party who is trusted by both parties and operates in accordance with relevant national laws and regulations to provide certification, authentication, and related services). + +When securing the TMN, it is not enough to control the behaviour of known TMN users. One must also consider the possibility of an intruder attempting illegal access to the TMN. + +Some security measures require actors playing the role of a Trusted Third Party (TTP). An important security issue is how these actors should be allowed to interact with the TMN. + +## 6.2 Security domains + +ITU-T Rec. M.3010 introduces the concept of a Logical Layered Architecture (LLA) in which the management functionality is partitioned into layers. Each layer is concerned with a clearly bound subset of the total management activity. Each functional layer will be a separate *management domain* under the control of an Operation System Function (OSF), called an OSF-domain. Network Element Functions (NEFs) controlled by the OSF will be part of the OSF-domain. A TMN will as such be composed of one or several OSF domains, where the different OSF-domains can be either disjoint, interacting, overlapping or contained. + +A *security domain* is defined as a set of entities and parties that are subject to a single security policy and a single security administration. A normal assumption has been to consider a TMN as a single security domain. This will often be the case, but it might not be valid to make it a general assumption. In larger TMNs, consisting of many different management systems, different parts of the TMN might be subject to different security policies and security requirements. Therefore, it seems more appropriate to say that a TMN security domain encompasses one single OSF-domain or a set of OSF-domains. + +Using this assumption, the following inter-security domain and intra-security domain relationships will apply: + +Possible intra-security domain relationships: + +- q (OSF-NEF, OSF-OSF). + +Possible inter-security domain relationships: + +- x (OSF-OSF); +- f (WSF-OSF, WSF-MF); +- q (OSF-OSF, OSF-TF). + +Note that the above relationships refer to security domains and not to management domains. An important thing to note is that a q reference point may be involved in both intra-security domain and inter-security domain relationships. One main difference between intra-domain and inter-domain relationships is the degree of trust that exists between the involved entities. + +# 7 Generic security objectives for TMN + +The purpose of this clause is to describe the ultimate aim of the security measures taken in a TMN compliant environment. The focus is on what security will achieve rather than on how it is done. + +Security objectives should be derived from the operator's; and other actors', interests, business relations, legal and regulatory constraints, contractual constraints, etc. + +The security objectives for the TMN are: + +- Only legitimate actors should be able to access and operate on assets in a TMN. +- Legitimate actors should be able to access and operate on assets they are authorized to access. +- All actors should be held accountable for their own but only their own actions in the TMN. +- Availability of the TMN should be protected against unsolicited access or operations. +- It should be possible to retrieve security-related information from the TMN. +- If security violations are detected, they should be handled in a controlled way, thus minimizing the damage caused. +- After a security breach is detected, it should be possible to restore normal security levels. +- The security architecture of the TMN should provide a certain flexibility in order to support different security policies, e.g., different strength of security mechanisms. + +The term "to access assets" is understood not only to be the possibility to perform functions but also to read information. + +The generic objectives are phrased according to the view and language of enterprise management. The following clauses need to be expressed in more technical terms leading to implementable security services and functions. The mapping between the two languages is not always obvious. + +It can be shown that by meeting the following set of security objectives the first five of the above-mentioned security objectives for TMN of this clause will be met: + +- confidentiality; +- data integrity; +- accountability; +- availability. + +Threats and risks identified in clause 9 and functional requirements in clause 6 will be based on these more formal terms. For definitions, see clause 9. + +# 8 Legislation issues + +The security infrastructure of a TMN must be able to accommodate constraints imposed by government laws, contractual legislation, treaties, and regulations. These constraints may include mandatory security services (such as assuring the privacy of customer information), the exclusion of certain security mechanisms (such as some types of encryption) and/or support for secret wiretapping by law enforcement agencies. + +# 9 Threats and risks + +The intention of this clause is to explore the threats and risks to a TMN. It is not the intention to specify risk assessment or threat analysis for individual TMN instances. These are local matters that can be handled differently by each provider without affecting interoperability. + +A threat is a potential violation of security. According to the identified generic security objectives in TMN, threats may be directed at four different kinds of objectives: + +- **confidentiality** (confidentiality of stored and transferred information); +- **data integrity** (protection of stored and transferred information); +- **accountability** (any entity should be responsible for any actions initiated); and +- **availability** (all legitimate entities should experience correct access to TMN facilities). + +This Recommendation distinguishes between three kinds of threats: + +- accidental threat: a threat whose origin does not involve any malicious intent; +- administrative threat: a threat that arises from a lack of administration of security; and +- intentional threat: a threat that involves a malicious entity which may attack either the communication itself or network resources. + +Accidental and administrative threats may be taken into account by TMN standardization work as long as their consequences are the same as intentional threats. In order to give a more accurate analysis of threats, taking into account the TMN architecture, this Recommendation focuses on intentional threats involving communication between different actors of the TMN. The aim of this approach is to give a shorter list of threats that may be used directly in the standardization work of TMN. A threat analysis of TMN should thus address the following items based on ITU-T Rec. X.800: + +- **masquerade ("spoofing")**: the pretence by an entity to be a different entity; + +- **eavesdropping**: a breach of confidentiality by monitoring communication; +- **unauthorized access**: an entity attempts to access data in violation of the security policy in force; +- **loss or corruption of information**: the integrity of data transferred is compromised by unauthorized deletion, insertion, modification, re-ordering, replay or delay; +- **repudiation**: an entity involved in a communication exchange subsequently denies the fact; +- **forgery**: an entity fabricates information and claims that such information was received from another entity or sent to another entity; +- **denial of service**: This occurs when an entity fails to perform its function or prevents other entities from performing their functions. This may include denial of access to TMN and denial of communication by flooding the TMN. In a shared network, this threat can be recognized as a fabrication of extra traffic that floods the network, preventing others from using the network by delaying the traffic of others. + +Table 1 gives a map of threats and objectives. + +**Table 1/M.3016.0 – Mapping of threats and objectives** + +| Threat | Confidentiality | Data Integrity | Accountability | Availability | +|-------------------------------------------------|-----------------|----------------|----------------|--------------| +| Masquerade | x | x | x | x | +| Eavesdropping | x | | | | +| Unauthorized access | x | x | x | x | +| Loss or corruption of information (transferred) | | x | | x | +| Repudiation | | | x | | +| Forgery | | x | x | | +| Denial of service | | | | x | + +A potential threat to a system is of no harm unless there is a corresponding weakness in the system and a point in time when that weakness is exploited. Each threat will imply a risk. Evaluation of the risk may be split into the evaluation of the likelihood of each threat and an evaluation of the impact the threat may have. Threat and risk evaluation must be part of an iterative process: new threats may emerge when countermeasures are established, e.g., threats to cryptography keys when cryptographic measures are used. + +# 10 Security requirements and services + +Figure 2 describes the relationships between Security objectives, Threats, Security requirements, and Services. It describes the process how to derive "Security requirements" from "Threats" and "Security objectives" which in turn will be realized by a set of security services. These "Services", which counteract threats, will make use of "Mechanisms" which themselves make use of "Security algorithms". + +![Figure 2/M.3016.0 – Security framework flowchart showing the relationship between Threat, Security requirements, Security services, Security mechanisms, and Security algorithms, with Security objectives influencing Security requirements.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + Threat[Threat] --> SR[Security requirements] + SR --> SS[Security services] + SS --> SM[Security mechanisms] + SM --> SA[Security algorithms] + SO[Security objectives] --> SR + +``` + +Figure 2/M.3016.0 – Security framework flowchart showing the relationship between Threat, Security requirements, Security services, Security mechanisms, and Security algorithms, with Security objectives influencing Security requirements. + +M.3016.0\_F2 + +**Figure 2/M.3016.0 – Security framework** + +Clause 10.1 lists such security requirements. Unless otherwise specified, the word "requirement" in this Recommendation does not mean that some functionality is always mandatory in each TMN; rather, it means that a functionality can be made mandatory by a TMN administration for some specific applications and/or interfaces of that TMN. The actual choice will depend on the security objectives stated in the security policy of the operator. + +In addition to security requirements and services, this clause also states some generic requirements for the management of the security services (see 10.2) and architectural requirements governing the integration of security services into the TMN architecture (see 10.3). Administrative and life-cycle requirements are important but will not affect the architecture and are not included in this clause. + +## 10.1 Security requirements and corresponding services + +This clause describes a set of generic functional requirements and the corresponding services which can be used to counteract threats to a TMN. + +### 10.1.1 Mapping functional requirements, threats and security objectives + +This clause will identify functional security requirements to cover the threats listed in clause 9. This has been done in Table 2. From this, the security requirements have been mapped (Table 3) to the security objectives stated in clause 7. The list is limited to requirements which are generic in nature and have substantial impact on components and architecture. + +**Table 2/M.3016.0 – Mapping of functional requirements and threats** + +| Functional requirement | Masquerade | Eavesdropping | Unauthorized access | Loss or corruption of information | Repudiation | Forgery | Denial of service | +|-------------------------------------|------------|---------------|---------------------|-----------------------------------|-------------|---------|-------------------| +| Verification of identities | x | | x | | | | | +| Controlled access and authorization | | | x | | | | x | +| Protection of confidentiality | | x | x | | | | | +| Protection of data integrity | | | | x | | | | +| Accountability | | | | | x | x | | +| Activity logging | x | | x | | x | x | x | +| Alarm reporting | x | | x | x | | | x | +| Audit | x | | x | | x | x | x | + +The objectives used are the four formal ones defined in clause 3, each with a column in Table 3, indicating the set of functional requirements to meet the objective in question. + +### 10.1.2 Description of functional requirements and the corresponding services + +The functional requirements of Tables 2 and 3 are further discussed in the text which follows and, to each of the requirements, the corresponding security services are identified. Observe that the requirements for any of these functions do not automatically invoke a security service as defined by ISO. In practice, however, there is a coincidence in some of the cases. + +**Table 3/M.3016.0 – Mapping of security objectives and functional requirements** + +| Functional requirement | Confidentiality | Data integrity | Accountability | Availability | +|-------------------------------------|-----------------|----------------|----------------|--------------| +| Verification of identities | x | x | x | | +| Controlled access and authorization | x | x | x | x | +| Protection of confidentiality | x | | | | +| Protection of data integrity | | x | | | +| Accountability | | | x | | +| Activity logging | | | x | x | +| Alarm reporting | x | x | x | x | +| Audit | | | x | x | + +#### 10.1.2.1 Verification of identities + +*A TMN should provide capabilities to establish and verify the claimed identity of any actor in the TMN.* + +Actors can be human users or entities within the TMN. Verified identities provide the basis of accountability and are fundamental to meet most of the security requirements listed in this clause. + +The security service to support the requirement is **authentication**. The authentication service delivers proof that the identity of an object or subject has indeed the identity it claims to have. Depending on the type of actor and on the purpose of identification, the following kinds of authentication may be required: + +- user authentication, establishing proof of the identity of the human user or application process; +- peer entity authentication, establishing the proof of the identity of the peer entity during a communication relationship; +- data origin authentication, establishing the proof of identity responsible for a specific data unit. + +Usage of an authentication service establishes the proof for a particular instance of time. To ensure continued proof, the authentication has to be repeated or linked to an integrity service. + +Examples of mechanisms used to implement the authentication service are passwords and Personal Identification Numbers (PINs) (simple authentication) and cryptographic-based methods (strong authentication). + +#### 10.1.2.2 Controlled access and authorization + +*A TMN should provide capabilities to ensure that actors are prevented from gaining access to information or resources that they are not authorized to access.* + +The security service to meet this requirement is **access control**. The access control service provides means to ensure that resources are accessed by subjects only in an authorized manner. Resources concerned may be the physical system, the system software, applications and data. The access + +control service can be defined and implemented at different levels of granularity in the TMN: at agent level, object level or attribute level. The limitations of access are laid out in access control information, which specify: + +- the means to determine which entities are authorized to have access; +- what kind of access is allowed (reading, writing, modifying, creating, deleting). + +More specific TMN access control can be divided into three types: + +- *Management association access control* + +This service enables access control at the management association level, meaning that the access rights are related to the association itself, i.e., the right to establish the association. + +- *Management notification access control* + +This service enables access control with respect to notifications, i.e., to ensure that notifications are only disclosed to entities authorized to receive them. + +- *Managed resource access control* + +This service provides access control with respect to the resources themselves. + +The identity of the entity trying to gain access needs to be checked before access to the resource is granted. This means that usage of access control is always linked to the usage of an authentication service. + +#### 10.1.2.3 Protection of confidentiality + +*A TMN should provide capabilities to ensure the confidentiality of stored and communicated data.* + +The security services to support the requirement are: **access control** for stored data and **data confidentiality** for communicated data. **Data confidentiality** may also be required for certain kinds of stored data such as passwords. + +The confidentiality service provides protection against unauthorized disclosure of exchanged data. The following kinds of confidentiality services are distinguished: + +- selective field confidentiality; +- connection confidentiality; +- data flow confidentiality. + +#### 10.1.2.4 Protection of data integrity + +*A TMN should be able to guarantee the integrity of stored and communicated data.* + +The security services to support the requirement are: **access control** and **data integrity** for stored data and **data integrity** for communicated data. + +The integrity service provides means to ensure the correctness of exchanged data, protecting against modification, deletion, creation (insertion) and replay of exchanged data. The following kinds of integrity services are distinguished: + +- selective field integrity; +- connection integrity without recovery; +- connection integrity with recovery. + +#### 10.1.2.5 Accountability + +*A TMN should provide the capability that an entity cannot deny the responsibility for any of its performed actions as well as their effects.* + +The requirement is supported by the **non-repudiation** service binding the individual (or entity) to the operation performed. The non-repudiation services provide means to prove that exchange of data actually took place. It comes in two forms: + +- non-repudiation: proof of origin; +- non-repudiation: proof of delivery. + +Another more general, and possibly weaker, realization of accountability is achieved by the appropriate combinations of the **authentication**, **access control** and **audit trail** services. + +#### 10.1.2.6 Activity logging, alarm reporting and audit + +These requirements cover the needs to store and analyze information about security-relevant activities within the TMN. In addition, alarm notifications should be generated on certain adjustable events. The appropriate services are **audit trail** and **alarm reporting**. Each of the requirements is discussed below in some detail. + +##### 10.1.2.6.1 Activity logging + +*A TMN should provide the capability of storing information about activities on the system with the possibility of tracing this information to individuals or entities.* + +A log is a repository for records: it is the OSI abstraction of logging resources in real open systems. Records contain the information that is logged. + +For the purpose of many management functions, it is necessary to be able to preserve information about events that have occurred or operations that have been performed or attempted by, or on, various resources. + +Furthermore, when such information is retrieved from a log, the manager should be able to determine whether any records were lost or whether the characteristics of the records stored in the log were modified at any time. + +###### 10.1.2.6.2 Security alarm reporting + +*A TMN should provide the capability to generate alarm notifications on selected events. The user should be able to define the selection criteria.* + +The security audit control function is a systems management function describing the notification for collection of security events. The security alarm notification defined by this systems management function provides information regarding the operational condition pertaining to security. + +###### 10.1.2.6.3 Security audit + +*A TMN should provide the capability to analyze logged data on security relevant events in order to check them for violations of the security policy.* + +An audit should be seen as an independent review and examination of system records and activities in order to test for adequacy of system controls, to ensure compliance with the established security policy and operational procedures and to detect breaches in security. The result of the Audit would identify changes in control, policy and procedures. + +Table 4 gives an overview of the relationship between Requirements and Security services. This clause only defines the security services which are covered by standard solutions; other possible services (e.g., detection of denial of service) are left out. + +**Table 4/M.3016.0 – Mapping of security requirements and security services** + +| Functional requirement | Security service | +|--------------------------------------------------|---------------------------------------------------------------------------------| +| Verification of identities | user authentication
peer entity authentication
data origin authentication | +| Controlled access and authorization | access control | +| Protection of confidentiality – stored data | access control
confidentiality | +| Protection of confidentiality – transferred data | confidentiality | +| Protection of data integrity – stored data | access control | +| Protection of data integrity – transferred data | integrity | +| Accountability | non-repudiation | +| Activity logging | audit trail | +| Security alarm reporting | security alarm | +| Security audit | audit trail | +| Protection of the DCN | packet inspection | + +NOTE – The following requirements are not the same type as those expressed before Table 4 and may not be seen as obvious candidates for standardization. Nevertheless, they should be taken into account during the design phase along with the implementation of the Core TMN requirements expressed above. + +###### 10.1.2.6.4 System integrity + +*It is essential that the software and hardware environment of the implemented security functions maintain the requested level of security.* + +This includes the correct configuration of operating systems and the elimination of system defects. + +These aspects do not form part of the functional security profile itself, but they have to be stated together with those specifications in order to guarantee the strength of the functions in the real-world environment. + +##### 10.1.2.6.5 Remarks on availability + +A requirement on availability does not have a single or a limited set of security services which are able to fulfill this requirement. All the security services listed here should form a coherent set which together is able to maintain availability. Security services alone, however, will never be able to ensure availability: this is also a matter of reliability of hardware and software (both from a design and from an implementation point of view). + +#### 10.1.2.7 Protection of the DCN + +*A TMN should provide protection of the DCN from customer and peer network traffic.* + +A TMN should provide isolation of DCN traffic from other types of traffic, especially in a packet-based DCN. + +## 10.2 Requirements on the management of security + +*A TMN should contain information models and management capabilities for the services used to secure the TMN.* + +Detailed requirements on security management state what management applications should be introduced and how they should be designed. This is done in order to provide the security manager + +with the proper tools to monitor and to control security services in an effective and correct way. Objectives for and targets of security management are presented at three different levels of a telecom system, which corresponds to the management of systems security, security services and security mechanisms, respectively. + +Operations and information related to the management of security services in TMN need special consideration from a security point of view. Secret encryption keys, authentication information and access control lists are examples where the required strength of protection may be higher than for network management. + +The management of Security should be consistent with the security management functions defined in ITU-T Rec. M.3400. + +*Recovery to a secure state of the system after a security breach should be supported.* + +Whenever a breach of security occurs, the TMN should be able to handle this attempt in a controlled manner, meaning that the attempt should not result in a severe degradation of the TMN in terms of availability. + +## **10.3 Architectural requirements** + +The most important requirements that have to be satisfied by the security measures taken to fit into the TMN framework are: + +- Measures should be based on the principles of the TMN functional model. +- Measures should conform to the object-oriented data and information model of TMN. +- Measures should be applicable to all TMN domains in the public and private sector. +- Solutions should be scaleable to fit small and large TMNs. +- Solutions should be compatible with the internal architecture of the TMN reference points considered. +- Solutions should address the concerns of all internal and external TMN users. +- Solutions should consider robustness aspects. +- Solutions should support reconfiguration through the addition or removal of users or applications. + +Conflicts are bound to appear between the security area and other functional areas. For example, integrity and confidentiality of charging data have to be balanced with requirements on throughput of the vast amount of information needed for toll-ticketing. A trustworthy set of security requirements needs to take the effects on characteristics of other functional areas into consideration. + +Further architectural requirements may arise when specific TMN scenarios are being analyzed. + +## **10.4 Security services and OSI layers** + +This clause describes which OSI layers are used to provide the security services and, therefore, shows how they can be provided for TMN in a meaningful way. + +It is assumed that if a layer provides a security service, that service is provided to the layer above the considered layer. The provision of services by layers laid out in ITU-T Rec. X.800 is used as a basis to limit the possibilities. + +### **10.4.1 User authentication** + +This service is dependent on interaction with the user. It is, therefore, outside the scope of the OSI model. + +### **10.4.2 Authentication (peer entity and data origin)** + +The following layers can provide this service (according to ITU-T Rec. X.800): + +- Network layer (corroboration of the identity of transport layer peers); +- Transport layer (corroboration of the identity of session layer peers); +- Application layer (corroboration of the identity of application processes); +- Outside OSI: in the application process itself. + +Considering that the requirement for the TMN will be to identify and authenticate managers and agents and the link of authentication with access control, recommended positions with respect to the OSI stack are the application layer and the application process. + +### **10.4.3 Access control** + +- *Management association access control* + +This service is usable at those levels at which an association exists; this will be at Application layer (access control for application processes) or in the application process itself. + +Association access control can be provided at the Network layer, e.g., using X.25 closed user group service. Furthermore, association access control can be provided at the Application layer or in the application process itself. + +- *Management notification access control* + +This service can be used in the Application layer or in the application process itself, since it is the application process itself which can discriminate between (application process) entities like managers and agents. + +- *Managed resource access control* + +This service can be used in the Application layer or in the application process itself, since it is the application process itself which can discriminate between (application process) entities like managers and agents. + +### **10.4.4 Security alarm, audit trail and recovery** + +These services are linked to other services and are therefore present in those layers where the other services are present. + +### **10.4.5 Integrity** + +- *Selective field integrity* + +This service can be used in the Application layer or in the application process itself, since it is the application process which can discriminate between fields. + +- *Connection integrity with recovery* + +Can be provided at the Transport layer, at the Application layer or in the application process. + +- *Connection integrity without recovery* + +Can be provided at the Network layer, the Transport layer, the Application layer or in the application process. + +### **10.4.6 Confidentiality** + +- *Selective field confidentiality* + +This service can be used in the Application layer or in the application process itself, since it is the application process which can discriminate between fields. + +- *Connection and connectionless confidentiality* + +Considering that end-to-end confidentiality is needed, which excludes the Physical layer and the Data link layer, confidentiality can be provided at the Network layer, the Transport layer, the Presentation layer, the Application layer or in the application process. + +- *Traffic flow confidentiality* + +This service can be provided in the Network, Transport, or Application layers, or in the application process. + +### 10.4.7 Non-repudiation + +- non-repudiation – proof of sending; +- non-repudiation – proof of delivery. + +This service can be used in the Presentation layer, the Application layer or in the application process itself. + +This is summarized in Table 5. + +**Table 5/M.3016.0 – Linking security services and OSI reference model** + +| Service | Layer | | | | | | | +|-------------------------------------------|-------|---|---|---|---|---|---| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| User authentication | – | – | – | – | – | – | + | +| Peer entity authentication | – | – | + | + | – | – | + | +| Data origin authentication | – | – | + | + | – | – | + | +| Management association access control | – | – | + | – | – | – | + | +| Management notification access control | – | – | – | – | – | – | + | +| Managed resource access control | – | – | – | – | – | – | + | +| Security alarm, audit trail and recovery | + | + | + | + | + | + | + | +| Selective field integrity | – | – | – | – | – | – | + | +| Connection integrity with recovery | – | – | – | + | – | – | + | +| Connection integrity without recovery | – | – | + | + | – | – | + | +| Selective field confidentiality | – | – | – | – | – | – | + | +| Connection/connectionless confidentiality | – | – | + | + | – | + | + | +| Traffic flow confidentiality | – | – | + | + | – | + | + | +| Non-repudiation – proof of sending | – | – | – | – | – | + | + | +| Non-repudiation – proof of delivery | – | – | – | – | – | + | + | + +## 10.5 Security management + +Security management comprises all activities to establish, maintain and terminate the security aspects of a system. + +Topics covered are: + +- management of security services; +- installation of security mechanisms; +- key management (management part); +- establishment of identities, keys, access control information, etc.; +- management of security audit trail and security alarms. + +# Appendix I + +## Functional classes and security subprofiles + +## I.1 Grouping of security measures + +Security measures can be grouped into "Functional Classes" (FC). The following definition does not include the strength of security measure: + +A functional class is a consistent set of security measures to meet requirements of varying functional levels. + +#### I.1.1 The use of FCs in the inter-domain case + +The security of a TMN should not be negatively affected as a result of inter-domain activities. The rules for domain interaction should be defined in an inter-domain security policy. These rules will define which security measures should be used in which case. To facilitate agreement between interacting domains, these security measures can be referred to as a particular functional class. + +#### I.1.2 The use of FCs in the intra-domain case + +In the intra-domain case, functional classes can facilitate the definition of security. FCs can also be used for the purpose of security assurance. To achieve this, the functional classes should be associated with a level of assurance claimed by the manufacturer of management products. This topic has strong relations with formal evaluation criteria. + +It may be possible that, for the purpose of inter-domain interaction, one operator could require the application of a particular FC for the intra-domain case of the other operator. A reason for this might be that not all threats can be efficiently dealt with at the interface between the two domains. Ensuring that a minimum internal security level exists for interacting TMNs could be a solution for this. A TMN security standard should not prescribe that FCs are required, but should enable the possibility to require certain FCs, by defining appropriate items for selection. + +## I.2 Functional classes + +Functional classes are used to define a concise group of security services aimed at meeting a certain security level. This clause works out a set of functional classes which serves as an example of how functional classes can be defined. Functional classes *for the X-interface* are proposed at three distinct security levels: + +- 1) minimal functional class: (FC 1); +- 2) basic functional class: (FC 2); +- 3) advanced functional class: (FC 3). + +For practical purposes, the number of FCs should not be too high. On the other hand, it should be possible to match the requirements of many different organizations. The functional classes may be changed in the following ways: + +- Functional classes defined only for the X-interface may also include the Q interfaces. +- Confidentiality is supposed to be an optional feature for all classes for two reasons: + - it is a less severe requirement; + - mandatory inclusion in a functional class may have legal implications for the usability of the class. + +Table I.1 provides an overview of the functional classes. + +**Table I.1/M.3016.0 – Functional classes of security services** + +| FC 1 | FC 2 | FC 3 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Emphasis on the integrity of stored managed resources | Emphasis on the integrity of stored managed resources and on integrity of transferred data | FC 2 plus accountability of management operations | +|
  • • Authentication (peer entity and user)
  • • Management association access control
  • • Managed resource access control
  • • Security alarm, audit and recovery
|
  • • Authentication (peer entity and user)
  • • Management association access control
  • • Managed resource access control
  • • Data origin authentication
  • • Selective field integrity
  • • Connection integrity
  • • Security alarm, audit and recovery
|
  • • Authentication (peer entity and user)
  • • Management association access control
  • • Managed resource access control
  • • Data origin authentication
  • • Selective field integrity
  • • Connection integrity
  • • Source non-repudiation
  • • Destination non-repudiation
  • • Security alarm, audit and recovery
| +| Optional:
  • • Connection integrity
  • • Connection confidentiality
| Optional:
  • • Connection confidentiality
  • • Selective field confidentiality
| Optional:
  • • Connection confidentiality
  • • Selective field confidentiality
| + +In addition, a distinction should be made between FCs applicable for the inter-domain case and FCs for the intra-domain case. The requirements will be different in both cases and, for that reason, also the security measures might be different. + +The next part gives an overview of the different cases so that one can find out which FCs are needed and which are relevant. + +#### Assumption + +For each domain, an authority exists that is responsible for the decision which security measures should be applied in the domain. + +Three cases are distinguished: + +- 1) FCs defined by a domain authority and applicable to the own domain (intra-domain); +- 2) FCs defined by a domain authority and applicable to the domain interactions (inter-domain). These FCs will be the result of an agreement between the authorities of the interacting domains; +- 3) FCs defined by a domain authority as requirements to the internal security of the other domain. + +In each case, the number of FCs for different security levels can be identified. + +The number of security levels is for further study. + +The set of security measures that form an FC is for further study. + +FCs in the different cases might be equal, thus reducing the total number of FCs. + +One could also consider a trade-off between the different cases, e.g., when the inter-domain security is at a high level, the requirements for internal security in the other domain might be low and vice versa. Another possibility might be that an FC represents a minimum set of security measures that can be extended with additional measures as is appropriate. + +## **I.3 Security profiles** + +Functional classes do not require the use of standardized security mechanisms; any mechanisms that fulfill the requirements can be applied. + +To enable interaction between security measures in different domains, the measures should conform to standards. A prescription of the use of particular standards that together provide a functional class is called a security profile. + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3016.1-200504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3016.1-200504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3016.1-200504-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3016.1-200504-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/M/T-REC-M.3016.1-200504-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..445a55b7c0927701f73edd0dea9727bf0d80e726 --- /dev/null +++ b/marked/M/T-REC-M.3016.1-200504-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53392787306505ae1cf77e3af986523e085938b233431928ff8b84f2a07749f5 +size 92185 diff --git a/marked/M/T-REC-M.3016.1-200504-I_PDF-E/raw.md b/marked/M/T-REC-M.3016.1-200504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c125ddc8888500a313bfe491dbc0858db3af1a70 --- /dev/null +++ b/marked/M/T-REC-M.3016.1-200504-I_PDF-E/raw.md @@ -0,0 +1,1446 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3016.1** + +(04/2005) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Security for the management plane: Security requirements** + +ITU-T Recommendation M.3016.1 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3016.1** + +# **Security for the management plane: Security requirements** + +## **Summary** + +This Recommendation identifies the security requirements for the management plane in telecommunication management. It focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the telecommunication infrastructure. + +## **Source** + +ITU-T Recommendation M.3016.1 was approved on 13 April 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | | Page | +|------|---------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 1.1 | Purpose ..... | 1 | +| 1.2 | Relationship with X.805 Security Architecture..... | 1 | +| 1.3 | Relationship with E.408 telecommunication networks security requirements ..... | 1 | +| 2 | References..... | 2 | +| 3 | Terms and definitions ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Security requirements ..... | 5 | +| 6.1 | Verification of identities..... | 5 | +| 6.2 | Controlled access and authorization ..... | 7 | +| 6.3 | Protection of confidentiality ..... | 11 | +| 6.4 | Protection of data integrity ..... | 12 | +| 6.5 | Accountability ..... | 13 | +| 6.6 | Security logging and audit..... | 13 | +| 6.7 | Security alarm reporting ..... | 14 | +| 6.8 | Protection of the DCN ..... | 14 | +| | Annex A – Mapping of security requirements, services and mechanisms ..... | 14 | +| | Appendix I – Additional security considerations..... | 20 | +| I.1 | Applicability to enterprise operations, administration, maintenance and provisioning..... | 20 | +| I.2 | Common object request broker architecture, simple network management protocol, extensible markup language, and simple object access protocol .... | 20 | +| I.3 | Lawfully authorized electronic surveillance ..... | 23 | +| I.4 | Physical security considerations..... | 24 | +| I.5 | Development process..... | 29 | +| | Appendix II – Framework and design guidelines ..... | 35 | +| II.1 | Framework and model ..... | 35 | +| II.2 | Design guidelines ..... | 37 | +| | Appendix III – Semantics of terms used in the M.3016.x series ..... | 38 | +| | BIBLIOGRAPHY ..... | 43 | + +# Introduction + +Telecommunications is a critical infrastructure for global communication and economy. Appropriate security for the management functions controlling this infrastructure is essential. Many standards for Telecommunication network management security exist. However, compliance is low and implementations are inconsistent across the various telecommunication equipment and software components. This Recommendation identifies the security requirements to allow vendors, agencies, and service providers to implement a secure telecommunication management infrastructure. Although the present set of requirements represents the current understanding of the state of the art, technologies will advance and conditions change. To be successful, this Recommendation must evolve as conditions warrant. This Recommendation is intended as a foundation. Service providers may include additional requirements to meet their specific needs over and above those dealt within this Recommendation. + +This Recommendation is part of the M.3016.x series of ITU-T Recommendations intended to provide guidance and recommendations for securing the management plane of evolving networks: + +- ITU-T Rec. M.3016.0 – Security for the management plane: Overview. +- ITU-T Rec. M.3016.1 – Security for the management plane: Security requirements. +- ITU-T Rec. M.3016.2 – Security for the management plane: Security services. +- ITU-T Rec. M.3016.3 – Security for the management plane: Security mechanism. +- ITU-T Rec. M.3016.4 – Security for the management plane: Profile proforma. + +## ITU-T Recommendation M.3016.1 + +# Security for the management plane: Security requirements + +# 1 Scope + +ITU-T Recs M.3016.1-3 specify a set of requirements, services and mechanisms for the appropriate security of the management functions necessary to support the telecommunication infrastructure. Because different administrations and organizations require varying levels of security support, ITU-T Recs M.3016.1-3 do not specify whether a requirement, service/or mechanism is mandatory or optional. + +This Recommendation identifies the security requirements for the management plane in Telecommunication management. It focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the Telecommunication infrastructure. + +This Recommendation is generic in nature and does not identify or address the requirements for a specific Telecommunications Management Network (TMN) interface. + +The proforma defined in ITU-T Rec. M.3016.4 is provided to assist organizations, administrations and other national/international organizations, specify the mandatory and optional support of the requirements as well as value ranges, values, etc. to help implement their security policies. + +## 1.1 Purpose + +ITU-T Rec. M.3016.0 identifies a number of objectives, for securing the management network and threats that introduce risks with regard to meeting these objectives. This Recommendation derives the requirements from the objectives against threats and identifies the security services that counter them. In defining the services, mechanisms are used based on certain algorithms. The other Recommendations in this series build on the structure set forth in the ITU-T Rec. M.3016.0 overview. It augments the various steps required to secure the management plane. + +## 1.2 Relationship with X.805 security architecture + +ITU-T Rec. X.805 defines security architecture for providing end-to-end network security. The X.805 security architecture logically divides a complex set of end-to-end network security-related features into three separate architectural components, namely Security Dimensions, Security Layers and Security Planes (see Figure 2/X.805). A Security Dimension is a set of security measures designed to address a particular aspect of the network security. ITU-T Rec. X.805 defines three Security Layers: the Infrastructure Security Layer, the Services Security Layer, and the Applications Security Layer, which build on one another to provide network-based solutions. A Security Plane is a certain type of network activity protected by Security Dimensions. Three Security Planes are identified in ITU-T Rec. X.805, namely, Management Plane, Control Plane, and End-User Plane. To provide a complete solution, security measures (e.g., access control, authentication) should be applied to each type of network activity (i.e., management plane activity, control plane activity, and end user plane activity) for the network infrastructure, network services, and network applications. This Recommendation focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the network infrastructure. + +## 1.3 Relationship with E.408 telecommunication networks security requirements + +ITU-T Rec. E.408 provides an overview of security requirements and a framework that identifies security threats to telecommunication networks in general (both fixed and mobile; both voice and data) and gives guidance for planning countermeasures that can be taken to mitigate the risks + +arising from the threats. It is generic in nature and does not identify or address requirements for specific networks. The M.3016.x series identifies the security requirements, services, and mechanisms for the telecommunication network, i.e., the management plane in general in telecommunication management. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation + +- ITU-T Recommendation E.408 (2004), *Telecommunication networks security requirements*. +- ITU-T Recommendation G.8080/Y.1304 (2001), *Architecture for the automatically switched optical network (ASON)*, plus Amendment 2 (2005). +- ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- ITU-T Recommendation M.3013 (2000), *Considerations for a telecommunications management network*. +- ITU-T Recommendation M.3016.0 (2005), *Security for the management plane: Overview*. +- ITU-T Recommendation M.3016.2 (2005), *Security for the management plane: Security services*. +- ITU-T Recommendation M.3016.3 (2005), *Security for the management plane: Security mechanism*. +- ITU-T Recommendation M.3016.4 (2005), *Security for the management plane: Profile proforma*. +- ITU-T Recommendation X.509 (2000), *Information Technology – Open Systems Interconnection: The Directory: Public-key and attribute certificate frameworks*, plus Technical Cor.1 (2001), Technical Cor.2 (2002) and Technical Cor.3 (2003). +- ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*, plus Amendment 1 (1996), *Layer Two Security Service and Mechanisms for LANs*. +- ITU-T Recommendation X.805 (2003), *Security architecture for systems providing end-to-end communications*. +- IETF RFC 1750 (1994), *Randomness Recommendations for Security*. + +# 3 Terms and definitions + +This Recommendation uses the following terms from ITU-T Rec. G.8080/Y.1304: + +- Control Plane; +- Management Plane; +- Transport Plane. + +This Recommendation uses the following terms from ITU-T Rec. M.3010: + +- Management System; +- Network Element. + +This Recommendation uses the following term from ITU-T Rec. M.3013: + +- Element Management System. + +This Recommendation uses the following term from ITU-T Rec. X.509: + +- Strong Authentication. + +This Recommendation uses the following terms from ITU-T Rec. X.800: + +- Access Control; +- Authentication. + +This Recommendation defines the following term: + +**3.1 critical security administration actions;** which include but are not limited to: + +- a) Defining and assigning user privileges; +- b) Adding and deleting user IDs; +- c) Disabling the use of specific user IDs as login IDs; +- d) Initializing and resetting login passwords; +- e) Initializing and changing cryptographic keys; +- f) Setting the system's aging threshold for login passwords; +- g) Setting the system's limit on the number of failed logins for each login ID; +- h) Removing a lockout, or changing the system's lockout timer value; +- i) Setting the system's inactivity timer value; +- j) Setting system security logging and alarm configuration; +- k) Managing the security logging processes; +- l) Upgrading security software; +- m) Terminating any user or system session. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|--------|----------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| ACS | Access Control Server | +| ALE | Annualized Loss Expectancy | +| ANSI | American National Standards Institute | +| CO | Central Office | +| CORBA | Common Object Request Broker Architecture | +| CSI | Common Secure Interoperability | +| DoS | Denial of Service | +| EMS | Element Management System | +| FTP | File Transfer Protocol | +| HAZMAT | Hazardous Materials | + +| | | +|---------|------------------------------------------------------------------------------------------| +| HTTP | HyperText Transfer Protocol | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| IPsec | Internet Protocol Security | +| ISO/IEC | International Organization for Standardization/International Electrotechnical Commission | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| LAES | Lawfully Authorized Electronic Surveillance | +| MS | Management System; any EMS, NMS, or OSS 1 | +| NE | Network Element | +| NE/MS | NE or MS | +| NMS | Network Management System | +| NTP | Network Time Protocol | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OASIS | Organization for the Advancement of Structured Information Standards | +| OEM | Original Equipment Manufacturer | +| ORB | Object Request Broker | +| OS | Operating System | +| OSS | Operations Support System | +| RFC | Request for Comments | +| SAML | Security Assertion Markup Language | +| SNMP | Simple Network Management Protocol | +| SOAP | Simple Object Access Protocol | +| SSH | Secure Shell | +| SSL | Secure Socket Layer | +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security | +| TMN | Telecommunications Management Network | +| XML | Extensible Markup Language | + +# 5 Conventions + +In ITU-T Recs M.3016.1-3, a descriptor is used to identify the different requirements, services and mechanisms. The descriptor consists of one of the following three-letter labels followed by a number: + +- REQ for requirement; + +--- + +1 OSSs generally can be used in the same context as MSs on any layer of the telecommunication management network hierarchy. + +- SER for service; +- MEC for mechanism. + +# 6 Security requirements + +This clause contains the security requirements for operations, administration, maintenance and provisioning (OAM&P) and operations support system (OSS) of the **Management Plane**. + +Figure 1/M.3016.0 describes the relationships between Security objectives, Threats, Risks, Security requirements, and Services. It describes the process how to derive "Security requirements" from "Threats" and "Security objectives" which in turn will be realized by a set of security services. These "Services", which counteract threats, will make use of "Mechanisms" which themselves make use of "Security algorithms". Table 1 (which is Table 4/M.3106.0) gives the relationship between Security requirements and Security services. The security requirements described in this clause are organized, following Table 1, as follow: + +- Verification of identities; +- Controlled access and authorization; +- Protection of confidentiality; +- Protection of data integrity; +- Accountability; +- Security logging and audit; +- Security alarm reporting. + +NOTE – Recovery from security breach is an area for further study. + +**Table 1/M.3016.1 – Mapping of security requirements and security services +(Table 4/M.3016.0)** + +| Functional requirement | Security service | +|--------------------------------------------------|---------------------------------------------------------------------------------| +| Verification of identities | User authentication
Peer entity authentication
Data origin authentication | +| Controlled access and authorization | Access control | +| Protection of confidentiality – stored data | Access control
Confidentiality | +| Protection of confidentiality – transferred data | Confidentiality | +| Protection of data integrity – stored data | Access control | +| Protection of data integrity – transferred data | Integrity | +| Accountability | Non-repudiation | +| Activity logging | Audit trail | +| Security alarm reporting | Security alarm | +| Security audit | Audit trail | + +## 6.1 Verification of identities + +**Authentication** has two purposes in securing the **Management Plane**: + +- 1) it ensures the identity of the communicating parties, providing a basis for setting up private communications with full data integrity and confidentiality between two systems; and + +- 2) it provides a basic mechanism for logging into a management system and/or auditing the management activities on any system. + +### 6.1.1 User Authentication, Passwords, and User IDs + +User **Authentication** concerns the **Authentication** of clients involved in the management of the network. In this case, **Authentication** proves the identity of the legitimate user and prevents masquerading attacks by illegitimate users. With proper **Authentication**, it is possible to track activities and restrict users to pre-authorized activities or roles as discussed in 6.3. + +The minimum requirements for **Authentication** are the use of a user ID and static **Complex Password**. Other mechanisms may be used as long as the administrators of the NE/MS are confident that the security level is at least as strong as that provided by a user ID and static **Complex Password**. Other mechanisms that may be considered include: + +- A user ID and **Two-Factor Authentication** using a one-time password generator;2 and +- **Two-Factor Authentication** using a smart-card with credentials stored on it in a protected manner. + +**REQ 1:** For NE/MS logging in, logging, and auditing, strong authentication should be supported. + +REQ 1 presents the security requirement. Description of general authentication mechanism is given in ITU-T Rec. M.3016.3. It is expected that **Authentication** techniques and single sign-on technologies will continue to improve. + +In secure single sign-on, the protocol still challenges the entity(s) for credentials; however, a user may not have to enter the credentials because they are securely cached in some way (e.g., Kerberos). + +The following requirements help maintain password complexity and are useful for auditing and logging. + +**REQ 2:** Each NE/MS should enforce **Authentication** according to organizational policy. + +**REQ 3:** Each NE/MS should support the Minimum complexity rules for **Authentication** according to the organizational policy. + +**REQ 4:** The NE/MS should prevent another user from changing a logged-on user's password without their knowledge. + +**REQ 5:** Each NE/MS should automatically ensure that each new login password differs from the previous password. The degree of difference should be configurable according to organizational policy. + +Because passwords are typically stored via one-way encryption, the entry of the old password is also required to allow the NE/MS to determine the degree of difference between the old and new passwords. + +**REQ 6:** Each NE/MS should support prevention of password reuse. Password use prevention parameters should be configurable according to organizational policy. + +**REQ 7:** Each user ID should have its own settable login password. + +**REQ 8:** Passwords should be user changeable at the user's discretion, following a minimum interval since the last change. The minimum interval should be configurable according to the organizational policy and set by the **System Security Administrator**. + +--- + +2 This clause does not discuss dynamic passwords as those are considered to be outside of the scope of this Recommendation. + +**REQ 9:** Each NE/MS should support multi-level password control. Some users can be locked out (e.g., due to password aging or login failure) while some users cannot be. + +### 6.1.2 Authentication defaults + +The proper use of default passwords has been discussed at length in security literature. Historically, default passwords ranged from hard coded in the program to a default associated with each software release or upgrade. The following are **Authentication** default requirements. + +**REQ 10:** One of the following should apply: + +- The configuration software should create a unique initialization password for each application in the new release or upgrade3 of the software. +- If a default password is used, the system should require the replacement of the default password with a unique password before the device goes into service. +- If a device is delivered without a password or a null password, a unique password should be assigned during the installation process before the device goes into service. + +**REQ 11:** The system age threshold for login passwords should be configurable if the functionality is also built into the application. At the expiration of the age threshold, the login password for an affected application should be reset to an original default state defined in REQ 10. All password change privileges should be revoked for all users except for the user role, which has the highest level of security authority for a system or application instance. + +**REQ 12:** The system inactivity timer value should be configurable if the functionality is also built into the application. When the system inactivity timer is enabled, an access to the system for a given user ID should be prevented and login process for this user should be disabled. + +**REQ 13:** The system limit on consecutive failed logins for a given user ID should be configurable if the functionality is also built into the application. When the system limit on consecutive failed logins for a given user ID is reached, the system inactivity timer defined in REQ 12 shall be invoked. + +## 6.2 Controlled access and authorization + +Each NE/MS must support the concept of "least privilege" (i.e., a person will have a role and will have authorization to view data, modify data, or initiate **Management Actions** only for those functions allowed by that role). This clause defines basic requirements for implementing "least privilege" through good system security administration. + +### 6.2.1 Security administration + +Each NE/MS must ensure that only authorized users are allowed to manage system security resources. All administrative actions are linked to user roles, and those user roles are assigned to specific individuals. Though only a few types of user roles are discussed, many other types of user roles with varying degrees of privileges may exist, especially with respect to critical security **Management Actions**. The goal is to ensure that only authorized, privileged users can manage critical security resources. + +**REQ 14:** Each NE/MS should have support for multiple user-defined types of user roles, and **Management Actions** are assignable to each user role. + +--- + +3 This is similar to the practice in which each commercially purchased compact disk carries a unique enabling password. + +User roles might result in a hierarchy of roles such that each user role has different or fewer tasks assigned such that it has less authority than the more privileged user role. An example of such a hierarchy is one which a user role has the ability to perform all **Management Actions**, like a computer 'super-user'. Another user role supports only read-only access to support monitoring of the devices, such as an operator. + +**REQ 15:** Each NE/MS should support a default user type, which has minimal or restrictive **Management Actions**. + +**REQ 16:** Each NE/MS should support the following **Critical Security Administration Actions**, but is not limited to: + +- Defining and assigning user and group privileges. +- Maintaining a record of all requests for login IDs to the system. +- Adding and deleting user IDs. +- Disabling and enabling the use of specific user IDs as login IDs. +- Initializing and resetting login passwords. +- Initializing and changing cryptographic keys. +- Setting the system's aging threshold for login passwords. +- Setting the system's limit on the number of failed logins for each login ID. +- Removing a lockout or change the system's lockout timer value. +- Setting the system's inactivity timer value. +- Setting system security logging and alarm configuration. +- Monitoring all system security logs. +- Managing system security logging processes. +- Upgrading security software. +- Terminating any user or system session. +- Delegating security authorizations to specific persons in other roles. +- Setting password complexity rules. + +**REQ 17:** Each NE/MS should support the following application security **Management Actions**, but is not limited to: + +- Defining and assigning new user and group privileges at the application level. +- Maintaining a record of all requests for login IDs to the application. +- Adding and deleting users at the application level. +- Monitoring all application security logs. +- Configuring application security logging and alarms. +- Managing application security logging processes. +- Terminating user application session. + +### 6.2.2 NE/MS use and operation + +The requirements in this clause apply to both remote and console access to a NE/MS. These mandatory requirements represent a baseline for NE/MS that actually store user IDs and passwords. Many NE/MS reference a centralized ACS to store user IDs and passwords. The mandatory requirements expressed throughout this Recommendation apply to a NE/MS if it holds user IDs and passwords and the user IDs and passwords stored on the ACS. + +**REQ 18:** NE/MS should synchronize time in an authenticated manner (e.g., NTP Version 3). + +- REQ 19:** For an NE/MS, each **Management Action** should be associated with a single authorized SESSION. +- REQ 20:** Each SESSION should be established via proper **Authentication** as detailed in requirement REQ 1. +- REQ 21:** Communications between a NE/MS and an ACS for the purposes of conveying **Authentication** credentials should occur over a **Trusted Path**. +- REQ 22:** NE/MS should use **Access Control** and partitions to allow, deny, or otherwise control a user, user group, or remote system's access to the NE/MS and should provide functionality restricting users to the data, transactions, and equipment necessary to fulfill their roles. Access permissions should include, and not be limited to, read-only and read-write. + +### 6.2.3 Login process + +- REQ 23:** The NE/MS should support the ability to assign to every individual a unique user ID to login to an application or host computer system. +- REQ 24:** NE/MS should have the capability, when necessary, to automatically force the user to change their password on the first access after the account has been established and on the first access after the password has been reset. + +NOTE – The following requirement (REQ 25) demands that a distinction be made as it pertains to the management of a Network Element (NE) vs a Management System (MS). Management of Network Elements requires the monitoring of a device through several mechanisms, perhaps simultaneously, while making configuration changes. In the case of an MS, this is not necessary. + +The intent of this requirement is to manage users capability of consuming all available resources of an NE/MS. Operations staffs should adjust the NE default as needed for individual situations, and should monitor and investigate attempts to exceed these limits, as they may indicate an operational deficiency or an attempt at mischievous activities. + +- REQ 25:** NE/MS should prevent, control, or limit the simultaneous active usage of the same user ID, when appropriate. The number of simultaneous active sessions should be configurable on a user ID basis. +- REQ 26:** The NE/MS application should note require **Superuser** access privileges in order to work properly. +- REQ 27:** NE/MS should have the capability of displaying to the user, when appropriate, during the logon process, the time and date of that user's last successful **Authentication**. +- REQ 28:** A customizable proprietary information statement and no trespassing warning should be displayed on the initial entry screen before any logical access is allowed. Equipment should support a minimum length of 1600 characters. A default message should be provided. + +The following is an example of a warning banner. + +``` +WARNING! This computer system and network is +PRIVATE and PROPRIETARY and may only be accessed by +authorized users. Unauthorized use of this computer +system or network is strictly prohibited and may be +subject to criminal prosecution, employee +discipline up to and including discharge, or the +termination of vendor/service contracts. The owner, +or its agents, may monitor any activity or +communication on the computer system or network. +The owner, or its agents, may retrieve any +``` + +information stored within the computer system or network. By accessing and using this computer system or network, you are consenting to such monitoring and information retrieval for law enforcement and other purposes. Users should have no expectation of privacy as to any communication on or information stored within the computer system or network, including information stored locally or remotely on a hard drive or other media in use with this computer system or network. + +It is recommended that each entity develop an appropriate warning banner. + +**REQ 29:** Any failed login attempt should report to the user only that the login process has failed or is invalid. Information such as "invalid user ID" or "invalid password" should not be reported. + +**REQ 30:** NE/MS should **Lockout** a user account from logging in after a configurable threshold number of login failures has been reached. The **Lockout** should include the console interface. The **Lockout** should NOT include the original default account that supports all the management actions. + +**REQ 31:** NE/MS should NOT have a mechanism for bypassing the login **Authentication** and logging in processes. + +**REQ 32:** No NE/MS should ever display a plaintext credential, such as password, in any media, including displays on terminal screens, printouts, and storing in log records. + +**REQ 33:** NE/MS should enforce password aging with a configurable threshold. + +A common and acceptable implementation of REQ 33 is for the system to immediately require the user to set a new password after authenticating the user with the old password. Alternatively, the system may require an administrator to properly change the password. If an account has not been used for a period of time, it will be considered dormant. + +**REQ 34:** If a login password has surpassed the age limit for that system, then the NE/MS should **Lockout** the login for that user ID until the password is properly changed. + +**REQ 35:** If an account has been dormant for a configurable threshold period of time, each NE/MS should generate an alert. + +**REQ 36:** If an account has been dormant for a configurable threshold period of time, the NE/MS should disable the account after generating a Disable alert. The **DISABLE** process should NOT include the **System Administrator** account, the **System Security Administrator** account, and the **Superuser** account. + +**REQ 37:** To re-enable a **Disabled** login ID, a properly logged in administrator, with the assigned Critical Security Administration Action to initialize and reset login passwords, is required. + +The options to re-enable login IDs can be configured as a system-wide parameter at the role level. + +**REQ 38:** To reset a **LOCKED OUT** login ID and to remove the **Lockout** condition, a properly logged in administrator with the assigned Critical Security Administration Action to remove a lockout or change the system's Lockout timer value is required. + +The options to remove a **Lockout** from login IDs can be configured as a system-wide parameter at the role level. + +### 6.2.4 Logout process + +**REQ 39:** Each properly logged-in **Session** should be logged out by the user or by system inactivity. + +**REQ 40:** NE/MS should log out a properly logged-in **Session** when the time, since the last activity for that **Session**, exceeds the system's configurable inactivity timer value. + +### 6.2.5 Applications + +**REQ 41:** A user's role type should remain unchanged during the execution of and exit from any NE/MS application. + +The user should not be able to use a control sequence mechanism, for example, shell escape to a **Superuser** mode. Or, if the application fails, it must not leave the user in a different role with more privileges. The user must re-authenticate (relogin) in order to assume a different role. + +## 6.3 Protection of confidentiality + +This clause specifies requirements for cryptographic algorithms and key management to help ensure system and network security. Symmetric algorithms are normally used for both confidentiality and integrity services. The keys for symmetric algorithms should normally be exchanged in a process tightly bound to authentication. Asymmetric algorithms may also be used in support of authentication and key exchange services. The methods used to generate, store, distribute, destroy, and revoke these keys are of paramount importance. In addition, factors such as key length, key selection, and algorithm selection have a direct bearing on the security strength of a specific cryptosystem. + +**Protected Authentication** and data confidentiality are based on a cryptographic foundation. Cryptography uses special algorithms that are standards-based and publicly available, thereby allowing for widespread scrutiny and ease of implementation. Cryptographic "strength" is based on the cryptographic algorithm used, as well as the key size used (i.e., strength refers to the amount of time required to reverse engineer (i.e., find or guess) the key value(s) being used with a specific algorithm). + +Security protocols (e.g., IPsec, SSL, SSH) typically provide **Authentication**, integrity, and confidentiality. Security extensions to other protocols such as Simple Network Management Protocol Version 3 (SNMPv3)4, Common Object Request Broker Architecture (CORBA), Border Gateway Protocol, and Open Shortest Path First are designed to provide **Authentication** and integrity. **Protected Authentication** and integrity are essential between NE/MS and, where deemed appropriate, confidentiality is also required. + +### 6.3.1 Symmetric encryption algorithms + +Symmetric or secret key encryption refers to a cryptographic system where enciphering and deciphering keys are the same. Symmetric cryptosystems require that initial arrangements be made for the individuals to share a unique secret key (e.g., the encryption key). The key must be distributed to the individuals via a secure means, or internally generated (e.g., based on a shared secret root key) because knowledge of the enciphering key implies knowledge of the deciphering key and vice versa. + +**REQ 42:** For all symmetric encryption applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. + +--- + +4 SNMPv3 may also provide confidentiality. + +### 6.3.2 Asymmetric encryption algorithms + +An asymmetric encryption system is one in which the enciphering and deciphering keys are related but different. One is made public, whereas the other is kept secret. The public key is different from the private key, and no feasible way is known for deriving the private key from the public key. Public keys are distributed widely; however, the private key is always kept secret. The use of asymmetric encryption is usually limited to the encryption of symmetric keys for key exchange and the signing of message digests for digital signatures. In key exchange, the recipient's public key is used and, in the signing of message digests, the signer's private key is used. + +**REQ 43:** For all asymmetric encryption applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. + +**REQ 44:** For all key exchange applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. + +### 6.3.3 Cryptographic key management + +Properly managing cryptographic key material is difficult and often complex because key management involves expiration, secure exchange, and secure publication, in addition to key generation. IETF RFC 1750, *Randomness Recommendations for Security*, provides additional guidance. + +### 6.3.4 Communications + +Secure communications are the foundation for securing the **Management Plane** in a modern network. Annex A discusses architectures and protocols for implementing secure **Management Communications**. The mandatory requirements defined in this clause apply to all interfaces of a TMN as described in the ITU-T Rec. M.3010, *Principles for a Telecommunications Management Network*. + +**REQ 45:** For each physical or logical interface that carries any **Management Traffic** in an NE/MS, the NE/MS should be configurable to secure **Management Traffic** with **Strong Authentication** and cryptographic protection in order to provide confidentiality, integrity and replay protection. + +**REQ 46:** Any password transmitted in clear text should only be transmitted across a **Trusted Path** unless a one-time password mechanism is used. If one-time passwords are used, then they may be sent in clear text as long as there is no intermediate host. + +## 6.4 Protection of data integrity + +### 6.4.1 Data integrity algorithms + +Keyed message digest algorithms combined with hashing functions could be used to ensure data integrity for arbitrary length messages. + +**REQ 47:** For all symmetric secure data integrity applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. + +**REQ 48:** For all asymmetric secure data integrity applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. + +### 6.4.2 NE/MS development and delivery + +Security of an NE/MS is dependent on the complete lifecycle process. Security is an issue during conceptual design and remains an issue through detailed design, development, deployment, and decommissioning of a product. Appropriate controls and testing during the complete lifecycle process are critical to providing acceptable levels of security. Clauses I.5.2 and I.5.3, discuss additional lifecycle considerations. + +**REQ 49:** All software delivered to a service provider or other customer should include, when appropriate, cryptographic **Authentication** and integrity protection mechanisms such as digital signatures or symmetric message **Authentication** as specified in ITU-T M.3016.3. + +**REQ 50:** All NE/MS receiving software should be capable of interpreting the cryptographic **Authentication** and integrity protection mechanisms and verifying the source and integrity of the software, when appropriate. + +**REQ 51:** All software updates, including patches, should be transmitted to the receiving NE/MS over a **Trusted Path**. + +NE/MS should be able to electronically determine their current software and hardware revision levels and validate appropriate software/firmware configurations. + +## 6.5 Accountability + +The objective of accountability is to ensure that any entity should be responsible for any actions it initiates. + +**REQ 52:** All NE/MS should provide the capability that an entity cannot deny the responsibility of any of its performed actions as well as their effects. + +Also see REQ 49 and REQ 50 for accountability requirements related to NE/MS development and delivery. + +## 6.6 Security logging and audit + +It is important that each NE/MS provide adequate capabilities to allow investigation, audit, real-time detection, analysis, and protection activities, so that proper remedial actions can be taken. This clause considers security audit logs; however, the specific details of the content and format of the security audit logs are beyond the scope of this Recommendation. + +Note that investigation and forensic analysis activities may include investigation of non-security related OAM&P messages as well as the information stored in the security audit logs described in this clause. Logging of non-security related OAM&P messages, sometimes referred to as "recent change" messages, is required for any actions that are auditable. + +**REQ 53:** NE/MS should be able to log any action that changes the security attributes and services, access controls, configuration parameters of the devices. + +**REQ 54:** NE/MS should provide the capability to configure those **Critical Security Administration Actions** that are to be included in the security log. + +**REQ 55:** The NE/MS should be able to log each login attempt and its result; each logout or Session termination (whether remote or console) and each login attempt and its result that caused invocation of the system inactivity timer defined in REQ 12. + +It is recommended that audit log entries be sent to an unalterable audit server after being sequence labeled and cryptographically authenticated (signed) by the NE/MS. + +**REQ 56:** NE/MS should be capable of remote logging over a **Trusted Path**. + +**REQ 57:** Each log entry should contain the following information: + +- A description of the action or the actual action that is being logged; +- The identity and security level of the user or process that initiated the action; +- The date and time the action occurred; +- Network source and destination information, if applicable (e.g., when logging in); +- An indication of the success or failure of the activity. + +## 6.7 Security alarm reporting + +Certain events need to be reported as security alarms, e.g., see REQ 35. However, it is beyond the scope of this Recommendation to identify the specific events that need to be reported. + +**REQ 58:** All NE/MS should provide the capability to generate alarm notifications on selected events. + +**REQ 59:** All NE/MS should provide the capability to allow the user to define the selection criteria for events that generate alarm notifications. + +## 6.8 Protection of the DCN + +To protect the management infrastructure, and the DCN in general, it is useful for the network operator to inspect and take action on certain traffic received from or destined to outside the DCN (e.g., from peer networks and customers). For example, packets with source IP addresses that match the address space of the DCN should not be permitted into the DCN from outside networks. + +**REQ 60:** All NE/MS with packet-based connectivity should prevent traffic that does not meet the DCN security policy. + +# Annex A + +## Mapping of security requirements, services and mechanisms + +This annex provides the mapping from the security requirements to the security services defined in ITU-T Rec. M.3016.2 and the security mechanisms defined in ITU-T Rec. M.3016.3. + +| M.3016.1 security requirements | M.3016.2 security services | M.3016.3 security mechanisms | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------| +| REQ 1: For NE/MS logging in, logging, and auditing, strong authentication should be supported. | SER 1, SER 2, SER 3, SER 8 | MEC 1-MEC 13 | +| REQ 2: Each NE/MS should enforce Authentication according to organizational policy. | SER 1, SER 2, SER 3 | MEC 1-MEC 6 | +| REQ 3: Each NE/MS should support the Minimum complexity rules for Authentication according to the organizational policy. | SER 1, SER 2, SER 3 | MEC 1-MEC 6 | +| REQ 4: The NE/MS should prevent another user from changing a logged-on user's password without their knowledge. | SER 8 | MEC 7-MEC 11 | +| REQ 5: Each NE/MS should automatically ensure that each new login password differs from the previous password. The degree of difference should be configurable according to organizational policy. | SER 1 | MEC 7-MEC 11 | +| REQ 6: Each NE/MS should support prevention of password reuse. Password use prevention parameters should be configurable according to organizational policy. | SER 1 | MEC 7-MEC 11 | +| REQ 7: Each user ID should have its own settable login password. | SER 1 | MEC 7-MEC 11 | + +| M.3016.1 security requirements | M.3016.2 security services | M.3016.3 security mechanisms | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------| +| REQ 8: Passwords should be user changeable at the user's discretion, following a minimum interval since the last change. The minimum interval should be configurable according to the organizational policy and set by the System Security Administrator . | SER 1 | MEC 7-MEC 11 | +| REQ 9: Each NE/MS should support multi-level password control. Some users can be locked out (e.g., due to password aging or login failure) while some users cannot be. | SER 1, SER 2, SER 3, SER 4 | MEC 20-MEC 23 | +| REQ 10: One of the following should apply:
  • The configuration software should create a unique initialization password for each application in the new release or upgrade of the software.
  • If a default password is used, the system should require the replacement of the default password with a unique password before the device goes into service.
  • If a device is delivered without a password or a null password, a unique password should be assigned during the installation process before the device goes into service.
| SER 1, SER 2, SER 3 | MEC 7-MEC 11 | +| REQ 11: The system age threshold for login passwords should be configurable if the functionality is also built into the application. At the expiration of the age threshold, the login password for an affected application should be reset to an original default state defined in REQ 10. All password change privileges should be revoked for all users except for the user role, which has the highest level of security authority for a system or application instance. | SER 4 | MEC 7-MEC 11 | +| REQ 12: The system inactivity timer value should be configurable if the functionality is also built into the application. When the system inactivity timer is enabled, an access to the system for a given user ID should be prevented and login process for this user should be disabled. | SER 4 | MEC 7-MEC 11 | +| REQ 13: The system limit on consecutive failed logins for a given user ID should be configurable if the functionality is also built into the application. When the system limit on consecutive failed logins for a given user ID is reached, the system inactivity timer defined in REQ 12 should be invoked. | SER 4 | MEC 7-MEC 11 | +| REQ 14: Each NE/MS should have support for multiple user-defined types of user roles, and Management Actions are assignable to each user role. | SER 4 | MEC 20-MEC 23 | +| REQ 15: Each NE/MS should support a default user type, which has minimal or restrictive Management Actions . | SER 4 | MEC 20-MEC 23 | + +| M.3016.1 security requirements | M.3016.2 security services | M.3016.3 security mechanisms | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|------------------------------| +| REQ 16: Each NE/MS should support the following Critical Security Administration Actions , but is not limited to:
  • • Define and assign user and group privileges.
  • • Maintain a record of all requests for login IDs to the system.
  • • Add and delete user IDs.
  • • Disable and enable the use of specific user IDs as login IDs.
  • • Initialize and reset login passwords.
  • • Initialize and change cryptographic keys.
  • • Set the system's aging threshold for login passwords.
  • • Set the system's limit on the number of failed logins for each login ID.
  • • Remove a lockout or change the system's lockout timer value.
  • • Set the system's inactivity timer value.
  • • Set system security logging and alarm configuration.
  • • Monitor all system security logs.
  • • Manage system security logging processes.
  • • Upgrade security software.
  • • Terminate any user or system session.
  • • Delegate security authorizations to specific persons in other roles.
  • • Set password complexity rules.
| SER 4, SER 8 | MEC 20-MEC 23 | +| REQ 17: Each NE/MS should support the following application security Management Actions , but is not limited to:
  • • Define and assign new user and group privileges at the application level.
  • • Maintain a record of all requests for login IDs to the application.
  • • Add and delete users at the application level.
  • • Monitor all application security logs.
  • • Configure application security logging and alarms.
  • • Manage application security logging processes.
  • • Terminate user application session.
| SER 4, SER 8 | MEC 20-MEC 23 | +| REQ 18: NE/MS should synchronize time in an authenticated manner (e.g., NTP Version 3). | SER 8 | N/A | +| REQ 19: For an NE/MS, each Management Action should be associated with a single authorized SESSION . | SER 4 | MEC 20-MEC 23 | +| REQ 20: Each SESSION should be established via proper Authentication as detailed in requirement REQ 1. | SER 1, SER 2, SER 3 | MEC 1-MEC 12 | +| REQ 21: Communications between a NE/MS and an ACS for the purposes of conveying Authentication credentials should occur over a Trusted Path . | SER 5, SER 6 | MEC 19 | + +| M.3016.1 security requirements | M.3016.2 security services | M.3016.3 security mechanisms | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------------------------| +| REQ 22: NE/MS should use Access Control and partitions to allow, deny, or otherwise control a user, user group, or remote system's access to the NE/MS, and should provide functionality restricting users to the data, transactions, and equipment necessary to fulfill their roles. Access permissions should include, and not be limited to, read-only and read-write. | SER 4 | MEC 20-MEC 23 | +| REQ 23: The NE/MS should support the ability to assign to every individual a unique user ID to log in to an application or host computer system. | SER 1, SER 2, SER 3 | MEC 7-MEC 11 | +| REQ 24: NE/MS should have the capability, when necessary, to automatically force the user to change their password on the first access after the account has been established and on the first access after the password has been reset. | SER 4 | MEC 7-MEC 11 | +| REQ 25: NE/MS should prevent, control, or limit the simultaneous active usage of the same user ID, when appropriate. The number of simultaneous active sessions should be configurable on a user ID basis. | SER 1, SER 2, SER 3, SER 4 | MEC 7-MEC 11 | +| REQ 26: The NE/MS application should not require Superuser access privileges in order to work properly. | SER 4 | MEC 20-MEC 23 | +| REQ 27: NE/MS should have the capability of displaying to the user, when appropriate during the logon process, the time and date of that user's last successful Authentication . | SER 4, SER 8 | MEC 7-MEC 11 | +| REQ 28: A customizable proprietary information statement and no trespassing warning should be displayed on the initial entry screen before any logical access is allowed. Equipment should support a minimum length of 1600 characters. A default message should be provided. | SER 4 | N/A | +| REQ 29: Any failed login attempt should report to the user only that the login process has failed or is invalid. Information such as "invalid user ID" or "invalid password" should not be reported. | SER 8 | MEC 7-MEC 11 | +| REQ 30: NE/MS should Lockout a user account from logging in after a configurable threshold number of login failures has been reached. The Lockout should include the console interface. The Lockout should NOT include the original default account that supports all the Management Actions. | SER 4 | MEC 7-MEC 11 | +| REQ 31: NE/MS should NOT have a mechanism for bypassing the login Authentication and logging in processes. | SER 1, SER 2, SER 3 | MEC 7-MEC 11 | +| REQ 32: No NE/MS should ever display a plaintext credential, such as password, in any media, including displays on terminal screens, printouts, and storing in log records. | SER 8 | MEC 7-MEC 11 | +| REQ 33: NE/MS should enforce password aging with a configurable threshold. | SER 4 | MEC 7-MEC 11 | +| REQ 34: If a login password has surpassed the age limit for that system, then the NE/MS should Lockout the login for that user ID until the password is properly changed. | SER 4 | MEC 7-MEC 11 | +| REQ 35: If an account has been dormant for a configurable threshold period of time, each NE/MS should generate an alert. | SER 4, SER 8, SER 9 | MEC 7-MEC 11
MEC 33-MEC 37
| + +| M.3016.1 security requirements | M.3016.2 security services | M.3016.3 security mechanisms | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------| +| REQ 36: If an account has been dormant for a configurable threshold period of time, the NE/MS should Disable the account after generating a Disable alert. The DISABLE process should NOT include the System Administrator account, the System Security Administrator account, and the Superuser account. | SER 4, SER 8 | MEC 7-MEC 11
MEC 20-MEC 23
| +| REQ 37: To re-enable a Disabled login ID, a properly logged-in administrator with the assigned Critical Security Administration Action to initialize and reset login passwords is required. | SER 4 | MEC 7-MEC 11
MEC 20-MEC 23
| +| REQ 38: To reset a LOCKED OUT login ID and to remove the Lockout condition, a properly logged-in administrator with the assigned Critical Security Administration Action to remove a lockout or change the system's Lockout timer value is required. | SER 4 | MEC 7-MEC 11
MEC 20-MEC 23
| +| REQ 39: Each properly logged-in Session should be logged out by the user or by system inactivity. | SER 4 | MEC 33-MEC 37 | +| REQ 40: NE/MS should log out a properly logged-in Session when the time, since the last activity for that Session , exceeds the system's configurable inactivity timer value. | SER 4 | MEC 7-MEC 11 | +| REQ 41: A user's role type should remain unchanged during the execution of and exit from any NE/MS application. | SER 4 | MEC 20-MEC 23 | +| REQ 42: For all symmetric encryption applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. | SER 5, SER 6 | MEC 24-MEC 26 | +| REQ 43: For all asymmetric encryption applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. | SER 5, SER 6 | MEC 27-MEC 28 | +| REQ 44: For all key exchange applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. | SER 5, SER 6 | MEC 38-MEC 40 | +| REQ 45: For each physical or logical interface that carries any Management Traffic in an NE/MS, the NE/MS should be configurable to secure Management Traffic with Strong Authentication and cryptographic protection in order to provide confidentiality, integrity, and replay protection. | SER 2, SER 3,
SER 5, SER 6
| MEC 24-MEC 32 | +| REQ 46: Any password transmitted in clear text should only be transmitted across a Trusted Path unless a one-time password mechanism is used. If one-time passwords are used, then they may be sent in clear text as long as there is no intermediate host. | SER 1, SER 2,
SER 3, SER 5,
SER 6
| MEC 19 | +| REQ 47: For all symmetric secure data integrity applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. | SER 5 | MEC 29-MEC 30 | +| REQ 48: For all asymmetric secure data integrity applications, the strength of the algorithms should be consistent with the national, industrial, or organizational policy. | SER 5 | MEC 31-MEC 32 | +| REQ 49: All software delivered to a service provider or other customer should include, when appropriate, cryptographic Authentication and integrity protection mechanisms such as digital signatures or symmetric message Authentication as specified in ITU-T Rec. M.3016.3. | SER 7 | MEC 29-MEC 32 | + +| M.3016.1 security requirements | M.3016.2 security services | M.3016.3 security mechanisms | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------| +| REQ 50: All NE/MS receiving software should be capable of interpreting the cryptographic Authentication and integrity protection mechanisms and verifying the source and integrity of the software, when appropriate. | SER 7 | MEC 29-MEC 32 | +| REQ 51: All software updates, including patches, should be transmitted to the receiving NE/MS over a Trusted Path . | SER 5, SER 6 | MEC 19 | +| REQ 52: All NE/MS should provide the capability that an entity cannot deny the responsibility of any of its performed actions, as well as their effects. | SER 7 | MEC 29-MEC 32 | +| REQ 53: NE/MS should be able to log any action that changes the security attributes and services, access controls, configuration parameters of the devices, and each login attempt and its result that caused invocation of the system inactivity timer defined in REQ 12. | SER 8 | MEC 33-MEC 37 | +| REQ 54: NE/MS should provide the capability to configure those Critical Security Administration Actions that are to be included in the security log. | SER 4 | MEC 33-MEC 37 | +| REQ 55: The NE/MS should be able to log each login attempt and its result; and each logout or Session termination (whether remote or console). | SER 8 | MEC 33-MEC 37 | +| REQ 56: NE/MS should be capable of remote logging over a Trusted Path . | SER 5, SER 6, SER 8 | MEC 33-MEC 37
MEC 19
| +| REQ 57: Each log entry should contain the following information:
  • • A description of the action or the actual action that is being logged.
  • • The identity and security level of the user or process that initiated the action.
  • • The date and time the action occurred.
  • • Network source and destination information, if applicable (e.g., when logging in).
  • • An indication of the success or failure of the activity.
| SER 8 | MEC 33-MEC 37 | +| REQ 58: All NE/MS should provide the capability to generate alarm notifications on selected events. | SER 9 | MEC 41 | +| REQ 59: All NE/MS should provide the capability to allow the user to define the selection criteria for events that generate alarm notifications. | SER 9 | MEC 41 | +| REQ 60: All NE/MS with packet-based connectivity should prevent traffic that does not meet the DCN security policy. | SER 10 | MEC 42 | + +# Appendix I + +### Additional security considerations + +The security procedures detailed in the subsequent clauses are tutorial in nature. They are outside the scope of detailed requirements provided by this Recommendation, but should be considered to provide a secure system. In some cases, mandatory language is used; however, this is provided for informational purposes and should serve only as an example. Protocols and recommendations included in this appendix are subject to future discussions and contributions. They do not represent any intent to include or exclude content in existing or emerging standards. + +### **I.1     Applicability to enterprise operations, administration, maintenance and provisioning** + +Enterprises today have evolved beyond the traditional isolated enterprise networks of the past. Enterprises have grown to multi-site businesses that span large geographical areas requiring extranet network connection to customers and business partners. Enterprises must allow partners and customers to gain access to internal data and make operational business decisions based on this data. + +Enterprise networks are developed and administered by the enterprise itself or have been purchased as a managed network from a network provider. Services being developed by providers will allow the enterprise to manage their portion of a larger network environment. + +As the industry moves forward, requirements for access to fault and performance data, and the ability to configure various components of the network by the contracting enterprise, necessitates that appropriate security mechanisms are in place. These mechanisms must provide adequate control for protecting not only the enterprises' managed network, but also providers' own internal network. The internal network may be interconnected to these enterprise networks and may be a part of the telecommunication infrastructure. In summary, the security requirements for operations, administration, maintenance, and provisioning traffic outlined in this appendix are fully applicable to enterprises and service provider/carrier networks. + +### **I.2     Common object request broker architecture, simple network management protocol, extensible markup language, and simple object access protocol** + +The following considerations should be taken into account with regard to security for common object request broker architecture (CORBA), simple network management protocol (SNMP), extensible markup language (XML), and simple object access protocol (SOAP). In addition, there are other protocols that may be equally applicable such as the blocks extensible exchange protocol. Although no changes to these evolving protocols are proposed, the following discussion could be used to enhance security. + +#### **I.2.1   CORBA** + +The CORBA security service comprises the security functionality of authentication of principals (human users and objects), authorization of access to objects by principals, security auditing, communication security, nonrepudiation, and administration. All of this may be overkill for many applications, though. Instead, applications might require only the communication security and system-level authentication functionality based on transport layer security (TLS) technology (and its precursor, secure socket layer (SSL)) for availability and simplicity reasons. Finally, some applications might require no security. The optional requirements below, therefore, reflect three possible choices: + +- No security; +- Object request brokers (ORB) use TLS (or SSL) to provide communications security and system-level authentication, which is essentially "session" security; + +- ORBs use the CORBA security service to provide communications security, authentication, nonrepudiation, and access control lists for groups or individuals accessing individual objects and operations. + +Additional information on security in the CORBA framework may be found in ITU-T Rec. Q.816, *CORBA-based TMN services* and ITU-T Rec. Q.816.1, *CORBA-based TMN services: Extensions to support coarse-grained interfaces*. + +If CORBA is used in the network element/management system (NE/MS) interfaces, then CORBA security mechanisms should be applied. Conformance level of the CORBA security implementation should be clear. The following discussion provides guidance regarding CORBA security. No attempt to identify standards should be inferred. When supplying products or systems based on CORBA, the basic security levels are as follows: + +- Level 0: No application security is provided, and programs are security unaware. Authentication, encryption, data integrity, object invocation authorization, audit trails, and security domain administration should be provided. +- Level 1: Programs may be security aware, which means that they may call an application programming interface for access to additional services such as verification of signatures, check access to objects, and write audit records. +- Level 2: Provides support for digital signatures permitting signing and nonrepudiation of transactions. This is particularly important when operating across various organizations, for example, in a business-to-business context or network management peering arrangement. + +The common secure interoperability (CSI) Specification defines standards by codifying the specification for secure interoperability when using General Inter-ORB Protocol/Internet Inter-ORB Protocol: + +- CSI Level 1: The identity of the initiating principal is communicated from sender to receiver. +- CSI Level 2: The identity of the initiating principal is communicated from sender to receiver, but the identity can be delegated to other objects so that other objects can impersonate the user. +- CSI Level 3: In addition to identity being passed, the attributes of the initiating principal passed from client to target may include other authorization information, such as membership of roles or groups. + +It is incumbent on suppliers to: + +- Be fully conversant with the security capabilities of the ORB technology selected; +- Ensure it meets the requirements for security outlined elsewhere in this Recommendation. + +As its name implies, CORBA deals with objects. Object security is about preventing the unauthorized use of objects by enforcing a set of access control rules. CORBA security ensures users are accountable for their actions on or with an object, and ensures the availability of objects. + +Object security differs from many other aspects of security. Frequently, the developer does not need to know security details because security is applied at a later stage, as with a wrapper. Therefore, certain aspects are vitally important. In CORBA, names may be duplicated or may not exist at all; only reference numbers may exist. It should be possible to define an object's policy without knowing the object's name. Similarly, it must be possible to define an object's policy even on objects with many names, and the policy must be applied regardless of the name used to secure the object. + +Typical object-oriented systems have tens of thousands of objects, and it is not reasonable to expect security to be defined for individual objects. Therefore, it should be possible to group together objects and define a policy for the group of objects whose protection needs are similar. + +- *End-to-end authentication:* CORBA can pass the user context to another application. Where a strong trust relationship has been established between these systems, it may be possible to accept this information without further verification. However, where other mechanisms do not exist, it may be necessary for the security of other systems to be tightly coupled with CORBA security. End-to-end authentication is very important, and it is worth checking whether the vendor supports this. +- *Access control:* CORBA supports the idea of role-based login. Systems should always be developed using this feature because not only does it reduce administration costs, it simplifies it, which means that the configuration is less likely to have errors. +- *Encryption:* Use of encryption within CORBA must comply with the requirements stated in this Recommendation. Full use should be made of CORBA features for integrity, confidentiality, and origin authentication, especially when communicating over a network of any type. +- *Policy administration:* CORBA policy administration is responsible for setting up information about domains, users, roles object access policy, message protection policy, and audit policy. Clarity should exist throughout the design of all aspects of domain and object naming. Roles should be clearly defined with the aim of ensuring appropriate segregation of duties. + +#### I.2.2 SNMP security + +SNMP, a widely used method of administering a variety of processor-based equipment, offers the ability to: + +- Obtain device configuration parameters; +- Set device configuration parameters; +- Send alerts from the managed device to a central analysis system. + +Many deployed versions of SNMP have significant security vulnerabilities. In Versions 1 and 2, the password (known as the community string) is transmitted in clear text. In addition, although checks may be made to validate the Internet protocol (IP) address of the client, a moderately determined attacker can spoof IP addresses. Versions 1 and 2 of SNMP create significant security exposures in several networks. Therefore, SNMP Versions 1 and 2 should be used only as a last resort. ITU-T Study Group 4 is considering the establishment of two new protocol stacks: + +- SNMPv3 or V2C with TLS over transmission control protocol (no access control); and +- SNMPv3 with user security model over user datagram protocol (as a forward looking stack). + +Where SNMP is deployed, Version 3 is the preferred level. SNMP Version 3 is more secure and should be used in all new systems because it provides protection against modification of data, masquerade, re-ordering of messages, and loss of confidentiality. The following countermeasures should be considered to secure SNMPv3 access to NEs: + +- An SNMP agent should send an alert to a manager if it receives a command originating from an unknown source. +- Access controls should be used to allow SNMP messages only from an authorized manager. SNMP messages from all other sources should be denied and treated according to appropriate security policies. It may be desirable to block unauthorized requests at the device and at a network perimeter. +- The default community string should not be used. +- Access violations and access errors should be logged. +- SNMPv3 uses the data encryption standard as default; however, more secure algorithms can be used. + +- SNMPv3 should be used at least with AuthNoPriv, which provides authentication but no confidentiality of transactions. Preferably, AuthPriv will be used. +- SNMP agent logging should be enabled. +- Any service or capability not explicitly required should be disabled, including SNMP if it is enabled. + +#### I.2.3 XML + +The XML standard provides language for defining data structures. The current standard is 1.0. Version 1.1 is a candidate Recommendation under review. The Organization for the Advancement of Structured Information Standards' (OASIS) Security Services Technical Committee is seeking to broaden security functionality by leveraging XML. OASIS is working on finalizing security assertion markup language (SAML). SAML is based on four assertions: + +- *Authentication* – issuer has authenticated the object; +- *Attribute* – specific uniform resource identifier or extension schema that defines the attribute; +- *Decision* – reports validity of authentication; and +- *Authorization* – subject has permission to access resource(s). + +The XML assertions must include the following: + +- *Basic information* – unique identifier or name for the assertion and commonly includes date and time of issue and validity time span; +- *Claim* – a document describing the use of the assertion; +- *Condition* – the assertion may be subject to conditions that make it valid or invalid; and +- *Advice* – provides additional information such as assertions used to make a policy decision. + +#### I.2.4 SOAP + +SOAP 1.1 is the current Recommendation from the World Wide Web Consortium. SOAP is a message format not tied to a specific protocol. It most commonly uses hypertext transfer protocol (HTTP), but can use other protocols such as SMTP or file transfer protocol (FTP). When SOAP is used with HTTP, the firewall views SOAP as HTTP and usually will allow it to pass. SOAP could potentially be filtered by the firewall, even when the firewall is not aware of SOAP. This filtering, however, is not an easy task and is susceptible to errors. Filtering is a challenge because encryption can hide the content and context of the data transported (i.e., XML), and SOAP has no uniform addressing scheme or internal structure (i.e., headers and method names are optional). + +### I.3 Lawfully authorized electronic surveillance + +Telecommunication carriers should take the following security considerations into account with respect to the implementation of Lawfully Authorized Electronic Surveillance (LAES). + +Security practices for LAES activities should be robust and the same as for any critical NE, operations support system (OSS), or MS with some exceptions as listed below. These practices relate to the necessity of keeping LAES activities confidential. + +- Only authorized employees will participate in LAES activities. +- LAES information, including target identity, law enforcement agency(ies) involved, call content and call-identifying information will be protected from disclosure to unauthorized personnel. +- Only authorized personnel will have access to LAES commands and processes. +- An up-to-date list of personnel authorized to access, maintain, administer and manage LAES activities, processes, and procedures will be maintained. + +- LAES security activities, policies, and procedures will be adequately documented and made available to authorized personnel. +- LAES-related security logs and activity records will be maintained and stored in a secure facility. +- A rigorous documented process will be implemented to identify and authenticate law enforcement agencies and process LAES requests. + +### **I.4 Physical security considerations** + +The following considerations should be taken into account for physical security. When preparing security requirements, physical security is an important component. Most security architecture's assume that the physical environment is protected. At one time, all NE were contained in central office (CO) buildings. These buildings had employees working around the clock to operate, provision, administer, and maintain this equipment. Employees knew each other, and outsiders could not gain access to the sites without someone noticing and challenging them. However, the environment is very different today. Wireless equipment tends to be installed outdoors in an insecure environment. Also, many, if not most, COs are unmanned and dark most of the time. Roving crews and individuals who are dispatched by a central location, perform scheduled upgrades and maintenance tasks. Today, 24/7 security guards are the rare exception. COs are also used by outside plant personnel as a convenient place to meet and store tools and equipment. The following are characteristics of a secure facility: + +- All personnel entry and exit is logged and recorded. +- Vendors and co-located personnel are vetted and their entry/exit is logged and recorded. +- Physical access to NE is limited to authorized employees. +- Co-located personnel are subject to the same access requirements as the incumbent service provider. +- No one who has legitimate physical access to the building has logical access to NEs, consoles, network access device's OSSs without protected authentication. +- Unauthorized access will be detected and responded to in a timely manner. +- Services such as water, power, and telecommunications will be available. +- Sites are under surveillance by random roaming security personnel, alarm systems that monitor and record door and window openings and closings, motion detectors, and inferred detectors, and remote video monitoring of critical locations. +- Retention of surveillance media and logs should be documented. Length of retention would vary depending on risk level. + +The following clauses provide additional information regarding physical security. A detailed description of physical security issues can be found in the National Communication System, *Public Switched Network Security Assessment Guidelines*, September 2000. + +#### **I.4.1 Physical premises security** + +Organizations will usually implement various levels of building access controls in accordance with the importance of the assets resident in the facility. Often, large corporations will build separate high-security facilities for critical network components, such as switches or data centers. The importance of the assets resident there determines the level of security. This determination comes during a discovery phase and asset assessment review. The following clauses include assessment items for a facility housing high-value or critical assets. Less strenuous reviews would be undertaken for less sensitive facilities. The overall physical security assessment must determine the level of protection needed and the relative quality of the protective mechanisms in place. + +##### **I.4.1.1 General building security** + +Although a building's doors and windows are usually considered to be its primary access points, other points (e.g., air vents, entry points for water, gas, communications, and electricity, and drainage conduits) must be considered, depending on the kinds of threats. Additional entry points such as CO cable vaults need to be considered, as do other places where the potential to cause damage exists. Furthermore, the buffer space between the public and the building itself must be considered. Lawns, landscaping, lighting, and fences can contribute to the first layer of perimeter defense because they slow or prevent covert approaches. Physical barriers such as concrete posts or large concrete landscaping planters can be used to prevent approach by cars, trucks, or other vehicles with the potential destructive intent. Outside cameras and other surveillance gear further enhance or enlarge this buffer space. + +##### **I.4.1.2 Guards, locks, and identification badges** + +Building guards protect the external perimeter of the building and sometimes protect internal areas. For critical facilities, the review should ensure the following: + +- All doors providing access to the facility are either locked or guarded at all times. +- Any doors not normally in use, such as emergency exits, are alarmed. The review should ensure that alarms function properly and procedures exist to respond to alarms. +- Doors are installed properly so that they cannot be removed from the outside (e.g., hinges and bolts are protected from outside tampering). +- During peak periods of ingress and egress, entrances and exits have a guard present. During off-peak times, the door should be monitored, and some other form of access control should exist (e.g., swipe cards, proximity cards, and keys). +- Access through unguarded doors uses a method requiring identification of the entrant. +- Unguarded doors that provide access via keys or other means have mechanisms to prevent "tailgating".5 Mantraps, revolving doors, and detectors can be used to prevent tailgating or send an alarm that tailgating has occurred. +- The recruitment qualifications, training, and retention methods used for employing guards are adequate and appropriate. This is particularly important for contracted guard services, which are common. +- Employees, onsite vendors, contractors, and other authorized individuals possess and display a badge at all times while in the building. +- Non-employee visitors are given a temporary identifier, such as a visitor's pass, and are required to display it clearly. +- Procedures and conditions exist under which visitors can enter and work unescorted, and the conditions under which they must be escorted. +- Employee badges display a color photograph. The photograph should be big enough so that the employee need not have to hand the badge to a guard for the guard to see it. It should be constructed so that the photograph cannot be altered or replaced. The photograph should be clear enough so that the guard can compare the picture with the face of its wearer. +- The badge displays the employee's name and any other identifying information (e.g., number, bar code) clearly. +- The badge has a mark or indication that distinguishes employees from non-employees with access to buildings. + +--- + +5 Tailgating refers to an unauthorized person's act of following through a door opened by an authorized person. + +- The badge is durable and resistant to wear, damage, or alteration as much as possible. +- The badge contains electronic or magnetic information that may be needed by card readers. +- The badge may include a smart chip that embeds additional information, such as biometric data or X.509 certificates. +- Badge authentication and authorization systems should be linked to a central security directory to allow immediate change or removal of access privileges. +- The badge supports a capability to limit access to some areas of the corporate campus, as opposed to full access, when appropriate. +- The badge has an address to which it can be mailed without postage, if lost, if a non-employee were to find it. +- Corporate or building security can disable or invalidate any badge that has been lost, or whose wearer is no longer permitted to enter the building or corporate campus. +- When the wearer terminates employment, someone (manager, building guard, corporate security) will retain or destroy the badge so that it cannot be used illicitly. + +Guards are not the only personnel responsible for preserving the internal security of a building. Authorized occupants often enhance building security by vigilance and passive monitoring. The assessment should determine whether the staff has been empowered to challenge unauthorized personnel in controlled areas. A penetration test can be valuable for ascertaining the degree to which guards and employees are appropriately trained in the importance of physical security. Reviewers may attempt to sneak past or talk their way past guards or to entice employees to provide admittance through unguarded entrances. + +##### **I.4.1.3 Physical and logical key administration** + +Traditional physical keys are rarely used in sensitive facilities because they are difficult to inventory and recover and they do not provide an audit trail of the user. Often, the use of physical keys is restricted to access to internal portions of the building, such as storerooms, custodial rooms, and wire closets. It is still common, however, to find businesses and installations that use key locks as their primary means for ingress to buildings or access to critical areas within buildings. When that is true, the following precautions are important: + +- Procedures should exist for authorizing distribution of keys to individuals, including key control and logging of access and distribution; +- Keys should be individually numbered; +- A complete inventory of keys and their owners should be maintained and audited; +- Criteria for replacing locks when keys are lost should be in place; +- Periodic audits of the key inventory should be enforced, and procedures for reconciling discrepancies should be in place; +- Procedures are in place for recovering keys when access is no longer needed or authorizations change. + +Logical key (e.g., proximity cards) procedures must be evaluated against the same criteria. Key recovery, ingress and egress recording, and authorization procedures are simplified with logical keys because these systems provide central facilities for monitoring use, assigning authorization, and disabling of keys. Still, procedures must be in place to ensure that those responsible for maintaining the key inventory and authorization database are notified when individuals leave or their access requirements change. Combination locks, a special case of logical locks, should be assessed to ensure that combinations are not discernible from wear patterns or from combinations written down. Combinations should be changed if entry authorizations are changed. + +##### **I.4.1.4 Functional separation of facilities and multilevel access control** + +Physical security applies to internal portions of a building as well as to the external perimeter. Access to internal areas that are considered sensitive or operationally critical should be controlled when access to their contents is limited for any reason (e.g., they contain sensitive data, experiments, or equipment). In general: + +- Critical computer and network facilities should be contained in areas having separate physical access control mechanisms. Access should be granted only to those having a need. +- Procedures should be in place to ensure that proprietary information is kept in secure facilities when not in use. Offices and file rooms where such material is routinely kept should be locked. The cabinets in which proprietary information is kept should also be locked. +- All potential access points to critical computer and network facilities (e.g., consoles, operations centres) should be controlled in a manner commensurate with the control enforced over the facility itself. +- A record of access to all such controlled spaces should be maintained. +- Storage media holding critical information should be encrypted or housed in locked, limited-access areas. +- A critical system's physical address should not be disclosed to those not having a need to know. + +Controlling the internal areas of a building can be enhanced through the use of segregated roles and responsibilities. For example, administrative staff does not require access to an organization's computer rooms. Likewise, engineers do not generally require access to the document control room. The review should assess whether existing functional segregation is appropriate. In addition, dual entry key or combination locks can be used if the degree of risk so indicates. + +#### **I.4.2 Building services** + +An organization's operations are critically dependent on the availability of services, such as water, power, telecommunications, and waste disposal. + +##### **I.4.2.1 Utilities (water, power, telecommunications and waste disposal)** + +Without water, power, telecommunications and waste disposal services, an organization cannot operate effectively, if at all. Dependency on these services is often undervalued. The assessment should evaluate the organization's planned reactions to service interruptions. For services critical to the continuing function of the business, the following steps are essential: + +- Power feeds should be duplicated and geographically separated to prevent accidental loss of power. +- Emergency power should be available to allow the continued operation for greater than the average duration of power outages. Generating capacity should be available for deployment before emergency supplies are exhausted. (Mobile generators may be owned or contracted.) +- Sufficient onsite water storage (or delivery services) should be available to support continued operation of critical components of the facility. +- Outside communications must either have active-standby backups, or must be robust enough to operate in a crisis, as must internal communications. Capacity should be sufficient to handle crisis-level traffic. +- Restroom and sewage facilities must function through crises, or temporary arrangements must be in place (at least contractually) for quick activation. +- Air conditioning for computer rooms and other areas that require controlled environments must be backed up to prevent machine failure or damage from overheating. + +- Locked containers for disposal and destruction of proprietary information should be readily available wherever such material is used. The review should trace the disposal path of such material to ensure that it is closed. + +Of interest for the assessment is the distribution of these services within buildings. The assessment should evaluate the overall resistance of the facility to service interruption from the origination of the service at the utility provider to the distribution paths inside the building. + +##### **I.4.2.2 Emergency facilities** + +The review should assess the adequacy of emergency facilities such as fire detection and suppression, power conditioning, air conditioning, ventilation, and other environmental protection systems necessary for continued operation of critical systems. These systems must react in ways that allow: + +- People to evacuate the premises; +- Equipment to be protected (at least long enough for fire companies or others to arrive); +- Facilities to retain structural integrity; +- The building's contents to be protected from the outside environment, as much as possible. + +Emergency facilities are important as much for the aftermath of a security breach as they are for accidents and natural disasters, as suggested in the previous clause. + +##### **I.4.2.3 Transport redundancy and physical protection of critical facilities** + +Critical computer and communication systems facilities should be geographically dispersed to the extent possible without unduly affecting operational costs, performance, and security. In addition, routing of critical communication links (e.g., important interoffice trunks, signalling links) should be redundant and geographically dispersed inside and outside the facility so that communications may be immediately rerouted over physically diverse backup routes, when necessary. The communication networks required for maintaining service should be designed in such a way that no single point of failure will result in a widespread or serious outage. + +#### **I.4.3 Environmental and geographical threats** + +Critical sites should be reviewed to identify any risks resulting from their location in areas likely to experience natural disasters, serious accidents (e.g., chemical spills, gasline explosions), power interruptions, and related problems. The review should also consider the effects of simple environmental factors, such as extreme heat or cold, damage from salts and pollution, and harsh climate conditions. + +Geographical issues include the reactions of the local populace, such as acts of hostility, responsiveness of local emergency services, and the level of safety afforded to staff, on site and en route to the facility. Because human activities and motivations change over time as a result of unrest, political problems, religious views, or other factors, reviews should be repeated periodically according to a predetermined schedule. Although it is often impractical to abandon facilities where such risks exist, it may be appropriate to duplicate or relocate critical systems and resources housed in high-risk facilities. + +Business continuity and disaster recovery plans should be developed that address responding to events resulting from these threats and issues. Plans should include command, control, and communication procedures, and should be tested on a regular basis. Operations recovery plans should also include provisions and contracts that can be quickly executed in response to hazardous material (HAZMAT) incidents. These plans should also consider that complete restoration to a safe environment might prevent normal access to the facility over an extended period of time. Potential remediation may require relocating to a backup facility or the availability of HAZMAT trained and equipped personnel to operate the facility during the interim. + +#### **I.4.4 Co-location procedures** + +Co-location refers to a situation that prevails when plant belonging to multiple providers is present in the same physical location. Of particular concern, for the purposes of physical security reviews, is that providing such access often means that competitors (sometimes multiple competitors) will require access to physical components and facilities of the host provider. The review should note that: + +- Physical barriers should isolate critical equipment; however, co-located personnel are subject to the same access requirements as the incumbent service provider. +- Key distribution, accounting, and auditing procedures are in place. Processes should be in place to ensure that personnel changes can be monitored across co-located companies. +- Critical equipment and facilities do not draw attention to themselves. The traditional method of clearly marking crucial equipment and transport facilities (so-called "red blocking"6) becomes a potential hazard in an open environment and should be avoided. + +### **I.5 Development process** + +#### **I.5.1 Bootstrapping, installation and failure modes** + +The following considerations should be taken into account for bootstrapping, installation and failure mode security procedures. + +Several distinct efforts must be completed to secure an implementation from a "new installation" through the implementation's lifetime. To address these issues, it is important to begin by understanding the threats to an implementation. These threats are referenced in ANSI T1.233-2004, *Operations, Administration, Maintenance, and Provisioning – Security framework for Telecommunications Management Network Interfaces*, and ISO/IEC 10181, *Open Systems Interconnection – Security frameworks for open systems* standards documents. General connectivity to open systems broadens threats such as: + +- Bootstrap viruses; +- Unauthorized access; +- Masquerade; +- Threats to data integrity; +- Threats to confidentiality; +- Denial of service (DoS); and +- Repudiation. + +#### **I.5.2 Patching process** + +Service providers contract with vendors who develop and provide both an application and a platform on which an application is installed, or only application software. In the latter case, providers install the software onto a platform they have previously purchased. + +Vendors develop patches to correct or modify operating system (OS) or application software, or both, between general releases. Following appropriate testing, a patch is released to the service provider. In some instances, an application software vendor may release patches in "bundles", perhaps with some contractual regularity. Releases every six months are not uncommon. + +An OS patch generally should not affect the manner in which an application runs; however, that is not always the case. Consequently, when a platform vendor releases an OS patch, it is incumbent on + +--- + +6 Red blocking alerts support personnel that the circuit is especially important and that care must be taken not to disturb it accidentally. + +the provider to verify with the application vendor that the OS patch released will not adversely affect the running of the/an application. + +In a situation where an application vendor supplies both an application and a hardware platform, but is not an original equipment manufacturer (OEM) of the platform, and an OS security patch is released by the OEM of the platform, it is incumbent upon both the application vendor and the service provider to be aware that a security patch has been released and to make arrangements for the patch to be tested in a timely manner, in order to verify that the patch will not adversely affect the application. + +The application of security patches must be assigned a priority for review by the application vendor (a matter of weeks versus months). As such, a routine process must be established such that when a provider communicates a concern regarding a security patch to an application vendor, the vendor will take appropriate action in an expedited manner. In addition, the vendor will ensure that installation of the patch will not corrupt previously installed security patches. + +If security patch testing reveals an impact to an application, appropriate corrective actions must be taken in a timely manner to identify the issue and formulate plans to correct the condition causing the application to fail and, subsequently, to apply the security patch. + +The following security considerations should be taken into account when implementing patches to the OS or application software. + +- Equipment vendors or system integrators should provide security reference and training manuals for administrators that include details of OS and application security functions and procedures and user access procedures. +- OS security and other patches should be verified as compatible with NE and MS applications. +- OS software: Only patches approved by an OEM should be applied to an operational network element or management platform operating system. +- Management application software: Only patches approved by an original management application vendor should be applied to an operational management application. +- High-impact patches should be distributed in a timely manner and should not be constrained by periodic patch dissemination processes. +- All downloads or uploads of any software or configuration data must be secured with strong data origin authentication and strong integrity protection. Ideally, both would be provided through the software provider's digital signature. In addition, the software provider may choose to encrypt the software or configuration data. +- A description of the procedure(s) for acquiring and incorporating the latest security patches for the system and application software executing within each element should be provided at time of delivery. +- A description of the process for testing each security patch, before approving release to the service provider, should be provided at time of delivery. +- The level of backward compatibility of the system software releases and security maintenance patch releases should be specified at the time of delivery. +- System software or a process must track applied patches and upgrades. Patch and upgrade status should be auditable. + +#### **I.5.3 Development lifecycle security** + +Security of a product or service is dependent on the complete lifecycle process. Security is an issue during conceptual design and remains an issue through detailed design, development, deployment, and decommissioning of a product. For products or services dealing with sensitive information, security may be required even beyond the decommissioning of the product or service. Appropriate + +controls and testing during the complete lifecycle process are critical to providing acceptable levels of security. + +##### **I.5.3.1 Personnel management** + +A fundamental issue of security that is often overlooked is the trustworthiness of the staff. All staff with access to design, development, and testing must be trustworthy. + +- All personnel, contractors, subcontractors, consultants, and employees involved in developing and testing critical software components must pass a background check. + +##### **I.5.3.2 Security awareness and training** + +All personnel must be aware of security policies and procedures and the need to protect information assets. The weakest link in security is often the people involved. Security awareness and training dramatically strengthens the weakest link. Awareness reduces the number of unauthorized actions attempted by staff; increases the effectiveness of protection controls; and helps avoid fraud, waste, and abuse of computing resources. + +- Security awareness and training should be provided to all staff, including contractors, subcontractors, consultants and employees. + +##### **I.5.3.3 Risk management** + +Risk management is fundamental to information security. Risk management is defined as the identification, analysis, control, and minimization of loss associated with an "event". The primary steps identifying risk include identification of actual threats, consequences of a realized threat, potential frequency of occurrence of a threat, and the likelihood of a realized threat. Risk management not only involves performing risk analysis with a cost benefit analysis of protections but also implementing, reviewing and maintaining protection. + +A risk analysis identifies the risks and provides a cost-benefit justification of countermeasures. This information is used to influence the decision-making process of all lifecycle phases, including site selection, building design, and construction decisions. To determine if a safeguard is warranted, the annualized loss expectancy (ALE) is determined. The (ALE before safeguard implementation) – (ALE after safeguard implementation) = value of safeguard. Note that the safeguard implementation should include the annual cost for operation and maintenance. + +- A risk analysis should be performed for each new product or service. This analysis should include a formal document outlining the approach used and results of the analysis. At a minimum, the report should identify all data accessible and the data owner (i.e., corporate, Internet service provider), quantify or qualify the value of the data or service at risk, and determine potential upstream and downstream impacts of the threat to NEs or OSSs. + +##### **I.5.3.4 Requirements** + +- Security requirements should be documented during the requirements-gathering phase for the product or service. + +##### **I.5.3.5 Design** + +- Security requirements should be addressed at the design phase, not added after development has begun. +- A security design review should be performed to locate design flaws that affect security. +- All access points into the system must be well documented and provide support for identification and authentication. +- Maintenance backdoors or trap doors that violate the security policy must NOT be allowed. + +##### **I.5.3.6 Separation of duty** + +Functions that are harmless in a trusted environment can create security vulnerabilities when used in untrusted environments. For example, a postscript interpreter was designed to view documents. An untrusted document could use the functions within the postscript interpreter in malicious ways, such as making copies or deleting files. + +- The system should support at a minimum three user levels: user, system administrator/operator and security administrator. +- Each function should have the minimum level of privilege required to perform the job function. + +##### **I.5.3.7 Implementation** + +- Reused resources should be purged of any information before re-use (i.e., files, memory, and temporary storage). +- Developers should follow best practices for secure programming (i.e., manage buffers so that buffer overflows do not occur). +- Periodic security audits should be performed on the development, test, and support environments. +- Development environments should not be used for non-company business. +- Public domain software should not be imported, used, or distributed for use on development, test, or support systems unless it is available in source code and the source code has been inspected for malicious code. + +##### **I.5.3.8 Documentation** + +- Documentation should be marked with proprietary markings, where appropriate. +- The end-user documentation must describe the security functionality that is not transparent to the user, explain its function, and provide guidelines on use. +- The system administrator's guide should include the following: + - Cautions regarding functions and privileges that need to be controlled when running in secure mode; + - Document use of audit functions; + - Procedures for examining and maintaining audit logs; + - Detailed audit log structures; + - Procedures for audit log backup and deletion; + - Procedures for checking amount of free space available for audit logs. + +##### **I.5.3.9 Operating system** + +The OS must be able to provide effective hardware and software controls to provide protection appropriate to the value of data and resources being managed. For the proposed security architecture, it is assumed that the OS will provide the security level required for the data and resources being managed. This assumption may need to be reviewed for specific service provider needs. If the OS does not meet the security provider's security needs, then the software may need to be installed in another OS that supports higher levels of security. + +- The OS must have relevant security patches installed. +- The OS must be configured securely and must be delivered with a restrictive security access privilege configuration. There are several documents and Web sites that discuss OS + +security. Although it is beyond the scope of this Recommendation to list them, some examples include the Common Criteria, and OS Protection Profiles.7 8 9 + +- Only a minimum of services will be enabled that are required for operation by default. + +##### **I.5.3.10 Software engineering** + +Security is an integral part of software engineering. To develop a secure product, secure programming techniques and secure protocols must be used. Non-secure programming techniques can circumvent the best security protocols and mechanisms. For example, if a programmer does not manage buffers properly, a buffer overflow may occur and provide more privilege to a user than is appropriate. + +- Vendors should follow formal documented development processes, such as the Capability Maturity Model developed by the Software Engineering Institute. Secure programming best practices must be followed in design, development, testing, and distribution of the software. + +##### **I.5.3.11 Availability and performance** + +Availability and performance are integral to a secure system. Performance can be degraded to the point that the system is no longer usable. + +- Design, development, and implementation should minimize the effects of a DoS attack. +- Design, development, and implementation should ensure high availability. +- The network architecture and implementation should have no single point of failure. + +##### **I.5.3.12 System software** + +The software used to operate and maintain the computer systems (OSs, utilities, and MSs) must be able to be configured and maintained securely. Testing should be conducted to provide assurance that components and security features have been robustly implemented and correctly configured. + +- System software and middleware products must be installed and configured securely, including installation of security patches. The software must be delivered with a restrictive security access privilege configuration. + +##### **I.5.3.13 Transmission** + +- The option to secure data transmissions must be available to be used at the service provider's discretion. Secure transmissions options should be available for both client-to-server and system-to-system. + +##### **I.5.3.14 Secure storage** + +- Service provider configurable options for securely storing data should be provided. The service provider should be able to specify which fields are stored securely. + +##### **I.5.3.15 Software assurance** + +Software assurance should be addressed from two perspectives: testing of security features and testing for potential security policy violations. + +- Duties must be segregated between software development groups and software testing groups. +- A security test plan, test procedures, and results should be documented. + +--- + +7 The Common Criteria is becoming an internationally recognized standard for formal security evaluation (). + +8 Information Assurance Technical Framework Forum Operating System Protection Profiles, [http://www.iatf.net/protection\\_profiles/operating\\_systems.cfm](http://www.iatf.net/protection_profiles/operating_systems.cfm) + +9 National Institute of Standards and Technology, Computer Security Resource Center, + +- All security features must be tested. +- Tests should include attempts to locate violations of security policy (i.e., vulnerabilities such as access control). +- As part of the test, verification must be done so that the newly developed system or application does not introduce vulnerabilities in existing structures, common networks, and systems. +- Verification of secure programming techniques must be performed. Verification may be done via code reviews or software tools. +- All security flaws must be corrected, removed, or neutralized and the system retested. + +##### **I.5.3.16 Packaging and delivery** + +A software configuration management system must be used throughout the lifecycle of a product that maintains control of changes to source code and documentation. + +- Developers should not maintain the software configuration management system. +- Developers should not have access to production systems except under controlled emergency provisions that are approved and logged. +- Only authorized code and code modifications should be added to the deliverable source baseline. +- All changes must be documented and reviewed. +- Tools or procedures must exist to generate a new version of the system from source code. +- Tools or procedures must exist to protect the source code from unauthorized modifications. +- Tools or procedures must exist to verify the appropriate versions and levels of component source modules that were used. +- The product must contain integrity mechanisms such that it is possible to verify the installed software is consistent with the delivered software (i.e., no unauthorized modifications have been made). +- Where a mechanized scanning tool is available, a vulnerability scan must be completed after upgrades or other significant changes to the OS or application software. +- Security flaw remedies or "fixes" must be provided in a timely manner commensurate with the threat. +- A master database must exist that contains copies of all delivered software. The software must have a release number and specifications for appropriate OSs and hardware. + +##### **I.5.3.17 Secure installation, configuration and operation** + +- Secure configuration parameters should be defined for the software. +- Secure operations procedures should be defined and documented for the software. +- All remote support of the software should be performed in a secure manner. +- All default user IDs delivered with the system should be delivered in an inactive state that requires explicit action by the administrator/software installer to be usable. +- All installation processes should be secure and should not rely on trust relationships (i.e., share drives). + +## Appendix II + +## Framework and design guidelines + +### II.1 Framework and model + +In the context of this Recommendation, to secure something means to protect it (i.e., computers, networks, data, or other resources) from unauthorized access, use, or activity. Loss of data, denial of service (DoS), and theft of service are only some of the results of security incidents. System and network administrators need to protect systems and their component elements from internal and external users and from attackers. Although security is multifaceted (spanning operations, physical, communications, processing, and personnel), of concern here are security problems resulting from weaknesses inherent in commonly employed configurations and technology. A threat consists of, but is not limited to, disclosure, unauthorized use, information element modifications, and denial of service. Table II.1 lists some security threats. + +**Table II.1/M.3016.1 – Threats** + +| Threat category (Note) | Examples of threats | +|------------------------------------|-----------------------------------------------------------------------------------------------------| +| Unauthorized access | Hacking
Unauthorized system access to carry out attacks
Theft of service | +| Masquerade | Session replay
Session hijacking
Man-in-the-middle attacks | +| Threats to system integrity | Unauthorized manipulation of system configuration files
Unauthorized manipulation of system data | +| Threats to communication integrity | Unauthorized manipulation of data in transit | +| Threats to confidentiality | Eavesdropping
Session recording and disclosure
Privacy violations | +| Denial of service | Transmission control protocol (TCP) SYN flood
Malformed packet attacks
Distributed DoS | + +NOTE – Derived from American National Standards Institute T1.233-1993 (R1999), *Operations, Administration, Maintenance, and Provisioning – Security Framework for Telecommunications Management Network Interfaces* and International Organization for Standardization (ISO) 7498-2:1989, *Information processing systems – Open Systems Interconnection – Basic Reference Model – Part 2: Security Architecture*. + +These security threats may be minimized or mitigated within a network system or NE platform or application by inclusion of security services (as defined in ISO 7498-2:1989, *Information processing systems – Open Systems Interconnection – Basic Reference Model – Part 2: Security Architecture*) to enforce the following: + +- Identification and **Authentication**; +- Authorization and **Access Control** Level; +- Data Integrity; +- Privacy and Confidentiality; +- Nonrepudiation. + +This Recommendation addresses security for the management plane, that is, security features to ensure that the network can be administered and managed in a secure manner. Some vulnerability may still exist, even after following the recommendations contained in this Recommendation. The following risks are among those with the capability to compromise the management plane: + +- Inappropriate actions by authorized users or attackers. These actions can be either malevolent or accidental. +- Bridge of the control plane security (e.g., signalling, routing, naming, and discovery protocols). +- The effects of vulnerabilities in specific protocols. +- Malware (e.g., viruses, Trojan horses, worms, or other embedded code). Once malware successfully compromises any NE/MS, the malware may use the secure network communication links to transmit attacks to other NE/MS components. These attacks may continue until network managers detect the attack and take action to eliminate it. + +This Recommendation is concerned with the security of management traffic, especially when it traverses networks mixed with end-user traffic. Figure II.1 illustrates a reference model that is used to specify network management security solutions. This model is used to examine logical communication paths within the entire network and quantify which protocols are used for communications on each path. Using this model, threats and vulnerabilities can be examined for each path, and appropriate security mechanisms can be applied. + +Multivendor NEs are shown at the bottom of the model in Figure II.1. EMSs that provide specific management functions for the particular NE are illustrated above the NE. The network management system (NMS) itself is at the top of the model. The NMS provides overall management to the NE and EMS, and contains the specific service management applications and the business management applications, such as configuration and billing systems. Remote and local operators are also shown in the model and communication paths are shown with all other system elements. + +![Figure II.1/M.3016.1 – Network management security reference model. The diagram shows the interactions between a Remote operator, Network management system (NMS), Element management system (EMS), Network element (NE), and Multi-vendor network element. Arrows indicate various management and operator interactions labeled 1 through 12. A small text 'M.3016.1_FII.1' is at the bottom right.](798679874d1c29f8343506a156c79d7e_img.jpg) + +Figure II.1/M.3016.1 – Network management security reference model. The diagram shows the interactions between a Remote operator, Network management system (NMS), Element management system (EMS), Network element (NE), and Multi-vendor network element. Arrows indicate various management and operator interactions labeled 1 through 12. A small text 'M.3016.1\_FII.1' is at the bottom right. + +**Figure II.1/M.3016.1 – Network management security reference model** + +The security reference model (Figure II.1) may also be useful in correlating telecommunication management network (TMN)-defined interfaces to the security model. The TMN is defined in ITU-T Rec. M.3010, *Principles for a Telecommunications Management Network*. It is defined as an architecture for management, including planning, provisioning, installation, maintenance, operations, and administration of telecommunication equipment, networks and services. + +### **II.2 Design guidelines** + +Table II.2 presents design guideline objectives that attempt to satisfy the requirements in clause 6 to mitigate the threats proposed in Table II.1. + +**Table II.2/M.3016.1 – Design guidelines considered** + +| Guideline | Description | +|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Isolation | Insulation of management traffic from customer traffic. | +| Effective security policies | Requirements and supporting architectures must allow for policies that are definable, flexible, enforceable, auditable, verifiable, reliable, and usable. | +| Strong Authentication , Authorization, and Accounting (AAA) | Reliable accounting of properly authorizes sessions between authenticated entities. | +| Highest benefit for a given cost | Improve security by implementing security mechanisms that are standardized, have widely available implementations, and widespread deployment, so that use histories allow security mechanisms to be evaluated. | +| Path for improvement | Consider next steps for enhancing and improving network management security to further satisfy given requirements with evolving technology and mechanisms or to satisfy newly defined security requirements. | + +| Guideline | Description | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Technical feasibility | Requirements must be satisfied with products, solutions, and/or technologies available today. | +| Housekeeping | Requirements should be consistent with standard operating procedures of well-run network management operations. | +| Open standards | Use ideas and concepts that are already standardized or are being standardized by the standards organizations (e.g., IP security (IPsec), digital signatures). All aspects of the open standards should be considered, including system, protocols, modes, algorithm, option, key size and encoding | + +## Appendix III + +## Semantics of terms used in the M.3016.x series + +The following terms appear in **bold** when they are used in a requirement statement. + +**III.1 access control:** The prevention of unauthorized use of a resource including the prevention of use of a resource in an unauthorized manner.10 + +**III.2 access control server (ACS):** An auxiliary network element that is deployed to enforce and authenticate access to an MS based on **Complex Passwords**, if an NE cannot directly enforce this functionality. + +**III.3 application administrator:** A role that is responsible for the proper activation, maintenance, and usage of an NE/MS application. Application administration tasks include upgrading application software.11 + +**III.4 application security administrator:** A role that is responsible for the proper activation, maintenance, and usage of the application layer security features of a NE/MS. Represents the highest level of security authority for a NE/MS application instance. Tasks may include: + +- Defining and assigning new user and group privileges at the application level; +- Maintaining a record of all requests for login IDs to the application; +- Adding and deleting users at the application level; +- Monitoring all application security logs; +- Configuring application security logging and alarms; +- Managing application security logging processes; +- Terminating user application session. + +**III.5 authentication:** **Authentication** is the act of verifying a claimed identity. + +**III.6 complex passwords:** A password is characterized as "complex" when it has some combination of alphabetic, numeric, and special characters, which should make guessing the password through social engineering or automated means difficult or unlikely. + +10 Taken from ANSI T1.233-1993 (R1999), *Operations, Administration, Maintenance, and Provisioning – Security Framework for Telecommunications Management Network Interfaces*, clause 3.1. + +11 This task may be a function of the **System Administrator**, if **Superuser** authority is necessary to complete this task. Processes may be developed to control access to the **Superuser** account. + +**III.7 control plane:** The **Control Plane** performs call control and connection control functions. Through signalling, the **Control Plane** sets up and releases connections, and may restore a connection in case of a failure.12 + +**III.8 critical security administration actions:** A **System Security Administrator** is responsible for critical security administration actions, which allow the proper activation, maintenance, and usage of the security features of a system (NE/MS). **Critical Security Administration Actions** include, but are not limited to: + +- Defining and assigning user privileges; +- Adding and deleting user IDs; +- Disabling the use of specific user IDs as login IDs; +- Initializing and resetting login passwords; +- Initializing and changing cryptographic keys; +- Setting the system's aging threshold for login passwords; +- Setting the system's limit on the number of failed logins for each login ID; +- Removing a lockout, or change the system's lockout timer value; +- Setting the system's inactivity timer value; +- Setting system security logging and alarm configuration; +- Managing the security logging processes; +- Upgrading security software; +- Terminating any user or system session. + +**III.9 disable/disabled:** When referring to a user ID, a state in which the user ID cannot be used for login until the ID has been enabled by specific action from another user ID with the appropriate authorization privileges (e.g., **System Security Administrator** or **Application Security Administrator**). + +**III.10 element management system (EMS):** The system that performs the OS function in the element management layer. + +**III.11 key strength:** Different cryptographic algorithms have varying degrees of security depending on how difficult they are to break. A cryptographic algorithm is considered strong if it is computationally infeasible to break, that is, it has sufficient complexity that it cannot be broken within a "reasonable" amount of time with available resources either currently or in the foreseeable future. Computational complexity is most often measured in terms of processing complexity, or the amount of time and memory space needed to perform an attack. Although the complexity of an attack remains constant for a particular algorithm and key size, computing power is constantly increasing. Good cryptosystems are designed to be impossible to break with the computing power that is expected to evolve many years in the future. As a result of the rapid development of new technology and cryptanalytic methods, the correct key size for a particular application is continuously changing. + +**III.12 lockout/locked out:** When referring to a user ID, a state in which the user ID cannot be used for login until the lockout state has been removed by one or more appropriate actions. Appropriate actions include, but are not limited to: + +- Automatic resetting after a threshold period of time has elapsed (e.g., after 60 minutes); + +--- + +12 ITU-T Rec. G.8080/Y.1304, *Architecture for the automatically switched optical network (ASON)*, November 2001 (available at ITU Electronic Bookshop). + +- Automatic resetting after successful completion of a predefined reset process (e.g., after the owner correctly answers a scripted set of questions); or +- Resetting by specific action from another user ID with the appropriate authorization privileges (e.g., **System Security Administrator** or **Application Security Administrator**). + +**III.13 management action:** Actions that are undertaken by or on behalf of the **System Administrator**. + +**III.14 management communication:** Any communication of a **Management Action**. + +**III.15 management plane:** The **Management Plane** performs management functions for the **Transport Plane**, the **Control Plane**, and the system as a whole. It also provides coordination between all the planes. Performance, fault, configuration, accounting, and security management functional areas identified in ITU-T Rec. M.3010, *Principles for a Telecommunications Management Network*, are performed in the **Management Plane**.13 + +**III.16 network element (NE):** See ITU-T Rec. M.3010. + +**III.17 network management system (NMS):** The system that performs the OS function in the network management layer. + +**III.18 network element/management system (NE/MS):** A collective term used to describe the entirety of elements within a telecommunications network including NEs, EMSs, NMSs and OSSs. + +**III.19 protected authentication:** Includes **Strong Authentication**, **Two-Factor Authentication**, **Trusted Path Authentication**, cryptographic third-party authentication (e.g., Kerberos), or one-time password authentication. + +**III.20 session:** A sequence of operations, either machine-to-machine or human-to-machine, that are associated with a unique process or user ID. + +**III.21 strong authentication:** **Strong Authentication** is **Authentication** that relies on the use of cryptographic techniques (e.g., public key encryption, symmetric key encryption, digital signatures, and digital hashing techniques). **Strong Authentication** should include two-way authentication, which can be used to prevent active attacks. + +**III.22 strong encryption:** A brute force attack occurs when an attacker tries all possible key combinations using available computing resources to uncover an encrypted message. In this fashion, the correct key can be found on average after one-half of all possible key combinations have been tried. The expected time to test one half of the key combinations is a measure of the strength of the encryption. Therefore, at any given time, **Strong Encryption** mechanisms use algorithms and keys such that it would take any attacker more than 2 years to break with current technology. + +**III.23 system administrator:** A role that is responsible for OS level processes and procedures pertaining to installation, operations, maintenance of the operating platform, installation of software on the platform, and control of **Super user** authority. Tasks may include: + +- Coordinating the installation of a new platform; +- Defining and assigning new user and group privileges at the OS level; +- Maintaining a record of all requests for login IDs to the OS; +- Adding and deleting users at the OS level; + +13 The TMN architecture is described in ITU-T Rec. M.3010, *Principles for a Telecommunication Management Network* and additional details regarding the MANAGEMENT PLANE are provided in the M-series Recommendations. ITU-T Rec. G.8080/Y.1304, *Architecture for the automatically switched optical network (ASON)*, November 2001 (available at ITU Electronic Bookshop). + +- Disabling the use of specific IDs as login IDs (bin, sys, uucp); +- Installing OS upgrades and patches; +- Installing application and database software to the OS; +- Monitoring all system logs; +- Maintaining and monitoring access and changes to **Super user** password; +- Control access to the **Super user** account, allowing appropriate access as the business requires; +- Managing system logging processes; +- Delegating administration authorizations to specific persons in other roles, including **Application Administrators**; +- Terminating any user or system session. + +**III.24 System Security Administrator:** A role that is responsible for the proper activation, maintenance, and usage of the system security features of a NE/MS. Represents the highest level of security authority for a system/application instance. Tasks may include: + +- Defining and assigning new user and group privileges at the OS level; +- Maintaining a record of all requests for login IDs to the OS; +- Adding and deleting users at the OS level; +- Disabling the use of specific IDs as login IDs (bin, sys, uucp); +- Monitoring all system security logs; +- Initializing and changing cryptographic keys; +- Setting the system's aging threshold for login passwords; +- Setting the system's limit on the number of failed logins for each login ID; +- Removing a lockout or changing the system's lockout timer value; +- Setting the system's inactivity timer value; +- Configuring system logging and alarms; +- Managing system security logging processes; +- Delegating security authorizations to specific persons in other roles, including **Application Security Administrators**; +- Terminating any user or system session. + +**III.25 transport plane:** The **Transport Plane** provides bidirectional or unidirectional transfer of user information from one network element to another. It can also provide transfer of some control and network management information. The **Transport Plane** is layered; it is equivalent to the transport network defined in ITU-T Rec. G.8080/Y.1304, *Architecture for the automatically switched optical network (ASON)*.12 + +**III.26 trusted path:** A mechanism by which any user/operator-to-system or system-to-system interactions with a system are secured. This mechanism can be activated only by the user/operator or system and cannot be imitated. A **Trusted Path** can either be a dedicated physical path (i.e., a terminal directly connected to the system) or an encrypted pathway, which includes integrity and replay protection (e.g., "secured" virtual private network, Secure Socket Layer (SSL) tunnel, Secure Shell (SSH)).14 + +14 Adapted from National Computer Security Center, NCSC-TG-004-88, *Glossary of Computer Security Terms*, October 1998 (available at [http://csrc.nist.gov/SBC/PDF/NCSC-TG-004\\_COMPUSEC\\_Glossary.pdf](http://csrc.nist.gov/SBC/PDF/NCSC-TG-004_COMPUSEC_Glossary.pdf)). + +**III.27 two-factor authentication:** **Two-Factor Authentication** is a term commonly used to describe an **Authentication** process that requires the possession of a physical entity (e.g., token or card), and knowledge of a secret (e.g., password or passphrase). + +# BIBLIOGRAPHY + +The items in this bibliography provide additional information on many of the topics addressed in Appendices I and II. + +- ANSI J-STD-025-A-2003, *Lawfully Authorized Electronic Surveillance*. +- ANSI X9.52-1998, *Triple Data Encryption Algorithm Modes of Operation*, (available from the ANSI X9 Electronic Standards Store, [http://webstore.ansi.org/ansidocstore/dept.asp?dept\\_id=80](http://webstore.ansi.org/ansidocstore/dept.asp?dept_id=80)). +- ANSI X9.62-1998, *Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital Signature Algorithm (ECDSA)*, (available from the ANSI X9 Electronic Standards Store, [http://webstore.ansi.org/ansidocstore/dept.asp?dept\\_id=80](http://webstore.ansi.org/ansidocstore/dept.asp?dept_id=80)). +- ANSI T1.210-2004, *OAM&P – Principles of Functions, Architectures, and Protocols for Telecommunications Management Network (TMN) Interfaces*. +- ANSI T1.233-2004, *OAM&P – Security Framework for Telecommunications Management Network (TMN) Interfaces*. +- ANSI T1.252-1996 (R2002), *Operations, Administration, Maintenance and Provisioning OAM&P – Security for the Telecommunications Management Network (TMN) Directory*. +- ANSI T1.261-1998 (R2004), *OAM&P – Security for TMN Management Transactions over the TMN Q3 Interface*. +- ANSI T1.268-2000, *TMN – PKI – Digital Certificates and Certificate Revocation Lists Profile*. +- ANSI X9.31-1998, *Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA)*. +- ATM Forum. AF-SEC-0179.000 (April 2002), *Methods of Securely Managing ATM Network Elements – Implementation Agreements Version 1.1*, (available at ). +- BARRETT (D.), SILVERMAN (R.): *SSH, The Secure Shell: The Definitive Guide*, O'Reilly, January 2001. +- BELLOVIN (S.): *An Issue With DES-CBC When Used Without Strong Integrity, Proceedings of the 32nd Internet Engineering Task Force*, Danvers, MA, April 1995. +- BLEICHENBACHER (D.): *Chosen Ciphertext Attacks Against Protocols Based on the RSA Encryption Standard PKCS#1, Advances in Cryptology-Crypto '98*, Springer LNCS Vol. 1462, pp. 1-12, 1998. +- BONEH (D.): *Twenty Years of Attacks on the RSA Cryptosystem, Notices of the American Mathematical Society (AMS)*, Vol. 46, No. 2, pp. 203-213, February 1999, (available at ). +- BONEH (D.), JOUX (A.), NGUYEN (P.): *Why Textbook RSA and ElGamal Encryption Are Insecure, Advances in Cryptology-Asiacrypt 2000*, Springer LNCS Vol. 1976, pp. 30-43, 2000. +- Federal Communications Commission Docket Number 97-213 *Implementation of the Communications Assistance for Law Enforcement Act*, September 1999. +- General Requirements (GR)-815, *Generic Requirements for Network Element/Network System Security*, March 2002 (available at Telcordia Information SuperStore, ). + +- GR-1194, *Bellcore Operations Systems Security Requirements*, December 1998, (available at Telcordia Information SuperStore, ). +- GUTMANN (P.): Software Generation of Practically Strong Random Numbers, *Seventh USENIX Security Symposium Proceedings*, The USENIX Association, pp. 243-257, 1998, (available at [http://www.usenix.org/publications/library/proceedings/sec98/full\\_papers/gutmann/gutmann.pdf](http://www.usenix.org/publications/library/proceedings/sec98/full_papers/gutmann/gutmann.pdf)). +- Information Assurance Technical Framework Forum (IATF), and [http://www.iatf.net/protection\\_profiles/profiles.cfm](http://www.iatf.net/protection_profiles/profiles.cfm). +- IEEE 1363-2000, *IEEE Standard Specifications for Public Key Cryptography*, (available at IEEE Standards Online, [http://standards.ieee.org/catalog/olis/\\_busarch.html](http://standards.ieee.org/catalog/olis/_busarch.html)). +- IETF RFC 768, *User Datagram Protocol*, J. Postel, August 1980 (available at ). +- IETF RFC 791 (1981), *Internet Protocol – DARPA Internet Program Protocol Specification*, (available at ). +- IETF RFC 792 (1981), *Internet Control Message Protocol – DARPA Internet Program Protocol Specification*, (available at ). +- IETF RFC 793 (1981), *Transmission Control Protocol – DARPA Internet Program Protocol Specification*, (available at ). +- IETF RFC 826 (1982), *An Ethernet Address Resolution Protocol – or – Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware*, (available at ). +- IETF RFC 859 (1983), *Telnet Status Option*, (available at ). +- IETF RFC 959 (1985), *File Transfer Protocol (FTP)*, (available at ). +- IETF RFC 1157 (1990), *A Simple Network Management Protocol (SNMP)*, (available at ). +- IETF RFC 1288 (1991), *The Finger User Information Protocol*, (available at ). +- IETF RFC 1905 (1996), *Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)*, (available at ). +- IETF RFC 2045 (1996), *Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies*, (available at ). +- IETF RFC 2202 (1997), *Test Cases for HMAC-MD5 and HMAC-SHA-1*, (available at ). +- IETF RFC 2222 (1997), *Simple Authentication and Security Layer (SASL)*, (available at ). +- IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*, (available at ). + +- IETF RFC 2271 (1998), *An Architecture for Describing SNMP Management Frameworks*, (available at ). +- IETF RFC 2272 (1998), *Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)*, (available at ). +- IETF RFC 2273 (1998), *SNMPv3 Applications*, (available at ). +- IETF RFC 3414 (2002), *User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)*, (available at ). +- IETF RFC 2275 (1998), *View-based Access Control Model for the Simple Network Management Protocol (SNMP)*, (available at ). +- IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*, (available at ). +- IETF RFC 2402 (1998), *IP Authentication Header*, (available at ). +- IETF RFC 2406 (1998), *IP Encapsulating Security Payload (ESP)*, (available at ). +- IETF RFC 2451 (1998), *The ESP CBC-Mode Cipher Algorithms*, (available at ). +- IETF RFC 2616 (1999), *Hypertext Transfer Protocol (HTTP) – HTTP/1.1*, (available at ). +- IETF RFC 2631 (1999), *Diffie-Hellman Key Agreement Method*, (available at ). +- IETF RFC 3080 (2001), *The Blocks Extensible Exchange Protocol Core*, (available at ). +- IETF RFC 3081 (2001), *Mapping the BEEP Core onto TCP*, (available at ). +- ISO 7498-2:1989, *Information processing systems – Open Systems Interconnection – Basic Reference Model – Part 2: Security Architecture*, (available at ISO Online Store, ). +- ITU-T Recommendation M.3010 (2000), *Principles for a Telecommunications Management Network*, (available at ITU Electronic Bookshop). +- ITU-T Recommendation M.3013 (2000), *Considerations for a Telecommunications Management Network*, (available at ITU Electronic Bookshop). +- JANSEN (W.A.): A Revised Model for Role Based Access Control, *NIST-IR 6192*, July 1998, (available at ). +- JONSSON (J.), KALISKI (B.): On the Security of RSA Encryption in TLS, *Advances in Cryptology-Crypto 2002*, Springer LNCS Vol. 2442, pp. 127-142, August 2002. +- KELSEY (J.), SCHNEIER (B.), FERGUSON (N.): Yarrow-160: Notes on the Design and Analysis of the Yarrow Cryptographic Pseudorandom Number Generator, *Sixth Annual* + +*Workshop on Selected Areas in Cryptography*, Springer-Verlag, August 1999, (available at ). + +- KRAWCZYK (H.): Security Analysis of the Internet Key Exchange's Signature-Based Key Exchange Protocol, *Advances in Cryptology-Crypto 2002*, Springer LNCS Vol. 2442, pp. 143-161, August 2002. +- LENSTRA (A.), VERHEUL (E.): Selecting Cryptographic Key Sizes, *Journal of Cryptology*, Vol. 14, No. 4, pp. 255-293, 2001. +- National Computer Security Center, NCSC-TG-004-88, *Glossary of Computer Security Terms*. October 1988, (available at [http://csrc.nist.gov/SBC/PDF/NCSC-TG-004\\_COMPUSEC\\_Glossary.pdf](http://csrc.nist.gov/SBC/PDF/NCSC-TG-004_COMPUSEC_Glossary.pdf)). +- National Communications System, *Public Switched Network Security Assessment Guidelines*, September 2000, (available at [http://www.ncs.gov/ncs/Reports/NCS\\_Security\\_Assessment\\_Guidelines\\_Version1\\_sep00.pdf](http://www.ncs.gov/ncs/Reports/NCS_Security_Assessment_Guidelines_Version1_sep00.pdf)). +- Object Management Group, *Common Object Request Broker Architecture Security Service Specification, Version 1.8*, March 2002, (available at ). +- Object Management Group, *Common Object Request Broker Architecture Security Service Specification, Version 1.7*, March 2001, (available at ). +- Partnership for Critical Infrastructure Security, *Partnership for Critical Infrastructure Security Common Reference Glossary of Terms, Version 2001-09*, September 2001, (available at ). +- RESCORLA (E.): SSL and TLS, Addison-Wesley, 2001. +- SCHNEIER (Bruce.): Applied Cryptography, Second Edition, John Wiley & Sons, 1996. +- SILVERMAN (R.): The Mythical MIPS Year, *IEEE Computer*, August 1999. +- SILVERMAN (R.): A Cost-Based Security Analysis of Symmetric and Asymmetric Key Lengths, *RSA Laboratories Bulletin*, No. 13, April 2000. +- VAUDENAY (S.): Security Flaws Induced by CBC Padding – Applications to SSL, IPsec, WTLS, *Advances in Cryptology-Eurocrypt 2002*, Springer LNCS Vol. 2332, pp. 534-545, April-May 2002. +- World Wide Web Consortium, *Extensible Markup Language (XML) 1.0*, February 1998, (available at ). +- World Wide Web Consortium, *Simple Object Access Protocol 1.1*, D. Box et al, May 2000, (available at ). +- WU (T.): The Secure Remote Password Protocol, *Proceedings of the 1998 Internet Society Symposium on Network and Distributed Systems Security*, San Diego, California, pp. 97-111, March 1998, (available at ) +- YLÖNEN, T.: SSH – Secure Login Connections Over the Internet, *Sixth USENIX Security Symposium Proceedings*, pp. 37-42, July 1996, (available at [http://www.usenix.org/publications/library/proceedings/sec96/full\\_papers/ylonen/index.html](http://www.usenix.org/publications/library/proceedings/sec96/full_papers/ylonen/index.html)). + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3016.2-200504-I_PDF-E/raw.md b/marked/M/T-REC-M.3016.2-200504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1f6c9e074da76fed024c702b1594bcbe245fd06c --- /dev/null +++ b/marked/M/T-REC-M.3016.2-200504-I_PDF-E/raw.md @@ -0,0 +1,431 @@ + + +International Telecommunication Union + +**ITU-T** + +**M.3016.2** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/2005) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Security for the management plane: Security +services** + +ITU-T Recommendation M.3016.2 + +**ITU-T** + +![ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above the full name. + +ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'. + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3016.2** + +## **Security for the management plane: Security services** + +## **Summary** + +This Recommendation identifies the security services for the management plane in Telecommunication management. It focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the Telecommunication infrastructure. + +###### **Source** + +ITU-T Recommendation M.3016.2 was approved on 13 April 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|--------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Security services ..... | 2 | +| 6.1 Authentication ..... | 3 | +| 6.2 Access control ..... | 5 | +| 6.3 Data confidentiality ..... | 6 | +| 6.4 Data integrity ..... | 6 | +| 6.5 Non-repudiation..... | 6 | +| 6.6 Audit trail..... | 7 | +| 6.7 Alarm reporting ..... | 7 | +| 6.8 Packet inspection ..... | 8 | + +# Introduction + +Telecommunications is a critical infrastructure for global communication and economy. Appropriate security for the management functions controlling this infrastructure is essential. Many standards for Telecommunications network management security exist. However, compliance is low and implementations are inconsistent across the various telecommunications equipment and software components. This Recommendation identifies the security services to allow vendors, agencies, and service providers to implement a secure Telecommunications management infrastructure. Although the present set of security services and mechanisms represent the current understanding of the state of the art, technologies will advance and conditions will change. To be successful, this Recommendation must evolve as conditions warrant. This Recommendation is intended as a foundation. Service providers may include additional security services and mechanisms to meet their specific needs over and above those in this Recommendation. + +This Recommendation is part of the M.3016.x series of ITU-T Recommendations intended to provide guidance and recommendations for securing the management plane of evolving networks: + +ITU-T-T Rec. M.3016.0 – *Security for the management plane: Overview.* + +ITU-T-T Rec. M.3016.1 – *Security for the management plane: Security requirements.* + +ITU-T-T Rec. M.3016.2 – *Security for the management plane: Security services.* + +ITU-T-T Rec. M.3016.3 – *Security for the management plane: Security mechanism.* + +ITU-T-T Rec. M.3016.4 – *Security for the management plane: Profile proforma.* + +## ITU-T Recommendation M.3016.2 + +## Security for the management plane: Security services + +# 1 Scope + +ITU-T Recs M.3016.1, M.3016.2 and M.3016.3 specify a set of requirements, services and mechanisms for the appropriate security of the management functions necessary to support the telecommunications infrastructure. Because different administrations and organizations require varying levels of security support, ITU-T Recs M.3016.1-M.3016.3 do not specify whether a requirement/service/mechanism is mandatory or optional. + +This Recommendation identifies the security services requirements for the management plane in Telecommunication management. It focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the Telecommunication infrastructure. + +This Recommendation is generic in nature and does not identify or address the requirements for a specific Telecommunications Management Network (TMN) interface. + +This Recommendation does not define the security requirements or the security mechanisms for supporting the security services requirements. + +This Recommendation is part of the M.3016.x series of Recommendations. Security requirements, mechanisms, and profile proformas are specified in other parts of the M.3016.x series. + +The Proforma defined in ITU-T Rec. M.3016.4 is provided to assist the organizations, administrations and other national/international organizations, specify the mandatory and optional support of the requirements as well as value ranges, values, etc. to help implement their security policies. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation E.408 (2004), *Telecommunication networks security requirements*. +- ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications*. +- ITU-T Recommendation X.805 (2003), *Security architecture for systems providing end-to-end communications*. + +# 3 Definitions + +This Recommendation uses the following terms from ITU-T Rec. X.800: + +- access control; +- authentication; +- confidentiality; +- data integrity; +- non-repudiation. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------| +| MS | Management System | +| NE | Network Element | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OSI | Open System Interconnection | +| TMN | Telecommunications Management Network | + +# 5 Conventions + +In the ITU-T Recs M.3016.1, M.3016.2 and M.3016.3, a descriptor is used to identify the different requirements, services and mechanisms. The descriptor consists of a three-letter label followed by a number: + +- REQ for requirement; +- SER for service; +- MEC for mechanism. + +# 6 Security services + +Figure 1 describes the relationships between Security objectives, Threats, Risks, Security requirements, and Services. It describes the process how to derive "Security requirements" from "Threats" and "Security objectives" which in turn will be realized by a set of security services. These "Services", which counteract threats, will make use of "Mechanisms" which themselves make use of "Security algorithms". + +![Flowchart of the security framework showing the relationship between Threat, Security requirements, Security services, Security mechanisms, and Security algorithms, with Security objectives influencing Security requirements.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +``` +graph LR; Threat[Threat] --> SR[Security requirements]; SO[Security objectives] --> SR; SR --> SS[Security services]; SS --> SM[Security mechanisms]; SM --> SA[Security algorithms]; +``` + +M.3016.2\_F1 + +Flowchart of the security framework showing the relationship between Threat, Security requirements, Security services, Security mechanisms, and Security algorithms, with Security objectives influencing Security requirements. + +**Figure 1/M.3016.2 – Security framework** + +Table 1 below is reproduced from ITU-T Rec. M.3016.0 (Table 4 in ITU-T Rec. M.3016.0). This table gives an overview of the relationship between Requirements and Security services, and is used as the basis for organization of the other Recommendations in the series. For example, ITU-T + +Rec. M.3016.1 discusses the security Functional Requirements, this Recommendation (ITU-T Rec. M.3016.2) discusses the Security Services, and ITU-T Rec. M.3016.3 discusses specific security mechanisms corresponding to the Security Services. + +This clause only defines the security services, which are covered by standard solutions; other possible services (e.g., detection of denial of service) are left out. + +**Table 1/M.3016.2 – Mapping of security requirements and security services** + +| Functional requirement | Security service | +|--------------------------------------------------|---------------------------------------------------------------------------------| +| Verification of identities | user authentication
peer entity authentication
data origin authentication | +| Controlled access and authorization | access control | +| Protection of confidentiality – stored data | access control
confidentiality | +| Protection of confidentiality – transferred data | confidentiality | +| Protection of data integrity – stored data | access control | +| Protection of data integrity – transferred data | integrity | +| Accountability | non-repudiation | +| Activity logging | audit trail | +| Security alarm reporting | security alarm | +| Security audit | audit trail | +| Protection of the DCN | packet inspection | + +Table 2 outlines the organization of this clause: + +**Table 2/M.3016.2 – Organization of clause 6** + +| Clause | Contents | +|---------------|------------------------------------------------------------------------------------------------------------------------------| +| 6.1 | Discusses authentication services including user authentication, peer entity authentication, and data origin authentication. | +| 6.2 | Discusses access control service. | +| 6.3 | Discusses data confidentiality service. | +| 6.4 | Discusses data integrity service. | +| 6.5 | Discusses non-repudiation service. | +| 6.6 | Discusses audit trail service. | +| 6.7 | Discusses security alarm service. | + +## **6.1 Authentication** + +A TMN should provide capabilities to establish and verify the claimed identity of any actor in the TMN. + +Actors can be human users or entities within the TMN. Verified identities provide the basis of accountability and are fundamental in meeting most of the security requirements listed in this clause. + +The security service to support the requirement is **authentication**. The authentication service delivers proof that the identity of an object or subject has indeed the identity it claims to have. Depending on the type of actor and on the purpose of identification, the following kinds of authentication may be required: + +- user authentication, establishing proof of the identity of the human user or application process; +- peer entity authentication, establishing the proof of the identity of the peer entity during a communication relationship; +- data origin authentication, establishing the proof of identity responsible for a specific data unit. + +Usage of an authentication service establishes the proof for a particular instance of time. To ensure continued proof, the authentication has to be repeated or linked to an integrity service. + +Examples of mechanisms used to implement the authentication service are passwords and Personal Identification Numbers (PINs) (simple authentication) and cryptographic-based methods (strong authentication). + +**Authentication** has two purposes in securing the **Management Plane**: + +- 1) It ensures the identity of the communicating parties, providing a basis for setting up private communications with full data integrity and confidentiality between two systems; and +- 2) It provides a basic mechanism for logging events into a management system and/or auditing the management activities on any system. + +The following layers can provide this service (according to ITU-T Rec. X.800): + +- Network layer (corroboration of the identity of transport layer peers); +- Transport layer (corroboration of the identity of session layer peers); +- Application layer (corroboration of the identity of application processes); +- outside OSI: in the application process itself. + +Considering that the requirement for the TMN will be to identify and authenticate managers and agents and the link of authentication with access control, recommended positions with respect to the OSI stack are the application layer and the application process. + +### 6.1.1 User authentication + +**User Authentication** concerns the **Authentication** of clients involved in the management of the network. In this case, **Authentication** proves the identity of the legitimate user and prevents masquerading attacks by illegitimate users. With proper **Authentication**, it is possible to track activities and restrict users to pre-authorized activities or roles. + +**SER 1:** Each NE/MS providing user access should support a strong authentication service for proof of identity. + +It should be noted that this Recommendation does not require a single sign-on service, but one may be provided in a future Recommendation. However, if one is established, the protocol must still challenge the entity(s) for credentials. A user may not have to enter the credentials if they are securely cached in some way (e.g., a Kerberos mechanism). + +### 6.1.2 Peer entity authentication + +Peer entity authentication concerns the **Authentication** of the peer entity during communication between entities, such as applications, systems or devices. The **Authentication** proves the identity of the peer and prevents masquerading attacks by illegitimate devices. + +Peer entity **Authentication** provides **Authentication** during data communications between systems (e.g., system-to-system, application-to-application), and is the basis for setting up private communications with full data integrity. During data communications, **Authentication** of the sending entity allows the receiver of a message to ascertain the origin of the message. Within a secure communication channel, cryptographic **Authentication** should be associated with each message to bind the sending entity's identity to the message. The receiver will check the cryptographic information supplied with the message to verify the true identity of the sending entity. + +**SER 2:** Each NE/MS providing data communications between systems should support peer entity **Authentication** for communications, and should use X.509 certificate-based systems for **Authentication** or **Protected Authentication**. + +### 6.1.3 Data origin authentication + +Data origin **Authentication** concerns establishing the proof of identity of a system entity that is claimed to be the original source of received data. This **Authentication** provides the substantiating of the source of data is as claimed. This service is usually bundled with a data integrity service. This service is independent of any association between the originator and the recipient, and the data in question may have originated at any time in the past. + +**SER 3:** Each NE/MS providing the identity of a system entity with the substantiation of the source of data should support the data origin **Authentication** service. + +## 6.2 Access control + +A TMN should provide capabilities to ensure that actors are prevented from gaining access to information or resources that they are not authorized to access. + +The security service to meet this requirement is **access control**. The access control service provides means to ensure that subjects access resources only in an authorized manner. There may be re-authentication required due to idle timeouts, or password change requirements. Resources concerned may be the physical system, the system software, applications and data. The access control service can be defined and implemented at different levels of granularity in the TMN: at agent level, object level or attribute level. + +The limitations of access are laid out in access control information, which specify: + +- the means to determine which entities are authorized to have access; +- what kind of access is allowed (reading, writing, modifying, creating, deleting); +- the means to associate the dimension of time with the authenticated entities and the tokens they use for authentication. + +More specific TMN access control can be divided into three types: + +- *Management association access control* + +This service enables access control at the management association level, meaning that the access rights are related to the association itself, i.e., the right to establish the association. + +- *Management notification access control* + +This service enables access control with respect to notifications, i.e., to ensure that notifications are only disclosed to entities authorized to receive them. + +- *Managed resource access control* + +This service provides access control with respect to the resources themselves. + +The identity of the entity trying to gain access needs to be checked before access to the resource is granted. This means that usage of access control is always linked to the usage of an authentication service. + +**SER 4:** Each NE/MS should support access control services for management association, management notification, and management resource access control. + +## 6.3 Data confidentiality + +A TMN should provide capabilities to ensure the confidentiality of stored and communicated data. + +The security services to support the requirement are: **access control** for stored data and **data confidentiality** for communicated data. + +The confidentiality service provides protection against unauthorized disclosure of exchanged data. The following kinds of confidentiality services are distinguished: + +- *Selective field confidentiality* + +This service can be used in the Application layer or in the application process itself, since it is the application process, which can discriminate between fields. + +- *Connection and connectionless confidentiality* + +Considering that end-to-end confidentiality is needed, which excludes the Physical layer and the Data link layer, confidentiality can be provided at the Network layer, the Transport layer, the Presentation layer, the Application layer or in the application process. + +**SER 5:** Each NE/MS should support a data confidentiality service to protect against unauthorized disclosure of connection oriented or connectionless data exchanges and provide confidentiality on selected fields. + +## 6.4 Data integrity + +A TMN should be able to guarantee the integrity of stored and communicated data. + +The security services to support the requirement are: **access control** for stored data and **data integrity** for communicated data. + +The integrity service provides means to ensure the correctness of exchanged data, protecting against modification, deletion, creation (insertion) and replay of exchanged data. The following kinds of integrity services are distinguished: + +- selective field integrity; +- connection integrity without recovery; +- connection integrity with recovery. + +The data integrity service requires the use of a secret value known only to communicating parties. Several protocols use the secret value to create an HMAC-MD5 digest, and this digest is added to each message. + +**SER 6:** Each NE/MS should support a data integrity service to protect against modification, deletion, insertion and replay of exchanged data. + +## 6.5 Non-repudiation + +A TMN should provide the capability that an entity cannot deny the responsibility for any of its performed actions as well as their effects. + +The requirement is supported by the **non-repudiation** service binding the individual (or entity) to the operation performed. The non-repudiation services provide means to prove that exchange of data actually took place. It comes in two forms: + +- non-repudiation: proof of origin; +- non-repudiation: proof of delivery. + +The appropriate combinations of the authentication, access control and audit trail services may be used to achieve another more general realization of non-repudiation. + +**SER 7:** Each NE/MS should support a non-repudiation service to ensure that no entity can deny responsibility for their actions and the effects of those actions. + +## 6.6 Audit trail + +A TMN should provide the capability of storing information about activities on the system with the possibility of tracing this information to individuals or entities. Also a TMN should provide the capability to analyze logged data on security relevant events in order to check them for violations of the security policy. + +A log is a repository for records: it is the OSI abstraction of logging resources in real open systems. Records contain the information that is logged. + +For the purpose of many management functions, it is necessary to be able to preserve information about events that have occurred, or operations that have been performed or attempted by, or on, various resources. + +Furthermore, when such information is retrieved from a log, the manager must be able to determine whether any records were lost or whether the characteristics of the records stored in the log were modified at any time. + +An audit should be seen as an independent review and examination of system records and activities in order to test for adequacy of system controls, to ensure compliance with the established security policy and operational procedures and to detect breaches in security. The result of the Audit would identify changes in control, policy and procedures. + +It is important that each NE/MS provide adequate capabilities to allow investigation, audit, and real-time detection and analysis activities, so that proper remedial actions can be taken. This clause considers security audit logs; however, the specific details of the content and format of the security audit logs are beyond the scope of this Recommendation. + +Note that investigation and forensic analysis activities may include investigation of non-security related OAM&P messages as well as the information stored in the security audit logs described in this clause. Logging of non-security related OAM&P messages, sometimes referred to as "recent change" messages, is required for any actions that are auditable. + +**SER 8:** NE/MS should be able to log any action that changes the security attributes and services, access controls, configuration parameters of the devices, and each login attempt and its result that caused invocation of the system inactivity timer, and any action, which requires auditing. Each NE/MS should support the ability to audit these logs. + +It is recommended that audit log entries be sent to an unalterable audit server after being sequence labelled and cryptographically authenticated (signed) by the NE/MS. + +## 6.7 Alarm reporting + +A TMN should provide the capability to generate alarm notifications on selected events. The user should be able to define the selection criteria. + +The security audit control function is a systems management function describing the notification for collection of security events. The security alarm notification defined by this systems management function provides information regarding the operational condition pertaining to security. + +**SER 9:** Each NE/MS should support an alarm notification service to alert security administrators about operational conditions pertaining to security. + +## 6.8 Packet inspection + +A TMN should provide the capability to inspect packets for packet-based traffic destined to the management plane of any TMN device. The user should be able to define the filtering based on the source and destination network addresses, the protocol and the source and destination ports of a packet. + +Packet inspection is the process of examining the header values of each packet that passes through a network element based on specified match criteria. There could be an action taken based on the results of the packet inspection. + +**SER 10:** Each NE/MS should support a packet inspection service to protect the management plane of the TMN from all traffic that does meet the security policy. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3016.3-200504-I_PDF-E/raw.md b/marked/M/T-REC-M.3016.3-200504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..46403e6112b8274b00f673f31e54eaccd851b3da --- /dev/null +++ b/marked/M/T-REC-M.3016.3-200504-I_PDF-E/raw.md @@ -0,0 +1,842 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3016.3** + +(04/2005) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Security for the management plane: Security mechanism** + +ITU-T Recommendation M.3016.3 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3016.3** + +# **Security for the management plane: Security mechanism** + +## **Summary** + +This Recommendation identifies the security mechanisms for the management plane in the Telecommunications management network. This Recommendation focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the Telecommunication infrastructure. + +## **Source** + +ITU-T Recommendation M.3016.3 was approved on 13 April 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|---------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Security mechanisms ..... | 3 | +| 6.1 User authentication..... | 4 | +| 6.2 Peer entity and data origin authentication ..... | 5 | +| 6.3 Access control ..... | 6 | +| 6.4 Data confidentiality ..... | 7 | +| 6.5 Data integrity ..... | 10 | +| 6.6 Audit trail..... | 11 | +| 6.7 Key exchange ..... | 12 | +| 6.8 Alarm reporting ..... | 12 | +| 6.9 Packet filtering..... | 13 | +| Appendix I – IPsec, SSL/TLS and SSH security mechanisms ..... | 13 | +| I.1 IPsec ..... | 13 | +| I.2 SSL/TLS ..... | 14 | +| I.3 SSH..... | 15 | +| Appendix II ..... | 16 | +| II.1 Objectives ..... | 16 | +| II.2 Network design considerations affecting packet filtering ..... | 16 | +| II.3 Basic packet filtering..... | 19 | +| II.4 Enhanced packet filtering ..... | 19 | +| BIBLIOGRAPHY ..... | 20 | + +# Introduction + +Telecommunications is a critical infrastructure for global communication and economy. Appropriate security for the management functions controlling this infrastructure is essential. Many standards for Telecommunications network management security exist. However, compliance is low and implementations are inconsistent across the various telecommunications equipment and software components. This Recommendation identifies the security mechanisms to allow vendors, agencies, and service providers to implement a secure Telecommunications management infrastructure. Although the present set of security mechanisms represents the current understanding of the state of the art, technologies will advance and conditions will change. To be successful, this Recommendation must evolve as conditions warrant. This Recommendation is intended as a foundation. Service providers may include additional security mechanisms to meet their specific needs over and above those in this Recommendation. + +This Recommendation is part of the M.3016.x series of ITU-T Recommendations intended to provide guidance and recommendations for securing the management plane of evolving networks: + +ITU-T Rec. M.3016.0 – *Security for the management plane: Overview.* + +ITU-T Rec. M.3016.1 – *Security for the management plane: Security requirements.* + +ITU-T Rec. M.3016.2 – *Security for the management plane: Security services.* + +ITU-T Rec. M.3016.3 – *Security for the management plane: Security mechanism.* + +ITU-T Rec. M.3016.4 – *Security for the management plane: Profile proforma.* + +## ITU-T Recommendation M.3016.3 + +# Security for the management plane: Security mechanism + +# 1 Scope + +ITU-T Recs M.3016.1-M.3016.3 specify a set of requirements, services and mechanisms for the appropriate security of the management functions necessary to support the telecommunications infrastructure. Because different administrations and organizations require varying levels of security support, the ITU-T Recs M.3016.1-M.3016.3 do not specify whether a requirement/service/mechanism is mandatory or optional. + +This Recommendation identifies the security mechanisms for the management plane in the Telecommunications management network. This Recommendation focuses specifically on the security aspect of the management plane for network elements (NE) and management systems (MS), which are part of the Telecommunication infrastructure. + +This Recommendation is generic in nature and does not identify or address the security mechanisms for a specific Telecommunications Management Network (TMN) interface. + +The proforma defined in ITU-T Rec. M.3016.4 is provided to assist the organizations, administrations and other national/international organizations, in specifying the mandatory and optional support of the requirements as well as value ranges, values etc., to help implement their security policies. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation G.8080/Y.1304 (2001), *Architecture for the Automatically Switched Optical Network (ASON)*, plus Amendment 2 (2005). +- ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- ITU-T Recommendation M.3016.0 (2005), *Security for the management plane: Overview*. +- ITU-T Recommendation M.3016.2 (2005), *Security for the management plane: Security services*. +- ITU-T Recommendation M.3016.3 (2005), *Security for the management plane: Security mechanism*. +- ITU-T Recommendation M.3016.4 (2005), *Security for the management plane: Profile proforma*. +- ITU-T Recommendation X.509 (2000), *Information technology – Open Systems Interconnection: The Directory: Public-key and attribute certificate frameworks*, plus Corrigendum 1 (2001), Corrigendum 2 (2002), and Corrigendum 3 (2004). +- ITU-T Recommendation X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT Applications*, plus Amendment 1 (1996). + +- ITU-T Recommendation X.805 (2003), *Security architecture for systems providing end-to-end communications*. + +# 3 Definitions + +This Recommendation does not define any new terms. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|---------|------------------------------------------------------------------------------------------| +| CORBA | Common Object Request Broker Architecture | +| DoS | Denial of Service | +| EMS | Element Management System | +| FTP | File Transfer Protocol | +| HTTP | Hypertext Transfer Protocol | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| IPSec | Internet Protocol Security | +| ISO/IEC | International Organization for Standardization/International Electrotechnical Commission | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| MS | Management System; any EMS, NMS, or OSS 1 | +| NE | Network Element | +| NE/MS | NE or MS | +| NMS | Network Management System | +| NTP | Network Time Protocol | +| NTPv3 | NTP version 3 | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OS | Operating System | +| OSS | Operations Support System | +| RFC | Request for Comments | +| SAML | Security Assertion Markup Language | +| SNMP | Simple Network Management Protocol | +| SNMPv3 | Simple Network Management Protocol version 3 | +| SOAP | Simple Object Access Protocol | +| SSH | Secure Shell | +| SSL | Secure Socket Layer | + +--- + +1 OSSs generally can be used in the same context as MSs on any layer of the telecommunications management network hierarchy. + +| | | +|-----|---------------------------------------| +| TCP | Transmission Control Protocol | +| TLS | Transport Layer Security | +| TMN | Telecommunications Management Network | +| XML | Extensible Markup Language | + +# 5 Conventions + +In ITU-T Recs M.3016.1, M.3016.2 and M.3016.3, a descriptor is used to identify the different requirements, services and mechanisms. The descriptor consists of one of the following three-letter label followed by a number: + +- REQ for requirement; +- SER for service; +- MEC for mechanism. + +# 6 Security mechanisms + +This clause contains the specific security mechanisms for operations, administration, maintenance, and provisioning (OAM&P) and operations support system (OSS) security as they specifically apply to Management Plane security for infrastructure, services, and applications. + +Table 1 below is reproduced from ITU-T Rec. M.3016.0 (Table 4 in ITU-T Rec. M.3016.0). This table gives an overview of the relationship between Requirements and Security services, and is used as the basis for organization of the other Recommendations in the series. For example, ITU-T Rec. M.3016.1 discusses the security Functional Requirements, ITU-T Rec. M.3016.2 discusses the Security Services, and this Recommendation (ITU-T Rec. M.3016.3) discusses specific security mechanisms corresponding to the Security Services. + +This clause only defines the security services which are covered by standard solutions; other possible services (e.g., detection of denial of service) are left out. + +**Table 1/M.3016.3 – Mapping of security requirements and security services** + +| Security functional requirement | Security service | +|--------------------------------------------------|---------------------------------------------------------------------------------| +| Verification of identities | user authentication
peer entity authentication
data origin authentication | +| Controlled access and authorization | access control | +| Protection of confidentiality – stored data | access control
confidentiality | +| Protection of confidentiality – transferred data | confidentiality | +| Protection of data integrity – stored data | access control | +| Protection of data integrity – transferred data | integrity | +| Accountability | non-repudiation | +| Activity logging | audit trail | +| Security alarm reporting | security alarm | +| Security audit | audit trail | +| Protection of the DCN | packet inspection | + +Table 2 below outlines the organization of this clause: + +**Table 2/M.3016.3 – Organization of this clause** + +| Clause | Contents | +|--------|---------------------------------------------------------------------------------------------------------| +| 6.1 | Discusses authentication security mechanisms including user authentication, peer entity authentication. | +| 6.2 | Discusses data origin authentication. | +| 6.3 | Discusses access control security mechanisms. | +| 6.4 | Discusses data confidentiality security mechanisms. | +| 6.5 | Discusses data integrity security mechanisms. | +| 6.6 | Discusses audit trail security mechanisms. | + +## 6.1 User authentication + +User authentication is the act of verifying a claimed identity of a person. User authentication may be based on security mechanisms which include: + +- User ID and password combination (with suitably complex passwords) where the password may be a one time password (e.g., SecureID). +- Multi-factor authentication. +- Single sign-on authentication. + +A discussion of user authentication security mechanisms is given in this clause. + +### 6.1.1 User ID and Passwords authentication + +User ID and static passwords may be used for user authentication. User authentication involves proving the true identity of the legitimate system user and preventing masquerading by illegitimate imposters. With proper authentication, it is possible to track activities and apply access control to restrict users to pre-authorized activities or roles as discussed in 6.2. + +User ID and password authentication involves assigning a unique User ID to each user, and then assigning a suitably complex secret password which is used in combination with the User ID to prove identity. + +Passwords should contain enough characters and other randomness to prevent guessing by persons or by machine automated techniques. Examples of characteristics of complex passwords may include such requirements as the following: + +- MEC 1:** Passwords may be required to be a minimum number of characters long (e.g., eight characters). +- MEC 2:** Passwords may be prevented containing certain characters. +- MEC 2a:** Passwords may be prevented from including a repeat or the reverse of the associated user ID. +- MEC 2b:** Passwords may be required not to contain a set of configured character sequences anywhere within them (e.g., words from a dictionary or product names). +- MEC 3:** Passwords may be required to have no more than a certain number of the same characters used consecutively. +- MEC 4:** Passwords may be required to contain at least a certain number of lower case and/or upper case alpha characters. +- MEC 5:** Passwords may be required to contain at least a certain number of numeric characters. + +**MEC 6:** Passwords may be required to contain at least a certain number of special characters. + +Administration of passwords is also very important to ensure a secure authentication system. For example the following password system administration capabilities may be desired: + +**MEC 7:** The password administration system may require the entry of the old password to prevent another user from changing a logged-on user's password without their knowledge. + +**MEC 8:** The system may automatically check to ensure that each new login password differs from the previous password. (Because passwords are typically stored via one-way encryption, the entry of the old password may also be required to allow the system to determine the degree of difference between the old and new passwords2). + +**MEC 9:** The system may support a password history list to prevent password reuse. + +**MEC 10:** The system may enforce the changing of passwords after certain time intervals. + +**MEC 11:** After a certain number of invalid password attempts, the system may restrict further password attempts for a certain amount of time (e.g., 60 minutes) or force a lock out of users. Locked out users may need to contact security administration personnel to clear the locked out condition. + +### 6.1.2 Multi-factor authentication + +Multi-factor authentication refers to an authentication process that requires two or more different types of information or factors to prove identity for user authentication. Requiring multiple factors increases the security of the authentication system by not relying on only a single factor which may be more easily spoofed. + +Authentication factors typically used in multi-factor user authentication systems include: + +Something the user **knows**: e.g., knowledge of a secret password or pass phrase. + +Something the user **has**: e.g., token, smart-card, one-time password generator. + +Something the user **is**: e.g., Fingerprint or other biometric measurement. + +A common multi-factor authentication mechanism is two-factor authentication, which requires two credentials for authentication. A typical example of two-factor authentication is a bank card system whereby the user must have the card in their possession and also prove knowledge of the secret PIN number associated with the card. + +**MEC 12:** Multi-factor authentication with a specified number of factors. + +### 6.1.3 Single sign-on user authentication + +User authentication may support methods for secure single sign-on and X.509 certificate public key infrastructure. In secure single sign-on, the protocol still challenges the entity(s) for credentials; however, a user may not have to enter the credentials because they are securely cached in some way (e.g., Kerberos). Secure single sign-on techniques are used to reduce the necessity of the user having to authenticate to the system multiple times which may become inconvenient. + +**MEC 13:** Single sign-on authentication. + +## 6.2 Peer entity and data origin authentication + +Peer entity authentication mechanisms are used to verify claimed identity between peer systems. Data origin authentication security mechanisms are used to ensure that messages are received from + +--- + +2 As an exception to one-way encryption, symmetrically encrypted passwords may be used for passwords that need to be decrypted for internal, transient use in trusted system-to-system communication or single sign-on. + +the system that claims to have sent them. Peer entity authentication and data origin authentication are closely related, and may be based on security mechanisms which include: + +- Cryptographic authentication mechanisms. +- Trusted path authentication mechanisms. + +A discussion of these authentication security mechanisms is given in this clause. + +### 6.2.1 Cryptographic authentication + +Cryptographic authentication mechanisms provide authentication during data communications between systems (e.g., system-to-system, application-to-application), and is the basis for setting up private communications with full data integrity. During data communications, cryptographic authentication of the sending entity allows the receiver of a message to authenticate the sender's identity (peer entity authentication) and ascertain the origin of the message (data origin authentication). Within a secure communication channel, peer entity and data origin authentication may be based on cryptographic information associated with each message to bind the sending entity's identity to the message. The receiver will check the cryptographic information supplied with the message to verify the true identity of the sending entity. + +Cryptographic techniques that can be used for peer entity and data origin authentication include public key encryption, symmetric key encryption, digital signatures, and digital hashing techniques).3 Cryptographic authentication may be unidirectional where only one end of the conversation is authenticated, or can be bidirectional where both ends are authenticated. Bidirectional authentication is more secure and can be used to help prevent active attacks. + +**MEC 14:** Peer entity and data origin authentication based on public key encryption. + +**MEC 15:** Peer entity and data origin authentication based on symmetric key encryption. + +**MEC 16:** Peer entity and data origin authentication based on digital signatures. + +**MEC 17:** Peer entity and data origin authentication based on digital hashing techniques. + +**MEC 18:** Bidirectional cryptographic authentication. + +### 6.2.2 Trusted path user authentication + +Trusted path authentication is a security mechanism whereby any system-to-system authentication interactions are secured over a secure communication path. This mechanism can be activated only by the system and cannot be imitated. A Trusted Path can either be a dedicated physical path (i.e., a terminal directly connected to the system) or an encrypted pathway which includes integrity and replay protection (e.g., IPsec virtual private network, Secure Socket Layer/Transport Layer Security (SSL/TLS) tunnel, or Secure Shell (SSH)).4 See Appendix I for a discussion of IPsec, SSL/TLS and SSH security protocols. + +**MEC 19:** Peer entity and data origin authentication based on a trusted path. + +## 6.3 Access control + +A TMN may provide capabilities to ensure that actors are prevented from gaining access to information or resources that they are not authorized to access. Access control security mechanisms ensure that only authorized users are allowed to manage system security resources. + +--- + +3 American National Standards Institute T1.243-1995, *Operations, Administration, Maintenance*. + +4 Adapted from National Computer Security Centre, NCSC-TG-004-88, *Glossary of Computer Security Terms*, October 1998 (available at [http://csrc.nist.gov/SBC/PDF/NCSC-TG-004\\_COMPUSEC\\_Glossary.pdf](http://csrc.nist.gov/SBC/PDF/NCSC-TG-004_COMPUSEC_Glossary.pdf)). + +Access control security mechanisms may be provided by a centralized system, often in conjunction with the authentication system. For example, a centralized Remote Access Dial-In User System (RADIUS) server may be used in conjunction with an Lightweight Directory Access Protocol (LDAP) database to provide a centralized system for authentication and access control. + +Access control security mechanisms may have some of the following characteristics: + +- MEC 20:** All administrative actions may be linked to specific individuals. +- MEC 21:** The access control security mechanism may support the concept of "least privilege" (i.e., a person will have a role and will have authorization to view data, modify data, or initiate Management Actions only for those functions allowed by that role). +- MEC 22:** At least some administrator accounts may not be allowed to be locked out due to password related activities such as login failures or timeouts. +- MEC 23:** A number of administrator roles may be defined, each with varying degrees of privilege with respect to critical security management actions. For example, a system may define five administrator user roles. Another system may define three administrator user roles. In either case, the roles may be defined to allow different privileges with respect to the following security actions: + - MEC 23a:** Define and assign user privileges. + - MEC 23b:** Add and delete user IDs. + - MEC 23c:** Initialize and reset login passwords. + - MEC 23d:** Initialize and change cryptographic keys. + - MEC 23e:** Set the system's aging threshold for login passwords. + - MEC 23f:** Set the system's limit on the number of failed logins for each user ID. + - MEC 23g:** Remove a lockout or change the system's Lockout timer value. + - MEC 23h:** Set the system's inactivity timer value. + - MEC 23i:** Set system security logging and alarm configuration. + - MEC 23j:** Manage system security logging processes. + - MEC 23k:** Upgrade security software. + - MEC 23l:** Terminate any user or system session. + - MEC 23m:** Define and assign new user and group privileges at the application level. + - MEC 23n:** Maintain a record of all requests for access to the application. + - MEC 23o:** Add and delete users at the application level. + - MEC 23p:** Monitor all application security logs. + - MEC 23q:** Configure application security logging and alarms. + - MEC 23r:** Manage application security logging processes. + - MEC 23s:** Terminate any user application session. + +## **6.4 Data confidentiality** + +Data confidentiality security mechanisms are used to prevent unauthorized reception of communicated data. Cryptographic security mechanisms to provide data confidentiality are discussed in this clause. + +Data confidentiality is based on cryptographic foundations. Cryptography uses special algorithms that are standards-based and publicly available thereby allowing for widespread scrutiny and ease of implementation. Cryptographic "strength" is based on the cryptographic algorithm used, as well as + +the key size used (i.e., strength refers to the amount of time required to reverse engineer (i.e., find or guess) the key value(s) being used with a specific algorithm). + +Security protocols (e.g., IPsec, SSL/TLS, SSH) typically provide data origin authentication, data integrity, and data confidentiality. (See Annex A for a discussion of IPsec, SSL/TLS and SSH security protocols). Security extensions to other protocols such as Simple Network Management Protocol Version 3 (SNMPv3)5, Common Object Request Broker Architecture (CORBA), Border Gateway Protocol, and Open Shortest Path First are designed to provide data origin authentication and data integrity. + +The methods used to generate, store, distribute, destroy, and revoke cryptographic keys for data confidentiality are of very important. In addition, factors such as key length, key selection, and algorithm selection have a direct bearing on the security strength of a specific cryptosystem. + +### 6.4.1 Symmetric data confidentiality + +Symmetric, or secret key encryption, refers to a cryptographic system where enciphering and deciphering keys are the same. Symmetric cryptosystems require that initial arrangements be made for the individuals to share a unique secret key (e.g., the encryption key). The key must be distributed to the individuals via a secure means, or internally generated (e.g., based on a shared secret root key) because knowledge of the enciphering key implies knowledge of the deciphering key and vice-versa. + +Data confidentiality security mechanisms may be based on symmetric cryptographic algorithms such as Data Encryption Standard (DES), Advanced Encryption Standard (AES), Triple Data Encryption Algorithm (3DES), and other algorithms. + +DES is a 56-bit symmetric encryption algorithm that has been in use for many years. Due to its short key length, DES is vulnerable to key exhaustion using massive parallel computations, and is now considered weak. DES has been deprecated by the US National Institute of Standards and Technology (NIST). + +AES has been chosen by NIST as the standard symmetric encryption algorithm to replace DES for US government applications. AES has key lengths of 128, 192 and 256 bits. + +3DES is essentially the DES algorithm run three times with either two 56-bit keys or three 56-bit keys. 3DES is specified in Federal Information Processing Standard (FIPS) Publication 46-3, *Data Encryption Standard*, October 1999, Appendix 2, Page 22 (available at ). + +3DES can be performed using either two independent 56-bit keys or three independent 56-bit keys, which could be expected to have strength of 112 bits and 168 bits, respectively. However, 3DES is subject to the "meet in the middle" attack, which can reduce two key 3DES strength to only 57 bits rather than the expected 112 bits. The same attack can render three key 3DES strength to only 112 bits rather than the expected 168 bits. Thus for higher security 3DES should be used with three independent keys and the worst case strength should be assumed to be 112 bits. + +The DES algorithm may be performed relatively quickly due to its short 56-bit key, whereas 3DES must essentially perform DES three times and is, hence, much slower. AES, which has a minimum key length of 128 bits, is cryptographically stronger than 3DES and yet may be performed very quickly in both hardware and software. For example, a software implementation of AES may be processed approximately as fast as DES on the same platform, but with far greater cryptographic strength than DES. + +**MEC 24:** Symmetric data confidentiality based on DES cryptographic algorithm. + +--- + +5 SNMPv3 may also provide confidentiality. + +**MEC 25:** Symmetric data confidentiality based on AES cryptographic algorithm. + +**MEC 26:** Symmetric data confidentiality based on 3DES cryptographic algorithm. + +### **6.4.2 Asymmetric data confidentiality** + +An asymmetric encryption system is one in which the enciphering and deciphering keys are related but different. One is made public, whereas the other is kept secret. The public key is different from the private key, and no feasible way is known for deriving the private key from the public key. Public keys are distributed widely; however, the private key is always kept secret. + +Data confidentiality security mechanisms may be based on asymmetric cryptographic algorithms such as Rivest Shamir Adleman (RSA), Elliptic Curve Cryptography (ECC), and others. + +The RSA algorithm is a commonly used asymmetric algorithm which may be used for encryption and digital signatures. RSA is based on the mathematical difficulty of factoring large prime numbers. Common key lengths for the RSA algorithm are 1024 bits and 2048 bits. Note that RSA with a key length of 2048 bits is approximately equivalent in cryptographic strength to 128-bit symmetric encryption. + +Elliptic Curve Cryptography (ECC) is a new method of performing public key cryptography (i.e., comparable to the RSA algorithm). With ECC, an elliptic curve is defined over a certain field; then, the elliptic curve discrete logarithm problem is solved over this field. The main advantage of ECC as compared to other public-key algorithms is the key size. A 160-bit ECC key is approximately equivalent in security to a 1024-bit RSA algorithm key, and a 210-bit ECC key is approximately equivalent to a 2048-bit RSA algorithm. The smaller ECC key results in less computational overhead and a more efficient cryptosystem.6 + +**MEC 27:** Asymmetric data confidentiality based on RSA cryptographic algorithm with specified key length. + +**MEC 28:** Asymmetric data confidentiality based on ECC cryptographic algorithm with specified key length. + +### **6.4.3 Data confidentiality – Summary** + +Examples of algorithms which may be used to provide data confidentiality are presented in tabular format in Table 3. Issues such as formatting, padding, handling error conditions, and choosing appropriate primes and the size of the public exponent, and in the case of ECC, base field and curve must also be considered; however, these issues are outside the scope of this Recommendation. + +**Table 3/M.3016.3 – Example cryptographic algorithms for data confidentiality** + +| Category | Algorithm | Comments | +|----------------------------------|------------------|----------------------------------| +| Symmetric encryption algorithms | AES | Advanced Encryption Standard | +| | 3-DES | Triple Data Encryption Algorithm | +| | DES | Data Encryption Standard | +| Asymmetric encryption algorithms | RSA | Rivest, Shamir, Adleman | +| | ECC | Elliptic Curve Cryptography | + +6 See *Digital Signature Standard*, November 2002, (available at ) for additional details on RSA, Diffie-Hellman, and ECC algorithms. + +## 6.5 Data integrity + +Data integrity security mechanisms are used to guarantee communicated data has not been modified. + +Data integrity is based on cryptographic foundations. Cryptography uses special algorithms that are standards-based and publicly available, thereby allowing for widespread scrutiny and ease of implementation. Security protocols (e.g., IPsec, SSL/TLS, SSH) typically provide data integrity services based on underlying cryptographic algorithms in addition to other security services such as data confidentiality and data origin authentication. (See Appendix I for a discussion of IPsec, SSL/TLS and SSH security protocols.) + +The methods used to generate, store, distribute, destroy, and revoke cryptographic keys for data integrity are of paramount importance. In addition, factors such as key length, key selection, and algorithm selection have a direct bearing on the security strength of a specific cryptosystem. + +### 6.5.1 Symmetric data integrity + +Symmetric, or secret key data integrity, refers to a cryptographic system where keys used for data integrity are the same for both the information sender and receiver. Symmetric cryptosystems require that initial arrangements be made for the individuals to share a unique secret key (e.g., the verification key). The key must be distributed to the individuals via a secure means, or internally generated (e.g., based on a shared secret root key). + +Symmetric data integrity security mechanisms for arbitrary length messages may be based on keyed message digest algorithms combined with hashing functions. Examples of keyed message digest algorithms include the Hashed Message Authentication Code with Message Digest 5 (HMAC-MD5-96)7 algorithm and the Hashed Message Authentication Code with Secure Hash Algorithm 1 (HMAC-SHA-1-96)8. + +**MEC 29:** Symmetric data integrity based on HMAC-MD5-96 cryptographic algorithm. + +**MEC 30:** Symmetric data integrity based on HMAC-SHA-1-96 cryptographic algorithm. + +### 6.5.2 Asymmetric data integrity + +An asymmetric data integrity system is one in which the signing and verification keys are related but different. The verification key is made public, whereas the signing key is kept secret. The signing key is different from the verification key, and no feasible way is known for deriving the signing key from the verification key. Verification keys are distributed widely; however, the signing key is always kept secret. + +Data integrity security mechanisms may be based on asymmetric cryptographic algorithms such as the Digital Signature Algorithm (DSA) and the Rivest Shamir Adleman (RSA) algorithm. + +With asymmetric data integrity security mechanisms, the sender signs a message digest with a signing (private) key and the verification (public) key is used by the receiver to verify that the message digest was signed by the claimed originator. + +**MEC 31:** Asymmetric data integrity based on DSA cryptographic algorithm with specified key length. + +**MEC 32:** Asymmetric data integrity based on RSA cryptographic algorithm with specified key length. + +--- + +7 Internet Engineering Task Force Request for Comment 2403, *The Use of HMAC-MD5-96 within ESP and AH*, C. Madson, R. Glenn, November 1998. + +8 Internet Engineering Task Force Request for Comment 2404, *The Use of HMAC-SHA-1-96 within ESP and AH*, C. Madson, R. Glenn, November 1998. + +### 6.5.3 Data integrity – Summary + +Examples of algorithms which may be used to provide data integrity are presented in tabular format in Table 4. Issues such as formatting, padding, handling error conditions, and choosing appropriate primes must also be considered; however, these issues are outside the scope of this Recommendation. + +**Table 4/M.3016.3 – Example cryptographic algorithms for data confidentiality** + +| Category | Algorithm | Comments | +|--------------------------------------------|---------------|------------------------------------------------------------------| +| Asymmetric message verification algorithms | DSA | Digital Signature Algorithm. | +| Symmetric message verification algorithms | HMAC-MD5-96 | Hashed Message Authentication Code with Message Digest 5. | +| | HMAC-SHA-1-96 | Hashed Message Authentication Code with Secure Hash Algorithm 1. | + +## 6.6 Audit trail + +Network elements and management systems should provide adequate capabilities to allow investigation, audit, and real-time detection, analysis and protection activities, so that proper remedial actions can be taken. This clause considers security mechanisms used for such security audit logs. The specific details of the content and format of the security audit logs are beyond the scope of this Recommendation. + +Security audit logs may be kept by network element and management systems. These security audit logs may be kept locally, and may be transmitted to a centralized log repository and/or log analysis device. + +Syslog is one common mechanism used for transmitting security audit logs from local storage to a centralized log repository. + +In general, a device may be able to log any action that changes the security attributes and services, access controls, or other configuration parameters of the devices; each login attempt and its result; and each logout or session termination, whether remote or console. Logging of non-security related OAM&P messages, sometimes referred to as "recent change" messages, is required for any actions that are auditable. + +Audit log entries may be sent to an unalterable audit server after being sequence labelled and cryptographically authenticated (signed) by the network element or management system. Security audit logs may be sent to a central repository over a trusted path. To ensure accurate analysis of actions, the date and time of numerous log sources must be synchronized accurately and securely (e.g., NTPv3). + +**MEC 33:** Security audit logs based on Syslog. + +**MEC 34:** Security audit log entry containing the following information: + +**MEC 34a:** A description of the action or the actual action that is being logged. + +**MEC 34b:** The identity and security level of the user or process that initiated the action. + +**MEC 34c:** The date and time the action occurred. + +**MEC 34d:** Network source and destination information, if applicable (e.g., when logging in). + +**MEC 34e:** An indication of the success or failure of the activity. + +**MEC 34f:** Any action that requires auditing. + +**MEC 35:** Security audit logs sent to an unalterable audit server. + +**MEC 36:** Security audit logs cryptographically signed. + +**MEC 37:** Security audit logs sent to a central repository over a trusted path. + +## **6.7 Key exchange** + +For symmetric data confidentiality and symmetric data integrity applications, cryptographic keys must be securely exchanged between endpoints. The keys for such symmetric algorithms should normally be exchanged in a process tightly bound to authentication, lest an attacker gets between the authentication and key distribution processes. + +The methods used to generate, store, distribute, destroy, and revoke these cryptographic keys are of paramount importance. In addition, factors such as key length, key selection, and algorithm selection have a direct bearing on the amount of security a cryptosystem provides. + +Various methods can be used for provisioning and/or exchanging cryptographic keys. One conceptually simple method is pre-shared key exchange whereby keys are sent out-of-band and provisioned into each endpoint as necessary. For example, keys can be selected and configured into endpoints by network administrators upon commissioning. Pre-shared key exchange may be acceptable for a small number of endpoints however this does not scale well for a large numbers since it becomes very cumbersome to generate and configure large numbers of keys. + +Asymmetric algorithms such as the Rivest, Shamir, Adleman (RSA) can be used in support of key exchange services. Using RSA, one endpoint selects symmetric cryptographic keys and distributes these to other endpoints under protection of the RSA encryption algorithm. Using this method, the asymmetric algorithm should have an appropriate key length in order to protect the symmetric keys being sent. To protect a 128-bit symmetric key, for example, the RSA algorithm should use a key length 2048 bits or greater to be roughly equivalent in cryptographic strength to the 128-bit symmetric key encryption. + +The Diffie-Hellman key agreement algorithm is a common method of key distribution. Using the Diffie-Hellman algorithm, endpoints independently derive secret symmetric cryptographic keys over a public network. Only intermediate results are sent between endpoints during the Diffie-Hellman process, and the secret key is never revealed. With appropriate Diffie-Hellman prime number selection, it is computationally unfeasible for attackers to derive the secret key from the intermediate results. + +For RSA and Diffie-Hellman algorithms, issues such as choosing appropriate primes, choosing public exponents, and handling error conditions must also be considered. + +**MEC 38:** Cryptographic key exchange based on pre-shared keys. + +**MEC 39:** Cryptographic key exchange based on asymmetric RSA algorithm, with a specified RSA key length. + +**MEC 40:** Cryptographic key exchange based on the Diffie-Hellman key agreement algorithm with a specified Diffie-Hellman prime group. + +## **6.8 Alarm reporting** + +Security alarms should be sent to administrators on the detection of any security violation or the inability to continue to write audit logs. + +**MEC 41:** Security alarms reporting mechanisms such as X.736. + +## 6.9 Packet filtering + +In order to protect the DCN from attack and the loss of information about the DCN, packet filtering should be used for devices with packet-based connectivity. + +**MEC 42:** Packet filtering based on one or more of the following inspection criteria: + +**MEC 42a:** Source IP Address. + +**MEC 42b:** Destination IP Address. + +**MEC 42c:** Protocol. + +**MEC 42d:** Source Port. + +**MEC 42e:** Destination Port, + +and providing one or more of the following actions: + +**MEC 42f:** Pass. + +**MEC 42g:** Drop. + +**MEC 42h:** Modify. + +**MEC 42i:** Forward. + +potentially with the capability to consider previous decisions (i.e., stateful). + +# Appendix I + +## IPsec, SSL/TLS and SSH security mechanisms + +## I.1 IPsec + +IPsec addresses security at the IP layer, provided through the use of a combination of cryptographic and protocol security mechanisms. IPsec protocol runs between the Network layer (Layer 3) and the Transport layer (Layer 4) and can be used to protect any type of data traffic (TCP or UDP) and is independent of applications. IPsec is designed to provide interoperable, high quality, cryptographically-based security for IPv4 and IPv6. The set of security services offered by IPsec includes: + +- a) Data integrity; +- b) Data origin authentication based on IP address; +- c) Machine-to-machine authentication; +- d) Anti-Replay Protection; +- e) Data confidentiality; +- f) Cryptographic key exchange. + +These objectives are met through the use of two traffic security services, the Authentication Header (AH) and the Encapsulating Security Payload (ESP), and through the use of cryptographic key management procedures and protocols. AH service provides data origin authentication, machine-to-machine authentication and data integrity for IP packets. ESP service provides data confidentiality service in addition to data origin authentication, machine-to-machine authentication and data integrity for IP packets. IPsec mechanisms also designed to be cryptographic algorithm-independent to permit selection of different sets of algorithms without affecting the other parts of the implementation. + +Key Management is provided by the Internet Key Exchange (IKE) protocol. Both manual and automatic mechanisms for key negotiation between endpoints are provided. Automatic key negotiation can be based on pre-shared keys (e.g., passwords) or X.509 certificates. + +References [RFC 2401], [RFC 2402], [RFC 2403], [RFC 2404], [RFC 2405], [RFC 2406], [RFC 2407], [RFC 2408], [RFC 2409], [RFC 2410], [RFC 2411], [RFC 2412], [RFC 3602], [RFC 2451], [FIPS-197]. + +### 1.2 SSL/TLS + +The Secure Socket Layer (SSL) security protocol provides data encryption, server authentication, message integrity, and optional client authentication for a TCP/IP connection at the transport layer (Layer 4). SSL is currently at revision 3.0. Transport Layer Security (TLS) is the IETF standardized version of SSL which includes security enhancements over SSL including: + +- Required Diffie-Hellman and DSA digital signatures algorithm (DSA) support, with optional RSA support. +- Use of stronger hashed message authentication algorithm (HMAC) instead of a non-standard SSL defined MAC algorithm. +- Modified key generation algorithm which uses MD5 (Message Digest 5) and SHA-1 (Secure Hash Algorithm 1) with the HMAC. + +The SSL/TLS protocol runs above the Network Layer (Layer 4) and works with Transport Control Protocol (TCP) protocol only and cannot work with User Datagram Protocol (UDP). The application layer protocols that commonly run on top of SSL/TLS include, but are not limited to, Hypertext Transport Protocol (HTTP), the Lightweight Directory Access Protocol (LDAP), and the Internet Messaging Access Protocol. Higher application-level protocol can work above SSL/TLS without any regard for SSL/TLS; however, the application level must be linked to SSL/TLS through the use of I/O callbacks. + +The SSL/TLS protocol provides three security functions for TCP traffic: data confidentiality, data integrity and authentication. + +The SSL/TLS security protocol architecture provides two layers which run over TCP: + +- The SSL/TLS Upper Layer Protocols; +- SSL/TLS Record Protocol. + +The SSL/TLS Upper Layer Protocols include the SSL/TLS Handshake Protocol, SSL/TLS Cipher Change Protocol, and the SSL/TLS Alert Protocol for notifications. SSL/TLS sessions are initially created by the SSL/TLS handshake protocol which provides: + +- a) Negotiation of authentication and security mechanisms. +- b) Authentication of client and server. (Using the server and client public/private keys.) +- c) Establishment of security keys. + +Once the SSL/TLS session is established, the SSL/TLS Record Protocol is used for bulk data transport services. The SSL/TLS Record Protocol provides: + +- a) Data origin authentication based on the server keys. +- b) Data integrity. +- c) Confidentiality. + +Note that SSL is now at version 3 (SSLv3), and TLS is at version 1. Earlier versions of SSL and TLS are not recommended. + +SSL/TLS allows either unidirectional authentication where the server is authenticated to the client only, or bidirectional authentication where both client and server authenticate to each other. Unidirectional authentication is the usual method used in the public internet. For network management applications, bidirectional authentication is recommended to allow both parties to know they are communicating with the desired endpoint. + +References [RFC 2246], [RFC 3546], [SSL V3]. + +### **I.3      SSH** + +SSH is an Application Layer (Layer 7) security protocol commonly used to directly replace insecure protocols Telnet and File Transfer Protocol (FTP) protocols. Telnet and FTP are insecure protocols which transmit passwords and all other data in the clear. SSH can also be used to protect other protocols through the use of port forwarding, so it can be used as a general network security protocol. + +There are two versions of SSH: SSHv1 and SSHv2. SSHv1 was developed in 1998 and is now considered insecure/obsolete. + +Secure Shell 2 features are: + +- Full replacement for Telnet, Rlogin, Rsh, Rcp, and FTP protocols to provide secure file transfer and file copying. +- Automatic authentication of users. (No passwords sent in clear-text.) +- Bidirectional authentication (both the server and the client are authenticated). +- Tunnelling of arbitrary TCP/IP-based applications through the use of port forwarding. +- Encryption of data for data confidentiality. +- Multiple authentication options including passwords, public key, and SecureID authentication. +- Multiple ciphers suites available. + +The SSHv2 architecture consists of three major components: + +- The Transport Layer Protocol [SSH-TRANS] provides server authentication, data confidentiality, and data integrity. It may optionally also provide compression. +- The User Authentication Protocol [SSH-USERAUTH] authenticates the client-side user to the server. +- The Connection Protocol [SSH-CONNECT] multiplexes the encrypted tunnel into several logical channels. + +The connection protocol provides channels that can be used for a wide range of purposes. Standard methods are provided for setting up secure interactive shell sessions and for forwarding ("tunnelling") arbitrary TCP/IP ports and connections. + +Port number 22 has been registered with the IANA as the standard port to use for SSHv2 applications. + +References [SSH-ARCH], [SSH-TRANS], [SSH-USERAUTH], [SSH-CONNECT]. + +# Appendix II + +This appendix describes a mechanism for Packet Filtering to enhance the security of the Data Communications Network (DCN). The Data Communications Network (DCN) is the network used to connect the management applications (usually located in the Network Operations Centre) to the network elements for centralized service provisioning, alarm monitoring, testing, billing, and other network management activities. Sections 2.8–2.10 of RFC 3871 provide a set of requirements for packet filtering for large Internet Service Provider IP network infrastructure. This contribution draws on RFC 3871 to define filtering recommendations for the DCN. + +Packet filtering is the process of deciding the disposition of each packet that passes through a network element based on specified match criteria9. There could be several dispositions, e.g., Pass, Drop, Forward (direct it to elsewhere), etc. Packet filtering provides the basic protection mechanism determining what traffic passes into or through the network element or management system. + +The main concern is filtering traffic from other networks (e.g., networks carrying customer traffic, peer management networks) onto the DCN. In addition, certain elements of the DCN may need to be segregated from other elements. Therefore, filtering can be used between different sub-networks (or domains) of the DCN. + +## II.1 Objectives + +Broad objectives for the packet filtering mechanism are to: + +- 1) Protect the DCN infrastructure from customer traffic. The protection should include proper sharing of common resources to avoid degradation or denial of service. +- 2) Protect the DCN infrastructure from peer networks. +- 3) Prevent traffic on the DCN that is not in compliance with the applicable security policy from propagating any further through the DCN infrastructure. + +## II.2 Network design considerations affecting packet filtering + +This appendix does not imply requirements for design of the DCN; however, the design and deployment of the DCN will affect the deployment of and requirements for packet filtering in the network. Figure II.1 shows a typical DCN design. + +--- + +9 This description of packet filtering is very similar to packet routing; however, this appendix focuses on packet filtering and does not address packet routing. + +![Figure II.1/M.3016.3 – Generic DCN illustration. This diagram shows a network architecture with various components and their connections. At the top left, 'Other nets' and 'Other CO/POPs' are connected to a 'Service transport' cloud. Below them, a 'Service centre' contains two 'Softswitch' units. To the right, 'Access CO/POPs' contain 'Access NE A' and 'Access NE B' connected to a 'Customer'. A 'Service transport' cloud and an 'IP DCN' cloud are also present. In the center is a 'Core IP DCN' cloud connected to multiple 'Firewall' units (represented by brick wall icons). Below the Core IP DCN, a 'Data centre' contains 'Call detail', 'Monitoring', 'Provisioning', and 'Traffic eng.' units. Other connections include 'ASPs?', 'Enterprise', 'Partners', 'Internet', and two 'NOC technician' boxes. A legend at the bottom left defines line types: blue dashed for 'User data', red dashed for 'In-band DCN', and blue dashed with a red stripe for 'Out-of-band DCN'. A legend at the bottom center defines filter types: green rectangle for 'Basic Pkt filter' and brick wall for 'Enhanced Pkt filter' / 'Firewall'. The diagram is labeled 'M.3016_FII.1' in the bottom right.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure II.1/M.3016.3 – Generic DCN illustration. This diagram shows a network architecture with various components and their connections. At the top left, 'Other nets' and 'Other CO/POPs' are connected to a 'Service transport' cloud. Below them, a 'Service centre' contains two 'Softswitch' units. To the right, 'Access CO/POPs' contain 'Access NE A' and 'Access NE B' connected to a 'Customer'. A 'Service transport' cloud and an 'IP DCN' cloud are also present. In the center is a 'Core IP DCN' cloud connected to multiple 'Firewall' units (represented by brick wall icons). Below the Core IP DCN, a 'Data centre' contains 'Call detail', 'Monitoring', 'Provisioning', and 'Traffic eng.' units. Other connections include 'ASPs?', 'Enterprise', 'Partners', 'Internet', and two 'NOC technician' boxes. A legend at the bottom left defines line types: blue dashed for 'User data', red dashed for 'In-band DCN', and blue dashed with a red stripe for 'Out-of-band DCN'. A legend at the bottom center defines filter types: green rectangle for 'Basic Pkt filter' and brick wall for 'Enhanced Pkt filter' / 'Firewall'. The diagram is labeled 'M.3016\_FII.1' in the bottom right. + +**Figure II.1/M.3016.3 – Generic DCN illustration** + +Three types of DCN design are generally recognized: + +- In-band Management: DCN uses reserved bandwidth from the Service Network used to carry customer data. For example, a VLAN on an Ethernet link could be dedicated to management traffic or an IPSec or SSH connection could be used over an Internet connection (e.g., for the NOC Technician in Figure II.1 connected over the Internet). +- Out-of-band Management: The DCN is a completely different network from the Service network carrying customer traffic. This network could be overlaid on top of the same physical network that also carries user data traffic. +- Hybrid: Combines in-band and out-of-band approaches. + +The comparison & general discussion of these types of management architectures are beyond the scope of this Recommendation (see section 2.2 of RFC 3871); however, utilization of one or the other will affect filtering requirements. + +The rationale used to create DCNs will vary based on the type of network elements supported, operational procedures and preferences, network topologies, economics, etc. Network capacity, resiliency, and security are issues that are considered for each approach. + +Next-generation managed service offerings will be implemented using packet-based (e.g., frame-relay, ATM, IP, MPLS, Ethernet) transport equipment. The advent of such services makes it necessary to manage the access equipment (CPE). + +It may be necessary to use a hybrid model using out-of-band management to the points-of-presence (POP) and in-band management from the POP to the CPE access devices, as it may not be economically feasible to extend the out-of-band management all the way to the CPE access device. Access NE B illustrates the latter in Figure II.1. In this case, enhanced filtering (e.g., firewall) can + +be used to protect the DCN from the CPE. Other examples of the use of an in-band connection are the management of a remote, isolated POP where it is infeasible to build out a separate network and the use of the service network as a backup to the DCN. + +The use of packet filtering also assumes the address space used by the DCN is separate from that assigned to customers and there is no need for the traffic to flow between these two domains. Separation of address space simplifies development of packet filters to block customer traffic from accessing management resources. The easiest approach is to block all traffic destined to the DCN that originates from outside the DCN to protect the management infrastructure from customer traffic. However, some traffic may need to be exchanged between outside networks and the DCN in some cases, e.g., management information exchange between two Service Providers (e.g., the DCC at a mid-point meet between two SPs). + +Thus provision needs to be made to allow some restricted traffic to flow between domains and more controls (e.g., enhanced packet filtering) are needed to provide adequate security for the DCN. + +Figure II.1 illustrates a DCN design based on the assumptions above. The Service Transport (blue) carries the customer traffic. The DCN (red) carries the management traffic. The Service Centre contains servers, etc., that provide services to the customers and that the customers have access to (e.g., soft switches). The Data Centre contains servers and other operations systems used to manage and monitor the network and is not directly accessible to customers. The connection from the DCN to the Network Elements can use IP, X.25, async or ISO CLNS. + +Providing ingress packet filtering on DCN/Service network boundary is a basic requirement for providing DCN security at the Access NE. However, such basic packet filtering may not be sufficient since attacks could also come from a compromised NE or host within the DCN. Therefore, suitable packet filtering mechanisms may need to be strategically implemented at multiple points in the DCN to ensure compliance with the applicable security policy. In addition, enhanced packet filtering may be needed where the DCN connects to external networks (e.g., Internet, SP's enterprise network, partners, etc.). + +While packet filtering is a component of a network security strategy, it must be used within the context of overall network security principles and strategies including, e.g., compartmentalization and defense-in-depth. So, while a good security strategy will include security requirements on the hosts themselves (e.g., soft switches) and compartmentalization of the network, these are outside the scope of this Recommendation. + +To protect the management infrastructure, and the DCN in general, it is useful for the network operator to discard certain packets received from outside the perimeter of the DCN (i.e., from peers and customers). For example, packets with invalid source IP addresses and packets destined for IP addresses used exclusively on the DCN should not be permitted inside the perimeter of the DCN. This function is called ingress filtering. These requirements are derived from [RFC 3871] and [RFC 2827]. + +There are two categories of packet filtering: + +- Basic Packet Filtering based on the packet header information including the capability to detect and block packets with spoofed source address. +- Enhanced Packet Filtering, including: + - Stateful examination of packets where the context or state information is also used in making the filtering decisions. + - Dynamic filtering for specific protocols where filters are opened dynamically based on the information carried in the protocol payload. + - Deep packet inspection where the application level protocols are examined for any protocol anomaly, unusual or suspicious contents. + +## **II.3 Basic packet filtering** + +Equipment connecting to the DCN should have an option to drop packets received from external-facing interfaces (e.g., customers and peers) containing invalid source IP addresses. Invalid source IP addresses can consist of: + +- Bogon addresses (see Section 1.8 of RFC 3871). +- Martians (see Section 1.8 of RFC 3871). +- IP addresses not assigned to the customer (or not valid for the peer to send). + +The packet filtering mechanism should be able to filter traffic addressed to the address blocks allocated to the DCN and originated from outside (e.g., from customers) based on the attributes specified in MEC 42. + +The packet filtering mechanism should provide accurate per-interface traffic statistics. The level of granularity of statistics may vary depending on packet filtering mechanism. + +Equipment should be able to filter traffic from outside the DCN (e.g., from customers), that is, addressed directly to a Network Element via any of its interfaces, including loopback interfaces, based on attributes specified in MEC 42. + +The packet filtering mechanism may support the multiple security domains concept of the TMN model where all elements in a security domain are mandated to follow a common security policy. + +Equipment may have the capability to generate suitable alarms based on the traffic, exceptions and its operating conditions. + +## **II.4 Enhanced packet filtering** + +These recommendations should be considered where a high degree of overlap exists between the user and management traffic, i.e., the user and management traffic are not segregated right at the edge of the network, and where the DCN connects directly to other networks. In addition, these filtering capabilities should be used at the boundaries of protected sub-networks (e.g., between the DCN and Data Centre). + +The mechanism should examine the application protocols used on the DCN for any protocol anomaly or abnormal behavior and should suitably block such traffic. + +The mechanism should examine the content of the traffic on the DCN for malicious content like viruses, worms, Trojans, etc., wherever applicable. + +The mechanism should provide protection for applicable types of Denial of Service (DoS) attacks. + +The mechanism should be capable of stateful filtering, i.e., the session information is used for packet filtering. Return traffic for a session should always be allowed to pass. + +The mechanism should support dynamic pinhole capability for all protocols used in the network carrying the port information in their payload, e.g., FTP, SIP, etc. The packet filtering mechanism should examine the port information in the payload and open the communication on the specified port (dynamic pinhole) for the life of the session. In case of abrupt termination of the session, a suitable time-out mechanism shall exist to close the port. + +The mechanism should support protocol enforcement including dropping of malformed packets or improper session establishment, etc. + +Other recommended filtering capabilities can be found in sections 2.7–2.10 of RFC 3871. + +# BIBLIOGRAPHY + +- [RFC 2827] IETF RFC 2827 (2000), *Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing*. +- [RFC 2401] IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*, +- [RFC 3704] IETF RFC 3704 (2004), *Ingress Filtering for Multihomed Networks*. +- [RFC 3871] IETF RFC 3871 (2004), *Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure*. +- [NDS/IP] 3GPP TS 33.210 (2001), *3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Network Domain Security; IP network layer security*. +- [RFC 2402] IETF RFC 2402 (1998), *IP Authentication Header*, +- [RFC 2403] IETF RFC 2403 (1998), *The Use of HMAC-MD5-96 within ESP and AH*, +- [RFC 2404] IETF RFC 2404 (1998), *The Use of HMAC-SHA-1-96 within ESP and AH*, +- [RFC 2405] IETF RFC 2405 (1998), *The ESP DES-CBC Cipher Algorithm with Explicit IV*, +- [RFC 2406] IETF RFC 2406 (1998), *IP Encapsulating Security Payload (ESP)*, +- [RFC 2407] IETF RFC 2407 (1998), *The Internet IP Security Domain of Interpretation for ISAKMP*, +- [RFC 2408] IETF RFC 2408 (1998), *Internet Security Association and Key Management Protocol (ISAKMP)*, +- [RFC 2409] IETF RFC 2409 (1998), *The Internet Key Exchange (IKE)*, +- [RFC 2410] IETF RFC 2410 (1998), *The NULL Encryption Algorithm and Its Use with IPsec*, +- [RFC 2411] IETF RFC 2411 (1998), *IP Security Document Roadmap*, +- [RFC 2412] IETF RFC 2412 (1998), *The OAKLEY Key Determination Protocol*, +- [RFC 3602] IETF RFC 3602 (2003), *The AES-CBC Cipher Algorithm and Its Use with IPsec*, +- [RFC 2451] IETF RFC 2451 (1998), *The ESP CBC-Mode Cipher Algorithms*, +- [RFC 2246] IETF RFC 2246 (1999), *The TLS Protocol, Version 1.0*, +- [RFC 3546] IETF RFC 3546 (2003), *Transport Layer Security (TLS) Extensions*, + +- [SSL V3] *Secure Socket Layer Version 3.0 Specification*, Netscape Communications. + +- [SSH-ARCH] YLONEN (T.): *SSH Protocol Architecture*, I-D draft-ietf-architecture-15.txt, October 2003. +- [SSH-TRANS] YLONEN (T.): *SSH Transport Layer Protocol*, I-D draft-ietf-transport-17.txt, October 2003. +- [SSH-USERAUTH] YLONEN (T.): *SSH Authentication Protocol*, I-D draft-ietf-userauth-18.txt, September 2002. +- [SSH-CONNECT] YLONEN (T.): *SSH Connection Protocol*, I-D draft-ietf-connect-18.txt, October 2003. +- [FIPS-46-3] Data Encryption Standard. (Describes both DES and 3DES). + +- [FIPS-197] Advanced Encryption Standard (AES), FIPS Publication 197, National Institute of Standards and Technology, November 2001. + +- [RFC 2437] IETF RFC 2437 (1998), *PKCS #1: RSA Cryptography Specifications Version 2.0*, + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3016.4-200504-I_PDF-E/raw.md b/marked/M/T-REC-M.3016.4-200504-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..597f79d775ba551b392cde48502cf62c79ac994a --- /dev/null +++ b/marked/M/T-REC-M.3016.4-200504-I_PDF-E/raw.md @@ -0,0 +1,356 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3016.4** + +(04/2005) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Security for the management plane: Profile proforma** + +ITU-T Recommendation M.3016.4 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3016.4** + +# **Security for the management plane: Profile proforma** + +## **Summary** + +This Recommendation defines the Conformance Profile proforma for organizations using ITU-T Recs M.3016.1-M.3016.3 for specifying the telecommunications management plane requirements. By completing the proforma in this Recommendation, different profiles are specified. + +## **Source** + +ITU-T Recommendation M.3016.4 was approved on 13 April 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | Page | +|------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 2 | +| 6 Basis of profile proforma for security requirements..... | 2 | +| 6.1 Overview ..... | 2 | +| 6.2 Guidelines and instructions for proforma specification ..... | 2 | +| 7 Proforma ..... | 3 | +| 7.1 M.3016.1 security requirements ..... | 3 | +| 7.2 M.3016.2 security services ..... | 5 | +| 7.3 M.3016.3 security mechanisms ..... | 6 | + + + +## ITU-T Recommendation M.3016.4 + +# Security for the management plane: Profile proforma + +# 1 Scope + +ITU-T Recs M.3016.1-M.3016.3 specify a set of requirements, services, and mechanisms for the appropriate security of the management functions necessary to support the telecommunications infrastructure. Because different administrations and organizations require varying levels of security support, ITU-T Recs M.3016.1-M.3016.3 do not specify whether a requirement/service/mechanism is mandatory or optional. + +This Recommendation specifies the Proforma for the security requirements, mechanisms and services in ITU-T Recs M.3016.1-M.3016.3. The Proforma, when completed by different organizations, results in a profile for the security requirements, services and mechanisms. These profiles may be used by implementations to specify conformance. + +The proforma defined in ITU-T Rec. M.3016.4 is provided to assist organizations, administrations and other national/international organizations, specify the mandatory and optional support of the requirements as well as value ranges, values, etc. to help implement their security policies. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- ITU-T Recommendation M.3016.0 (2005), *Security for the management plane: Overview*. +- ITU-T Recommendation M.3016.1 (2005), *Security for the management plane: Security requirements*. +- ITU-T Recommendation M.3016.2 (2005), *Security for the management plane: Security services*. +- ITU-T Recommendation M.3016.3 (2005), *Security for the management plane: Security mechanisms*. + +# 3 Definitions + +There are no new definitions in this Recommendation. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +PP Profile Proforma + +# 5 Conventions + +In ITU-T Recs M.3016.1-M.3016.3, a descriptor is used to identify the different requirements, services and mechanisms. The descriptor consists of one of the following three-letter labels followed by a number: + +- REQ for requirement; +- SER for service; +- MEC for mechanism. + +# 6 Basis of profile proforma for security requirements + +## 6.1 Overview + +ITU-T Recs M.3016.1-M.3016.3 specify a set of requirements, services and mechanisms for the appropriate security of the management functions necessary to support the telecommunications infrastructure. Because different administrations and organizations require varying levels of security support, ITU-T Recs M.3016.1-M.3016.3 do not specify whether a requirement/mechanism/service is mandatory or optional. + +The proforma defined in this Recommendation is to assist administrations and other national/international organizations to specify the mandatory and optional support of the requirements, as well as value ranges, values, etc. + +The proforma is specified using the numbered requirements from ITU-T Recs M.3016.1-M.3016.3. + +## 6.2 Guidelines and instructions for proforma specification + +The proforma is specified using tabular representation. For each Recommendation, one table is provided and should be completed for the profile. Each table has the following columns: + +- a) The requirement number from the Recommendation; +- b) Status; +- c) The value range or value; +- d) Comments or notes. + +The tables in this Recommendation have the first column completed. Organizations using the profiles should complete the tables as follows. + +For each requirement in the status column indicate: + +- m Mandatory; +- o Optional; +- c Conditional; +- x Prohibited ("x" stands for "excluded"); +- Not applicable or out of scope. + +If status is "c", the comment column should define the condition that must be true for supporting the requirement. + +The value range or value column specifies applicable range or specific values. For example, a requirement for the length of the key is placed in that column. + +The comment column is used to include information relevant for the implementing the requirement according to that profile. + +# 7 Proforma + +## 7.1 M.3016.1 security requirements + +Table 1/M.3016.4 contains the requirements from ITU-T Rec. M.3016.1 and the user should complete the other columns according to the guidelines provided above. + +**Table 1/M.3016.4 – Proforma for requirements in ITU-T Rec. M.3016.1** + +| Security requirements | Status | Value range/Values | Comments | +|-----------------------|--------|--------------------|----------| +| REQ 1 | | | | +| REQ 2 | | | | +| REQ 3 | | | | +| REQ 4 | | | | +| REQ 5 | | | | +| REQ 6 | | | | +| REQ 7 | | | | +| REQ 8 | | | | +| REQ 9 | | | | +| REQ 10 | | | | +| REQ 11 | | | | +| REQ 12 | | | | +| REQ 13 | | | | +| REQ 14 | | | | +| REQ 15 | | | | +| REQ 16 | | | | +| REQ 17 | | | | +| REQ 18 | | | | +| REQ 19 | | | | +| REQ 20 | | | | +| REQ 21 | | | | +| REQ 22 | | | | +| REQ 23 | | | | +| REQ 24 | | | | +| REQ 25 | | | | +| REQ 26 | | | | +| REQ 27 | | | | +| REQ 28 | | | | +| REQ 29 | | | | +| REQ 30 | | | | +| REQ 31 | | | | +| REQ 32 | | | | +| REQ 33 | | | | +| REQ 34 | | | | + +**Table 1/M.3016.4 – Proforma for requirements in ITU-T Rec. M.3016.1** + +| Security requirements | Status | Value range/Values | Comments | +|------------------------------|---------------|---------------------------|-----------------| +| REQ 35 | | | | +| REQ 36 | | | | +| REQ 37 | | | | +| REQ 38 | | | | +| REQ 39 | | | | +| REQ 40 | | | | +| REQ 41 | | | | +| REQ 42 | | | | +| REQ 43 | | | | +| REQ 44 | | | | +| REQ 45 | | | | +| REQ 46 | | | | +| REQ 47 | | | | +| REQ 48 | | | | +| REQ 49 | | | | +| REQ 50 | | | | +| REQ 51 | | | | +| REQ 52 | | | | +| REQ 53 | | | | +| REQ 54 | | | | +| REQ 55 | | | | +| REQ 56 | | | | +| REQ 57 | | | | +| REQ 58 | | | | +| REQ 59 | | | | +| REQ 60 | | | | + +## 7.2 M.3016.2 security services + +Table 2/M.3016.4 contains the requirements from ITU-T Rec. M.3016.2 and the user should complete the other columns according to the guidelines provided above. + +**Table 2/M.3016.4 – Proforma for Requirements in M.3016.2** + +| Security requirements | Status | Value range/Values | Comments | +|------------------------------|---------------|---------------------------|-----------------| +| SER 1 | | | | +| SER 2 | | | | +| SER 3 | | | | +| SER 4 | | | | +| SER 5 | | | | +| SER 6 | | | | +| SER 7 | | | | +| SER 8 | | | | +| SER 9 | | | | +| SER 10 | | | | + +## 7.3 M.3016.3 security mechanisms + +Table 3/M.3016.4 contains the requirements from ITU-T Rec. M.3016.2 and the user should complete the other columns according to the guidelines provided above. + +**Table 3/M.3016.4 – Proforma for requirements in M.3016.3** + +| Security requirements | Status | Value range/Values | Comments | +|-----------------------|--------|--------------------|----------| +| MEC 1 | | | | +| MEC 2 | | | | +| MEC 3 | | | | +| MEC 4 | | | | +| MEC 5 | | | | +| MEC 6 | | | | +| MEC 7 | | | | +| MEC 8 | | | | +| MEC 9 | | | | +| MEC 10 | | | | +| MEC 11 | | | | +| MEC 12 | | | | +| MEC 13 | | | | +| MEC 14 | | | | +| MEC 15 | | | | +| MEC 16 | | | | +| MEC 17 | | | | +| MEC 18 | | | | +| MEC 19 | | | | +| MEC 20 | | | | +| MEC 21 | | | | +| MEC 22 | | | | +| MEC 23 | | | | +| MEC 24 | | | | +| MEC 25 | | | | +| MEC 26 | | | | +| MEC 27 | | | | +| MEC 28 | | | | +| MEC 29 | | | | +| MEC 30 | | | | +| MEC 31 | | | | +| MEC 32 | | | | +| MEC 33 | | | | +| MEC 34 | | | | +| MEC 35 | | | | +| MEC 36 | | | | + +**Table 3/M.3016.4 – Proforma for requirements in M.3016.3** + +| Security requirements | Status | Value range/Values | Comments | +|------------------------------|---------------|---------------------------|-----------------| +| MEC 37 | | | | +| MEC 38 | | | | +| MEC 39 | | | | +| MEC 40 | | | | +| MEC 41 | | | | +| MEC 42 | | | | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45cb627fe8d1ebed57a6f0bc11b0f81c9a03cd42 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c6c7b9773977e35d83484ec0f27d4555845263da03fcb66d28bbc6680e3c7e3 +size 8850 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91e4549cd76a86249adcb59b12d5bc6439ce2884 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb3b38143c19f659e9b0dd9eaa28274150551702bff6ef0cb2c4a3d131101c5a +size 27237 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2efb984206e1606d708d36597bb38fec5a4e59c --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c699cd03ab5f723207cf09cfc71b1159f533e2b3f11dcb882542995508da987b +size 96182 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a1415f756aa6726694553527c878ae0ee24cc02 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:872876d8970f3365964a313f1d371f9cd13d257a51f3e7b1c8ed8cfd2f94c12b +size 3897 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/2beb95006f1933bed737cfe1e6598db8_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/2beb95006f1933bed737cfe1e6598db8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..161e4a3f498020f5544731cf8ea58dea5a4c10e6 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/2beb95006f1933bed737cfe1e6598db8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:742b3e99d4eb505917012420aab2956f22dc6d08b362d667c7f69afd3d4059d5 +size 13615 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5c8a52a3737496668e437bf52696605ad7fd4c3 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/3493d7ba4c86f944e159de1bf45ff03d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7bcf0703919f6984f594c78539893473bae3d9f0540e8fc4b4f8d4c8b9a6c8d +size 10517 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf0d7ca6189d205ca01daef8639140ef7b1c87cc --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e1eaf808c93b1496333badb7cc4138a80ee85418aa5811286c61ba39c5f94ef +size 20765 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f3459dc0fd3478ba65065138445f3f0e5fc8c5b --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcb6fcb881242585406bc66cd35c890bda3d379462e9208ed09bfddab96800b5 +size 11306 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0555c9c808b716a4224b58ecc054176bdd60c26a --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9abdb571b7b2b6250d7233cc01b675d81fb4a2839d7a714dadcd639fd852addb +size 10636 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/4bfb457b83429c217736e6d51b2f3945_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/4bfb457b83429c217736e6d51b2f3945_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbe9febac4063db33a6ebc343cbb10e239321cc1 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/4bfb457b83429c217736e6d51b2f3945_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7d44093af1ccbb94fff816d410d02fef4c6906e798360777e281ed8ba5885b6 +size 35419 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88268eefc2ce9d28b16c74246d782a4d1337345d --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bffe53ab883006191cd60c6c5ce0f22c622854eb7200a434e47cbdb94acd793 +size 8028 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/4f6da7645cec40b72385c93b2f4dc4be_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/4f6da7645cec40b72385c93b2f4dc4be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0379237bbef9531a9543e5e10a8caddef6721b64 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/4f6da7645cec40b72385c93b2f4dc4be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:909c7949658d039b0b2af1d6601e97eb5121e58ba531d688c7690a012c5a8886 +size 8370 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/6584b95e34ea1f0b67144aa841db0863_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/6584b95e34ea1f0b67144aa841db0863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da3c72635d4432c9cd9323bc657bd479fbfef991 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/6584b95e34ea1f0b67144aa841db0863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe251367a13502b684e3acba8ff0dd43a0d4af3d5834e2f3096ae8b1323fe150 +size 9863 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/6757222e979ee95c44354a897c5cc1c1_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/6757222e979ee95c44354a897c5cc1c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..249949ebb8cb393d66fc402e65275cade0532800 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/6757222e979ee95c44354a897c5cc1c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2837f28df6a4e92a37934ef8428473ea00b244b1908cd61b8b3c2524ceb5d6c +size 4756 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6517ba66761b0e8a70d3c2d4bdc9087568dd82a5 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/683f755e8456c884716de4fce48c7e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:663bab4888978977dffe77fade4d4f303fcfeeb9d3ab48c3cfee590a91f705e1 +size 9974 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16206fd05c640fa0f1e59d7bbc39211ce75b45d1 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/70a863dc6cd47bac82c12162a9479aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8ea025daaaca04372d7070e956c908697f3b62a58f01f4ee0edf5f4d7a4d38c +size 6149 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a8f89058c523c0a12c600ee413614295ed90ea --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e39448d29c54ac534e6b74cc374fe8985b576c7dc77e9df8a6d4c940f23ea1a6 +size 45483 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd675c009fc09d946bdbe2238d55ff77f94fde35 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/772cc583a60eeb058cc19de48269ad22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a480bd7cacf237295f346e72f3cba7aa93ec493af58349168aec7572ad9e44dc +size 26363 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/781be1b7270da21ee7b75b51db2ee1b3_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/781be1b7270da21ee7b75b51db2ee1b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9ddfb92fad898fd961fe644648df3a104672c4f --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/781be1b7270da21ee7b75b51db2ee1b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92de009e1fca36df5e25ed6fe7d390d35267e11931a2856116675e176c36535d +size 4553 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..911b22c94f1a81beda4b5f1c98762cb5c433197f --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/834fb96b114b8fdc001625e1ae28e8b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a431abdf4ee3a1abb9c7c126df1014312bae7e8228d346a5e547eff2810d3e4 +size 3976 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7e7dc1bd192c3dc208da5627b57b8c23acc946c --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a98292b43f0d798622fdd69ce97fd7d140a9a8046173e891d9473bedb40c3284 +size 60957 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/935075de5250cfe8aa0fb9d65d63dde5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..005ee834a36edf6edbd771567aede81f86143fa2 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/935075de5250cfe8aa0fb9d65d63dde5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd42542a0e28e9565b40f6df34cf830f414537af2d7dfca584247661a3d424e2 +size 14981 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2520d1377d51c4d9ec7f988028186530f245aa5a --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08aa9e0b267cd5b3499ba1c22efed188a975fa4d6e6be24560032c8226579777 +size 15174 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48b4510762b4361698e86d99f8dff11d29b1ede1 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40e763cf4252e61d40f13a555a715d49ea1d465b745d0811bd63f8c46253dbdc +size 45800 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..350ac4bde8d0a58c8f2a60c5888628588d27a6b3 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e373b58be86a672f34df76caec820c97372531cee4c107a236053257913b8ad7 +size 11960 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60a6ccb7b758047a7cdbf7c07aa54dce2561de01 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f83486c89db819d9bfc2dac92eea670c4bc22ce57801ae935869c69815a93a99 +size 80510 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a480629e43d0182593f98035bb2b9ba51063335c --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b10e4bbff16e06087b671fbe8998145638f3f2258dac6d41ab9e8d940426b8ac +size 7436 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbe00c827195d8a6a5a8977b88b7c992d1f1a5af --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f17d43757f71838be203e84efddc7dbd5e8687f983e36e9b0ebcae4f72ab7048 +size 26449 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21f25da0ac291baaf4506e78c45a0dd4246d907d --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/cf8bd014a50b7c69435e804f67f9617f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbc617e27ac946f6505159ed699e55eeb0c3cef1bb53a5793abe2bff2b5a4347 +size 11503 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042c2000cac69f77c7d2126998eda2a3d242f332 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c104e523abae15f2f5d268259ec9be5349e57d40c774f64513b23541fec4211 +size 15278 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/f943b07ab747bfd85e302e5a31c20ba8_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/f943b07ab747bfd85e302e5a31c20ba8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87ff26fe6215321e85a6f812f2868b56da229cd5 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/f943b07ab747bfd85e302e5a31c20ba8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5efcbdb2d654f01698e1ff948917420e2e67908f38c10955d46c38b784f2bdb4 +size 10950 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/f98674fcf898dbd5225f8f732a393e1c_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/f98674fcf898dbd5225f8f732a393e1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..680445701ae11dc32651d63cbc64f20ddb11fc74 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/f98674fcf898dbd5225f8f732a393e1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30335dd8c80d4cd09b019557090b4ea677a1588fce1f11cdbb22caf3bd86817d +size 5551 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/fb5442ad7130829bed9e3682ccb84c87_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/fb5442ad7130829bed9e3682ccb84c87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c38c3954af7b1206fe694a11a41548fda65abfd --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/fb5442ad7130829bed9e3682ccb84c87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bcdd1f139504c17d535b64858e2ed9698e61cf048bae4f0c0b31055049e32b5 +size 3833 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/fc0cdcafc5389b99674ba116c9787ffd_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/fc0cdcafc5389b99674ba116c9787ffd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e07e6f8f2eaa6a90cb415cd35d70e706c115e62 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/fc0cdcafc5389b99674ba116c9787ffd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f30d239573cf1f3afa3afdc627c33db27eddd7f97a8a8aaf5bf5759fc4f7b8f0 +size 32104 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c59e86d64a318569e8790e5b8b3f38f21fb46d5e --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efa5d6241b34ef2d113f64a4b409e2c9a455c7f0b5d68370376bca0645a892e8 +size 84464 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/M/T-REC-M.3020-202304-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24aeec3018572b88a549b31cf63e45c8be51fdc5 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b03da3f01aac4feb81050f5274e0a0d8ebdfcafec19734cf295bb0f3d36ae66 +size 19562 diff --git a/marked/M/T-REC-M.3020-202304-I_PDF-E/raw.md b/marked/M/T-REC-M.3020-202304-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7e08bf0c10fc75a4c39e13d64cbb33630b62c983 --- /dev/null +++ b/marked/M/T-REC-M.3020-202304-I_PDF-E/raw.md @@ -0,0 +1,2883 @@ + + +# Recommendation **ITU-T M.3020 (04/2023)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +## --- **Management interface specification methodology** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3020 + +# Management interface specification methodology + +## Summary + +Recommendation ITU-T M.3020 describes the management interface specification methodology (MISM). It describes the process to derive interface specifications based on user requirements, analysis and design (RAD). Guidelines are given on RAD using unified modelling language (UML) notation; however, other interface specification techniques are not precluded. The guidelines for using UML are described at a high level in this ITU-T Recommendation. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3020 | 1992-10-05 | | 11.1002/1000/1516 | +| 2.0 | ITU-T M.3020 | 1995-07-27 | 4 | 11.1002/1000/1517 | +| 3.0 | ITU-T M.3020 | 2000-02-04 | 4 | 11.1002/1000/4871 | +| 4.0 | ITU-T M.3020 | 2007-07-22 | 4 | 11.1002/1000/9097 | +| 5.0 | ITU-T M.3020 | 2008-07-29 | 4 | 11.1002/1000/9550 | +| 6.0 | ITU-T M.3020 | 2009-05-14 | 2 | 11.1002/1000/9736 | +| 7.0 | ITU-T M.3020 | 2010-09-06 | 2 | 11.1002/1000/10863 | +| 8.0 | ITU-T M.3020 | 2011-07-14 | 2 | 11.1002/1000/11368 | +| 8.1 | ITU-T M.3020 (2011) Amd. 1 | 2014-07-14 | 2 | 11.1002/1000/12202 | +| 9.0 | ITU-T M.3020 | 2017-07-22 | 2 | 11.1002/1000/13268 | +| 10.0 | ITU-T M.3020 | 2023-04-29 | 2 | 11.1002/1000/15514 | + +## Keywords + +Management interface, specification methodology. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|---------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation ..... | 3 | +| 4 | Abbreviations and acronyms ..... | 4 | +| 5 | Conventions ..... | 5 | +| 6 | Requirements for methodology and notational support..... | 5 | +| 7 | Methodology..... | 5 | +| 7.1 | General considerations ..... | 5 | +| 7.2 | Application and structure of the methodology ..... | 6 | +| 7.3 | Detailed methodology ..... | 6 | +| 8 | Management interface specifications..... | 9 | +| 9 | Traceability in MISIM process ..... | 9 | +| 10 | Documentation structure ..... | 9 | +| | Annex A – Requirements ..... | 10 | +| A.1 | Conventions ..... | 10 | +| A.2 | Requirements template..... | 13 | +| A.3 | Simplified requirements template..... | 16 | +| | Annex B – Analysis ..... | 18 | +| B.1 | Conventions ..... | 19 | +| B.2 | Analysis template ..... | 21 | +| B.3 | IOC properties and inheritance..... | 32 | +| | Annex C – MISIM UML repertoire ..... | 34 | +| C.1 | Introduction..... | 34 | +| C.2 | Basic model elements..... | 34 | +| C.3 | Stereotypes..... | 43 | +| C.4 | Others ..... | 49 | +| C.5 | Qualifiers..... | 51 | +| C.6 | UML diagram requirements..... | 52 | +| | Annex D – Design..... | 53 | +| | Annex E – Information type definitions – type repertoire..... | 54 | +| E.1 | Basic types ..... | 54 | +| E.2 | Enumerated type ..... | 54 | +| E.3 | Complex types ..... | 54 | +| E.4 | Useful types ..... | 54 | +| E.5 | Keywords ..... | 55 | + +| | Page | +|----------------------------------------------------------------------------|-------------| +| Annex F – Guidelines on IOC properties, inheritance and entity import..... | 56 | +| F.1     IOC property ..... | 56 | +| F.2     Inheritance..... | 57 | +| F.3     Entity (interface, IOC and attribute) import ..... | 57 | +| Annex G – Attribute Properties..... | 58 | +| Annex H – Design patterns..... | 59 | +| H.1     Intervening class and association class ..... | 59 | +| H.2     Use of "ExternalXyz" class..... | 63 | +| Appendix I – Comparison with Recommendation ITU-T Z.601 ..... | 64 | +| Appendix II – Additional UML usage examples ..... | 65 | +| II.1     Proxy class ..... | 65 | +| Appendix III – Guidelines on requirements numbering ..... | 67 | +| Appendix IV – Stereotypes for naming purposes ..... | 68 | +| Bibliography ..... | 69 | + +# Recommendation ITU-T M.3020 + +## Management interface specification methodology + +# 1 Scope + +This Recommendation describes the management interface specification methodology (MISM). It describes the process to derive machine-machine interface specifications based on user requirements, analysis and design (RAD). Guidelines are given on RAD using unified modelling language (UML) notation; however, other interface specification techniques are not precluded. The guidelines for using UML are described in this Recommendation. An interface specification addresses management service(s) defined in [ITU-T M.3200] and/or supporting the management processes defined in [ITU-T M.3050.x] series. Such a specification may support part of or one or more management services. The management services comprise of management functions. These functions may reference those defined in [ITU-T M.3400] or the processes defined in [ITU-T M.3050.x] series, specialized to suit a specific managed area, or new functions may be identified as appropriate. + +The methodology is applicable to both the traditional manager/agent style of management interfaces [ITU-T M.3010] and the service oriented architecture (SOA) principles adopted for the management architecture of next generation networks [ITU-T M.3060]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3050.0] Recommendation ITU-T M.3050.0 (2007), *Enhanced Telecom Operations Map (eTOM) – Introduction*. +- [ITU-T M.3050.x] ITU-T M.3050.x (2007) series of Recommendations, *Enhanced Telecom Operations Map (eTOM)*. +- [ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the Management of Next Generation Networks*. +- [ITU-T M.3200] Recommendation ITU-T M.3200 (1997), *TMN management services and telecommunications managed areas: Overview*. +- [ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*. +- [ITU-T Q.812] Recommendation ITU-T Q.812 (2004), *Upper layer protocol profiles for the Q and X interfaces*. +- [ITU-T X.501] Recommendation ITU-T X.501 (2019) | ISO/IEC 9594-2:2019, *Information Technology – Open Systems Interconnection – The Directory: Models*. +- [ITU-T X.680] Recommendation ITU-T X.680 (2021) | ISO/IEC 8824-1:2021, *Information Technology – Abstract Syntax Notation One (ASN.1): Specification of Basic Notation*. + +- [ITU-T X.681] Recommendation ITU-T X.681 (2021) | ISO/IEC 8824-2:2021, *Information technology – Abstract Syntax Notation One (ASN.1): Information Object Specification*. +- [ITU-T X.722] Recommendation ITU-T X.722 (1992) | ISO/IEC 10165-4:1992, *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects*. +- [ITU-T Z.100] Recommendation ITU-T Z.100 (2016), *Specification and Description Language (SDL) – Overview of SDL-2010*. +- [OMG UML1] Object Management Group (2011), *Unified Modeling Language (OMG UML), Infrastructure, Version 2.4.1*. +- [OMG UML2] Object Management Group (2011), *Unified Modeling Language (OMG UML), Superstructure, Version 2.4.1*. + +A list of non-normative references can be found in the Bibliography. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 actor** [OMG UML2]: An actor specifies a role played by a user or any other system that interacts with the subject. + +**3.1.2 association** [OMG UML1]: An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link. A link is a tuple with one value for each end of the association, where each value is an instance of the type of the end. + +**3.1.3 class** [OMG UML1]: A class describes a set of objects that share the same specifications of features, constraints, and semantics. + +**3.1.4 distinguished name** [ITU-T X.501]: The name of an entry which is formed from the sequence of the relative distinguished names (RDNs) of the entry and each of its superior entries. Every object entry, alias entry and subentry has precisely one distinguished name. + +**3.1.5 management function set** [ITU-T M.3010]: TMN management function set is a grouping of TMN management functions that contextually belong together, i.e., they are related to a specific management capability (e.g., alarm reporting functions, traffic management control). The TMN management function set is the smallest reusable item of functional specification. The TMN management function set must be considered as a whole. It is similar to the requirements part of the OSI SMF (system management function). + +**3.1.6 management service** [ITU-T M.3010]: A management service is an offering fulfilling specific telecommunications management needs. + +**3.1.7 reference point** [ITU-T M.3010]: An architectural concept used to delineate management function blocks and which defines a service boundary between two management function blocks. + +**3.1.8 stereotype** [OMG UML1]: A stereotype defines how an existing metaclass may be extended, and enables the use of platform or domain specific terminology or notation in place of, or in addition to, the ones used for the extended metaclass. + +**3.1.9 user** [ITU-T M.3010]: A person or process applying management services for the purpose of fulfilling management operations. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 agent:** Encapsulates a well-defined subset of management functionality. It interacts with managers using a management interface. From the manager's perspective, the agent behaviour is only visible via the management interface. + +NOTE – Considered equivalent to IRPAgent [b-3GPP TS 32.150]. + +**3.2.2 information object class:** 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 Annex B. + +**3.2.3 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. Information services are defined for all IRPs. + +NOTE – Considered identical to the definition of information service found in [b-3GPP TS 32.150]. + +**3.2.4 information type:** Specification of the type of input parameters of operations. + +**3.2.5 integration reference point:** An architectural concept that is described by a set of specifications for the definition of a certain aspect of the management interface, comprising a requirements specification, an information service specification, and one or more solution set specifications. + +NOTE – Considered identical to the definition of IRP found in [b-3GPP TS 32.150]. + +**3.2.6 lower camel case:** The practice of writing compound words in which the words are joined without spaces. Initial letter of all except the first word shall be capitalized. Examples: 'managedNodeIdentity' and 'minorDetails' are the lower camel case (LCC) for "managed node identity" and "minor details" respectively. + +**3.2.7 management goals:** High-level objectives of a user in performing management activities. + +**3.2.8 management interface:** The realization of management capabilities between a manager and an agent, allowing a single manager to use multiple agents and a single agent to support multiple managers. + +NOTE – Q, C2B/B2B and Itf-N (3GPP) are examples of management interfaces. + +**3.2.9 management role:** Defines the activities that are expected of the operational staff or systems that perform telecommunications management. Management roles are defined independent of other components, i.e., telecommunications resources and management functions. + +**3.2.10 management scenario:** An example of management interactions from a management service. + +**3.2.11 manager:** Models a user of agent(s) and it interacts directly with the agent(s) using management interfaces. + +Since the manager represents an agent user, it gives a clear picture of what the agent is supposed to do. From the agent perspective, the manager behaviour is only visible via the management interface. + +NOTE – Considered equivalent to IRPManager [b-3GPP TS 32.150]. + +**3.2.12 matching information:** Specification of the type of a parameter (possibly reference to IOC or attribute of IOC). + +**3.2.13 naming attribute:** A class attribute that holds the class instance identifier. + +NOTE – See examples of naming attribute in [b-3GPP TS 32.300]. + +**3.2.14 protocol-neutral specification:** Defines the management interfaces in support of management capabilities without concern for the protocol and information representation implied or required by, e.g., CORBA and XML. + +**3.2.15 protocol-specific specification:** Defines the management interfaces in support of management capabilities for one specific choice of management technology (e.g., CORBA). + +NOTE – Considered equivalent to solution set [b-3GPP TS 32.150]. + +**3.2.16 telecommunication resources:** Physical or logical entities requiring management, using management services. + +**3.2.17 upper camel case:** It is the lower camel case except that the first letter is capitalized. Examples: 'ManagedNodeIdentity' and 'MinorDetails' are the upper camel case (UCC) for "managed node identity" and "minor details" respectively. + +**3.2.18 well known abbreviation:** An abbreviation can be used as the modelled element name or as a component of a modelled element name. The abbreviation, when used in such manner, must be documented in the same document where the modelled element is defined. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------------| +| ADM | Administrative (usage: requirements category) | +| ASN.1 | Abstract Syntax Notation One | +| CM | Conditional-Mandatory | +| CO | Conditional-Optional | +| CON | Conceptual (usage: requirements category) | +| CORBA | Common Object Request Broker Architecture | +| DN | Distinguished Name | +| FUN | Functional (usage: requirements category) | +| GDMO | Guidelines for the Definition of Managed Objects | +| IDL | Interface Definition Language | +| IOC | Information Object Class | +| IRP | Integration Reference Point | +| IS | Information Service | +| JSON | JavaScript Object Notation | +| LCC | Lower Camel Case | +| MCC | Mobile Country Code | +| MISM | Management Interface Specification Methodology | +| MNC | Mobile Network Code | +| N/A | Not Applicable | +| NE | Network Element | +| NON | Non-functional (usage: requirements category) | +| OO | Object Oriented | +| OSI | Open Systems Interconnection | + +| | | +|------|----------------------------------------| +| RAD | Requirements, Analysis and Design | +| RDN | Relative Distinguished Name | +| SDL | Specification and Description Language | +| SOA | Service Oriented Architecture | +| SS | Solution Set | +| SNC | Sub Network Connection | +| TP | Termination Point | +| TS | Technical Specification | +| UCC | Upper Camel Case | +| UML | Unified Modelling Language | +| WKA | Well Known Abbreviation | +| WSDL | Web Services Description Language | +| XML | extensible Markup Language | +| XSD | XML Schema Definition | +| YAML | YAML Ain't Markup Language | + +# 5 Conventions + +Clause A.1 contains conventions applicable to the requirements phase. + +Clause B.1 contains conventions applicable to the analysis phase. + +# 6 Requirements for methodology and notational support + +In developing the methodology and choosing a notation, the following requirements apply: + +- 1) The methodology, including the choice of notation, shall support the capture of all the relevant requirements of the problem space, namely telecommunications management. +- 2) The methodology facilitates the production of requirements, its corresponding Analysis|Information Services and their corresponding Design Specifications|Solution Sets. +- 3) The notation shall facilitate unambiguous generation of the specification in the target management protocol profile. The methodology does not address possible choices of protocol services (e.g., CORBA Security Service). + +NOTE – Management protocols applicable for ITU-T use are specified in [ITU-T Q.812]. + +- 4) The methodology shall allow specification of mandatory and optional items in all three phases. It also specifies the relation of mandatory|optional items between the three phases. +- 5) It should be possible to generate, from the protocol-neutral specification (Analysis|IS), interoperable language specific definitions, i.e., Design|SS (for example UML to interface definition language (IDL), UML to GDMO/ASN.1). + +# 7 Methodology + +## 7.1 General considerations + +The purpose of this methodology is to provide a description of the processes leading towards the definition of machine-machine management interfaces. + +## 7.2 Application and structure of the methodology + +The management interface specification methodology (MISM) specifies a three-phase process with features that allow traceability across the three phases. The three phases apply industry-accepted techniques using object oriented analysis and design principles. The three phases are requirements, analysis and design. The techniques should allow the use or development of commercially available support tools. Different techniques may be used for the phases depending on the nature of the problem. + +## 7.3 Detailed methodology + +### 7.3.1 General + +The requirements and analysis phases produce UML specifications. The design phase uses network management paradigm specific notation. The outputs of the 3 phases are: + +- Requirements phase – Requirements. +- Analysis phase – Implementation independent specification. +- Design phase – Technology specific specification. + +Initially, the design phase will be developed using a manual or customized approach. When interoperable protocol specific definition can be generated by tools, then UML notation can be applied to the design phase. + +The clauses below describe the three phases. + +### 7.3.2 Requirements + +The requirements for the problem being solved fall into two classes. The first class of requirements is referenced here as business requirements. A subject matter expert on the topic shall be able to determine that the requirements adequately represent the needs of the management problem being solved. The second class is referred to as specification requirements. These requirements shall provide sufficient details so that the interface definition in the analysis and design phases can be developed. As final interface definitions must be traceable to the requirements, it may be necessary to have interaction between the three phases. Any ambiguity in the requirements will have to be resolved by this interaction to assure that an implementable specification can be developed. + +Human-computer interface data may be specified in the second class of requirements. These requirements may have great impact on concepts and data designed in the subsequent phases. For more details, see Appendix I. + +Different techniques may be used to specify the two classes of requirement. Irrespective of the technique, the readability of the requirements is critical. The requirements themselves are not required to be in a machine-readable notation as long as readability and traceability are possible. Enumerating requirements is the recommended solution to delineate the different requirements for traceability. + +The requirements phase includes identifying aspects such as security policy, scope of the problem domain in terms of the applications, resources, and roles assumed by the resources. The requirements specify roles, responsibilities, and the relationships between the constituent entities for the problem space. Different techniques, including textual representation, may be used to specify the business level requirements. In order to facilitate traceability of these requirements to the design and implementation phases, enumerating requirements is recommended. + +The problem must be bounded with a specific scope. One way to determine the scope is by using the management services identified in [ITU-T M.3200] and function sets identified in [ITU-T M.3400]. Requirements are specified using the resources being managed and management functions. An alternative to the management services approach is described in [ITU-T M.3050.x] "enhanced Telecom Operations Map (eTOM)" which provides a business process based approach. + +The relationship between the [ITU-T M.3200] and [ITU-T M.3050.x] approaches is described in [ITU-T M.3050.0]. + +Management functions must be grouped and supported within applications that address specific business needs, so the linkage between the eTOM processes, the [ITU-T M.3200] management services, the [ITU-T M.3400] management function sets and management functions is important to assist in making this grouping clear and effective. Augmenting [ITU-T M.3400] may be required in order to meet the business requirements of the problem. + +UML use cases and scenarios should be used to interact with subject matter experts in capturing the business level requirements. The requirements should also identify the failure conditions visible to the business process. + +NOTE – It is not required that every requirement be expressed as a use case. + +The requirements produced must be complete and detailed. The recursive nature of the methodology is used to achieve this completeness. The completeness of the requirements (clear and well-documented) drives the analysis and design phases. + +Guidelines and template for requirement structure and identification are described in clause A.1.2. + +Use cases are goals that are fulfilled through a sequence of steps. Each step can be considered as a sub-goal of the use case. As such each step represents either another use case (subordinate use case) or an autonomous action that is at the lowest level of the case decomposition. + +Guidelines and template for use cases are described in clause A.1.2. + +### 7.3.3 Analysis + +In the analysis phase, the requirements are used to identify the interacting entities, their properties and the relationships among them. This allows the interfaces offered by the entities to be defined. In the UML notation, these entities become classes. The class descriptions along with the interfaces exposed should be traceable to the requirements. The relationship among the classes, defined in the analysis specification, and the classes in the design specification is not necessarily one to one. + +This phase should take into account the needs of human-computer interface data (i.e., the information model must contain sufficient information so that designs can be developed based on the analysis results). + +This Recommendation gives high-level guidance on the use of UML notation to support management interface specification; however, Specification and Description Language (SDL) [ITU-T Z.100] might be used to augment the UML definitions. + +The analysis phase should be independent of design constraints. For example, the analysis may be documented using object oriented (OO) principles even though the design may use a non-object-oriented technology. The information specified in the analysis phase includes class descriptions, data definitions, class relationships, interaction diagrams (the most common variant is the sequence diagrams, see 14.4 of [OMG UML2]), state machine diagrams (see 15.4 of [OMG UML2]) and activity diagrams (see 12.4 of [OMG UML2]). The class definitions include specification of operations, notifications, attributes and behaviour captured as notes or textual description. + +Protocol-neutral common management services (if available) – or other existing services – should be reused during the analysis phase in order to support management interface harmonization. + +Guidelines and template for use cases are described in Annex A. + +The analysis template uses information type as one characteristic to describe information object class (IOC) attributes and operation/notification parameters. The valid information type(s) that can be used and their semantics are defined in Annex E. + +### **7.3.4 Design** + +#### **7.3.4.1 General** + +In the design phase, an implementable interoperable interface specification is produced. This will involve the selection of a target specification language. The design phase specifications are dependent on the specific management paradigm (e.g., IDL for CORBA interfaces). + +This phase distinguishes three kinds of specifications of data: management paradigm (e.g., extensible markup language (XML)) dependent design of data to be communicated across multiple interfaces (e.g., fault and performance), messages (e.g., alarm report) to be communicated over each individual interface, and encoding method of the data (e.g., compressed XML) consistent with a particular paradigm. + +The selection of a specific management paradigm is addressed in other ITU-T Recommendations. An overview is provided in the following clauses. + +In the design phase, it is recommended that the UML descriptions from the requirements and analysis phases be referenced to augment behavioural specification. For example, the behaviour definition of guidelines for the definition of managed objects (GDMO) can reference state charts, sequence diagrams and class definition in the analysis phase. If required, additional UML diagrams describing interactions between entities, corresponding to specific protocol paradigms, may be included. + +As additional paradigms are adopted for use by management, the notations/languages defined by these paradigms will be used. + +#### **7.3.4.2 CORBA** + +In the context of common object request broker architecture (CORBA) based management, the information model is defined using IDL. + +#### **7.3.4.3 GDMO** + +In the context of the paradigm based on open systems interconnection (OSI) systems management [ITU-T X.722], the design specification is the information model specification using GDMO templates for managed object classes, attributes, behaviour, notifications, actions, naming instances of the class, and error/exception specifications. The syntax of the information is specified using Abstract Syntax Notation One (ASN.1) notation [ITU-T X.680]. + +In GDMO, the object class hierarchy specifies the properties of the object classes that are needed for management. Extensive use of inheritance (super and subclasses) is needed to benefit the most from the reuse of specifications. The object classes are specified using the templates from [ITU-T X.722]. The templates defining the information model should be registered (according to the rules of [ITU-T X.722]) with a value for the ASN.1 object identifier. For those object classes that are already specified in other ITU-T Recommendations and ISO standards, only a reference to the particular Recommendation and object class is needed. Naming is not a part, nor the purpose, of the object class hierarchy. + +#### **7.3.4.4 XML** + +In the context of extensible markup language (XML) based management, the information model is defined using XML Schema Definition (XSD). + +#### **7.3.4.5 Web services** + +In the context of web services based management, the information model is defined using Web Service Description Language (WSDL) and XSD. + +#### 7.3.4.6 REST + +In the context of REST-based management, the information model is defined using JSON Schema or YAML Schema. + +# 8 Management interface specifications + +A management interface specification includes the requirements, analysis and design specifications discussed in clause 7. A structure for specifying these specifications is provided in Annexes A, B and C. + +These techniques and supporting notations are also applicable when designing a system to the management interface specifications, even though system design is not considered as part of the ITU-T management Recommendations. They assist in describing how the interface specifications are applied in managing the resources within a system such as a network element (NE). + +# 9 Traceability in MISIM process + +In order to achieve traceability between requirements, analysis and design, it is necessary that appropriate identification be assigned. Traceability is supported through references between entities specified within each phase and between phases. Traceability is from design|solution set to analysis|information services and from analysis|information services to requirements. Traceability is further applicable between artifacts of the requirements specification and between artifacts of the analysis|information service, e.g., between use cases and textual requirements. Requirements should be identified as described in clause 7.3.2. The analysis phase output specifies for the various use cases further detailed information requirements. The design phase should point to the various diagrams and text in the analysis phase output. The pointer may be in terms of a reference to the appropriate clauses. + +Traceability from the design phase to subject matter level requirements is usually indirect. This is required because the output of the phases is defined to different level of details. + +Guidelines for traceability between the requirements phase and the analysis phase are described in Annex B. + +The following mechanism for traceability with requirements, etc., specified in other documents (possibly not following the advocated identification schema) is recommended: + +forum/body "::" document ID "::" id + +where "id" could be one of: + +- 1) requirement ID; +- 2) use case ID; +- 3) requirement title/text; +- 4) use case title; +- 5) subclause of the document which uniquely identifies a requirement or use case. + +Examples: + +3GPP::32.111-1::getAlarmList + +ITU-T::M.3016::1.5.1.2 + +# 10 Documentation structure + +Even though there are three phases, the documentation of the interface may combine their outputs into one or more documents. It is recommended that the requirements and analysis be combined and separate design documents are developed for each specific network management protocol paradigm. + +# Annex A + +## Requirements + +(This annex forms an integral part of this Recommendation.) + +## *A.1 Conventions* + +#### *A.1.1 Use of UML notation for requirements* + +#### *A.1.2 Use case template* + +#### *A.1.3 Requirements categories* + +### *A.2 Requirements template* + +### *1 Concepts and background* + +### *2 Business level requirements* + +#### *2.1 Requirements* + +#### *2.2 Actor roles* + +#### *2.3 Telecommunication resources* + +#### *2.4 High-level use cases* + +### *3 Specification level requirements* + +#### *3.1 Requirements* + +#### *3.2 Actor roles* + +#### *3.3 Telecommunication resources* + +#### *3.4 Use cases* + +### *A.3 Simplified requirements template* + +### *1 Concepts and background* + +### *2 Requirements* + +The following are guidelines for specification of requirements. + +The normal (or full format) requirements template is found in clause A.2. In addition, a simplified requirements template is defined and found in clause A.3. + +## **A.1 Conventions** + +#### **A.1.1 Use of UML notation for requirements** + +Table A.1 identifies the correspondence between management concepts and UML notation. This Recommendation specifies the high-level concepts and notations to be used in the different phases. Stereotypes are used to extend UML notation. The approved stereotypes for use within the management environment are included in this Recommendation (see Annex C). + +**Table A.1 – Requirements concepts** + +| Management concept | UML notation | Comment | +|---------------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| user | Actor | A user is modelled as an actor. | +| management role | Actor | An actor plays a role. It is normally advisable to only model a single role for each actor. | +| management function | use case | A management function is modelled by one or more use cases. | +| management function set | use case | A management function set is a composite use case with each management function (potentially) modelled as a separate use case. | +| management service | use case | A management service is modelled as a high-level use case. | +| management scenario | sequence diagram | Sequence diagrams are preferred over collaboration diagrams. | +| telecommunication resource type | Class | The classes diagrams (see 10.2 of [OMG UML1]) depict the property details of the telecommunications resource type, at the level of detail appropriate to the phase of the methodology. | +| management goals | – | Management goals are captured as textual descriptions as there is no applicable UML notation. | + +#### A.1.2 Use case template + +When use cases are provided, the conventions and templates in Table A.2 should be followed unless the use case can be sufficiently described without the table format. + +**Table A.2 – Use case template** + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal (*) | This is the objective/end result the use case strives to achieve and should be a concise statement of what the use case should achieve in a successful scenario.
There may be a statement about priority relative to other use cases and required performance of the use case, e.g.:
  • • Real Time.
  • • Near real time.
  • • Not real time.
| | +| Actors and roles (*) | The names of actors/roles involved in the use case including role characteristic for each actor. | | +| Telecom resources | The names of the telecommunication resources involved in the use case. | | +| Assumptions | A description of the environment providing a context for the use case.
Assumptions are mutually exclusive to pre-conditions.
Assumptions are concerned with static properties. | | + +**Table A.2 – Use case template** + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| Pre-conditions | A list of all system and environment conditions that must be true before the use case can be triggered.
Pre-conditions are mutually exclusive to assumptions.
Pre-conditions are related to dynamic properties and can result in an exception. This is never the case with assumptions. | | +| Begins when | The name of the single event that triggers the start of the use case.
Optional and normally not used to specify triggers such as "when the manager must retrieve information". | | +| Step 1 (*) (M O) | A use case describes a list of steps (manual and automated) that are necessary to accomplish the goal of the use case.
Steps may invoke other use cases.
Steps are numbered for traceability.
Each step is identified as being mandatory (M) or optional (O).
Sub-steps are identified relative to the containing step, e.g.:
Step n
Step n.1
Step n.2
where n.1 and n.2 are sub-steps of step n. | Reference to a used use case. | +| Step n (M O) | Steps added as necessary and in a logical sequence. | | +| Ends when (*) | The list of event(s) that indicates the use case completion.
NOTE – In this context, "event" should be considered in the most general sense and not limited to, e.g., notifications exchanged across a management interface. As an example, the completion of processing can be considered an event that indicates completion of a use case. | | +| Exceptions | A summary list of exception conditions and faults detected by the use case during its operation. | | +| Post-conditions | A list of all system and environmental conditions that must be true when the use case has completed. The statement of post-conditions determines if the use case is expected to be fully successful, partially successful or even to have failed in order to be completed. | | +| Traceability (*) | Requirements or use case exposed by the use case. | | + +NOTE – Fields marked with "\*" are mandatory for all use case specifications. Other fields are only mandatory when relevant for the specific use case. + +#### A.1.3 Requirements categories + +It is useful to classify requirements in different categories. The following categories are considered relevant for MISM: + +- Conceptual (CON) – Identifies a concept, data type, relationship, format, or structure. +- Functional (FUN) – Identifies a functional capability, dynamic situation, a sequence, timing parameters, or an interaction. +- Non-functional (NON) – Non-functional requirements, including abnormal conditions, error conditions and bounds of performance. +- Administrative (ADM) – System administration and operational requirements not related to the use cases normal operations. + +Requirements should be written based on the following template: + +REQ-Label-Category-Number {Category, number} Details {Source Citation} + +where "Label" is an abbreviation for the Recommendation (or part thereof). The set of labels is not finite and not subject for standardization. + +Guidelines on requirements numbering can be found in Appendix III. + +### A.2 Requirements template + +| 1 Concepts and background | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Define major goals and objectives and the applicable management interfaces (and reference points) for this specification. Use [ITU-T M.3200] categorization as a source for identifying the management service(s) supported by this interface. | | | | | | | +| This subclause should give a clear description of the users' benefit, i.e., the reason for performing this management service. Background and context should be added as necessary, but the explanatory and descriptive parts should be separated. Supporting background information, where required, should be placed in an appendix. | | | | | | | +| 1.a SubClauseTitle | | | | | | | +| SubClauseTitle is the name of the subclause. | | | | | | | +| "a" represents a number, starting at 1 and increasing by 1 with each new subclause. | | | | | | | +| The use of subclauses is optional. | | | | | | | +| 2 Business level requirements | | | | | | | +| 2.1 Requirements | | | | | | | +| 2.1.a SubSetTitle | | | | | | | +| SubSetTitle is the name of a sub-set of the business level requirements. | | | | | | | +| "a" represents a number, starting at 1 and increasing by 1 with each new sub-set. | | | | | | | +| The use of sub-sets is optional and all business level requirements can be stated in subclause 2.1 (requirements). | | | | | | | +| List major requirements in text, and identify use cases with actor/role and resources. The high-level use cases (subclause 2.4 below) should bring out the business level requirements and are distinguished from the specification requirements by not refining to lower levels. Clause 2.4 contains many examples of what makes up the high-level use cases. Policy-related information (e.g., security, persistence) are candidates for inclusion at this level. Numbering the requirements is required for traceability. | | | | | | | +| Requirements should be specified as described in clause A.1.3. Within a requirements specification, it is suggested that requirements be written in the sequence of clause A.1.3 (either for the entire specification or for each sub-set). | | | | | | | +| Use of requirements categories is optional, and – when used – a subset of the categories can be applied. As an example, conceptual requirement number 23 in Recommendation tagged 'SM' would be specified as follows: | | | | | | | +|
Identifier1Definition2Related use case(s) / Motivation
REQ-SM-CON-23A Service Order consists of a name, address, phone number, service description and an optional FAX number for contacts {T1M1.5 Document 246 11/96}
| Identifier 1 | Definition 2 | Related use case(s) / Motivation | REQ-SM-CON-23 | A Service Order consists of a name, address, phone number, service description and an optional FAX number for contacts {T1M1.5 Document 246 11/96} | | +| Identifier 1 | Definition 2 | Related use case(s) / Motivation | | | | | +| REQ-SM-CON-23 | A Service Order consists of a name, address, phone number, service description and an optional FAX number for contacts {T1M1.5 Document 246 11/96} | | | | | | + +1 "Identifier" in this table is equivalent to "Requirement label" in the table of X.a.3 in [b-3GPP TS 32.160]. + +2 "Definition" in this table is equivalent to "Description" in the table of X.a.3 in [b-3GPP TS 32.160]. + +*One or more tables can be used with supportive text between tables as necessary.* + +*In some cases, supplementary text can be added to the requirements as an alternative to very rudimentary use case statements. This can either be done within the table structure itself or following the table (typically relevant when there are only a few requirements in the table).* + +*As an example, supplementary text can be added to the requirement statement as follows:* + +| Identifier | Definition | Related use case(s)
/ Motivation
| +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| REQ-SM-CON-24 | A Service Order consists of a name, address, phone number, service description and an optional FAX number for contacts {TIM1.5 Document 246 11/96}.
Additional information:
One or more paragraphs of additional information can be added to the formal requirement statement. The additional information is intended to provide guidance to the understanding of the requirement and is not formally part of the requirement. The information can be provided within the table (like this example) or below the table. | REQ-SM-CON-21 | + +#### **2.2 Actor roles** + +*A textual description of the actor (see clause 3) is included here.* + +#### **2.3 Telecommunication resources** + +*Textual description of the relevant resources (see clause 3) required to support the use cases are presented here.* + +#### **2.4 High-level use cases** + +*A high-level use case diagram may be presented. In order to understand the use case by subject matter experts, they should be augmented with a textual description for each use case. The description should serve two purposes: to capture the domain experts' knowledge and to validate the models in analysis and design phases with respect to the requirements. An example of a high-level use case diagram is given in Appendix I.* + +*Use cases can be described using the full use case format as described in 2.4.a or more simply as natural text depending on the nature of the use case.* + +*In some cases, the text of a use case can be seen as a detailing of requirements. In these cases, it can be more practical to handle this text as a supplement to the relevant requirement. See clause 3.1.a for more details on this.* + +#### **2.4.a UseCaseName** + +*UseCaseName is the name of the use-case.* + +*"a" represents a number, starting at 1 and increasing by 1 with each new definition of a use case.* + +*This subclause is repeated for each high-level use case defined for the interface specification requirements.* + +*The high-level use cases may identify the various function sets defined in [ITU-T M.3400] or the management processes defined in [ITU-T M.3050.x]. These use cases may be further refined as described in the specification level requirement subclause below by using stereotypes such as "include" and "extend".* + +*If appropriate, sequence diagrams may be used. However, at the high-level requirements these diagrams are not expected to be used. When the use cases at this level are further decomposed in the next level of requirements, these diagrams may be more suitable.* + +*The traceability of the next level of requirements from this level may be identified by how each function set is further refined with new use cases.* + +*A set of use case tables, using the template defined in Table A.2, may be used to represent the significant capabilities studied at a level of abstraction appropriate to the problem being analysed.* + +*The level of detail, and extent of coverage provided in the use cases is dependent upon the authoring team's familiarity with the subject matter and is therefore subjective. The lower levels of details are most likely an indication of analysis rather than requirements capture.* + +*It is permitted to develop successively more detailed analysis of each step of a higher abstraction level use case by referring to the more detailed use case in the table cell reserved for this purpose. It is emphasized this does not have to be done, and is subjective depending upon the need of the author/group.* + +*The following list is provided to aid the initial identification of suitable use cases:* + +- What is the main purpose of the system?* +- What types of people/system need to interact with the system?* +- How can these people/systems be grouped or abstracted to roles?* +- What are the start up, normal running, failure and recovery aspects of the system?* +- What types of reports or data may be needed from the system?* +- Which special activities are required (e.g., based on times of day and network loads)?* + +*It is useful to document use cases in a common manner. The following structure is suggested:* + +- (see Table A.2)* +- * +- * + +A simplified use case documentation approach can also be used. In that case, the use case is described without a pre-defined format or template, e.g., one or more text paragraphs. + +### **3 Specification level requirements** + +#### **3.1 Requirements** + +*The business level requirements are further refined here using management functions from [ITU-T M.3400]. Since [ITU-T M.3400] is not exhaustive enough to address all management services for all managed areas, it is expected that new functions will be required. The new functions should be included in the requirements as described below.* + +##### **3.1.a SubSetTitle** + +*SubSetTitle represents the name of a subset of specification level requirements.* + +*"a" represents a number, starting at 1 and increasing by 1 with each new sub-set.* + +*The use of sub-sets is optional and all specification level requirements can be stated in subclause 3.1 (requirements).* + +*List major detailed and concrete requirements in text, and identify use cases with actor/role and resources. The use cases in subclause 3.4 should bring out specification level requirements with lower level details and be more implementation-oriented compared to the business level use case requirements. Numbering the requirements is required for traceability.* + +*Requirements should be specified as described in clause A.1.3. Within a requirements specification, it is suggested that requirements be written in the sequence of clause A.1.3 (either for the entire specification or for each sub-set).* + +*Use of requirements categories is optional, and – when used – a subset of the categories can be applied. As an example, functional requirement number 33 in a Recommendation tagged 'OM' would be specified as follows:* + +| Identifier | Definition | +|-------------------|--------------------------------------------------------| +| REQ-OM-FUN-33 | A pending operation can be cancelled by the initiator. | + +*One or more tables can be used with supportive text between tables as necessary.* + +*Specification level requirements should follow the conventions and templates defined in clause A.1.* + +*In some cases, supplementary text can be added to the requirements as described in clause 2.1.a.* + +#### **3.2 Actor roles** + +*A list of all actors and textual description of actors not already defined in the business level requirements is included here.* + +#### **3.3 Telecommunication resources** + +*A list of all passive resources and textual description of resources not already defined in the business level requirements is presented here.* + +#### **3.4 Use cases** + +*The high-level use cases are further refined here using several specification level use cases, each of which will be further explained in detail in a subclause as described below.* + +*See also clause 2.4 for additional guidelines on use case format alternatives.* + +#### **3.4.a UseCaseName** + +*UseCaseName is the name of the use-case.* + +*"a" represents a number, starting at 1 and increasing by 1 with each new definition of a use case.* + +*If appropriate, sequence and state chart diagrams may be used.* + +*NOTE – Guidelines and criteria for use of sequence diagrams and state chart diagrams are for further study.* + +*Use case specifications should follow the conventions and templates defined in clause A.1.* + +*See also clause 2.4.a for additional guidelines on simplified use case formats.* + +### **A.3 Simplified requirements template** + +The simplified requirements template is an alternative template for use in cases when only the textual requirements are required. A separate template is defined to avoid ambiguity that would result by adding options in the full-form template described in clause A.2. + +### 1 Concepts and background + +*Define major goals and objectives and the applicable management interfaces (and reference points) for this specification. Use [ITU-T M.3200] categorization as a source for identifying the management service(s) supported by this interface.* + +*This clause should give a clear description of the users' benefit, i.e., the reason for performing this management service. Background and context should be added as necessary, but the explanatory and descriptive parts should be separated. Supporting background information, where required, should be placed in an appendix.* + +#### 1.a SubClauseTitle + +*SubClauseTitle is the name of the subclause.* + +*"a" represents a number, starting at 1 and increasing by 1 with each new subclause.* + +*The use of subclauses is optional.* + +### 2 Requirements + +#### 2.a SubSetTitle + +*SubSetTitle is the name of a sub-set of the business level requirements.* + +*"a" represents a number, starting at 1 and increasing by 1 with each new sub-set.* + +*The use of sub-sets is optional and all business level requirements can be stated in clause 2 (requirements).* + +*List major requirements in text, and identify use cases with actor/role and resources. The use cases should bring out high-level requirements and are distinguished from the specification requirements by not refining to lower levels. Policy-related information (e.g., security, persistence) are candidates for inclusion at this level. Numbering the requirements is required for traceability.* + +*Requirements should be specified as described in clause A.1.3. Within a requirements specification, it is suggested that requirements are written in the sequence of clause A.1.3 (either for the entire specification or for each sub-set).* + +*Use of requirements categories is optional, and – when used – a subset of the categories can be applied.* + +*As an example, conceptual requirement number 23 in a Recommendation tagged 'SM' would be specified as follows:* + +| Identifier | Definition | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-SM-CON-23 | A Service Order consists of a name, address, phone number, service description and an optional FAX number for contacts {T1M1.5 Document 246 11/96} | + +*One or more tables can be used with supportive text between tables as necessary.* + +*See also A.2/2.1.a for additional guidelines.* + +# Annex B + +## Analysis + +(This annex forms an integral part of this Recommendation.) + +## *B.1 Conventions* + +#### *B.1.1 Mandatory, optional and conditional qualifiers* + +## *B.2 Analysis template* + +### *1 Concepts and background* + +#### *1.a SubClauseTitle* + +### *2 Model* + +#### *2.1 Imported and associated information entities* + +#### *2.1.1 Imported information entities and local labels* + +#### *2.1.2 Associated information entities and local labels* + +#### *2.2 Class diagram* + +#### *2.2.1 Relationships* + +#### *2.2.2 Inheritance* + +#### *2.3 Class definitions* + +#### *2.3.a InformationObjectClassName* + +##### *2.3.a.1 Definition* + +##### *2.3.a.2 Attributes* + +##### *2.3.a.3 Attribute constraints* + +##### *2.3.a.4 Notifications* + +##### *2.3.a.5 State diagram* + +#### *2.4 Attribute definitions* + +#### *2.4.1 Attribute properties* + +#### *2.4.2 Constraints* + +#### *2.5 Common notifications* + +#### *2.5.1 Alarm notifications* + +#### *2.5.2 Configuration notifications* + +#### *2.6 System state model* + +### *3 Interface definition* + +#### *3.1 Class diagram representing interfaces* + +#### *3.2 Generic rules* + +#### *3.b Interface InterfaceName (supportQualifier)* + +#### *3.b.a Operation OperationName (supportQualifier)* + +##### *3.b.a.1 Definition* + +##### *3.b.a.2 Input parameters* + +##### *3.b.a.3 Output parameters* + +##### *3.b.a.4 Pre-condition* + +- 3.b.a.5 *Post-condition* +- 3.b.a.6 *Exceptions* +- 3.b.a.6.c *exceptionName* +- 3.b.a.7 *Constraints* +- 3.b.b *Notification NotificationName (supportQualifier)* +- 3.b.b.1 *Definition* +- 3.b.b.2 *Input parameters* +- 3.b.b.3 *Triggering event* +- 3.b.b.3.1 *From state* +- 3.b.b.3.2 *To state* +- 3.b.b.4 *Constraints* +- 3.c *Scenario* +- B.3 *IOC properties, inheritance and import* +- B.3.1 *Property* +- B.3.2 *Inheritance* +- B.3.3 *Import* + +The following are guidelines for specification of the results of the analysis phase. + +The analysis template is based on the 3rd Generation Partnership Project (3GPP) information service [b-3GPP TS 32.157] and augmented to meet additional requirements on the methodology (e.g., traceability). + +For a management interface specification, both subclauses 2.2 and 2.3 of "Analysis" template indicated in clause B.2 shall be used. For an information model (e.g., a network resource model), only subclause 2.2 shall be used. + +The analysis 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 Annex E. + +An example of the use of this template can be found in Appendix II. + +The constructs "Analysis|Information Service" and "Design|Solution" sets are used to denote the equivalent, but differently named, specifications developed by ITU-T and 3GPP. + +## **B.1 Conventions** + +#### **B.1.1 Mandatory, optional and conditional qualifiers** + +This clause defines a number of terms used to qualify the relationship between the Analysis|Information service, the Design|Solution sets and their impact on the interface implementations. The qualifiers defined in this clause are used to qualify agent behaviour only. This is considered sufficient for the specification of the management interfaces. + +Analysis specification|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 Recommendation|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 Recommendation|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 Designs|Solutions sets (SSs). + +Design|SS specifications define the SS-equivalents of the 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 Analysis|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 B.1 defines the semantics of qualifiers of the equivalents, in terms of support from the agent perspective. + +**Table B.1 – Semantics for qualifiers used in Design|Solution sets** + +| Mapped SS equivalent | Mandatory | Optional | Conditional-Mandatory (CM) | Conditional-Optional (CO) | +|--------------------------------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Mapped notification equivalent | The agent shall generate the notification. | The agent may or may not generate it. | The agent shall generate this notification if the constraint for this item is satisfied. | The agent may choose whether or not to generate it. If the agent chooses to generate it, the constraint for this notification must be satisfied. | +| Mapped operation equivalent | The agent shall support it. | The agent may or may not support this operation. If the agent does not support this operation, the agent shall reject the operation invocation with a reason indicating that the agent does not support this operation. The rejection, | The agent shall support this operation if the constraint for this item is satisfied. | The agent may support this operation if the constraint for this item is satisfied. | + +**Table B.1 – Semantics for qualifiers used in Design|Solution sets** + +| Mapped SS equivalent | Mandatory | Optional | Conditional-Mandatory (CM) | Conditional-Optional (CO) | +|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| | | together with a reason, shall be returned to the manager. | | | +| Input parameter of the mapped operation equivalent | The agent shall accept and behave according to its value. | The agent may or may not support this input parameter. If the agent does not support this input parameter and if it carries meaning (i.e., it does not carry no-information semantics), the 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 manager. | The agent shall accept and behave according to its value if the constraint for this item is satisfied. | The agent may accept and behave according to its value if the constraint for this item is satisfied. | +| Input parameter of mapped notification equivalent
AND
output parameter of mapped operation equivalent | The agent shall supply this parameter. | The agent may supply this parameter. | The agent shall supply this parameter if the constraint for this item is satisfied. | The agent may supply this parameter if the constraint for this item is satisfied. | +| Mapped IOC attribute equivalent | The agent shall support it. | The agent may support it. | The agent shall support this attribute if the constraint for this item is satisfied. | The agent may support this attribute if the constraint for this item is satisfied. | + +### B.2 Analysis template + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

1 Concepts and background
This clause should provide an introduction to the management interface specification analysis.

1.a SubClauseTitle
SubClauseTitle is the name of a subclause.
"a" represents a number, starting at 1 and increasing by 1 with each new subclause.
The use of subclauses is optional.

2 Model
This clause shall be used for all specifications (both management interface specifications and information model only specifications).

2.1 Imported and associated information entities

2.1.1 Imported information entities and local labels
This subclause identifies a list of information entities (e.g., information object class, interface, attribute) that have been defined in other specifications and that are imported in the present (target) specification. All

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +*imported entities shall be treated as defined locally in the target specification. One usage for import is for inheritance purpose.* + +*Each element of this list is a pair (label reference, local label). The local label contains the name of the information entity that appears in the target specification, and the entity name in the local label shall be kept identical to the name defined in the original specification. 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 as shown below.* + +| Label reference | Local label | +|------------------------|--------------------| +| | | + +*Guidelines on entity import as well as IOC properties and inheritance can be found in Annex F.* + +#### **2.1.2 Associated information entities and local labels** + +*This clause identifies a list of information entities (e.g., information object class, interface, attribute) that have been defined in other specifications and that are associated with the information entities defined in the present (target) specification. For the associated information entity, only its properties, attribute of an instance of the associated information entity) used as associated information needs to be supported locally in the target specification.* + +*Each element of this list is a pair (label reference, local label). The label reference contains the name of the original specification where the information entity is defined, the information entity type and its name. The local label contains the name of the information entity that appears in the target specification. The local label can then be used throughout the target specification instead of that which appears in the label reference.* + +*This information is provided in a table as shown below.* + +| Label reference | Local label | +|------------------------|--------------------| +| | | + +#### **2.2 Class diagram** + +#### **2.2.1 Relationships** + +*This first set of diagrams represents all classes defined in this specification with all their relationships and all their attributes, including relationships with imported and associated information entities (if any). These diagrams shall contain information object class cardinalities (for associations as well as containment relationships) and may also contain role names. These shall be UML compliant classes diagrams (see also Annex C).* + +*Characteristics (relationships) of imported and associated information object classes need not be repeated in the diagram.* + +*Allowable classes are specified in Annex C.* + +*Use this as the first paragraph: "This clause depicts the set of classes (e.g., IOCs) that encapsulates the information relevant for this management specification. 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."* + +#### **2.2.2 Inheritance** + +*This second set of diagrams represents the inheritance hierarchy of all information object classes defined in this specification. These diagrams do not need to contain the complete inheritance hierarchy but shall at least contain the parent classes of all classes defined in the present document. By default, a class inherits from the class "top".* + +*Characteristics (attributes, relationships) of imported classes need not be repeated in the diagram.* + +*NOTE 1 – Some inheritance relationships presented in subclause 2.2.2 can be repeated in subclause 2.2.1 to enhance readability.* + +*Use "This subclause depicts the inheritance relationships." as the first paragraph.* + +#### 2.3 Class definitions + +Each class is defined using the following structure. + +Inherited items (attributes, etc.) shall not be shown, as they are defined in the parent classes(es) and thus valid for the subclass. + +#### 2.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 a class. + +##### 2.3.a.1 Definition + +This subclause is written in natural language. This subclause refers to the class itself. + +Optionally, information on traceability back to one or more requirements supported by this class can be defined here, in the following form: + +| Referenced specification | Requirement label | Comment | +|--------------------------|-------------------|---------| +| | | | + +##### 2.3.a.2 Attributes + +This clause presents the list of attributes, which are the manageable properties of the class. + +Each attribute is characterised by some of the attribute properties (see Table C.1), i.e., supportQualifier, isReadable, isWriteable, isInvariant and isNotifyable. + +The legal values and their semantics for attribute properties are defined in Annex C. + +This information is provided in a table as shown below. + +| Attribute name | Support qualifier | isReadable | isWriteable | isInvariant | isNotifyable | +|----------------|-------------------|------------|-------------|-------------|--------------| +| | | | | | | + +The attributeName indicates the name of the attribute. An attributeName with an "\*" sign indicates that this attribute is a naming attribute that will be used in the DN/RDN naming tree. The value of the naming attribute in each object instance shall be unique under its parent object instance. + +In case there is one or more attributes related to role (see clause 2.10 of Annex C), the attributes related to role shall be specified at the bottom of the table with a divider "Attribute related to role", as shown in the following example: + +| Attribute name | Support qualifier | isReadable | isWriteable | isInvariant | isNotifyable | +|----------------------------------|-------------------|------------|-------------|-------------|--------------| +| ... | | | | | | +| ... | | | | | | +| Attribute related to role | | | | | | +| ... | | | | | | +| ... | | | | | | + +##### 2.3.a.3 Attribute constraints + +This clause presents constraints for the attributes, and one usage is to present the predicates for conditional qualifiers (CM/CO). + +This information is provided in a table as shown below. + +| Name | Definition | +|------|------------| +| | | + +This subclause shall state "None." when there is no attribute constraint to define. + +##### 2.3.a.4 Notifications + +The subclause, for this class, presents one of the following options: + +- a) The class defines (and independent from those inherited) the support of a set of notifications that is identical to that defined in clause 2.5. In such case, use "The common notifications defined in clause 2.5 are valid for this class, without exceptions or additions." as the lone sentence of this clause. +- b) The class defines (and independent from those inherited) the support of a set of notifications that is a superset of that defined in clause 2.5. In such case, use "The common notifications defined in clause 2.5 are valid for this class. In addition, the following set of notification is also valid." as the lone paragraph of this clause. Then, define the 'additional' notifications in a table. See clause 2.5 for the notification table format. +- c) The class defines (and independent from those inherited) the support of a set of notifications that is not identical to, nor a superset of, that defined in clause 2.5. In such case, use "The common notifications defined in clause 2.5 are not valid for this class. The set of notifications defined in the following table is valid." as the lone paragraph of this clause. Specify the set of notifications in a table. See clause 2.5 for the notification table format. +- d) The class does not define (and independent from those inherited) the support of any notification. In such case, use "There is no notification defined." as the lone sentence of this clause. + +The notifications identified (options a-c above) in this subclause are notifications that can be emitted across the management interface, where the "object class" and "object instance" parameters of the notification header (see Note 2) of these notifications identify an instance of the IOC defined by the encapsulating subclause (i.e., subclause 2.3.a). + +The notifications identified (options a-c above) in this subclause may originate from implementation object(s) whose identifier is mapped in the implementation, to the object instance identifier used over the management interface may or may not be the same as that carried in the notification parameters "object class" and "object instance". Hence, the identification of notifications in this subclause does not imply nor identify those notifications as being originated from an instance of the class (or its direct or indirect derived class) defined by the encapsulating subclause (i.e., subclause 2.3.a). + +**NOTE 1** – This clause shall state "This class does not support any notification." (see option-c) when there is no notification defined for this class. (Note that if its parent class has defined some notifications, the implementation of this class is capable of emitting those inherited defined notifications.). + +**NOTE 2** – The notification header is defined in the notification integration reference point (IRP) information service [b-3GPP TS 32.302]. + +**NOTE 3** – The qualifier of a notification, specified in Notification Table, indicates if an implementation can generate a notification carrying the DN of the subject class. The qualifier of a notification, specified in a management specification, indicates if an implementation of the management specification can generate such notification in general. + +A Manager can receive notification-XYZ that carries DN (the "object class" and "object instance") of class-ABC instance if and only if: + +- 1) The class-ABC Notification Table defines the notification-XYZ and +- 2) The class-ABC instance implementation supports this notification-XYZ and +- 3) A management interface defines the notification-XYZ and +- 4) The management interface implementation supports this notification-XYZ. + +##### 2.3.a.5 State diagram + +This 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 machine diagram (see 15.4 of [UML2]). + +This subclause shall state "None." when there is no State diagram defined. + +#### 2.4 Attribute definitions + +#### 2.4.1 Attribute properties + +It has a lone paragraph "The following table defines the properties of attributes that are specified in the present document." + +Each information attribute is defined using the following structure. + +Inherited attributes shall not be shown, as they are defined in the parent class(es) and thus valid for this class. + +An attribute has properties (Table C.1). Some properties of an attribute are defined in 2.3.a.2 (e.g., Support Qualifier). The remaining properties of an attribute (e.g., documentation, default value) are defined here. + +The information is provided in a table. In case a) attributes of the same name are specified in more than one class and b) the attributes have different properties, then the attribute names (first column) should be prefixed with the class name followed by a period. + +An example is given below: + +| Attribute Name | Documentation and Allowed Values | Properties | +|----------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| xyzId | It identifies ...
allowedValues ... | type: Integer
multiplicity: ...
isOrdered: ...
isUnique: ...
defaultValue: ...
isNullable: False | +| | | | +| | | | + +In case there is one or more attributes related to role (see clause 2.10 of Annex C), the attributes related to role shall be specified at the bottom of the table with a divider "Attribute related to role". See example below. + +| Attribute Name | Documentation and Allowed Values | Properties | +|----------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| abc | It identifies ...
allowedValues ... | type: Integer
multiplicity: ...
isOrdered: ...
isUnique: ...
defaultValue: ...
isNullable: False | +| Attribute Related to Role | | | +| aEnd | It identifies ...
allowedValues ... | type: DN
multiplicity: ...
isOrdered: ...
isUnique: ...
defaultValue: ...
isNullable: False | + +This clause shall state "None." if there is no attribute to define. + +#### 2.4.2 Constraints + +This clause indicates whether there are any constraints affecting attributes. Each constraint is defined by a tuple (propertyName, affected attributes, propertyDefinition). PropertyDefinitions are expressed in natural language. + +This information is provided in a table as shown below. + +| Name | Affected attribute(s) | Definition | +|------|-----------------------|------------| +| | | | + +This subclause shall state "None." if there is no constraint. + +#### 2.5 Common notifications + +This clause presents a list of notifications that can be referred to by any class defined in the specification. This information is provided in a table as shown below. + +| Name | Qualifier | Notes | +|------|-----------|-------| +| | | | + +*This subclause shall state "None." if there are no common notifications.* + +#### 2.5.1 Alarm notifications + +*The following quoted text shall be copied as the only paragraph of this clause.* + +"This clause presents a list of notifications, defined in [x], that a manager can receive. The notification header attribute objectClass/objectInstance, defined in [y], shall capture the DN of an instance of a class defined in this specification." + +*The information is provided in a table as shown below.* + +| Name | Qualifier | Notes | +|------|-----------|-------| +| | | | + +#### 2.5.2 Configuration notifications + +*The following quoted text shall be copied as the only paragraph of this clause.* + +"This clause presents a list of notifications, defined in [x], that IRPManager can receive. The notification header attribute objectClass/objectInstance, defined in [z], shall capture the DN of an instance of a class defined in this specification." + +*The information is provided in a table as shown below.* + +| Name | Qualifier | Notes | +|------|-----------|-------| +| | | | + +#### 2.6 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 subclause 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.* + +### 3 Interface definition + +*This clause shall be used for all management interface specifications and optional for information model only specifications.* + +#### 3.1 Class diagram representing interfaces + +*Each interface is defined in one or more UML-compliant classes diagrams (see also Annex C, and 10.2 of [OMG UML1]).* + +#### 3.2 Generic rules + +*The following rules are relevant to all specifications. 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 regard 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.* + +*NOTE – Security considerations and resulting generic rules are for further study.* + +#### 3.b Interface `InterfaceName` (`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) (see also clause B.1).* + +*"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.* + +*If the interface is related to operation(s), the following subclause 3.b.a "`Operation OperationName` (`supportQualifier`)" shall be applied.* + +*If the interface is related to notification(s), subclause 3.b.b "`Notification NotificationName` (`supportQualifier`)" below shall be applied.* + +#### 3.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) (see clause B.1).* + +*"a" represents a number, starting at 1 and increasing by 1 with each new definition of an operation.* + +##### 3.b.a.1 Definition + +*This 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:* + +| Reference | Requirements label | Comment | +|-----------|--------------------|---------| +| | | | + +##### 3.b.a.2 Input parameters + +*List of input parameters of the operation. Each element is a tuple (Parameter Name, Support Qualifier, Information Type (see Annex E and Note in clause E.2) and an optional list of Legal Values supported by the parameter, Comment). Legal values for the Support Qualifier are: Legal Values for the Support Qualifier are: Mandatory (M), Optional (O), Conditional-Mandatory (CM), Conditional-Optional (CO), or SS-Conditional (C) (see also in clause B.1).* + +*This information is provided in a table as shown below.* + +| Parameter Name | Support Qualifier | Information Type/
Legal Values | Comment | +|----------------|-------------------|-----------------------------------|---------| +| | | | | + +*NOTE – 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.* + +##### 3.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 Annex E and Note in clause E.2) 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) (see also clause B.1).* + +*This information is provided in a table as shown below.* + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|----------------|-------------------|------------------------------------------------------------|---------| +| | | | | + +*NOTE – 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.).* + +##### 3.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 (name, definition). All assertions constituting the pre-condition are provided in a table as shown below. + +| Assertion name | Definition | +|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notificationCategoriesNotAllSubscribed | At least one notificationCategory identified in the notificationCategories input parameter is supported by IRP Agent 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 IRP Agent 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. | + +##### 3.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 (name, definition). All assertions constituting the post-condition are provided in a table as shown 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 longer involved in any subscription relationship and is deleted, the corresponding ntfSubscription have been deleted as well. | + +##### 3.b.a.6 Exceptions + +List of exceptions that can be raised by the operation. Each element is a tuple (exceptionName, condition, ReturnedInformation, exitState). + +###### 3.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 as shown below.* + +| Exception name | Definition | | +|----------------|-------------|--| +| | Condition | | +| | Return info | | +| | Exit state | | +| | Condition | | +| | Return info | | +| | Exit state | | + +##### 3.b.a.7 Constraints + +*This subclause presents constraints for the operation or its parameters.* + +*NOTE – This subclause does not need to be present when there are no constraints to be defined.* + +#### 3.b.b 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) (see clause B.1).* + +*"b" represents a number, starting at 1 and increasing by 1 with each new definition of a notification.* + +##### 3.b.b.1 Definition + +*This 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:* + +| Reference | Requirement label | Comment | +|-----------|-------------------|---------| +| | | | + +##### 3.b.b.2 Input parameters + +*List of input parameters of the notification. Each element is a tuple (Parameter Name, Qualifiers, Matching Information/Information Type (see Annex E and Note in clause E.2) and an optional list of Legal Values supported by the parameter, Comment).* + +*The column "Qualifiers" contains the two qualifiers, Support Qualifier (see clause B.1) and Filtering Qualifier, separated by a comma. 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 as shown below.* + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| alarmType | M,Y | AlarmInformation.eventType /
ENUMERATED /
"Communications Alarm": a
communication error alarm.
"Processing Error Alarm": a
processing error alarm.
"Environmental Alarm": an
environmental violation
alarm.
"Quality Of Service Alarm": a
quality of service violation
alarm.
"Equipment Alarm": an alarm
related to equipment
malfunction. | | + +*NOTE – 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.* + +##### 3.b.b.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.* + +###### 3.b.b.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 (name, definition). All assertions constituting the state "from state" are provided in a table as shown below.* + +| Assertion name | Definition | +|----------------|------------| +| | | + +###### 3.b.b.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.* + +*Each assertion is defined by a pair (name, definition). All assertions constituting the state "to state" are provided in a table as shown below.* + +| Assertion name | Definition | +|----------------|------------| +| | | + +##### 3.b.b.4 Constraints + +*This subclause presents constraints for the notification or its parameters.* + +*NOTE – This subclause does not need to be present when there are no constraints to be defined.* + +#### 3.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.* + +### B.3 IOC properties and inheritance + +#### B.3.1 Property + +The following guidelines are based on Annex G of [b-3GPP TS 32.150]. + +The properties of an IOC (excluding 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 A and B is optional. It is mandatory if the A instance belongs to one ManagedElement instance while the B 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 is abstract and no parents have yet been designated. + - 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. + - 3) The IOC is not abstract and all of the possible parent(s) have been designated and whether the IOC can be designated as a root IOC. + +An IOC instance is either a root IOC or it has one and only one parent. + +NOTE 2 – The parent and child relation in this subclause 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. + - 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. + - 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. +- g) Whether An IOC can be instantiated or not (i.e., whether an IOC is an abstract IOC). +- h) An attribute for naming purpose. + +#### B.3.2 Inheritance + +The following guidelines are based on Annex G of [b-3GPP TS 32.150]. + +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. + +#### **B.3.3 Import** + +The following guidelines are based on Annex I of [b-3GPP TS 32.150]. + +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 C + +## MIISM UML repertoire + +(This annex forms an integral part of this Recommendation.) + +The following are guidelines for specification of the results of the analysis phase as based on 3GPP unified modelling language (UML) repertoire [b-3GPP TS 32.156]. + +### C.1 Introduction + +UML provides a rich set of concepts, notations and model elements to model distributed systems. Usage of all UML notations and model elements is not necessary for the purpose of analysis specifications. This annex documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <>, for use by development of protocol-neutral specifications. Collectively, this set of notations and model elements is called the UML modelling repertoire. + +Recommendations following the methodology shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. + +### C.2 Basic model elements + +#### C.2.1 General + +UML has defined a number of basic model elements. This clause lists the selected subset for use in specifications based on the repertoire. The semantics of these selected basic model elements are defined in [OMG UML1]. + +For each basic model element listed, there are three parts. The first part contains its description. The second part contains its graphical notation examples and the third part contains the rule, if any, recommended for labelling or naming it. + +The graphical notation has the following characteristics: + +- a) Subclause 7.2.7 of [OMG UML2] specifies "A class is often shown with three compartments. The middle compartment holds a list of attributes while the bottom compartment holds a list of operations" and "Additional compartments may be supplied to show other details". This repertoire only allows the use of the name (top) compartment and attribute (middle) compartment. The operation (bottom) compartment may be present but is always empty, as shown in the figure below. + +![UML class diagram with three compartments: top compartment contains '', middle compartment contains 'Attribute', and bottom compartment is empty.](6757222e979ee95c44354a897c5cc1c1_img.jpg) + +A UML class diagram consisting of a rectangle divided into three horizontal compartments. The top compartment contains the text "". The middle compartment contains the text "Attribute". The bottom compartment is empty. + +UML class diagram with three compartments: top compartment contains '', middle compartment contains 'Attribute', and bottom compartment is empty. + +- b) Classes may or may not have attributes. The graphical notation of a class may show an empty attribute (middle) compartment even if the class has attributes, as shown in figure below. + +![UML class diagram with three compartments: top compartment contains '', middle compartment is empty, and bottom compartment is empty.](fb5442ad7130829bed9e3682ccb84c87_img.jpg) + +A UML class diagram consisting of a rectangle divided into three horizontal compartments. The top compartment contains the text "". The middle compartment is empty. The bottom compartment is empty. + +UML class diagram with three compartments: top compartment contains '', middle compartment is empty, and bottom compartment is empty. + +- c) The visibility symbol shall not appear along with the class attribute, as shown below. + +![UML class diagram showing a class named 'Xvz' with the stereotype '«InformationObjectClass»'. The class has three compartments: the top compartment contains the stereotype and name, the middle compartment contains attributes 'a', 'b', and 'c', and the bottom compartment is empty.](70a863dc6cd47bac82c12162a9479aac_img.jpg) + +UML class diagram showing a class named 'Xvz' with the stereotype '«InformationObjectClass»'. The class has three compartments: the top compartment contains the stereotype and name, the middle compartment contains attributes 'a', 'b', and 'c', and the bottom compartment is empty. + +- d) The use of the decoration, i.e., the symbol in the name (top) compartment, is optional. + +#### C.2.2 Attribute + +##### C.2.2.1 Description + +It is a typed element representing a property of a class. See 10.2.5 Property of [OMG UML1]. + +An element that is typed implies that the element can only refer to a constrained set of values. + +See 10.1.4 Type of [OMG UML1] for more information on type. + +See clauses C.3.5 and C.4.3 for predefined data types and user-defined data types that can apply type information to an element. + +Table C.1 captures the properties of this modelled element. + +**Table C.1 – Attribute properties** + +| Property name | Description | Legal values | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| type | Refers to a predefined (see clause C.4.3) or user defined data type (see clause C.3.5. See also clause 7.3.44 of [OMG-UML2]; inherited from StructuralFeature. | N/A | +| allowedValues | Specifies restrictions to the data type defined by type. This property is useful when no dedicated data type, that includes the restriction, shall be defined. The property may be absent when no restrictions are defined.

(When specific values or restrictions are listed, it means that other values are not allowed) | Dependent on type | +| defaultValue | Identifies a value at specification time that is used at object creation time under conditions defined in Annex G.
If there is no defined default value, the property shall be omitted from the attribute description or specified as 'defaultValue: None.' | No value (default) or a value that is dependent on allowedValues | +| multiplicity | Defines the number of values the attribute can simultaneously have. See clause 7.3.44 of [OMG UML2]; inherited from StructuralFeature. | See clause C.2.9
Default is 1 | +| isOrdered | For a multi-valued multiplicity; this specifies if the values of this attribute instance are sequentially ordered. See clause 7.3.44 and its Table 7.1 of [OMG UML2].
If the property is present for attributes with a multiplicity of greater than "1", it shall be set to either "True" or "False". It shall not be set to "N/A". | True, False (default) | + +**Table C.1 – Attribute properties** + +| Property name | Description | Legal values | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| isUnique |

For a multi-valued multiplicity, this specifies if the values of this attribute instance are unique (i.e., no duplicate attribute values). See clause 7.3.44 and its Table 7.1 of [OMG UML2].

If the property is present for attributes with a multiplicity of greater than "1", it shall be set to either "True" or "False". It shall not be set to "N/A".

| True (default), False | +| isNullable |

Identifies if an attribute can carry no information. The implied meaning of carrying "no information" is context sensitive and is not defined in this Recommendation.

Note, the property "isNullable: True" is semantically identical to adding the value "0" to the "multiplicity" specified. Usage of the "multiplicity" property is preferred to express an attribute can have no value or carry no information.

| True, False (default) | +| passedById | See Table C.4: passedById property | True, False (default) | +| isInvariant |

If an attribute has an "isInvariant: True" property, its value can be set only upon object creation. After object creation, the initial value cannot be modified.

If an attribute has an "isInvariant: False" property, its value can be set at object creation time. After object creation, the initial value can be modified.

Details on how initial values are provided upon object creation are specified in Annex G.

| True, False (default) | +| isWritable |

If an attribute has an "isWritable: True" property, a manager can set its value upon object creation. After object creation, a manager can modify the initial value if "isInvariant: False". If "isInvariant: True", a manager cannot modify the initial value. The "isInvariant" property supersedes hence the "isWritable" property.

If an attribute has an "isWritable: False" property, a manager cannot set the value upon object creation nor modify it later. A "isWritable: True" property might be restricted by access control.

| True, False (default) | +| isReadable |

Specifies if the attribute can be read by the manager.

A "isReadable: True" property might be restricted by access control.

| True (default), False | +| isNotifiable | Identifies if a notification shall be sent in case of a value change. | True (default), False | +| documentation |

Contains a textual description of the attribute.

Should refer (to enable traceability) to the specific requirement.

| Any | +| supportQualifier | Identifies the required support of the attribute. See also clause 7. | M, O (default), CM, CO, C | + +##### C.2.2.2 Example + +This example shows three attributes, i.e., a, b and c, listed in the attribute (the second) compartment of the class Xyz. + +![UML class diagram showing a class named Xyz with three attributes: a, b, and c.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) + +The diagram shows a class box for 'Xyz'. The top compartment contains the stereotype «InformationObjectClass» and the class name 'Xyz'. The second compartment contains the attributes 'a', 'b', and 'c' listed vertically. The third compartment is empty. + +UML class diagram showing a class named Xyz with three attributes: a, b, and c. + +**Figure C.1 – Attribute notation** + +##### C.2.2.3 Name style + +An attribute name shall use the LCC style. + +Well known abbreviation (WKA) is treated as a word if used in a name. However, WKA shall be used as is (its letter case cannot be changed) except when it is the first word of a name; and if so, its first letter must be in lower case. + +#### C.2.3 Association relationship + +##### C.2.3.1 Description + +It shows a relationship between two classes and describes the reasons for the relationship and the rules that might govern that relationship. + +It has ends. Its end, the association end(s), specifies the role that the object at one end of a relationship performs. Each end of a relationship has properties that specify the role (see clause C.2.10), multiplicity (see clause C.2.9), visibility and navigability (see the arrow symbol used in Figure C.3 – Unidirectional association relationship notation) and may have constraints. Note that visibility shall not be used in models based on this Repertoire (see paragraph 3 of clause C.2.1). + +See 7.3.3 Association of [OMG UML2]. + +The three examples given in Figures C.2 to C.4 show a binary association between two model elements. The association can include the possibility of relating a model element to itself. + +The first example (Figure C.2) shows a bidirectional navigable association in that each model element has a pointer to the other. The second example (Figure C.3) shows a unidirectional association (shown with an open arrow at the target model element end) in that only the source model element has a pointer to the target model element and not vice-versa. The third example (Figure C.4) shows a bidirectional non-navigable association in that each model element does not have a pointer to the other; i.e., such associations are just for illustration purposes. + +##### C.2.3.2 Example + +An association shall have an indication of cardinality (see clause C.2.9). + +It shall, except the case of non-navigable association, have an indication of the role name (see clause C.2.10). The model element involved in an association is said to be "playing a role" in that association. The role has a name such as +class3 in the first example below. Note that the "+" character in front of the role name, indicating the visibility, is ignored. + +![Figure C.2: Bidirectional association relationship notation. Two identical diagrams showing Class3 and Class4 connected by a bidirectional association line. In both, Class3 is on the left and Class4 is on the right. The association has role names '+ class3' and '+ class4'. The multiplicity at the Class3 end is 0..1, and at the Class4 end is *.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +``` + +classDiagram + Class3 "0..1" <--> "*" Class4 : + class3 / + class4 + Class3 "0..1" <--> "*" Class4 : + class3 / + class4 + +``` + +Figure C.2: Bidirectional association relationship notation. Two identical diagrams showing Class3 and Class4 connected by a bidirectional association line. In both, Class3 is on the left and Class4 is on the right. The association has role names '+ class3' and '+ class4'. The multiplicity at the Class3 end is 0..1, and at the Class4 end is \*. + +Figure C.2 – Bidirectional association relationship notation + +![Figure C.3: Unidirectional association relationship notation. Class3 is on the left and Class4 is on the right. A unidirectional association line points from Class3 to Class4. The association is named 'Class3IsRelatedToClass4'. The multiplicity at the Class3 end is *, and at the Class4 end is 0..1. A role name '+ class4' is present at the Class4 end.](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) + +``` + +classDiagram + Class3 "*" --> "0..1" Class4 : Class3IsRelatedToClass4 / + class4 + +``` + +Figure C.3: Unidirectional association relationship notation. Class3 is on the left and Class4 is on the right. A unidirectional association line points from Class3 to Class4. The association is named 'Class3IsRelatedToClass4'. The multiplicity at the Class3 end is \*, and at the Class4 end is 0..1. A role name '+ class4' is present at the Class4 end. + +Figure C.3 – Unidirectional association relationship notation + +![Figure C.4: Non-navigable association relationship notation. Class3 is on the left and Class4 is on the right. A non-navigable association line connects them. The multiplicity at the Class3 end is 1, and at the Class4 end is *.](cf8bd014a50b7c69435e804f67f9617f_img.jpg) + +``` + +classDiagram + Class3 "1" -- "*" Class4 + +``` + +Figure C.4: Non-navigable association relationship notation. Class3 is on the left and Class4 is on the right. A non-navigable association line connects them. The multiplicity at the Class3 end is 1, and at the Class4 end is \*. + +Figure C.4 – Non-navigable association relationship notation + +Note that some tools do not use arrows in the UML graphical representation for bidirectional associations. Therefore, absence of arrows is not, but absence of role names is, an indication of a non-navigable association. + +##### C.2.3.3 Name style + +An Association can have a name. The use of Association name is optional. Its name style is UCC style. + +A role name shall use the LCC style. + +#### C.2.4 Aggregation association relationship + +##### C.2.4.1 Description + +It shows a class as a part of or subordinate to another class. + +An aggregation is a special type of association in which objects are assembled or configured together to create a more complex object. Aggregation protects the integrity of an assembly of objects by defining a single point of control called aggregate, in the object that represents the assembly. + +See 7.3.2 AggregationKind (from Kernel) of [OMG UML2]. + +##### C.2.4.2 Example + +Figure C.5 shows that a hollow diamond attached to the end of a relationship is used to indicate an aggregation. The diamond is attached to the class that is the aggregate. The aggregation association shall have an indication of cardinality at each end of the relationship (see clause C.2.9). + +![Figure C.5: Aggregation association relationship notation. Class12 is on the left and Class13 is on the right. A hollow diamond is attached to the Class12 end, indicating aggregation. The multiplicity at the Class12 end is 1, and at the Class13 end is *. A role name '+ class13' is present at the Class13 end.](c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg) + +``` + +classDiagram + Class12 "1" o-- "*" Class13 : + class13 + +``` + +Figure C.5: Aggregation association relationship notation. Class12 is on the left and Class13 is on the right. A hollow diamond is attached to the Class12 end, indicating aggregation. The multiplicity at the Class12 end is 1, and at the Class13 end is \*. A role name '+ class13' is present at the Class13 end. + +Figure C.5 – Aggregation association relationship notation + +##### C.2.4.3 Name style + +An Association can have a name. Use of Association name is optional. Its name style is UCC. + +#### C.2.5 Composite aggregation association relationship + +##### C.2.5.1 Description + +A composite aggregation association is a strong form of aggregation that requires a part instance be included in at most one composite at a time. If a composite is deleted, all of its parts are deleted as well. + +A composite aggregation shall contain a description of its use. + +See 7.3.3 Association (from Kernel) of [OMG UML2]. + +##### C.2.5.2 Example + +A filled diamond attached to the end of a relationship (see Figure C.6) is used to indicate a composite aggregation. The diamond is attached to the class that is the composite. The composition association shall have an indication of cardinality at each end of the relationship (see clause C.2.9). + +![UML Class Diagram showing a composite aggregation association between ManagedElement and ManagedElementPropertySet.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +The diagram shows two classes: «InformationObjectClass» **ManagedElement** and «InformationObjectClass» **ManagedElementPropertySet**. A relationship line connects them. On the **ManagedElement** side, there is a filled diamond, indicating it is the composite. The cardinality at this end is '1'. The relationship is named '+ managedElementPropertySet' near the **ManagedElementPropertySet** end. The cardinality at the **ManagedElementPropertySet** end is '0..1'. + +UML Class Diagram showing a composite aggregation association between ManagedElement and ManagedElementPropertySet. + +Figure C.6 – Composite aggregation association relationship notation + +##### C.2.5.3 Name style + +An Association can have a name. The use of Association name is optional. Its name style is UCC. + +#### C.2.6 Generalization relationship + +##### C.2.6.1 Description + +Generalization indicates a relationship in which one class (the child) inherits from another class (the parent). + +See 7.3.20 Generalization of [OMG UML2]. + +##### C.2.6.2 Example + +The example in Figure C.7 shows a generalization relationship between a more general model element (the **IRPAgent**) and a more specific model element (the **IRPAgentVendorA**) that is fully consistent with the first element and that adds additional information. + +![UML Class Diagram showing a generalization relationship between IRPAgent and IRPAgentVendorA.](4f6da7645cec40b72385c93b2f4dc4be_img.jpg) + +The diagram shows two classes: «InformationObjectClass» **IRPAgent** and «InformationObjectClass» **IRPAgentVendorA**. A relationship line connects them with an open triangle arrowhead pointing towards **IRPAgent**, indicating that **IRPAgentVendorA** inherits from **IRPAgent**. + +UML Class Diagram showing a generalization relationship between IRPAgent and IRPAgentVendorA. + +Figure C.7 – Generalization relationship notation + +##### C.2.6.3 Name style + +Generalization has no name, so there is no name style. + +#### C.2.7 Dependency relationship + +##### C.2.7.1 Description + +A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation. This means that the complete semantics of + +the depending elements is either semantically or structurally dependent on the definition of the supplier element(s)...", an extract from 7.3.12 Dependency of [OMG UML2]. + +##### C.2.7.2 Example + +The example in Figure C.8 shows that the BClass instances have a semantic relationship with the AClass instances. It indicates a situation in which a change to the target element (the AClass in the example) will require a change to the source element (the BClass in the example) in the dependency. + +![UML diagram showing a dependency relationship between two classes. A dashed arrow points from a class labeled '«InformationObjectClass» BClass' to a class labeled '«InformationObjectClass» AClass'.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` +classDiagram + class AClass["«InformationObjectClass» AClass"] + class BClass["«InformationObjectClass» BClass"] + BClass --> AClass : dependency +``` + +UML diagram showing a dependency relationship between two classes. A dashed arrow points from a class labeled '«InformationObjectClass» BClass' to a class labeled '«InformationObjectClass» AClass'. + +Figure C.8 – Dependency relationship notation + +##### C.2.7.3 Name style + +A Dependency can have a name. Use of Dependency name is optional. Its name style is UCC. + +#### C.2.8 Comment + +##### C.2.8.1 Description + +A comment is a textual annotation that can be attached to a set of elements. + +See 7.3.9 Comment (from Kernel) from [OMG UML2]. + +##### C.2.8.2 Example + +The example in Figure C.9 shows a comment as a rectangle with a "bent corner" in the upper right corner. It contains text. It appears on a particular diagram and may be attached to zero or more modelling elements by dashed lines. + +![UML diagram showing a comment attached to a class. A class labeled '«InformationObjectClass» Function' is connected by a solid line to a yellow comment box with a bent corner. The comment box contains the text: 'This Function class is conceptually the same as ManagedFunction class (in the context of 3GPP NRM IRP).'](2beb95006f1933bed737cfe1e6598db8_img.jpg) + +``` +classDiagram + class Function["«InformationObjectClass» Function"] + note for Function "This Function class is conceptually the same as ManagedFunction class (in the context of 3GPP NRM IRP)." +``` + +UML diagram showing a comment attached to a class. A class labeled '«InformationObjectClass» Function' is connected by a solid line to a yellow comment box with a bent corner. The comment box contains the text: 'This Function class is conceptually the same as ManagedFunction class (in the context of 3GPP NRM IRP).' + +Figure C.9 – Comment notation + +##### C.2.8.3 Name style + +Comment notations have no name so there is no name style. + +#### C.2.9 Multiplicity (also known as cardinality in relationships) + +##### C.2.9.1 Description + +"A multiplicity is a definition of an inclusive interval of non-negative integers beginning with a lower bound and ending with a (possibly infinite) upper bound. A multiplicity element embeds this information to specify the allowable cardinalities for an instantiation of this element...", an extract from 7.3.32 MultiplicityElement of [OMG UML2]. + +**Table C.2 – Multiplicity-string definitions** + +| Multiplicity | Explanation | +|--------------|----------------------------------------------------------------------------| +| 1 | Attribute has one attribute value | +| m | Attribute has m attribute values | +| 0..1 | Attribute has zero or one attribute value | +| 0..* | Attribute has zero or more attribute values | +| * | Attribute has zero or more attribute values | +| 1..* | Attribute has at least one attribute value | +| m..n | Attribute has at least m but no more than n attribute values | + +The use of "0..n" and "0..\*" is not recommended although it has the same meaning as "\*". + +The use of a standalone symbol zero (0) is not allowed. + +##### **C.2.9.2 Example** + +Figure C.10 shows a multiplicity attached to the end of an association path. The meaning of this multiplicity is one to many. One Network instance is associated with zero, one or more SubNetwork instances. Other valid examples can show the "many to many" relationship. + +![UML Class diagram showing an association between Class1 and Class2. Class1 is on the left with multiplicity '1'. Class2 is on the right with multiplicity '*'. The association is labeled '+ class2' above the Class2 box.](683f755e8456c884716de4fce48c7e63_img.jpg) + +``` + +classDiagram + Class1 "1" --> "*" Class2 : + class2 + class Class1 { + <> + } + class Class2 { + <> + } + +``` + +UML Class diagram showing an association between Class1 and Class2. Class1 is on the left with multiplicity '1'. Class2 is on the right with multiplicity '\*'. The association is labeled '+ class2' above the Class2 box. + +**Figure C.10 – Cardinality notation** + +The cardinality zero is not used to indicate the IOC's so-called "transient state" characteristic. For example, it is not used to indicate that the instance is not yet created but it is in the process of being created. The cardinality zero will not be used to indicate this characteristic since such characteristic is considered inherent in all IOCs. All IOCs defined are considered to have such inherent "transient state" characteristics. + +Note that the use of "0..\*", "0..n" or "\*" means "zero to many". The use of "0..\*" is recommended. The following table shows some valid examples of multiplicity. + +**Table C.3 – Multiplicity-string examples** + +| Multiplicity | Explanation | +|--------------|---------------------------------------------------------------| +| 1 | Attribute has exactly one attribute value | +| 5 | Attribute has exactly 5 attribute values | +| 0..1 | Attribute has zero or one attribute value | +| 0..* | Attribute has zero or more attribute values | +| 1..* | Attribute has at least one attribute value | +| 4..12 | Attribute has at least 4 but no more than 12 attribute values | + +##### **C.2.9.3 Name style** + +Cardinality has no name so there is no name style. + +#### C.2.10 Role + +##### C.2.10.1 Description + +A role indicates navigation, from one class to another class, involved in an association relationship. A role is named. The direction of navigation is to the class attached to the end of the association relationship with (or near) the role name. + +The use of role name in the graphical representation is mandatory for bidirectional and unidirectional association relationship notations (see Figure C.2 – Bidirectional association relationship notation and Figure C.3 – Unidirectional association relationship notation). Role name shall not be used in non-navigable association relationship notation (see Figure C.4 – Non-navigable association relationship notation). + +A role at the navigable end of a relationship becomes (or is mapped into) an attribute (called role-attribute) in the source class of the relationship. Therefore roles have the same behaviour (or properties) as attributes. + +The role-attribute shall have all properties defined for attributes in clause C.2.2 and in addition the following property: + +**Table C.4 – passedById property** + +| Property name | Description | Legal values | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| passedById |

If True, the role-attribute (navigable association source end) contains a DN of the navigable association target end instance.

If False, the role-attribute contains (a copy of) the whole target end instance (e.g., X). If X has a role-attribute whose "passedById==False", then the subject role-attribute contains (a copy of) X's target end instance as well.

The above rule is applied repeatedly for all occurrences of "passedById==False". This application can result in a collection of instances where no ordering can be implied and no instances are duplicated.

Use of "passedById==False" supports the efficient access of target end instances from a source end instance. The mechanism by which such access is achieved is operation model design specific (e.g., not related to resource model design).

| True (default), False | + +##### C.2.10.2 Example + +The example in Figure C.11 shows that 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". + +![UML Class Diagram showing a bidirectional association between Company and Person. The Company class is on the left and the Person class is on the right. An association line connects them. At the Company end, there is a multiplicity of '1' and a role name '+ theCompany'. At the Person end, there is a multiplicity of '1'. Both classes are labeled with the stereotype <>.](f943b07ab747bfd85e302e5a31c20ba8_img.jpg) + +``` + +classDiagram + class Company { + <> + } + class Person { + <> + } + Company "1" -- "1" Person : + theCompany + +``` + +UML Class Diagram showing a bidirectional association between Company and Person. The Company class is on the left and the Person class is on the right. An association line connects them. At the Company end, there is a multiplicity of '1' and a role name '+ theCompany'. At the Person end, there is a multiplicity of '1'. Both classes are labeled with the stereotype <>. + +**Figure C.11 – Role notation** + +##### C.2.10.3 Name style + +A role has a name. Use noun for the name. The name style follows the attribute name style; see clause C.2.2.3. + +#### C.2.11 Xor constraint + +##### C.2.11.1 Description + +"A Constraint represents additional semantic information attached to the constrained elements. A constraint is an assertion that indicates a restriction that must be satisfied by a correct design of the system. The constrained elements are those elements required to evaluate the constraint specification...", an extract from 7.3.10 Constraint (from Kernel) of [OMG UML2]. + +For a constraint that applies to two elements such as two associations, the constraint shall be shown as a dashed line between the elements labelled by the constraint string (in braces). The constraint string, in this case, is xor. + +##### C.2.11.2 Example + +Figure C.12 shows a `ServerObjectClass` instance that has relation(s) to multiple instances of a class from the choice of `ClientObjectClass_Alternative1`, `ClientObjectClass_Alternative2` or `ClientObjectClass_Alternative3`. + +![UML Class Diagram illustrating the {xor} constraint notation. A base class 'ServerObjectClass' (stereotyped as <>) is shown at the top. It has three associations leading to three alternative classes: 'ClientObjectClass_Alternative1', 'ClientObjectClass_Alternative2', and 'ClientObjectClass_Alternative3' (all stereotyped as <>). Each association from 'ServerObjectClass' has a multiplicity of '1' at the top and '*' at the bottom, with the role name '+ clientObjectClass'. A dashed line connects the three associations, and a red box labeled '{xor}' is placed on this dashed line, indicating that the associations are mutually exclusive.](772cc583a60eeb058cc19de48269ad22_img.jpg) + +UML Class Diagram illustrating the {xor} constraint notation. A base class 'ServerObjectClass' (stereotyped as <>) is shown at the top. It has three associations leading to three alternative classes: 'ClientObjectClass\_Alternative1', 'ClientObjectClass\_Alternative2', and 'ClientObjectClass\_Alternative3' (all stereotyped as <>). Each association from 'ServerObjectClass' has a multiplicity of '1' at the top and '\*' at the bottom, with the role name '+ clientObjectClass'. A dashed line connects the three associations, and a red box labeled '{xor}' is placed on this dashed line, indicating that the associations are mutually exclusive. + +Figure C.12 – {xor} notation + +##### C.2.11.3 Name style + +The Xor constraint has no name so there is no name style. + +### C.3 Stereotypes + +#### C.3.1 General + +Clause C.2 lists the UML defined basic model elements. UML defined a stereotype concept allowing the specification of simple or complex user-defined model elements. + +This clause lists all allowable stereotypes for this repertoire. + +For each stereotype model element listed, there are three parts. The first part contains its description. The second part contains its graphical notation examples and the third part contains the rule, if any, recommended for labelling or naming it. + +#### C.3.2 <> + +##### C.3.2.1 Description + +This represents a number of <>. It encapsulates attributes, links, methods (or operations), and interactions that are present in the represented <>. + +The semantics of a <> is that all behaviour of the <> are present in the represented <>. 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 `<>`. + +A particular `<>` can be represented by zero, one or more `<>`. For example, the `ManagedElement` `<>` can have `MonitoredEntity` `<>` and `ManagedEntity` `<>`. + +The attributes of the `<>` are accessible by the source entity that has an association with the `<>`. + +##### C.3.2.2 Example + +Figure C.13 shows a `<>` named `MonitoredEntity`. It represents (or its constraints is that it represents) all NRM `<>` (e.g., `GgsnFunction` `<>`) whose instances are being monitored for alarm conditions. It is mandatory to use a Note to capture the constraint. + +![UML diagram showing a ProxyClass named MonitoredEntity with a note explaining its constraint.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +The diagram shows a class box for `<> MonitoredEntity`. A note box containing the text "It represents all NRM IOCs that can have alarms." is connected to the class box by a line. + +UML diagram showing a ProxyClass named MonitoredEntity with a note explaining its constraint. + +**Figure C.13 – `<>` Notation** + +See Appendix II for more examples that use `<>`. + +##### C.3.2.3 Name style + +For `<>` name, use the same style as `<>` (see clause C.3.3). + +#### C.3.3 `<>` + +##### C.3.3.1 Description + +The `<>` is identical to UML *class* except that it does not include/define methods or operations. + +A UML *class* represents a capability or concept within the system being modelled. Classes have data structure and behaviour and relationships to other elements. + +This class can inherit from zero, one or multiple classes (multiple inheritances). + +See more on UML *class* in 10.2.1 of [OMG UML1]. + +##### C.3.3.2 Example + +The example in Figure C.14 shows an `AbcFunction` `<>`. + +![UML diagram showing an InformationObjectClass named AbcFunction.](781be1b7270da21ee7b75b51db2ee1b3_img.jpg) + +The diagram shows a class box for `<> AbcFunction`. The box is light blue with a small icon representing a class. + +UML diagram showing an InformationObjectClass named AbcFunction. + +**Figure C.14 – `<>` Notation** + +Table C.5 captures the properties of this modelled element. + +**Table C.5 – <> properties** + +| Property name | Description | Legal values | +|------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| documentation | Contains a textual description of this modelled element. Should refer (to enable traceability) to a specific requirement. | Any | +| isAbstract | Indicates if the class can be instantiated or is just used for inheritance. | True, False (default) | +| isNotifyable | Identifies the list of the supported notifications. | List of names of notification | +| supportQualifier | Identifies the required support of the class. See also clause 7. | M, O (default), CM, CO, C | + +#### C.3.4 <> + +##### C.3.4.1 Description + +The <> is modelled by a composition association where both ends are non-navigable. The source class is the composition and the target class is the component. The target instance is uniquely identifiable, within the namespace of the source entity, among all other targeted instances of the same target class and among other targeted instances of other classes that have the same <> composition with the source. + +The source class and target class shall each have its own naming attribute. + +The composition aggregation association relationship is used as the act of name containment providing 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 cannot have multiple <> with multiple sources, i.e., a target instance cannot participate in or belong to multiple namespaces. + +##### C.3.4.2 Example + +Figure C.15 shows that all instances of Class4 are uniquely identifiable within a Class3 instance's namespace. + +![UML Class diagram showing a composition association between Class3 and Class4. Class3 is the composition (source) and Class4 is the component (target). The association is labeled '«names»'. Multiplicity '1' is at the Class3 end and '*' is at the Class4 end. Class3 and Class4 are both stereotyped as «InformationObjectClass».](6584b95e34ea1f0b67144aa841db0863_img.jpg) + +``` + +classDiagram + class3["«InformationObjectClass»\nClass3"] "1" *-- "*" "«InformationObjectClass»\nClass4" : «names» + +``` + +UML Class diagram showing a composition association between Class3 and Class4. Class3 is the composition (source) and Class4 is the component (target). The association is labeled '«names»'. Multiplicity '1' is at the Class3 end and '\*' is at the Class4 end. Class3 and Class4 are both stereotyped as «InformationObjectClass». + +**Figure C.15 – <> notation** + +##### C.3.4.3 Name style + +<> has no name so there is no name style. + +#### C.3.5 <> + +##### C.3.5.1 Description + +<> represents the general notion of being a data type (i.e., a type whose instances are identified only by their values) whose definition is defined by user (e.g., specification authors). + +This repertoire uses two kinds of data types: predefined data types and user-defined data types. The former is defined in clause C.4.3. The latter is defined by the specifications authors using this <> model element. + +The user-defined data types support the modelling of structured data types (see <> notations in clause C.3.5.3). When user-defined or predefined data type is used to apply type information to a class attribute (see clause C.2.2), the data type name is shown along with the class attribute. See user example of <> in clause C.3.5.3. + +##### C.3.5.2 Example + +The following examples are two user-defined data types. The left-most is named `PlmnId` that consists of mobile country code (MCC) and mobile network code (MNC), whose types are the predefined data types in clause C.4.3. The right-most is named `Xyz` that consists of two predefined data types (i.e., `String`, `Integer`) and one user-defined data type `PlmnId`. + +![Figure C.16: Two <> notations. The first is 'PlmnId' with attributes 'mCC : String' and 'mNC : String'. The second is 'Xyz' with attributes 'attribute1 : String', 'attribute2 : Integer', and 'attribute3 : PlmnId'.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|--------------------------------------------------------------------| +|
<<dataType>>
PlmnId
mCC : String
mNC : String
| <>
PlmnId | mCC : String
mNC : String |
<<dataType>>
Xyz
attribute1 : String
attribute2 : Integer
attribute3 : PlmnId
| <>
Xyz | attribute1 : String
attribute2 : Integer
attribute3 : PlmnId | +| <>
PlmnId | | | | | | +| mCC : String
mNC : String | | | | | | +| <>
Xyz | | | | | | +| attribute1 : String
attribute2 : Integer
attribute3 : PlmnId | | | | | | + +Figure C.16: Two <> notations. The first is 'PlmnId' with attributes 'mCC : String' and 'mNC : String'. The second is 'Xyz' with attributes 'attribute1 : String', 'attribute2 : Integer', and 'attribute3 : PlmnId'. + +**Figure C.16 – <> notations** + +Figure C.17 shows an example of a `ZClass` using two user-defined data types and two predefined data types. + +![Figure C.17: Usage example of <>. A ZClass with attributes attribute1 : PlmnId, attribute2 : Integer [1..*], attribute3 : String, and attribute4 : Xyz.](3493d7ba4c86f944e159de1bf45ff03d_img.jpg) + +| | +|-----------------------------------------------------------------------------------------------| +| <>
ZClass | +| attribute1 : PlmnId
attribute2 : Integer [1..*]
attribute3 : String
attribute4 : Xyz | + +Figure C.17: Usage example of <>. A ZClass with attributes attribute1 : PlmnId, attribute2 : Integer [1..\*], attribute3 : String, and attribute4 : Xyz. + +**Figure C.17 – Usage example of <>** + +##### C.3.5.3 Name style + +For <> name, use the same style as <> (see clause C.3.3). + +For <> attribute, use the same style as Attribute (see clause C.2.2). + +#### C.3.6 <> + +##### C.3.6.1 Description + +An enumeration is a data type. It contains sets of named literals that represent the values of the enumeration. An enumeration has a name. + +See 10.3.2 Enumeration of [OMG UML1]. + +##### C.3.6.2 Example + +The example in Figure C.18 shows an enumeration model element whose name is `Account` and it has four enumeration literals. The upper compartment contains the keyword <> and the name of the enumeration. The lower compartment contains a list of enumeration literals. + +Note that the symbol to the right of <> `Account` in the figure below is a feature specific to a particular modelling tool. It is recommended that modelling tool features should be used when appropriate. + +![UML diagram of an enumeration class named Account. It contains four literals: CASH_ACCOUNT, STUDENT_ACCOUNT, SENIOR_ACCOUNT, and PREMIUM_ACCOUNT.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +``` + +classDiagram + class Account { + <> + CASH_ACCOUNT + STUDENT_ACCOUNT + SENIOR_ACCOUNT + PREMIUM_ACCOUNT + } + +``` + +UML diagram of an enumeration class named Account. It contains four literals: CASH\_ACCOUNT, STUDENT\_ACCOUNT, SENIOR\_ACCOUNT, and PREMIUM\_ACCOUNT. + +**Figure C.18 – <> notation** + +##### **C.3.6.3 Name style** + +For <> name, use the same style as <> (see clause C.3.3). + +For <> attribute (the enumeration literal), use the following rules: + +- Enumeration literal is composed of one or more words of upper case characters. Words are separated by the underscore character. + +#### **C.3.7 <>** + +##### **C.3.7.1 Description** + +The «choice» stereotype represents one of a set of classes (when used as an information model element) or one of a set of data types (when used as an operations model element). + +This stereotype property, e.g., one out of a set of possible alternatives, is identical to the {xor} constraint (see clause C.2.11). + +##### **C.3.7.2 Example** + +Sometimes the specific kind of class cannot be determined at model specification time. In order to support such scenario, the specification is done by listing all possible classes. + +Figure C.19 lists 3 possible classes. It also shows a «choice, InformationObjectClass» named SubstituteObjectClass. This scenario indicates that only one of the three «InformationObjectClass» named Alternative1ObjectClass, Alternative2ObjectClass, Alternative3ObjectClass shall be realised. + +The «choice» stereotype represents one of a set of classes when used as an information model element. + +![UML diagram showing a choice class SubstituteObjectClass with three possible alternatives: Alternative1ObjectClass, Alternative2ObjectClass, and Alternative3ObjectClass. The alternatives are connected to the choice class via association lines with multiplicity 1 at both ends.](fc0cdcafc5389b99674ba116c9787ffd_img.jpg) + +``` + +classDiagram + class SubstituteObjectClass { + <> + } + class Alternative1ObjectClass { + <> + } + class Alternative2ObjectClass { + <> + } + class Alternative3ObjectClass { + <> + } + SubstituteObjectClass "1" -- "1" Alternative1ObjectClass : + alternative1 + SubstituteObjectClass "1" -- "1" Alternative2ObjectClass : + alternative2 + SubstituteObjectClass "1" -- "1" Alternative3ObjectClass : + alternative3 + +``` + +UML diagram showing a choice class SubstituteObjectClass with three possible alternatives: Alternative1ObjectClass, Alternative2ObjectClass, and Alternative3ObjectClass. The alternatives are connected to the choice class via association lines with multiplicity 1 at both ends. + +**Figure C.19 – Information model element example using <> notation** + +Sometimes the specific kind of data type cannot be determined at model specification time. In order to support such scenario, the specification is done by listing all possible data types. + +Figure C.20 lists 2 possible data types. It also shows a «choice» named ProbableCause. This scenario indicates that only one of the two «dataType» named IntegerProbableCause, StringProbableCause shall be realised. + +The «choice» stereotype represents one of a set of data types when used as an operations model element. + +![UML diagram showing a choice stereotype ProbableCause associated with two possible data types: IntegerProbableCause and StringProbableCause.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +classDiagram + class ProbableCause { + <> + } + class IntegerProbableCause { + <> + probableCause : Integer + } + class StringProbableCause { + <> + probableCause : String + } + ProbableCause "1" *--> "1" IntegerProbableCause : + probableCause + ProbableCause "1" *--> "1" StringProbableCause : + probableCause + +``` + +The diagram illustrates a «choice» stereotype named **ProbableCause**. It has two associations, each with a multiplicity of 1 at the **ProbableCause** end and 1 at the target end. The first association points to a «dataType» named **IntegerProbableCause**, which contains an attribute `probableCause : Integer`. The second association points to a «dataType» named **StringProbableCause**, which contains an attribute `probableCause : String`. Both associations are labeled with `+ probableCause` near the target class. + +UML diagram showing a choice stereotype ProbableCause associated with two possible data types: IntegerProbableCause and StringProbableCause. + +Figure C.20 – Operations model element example using «choice» notation + +Sometimes models distinguish between sink/source/bidirectional termination points. A generic class which comprises these three specific classes can be modelled using the «choice» stereotype (see Figure C.21). + +![UML diagram showing a choice stereotype GenericTerminationPoint associated with three specific information object classes: TerminationPointSource, TerminationPointSink, and TerminationPointBidirectional.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +``` + +classDiagram + class GenericTerminationPoint { + <> + } + class TerminationPointSource { + <> + } + class TerminationPointSink { + <> + } + class TerminationPointBidirectional { + <> + } + GenericTerminationPoint "1" *--> "0..1" TerminationPointSource : + terminationPointSource + GenericTerminationPoint "1" *--> "0..1" TerminationPointSink : + terminationPointSink + GenericTerminationPoint "1" *--> "0..1" TerminationPointBidirectional : + terminationPointBidirectional + TerminationPointSource <|-- TerminationPointBidirectional + TerminationPointSink <|-- TerminationPointBidirectional + +``` + +The diagram shows a «choice, InformationObjectClass» stereotype named **GenericTerminationPoint**. It has three associations, each with a multiplicity of 1 at the **GenericTerminationPoint** end and 0..1 at the target end. The first association points to an «InformationObjectClass» named **TerminationPointSource** and is labeled `+ terminationPointSource`. The second association points to an «InformationObjectClass» named **TerminationPointSink** and is labeled `+ terminationPointSink`. The third association points to an «InformationObjectClass» named **TerminationPointBidirectional** and is labeled `+ terminationPointBidirectional`. Below the associations, **TerminationPointBidirectional** is shown with inheritance arrows pointing to it from both **TerminationPointSource** and **TerminationPointSink**. + +UML diagram showing a choice stereotype GenericTerminationPoint associated with three specific information object classes: TerminationPointSource, TerminationPointSink, and TerminationPointBidirectional. + +Figure C.21 – Sink/source/bidirectional termination points example using «choice» notation + +##### C.3.7.3 Name style + +For «choice» name, use the same style as «InformationObjectClass» (see clause C.3.3). + +### C.4 Others + +#### C.4.1 Association class + +##### C.4.1.1 Description + +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. + +See 7.3.4 AssociationClass of [OMG UML2]. + +Association classes are appropriate for use when an «InformationObjectClass» needs to maintain associations to several other instances of «InformationObjectClass» 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 identifier. A NameBinding «InformationObjectClass» can be modelled as an Association Class that provides the binding semantics to the relationship between an identifier and some other «InformationObjectClass» such as Object in the figure. This is depicted in Figure C.22. + +##### C.4.1.2 Example + +![UML diagram showing an association class. A class named 'Name' (stereotyped as «InformationObjectClass») is associated with a class named 'Object' (stereotyped as «InformationObjectClass»). The association is named 'names' and has a multiplicity of 1 at the 'Name' end and * at the 'Object' end. An association class named 'NameBinding' (stereotyped as «InformationObjectClass») is attached to the association line via a dashed line. A class named 'Identifier' (stereotyped as «InformationObjectClass») is also associated with 'Object' with a multiplicity of 1 at both ends.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +``` +classDiagram + class Name["«InformationObjectClass»\nName"] + class NameBinding["«InformationObjectClass»\nNameBinding"] + class Identifier["«InformationObjectClass»\nIdentifier"] + class Object["«InformationObjectClass»\nObject"] + + Name "1" -- "*" Object : «names» + (Name, Object) .. NameBinding + Identifier "1" -- "1" Object +``` + +UML diagram showing an association class. A class named 'Name' (stereotyped as «InformationObjectClass») is associated with a class named 'Object' (stereotyped as «InformationObjectClass»). The association is named 'names' and has a multiplicity of 1 at the 'Name' end and \* at the 'Object' end. An association class named 'NameBinding' (stereotyped as «InformationObjectClass») is attached to the association line via a dashed line. A class named 'Identifier' (stereotyped as «InformationObjectClass») is also associated with 'Object' with a multiplicity of 1 at both ends. + +Figure C.22 – Association class notation + +##### C.4.1.3 Name style + +The name shall use the same style as in «InformationObjectClass» (see clause C.3.3). + +#### C.4.2 Abstract class + +##### C.4.2.1 Description + +Abstract class specifies a special kind of «InformationObjectClass» as the general model element involved in a generalization relationship (see clause C.2.6). An abstract class cannot be instantiated. + +This modelled element has the same properties as class. See clause C.3.3. + +##### C.4.2.2 Example + +Figure C.23 shows that *Class5\_* is an abstract class. It is the base class for *SpecialisedClass5*. + +![UML diagram showing an abstract class. A class named 'Class5_' is shown as the base class for a class named 'SpecialisedClass5'. The relationship is a generalization, indicated by a solid line with an open triangle arrowhead pointing from 'SpecialisedClass5' to 'Class5_'.](f98674fcf898dbd5225f8f732a393e1c_img.jpg) + +``` +classDiagram + Class5_ <|-- SpecialisedClass5 +``` + +UML diagram showing an abstract class. A class named 'Class5\_' is shown as the base class for a class named 'SpecialisedClass5'. The relationship is a generalization, indicated by a solid line with an open triangle arrowhead pointing from 'SpecialisedClass5' to 'Class5\_'. + +Figure C.23 – Abstract class notation + +##### C.4.2.3 Name style + +For abstract class name, use the same style as <> (see clause C.3.3). The name shall be in italics. + +#### C.4.3 Predefined data types + +##### C.4.3.1 Description + +It represents the general notion of being a data type (i.e., a type whose instances are identified only by their values) whose definition is defined by this specification and not by the user (e.g., specification authors). + +This repertoire uses two kinds of data types: predefined data types and user-defined data types. The latter are defined in clauses C.3.5 and C.3.6. + +Table C.6 lists the UML data types selected for use as predefined data type. + +**Table C.6 – UML defined data types** + +| Name | Description and reference | +|---------|--------------------------------------------| +| Boolean | See Boolean type of [ITU-T X.680]. | +| Integer | See Integer type of [ITU-T X.680]. | +| String | See PrintableString type of [ITU-T X.680]. | + +Table C.7 lists data types that are defined by this repertoire. + +**Table C.7 – Non-UML defined data types** + +| Name | Description and reference | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AttributeValuePair | This data type defines an attribute name and the attribute's value. | +| BitString | This data type is defined by Bit string of clause 3 and clause G.2.5 of [ITU-T X.680]. | +| DateTime | This data type is defined by GeneralizedTime of [ITU-T X.680]. | +| DN | This data type defines the distinguished name (DN) (see Distinguished Name of [ITU-T X.501]) of an object. It contains a sequence of one or more name components. Each initial sub-sequence (Note 1) of the object name is also the name of an object. The sequence of objects so identified, starting with the one identified by only the first name component and ending with the object being named, is such that each is the immediate superior (Note 2) of that which follows it in the sequence.
NOTE 1 – Suppose an object's DN is composed of a sequence of 4 name components, i.e., 1st, 2nd, 3rd and 4th components. The "initial sub-sequence" is composed of the 1st, 2nd and 3rd components.
NOTE 2 – Suppose object A is name-contained (see clause C.3.4) by object B, object B is said to be the immediate superior of object A. | +| External | This data type is defined by another organization. | +| OperationStatusAtomic | This enumeration defines the status values of an atomic operation.
  • • SUCCESSFUL: The operation has been successfully completed as a whole;
  • • NOT_SUCCESSFUL: The operation has not been successfully completed as a whole; i.e., the states of the involved object instances are the same as before the operation (roll back is necessary).
| + +**Table C.7 – Non-UML defined data types** + +| Name | Description and reference | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OperationStatusBestEffort | This enumeration defines the status values of a best effort operation.
  • • SUCCESSFUL: The operation has been completed successfully as a whole;
  • • PARTIALLY_SUCCESSFUL: The operation has been completed partially successfully. Further definition what this means for a specific operation is to be specified by the interface specification author;
  • • NOT_SUCCESSFUL The operation has not been completed at all, i.e., the state of the involved object instances is unchanged.
| +| Real | This data type is defined by Real type of [ITU-T X.680]. | + +##### **C.4.3.2 Example** + +Figure C.24 shows an example of predefined data types usage. + +![UML class diagram for Class1 with attributes: identifier : DN, sourceTime : DateTime, measurementValue : Real, suspectFlag : Boolean.](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +``` + +classDiagram + class Class1 { + identifier : DN + sourceTime : DateTime + measurementValue : Real + suspectFlag : Boolean + } + +``` + +UML class diagram for Class1 with attributes: identifier : DN, sourceTime : DateTime, measurementValue : Real, suspectFlag : Boolean. + +**Figure C.24 – Predefined data types usage** + +NOTE – Use of this is optional. Uses of other means, to specify Predefined data types, are allowed. + +##### **C.4.3.3 Name style** + +It shall use the UCC style. + +### **C.5 Qualifiers** + +This clause defines the qualifiers applicable for model elements specified in this document, e.g., the IOC (see clause C.3.3), the Attribute (see clause C.2.2). The qualifications are M, O, CM, CO, C and 'SS'. Their meanings are specified in this section. This type of qualifier is called Support Qualifier (see supportQualifier of IOC in Table C.3 and supportQualifier of attribute in Table C.1). + +This clause also defines the qualifiers applicable to various properties of a model element, e.g., see the IOC properties excepting 'supportQualifier' in Table C.3 and attributes properties excepting supportQualifier in Table C.1. The qualifications are M, O, CM, CO, C and '-'. Their meanings are specified in this section. This type of qualifier is simply called Qualifier. + +Definition of M (Mandatory) qualification: + +- The capability (e.g., the Attribute named `abc` of an IOC named `Xyz`; the write property of Attribute named `abc` of an IOC named `Xyz`; the IOC named `Xyz`) shall be supported. + +Definition of O (Optional) qualification: + +- The capability may or may not be supported. + +Definition of CM (Conditional-Mandatory) qualification: + +- The capability shall be supported under certain conditions, specifically: + - When qualified as CM, the capability shall have a corresponding constraint defined in the specification. If the specified constraint is met then the capability shall be supported. + +Definition of CO (Conditional-Optional) qualification: + +- The capability may be supported under certain conditions, specifically: + - When qualified as CO, the capability shall have a corresponding constraint defined in the specification. If the specified constraint is met then the capability may be supported. + +Definition of C (Conditional) qualification: + +- Used for items that have multiple constraints. Each constraint is worded as a condition for one kind of support such as mandatory support, optional support or "no support". All constraints must be related to the same kind of support. Specifically: + - Each item with C qualification shall have the corresponding multiple constraints defined in the specification. If all specified constraints are met and are related to mandatory, then the item shall be supported. If all the specified constraints are met and are related to optional, then the item may be supported. If all the specified constraints are met and are related to "no support", then the item shall not be supported. +- NOTE – This qualifier should only be used when absolutely necessary, as it is more complex to implement. + +Definition of SS (SS Conditional) qualification: + +- The capability shall be supported by at least one but not all solutions. + +Definition of '-' (no support) qualification: + +- The capability shall not be supported. + +### C.6 UML diagram requirements + +Classes and their relationships shall be presented in classes diagrams. + +It is recommended to create: + +- An overview classes diagram containing all classes related to a specific management area (Class Diagram). + - The class name compartment should contain the location of the class definition (e.g., "Qualified Name") + - The class attributes should show the "Signature" (see clause 7.3.45 of [OMG UML2] for the signature definition); +- A separate inheritance classes diagram in case the overview diagram would be overloaded when showing the inheritance structure (Inheritance Class Diagram); +- A classes diagram containing the user defined data types (Type Definitions Diagram); +- Additional classes diagrams to show specific parts of the specification in detail; +- State diagrams for complex state attributes. + +# **Annex D** + +## **Design** + +(This annex forms an integral part of this Recommendation.) + +This annex provides guidelines for the specification of protocol-specific designs. It is for further study. + +# Annex E + +## Information type definitions – type repertoire + +(This annex forms an integral part of this Recommendation.) + +This annex defines a repertoire of types that shall be used to specify type information in the conceptual model (analysis model/information service). + +The repertoire is defined as a subset of types defined by ASN.1 [ITU-T X.680] combined with types derived from the types defined by ASN.1 (clause E.4). + +The keywords to be used for each type are summarized in Table E.1. + +## E.1 Basic types + +Basic types are types that can be used directly to define attributes and parameters. Basic types can also be used to construct complex types. Basic types include the following ASN.1 types: + +- E.1.1 **integer type** clause 19 of [ITU-T X.680] +- E.1.2 **real type** clause 21 of [ITU-T X.680] +- E.1.3 **boolean type** clause 18 of [ITU-T X.680] +- E.1.4 **bitstring type** clause 22 of [ITU-T X.680] +- E.1.5 **null type** clause 24 of [ITU-T X.680] +- E.1.6 **generalized time type** clause 38 of [ITU-T X.680] + +### E.2 Enumerated type + +Enumerated type clause 20 of [ITU-T X.680] represents enumerated values. All values that may be used by a specific attribute or parameter shall be listed in the legal value columns. Only the listed names style is applicable for the conceptual model, i.e., the identification of concrete values (numbers or strings) are left for the concrete design models. + +NOTE – If the number of these values is more than 50, it is recommended to define them in an appendix or an independent document. + +## E.3 Complex types + +Complex types can be defined using the following concepts: + +- E.3.1 **sequence types** clause 25 of [ITU-T X.680] +- E.3.2 **choice types** clause 29 of [ITU-T X.680] +- E.3.3 **set types** clause 27 of [ITU-T X.680] + +In addition, lists and sets of complex types are supported using: + +- E.3.4 **sequence-of types** clause 26 of [ITU-T X.680] +- E.3.5 **set-of types** clause 28 of [ITU-T X.680] + +### E.4 Useful types + +#### E.4.1 String type + +String represents a string of characters, the character set is not restricted, i.e.: + +String ::= UnrestrictedCharacterStringType clause 44 of [ITU-T X.680] + +#### E.4.2 Name type + +Name represents an exclusive name of an object instance in name space. It might include object containment tree hierarchy information, but it is implementation dependent and is out of the scope of this Recommendation. Formally, the name type is defined as: + +Name ::= TYPE-IDENTIFIER Annex A of [ITU-T X.681] + +### E.5 Keywords + +Table E.1 defines the list of keywords to be used in the analysis template (see Annex B) for definition of information type, e.g.: + +| Parameter Name | Support Qualifier | Information Type/Legal Values | Comment | +|----------------|-------------------|-------------------------------|----------------------------------------| +| ... | | | | +| eventIdList | M | SET OF INTEGER/- | The list of alarms to be acknowledged. | + +**Table E.1 – Keywords** + +| Type | Keyword | +|-----------------------|-----------------| +| integer type | INTEGER | +| real type | REAL | +| boolean type | BOOLEAN | +| bitstring type | BIT STRING | +| null type | NULL | +| generalized time type | GeneralizedTime | +| enumerated type | ENUMERATED | +| sequence type | SEQUENCE | +| choice type | CHOICE | +| set type | SET | +| sequence-of type | SEQUENCE OF | +| set-of type | SET OF | +| string type | String | +| name type | Name | + +# Annex F + +## Guidelines on IOC properties, inheritance and entity import + +(This annex forms an integral part of this Recommendation.) + +The following guidelines are based on [b-3GPP TS 32.150]. + +## F.1 IOC 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. + +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 subclause 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. + +## F.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. + +## F.3 Entity (interface, IOC and attribute) import + +Management interface specifications define entities (e.g., IOCs, interfaces and attribute). To facilitate the reuse of entity definitions among interface specifications, an import mechanism is used. When a management interface specification (the subject specification) imports an entity defined in another management interface specification, the subject specification is considered to have defined the imported entity in its specification. Furthermore, the subject 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 G + +## Attribute Properties + +(This annex forms an integral part of this Recommendation.) + +The following guidelines are based on Annex B of [b-3GPP TS 32.156]. + +| isInvariant | write | defaultValue | manager must provide a value when manager requests object creation | Meaning | +|-------------------------------------|-------------------------------------|-------------------------------------|--------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| | | | | Not valid. | +| | | | | May be set by the manager only during object creation time; if no value is provided by the manager, the default value is used. | +| | | | | Must be set by the manager during object creation time. | +| | | | | May be set by the manager only during object creation time; if no value is provided by the manager, the agent must provide a value. | +| | | | | Not valid. | +| | | | | Valid but not useful. | +| | | | | Not valid. | +| | | | | Must be set by the agent during object creation time. | +| | | | | Not valid. | +| | | | | May be set by the manager anytime; if no value is provided by the manager at object creation time, it is set to the default value. | +| | | | | Must be set by the manager at object creation time and may be changed anytime. | +| | | | | May be set by the manager at object creation time and may be changed anytime. | +| | | | | Not valid. | +| | | | | Must be set by the agent to the default value at object creation time; may be changed by the agent anytime. | +| | | | | Not valid. | +| | | | | May be set by the agent at object creation time and may be changed by the agent anytime. | + +# Annex H + +## Design patterns + +(This annex forms an integral part of this Recommendation.) + +The following guidelines are based on Annex C of [b-3GPP TS 32.156]. + +### H.1 Intervening class and association class + +#### H.1.1 Concept and definition + +Classes may be related via simple direct associations or via associations with related association classes. + +However, in situations where the relationships between a number of classes is complex and especially where the relationships between instances of those classes are themselves interrelated there may be a need to encapsulate the complexity of the relationships within a class that sits between the classes that are to be related. The term "intervening class" is used here to name the pattern that describes this approach. The name "intervening class" is used as the additional class "intervenes" in the relationships between other classes. + +The "intervening class" differs from the association class as the intervening class does break the association between the classes whereas the association class does not but instead sits to one side. This can be seen in the Figure H.1. A direct association between class A and C appears the same at A and C regardless of the presence or absence of an association class where as in the case of the "intervening class" there are associations between A and the "intervening class" B and C and the "intervening class" B. + +![Figure H.1 – Various association forms. The diagram shows four UML class diagrams illustrating different association patterns: 1. Basic association: ClassA (0..1) is associated with ClassC (0..1). 2. Association Class: ClassA (*) is associated with ClassC (*), with ClassB acting as the association class. 3. Intervening class: ClassA (*) is associated with ClassB (0..1), which is associated with ClassC (*). 4. Another intervening class pattern: ClassA (0..1) is associated with ClassB (*), which is associated with ClassC (0..1). Each diagram includes a descriptive note on the right.](921458d4fc1b778c2450592ac9745b48_img.jpg) + +**Basic association** +Note class A points a C and C at A + +**Association Class** +Association where there is a need to represent: the associations own features (i.e. that do not belong to any of the connected classes): +• Some behavior and state +• Some additional data related to the association +Note that class A points a C and C at A + +**"Intervening" class** +Where there is a complex assembly of state/data bound to a number of associations. +Note that Class A and C point to B and potentially B points to C and A. + +Figure H.1 – Various association forms. The diagram shows four UML class diagrams illustrating different association patterns: 1. Basic association: ClassA (0..1) is associated with ClassC (0..1). 2. Association Class: ClassA (\*) is associated with ClassC (\*), with ClassB acting as the association class. 3. Intervening class: ClassA (\*) is associated with ClassB (0..1), which is associated with ClassC (\*). 4. Another intervening class pattern: ClassA (0..1) is associated with ClassB (\*), which is associated with ClassC (0..1). Each diagram includes a descriptive note on the right. + +Figure H.1 – Various association forms + +The "intervening class" is essentially no different to any other class in that it may encapsulate attributes, complex behaviour, etc. + +Figure H.2 shows an instance view of both an association class form and an "intervening class" form for a complex interrelationship. + +![UML class diagram illustrating two forms of complex interrelationships: Association Class and Intervening Class.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) + +The diagram illustrates two forms of complex interrelationships between Class A, Class B, and Class C. + +**Association Class Form:** + +- Class A Instance 1 (ClassA)** (classC = Entries[2]) is associated with **Class B Instance 1 (ClassB)** (classA = Entries[1], classC = Entries[1]) via an association labeled "classA". +- Class A Instance 2 (ClassA)** (classC = Entries[2]) is associated with **Class C Instance 1 (ClassC)** (classA = Entries[2]) via an association labeled "classC". +- Class B Instance 3 (ClassB)** (classC = Entries[1], classA = Entries[1]) is associated with **Class C Instance 2 (ClassC)** (classA = Entries[2]) via an association labeled "classC". +- Class B Instance 2 (ClassB)** (classA = Entries[1], classC = Entries[1]) is associated with **Class C Instance 2 (ClassC)** (classA = Entries[2]) via an association labeled "classC". +- Class B Instance 4 (ClassB)** (classC = Entries[1], classA = Entries[1]) is associated with **Class C Instance 2 (ClassC)** (classA = Entries[2]) via an association labeled "classC". + +**Association Class** +Many instances of association class, one per association instance. + +**Intervening Class Form:** + +- Class A Instance 1 (ClassA)** (classB = ClassBInstance) is associated with **Class B Instance (ClassB)** (classA = Entries[2], classC = Entries[2]) via an association labeled "classA". +- Class A Instance 2 (ClassA)** (classB = ClassBInstance) is associated with **Class B Instance (ClassB)** (classA = Entries[2], classC = Entries[2]) via an association labeled "classA". +- Class C Instance 1 (ClassC)** (classB = ClassBInstance) is associated with **Class B Instance (ClassB)** (classA = Entries[2], classC = Entries[2]) via an association labeled "classC". +- Class C Instance 2 (ClassC)** (classB = ClassBInstance) is associated with **Class B Instance (ClassB)** (classA = Entries[2], classC = Entries[2]) via an association labeled "classC". + +**"Intervening" class** +One instance of intervening class that captures complex association and intertwining between Classes. +Also captures behaviour interaction such as protection switching and state (e.g where class A and C are TPs and class B is an SNC). + +UML class diagram illustrating two forms of complex interrelationships: Association Class and Intervening Class. + +Figure H.2 – Instance view of "intervening class" + +The case depicted above does not show interrelationships between the relationships. A practical case from modelling of the relationships between termination points in a fixed network does show this relationship interrelationship challenge. In this case the complexity of relationship is between instances of the same class, the termination point (TP). The complexity is encapsulated in a SubNetworkConnection (SNC) class. + +For an example of an SNC intervening in TP-TP relationship see Figure H.3. + +![UML Class diagram showing a relationship between TP and SNC classes. TP has a multiplicity of '*' and a role name '- tP'. SNC has a multiplicity of '0..2' and a role name '- sNC'. A line connects them.](1b23b78336d8bd286c653cbdb38428dd_img.jpg) + +UML Class diagram showing a relationship between TP and SNC classes. TP has a multiplicity of '\*' and a role name '- tP'. SNC has a multiplicity of '0..2' and a role name '- sNC'. A line connects them. + +**Simplified SNC and TP case** + An SNC can not exist without at least 2 TPs being related. + Some simplifications: In this case the TP and SNC model is assumed to be bidirectional only. The TPs have roles with respect to the SNC but these are ignored here. There are many other attributes and properties related to protection that are ignored here. + +![UML Class diagram showing an intervening class (SNC) in a TP-TP relationship. Four TP instances (TPInstance1, TPInstance2, TPInstance3, TPInstance4) are connected to a central SNC instance (SNCInstance : SNC). The SNC instance has an attribute 'tp = Entries[4]'. The connections are labeled with '- tP'.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) + +UML Class diagram showing an intervening class (SNC) in a TP-TP relationship. Four TP instances (TPInstance1, TPInstance2, TPInstance3, TPInstance4) are connected to a central SNC instance (SNCInstance : SNC). The SNC instance has an attribute 'tp = Entries[4]'. The connections are labeled with '- tP'. + +**"Intervening class" instance view** + One instance of intervening class that captures complex association and intertwining between Classes. Also captures behaviour interaction such as protection switching and state. + +**Figure H.3 – SNC intervening in TP-TP relationship** + +The SNC also encapsulates the complex behaviour of switching and path selection as depicted in Figure H.4. + +![UML Class diagram showing complex relationship interrelationships. It includes TP instances (TPInstance1, TPInstance2, TPInstance3, TPInstance4) with attributes like 'tp = Entries[2]'. These are connected to SncAssociation instances (SncAssociationInstance1, SncAssociationInstance2, SncAssociationInstance3, SncAssociationInstance4) which in turn connect to a ProtectionInstance. Associations are labeled with '- tp' and '- protection'. Text annotations on the right mention 'Association Class' and 'protection switching rule and state'.](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +UML Class diagram showing complex relationship interrelationships. It includes TP instances (TPInstance1, TPInstance2, TPInstance3, TPInstance4) with attributes like 'tp = Entries[2]'. These are connected to SncAssociation instances (SncAssociationInstance1, SncAssociationInstance2, SncAssociationInstance3, SncAssociationInstance4) which in turn connect to a ProtectionInstance. Associations are labeled with '- tp' and '- protection'. Text annotations on the right mention 'Association Class' and 'protection switching rule and state'. + +**Association Class** + With protection switching rule and state. + There is complex creation transaction interrelationship + +**Figure H.4 – Complex relationship interrelationships** + +#### **H.1.2 Usage in the non-transport domain** + +The choice of association class pattern or intervening class pattern is on a case-by-case basis. The transport domain boundary is highlighted in the Figure H.5. + +![Diagram illustrating the boundary between transport and non-transport domains in a network architecture. The diagram shows a 'Management environment' box at the top left. Below it, a 'Function e.g., eNodeB function' is shown within an 'NE with wireless access' box. A dashed red line separates the 'non-transport domain' (above) from the 'transport domain' (below). In the non-transport domain, a blue 'Link entity (connectivity e.g., X2)' connects the 'Function e.g., eNodeB function' to a 'Network element' (orange box) on the right. In the transport domain, an orange 'Topological link' connects the 'Function e.g., eNodeB function' to a 'Wire-line NE' box. The 'Wire-line NE' box contains a 'Connection termination point' (green box) and a 'Physical termination point' (purple box). A dashed green line connects the 'Function e.g., eNodeB function' to the 'Connection termination point'. A dashed purple line connects the 'Function e.g., eNodeB function' to the 'Physical termination point'. A solid blue line connects the 'Function e.g., eNodeB function' to the 'Wire-line NE'. The 'Wire-line NE' is connected to another 'NE with wireless access' box on the right. A legend on the right side defines the symbols: orange box for 'Network element', blue box for 'Link entity (connectivity e.g., X2)', orange line for 'Topological link', dashed green line for 'Based on connection termination point concept', dashed purple line for 'Based on physical termination point concept', blue box for '3GPP managed function', green box for 'Connection termination point', purple box for 'Physical termination point', dashed blue line for 'Association/relationship', and solid blue line for 'Optical fibre'. The text 'M.3020(17)_FH.5' is at the bottom right.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +Diagram illustrating the boundary between transport and non-transport domains in a network architecture. The diagram shows a 'Management environment' box at the top left. Below it, a 'Function e.g., eNodeB function' is shown within an 'NE with wireless access' box. A dashed red line separates the 'non-transport domain' (above) from the 'transport domain' (below). In the non-transport domain, a blue 'Link entity (connectivity e.g., X2)' connects the 'Function e.g., eNodeB function' to a 'Network element' (orange box) on the right. In the transport domain, an orange 'Topological link' connects the 'Function e.g., eNodeB function' to a 'Wire-line NE' box. The 'Wire-line NE' box contains a 'Connection termination point' (green box) and a 'Physical termination point' (purple box). A dashed green line connects the 'Function e.g., eNodeB function' to the 'Connection termination point'. A dashed purple line connects the 'Function e.g., eNodeB function' to the 'Physical termination point'. A solid blue line connects the 'Function e.g., eNodeB function' to the 'Wire-line NE'. The 'Wire-line NE' is connected to another 'NE with wireless access' box on the right. A legend on the right side defines the symbols: orange box for 'Network element', blue box for 'Link entity (connectivity e.g., X2)', orange line for 'Topological link', dashed green line for 'Based on connection termination point concept', dashed purple line for 'Based on physical termination point concept', blue box for '3GPP managed function', green box for 'Connection termination point', purple box for 'Physical termination point', dashed blue line for 'Association/relationship', and solid blue line for 'Optical fibre'. The text 'M.3020(17)\_FH.5' is at the bottom right. + +**Figure H.5 – Highlighting the boundary between transport and non-transport domains** + +### H.1.3 Usage in the transport domain + +The following guidelines must be applied to the models of the "transport domain". + +When considering interrelationships between classes the following guidelines should be applied: + +- If considering all current and recognised potential future cases it is expected that the relationship between two specific classes will be 0..1:0..1 then a simple association should be used + - This may benefit from an association class to convey rules and parameters about the association behaviour in complex cases. +- If there is recognised potential for cases currently or in future where there is a 0..\*:0..\* between two specific classes then intervening classes should be used to encapsulate the groupings, etc. so as to convert it to 0..1:n..\* + - Note that the 0..1:n..\* association may benefit from an association class to convey rules and parameters about the association behaviour in complex cases but in the instance form this can probably be ignored or folded into the intervening class +- In general it seems appropriate to use an association class when the properties on the relationship instance cannot be obviously or reasonably folded into one of the classes at either end of the association and when there is no interdependency between association instances between a set of instances of the classes. + +An example of usage of intervening class is the case of the TP-TP (TerminationPoint) relationship (0..\*:0..\*) where the SNC (SubNetworkConnection) is added as the intervening class between + +multiple TPs, i.e., TP-SNC. Note that TP-SNC actually becomes 0..2:n..\* due to directionality encapsulation. + +Considering the case of the adjacency relationship between PTPs it is known that although the current common cases are 1:1 there are some current and many potential future case of 0..\*:0..\* and hence a model that has an intervening class, i.e., the TopologicalLink, should be used. + +For a degenerate instance cases of 0..\*:0..\* that happens to be 0..1:0..1 the intervening class pattern should still be used: + +- Using the 0..1:0..1 direct association in this degenerate case brings unnecessary variety to the model and hence to the behaviour of the application (the 0..1:n..\* model covers the 0..1:0..1 case with one single code form clearly) +- An instance of the 0..1:0..1 model may need to be migrated to 0..1:n..\* as a result of some change in the network forcing an unnecessary administrative action to transition the model form where as in the 0..1:n..\* form requires no essential change. + +## H.2 Use of "ExternalXyz" class + +For further study. + +# Appendix I + +## Comparison with Recommendation ITU-T Z.601 + +(This appendix does not form an integral part of this Recommendation.) + +This appendix provides information on the relationship between this Recommendation and [b-ITU-T Z.601] that is used for the development of ITU-T M.1400.x series of Recommendations (see Bibliography). + +While this Recommendation provides a methodology for specifying management interfaces between two physical systems, [b-ITU-T Z.601] provides a framework for the development of one system. This data architecture identifies candidate interfaces within one system as well as the interfaces on the boundary of this system. These interfaces at the boundary will be between systems. + +The methodology specified by this Recommendation is primarily aimed at the development of a set of management interface Recommendations rather than of individual systems. The data architecture prescribes no requirements capture similar to the requirements phase, as it prescribes the specification of individual systems only, not their purpose relative to an organization. + +[b-ITU-T Z.601] focuses on specification of the external terminology and grammar as perceived by the end users. This Recommendation focuses on specification of management interfaces, which may not be perceived by the end users. + +In this Recommendation, the requirements for the problem being solved fall into two classes. The first class of requirements is referred to as business requirements; the second class is referred to as specification requirements. The specification requirements may include requirements to support end-user interaction at their human-computer interfaces. Some of these requirements may specify syntactical requirements to be supported over any management interface. Syntactical requirements correspond to external terminology schemata of the data architecture as described in [b-ITU-T Z.601]. + +The output of the analysis phase will be an information model. This corresponds to a concept schema of the data architecture as described in [b-ITU-T Z.601]. If the information models from the analysis phase do not convey all the necessary information from the syntactical requirements, the implementation design may need to include a mapping from the syntactical requirements. + +The documentation from the implementation design phase will consist of two parts: + +- 1) A technology-dependent data specification common for several interfaces, e.g., using GDMO or CORBA IDL, corresponding to an internal terminology schema according to the data architecture in [b-ITU-T Z.601]. +- 2) A technology-dependent specification of each interface, e.g., using CMIP or CORBA IDL, corresponding to a distribution schema according to the data architecture in [b-ITU-T Z.601]. + +# Appendix II + +## Additional UML usage examples + +(This appendix does not form an integral part of this Recommendation.) + +This appendix contains additional examples on the use of the UML described in Annex C. + +## II.1 Proxy class + +#### II.1.1 First example + +This shows a <> named YyyFunction. It represents all IOCs listed in the Note under the UML diagram. All the listed IOCs, in the context of this example, inherit from ManagedFunction IOC (see Figure II.1). + +The use of <> eliminates the need to draw multiple UML <> boxes, i.e., those whose names are listed in the Note, in the UML diagram. + +![UML diagram showing a ProxyClass (YyyFunction) inheriting from an InformationObjectClass (ManagedFunction).](ff7977984f2552f326b2089d7595fff3_img.jpg) + +The diagram shows two classes. The top class is a yellow box labeled <> ManagedFunction (from TS 32.622). The bottom class is a yellow box labeled <> YyyFunction. A red inheritance arrow points from the bottom class to the top class. + +UML diagram showing a ProxyClass (YyyFunction) inheriting from an InformationObjectClass (ManagedFunction). + +NOTE – The YyyFunction <> represents AsFunction, AucFunction, BgFunction, etc. + +Figure II.1 – <> Notation example II.1 + +#### II.1.2 Second sample + +Figure II.2 shows a <> 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 <> and by the ExternalYyyFunction <> are listed under the subclause 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 <> and by ExternalLink\_a\_z <> are listed under the subclause 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 [b-3GPP TS 23.002]. + +The linked InternalYyyFunction <> represents SlsFunction, CscfFunction, HlrFunction ... + +The linked ExternalYyyFunction <> represents ... + +The Link\_a\_z <> represents Link\_As\_Scscf, Link\_Bgcf\_Scscf ... + +The ExternalLink\_a\_z <> represents ... + +" + +![UML class diagram showing relationships between proxy classes.](4bfb457b83429c217736e6d51b2f3945_img.jpg) + +``` +classDiagram + class Link_a_z["<> Link_a_z"] + class ExternalLink_a_z["<> ExternalLink_a_z"] + class InternalYyyFunction["<> InternalYyyFunction"] + class YyyFunction["<> YyyFunction"] + class ExternalYyyFunction["<> ExternalYyyFunction"] + + Link_a_z --- YyyFunction + ExternalLink_a_z --- YyyFunction + InternalYyyFunction --- YyyFunction + YyyFunction --- ExternalYyyFunction +``` + +The diagram illustrates a network of proxy classes. At the center is a class box labeled '<> YyyFunction'. To its left is '<> InternalYyyFunction', connected by a horizontal line. To its right is '<> ExternalYyyFunction', also connected by a horizontal line. Above the central class is '<> Link\_a\_z', connected by a vertical line that meets a horizontal line extending from the left class. Similarly, above the central class is '<> ExternalLink\_a\_z', connected by a vertical line that meets a horizontal line extending from the right class. + +UML class diagram showing relationships between proxy classes. + +NOTE – The 'Yyy' of YyyFunction <> represents AsFunction, AucFunction, etc. + +**Figure II.2 – <> Notation sample II.2** + +# Appendix III + +## Guidelines on requirements numbering + +(This appendix does not form an integral part of this Recommendation.) + +The format for requirements numbering is the following: + +REQ-Label-Category-Number + +where "Label" is an abbreviation for the Recommendation (or part thereof). The set of labels is not finite and not subject for standardization. The set of categories is defined in this Recommendation. + +Some issues: + +- How to structure the label in a large requirements specification? +- How to handle deletion and addition of requirements? + +The following guidelines are found to be useful: + +- Requirements should never be renumbered. The only exception to this case is the first publication of a specification, but even in this case it may be better to avoid renumbering as the specification may have been used also in its draft form. +- Given that requirements are not to be renumbered, it cannot be expected that the requirements are numbered sequentially throughout the specification. +- The label can be used to divide the numbering into logical partitions. As an example, the style of "A\_B" is recommended to identify "B" as a logical partition of "A". However, other styles can be used as long as the structure with "-" separating the fields of the requirements number is maintained. +- Use of postfix or prefix notations, i.e., adding something in front of "Number" or following "Number", are not recommended since the "Number" part is not intended to convey semantic information. +- As an alternative to the "A\_B" style, the authors of a specification may choose to assign a number range to a group of requirements. This approach should be allowed. + +# Appendix IV + +## Stereotypes for naming purposes + +(This appendix does not form an integral part of this Recommendation.) + +Figure IV.1 illustrates the various stereotypes for naming purposes. + +- a) The `<>` with solid-diamond (see clause C.3.3) identifies: + - The naming class (close to the solid diamond) and a named class; + - The naming scheme is DN; + - The container (close to the solid diamond) and the content. +- b) The `<>` with other types of associations (and excluding those labelled "Not Allowed") identifies: + - The naming class (close to the hollow diamond or the source with regard to arrow direction) and a named class (the target); + - The naming scheme is DN. +- c) The `<>` with dependency (dotted arrowed line) identifies: + - The naming class (target with regard to arrow direction) and a named class (the source); + - The naming scheme is DN. + +![Figure IV.1 – Various forms of naming stereotypes. The diagram shows 18 classes (Class1 to Class18) grouped into four colored boxes with annotations. A legend at the bottom identifies 'naming classes' (green) and 'named classes' (blue).](a634891d16b60b21df90a35c2af72c67_img.jpg) + +The diagram illustrates various forms of naming stereotypes using UML class diagrams. It is divided into four colored boxes, each containing a different association type between a 'naming class' (green) and a 'named class' (blue). Annotations on the right indicate the status of these stereotypes. + +- Top Box (Blue):** Contains Class1, Class2, Class3, Class4, Class5, and Class6. Class1 has a `<>` dependency on Class2. Class3 has a `<>` association with Class4 (multiplicity 0..1). Class5 has a `<>` association with Class6 (multiplicity \*). A note indicates this group is "under investigation in RMA Phase 2". +- Second Box (Green):** Contains Class7 and Class8. Class7 has a `<>` association with Class8 (multiplicity \*). A note indicates this is "allowed in RMA Phase1". +- Third Box (Red):** Contains Class9, Class10, Class11, Class12, Class17, and Class18. Class9 has a `<>` association with Class10 (multiplicity \*). Class11 has a `<>` association with Class12 (multiplicity 1). Class17 has a `<>` association with Class18 (multiplicity 0..1). A note indicates this group is "not allowed". +- Bottom Box (Blue):** Contains Class13, Class14, Class15, and Class16. Class13 has a `<>` dependency on Class14. Class15 has a `<>` dependency on Class16. A note indicates this group is "under investigation in RMA Phase 2". + +Legend: **naming classes** (green), **named classes** (blue). + +Figure IV.1 – Various forms of naming stereotypes. The diagram shows 18 classes (Class1 to Class18) grouped into four colored boxes with annotations. A legend at the bottom identifies 'naming classes' (green) and 'named classes' (blue). + +Figure IV.1 – Various forms of naming stereotypes + +# Bibliography + +- [b-ITU-T M.1401] Recommendation ITU-T M.1401 (2006), *Formalization of interconnection designations among operators' telecommunication networks.* +- [b-ITU-T M.1402] Recommendation ITU-T M.1402 (2012), *Formalization of data for service management.* +- [b-ITU-T M.1403] Recommendation ITU-T M.1403 (2007), *Formalization of generic orders.* +- [b-ITU-T M.1404] Recommendation ITU-T M.1404 (2007), *Formalization of orders for interconnections among operators' networks.* +- [b-ITU-T M.1405] Recommendation ITU-T M.1405 (2007), *Formalization of orders for service management among operators.* +- [b-ITU-T Z.601] Recommendation ITU-T Z.601 (2007), *Data architecture of one software system.* +- [b-3GPP TS 23.002] 3GPP TS 23.002 V17.0.0 (2021-03), *Network architecture.* +- [b-3GPP TS 32.101] 3GPP TS 32.101 V17.0.0 (2022-03), *Telecommunication management; Principles and high level requirements.* +- [b-3GPP TS 32.150] 3GPP TS 32.150 V17.0.0 (2022-03), *Telecommunication management; Integration Reference Point (IRP) Concept and definitions.* +- [b-3GPP TS 32.156] 3GPP TS 32.156 V17.2.0 (2022-12), *Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire.* +- [b-3GPP TS 32.157] 3GPP TS 32.157 V17.0.0 (2022-03), *Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template.* +- [b-3GPP TS 32.160] 3GPP TS 32.160 V17.6.0 (2022-12), *Management and orchestration; Management service template.* +- [b-3GPP TS 32.300] 3GPP TS 32.300 V17.0.0 (2022-03), *Telecommunication management; Configuration Management (CM); Name convention for Managed Objects.* +- [b-3GPP TS 32.302] 3GPP TS 32.302 V17.0.0 (2022-03), *Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS).* + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3031-200407-I_PDF-E/raw.md b/marked/M/T-REC-M.3031-200407-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f7cb7899be421bdebcb1a9892992e5f160d857a --- /dev/null +++ b/marked/M/T-REC-M.3031-200407-I_PDF-E/raw.md @@ -0,0 +1,808 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3031** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/2004) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**Guidelines for Implementation Conformance +Statement proformas for tML schemas** + +ITU-T Recommendation M.3031 + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3031** + +# **Guidelines for Implementation Conformance Statement proformas for tML schemas** + +## **Summary** + +This Recommendation provides guidelines for defining Schema Implementation Conformance Statement (SICS) proformas for any tML-based interface information specifications. The Schema Implementation Conformance Statement (SICS) specifies how an implementation is conformant to the proformas defined for a tML schema definition. + +## **Source** + +ITU-T Recommendation M.3031 was approved on 14 July 2004 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +eXtensible Markup Language, ICS proforma, Implementation Conformance Statement, telecommunications Markup Language, tML schema. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2005 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Implementation conformance statements definitions..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 tML schema ICS proformas..... | 2 | +| 5.1 Schema overview..... | 2 | +| 5.2 Guidelines for specification of SICS proformas ..... | 3 | +| 6 Instructions for completing the SICS proforma..... | 9 | +| 6.1 The "Element Support Table" ..... | 9 | +| 6.2 The "Type Support Table"..... | 9 | +| 6.3 The "Status" column..... | 9 | +| 6.4 The "Support" column..... | 11 | +| 6.5 The "Index" column ..... | 11 | +| 6.6 The "Subindex" column..... | 11 | +| 6.7 The "Identifier" column..... | 12 | +| 6.8 The "Content model" column ..... | 12 | +| 6.9 The "Type/Content model" column..... | 12 | +| 6.10 The "Type" column ..... | 12 | +| 6.11 The "Category" column ..... | 13 | +| 6.12 The "Constraints" column ..... | 13 | +| 6.13 The "Values" column ..... | 13 | +| 6.14 The "Additional information" column..... | 13 | +| 6.15 The "Use" column ..... | 14 | +| 6.16 The "Order" column ..... | 14 | +| 6.17 The "Nillable" column..... | 14 | +| 6.18 The "Abstract" column ..... | 14 | +| 6.19 The "Selector" column..... | 14 | +| 6.20 The "Field" column ..... | 14 | +| Annex A – An example of SICS proforma specification..... | 15 | +| A.1 tML schema definition ..... | 15 | +| A.2 SICS..... | 16 | + + + +# Guidelines for Implementation Conformance Statement proformas for tML schemas + +# 1 Scope + +This Recommendation provides guidelines for defining Schema Implementation Conformance Statement (SICS) proformas for any tML-based interface information specifications. The Schema Implementation Conformance Statement (SICS) specifies how an implementation is conformant to the proformas defined for a tML schema definition. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation X.291 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Abstract test suite specification*. +- [2] ITU-T Recommendation X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*. +- [3] ITU-T Recommendation X.724 (1996) | ISO/IEC 10165-6:1997, *Information technology – Open Systems Interconnection – Structure of management information: Requirements and guidelines for implementation conformance statement proformas associated with OSI management*. +- [4] ITU-T Recommendation M.3030 (2002), *Telecommunications Markup Language (tML) framework*. +- [5] W3C, *eXtensible Markup Language (XML) 1.0 (Second Edition)*, 6 October 2000. +- [6] W3C, *XML Schema Part 0: Primer*, 2 May 2001. +- [7] W3C, *XML Schema Part 1: Structures*, 2 May 2001. +- [8] W3C, *XML Schema Part 2: Datatypes*, 2 May 2001. +- [9] W3C, *Namespaces in XML*, 14 January 1999. +- [10] W3C, *XML Path Language (XPath) Version 1.0*, 16 November 1999. + +# **3 Definitions** + +## **3.1 Implementation conformance statements definitions** + +This Recommendation makes use of the following terms defined in ITU-T Rec. X.296 [2]: + +- a) (ICS) item; +- b) (ICS) question; +- c) status (value); +- d) (support) answer. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| ICS | Implementation Conformance Statement | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| SICS | Schema Implementation Conformance Statement | +| tML | telecommunications Markup Language | +| W3C | World Wide Web Consortium | +| XML | eXtensible Markup Language | + +# **5 tML schema ICS proformas** + +tML schema is used as a template for defining tML-based interface information. The SICS proformas must express the tML schema features such as schema elements and attributes. This clause introduces the features of tML schema and specifies the SICS proformas according to these language features. + +## **5.1 Schema overview** + +tML schemas [4] express shared vocabularies and allow machines to carry out rules made by people. They provide a means for defining the structures, contents and semantics of tML documents, and define the cardinality of an element (e.g., the number of its possible occurrences) with some precision. This element may or may not have attributes, text children and sub-elements. An ordered sequence of sub-elements shall be considered if the element contains sub-elements. The definition of the target namespace [9] and several default options can also be held. tML schemas use a reference to an element or an attribute somewhat comparable to cloning an object. + +According to the schema syntax specifications [6][7][8], the containment relationship among these constructs can be illustrated as in Figure 5-1. + +![Figure 5-1/M.3031 – Containment relationship in tML schema specification. The diagram shows a hierarchy of tML schema constructs. At the top is 'tML schema', which contains 'element', 'complexType', and 'identity constraint'. 'element' contains 'group', 'complexType', and 'identity constraint'. 'complexType' contains 'group', 'attribute group', 'attribute', and 'simpleType'. 'identity constraint' contains 'key', 'keyref', and 'unique'. 'group' contains 'nestable1', 'all', and 'choice'. 'nestable1' contains 'sequence'. 'all' contains 'sequence'. 'choice' contains 'sequence'. 'attribute group' contains 'attribute'. 'attribute' contains 'simpleType'. 'simpleType' contains 'atomic types', 'nestable2', 'list', and 'union'. 'nestable2' contains 'atomic types', 'list', and 'union'. A legend defines the symbols: solid oval for actual tML schema constructs, dashed oval for conceptual tML schema constructs, solid rectangle for actual or conceptual tML schema constructs, solid arrow for contains, dashed arrow for shall be replaced by, and hollow arrow for may be replaced by.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Figure 5-1/M.3031 – Containment relationship in tML schema specification. The diagram shows a hierarchy of tML schema constructs. At the top is 'tML schema', which contains 'element', 'complexType', and 'identity constraint'. 'element' contains 'group', 'complexType', and 'identity constraint'. 'complexType' contains 'group', 'attribute group', 'attribute', and 'simpleType'. 'identity constraint' contains 'key', 'keyref', and 'unique'. 'group' contains 'nestable1', 'all', and 'choice'. 'nestable1' contains 'sequence'. 'all' contains 'sequence'. 'choice' contains 'sequence'. 'attribute group' contains 'attribute'. 'attribute' contains 'simpleType'. 'simpleType' contains 'atomic types', 'nestable2', 'list', and 'union'. 'nestable2' contains 'atomic types', 'list', and 'union'. A legend defines the symbols: solid oval for actual tML schema constructs, dashed oval for conceptual tML schema constructs, solid rectangle for actual or conceptual tML schema constructs, solid arrow for contains, dashed arrow for shall be replaced by, and hollow arrow for may be replaced by. + +**Figure 5-1/M.3031 – Containment relationship in tML schema specification** + +NOTE 1 – Figure 5-1 illustrates the schema constructs that are related to conformance statements. Some constructs, which have nothing to do with schema conformance, such as annotation, are not shown in this figure. A conceptual tML schema construct will always be replaced by an actual tML schema construct. The "group" can be viewed as either actual or conceptual tML schema constructs according to specific schema definitions. That is, "group" can appear as an individual construct, or may be replaced by another actual schema construct. + +NOTE 2 – All tML built-in simple types can be found in 2.3 of W3C XML Schema Part 0: Primer [6], which can be used for replacement in the "atomic types" in Figure 5-1. + +The ICS proformas must represent the relationships shown above. + +## 5.2 Guidelines for specification of SICS proformas + +Proforma specifications shall follow the style as documented in the following clauses. Proforma specifications shall provide the information required by this Recommendation. Additional tables may be included for other information, if needed. + +There are three levels of documentation pertaining to SICS, namely: + +- a) Guidelines or recommendation tools for the production of SICS proformas; +- b) A SICS proforma, associated with a standard related to tML-based network management. This is to be entered by a supplier of the implementation. A completed SICS proforma is a SICS; +- c) A SICS prepared by a supplier of the implementation as part of a conformance claim to a standard related to tML-based network management. + +In the scope of this Recommendation, only the guidelines for item b are provided. + +### 5.2.1 General instructions for SICS proforma specification + +This Recommendation provides instructions to construct a tML-based management interface ICS proforma specification. SICS proformas include six sub-proformas: element support proforma, type support proforma, attribute support proforma, identity constraint support proforma, complex type replacement support proforma, and substitution group support proforma. All these proformas are in a tabular form that are similar to the proformas specified in ITU-T Rec. X.724 | ISO/IEC 10165-6 [3]. + +Clause 5.2.2 describes the SICS proforma for element. Clause 5.2.3 describes the SICS proforma for type. Clause 5.2.4 describes the SICS proforma for attribute. Clause 5.2.5 describes the SICS proforma for identity constraint. Clause 5.2.6 describes the SICS proforma for complex type replacement. Clause 5.2.7 describes the SICS proforma for substitution group. Annex A provides an example of SICS proforma specification, which is to be entered by a supplier of an implementation. + +The following common notations, defined in ITU-T Recs X.291 [1] and X.296 [2] are used for the status value column in this Recommendation: + +- m Mandatory; +- o Optional; +- c Conditional; +- x Prohibited ("x" stands for "excluded"); +- Not applicable or out of the scope of this Recommendation. + +NOTE 1 – The notations 'c', 'm', 'o' and 'x' are prefixed by a "c:" when nested under a conditional or optional item of the same table. + +NOTE 2 – The notation 'c' standing for Conditional shall be followed by a number to specify a unique condition, e.g., c1, c3. Different numbers are standard for different conditions, and these conditions shall be clearly stated somewhere in the ICS proforma document. + +NOTE 3 – The notation 'o' may be suffixed by ".n" (where 'n' is a unique number) for mutually exclusive or selectable options among a set of status values. The requirement for this numbered set shall be explicitly stated, preferably in a footnote to the relevant table. + +The following common notations, defined in ITU-T Recs X.291 [1] and X.296 [2] are used for the support answer column: + +- Y Implemented; +- N Not implemented; +- No answer required; +- Ig The item is ignored (i.e., processed syntactically but not semantically). + +The SICS proforma specification is formed by copying clauses 5.2.2, 5.2.3, 5.2.4, 5.2.5, 5.2.6 and 5.2.7, completing the tables except for the "Support" and "Additional information" columns, and extending the remaining tables to meet the requirements of the interface specification. SICS proformas shall provide tables for all the instantiable elements, and their supporting types and attributes, which are defined in a tML-based interface information model. These types can be defined using a variety of methods which can be found in Section 4.5 of W3C Recommendation XML Schema Part 0: Primer [6]. + +To form a SICS from a SICS proforma, the supplier of the implementation shall fill in the "Support" and, if appropriate, the "Additional information" columns of all the tables in the SICS proformas. + +### 5.2.2 Element support proforma + +The purpose of the proforma for element is to provide a mechanism for a supplier of an implementation who claims conformance to a schema element definition to provide conformance information in a standard form. + +The element support proforma is shown in Table 5-1: + +**Table 5-1/M.3031 – Element support table** + +| Index | Identifier | Content model | Values | Nillable | Status | Support | Additional information | +|--------------|-------------------|----------------------|---------------|-----------------|---------------|----------------|-------------------------------| +| | | | | | | | | + +where: + +- The "Index" field is assigned a unique number for each instantiable root element defined in a tML-based interface information model. This index may be referenced in other tables. +- The "Identifier" field is used to identify the name of the element. +- The "Content model" field is provided to identify the content model of the element, which can be one of "empty", "any", "mixed", or "children". See 6.8 for details. The content mode is further expanded in the successive supporting tables. +- The "Values" field is used to identify the fixed or default value of this element, if it is defined in the tML schema. See 6.13 for details. +- The "Nillable" field is used to identify whether the value of this element can be set to nil or not. This field may be entered either "true" or "false". +- The "Status" field is provided to identify the conformance requirement for this element. For each instantiable non-abstract element, if it is mandatory, the "Status" shall be entered 'm'; if it is optional, this field shall be entered 'o' (it may be suffixed by ".n" for some specific conditions, see 5.2.1 for details.); if its occurrence in an instance tML document is under a specific condition, this field shall be entered 'c' followed by a unique number; if it is not instantiable, there will not be such a table for it. +- The "Additional information" field is used for the implementor to provide some implementation-specific information about this element. + +### 5.2.3 Type support proforma + +The purpose of the proforma for type is to provide a mechanism for a supplier of an implementation who claims conformance to a Schema type definition of an element to provide conformance information in a standard form. This table is an expansion for element support table, when the element is of a Schema type "complexType" or "simpleType". This table is expanded by the type information of the complex type and the sub-elements or sub-types it contains in a nested way. + +The type support proforma is shown in Table 5-2: + +**Table 5-2/M.3031 – Type support table** + +| Index | Identifier | Type/ Content model | Order | Nillable | Abstract | Constraints | Values | Status | Support | Additional information | +|--------------|-------------------|----------------------------|--------------|-----------------|-----------------|--------------------|---------------|---------------|----------------|-------------------------------| +| | | | | | | | | | | | + +where: + +- "Index" is the unique reference for a type within the element, or the unique reference for a sub-element within a complex type. +- The "Identifier" field is used to identify the name of a type or the name of a sub-element that is contained in a complex type. + +- The "Type/Content model" field is used to identify the type name of an element, or the category of a simple type of a sub-element. If the row denotes a simple type, this field shall be entered the base type of the simple type, and "union" or "list" could also be entered with the base type if this simple type is such an expansion to one of the basic types; in such a case, more rows are required for the detailed descriptions for the constraints for the simple type; if the row denotes a complex type, this field shall be entered "complexType", or "group" when this is a reference to a group; if the row denotes a sub-element, this field shall be entered the type name of the element type. See 6.9 for details. +- The "Order" field is used to specify the way that the sub-elements may appear in the content model of the complex type, which may be one of the following: "sequence", "choice", "all". +NOTE – This field is valid only when the row denotes a complex type. See 6.16 for details. +- The "Nillable" field is used to specify whether the value of the sub-element can be set to nil or not, when the row denotes a sub-element. +- The "Abstract" field is used to specify whether the complex type or the sub-element is abstract or not. This field may be entered either "true" or "false". +- The "Constraints" field is used to specify the possible constraints for the corresponding table item. The constraints may be divided into three kinds, which are the constraints for a complex type, the constraints for a sub-element, and the constraints for a simple type respectively. "block" or "–" may be applied to the constraints for complex types; "minOccurs" and "maxOccurs" may be applied to those for sub-elements; and all the applicable facets may be applied to those for elements with simple types; when multiple facets are specified in the tML schema, all of them shall be listed in this field with appropriate prefixes. See 6.12 for details. +- The "Values" field is used to identify the fixed or default value (if it is defined in the tML schema) when the row denotes a sub-element. See 6.13 for details. +- The "Additional information" field is used for implementors to indicate some implementation-specific information about a type or a sub-element. + +### **5.2.4 Attribute support proforma** + +The purpose of the proforma for attribute is to provide a mechanism for a supplier of an implementation who claims conformance to a schema attribute definition in a complex type to provide conformance information in a standard form. This table is an expansion for "Type support table" when the complex type or any complex types of its contained sub-elements have attributes defined. This table is expanded by the attributes information defined in the complex type or in the types of its contained sub-elements in a nested way. + +The attribute support proforma is shown in Table 5-3, which is to be applied per complex type that contains attributes: + +**Table 5-3/M.3031 – Attribute support table** + +| Index | Subindex | Identifier | Type | Use | Constraints | Values | Status | Support | Additional information | +|--------------|-----------------|-------------------|-------------|------------|--------------------|---------------|---------------|----------------|-------------------------------| +| | | | | | | | | | | +| | | | | | | | | | | +| | | | | | | | | | | +| | | | | | | | | | | + +where: + +- "Index" is the unique reference for the complex type that has such an attribute definition or declaration. +- The "Subindex" field is to describe the reference of each attribute of the complex type, which is formed by connecting the index of corresponding complex type and a unique number with a delimiter '!'. +- The "Identifier" field is used to identify the name of the attribute. +- The "Type" field is used to identify the type name and its base type of the attribute. As attribute can just be of a simple type, this field has the same semantic for simple types as described in 5.2.3 for the same column. See also 6.10 for details. +- The "Use" field is used to indicate the restrictions on the occurrence of the attribute in an instance document, and it shall be entered the value specified in the tML schema for this attribute, if applicable. +- The "Constraints" field is used to identify the applicable facets for the simple type of the attribute. This field has the same semantic for simple types as described in 5.2.3 for the same column. See also 6.12 for details. +- The "Values" field is used to specify the fixed or default value of this attribute, if it is defined in the tML schema. See 6.13 for details. +- The "Additional information" field is to provide a space for the implementor to add some implementation-specific information about this attribute. + +### 5.2.5 Identity constraint support proforma + +The purpose of the proforma for identity constraint is to provide a mechanism for a supplier of an implementation who claims conformance to a schema identity constraint definition in an element to provide conformance information in a standard form. This table is an expansion for the element support table, when the element and/or its contained sub-elements have identity constraints defined in the tML schema. This table is expanded by the identity information of the element and/or the sub-elements it contains in a nested way. + +The identity constraint support proforma is shown in Table 5-4, which is to be applied per element that contains identity constraints: + +**Table 5-4/M.3031 – Identity constraint support table** + +| Index | Identifier | Category | Selector | Field | Status | Support | Additional information | +|--------------|-------------------|-----------------|-----------------|--------------|---------------|----------------|-------------------------------| +| | | | | | | | | + +where: + +- "Index" is the unique reference of this identity constraint within an element. +- The "Identifier" field is used to identify the name of the identity constraint. +- The "Category" field is used to identify the kind of uniqueness identity, which may be one of the following: "unique", "key", or "keyref". See 6.11 for details. +- The "Selector" field is used to identify the scope of the selected element for uniqueness identity, which is an XPath1 expression. + +1 The XPath concept can be found in XML Path Language 1.0 [10]. + +- The "Field" field is to identify the parts (attributes or elements) relative to each selected element that has to be unique within the scope of the set of selected elements. +- The "Additional information" is to provide a space for the implementor to add some implementation-specific information about the identity constraint. + +### 5.2.6 Complex type replacement support proforma + +The purpose of the proforma for "complex type replacement" is to provide a mechanism for a supplier of an implementation who claims conformance to a schema complex type replacement definition to provide conformance information in a standard form. This table is a normative annex to the type support table, when the complex type of an element may be replaced by its derived type(s) in an instance document. This table is expanded by the information of all the suitable types that are derived from this complex type and is followed by another "Type support table" to describe the details for each item. + +The complex type replacement support proforma is shown in Table 5-5: + +**Table 5-5/M.3031 – Complex type replacement support table** + +| Index | Identifier | Derivation | Status | Support | Additional information | +|--------------|-------------------|-------------------|---------------|----------------|-------------------------------| +| | | | | | | + +where: + +- "Index" is the unique reference for the derived type within this normative annex. +- The "Identifier" field is used to indicate the name of the derived complex type. +- The "Derivation" field is used to indicate the way by which this type has extended the original complex type, which can be "extension" or "restriction". +- The "Additional information" is to provide a space for the implementor to add some implementation-specific information about the complex type replacement. + +### 5.2.7 Substitution group support proforma + +The purpose of the proforma for "substitution group" is to provide a mechanism for a supplier of an implementation who claims conformance to a schema substitution group definition to provide conformance information in a standard form. This table is a normative annex to the type support table, when one or more sub-elements of the complex type may be replaced by their substitution elements in an instance document. This table is expanded by the information of all the possible elements that have been defined as a substitution group for this element. This table is followed by another "Type support table" to describe the details for each element and their types. + +The substitution group support proforma is shown in Table 5-6: + +**Table 5-6/M.3031 – Substitution group support table** + +| Index | Substitutable element | Status | Support | Additional information | +|--------------|------------------------------|---------------|----------------|-------------------------------| +| | | | | | + +where: + +- "Index" is the unique reference for this derived type within this normative annex. +- The "Substitutable element" field is used to indicate the name of the element that can be a substitution for the element in an instance document. +- The "Additional information" is to provide a space for the implementor to add some implementation-specific information about the substitution group. + +# **6 Instructions for completing the SICS proforma** + +This clause gives the instructions for completing each column defined in 5.2 and its subclauses. These instructions can be divided into two classes; one is the instruction for developing the ICS proforma specification, and the other is for the implementors to complete the proformas. + +## **6.1 The "Element Support Table"** + +In a complete tML-based interface information model there are one or more root elements. Corresponding to each root element there shall be an "Element Support table" in the ICS proforma. Each table is assigned a unique index within the scope of an ICS proforma document. + +## **6.2 The "Type Support Table"** + +When elements or types include nested definitions of direct and/or indirect child, the expansion of the child is not repeated more than once. Instead, after expanding once, a reference is made in the "Additional Information" column to the index where the definition is expanded. In other words, this approach avoid repeating the contents multiple times within the same table. + +## **6.3 The "Status" column** + +This column specifies the conformance requirements and indicates the level of support required for conformance to a specific tML schema. The values are the ones defined in 5.2.1. + +Figure 6-1 illustrates the status of tML schema constructs with containment relationships according to different conformance requirements: + +![A hierarchical tree diagram showing the status of contained constructs. The root element has Status: m. It branches into three 'type' boxes: Status: m (mandatory), Status: o (optional), and Status: c(n) (conditional). The 'type' box with Status: m branches into three 'sub-element' boxes: Status: m (mandatory), Status: o (optional), and Status: c(n) (conditional). The 'type' box with Status: o branches into one 'sub-element' box with Status: c:m (mandatory). The 'type' box with Status: c(n) branches into three 'sub-element' boxes: Status: c(n) (mandatory), Status: c(n):o (optional), and Status: c(n):c(n2) (conditional).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +A hierarchical tree diagram showing the status of contained constructs. The root element has Status: m. It branches into three 'type' boxes: Status: m (mandatory), Status: o (optional), and Status: c(n) (conditional). The 'type' box with Status: m branches into three 'sub-element' boxes: Status: m (mandatory), Status: o (optional), and Status: c(n) (conditional). The 'type' box with Status: o branches into one 'sub-element' box with Status: c:m (mandatory). The 'type' box with Status: c(n) branches into three 'sub-element' boxes: Status: c(n) (mandatory), Status: c(n):o (optional), and Status: c(n):c(n2) (conditional). + +(a) The root element is mandatory + +![Two hierarchical tree diagrams. The left diagram (b) shows a root element with Status: o branching into three 'type' boxes: Status: c:m (mandatory), Status: c:o (optional), and Status: c:c(n) (conditional). The right diagram (c) shows a root element with Status: c(n) branching into three 'type' boxes: Status: c(n) (mandatory), Status: c(n):o (optional), and Status: c(n):c(n2) (conditional).](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +Two hierarchical tree diagrams. The left diagram (b) shows a root element with Status: o branching into three 'type' boxes: Status: c:m (mandatory), Status: c:o (optional), and Status: c:c(n) (conditional). The right diagram (c) shows a root element with Status: c(n) branching into three 'type' boxes: Status: c(n) (mandatory), Status: c(n):o (optional), and Status: c(n):c(n2) (conditional). + +(b) The root element is optional + +(c) The root element is conditional + +M.3031\_F6-1 + +**Figure 6-1/M.3031 – The status diagram for contained constructs** + +Guidelines for completing this field are as follows: + +- a) For the "Element support table", if it is mandatory, the "Status" field shall be entered 'm'; if it is optional, this field shall be entered 'o' (it may be suffixed by ".n" for some specific conditions, see 5.2.1 for details); if its occurrence in an instance document is under a specific condition, this field shall be entered 'c' followed by a unique number. If this element is substitutable, the same rules described in item f shall be applied. +- b) For the "Type support table", if the row denotes a type, the status of the item is shown in Figure 6-1: this field shall be entered the same value as entered in "Element support table", except that when the element with this type is optional, this field shall be entered the status of the type with "c:" as the prefix. The same rule is also applicable for the constructs that have a containment relationship between them, that is, the status of a contained construct is subject to the status of its containing construct. If the row denotes a sub-element, the status follows the same rule as described above, which is also shown in Figure 6-1. If a sub-element is abstract, this field shall be entered 'x'. Otherwise, if the status of its containing type is conditional, this field is composed of the numbers starting with the value of the containing type and includes its own conformance requirements. If the status of its + +containing type is 'm', this field shall be entered its own conformance requirement. If the complex type is replaceable, the same rules described in item f shall be applied. + +- c) For "Attribute support table", the completing rule follows the same one as described in item b for sub-element. The default policy for the requirements is: when the "Use" field for this attribute is entered "required", its status is mandatory; if the "Use" field is entered "optional", its status is also optional; if the "Use" field is entered "prohibited", its status is also prohibited. +- d) For "Identity constraint support table", the completing rule follows the same one as described in item b for simple types. +- e) For "Complex type replacement support table", and "Substitution group support table", if there are no specific constraints specified for the type or element to be replaced or substituted (in the "Element support table" or "Type support table"), the default value for "Status" field in these two tables is optional (it may be suffixed by ".n" for some specific conditions, see 5.2.1 for details). If the type or element (sub-element) to be replaced or substituted is abstract, the default value for "Status" field in these two tables is mandatory. The default value may be changed according to the actual usage allowed or prohibited stated in the tML-based interface specification. +- f) If a root element, sub-element or complex type is substitutable or replaceable, the "status" column of the item shall be entered 'o' (it may be suffixed by ".n" for some specific conditions, see 5.2.1 for details). + +## 6.4 The "Support" column + +This column shall be completed by the supplier or implementor to indicate the support level of implementation of each item. The available selections for this field are listed in 5.2.1. + +If an item is mandatory, the "Support" column must be entered 'Y' for a conformant claim. Otherwise, this column may be entered either 'Y' or 'N'. + +## 6.5 The "Index" column + +Each line within the SICS proforma is numbered at the left-hand edge of the line. This numbering is included as a means of uniquely identifying all possible implementation details within the SICS proforma. + +The means of referring to individual responses is done by the following sequence. + +- a) A reference to the super-clause of the item; +- b) The delimiting character '.'; +- c) A unique number. + +An example of the use of this notation is illustrated in Annex A. + +The "Index" column exhibits the containment relationship between the constructs within the scope of a root element. The containment relationship is illustrated in 5.1: Schema overview. + +## 6.6 The "Subindex" column + +This column has the same format as the "Index" column. It is composed of numbers starting with the value in the "Index" field and includes the hierarchy down one or two levels. For the following example shown in Table 6-1, the value of the "Index" field is "2", and the "Subindex" field are entered "2.2" and "2.2.1", respectively. + +**Table 6-1/M.3031 – An example for the usage of "Subindex" column** + +| Index | Subindex | Identifier | Type | Use | Constraints | Values | Status | Support | Additional information | +|-------|----------|------------|------------|----------|-------------|--------|--------|---------|------------------------| +| 2 | 2.2 | postcode | simpleType | optional | | | o | | | +| | 2.2.1 | | string | | length=6 | | c:m | | | + +## 6.7 The "Identifier" column + +This column specifies the name or identifier of a specific item in the appropriate table. + +- a) For the "Element support table", this field shall be entered the name of the element2. +- b) For the "Type support table", if the row denotes a complex type or a simple type, this field shall be entered the name of the type. If the row denotes a sub-element, this field shall be entered the name of the sub-element. +- c) For the "Attribute support table", this field shall be entered the name of the attribute. +- d) For the "Identity constraint support table", this field shall be entered the name for this constraint, or left empty when the constraint is unnamed. +- e) For the "Complex type replacement support table", this field shall be entered the name of the complex type replacing the original type. +- f) For the "Substitution group support table", this field shall be entered the name of the element that is declared as a substitution group of the specified element. + +## 6.8 The "Content model" column + +The "Content model" field in the "Element support table" shall be entered the content model of the element. The valid values for the content model are "empty", "any", "mixed", or "children". If the element is empty, that is, the element has no content at all, this field shall be entered "empty"; if there is no constraint on its content in any way, this field shall be entered "any"; if character data may appear alongside sub-elements and is not confined to the deepest sub-elements, this field shall be entered "mixed"; otherwise, if it contains sub-elements, this field shall be entered "children". + +## 6.9 The "Type/Content model" column + +The "Type/Content model" column of the "Type support table" (which is to be entered in the proforma specification if applicable) contains the type or content model information of a specific item. If the row denotes a simple type, this field shall be entered the base type of the simple type. Besides the built-in types, this field may also be entered "union" or "list", with its base atomic types followed in a bracket if this simple type is such an expansion to one of the built-in basic types; if the row denotes a complex type, this field shall be entered "complexType"; if the row denotes a group, this field shall be entered "group"; if the row denotes a sub-element, this field shall be entered either the content model of the sub-element (see 6.8 for the possible values), when its type is a complex type, or the base type of the simple type, when its type is a simple type. + +## 6.10 The "Type" column + +The "Type" column of the "Attribute support table" contains the type information of an attribute. This field shall be entered the name of the simple type and the base type of the attribute, or just the base type of the attribute when the simple type is unnamed. The completing instructions follow the same rules as described in 6.9 for simple type. + +2 The name of the element should include the namespace information for uniqueness, if applicable. The same rule also applies to names of types or sub-elements. + +## 6.11 The "Category" column + +The "Category" column of the "Identity constraint support table" contains the category for the uniqueness identity type information of a specific item. The value of the uniqueness identity must be one of the following: "unique", "key", or "keyref". When an attribute is marked with "key" in the identity constraint, its value must be unique and cannot be set to nil. + +## 6.12 The "Constraints" column + +The "Constraints" columns of the tables (which are to be entered in the proforma specification if applicable) contain the constraints for the specific item. + +- a) For the "Attribute support table", this field shall be entered the information of applicable facets3 for the simple type. When multiple facets are specified in the tML schema, all values shall be listed in this field with the corresponding facet as the prefix, for example: "maxInclusive=20", "totalDigits=4". When the type is an enumeration, all the possible values shall be listed in this field in a bracket with the prefix "enum=", e.g., "enum={one, two, three}". +- b) For the "Type support table", the constraints may be divided into three kinds: the constraints for a complex type, the constraints for a sub-element, or the constraints for a simple type. When the row denotes a simple type, the completing instructions follow the same rules as described in item a. When the row denotes a complex type, and the "block" attribute is specified for this type in the tML schema, the value of the "block" attribute, which may be "restriction", "expansion", or "all", shall be entered in this field with the prefix "block=", otherwise '-' shall be applied. When the row denotes a sub-element, and the value of "minOccurs" and/or "maxOccurs" is defined, this field shall contain these values with the corresponding prefixes. If the sub-element is of a simple type, the possible facets constraints for its type shall also be listed in this field in a sub-unit, which follows the same rules as specified in item a. In Annex A, there is an example showing this usage. + +## 6.13 The "Values" column + +The "Values" columns of the tables (which are to be entered in the proforma specification if applicable) contain the predefined special values for the specific item. This field shall be entered the "fixed" or "default" values for an element of a simple type or an attribute, if the values are defined in the tML schema. The value is prefixed by either "fixed=" or "default=". This rule applies to "Element support table", "Type support table", and "Attribute support table". + +## 6.14 The "Additional information" column + +This column contains additional information provided by suppliers not contained anywhere else. In the following cases, extra information shall be entered according to the tML schema. + +For "Type Support table", if the row denotes a complex type that may be replaced by any of its derived types in an instance document, a reference to the corresponding "Complex type replacement support table" shall be entered in this field. If the row denotes an element that can be replaced by any of its substitutable elements in an instance document, a reference to the corresponding "Substitution group support table" shall be entered in this field, e.g., "See Annex A x.x". If the row denotes a type or element that regards itself as a direct or indirect child, the table will stop expanding for this branch. However, information shall be entered in this field, indicating the index of its direct or indirect parent. + +--- + +3 All the facet definitions can be found in Annex B in W3C XML Schema Part 0: Primer [6]. + +## **6.15 The "Use" column** + +The valid values for the "Use" column in the "Attribute support table" are "required", "optional", and "prohibited". If the attribute must appear once, this field shall be entered "required"; if the attribute may appear once or not at all, it shall be entered "optional"; if the attribute must not appear, it shall be entered "prohibited". + +## **6.16 The "Order" column** + +The valid values for the "Order" column in the "Type support table" are "sequence", "choice", and "all", when the row denotes a complex type. If one or more of the sub-elements defined in a complex type must appear in a predefined order, this field shall be entered "sequence". If only one or one group of the sub-elements contained in the complex type will appear in an instance document, the field shall be entered "choice". If the children may appear once or not at all, and may appear in any order, this field shall be entered "all". + +## **6.17 The "Nillable" column** + +The "Nillable" column is used to specify whether the value of an element or sub-element can be set to nil or not. For the "Element support table", or the "Type support table" when the row denotes a sub-element, the "Nillable" field shall be entered "true" if the element can be set to a nil value; otherwise this field shall always be entered "false". + +## **6.18 The "Abstract" column** + +The "Abstract" column in the "Type support table" indicates whether or not the corresponding complex type or sub-element is abstract. If the complex type or element is abstract, "true" is entered; if it is not, "false" is entered; for all the other cases, "-" is applied. + +## **6.19 The "Selector" column** + +The "Selector" column in the "Identity constraint support table" shall be entered the XPath expression for the scope of the elements for uniqueness identity. The XPath is composed of a sequence of elements, each of which is a direct sub-element of its parent, except the first sub-element in the tree which does not possess a parent. See Annex A for the usage example. + +## **6.20 The "Field" column** + +The "Field" column in "Identity constraint support table" shall be entered the XPath expression for the parts (attributes or elements) relative to each selected element. The attribute or element must be unique within the scope of the set of selected elements. + +# Annex A + +## An example of SICS proforma specification + +## A.1 tML schema definition + +In this annex, the SICS proformas for "Element support", "Type support", "Attribute support", "Identity constraint support", "Complex type replacement support", and "Substitution group support" are illustrated. The following is a simple example of a tML schema definition: + +``` + + + + + + Dong Wenli - BUPT China + 05-04-2004 + This Schema contains some example Schema definitions. + This example doesn't include the whole tML schema metadata provided + in Annex A/M.3030, only because this is just an example showing some + Schema features in order to display the corresponding SICS proformas + in A.2. It is not necessary to include the whole tML schema metadata + in M.3030 for this purpose. No more annotation is provided in + this Schema example. + M.tMLconf + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## A.2 SICS + +Assuming that in the above schema definition, only the externalGsmCell is the root element, the SICS proformas for this simple schema-based information model can be illustrated as follows: + +E 1 : tML:externalGsmCell + +Table 1 : Element support + +| Index | Identifier | Content model | Values | Nillable | Status | Support | Additional information | +|-------|---------------------|---------------|--------|----------|--------|---------|------------------------| +| 1 | tML:externalGsmCell | children | | false | m | | | + +Table 1.1 : Type support + +| Index | Identifier | Type/Content model | Order | Nillable | Abstract | Constraints | Values | Status | Support | Additional information | +|-------------------|---------------------|---------------------|----------|----------|----------|----------------------------|--------|--------|---------|----------------------------| +| 1.1 | | complexType | sequence | – | false | | – | m | | | +| 1.1.1 | tML:userLabel | children | – | false | false | maxOccurs=
unbounded | | m | | | +| 1.1.1.1 | tML:Usertype | complexType | sequence | – | false | | – | o | | see Annex
[A 1.1.1.1] | +| 1.1.1.1.1 | tML:name | children | – | true | false | minOccurs=0
maxOccurs=3 | | c:o | | see Annex
[A 1.1.1.1.1] | +| 1.1.1.1.1.1 | | complexType | choice | – | false | | – | c:m | | | +| 1.1.1.1.1.1.1 | tML:metar | decimal | – | false | false | | | c:o | | | +| 1.1.1.1.1.1.2 | tML:name | children | – | true | false | | | c:o | | see Table
1.1.1.1.1 | +| 1.1.1.1.2 | tML:ddTop | group | choice | – | – | | – | c:m | | | +| 1.1.1.1.2.1 | tML:ddc1 | simple | – | false | false | | | c:o | | | +| 1.1.1.1.2.1.1 | | tML:ListOfMyIntType | – | – | – | | – | c:m | | | +| 1.1.1.1.2.1.1.1 | tML:ListOfMyIntType | list | – | – | – | | – | c:m | | | +| 1.1.1.1.2.1.1.1.1 | | string | – | – | – | enum {one
two three } | – | c:m | | | +| 1.1.1.1.2.2 | tML:ddc2 | date | – | false | false | | | c:o | | | +| 1.1.2 | tML:absElement | string | – | false | true | | | x | | see Annex
[A 1.1.2] | + +### Attribute support + +| Index | Subindex | Identifier | Type | Use | Constraints | Values | Status | Support | Additional information | +|---------|-------------|------------|------------|----------|----------------------------|---------------|--------|---------|------------------------| +| 1.1.1.1 | 1.1.1.1.3 | id | string | required | | fixed=bj88 | c:m | | | +| 1.1.1.1 | 1.1.1.1.4 | contr | simpleType | optional | | default=66666 | c:o | | | +| | 1.1.1.1.4.1 | | string | | minLength=5
maxLength=8 | – | c:m | | | + +Table 1.2 : Identity constraint support + +| Index | Identifier | Category | Selector | Field | Status | Support | Additional information | +|-------|------------|----------|---------------|-------|--------|---------|------------------------| +| 1.2.1 | empid | key | tML:userLabel | id | m | | | + +### Annex [A 1.1.1.1] + +Table A.1.1.1.1 : Complex type replacement support for "tML:Usertype" + +| Index | Identifier | Derivation | Status | Support | Additional information | +|-------|---------------|-------------|--------|---------|------------------------| +| 1 | tML:Busertype | restriction | o | | | +| 2 | tML:Ausertype | extension | o | | | + +| Index | Identifier | Type/Content model | Order | Nillable | Abstract | Constraints | Values | Status | Support | Additional information | +|-----------|--------------|--------------------|----------|----------|----------|----------------------------|--------|--------|---------|------------------------| +| 1.1 | tML:Usertype | complexType | sequence | – | false | | – | c:m | | | +| 1.1.1 | tML:name | children | – | true | false | MinOccurs=0
maxOccurs=3 | | c:o | | | +| 1.1.1.1 | | complexType | choice | – | false | | – | c:m | | | +| 1.1.1.1.1 | tML:metar | decimal | – | false | false | | | c:o | | | +| 1.1.1.1.2 | tML:name | children | – | true | false | | | c:o | | see Table 1.1.1 | + +### Attribute support + +| Index | Subindex | Identifier | Type | Use | Constraints | Values | Status | Support | Additional information | +|-------|----------|------------|--------|----------|-------------|------------|--------|---------|------------------------| +| 1.1 | 1.1.2 | id | string | required | | fixed=bj88 | c:m | | | + +| Index | Identifier | Type/Content model | Order | Nillable | Abstract | Constraints | Values | Status | Support | Additional information | +|---------------|---------------------|---------------------|----------|----------|----------|----------------------------|--------|--------|---------|------------------------| +| 2.1 | tML:Usertype | complexType | sequence | – | false | | – | c:m | | | +| 2.1.1 | tML:name | children | – | true | false | minOccurs=0
maxOccurs=3 | | c:o | | | +| 2.1.1.1 | | complexType | choice | – | false | | – | c:m | | | +| 2.1.1.1.1 | tML:metar | decimal | – | false | false | | | c:o | | | +| 2.1.1.1.2 | tML:name | children | – | true | false | | | c:o | | see Table 2.1.1 | +| 2.1.2 | tML:ddTop | group | choice | – | false | | – | c:m | | | +| 2.1.2.1 | tML:ddc1 | simple | – | false | false | | | c:o | | | +| 2.1.2.1.1 | | tML:ListOfMyIntType | – | – | – | | – | c:m | | | +| 2.1.2.1.1.1 | tML:ListOfMyIntType | list | – | – | – | | – | c:m | | | +| 2.1.2.1.1.1.1 | | string | – | – | – | enum {one
two three } | – | c:m | | | +| 2.1.2.2 | tML:ddc2 | date | – | false | false | | | c:o | | | + +### Attribute support + +| Index | Subindex | Identifier | Type | Use | Constraints | Values | Status | Support | Additional information | +|-------|----------|------------|------------|----------|----------------------------|---------------|--------|---------|------------------------| +| 2 | 2.2 | postcode | simpleType | optional | | | c:o | | | +| | 2.2.1 | | string | | length=6 | | c:m | | | +| 2.1 | 2.1.3 | id | string | required | | fixed=bj88 | c:m | | | +| 2.1 | 2.1.4 | contr | simpleType | optional | | default=66666 | c:o | | | +| | 2.1.4.1 | | string | | minLength=5
maxLength=8 | – | c:m | | | + +### Annex [A 1.1.1.1.1] + +Table A 1.1.1.1.1: Substitution group support for element "tML:name" + +| Index | Substitutable element | Status | Support | Additional information | +|-------|-----------------------|--------|---------|------------------------| +| 1 | tML:namesub | o | | | + +| Index | Identifier | Type/Content model | Order | Nillable | Abstract | Constraints | Values | Status | Support | Additional information | +|-------|-------------|--------------------|-------|----------|----------|-------------|--------|--------|---------|------------------------| +| 1 | tML:namesub | string | – | false | false | | | o | | | + +## Annex [A 1.1.2] + +Table A 1.1.2 : Substitution group support for element "tML:absElement" + +| Index | Substitutable element | Status | Support | Additional information | +|-------|-----------------------|--------|---------|------------------------| +| 1 | tML:absElementSub | m | | | + +| Index | Identifier | Type/Content model | Order | Nillable | Abstract | Constraints | Values | Status | Support | Additional information | +|-------|-------------------|--------------------|-------|----------|----------|-------------|--------|--------|---------|------------------------| +| 1 | tML:absElementSub | integer | – | false | false | | | m | | | + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3040-201904-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/M/T-REC-M.3040-201904-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8869304219db09dc5b24a972e30e09259c98f01b --- /dev/null +++ b/marked/M/T-REC-M.3040-201904-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf2224b6bb2eec9e33502f99398d2b2d00905a4daa8c7bfeb1018a8150141607 +size 38800 diff --git a/marked/M/T-REC-M.3040-201904-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/M/T-REC-M.3040-201904-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/M/T-REC-M.3040-201904-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/M/T-REC-M.3040-201904-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/M/T-REC-M.3040-201904-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05d46e51da48f5a818bd1067fb40faa7eb0b8a5b --- /dev/null +++ b/marked/M/T-REC-M.3040-201904-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:127aebd9aa9bbf60821a89951dfb461b88f5de2c52a3461b6f4149e94b42bd81 +size 21904 diff --git a/marked/M/T-REC-M.3040-201904-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/M/T-REC-M.3040-201904-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51018fe4d395f59b537eae13f99507b9fb21d105 --- /dev/null +++ b/marked/M/T-REC-M.3040-201904-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b392a6651223ba2870d74b3f744796912fa65109d13c82aadddb1e1ad0d6900 +size 37483 diff --git a/marked/M/T-REC-M.3040-201904-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/M/T-REC-M.3040-201904-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18df5a168a7e66d7848983df7157337de34deed2 --- /dev/null +++ b/marked/M/T-REC-M.3040-201904-I_PDF-E/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bef32528f8965695ecc2ce2bbc789408736b857c993b4c4bce5223ced7cf4a63 +size 14355 diff --git a/marked/M/T-REC-M.3040-201904-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/M/T-REC-M.3040-201904-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5b1f68e595997f66dac341d7e447041109eb45d --- /dev/null +++ b/marked/M/T-REC-M.3040-201904-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82dbe389caa7703ede4c33abc2fb756c13d6dc19d4f96c137ce8be8b28632009 +size 18442 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/M/T-REC-M.3041-202002-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfceb9ceb1e12792d340bde681ee00b7b6945017 --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f5dea0273238d32f99ab98cadd509018b0895f743fbe1ac28cfe7b640d5bfe8 +size 21088 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3041-202002-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..202e5125c69495a2875d5ef494c4b0d95a9c60df --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af5921cc60392ab4ff1852d635b059e25bc14a7d4f31935a28284e63774d9fbd +size 114532 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/M/T-REC-M.3041-202002-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23680357c37214ad9b29dc1d988b9f3b3333a340 --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5052cff6d0002e1be48d9f56bc18660e89cdc9e6ccc3c6d103606460263184fe +size 31495 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3041-202002-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca0dce65df64f4fb10a81b8f87284f793e4b1d3d --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e92e387e62cb6d86114f61d012b89bb4f66ab5171494a2177d9dfd36f6a2a566 +size 4206 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/M/T-REC-M.3041-202002-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..484e4e770e855fa4b736c43f34b6c680c033c6f2 --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eaab62524f3efc046bedd311c829b9919de3d2d3e7eb9d8b5b9c449c425f5da1 +size 26071 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3041-202002-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb23ad0c70588cce76eeff56fb6024f7ccf3eaf2 --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ead3e5dfd9053647fd0fe4a2dc029d5e44480fcbe94ef6771d36a448ab32b71 +size 98487 diff --git a/marked/M/T-REC-M.3041-202002-I_PDF-E/raw.md b/marked/M/T-REC-M.3041-202002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d59caaa8c55e1bc4d8ff37f20ea103220b4c59d9 --- /dev/null +++ b/marked/M/T-REC-M.3041-202002-I_PDF-E/raw.md @@ -0,0 +1,548 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3041** + +(02/2020) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Framework of smart operation, management and maintenance** + +Recommendation ITU-T M.3041 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3041 + +# Framework of smart operation, management and maintenance + +## Summary + +Recommendation ITU-T M.3041 introduces a framework of smart operation, management and maintenance (SOMM). In this Recommendation, characteristics, scenarios and the functional architecture of SOMM are provided to support service operation, network management and infrastructure maintenance for both traditional non software-defined networking/network function virtualization (non-SDN/VFN), and SDN/NFV aware networks. This Recommendation also describes the relationship of the functional architecture of SOMM with the logical layered architecture (LLA) of a telecommunications management network (TMN). + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.3041 | 2020-02-13 | 2 | 11.1002/1000/14181 | + +## Keywords + +Maintenance, management, operation, smart. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "*shall*" or some other obligatory language such as "*must*" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------------------------|------| +| 1 Scope | 1 | +| 2 References | 1 | +| 3 Definitions | 1 | +| 3.1 Terms defined elsewhere | 1 | +| 3.2 Terms defined in this Recommendation | 2 | +| 4 Abbreviations and acronyms | 2 | +| 5 Conventions | 3 | +| 6 Introduction | 3 | +| 7 Scenario classification of SOMM | 4 | +| 7.1 Smart operation scenarios | 4 | +| 7.2 Smart management scenarios | 5 | +| 7.3 Smart maintenance scenarios | 5 | +| 7.4 Smart comprehensive analysis scenarios | 5 | +| 7.5 Traditional OAM scenarios | 5 | +| 8 Functional architecture of SOMM | 5 | +| 8.1 Top-view of SOMM for integrated network | 5 | +| 8.2 Layered functional architecture of SOMM | 6 | +| 8.3 Sub-functions in layered functional architecture of SOMM | 7 | +| 9 Development considerations of SOMM | 10 | +| Annex A – Relationship between the LLAs of [ITU-T M.3010] and this Recommendation | 11 | + + + +# Recommendation ITU-T M.3041 + +# Framework of smart operation, management and maintenance + +# 1 Scope + +This Recommendation provides the framework of smart operation, management and maintenance (SOMM). It describes the characteristics, scenarios and the functional architecture of SOMM to support service operation, network management, and infrastructure maintenance for both traditional non-SDN/NFV and SDN/NFV aware networks. + +This Recommendation also describes the relationship of the functional architecture of SOMM with the logical layered architecture (LLA) of a telecommunication management network (TMN). + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions*. +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3040] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. +- [ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*. +- [ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network*. +- [ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 logical layered architecture** [ITU-T M.3010]: An architectural concept that organizes the management functions into a grouping of management layers and describes the relationship between the layers. + +**3.1.2 management function** [ITU-T M.3010]: The smallest part of a management service as perceived by the user of the service. + +**3.1.3 management function set** [ITU-T M.3010]: TMN management function set is a grouping of TMN management functions that contextually belong together, i.e., they are related to a specific management capability (e.g., alarm reporting functions, traffic management control). The TMN management function set is the smallest reusable item of functional specification. The TMN + +management function set must be considered as a whole. It is similar to the requirements part of the OSI SMF (system management function). + +**3.1.4 management service** [ITU-T M.3010]: A management service is an offering fulfilling specific telecommunications management needs. + +**3.1.5 network slice** [ITU-T Y.3100]: A logical network that provides specific network capabilities and network characteristics. + +**3.1.6 operations system** [ITU-T M.3010]: A physical block which performs operations systems functions (OSFs). + +**3.1.7 operations systems function (OSF)** [ITU-T M.3010]: A function block that processes information related to the telecommunications management for the purpose of monitoring/coordinating and/or controlling telecommunication functions including management functions (i.e., the TMN itself) + +**3.1.8 orchestration** [ITU-T M.60]: Sequencing where a management operation is dependent upon several managed objects in a network being changed in a strict sequence. + +**3.1.9 q reference points** [ITU-T M.3010]: A reference point located between NEF and OSF, between QAF and OSF, and between OSF and OSF. + +**3.1.10 software-defined networking** [ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner. + +**3.1.11 telecommunication smart maintenance** [ITU-T M.3040]: The maintenance carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system, which can provide strong human-computer interaction capabilities and online guidance to personnel, to achieve higher efficiency and precision of actions. + +**3.1.12 x reference points** [ITU-T M.3010]: A reference point located between OSF function blocks in different TMNs. + +NOTE – Entities located beyond the x reference point may be part of an actual TMN (OSF) or part of a non-TMN environment (OSF-like). This classification is not visible at x reference points. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|---------------------------------------------------------------------| +| AI | Artificial Intelligence | +| AR | Augmented Reality | +| DevOps | Development Operations | +| DM-OSF | Data Convergence and Management Layer – Operations Systems Function | +| EMS | Equipment Management System | +| E-OSF | Element Management Layer – Operations Systems Function | +| FCAPS | Fault, Configuration, Accounting, Performance, and Security | +| IoT | Internet of Things | +| IM-OSF | Infrastructure Management Layer – Operations Systems Function | +| IT | Information Technology | + +| | | +|--------|----------------------------------------------------------| +| LLA | Logical Layered Architecture | +| MANO | Management and Orchestration | +| MS-OSF | Management Service Layer – Operations Systems Function | +| NE | Network Element | +| NEF | Network Element Function | +| NFV | Network Function Virtualization | +| NMS | Network Management System | +| N-OSF | Network Management Layer – Operations Systems Function | +| OAM | Operations, Administration and Maintenance | +| OS | Operations System | +| OSF | Operations Systems Function | +| OSI | Open Systems Interconnection | +| PaaS | Platform as a Service | +| QAF | Q Adapter Function block | +| SDN | Software-defined Networking | +| SA-OSF | Scenario Application Layer – Operations Systems Function | +| SMF | System Management Function | +| SOMM | Smart Operation, Management and Maintenance | +| S-OSF | Service Management Layer – Operations Systems Function | +| TMN | Telecommunication Management Network | + +# 5 Conventions + +None. + +# 6 Introduction + +This Recommendation presents scenarios and functional architecture of smart operation, management and maintenance (SOMM), which is to support service operation, network management, and infrastructure maintenance for both traditional non software-defined networking (SDN)/network function virtualization (NFV) networks and SDN/NFV aware networks. + +The objective of the SOMM framework is to extend the traditional logical layered architecture (LLA) of [ITU-T M.3010] by introducing new layers and operations systems functions (OSFs) to support a wider variety of telecommunication management activities for the integrated network, and to support rapid deployment of complicated operations systems (OSs) based on open services and convergent data. + +With the rapid evolution of network and information technology (IT), the main characteristics of the SOMM framework can be described as follows: + +- **Intelligent:** Based on big data, artificial intelligence (AI) algorithms and smart devices, the OSs in a SOMM framework can perform management and maintenance work instead of humans in a more precise and easier way, and can even give predictive judgements on network or service failures. + +- **Data driven:** A SOMM framework converges masses of data from different OSs to a unified data model, supporting data sharing, data mining, data correlation, machine learning and other usage intents. +- **Integrated:** A SOMM framework can be applied for current and future networks. It can also support cross-domain management activities to fulfil end-to-end services for customers. +- **Agile:** A SOMM framework is a service-oriented architecture in which each operations systems function (OSF) is packaged as a service to be opened. A new OS can be deployed quickly with these open services and convergent data, along with the common infrastructure platform for OSs. + +Typical application scenarios of a SOMM framework are presented in clause 7. + +# 7 Scenario classification of SOMM + +Some typical application scenarios of SOMM are listed in Table 1. It should be noted that the scenarios listed in the table are typical ones, and that these do not cover all the possibilities. Any possible scenario that can be classified into these types should also be supported by SOMM. + +The scenarios of SOMM could be classified into five types which are smart operation, smart management, smart maintenance, smart comprehensive analysis and traditional operations, administration and maintenance (OAM). + +**Table 1 – Scenario classification of SOMM** + +| | | +|-----|---------------------------------------------| +| 1) | Smart operation scenarios | +| i. | Customer service support | +| ii. | End-to-end service provision and operation | +| 2) | Smart management scenarios | +| i. | Synergy management of multi-tech networks | +| ii. | Smart network monitoring | +| 3) | Smart maintenance scenarios | +| i. | On-site telecommunication smart maintenance | +| 4) | Smart comprehensive analysis scenarios | +| i. | What-if analysis | +| ii. | Big data analysis | +| 5) | Traditional OAM scenarios | + +## 7.1 Smart operation scenarios + +### 7.1.1 Customer service support + +Typical scenarios of customer service support include malfunction complaint pre-treatment, large area fault interception of customers, end-to-end service fault processing and customer-specific network monitoring. + +### 7.1.2 End-to-end service provision and operation + +End-to-end service provision and operation can occur in the situation of cross-vendor, cross-domain cases, which is an important way to achieve the closed-loop operation and the quality of service for customers through operation processes. + +## **7.2 Smart management scenarios** + +### **7.2.1 Synergy management of multi-tech networks** + +Typical scenarios of synergy management of multi-tech networks currently include cloud and network synergy management and 5G network slice management. + +In the cloud and network synergy management scenario, unified orchestration of network and cloud resources are needed to support cloud and network convergent services be deployed and fulfilled quickly on customer's demands. + +5G network slice management is another typical synergy management scenario. 5G network slicing management occurs among multi-layer and multi-domain networks, in which different technologies are used. To realize an end-to-end slice management, orchestration of different slice segments should be supported. + +### **7.2.2 Smart network monitoring** + +Typical scenarios of smart network monitoring include daily operation monitoring for networks and services in an end-to-end view. In addition, operation monitoring under the cases such as critical incidents, natural disasters, and emergency communication scenarios are also included. + +## **7.3 Smart maintenance scenarios** + +### **7.3.1 On-site telecommunication smart maintenance** + +Typical scenarios of on-site telecommunication smart maintenance include on-site patrol, on-site overhaul, on-site troubleshooting and activating new services such as installation and configuration of home gateway. These maintenance activities can be carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system [ITU-T M.3040]. + +## **7.4 Smart comprehensive analysis scenarios** + +### **7.4.1 What-if analysis** + +SOMM can provide cross-layer and cross-domain operation and management, making smart what-if analysis possible. Smart what-if analysis can perform failure simulation, network capacity expansion simulation, throughput simulation, etc. Smart what-if analysis is carried out off-line, and AI prediction can be used in what-if analysis. + +### **7.4.2 Big data analysis** + +SOMM can support big data analysis for different applications based on convergent data with the use of data collecting, data processing, data modelling, data mining and machine learning technologies, assisting operators to better realize the value of data. + +## **7.5 Traditional OAM scenarios** + +Traditional OAM scenarios include the telecommunication traditional business management, service management, network management and element management activities of [ITU-T M.3010]. + +# **8 Functional architecture of SOMM** + +This clause first introduces the top-view of SOMM for integrated networks in clause 8.1. Then clauses 8.2 and 8.3 describe layered functional architecture of SOMM. + +## **8.1 Top-view of SOMM for integrated network** + +The SOMM framework needs to support integrated networks, including SDN/NFV aware networks and non-SDN/NFV networks, as is shown in Figure 1. + +The SOMM system includes network management system (NMS)/ equipment management system (EMS) which is used for the management of non-SDN/NFV networks. The SOMM system also includes software-defined networking (SDN) orchestrator/controller, network function virtualization (NFV) management and orchestration (MANO) for the management of SDN/NFV aware networks. + +SDN aware networks and NFV aware networks can be managed by SDN orchestrator/controller and NFV MANO separately, or by a unified orchestrator jointly. + +![Figure 1: Top-view of smart operation, management and maintenance system. The diagram shows a top-level box labeled 'Smart operation, management and maintenance system' which contains a dashed box labeled 'Traditional NMS/EMS'. Below this top box, two boxes are connected: 'Non-SDN/NFV network' on the left and 'SDN/NFV aware network' on the right. The label 'M.3041(20)_F01' is at the bottom right.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +``` + +graph TD + subgraph SOMM [Smart operation, management and maintenance system] + NMS[Traditional NMS/EMS] + end + SOMM --- NonSDN[Non-SDN/NFV network] + SOMM --- SDNAware[SDN/NFV aware network] + style NMS stroke-dasharray: 5 5 + +``` + +Figure 1: Top-view of smart operation, management and maintenance system. The diagram shows a top-level box labeled 'Smart operation, management and maintenance system' which contains a dashed box labeled 'Traditional NMS/EMS'. Below this top box, two boxes are connected: 'Non-SDN/NFV network' on the left and 'SDN/NFV aware network' on the right. The label 'M.3041(20)\_F01' is at the bottom right. + +**Figure 1 – Top-view of smart operation, management and maintenance system** + +## 8.2 Layered functional architecture of SOMM + +The layered functional architecture of SOMM has extended the traditional logical layered architecture (LLA) of [ITU-T M.3010] by introducing new layers and OSFs to support a wider variety of telecommunication management activities for the integrated network, and to support rapid deployment of complicated OSs based on open services and convergent data. + +Figures 2 describes the layered functional architecture of SOMM, including scenario application layer, management service layer, data convergence and management layer and infrastructure management layer. + +![Figure 2: Layered functional architecture of SOMM. The diagram shows four stacked layers, each with an associated OSF (Open Service Function) represented by a circle with three overlapping circles. From top to bottom: 'Scenario application layer' with 'SA-OSF', 'Management service layer' with 'MS-OSF', 'Data convergence and management layer' with 'DM-OSF', and 'Infrastructure management layer' with 'IM-OSF'. Each OSF has an 'x' input on the right and a 'q' output on the bottom. The label 'M.3041(20)_F02' is at the bottom right.](853f59c89931a666c07903b31d098277_img.jpg) + +``` + +graph TD + subgraph Scenario [Scenario application layer] + SA[SA-OSF] + end + subgraph Management [Management service layer] + MS[MS-OSF] + end + subgraph Data [Data convergence and management layer] + DM[DM-OSF] + end + subgraph Infrastructure [Infrastructure management layer] + IM[IM-OSF] + end + SA -- q --> MS + MS -- q --> DM + DM -- q --> IM + SA --- X1[x] + MS --- X2[x] + DM --- X3[x] + +``` + +Figure 2: Layered functional architecture of SOMM. The diagram shows four stacked layers, each with an associated OSF (Open Service Function) represented by a circle with three overlapping circles. From top to bottom: 'Scenario application layer' with 'SA-OSF', 'Management service layer' with 'MS-OSF', 'Data convergence and management layer' with 'DM-OSF', and 'Infrastructure management layer' with 'IM-OSF'. Each OSF has an 'x' input on the right and a 'q' output on the bottom. The label 'M.3041(20)\_F02' is at the bottom right. + +**Figure 2 – Layered functional architecture of SOMM** + +**Scenario application layer:** This layer mainly includes the typical and emerging operation maintenance scenarios summarized in clause 7 which includes smart operation, smart management, smart maintenance, smart comprehensive analysis and traditional business-level OAM. The OS of this layer accesses information and functionality in the other layers. + +**Management service layer:** This layer incorporates the capacity of fundamental functions of OSs which can be packaged as different services to be opened to scenario application layer. The management services of this layer include traditional telecommunication service management, network management and element management functions, as well as the orchestration functions, etc. + +**Data convergence and management layer:** This layer provides data-driven ability for SOMM and converges mass of data from different OSs to unified data model, supporting data sharing, data mining, data correlation, machine learning and other usage intents. Data in this layer can be opened to support management service layer and scenario application layer. + +**Infrastructure management layer:** This layer is the operational foundations for SOMM. The infrastructure could possibly be based on physical servers or cloud, and platform as a service (PaaS) components providing IT services can also be included to support rapid deployment of OSs in SOMM. + +Each layer described above may consist of different operations systems functions (OSFs) as outlined in [ITU-T M.3010], and will be explained further in clause 8.3. In order to distinguish the layers, a different type of OSF is used for each one as follows: + +- 1) OSF in the scenario application layer is SA-OSF; +- 2) OSF in the management service layer is MS-OSF; +- 3) OSF in the data convergence and management layer is DM-OSF; +- 4) OSF in the infrastructure management layer is IM-OSF; + +In Annex A, the relationship between the LLAs of [ITU-T M.3010] and this Recommendation is described in detail for comparison. + +The q and x reference points defined in [ITU-T M.3010] also exist in SOMM. + +## **8.3 Sub-functions in layered functional architecture of SOMM** + +Figure 3 outlines the sub-functions in the layered functional architecture of SOMM. + +![Diagram of the layered functional architecture of SOMM, showing four layers: Scenario application layer, Management service layer, Data convergence and management layer, and Infrastructure management layer.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the layered functional architecture of SOMM, consisting of four layers: + +- Scenario application layer**: Contains five management function sets: Smart operation, Smart management, Smart maintenance, Smart comprehensive analysis, and Traditional B-OSFs. +- Management service layer**: Divided into two sub-layers: + - Service opening sub-layer**: Contains Service directory and Service management. + - Service providing sub-layer**: Contains SDN/NFV aware orchestration and Traditional S-OSFs, N-OSFs and E-OSFs. +- Data convergence and management layer**: Divided into two sub-layers: + - Data management sub-layer**: Contains Data lifecycle management and Data security management. + - Data convergence sub-layer**: Contains Data acquisition, Data processing, Data storage, and Traditional N-OSFs and E-OSFs. +- Infrastructure management layer**: Contains Infrastructure maintenance and Infrastructure monitoring. + +Diagram of the layered functional architecture of SOMM, showing four layers: Scenario application layer, Management service layer, Data convergence and management layer, and Infrastructure management layer. + +M.3041(20)\_F03 + +**Figure 3 – Sub-functions in layered functional architecture of SOMM** + +### 8.3.1 Scenario application layer + +The scenario application layer consists of five management function sets as follows, all supported by data and services from lower layers. + +- 1) **Smart operation** – This management function set mainly includes a group of OSFs which are used to support application of scenarios such as customer service support scenarios and end-to-end service provision and operation scenarios. The related scenarios are described in clause 7.1. +- 2) **Smart management** – This management function set mainly includes a group of OSFs which are used to support application of scenarios such as synergy management of multi-tech networks scenarios and smart network monitoring scenarios. The related scenarios are described in clause 7.2. +- 3) **Smart maintenance** – This management function set mainly includes a group of OSFs which are used to support efficient and precise maintenance activities with advanced technology. The related scenarios are described in clause 7.3. +- 4) **Smart comprehensive analysis** – This management function set mainly includes the OSFs which are used to support kinds of simulation analysis and big data analysis scenarios. The related scenarios are described in clause 7.4. +- 5) **Traditional B-OSFs** – This management function set mainly includes a group of traditional business management functions which are aimed at supporting the decision-making process for the optimal investment and use of new telecommunications resources, supporting management of OAM related budget, supporting the supply and demand of OAM related manpower and maintaining aggregate data about the total enterprise [ITU-T M.3010]. The related scenarios are described in clause 7.5. + +### 8.3.2 Management service layer + +Management service layer includes two sub-layers. + +#### **8.3.2.1 Service opening sub-layer** + +Service opening sub-layer includes the following management function sets: + +- 1) Service directory – This management function set is required to establish and maintain a directory for all the abilities of services opened to the upper scenario application layer's OSs. +- 2) Service management – This management function set is required to monitor the performance and quality of the open services established in this layer, as well as troubleshooting and lifecycle management for these services. + +#### **8.3.2.2 Service providing sub-layer** + +All the services in the service directory of service opening sub-layer are provided by this layer. The service providing sub-layer includes the following management function sets: + +- 1) SDN/NFV aware orchestration – This management function set is aimed at arranging and coordinating networks' resources to satisfy customers' demands for both physical and virtual infrastructures. It usually includes service orchestration and resource orchestration. +- 2) Traditional S-OSFs, N-OSFs and E-OSFs – In this management function set, there are traditional OSFs includes S-OSFs, N-OSFs and E-OSFs of [ITU-T M.3010] which are used to provide TMN management functions for traditional network, such as fault, configuration, accounting, performance, and security (FCAPS) management. + +In both SDN/NFV aware orchestration and traditional S-OSFs, N-OSFs and E-OSFs management function sets, AI assistance in the form of advanced mathematical analysis and prediction in machine learning will be used to meet management needs, such as correlation analysis of alarming, automatic troubleshooting, and automatic fulfilment of service, etc. + +### **8.3.3 Data convergence and management layer** + +Data convergence and management layer includes two sub-layers. + +#### **8.3.3.1 Data management sub-layer** + +Data management sub-layer includes the following management function sets: + +- 1) Data lifecycle management – This management function set is aimed at managing the quality and model of data within a whole range of data processing phases. +- 2) Data security management – This management function set provides the ability for the authorization, authentication and audit management of data access, display and export. The encryption function for data transmission is also included. + +#### **8.3.3.2 Data convergence sub-layer** + +Data convergence sub-layer includes the following management function sets: + +- 1) Data acquisition – This management function set provides various methods for collecting and adapting various data from all kind of network, terminals and infrastructure. +- 2) Data processing – This management function set provides different ways to handle the data, including data cleaning and tagging. +- 3) Data storage – This management function set provides the ability to save massive data in a distributed way in the cloud. Data copies are stored in multiple nodes, which can avoid data unavailability due to single machine failure or storage medium damage. +- 4) Traditional N-OSFs and E-OSFs – This management function set in the data convergence sub-layer contains only the data-related N-OSF and E-OSFs defined in [ITU-T M.3010], such as the ability to communicate with network elements or lower OSs. + +### 8.3.4 Infrastructure management layer + +Infrastructure management layer is aimed at managing the common infrastructure of OSs. These infrastructures are usually the cloud-based distributed infrastructures, they are physical foundations of SOMM. This management layer includes the following management function sets: + +- 1) Smart infrastructure maintenance – This management function set provides both on-site and remote maintenance abilities for the infrastructure of OSs. New technologies such as IoT, AI and smart wearable technology can help to make the maintenance smarter. +- 2) Infrastructure monitoring – This management function set provides the ability to gather the alarm, performance, capacity and usage data of infrastructures continuously in a centralized way. + +# 9 Development considerations of SOMM + +With the introduction of development operations (DevOps) technologies and methods, the construction and continuous updates of SOMM systems could be more agile. + +Since the framework of SOMM is a kind of open and loose-coupled structure, the OSs of each management function set in each layer of SOMM can be designed, developed, tested in the development environment. At this stage, the software of OS is in the development state. When the software of OS is released to the operation environment, it will be in the operation state. + +The DevOps mode of SOMM is shown in Figure 4. + +![Diagram illustrating the DevOps mode of SOMM. It shows two environments: 'Development environment' and 'Operation environment'. The 'Development environment' contains a stack of boxes labeled 'OS in development state'. The 'Operation environment' contains a stack of boxes labeled 'OS in operation state'. An arrow labeled 'Release' points from the 'OS in development state' to the 'OS in operation state'. A return arrow labeled 'Design' points from the 'OS in operation state' back to the 'OS in development state'. The diagram is labeled M.3041(20)_F04.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +``` +graph LR; subgraph Development_environment [Development environment]; OS_dev[OS in development state]; end; subgraph Operation_environment [Operation environment]; OS_op[OS in operation state]; end; OS_dev -- Release --> OS_op; OS_op -- Design --> OS_dev; +``` + +Diagram illustrating the DevOps mode of SOMM. It shows two environments: 'Development environment' and 'Operation environment'. The 'Development environment' contains a stack of boxes labeled 'OS in development state'. The 'Operation environment' contains a stack of boxes labeled 'OS in operation state'. An arrow labeled 'Release' points from the 'OS in development state' to the 'OS in operation state'. A return arrow labeled 'Design' points from the 'OS in operation state' back to the 'OS in development state'. The diagram is labeled M.3041(20)\_F04. + +**Figure 4 – DevOps mode of SOMM** + +# Annex A + +## Relationship between the LLAs of [ITU-T M.3010] and this Recommendation + +(This annex forms an integral part of this Recommendation.) + +[ITU-T M.3010] defines the logical layered architecture (LLA) which organizes management functions into groupings called "logical layers", and each logical layer reflects particular aspects of management arranged by different levels of abstraction. The operations systems functions (OSFs) in each logical layer are known as B-OSF, S-OSF, N-OSF and E-OSF respectively as shown in Figure A.1. + +![Diagram illustrating the relationship between the Logical layered architecture (LLA) of ITU-T M.3010 and the Layered functional architecture of SOMM.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +The diagram compares two architectural models. On the left, the 'Logical layered architecture (LLA) of ITU-T M.3010' consists of four layers: Business management layer (B-OSF), Service management layer (S-OSF), Network management layer (N-OSF), and Element management layer (E-OSF). On the right, the 'Layered functional architecture of SOMM' consists of four layers: Scenario application layer (SA-OSF), Management service layer (MS-OSF), Data convergence and management layer (DM-OSF), and Infrastructure management layer (IM-OSF). Vertical 'q' connections link OSFs within each column. Horizontal 'x' connections link OSFs within each row. Dashed arrows show mapping: B-OSF to SA-OSF; S-OSF to MS-OSF; N-OSF to both DM-OSF and MS-OSF; E-OSF to both DM-OSF and MS-OSF. + +Diagram illustrating the relationship between the Logical layered architecture (LLA) of ITU-T M.3010 and the Layered functional architecture of SOMM. + +Figure A.1 – Relationship between the LLAs of [ITU-T M.3010] and this Recommendation + +The relationship with LLA of [ITU-T M.3010] is illustrated in three aspects: + +- 1) The functional architecture of SOMM is also within the scope of TMN and it can be treated as a re-organization of OSFs in LLA as well as extensions of LLA of [ITU-T M.3010] because it also introduced new functions when compared with [ITU-T M.3010]. +- 2) The functional architecture of SOMM has a tight mapping relationship with the LLA of [ITU-T M.3010], as shown in Figure A.1. The mapping relationships are described as follows: + - E-OSFs in element management layer are mapped to DM-OSFs in data convergence and management layer and MS-OSFs in the management service layer; + - N-OSFs in the network management layer are mapped to DM-OSFs in the data convergence and management layer and MS-OSFs in the management service layer; + - S-OSFs in the service management layer are mapped to MS-OSFs in the management service layer; + +- B-OSFs in the business management layer is mapped to SA-OSFs in the scenario application layer; + - The functions in SOMM has a wider scope than in [ITU-T M.3010], The OSFs in SOMM includes but are not limited to those in the LLA of [ITU-T M.3010], because the framework of SOMM should support both traditional scenarios and new scenarios and it should also support both non-SDN/NFV networks and SDN/NFV aware networks. +- 3) In the functional architecture of SOMM, the q reference points and x reference points are also used to describe intra-communication between OSFs within one TMN and inter-communication between different TMNs respectively. + +Data in SOMM are centralized and managed in a converged way, which includes both network element data and network data. In TMN, these data are usually collected and generated by EMS and NMS. Besides, all other manage-related data are within the scope of SOMM and should be managed in the data convergence and management layer. + +It should be noted that "service" in SOMM refers to "management service" which is related to the opened network capacities opened. It should be clearly distinguished from "customer service". + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94b4bdd8861c5e9d34a56dcf1c9dad149639a40c --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5b9eb70322bc60cc13b83d14f24ec6224a6bb20c4a6d2f606703e0fd3d9225a +size 138107 diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b07dd41ecdb7a8dfeaa5977235690b1ae66fd093 --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6297fdd774be565eb526e9cc275fc30df6fa796633631b0dd636e30a3e627a5e +size 138563 diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25f8fbfaef317942ed3102c74b40a7d42f80608b --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83cab7dcabfe939b223d97242d8523e461968d21f7c5432693c30a64f2d95521 +size 7050 diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a15a51d63ff0e193764f173ff674ca455e0243e --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b294f0b84d402156f90a4735629acf0e1dc0a60646737507022e3c0b9ed6026 +size 226574 diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a02ed8d9c6e9064c430bdf2c0d1c47b78e4e0a2 --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7c92e17a3cd784154674d378db0ad32bfd2fb6234839c77a5c7a45d8cf35b79 +size 112060 diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25075a4fca6569b91a0775ebd1a3db76463fb86f --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca98673460f8add01f6d0c85d852f254588f915c6756f4e74eea9dc1d7d24258 +size 91005 diff --git a/marked/M/T-REC-M.3043-202510-I_PDF-E/fa17ecf8c66b02ac92d9e609ae5599e4_img.jpg b/marked/M/T-REC-M.3043-202510-I_PDF-E/fa17ecf8c66b02ac92d9e609ae5599e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b02a4eb384a480405f5859af81480b0d8369435 --- /dev/null +++ b/marked/M/T-REC-M.3043-202510-I_PDF-E/fa17ecf8c66b02ac92d9e609ae5599e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da64f4a0277035d081c95a5f2ccb598961a15a7c7dae190912c708d84f52e4f6 +size 18290 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ef650f86e179b0483b023ebc1d3a3d5dab1a00d --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f63abbed341943a047534f720f07a8e5578e09db637c3848707473d29a433b8 +size 52838 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/0681cad811f269a7c9592f8e3d824b06_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/0681cad811f269a7c9592f8e3d824b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1872440d2c03ac06ee551daff5493e1302ecee23 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/0681cad811f269a7c9592f8e3d824b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f9e984e15c67002c26806076af043d880ff7c25828d9c8a0fb3d00bb1d7857f +size 51497 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a23d1b6be6d1347826bbf6e86161c1ea1047a15 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/0897c77315bfe37a098f6b4ea39570d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23990b7eb3da6914de240e64d70ef2649e1f99bdc49a45095cb902fa789eb6cd +size 51707 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/11bbed8294a393058c901641b8f50b5c_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/11bbed8294a393058c901641b8f50b5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51755acae1b183116c986d587a46f3a2e575ab75 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/11bbed8294a393058c901641b8f50b5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd855659bf2dcdb6d3f1c06f6d087388f73ab6bfa84ff04767355cf4490f4ee9 +size 29132 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/16d5f9c016e78737423c11d4fba9ae25_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/16d5f9c016e78737423c11d4fba9ae25_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcbcfd508508c0c0c67bcf72e27d0baf4fd02922 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/16d5f9c016e78737423c11d4fba9ae25_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0624c981974ebd3bff94dc4cebbcfaee7e2b9e0fdb4271590ce32aeef04822b3 +size 31983 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6bd630377cddf18e3371444aad217e71d40febf --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f71d5b78f230489c540c02ad9eb9c39651f4ffc381743615aa2f84e55a06deb +size 50128 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76cd1c518e81f735faf12428cfaa5c6b7d73c7a0 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a4b0eebc1a428a3a0ec62623f75b990587dbc9bf59e191ee01a8206a084d156 +size 25986 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1ca688982d625c3b8a8e382b675de466_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1ca688982d625c3b8a8e382b675de466_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65dc1f49d7866a58856854a18454a0fc1c5bc734 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1ca688982d625c3b8a8e382b675de466_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a937deffeee1c2a83c38cbf66e8457576ef1b86e11269543e11e7453ef0ab60e +size 44016 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1db1724d23ebada3bc4c8fc665159897_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1db1724d23ebada3bc4c8fc665159897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1ad7e62614c6da54ddbd38e4e74bc97155d5c79 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1db1724d23ebada3bc4c8fc665159897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d27b872b859cac09da58f4b7b04b22df5057f750279349360a2de6b52c2665b8 +size 49473 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1e95fc0be1c9782d078a26fb32facddd_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1e95fc0be1c9782d078a26fb32facddd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14d276ae08d9ce6e1a96c4051974226dda1b7199 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/1e95fc0be1c9782d078a26fb32facddd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2ec6408fa88403c96c524a1b80015ff0faaca8880fdec652f5cdc52acb34cb5 +size 44913 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/20e1585db1a707a774877194c689de82_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/20e1585db1a707a774877194c689de82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9ed9558af89f4861b8ad4c75c877c71af72f17b --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/20e1585db1a707a774877194c689de82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37a50681016279b7c41563365c1346e7798c876cf9d81ab7c58965313b3d67f3 +size 40139 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9780d572a826a3d632ccd9cb4cacb9b5ae4c230 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa92345ee91779bd3ff2e21b434feb9dcd641d4ef91df15accde79d5bccce4cc +size 44303 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/221895a377f82a586cef87812415c431_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/221895a377f82a586cef87812415c431_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaa12dc37b059831e01461d386d6256bf208a9bb --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/221895a377f82a586cef87812415c431_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0a695259a5ce764cbd43f58d771cd35aca5ef3dd66d9205a0b2d21e5cba7429 +size 66367 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2957154f4dc666a6cafb7b4d2d882910_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2957154f4dc666a6cafb7b4d2d882910_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..562fdb4d2dbad914c23d38053a6cbec00f5aa2e5 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2957154f4dc666a6cafb7b4d2d882910_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:488527f2f5b8335f04284e94987402a56af66c05b7b02545d12982c4a81863ff +size 51854 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a94ea47222e4ac52ccec50edae879ea92c046f75 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bffbee9f149b29409ee15fbdf98c9bfd9568bb55395922f36590dc11bff2ca9c +size 52335 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2c4c90917583576b27072e2083d75906_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2c4c90917583576b27072e2083d75906_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fbdfe4b21f77af3cb13b9aeabfc09087b3e353c --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2c4c90917583576b27072e2083d75906_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7907a92654a1f5314397c18e9318d6545f12671504fe3d04103e396b9ff98081 +size 53376 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2cf1f70c3a387c43e15192a30d212546_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2cf1f70c3a387c43e15192a30d212546_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97979c4e7963e96af7903f1083a5e4f2e73a17b2 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/2cf1f70c3a387c43e15192a30d212546_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4c7ab1f07e940ab199546224eea1e5d2ad59bd3fed31cd33d70816d77bbefc0 +size 25932 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0569e7a5d01aec069cc7138f017f0ad7da5d17e3 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b05f8535d6cda0ae5ac6c98d417ec1e5e34107448c7b3ab316bbe395e209ba +size 42020 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/3c30ec86a05e7fe7e7c6246a1863ad08_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/3c30ec86a05e7fe7e7c6246a1863ad08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..972617324928ceb199e9385c574531c4228ae980 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/3c30ec86a05e7fe7e7c6246a1863ad08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24e15de7c09d59fb3b3166682db55696dc7d4f6ab927e7468674c3b2c4a171dd +size 44117 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/3d6329ca9f16b262b91833b08e4dfefa_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/3d6329ca9f16b262b91833b08e4dfefa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b044ad9b919944e4bd348a03332bf09e192397f --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/3d6329ca9f16b262b91833b08e4dfefa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d1c434a6e21e218b21b04220cba03092e2634a38d599c789837efb89003878f +size 41738 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/450946c7ffef8b7fce38c312987a46e4_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/450946c7ffef8b7fce38c312987a46e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3d0fc5d5c3060a8da0b1330e7329eb02fd02de0 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/450946c7ffef8b7fce38c312987a46e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:704471da2d3dfc1a93483abf73e15af9a6671e8c6ef2accf54ad104672a6ccb0 +size 31218 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/4661ff3f0d91c8e2b0a4270557626055_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/4661ff3f0d91c8e2b0a4270557626055_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e9a48d121b900969de036a97eae19812806aac5 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/4661ff3f0d91c8e2b0a4270557626055_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5e48a9e01366d4f7042111bed16115eee99a59962bd39eb80d1ae8d1d943337 +size 45212 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66bf676d787c736e23aa86046811d538065f7427 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5742e0cf2857ae6d6b0aa2bc55ea6643723936b8825de00e8af1ce1618595b02 +size 29518 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/55af54cd78b1a8398875e43ca2bf4c69_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/55af54cd78b1a8398875e43ca2bf4c69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3d7ef7e3af9caff8e764838e03da86a589962a5 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/55af54cd78b1a8398875e43ca2bf4c69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee16ad312acdeb5aec64d9f42a134ef7582655e57af97e1b6b34e1457c8e0701 +size 26913 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/5661815043254c37a4e3e4833f51e727_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/5661815043254c37a4e3e4833f51e727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d38a8f5d27e6f82769ea124eec11206e1f8c4a6 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/5661815043254c37a4e3e4833f51e727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a4598dfdbbaac493fbd00a149b5004b0c4299f70a6e1b2f1da06406a76d50eb +size 60602 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f942bb23d0d8c527bdbf50e5197e3b6fe1561237 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1697f61b7f8878b2c3d8111e656d53a5d3564e3fa0deccfcb5b26f947ba35396 +size 20842 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/6308d51a4454ddd3509eba3e3b6a11a5_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/6308d51a4454ddd3509eba3e3b6a11a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b30156554ad0b40b9657fbc3005ee9414a6dd8a8 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/6308d51a4454ddd3509eba3e3b6a11a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fae1208cd3e8bb09d352d009f4081f9b622d3d7bf12fe5f5c2de23ab1d040ac8 +size 42367 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/66bf96eec8f739d5e7c9957a178e34e2_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/66bf96eec8f739d5e7c9957a178e34e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57618882aeb12056939ec892bd81f4a344973ccd --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/66bf96eec8f739d5e7c9957a178e34e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a826ae774709d73da17262a54489583b848466d68ebd67fc7603bdab78097952 +size 48720 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/66d5189a924662748cac6a9b22a272e9_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/66d5189a924662748cac6a9b22a272e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc14cd06ec20fbfac5172f1f1886901343ea9331 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/66d5189a924662748cac6a9b22a272e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1477aec2cb22b16fd0c5a3953d60983d7d9706c099fdacc085a1a7b9f429858 +size 29890 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca3768d74595b7fbe91e1441887daf5055e6ebc3 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/67114ecf6da13c97a89aeff0d86885d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aa9bda929b2add52d441dc7145057ccdb3a0a5ab96c65b3826408277ea0c499 +size 43485 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7c19fc92dc74a74ec346d46bc39a3946_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7c19fc92dc74a74ec346d46bc39a3946_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a72d8bbd5329b514e7449d9a8f0682f3e0913d9b --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7c19fc92dc74a74ec346d46bc39a3946_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35ff9a5f09a81c0d5957a42d1fd13b8becf6072f827f10c49eb97740188623b7 +size 57002 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e231d154694b97423e35021aea661c9656e90ea6 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a655c85fece97c5f9bcc50e0068f0b4844c89751ef3f108fc66465d0f87ff530 +size 62593 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7e5f0aeb4d1adb2bbeed7cdd265a1707_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7e5f0aeb4d1adb2bbeed7cdd265a1707_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8256b2a0acbcd77a3fd3aa53036f501bf2559f4b --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7e5f0aeb4d1adb2bbeed7cdd265a1707_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b634cf4cef86b6d14a9201eca35427c9fc6a49588a7978fc879110ad20fa8702 +size 53737 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7ef82ab74729923b27507495301d73a6_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7ef82ab74729923b27507495301d73a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b6489836793ff331a406942d69bd3e91544aad9 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/7ef82ab74729923b27507495301d73a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b2234baab4d2e7d47f41fd409a919a4c2146cc81c1c4d0c4070a41f6232e77f +size 50417 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..196ff2861fb2f612ce70c6902bd673e94eda421e --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:816c33df16198c02464aad5402248be3f8be4d0872f628fc52a8bb9292208fd6 +size 28670 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5de46f6f1d55bd50feaac79d8d0cd50b124502cc --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4724af19be145bb7c68b131adbf51c97f8197a665afb269d35d0bf96a9285ec2 +size 56865 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/8b40238e5eff3457dd5ae0011536e2d9_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/8b40238e5eff3457dd5ae0011536e2d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f5fbdd25a898e3334376942da44059b58eaa3a --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/8b40238e5eff3457dd5ae0011536e2d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f210bac42b8548b1ef9d15c4c8c8687bdc3f34cd42041976b1b6f0c5777a34b +size 52685 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/8b4d7208d4d64f4017262028d2cb2403_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/8b4d7208d4d64f4017262028d2cb2403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53467987f7c77b0d1cf56727c537d29258cae158 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/8b4d7208d4d64f4017262028d2cb2403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8b059d3d80a9f0c7dace043ec3f8ec09a94aaeca69bc1f5477733927f985567 +size 35488 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26673781ea3bd9284d9c7a045a693d565a0a9ea5 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:add9ba0cf0e5a154238d03e5ecc881b050471109d528d8dc0cf8c4c1cee038d6 +size 35723 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/a74b99731e3d365b0c46960997058734_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/a74b99731e3d365b0c46960997058734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52f2140df292cde25bf1626659ab5e3971077fb5 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/a74b99731e3d365b0c46960997058734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47ecaeb54e4b15030db8772f7a197672b23e6aa318d6ec66e0a6ec218711c3a0 +size 34336 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/a7c4533d526366db3c7f9d57de31c314_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/a7c4533d526366db3c7f9d57de31c314_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7c40d903f8f5573aba7ceb44c3bed35d3d5c545 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/a7c4533d526366db3c7f9d57de31c314_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c87e9e03ac5afd9b0fc6f2c3200401cf5b404627d90754d94cc9ef34720a6f8 +size 56771 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/aa3ef65bfc491f098a98ad92ce8d6c2c_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/aa3ef65bfc491f098a98ad92ce8d6c2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e52f7ebcb3f52b51d5e233fccfe7fe595f64cd0 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/aa3ef65bfc491f098a98ad92ce8d6c2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00a03c8c1b1f864ab0e6c0329ed27a6039c0d14fe96d6f3e1bbc352f177529d7 +size 57335 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/afadddeb3fc15146e0758d5212f4fbce_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/afadddeb3fc15146e0758d5212f4fbce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..796b91308af0f6b2546ff233d99ecc7ef9fa0d35 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/afadddeb3fc15146e0758d5212f4fbce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9460b38d5602bed575dc422ad6a7d13da4583f82fbe611c7ed899ffb8698129c +size 55490 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/b5b908b453ca50ed3b4cca88aef080fa_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/b5b908b453ca50ed3b4cca88aef080fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af635e7d4eb35b20bba42a8ca06fe0299ec40f8d --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/b5b908b453ca50ed3b4cca88aef080fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc78e9156c98595a4c9faa5d30625f1a2ab957ae797722da89646a33285f177c +size 55553 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/b61f69e2e373887d5d11df288c845f73_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/b61f69e2e373887d5d11df288c845f73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85a73cf8bd6180b8f805d4091e310d1286719a15 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/b61f69e2e373887d5d11df288c845f73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:530c7b7f1bd07f34d407523ad3dabd8f85b01ea7b7a91884f90537bc1a41e273 +size 53859 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/beefc2239bc009e7b97963ac4f166db1_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/beefc2239bc009e7b97963ac4f166db1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0395e078f6d8a5562d82cc8bbc43707d9373cb8 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/beefc2239bc009e7b97963ac4f166db1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c9842be14744e0069fa51a0771e8965957c9842e6bb6cd93f08b5adb2363b2e +size 52954 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80862d60baf4c23c5ecd6c91a5a20aeccfbe743 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9852159c3f3d9998e230453dee2ba4205dbcabb1b7d534aba4aca82ee606201f +size 66943 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d303e7cb6006836a0f10a9c3bb489cc6f35ca5e --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36cf55351d5d44d4a834e8a8da5693d23362cd7acfd7aab16d787fbcc2f4bd5b +size 45347 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/cad41f28af38bf1707891b7ab8746331_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/cad41f28af38bf1707891b7ab8746331_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2024849cc124ef25328bfbf429049abdca775fa --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/cad41f28af38bf1707891b7ab8746331_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f9e01f4f0353eb6f249a47e98e0452ec0649b07288232c66dc090a7d91579d5 +size 31993 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c6150b8c5a7ef602f63426a98cae44dc8a281ee --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26e653fa36da96c0f6e197a26db8c7d7df3742ef90ff24f3f34c5e967bb52f5c +size 79953 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d24991add1927bb17af2ee171454a31f_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d24991add1927bb17af2ee171454a31f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29a45d174f71b1ae182ce235f316a90e386d40d0 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d24991add1927bb17af2ee171454a31f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e21fa3421c0251e83a8b49d84f1ef56a52eea8b31aabd77d17cea0b00777b9b +size 54068 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d2f4940093768001d427ab18d4e40cf1_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d2f4940093768001d427ab18d4e40cf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db3eca577dbd34e8289f3cbdd37a8e4726ed9cb3 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d2f4940093768001d427ab18d4e40cf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d7afecf084cdc377761ca50f1079c77aad9fa3accc122d0073004d5ce2972c0 +size 38319 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d4924fd23ef11c8a89227c9da6d428c0_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d4924fd23ef11c8a89227c9da6d428c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a32fd542668791ebcdfa2f30f54e092580ca520 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/d4924fd23ef11c8a89227c9da6d428c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:980bc7f22a33e358b117abf13808af6eb94ae1c3265963ab3347d2867932a1e2 +size 30434 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3775c6eb88606c82021aa72c9ae849261dcb70c8 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e669187ff7c974d0047e4dbfa7e75a99aae93a8cbd627e1a6c282b8d462853a +size 58632 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/dffc963834960a94cebd7918705d96b4_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/dffc963834960a94cebd7918705d96b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1306e628423a8ffc209a375e954810e724a817e --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/dffc963834960a94cebd7918705d96b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30d22d6033f75f1c5da29d3ccb4ab493e49704607d2ab889ee7347c2e9a9f913 +size 45895 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df5d1ae2305a5b8ea94ab3d6482d09dd2b30f1cd --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12b695f69d5dd767410ee9d29467ea3520f2392542925fc09a3f62dc12b08fc6 +size 34922 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/f1305079e63f62c87f7d18a6867d7d94_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/f1305079e63f62c87f7d18a6867d7d94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ebee62ff8430297cac9971125973dec4492ca1 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/f1305079e63f62c87f7d18a6867d7d94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f5243f1d69983ce71f56815ed4c17b4e58e76c6f3cdd2296a8fb73a81c26c5c +size 33880 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/f2d3777af38ac0d2c0e63b42ac25c924_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/f2d3777af38ac0d2c0e63b42ac25c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63d0682ee54806d5659f55c17747e29436cfd041 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/f2d3777af38ac0d2c0e63b42ac25c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e56446995ed272719f1a7ed13af3f583637ed4b9e4e1d0a704eb2101db505bc +size 47520 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/fae02fa1dac97fc5f19a7b85d20df290_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/fae02fa1dac97fc5f19a7b85d20df290_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d54e6b5d604c626728345f016c123e9ce7dddc2b --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/fae02fa1dac97fc5f19a7b85d20df290_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05c6d49003e4ecd041d582895aefb3cf6a423a66114c44687330f7e1cd7195cc +size 43943 diff --git a/marked/M/T-REC-M.3050.2-200703-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aea57ba799156c2aa890af152520b7b74225338 --- /dev/null +++ b/marked/M/T-REC-M.3050.2-200703-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a84e034bf6e3fdcd67f99ea3eadd4f3b039d842a3a8b757915e20e07691d941 +size 54890 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f94ec988191e7acb919c8056dd52c3ef64791067 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c53b72541b189c4a910818bf0273c0ee9739a3172e67821570c2b87cd47fa601 +size 78079 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aeb1fb6cdf66c115b0f079c2a8713e787cef935 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:311886db4bc5347af57829398bfc98b51f7b76c22116e2cce3b8947fbdc58699 +size 122647 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14aaeda1dcb41cdaf80c9c87ce99d222130d1b31 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9616179defbabbc037a72e312494e874a486f754d41a672f8f3fe1ee849a4842 +size 232803 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba5baff68e7eeab6116adb4e523a33b09db6e706 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/12c19090355e19922e23044633b9d1ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd87e504b0d79012e19fb20a48d991de0a3dd5329fa77c4d3328763069a8fe66 +size 110643 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97526f4a850afca8dab2f93b77406c3c5ddfc085 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d239fa4c8e9a9237a51d004b9e823d0aa44045860e38df86a1505111a43c1349 +size 4571 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9a971823fa2e019dadfe00f72d72100afb61e5a --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4437af22a9ff1269efd602356b7ec156c05fe388605eca5d69da609cc5eee2e2 +size 219988 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/41245ac07db266bea228735b9e8c8b73_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/41245ac07db266bea228735b9e8c8b73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08702fb4a3c054af75fa68d3c739f28d5cb514f6 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/41245ac07db266bea228735b9e8c8b73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc683c69c46b7ea18af1ba90f8908f39a699749b63e5feba42307c7ee2a13c8 +size 4756 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/57b6be8f71ad3ed20e986bff929f479d_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/57b6be8f71ad3ed20e986bff929f479d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09616e4d508462e4bd93d4afee578c93fbed585f --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/57b6be8f71ad3ed20e986bff929f479d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1054564bcc0cbfab5ad51683797b573b271e88c0ba6fd859f42d3038d2d90b58 +size 4765 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b247954feb86c764159d04716f27119744b9ce34 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e41a1f6f05b760c816dd23547f82dec36bf0efaa0fc62f79e608c5bf44bc807 +size 171941 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51b889951ce3e2c222dbc3549c1b57dc7799bcd0 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa3fdb228749f50ee9ae4da1d78dc287fdc9cc03e7cc84df0280c1b14b121f4b +size 87466 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00509b8b13c751a65c7a8c8caa82d0899813273f --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e08a99efaf1b9ba6d977ba2b5bd34c32b398305ccbce174f7e6caed566cdb57 +size 143104 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbdafcf281a4a8f212a7becb20ad07326d688fce --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f06fc022d5a82ac4db337089b1b4bc452bc33831ac7c7a8670dd7f54e05db2fa +size 79758 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a6ca6d6ea86731a35c834f22de50665ef2f7e16 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45fa2e6d46f37ecc4f48d8cb676e976792d6d4ef50247883f2d64ab87a2862df +size 53863 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f86f679b1f7a778dfc5a1e336c0200d435ef447b --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c64c554a493d3fb9f3db75807d172a02ec4626694c4a6c8a5001501ac27f7f0 +size 192126 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20c71d59bf2c37de45839e5ff53cbd76c3009321 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d22a9a8cea551f8e28f6ce869f897979f6e4cb9ffbed804109c1928482bb40d9 +size 294723 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/7b1cea8c45c49887a750926f2135fa84_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/7b1cea8c45c49887a750926f2135fa84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7775c0c4a9da656d47a84dac758e4b16b3e51104 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/7b1cea8c45c49887a750926f2135fa84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5775ce611da2713200b39e8c84bc83d5bd3b38c7a23b00b228784747afb84529 +size 4743 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d8d9f74d20a62e2c7b1a13c3473163dcecd5a88 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ded1ad219bd61231ed946f5841f248d5a1c8edb8f9d802ef44e9f63f857be4e2 +size 138323 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac7162a3488b251aeb2bb89c3becf193111140b1 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c7ee33497ddf80972f95a8c981468e811fc765fb76d73b60467dc5c711980b +size 293720 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b3badc333e476f50a948bb4e0617f1a3e1a470 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c36d38bd2662581807f1c970687d4d063c9a3fba65064c775126f16071d606e +size 297317 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27aef2bbd941b5c1ca9b5a5a23b6f0fa9bf25f86 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:767e62cb6ce6091b009d47ebcfe6dfbc86eb68c09dd953dcd39d6634b5335dbe +size 257344 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64be81c94cdf3f172f8f8b0f9eece82ddf1842f8 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9b766dc488f6686def69214dfe99ad8aa8b0fb2f12f5824fe57e98054143268 +size 72907 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f378cb614c4ce7fe4a12b4d65eae8959722bf24c --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e70c31190d6964f125fb17f53efcc192fa4238be9740b30a042b87f55ecd6e14 +size 32239 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..355dcb90653e57171ca7ca8041ea769acfa752ed --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc96f9222595a6ce0886aa7a80f94baee7e13153f2fad7b5f0b60ca4db5fb242 +size 91715 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a1693e7eaee2c8f6c8a16915aabe51584e5eef9 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b275c53a958166728218dbfb909ee83122a5bb568dbb02b23d7e4fb4b53cfc0c +size 109852 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aeb2e769b57e2813f941f238e9605a983525adc9 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed95619e53cd62a276b22b4be161d22dfd05ae6117c0fac25324ae216e5d5f78 +size 163776 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd1b4a0a52c2bfbf62b3701b906d2f6b1d0eb592 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5180eb10e75679234f201b9ba3ada03e534a797053676befb4aa9c752d97d0e +size 112687 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38d1673c7170e89e1c038fbd500958e77247918c --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd83e417f6eb77483667ffe696616460e8035c6f98195878271288aeeff73e0e +size 282377 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80f29cea5e1e5ca24c53ace1c554066b33e6b41d --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50ce939f0d7e27bb85bcebc3d5d3c58cdc593abc09888e0b60ac4dec4163380c +size 198568 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11661980635f074a8974488fa54ddd07d777a794 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30505e2e35ad8a6502dafd6287fca17fd2509c8d966493b52f071b3f9482a6e3 +size 219333 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13df8a4c1a5993118f45436721e1aa045dc7fdaa --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf42b86f6462dd6ce5826deeac13c620c71d69970e99759e8358ef2d877c96e6 +size 156514 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0d80d293dcdb42afb0f60838596ece34a86aa25 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72a0cc62e123211046b49665da7caa950683808265dc4da322c8a423dab57048 +size 257030 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d16327195379b3dc77846aff761217d681703c4a --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad30abaaae983f640451071925cb8b1bd49a52fd9b79ac3786d61c584717d3f0 +size 286965 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35e5b63c665a63e287078cf8b939c24fad2a7e2c --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7f5a2067e407469e996f3c14e4e8d0641b9924a41b1561c879cc4332b2ed8fe +size 169572 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bf5e687509692e554d25390b6357e405f1401a --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6925218db8df58ced2b846f73f976810c3edc3f36e18574f2bfc595fd9a9bae9 +size 184601 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f7bc9b0327ed4589a3faf9a7b3c92712_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f7bc9b0327ed4589a3faf9a7b3c92712_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f327bd7407d6928bc09af9e9327c1ee566b4f118 --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f7bc9b0327ed4589a3faf9a7b3c92712_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e3f175305a80774e79d9c56eb75c121c83b8d139cfb1ddcca65762a0c3cfcef +size 4458 diff --git a/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2183f5b7f40940b81680a143ae3f122cfc4fddff --- /dev/null +++ b/marked/M/T-REC-M.3050.3-200703-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0210e9024b41a8d0e1d3726bfd534a7c1665650311722b94fb893b49324a946f +size 293075 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efc186cee28bf1626101de77dcd0fe7afa19630e --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39f0cfc5c852bc8a3364bf22ec51ade255271f2a3eb7aa3f55185db15c259f9f +size 4828 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..811c8b3654d0a8a099614f79de10f80109ccdbfb --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb6e52a0a1c9b85ceeafc858e1d9898645349725708a4a69b5b6f359b7334118 +size 43915 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a670bc774126040f1a1be96b93c7f1bf0bb1f7b4 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bccd5dda578727576cde0f442e1a28ef84ad9ac8894b5ce37fac19dc2c5cb88 +size 59608 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ac5dde27327623e12404b620071a15093de80ad --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98b45d21a6cde55d0038c1dc9816e49852e7f33ca1c429e8ae4634a8620a305f +size 119170 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af1f9b27a333aac01a3c8fa6ba18116f32602671 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0306e2148bdb6f1b908a3c997f201a142378f7fc2e4d4378b5077960857bb7b9 +size 80056 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..621138cc6a0a3ca16dc7c9a6fdd6a417bf1f45db --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f26bbb3955bd8cf65f0f7ecbb345c37552cce375a7ec68f3f783b2f93e136e0b +size 32161 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40d0100fb660e0d725eee687d822d381d95057cc --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:223398bc2d2224d09a1bc2ebd8b851866bf4bc44abfe7977cc51e4f3686787e5 +size 275056 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ec5ca0bd4940d88711b7c3b9c00e5fb4270b2b2 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69a66fbb3a3e5783b6319741f2bda90c551b91e6b3aa60bd374910433dc846e9 +size 90920 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa71cf2c058fc3698252d0f238fcc283361d6647 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b81e04264f1b8d1e427d361564b5cbdf656dcee2badd81cd3c3e39f01cf13181 +size 65101 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6606a69444360ea695b9c8df325453c84949cca6 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d678a29900324d43fd410bcd59a0f6c5644418602367192a1f9fbbe736bee467 +size 78687 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b65bad10069e80c46f06dd95bd39c0bc6eb85154 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04380e9e657aa025d179605e194febf64146fa8c7e53726d487a8e6a0c156ead +size 43950 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c080270fdeaaabc97192a9b0841015d48a715c01 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa988d4bc8e904995e499a8b4e2581f69cbb8f0239a482cf797eefde5f19d48a +size 47999 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f6c8c8dd3aa2507a329e2164b65d71334018eec --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91935f47cf1fb36b8a6821dd412cd9eeabf612c4850992fb5268737d5e03f50b +size 29047 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1586b56db2059569c69bfdd236b27edcbdce40e --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5dbd008fe660867337ac14503359245e7d7edcde4eb7f2834ffcbdb972f8ac0 +size 99324 diff --git a/marked/M/T-REC-M.3050.4-200703-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0d9181a9cd73ba7495165f45705171dfe57d379 --- /dev/null +++ b/marked/M/T-REC-M.3050.4-200703-I_PDF-E/fc0735d325f0ebd9214171975c68a888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8503a211db3505348f59d006a5375868cddb0d844919a624d58c33f6250614a1 +size 67499 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aa246dc96be02ac0ffa8096fece735deb8d6141 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b5a8a04646064c4095a088f56209ff851c946a681a6fc9ba73183c5049d6fc2 +size 171946 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c02324699a52c50f67559ee48b94fe4c0a46fe2 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:876e11569db118fab4842c15e3458eed0a0f86c0ccb2f3130c87a84856b040f2 +size 142936 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a58d5357e2522c777f543acc1a610494e76f291 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f140a8f0b6ef061cdc957413f04f8b12363e3c96338b8a5143b98f4d14c34319 +size 61457 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e82c56125b72ea5c3934d23f6ff32ea84f9a757 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f26ee1bb4f6076e567026e2198fcdb2e24cb9b4b4465ea927c831293dde3d1a +size 123183 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5568817bcc81cfa2734d6117e0035db8dd655563 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a8775c97aa1c12954d2f338a5341e9af7e2f0902c8b32657563f8bf8d25af5d +size 78662 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f32c02c4f38fc778076c6ed43296023e1addf4a6 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29d72d34ae17fe4ca90e8030aa0e956989cebfa7a8238e5a850753b652ab598d +size 18706 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68508b598ee31fa5b3e2f7046d338e4b49b1b483 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baa84f3377ab735d218a59a2b69a9106c0310c7bbaa94f139b28bbe92e533e88 +size 88136 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89687a7d48ac1332a9f93e0f6a5fc9574f126396 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42fa34082f926368d512bdc4c8312b0cb533e1b3896ca29551cdd3b254e76843 +size 79867 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..326ad0e209ef9ac0da16c780fc4d13866285ec66 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da8ea36b7ca7c818d66d7052a779d17be198e77d8c10b93a46eb4a83b18fefbf +size 113134 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8a39d95866f0123d4b8bb8bea69e73e90fad026 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19ea884692fc3cca61e7721df21caa2fff1e32a493957a1123955397a3898239 +size 80660 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..841bb7b422fcc2e357a58fb065e8c9ede26d70af --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0c6a15b82cbcd57986fadf575c530f4ae2573ddc08221429d8e169bbc43f364 +size 169977 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbc9495ea95b9c2d6192b7c765ce4ca560bd3803 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51b201c7d7138027f85d8feeea92b1b9854834da30f3acd2d1027e203482fbbf +size 61970 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03d1e73450ef90ee03043478ae3978b4b8482920 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de0e350150dc842b05959bea3647428d070ee04549b640c18a760fc79c924984 +size 35182 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6fb81702cf57909d5af764e3fab0173f161976b --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33a1318db4760d685bd3ff5e16b82b11780ce9f11597354be834cf161b70a7c0 +size 41103 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c91b24ea26eb13a91f6cebcd1400cfedefd5e131 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36c80caf89adaed4c494f93743c19d6ba8f3d003341263120727d4f380dc739b +size 32787 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aa02282cddfe67bc630ec9d57a83d792d89aacf --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c73c43083be1589333413706032c63dfce766e94dee7a4c78d4aff880e77276e +size 19079 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd45935e252c2e0fc526059c87a5f74491c3bdec --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b12c5a57707cb3d0fe029e0f3a739524a51d0a048e98b36b2ce9a1eb4831e7fa +size 74768 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0818fbdc3203b3faa23924714a90989534b9c78c --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:148ec6c80abdbe4c0202f8989af00352946cad3a50bb7ffa745c04d9d76b489c +size 75729 diff --git a/marked/M/T-REC-M.3060-200603-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/M/T-REC-M.3060-200603-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59da66b37cb9c64834ba7c9fa3c547e2ed5cbdc7 --- /dev/null +++ b/marked/M/T-REC-M.3060-200603-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78a374f9eb3375aeab1d39ce62711b08b1b84e380e831af3f8dcccd1c5159968 +size 92696 diff --git a/marked/M/T-REC-M.3071-201801-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/M/T-REC-M.3071-201801-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..484965c79df8cfefead22ab2de5e3fdc304fc849 --- /dev/null +++ b/marked/M/T-REC-M.3071-201801-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:952c38909b0a9f2e3adb1cb56babf9ae37e8a199e262e185f06bc4a83347efa9 +size 26097 diff --git a/marked/M/T-REC-M.3071-201801-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/M/T-REC-M.3071-201801-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/M/T-REC-M.3071-201801-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/M/T-REC-M.3071-201801-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/M/T-REC-M.3071-201801-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b033c20c8ddcd8b82dcc5e4a77cb91b55d5b493 --- /dev/null +++ b/marked/M/T-REC-M.3071-201801-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e358c2eccb3bd3f19bb9bc95a4ed496abd42b0f73d4cd5ca93fa9a07131c867 +size 99348 diff --git a/marked/M/T-REC-M.3071-201801-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3071-201801-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72d883da47163399c9f9e571df3da70f0fef8836 --- /dev/null +++ b/marked/M/T-REC-M.3071-201801-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc01fbdcf1f3af8bffe8f8ce7b486ea125c47bce315e80764376abf3cd26d38b +size 110348 diff --git a/marked/M/T-REC-M.3071-201801-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/M/T-REC-M.3071-201801-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b24bac9a81e4a7373d52ae6355f29c9ef5145c3 --- /dev/null +++ b/marked/M/T-REC-M.3071-201801-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:129496a42439facb3ef426512a159526c6767c446e8b5a740b87df7e7e95d62d +size 83454 diff --git a/marked/M/T-REC-M.3071-201801-I_PDF-E/raw.md b/marked/M/T-REC-M.3071-201801-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6164546163a570e9e9f292ea9ba7e8d0fd7591f7 --- /dev/null +++ b/marked/M/T-REC-M.3071-201801-I_PDF-E/raw.md @@ -0,0 +1,372 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3071** + +(01/2018) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Cloud-based network management functional architecture** + +Recommendation ITU-T M.3071 + +**ITU-T** + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a large, bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +## ITU-T M-SERIES RECOMMENDATIONS + +## TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T M.3071 + +# Cloud-based network management functional architecture + +## Summary + +Recommendation ITU-T M.3071 introduces a new network management functional architecture with cloud-computing technology. In this Recommendation, the background and basic concept of cloud-based network management are provided. This Recommendation also provides details of a cloud-based network management functional architecture, including its basic components, functionalities and the relationship between its components. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.3071 | 2018-01-13 | 2 | 11.1002/1000/13479 | + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2018 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Introduction..... | 2 | +| 7 Cloud-based network management functional architecture ..... | 3 | +| 7.1 Basic concept..... | 3 | +| 7.2 Detailed structure of cloud-based network management functional architecture ..... | 4 | +| 7.3 The functions of each part in the architecture ..... | 5 | +| 7.4 The relationship between the components in the architecture..... | 6 | + + + +## Recommendation ITU-T M.3071 + +## Cloud-based network management functional architecture + +# 1 Scope + +This Recommendation provides details on the concept of cloud-based network management functional architecture and its fundamental components. It describes the composition of a cloud-based network management functional architecture, explains the functions of each component in the architecture, and also introduces the relationship between these components. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. + +[ITU-T Y.3521] Recommendation ITU-T Y.3521/M.3070 (2016), *Overview of end-to-end cloud computing management*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 management service** [ITU-T M.3010]: A management service is an offering fulfilling specific telecommunications management needs. + +**3.1.2 network element** [ITU-T M.3010]: An architectural concept that represents telecommunication equipment (or groups/parts of telecommunication equipment) and supports equipment or any item or groups of items considered belonging to the telecommunications environment that performs network element functions (NEFs). + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 cloud-based network management**: Cloud-based network management is to perform network management functions using cloud-computing technology, and it can also be used to manage both traditional telecommunication networks and/or cloud computing infrastructures. + +**3.2.2 management service analysis function:** The management service analysis function provides the ability to analyse each management service in the network management. Each management service is registered in this analyser function, and all related information about this service is analysed and stored for future use. + +**3.2.3 management service composing function:** The management service composing function provides the ability of composing several small management functions into a new complex management service, so that a new type of management functionality can be easily provided without having to change the implementation of the component management functions. + +**3.2.4 management service deployment function:** The management service deployment function provides the ability of deploying required services for a management task. Each management task may need the support of multiple management services, and for those services which are not ready for use, they will appropriately be deployed into some virtualized resources on the cloud infrastructure. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|--------------------------| +| FS | Function Set | +| IT | Internet Technology | +| NE | Network Element | +| NEF | Network Element Function | +| P&C | Perception and Control | +| VM | Virtual Machine | + +# 5 Conventions + +None. + +# 6 Introduction + +Current network management and technologies have the weak point that when new management requirements are proposed, it is difficult to provide a new management service based on the existing services using traditional management technology. It is also hard to compose a small system with simplified management functions on demand. + +Cloud computing has become one of the mainstream technologies used in telecommunication networks, as well as Internet services. Cloud-computing technology has the following benefits: high usage rate of physical resources, reliable service provision, high extensibility, cost efficient and service on demand, etc. When introducing cloud computing technology into the network management domain, it is easy to solve the above problems, and it will be very flexible to provide new management services. + +When introducing the cloud into network management, it means that different management function blocks can be placed into virtual resources, and the virtualized resources can be grouped together to form a composed management service that is more powerful to provide complex management functions. It is also capable of dealing with a large amount of management data, as distributed computing can be carried out on cheap servers. + +The term management services used in this Recommendation is not the cloud service provided by a network operator or a cloud operator. Management services are provided by a management system, regardless of whether it is based on the cloud or not. A cloud service is provided by a cloud-service provider to end users for resource virtualization, which provides end users with the cloud-computing and/or cloud-storing capabilities. + +A cloud-aware management system described in [ITU-T Y.3521] is a management system which can be used to manage both traditional telecommunication networks and cloud-computing infrastructures. A cloud-based management system in this Recommendation is a management system which is built using cloud-computing technology, and it can also be used to manage both traditional telecommunication networks and/or cloud-computing infrastructures. A cloud-based management system can be a cloud-aware management system, but it is not necessary to manage cloud infrastructures using a cloud-based management system. + +# 7 Cloud-based network management functional architecture + +## 7.1 Basic concept + +Cloud computing is a technology from the IT domain, with the aim for a supplier to share computing and storage capabilities in the cloud to multiple customers. A system can be built using the traditional means, or using cloud-computing technology to provide services to customer and using the cloud as its infrastructure, as far as the services can be provided. A network management system is a software system which provides network management services to operators or telecommunication service providers. Thus using cloud technology in network management systems will also bring the benefits of the cloud into the network management field. + +Cloud-based network management systems may include two main parts, one is the cloud-based network management platform, and the other is management applications for various network technologies which are built over the management platform. + +Figure 1 shows the basic concept of the cloud-based network management platform and the management applications. + +![Diagram showing three 'Management application' ovals above a 'Cloud-based network management platform' rectangle, with arrows pointing from each application to the platform.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates the basic concept of the cloud-based network management platform and applications. It consists of three ovals, each labeled "Management application", arranged horizontally at the top. Below these ovals is a single rectangle labeled "Cloud-based network management platform". Three vertical arrows point from each of the three ovals down to the rectangle, indicating that the applications run on or are supported by the platform. Below the rectangle, the text "M.3071(18)\_F01" is displayed. + +Diagram showing three 'Management application' ovals above a 'Cloud-based network management platform' rectangle, with arrows pointing from each application to the platform. + +**Figure 1 – Cloud-based network management platform and applications** + +The cloud-based network management platform is described in detail in clause 7.2. Management application functions can be the applications that provide functions dedicated to the management of a specific network technology (e.g., mobile core network, transport network), and they provide their own functionality for its dedicated network, and share the lower layer functions of the cloud-based network management platform, e.g., cloud infrastructure management, or common management services. + +## 7.2 Detailed structure of cloud-based network management functional architecture + +### 7.2.1 High-level layering of cloud-based network management functional architecture + +![Diagram of the high-level layering of cloud-based network management functional architecture showing three layers: Management service layer, Perception and control layer, and Managed network layer.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +``` + +graph TD + subgraph Management_service_layer [Management service layer] + direction LR + MSF1[Management service function] + MSF2[Management service function] + MSF3[Management service function] + MSF4[Management service function] + end + + subgraph Perception_and_control_layer [Perception and control layer] + PCMF[P&C management function] + PCAF1[P&C application function] + PCAF2[P&C application function] + PCAF3[P&C application function] + PCMF --> PCAF1 + PCMF --> PCAF2 + PCMF --> PCAF3 + end + + subgraph Managed_network_layer [Managed network layer] + direction LR + NEF1((NEF)) + NEF2((NEF)) + NEF3((NEF)) + NEF4((NEF)) + end + + MSF1 --> PCMF + MSF2 --> PCMF + MSF3 --> PCMF + MSF4 --> PCMF + + PCAF1 --> NEF1 + PCAF2 --> NEF2 + PCAF3 --> NEF3 + PCAF3 --> NEF4 + +``` + +M.3071(18)\_F02 + +Diagram of the high-level layering of cloud-based network management functional architecture showing three layers: Management service layer, Perception and control layer, and Managed network layer. + +**Figure 2 – High-level layering of cloud-based network management functional architecture** + +Figure 2 shows the high-level layering of cloud-based network management functional architecture, which includes the following three layers: + +- **Managed network layer:** This layer indicates the layer containing all the network element functions (NEFs) that are to be managed. The NEs providing the NEFs can be the traditional telecommunication network elements, or elements in a cloud infrastructure. +- **Perception and control layer (P&C layer):** This layer indicates the perception function blocks and the NE controlling function blocks. Perception function blocks have the capability to collect the configuration information, running status, or the performance data from the NEFs, and the NE controlling function blocks are able to make necessary reconfigurations or modifications to NE parameters, through interactions with the specified NEFs. +- **Management service layer:** This layer mainly contains the network management function blocks, which provide management services to network operators. + +### 7.2.2 Detailed composition of cloud-based network management functional architecture + +![Figure 3: Detailed composition of the management service layer. The diagram shows two main functional sets: Network management application function set and Cloud infrastructure function set. The Network management application function set is divided into Management service FS (containing four Management service functions) and Management controller FS (containing VM monitor, Management service analysis, Management service deployment, and Management service composing functions). The Cloud infrastructure function set is divided into Cloud hypervisor function and Cloud physical element functions.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +The diagram illustrates the detailed composition of the management service layer, organized into two primary functional sets: + +- Network management application function set:** This set is further divided into two functional sets: + - Management service FS:** Contains four identical "Management service function" blocks. + - Management controller FS:** Contains four distinct functions: "VM monitor function", "Management service analysis function", "Management service deployment function", and "Management service composing function". +- Cloud infrastructure function set:** This set is divided into: + - Cloud hypervisor function:** A single function block. + - Cloud physical element functions:** A single function block. + +M.3071(18)\_F03 + +Figure 3: Detailed composition of the management service layer. The diagram shows two main functional sets: Network management application function set and Cloud infrastructure function set. The Network management application function set is divided into Management service FS (containing four Management service functions) and Management controller FS (containing VM monitor, Management service analysis, Management service deployment, and Management service composing functions). The Cloud infrastructure function set is divided into Cloud hypervisor function and Cloud physical element functions. + +**Figure 3 – Detailed composition of the management service layer** + +Figure 3 shows the detailed composition of cloud-based network management functional architecture, which is a "refinery" of the components in the management service layer as shown in Figure 2. + +The cloud-based network management functional architecture is composed of the following two main parts: cloud infrastructure function set and network management application function set. + +The cloud infrastructure function set includes cloud physical element functions and a cloud hypervisor function above them. Cloud physical element functions provide the basic functions of computing and storage. The cloud hypervisor function provides the functionality to manage cloud physical elements, and provide virtualization functions above them. + +The network management application function set may be further divided into two parts: management controller function set and management service function set. The management controller function set includes the basic supporting functions of the management platform, and also provides common functions to support management applications. The management service function set provides management functions, which are divided into several aspects of network management, and usually they are application specific. + +## 7.3 The functions of each part in the architecture + +In Figure 3, the functions of each component are further explained in this clause. + +- 1) **Cloud physical element function:** This is the lowest level of cloud infrastructure and is usually composed of the functions provided by physical servers, computers, disks, network connectors, and all other elements that form a physical cloud computing environment. It provides the basic computing and storage resources from the physical layer. +- 2) **Cloud hypervisor function:** This is a management layer over cloud physical element functions. The cloud hypervisor function provides the management ability of virtualized resources, for example, creating/deleting a new virtual machine (VM), start/suspend a VM, + +and query/change a configuration of a VM, etc. It also provides users with virtualized resources using a unified interface. From the users' perspective the cloud hypervisor function can provide computing and storage capabilities dynamically, based on users' requirements. + +- 3) Management controller function set: This contains multiple controlling functions that support the running of the cloud-based network management platform, and each function can be implemented by a small function block. Some basic function blocks in the controllers are listed below. + - VM monitoring function: This function provides the ability to monitor the performance of VMs. It monitors the dynamic information of the running status of VMs. When performance degradation is detected, the monitor informs the controller to handle the resource reassignment or service transportation. + - Management service analysis function: This function provides the ability of analysing each management service in the network management. Each management service is registered in this analyser, and all the related information about this service is analysed and storage for future use. + - Management service deployment function: This function provides the ability of deploying required services for a management task. Each management task may need the support of multiple management services, and for those services which are not ready for use they will appropriately be deployed into some virtualized resources on the cloud infrastructure. + - Management service composing function: This function provides the ability of composing several small management functions into a new complex management service, so that they can easily provide a new type of management functionality without having to change the implementation of the component management functions. + - More function blocks can be extended to support the running of the cloud-based network management architecture. +- 4) Management service function set: This provides management functions to network operators, and is composed of all kinds of small management functions. Each network management function is performed by a service application, and those management functions can form composed services that provide more complex network management functions. Most management service applications are application-specific to a network technology, but there are still some applications which are more general to be used across different network technologies. In such cases, the common service application will be reused. + +## **7.4 The relationship between the components in the architecture** + +This clause will introduce the relationship between the components in the architecture. + +![Diagram of cloud-based network management functional architecture showing layers for management services, management controller, cloud hypervisor, and physical equipment functions, with reference points r1 through r5.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the cloud-based network management functional architecture, organized into three main layers within a dashed boundary, with an external component on the right. + +- Top Layer (Management service FS):** Contains three boxes labeled "Management service function". They are connected horizontally by reference points **r4**. The rightmost box connects to an external box labeled "NEFs of the network to be managed" via reference point **r5**. +- Middle Layer (Management controller FS):** Contains four boxes: "VM monitor function", "Management service analysis function", "Management service deployment function", and "Management service composing function". This layer is connected to the top layer via reference point **r3**. +- Bottom Layer (Cloud infrastructure function sets):** + - Contains a box labeled "Cloud hypervisor function" at the top. + - Below it, three boxes labeled "Element function" are shown, collectively labeled "Cloud physical equipment functions". + - The "Cloud hypervisor function" box is connected to the "Element function" boxes via reference point **r1**. + - The entire bottom layer is connected to the middle layer via reference point **r2**. + +Labels on the left side of the diagram identify the top two layers as the "Network management application function set" and the bottom layer as "Cloud infrastructure function sets". A label **M.3071(18)\_F04** is located in the bottom right corner. + +Diagram of cloud-based network management functional architecture showing layers for management services, management controller, cloud hypervisor, and physical equipment functions, with reference points r1 through r5. + +**Figure 4 – Reference point between the components in the cloud-based network management functional architecture** + +Figure 4 shows the reference point between the components in the cloud-based network management functional architecture. All the reference points in Figure 4 are defined in [ITU-T M.3010]. In order to distinguish these references points in this Recommendation, which can show the relationship among functional components, they are numbered as r1, r2, r3, r4 and r5 respectively, as explained in Table 1. + +**Table 1 – Reference points in cloud-based network management functional architecture** + +| Name | Position | Definition | +|-------------|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| r1 | Between cloud hypervisor function and cloud physical element function. | Through reference point r1 a hypervisor function can connect to cloud physical element functions to perform the virtualized resource management functions (for example, VM management, including but not limited to, creation, deletion, query and modification of virtualized resources.) In this Recommendation the virtualized resource will be assigned to building the management system itself. | +| r2 | Between management controller function set and cloud hypervisor function. | Through reference point r2 the management controller function set can interact with the cloud hypervisor function. The management controller function set sometimes may ask the cloud infrastructure function set to assign new virtual resources in order to meet new management requirements. Through this reference point there is no need for management controller FS to know any details about the physical layer resources, and it only sends the command including the requirement for the virtualized resources, and then the cloud hypervisor function will handle the rest. | +| r3 | Between management service function set and management controller function set. | Reference point r3 is provided from the management controller function set to the management service function set. Through this reference point applications can use the common functions provided by the management controller FS. For example, one service application can search for another service application which may be able to meet its requirements. Management controller FS can also use this reference point to perform the management service analysis and composition, etc. | +| r4 | Between management service applications. | Reference point r4 is between the management service functions at the application level. Usually, there are cases when one management service function needs the support of another management service function, then it just invokes the function provided by that management service function. Reference point r4 is used in this situation. | +| r5 | Between management service function set and the NEFs of the network to be managed. | The network to be managed is the target for network management. Through reference point r5 management service functions can interact with the NEFs in the network to be managed, and perform the actual network management functions. | + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db3a38c033347284e438d3c46e2d6076a9731f6e --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b99872ab48d68a8ad37d9d342b3b1a072c965da954770493c2ff5545913f5f75 +size 165640 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/0f2a1e4a7b12fe5b8749882ecd636f5c_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/0f2a1e4a7b12fe5b8749882ecd636f5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc0b7d230aa814ba7ff9ac76ad42df85d1a5e392 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/0f2a1e4a7b12fe5b8749882ecd636f5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0c7abe2c31f090e1c85560f9d1d8a3f7be583ad8383d32f010ee596b2f00001 +size 5264 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed476c5649e9eff05f321dedca1c27fd9d06292e --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5d6ca7c564f9ab460a2e13cdcf1238a34c895bc9de4cd17bdb8b7379ec4b288 +size 5530 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51e404213a852c62852a622b8323af431aa89060 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da3a8eb5a8ecdc6aad8366379c639207b2a0ff533e31cdd358a81eecac82f8f0 +size 166423 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab436a3a95630a6d01951b6ad4a063fe884b7874 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e32c36d24563c259c2bc035cdf58d261c73e6f36ea9e000162c56375c0b4df8c +size 3110 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d10e210fc9681951b00a7be5d996ed8b71ff48ab --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ea1eff168abaa18ee3e807d158ec9f3e65fe7aec8baddea323140a33197802b +size 165051 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e8963c5aa28ec3ba478d5cbad525ffe2b820c31 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7930c93851400e06322e92a6cbb3cfeabf048c7f4689df22eb0e5f8aeabe9d88 +size 20426 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..456a7824257a4f4bb120213fd94030a74b10afe7 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa343546063e2cb39bdc4ce620e72a0246d28b0cc597ffcbcc28ec6a3f43ae02 +size 161088 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0b1e6b203489d5805750da6f0697b7fecf0dc0c --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dc554f50d327f5fbdb235dde887700d91aae7663aa5fd3e8a3c502d3a09ed20 +size 49469 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32ffd4d8d8033ee7dab5adfc41585e7c0997a259 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45e1a68822ed0fa0c28a8a33951f67f7e04444a3a494786a86a113252b52ce9c +size 201254 diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed21fe65ace00bbe913373659ca833f5d5766b43 --- /dev/null +++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02bf87cc334cc0ebe54f371c4ecf5955b05b9b2394b7ba684c201abcb9be6d0a +size 100816 diff --git a/marked/M/T-REC-M.3101-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3101-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07882e53216010a60e9a65c2269a1383f90fa8f5 --- /dev/null +++ b/marked/M/T-REC-M.3101-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d55bc1404a00110e016e59b37c568857c51417048eaede96b71d932cccb62e1 +size 8202 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50ce836e01a3c0ed06644e7e92f99c9015c3952e --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dc3a6dc9e552fc36ac9e91ae7dfe357683e40cd847c97ee41ce3566fff1151a +size 92910 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0660fa30e9d6f1ad534b453f29e2fc622b3bb938 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2e3ca2fcbd91ed5602bb990c4cb2a138b0afa2c969f04ebabfd3ff0c5ab1bf9 +size 8209 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a921feacf2f611e6a965e988b0acd4a15fa69f1 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a463e04430965f707b115ee601f4750e864ce43bd7dd32010424abcdb5628cec +size 85643 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b847031edac4ec46c3fd266f2acfc895585d000d --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fda82fa139def1ce33154a37c6f4ce99478665a3daf633135baa03fec0605024 +size 17583 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96bec7a9b09f511a57049c6b8eb89c36ce619d05 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b67b549276b1faef9b7a7a7281920ab561b3e44b54731d98f52d879a6d8ee18 +size 51681 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6b9d0afa052282eb9cc55f347046f5e043b8b68 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34923dfe73207c600215363c98c8b153bf62425c126ce6d41d3f4fdf12925deb +size 37343 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49a9c92c2f31b12c610022cf9dfdba2a3e159f7b --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4aaa80da370dcafa628800a813a65ddddd9982e5bfa96fd43ac485ca4803e4d1 +size 105937 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08f6ce9754fd131441b1806577c2f8754080f268 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8a45275dda135228f4aeacb07f6137e63d85bb46459a985989f5eda0a69bbc0 +size 104294 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66960163ddd69685525088d448ba53bbf33f94f7 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be41dd293f59149c05260c189483aff306ff5a8490d4246b287022290cff115f +size 86786 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74af7694a11487098ea5e346120e1a36021a0737 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d3ac32a2b29fb51bebe46677e839d82f5e5e3fd76f93bbff9c5e9ad5b91b653 +size 136210 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8ab78bc244d66438a3bcfb8d97a9a2d877dcc68 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d635cb8d02b8fe0452e59771e762553aa108f7daedd95ea7eb4d54961c59a42b +size 59473 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26abdca8a68250c2346fc3579041fa8407090cac --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be4b05e49710a1d241f0efd3817a3153bafcd9cdcd290f668e6d521cdd5ee831 +size 170133 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5916e73ba7e6ee539cde8c831ce6e0f4001de203 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae56dd975c72eec94637739d3de1f660819d0a0a6c1fd35d64ce3f648d718757 +size 44395 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53d590f38cf50cfe454e83430c71cda346ee1d04 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfea0b0b7113ad3bce3fd6a5a8ed22916bcd5d8880cbc038b7f7b8dcbde78b82 +size 26462 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..427e8a77c76fa047f0f76a123863cb622e051361 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f33ecfea31c54e43ec44541e2e9fa53b1818a5536e649c1995a6dc6ad34416c0 +size 119640 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f674f71d7581e7e841e202251c5bac1fe72af2da --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9ae24c0642f98508b7a32fb9a0c63f02fa17327448d2b3989f61324100e4bdc +size 71249 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47c98873329e3f6eb11ea04fc894bd6070739f81 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd0c370b88b51feb446caf32a0cd7cc432316aa13ab6c7685401d9060f2c5545 +size 18750 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e3d0b52e8b5fb8bdba16f6369c68215c842ae16 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5000953ea30efbd99cc4f96fa75495394907fd8a7154d7a10cdd07edcc14d541 +size 43836 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..763641d0988d547169a8f91a0b5eefcb8b4b77ba --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9db3266039ab4a128387f4e2db0d61c97c566d8041652f5d6534980911b1a02b +size 23365 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ab46520c9d0fe27294a8582deaff7fd422806a4 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a86edd392c0f7b23e7ce794cee43ce7130a20d924f7cae2ce1b84fb848d2ab7 +size 26758 diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/raw.md b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..36332413b9a630bb1916734f282a71ad86b37940 --- /dev/null +++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/raw.md @@ -0,0 +1,4095 @@ + + +![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with the letters ITU and a lightning bolt. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3108.1** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/99) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**Information model for management of leased +circuit and reconfigurable services** + +ITU-T Recommendation M.3108.1 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **INFORMATION MODEL FOR MANAGEMENT OF LEASED CIRCUIT AND RECONFIGURABLE SERVICES** + +## **Summary** + +This Recommendation provides a GDMO-based information model to support the management of the leased circuit service as outlined in Recommendation M.3208.1. Appendix I provides a protocol-independent version of this information model in "structured" English. Appendix II provides a mapping from the management functions in Recommendation M.3208.1 to the Managed Objects defined in this Recommendation. Appendix III provides a Unified Modelling Language (UML) view of the same information model. + +###### **Source** + +ITU-T Recommendation M.3108.1 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1999 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------------------|----| +| 1 | Scope, purpose and application..... | 1 | +| 1.1 | Scope..... | 1 | +| 1.2 | Purpose..... | 1 | +| 1.3 | Application..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 2 | +| 5 | Overview..... | 3 | +| 5.1 | Generic service request fragment..... | 5 | +| 5.2 | LCS service request fragment..... | 5 | +| 5.3 | Link connection service request fragment ..... | 5 | +| 5.4 | Transport service fragment ..... | 6 | +| 5.5 | Resource fragment ..... | 6 | +| 6 | Information model ..... | 8 | +| 6.1 | Managed objects for generic service request fragment..... | 8 | +| 6.1.1 | currentServiceRequest ..... | 8 | +| 6.1.2 | serviceRequestHistoryRecord..... | 10 | +| 6.1.3 | serviceModifyRequest ..... | 10 | +| 6.2 | Managed objects for LCS request fragment..... | 11 | +| 6.2.1 | currentLcsRequest ..... | 11 | +| 6.2.2 | lcsRequestHistoryRecord ..... | 11 | +| 6.2.3 | lcsModifyRequest..... | 12 | +| 6.3 | Managed objects for link connection service request fragment..... | 12 | +| 6.3.1 | currentLinkConnectionServiceRequest ..... | 12 | +| 6.3.2 | linkConnectionServiceRequestHistoryRecord ..... | 13 | +| 6.3.3 | linkConnectionServiceModifyRequest..... | 13 | +| 6.4 | Managed objects for service fragment ..... | 13 | +| 6.4.1 | Transport service ..... | 13 | +| 6.4.2 | lcs..... | 14 | +| 6.4.3 | linkConnectionService..... | 15 | +| 6.4.4 | Service Access Domain ..... | 15 | +| 6.4.5 | Service Access Group..... | 16 | +| 6.5 | Managed objects for resource fragment..... | 16 | +| 6.5.1 | Service Access Equipment ..... | 16 | + +| | Page | +|----------------------------------------------------------|-------------| +| 6.6 Packages..... | 17 | +| 6.6.1 aliasNameInfoPackage..... | 17 | +| 6.6.2 aliasNamePackage..... | 17 | +| 6.6.3 bandwidthInfoPackage..... | 17 | +| 6.6.4 bandwidthPackage..... | 17 | +| 6.6.5 customerRequestNumberPackage..... | 17 | +| 6.6.6 dateOfInstallationPackage..... | 17 | +| 6.6.7 dailySchedulingInfoPackage..... | 18 | +| 6.6.8 dailySchedulingCurrentPackage..... | 18 | +| 6.6.9 diversityInfoPackage..... | 18 | +| 6.6.10 diversityPackage..... | 18 | +| 6.6.11 equipmentManufacturerPackage..... | 18 | +| 6.6.12 equipmentTypePackage..... | 18 | +| 6.6.13 expectedDateOfInstallationInfoPackage..... | 18 | +| 6.6.14 expectedDateOfInstallationPackage..... | 19 | +| 6.6.15 externalSchedulerCurrentPackage..... | 19 | +| 6.6.16 externalSchedulerInfoPackage..... | 19 | +| 6.6.17 initialServiceAdministrativeStateInfoPackage..... | 19 | +| 6.6.18 initialServiceAdministrativeStatePackage..... | 19 | +| 6.6.19 modelTypePackage..... | 19 | +| 6.6.20 originatingLocationCPEInfoPackage..... | 19 | +| 6.6.21 originatingLocationCPEModifyPackage..... | 19 | +| 6.6.22 originatingLocationCPEPackage..... | 20 | +| 6.6.23 originatingLocationCPInfoPackage..... | 20 | +| 6.6.24 originatingLocationInfoPackage..... | 20 | +| 6.6.25 originatingLocationSapInfoPackage..... | 20 | +| 6.6.26 originatingLocationSapPackage..... | 20 | +| 6.6.27 procedurePackage..... | 20 | +| 6.6.28 quantityInfoPackage..... | 20 | +| 6.6.29 quantityPackage..... | 20 | +| 6.6.30 reflectiveOperationalStatePackage..... | 21 | +| 6.6.31 reflectiveAdministrativeStatePackage..... | 21 | +| 6.6.32 routeInfoPackage..... | 21 | +| 6.6.33 routePackage..... | 21 | +| 6.6.34 serviceAdministrativeStatePackage..... | 21 | +| 6.6.35 serviceAvailabilityDateInfoPackage..... | 21 | +| 6.6.36 serviceAvailabilityDatePackage..... | 21 | +| 6.6.37 serviceCustomerContactPackage..... | 22 | +| 6.6.38 serviceDescriptionInfoPackage..... | 22 | + +| | Page | +|---------------------------------------------------------|-------------| +| 6.6.39 serviceDescriptionPackage ..... | 22 | +| 6.6.40 serviceProviderContactPackage ..... | 22 | +| 6.6.41 serviceTerminationDateInfoPackage ..... | 22 | +| 6.6.42 serviceTerminationDatePackage ..... | 22 | +| 6.6.43 serviceTypeInfoPackage ..... | 22 | +| 6.6.44 terminatingLocationCPEInfoPackage..... | 23 | +| 6.6.45 terminatingLocationCPEModifyPackage ..... | 23 | +| 6.6.46 terminatingLocationCPEPackage ..... | 23 | +| 6.6.47 terminatingLocationCPInfoPackage ..... | 23 | +| 6.6.48 terminatingLocationInfoPackage ..... | 23 | +| 6.6.49 terminatingLocationSapInfoPackage ..... | 23 | +| 6.6.50 terminatingLocationSapPackage ..... | 23 | +| 6.6.51 weeklySchedulingInfoPackage ..... | 23 | +| 6.6.52 weeklySchedulingCurrentPackage ..... | 24 | +| 6.7 Attributes ..... | 24 | +| 6.7.1 aliasName ..... | 24 | +| 6.7.2 bandwidth ..... | 24 | +| 6.7.3 cp ..... | 24 | +| 6.7.4 customerRequestNumber..... | 24 | +| 6.7.5 dateOfInstallation ..... | 25 | +| 6.7.6 diversity ..... | 25 | +| 6.7.7 equipmentManufacturer..... | 25 | +| 6.7.8 equipmentType ..... | 25 | +| 6.7.9 expectedDateOfInstallation ..... | 25 | +| 6.7.10 listOfSags..... | 25 | +| 6.7.11 listOfSaps..... | 26 | +| 6.7.12 modelType ..... | 26 | +| 6.7.13 numberOfUnspecifiedSaps ..... | 26 | +| 6.7.14 originatingLocation..... | 26 | +| 6.7.15 originatingLocationCP ..... | 26 | +| 6.7.16 originatingLocationCPE ..... | 26 | +| 6.7.17 originatingLocationSap..... | 27 | +| 6.7.18 procedure ..... | 27 | +| 6.7.19 providerRequestNumber..... | 27 | +| 6.7.20 quantity ..... | 27 | +| 6.7.21 requestedInitialServiceAdministrativeState ..... | 27 | +| 6.7.22 requestReceptionTime ..... | 28 | +| 6.7.23 requestSequenceNumber ..... | 28 | +| 6.7.24 route ..... | 28 | + +| | Page | +|--------------------------------------------------------|-------------| +| 6.7.25 sadId..... | 28 | +| 6.7.26 sagId..... | 28 | +| 6.7.27 sagLocation..... | 29 | +| 6.7.28 serviceAvailabilityDate ..... | 29 | +| 6.7.29 serviceCustomerContact..... | 29 | +| 6.7.30 serviceInstance..... | 29 | +| 6.7.31 serviceProviderContact..... | 29 | +| 6.7.32 serviceRequestState ..... | 29 | +| 6.7.33 serviceTerminationDate..... | 30 | +| 6.7.34 terminatingLocation..... | 30 | +| 6.7.35 terminatingLocationCP ..... | 30 | +| 6.7.36 terminatingLocationCPE ..... | 30 | +| 6.7.37 terminatingLocationSap..... | 30 | +| 6.8 Error messages ..... | 31 | +| 6.8.1 addToSagError..... | 31 | +| 6.8.2 bandwidthUnavailable ..... | 31 | +| 6.8.3 CreateLCSError ..... | 31 | +| 6.8.4 createLinkConnectionError ..... | 31 | +| 6.8.5 createSadError ..... | 31 | +| 6.8.6 createSagError ..... | 31 | +| 6.8.7 deleteLCSError ..... | 32 | +| 6.8.8 deleteLinkConnectionError ..... | 32 | +| 6.8.9 deleteSadError ..... | 32 | +| 6.8.10 deleteSagError ..... | 32 | +| 6.8.11 modifyLCSError ..... | 32 | +| 6.8.12 removeFromSagError ..... | 32 | +| 6.8.13 resourcesUnavailable..... | 33 | +| 6.9 Notifications..... | 33 | +| 6.9.1 lcsModifyProgressProblemReport..... | 33 | +| 6.9.2 lcsRequestProgressProblemReport..... | 33 | +| 6.9.3 linkConnectionModifyProgressProblemReport ..... | 33 | +| 6.9.4 linkConnectionRequestProgressProblemReport ..... | 33 | +| 6.10 Actions ..... | 34 | +| 6.10.1 updateServiceRequest..... | 34 | +| 6.10.2 AddSapsToSag ..... | 34 | +| 6.11 Name bindings ..... | 34 | +| 6.11.1 currentLcsRequest-account..... | 34 | +| 6.11.2 lcsRequestHistoryRecord-currentLCSRequest..... | 34 | + +| | Page | +|------------------------------------------------------------------------------------------------|-------------| +| 6.11.3 lcsModifyRequest-lcs ..... | 35 | +| 6.11.4 currentLinkConnectionServiceRequest-account ..... | 35 | +| 6.11.5 linkConnectionServiceRequestHistoryRecord-
currentLinkConnectionServiceRequest ..... | 35 | +| 6.11.6 linkConnectionServiceModifyRequest-linkConnectionService ..... | 35 | +| 6.11.7 serviceAccessEquipmentView-account ..... | 35 | +| 6.11.8 linkConnectionService-account ..... | 36 | +| 6.11.9 lcs-account ..... | 36 | +| 6.11.10 serviceAccessDomain-account ..... | 36 | +| 6.11.11 serviceAccessGroup-serviceAccessDomain ..... | 36 | +| 6.12 ASN.1 syntax ..... | 37 | +| 6.12.1 Rules of extensibility ..... | 37 | +| 6.12.2 ASN.1 module ..... | 37 | +| 7 Functional units ..... | 44 | +| 7.1 Basic transport service functional unit ..... | 45 | +| 7.2 Transport service order functional unit ..... | 45 | +| 7.3 Transport service order history functional unit ..... | 45 | +| 7.4 Transport service modify functional unit ..... | 45 | +| 7.5 Transport resource visibility functional unit ..... | 45 | +| 7.6 Negotiation of functional units ..... | 45 | +| 8 Conformance ..... | 46 | +| 8.1 Static conformance ..... | 46 | +| 8.2 Dynamic conformance ..... | 46 | +| 8.3 Conformance to managed object definitions ..... | 46 | +| Appendix I – Protocol-independent object description ..... | 47 | +| I.1 Generic service request fragment ..... | 48 | +| I.1.1 currentServiceRequest ..... | 48 | +| I.1.2 serviceRequestHistoryRecord ..... | 50 | +| I.1.3 serviceModifyRequest ..... | 52 | +| I.2 LCS request fragment ..... | 53 | +| I.2.1 currentLcsRequest ..... | 53 | +| I.2.2 lcsRequestHistoryRecord ..... | 55 | +| I.2.3 lcsModifyRequestRecord ..... | 55 | + +| | Page | | +|--------------|---------------------------------------------------------------------|----| +| I.3 | Link connection service request fragment ..... | 56 | +| I.3.1 | currentLinkConnectionServiceRequest ..... | 56 | +| I.3.2 | linkConnectionServiceRequestHistoryRecord ..... | 58 | +| I.3.3 | linkConnectionServiceModifyRequest..... | 58 | +| I.4 | Service fragment ..... | 59 | +| I.4.1 | transportService ..... | 59 | +| I.4.2 | lcs..... | 60 | +| I.4.3 | linkConnectionService..... | 61 | +| I.5 | Reconfigurable service fragment ..... | 62 | +| I.5.1 | serviceAccessDomain..... | 62 | +| I.5.2 | serviceAccessGroup ..... | 63 | +| I.6 | Resource fragment ..... | 64 | +| I.6.1 | serviceAccessEquipment ..... | 64 | +| Appendix II | – Mapping of M.3208.1 functions into M.3108.1 MOs ..... | 65 | +| Appendix III | – UML diagrams for leased circuit service object model ..... | 68 | +| III.1 | Introduction..... | 68 | +| III.2 | UML class diagrams for inheritance of M.3208.1 object classes ..... | 68 | +| III.3 | UML class diagrams for modelling relationships ..... | 70 | +| III.4 | UML class diagrams for modelling agent functionality..... | 72 | +| III.5 | UML sequence diagrams to illustrate scenarios of object usage ..... | 73 | + +###### Recommendation M.3108.1 + +# INFORMATION MODEL FOR MANAGEMENT OF LEASED CIRCUIT AND RECONFIGURABLE SERVICES + +(Geneva, 1999) + +# 1 Scope, purpose and application + +## 1.1 Scope + +This Recommendation provides a GDMO-based information model to support the management of the leased circuit service as outlined in Recommendation M.3208.1. Appendix I provides a protocol-independent version of this information model in "structured" English. Appendix II provides a mapping from the management functions in Recommendation M.3208.1 to the managed objects defined in this Recommendation. Appendix III provides a Unified Modelling Language (UML) view of the same information model. + +## 1.2 Purpose + +The purpose of this Recommendation is to support standard interfaces, across the X interface, among service customers, service providers and network providers for the purposes of managing leased circuit services in the service management layer of the TMN. It specifically intended to support the requirements provided in Recommendation M.3208.1. + +## 1.3 Application + +This Recommendation is applicable to interfaces between systems that participate in the ordering and management of leased circuit services. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation G.805 (1995), *Generic functional architecture of transport networks*. +- ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network*. +- ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: Overview*. +- ITU-T Recommendation M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*. +- ITU-T Recommendation M.3400 (1997), *TMN management functions*. + +- ITU-T Recommendation Q.821 (1993), *Stage 2 and stage 3 description for the Q3 interface – Alarm surveillance.* +- CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- CCITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, *Information technology – Open Systems Interconnection – Systems management: Event report management function.* +- CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems management: Log control function.* +- ITU-T Recommendation X.746 (1995) | ISO/IEC 10164-15:1995, *Information technology – Open Systems Interconnection – Systems management: Scheduling function.* +- ITU-T Recommendation X.790 (1995), *Trouble management function for ITU-T applications.* + +# 3 Definitions + +This Recommendation uses the definitions provided in Recommendation M.3208.1. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|------|----------------------------------------------------------| +| AP | Access Point | +| ATM | Asynchronous Transfer Mode | +| CP | Connection Point | +| CPE | Customer Premises Equipment | +| GDMS | Guidelines for the Definition of TMN Management Services | +| LC | Link Connection | +| LCS | Leased Circuit Service | +| MS | Management Services | +| NML | Network level Management Layer | +| PDH | Plesiochronous Digital Hierarchy | +| SAD | Service Access Domain | +| SAG | Service Access Group | +| SC | Service Customer | +| SDH | Synchronous Digital Hierarchy | +| SML | Service level Management Layer | +| SN | Service Node | +| SNC | Sub-Network Connection | +| SP | Service Provider | +| TCP | Termination Connection Point | + +TMN            Telecommunications Management Network + +UML            Unified Modelling Language + +# 5        Overview + +This clause provides an overview of the information model and its use in the management of LCS. Clause 6 provides the formal definition of the GDMO-based information model. + +The information model consists of five fragments: + +- Generic service request – contains generic MOs to be used for subclassing MOs in support of specific services. +- LCS service request – supports the service request process for LCS. +- Link connection service request – supports the service request process for link connection service. +- Transport service – represents transport services, supports SC's management of provisioned services. +- Resources – represents resources used for the provisioning of LCS and link connection service. + +The first four are defined in this Recommendation. The fifth also includes information elements defined in other Recommendations, such as Recommendations M.3100 and G.855.1. + +The management of a LCS or a link connection service starts when a Service Customer (SC) requests the service. This can be achieved by the SC creating an instance of a subclass of transportService MO, or the SC creates an instance of a subclass of currentServiceRequest MO. More specifically, the created object is an instance of one of the following MO classes: + +- lcs; +- linkConnectionService; +- currentLcsRequest; +- currentLinkConnectionService. + +The first two bullets above correspond to instant service provisioning, without going through the service request process. The last two bullets above correspond to the case where the SC's request goes through the service request process. + +The request must satisfy the terms of the Service Level Agreement (SLA) between the SC and the SP. + +The following scenario applies when the request proceeds through the service request process. The Service Provider (SP), assuming the Agent role, creates an instance of a (subclass of) currentServiceRequest MO. Upon creation of this MO instance the SP fills in the values of some of the attributes, as specified in Recommendation M.3208.1 (e.g. the actual due date for the service). The SP then sends a create reply regarding that creation to the SC, assuming the Manager role. The create reply includes the values of the attributes that must be communicated by the SP to the SC in response to the service request, as per Recommendation M.3208.1. If the SC has created an instance of a (subclass of) currentServiceRequest MO, then the SC can update the request through the updateServiceRequest action, e.g. the SC may request a change to the date when the service is desired, or a different route. The SC may also cancel the initial request by deleting the currentServiceRequest. The (subclasses of) currentServiceRequest represent the current view of the service request. In order to keep track of the modifications issued by the SC, the SP may create (subject to SLA) instances of (a subclass of) serviceRequestHistoryRecord that represent the values + +of the attributes requested to be modified by specific updateServiceRequest action. The first instance of serviceRequestHistoryRecord created for a specific service request represents the values of the attributes of the initial service request. The values of the currentServiceRequest may be different from the values requested by the SC due to changes made by the SP (and reported to the SC). + +After the requested LCS or link connection service has been implemented by the SP, the SP instantiates an instance of the lcs or linkConnectionService MO. Both are subclasses of the transportService MO. More specifically, the SP creates an instance of one of the following MO classes: + +- linkConnectionService; +- lcs. + +The SP then informs the SC of the availability of the requested service through a notification of the creation of an instance of a MO representing that service. + +In some cases the SP may provide the requested service instantaneously, even though formally it goes through the service request process. In this case the SP will send the SC three consecutive notifications: for the creation of a service create request record, for the deletion of the just created service create request record, and for the creation of the requested service. In this case the service create request record is purely transient and the SC does not interact with it. This scenario applies when the SC initiates the request through the service request process. If the SP represents to provide requested LCS or link connection service instantaneously, then another scenario is also possible: the SC skips the service request process and requests the service by issuing a "create an instance of" (a subclass of) transportService. + +After the SC has been notified about the creation of that MO (a subclass of transportService), the SC can modify the service through management operations for some attributes. For other attributes the modification is done by creating an instance of the modifyRequestRecord MO class, referring to the lcs or linkConnectionService MO instance. The SP may choose to require that an instance of serviceModifyRequest MO be created every time the SC wishes to make changes to any attributes of the service. + +An instance of a (subclass of) transportService MO class may refer to instances of serviceAccessEquipmentView MO classes (representing CPE) and/or instances of MO classes corresponding to topological elements such as link, connection point and subnetwork. + +An instance of the networkR1 MO is used for naming. All entries in that MO instance can be changed only by the SP, though the SC can read (GET) such information. + +An instance of the account MO class (imported from Recommendation X.790) contains information regarding the SC, such as the SC's contact information. In general, only the SC can set information in the account MO. The account MO is contained in the network MO (imported from Recommendation M.3100). + +The SC can create an instance of a serviceAccessDomain MO class. A serviceAccessDomain contains zero or more serviceAccessGroups, though a serviceAccessDomain containing less than two serviceAccessGroups is not very useful. The SC can create instances of serviceAccessGroup MO class. A serviceAccessGroup MO contains zero or more SAPs. A serviceAccessGroup is created without any SAPs. After creation of a serviceAccessGroup, the SC can add or remove SAPs from the serviceAccessGroup. The SC can identify some or all of the SAPs desired in a serviceAccessGroup. If the SC adds to a serviceAccessGroup more SAPs than are explicitly identified, then the SP assigns additional SAPs, from the same service location to the serviceAccessGroup, and informs the SC about the identity of those SAPs. The SC can add or remove SAPs from a serviceAccessGroup through management operations. If the two SAPs corresponding to a LCS belong to + +serviceAccessGroups that are members of the same serviceAccessDomain, then the LCS is a reconfigurable LCS. This is usually also reflected in the service name and service type of the LCS. + +## 5.1 Generic service request fragment + +The (generic) service request MOs are not instantiable. They are used as superclasses for service-specific, instantiable MOs. As such the generic MOs can be reused to define instantiable MOs for other services. The LCS and link connection service requests instantiable MOs are derived from the generic ones. + +The generic service request fragment consists of MOs that support the request of a service as well as updates to service requests and modifications to existing services. It defines three generic, non-instantiable, classes: + +- currentServiceRequest; +- serviceRequestHistoryRecord; +- serviceModifyRequest. + +The currentServiceRequest represents the up-to-date values of the attributes describing the requested service. Those values may be different from those in the initial service request due to subsequent changes requested by the SC or introduced by the SP. Indeed, the SP may replace the values of some attributes (e.g. if the available bandwidth does not match the bandwidth requested by the SC). The SLA may specify that the service request history is kept through (subclasses of) serviceRequestHistoryRecord. Several instances of serviceRequestHistoryRecord may be created. The first instance of serviceRequestHistoryRecord represents the SC initial request for service. Subsequently created instances represent changes to the request submitted by the SC. + +If there is a large number of updates, it may not be clear what the SC really wants. To this end the SP may create an instance of a currentServiceRequest MO class. This is a generic, non-instantiable class that represents the current information about what the SC wants. It is derived from serviceCreateRequestRecord, though the values of its attributes are updated (by the SP) whenever a new serviceUpdateRequestRecord is received. When this happens it sends an attribute value change notification to the SC, thus keeping the SC updated. The SC can inquire about the current information in the request by retrieving values of attributes of the currentServiceRequest. + +After the requested service has been created, the SC can modify that service through management operations or by creating instances of (a subclass of) serviceModifyRequest MO class. As in the case of service request, the SC may issue management operations against the MO representing the service instead of creating new instances of serviceModifyRequest. In that case the SP may keep a log of the management operations issued by the SC to update attributes in the MO representing the service. (The mechanism for such storage is outside the scope of this Recommendation.) + +Instantiable, service-specific MO classes are derived from the MOs in this fragment. + +## 5.2 LCS service request fragment + +The MO classes in this fragment consist of LCS-specific subclasses of the MO classes in the generic service request fragment. + +## 5.3 Link connection service request fragment + +The MO classes in this fragment consist of link connection service-specific subclasses of the MO classes in the generic service request fragment. + +## 5.4 Transport service fragment + +The transport service fragment contains a generic, non-instantiable MO transportService from which two instantiable MOs are derived: lcs and linkConnectionService. + +This fragment further contains two objects representing serviceAccessGroup and serviceAccessDomain. Those instantiable objects allow the SC to manage the existing services through management operations directed at the corresponding objects. This is a plausible alternative to the management of existing services through the creation of serviceModifyRequestRecord MOs. + +## 5.5 Resource fragment + +The resource fragment contains two MOs that represent physical resources and which are needed in some aspects of LCS management: network, as defined in Recommendation M.3100, and serviceAccessEquipment, which is defined in this Recommendation. It further includes MOs that would be defined in support of elements in Recommendation G.805 corresponding to topological entities (link, connectionPoint, subNetwork). Those MOs allow the SP to offer the SC a more detailed view of how the service is provisioned. + +Figures 5-1 and 5-2 represent the inheritance and containment relationships of the MOs respectively. Inheritance and containment are not shown for all the MOs that are imported from other Recommendations. Figure 5-2 does not show the containment of the M.3100 network MO in directory objects as specified in Recommendation M.3100. + +This Recommendation defines six Functional Units (FUs): + +- Service order; +- Service modify; +- Leased circuit service; +- Link connection service; +- Reconfigurable circuit service; +- Resource visibility. + +These FUs cover the management functions defined in Recommendation M.3208.1. This Recommendation provides a mapping of the M.3208.1 functions into the FUs and specifies the MOs required for each of the FUs. + +![UML class diagram showing inheritance relationships between service request fragments and resource fragments. The diagram is structured into three main horizontal sections. The top section, labeled 'top (X.721)', contains three gray boxes: 'Generic service request fragment' (with sub-classes 'currentServiceRequest', 'serviceRequestHistoryRecord', and 'serviceModifyRequest'), 'Link connection service request fragment' (with sub-classes 'currentLinkConnectionServiceRequest', 'linkConnectionServiceRequestHistoryRecord', and 'linkConnectionServiceModifyRequest'), and 'LCS service request fragment' (with sub-classes 'currentLcsRequest', 'lcsRequestHistoryRecord', and 'lcsModifyRequest'). A separate box labeled 'Account (X.790)' is also in this section. The bottom section contains two gray boxes: 'transport service request fragment' (with sub-classes 'serviceAccessGroup', 'serviceAccessDomain', 'transportService', 'lcs', and 'linkConnectionService') and 'resource fragment' (with sub-classes 'serviceAccessEquipment' and 'networkR1 (M.3100)'). Lines connect the sub-classes to their parent fragments and to the 'top (X.721)' box.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +``` + +classDiagram + class top_X721_top [top (X.721)] + class Generic_service_request_fragment [Generic service request fragment] + class Account_X790 [Account (X.790)] + class currentServiceRequest + class serviceRequestHistoryRecord + class serviceModifyRequest + class Link_connection_service_request_fragment [Link connection service request fragment] + class currentLinkConnectionServiceRequest + class linkConnectionServiceRequestHistoryRecord + class linkConnectionServiceModifyRequest + class LCS_service_request_fragment [LCS service request fragment] + class currentLcsRequest + class lcsRequestHistoryRecord + class lcsModifyRequest + class transport_service_request_fragment [transport service request fragment] + class serviceAccessGroup + class serviceAccessDomain + class transportService + class lcs + class linkConnectionService + class resource_fragment [resource fragment] + class serviceAccessEquipment + class networkR1_M3100 [networkR1 (M.3100)] + + top_X721_top --- Generic_service_request_fragment + top_X721_top --- Account_X790 + top_X721_top --- Link_connection_service_request_fragment + top_X721_top --- LCS_service_request_fragment + top_X721_top --- transport_service_request_fragment + top_X721_top --- resource_fragment + + Generic_service_request_fragment --- currentServiceRequest + Generic_service_request_fragment --- serviceRequestHistoryRecord + Generic_service_request_fragment --- serviceModifyRequest + + Link_connection_service_request_fragment --- currentLinkConnectionServiceRequest + Link_connection_service_request_fragment --- linkConnectionServiceRequestHistoryRecord + Link_connection_service_request_fragment --- linkConnectionServiceModifyRequest + + LCS_service_request_fragment --- currentLcsRequest + LCS_service_request_fragment --- lcsRequestHistoryRecord + LCS_service_request_fragment --- lcsModifyRequest + + transport_service_request_fragment --- serviceAccessGroup + transport_service_request_fragment --- serviceAccessDomain + transport_service_request_fragment --- transportService + transport_service_request_fragment --- lcs + transport_service_request_fragment --- linkConnectionService + + resource_fragment --- serviceAccessEquipment + resource_fragment --- networkR1_M3100 + +``` + +UML class diagram showing inheritance relationships between service request fragments and resource fragments. The diagram is structured into three main horizontal sections. The top section, labeled 'top (X.721)', contains three gray boxes: 'Generic service request fragment' (with sub-classes 'currentServiceRequest', 'serviceRequestHistoryRecord', and 'serviceModifyRequest'), 'Link connection service request fragment' (with sub-classes 'currentLinkConnectionServiceRequest', 'linkConnectionServiceRequestHistoryRecord', and 'linkConnectionServiceModifyRequest'), and 'LCS service request fragment' (with sub-classes 'currentLcsRequest', 'lcsRequestHistoryRecord', and 'lcsModifyRequest'). A separate box labeled 'Account (X.790)' is also in this section. The bottom section contains two gray boxes: 'transport service request fragment' (with sub-classes 'serviceAccessGroup', 'serviceAccessDomain', 'transportService', 'lcs', and 'linkConnectionService') and 'resource fragment' (with sub-classes 'serviceAccessEquipment' and 'networkR1 (M.3100)'). Lines connect the sub-classes to their parent fragments and to the 'top (X.721)' box. + +T0410050-98 + +**Figure 5-1/M.3108.1 – Inheritance** + +![Containment diagram for networkR1 (M.3100) and account (X.790) showing various managed objects and their relationships.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +graph TD + networkR1["networkR1 (M.3100)"] + account["account (X.790)"] + currentLCSRequest["currentLCSRequest"] + currentLinkConnectionServiceRequest["currentLinkConnectionService Request"] + serviceAccessEquipment["serviceAccess Equipment"] + linkConnectionService["LinkConnection Service"] + lcs["lcs"] + lcsRequestHistoryRecord["lcsRequestHistory Record"] + linkConnectionServiceRequestHistoryRecord["LinkConnectionService RequestHistoryRecord"] + linkConnectionServiceModifyRequest["LinkConnectionService ModifyRequest"] + serviceAccessDomain["serviceAccessDomain"] + lcsModifyRequest["lcsModifyRequest"] + serviceAccessGroup["serviceAccessGroup"] + otherMOs["other MOs describing resources and defined elsewhere"] + + networkR1 --> account + account --> currentLCSRequest + account --> currentLinkConnectionServiceRequest + account --> serviceAccessEquipment + account --> linkConnectionService + account --> lcs + currentLCSRequest --> lcsRequestHistoryRecord + currentLinkConnectionServiceRequest --> linkConnectionServiceRequestHistoryRecord + linkConnectionService --> linkConnectionServiceModifyRequest + lcs --> lcsModifyRequest + serviceAccessGroup --> serviceAccessDomain + serviceAccessDomain --> account + otherMOs -.-> networkR1 + otherMOs -.-> account + +``` + +T0410060-98 + +Containment diagram for networkR1 (M.3100) and account (X.790) showing various managed objects and their relationships. + +**Figure 5-2/M.3108.1 – Containment** + +# 6 Information model + +This clause provides the information model for the management of LCS using GDMO. + +The objects are grouped by fragment. + +## 6.1 Managed objects for generic service request fragment + +### 6.1.1 currentServiceRequest + +``` + +currentServiceRequest MANAGED OBJECT CLASS + DERIVED FROM "Rec. X.721|ISO/IEC 10165-2:1992":top; + CHARACTERIZED BY + serviceRequestPackage PACKAGE + BEHAVIOUR + currentServiceRequestBehaviour BEHAVIOUR + DEFINED AS + +``` + +"The currentServiceRequest MO class represents information elements that are common to all service requests and captures the current value of a service request. It is a superclass from which service-specific subclasses can be defined. + +This MO represents the current view of the values of the service request that the SP will process on behalf of the SC. They may be different from the values requested by the SC due to the availability or lack thereof of SP's resources. + +The updateServiceRequest action can be used by the service customer to modify the service request following creation of this object class (or subclasses). The following attributes specified in this object class can be modified by the updateServiceRequest action: + +- serviceCustomer contact; +- serviceAvailabilityDate; +- serviceTerminationDate; +- initialServiceAdministrativeState; +- aliasName; +- intervalsOfDay; +- weekMask. + +Subclasses of this object class can specify additional attributes that can be modified by the updateServiceRequest action. + +It is the responsibility of the SC to check the values of the attributes in the create notification and attribute value change notification emitted by this MO. If the values of any attributes in the notifications are different from those supplied by the SC, and if they are unacceptable to the SC, then the SC may cancel the service request by deleting this object. + +If the history of the requested values is to be kept by the SP, then a serviceRequestHistoryRecord is created when the service customer issues an updateServiceRequest action towards a currentServiceRequest (and subclasses); the serviceRequestHistoryRecord contains a record of the attribute values specified in the request. The SP also creates a serviceRequestHistoryRecord of the initial service request values (when the SC creates the currentServiceRequest).";; + +#### ATTRIBUTES + +| | | | +|--------------------------|--------------------|------------------------------------| +| providerRequestNumber | GET, | -- used as naming attribute | +| requestSequenceNumber | GET, | | +| requestReceptionTime | GET, | | +| "Rec. X.790":serviceType | GET SET-BY-CREATE, | | +| serviceProviderContact | GET, | | +| serviceCustomerContact | GET SET-BY-CREATE, | | +| serviceAvailabilityDate | GET SET-BY-CREATE, | | +| serviceTerminationDate | GET SET-BY-CREATE, | | +| serviceRequestState | GET; | | + +*-- this attribute represents the service request state* + +*-- defined in Rec. M.3208.1 and behaves according to the* + +*-- state model* + +##### ACTIONS + +updateServiceRequest; + +#### NOTIFICATIONS + +"Rec.X.721 | ISO/IEC 10165-2:1992": attributeValueChange, + +"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion;;; + +#### CONDITIONAL PACKAGES + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| initialServiceAdministrativeStatePackage | PRESENT IF "SLA supports it", | +| serviceDescriptionPackage | PRESENT IF "SLA supports it", | +| -- represents the service class in Rec. M.3208.1 | | +| customerRequestNumberPackage | PRESENT IF "SC provides it", | +| aliasNamePackage | PRESENT IF "SLA supports it", | +| "Rec. X.721":availabilityStatus | PRESENT IF "Any scheduling (daily, weekly, external) is present", | +| dailySchedulingCurrentPackage | | +| PRESENT IF "both the weekly scheduling current package and external scheduler current packages are not present and daily scheduling is supported for the requested service", | | +| weeklySchedulingCurrentPackage | | +| PRESENT IF "both the daily scheduling current package and external scheduler current packages are not present and weekly scheduling is supported for the requested service", | | +| externalSchedulerCurrentPackage | | +| PRESENT IF "both the daily scheduling current package and weekly scheduling current packages are not present and external scheduling is supported for the requested service"; | | + +REGISTERED AS {m3108Part1ObjectClass 1}; + +### 6.1.2 serviceRequestHistoryRecord + +serviceRequestHistoryRecord MANAGED OBJECT CLASS +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +serviceRequestHistoryRecordPackage PACKAGE +BEHAVIOUR +serviceRequestRecordBehaviour BEHAVIOUR +DEFINED AS +"This MO represents a history record of the content of a service (update) request by the SC to a service request. The serviceRequestHistoryRecord is created when the service customer issues an updateServiceRequest action towards a currentServiceRequest (and subclasses) and contains a record of the attribute values specified in the request. The service provider also creates a serviceRequestHistoryRecord of the initial service request values (when the SC creates the currentServiceRequest).";; +ATTRIBUTES +requestSequenceNumber GET, -- used as naming attribute +requestReceptionTime GET; +NOTIFICATIONS +"Rec.X.721 | ISO/IEC 10165-2:1992": objectCreation, +"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion;;; +CONDITIONAL PACKAGES +aliasNameInfoPackage PRESENT IF "part of the service (update) request", +dailySchedulingInfoPackage PRESENT IF "part of the service (update) request", +externalSchedulerInfoPackage PRESENT IF "part of the service (update) request", +initialServiceAdministrativeStateInfoPackage +PRESENT IF "part of the service (update) request", +serviceAvailabilityDateInfoPackage PRESENT IF "part of the service (update) request", +serviceCustomerContactPackage PRESENT IF "part of the service (update) request", +serviceDescriptionInfoPackage PRESENT IF "part of the service (update) request", +serviceTypeInfoPackage PRESENT IF "part of the service (update) request", +serviceTerminationDateInfoPackage PRESENT IF "part of the service (update) request", +weeklySchedulingInfoPackage PRESENT IF "part of the service (update) request";; +REGISTERED AS {m3108Part1ObjectClass 2}; + +### 6.1.3 serviceModifyRequest + +serviceModifyRequest MANAGED OBJECT CLASS +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +serviceModifyRequestPackage PACKAGE +BEHAVIOUR +serviceModifyRequestBehaviour BEHAVIOUR +DEFINED AS "This MO represents SC's request to modify an existing service. It is a superclass from which service-specific subclasses are derived. When changes to the service occur as a result of such a modification request, or for any other reason, the MO representing the affected service (e.g. lcs or link connection service) will issue the appropriate attribute value change notifications. After all the modifications requested by the SC through this MO have been resolved, this MO instance will be deleted and a notification of its deletion shall be sent to the SC.";; +ATTRIBUTES +providerRequestNumber GET, -- used as naming attribute +serviceRequestState GET, +serviceInstance GET SET-BY-CREATE, +requestReceptionTime GET; +NOTIFICATIONS +"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion, +"Rec.X.721 | ISO/IEC 10165-2:1992": objectCreation;;; +CONDITIONAL PACKAGES +aliasNamePackage +PRESENT IF "SLA supports it", + +``` + +"Rec. X.721":availabilityStatus PRESENT IF "Any scheduling (daily, weekly, external) is + present", +dailySchedulingCurrentPackage + PRESENT IF "both the weekly scheduling current package and external scheduler current packages are not + present and daily scheduling is supported for the requested service", +externalSchedulerCurrentPackage + PRESENT IF "both the daily scheduling current package and weekly scheduling current packages are not + present and external scheduling is supported for the requested service", +serviceCustomerContactPackage + PRESENT IF "SLA supports it", +weeklySchedulingCurrentPackage + PRESENT IF "both the daily scheduling current package and external scheduler current packages are not + present and weekly scheduling is supported for the requested service"; +REGISTERED AS {m3108Part1ObjectClass 3}; + +``` + +## 6.2 Managed objects for LCS request fragment + +### 6.2.1 currentLcsRequest + +``` + +currentLcsRequest MANAGED OBJECT CLASS +DERIVED FROM currentServiceRequest; +CHARACTERIZED BY + currentLcsRequestPackage PACKAGE + BEHAVIOUR + currentLcsRequestBehaviour BEHAVIOUR + DEFINED AS "This MO represents the LCS the SC currently wants, as per the SC's create service request + and subsequent updates related to that create service request.";; + ATTRIBUTES + originatingLocation GET SET-BY-CREATE, + terminatingLocation GET SET-BY-CREATE; + ACTIONS + updateServiceRequest + bandwidthUnavailable + modifyLCSError + resourcesUnavailable; + NOTIFICATIONS + lcsRequestProgressProblemReport;; + -- used to report problems in progressing the request. + -- changes in the value of the serviceRequestState are + -- reported using the attribute value change notification. + CONDITIONAL PACKAGES + quantityPackage PRESENT IF "SLA supports it", + bandwidthPackage PRESENT IF "SLA supports it", + diversityPackage PRESENT IF "SLA supports it", + routePackage PRESENT IF "SLA supports it", + originatingLocationCPEPackage PRESENT IF "SLA supports it", + terminatingLocationCPEPackage PRESENT IF "SLA supports it", + originatingLocationSapPackage PRESENT IF "SLA supports it", + terminatingLocationSapPackage PRESENT IF "SLA supports it"; +REGISTERED AS {m3108Part1ObjectClass 4}; + +``` + +### 6.2.2 lcsRequestHistoryRecord + +``` + +lcsRequestHistoryRecord MANAGED OBJECT CLASS +DERIVED FROM serviceRequestHistoryRecord; +CHARACTERIZED BY + lcsRequestHistoryRecordPackage PACKAGE + BEHAVIOUR + lcsRequestHistoryRecordBehaviour BEHAVIOUR + +``` + +DEFINED AS "This MO represents a record of the attributes of a create or update request of a LCS.";;; + +#### **CONDITIONAL PACKAGES** + +| | | +|-----------------------------------|----------------------------------------------------| +| originatingLocationInfoPackage | PRESENT IF "part of the service (update) request", | +| terminatingLocationInfoPackage | PRESENT IF "part of the service (update) request", | +| quantityInfoPackage | PRESENT IF "part of the service (update) request", | +| bandwidthInfoPackage | PRESENT IF "part of the service (update) request", | +| diversityInfoPackage | PRESENT IF "part of the service (update) request", | +| routeInfoPackage | PRESENT IF "part of the service (update) request", | +| originatingLocationCPEInfoPackage | PRESENT IF "part of the service (update) request", | +| terminatingLocationCPEInfoPackage | PRESENT IF "part of the service (update) request", | +| originatingLocationSapInfoPackage | PRESENT IF "part of the service (update) request", | +| terminatingLocationSapInfoPackage | PRESENT IF "part of the service (update) request"; | + +REGISTERED AS {m3108Part1ObjectClass 5}; + +### 6.2.3 lcsModifyRequest + +lcsModifyRequest MANAGED OBJECT CLASS + +DERIVED FROM serviceModifyRequest; + +CHARACTERIZED BY + +lcsModifyRequestPackage PACKAGE + +BEHAVIOUR + +lcsModifyRequestBehaviour BEHAVIOUR + +DEFINED AS "This MO represents a request to modify an existing LCS service or a previous modify against an LCS.";; + +NOTIFICATIONS + +lcsModifyProgressProblemReport;; + +-- used to report problems in progressing the request. + +-- changes in the value of the serviceRequestState are + +-- reported using the attribute value change notification. + +#### **CONDITIONAL PACKAGES** + +| | | +|-------------------------------|-------------------------------| +| bandwidthPackage | PRESENT IF "SLA supports it", | +| diversityPackage | PRESENT IF "SLA supports it", | +| routePackage | PRESENT IF "SLA supports it", | +| originatingLocationCPEPackage | PRESENT IF "SLA supports it", | +| terminatingLocationCPEPackage | PRESENT IF "SLA supports it"; | + +REGISTERED AS {m3108Part1ObjectClass 6}; + +## 6.3 Managed objects for link connection service request fragment + +### 6.3.1 currentLinkConnectionServiceRequest + +currentLinkConnectionServiceRequest MANAGED OBJECT CLASS + +DERIVED FROM currentServiceRequest; + +CHARACTERIZED BY + +currentLinkConnectionServiceRequestPackage PACKAGE + +BEHAVIOUR + +currentLinkConnectionServiceRequestBehaviour BEHAVIOUR + +DEFINED AS "This instantiable MO represents a SC's request for a link connection service. + +The following attributes specified by this object class (in addition to those inherited from currentServiceRequest) can be modified by the service customer using the updateServiceRequest action: + +- bandwidth +- originatingLocationCP +- terminationLocationCP + +The SC must provide either the Originating or Terminating Location Connection Point or both. If one of the points is at the customer premises, that point must be provided by the SC. If one of the points is in a network of a service provider other than the one receiving create request, it must be provided by the SC.";; + +#### ATTRIBUTES + +originatingLocationCP GET SET-BY-CREATE, +terminatingLocationCP GET SET-BY-CREATE; + +##### ACTIONS + +updateServiceRequest +    bandwidthUnavailable -- *specific action reply parameter values* +    resourcesUnavailable; + +#### NOTIFICATIONS + +linkConnectionRequestProgressProblemReport;;; +    -- *used to report problems in progressing the request.* +    -- *changes in the value of the serviceRequestState are* +    -- *reported using the attribute value change notification.* + +#### CONDITIONAL PACKAGES + +bandwidthPackage PRESENT IF "SLA supports it"; +REGISTERED AS {m3108Part1ObjectClass 7}; + +### 6.3.2 linkConnectionServiceRequestHistoryRecord + +linkConnectionServiceRequestHistoryRecord MANAGED OBJECT CLASS + +DERIVED FROM serviceRequestHistoryRecord; + +#### CHARACTERIZED BY + +linkConnectionServiceRequestHistoryRecordPackage PACKAGE + +#### BEHAVIOUR + +linkConnectionServiceRequestHistoryRecordBehaviour + +BEHAVIOUR DEFINED AS "This MO represents a request to update either a previously issued request to create a link connection service, or a previous update against that link connection service request.";;; + +#### CONDITIONAL PACKAGES + +bandwidthInfoPackage PRESENT IF "part of the service (update) request", +originatingLocationCPInfoPackage PRESENT IF "part of the service (update) request", +terminatingLocationCPInfoPackage PRESENT IF "part of the service (update) request"; + +REGISTERED AS {m3108Part1ObjectClass 8}; + +### 6.3.3 linkConnectionServiceModifyRequest + +linkConnectionServiceModifyRequest MANAGED OBJECT CLASS + +DERIVED FROM serviceModifyRequest; + +#### CHARACTERIZED BY + +linkConnectionServiceModifyRequestPackage PACKAGE + +#### BEHAVIOUR + +linkConnectionServiceModifyRequestBehaviour BEHAVIOUR + +DEFINED AS "This MO represents a request to modify an existing link connection service or a previous modify against a link.";;; + +#### NOTIFICATIONS + +linkConnectionModifyProgressProblemReport;;; + +#### CONDITIONAL PACKAGES + +bandwidthPackage PRESENT IF "SLA supports it"; + +REGISTERED AS {m3108Part1ObjectClass 9}; + +## 6.4 Managed objects for service fragment + +### 6.4.1 Transport service + +transportService MANAGED OBJECT CLASS + +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; + +#### CHARACTERIZED BY + +"Rec. M.3100:1995":administrativeOperationalStatesPackage, +"Rec. M.3100:1995":stateChangeNotificationPackage, +"Rec. M.3100:1995":createDeleteNotificationsPackage, +"Rec. M.3100:1995":attributeValueChangeNotificationPackage, + +``` + +transportServicePackage PACKAGE + BEHAVIOUR + transportServiceBehaviour BEHAVIOUR + DEFINED AS "This MO represents a transport service. This MO class cannot be instantiated; service- + specific subclasses of this class can be instantiated. Values of attributes of subclasses of this MO class + can be set through management operations or through the creation of an instance of a service-specific + subclass of the serviceModifyRequest MO class. If an attribute is supported by the SLA, and it can be + set by the SC, and the SC has not specified its value in the service request, then it shall have its default + value when this MO is instantiated.";; + ATTRIBUTES + "Rec. X.790":serviceID GET SET-BY-CREATE, + -- represents the circuit ID or link connection ID specified in Rec. M.3208.1 + -- the serviceID is used for naming + serviceTerminationDate GET-REPLACE, + bandwidth GET-REPLACE, + serviceProviderContact GET, + -- the value of this attribute is set at creation by the SP + -- this attribute points to an instance of X.790 contact MO + -- or it contains X.790 PersonReach information. + serviceCustomerContact GET-REPLACE; + -- this attribute points to an instance of X.790 contact MO + -- or it contains X.790 PersonReach information. + NOTIFICATIONS + "Rec. X.721 | ISO/IEC 10165-2": qualityOfServiceAlarm;; + CONDITIONAL PACKAGES + aliasNamePackage PRESENT IF "SLA supports it", + serviceDescriptionPackage PRESENT IF "present in the service request", + -- represents the service class in Rec. M.3208.1 + "Rec. X.721":availabilityStatus PRESENT IF "Any scheduling (daily, weekly, external) is + present", + "Rec. X.721 | ISO/IEC 10165-2":dailyScheduling + PRESENT IF "present in the service request.", + "Rec. X.721 | ISO/IEC 10165-2":weeklyScheduling + PRESENT IF " present in the service request ", + "Rec. X.721 | ISO/IEC 10165-2":externalScheduler + PRESENT IF " present in the service request "; + REGISTERED AS {m3108Part1ObjectClass 10}; + +``` + +### 6.4.2 lcs + +``` + +lcs MANAGED OBJECT CLASS + DERIVED FROM transportService; + CHARACTERIZED BY + lcsPackage PACKAGE + BEHAVIOUR + lcsBehaviour BEHAVIOUR + DEFINED AS "This instantiable MO represents a LCS. If the SLA allows the SC to specify the route + and the SC did not specify the route in the service request, then the route attribute shall be present as + an empty SEQUENCE. The route cannot be changed through a management operation on this MO. + The route can be changed by the SC by creating an instance of the lcsModifyRequest MO class.";; + ATTRIBUTES + originatingLocationSap GET SET-BY-CREATE, + "Rec. X.790":serviceType GET SET-BY-CREATE, + -- represents the service name in Rec. M.3208.1 + "Rec. X.790":serviceLocationList GET SET-BY-CREATE, + -- represents the originating and terminating + -- locations in Rec. M.3208.1 + serviceAvailabilityDate GET SET-BY-CREATE, + terminatingLocationSap GET SET-BY-CREATE;; + +``` + +#### CONDITIONAL PACKAGES + +| | | +|-------------------------------------|-------------------------------------------------------------------------| +| diversityPackage | PRESENT IF "present in the service request", | +| routePackage | PRESENT IF "route was present in the service request", | +| originatingLocationCPEModifyPackage | PRESENT IF "originatingLocationCPE was present in the service request", | +| terminatingLocationCPEModifyPackage | PRESENT IF "terminatingLocationCPE was present in the service request"; | + +REGISTERED AS {m3108Part1ObjectClass 11}; + +### 6.4.3 linkConnectionService + +linkConnectionService MANAGED OBJECT CLASS + +DERIVED FROM transportService; + +CHARACTERIZED BY + +linkConnectionServicePackage PACKAGE + +BEHAVIOUR + +linkConnectionServiceBehaviour BEHAVIOUR + +DEFINED AS "This instantiable MO represents a link connection service.";; + +ATTRIBUTES + +| | | +|--------------------------------------------------------|----------------------| +| originatingLocationCP | GET SET-BY-CREATE, | +| "Rec. X.790":serviceType | GET SET-BY-CREATE, | +| -- represents the service name in Rec. M.3208.1 | | +| "Rec. X.790":serviceLocationList | GET SET-BY-CREATE, | +| -- represents the originating and terminating | | +| -- locations in Rec. M.3208.1 | | +| serviceAvailabilityDate | GET SET-BY-CREATE, | +| terminatingLocationCP | GET SET-BY-CREATE;;; | + +REGISTERED AS {m3108Part1ObjectClass 12}; + +### 6.4.4 Service Access Domain + +serviceAccessDomain MANAGED OBJECT CLASS + +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; + +CHARACTERIZED BY + +serviceAccessDomainPackage PACKAGE + +BEHAVIOUR + +serviceAccessDomainBehaviour BEHAVIOUR + +DEFINED AS "This MO represents a Service Access Domain consisting of Service Access Groups having similar characteristics (e.g. supporting the same bandwidths). Although Rec. M.3208.1 specifies that a provider request number be provided by the SP, it is not included in this MO since this MO is created directly by the SC.";; + +ATTRIBUTES + +| | | +|------------------------|--------------------| +| providerRequestNumber | GET, | +| serviceCustomerContact | GET-REPLACE, | +| sadId | GET SET-BY-CREATE, | + +*-- sadId can be provided by the SC, otherwise it is set by the SP; used as naming attribute* + +| | | +|--------------------------|-------------------------| +| listOfSags | GET-REPLACE ADD-REMOVE, | +| "Rec. X.790":serviceType | GET SET-BY-CREATE, | +| serviceProviderContact | GET; | + +NOTIFICATIONS + +| | | +|------------------------------------------------------|--| +| "Rec.X.721 ISO/IEC 10165-2:1992":objectDeletion, | | +| "Rec.X.721 ISO/IEC 10165-2:1992":objectCreation;;; | | + +CONDITIONAL PACKAGES + +| | | +|---------------------------|---------------------------------------------------------------------| +| aliasNamePackage | PRESENT IF "aliasName was present in the service request", | +| serviceDescriptionPackage | PRESENT IF "serviceDescription was present in the service request"; | + +REGISTERED AS {m3108Part1ObjectClass 13}; + +### 6.4.5 Service Access Group + +serviceAccessGroup MANAGED OBJECT CLASS +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +serviceAccessGroupPackage PACKAGE +BEHAVIOUR +serviceAccessGroupBehaviour BEHAVIOUR +DEFINED AS "This MO represents a Service Access Group consisting of Service Access Points having similar characteristics (e.g. supporting the same bandwidths). If the administrative state is locked, then all the SAPs in the SAG are locked";; +ATTRIBUTES +sagId GET SET-BY-CREATE, +listOfSaps GET-REPLACE ADD-REMOVE +addToSagError +removeFromSagError, +sagLocation GET SET-BY-CREATE; +ACTIONS +addSapsToSag; +NOTIFICATIONS +"Rec.X.721 | ISO/IEC 10165-2:1992":objectDeletion, +"Rec.X.721 | ISO/IEC 10165-2:1992":objectCreation;;; +CONDITIONAL PACKAGES +aliasNamePackage PRESENT IF "aliasName was present in the service request", +"Rec. X.721 | ISO/IEC 10165-2:1992":administrativeStatePackage +PRESENT IF "SLA supports it", +REGISTERED AS {m3108Part1ObjectClass 14}; + +## 6.5 Managed objects for resource fragment + +### 6.5.1 Service Access Equipment + +serviceAccessEquipmentView MANAGED OBJECT CLASS +DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top; +CHARACTERIZED BY +serviceAccessEquipmentViewPackage PACKAGE +BEHAVIOUR +serviceAccessEquipmentViewBehaviour BEHAVIOUR +DEFINED AS "The serviceAccessEquipment MO class represents customer-owned equipment that terminates LCS(s). The SC updates information in this MO to correctly reflect the actual state of the service access equipment in the SC's premises.";; +ATTRIBUTES +"Rec. M3100:1995": equipmentId GET SET-BY-CREATE, +listOfSaps GET-REPLACE ADD-REMOVE, +"Rec. X.790:1995": locationAddress GET SET-BY-CREATE; +NOTIFICATIONS +"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion, +"Rec.X.721 | ISO/IEC 10165-2:1992": objectCreation;;; +CONDITIONAL PACKAGES +reflectiveAdministrativeStatePackage +PRESENT IF "SLA supports it", +reflectiveOperationalStatePackage +PRESENT IF "SLA supports it", +equipmentTypePackage +PRESENT IF "SLA supports it", +equipmentManufacturerPackage +PRESENT IF "SLA supports it", +modelTypePackage +PRESENT IF "SLA supports it", + +``` + +dateOfInstallationPackage + PRESENT IF "SLA supports it", +expectedDateOfInstallationPackage + PRESENT IF "SLA supports it", +procedurePackage + PRESENT IF "SLA supports it"; +REGISTERED AS {m3108Part1ObjectClass 15}; + +``` + +## 6.6 Packages + +### 6.6.1 aliasNameInfoPackage + +``` + +aliasNameInfoPackage PACKAGE + ATTRIBUTES + aliasName GET; +REGISTERED AS {m3108Part1Package 1}; + +``` + +### 6.6.2 aliasNamePackage + +``` + +aliasNamePackage PACKAGE + ATTRIBUTES + aliasName GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 2}; + +``` + +### 6.6.3 bandwidthInfoPackage + +``` + +bandwidthInfoPackage PACKAGE + ATTRIBUTES + bandwidth GET; +REGISTERED AS {m3108Part1Package 3}; + +``` + +### 6.6.4 bandwidthPackage + +``` + +bandwidthPackage PACKAGE + BEHAVIOUR + bandwidthPackageBehaviour BEHAVIOUR + DEFINED AS "If the requested bandwidth cannot be provided by the SP, the SP shall return the value together + with a reason code indicating that the bandwidth is not available.";; + ATTRIBUTES + bandwidth GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 4}; + +``` + +### 6.6.5 customerRequestNumberPackage + +``` + +customerRequestNumberPackage PACKAGE + ATTRIBUTES + customerRequestNumber GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 7}; + +``` + +### 6.6.6 dateOfInstallationPackage + +``` + +dateOfInstallationPackage PACKAGE + ATTRIBUTES + dateOfInstallation GET; +REGISTERED AS {m3108Part1Package 8}; + +``` + +### **6.6.7 dailySchedulingInfoPackage** + +dailySchedulingInfoPackage PACKAGE +ATTRIBUTES +"Rec. X.721 | ISO/IEC 10165-2":intervalsOfDay GET; +REGISTERED AS {m3108Part1Package 9}; + +### **6.6.8 dailySchedulingCurrentPackage** + +dailySchedulingCurrentPackage PACKAGE +BEHAVIOUR +dailySchedulingCurrentPackageBehaviour BEHAVIOUR +DEFINED AS "If the SC specifies a value and the SP is not able to accommodate the requested schedule, the SP must return an error with a reason code indicating that the schedule can not be met.";; +ATTRIBUTES +"Rec. X.721 | ISO/IEC 10165-2":intervalsOfDay +GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 10}; + +#### **6.6.9 diversityInfoPackage** + +diversityInfoPackage PACKAGE +ATTRIBUTES +diversity GET; +REGISTERED AS {m3108Part1Package 11}; + +### **6.6.10 diversityPackage** + +diversityPackage PACKAGE +BEHAVIOUR +diversityPackageBehaviour BEHAVIOUR +DEFINED AS "In the case of partial success, the SP may indicate the common (i.e. non-diverse) components of the circuits (new and/or old) as a set of topological entities.";; +ATTRIBUTES +diversity GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 12}; + +### **6.6.11 equipmentManufacturerPackage** + +equipmentManufacturerPackage PACKAGE +ATTRIBUTES +equipmentManufacturer GET-REPLACE; +REGISTERED AS {m3108Part1Package 14}; + +### **6.6.12 equipmentTypePackage** + +equipmentTypePackage PACKAGE +ATTRIBUTES +equipmentType GET-REPLACE; +REGISTERED AS {m3108Part1Package 16}; + +### **6.6.13 expectedDateOfInstallationInfoPackage** + +expectedDateOfInstallationInfoPackage PACKAGE +ATTRIBUTES +expectedDateOfInstallation GET; +REGISTERED AS {m3108Part1Package 17}; + +### **6.6.14 expectedDateOfInstallationPackage** + +expectedDateOfInstallationPackage PACKAGE +ATTRIBUTES +    expectedDateOfInstallation    GET-REPLACE; +REGISTERED AS {m3108Part1Package 18}; + +#### **6.6.15 externalSchedulerCurrentPackage** + +externalSchedulerCurrentPackage PACKAGE +ATTRIBUTES +    "Rec. X.721 | ISO/IEC 10165-2":schedulerName    GET-REPLACE; +REGISTERED AS {m3108Part1Package 19}; + +### **6.6.16 externalSchedulerInfoPackage** + +externalSchedulerInfoPackage PACKAGE +ATTRIBUTES +    "Rec. X.721 | ISO/IEC 10165-2":schedulerName    GET; +REGISTERED AS {m3108Part1Package 20}; + +### **6.6.17 initialServiceAdministrativeStateInfoPackage** + +initialServiceAdministrativeStateInfoPackage PACKAGE +ATTRIBUTES +    requestedInitialServiceAdministrativeState    GET; +REGISTERED AS {m3108Part1Package 21}; + +### **6.6.18 initialServiceAdministrativeStatePackage** + +initialServiceAdministrativeStatePackage PACKAGE +BEHAVIOUR +    initialServiceAdministrativeStateBehaviour    BEHAVIOUR +        DEFINED AS "If this package is not present then the value of the service, when created, is subject to the SLA.";; +ATTRIBUTES +    requestedInitialServiceAdministrativeState +        GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 22}; + +#### **6.6.19 modelTypePackage** + +modelTypePackage PACKAGE +ATTRIBUTES +    modelType    GET-REPLACE; +REGISTERED AS {m3108Part1Package 23}; + +#### **6.6.20 originatingLocationCPEInfoPackage** + +originatingLocationCPEInfoPackage PACKAGE +ATTRIBUTES +    originatingLocationCPE    GET; +REGISTERED AS {m3108Part1Package 25}; + +#### **6.6.21 originatingLocationCPEModifyPackage** + +originatingLocationCPEModifyPackage PACKAGE +ATTRIBUTES +    originatingLocationCPE    GET-REPLACE; +REGISTERED AS {m3108Part1Package 26}; + +#### **6.6.22 originatingLocationCPEPackage** + +originatingLocationCPEPackage PACKAGE +ATTRIBUTES +    originatingLocationCPE            GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 27}; + +#### **6.6.23 originatingLocationCPInfoPackage** + +originatingLocationCPInfoPackage PACKAGE +ATTRIBUTES +    originatingLocationCP            GET; +REGISTERED AS {m3108Part1Package 28}; + +#### **6.6.24 originatingLocationInfoPackage** + +originatingLocationInfoPackage PACKAGE +ATTRIBUTES +    originatingLocation                GET; +REGISTERED AS {m3108Part1Package 30}; + +#### **6.6.25 originatingLocationSapInfoPackage** + +originatingLocationSapInfoPackage PACKAGE +ATTRIBUTES +    originatingLocationSap            GET; +REGISTERED AS {m3108Part1Package 31}; + +#### **6.6.26 originatingLocationSapPackage** + +originatingLocationSapPackage PACKAGE +ATTRIBUTES +    originatingLocationSap            GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 32}; + +#### **6.6.27 procedurePackage** + +procedurePackage PACKAGE +ATTRIBUTES +    procedure                            GET-REPLACE; +REGISTERED AS {m3108Part1Package 33}; + +#### **6.6.28 quantityInfoPackage** + +quantityInfoPackage PACKAGE +ATTRIBUTES +    quantity                            GET; +REGISTERED AS {m3108Part1Package 35}; + +#### **6.6.29 quantityPackage** + +quantityPackage PACKAGE +ATTRIBUTES +    quantity                            GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 36}; + +#### **6.6.30 reflectiveOperationalStatePackage** + +reflectiveOperationalStatePackage PACKAGE +ATTRIBUTES +"Rec.X.721 | ISO/IEC 10165-2:1992":operationalState GET-REPLACE; +REGISTERED AS { m3108Part1Package 37}; + +#### **6.6.31 reflectiveAdministrativeStatePackage** + +reflectiveAdministrativeStatePackage PACKAGE +ATTRIBUTES +"Rec.X.721 | ISO/IEC 10165-2:1992":administrativeState GET-REPLACE; +REGISTERED AS { m3108Part1Package 38}; + +#### **6.6.32 routeInfoPackage** + +routeInfoPackage PACKAGE +ATTRIBUTES +route GET; +REGISTERED AS {m3108Part1Package 39}; + +### **6.6.33 routePackage** + +routePackage PACKAGE +BEHAVIOUR +routePackageBehaviour BEHAVIOUR +DEFINED AS "The SP may reject the requested route with returning the reason code or may return alternate route when the requested route is not available.":: +ATTRIBUTES +route GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 40}; + +#### **6.6.34 serviceAdministrativeStatePackage** + +serviceAdministrativeStatePackage PACKAGE +ATTRIBUTES +"Rec.X.721 | ISO/IEC 10164-2":administrativeState GET-REPLACE; +REGISTERED AS {m3108Part1Package 41}; + +#### **6.6.35 serviceAvailabilityDateInfoPackage** + +serviceAvailabilityDateInfoPackage PACKAGE +ATTRIBUTES +serviceAvailabilityDate GET; +REGISTERED AS {m3108Part1Package 42}; + +#### **6.6.36 serviceAvailabilityDatePackage** + +serviceAvailabilityDatePackage PACKAGE +BEHAVIOUR +serviceAvailabilityDatePackageBehaviour BEHAVIOUR +DEFINED AS "The Service Availability Date can be modified only if the service has not been established.":: +ATTRIBUTES +serviceAvailabilityDate GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 43}; + +#### **6.6.37 serviceCustomerContactPackage** + +serviceCustomerContactPackage PACKAGE +ATTRIBUTES +    serviceCustomerContact            GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 45}; + +#### **6.6.38 serviceDescriptionInfoPackage** + +serviceDescriptionInfoPackage PACKAGE +ATTRIBUTES +    "Rec. X.790":serviceDescription            GET; +REGISTERED AS {m3108Part1Package 46}; + +#### **6.6.39 serviceDescriptionPackage** + +serviceDescriptionPackage PACKAGE +BEHAVIOUR +    serviceDescriptionPackageBehaviour BEHAVIOUR +        DEFINED AS "If the requested service class is not equal to the class of service provided by the SP, then the SP +        must supply the value, else it is optional.";; +ATTRIBUTES +    "Rec. X.790":serviceDescription            GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 47}; + +#### **6.6.40 serviceProviderContactPackage** + +serviceProviderContactPackage PACKAGE +ATTRIBUTES +    serviceProviderContact            GET; +REGISTERED AS {m3108Part1Package 48}; + +#### **6.6.41 serviceTerminationDateInfoPackage** + +serviceTerminationDateInfoPackage PACKAGE +ATTRIBUTES +    serviceTerminationDate            GET; +REGISTERED AS {m3108Part1Package 49}; + +#### **6.6.42 serviceTerminationDatePackage** + +serviceTerminationDatePackage PACKAGE +BEHAVIOUR +    serviceTerminationDatePackageBehaviour BEHAVIOUR +        DEFINED AS "If the SP cannot accept the date, an alternate date is provided.";; +ATTRIBUTES +    serviceTerminationDate            GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 50}; + +#### **6.6.43 serviceTypeInfoPackage** + +serviceTypeInfoPackage PACKAGE +ATTRIBUTES +    "Rec. X.790":serviceType            GET; +REGISTERED AS {m3108Part1Package 51}; + +#### **6.6.44 terminatingLocationCPEInfoPackage** + +terminatingLocationCPEInfoPackage PACKAGE +ATTRIBUTES +terminatingLocationCPE GET; +REGISTERED AS {m3108Part1Package 52}; + +#### **6.6.45 terminatingLocationCPEModifyPackage** + +terminatingLocationCPEModifyPackage PACKAGE +ATTRIBUTES +terminatingLocationCPE GET-REPLACE; +REGISTERED AS {m3108Part1Package 53}; + +#### **6.6.46 terminatingLocationCPEPackage** + +terminatingLocationCPEPackage PACKAGE +ATTRIBUTES +terminatingLocationCPE GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 54}; + +#### **6.6.47 terminatingLocationCPInfoPackage** + +terminatingLocationCPInfoPackage PACKAGE +ATTRIBUTES +terminatingLocationCP GET; +REGISTERED AS {m3108Part1Package 55}; + +### **6.6.48 terminatingLocationInfoPackage** + +terminatingLocationInfoPackage PACKAGE +ATTRIBUTES +terminatingLocation GET; +REGISTERED AS {m3108Part1Package 57}; + +### **6.6.49 terminatingLocationSapInfoPackage** + +terminatingLocationSapInfoPackage PACKAGE +ATTRIBUTES +terminatingLocationSap GET; +REGISTERED AS {m3108Part1Package 58}; + +#### **6.6.50 terminatingLocationSapPackage** + +terminatingLocationSapPackage PACKAGE +ATTRIBUTES +terminatingLocationSap GET-REPLACE; +REGISTERED AS {m3108Part1Package 59}; + +#### **6.6.51 weeklySchedulingInfoPackage** + +weeklySchedulingInfoPackage PACKAGE +ATTRIBUTES +"Rec. X.721 | ISO/IEC 10165-2": weekMask GET; +REGISTERED AS {m3108Part1Package 60}; + +### 6.6.52 weeklySchedulingCurrentPackage + +weeklySchedulingCurrentPackage PACKAGE +BEHAVIOUR +  weeklySchedulingCurrentPackageBehaviour BEHAVIOUR +    DEFINED AS "If the SC specifies a value and the SP is not able to accommodate the requested schedule, the SP must return an error with a reason code indicating that the schedule can not be met.";; +  ATTRIBUTES +    "Rec. X.721 | ISO/IEC 10165-2":weekMask +    GET SET-BY-CREATE; +REGISTERED AS {m3108Part1Package 61}; + +## 6.7 Attributes + +### 6.7.1 aliasName + +aliasName ATTRIBUTE +  WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.AliasName; +  MATCHES FOR EQUALITY, SUBSTRINGS; +REGISTERED AS {m3108Part1Attribute 1}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], +-- [3.3.3.2.6.2], [3.3.3.2.9.2], [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2], [3.3.3.4.3.2], [3.3.3.4.4.2], +-- [3.3.3.4.6.2], [3.3.3.4.9.2], [3.3.3.7.1.2], [3.3.3.7.2.2] + +### 6.7.2 bandwidth + +bandwidth ATTRIBUTE +  WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Bandwidth; +  MATCHES FOR EQUALITY, ORDERING; +REGISTERED AS {m3108Part1Attribute 2}; +-- represents Bandwidth, Link Connection Bandwidth information in the M.3208.1 "Information flow" +-- [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2], +-- [3.3.3.3.1.2], [3.3.3.4.1.2], [3.3.3.3.3.2], [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2] + +### 6.7.3 cp + +cp ATTRIBUTE +  WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cp; +  MATCHES FOR EQUALITY, SUBSTRINGS; +BEHAVIOUR +  cpBehaviour BEHAVIOUR +    DEFINED AS "This attribute identifies the connection point or the service node specified in Rec. M.3208.1";; +REGISTERED AS {m3108Part1Attribute 3}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2], +-- [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2] + +### 6.7.4 customerRequestNumber + +customerRequestNumber ATTRIBUTE +  WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestNumber; +  MATCHES FOR EQUALITY, ORDERING; +REGISTERED AS {m3108Part1Attribute 4}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2] + +### 6.7.5 **dateOfInstallation** + +dateOfInstallation ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering; +REGISTERED AS {m3108Part1Attribute 5}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]* + +### 6.7.6 **diversity** + +diversity ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Diversity; +MATCHES FOR EQUALITY; +BEHAVIOUR +diversityBehaviour BEHAVIOUR +DEFINED AS "This attribute identifies the topological entities from which the circuit should be diverse, or the other circuits from which the circuit should be diverse, or the number of the circuits in the diverse group and the topological entities from which the circuits in the group should be diverse.";; +REGISTERED AS {m3108Part1Attribute 6}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.2.1.2], [3.3.3.2.4.2]* + +### 6.7.7 **equipmentManufacturer** + +equipmentManufacturer ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.EquipmentManufacturer; +MATCHES FOR EQUALITY, SUBSTRINGS; +REGISTERED AS {m3108Part1Attribute 7}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]* + +### 6.7.8 **equipmentType** + +equipmentType ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.EquipmentType; +MATCHES FOR EQUALITY, SUBSTRINGS; +REGISTERED AS {m3108Part1Attribute 8}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]* + +#### 6.7.9 **expectedDateOfInstallation** + +expectedDateOfInstallation ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time; +MATCHES FOR EQUALITY, ORDERING; +REGISTERED AS {m3108Part1Attribute 9}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]* + +#### 6.7.10 **listOfSags** + +listOfSags ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ListOfSags; +MATCHES FOR EQUALITY, SET-INTERSECTION, SET-COMPARISON; +REGISTERED AS {m3108Part1Attribute 10}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.7.1.2]* + +#### 6.7.11 listOfSaps + +listOfSaps ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ListOfSaps; +MATCHES FOR EQUALITY, SET-INTERSECTION, SET-COMPARISON; +REGISTERED AS {m3108Part1Attribute 11}; +*-- represents Service Access Point Ids, Service Access Point* +*-- information in the M.3208.1 "Information flow" [3.3.3.7.4.2], [3.3.3.7.5.2], [3.3.3.9.1.2], [3.3.3.9.2.2]* + +#### 6.7.12 modelType + +modelType ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ModelType; +MATCHES FOR EQUALITY, SUBSTRINGS; +REGISTERED AS {m3108Part1Attribute 12}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]* + +#### 6.7.13 numberOfUnspecifiedSaps + +numberOfUnspecifiedSaps ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.NumberOfUnspecifiedSaps; +MATCHES FOR EQUALITY, ORDERING; +REGISTERED AS {m3108Part1Attribute 13}; +*-- represents information in the M.3208.1 "Information flow" [ 3.3.3.7.4.2]* + +#### 6.7.14 originatingLocation + +originatingLocation ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.OriginatingLocation; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 14}; +*-- represents information in the M.3208.1 "Information flow" [ 3.3.3.1.1.2], [3.3.3.2.1.2]* + +#### 6.7.15 originatingLocationCP + +originatingLocationCP ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cp; +MATCHES FOR EQUALITY, SUBSTRINGS; +REGISTERED AS {m3108Part1Attribute 15}; +*-- represents information in the M.3208.1 "Information flow" [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2],* +*-- [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]* + +#### 6.7.16 originatingLocationCPE + +originatingLocationCPE ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cpe; +MATCHES FOR EQUALITY; +BEHAVIOUR +originatingLocationCPEBehaviour BEHAVIOUR +DEFINED AS "This attribute describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit."; +REGISTERED AS {m3108Part1Attribute 16}; +*-- represents Originating Location CPE Type information in the M.3208.1 "Information flow"* +*-- [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.2.9.2]* + +#### 6.7.17 originatingLocationSap + +originatingLocationSap ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Sap; +MATCHES FOR EQUALITY; +BEHAVIOUR +originatingLocationSAPBehaviour BEHAVIOUR +DEFINED AS "This attribute identifies access point where the Leased Circuit Service originates.";; +REGISTERED AS {m3108Part1Attribute 17}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], +-- [3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2] + +#### 6.7.18 procedure + +procedure ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Procedure; +MATCHES FOR EQUALITY; +BEHAVIOUR +procedureBehaviour BEHAVIOUR +DEFINED AS "This attribute describes the changes of the (test) procedure.";; +REGISTERED AS {m3108Part1Attribute 18}; +-- represents Changes In Procedure information in the M.3208.1 "Information flow" [3.3.3.9.2.2] + +#### 6.7.19 providerRequestNumber + +providerRequestNumber ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestNumber; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR +providerRequestNumberBehaviour BEHAVIOUR +DEFINED AS "This attribute is a unique identifier provided by the SP to identify the request. The providerRequestNumber attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the current service request and service modify request object class";; +REGISTERED AS {m3108Part1Attribute 19}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2], +-- [3.3.3.1.4.2], [3.3.3.2.1.2], [3.3.3.2.4.2], [3.3.3.2.7.2], [3.3.3.2.8.2], [3.3.3.2.9.2], [3.3.3.3.1.2], +-- [3.3.3.3.2.2], [3.3.3.3.3.2], [3.3.3.3.4.2], [3.3.3.4.1.2], [3.3.3.4.4.2], [3.3.3.4.7.2], [3.3.3.4.8.2], +-- [3.3.3.4.9.2], [3.3.3.7.1.2] + +#### 6.7.20 quantity + +quantity ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Number; +MATCHES FOR EQUALITY, ORDERING; +REGISTERED AS {m3108Part1Attribute 21}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.2.1.2], [3.3.3.2.4.2] + +#### 6.7.21 requestedInitialServiceAdministrativeState + +requestedInitialServiceAdministrativeState ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestedInitialServiceAdministrativeState; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 22}; +-- represents Service Administrative State, Link Connection Service Administrative State +-- information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.3.1.2] + +#### 6.7.22 requestReceptionTime + +requestReceptionTime ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering; +REGISTERED AS {m3108Part1Attribute 23}; + +#### 6.7.23 requestSequenceNumber + +requestSequenceNumber ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestNumber; +MATCHES FOR EQUALITY; +BEHAVIOUR +requestSequenceNumberBehaviour BEHAVIOUR +DEFINED AS "The requestSequenceNumber attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service request history record object class";; +REGISTERED AS {m3108Part1Attribute 24}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.3.2], [3.3.3.1.4.2], [3.3.3.2.4.2], +-- [3.3.3.3.3.2], [3.3.3.3.4.2] + +#### 6.7.24 route + +route ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Route; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 25}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], +-- [3.3.3.2.3.2], [3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2] + +#### 6.7.25 sadId + +sadId ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.SadId; +MATCHES FOR EQUALITY; +BEHAVIOUR +sadIDBehaviour BEHAVIOUR +DEFINED AS "The sadID attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service access domain object class";; +REGISTERED AS {m3108Part1Attribute 26}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.7.1.2], [3.3.3.7.2.2], [3.3.3.7.3.2] + +#### 6.7.26 sagId + +sagId ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.SagId; +MATCHES FOR EQUALITY; +BEHAVIOUR +sagIDBehaviour BEHAVIOUR +DEFINED AS "The sagID attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service access group object class";; +REGISTERED AS {m3108Part1Attribute 27}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.7.2.2], [3.3.3.7.3.2], [3.3.3.7.4.2], [3.3.3.7.5.2] + +#### 6.7.27 sagLocation + +sagLocation ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.SagLocation; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 28}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.7.2.2] + +#### 6.7.28 serviceAvailabilityDate + +serviceAvailabilityDate ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering; +REGISTERED AS {m3108Part1Attribute 29}; +-- represents Service Availability Date, Link Connection Availability Date information in the +-- M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.4.2], [3.3.3.2.6.2], +-- [3.3.3.2.9.2], [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2], [3.3.3.4.6.2], [3.3.3.4.9.2] + +#### 6.7.29 serviceCustomerContact + +serviceCustomerContact ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Contact; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 30}; +-- represents Customer Contact information in the M.3208.1 "Information flow" [3.3.3.1.1.2], +-- [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.2.9.2], [3.3.3.3.1.2], [3.3.3.3.3.2], +-- [3.3.3.4.6.2], [3.3.3.4.9.2], [3.3.3.7.1.2] + +#### 6.7.30 serviceInstance + +serviceInstance ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ObjectInstance; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 31}; +-- represents Circuit Number, Link Connection Identifier information in the M.3208.1 "Information +-- flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.2.2], [3.3.3.2.3.2], [3.3.3.2.4.2], +-- [3.3.3.2.5.2], [3.3.3.2.6.2], [3.3.3.3.1.2], [3.3.3.3.2.2], [3.3.3.3.3.2], [3.3.3.4.1.2], [3.3.3.4.2.2], +-- [3.3.3.4.3.2], [3.3.3.4.5.2], [3.3.3.4.6.2], [3.3.3.4.9.2] + +#### 6.7.31 serviceProviderContact + +serviceProviderContact ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Contact; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 32}; +-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.2.1.2], +-- [3.3.3.2.2.2], [3.3.3.2.4.2], [3.3.3.3.1.2], [3.3.3.3.2.2], [3.3.3.4.1.2], [3.3.3.4.2.2], [3.3.3.4.3.2], +-- [3.3.3.4.4.2], [3.3.3.7.1.2] + +#### 6.7.32 serviceRequestState + +serviceRequestState ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ServiceRequestState; +MATCHES FOR EQUALITY; +BEHAVIOUR +serviceRequestStateBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the service request state specified in Rec. M.3208.1."; + +REGISTERED AS {m3108Part1Attribute 33}; +-- *represents Service Request State, Link Connection Request State information in the M.3208.1* +-- *"Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2], [3.3.3.2.7.2], [3.3.3.2.8.2], [3.3.3.3.1.2],* +-- *[3.3.3.3.3.2], [3.3.3.4.7.2], [3.3.3.4.8.2], [3.3.3.4.9.2]* + +#### 6.7.33 serviceTerminationDate + +serviceTerminationDate ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module. ServiceTerminationDate; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering; +REGISTERED AS {m3108Part1Attribute 34}; +-- *represents Service Termination Date, Link Connection Termination Date, Link Termination Date* +-- *information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2],* +-- *[3.3.3.2.1.2], [3.3.3.2.2.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.3.1.2], [3.3.3.3.2.2], [3.3.3.3.3.2],* +-- *[3.3.3.4.1.2], [3.3.3.4.2.2], [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]* + +#### 6.7.34 terminatingLocation + +terminatingLocation ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.TerminatingLocation; +MATCHES FOR EQUALITY; +REGISTERED AS {m3108Part1Attribute 36}; +-- *represents information in the M.3208.1 "Information flow" [ 3.3.3.1.1.2], [3.3.3.2.1.2]* + +### 6.7.35 terminatingLocationCP + +terminatingLocationCP ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cp; +MATCHES FOR EQUALITY, SUBSTRINGS; +REGISTERED AS {m3108Part1Attribute 37}; +-- *represents information in the M.3208.1 "Information flow" [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2],* +-- *[3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]* + +#### 6.7.36 terminatingLocationCPE + +terminatingLocationCPE ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cpe; +MATCHES FOR EQUALITY; +BEHAVIOUR +terminatingLocationCPEBehaviour BEHAVIOUR +DEFINED AS "This attribute describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit.";; +REGISTERED AS {m3108Part1Attribute 38}; +-- *represents Originating Location CPE Type information in the M.3208.1 "Information flow"* +-- *[3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.2.9.2]* + +#### 6.7.37 terminatingLocationSap + +terminatingLocationSap ATTRIBUTE +WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Sap; +MATCHES FOR EQUALITY; +BEHAVIOUR +terminatingLocationSAPBehaviour BEHAVIOUR +DEFINED AS "This attribute identifies access point where the Leased Circuit Service terminates.";; +REGISTERED AS {m3108Part1Attribute 39}; +-- *represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2],* +-- *[3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2]* + +## 6.8 Error messages + +#### 6.8.1 addToSagError + +addToSagError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.AddToSagError; +BEHAVIOUR addToSagErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request add a SAP to a SAG is invalid or if the SP cannot comply with the request.";; +REGISTERED AS {m3108Part1Parameter 1}; + +### 6.8.2 bandwidthUnavailable + +bandwidthUnavailable PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.Null; +BEHAVIOUR bandwidthUnavailableBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the SP does not have the bandwidth to comply with the request.";; +REGISTERED AS {m3108Part1Parameter 2}; + +### 6.8.3 CreateLCSError + +createLCSError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.CreateLCSError; +BEHAVIOUR createLCSErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request for LCS is invalid or if the SP cannot provide the requested service.";; +REGISTERED AS {m3108Part1Parameter 3}; + +### 6.8.4 createLinkConnectionError + +createLinkConnectionError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.CreateLinkConnectionError; +BEHAVIOUR createLinkConnectionErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request for link connection service is invalid or if the SP cannot provide the requested service.";; +REGISTERED AS {m3108Part1Parameter 4}; + +### 6.8.5 createSadError + +createSadError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.CreateSadError; +BEHAVIOUR createSadErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request for a SAD is invalid or if the SP cannot provide the requested SAD.";; +REGISTERED AS {m3108Part1Parameter 5}; + +### 6.8.6 createSagError + +createSagError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.CreateSagError; +BEHAVIOUR createSagErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request for a SAG is invalid or if the SP cannot provide the requested SAG.";; +REGISTERED AS {m3108Part1Parameter 6}; + +### **6.8.7 deleteLCSError** + +deleteLCSError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.DeleteLCSError; +BEHAVIOUR deleteLCSErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request to delete a LCS is incorrect.";; +REGISTERED AS {m3108Part1Parameter 7}; + +#### **6.8.8 deleteLinkConnectionError** + +deleteLinkConnectionError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.DeleteLinkConnectionError; +BEHAVIOUR deleteLinkConnectionErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request to delete a link connection service is incorrect.";; +REGISTERED AS {m3108Part1Parameter 8}; + +### **6.8.9 deleteSadError** + +deleteSadError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.DeleteSadError; +BEHAVIOUR deleteSadErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request to delete a SAD is incorrect, in particular, if the SAD contains +SAG(s).";; +REGISTERED AS {m3108Part1Parameter 9}; + +### **6.8.10 deleteSagError** + +deleteSagError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.DeleteSagError; +BEHAVIOUR deleteSagErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request to delete a SAG is incorrect.";; +REGISTERED AS {m3108Part1Parameter 10}; + +### **6.8.11 modifyLCSError** + +modifyLCSError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.ModifyLCSError; +BEHAVIOUR modifyLcsErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the SP cannot comply with the request.";; +REGISTERED AS {m3108Part1Parameter 11}; + +### **6.8.12 removeFromSagError** + +removeFromSagError PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.RemoveFromSagError; +BEHAVIOUR removeFromSagErrorBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the request remove a SAP from a SAG is invalid or if the SP cannot +comply with the request.";; +REGISTERED AS {m3108Part1Parameter 12}; + +### **6.8.13 resourcesUnavailable** + +resourcesUnavailable PARAMETER +CONTEXT SPECIFIC-ERROR; +WITH SYNTAX M3108Part1ASN1Module.Null; +BEHAVIOUR resourcesUnavailableBehaviour BEHAVIOUR +DEFINED AS "This error is issued if the SP does not have the resources to comply with the request.";; +REGISTERED AS {m3108Part1Parameter 13}; + +## **6.9 Notifications** + +### **6.9.1 lcsModifyProgressProblemReport** + +lcsModifyProgressProblemReport NOTIFICATION +BEHAVIOUR lcsModifyProgressProblemReportBehaviour; +WITH INFORMATION SYNTAX M3108Part1ASN1Module.LcsModifyProgressProblemReport; +REGISTERED AS {m3108Part1Notification 1}; + +lcsModifyProgressProblemReportBehaviour +BEHAVIOUR +DEFINED AS "This notification is used to report problems with a LCS modification request."; + +### **6.9.2 lcsRequestProgressProblemReport** + +lcsRequestProgressProblemReport NOTIFICATION +BEHAVIOUR lcsRequestProgressProblemReportBehaviour; +WITH INFORMATION SYNTAX M3108Part1ASN1Module.LcsRequestProgressProblemReport; +REGISTERED AS {m3108Part1Notification 2}; + +lcsRequestProgressProblemReportBehaviour +BEHAVIOUR +DEFINED AS " This notification is used to report problems with a LCS request."; + +### **6.9.3 linkConnectionModifyProgressProblemReport** + +linkConnectionModifyProgressProblemReport NOTIFICATION +BEHAVIOUR linkConnectionModifyProgressProblemReportBehaviour; +WITH INFORMATION SYNTAX M3108Part1ASN1Module.LinkConnectionModifyProgressProblemReport; +REGISTERED AS {m3108Part1Notification 3}; + +linkConnectionModifyProgressProblemReportBehaviour +BEHAVIOUR +DEFINED AS "This notification is used to report problems with a link connection service modification request."; + +### **6.9.4 linkConnectionRequestProgressProblemReport** + +linkConnectionRequestProgressProblemReport NOTIFICATION +BEHAVIOUR linkConnectionRequestProgressProblemReportBehaviour; +WITH INFORMATION SYNTAX M3108Part1ASN1Module.LinkConnectionRequestProgressProblemReport; +REGISTERED AS {m3108Part1Notification 4}; + +linkConnectionRequestProgressProblemReportBehaviour +BEHAVIOUR +DEFINED AS "This notification is used to report problems with a link connection service request."; + +## 6.10 Actions + +### 6.10.1 updateServiceRequest + +updateServiceRequest ACTION +BEHAVIOUR updateServiceRequestBehaviour; +WITH INFORMATION SYNTAX M3108Part1ASN1Module.UpdateServiceRequest; +WITH REPLY SYNTAX M3108Part1ASN1Module.UpdateServiceReply; +REGISTERED AS {m3108Part1Action 1}; + +updateServiceRequestBehaviour BEHAVIOUR +DEFINED AS "The updateServiceRequest action is used by the service customer to modify a non-completed service request. The attributes that can be modified are identified by the service request object class. If the values provided by the SP are different from the values requested by the SC, then the values of those attributes must be returned by the SP to the SC. If as result of the action some other attributes have changed (e.g. the SC requests a different bandwidth, the request is implemented, but the route has changed, then the values of those changed attributes must be included in the response from the SP to the SC."; + +### 6.10.2 AddSapsToSag + +AddSapsToSag ACTION +BEHAVIOUR AddSapsToSagBehaviour; +WITH INFORMATION SYNTAX M3108Part1ASN1Module.AddSapsToSagInformation; +WITH REPLY SYNTAX M3108Part1ASN1Module.AddSapsToSagResult; +REGISTERED AS {m3108Part1Action 2}; + +AddSapsToSagBehaviour BEHAVIOUR +DEFINED AS "This action is used to arrange service access points into SAGs. Contained service access points IDs are added; if the service access points IDs are empty and the number of access service access points is provided, the SP adds as many SAPs as specified in the number of SAPs; the SP further provides their IDs. If the number of SAPs is not provided and no SAP IDs are specified, then the SP adds a single SAP to the SAG and provides its Id. If both the number of SAPs and SAP IDs are present, then the SP adds the identified SAPs to the SAG, the SP further adds as many SAPs as specified by the number of SAPs and provides their IDs. The SAP IDs must be present in case of an error or if the SAP IDs are provided by the SP to the SC in the reply value."; + +## 6.11 Name bindings + +### 6.11.1 currentLcsRequest-account + +currentLcsRequest-account NAME BINDING +SUBORDINATE OBJECT CLASS currentLcsRequest AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES; +WITH ATTRIBUTE providerRequestNumber; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING +createLCSError; +DELETE DELETES-CONTAINED-OBJECTS +deleteLCSError; +REGISTERED AS {m3108Part1NameBinding 1}; + +### 6.11.2 lcsRequestHistoryRecord-currentLCSRequest + +lcsRequestHistoryRecord-currentLCSRequest NAME BINDING +SUBORDINATE OBJECT CLASS lcsRequestHistoryRecord; +NAMED BY SUPERIOR OBJECT CLASS currentLcsRequest AND SUBCLASSES; +WITH ATTRIBUTE requestSequenceNumber; +REGISTERED AS {m3108Part1NameBinding 2}; + +### 6.11.3 lcsModifyRequest-lcs + +lcsModifyRequest-lcs NAME BINDING +SUBORDINATE OBJECT CLASS lcsModifyRequest AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS lcs AND SUBCLASSES; +WITH ATTRIBUTE providerRequestNumber; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {m3108Part1NameBinding 3}; + +### 6.11.4 currentLinkConnectionServiceRequest-account + +currentLinkConnectionServiceRequest-account NAME BINDING +SUBORDINATE OBJECT CLASS currentLinkConnectionServiceRequest +AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES; +WITH ATTRIBUTE providerRequestNumber; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING +createLinkConnectionError; +DELETE DELETES-CONTAINED-OBJECTS +deleteLinkConnectionError; +REGISTERED AS {m3108Part1NameBinding 4}; + +### 6.11.5 linkConnectionServiceRequestHistoryRecord-currentLinkConnectionServiceRequest + +linkConnectionServiceRequestHistoryRecord-currentLinkConnectionServiceRequest NAME BINDING +SUBORDINATE OBJECT CLASS linkConnectionServiceRequestHistoryRecord; +NAMED BY SUPERIOR OBJECT CLASS currentLinkConnectionServiceRequest +AND SUBCLASSES; +WITH ATTRIBUTE requestSequenceNumber; +BEHAVIOUR +historyBindingBehaviour BEHAVIOUR +DEFINED AS "The service provider creates a serviceRequestHistoryRecord of the initial service +request (currentServiceRequest) values. The serviceRequestHistoryRecord is also created when the +service customer issues an updateServiceRequest action towards a currentServiceRequest (and +subclasses) and contains a record of the attribute values specified in the request.";; +REGISTERED AS {m3108Part1NameBinding 5}; + +### 6.11.6 linkConnectionServiceModifyRequest-linkConnectionService + +linkConnectionServiceModifyRequest-linkConnectionService NAME BINDING +SUBORDINATE OBJECT CLASS linkConnectionServiceModifyRequest; +NAMED BY SUPERIOR OBJECT CLASS linkConnectionService +AND SUBCLASSES; +WITH ATTRIBUTE providerRequestNumber; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE; +REGISTERED AS {m3108Part1NameBinding 6}; + +### 6.11.7 serviceAccessEquipmentView-account + +serviceAccessEquipmentView-account NAME BINDING +SUBORDINATE OBJECT CLASS serviceAccessEquipmentView AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES; +WITH ATTRIBUTE "Rec. M3100:1995":equipmentId; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; + +DELETE; +REGISTERED AS {m3108Part1NameBinding 7}; + +### 6.11.8 linkConnectionService-account + +linkConnectionService-account NAME BINDING +SUBORDINATE OBJECT CLASS linkConnectionService AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES; +WITH ATTRIBUTE "Rec. X.790:1995": serviceID; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE DELETES-CONTAINED-OBJECTS; +REGISTERED AS {m3108Part1NameBinding 8}; + +### 6.11.9 lcs-account + +lcs-account NAME BINDING +SUBORDINATE OBJECT CLASS lcs AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES; +WITH ATTRIBUTE "Rec. X.790:1995": serviceID; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE DELETES-CONTAINED-OBJECTS; +REGISTERED AS {m3108Part1NameBinding 9}; + +### 6.11.10 serviceAccessDomain-account + +serviceAccessDomain-account NAME BINDING +SUBORDINATE OBJECT CLASS serviceAccessDomain AND SUBCLASSES; +NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES; +WITH ATTRIBUTE sadId; +BEHAVIOUR +serviceAccessDomainBindingBehaviour BEHAVIOUR +DEFINED AS "An instance of this MO class can be created by the SC. An instance of this MO class +can be deleted by the SC.";; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING +createSadError; +DELETE +deleteSadError; +REGISTERED AS {m3108Part1NameBinding 10}; + +### 6.11.11 serviceAccessGroup-serviceAccessDomain + +serviceAccessGroup-serviceAccessDomain NAME BINDING +SUBORDINATE OBJECT CLASS serviceAccessGroup; +NAMED BY SUPERIOR OBJECT CLASS serviceAccessDomain AND SUBCLASSES; +WITH ATTRIBUTE sagId; +BEHAVIOUR +serviceAccessGroupBindingBehaviour BEHAVIOUR +DEFINED AS "An instance of this MO class can be created by the SC. An instance of this MO class +can be deleted by the SC.";; +CREATE +WITH-AUTOMATIC-INSTANCE-NAMING +createSagError; +DELETE +deleteSagError; +REGISTERED AS {m3108Part1NameBinding 11}; + +## 6.12 ASN.1 syntax + +### 6.12.1 Rules of extensibility + +The following types will be indicated as being extensible: + +- ENUMERATED; +- named INTEGER; +- named BIT STRING; +- tagged SET; +- tagged SEQUENCE; +- tagged CHOICE. + +Under the rules of extensibility new enumerations (for ENUMERATED types), new bit name assignments (for named BIT STRING types), new named numbers (for named INTEGER types), and new tagged elements (for tagged SET, SEQUENCE, and CHOICE types) may be added in future versions of this Recommendation. + +When processing information in a System Management Application Protocol (SMAP) PDU, the accepting SMAP-machine shall ignore: + +- enumerations not recognized; +- unrecognized named numbers; +- unrecognized named bits; +- unrecognized tagged elements of sets, sequences, and choices. + +### 6.12.2 ASN.1 module + +M3108Part1ASN1Module {ccitt recommendation m lcs(3108) serviceManagement(1) informationModel(0) asnlModules(2) asnlDefinedTypesModule(0)} + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN + +-- EXPORTS *everything* + +IMPORTS + +NameType + +FROM ASN1DefinedTypesModule {ccitt recommendation m gnm(100) informationModel(0) + +asnlModules(2) asnlDefinedTypesModule(0)} + +AdditionalInformation, AdditionalText, AdministrativeState, AttributeList, AvailabilityStatus, NotificationIdentifier, SourceIndicator + +FROM Attribute-ASN1Module {joint-iso-ccitt ms(9) smi(3) part2(2) asnlModule (2) 1} + +ObjectInstance + +FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)} + +LocationAddress, PersonReach + +FROM X790ASN1Module {itu-t(0) recommendation(0) x(24) x790(790) informationModel(0) + +asnlmodule(2)} + +; + +m3108Part1InformationModel OBJECT IDENTIFIER ::= {ccitt recommendation m lcs(3108) serviceManagement(1) informationModel(0) } + +m3108Part1ObjectClass OBJECT IDENTIFIER ::= {m3108Part1InformationModel managedObjectClass(1)} + +m3108Part1Package OBJECT IDENTIFIER ::= {m3108Part1InformationModel package(2)} + +m3108Part1Attribute OBJECT IDENTIFIER ::= {m3108Part1InformationModel attribute(3)} + +m3108Part1NameBinding OBJECT IDENTIFIER ::= {m3108Part1InformationModel nameBinding(4)} + +m3108Part1Notification OBJECT IDENTIFIER ::= {m3108Part1InformationModel notification(5)} + +m3108Part1Parameter OBJECT IDENTIFIER ::= {m3108Part1InformationModel parameter(6)} + +m3108Part1Action OBJECT IDENTIFIER ::= {m3108Part1InformationModel action(7)} + +``` + +AddSapsToSagInformation ::= SEQUENCE { + listOfSaps ListOfSaps OPTIONAL, + numberOfServiceAccessPoints INTEGER OPTIONAL +} + +AddSapsToSagResult ::= CHOICE { + listOfSaps ListOfSaps, + addToSagError AddToSagError +} + +AddToSagError ::= ENUMERATED { + invalidSapId (0), + invalidSagId (1), + sapNotInAppropriateUsageState (2), + resourcesNotAvailable (3), + ... +} + +AliasName ::= PrintableString + +Bandwidth ::= CHOICE { + bitsPerSecond [0] Number, + kiloBitsPerSecond [1] Number, + megaBitsPerSecond [2] Number, + gigaBitsPerSecond [3] Number, + teraBitsPerSecond [4] Number + -- , ... +} + +CircuitId ::= NameType + +CircuitNumber ::= Number + +Contact ::= CHOICE { + person PersonReach, + contactObject ObjectInstance + -- the ObjectInstance points to an instance of a X.790 Contact object. +} + +Cp ::= TopologicalEntity + +Cpe ::= CHOICE { name PrintableString, + object ObjectInstance + } + +CreateSadError ::= ENUMERATED { + invalidLocation (0), + invalidServiceType (1), + invalidServiceDescription (2), + ... +} + +CreateSagError ::= ENUMERATED { + invalidLocation (0), + invalidSagId (1), + invalidSadId (2), + ... +} + +``` + +``` + +CreateLCSError ::= ENUMERATED { + unknownServiceDescription (0), + unknownServiceType (1), + resourcesUnavailable (2), + requestedBandwidthNotAvailable (3), + quantitySpecifiedOutOfRange (4), + contractViolation (5), + invalidValue (6), + requiredParameterNotAvailable (7), + serviceCannotBeCompleted (8), + invalidServiceTerminationDate (9), + invalidSchedule (10), + invalidServiceAvailabilityDate (11), + requestAlreadyClosed (12), + invalidAddress (13), + nonExistentSAP (14), + ... +} + +CreateLinkConnectionError ::= ENUMERATED { + unknownServiceDescription (0), + unknownServiceType (1), + resourcesUnavailable (2), + requestedLinkConnectionBandwidthNotAvailable (3), + contractViolation (4), + invalidValue (5), + requiredParameterNotAvailable (6), + linkConnectionRequestCannotBeCompleted (7), + invalidLinkConnectionTerminationDate (8), + invalidLinkConnectionAvailabilityDate (9), + nonExistentLinkConnectionPoint (10), + ... +} + +DeleteLCSError ::= ENUMERATED { + alreadyDeleted (0), + invalidCircuitNumber (1), + invalidServiceTerminationDate (2), + notBeingInAppropriateServiceAdministrativeState (3), + contractViolation (4), + ... +} + +DeleteLinkConnectionError ::= ENUMERATED { + alreadyDeleted (0), + invalidLinkConnectionIdentifier (1), + invalidLinkConnectionTerminationDate (2), + notBeingInAppropriateLinkConnectionAdministrativeState (3), + contractViolation (4), + ... +} + +DeleteSadError ::= ENUMERATED { + invalidSadId (0), + sadContainsSags (1), + ... +} + +``` + +``` + +DeleteSagError ::= ENUMERATED { + invalidSagId (0), + invalidSadId (1), + ... +} + +Diversity ::= CHOICE { + topologicalElements [1] SET OF TopologicalEntity, + -- the topological entities from which the circuit should be diverse -- + otherCircuits [2] SET OF CircuitId, + -- other circuits from which the circuit should be diverse -- + severalGroups [3] SET OF SEQUENCE { + numberOfCircuits INTEGER, + -- the number of circuits in the diverse group -- + topologicalElements SET OF TopologicalEntity + -- the topological entities from which the circuits in the group should be diverse -- + } +} + +EquipmentManufacturer ::= PrintableString + +EquipmentType ::= PrintableString + +LcsModifyProgressProblemReport ::= SEQUENCE { + sourceIndicator [1] SourceIndicator OPTIONAL, + lcsModifyProgressProblemReportInfo [2] LcsModifyProgressProblemReportInfo, + notificationIdentifier [3] NotificationIdentifier OPTIONAL, + additionalText [4] AdditionalText OPTIONAL, + additionalInformation [5] AdditionalInformation OPTIONAL +} + +LcsModifyProgressProblemReportInfo ::= ENUMERATED { + resourcesUnavailable (0), + requestedBandwidthNotAvailable (1), + ... +} + +LcsRequestProgressProblemReport ::= SEQUENCE { + sourceIndicator [1] SourceIndicator OPTIONAL, + lcsRequestProgressProblemReportInfo [2] LcsRequestProgressProblemReportInfo, + notificationIdentifier [3] NotificationIdentifier OPTIONAL, + additionalText [4] AdditionalText OPTIONAL, + additionalInformation [5] AdditionalInformation OPTIONAL +} + +LcsRequestProgressProblemReportInfo ::= ENUMERATED { + resourcesUnavailable (0), + requestedBandwidthNotAvailable (1), + serviceCannotBeCompleted (2), + invalidServiceAvailabilityDate (3), + invalidAddress (4), + nonExistentSap (5), + ... +} + +``` + +``` + +LinkConnectionModifyProgressProblemReport ::= SEQUENCE { + sourceIndicator [1] SourceIndicator OPTIONAL, + linkConnectionModifyProgressProblemReportInfo [2] +LinkConnectionModifyProgressProblemReportInfo, + notificationIdentifier [3] NotificationIdentifier OPTIONAL, + additionalText [4] AdditionalText OPTIONAL, + additionalInformation [5] AdditionalInformation OPTIONAL +} + +LinkConnectionModifyProgressProblemReportInfo ::= ENUMERATED { + resourcesUnavailable (0), + requestedBandwidthNotAvailable (1), + ... +} + +LinkConnectionRequestProgressProblemReport ::= SEQUENCE { + sourceIndicator [1] SourceIndicator OPTIONAL, + linkConnectionRequestProgressProblemReportInfo [2] +LinkConnectionRequestProgressProblemReportInfo, + notificationIdentifier [3] NotificationIdentifier OPTIONAL, + additionalText [4] AdditionalText OPTIONAL, + additionalInformation [5] AdditionalInformation OPTIONAL +} + +LinkConnectionRequestProgressProblemReportInfo ::= ENUMERATED { + resourcesUnavailable (0), + requestedLinkConnectionBandwidthNotAvailable (1), + linkConnectionRequestCannotBeCompleted (2), + nonExistentLinkConnectionPoint (3), + ... +} + +ListOfSags ::= SET OF SagId + +ListOfSaps ::= SET OF Sap + +M3108FunctionalUnits ::= BIT STRING { + basicTransportService (0), + transportServiceOrder (1), + transportServiceOrderHistory (2), + transportServiceModify (3), + transportResourceVisibility (4) +} + +ModelType ::= PrintableString + +ModifyLCSError ::= UpdateLCSError + +ModifyLinkConnectionError ::= ENUMERATED { + requiredBandwidthNotAvailable (0), + resourcesUnavailable (1), + unknownRoute (2), + serviceAdministrativeStateUnlocked (3), + ... +} + +NumberOfUnspecifiedSaps ::= INTEGER (1..MAX) + +``` + +``` + +Name ::= PrintableString + +Number ::= INTEGER (0..MAX) + +Null ::= NULL + +OriginatingLocation ::= LocationAddress + +Procedure ::= CHOICE { + name PrintableString, + number INTEGER + } + +RemoveFromSagError ::= SEQUENCE { + sourceIndicator [1] SourceIndicator OPTIONAL, + removeFromSagErrorInfo [2] RemoveFromSagErrorInfo, + notificationIdentifier [3] NotificationIdentifier OPTIONAL, + additionalText [4] AdditionalText OPTIONAL, + additionalInformation [5] AdditionalInformation OPTIONAL +} + +RemoveFromSagErrorInfo ::= ENUMERATED { + invalidSapId (0), + invalidSagId (1), + sapNotInAppropriateUsageState (2), + ... + } + +RequestedInitialServiceAdministrativeState ::= AdministrativeState + +RequestNumber ::= INTEGER (0..MAX) + +Route ::= SEQUENCE OF TopologicalEntity + +SadId ::= NameType + +SagId ::= NameType + +SagLocation ::= LocationAddress + +Sap ::= PrintableString + +ServiceRequestState ::= ENUMERATED { + pre-processing (0), + open-active (1), + pending (2), + closed (3) + } + +ServiceTerminationDate ::= CHOICE { time Time, + continous NULL} +-- continous means that no termination date has been specified, this is the default value +-- for ServiceTerminationDate + +Time ::= GeneralizedTime +-- without fractions of seconds, with time zone indication. -- + +TerminatingLocation ::= LocationAddress + +``` + +``` + +TopologicalEntity ::= CHOICE { name PrintableString, + object ObjectInstance + } + +UpdateLCSError ::= ENUMERATED { + invalidCpeType (0), + invalidSAP (1), + resourcesUnavailable (2), + requiredBandwidthNotAvailable (3), + unknownRoute (4), + contractViolation (5), + serviceAdministrativeStateUnlocked (6), + invalidCircuitNumber (7), + invalidServiceTerminationDate (8), + invalidSchedule (9), + invalidServiceAvailableState (10), + invalidProviderRequestNumber (11), + invalidAliasName (12), + ... + } + +UpdateLinkConnectionError ::= ENUMERATED { + invalidLinkConnectionPoint (0), + resourcesUnavailable (1), + requiredBandwidthNotAvailable (2), + contractViolation (3), + linkConnectionAdministrativeStateUnlocked (4), + invalidLinkConnectionIdentifier (5), + invalidLinkConnectionTerminationState (6), + invalidLinkConnectionAvailableState (7), + invalidProviderRequestNumber (8), + invalidLinkConnectionAliasName (9), + invalidSchedule (10), + ... + } + +UpdateServiceRequest ::= AttributeList + +UpdateServiceReply ::= SEQUENCE { + requestIdentifier SEQUENCE { + initialRequest RequestNumber OPTIONAL, + newRequest RequestNumber + } OPTIONAL, + alternateValues AttributeList OPTIONAL + } + +OriginatingLocationCP ::= TopologicalEntity + +OriginatingLocationSap ::= TopologicalEntity + +TerminatingLocationCP ::= TopologicalEntity + +TerminatingLocationSap ::= TopologicalEntity + +END + +``` + +## 7 Functional units + +The services defined to support the functions specified in Recommendation M.3208.1 have been grouped into several functional units to allow negotiation of their use on an association (during association establishment), and to allow referencing by other Recommendations. Functional unit negotiation shall be performed as described in Recommendation X.701. The bit string defined in 6.12.2 shall be used to represent functional units. No TMN-specific user information is supplied during association release or aborts. Table 7-1 lists these functional units and their corresponding managed object classes and functions from Recommendation M.3208.1. + +**Table 7-1/M.3108.1 – Functional units, object classes, and functions** + +| Functional unit | Object class(es) | Function(s) (M.3208.1) | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Basic transport service | networkR1 account (subclass of) transportService, lcs, linkConnectionService, serviceAccessGroup, serviceAccessDomain | Create LCS (3.3.3.1.1)
Delete LCS (3.3.3.1.2)
Report creation of LCS (3.3.3.2.1)
Report deletion of LCS (3.3.3.2.2)
Report LCS configuration change (3.3.3.2.3)
Control LCS administrative state (3.3.3.2.5)
Link connection configuration (3.3.3.3)
Create link connection service (3.3.3.3.1)
Delete link connection service (3.3.3.3.2)
Report creation of link connection service (3.3.3.4.1)
Report deletion of link connection service (3.3.3.4.2)
Report link connection service configuration change (3.3.3.4.3)
Control link connection service administrative state (3.3.3.4.5)
Reconfigurable leased circuit service configuration (3.3.3.5, 3.3.3.6)
Service access domain configuration set (3.3.3.7)
Create SAD (3.3.3.7.1)
Create SAG (3.3.3.7.2)
Delete SAG (3.3.3.7.3)
Add SAPs to SAG (3.3.3.7.4)
Remove SAPs from SAG (3.3.3.7.5) | +| Transport service order | networkR1 account (subclass of) currentServiceRequest | Create service request (3.3.3.1.1, 3.3.3.3.1)
Cancel service request (3.3.3.1.4, 3.3.3.3.4)
Report change of service request parameters (3.3.3.2.4, 3.3.3.4.4)
Monitor progress of service request (3.3.3.2.7)
Report progress of service request (3.3.3.2.8)
Retrieve service request parameters (3.3.3.2.9, 3.3.3.4.9) | + +**Table 7-1/M.3108.1 – Functional units, object classes, and functions (concluded)** + +| Functional unit | Object class(es) | Function(s) (M.3208.1) | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Transport service order history | networkR1 account (subclass of) serviceRequestHistoryRecord linkConnectionServiceRequestHistoryRecord, lcsRequestHistoryRecord | Modify service request (3.3.3.1.3) | +| Transport service modify | networkR1 account (subclass of) serviceModifyRecord, linkConnectionServiceModifyRequest, lcsModifyRequest | Modify LCS (3.3.3.1.3)
Modify link connection service (3.3.3.3.3) | +| Transport resource visibility | networkR1 account serviceAccessEquipmentView (additional resource subject to SLA) | Access equipment status (3.3.3.9)
Access equipment status update (3.3.3.9.1)
Access equipment status inquiry (3.3.3.9.2) | + +### 7.1 Basic transport service functional unit + +The basic transport service functional unit supports services (subject to service level agreement) on provisioned transport services with the exception of modification of the service characteristics. The service customer can modify parameters that are not affecting service, e.g. service customer contact. + +### 7.2 Transport service order functional unit + +The transport service order functional unit permits the service customer to issue requests for transport services and it makes visible the service order process. The service customer can provide missing parameters or change previously supplied parameters while the service order is in the pending or open/active states, i.e. not yet completed. + +### 7.3 Transport service order history functional unit + +The transport service order history functional unit allows the service provider to keep a history of all requests for modifications of the service order as issued by the service customer. + +### 7.4 Transport service modify functional unit + +The transport service modify functional unit allows the service customer to modify parameters of existing transport services. + +### 7.5 Transport resource visibility functional unit + +The transport service visibility functional unit provides visibility of transport resources. The set of transport resources made visible to the customer is not specified in this Recommendation and is in general subject to SLA. + +### 7.6 Negotiation of functional units + +This Recommendation assigns the following object identifier values: + +{itu-t (0) recommendation(0) m(31) m3108(3108) part1(1) protocolSupport(1) functionalUnitPackage(1)} + +as a value of the ASN.1 type FunctionalUnitPackageId defined in Recommendation X.701 to use for negotiating the following functional units: + +- 0 basic transport service +- 1 transport service order +- 2 transport service order history +- 3 transport service modify +- 4 transport resource visibility + +where the number identifies the bit positions in the BIT STRING assigned to the functional units, and the names referencing the functional units as defined in clause 7. + +Within the systems management application context, the mechanism for negotiating the functional units is described in Recommendation X.701. + +NOTE – The requirement to negotiate functional units is specified by the application context. + +## **8 Conformance** + +### **8.1 Static conformance** + +A system claiming conformance to this Recommendation shall: + +- a) support the role of manager or agent or both, with respect to the FUs defined or referenced in this Recommendation; +- b) support the transfer syntax derived from the encoding rules specified in Recommendation X.209 and named {joint-iso-ccitt asn(1) basicEncoding(1)}, for the purpose of generating and/or interpreting the MAPDUs defined by the abstract data types defined in this Recommendation for the role supported in a) above; +- c) support at least one of the FUs defined in Table 7-1; +- d) support the conformance requirements specified in Q.812 CMIP profile. + +### **8.2 Dynamic conformance** + +The system shall, for the role for which conformance is claimed, support the elements of procedure defined in: + +- Recommendation X.730 for the PT-GET, PT-CREATE, PT-DELETE, PT-SET services; +- Recommendation X.730 for the object creation reporting and object deletion reporting, if the create delete notifications are specified in the objects supported; +- Recommendation X.730 for the attribute value change reporting if the attribute value change notification is specified in the objects supported; +- Recommendation X.731 for the state change reporting service if the state change reporting notification is specified in the objects supported. + +### **8.3 Conformance to managed object definitions** + +The managed objects supported by the open system for service provisioning shall comply with the syntax and semantics of the information model specified for the FUs to which conformance is claimed. + +## APPENDIX I + +### Protocol-independent object description + +This appendix provides a protocol-independent description of the objects in the information model. + +The protocol-independent description of the objects is based on the following template: + +- 1) **Unique name** (within a uniquely identified module). +- 2) **Description**: general description of the object. +- 3) **Business purpose description**: provides traceability to specific business needs in Recommendation M.3208.1; traceability is provided through the title of the appropriate clause in Recommendation M.3208.1 and/or the number of the appropriate clause in Recommendation M.3208.1 enclosed in square brackets. In general, different combinations of MOs can support the same generic business need. The selection of the specific MOs in support of a management function is a local matter that may depend on local business practices. Therefore, the traceability provided here is not complete; it points only to one or two functions in Recommendation M.3208.1 that may be supported by the MO. Appendix II provides a more complete listing of the MOs that may support each of the management functions in Recommendation M.3208.1. +- 4) **Primary identifier**: the primary IDs for the modelling object. +- 5) **Attributes** + +Attribute name: for ease of reading, the attribute name is given in plain English, e.g. Alias name rather than aliasName; if the object definition includes any packages that consist only of attributes and/or behaviours, such packages are listed as entries under this appendix, and the attributes within the package are listed in parenthesis after the **package name**. + +Access modes (R = read; W = write, update; S = set to default) + +Optional or Mandatory + +Description of the attribute. + +- 6) **Behaviour description** + +**Creation** When is the object created. + +**Read** When is the object read. + +**Update** When is the object updated. + +**Action** What actions are allowed on the object and when. + +**Deletion** When is the object deleted. + +**Notifications** Notifications emitted from the object. + +- 7) **Notes/Comment** + +For an object class that is a subclass of another object class, the inherited properties are not repeated. Only differences from the superclass are shown in the descriptions below. + +## I.1 Generic service request fragment + +### I.1.1 currentServiceRequest + +- 1) **Unique name:** currentServiceRequest. +- 2) **Description:** Represents information elements that are common to all service requests and updates to service requests. It is used as a superclass for defining service-specific, instantiable managed objects representing requests for specific services. +- 3) **Business purpose description:** Every information element (attribute, notification) in this object is listed in the "Create dedicated leased circuit service function" [3.3.3.1.1] in Recommendation M.3208.1; in particular, the attributes are listed under "Information Flow" [3.3.3.1.1.2]. However, since the currentServiceRequest object is designed a super class for service-specific objects, it does not contain all the information exchange listed in Recommendation M.3208.1 for "Create dedicated leased circuit service function". +- 4) **Primary identifier:** providerRequestNumber. +- 5) **Attributes** + +| Attribute name | Access mode | Optional/Mandatory | Description | +|--------------------------------------|-------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Provider request number | R | M | Unique identifier provided by the SP to identify the request. | +| Request reception time | R | M | The time when the service request was received by the service provider. Used to establish an order among requests, and changes to requests. Such ordering may be needed since, in case of conflicting changes to a request, the most recent change request is effective. | +| Initial service administrative state | R, W | O |

The SC may specify the service administrative state when the service is created. Valid values are:

Unlocked – Indicating that the LCS is available for use (provides service) by the SC.

Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s).

See Figure 5/M.3208.1 for an explanation of the Service Administrative State Model.

| +| Customer request number | R | O | Unique identifier provided by the SC to identify the request. | +| Service termination date | R, W | O |

The date at which the LCS will be made inactive.

If the SC provides a termination date and the SP does not return a date, the requested date is accepted. In case the SP cannot accept the date, an alternate date is provided.

| +| Alias name | R, W | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. | + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|-------------------------------------|---------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Daily scheduling (intervals of day) | R, W | O | Allows the customer to specify during which periods of the day the service shall be available. | +| Weekly scheduling (week mask) | R, W | O | Allows the customer to specify during which days of the week the service shall be available. | +| External scheduler (schedule name) | R, W | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. | +| Service availability status | R | O | | +| Request sequence number | R | M | Allows the SP to "staple" together several changes to the same service request. | +| Service type | R, W
(at create) | M | The type of leased circuit service offered by the SP. Service names are not subject to standardization and are defined by the contract between the SC and the SP. | +| Service provider contact | R | M | The provider contact information for use by the SC in resolving questions or problems with the service. | +| Service customer contact | R, W | M | The customer contact information for use by the SP in resolving questions or problems with the service. | +| Service availability date | R, W | M | Date the service is due to be provisioned and placed in the requested Service Administrative State, as requested by the SC. | +| Service request state | R | M | This parameter indicates that the request is in progress.
Valid values are:
pre-processing – Indicates that the service request is currently being checked for validity of request parameters.
open/active – Indicates that the service request is open and is being actively processed.
Pending – Indicating that the service request is deactivated for reasons such as waiting for additional information, completion of other supporting tasks. Activation from this pending state is required before processing can be continued.
Closed – Indicates the service request is closed either as a result of successful completion or error or because the request was cancelled.
See Figure 4/M.3208.1 for allowed state transitions. | + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|---------------------|-------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service description | R, W
at create | O |

The name of a profile of service characteristics (associated with the service type) defined and supported by the SP. Examples of the service characteristics that may be included in the profile are directionality, channelization, signalling options, protection, quality of service objectives, application, etc. Service values of this attribute are not subject to standardization and are defined by the contract.

If the requested service is not equal to the service provided by the SP, then the SP must supply the value; else, it is optional.

| + +6) **Behaviour description** + +- Creation** When the customer requests a service or changes the request. +- Read** When the customer wants to know what is being requested, after any number of changes by the customer. +- Update** When the customer decides to change (parts of) the request or as the processing of the request by the service provider proceeds and the status of the request evolves. +- Action** An action allows the SC to update some of the attributes. If the updates are not feasible, the SP returns error messages. If agreed upon in the SLA, the action causes the SP to create an instance of a history record in order to log the action. +- Deletion** When the service is made available to the customer, when the customer has requested cancellation of the service request and the request has been cancelled, when the service provider has determined that the service cannot be provided and has notified the customer thereof. +- Notifications** Object creation, object deletion. + +7) **Notes/Comment** + +I.1.2 **serviceRequestHistoryRecord** + +- 1) **Unique name:** serviceRequestHistoryRecord. +- 2) **Description:** This MO represents historical record of SC initiated change to a pending service request. Values of attributes of this MO are set by the SP at the time of creation, based on an action issued by the SC against a pending request. Values of attributes in this MO cannot be changed. +- 3) **Business purpose:** This MO supports recording of generic information exchanged for the "Modify dedicated leased circuit service function" [3.3.3.1.3], in particular, the attributes in this MO correspond to information items listed in the "Information Flow" table [3.3.3.1.3.2]. +- 4) **Primary identifier:** requestSequenceNumber. + +## 5) Attributes + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|--------------------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Provider request number | R | M | Unique identifier provided by the SP to identify the request. | +| Request reception time | R | M | The time when the service request was received by the service provider. Used to establish an order among requests, and changes to requests. Such ordering may be needed since in case of conflicting changes to a request the most recent change request is effective. | +| Initial service administrative state | R | O | The SC may specify the service administrative state when the service is created. Valid values are:
Unlocked – Indicating that the LCS is available for use (provides service) by the SC.
Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s).
See Figure 5/M.3208.1 for an explanation of the Service Administrative State Model. | +| Service termination date | R | O | The date at which the LCS will be made inactive. If the SC provides a termination date and the SP does not return a date, the requested date is accepted. In case the SP cannot accept the date, an alternate date is provided. | +| Alias name | R | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. | +| Daily scheduling (intervals of day) | R | O | Allows the customer to specify during which periods of the day the service shall be available. | +| Weekly scheduling (week mask) | R | O | Allows the customer to specify during which days of the week the service shall be available. | +| External scheduler (schedule name) | R | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. | +| Service customer contact | R | O | The customer contact information for use by the SP in resolving questions or problems with the service. | +| Service availability date | R | O | Date the service is due to be provisioned and placed in the requested Service Administrative State. | +| Service description | R | O | | +| Service type | R | O | | + +6) **Behaviour description** + +**Creation** By SP when SC wants to modify a request for service. + +**Read** When the SC wants to verify what changes in the service request were requested. + +**Update** + +**Action** + +**Deletion** When the service is provided or when the SP notifies the SC that the requested service cannot be provided. + +**Notifications** Object creation and object deletion. + +7) **Notes/Comment** + +**I.1.3 serviceModifyRequest** + +1) **Unique name:** serviceModifyRequest. + +2) **Description:** This MO represents SC's request to modify an existing service. It is a superclass from which service-specific subclasses are derived. When changes to the service occur as a result of such a modification request, or for any other reason, the MO representing the affected service (e.g. lcs or link connection service) will issue the appropriate attribute value change notifications. After all the modifications requested by the SC through this MO have been resolved, this MO instance will be deleted and a notification of its deletion shall be sent to the SC. + +3) **Business purpose:** This MO represents generic information exchanged for the purpose of modifying an existing service, as described in "Modify dedicated leased circuit service function" [3.3.3.1.3], in particular, attributes in this MO correspond to generic information items in "Information Flow" [3.3.3.1.3.2]. + +4) **Primary identifier:** provider request number. + +5) **Attributes** + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|-------------------------|------------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Provider request number | R | M | Unique identifier provided by the SP to identify the request. | +| Request reception time | R | M | The time when the service request was received by the service provider. Used to establish an order among requests, and changes to requests. Such ordering may be needed since in case of conflicting changes to a request the most recent change request is effective. | +| Service request state | R | M | | +| Service instance | R | M | | +| Alias name | R, W
(at object creation) | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. | + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|----------------------------------------|------------------------------|------------------------|------------------------------------------------------------------------------------------------------------| +| Daily scheduling
(intervals of day) | R, W
(at object creation) | O | Allows the customer to specify during which periods of the day the service shall be available. | +| Weekly scheduling
(week mask) | R, W
(at object creation) | O | Allows the customer to specify during which days of the week the service shall be available. | +| External scheduler
(schedule name) | R, W
(at object creation) | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. | +| Service customer contact | R, W
(at object creation) | O | The customer contact information for use by the SP in resolving questions or problems with the service. | +| Availability status | R, W
(at object creation) | O | | + +## 6) Behaviour description + +**Creation** When a change to an existing service is requested. + +**Read** When the SC wishes to verify what changes were requested or what is the status of the request. + +### Update + +### Action + +**Deletion** When the requested changes have been performed by the SP or when the SP reports to the SC that the requested changes cannot be performed. + +**Notifications** Object creation and object deletion. + +## 7) Notes/Comment + +## I.2 LCS request fragment + +### I.2.1 currentLcsRequest + +1) **Unique name:** currentLcsRequest. + +2) **Description:** This instantiable MO represents an SC request for LCS. + +3) **Business purpose:** Every information element (attribute, notification) in this object is listed in the "Create dedicated leased circuit service function" [3.3.3.1.1] in Recommendation M.3208.1, in particular, the attributes are listed under "Information Flow" [3.3.3.1.1.2]. + +4) **Primary identifier:** See currentServiceRequest. + +5) **Attributes:** See currentServiceRequest, plus: + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|--------------------------|--------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating location | R, W
(at create only) | M | Physical location (e.g. street address) where the LCS originates. | +| Terminating location | R, W
(at create only) | M | Physical location (e.g. street address) where the LCS terminates. | +| Quantity | R, W | O | The number of LCSs to be generated by the SP. | +| Bandwidth | R, W | O | The bandwidth to be provided by the SP. | +| Diversity | R, W | O | Diversity may be specified with respect to existing leased circuit(s) by identification of leased circuit(s) from which this (these) new leased circuit(s) shall be diverse, or by identification of the set of topological entities from which this (these) new leased circuit(s) shall be diverse.

When more than one leased circuit is requested, diversity may be specified within the request. In this case, the SC specifies the number of diverse groups and the number of circuits within each group, and/or a set of topological entities. | +| Route | R, W | O | A sequence of topological entities over which LCS is provided (i.e. connection points, links, subnetworks). The SP may associate user-friendly names (i.e. city names) with such topological entities. | +| Originating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit. | +| Terminating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit. | +| Originating location SAP | R, W | O | Access point where the leased circuit service originates. | +| Terminating location SAP | R, W | O | Access point where the leased circuit service terminates. | + +6) **Behaviour description** + +**Creation** When the SC requests an LCS. + +**Read** When the SC wants to verify the LCS request. + +**Update** When the SC wants to change information in the LCS request or when the SP wants to update information in the LCS request. + +**Action** When the SC wants to change information in the LCS. + +**Deletion** When the SP provides the requested LCS to the SC or when the SP reports to the SC that the requested LCS cannot be provided. + +**Notifications** Object creation, object deletion, attribute value change, report problems in progressing the LCS request. + +- 7) **Notes/Comment** + +#### **I.2.2 lcsRequestHistoryRecord** + +- 1) **Unique name:** lcsRequestHistoryRecord. +- 2) **Description:** This MO provides a historical record of changes to a pending LCS request by the SC. +- 3) **Business purpose:** This MO supports the "Report change of leased circuit service request parameter function" [3.3.3.2.4], in particular, information items in "Information Flow" [3.3.3.2.4.2] and "Retrieve leased circuit service request parameters function [3.3.3.2.9], in particular, information in "Information Flow" [3.3.3.2.9.2]. +- 4) **Primary identifier:** See currentLcsRequest. +- 5) **Attributes:** See currentLcsRequest, but the attribute values cannot change. +- 6) **Behaviour description** + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------| +| Creation | When the SC requests LCS or makes changes to a pending LCS request changes to an LCS request. | +| Read | When the SC wishes to know the current information in the LCS request. | +| Update | | +| Action | | +| Deletion | When the service is provided or when the SP notifies the SC that the requested service cannot be provided. | +| Notifications | Object creation and object deletion. | +- 7) **Notes/Comment** + +#### **I.2.3 lcsModifyRequestRecord** + +- 1) **Unique name:** lcsModifyRequestRecord. +- 2) **Description:** This MO represents a request to modify an existing LCS. +- 3) **Business purpose:** This MO represents information exchanged for the purpose of modifying an existing LCS, as described in "Modify dedicated leased circuit service function" [3.3.3.1.3], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.1.3.2]. +- 4) **Primary identifier:** request sequence number. + +5) **Attributes:** See serviceModifyRequestRecord, plus: + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|--------------------------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bandwidth | R, W | O | The bandwidth to be provided by the SP. | +| Diversity | R, W | O | Diversity may be specified with respect to existing leased circuit(s) by identification of leased circuit(s) from which this (these) new leased circuit(s) shall be diverse, or by identification of the set of topological entities from which this (these) new leased circuit(s) shall be diverse.

When more than one leased circuit is requested, diversity may be specified within the request. In this case, the SC specifies the number of diverse groups and the number of circuits within each group, and/or a set of topological entities. | +| Route | R, W | O | A sequence of topological entities over which LCS is provided (i.e. connection points, links, subnetworks). The SP may associate user-friendly names (i.e. city names) with such topological entities. | +| Originating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit. | +| Terminating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit. | + +6) **Behaviour description** + +**Creation** When the SC wants to change an existing LCS. + +**Read** When the SC wants to verify information in a request to change an existing LCS. + +**Update** + +**Action** + +**Deletion** When the requested changes have been made by the SP or when the SP reports to the SC that the requested changes cannot be performed. + +**Notifications** Object creation, object deletion, progress problem report. + +7) **Notes/Comment** + +### I.3 Link connection service request fragment + +#### I.3.1 currentLinkConnectionServiceRequest + +1) **Unique name:** currentLinkConnectionServiceRequest. + +2) **Description:** This instantiable MO represents an SC request for a link connection. + +3) **Business purpose:** This MO represents information specified in "Create link connection function" [3.3.3.3.1], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.3.1.2]. + +4) **Primary identifier:** provider request number. + +5) **Attributes:** See currentServiceRequest, plus: + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|-------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bandwidth | R, W | O | The bandwidth to be provided by the SP. | +| Originating location CP | R, W | M |

CP or SN, where the Link Connection originates. Must exist prior to provisioning. The SC may not know the name at the time of the request. SP must provide the name of the CP to the SC.

SP cannot provision the service unless the CP is known.

The SC must provide either the originating or terminating location connection point or both.

If one of the points is at the customer premises, that point must be provided by the SC.

If one of the points is in a network of a service provider other than the one receiving this request, it must be provided by the SC.

If the link connection point name is not provided by the SC in the request and the response indicates the completion of the LC and the SC did not provide it in the request, then the value of this parameter must be provided by the SP in the response.

| +| Terminating location CP | R, W | M |

CP or SN, where the link connection terminates. Must exist prior to provisioning. The SC may not know the name at the time of the request. SP must provide the name of the CP to the SC.

SP cannot provision the service unless the CP is known.

If the link connection point name is not provided by the SC in the request and the response indicates the completion of the LC and the SC did not provide it in the request, then the value of this parameter must be provided by the SP in the response.

| + +6) **Behaviour description** + +**Creation** When the SC requests a link connection. + +**Read** When the SC wants to verify a link connection request. + +**Update** When the SC wants to change a link connection request or when the SP has additional information for the link connection request. + +**Action** When the SC wants to change a link connection request. + +**Deletion** When the requested link connection has been provided by the SP or when the SP reports to the SC that the requested link connection cannot be provided. + +**Notifications** Object creation, object deletion, attribute value change. + +7) **Notes/Comment** + +### I.3.2 linkConnectionServiceRequestHistoryRecord + +- 1) **Unique name:** linkConnectionServiceRequestHistoryRecord. +- 2) **Description:** This MO represents a request to update either a previously issued request to create a link connection service, or a previous update against that link connection service request. +- 3) **Business purpose:** This MO supports information exchange specified in "Modify link connection function" [3.3.3.3.3], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.3.2]. +- 4) **Primary identifier:** See serviceUpdateRequestRecord. +- 5) **Attributes:** See serviceRequestHistoryRecord, plus the additional attributes for currentLinkConnectionServiceRequest. +- 6) **Behaviour description** + - Creation** When the SC wants to change an existing link connection request. + - Read** When the SC wants to verify changes request to an existing link connection request. + - Update** + - Action** + - Deletion** When the requested link connection has been provided by the SP or when the SP reports to the SC that the requested link connection cannot be provided. + - Notifications** Object creation, object deletion. +- 7) **Notes/Comment** + +### I.3.3 linkConnectionServiceModifyRequest + +- 1) **Unique name:** linkConnectionServiceModifyRequest. +- 2) **Description:** This MO represents a request to modify an existing link connection. +- 3) **Business purpose:** This MO supports information exchange specified in "Modify link connection function" [3.3.3.3.3], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.3.2]. +- 4) **Primary identifier:** See serviceModifyRequest. +- 5) **Attributes:** See serviceModifyRequest plus: + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|----------------|-------------|------------------------|-----------------------------------------| +| Bandwidth | R, W | O | The bandwidth to be provided by the SP. | + +- 6) **Behaviour description** + - Creation** When the SC wants to change an existing link connection. + - Read** When the SC wants to verify a request for changing an existing link connection. + - Update** + - Action** + +**Deletion** When the requested changes have been implemented by the SP or when the SP reports to the SC that the requested changes cannot be made. + +**Notifications** Object creation, object deletion, link connection modify progress problem report. + +7) **Notes/Comment** + +**I.4 Service fragment** + +**I.4.1 transportService** + +- 1) **Unique name:** transportService. +- 2) **Description:** This MO represents a transport service. This MO class cannot be instantiated; service-specific subclasses of this class can be instantiated. Values of attributes of subclasses of this MO class can be set through management operations or through the creation of an instance of a service-specific subclass of the serviceModifyRequestRecord MO class. It is expected that only one of those two methods for changing values of attributes of subclasses of this MO class will be supported on any specific interface. +- 3) **Business purpose:** This MO supports information exchange specified for "Retrieve link connection parameters by the service customer function" [3.3.3.4.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.4.6.2]. It further supports information exchange specified for "Retrieve leased circuit service parameters by the service customer function" [3.3.3.2.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.2.6.2]. +- 4) **Primary identifier:** service ID. +- 5) **Attributes** + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|--------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service ID | R | M | Circuit number or link connection identifier. | +| Administrative state | R, W | M | Valid values are:

Unlocked – Indicating that the LCS is available for use (provides service) by the SC.
Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s).
See Figure 5/M.3208.1 for an explanation of the Service Administrative State Model. | +| Operational state | R | M | Indicates if the service is operational. Default value if parameter is absent is enabled. | +| Service type | R | M | Corresponds to service name in Recommendation M.3208.1. | +| Service location list | R | M | Represents the originating and terminating locations in Recommendation M.3208.1. | +| Bandwidth | R, W | M | | +| Service provider contact | R | M | The provider contact information for use by the SC in resolving questions or problems with the service. | + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|-------------------------------------|---------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service customer contact | R, W | M | The customer contact information for use by the SP in resolving questions or problems with the service. | +| Service availability date | R, W (at object creation) | M | Customer's requested start date, can be changed by the SP to the actual start date which may be different, depending on availability of SP's resources. | +| Service termination date | R, W | M | Date at which the SC wishes to terminate the service. | +| Alias name | R | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. | +| Service description | R | O | Corresponds to service class in Recommendation M.3208.1. | +| Availability status | R, W | O | | +| Daily scheduling (intervals of day) | R, W | O | Allows the customer to specify during which periods of the day the service shall be available. | +| Weekly scheduling (week mask) | R, W | O | Allows the customer to specify during which days of the week the service shall be available. | +| External scheduler (schedule name) | R, W | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. | + +## 6) Behaviour description + +**Creation** When a requested service is made available by the SP to the SC. + +**Read** When the SC wants to verify the service parameters. + +**Update** When the parameters of the service change as result of a SC request or SP initiative. + +### Action + +**Deletion** When the service is terminated. + +**Notifications** Object creation, object deletion, state change notification, attribute value change, quality of service alarm. + +## 7) Notes/Comment + +### I.4.2 lcs + +1) **Unique name:** lcs. + +2) **Description:** This instantiable MO represents an LCS. + +3) **Business purpose:** This MO supports information exchange specified for "Retrieve leased circuit service parameters by the service customer function" [3.3.3.2.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.2.6.2]. + +4) **Primary identifier:** Service ID. + +5) **Attributes:** See transportService, plus the following attributes: + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|--------------------------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Diversity | R, W | O | Diversity may be specified with respect to existing leased circuit(s) by identification of leased circuit(s) from which this (these) new leased circuit(s) shall be diverse, or by identification of the set of topological entities from which this (these) new leased circuit(s) shall be diverse.

When more than one leased circuit is requested, diversity may be specified within the request. In this case, the SC specifies the number of diverse groups and the number of circuits within each group, and/or a set of topological entities. | +| Route | R, W | O | A sequence of topological entities over which LCS is provided (i.e. connection points, links, subnetworks). The SP may associate user-friendly names (i.e. city names) with such topological entities. | +| Originating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit. | +| Terminating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit. | +| Originating location SAP | R, W | M | Access point where the leased circuit service originates. | +| Terminating location SAP | R, W | M | Access point where the leased circuit service terminates. | + +6) **Behaviour description** + +**Creation** When a requested LCS is provided. + +**Read** When a SC wants to verify the parameters of an LCS. + +**Update** When a SC wants to change some characteristics of an LCS. + +**Action** + +**Deletion** When the LCS is terminated. + +**Notifications** See transportService. + +7) **Notes/Comment** + +#### I.4.3 linkConnectionService + +1) **Unique name:** linkConnectionService. + +2) **Description:** This instantiable MO represents a link connection service. + +3) **Business purpose:** This MO supports information exchange specified for "Retrieve link connection parameters by the service customer function" [3.3.3.4.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.4.6.2]. + +4) **Primary identifier:** service ID. + +5) **Attributes:** See transportService, plus the following attributes: + +| Attribute name | Access mode | Optional/mandatory | Description | +|-------------------------|-------------|--------------------|-------------------------------------------------| +| Originating location CP | R, W | M | CP or SN, where the link connection originates. | +| Terminating location CP | R, W | M | CP or SN, where the link connection terminates. | + +6) **Behaviour description** + +**Creation** When a requested link connection is made available by the SP to the SC. + +**Read** When the SC wants to verify the parameters of a link connection. + +**Update** When the SC wants to change a link connection or when the SP changes a link connection in response to the SC's request or due to other circumstances. + +**Action** + +**Deletion** When the link connection is terminated. + +**Notifications** See transportService. + +7) **Notes/Comment** + +**I.5 Reconfigurable service fragment** + +**I.5.1 serviceAccessDomain** + +1) **Unique name:** serviceAccessDomain. + +2) **Description:** This MO represents a Service Access Domain consisting of Service Access Groups having similar characteristics (e.g. supporting the same bandwidths). + +3) **Business purpose:** This MO represents information exchanged in "Create service access domain function" [3.3.3.7.1], in particular, its attributes correspond to information items in "Information Flow" [3.3.3.7.1.2]. + +4) **Primary identifier:** provider request number (for SAD creation request) or sadId (for existing SAD). + +5) **Attributes** + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|--------------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Provider request number | R | M | SP-specific identifier for a SAD create request. | +| SAD identifier | R | M | Uniquely identifies the SAD. | +| Service type | R | M | Corresponds to service name in Recommendation M.3208.1. | +| Service provider contact | R | M | The provider contact information for use by the SC in resolving questions or problems with the service. | +| Service customer contact | R, W | M | The customer contact information for use by the SP in resolving questions or problems with the service. | +| Alias name | R | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. | +| Service description | R | O | Corresponds to service class in Recommendation M.3208.1. | +| List of SAGs | R, W | M | List of the SAGs making up the SAD. | + +#### 6) Behaviour description + +**Creation** When a SAD is created. + +**Read** When the SC wants to verify the SAD's parameters. + +**Update** When SAGs are added/removed from the SAD. + +##### Action + +**Deletion** When a SAD is deleted. + +**Notifications** Notifications emitted from the object. + +#### 7) Notes/Comment + +### I.5.2 serviceAccessGroup + +1) **Unique name:** serviceAccessGroup. + +2) **Description:** This MO represents a Service Access Group consisting of Service Access Points having similar characteristics (e.g. supporting the same bandwidths). + +3) **Business purpose:** This MO represents information exchanged in "Create service access group function" [3.3.3.7.2]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.7.2.2]; it further represents information exchanged in "Add service access points to service access group function" [3.3.3.7.4]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.7.4.2]. + +4) **Primary identifier:** SAG ID. + +5) **Attributes** + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|----------------------------|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SAG ID | R | M | Uniquely identifies the SAG. | +| List of SAPs | R, W | M | Lists the SAPs that make up the SAG. | +| SAG location | R | M | Physical location (e.g. street address) of the SAG. | +| Alias name | R, W | O | User-friendly name for the SAG. | +| Number of unspecified SAPs | R, W | O | Number of SAPs in the SAG that are not individually identified in the list of SAPs. | +| Administrative state | R, W | O | Valid values are:

Unlocked – Indicating that the LCS is available for use (provides service) by the SC.

Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s). | + +#### 6) Behaviour description + +**Creation** When a SAG is created. + +**Read** When the SC wants to verify the parameters of the SAG. + +**Update** When SAPs are added/removed from the SAG or when other parameters are updated. + +##### Action + +**Deletion** When the SAG is terminated. + +##### Notifications + +#### 7) Notes/Comment + +### I.6 Resource fragment + +#### I.6.1 serviceAccessEquipment + +1) **Unique name:** serviceAccessEquipment. + +2) **Description:** The serviceAccessEquipment MO class represents customer-owned equipment that terminates the LCS. + +3) **Business purpose:** This MO represents information exchanged in "Access equipment status update function" [3.3.3.9.1]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.9.1.2]; it further represents information exchanged in "Access equipment status inquiry function" [3.3.3.9.2]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.9.2.2]. + +4) **Primary identifier:** equipment ID. + +##### 5) Attributes + +| Attribute name | Access mode | Optional/
Mandatory | Description | +|-------------------------------|-------------|------------------------|--------------------------------------------| +| Equipment ID | R, W | M | SC-provided unique identifier for the CPE. | +| SAP | R, W | M | SAP connected to the equipment. | +| Location address | R, W | M | Physical location of the CPE. | +| Administrative state | R, W | O | | +| Operational state | R, W | O | | +| Equipment type | R, W | O | | +| Equipment manufacturer | R, W | O | | +| Model type | R, W | O | | +| Date of installation | R, W | O | | +| Expected date of installation | R, W | O | | +| Procedure | R, W | O | | + +#### 6) Behaviour description + +**Creation** When the CPE is connected to a LCS or to a link connection. + +**Read** When the SP wants to verify CPE parameters. + +**Update** When the SC changes the CPE. + +**Action** + +**Deletion** When the CPE is not connected to any service provided by the SP. + +**Notifications** Object creation, object deletion. + +#### 7) Notes/Comment + +### APPENDIX II + +#### Mapping of M.3208.1 functions into M.3108.1 MOs + +The mapping provided here refers to each function in Recommendation M.3208.1 by its clause number and title. Functions are grouped under the corresponding M.3208.1 function sets. For each M.3208.1 function, this mapping indicates one or more M.3108.1 MOs that may be used to support that function. In general, if more than one MO is indicated, then the decision on which MO(s) to select for that function is a local matter based on local business practices. + +NOTE – Recommendation M.3208.1 does not include an explicit function specifying that the SP needs to keep a log of the SC's changes to a pending service request. However, this functionality is implicit in the request sequence number that the SP issues for every SC's modification of a pending service request. This is reflected by the inclusion of the history records in the modify services in the following: + +| M.3208.1
subclause
| M.3208.1
Functions
| M.3108.1
Managed objects
| +|-------------------------------|-----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3.3.3.1 | Dedicated leased circuit service configuration function set | | +| 3.3.3.1.1 | Create dedicated leased circuit service function | currentLcsRequest | +| 3.3.3.1.2 | Delete dedicated leased circuit service function | lcs | +| 3.3.3.1.3 | Modify dedicated leased circuit service function | lcs
lcsModifyRequestRecord
currentLcsRequest
lcsRequestHistoryRecord | +| 3.3.3.1.4 | Cancel dedicated leased circuit service request function | currentLcsRequest | +| 3.3.3.2 | Dedicated leased circuit service status administration function set | | +| 3.3.3.2.1 | Report creation of leased circuit service to service customer function | lcs | +| 3.3.3.2.2 | Report deletion of leased circuit service to service customer function | lcs | +| 3.3.3.2.3 | Report configuration change of leased circuit service parameters to service customer function | lcs | +| 3.3.3.2.4 | Report change of leased circuit service request parameters function | currentLcsRequest | +| 3.3.3.2.5 | Control leased circuit service administrative state by the service customer function | lcs | +| 3.3.3.2.6 | Retrieve leased circuit service parameters by the service customer function | lcs | +| 3.3.3.2.7 | Monitor progress of the leased circuit service request function | currentLcsRequest | +| 3.3.3.2.8 | Report progress of the leased circuit service request function | currentLcsRequest | +| 3.3.3.2.9 | Retrieve leased circuit service request parameters function | currentLcsRequest | +| 3.3.3.3 | Link connection configuration service function set | currentLinkConnectionServiceRequest | +| 3.3.3.3.1 | Create link connection function | linkConnectionService | +| 3.3.3.3.2 | Delete link connection function | linkConnectionService | +| 3.3.3.3.3 | Modify link connection function | linkConnectionServiceModifyRequestRecord
currentLinkConnectionServiceRequest
linkConnectionServiceRequestHistoryRecord
linkConnectionService | +| 3.3.3.3.4 | Cancel link connection request function | currentLinkConnectionServiceRequest | + +| M.3208.1
subclause
| M.3208.1
Functions
| M.3108.1
Managed objects
| +|-------------------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| 3.3.3.4 | Link connection status administration function set | | +| 3.3.3.4.1 | Report creation of link connection to service customer function | linkConnectionService | +| 3.3.3.4.2 | Report deletion of link connection to service customer function | linkConnectionService | +| 3.3.3.4.3 | Report configuration change of link connection parameters to service customer function | linkConnectionService | +| 3.3.3.4.4 | Report change of link connection request parameters function | currentLinkConnectionServiceRequest
linkConnectionServiceModifyRequestRecord | +| 3.3.3.4.5 | Control link connection administrative state by the service customer function | linkConnectionService | +| 3.3.3.4.6 | Retrieve link connection parameters by the service customer function | linkConnectionService | +| 3.3.3.4.7 | Monitor progress of the link connection request function | currentLinkConnectionServiceRequest | +| 3.3.3.4.8 | Report progress of the link connection request function | currentLinkConnectionServiceRequest | +| 3.3.3.4.9 | Retrieve link connection request parameters function | currentLinkConnectionServiceRequest | +| 3.3.3.5 | Reconfigurable leased circuit service configuration function set | serviceAccessDomain
serviceAccessGroup | +| 3.3.3.6 | Reconfigurable leased circuit service function set | serviceAccessDomain
serviceAccessGroup | +| 3.3.3.7 | Service access domain configuration function set | serviceAccessDomain | +| 3.3.3.7.1 | Create service access domain function | serviceAccessDomain | +| 3.3.3.7.2 | Create service access group function | serviceAccessGroup | +| 3.3.3.7.3 | Delete service access group function | serviceAccessGroup | +| 3.3.3.7.4 | Add service access points to service access group function | serviceAccessGroup | +| 3.3.3.7.5 | Remove service access points from service access group function | serviceAccessGroup | +| 3.3.3.8 | Reconfigurable leased circuit service administration function set | see 3.3.3.2/M.3208.1 for all functions in this set | +| 3.3.3.9 | Access equipment status administration function set | | +| 3.3.3.9.1 | Access equipment status update function | serviceAccessEquipment | +| 3.3.3.9.2 | Access equipment status inquiry function | serviceAccessEquipment | + +## APPENDIX III + +### UML diagrams for leased circuit service object model + +#### III.1 Introduction + +This appendix provides UML (Unified Modelling Language) diagrams to assist in explanation of the M.3208.1 leased circuit service object model. + +#### III.2 UML class diagrams for inheritance of M.3208.1 object classes + +In these diagrams (Figures III.1 to III.5), classes are shown as boxes with three sections, including: object class name in the top section; the attribute names in the second section (not filled in for these figures for readability); and access operations in the bottom section. + +The operation "get( )" is used in the class diagrams to denote that the class attributes are readable after an instance of that class is created. + +The operation "set( )" is used to denote that some (at least one) of the class attributes may be modified after an instance of that class is created. + +UML class diagrams use large open-headed arrows to indicate inheritance relationships. When a class is related to another by inheritance, the operations from the superclass (the one which has the large arrowhead touching it) are also supported for the inherited class, but are not repeated in the operation section of the class box. + +![UML class diagram showing inheritance relationships for generic service request fragment. A 'top' class is at the top, with three classes below it: 'serviceModifyRequest', 'serviceRequestHistoryRecord', and 'currentServiceRequest'. Arrows point from each of these three classes up to the 'top' class. The 'serviceModifyRequest' class has 'get()' and 'delete()' operations. The 'serviceRequestHistoryRecord' class has 'get()' operation. The 'currentServiceRequest' class has 'get()', 'updateServiceRequest()', and 'delete()' operations. The 'top' class has three empty sections. A label 'T0410070-98' is at the bottom right.](42f0611a8a2766c986ff45551918ca5d_img.jpg) + +``` +classDiagram + class top + class serviceModifyRequest { + get() + delete() + } + class serviceRequestHistoryRecord { + get() + } + class currentServiceRequest { + get() + updateServiceRequest() + delete() + } + top <|-- serviceModifyRequest + top <|-- serviceRequestHistoryRecord + top <|-- currentServiceRequest +``` + +UML class diagram showing inheritance relationships for generic service request fragment. A 'top' class is at the top, with three classes below it: 'serviceModifyRequest', 'serviceRequestHistoryRecord', and 'currentServiceRequest'. Arrows point from each of these three classes up to the 'top' class. The 'serviceModifyRequest' class has 'get()' and 'delete()' operations. The 'serviceRequestHistoryRecord' class has 'get()' operation. The 'currentServiceRequest' class has 'get()', 'updateServiceRequest()', and 'delete()' operations. The 'top' class has three empty sections. A label 'T0410070-98' is at the bottom right. + +Figure III.1/M.3108.1 – Inheritance relationships for generic service request fragment + +![UML class diagram showing inheritance relationships for LCS request fragment. Three classes are at the top: 'currentServiceRequest', 'serviceRequestHistoryRecord', and 'serviceModifyRequest'. Below each of these classes is another class: 'currentLcsRequest', 'lcsRequestHistoryRecord', and 'lcsModifyRequest'. Arrows point from each of these three bottom classes up to the corresponding top class. The 'currentServiceRequest' class has 'get()', 'updateServiceRequest()', and 'delete()' operations. The 'serviceRequestHistoryRecord' class has 'get()' operation. The 'serviceModifyRequest' class has 'get()' and 'delete()' operations. The bottom classes are empty. A label 'T0410080-98' is at the bottom right.](cdc21bbfcba380e98ece42e5b8da50bb_img.jpg) + +``` +classDiagram + class currentServiceRequest { + get() + updateServiceRequest() + delete() + } + class serviceRequestHistoryRecord { + get() + } + class serviceModifyRequest { + get() + delete() + } + class currentLcsRequest + class lcsRequestHistoryRecord + class lcsModifyRequest + currentLcsRequest <|-- currentServiceRequest + lcsRequestHistoryRecord <|-- serviceRequestHistoryRecord + lcsModifyRequest <|-- serviceModifyRequest +``` + +UML class diagram showing inheritance relationships for LCS request fragment. Three classes are at the top: 'currentServiceRequest', 'serviceRequestHistoryRecord', and 'serviceModifyRequest'. Below each of these classes is another class: 'currentLcsRequest', 'lcsRequestHistoryRecord', and 'lcsModifyRequest'. Arrows point from each of these three bottom classes up to the corresponding top class. The 'currentServiceRequest' class has 'get()', 'updateServiceRequest()', and 'delete()' operations. The 'serviceRequestHistoryRecord' class has 'get()' operation. The 'serviceModifyRequest' class has 'get()' and 'delete()' operations. The bottom classes are empty. A label 'T0410080-98' is at the bottom right. + +Figure III.2/M.3108.1 – Inheritance relationships for LCS request fragment + +![UML class diagram showing inheritance relationships for link connection service request fragment. It includes classes: currentServiceRequest, serviceRequestHistoryRecord, serviceModifyRequest, currentLinkConnectionServiceRequest, and linkConnectionServiceModifyRequest. Operations include get(), updateServiceRequest(), and delete().](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +``` + +classDiagram + class currentServiceRequest { + get() + updateServiceRequest() + delete() + } + class serviceRequestHistoryRecord { + get() + } + class serviceModifyRequest { + get() + delete() + } + class currentLinkConnectionServiceRequest + class linkConnectionServiceModifyRequest + class linkConnectionServiceRequestHistoryRecord + + currentLinkConnectionServiceRequest --|> currentServiceRequest + linkConnectionServiceRequestHistoryRecord --|> serviceRequestHistoryRecord + linkConnectionServiceModifyRequest --|> serviceModifyRequest + +``` + +T0410090-98 + +UML class diagram showing inheritance relationships for link connection service request fragment. It includes classes: currentServiceRequest, serviceRequestHistoryRecord, serviceModifyRequest, currentLinkConnectionServiceRequest, and linkConnectionServiceModifyRequest. Operations include get(), updateServiceRequest(), and delete(). + +**Figure III.3/M.3108.1 – Inheritance relationships for link connection service request fragment** + +![UML class diagram showing inheritance relationships for reconfigurable service fragment. It includes classes: top, ServiceAccessDomain, and ServiceAccessGroup. Operations include get(), set(), and delete().](d31b402b650e68c7d6b55d3cf8fda086_img.jpg) + +``` + +classDiagram + class top + class ServiceAccessDomain { + get() + set() + delete() + } + class ServiceAccessGroup { + get() + set() + delete() + } + ServiceAccessDomain --|> top + ServiceAccessGroup --|> top + +``` + +Reconfigurable service fragment + +UML class diagram showing inheritance relationships for reconfigurable service fragment. It includes classes: top, ServiceAccessDomain, and ServiceAccessGroup. Operations include get(), set(), and delete(). + +![UML class diagram showing inheritance relationships for resource fragment. It includes classes: top and ServiceAccessEquipmentView. Operations include get(), set(), and delete().](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +classDiagram + class top + class ServiceAccessEquipmentView { + get() + set() + delete() + } + ServiceAccessEquipmentView --|> top + +``` + +T0410100-98 + +Resource fragment + +UML class diagram showing inheritance relationships for resource fragment. It includes classes: top and ServiceAccessEquipmentView. Operations include get(), set(), and delete(). + +**Figure III.4/M.3108.1 – Inheritance relationships for resource fragment and reconfigurable service fragment** + +![UML class diagram showing inheritance relationships. A 'top' class is at the top. Below it is a 'transportService' class with methods get(), set(), and delete(). At the bottom are two classes, 'lcs' and 'linkConnectionService', which inherit from 'transportService'. A small code 'T0410110-98' is at the bottom right.](f78d2e126f00fcc5d8d9797ca410cc09_img.jpg) + +``` + +classDiagram + top <|-- transportService + lcs <|-- transportService + linkConnectionService <|-- transportService + class top + class transportService { + get() + set() + delete() + } + class lcs + class linkConnectionService + +``` + +T0410110-98 + +UML class diagram showing inheritance relationships. A 'top' class is at the top. Below it is a 'transportService' class with methods get(), set(), and delete(). At the bottom are two classes, 'lcs' and 'linkConnectionService', which inherit from 'transportService'. A small code 'T0410110-98' is at the bottom right. + +**Figure III.5/M.3108.1 – Inheritance relationships for service fragment** + +### III.3 UML class diagrams for modelling relationships + +The possible relationships between instances are shown in UML class diagrams with associations (Figures III.6 and III.7). Containment relationships are denoted by a diamond headed line touching the parent (UML aggregation). Simple associations are shown with lines with roles indicates on the line ends. Relationship cardinalities are indicated by "0..\*" or "1..\*" tags on the end of the line representing a relationship. + +![UML class diagram showing containment relationships. An 'account' class is at the top with a 'get()' method. Below it is a 'currentLinkConnectionServiceRequest' class. At the bottom is a 'linkConnectionServiceRequestHistoryRecord' class. Arrows with cardinalities point from the bottom class to the middle, and from the middle class to the top. A small code 'T0410120-98' is at the bottom right.](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +``` + +classDiagram + account "0..*" <|-- currentLinkConnectionServiceRequest + currentLinkConnectionServiceRequest "1..*" <|-- linkConnectionServiceRequestHistoryRecord + class account { + get() + } + class currentLinkConnectionServiceRequest + class linkConnectionServiceRequestHistoryRecord + +``` + +T0410120-98 + +UML class diagram showing containment relationships. An 'account' class is at the top with a 'get()' method. Below it is a 'currentLinkConnectionServiceRequest' class. At the bottom is a 'linkConnectionServiceRequestHistoryRecord' class. Arrows with cardinalities point from the bottom class to the middle, and from the middle class to the top. A small code 'T0410120-98' is at the bottom right. + +**Figure III.6/M.3108.1 – Containment relationships for link connection service request with history records** + +![UML class diagram showing containment relationships for LCS request with history records. The diagram includes three classes: 'account', 'currentLcsRequest', and 'lcsRequestHistoryRecord'. 'account' has a method 'get()'. 'currentLcsRequest' has a 0..* association with 'account'. 'lcsRequestHistoryRecord' has a 1..* association with 'currentLcsRequest'. The identifier 'T0410130-98' is at the bottom right.](e404de9a69c05473fbd6af28ee32311b_img.jpg) + +``` + +classDiagram + account <|-- currentLcsRequest : 0..* + currentLcsRequest <|-- lcsRequestHistoryRecord : 1..* + class account { + get() + } + class currentLcsRequest + class lcsRequestHistoryRecord + +``` + +UML class diagram showing containment relationships for LCS request with history records. The diagram includes three classes: 'account', 'currentLcsRequest', and 'lcsRequestHistoryRecord'. 'account' has a method 'get()'. 'currentLcsRequest' has a 0..\* association with 'account'. 'lcsRequestHistoryRecord' has a 1..\* association with 'currentLcsRequest'. The identifier 'T0410130-98' is at the bottom right. + +**Figure III.7/M.3108.1 – Containment relationships for LCS request with history records** + +In Figure III.8, associations from account to service customer and service provider are shown, even though the classes "service customer" and "service provider" are not exposed as managed objects. + +![UML class diagram showing relationships beyond service creation and update. The diagram includes classes: 'serviceProvider', 'serviceCustomer', 'account', 'ServiceAccessEquipmentView', 'linkConnectionService', 'lcs', 'ServiceAccessDomain', 'ServiceAccessGroup', 'linkConnectionServiceModifyRequest', and 'lcsModifyRequest'. 'account' is central, with associations to 'serviceProvider' (+accountProvider), 'serviceCustomer' (+accountCustomer), 'ServiceAccessEquipmentView', 'linkConnectionService', 'lcs', 'ServiceAccessDomain', and 'ServiceAccessGroup'. 'ServiceAccessEquipmentView', 'ServiceAccessDomain', and 'ServiceAccessGroup' have methods 'get()', 'set()', and 'delete()'. 'linkConnectionServiceModifyRequest' and 'lcsModifyRequest' have associations with 'linkConnectionService' and 'lcs' respectively. A note indicates 'serviceProvider' and 'serviceCustomer' are not exposed as managed objects. The identifier 'T0410140-98' is at the bottom right.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +``` + +classDiagram + account "0..*" -- "0..*" serviceProvider : +accountProvider + account "0..*" -- "0..*" serviceCustomer : +accountCustomer + account "0..*" -- "0..*" ServiceAccessEquipmentView + account "0..*" -- "0..*" linkConnectionService + account "0..*" -- "0..*" lcs + account "0..*" -- "0..*" ServiceAccessDomain + account "0..*" -- "0..*" ServiceAccessGroup + ServiceAccessEquipmentView --> account + linkConnectionService --> account + lcs --> account + ServiceAccessDomain --> account + ServiceAccessGroup --> account + linkConnectionServiceModifyRequest --> linkConnectionService : 0..* + lcsModifyRequest --> lcs : 0..* + note for serviceProvider "These are not exposed as managed objects" + class account { + get() + } + class serviceProvider + class serviceCustomer + class ServiceAccessEquipmentView { + get() + set() + delete() + } + class linkConnectionService + class lcs + class ServiceAccessDomain { + get() + set() + delete() + } + class ServiceAccessGroup { + get() + set() + delete() + } + class linkConnectionServiceModifyRequest + class lcsModifyRequest + +``` + +UML class diagram showing relationships beyond service creation and update. The diagram includes classes: 'serviceProvider', 'serviceCustomer', 'account', 'ServiceAccessEquipmentView', 'linkConnectionService', 'lcs', 'ServiceAccessDomain', 'ServiceAccessGroup', 'linkConnectionServiceModifyRequest', and 'lcsModifyRequest'. 'account' is central, with associations to 'serviceProvider' (+accountProvider), 'serviceCustomer' (+accountCustomer), 'ServiceAccessEquipmentView', 'linkConnectionService', 'lcs', 'ServiceAccessDomain', and 'ServiceAccessGroup'. 'ServiceAccessEquipmentView', 'ServiceAccessDomain', and 'ServiceAccessGroup' have methods 'get()', 'set()', and 'delete()'. 'linkConnectionServiceModifyRequest' and 'lcsModifyRequest' have associations with 'linkConnectionService' and 'lcs' respectively. A note indicates 'serviceProvider' and 'serviceCustomer' are not exposed as managed objects. The identifier 'T0410140-98' is at the bottom right. + +**Figure III.8/M.3108.1 – UML model for relationships beyond service creation and update** + +### III.4 UML class diagrams for modelling agent functionality + +Some UML classes are introduced (factories and notification dispatcher) to model the actions for creating objects and distributing notifications from objects (Figure III.9). Instances of these agent functionality classes appear in the sequence diagrams. When a notification operation invocation is made onto a notification dispatch object, all destinations which have registered interest will receive a copy of that notification. These final delivery flows are not shown in the sequence diagrams in III.5, since many object may be interested in receiving them. + +![UML class diagram for objectFactory class. The class box contains the name 'objectFactory' and a list of 10 operations, each preceded by a diamond symbol. A dashed line connects the class to a note box on the right containing text about OSI Systems Management.](364054adcd1b427fa259450e006c6b38_img.jpg) + +``` +classDiagram + class objectFactory { + ◆ create_currentLcsServiceRequest() + ◆ create_currentLinkConnectionServiceRequest() + ◆ create_lcsModifyRequest() + ◆ create_linkConnectionServiceModifyRequest() + ◆ create_lcs() + ◆ create_linkConnectionService() + ◆ create_serviceAccessDomain() + ◆ create_serviceAccessGroup() + ◆ create_serviceAccessEquipmentView() + } + note right of objectFactory: For OSI Systems Management, these capabilities are provided by the Agent. +``` + +UML class diagram for objectFactory class. The class box contains the name 'objectFactory' and a list of 10 operations, each preceded by a diamond symbol. A dashed line connects the class to a note box on the right containing text about OSI Systems Management. + +Factory with operations for customer to create service and request objects + +![UML class diagram for notificationDispatcher class. The class box contains the name 'notificationDispatcher' and a list of 7 operations, each preceded by a diamond symbol. A dashed line connects the class to a note box on the right containing text about OSI Systems Management and Event Forwarding.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +``` +classDiagram + class notificationDispatcher { + ◆ objectCreation() + ◆ attributeValueChange() + ◆ objectDeletion() + ◆ lcsModifyProgressProblemReport() + ◆ lcsRequestProgressProblemReport() + ◆ linkConnectionModifyProgressProblemReport() + ◆ linkConnectionRequestProgressProblemReport() + } + note right of notificationDispatcher: For OSI Systems Management, these capabilities are provided by Event Forwarding. +``` + +UML class diagram for notificationDispatcher class. The class box contains the name 'notificationDispatcher' and a list of 7 operations, each preceded by a diamond symbol. A dashed line connects the class to a note box on the right containing text about OSI Systems Management and Event Forwarding. + +Notification Dispatcher to receive and distribute notifications + +T0410150-98 + +**Figure III.9/M.3108.1 – UML model for agent functions (creating objects and disseminating notifications)** + +### III.5 UML sequence diagrams to illustrate scenarios of object usage + +The sequence diagrams (Figures III.10 to III.15) in this subclause illustrate various scenarios discussed in the overview in clause 5. + +The message flows from the notification dispatcher to the ultimate registered destinations are not shown in these diagrams. It would be normal for the customer (as well as other objects) to be a registered recipient for the notifications shown in these sequence diagrams). + +![UML sequence diagram for explicit LCS create and automatic termination. Lifelines: customer, notification Dispatcher, objectFactory, lcs. The diagram shows 8 messages: 1. create_lcs(), 2. createResponse, 3. objectCreation(), 4. get(), 5. getResponse, 6. set(), 7. setResponse, 8. objectDeletion(). Annotations explain each step: Successful creation of LCS, Customer reads attribute values, Customer sets service termination date, Provider terminates lcs at termination date.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` +sequenceDiagram + participant customer + participant notification Dispatcher + participant objectFactory + participant lcs + + Note right of lcs: Successful creation of LCS + customer->>objectFactory: 1: create_lcs() + objectFactory-->>customer: 2: createResponse + objectFactory->>lcs: 3: objectCreation() + Note right of lcs: Customer reads attribute values + customer->>lcs: 4: get() + lcs-->>customer: 5: getResponse + customer->>lcs: 6: set() + Note right of lcs: Customer sets service termination date + lcs-->>customer: 7: setResponse + Note right of lcs: Provider terminates lcs at termination date + lcs->>objectFactory: 8: objectDeletion() +``` + +T0410160-98 + +UML sequence diagram for explicit LCS create and automatic termination. Lifelines: customer, notification Dispatcher, objectFactory, lcs. The diagram shows 8 messages: 1. create\_lcs(), 2. createResponse, 3. objectCreation(), 4. get(), 5. getResponse, 6. set(), 7. setResponse, 8. objectDeletion(). Annotations explain each step: Successful creation of LCS, Customer reads attribute values, Customer sets service termination date, Provider terminates lcs at termination date. + +**Figure III.10/M.3108.1 – Sequence diagram for explicit LCS create and automatic termination** + +![UML Sequence diagram for instantiation of LCS using request and explicit deletion. Lifelines: customer, notificationDispatcher, objectFactory, currentLcsRequest, lcs. The diagram shows 12 messages with associated notes explaining each step.](5e05915b2a93a3b404422e0966a7c924_img.jpg) + +``` + +sequenceDiagram + participant customer + participant notificationDispatcher + participant objectFactory + participant currentLcsRequest + participant lcs + + Note right of lcs: Successful request creation + customer->>objectFactory: 1: create_currentLcsServiceRequest() + objectFactory->>notificationDispatcher: 2: createResponse + Note right of lcs: Customer reads current request + customer->>currentLcsRequest: 3: get() + currentLcsRequest->>notificationDispatcher: 4: getResponse + Note right of lcs: Provider changes request values + lcs->>notificationDispatcher: 5: attributeValueChange() + Note right of lcs: Provider instantiates lcs and destroys + objectFactory->>notificationDispatcher: 6: objectCreation() + notificationDispatcher->>currentLcsRequest: 7: objectDeletion() + Note right of lcs: Customer reads lcs attribute + customer->>currentLcsRequest: 8: get() + currentLcsRequest->>customer: 9: getResponse + Note right of lcs: customer terminates lcs + customer->>currentLcsRequest: 10: delete() + currentLcsRequest->>customer: 11: deleteResponse + lcs->>notificationDispatcher: 12: objectDeletion() + +``` + +The sequence diagram illustrates the interaction for instantiating an LCS. It begins with the customer sending a `create_currentLcsServiceRequest()` message to the objectFactory, which responds with `createResponse` to the notificationDispatcher. A note indicates this is a 'Successful request creation'. Next, the customer sends a `get()` message to the currentLcsRequest, which responds with `getResponse` to the notificationDispatcher; a note indicates the 'Customer reads current request'. The lcs lifeline then sends an `attributeValueChange()` message to the notificationDispatcher, with a note that the 'Provider changes request values'. This is followed by `objectCreation()` from objectFactory to notificationDispatcher and `objectDeletion()` from notificationDispatcher to currentLcsRequest, with a note that the 'Provider instantiates lcs and destroys'. The customer then sends another `get()` message to currentLcsRequest, which responds with `getResponse` directly to the customer; a note indicates the 'Customer reads lcs attribute'. Finally, the customer sends a `delete()` message to currentLcsRequest, which responds with `deleteResponse` to the customer; a note indicates the 'customer terminates lcs'. The lcs lifeline sends a final `objectDeletion()` message to the notificationDispatcher. + +UML Sequence diagram for instantiation of LCS using request and explicit deletion. Lifelines: customer, notificationDispatcher, objectFactory, currentLcsRequest, lcs. The diagram shows 12 messages with associated notes explaining each step. + +T0410170-98 + +**Figure III.11/M.3108.1 – Sequence diagram for instantiation of LCS using request and explicit deletion** + +![Sequence diagram for instantiation of LCS using request and history records. Lifelines: customer, notification Dispatcher, object Factory, currentLcs Request, lcsRequest HistoryRec1, lcsRequest HistoryRec2, lcs. The diagram shows 18 messages with associated callouts explaining the steps.](caeb1637753f79f4cd005eda3768d1d5_img.jpg) + +``` + +sequenceDiagram + participant customer + participant notification Dispatcher + participant object Factory + participant currentLcs Request + participant lcsRequest HistoryRec1 + participant lcsRequest HistoryRec2 + participant lcs + + Note right of lcs: Successful creation of LCS request and history record 1 + customer->>object Factory: 1: create_currentLcsServiceRequest() + object Factory-->>notification Dispatcher: 2: createResponse + notification Dispatcher-->>customer: + object Factory->>lcsRequest HistoryRec1: 3: objectCreation() + customer->>currentLcs Request: 4: get() + currentLcs Request-->>notification Dispatcher: 5: getResponse + notification Dispatcher-->>customer: + currentLcs Request->>notification Dispatcher: 6: attributeValueChange() + Note right of lcs: Customer reads request + customer->>lcsRequest HistoryRec1: 7: get() + lcsRequest HistoryRec1-->>notification Dispatcher: 8: getResponse + notification Dispatcher-->>customer: + Note right of lcs: Provider changes a requested value + customer->>currentLcs Request: 9: updateServiceRequest() + currentLcs Request-->>notification Dispatcher: 10: updateResponse + notification Dispatcher-->>customer: + Note right of lcs: Customer reads original request + currentLcs Request->>notification Dispatcher: 11: attributeValueChange() + Note right of lcs: Customer updates request causing history record 2 + currentLcs Request->>lcsRequest HistoryRec2: 12: objectCreation() + currentLcs Request->>notification Dispatcher: 13: objectCreation() + currentLcs Request->>notification Dispatcher: 14: objectDeletion() + currentLcs Request->>lcsRequest HistoryRec1: 15: objectDeletion() + currentLcs Request->>notification Dispatcher: 16: objectDeletion() + Note right of lcs: Provider instantiates lcs then destroys request and history records + customer->>lcs: 17: get() + lcs-->>notification Dispatcher: 18: getResponse + notification Dispatcher-->>customer: + Note right of lcs: Customer reads lcs attributes + +``` + +Sequence diagram for instantiation of LCS using request and history records. Lifelines: customer, notification Dispatcher, object Factory, currentLcs Request, lcsRequest HistoryRec1, lcsRequest HistoryRec2, lcs. The diagram shows 18 messages with associated callouts explaining the steps. + +T0410180-98 + +Figure III.12/M.3108.1 – Sequence diagram for instantiation of LCS using request and history records + +![Sequence diagram for modification of existing LCS. Lifelines: customer, notification Dispatcher, object Factory, lcs, lcsModify Request. The sequence shows the customer interacting with the lcs object to get and set attributes, then creating a lcsModifyRequest to change attributes, and finally getting the response and destroying the request.](5cc4a2ef554f31ea0577731931007fff_img.jpg) + +``` + +sequenceDiagram + participant customer + participant notification Dispatcher + participant object Factory + participant lcs + participant lcsModify Request + + Note right of lcsModify Request: Customer reads lcs attribute values + customer->>lcs: 1: get() + lcs-->>customer: 2: getResponse + Note right of lcsModify Request: Customer changes settable lcs attributes, subject to SLA provisions + customer->>lcs: 3: set() + lcs-->>customer: 4: setResponse + lcs->>notification Dispatcher: 5: attributeValueChange() + Note right of lcsModify Request: Customer creates request to change lcs attributes subject to SLA provisions + customer->>object Factory: 6: create_lcsModifyRequest() + object Factory-->>customer: 7: createResponse + lcs->>lcsModify Request: 8: objectCreation() + Note right of lcsModify Request: Customer reads modify request + customer->>lcsModify Request: 9: get() + lcsModify Request-->>customer: 10: getResponse + Note right of lcsModify Request: Provider changes lcs attributes and destroys request + lcs->>notification Dispatcher: 11: attributeValueChange() + lcs->>notification Dispatcher: 12: objectDeletion() + +``` + +T0410190-98 + +Sequence diagram for modification of existing LCS. Lifelines: customer, notification Dispatcher, object Factory, lcs, lcsModify Request. The sequence shows the customer interacting with the lcs object to get and set attributes, then creating a lcsModifyRequest to change attributes, and finally getting the response and destroying the request. + +**Figure III.13/M.3108.1 – Sequence diagram for modification of existing LCS** + +![Sequence diagram for unsuccessful LCS instantiation using request without history. Lifelines: customer, notification Dispatcher, objectFactory, currentLcs Request. The sequence shows the customer creating a currentLcsServiceRequest, getting a response, then interacting with the currentLcs Request object to get, update, and delete it, with progress notifications being sent.](2b60ebe01f77d22e53da1fbe73083b01_img.jpg) + +``` + +sequenceDiagram + participant customer + participant notification Dispatcher + participant objectFactory + participant currentLcs Request + + Note right of currentLcs Request: Customer creates request + customer->>objectFactory: 1: create_currentLcsServiceRequest() + objectFactory-->>customer: 2: createResponse + Note right of currentLcs Request: Customer reads current request + customer->>currentLcs Request: 3: get() + currentLcs Request-->>customer: 4: getResponse + Note right of currentLcs Request: Progress problem notification + currentLcs Request->>notification Dispatcher: 5: lcsRequestProgressProblemReport() + Note right of currentLcs Request: Customer updates request + customer->>currentLcs Request: 6: updateServiceRequest() + currentLcs Request-->>customer: 7: updateResponse + Note right of currentLcs Request: Progress problem notification + currentLcs Request->>notification Dispatcher: 8: lcsRequestProgressProblemReport() + Note right of currentLcs Request: Customer cancels request + customer->>currentLcs Request: 9: delete() + currentLcs Request-->>customer: 10: deleteResponse + currentLcs Request->>notification Dispatcher: 11: objectDeletion() + +``` + +T0410200-98 + +Sequence diagram for unsuccessful LCS instantiation using request without history. Lifelines: customer, notification Dispatcher, objectFactory, currentLcs Request. The sequence shows the customer creating a currentLcsServiceRequest, getting a response, then interacting with the currentLcs Request object to get, update, and delete it, with progress notifications being sent. + +**Figure III.14/M.3108.1 – Sequence diagram for unsuccessful LCS instantiation using request without history** + +![Sequence diagram for unsuccessful LCS modification followed by LCS deletion. Lifelines: customer, notification Dispatcher, object Factory, lcs, lcsModify Request. The diagram shows 14 messages. The modification attempt (set()) fails, returning an error response. The customer then creates a modification request, which results in notifications. Finally, the customer cancels the request and explicitly deletes the lcs object.](d546a282ce562b4930a36fcf2ec3e7b3_img.jpg) + +``` + +sequenceDiagram + participant customer + participant notification Dispatcher + participant object Factory + participant lcs + participant lcsModify Request + + Note right of lcsModify Request: Customer reads lcs attribute values + customer->>lcs: 1: get() + lcs-->>customer: 2: getResponse + + Note right of lcsModify Request: Customer tries to set lcs attributes, without success + customer->>lcs: 3: set() + lcs-->>customer: 4: setErrorResponse + + Note right of lcsModify Request: Customer creates request to change lcs attributes, subject to SLA provisions + customer->>object Factory: 5: create_lcsModifyRequest() + object Factory-->>customer: 6: createResponse + + Note right of lcsModify Request: Notification of modify problem + object Factory->>notification Dispatcher: 7: objectCreation() + notification Dispatcher->>lcsModify Request: 8: lcsModifyProgressProblemReport() + + Note right of lcsModify Request: Customer cancels modification request + customer->>lcsModify Request: 9: delete() + lcsModify Request-->>customer: 10: deleteResponse + + Note right of lcsModify Request: Customer terminates lcs by explicit deletion + object Factory->>notification Dispatcher: 11: objectDeletion() + customer->>lcs: 12: delete() + lcs-->>customer: 13: deleteResponse + notification Dispatcher->>object Factory: 14: objectDeletion() + +``` + +Sequence diagram for unsuccessful LCS modification followed by LCS deletion. Lifelines: customer, notification Dispatcher, object Factory, lcs, lcsModify Request. The diagram shows 14 messages. The modification attempt (set()) fails, returning an error response. The customer then creates a modification request, which results in notifications. Finally, the customer cancels the request and explicitly deletes the lcs object. + +T0410210-98 + +**Figure III.15/M.3108.1 – Sequence diagram for unsuccessful LCS modification followed by LCS deletion** + + + +## ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression: definitions, symbols, classification +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Overall network operation, telephone service, service operation and human factors +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media, digital systems and networks +- Series H Audiovisual and multimedia systems +- Series I Integrated services digital network +- Series J Transmission of television, sound programme and other multimedia signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits** +- Series N Maintenance: international sound programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality, telephone installations, local line networks +- Series Q Switching and signalling +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminals for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communications +- Series Y Global information infrastructure and Internet protocol aspects +- Series Z Languages and general software aspects for telecommunication systems \ No newline at end of file diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a326625a941cf3a036d72948beb7cd51403c1001 --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d266933815a98f42e23eabda16e19bc77d87099be085f7de832227463e7d2854 +size 36601 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9652f7910b30c15c3b4fd1433cd478eb5ce0e82c --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19c2a6bdd92debd8cac66775ce47d3858a43d5ee8d5cb98778d3af441599bea1 +size 54887 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec81cfa3d93578d493ad714ad530ace3a4a440bb --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869d120e0e46e4e642a8fb21b99554d600df93b0b56b04aa52ded258c76cf9ee +size 33057 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6054e6cdf2e7e208966c5d6d271a9301a8bfe87 --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48bcee396c2c295727dee1752d3222ac47f5f8223f245ca704846ea1374567d9 +size 12438 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..049c43b73ac5f6e5649e4be5e6476e807e102be1 --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d3154bb6b3a15c5d7e776b4adbdc02fde5fd39384def7a08ce2a1552fa21a4 +size 44018 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9123bfc685c832a507fa99d3d65afac8abdcdaea --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f97a3359b9f0e0a90f441af53d6d1bd5a4749845a611f9ef036e48d2a3c045d7 +size 49858 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dffc744f5569f61dbb1ad4d1cee1ebcc3f979bcd --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15474232a616738c1fed769a7b20e89e716dd76ddec67381d000c3f9e01085cc +size 46616 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..060ca282e786a6ab22d478a434c9780b589fc262 --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec6f7f4d5a83e94cc843dc9c3fd8826a7df1e9dc161082ff77849b7d76de235c +size 44540 diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa252597bd53cd14ee87ad961428d438d20c7204 --- /dev/null +++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe9b4140bcbbba3480ae9618fcb2cf9fa7e8cc0336f885391557124b09344f81 +size 52477 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc35582281fc82f90ce4dba35cb8b9afd5594e4e --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44c78e9969761482c0a76a91ddb7629a8ac0b7fc559eac0693b1fa15d2dfe7c9 +size 42217 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae13d19a0c1fa5b2baf187d798eb1ab591c2fffc --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85dd23a875ddb80652f4d4e3020637fb3da41047f6399ac6707db540705a1ef0 +size 39365 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e79f451b79a2d2a77db7a08ec76901d472c3409b --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:070ad550fc0ca388dd40b622c21d6c67b492adaa6c8320107517c582f678006a +size 24362 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fcf69bb869388c8c887989ae7cc0db9ae66df22 --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd8b4c97eb9078df182a714da0bdbd6c0d690d71696eea386bb555b879a89652 +size 9742 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02e8b83783d5bdf2effe93fb869bb7dd688c8102 --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58ac276e50f5ef9bafb24890d7cbc88d2284fc8b3eb04bbde64276e0d90d7c33 +size 35729 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fd8ba6edd98fa5eb76828ecf32555f34a68878a --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db2927fc5aa26429fd6e2255601e33ee3094b35f77ee4d3829bc055b7eff6435 +size 48322 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbef8003ff5a11e2acd84ca290e2a55422608d64 --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7072718d1d89281029e8afda7a95614f954a19d124e43bea1187a8542babe14f +size 25293 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0adba9e482e187b2b720c5ff69dd9c80a4353baf --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6f900200b6051c08d3abc97280269f58851f18624f64d21cd89937c21436fa +size 47050 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b62bed9fce23c3e7173f8237f9ae15897c7bd651 --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41168dbf54b626044740ec7a5c5d03a0282abff135b8d5711a27843726d9c469 +size 34176 diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/raw.md b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..85e92775a747ff15d0d24aa3494fa78177028245 --- /dev/null +++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/raw.md @@ -0,0 +1,1015 @@ + + +# Recommendation**ITU-T M.3111.1 (03/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **X-interface between telecom operation system and Internet e-commerce platform – Protocol neutral requirements** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## Telecommunication management, including TMN and network maintenance + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T M.3111.1 + +## X-interface between telecom operation system and Internet e-commerce platform – Protocol neutral requirements + +## Summary + +With the current trend of digital transformation, information and communications service providers (ICSPs) need to expand their e-commerce ecology to improve customer experience and increase opportunities for ICSPs to provide services to customers. Recommendation ITU-T M.3111.1 provides the protocol neutral requirements for the X-interface between the telecom operation system (TOS) and the Internet e-commerce platform (IEP), following the interface specification methodology presented in Recommendation ITU-T M.3020. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3111.1 | 2025-03-29 | 2 | 11.1002/1000/16279 | + +## Keywords + +Internet e-commerce platform, management interface, protocol neutral, requirements, telecom operation system. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Concepts and background..... | 3 | +| 7 Requirements for the X-interface between the TOS and the IEP ..... | 4 | +| 7.1 Business level requirements ..... | 4 | +| 7.2 Specification level requirements ..... | 9 | +| Appendix I – Example of product classification catalogue ..... | 26 | +| Bibliography..... | 28 | + + + +# Recommendation ITU-T M.3111.1 + +## X-interface between telecom operation system and Internet e-commerce platform – Protocol neutral requirements + +# 1 Scope + +This Recommendation specifies the requirements for the X-interface between the telecom operation system (TOS) and the Internet e-commerce platform (IEP). In general, the interactions of the TOS and the IEP include product support and readiness, customer management, order handling, order bill invoice, product renewal and customer service. During these interactions, the exchange of information between the TOS and the IEP is required. This Recommendation focuses on the requirements of this interface which cover all of these interactions. The requirements are provided using the management interface specification methodology described in [ITU-T M.3020], in a protocol neutral manner. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. + +[ITU-T M.3020] Recommendation ITU-T M.3020 (2023), *Management interface specification methodology*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 customer** [b-ITU-T M.3050.1]: The customer buys products and services from the enterprise or receives free offers or services. A customer may be a person or a business. + +**3.1.2 e-commerce** [b-ITU-T M.3050.1]: e-commerce is Internet presence and business buying and selling transactions over digital media. + +**3.1.3 information and communications service provider (ICSP)** [b-ITU-T M.3050.1]: A service provider enterprise that sells information and/or communications services to other parties. + +**3.1.4 operation system** [ITU-T M.3010]: A physical block which performs operations systems functions (OSFs). + +**3.1.5 operation systems function (OSF)** [ITU-T M.3010]: A function block that processes information related to the telecommunications management for the purpose of monitoring/coordinating and/or controlling telecommunication functions including management functions (i.e., the TMN itself). + +**3.1.6 partner** [b-ITU-T M.3050.1]: A partner has a stronger profit and risk-sharing component in their business agreement with the enterprise than a supplier would have. A partner generally is more + +visible to the enterprise's customer than a supplier would be. A partner might be part of an alliance, a joint service offering, etc. + +**3.1.7 platform** [b-ITU-T X.1149]: A hardware or software system that serves as a foundation or base for realizing a certain functionality. + +**3.1.8 product** [b-ITU-T M.3050.1]: Product is what an entity (supplier) offers or provides to another entity (customer). Product may include service, processed material, software or hardware, or any combination thereof. A product may be tangible (e.g., goods) or intangible (e.g., concepts) or a combination thereof. However, a product ALWAYS includes a service component. + +**3.1.9 service provider** [b-ITU-T M.3050.1]: See under information and communications service provider (ICSP). Throughout this Recommendation, the terms "service provider" and "ICSP" are synonymous. + +**3.1.10 telecommunication service** [b-ITU-T M.60]: That which is offered by an Administration to its customers in order to satisfy a specific telecommunication requirement. + +**3.1.11 X interface** [ITU-T M.3010]: An interface applied at x reference points. + +**3.1.12 x reference points** [ITU-T M.3010]: A reference point located between OSF function blocks in different TMNs. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 stock keeping unit (SKU)**: The unit of measure in which the stocks of a material are managed, which is a distinct type of item for sale, purchase, or tracking in inventory (such as a product or service). + +NOTE – An example of SKU is an annual 300 Mbit/s home broadband package. + +**3.2.2 standard product unit (SPU)**: The unit of product aggregation, which is a set of reusable and easily retrievable standardized information that describes the characteristics of a class of products. + +NOTE 1 – An example of SPU is home broadband. The attribute of this SPU may include bandwidth: 300 Mbit/s / 1 000 Mbit/s, charging period: monthly / annual. + +NOTE 2 – One SPU may include multiple SKUs. In the above SPU example, there can be four SKUs. The first SKU is a 300 Mbit/s monthly home broadband package. The second SKU is a 300 Mbit/s annual home broadband package. The third SKU is a 1 000 Mbit/s monthly home broadband package. The fourth SKU is a 1 000 Mbit/s annual home broadband package. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-------------------------------------------------| +| CM | Customer Management | +| CS | Customer Service | +| FS | Function Set | +| ICSP | Information and Communications Service Provider | +| IEP | Internet e-commerce Platform | +| Mbit/s | Mega bits per second | +| OBI | Order Bill Invoice | +| OH | Order Handling | +| OS | Operations System | + +| | | +|-----|---------------------------------------| +| OSF | Operations Systems Function | +| PR | Product Renewal | +| PSR | Product Support and Readiness | +| SKU | Stock Keeping Unit | +| SPU | Standard Product Unit | +| TMN | Telecommunications Management Network | +| TOS | Telecom Operation System | +| URL | Uniform Resource Locator | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +For the qualifiers of a use case in the specification-level requirements, "M" standards for "Mandatory" and "O" stands for "Optional". + +# 6 Concepts and background + +With the current trend of digital transformation, information and communications service providers (ICSPs) need to respond to customers' increased demands for superior customer services. They have therefore been expanding their ecological cooperation, especially with Internet companies, to broaden their e-business. An ICSP needs to launch product onto external Internet companies for new customer development and for customers to order product more conveniently. + +According to the market sales demand, the ICSP decides what products need to be published to an Internet e-commerce platform (IEP) for sale and what product related information needs to be sent across the interface between the telecom operation system (TOS) and the IEP. When the products in the IEP are ready for sale, customers can browse the product information, order the product in the IEP, request for billing invoices from the IEP and submit complaint problems to the IEP. Related information needs to be exchanged across the interface between the TOS and the IEP. + +As described in [ITU-T M.3010], the X-interface is used to interconnect two telecommunications management networks (TMNs) or to interconnect a TMN with other systems which accommodate a TMN-like interface. The interface between the TOS and the IEP specified in this Recommendation is an X-interface, as shown in Figure 1. + +![Diagram showing the X-interface between the TOS and the IEP. Two circles labeled 'TOS' and 'IEP' are connected by a horizontal line. A small black dot on the line represents the interface, labeled 'X-interface' above it. Below the IEP circle is the text 'M.3111.1(25)'.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +``` + +graph LR + TOS((TOS)) --- X((X-interface)) --- IEP((IEP)) + M3111_1_25[M.3111.1(25)] --- IEP + +``` + +Diagram showing the X-interface between the TOS and the IEP. Two circles labeled 'TOS' and 'IEP' are connected by a horizontal line. A small black dot on the line represents the interface, labeled 'X-interface' above it. Below the IEP circle is the text 'M.3111.1(25)'. + +**Figure 1 – Position of the X-interface between the TOS and the IEP** + +This Recommendation contains requirements for the X-interface between the TOS and the IEP. In general, the information that needs to be exchanged across this interface between the TOS and the IEP includes the following function set (FS): product support and readiness, customer management, order handling, order bill invoice (OBI), product renewal and customer service: + +- Product support and readiness FS ensures that the product from the ICSP is available and ready to support Internet presence and business for buying and selling transactions over the IEP. +- Customer management FS ensures that customers from the IEP can complete the authentication and credit worthiness in the TOS. +- Order handling FS ensures that order actions initiated by customers in the IEP, such as order submission, order status inquiry and order cancellation, can be issued to the TOS for handling, and that the TOS can respond to the order handling result. +- Order bill invoice FS ensures that customers in the IEP can inquire and obtain bill invoices from the TOS. +- Product renewal FS ensures that customers in the IEP can continue to order the product which is used previously by the customers. +- Customer service FS ensures that customers in the IEP can initiate product consultation or complaints to the TOS. + +This interface can provide the means for creating common practices for ICSPs to launch products onto external e-commerce platforms and for customers to be able to order product of ICSPs from the IEP. + +# 7 Requirements for the X-interface between the TOS and the IEP + +## 7.1 Business level requirements + +### 7.1.1 Requirements + +The general requirements include: + +- product support and readiness (clause 7.1.1.1) +- customer management (clause 7.1.1.2) +- order handling (clause 7.1.1.3) +- order bill invoice (clause 7.1.1.4) +- product renewal (clause 7.1.1.5) +- customer service (clause 7.1.1.6) + +#### 7.1.1.1 Product support and readiness FS + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-PSR-FUN-101 | The TOS is required to send the product classification catalogue to the IEP, so that the customer-oriented product catalogue in the IEP can be established more easily according to this product classification catalogue. An example of the catalogue is shown in Appendix I. | +| REQ-PSR-FUN-102 | The TOS is required to send the product standard product unit (SPU) information to the IEP, so that the product SPU can be correlated to the appropriate catalogue item and then the product SKU can be correlated to the specific SPU in the IEP. | +| REQ-PSR-FUN-103 | The TOS is required to send the product SKU information to the IEP, so that the SKU can be correlated to a specific SPU in the IEP. | + +#### 7.1.1.2 Customer management FS + +| | | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-CM-FUN-201 | The IEP is required to send the information of the newly created customer, who has ordered product in the IEP, to the TOS, so that the TOS can determine if this customer is new in its own system and needs to initiate real name authentication according to this information. | +| REQ-CM-FUN-202 | The TOS is required to provide a real name authentication failure result back to the IEP, so that the IEP can require the customer to modify the customer newly created information. | +| REQ-CM-FUN-203 | The TOS is required to provide the customer newly created success response to the IEP.
See Notes 1 and 2 for more details. | +| REQ-CM-FUN-204 | The IEP is required to send the credit worthiness verification request of the customer, who has ordered product in the IEP, to the TOS, so that the TOS can verify the customer's credit worthiness. | + +NOTE 1 – a) Authentication should be performed. If the real name authentication succeeds, the new customer ID of the TOS will be created and sent back to the IEP for recording through this interface. + +b) The customer already existed in the TOS. In such cases, the customer may have already ordered some products in the telecommunication service hall offline. Then the TOS sends the existing customer ID of the TOS back to the IEP for recording through this interface. When this customer wants to order the TOS products in the future, he/she does not need to provide newly created information again. + +NOTE 2 – The IEP and the TOS have two different sets of customer IDs, which need to establish a mapping relationship of the two sets of customer IDs in both the IEP and the TOS, because the TOS does not use the IEP customer ID set for its own order process and other operation and management activities. When a customer orders a product in the IEP, the IEP will first decide whether the customer needs to provide newly created information to the TOS based on the customer ID of the TOS. If the customer ID of the TOS already existed in the IEP, the IEP will associate this customer's order to his/her customer ID of the TOS, and will send this customer's order information along with his/her customer ID of the TOS. + +##### 7.1.1.3 Order handling FS + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-OH-FUN-301 | The IEP is required to send the order information to the TOS, which has been submitted by the customer in the IEP. | +| REQ-OH-FUN-302 | The TOS is required to send the order fulfilment result to the IEP, so that the customer will be informed whether the order fulfilment is successful or has failed. | +| REQ-OH-FUN-303 | The IEP is required to send the order status inquiry to the TOS, so that the customer can track the process of the order handling. | +| REQ-OH-FUN-304 | The IEP is required to send the cancel products in the order request to the TOS, so that the customer can cancel all the products in the order or part of the products in order before the order fulfilment is completed. | + +##### 7.1.1.4 Order bill invoice FS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| REQ-OBI-FUN-401 | The IEP is recommended to send a bill invoice request to the TOS, so that the customer can inquire after the bill invoice in the IEP. | +| REQ-OBI-FUN-402 | The TOS is recommended to provide a bill invoice response to the IEP. | + +##### 7.1.1.5 Product renewal FS + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------------------| +| REQ-PR-FUN-501 | The IEP is required to send the product renewal order to the TOS, so that the customer can renew the product in the IEP. | +| REQ-PR-FUN-502 | The TOS is required to provide the product renewal result to the IEP. | + +##### 7.1.1.6 Customer service FS + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-CS-FUN-601 | The IEP is required to send service consulting initiated by the customer to the TOS, so that the customer's service consulting, which cannot be processed in the IEP, can be resolved in the TOS. | +| REQ-CS-FUN-602 | The TOS is required to provide the response of the customer's service consulting to the IEP, so that the customer's service consulting can be resolved. | +| REQ-CS-FUN-603 | The IEP is required to send the customer's problems and complaints to the TOS, which are categorized for the TOS to resolve, so that the TOS can perform root cause analysis and recover the problem. | +| REQ-CS-FUN-604 | The TOS is required to provide the response of the customer's problems and complaints to the IEP, so that the resolution result of the problems and complaints can be conveyed to the customer. | + +#### 7.1.2 Actor roles + +Telecom operation system (TOS): The entity performing the service provider role. + +Internet e-commerce platform (IEP): The entity performing the partner role. + +#### 7.1.3 Telecommunication resources + +The managed network resources are viewed as relevant telecommunication resources in this Recommendation. + +### 7.1.4 High level use case diagrams + +The function sets of the X-interface between the TOS and the IEP contain: product support and readiness function set, customer management function set, order handling function set, order bill invoice function set, product renewal function set and customer service function set. + +Figure 2 shows the top-level use case. + +Figure 3 shows the high-level use cases for the product support and readiness function set. + +Figure 4 shows the high-level use cases for the customer management function set. + +Figure 5 shows the high-level use cases for the order handling function set. + +Figure 6 shows the high-level use cases for the order bill invoice function set. + +Figure 7 shows the high-level use cases for the product renewal function set. + +Figure 8 shows the high-level use cases for the customer service function set. + +![Diagram of Interface function sets for the TOS and the IEP overview. It shows a central interface node connected to TOS and IEP actors, with six included function sets: Product Support and Readiness_FS, Customer_Management_FS, Order_Handling_FS, Order_Bill_Invoice_FS, Product_Renewal_FS, and Customer_Service_FS.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Interfaces for TOS and IEP + +TOS + +IEP + +<> + +Product Support and Readiness\_FS + +<> + +Customer\_Management\_FS + +<> + +Order\_Handling\_FS + +<> + +Order\_Bill\_Invoice\_FS + +<> + +Product\_Renewal\_FS + +<> + +Customer\_Service\_FS + +M.3111.1(25) + +Diagram of Interface function sets for the TOS and the IEP overview. It shows a central interface node connected to TOS and IEP actors, with six included function sets: Product Support and Readiness\_FS, Customer\_Management\_FS, Order\_Handling\_FS, Order\_Bill\_Invoice\_FS, Product\_Renewal\_FS, and Customer\_Service\_FS. + +**Figure 2 – Interface function sets for the TOS and the IEP overview** + +![Diagram of Product support and readiness FS. It shows a central interface node connected to TOS and IEP actors, with three included function sets: TOS sends product classification catalogue to IEP, TOS sends product SPU information to IEP, and TOS sends product SKU information to IEP.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) + +Product Support and Readiness\_FS + +TOS + +IEP + +<> + +TOS sends product classification catalogue to IEP + +<> + +TOS sends product SPU information to IEP + +<> + +TOS sends product SKU information to IEP + +M.3111.1(25) + +Diagram of Product support and readiness FS. It shows a central interface node connected to TOS and IEP actors, with three included function sets: TOS sends product classification catalogue to IEP, TOS sends product SPU information to IEP, and TOS sends product SKU information to IEP. + +**Figure 3 – Product support and readiness FS** + +![Diagram of Customer management FS. It shows a central interface node connected to TOS and IEP actors, with four included function sets: IEP sends information of newly created customer to TOS, TOS provides real name authentication failure result to IEP, TOS provides customer newly created success response to IEP, and IEP sends customer's credit worthiness verification request to TOS.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Customer\_Management\_FS + +TOS + +IEP + +<> + +IEP sends information of newly created customer to TOS + +<> + +TOS provides real name authentication failure result to IEP + +<> + +TOS provides customer newly created success response to IEP + +<> + +IEP sends customer's credit worthiness verification request to TOS + +M.3111.1(25) + +Diagram of Customer management FS. It shows a central interface node connected to TOS and IEP actors, with four included function sets: IEP sends information of newly created customer to TOS, TOS provides real name authentication failure result to IEP, TOS provides customer newly created success response to IEP, and IEP sends customer's credit worthiness verification request to TOS. + +**Figure 4 – Customer management FS** + +![UML Use Case Diagram for Order Handling FS. Actors: TOS, IEP. Use Case: Order_Handling_FS. Includes: IEP sends the information_of order_to_TOS, TOS sends order_fulfilment_result_to_IEP, IEP requests the_order_status_from_TOS, IEP cancels products in the_order_from_TOS. Reference: M.3111.1(25)](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +usecaseDiagram + actor TOS + actor IEP + usecase Order_Handling_FS + TOS --> Order_Handling_FS + IEP --> Order_Handling_FS + Order_Handling_FS -.-> IEP_sends_the_information_of_order_to_TOS : <> + Order_Handling_FS -.-> TOS_sends_order_fulfilment_result_to_IEP : <> + Order_Handling_FS -.-> IEP_requests_the_order_status_from_TOS : <> + Order_Handling_FS -.-> IEP_cancelled_products_in_the_order_from_TOS : <> + +``` + +M.3111.1(25) + +UML Use Case Diagram for Order Handling FS. Actors: TOS, IEP. Use Case: Order\_Handling\_FS. Includes: IEP sends the information\_of order\_to\_TOS, TOS sends order\_fulfilment\_result\_to\_IEP, IEP requests the\_order\_status\_from\_TOS, IEP cancels products in the\_order\_from\_TOS. Reference: M.3111.1(25) + +**Figure 5 – Order handling FS** + +![UML Use Case Diagram for Order Bill Invoice FS. Actors: TOS, IEP. Use Case: Order_Bill_Invoice_FS. Includes: IEP requests bill_invoice_from_TOS, TOS provides bill_invoice_response_to_IEP. Reference: M.3111.1(25)](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +``` + +usecaseDiagram + actor TOS + actor IEP + usecase Order_Bill_Invoice_FS + TOS --> Order_Bill_Invoice_FS + IEP --> Order_Bill_Invoice_FS + Order_Bill_Invoice_FS -.-> IEP_requests_bill_invoice_from_TOS : <> + Order_Bill_Invoice_FS -.-> TOS_provides_bill_invoice_response_to_IEP : <> + +``` + +M.3111.1(25) + +UML Use Case Diagram for Order Bill Invoice FS. Actors: TOS, IEP. Use Case: Order\_Bill\_Invoice\_FS. Includes: IEP requests bill\_invoice\_from\_TOS, TOS provides bill\_invoice\_response\_to\_IEP. Reference: M.3111.1(25) + +**Figure 6 – Order bill invoice FS** + +![UML Use Case Diagram for Product Renewal FS. Actors: TOS, IEP. Use Case: Product_Renewal_FS. Includes: IEP sends product_renewal_order_to_TOS, TOS sends renewal_order_fulfilment_result_to_IEP. Reference: M.3111.1(25)](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +usecaseDiagram + actor TOS + actor IEP + usecase Product_Renewal_FS + TOS --> Product_Renewal_FS + IEP --> Product_Renewal_FS + Product_Renewal_FS -.-> IEP_sends_product_renewal_order_to_TOS : <> + Product_Renewal_FS -.-> TOS_sends_renewal_order_fulfilment_result_to_IEP : <> + +``` + +M.3111.1(25) + +UML Use Case Diagram for Product Renewal FS. Actors: TOS, IEP. Use Case: Product\_Renewal\_FS. Includes: IEP sends product\_renewal\_order\_to\_TOS, TOS sends renewal\_order\_fulfilment\_result\_to\_IEP. Reference: M.3111.1(25) + +**Figure 7 – Product renewal FS** + +![Figure 8 – Customer service FS. A functional specification diagram showing interactions between TOS and IEP actors through a central 'Customer_Service_FS' function. The diagram includes five use cases connected via '<>' relationships: 'IEP sends service consulting to TOS', 'TOS sends response of customer's problems and complaints to IEP', 'TOS sends service consulting response to IEP', and 'IEP sends customer's problems and complaints to TOS'. A reference code 'M.3111.1(25)' is present at the bottom right.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Figure 8 – Customer service FS. A functional specification diagram showing interactions between TOS and IEP actors through a central 'Customer\_Service\_FS' function. The diagram includes five use cases connected via '<>' relationships: 'IEP sends service consulting to TOS', 'TOS sends response of customer's problems and complaints to IEP', 'TOS sends service consulting response to IEP', and 'IEP sends customer's problems and complaints to TOS'. A reference code 'M.3111.1(25)' is present at the bottom right. + +**Figure 8 – Customer service FS** + +## **7.2 Specification level requirements** + +The general exceptions (e.g., communication error, processing error) related to all functions are not described in clause 7 and will only be handled in the design phase. + +The exception "Invalid input parameter" in the following clauses indicates that there is some syntactic error(s) in the input parameters, which does not involve semantic issues. + +The exception "Specified catalogue ID does not exist" (for example) indicates that the ID of the catalogue in the input parameter is syntactically correct, but it cannot be found in the IEP, which is considered as a semantic error. + +### **7.2.1 Requirements** + +There are no specification level requirements. + +### **7.2.2 Actor roles** + +See clause 7.1.2. + +### **7.2.3 Telecommunication resources** + +See clause 7.1.3. + +### **7.2.4 Use cases** + +##### **7.2.4.1 Product support and readiness use cases** + +Figure 3 shows the high-level use cases for the product support and readiness function set and these use cases are presented in clauses 7.2.4.1.1 to 7.2.4.1.3. + +###### **7.2.4.1.1 The TOS sends a product classification catalogue to the IEP (M)** + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends the product classification catalogue to the IEP, so that the customer-oriented product catalogue in the IEP can be established more easily according to this product classification catalogue. | | +| Actors and roles | The IEP is the consumer of the product classification catalogue information sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The product classification catalogue information has existed in the TOS. | | +| Begins when | The TOS sends the product classification catalogue to the IEP. | | +| Step 1 | The TOS sends the product classification catalogue information to the IEP, which includes a list of items, and each item includes the following:
  • – item ID,
  • – item name,
  • – action type,
  • – item number,
  • – parent ID.
(An example of product classification catalogue is shown in Appendix I, with action types also illustrated.) | | +| Step 2.1 | If the product classification catalogue is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | | +| Step 2.2 | If the product classification catalogue cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | | +| Ends when | The IEP has received the product classification catalogue information. | | +| Exceptions |
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The IEP receives the product classification catalogue information. | | +| Traceability | REQ-PSR-FUN-101 | | + +###### 7.2.4.1.2 The TOS sends product SPU information to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends the product SPU information to the IEP, so that the product SPU can be correlated to the appropriate catalogue item and then the product SKU can be correlated to the specific SPU in the IEP. | | +| Actors and roles | The IEP is the consumer of the product SPU information sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The related product classification catalogue has already been sent from the TOS to the IEP. | Use case 7.2.4.1.1 | +| Begins when | The TOS sends the product SPU information to the IEP. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 1 | The TOS sends the product SPU information to the IEP, which includes:
  • – SPU ID,
  • – SPU name,
  • – catalogue ID it belongs to,
  • – action type,
  • – List of product SPU attributes, and each attribute may include:
    • SPU attribute ID,
    • SPU attribute name (optional, when action type is DEL),
    • SPU attribute value (optional, when action type is DEL).
| | +| Step 2.1 | If the product SPU information is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | | +| Step 2.2 | If the product SPU information cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | | +| Ends when | The IEP has received the product SPU information. | | +| Exceptions | 1) General exceptions:
  • – Specified catalogue ID does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
2) If the action type is ADD, exceptions may include:
  • – SPU ID has already existed,
  • – SPU name has already existed.
3) If the action type is MOD, exceptions may include:
  • – Specified SPU ID does not exist,
  • – SPU attribute ID does not exist.
4) If the action type is DEL, exceptions may include:
  • – Specified SPU ID does not exist.
| | +| Post-conditions | The IEP receives the product SPU information. | | +| Traceability | REQ-PSR-FUN-102 | | + +###### 7.2.4.1.3 The TOS sends product SKU information to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends the product SKU information to the IEP, so that the SKU can be correlated to a specific SPU in the IEP, and the products displayed for customers can be created. | | +| Actors and roles | The IEP is the consumer of the product SKU information sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Pre-conditions | The related product SPU information has already been sent from the TOS to the IEP. | Use case 7.2.4.1.2 | +| Begins when | The TOS sends the product SKU information to the IEP. | | +| Step 1 | The TOS sends the product SKU information to the IEP, which includes:
  • – SKU ID,
  • – SKU name,
  • – SPU ID it belongs to,
  • – SKU availability time,
  • – SKU expiration time,
  • – action type,
  • – list of product SKU attributes, and each attribute may include:
    • SKU attribute ID,
    • SKU attribute name (optional, when action type is DEL),
    • SKU attribute value (optional, when action type is DEL),
  • – product description detail.
| | +| Step 2.1 | If the product SKU information is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | | +| Step 2.2 | If the product SKU information cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | | +| Ends when | The IEP has received the product SKU information. | | +| Exceptions | 1) General exceptions:
  • – Specified SPU ID does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
2) If the action type is ADD, exceptions may include:
  • – SKU ID has already existed,
  • – SKU name has already existed,
  • – SKU expiration time is earlier that the current time,
  • – SKU expiration time is earlier that SKU availability time.
3) If the action type is MOD, exceptions may include:
  • – Specified SKU ID does not exist,
  • – Specified SKU attribute ID does not exist,
  • – SKU expiration time is earlier that the current time,
  • – SKU expiration time is earlier that SKU availability time.
4) If the action type is DEL, exceptions may include:
  • – Specified SKU ID does not exist.
| | +| Post-conditions | The IEP receives the product SKU information. | | +| Traceability | REQ-PSR-FUN-103 | | + +##### 7.2.4.2 Customer management use cases + +Figure 4 shows the high-level use cases for the customer management function set and these use cases are presented in clauses 7.2.4.2.1 to 7.2.4.2.4. + +###### 7.2.4.2.1 The IEP sends information of newly created customer to the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends the information of a newly created customer to the TOS. So that the TOS can determine whether this customer is new in its own system and initiate real name authentication according to this information. | | +| Actors and roles | The TOS is the consumer of the newly created customer information sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer submitting an order in the IEP is new for the IEP.
The customer creation information has been completed in the IEP. | | +| Begins when | The IEP sends the information of the newly created customer to the TOS. | | +| Step 1 | The IEP sends the information of the newly created customer to the TOS, which includes:
  • – customer ID of the IEP (Note),
  • – customer name,
  • – customer ID card number,
  • – front and back photos of the ID card,
  • – contact phone number,
  • – contact address,
  • – payment account.
NOTE – When a customer is newly created in the IEP, a customer ID of the IEP will be created. The customer ID of the IEP is different from the customer ID of the TOS. The mapping relationship of these two customer IDs will be stored in both the IEP and the TOS. | | +| Step 2.1 | If the information of the newly created customer is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the information of newly created customer cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | +| Ends when | The TOS has received the newly created customer information. | | +| Exceptions |
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The TOS receives the newly created customer information.
If this customer does not exist in the TOS, the TOS will start the real name authentication. | Use case 7.2.4.2.2 | +| Traceability | REQ-CM-FUN-201 | | + +###### 7.2.4.2.2 The TOS provides real name authentication failure result to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | If the real name authentication fails in the TOS, the TOS provides the real name authentication failure result back to the IEP. So that the IEP can ask the customer to modify the newly created customer information. | | +| Actors and roles | The IEP is the consumer of the real name authentication failure result sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The IEP has sent the information of the newly created customer to the TOS.
This customer does not exist in the TOS.
The customer real name authentication fails in the TOS. | Use case 7.2.4.2.1 | +| Begins when | The TOS sends the real name authentication failure result to the IEP. | | +| Step 1 | The TOS provides the real name authentication failure result back to the IEP, which includes:
  • – customer ID of the IEP,
  • – the reason of the authentication failure (such as the information missing, or the information does not meet the authentication requirement).
| | +| Step 2.1 | If the real name authentication failure result is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | | +| Step 2.2 | If the real name authentication failure result cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | | +| Ends when | The IEP has received the real name authentication failure result. | | +| Exceptions |
  • – Specified customer ID of the IEP does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The IEP receives the real name authentication failure result. | | +| Traceability | REQ-CM-FUN-202 | | + +###### 7.2.4.2.3 The TOS provides customer newly created success response to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | If the real name authentication is successful in the TOS, the TOS provides customer newly created success response to the IEP. | | +| Actors and roles | The IEP is the consumer of the customer newly created success response sent from the TOS. The TOS is the supplier. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| | The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The IEP has sent the information of the newly created customer to the TOS.
This customer's name and ID number have already existed in the TOS, or the real name authentication is successful in the TOS. | Use case 7.2.4.2.1 | +| Begins when | The TOS sends a customer newly created success response to the IEP. | | +| Step 1 | The TOS provides customer newly created success response to the IEP, which includes:
– customer ID of the IEP,
– customer ID of the TOS. | | +| Step 2.1 | If the customer newly created success response is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | | +| Step 2.2 | If the customer newly created success response cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | | +| Ends when | The IEP has received the customer newly created success response. | | +| Exceptions | – Specified customer ID of the IEP does not exist,
– Invalid parameter,
– Operation failed due to internal problem. | | +| Post-conditions | The IEP receives the customer newly created success response. | | +| Traceability | REQ-CM-FUN-203 | | + +###### 7.2.4.2.4 The IEP sends customer's credit worthiness verification request to the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends a customer's credit worthiness verification request to the TOS, who has ordered product in the IEP, so that the TOS can verify this customer's credit worthiness. | | +| Actors and roles | The TOS is the consumer of the customer verification request sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has submitted an order in the IEP.
The real name authentication for the customer is successful in the TOS. | Use case 7.2.4.2.3 | +| Begins when | The IEP sends the customer's credit worthiness verification request to the TOS. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 1 | The IEP sends a customer's credit worthiness verification request to the TOS, which includes:
– customer ID of the TOS. | | +| Step 2.1 | If the customer's credit worthiness verification request is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the customer's credit worthiness verification request cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | +| Ends when | The TOS has received the customer's credit worthiness verification request. | | +| Exceptions | – Specified customer ID of the TOS does not exist,
– Invalid parameter,
– Operation failed due to internal problem. | | +| Post-conditions | The TOS receives the customer's credit worthiness verification request. | | +| Traceability | REQ-CM-FUN-204 | | + +##### 7.2.4.3 Order handling use cases + +Figure 5 shows the high-level use cases for the order handling function set and these use cases are presented in clauses 7.2.4.3.1 to 7.2.4.3.4. + +###### 7.2.4.3.1 The IEP sends the order information to the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends the order information to the TOS, which has been submitted by the customer in the IEP. | | +| Actors and roles | The TOS is the consumer of the order information sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation on the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has submitted an order in the IEP. | | +| Begins when | The IEP sends the order information to the TOS. | | +| Step 1 | The IEP sends the order information to the TOS, which includes:
– customer ID of the TOS,
– order IDNOTE,
– SKU ID in the order,
– order payment status.

NOTE – Order ID in this Recommendation refers to the order ID of the IEP. The TOS has its own order ID set which is different from the order ID set of the IEP. Their mapping relationship is stored in the TOS, which the IEP does not need to know. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 2.1 | If the order information is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the order information cannot be successfully processed by the TOS, including order feasibility verification failure, the TOS will inform the IEP with a failure response. | | +| Ends when | The TOS has received the order information. | | +| Exceptions |
  • – Order ID has already existed,
  • – Specified customer ID of the TOS does not exist,
  • – Specified SKU ID does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The TOS receives the order information. | | +| Traceability | REQ-PSR-FUN-301 | | + +###### 7.2.4.3.2 The TOS sends order fulfilment result to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends the order fulfilment result to the IEP after the TOS has completed the implementation of the order. | | +| Actors and roles | The IEP is the consumer of the order fulfilment result sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The TOS has completed the implementation of the order. | Use case 7.2.4.3.1 | +| Begins when | The TOS sends the order fulfilment result to the IEP. | | +| Step 1 | The TOS sends the order fulfilment result to the IEP, which includes:
  • – order ID,
  • – order fulfilment result (successful or failed),
  • – fail reason (optional, only when the result is failed).
| | +| Step 2.1 | If the order fulfilment result is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | | +| Step 2.2 | If the order fulfilment result cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | | +| Ends when | The IEP has received the order fulfilment result. | | +| Exceptions |
  • – Specified order ID does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The IEP receives the order fulfilment result. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|----------------|-------------------------|---------------------------------| +| Traceability | REQ-PSR-FUN-302 | | + +###### 7.2.4.3.3 The IEP requests the order status from the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends the order status inquiry to the TOS. So that the customer can track the process of the order handling. | | +| Actors and roles | The TOS is the consumer of the order status inquiry sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation on the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has submitted an order status inquiry in the IEP. | Use case 7.2.4.3.2 | +| Begins when | The IEP sends the order status inquiry to the TOS. | | +| Step 1 | The IEP sends the order status inquiry to the TOS, which includes:
– order ID. | | +| Step 2.1 | If the order status inquiry is successfully received by the TOS without any problems, the TOS will inform the IEP with the order status inquiry result response, which includes:
– order ID,
– list of order SKU status, and each order SKU status includes:
SKU ID,
the SKU fulfilment status of the SKU ID in this order. | | +| Step 2.2 | If the order status inquiry cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | +| Ends when | The IEP has received the order status result or an exception. | | +| Exceptions | – Specified order ID does not exist,
– Specified SKU IDs do not exist,
– Invalid parameter,
– Operation failed due to internal problem. | | +| Post-conditions | The IEP receives the order status result or an exception. | | +| Traceability | REQ-PSR-FUN-303 | | + +###### 7.2.4.3.4 The IEP cancels products in the order from the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends the cancel products in the order request to the TOS, to cancel all the products in the order or part of products in the order. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Actors and roles | The TOS is the consumer of the cancel products in the order request sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has submitted an order cancellation in the IEP. | Use case 7.2.4.3.2 | +| Begins when | The IEP sends the cancel products in the order request to the TOS. | | +| Step 1 | The IEP sends the cancel products in the order request to the TOS, which includes:
– order ID,
– list of SKU IDs of products to be cancelled. | | +| Step 2.1 | If the order cancellation is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response including:
– refund amount. | | +| Step 2.2 | If the order cancellation cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response including:
– failure reason. | | +| Ends when | The IEP receives the cancellation response from the TOS. | | +| Exceptions | – Specified order ID does not exist,
– Specified SKU IDs do not exist,
– Invalid parameter,
– Operation failed due to internal problem. | | +| Post-conditions | The IEP receives the product cancellation response.
The specified products of the SKU IDs are cancelled, if the operation is successful. | | +| Traceability | REQ-PSR-FUN-304 | | + +##### 7.2.4.4 Order bill invoice use cases + +Figure 6 shows the high-level use cases for the order bill invoice function set and these use cases are presented in clauses 7.2.4.4.1 and 7.2.4.4.2. + +###### 7.2.4.4.1 The IEP requests bill invoice from the TOS (O) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP requests bill invoice from the TOS. So that the customer can inquire bill invoice in the IEP. | | +| Actors and roles | The TOS is the consumer of the bill invoice inquiry sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has submitted a bill invoice inquiry in the IEP. | | +| Begins when | The IEP sends the bill invoice request to the TOS. | | +| Step 1 | The IEP sends the bill invoice inquiry request to the TOS, which includes:
  • – order ID,
  • – list of SKU IDs,
  • – invoice header type (individual or enterprise),
  • – invoice header,
  • – tax identification number (optional, if the invoice header type is enterprise).
| | +| Step 2.1 | If the bill invoice inquiry is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the bill invoice inquiry cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | +| Ends when | The TOS has received the bill invoice inquiry. | | +| Exceptions |
  • – Specified order ID does not exist,
  • – Specified SKU IDs do not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The TOS receives the bill invoice inquiry. | | +| Traceability | REQ-PSR-FUN-401 | | + +###### 7.2.4.4.2 The TOS provides bill invoice response to the IEP (O) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS provides bill invoice response to the IEP. | | +| Actors and roles | The IEP is the consumer of the bill invoice response sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The TOS has already issued the invoice that is inquired by the customer in the IEP. | Use case 7.2.4.4.1 | +| Begins when | The TOS provides the bill invoice response to the IEP. | | +| Step 1 | The TOS provides the bill invoice response to the IEP, which includes:
  • – order ID,
  • – list of SKU IDs,
  • – URL for the bill invoice.
| | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 2.1 | If the bill invoice response is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | | +| Step 2.2 | If the bill invoice response cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | | +| Ends when | The IEP has received the bill invoice response. | | +| Exceptions |
  • – Specified order ID does not exist,
  • – Specified SKU IDs do not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The IEP receives the bill invoice response. | | +| Traceability | REQ-PSR-FUN-402 | | + +##### 7.2.4.5 Product renewal use cases + +Figure 7 shows the high-level use cases for the product renewal function set and these use cases are presented in clauses 7.2.4.5.1 and 7.2.4.5.2. + +###### 7.2.4.5.1 The IEP sends product renewal order to the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends the product renewal order to the TOS, which has been submitted by the customer in the IEP. So that the customer can renew the product in the IEP. | | +| Actors and roles |

The TOS is the consumer of the order information sent from the IEP.

The IEP is the supplier.

The IEP invokes the operation on the TOS.

| | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions |

The original order has been successfully fulfilled in the TOS.

The customer has submitted the product renewal order in the IEP.

| Use case 7.2.4.3.2 | +| Begins when | The IEP sends the product renewal order to the TOS. | | +| Step 1 |

The IEP sends the information of the product renewal order to the TOS, which includes:

  • – renewal order ID,
  • – original order ID,
  • – list of SKU IDs to be renewed,
  • – renewal order payment status.
| | +| Step 2.1 | If the renewal order information is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the renewal order information cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | +| Ends when | The TOS has received the renewal order information. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Exceptions |
  • – Renewal order ID has already existed,
  • – Specified original order ID does not exist,
  • – Specified SKU ID(s) do not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The TOS receives the information of the product renewal order. | | +| Traceability | REQ-PSR-FUN-501 | | + +###### 7.2.4.5.2 The TOS sends renewal order fulfilment result to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends the renewal order fulfilment result to the IEP. | | +| Actors and roles | The IEP is the consumer of the renewal order fulfilment result sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has submitted a product renewal order in the IEP. | Use case 7.2.4.5.1 | +| Begins when | The TOS sends the renewal order fulfilment result to the IEP. | | +| Step 1 | The TOS sends the renewal order fulfilment result to the IEP, which includes:
  • – renewal order ID,
  • – order fulfilment result (successful or failed),
  • – fail reason (optional, only when the result is failed, such as customer in arrears).
| | +| Step 2.1 | If the renewal order fulfilment result is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | | +| Step 2.2 | If the renewal order fulfilment result cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | | +| Ends when | The IEP has received the renewal order fulfilment result. | | +| Exceptions |
  • – Specified renewal order ID does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The IEP receives the order fulfilment result. | | +| Traceability | REQ-PSR-FUN-502 | | + +##### 7.2.4.6 Customer service use cases + +Figure 8 shows the high-level use cases for the customer service function set and these use cases are presented in clauses 7.2.4.6.1 to 7.2.4.6.4. + +###### 7.2.4.6.1 The IEP sends service consulting request to the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends a service consulting request to the TOS, which has been initiated by the customer in the IEP and cannot be processed in the IEP. | | +| Actors and roles | The TOS is the consumer of the service consulting sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation in the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has initiated service consulting in the IEP. The IEP cannot resolve it and needs to send this service consulting to the TOS for further processing. | | +| Begins when | The IEP sends a service consulting request to the TOS. | | +| Step 1 | The IEP sends a service consulting request to the TOS, which includes:
– work order ID,
– service consulting description. | | +| Step 2.1 | If the service consulting is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the service consulting cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | +| Ends when | The TOS has received the service consulting request. | | +| Exceptions | – Invalid parameter,
– Operation failed due to internal problem. | | +| Post-conditions | The TOS receives the service consulting. | | +| Traceability | REQ-PSR-FUN-601 | | + +###### 7.2.4.6.2 The TOS sends service consulting response to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends service consulting response to the IEP. | | +| Actors and roles | The IEP is the consumer of the service consulting response sent from the TOS. The TOS is the supplier.
The TOS invokes the operation in the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The IEP has sent service consulting to the TOS. The TOS has prepared the response to the service consulting. | Use case 7.2.4.6.1 | +| Begins when | The TOS sends the service consulting response to the IEP. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 1 | The TOS sends the service consulting response to the IEP, which includes:
– work order ID,
– service consulting reply. | | +| Step 2.1 | If the service consulting response is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | | +| Step 2.2 | If the service consulting response cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | | +| Ends when | The IEP has received the service consulting response. | | +| Exceptions | – Specified work order ID does not exist,
– Invalid parameter,
– Operation failed due to internal problem. | | +| Post-conditions | The IEP receives the service consulting response. | | +| Traceability | REQ-PSR-FUN-602 | | + +###### 7.2.4.6.3 The IEP sends customer's problems and complaints to the TOS (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IEP sends a customer's problems and complaints to the TOS are categorized for the TOS to resolve, so that the TOS can perform root cause analysis and recover the problem. | | +| Actors and roles | The TOS is the consumer of the customer's problems and complaints sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The customer has problems and complaints in the IEP, and these problems and complaints are categorized for the TOS to resolve. | | +| Begins when | The IEP sends customer's problems and complaints to the TOS. | | +| Step 1 | The IEP sends customer's problems and complaints to the TOS, which includes:
– work order ID,
– order ID,
– list of SKU IDs,
– problems and complaints description. | | +| Step 2.1 | If the customer's problems and complaints is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | | +| Step 2.2 | If the customer's problems and complaints cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Ends when | The TOS has received the customer's problems and complaints. | | +| Exceptions |
  • – Specified order ID does not exist,
  • – Specified SKU ID(s) do not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The TOS receives the customer's problems and complaints. | | +| Traceability | REQ-PSR-FUN-603 | | + +###### 7.2.4.6.4 The TOS sends response of customer's problems and complaints to the IEP (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TOS sends the response of the customer's problems and complaints to the IEP. So that the resolution result of the problems and complaints can be informed to the customer. | | +| Actors and roles | The IEP is the consumer of the service consulting response sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | | +| Telecom resources | See clause 7.2.3. | | +| Assumptions | The communication between the TOS and the IEP is available. | | +| Pre-conditions | The IEP has sent the customer's problems and complaints to the TOS.
The TOS has prepared the response to the problems and complaints. | Use case 7.2.4.6.3 | +| Begins when | The TOS sends the response of customer's problems and complaints to the IEP. | | +| Step 1 | The TOS sends the response of customer's problems and complaints to the IEP, which includes:
  • – work order ID,
  • – description of the resolution to the problems and complaints.
| | +| Step 2.1 | If the response of customer's problems and complaints is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | | +| Step 2.2 | If the response of customer's problems and complaints cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | | +| Ends when | The IEP has received the response of customer's problems and complaints. | | +| Exceptions |
  • – Specified work order ID does not exist,
  • – Invalid parameter,
  • – Operation failed due to internal problem.
| | +| Post-conditions | The IEP receives the response of customer's problems and complaints. | | +| Traceability | REQ-PSR-FUN-604 | | + +# Appendix I + +## Example of product classification catalogue + +(This appendix does not form an integral part of this Recommendation.) + +There is one basic product classification catalogue in one TOS. The basic catalogue can be sent to different IEPs to help them build their own customer-oriented product catalogue. A customer-oriented product catalogue in different IEPs can also be different. An example of the catalogue is shown in Figure I.1. The basic catalogues in different TOSs can also be different. + +![Figure I.1: Example of product classification catalogue. A hierarchical tree diagram showing product categories and sub-categories. 'Communication services' branches into 'Fixed line services' (subdivided into 'Broadband TV' and '.....') and 'Mobile services' (subdivided into 'Traffic', 'Voice', 'Message', and '.....'). 'Fixed line services' is linked to a box labeled 'SPU: Home broadband', which in turn branches into two boxes labeled 'SKU1' and 'SKU2'. 'Tangible goods' branches into 'Modems', 'Cameras', 'Phones', and '.....'. 'Manual on-site construction' branches into 'Broadband installation', 'Terminal installation', and '.....'. A small code 'M.3111.1(25)' is in the bottom right.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +Figure I.1: Example of product classification catalogue. A hierarchical tree diagram showing product categories and sub-categories. 'Communication services' branches into 'Fixed line services' (subdivided into 'Broadband TV' and '.....') and 'Mobile services' (subdivided into 'Traffic', 'Voice', 'Message', and '.....'). 'Fixed line services' is linked to a box labeled 'SPU: Home broadband', which in turn branches into two boxes labeled 'SKU1' and 'SKU2'. 'Tangible goods' branches into 'Modems', 'Cameras', 'Phones', and '.....'. 'Manual on-site construction' branches into 'Broadband installation', 'Terminal installation', and '.....'. A small code 'M.3111.1(25)' is in the bottom right. + +**Figure I.1 – Example of product classification catalogue** + +The catalogue information item sent from the TOS to the IEP includes item ID, item name, action type, item number, and parent ID. An example of a catalogue item list is shown in Table I.1, which is to establish the product catalogue as shown in Figure I.1. + +**Table I.1 – An example of a catalogue item list** + +| Catalogue ID | Catalogue name | Parent ID | Number | Action type | +|--------------|-----------------------------|-----------|--------|-------------| +| 101 | communication services | null | 1 | ADD | +| 1001 | fixed line services | 101 | 1 | ADD | +| 1002 | mobile services | 101 | 2 | ADD | +| 102 | tangible goods | null | 2 | ADD | +| 2001 | modems | 201 | 1 | ADD | +| 2002 | cameras | 201 | 2 | ADD | +| 2003 | phones | 201 | 3 | ADD | +| 301 | manual on-site construction | null | 3 | ADD | +| ..... | ..... | ..... | ..... | ..... | + +The catalogue name indicates the product type. The parent ID indicates the relationship from the child to the parent. For example, when the parent ID is 'null', it means that this catalogue item is a root catalogue node; when the parent ID of 'mobile services' is 101, it means that 'mobile services' is the child node of the node 'communication services'. The number indicates the sorted order of the child catalogue nodes which belong to the same parent catalogue node. For example, the number of 'fixed line services' is '1' and the number of 'mobile services' is '2'. It means that the catalogue node 'fixed line services' will be displayed above the catalogue node 'mobile services' in the catalogue structure. The action type indicates the operation type performed to this catalogue item, which includes 'ADD' for adding new catalogue item, 'MOD' for modifying the existing catalogue item, and 'DEL' for deleting the existing catalogue item. For example, in Table I.1, all the action types are 'ADD' in order to establish the new catalogue. When the catalogue item information needs to be modified, the action type will be 'MOD'. For example, if the catalogue name of catalogue ID 2003 needs to be changed from 'phone' to 'cell phone', the modification information sent across this interface is shown in Table I.2. + +**Table I.2 – An example of catalogue information modification** + +| Catalogue ID | Catalogue name | Parent ID | Number | Action type | +|--------------|----------------|-----------|--------|-------------| +| 2003 | cell phones | 201 | 3 | MOD | + +When the catalogue item information needs to be deleted, the action type will be 'DEL'. For example, if the catalogue information of catalogue ID 301 needs to be deleted, the information sent across this interface is shown in Table I.3. + +**Table I.3 – Examples of catalogue information deletion** + +| Catalogue ID | Catalogue name | Parent ID | Number | Action type | +|--------------|-----------------------------|-----------|--------|-------------| +| 301 | manual on-site construction | null | 3 | DEL | + +## Bibliography + +- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework.* +- [b-ITU-T X.1149] Recommendation ITU-T X.1149 (2020), *Security framework of an open platform for FinTech services.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3160-200811-I_PDF-E/raw.md b/marked/M/T-REC-M.3160-200811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..30dbd57cdee5ea72c761a45e7fd0e58ffb87724a --- /dev/null +++ b/marked/M/T-REC-M.3160-200811-I_PDF-E/raw.md @@ -0,0 +1,8288 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3160** + +(11/2008) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Generic, protocol-neutral management +information model** + +Recommendation ITU-T M.3160 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. The text "ITU" is prominently displayed in blue, with "International Telecommunication Union" written in smaller blue text to the right. + +ITU logo + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T M.3160** + +# **Generic, protocol-neutral management information model** + +## **Summary** + +Recommendation ITU-T M.3160 provides a generic network information model. The model describes information object classes (IOCs) and their properties that are generic and useful to describe information exchanged across all interfaces defined in Recommendation ITU-T M.3010 TMN architecture. These generic managed object classes are intended to be applicable across different technologies, architecture and services. The managed object classes in this Recommendation may be specialized to support the management of various telecommunications networks. + +This Recommendation follows Recommendation ITU-T M.3020, management interface specification methodology on the analysis phase. The information models provided in this Recommendation are in a protocol-neutral manner, and can be mapped to multiple protocol-specific information models (design phase). + +## **Source** + +Recommendation ITU-T M.3160 was approved on 13 November 2008 by ITU-T Study Group 2 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## **Keywords** + +Information model, protocol-neutral, protocol-specific, technology independent, technology-specific, TMN. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|----------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 1.1 Purpose ..... | 1 | +| 1.2 Field of application..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 3 | +| 4 Abbreviations..... | 3 | +| 5 Conventions ..... | 4 | +| 6 Concepts and background..... | 4 | +| 7 Information object classes ..... | 5 | +| 7.1 Imported information entities and local labels ..... | 5 | +| 7.2 Class diagram ..... | 5 | +| 7.3 Information object class definitions ..... | 30 | +| 7.4 Information relationship definitions ..... | 123 | +| 8 Common information definitions ..... | 181 | +| 8.1 Attributes ..... | 181 | +| 8.2 Notifications ..... | 214 | +| Appendix I..... | 215 | +| Bibliography..... | 218 | + + + +## **Recommendation ITU-T M.3160** + +## **Generic, protocol-neutral management information model** + +# **1 Scope** + +This Recommendation provides a generic network information model. It identifies TMN object classes that are common to managed telecommunication networks, or are of a generic type that can be used to manage a network at a technology-independent level, or are super-classes of technology-specific managed objects in a telecommunication network, or management support objects that are required for the management of the telecommunication network. These objects are relevant to information exchanged across standardized interfaces defined in the [b-ITU-T M.3010] TMN architecture. + +This Recommendation addresses generically the abstractions of those aspects of telecommunication resources (e.g., equipments, telecommunication services) required to manage the network. It also includes the abstractions related to the management services. [b-ITU-T G.805], on the generic functional architecture of the connection-oriented transport network, and [b-ITU-T G.809], on the functional architecture of connectionless layer networks, are used as the basis in developing the transport aspects of this model. + +The generic information model provided in this Recommendation follows the [ITU-T M.3020] interface methodology on the analysis phase, and they are developed in a protocol-neutral manner, which can be mapped to multiple protocol-specific information models. + +This Recommendation does not address abstractions relevant to technology-specific areas or implementation-specific details. + +## **1.1 Purpose** + +### **1.1.1 Interoperability** + +There will be a variety of TMN conformant management systems and managed systems concerning many technology-specific areas, such as switching and transmission. One purpose of this Recommendation is to provide a vehicle for management interoperability between such systems. + +### **1.1.2 Technology-independent management** + +By introducing the concept of technology-independent management, it is possible to perform management of diverse equipment using common communication interfaces. In this manner, an "abstract" view over a set of network-elements can be achieved. + +### **1.1.3 Facilitating information model development** + +This Recommendation also provides a framework from which technology-specific information models may be developed. + +## **1.2 Field of application** + +This Recommendation captures the generally applicable requirements of the technology-independent and technology-specific information models, as well as information relating to TMN management services. + +Through specialization, this Recommendation is applicable to technology-specific TMN information models. The mechanism for specialization is inheritance. + +Even though technology-specific models may be derived from this Recommendation, some of the generic managed object classes in this Recommendation are instantiable in order to provide interoperability between equipment supporting information models derived from this Recommendation and equipment that only supports the information model in this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T E.410] Recommendation ITU-T E.410 (1998), *International network management – General information*. +- [ITU-T M.1400] Recommendation ITU-T M.1400 (2006), *Designations for interconnections among operators' networks*. +- [ITU-T M.1401] Recommendation ITU-T M.1401 (2006), *Formalization of interconnection designations among operators' telecommunication networks*. +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2008), *Management interface specification methodology*. +- [ITU-T X.731] Recommendation ITU-T X.731 (1992) | ISO/IEC 10164-2:1993, *Information technology – Open Systems Interconnection – Systems management: State management function*. +- [ITU-T X.734] Recommendation ITU-T X.734 (1992) | ISO/IEC 10164-5:1993, *Information technology – Open Systems Interconnection – Systems Management: Event report management function*. +- [ISO 3166-1] ISO 3166-1:2006, *Codes for the representation of names of countries and their subdivisions – Part 1: Country codes*. + +Additional non-normative references can be found in the Bibliography. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 aggregate audible/visual indicators** [b-ITU-T M.3100]: An audible/visual alarm indicator that reflects information about a set of managed resources. +- 3.1.2 alarm reporting** [b-ITU-T M.3100]: Process of alerting, for the purposes of management, external systems and users regarding alarms. +- 3.1.3 ALarM reporting (ALM)** [b-ITU-T M.3100]: Alarm Reporting is turned on. +- 3.1.4 alarm reporting control** [b-ITU-T M.3100]: Involves the turning off of alarm reporting which includes inhibiting new autonomous alarm indication notification, and inhibiting the use of managed resource-specific/unit alarm information for the determination of aggregate audible/visual indicators. Autonomous alarm clear notification for previously reported alarms will not be suppressed. Alarm reporting "on" is supported by the "ALM" state. Alarm reporting "off" is supported by the "NALM-QI", "NALM-TI", and "NALM" states. + +- 3.1.5 ARC interval** [b-ITU-T M.3100]: Generic term that applies to both the persistence and timed intervals. +- 3.1.6 inhibited** [b-ITU-T M.3100]: This term is used throughout this feature description to identify that reporting is off (or in other words, is not allowed). +- 3.1.7 managed entity** [b-ITU-T M.3100]: A managed entity may be a managed system, a managed application, or a managed resource. This definition is dependent upon the context in which it is used. +- 3.1.8 managed resource** [b-ITU-T M.3100]: A specific component of a managed system/managed application (e.g., a specific circuit pack, termination point). +- 3.1.9 managed resource-specific/unit audible/visual indicator** [b-ITU-T M.3100]: An audible/visual alarm indicator that is specific to a single managed resource. +- 3.1.10 management interface** [b-ITU-T M.3100]: Any managed entity interface that is defined for the purpose of management (e.g., OS interface, craft interface, LED indicator). +- 3.1.11 No ALarM reporting (NALM)** [b-ITU-T M.3100]: Alarm Reporting is turned off. +- 3.1.12 No ALarM reporting, CountDown (NALM-CD)** [b-ITU-T M.3100]: This is a substate of NALM-QI and performs the persistence timing countdown function when the managed entity is qualified problem-free. +- 3.1.13 No ALarM reporting, NotReady (NALM-NR)** [b-ITU-T M.3100]: This is a substate of NALM-QI and performs a wait function until the managed entity is qualified problem-free. +- 3.1.14 No ALarM reporting, Qualified Inhibit (NALM-QI)** [b-ITU-T M.3100]: Alarm Reporting is turned off until the managed entity is qualified problem-free for a specified persistence interval. +- 3.1.15 No ALarM reporting, Timed Inhibit (NALM-TI)** [b-ITU-T M.3100]: Alarm Reporting is turned off for a specified timed interval. +- 3.1.16 persistence interval** [b-ITU-T M.3100]: A period of time for which a managed entity must be free of qualified problems. +- 3.1.17 qualified problem** [b-ITU-T M.3100]: A problem that affects the operability of the managed entity and used to qualify transitions between the "NALM-NR" and "NALM-CD" states. Additional detail for this definition is managed resource specific and is to be defined by the managed resource. +- 3.1.18 timed interval** [b-ITU-T M.3100]: A period of time. + +## 3.2 Terms defined in this Recommendation + +This Recommendation has no new definitions. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| AP | Access Point | +| ARC | Alarm Reporting Control | +| ASAP | Alarm Severity Assignment Profile | +| AVC | Attribute Value Change Notification | +| DN | Distinguished Name | +| FD | Flow Domain | + +| | | +|---------|--------------------------------------| +| FDFr | Flow Domain Fragment | +| FP | Flow Point | +| FPP | Flow Point Pool | +| FPPLink | Flow Point Pool Link | +| FTP | Flow Termination Point | +| ICC | ITU Carrier Code | +| IOC | Information Object Class | +| ME | Managed Element | +| MO | Managed Object | +| MOC | Managed Object Class | +| NE | Network Element | +| NEF | Network Element Function | +| NWCTP | Network Connection Termination Point | +| NWTTP | Network Trail Termination Point | +| OS | Operations System | +| RDN | Relative Distinguished Name | +| PBX | Private Branch eXchange | +| RDN | Relative Distinguished Name | +| SC | Service Customer | +| SCN | State Change Notification | +| SDH | Synchronous Digital Hierarchy | +| SLA | Service Level Agreement | +| SP | Service Provider | +| TMN | Telecommunication Management Network | +| UML | Unified Modelling Language | + +# 5 Conventions + +This Recommendation follows the conventions defined by the Methodology in [ITU-T M.3020]. + +# 6 Concepts and background + +A generic network information model is essential to the generation of uniform fault, configuration, performance, security, and accounting management standards. A common network model, identifying the generic resources that exist in a network and their associated attribute types, events, actions, and behaviours, provides a foundation for understanding the interrelationships between these resources and attributes, and may, in turn, promote uniformity in dealing with the various aspects of managing these resources and attributes. + +Network resources may be customer or provider owned; the latter includes portions that may be assigned for exclusive use by specific customers. Resources may be physical or logical in nature. Physical resources include customer (e.g., PBXs) or provider (e.g., digital cross-connect systems) systems, their associated subsystems (e.g., a line card within a PBX) and also the links that + +interconnect these systems. Such systems are generally known as network elements (NEs). Logical resources include communication protocols, application programs, logs, and network services. + +There may also exist (separate or integrated) resources involved in operating a telecommunications network. These resources include the operations systems (OSs) closely associated with managing specific NEs, and OSs that have network-wide responsibilities. + +Resources have attributes that allow the user to control and/or observe the behaviour of the resource. Attributes may also allow the user to control and/or observe the relationships between resources. + +There is a need to represent the way resources, or entities can be combined and interrelated (relationships). In this version, UML class diagram techniques have been used to represent inter-object relationships. + +These UML diagrams result in a high-level view (schema) of the model. This view can be used to derive information related to naming, to verifying consistency, and to ensuring completeness. For example, it ensures that sufficient information (i.e., relationships) is provided from a physical resource to identify the services that are dependent on that resource. + +Resources are modelled as objects, and the management view of a resource is called a managed object. Additional objects, called support managed objects, are defined to support the functions of managing a telecommunications network. + +Objects with similar attributes and behaviours may be grouped into object classes. An object is characterized by its object class and object instance, and may possess multiple attribute types and associated values. Similarly, the terms managed object class and managed object instance apply specifically to objects that are being managed. This Recommendation specifies the properties of the resource (i.e., managed object) visible for management. + +An object class may be a subclass of another object class. A subclass inherits attribute types and behaviours of its super-class, in addition to possessing its own specific attributes and properties. + +Object classes and attribute types are defined only for the purpose of communicating network management messages between systems, and need not be related to the structuring of data within these systems. Some object classes defined in these issues (and future issues) of the model apply to many management functional areas, while others support specific functional areas. + +# **7 Information object classes** + +## **7.1 Imported information entities and local labels** + +None. + +## **7.2 Class diagram** + +There are several different viewpoints of management information which may be defined for management purposes, with the network element level viewpoint, the network level viewpoint and the service level viewpoint defined below. These viewpoints are not restrictive but define the levels of abstraction of particular types of interfaces. That is, object class definitions are not forced into this categorization but are constructed to meet the needs of exchanging management information across management interfaces. Objects defined for a given viewpoint may be used in others, and any object may be used by any interface which requires it. The definition of viewpoint is a means of generating requirements, hence there is no implicit definition of interfaces or storage requirements. This information is defined for the purpose of management via an open interface. + +The network element level viewpoint is concerned with the information that is required to manage a network element (NE). This refers to the information required to manage the network element + +function (NEF) and the physical aspects of the NE. The information may be derived from open systems other than the NE. + +The network level viewpoint is concerned with the information representing the network, both physically and logically. It is concerned with how network element entities are related, topographically interconnected, and configured to provide and maintain end-to-end connectivity. + +The service level viewpoint is concerned with how network level aspects (such as an end-to-end path) are utilized to provide a network service, and as such is concerned with the requirements of a network service (e.g., availability, cost, etc.) and how these requirements are met through the use of the network, and all related customer information. + +The object classes that form the basis for the generic network information model are grouped into fragments. The purpose of defining fragments is only to have a document that is easier to read by grouping a limited number of object class definitions. Each fragment deals with a particular subject (e.g., network, managed element, transmission, support objects) but object classes of each fragment will be usable in various models depending on the functional area managed and/or on the level viewpoint considered. + +### 7.2.1 High level overview + +Clause 7.2.1.1 provides a high-level overview of each fragment with an emphasis of the containment relationship. + +#### 7.2.1.1 Network fragment + +The network fragment is a grouping of object classes that represent collections of interconnected telecommunications and management objects (logical or physical) capable of exchanging information. These objects have one or more common characteristics, for example, they may be owned by a single customer or provider, or associated with a specific service network. A network may be nested within another (larger) network, thereby forming a containment relationship. + +Information object classes (IOCs) in the network fragment are presented in Figures 1 and 2. + +![UML Class Diagram for Network fragment (part 1)](fbfa653853daf5541118a9ddecb92284_img.jpg) + +The diagram illustrates the Network fragment structure. At the top is the **Network \*** class, which is a generalization of **Layer Network Domain**, **Trail**, **Connection**, and **Managed Element \***. A containment relationship is shown between **Network \*** and **Layer Network Domain** with the role name <> and multiplicity 0..\* at the Layer Network Domain end. A similar containment relationship is shown between **Network \*** and **Trail**, **Connection**, and **Managed Element \*** with the role name <> and multiplicity 0..\* at each of these ends. A note indicates that **Network \*** includes its subclasses. Below **Layer Network Domain**, there is another containment relationship with **Sub Network** with the role name <> and multiplicity 0..\* at the Sub Network end. A note indicates that the object classes shown in dotted outlines (**Trail**, **Connection**, and **Managed Element \***) are found in other fragments. + +UML Class Diagram for Network fragment (part 1) + +Figure 1 – Network fragment (part 1) + +![UML Class diagram showing network object classes and their relationships. Classes include Operator, Cross-Coupling Site, Multipoint Trail, Site Relationship, Address, Association, Equipment Identity, Location, Exchange, Equipment Item, Physical Link, Trail (M.1401), Position, Component Item, Physical Link Connection, Trail Multiplex Channel, Port Item, Termination, and Trail Section. Relationships are shown with lines and diamond symbols, often labeled with '<>' and multiplicities like '0..*'.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Object classes shown in dotted outlines are found in other fragment + +**Operator** (dotted outline) + + +- Associated with **Cross-Coupling Site** (0..\*) and **Multipoint Trail** (0..\*) via a relationship labeled **<>**. + +**Cross-Coupling Site** + +- Associated with **Location** (0..\*) via a relationship labeled **<>**. +- Associated with **Exchange** (0..\*) via a relationship labeled **<>**. +- Associated with **Equipment Item** (0..\*) via a relationship labeled **<>**. + +**Location** + +- Associated with **Position** (0..\*) via a relationship labeled **<>**. + +**Exchange** + +- Associated with **Component Item** (0..\*) via a relationship labeled **<>**. + +**Equipment Item** + +- Associated with **Component Item** (0..\*) via a relationship labeled **<>**. + +**Component Item** + +- Associated with **Port Item** (0..\*) via a relationship labeled **<>**. + +**Site Relationship** + +- Associated with **Physical Link** (0..\*) and **Trail (M.1401)** (0..\*) via a relationship labeled **<>**. + +**Physical Link** + +- Associated with **Physical Link Connection** (0..\*) via a relationship labeled **<>**. + +**Trail (M.1401)** + +- Associated with **Trail Multiplex Channel** (0..\*) via a relationship labeled **<>**. + +**Trail Multiplex Channel** + +- Associated with **Termination** (0..\*) and **Trail Section** (0..\*) via a relationship labeled **<>**. + +Other classes shown on the right (not connected in this fragment): + + +- Address** +- Association** +- Equipment Identity** + +UML Class diagram showing network object classes and their relationships. Classes include Operator, Cross-Coupling Site, Multipoint Trail, Site Relationship, Address, Association, Equipment Identity, Location, Exchange, Equipment Item, Physical Link, Trail (M.1401), Position, Component Item, Physical Link Connection, Trail Multiplex Channel, Port Item, Termination, and Trail Section. Relationships are shown with lines and diamond symbols, often labeled with '<>' and multiplicities like '0..\*'. + +Figure 2 – Network fragment (part 2) + +#### 7.2.1.2 Managed element fragment + +IOCs in managed element fragment are presented in Figure 3. + +![UML Class Diagram for Managed element fragment](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +This UML class diagram illustrates the Managed element fragment. At the top is the **Network** class (dashed outline), which has a composition relationship with **Managed Element Complex** (solid box) labeled <> with a 0..\* multiplicity. **Managed Element Complex** has a composition relationship with **Managed Element** (solid box) labeled <> with a 0..\* multiplicity. **Managed Element** has a composition relationship with **Equipment** (solid box) labeled <> with a 0..\* multiplicity. **Equipment** has composition relationships with **Fabric** (dashed outline), **Software** (dashed outline), and **Termination Point** (dashed outline), each labeled <> with a 0..\* multiplicity. Callouts indicate that dashed outlines represent subclasses, with specific notes for Equipment (including EquipmentHolder and CircuitPack), Fabric, and Termination Point (representing source, sink, and bidirectional IOC). A note also states that object classes in dotted outlines are found in other fragments. + +UML Class Diagram for Managed element fragment + +Figure 3 – Managed element fragment + +#### 7.2.1.3 Physical equipment fragment + +IOCs in the physical equipment fragment are presented in Figure 4. + +![UML Class Diagram for Physical equipment fragment](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +This UML class diagram illustrates the Physical equipment fragment. It starts with **Managed Element** (dashed outline) at the top, which has a composition relationship with **Equipment Holder** (solid box) labeled <> with a 0..\* multiplicity. **Equipment Holder** has a composition relationship with **Circuit Pack** (solid box) labeled <> with a 0..\* multiplicity. **Circuit Pack** has a composition relationship with **Managed Element** (dashed outline) labeled <> with a 0..\* multiplicity. Callouts indicate that dashed outlines represent subclasses and that object classes in dotted outlines are found in other fragments. + +UML Class Diagram for Physical equipment fragment + +Figure 4 – Physical equipment fragment + +#### 7.2.1.4 Logical equipment fragment + +IOCs in the logical equipment fragment are presented in Figure 5. + +![UML Class Diagram for Figure 5: Logical equipment fragment. The diagram shows Managed Element as the root class, with Software and Equipment as subclasses. Software has its own subclasses. Associations are shown with multiplicities and role names like 'names'.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +``` + +classDiagram + class ManagedElement["<> Managed Element *"] + class Software1["<> Software *"] + class Equipment["<> Equipment *"] + class Software2["<> Software *"] + + ManagedElement <|-- Software1 + ManagedElement <|-- Equipment + Software1 <|-- Software2 + + ManagedElement "1" *-- "0..*" Software1 : <> + ManagedElement "1" *-- "0..*" Equipment : <> + Software1 "1" *-- "0..*" Software2 : <> + Equipment "1" *-- "0..*" Software2 : <> + + note for Software1 "* Includes its subclasses" + note for Software2 "* Includes its subclasses" + note for Equipment "Object classes shown in dotted outlines are found in other fragment" + +``` + +UML Class Diagram for Figure 5: Logical equipment fragment. The diagram shows Managed Element as the root class, with Software and Equipment as subclasses. Software has its own subclasses. Associations are shown with multiplicities and role names like 'names'. + +Figure 5 – Logical equipment fragment + +#### 7.2.1.5 Termination point fragment – Network element view + +IOCs in termination point fragment for the element view are presented in Figure 6. + +![UML Class Diagram for Figure 6: Termination point fragment – Network element view. The diagram shows Managed Element as the root class, with Trail Termination Point Sink, Trail Termination Point Source, Connection Termination Point Sink, and Connection Termination Point Source as subclasses. Associations are shown with multiplicities and role names like 'names'. Callouts explain relationships and where other object classes are defined.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` + +classDiagram + class ManagedElement["<> Managed Element *"] + class TrailTerminationPointSink["<> Trail Termination Point Sink *"] + class TrailTerminationPointSource["<> Trail Termination Point Source *"] + class ConnectionTerminationPointSink["<> Connection Termination Point Sink *"] + class ConnectionTerminationPointSource["<> Connection Termination Point Source *"] + + ManagedElement <|-- TrailTerminationPointSink + ManagedElement <|-- TrailTerminationPointSource + TrailTerminationPointSink <|-- ConnectionTerminationPointSink + TrailTerminationPointSource <|-- ConnectionTerminationPointSource + + ManagedElement "1" *-- "0..*" TrailTerminationPointSink : <> + ManagedElement "1" *-- "0..*" TrailTerminationPointSource : <> + TrailTerminationPointSink "1" *-- "0..*" ConnectionTerminationPointSink : <> + TrailTerminationPointSource "1" *-- "0..*" ConnectionTerminationPointSource : <> + + note for TrailTerminationPointSink "* Includes its subclasses" + note for TrailTerminationPointSource "* Includes its subclasses" + note for ManagedElement "Object classes shown in dotted outlines are found in other fragment" + note for ConnectionTerminationPointSink "Connection Termination Points (Sink and Source) may also be contained by Trail Termination Point Bidirectional" + +``` + +UML Class Diagram for Figure 6: Termination point fragment – Network element view. The diagram shows Managed Element as the root class, with Trail Termination Point Sink, Trail Termination Point Source, Connection Termination Point Sink, and Connection Termination Point Source as subclasses. Associations are shown with multiplicities and role names like 'names'. Callouts explain relationships and where other object classes are defined. + +Figure 6 – Termination point fragment – Network element view + +#### 7.2.1.6 Termination point fragment – Network view + +IOCs in termination point fragment for the network view are presented in Figure 7. + +![UML Class Diagram for Termination point fragment – Network view](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +This UML class diagram illustrates the Termination point fragment for the network view. At the top is the **Layer Network Domain** class (dotted outline), which has a composition relationship with the **Sub Network** class (dotted outline) via a **<>** association. A note indicates that **Layer Network Domain** includes its subclasses. The **Sub Network** class has a composition relationship with two proxy classes: **Network TTP** and **Network CTP**, both marked with **\*\***. These associations are also labeled **<>** and have a multiplicity of **0..\***. A note for these proxy classes indicates they include both Sink, Source, and Bidirectional types. A third note states that object classes shown in dotted outlines are found in other fragments. + +UML Class Diagram for Termination point fragment – Network view + +Figure 7 – Termination point fragment – Network view + +#### 7.2.1.7 Topology and connectivity fragment + +IOCs in the topology and connectivity fragment for the network view are presented in Figure 8. + +![UML Class Diagram for Topology and connectivity fragment](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +This UML class diagram illustrates the Topology and connectivity fragment. At the top is the **Layer Network Domain** class (dotted outline), which has a composition relationship with the **Sub Network** class (dotted outline) via a **<>** association with a multiplicity of **0..\***. A note indicates that **Layer Network Domain** includes its subclasses. The **Sub Network** class has composition relationships with three classes: **Logical Link** (dotted outline), **Topological Link** (solid outline), and **Access Group** (dotted outline), all via **<>** associations with a multiplicity of **0..\***. A note states that object classes shown in dotted outlines are found in other fragments. The **Logical Link** class has a composition relationship with the **Logical Link End** class (dotted outline) via a **<>** association with a multiplicity of **0..\***. A note indicates that **Logical Link** includes its subclasses. The **Topological Link** class has a composition relationship with the **Topological Link End** class (dotted outline) via a **<>** association with a multiplicity of **0..\***. A note indicates that **Topological Link** includes its subclasses. The **Access Group** class has a composition relationship with the **Link Connection** class (dotted outline) via a **<>** association with a multiplicity of **0..\***. A note indicates that **Access Group** includes its subclasses. Finally, the **Logical Link End**, **Topological Link End**, and **Link Connection** classes all have composition relationships with the **Sub Network Connection** class (dotted outline) via **<>** associations with a multiplicity of **0..\***. A note indicates that **Sub Network Connection** includes its subclasses. + +UML Class Diagram for Topology and connectivity fragment + +Figure 8 – Topology and connectivity fragment + +#### 7.2.1.8 Telemetry fragment + +IOCs in the telemetry fragment are presented in Figure 9. + +![UML Class Diagram for Telemetry fragment showing Managed Element Complex, Managed Element, Equipment, and External Point classes and their relationships.](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +``` + +classDiagram + class ManagedElementComplex["<> Managed Element Complex *"] + class ManagedElement["<> Managed Element"] + class Equipment["<> Equipment *"] + class ExternalPoint["<> External Point *"] + + ManagedElementComplex "1" *-- "0..*" ManagedElement : <> + ManagedElementComplex "1" *-- "0..*" Equipment : <> + ManagedElementComplex "1" *-- "0..*" ExternalPoint : <> + ManagedElement "1" *-- "0..*" Equipment : <> + ManagedElement "1" *-- "0..*" ExternalPoint : <> + Equipment "1" *-- "0..*" ExternalPoint : <> + + note right of ManagedElementComplex: Object classes shown in dotted outlines are found in other fragment + note right of Equipment: * Includes its subclasses + note right of ExternalPoint: Its subclasses (Control Point and Scan Point) includes both Sink and Source + +``` + +The diagram illustrates the Telemetry fragment structure. At the top is the **Managed Element Complex** class (dotted outline), which has a composition relationship with **Managed Element** (dotted outline), **Equipment**, and **External Point** (all with 0..\* multiplicity and <> role). **Managed Element** (dotted outline) further composes **Equipment** and **External Point** (both with 0..\* multiplicity and <> role). **Equipment** also composes **External Point** (0..\* multiplicity and <> role). Annotations indicate that classes in dotted outlines are found in other fragments, and that **External Point** subclasses include Control Point and Scan Point. + +UML Class Diagram for Telemetry fragment showing Managed Element Complex, Managed Element, Equipment, and External Point classes and their relationships. + +Figure 9 – Telemetry fragment + +#### 7.2.1.9 Transmission fragment + +IOCs in the transmission fragment are presented in Figure 10. + +![UML Class Diagram for Transmission fragment showing Network, Layer Network Domain, Connection, and Trail classes and their relationships.](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` + +classDiagram + class Network["<> Network *"] + class LayerNetworkDomain["<> Layer Network Domain"] + class Connection["<> Connection *"] + class Trail["<> Trail *"] + + Network "1" *-- "0..*" LayerNetworkDomain : <> + Network "1" *-- "0..*" Connection : <> + Network "1" *-- "0..*" Trail : <> + LayerNetworkDomain "1" *-- "0..*" Trail : <> + + note right of Network: Object classes shown in dotted outlines are found in other fragment + note left of Connection: * Includes its subclasses + +``` + +The diagram illustrates the Transmission fragment structure. The **Network** class (dotted outline) has a composition relationship with **Layer Network Domain** (dotted outline), **Connection**, and **Trail** (all with 0..\* multiplicity and <> role). **Layer Network Domain** (dotted outline) further composes **Trail** (0..\* multiplicity and <> role). Annotations indicate that classes in dotted outlines are found in other fragments, and that **Connection** includes its subclasses. + +UML Class Diagram for Transmission fragment showing Network, Layer Network Domain, Connection, and Trail classes and their relationships. + +Figure 10 – Transmission fragment + +#### 7.2.1.10 Cross-connection fragment + +IOCs in the cross-connection fragment are presented in Figure 11. + +![UML Class Diagram for Cross-connection fragment](dfe556fea00682b09a59427aaf72051c_img.jpg) + +``` + +classDiagram + class ManagedElement { + <> + ManagedElement * + } + class Fabric { + <> + Fabric * + } + class GroupTerminationPoint { + <> + GroupTerminationPoint * + } + class MultipointCrossConnection { + <> + MultipointCrossConnection * + } + class TerminationPointPool { + <> + TerminationPointPool * + } + class CrossConnection { + <> + CrossConnection * + } + + ManagedElement <|-- Fabric + Fabric <|-- GroupTerminationPoint + Fabric <|-- MultipointCrossConnection + Fabric <|-- TerminationPointPool + MultipointCrossConnection <|-- CrossConnection + CrossConnection <|-- GroupTerminationPoint + CrossConnection <|-- TerminationPointPool + + ManagedElement "1" *-- "0..*" Fabric : <> + Fabric "1" *-- "0..*" GroupTerminationPoint : <> + Fabric "1" *-- "0..*" MultipointCrossConnection : <> + Fabric "1" *-- "0..*" TerminationPointPool : <> + MultipointCrossConnection "1" *-- "0..*" CrossConnection : <> + + note for Fabric "* Includes its subclasses" + note for ManagedElement "Object classes shown in dotted outlines are found in other fragment" + note for CrossConnection "* Includes its subclasses" + note for CrossCouplingSite "Object classes shown in dotted outlines are found in other fragment" + +``` + +The diagram illustrates the cross-connection fragment. At the top is the **Managed Element** class (dotted outline). Below it is the **Fabric** class, which inherits from **Managed Element**. **Fabric** has three subclasses: **Group Termination Point**, **Multipoint Cross Connection**, and **Termination Point Pool**. **Multipoint Cross Connection** has a subclass **Cross Connection**. **Cross Connection** has two subclasses: **Group Termination Point** and **Termination Point Pool**. Associations with the stereotype **<>** and multiplicity **0..\*** are shown between **Managed Element** and **Fabric**, **Fabric** and its subclasses, and **Multipoint Cross Connection** and **Cross Connection**. Callouts indicate that classes with dotted outlines are found in other fragments and that solid lines represent inheritance. + +UML Class Diagram for Cross-connection fragment + +Figure 11 – Cross-connection fragment + +#### 7.2.1.11 Organization fragment + +IOCs in the organization fragment are presented in Figure 12. + +![UML Class Diagram for Organization fragment](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +``` + +classDiagram + class Country { + <> + Country + } + class Operator { + <> + Operator + } + class GeographicalArea { + <> + GeographicalArea + } + class CrossCouplingSite { + <> + Cross-Coupling Site + } + + Country "1" *-- "0..*" Operator : <> + Country "1" *-- "0..*" GeographicalArea : <> + Operator "1" *-- "0..*" CrossCouplingSite : <> + + note for CrossCouplingSite "Object classes shown in dotted outlines are found in other fragment" + +``` + +The diagram illustrates the organization fragment. The **Country** class has associations with the **Operator** and **Geographical Area** classes, both with a multiplicity of **0..\*** and the stereotype **<>**. The **Operator** class has an association with the **Cross-Coupling Site** class (dotted outline) with a multiplicity of **0..\*** and the stereotype **<>**. A callout indicates that classes with dotted outlines are found in other fragments. + +UML Class Diagram for Organization fragment + +Figure 12 – Organization fragment + +#### 7.2.1.12 Connectionless network fragment + +IOCs in the connectionless network fragment are presented in Figures 13 and 14. + +![UML Class Diagram for Figure 13: Connectionless network fragment (part 1) – Network view. The diagram shows a hierarchy starting with Layer Network Domain (dotted outline). It branches into Connectionless Trail (0..*), Access Group (dotted outline, 0..*), and Flow Domain (0..*). Flow Domain further branches into Flow Point Pool Link (0..*), Flow Point Pool (0..*), and Flow Domain Fragment (0..*). Associations are labeled with <>.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` + +classDiagram + class Layer_Network_Domain["<> +Layer Network Domain"] + class Connectionless_Trail["<> +Connectionless Trail"] + class Access_Group["<> +Access Group"] + class Flow_Domain["<> +Flow Domain"] + class Flow_Point_Pool_Link["<> +Flow Point Pool Link"] + class Flow_Point_Pool["<> +Flow Point Pool"] + class Flow_Domain_Fragment["<> +Flow Domain Fragment"] + + Layer_Network_Domain --> Connectionless_Trail : 0..* + Layer_Network_Domain --> Access_Group : 0..* + Layer_Network_Domain --> Flow_Domain : 0..* + Flow_Domain --> Flow_Point_Pool_Link : 0..* + Flow_Domain --> Flow_Point_Pool : 0..* + Flow_Domain --> Flow_Domain_Fragment : 0..* + +``` + +UML Class Diagram for Figure 13: Connectionless network fragment (part 1) – Network view. The diagram shows a hierarchy starting with Layer Network Domain (dotted outline). It branches into Connectionless Trail (0..\*), Access Group (dotted outline, 0..\*), and Flow Domain (0..\*). Flow Domain further branches into Flow Point Pool Link (0..\*), Flow Point Pool (0..\*), and Flow Domain Fragment (0..\*). Associations are labeled with <>. + +Figure 13 – Connectionless network fragment (part 1) – Network view + +![UML Class Diagram for Figure 14: Connectionless network fragment (part 2) – Network element view. The diagram shows a hierarchy starting with Managed Element (dotted outline). It branches into Flow Termination Point Source (0..*) and Flow Termination Point Sink (0..*). Flow Termination Point Source further branches into Flow Point Source (0..*). Flow Termination Point Sink further branches into Flow Point Sink (0..*). Associations are labeled with <>.](10781f43062bf3e9601a1e086710556c_img.jpg) + +``` + +classDiagram + class Managed_Element["<> +Managed Element"] + class Flow_Termination_Point_Source["<> +Flow Termination Point Source"] + class Flow_Termination_Point_Sink["<> +Flow Termination Point Sink"] + class Flow_Point_Source["<> +Flow Point Source"] + class Flow_Point_Sink["<> +Flow Point Sink"] + + Managed_Element --> Flow_Termination_Point_Source : 0..* + Managed_Element --> Flow_Termination_Point_Sink : 0..* + Flow_Termination_Point_Source --> Flow_Point_Source : 0..* + Flow_Termination_Point_Sink --> Flow_Point_Sink : 0..* + +``` + +UML Class Diagram for Figure 14: Connectionless network fragment (part 2) – Network element view. The diagram shows a hierarchy starting with Managed Element (dotted outline). It branches into Flow Termination Point Source (0..\*) and Flow Termination Point Sink (0..\*). Flow Termination Point Source further branches into Flow Point Source (0..\*). Flow Termination Point Sink further branches into Flow Point Sink (0..\*). Associations are labeled with <>. + +Figure 14 – Connectionless network fragment (part 2) – Network element view + +#### 7.2.1.13 Common information object + +IOCs in the common information object fragment are presented in Figure 15. + +![UML Class Diagram for Figure 15: Common information object fragment. The diagram shows four separate classes: Top, Generic Interface, Agent, and Generic Managed Interface. Each class is shown in a separate box.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +``` + +classDiagram + class Top["<> +Top"] + class Generic_Interface["<> +Generic Interface"] + class Agent["<> +Agent"] + class Generic_Managed_Interface["<> +Generic Managed Interface"] + +``` + +UML Class Diagram for Figure 15: Common information object fragment. The diagram shows four separate classes: Top, Generic Interface, Agent, and Generic Managed Interface. Each class is shown in a separate box. + +Figure 15 – Common information object fragment + +### 7.2.2 Attributes and relationships + +#### 7.2.2.1 ER diagram of network fragment + +The entity relationship (ER) diagrams of the network fragment are presented in Figures 16, 17 and 18. + +![ER diagram of network fragment (part 1) showing relationships between Managed Entity, Access Group, Sub Network, Network Termination Point, Abstract Link End, and Abstract Link.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the following components and relationships: + +- Managed Entity** (Proxy Class): + - Associated with **Access Group** (InformationObjectClass) via **relation-SubNetwork-AccessGroup**. Multiplicity: 0..\* at Access Group, 0..\* at Managed Entity. Role: #containedAccessGroupList. + - Associated with **Sub Network** (InformationObjectClass) via **relation-SubNetwork-ManagedEntity**. Multiplicity: 0..\* at Managed Entity, 0..\* at Sub Network. Role: #containedInSubNetworkList. + - Associated with **Network Termination Point** (InformationObjectClass) via **relation-SubNetwork-NetworkTerminationPoint**. Multiplicity: 0..\* at Network Termination Point, 0..1 at Managed Entity. Role: #containedNetworkTPList. + - Associated with **Abstract Link End** (InformationObjectClass) via **relation-SubNetwork-AbstractLinkEnd**. Multiplicity: 0..\* at Abstract Link End, 0..1 at Managed Entity. Role: #containedLinkEndList. +- Sub Network** (InformationObjectClass): + - Associated with **Access Group** (InformationObjectClass) via **relation-SubNetwork-AccessGroup**. Multiplicity: 0..\* at Access Group, 0..\* at Sub Network. Role: #containedInSubNetworkList. + - Associated with **Sub Network** (InformationObjectClass) via **relation-SubNetwork-SubNetwork**. Multiplicity: 0..\* at Sub Network, 0..\* at Sub Network. Role: #containedSubNetworkList. + - Associated with **Network Termination Point** (InformationObjectClass) via **relation-SubNetwork-NetworkTerminationPoint**. Multiplicity: 0..\* at Network Termination Point, 0..1 at Sub Network. Role: #containedLinkPointerList. + - Associated with **Abstract Link End** (InformationObjectClass) via **relation-SubNetwork-AbstractLinkEnd**. Multiplicity: 0..\* at Abstract Link End, 0..1 at Sub Network. Role: #containedLinkList. + - Associated with **Abstract Link** (InformationObjectClass) via **relation-SubNetwork-AbstractLink-2**. Multiplicity: 0..\* at Abstract Link, 0..2 at Sub Network. Role: #linkPointerList. +- Network Termination Point** (InformationObjectClass): + - Associated with **Managed Entity** (Proxy Class) via **relation-SubNetwork-NetworkTerminationPoint**. Multiplicity: 0..\* at Network Termination Point, 0..1 at Managed Entity. Role: #containedNetworkTPList. + - Associated with **Sub Network** (InformationObjectClass) via **relation-SubNetwork-NetworkTerminationPoint**. Multiplicity: 0..\* at Network Termination Point, 0..1 at Sub Network. Role: #containedLinkPointerList. + - Associated with **Abstract Link End** (InformationObjectClass) via **relation-SubNetwork-AbstractLinkEnd**. Multiplicity: 0..\* at Abstract Link End, 0..1 at Network Termination Point. Role: #containedLinkEndList. +- Abstract Link End** (InformationObjectClass): + - Associated with **Managed Entity** (Proxy Class) via **relation-SubNetwork-AbstractLinkEnd**. Multiplicity: 0..\* at Abstract Link End, 0..1 at Managed Entity. Role: #containedLinkEndList. + - Associated with **Sub Network** (InformationObjectClass) via **relation-SubNetwork-AbstractLinkEnd**. Multiplicity: 0..\* at Abstract Link End, 0..1 at Sub Network. Role: #containedLinkList. + - Associated with **Network Termination Point** (InformationObjectClass) via **relation-SubNetwork-AbstractLinkEnd**. Multiplicity: 0..\* at Abstract Link End, 0..1 at Network Termination Point. Role: #containedLinkEndList. + - Associated with **Abstract Link** (InformationObjectClass) via **relation-SubNetwork-AbstractLink-1**. Multiplicity: 0..\* at Abstract Link, 0..\* at Abstract Link End. Role: #containedLinkList. +- Abstract Link** (InformationObjectClass): + - Associated with **Sub Network** (InformationObjectClass) via **relation-SubNetwork-AbstractLink-2**. Multiplicity: 0..\* at Abstract Link, 0..2 at Sub Network. Role: #linkPointerList. + - Associated with **Abstract Link End** (InformationObjectClass) via **relation-SubNetwork-AbstractLink-1**. Multiplicity: 0..\* at Abstract Link, 0..\* at Abstract Link End. Role: #containedLinkList. + +Notes: + +- Object classes shown in dotted outlines are found in other fragment. +- \*\* Represent the IOC's that can be able to support the Sub Network IOC. +- \* Includes its subclasses: NetworkTTPSource, NetworkTTPSink, NetworkTTPBidirectional, NetworkCTPSource, NetworkCTPSink, and NetworkCTPBidirectional. +- Object classes shown in dotted outlines are found in other fragment. +- \* Includes its subclasses + +ER diagram of network fragment (part 1) showing relationships between Managed Entity, Access Group, Sub Network, Network Termination Point, Abstract Link End, and Abstract Link. + +Figure 16 – ER diagram of network fragment (part 1) + +![ER diagram of network fragment (part 2) showing relationships between Termination, Address, Operator, Trail (M.1401), Cross-Coupling Site, Site Relationship, Trail Section, Position, Multipoint Trail, and Physical Link Connection.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +This ER diagram illustrates a network fragment with the following classes and relationships: + +- Termination** (Information Object Class): + - Attributes: #cross-couplingSite (0..\*), #terminationList (1). + - Relationships: + - relation-Termination-Cross-CouplingSite: connects to **Cross-Coupling Site**. +- Address** (Information Object Class): + - Attributes: #siteList (1), #controlledSiteList (0..1), #currentOperator (0..\*), #address (0..\*). + - Relationships: + - relation-Address-Cross-CouplingSite: connects to **Cross-Coupling Site**. +- Operator** (Information Object Class, shown in dotted outline): + - Attributes: #controlledTrailList (0..\*). + - Relationships: + - relation-Operator-Cross-CouplingSite: connects to **Cross-Coupling Site**. + - relation-Operator-Trail(M.1401): connects to **Trail (M.1401)**. +- Trail (M.1401)** (Information Object Class): + - Attributes: #controllerList (0..\*), #associationList (1..\*), #routingTrailSection (1), #position (0..\*). + - Relationships: + - relation-Association-Trail(M.1401): connects to **Association**. + - relation-Position-Trail(M.1401): connects to **Position**. + - relation-TrailSection-Trail(M.1401): connects to **Trail Section**. + - relation-MultipointTrail-Trail(M.1401): connects to **Multipoint Trail**. +- Association** (Information Object Class): + - Attributes: #superiorTrail (0..\*), #trailList (0..\*). + - Relationships: + - relation-Association-superior\_Trail(M.1401): connects to **Trail (M.1401)**. +- Cross-Coupling Site** (Information Object Class): + - Attributes: #a-EndSite (0..\*), #b-EndSite (0..\*), #a-EndSiteRelationshipList (1), #b-EndSiteRelationshipList (1). + - Relationships: + - relation-SiteRelationship-aEnd\_CrossCouplingSite: connects to **Site Relationship**. + - relation-SiteRelationship-bEnd\_CrossCouplingSite: connects to **Site Relationship**. +- Site Relationship** (Information Object Class): + - Relationships: + - relation-SiteRelationship-aEnd\_CrossCouplingSite: connects to **Cross-Coupling Site**. + - relation-SiteRelationship-bEnd\_CrossCouplingSite: connects to **Cross-Coupling Site**. +- Trail Section** (Information Object Class): + - Attributes: #trail (1), #position (0..\*). + - Relationships: + - relation-TrailSection-Trail(M.1401): connects to **Trail (M.1401)**. + - relation-TrailSection-PhysicalLinkConnection: connects to **Physical Link Connection**. + - relation-TrailSection-Position: connects to **Position**. +- Position** (Information Object Class): + - Attributes: #trailList (1), #trailSectionList (1), #physicalLinkConnectionList (1), #position (0..\*). + - Relationships: + - relation-Position-Trail(M.1401): connects to **Trail (M.1401)**. + - relation-TrailSection-Position: connects to **Trail Section**. + - relation-PhysicalLinkConnection-Position: connects to **Physical Link Connection**. +- Multipoint Trail** (Information Object Class): + - Attributes: #trailList (0..1). + - Relationships: + - relation-MultipointTrail-Trail(M.1401): connects to **Trail (M.1401)**. +- Physical Link Connection** (Information Object Class): + - Attributes: #trailSection (1), #position (0..\*). + - Relationships: + - relation-TrailSection-PhysicalLinkConnection: connects to **Trail Section**. + - relation-PhysicalLinkConnection-Position: connects to **Position**. +- Trail Multiplex Channel** (Information Object Class): + - Attributes: #trailSeciton (1), #position (0..\*). + - Relationships: + - relation-TrailMultiplexChannel-Position: connects to **Position**. + +Object classes shown in dotted outlines are found in other fragment. + +ER diagram of network fragment (part 2) showing relationships between Termination, Address, Operator, Trail (M.1401), Cross-Coupling Site, Site Relationship, Trail Section, Position, Multipoint Trail, and Physical Link Connection. + +Figure 17 – ER diagram of network fragment (part 2) + +![ER diagram of network fragment (part 3) showing relationships between Exchange, Equipment Item, Location, Component Item, Equipment Identity, Trail Section, Port Item, and Position.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +This ER diagram illustrates another network fragment with the following classes and relationships: + +- Exchange** (Information Object Class): + - Attributes: #equipmentItem (0..1), #exchange (1). + - Relationships: + - relation-Exchange-EquipmentItem: connects to **Equipment Item**. +- Equipment Item** (Information Object Class): + - Attributes: #location (0..1), #equipmentItem (1), #equipmentIdentity (0..\*). + - Relationships: + - relation-Exchange-EquipmentItem: connects to **Exchange**. + - relation-EquipmentItem-Location: connects to **Location**. + - relation-EquipmentItem-EquipmentIdentity: connects to **Equipment Identity**. +- Location** (Information Object Class): + - Attributes: #componentItem (1), #equipmentItem (0..\*), #locationList (0..1). + - Relationships: + - relation-EquipmentItem-Location: connects to **Equipment Item**. + - relation-ComponentItem-Location: connects to **Component Item**. + - relation-Location-EquipmentIdentity: connects to **Equipment Identity**. +- Component Item** (Information Object Class): + - Attributes: #location (0..1), #componentItem (0..\*), #equipmentIdentity (0..\*). + - Relationships: + - relation-ComponentItem-Location: connects to **Location**. + - relation-Component-EquipmentIdentity: connects to **Equipment Identity**. +- Equipment Identity** (Information Object Class): + - Attributes: #equipmentItem (0..1), #locationList (0..1), #componentItemList (0..1), #equipmentIdentity (0..\*). + - Relationships: + - relation-EquipmentItem-EquipmentIdentity: connects to **Equipment Item**. + - relation-Location-EquipmentIdentity: connects to **Location**. + - relation-Component-EquipmentIdentity: connects to **Component Item**. + - relation-PortItem-EquipmentIdentity: connects to **Port Item**. +- Trail Section** (Information Object Class): + - Attributes: #portItem (1), #trailSection (1). + - Relationships: + - relation-TrailSection-PortItem: connects to **Port Item**. +- Port Item** (Information Object Class): + - Attributes: #position (0..\*), #portItemList (1). + - Relationships: + - relation-TrailSection-PortItem: connects to **Trail Section**. + - relation-PortItem-EquipmentIdentity: connects to **Equipment Identity**. + - relation-PortItem-Position: connects to **Position**. +- Position** (Information Object Class): + - Attributes: #position (1), #portItemList (1). + - Relationships: + - relation-PortItem-Position: connects to **Port Item**. + - relation-Position-Position: connects to itself. + +ER diagram of network fragment (part 3) showing relationships between Exchange, Equipment Item, Location, Component Item, Equipment Identity, Trail Section, Port Item, and Position. + +Figure 18 – ER diagram of network fragment (part 3) + +#### 7.2.2.2 ER diagram of managed element fragment + +The ER diagram of the managed element fragment is presented in Figure 19. + +![ER diagram of managed element fragment (Figure 19)](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +The diagram shows the following entities and relationships: + +- Managed Element** (Information Object Class) is at the top left. It has a relationship **relation-ManagedElement-AlarmSeverityAssignmentProfile** with **Alarm Severity Assignment Profile** (Information Object Class, dotted outline). The multiplicity at Managed Element is 0..\* and at Alarm Severity Assignment Profile is 0..1. The attribute **#alarmSeverityAssignmentProfilePointer** is associated with this relationship. +- Equipment** (Information Object Class) is at the top center. A note above it states: "\* include its sub classes Equipment Holder, and Circuit Pack." + - It has a relationship **relation-Equipment-AlarmSeverityAssignmentProfile** with **Alarm Severity Assignment Profile**. Multiplicity at Equipment is 0..\* and at Alarm Severity Assignment Profile is 0..1. The attribute **#alarmSeverityAssignmentProfilePointer** is associated with this relationship. + - It has a relationship **relation-Equipment-ManagedEntity-1** with **Managed Entity \*\*** (Proxy Class, dotted outline). Multiplicity at Equipment is 0..\* and at Managed Entity \*\* is 0..\*. The attribute **#affectedObjectList** is associated with this relationship. + - It has a relationship **relation-Equipment-ManagedEntity-2** with **Managed Entity \*\*** (Proxy Class, dotted outline). Multiplicity at Equipment is 0..\* and at Managed Entity \*\* is 0..\*. The attribute **#supportedByObjectList** is associated with this relationship. +- Alarm Severity Assignment Profile** (Information Object Class, dotted outline) is at the bottom left. A note below it states: "Object classes shown in dotted outlines are found in other fragment". +- There are two instances of **Managed Entity \*\*** (Proxy Class, dotted outline) at the bottom center and bottom right. + - A note below the center instance states: "\*\* Represent the IOCs that are affected by the Equipment IOC." + - A note below the right instance states: "\*\* Represent the IOCs that are supported by the Equipment IOC." + +ER diagram of managed element fragment (Figure 19) + +Figure 19 – ER diagram of managed element fragment + +#### 7.2.2.3 ER diagram of physical equipment fragment + +The ER diagram of the physical equipment fragment is presented in Figure 20. + +![ER diagram of physical equipment fragment (Figure 20)](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +The diagram shows the following entities and relationships: + +- Equipment Holder** (Information Object Class) is at the top left. It has a relationship **relation-Equipment-Software** with **Software** (Information Object Class, dotted outline). Multiplicity at Equipment Holder is 0..1 and at Software is 0..\*. The attribute **#subordinateCircuitPackSoftwareLoad** is associated with this relationship. +- Circuit Pack** (Information Object Class) is at the top center. + - It has a relationship **relation-CircuitPack-Trail** with **Trail** (Information Object Class, dotted outline). Multiplicity at Circuit Pack is 0..1 and at Trail is 0..\*. The attribute **#portAssociations** is associated with this relationship. + - It has a relationship **relation-Equipment-AlarmSeverityAssignmentProfile** with **Alarm Severity Assignment Profile** (Information Object Class, dotted outline). Multiplicity at Circuit Pack is 0..\* and at Alarm Severity Assignment Profile is 0..1. The attribute **#alarmSeverityAssignmentProfilePointer** is associated with this relationship. +- Software** (Information Object Class, dotted outline) is at the bottom left. A note below it states: "Object classes shown in dotted outlines are found in other fragment". +- Trail** (Information Object Class, dotted outline) is at the bottom center. A note below it states: "Object classes shown in dotted outlines are found in other fragment". +- Alarm Severity Assignment Profile** (Information Object Class, dotted outline) is at the bottom right. A note below it states: "Object classes shown in dotted outlines are found in other fragment". + +ER diagram of physical equipment fragment (Figure 20) + +Figure 20 – ER diagram of physical equipment fragment + +#### 7.2.2.4 ER diagram of logical equipment fragment + +The ER diagram of the logical equipment fragment is presented in Figure 21. + +![ER diagram of logical equipment fragment showing Software, Alarm Severity Assignment Profile, and Managed Entity classes and their relationships.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +This ER diagram illustrates the logical equipment fragment. At the top is the **Software** class (InformationObjectClass). It has two outgoing relationships: **relation-Software-AlarmSeverityAssignmentProfile** pointing to the **Alarm Severity Assignment Profile** class (InformationObjectClass, shown with a dotted outline) with a 0..\* to 0..1 multiplicity and attribute **#alarmSeverityAssignmentProfilePointer**; and **relation-Software-ManagedEntity** pointing to the **Managed Entity** class (ProxyClass, shown with a dotted outline and double asterisks) with a 0..\* to 0..\* multiplicity and attribute **#affectedObjectList**. Two callout boxes at the bottom explain that dotted outlines indicate classes found in other fragments and that double asterisks represent IOCs affected by the Software IOC. + +ER diagram of logical equipment fragment showing Software, Alarm Severity Assignment Profile, and Managed Entity classes and their relationships. + +Figure 21 – ER diagram of logical equipment fragment + +#### 7.2.2.5 ER diagram of termination point fragment – Network element view + +The ER diagram of the termination point fragment – Network element view is presented in Figure 22. + +![ER diagram of termination point fragment – Network element view showing various Termination Point classes and their relationships.](844077b3034f0030b404207db0ad76b4_img.jpg) + +This ER diagram shows the termination point fragment from a network element view. The central class is **Termination Point** (InformationObjectClass, marked with an asterisk). Above it, **Trail Termination Point Sink\*** and **Trail Termination Point Source\*** (both InformationObjectClass, marked with asterisks) are connected via inheritance (dashed lines) from a common superclass **Trail Termination Point Bidirectional** (callout: \* Includes its subclasses). Below **Termination Point**, **Connection Termination Point Sink\*** and **Connection Termination Point Source\*** (both InformationObjectClass, marked with asterisks) are connected via inheritance from a common superclass **Connection Termination Point Bidirectional** (callout: \* Includes its subclasses). Relationships include: **relation-TerminationPoint-AlarmSeverityAssignmentProfile** (0..\* to 0..1, attribute #alarmSeverityAssignmentProfilePointer) to **Alarm Severity Assignment Profile** (dotted outline); **relation-TerminationPoint-ManagedEntity** (0..\* to 0..\*, attribute #supportedByObjectList) to **Managed Entity** (dotted outline); **relation-TrailTerminationPointSink-TerminationPoint** (0..\* to 0..1, attribute #upstreamConnectivityPointer) to **Trail Termination Point Sink\***; **relation-TrailTerminationPointSource-TerminationPoint** (0..\* to 0..1, attribute #downstreamConnectivityPointer) to **Trail Termination Point Source\***; **relation-ConnectionTerminationPointSink-TerminationPoint** (0..\* to 0..1, attribute #downstreamConnectivityPointer) to **Connection Termination Point Sink\***; and **relation-ConnectionTerminationPointSource-TerminationPoint** (0..\* to 0..1, attribute #upstreamConnectivityPointer) to **Connection Termination Point Source\***. A callout box notes that dotted outlines represent classes in other fragments. + +ER diagram of termination point fragment – Network element view showing various Termination Point classes and their relationships. + +Figure 22 – ER diagram of termination point fragment – Network element view + +#### 7.2.2.6 ER diagram of termination point fragment – Network view + +The ER diagrams of the termination point fragment – Network view are presented in Figures 23 and 24. + +![ER diagram of termination point fragment – Network view (part 1).](366a77fdefb0097b3289b4a011911390_img.jpg) + +This ER diagram (Figure 23) illustrates the network view of the termination point fragment. Key components include: + +- Trail\_or\_LinkConnection \*** (ProxyClass): Marked with a note "\*\* Can be Trail or Link Connection". It has a relationship **relation-NetworkTerminationPoint-Trail\_or\_LinkConnection** (0..1) with **Network Termination Point \***. +- NE Termination Point \*** (ProxyClass): Note states "Includes its subclasses. The subclass should be an NE level Termination Point". It has a relationship **relation-NetworkTerminationPoint-NE\_TerminationPoint** (0..1) with **Network Termination Point \*** and **relation-SubNetwork-NetworkTerminationPoint** (0..1) with **Sub Network**. +- Network Termination Point \*** (InformationObjectClass): A central entity with multiple relationships: + - Self-relationship: **relation-NetworkTerminationPoint-NetworkTerminationPoint** (0..1 to 0..1). + - With **Pipe \***: **relation-Pipe-aEnd\_NetworkTerminationPoint** (0..1 to 1..\*) and **relation-Pipe-zEnd\_NetworkTerminationPoint** (0..1 to 1..\*). + - With **Sub Network Connection**: **relation-NetworkTerminationPoint-SubNetworkConnection** (0..1 to 0..\*). +- Sub Network** (InformationObjectClass): Associated with **NE Termination Point \***. +- Sub Network Connection** (InformationObjectClass): Associated with **Network Termination Point \*** via **#subNetworkConnectionPointer**. +- Pipe \*** (InformationObjectClass): Note states "Includes its subclasses. Its subclasses can be Trail, Link Connection, and Sub Network Connection". It connects to **Network Termination Point \*** via aEnd and zEnd relations. + +General notes: "Object classes shown in dotted outlines are found in other fragment". + +ER diagram of termination point fragment – Network view (part 1). + +Figure 23 – ER diagram of termination point fragment – Network view (part 1) + +![ER diagram of termination point fragment – Network view (part 2).](4b87467ad9642943235f48f7d4b59449_img.jpg) + +This ER diagram (Figure 24) continues the network view, focusing on CTP and TTP: + +- Network CTP \*** (ProxyClass): Note states "Includes its subclasses (Source, Sink and Bidirectional)". It has relationships: + - Self-relationship: **relation-NetworkCTP-NetworkCTP** (0..1 to 0..\*) via **#sub-partitionPointer** and **#superPartitionPointer**. + - With **Network TTP \***: **relation-NetworkCTP-NetworkTTP** (0..1 to 0..\*) via **#serverTTPPointer** and **#clientCTPList**. + - With **Logical Link End**: **relation-LogicalLinkEnd-NetworkCTP** (0..\* to 0..\*) via **#networkCTPsInLinkEndList**. +- Network TTP \*** (ProxyClass): Associated with **Network CTP \*** and **Topological Link End**. +- Logical Link End** (InformationObjectClass): Associated with **Network CTP \***. +- Topological Link End** (InformationObjectClass): Associated with **Network TTP \*** via **relation-TopologicalLinkEnd-NetworkTTP** (0..\* to 0..\*) using **#serverTTPPointer**. + +Note: "Object classes shown in dotted outlines are found in other fragment". + +ER diagram of termination point fragment – Network view (part 2). + +Figure 24 – ER diagram of termination point fragment – Network view (part 2) + +#### 7.2.2.7 Topology and connectivity fragment + +The ER diagrams of the topology and connectivity fragment are presented in Figures 25 and 26. + +![ER diagram of topology and connectivity fragment (part 1)](552265bdbcf6d43d341fd018a9076269_img.jpg) + +This ER diagram illustrates the topology and connectivity fragment (part 1). It features several object classes and their relationships: + +- End of Link\*\*** (Proxy Class): Two instances are shown at the top, each with a note indicating it can be an instance of **Abstract Link End** or its subclasses, **Sub Network**, or **Access Group**. They are connected via **relation-AbstractLink-a\_EndofLink** and **relation-AbstractLink-z\_EndofLink** to **Abstract Link**. +- Abstract Link** (Information Object Class): A central class with a note that it includes its subclasses. It is connected to **Access Group** via **relation-AccessGroup-AbstractLink**, to **Sub Network** via **relation-SubNetwork-AbstractLink-2** and **relation-SubNetwork-AbstractLink-1**, and to **Abstract Link End** via **relation-AbstractLinkEnd-AbstractLink**. +- Access Group** (Information Object Class): Connected to **Abstract Link** and **Network TTP** (via **relation-AccessGroup-NetworkTTP**). +- Sub Network** (Information Object Class): Connected to **Abstract Link** and **Abstract Link End** (via **relation-SubNetwork-AbstractLinkEnd**). +- Abstract Link End** (Information Object Class): Connected to **Abstract Link** and **Sub Network**. +- Network TTP** (Proxy Class): Shown with a dotted outline and a note that its object classes are found in another fragment. It is connected to **Access Group** and **Topological Link End** (via **relation-TopologicalLinkEnd-NetworkTTP**). +- Topological Link End** (Information Object Class): Connected to **Network TTP**. + +Relationships are labeled with names like **#linkPointerList**, **#containedInSubNetworkList**, **#accessPointList**, **#serverTTPPointer**, **#aEnd**, **#zEnd**, **#containedAccessGroupList**, **#containedLinkEndList**, and **#containedLinkList**. Multiplicities such as 0..\*, 0..1, 0..2, 0..1, 0..\*, 0..1, 0..\*, 0..1, 0..\*, 0..1, 0..\*, 0..1 are indicated on the relationship lines. + +ER diagram of topology and connectivity fragment (part 1) + +Figure 25 – ER diagram of topology and connectivity fragment (part 1) + +![ER diagram of topology and connectivity fragment (part 2)](e354b57563dae469c00b412b2abdf765_img.jpg) + +This ER diagram illustrates the topology and connectivity fragment (part 2). It features several object classes and their relationships: + +- Logical Link End** (Information Object Class): Connected to **Network CTP** (Proxy Class, shown with a dotted outline) via **relation-LogicalLinkEnd-NetworkCTP**. A note indicates that **Network CTP** includes its subclasses. +- Logical Link** (Information Object Class): Connected to **Link Connection** (Information Object Class) via **relation-LogicalLink-LinkConnection**. +- Topological Link** (Information Object Class): Connected to **Trail** (Information Object Class, shown with a dotted outline) via **relation-TopologicalLink-Trail**. A note indicates that **Trail** includes its subclasses. +- Link Connection** (Information Object Class): A central class connected to **Logical Link**, **Sub Network Connection** (via **relation-SubNetworkConnection-LinkConnection**), and **Trail** (via **relation-LinkConnection-server\_Trail** and **relation-LinkConnection-client\_Trail**). +- Trail** (Information Object Class): Connected to **Topological Link** and **Link Connection**. +- Sub Network Connection** (Information Object Class): Connected to **Link Connection** and to itself via **relation-SubNetworkConnection-SubNetworkConnection**. + +Relationships are labeled with names like **#networkCTPsInLinkEndList**, **#linkConnectionPointerList**, **#serverTrail**, **#clientLinkPointerList**, **#serverTrailList**, **#clientLinkConnectionPointerList**, **#connectionList**, **#componentPointers**, and **#compositePointer**. Multiplicities such as 0..\*, 0..1, 0..\*, 0..1, 0..\*, 0..1, 0..\*, 0..1, 0..\*, 0..1, 0..\*, 0..1 are indicated on the relationship lines. + +ER diagram of topology and connectivity fragment (part 2) + +Figure 26 – ER diagram of topology and connectivity fragment (part 2) + +#### 7.2.2.8 ER diagram of telemetry fragment + +The ER diagram of the telemetry fragment is presented in Figure 27. + +![ER diagram of telemetry fragment showing relationships between External Point, Scan Point, Managed Entity, and Alarm Severity Assignment Profile.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) + +The diagram shows the following classes and relationships: + +- External Point \*** (Information Object Class): + - Associated with **Managed Entity** (Proxy Class) via **relation-ExternalPoint-ManagedEntity** (multiplicity 0..\* at both ends). + - Associated with **Scan Point** (Information Object Class) via **supportedByObjectList** (multiplicity 0..\* at both ends). +- Scan Point** (Information Object Class): + - Associated with **Alarm Severity Assignment Profile** (Information Object Class) via **relation-ScanPoint-AlarmSeverityAssignmentProfile** (multiplicity 0..\* at Scan Point end, 0..1 at Alarm Severity Assignment Profile end). +- Managed Entity** (Proxy Class): + - Associated with **External Point \*** via **relation-ExternalPoint-ManagedEntity**. +- Alarm Severity Assignment Profile** (Information Object Class): + - Associated with **Scan Point** via **relation-ScanPoint-AlarmSeverityAssignmentProfile**. + +Notes: + +- \* Includes its subclasses (pointing to External Point) +- Object classes shown in dotted outlines are found in other fragment (pointing to Managed Entity and Alarm Severity Assignment Profile) + +ER diagram of telemetry fragment showing relationships between External Point, Scan Point, Managed Entity, and Alarm Severity Assignment Profile. + +Figure 27 – ER diagram of telemetry fragment + +#### 7.2.2.9 ER diagram of transmission fragment + +The ER diagrams of the transmission fragment are presented in Figures 28 and 29. + +![ER diagram of transmission fragment (part 1) showing relationships between Network Termination Point, Managed Entity, Pipe, and Alarm Severity Assignment Profile.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +The diagram shows the following classes and relationships: + +- Network Termination Point \*** (Information Object Class): + - Associated with **Pipe \*** (Information Object Class) via **relation-Pipe-aEnd\_NetworkTerminationPoint** (multiplicity 1..\* at Network Termination Point end, 0..1 at Pipe end). + - Associated with **Managed Entity** (Proxy Class) via **relation-Pipe-ManagedEntity** (multiplicity 1..\* at Network Termination Point end, 0..\* at Managed Entity end). +- Pipe \*** (Information Object Class): + - Associated with **Network Termination Point \*** via **relation-Pipe-aEnd\_NetworkTerminationPoint** and **relation-Pipe-zEnd\_NetworkTerminationPoint** (multiplicity 0..1 at Pipe end, 1..\* at Network Termination Point end). + - Associated with **Managed Entity** (Proxy Class) via **relation-Pipe-ManagedEntity** (multiplicity 0..\* at both ends). + - Associated with **Alarm Severity Assignment Profile** (Information Object Class) via **relation-Pipe-AlarmSeverityAssignmentProfile** (multiplicity 0..\* at Pipe end, 0..1 at Alarm Severity Assignment Profile end). +- Managed Entity** (Proxy Class): + - Associated with **Network Termination Point \*** via **relation-Pipe-ManagedEntity**. + - Associated with **Pipe \*** via **relation-Pipe-ManagedEntity**. +- Alarm Severity Assignment Profile** (Information Object Class): + - Associated with **Pipe \*** via **relation-Pipe-AlarmSeverityAssignmentProfile**. + +Notes: + +- Object classes shown in dotted outlines are found in other fragment (pointing to Network Termination Point and Managed Entity) +- \* Includes its subclasses: Network CTP Source, Network CTP Bidirectional, Network TTP Source, and Network TTP Bidirectional. (pointing to Network Termination Point) +- \* Includes its subclasses: Trail, Connection, Link Connection, and Sub Network Connector. (pointing to Pipe) +- \* Includes its subclasses: Network CTP Source, Network CTP Bidirectional, Network TTP Source, and Network TTP Bidirectional. (pointing to Network Termination Point) + +ER diagram of transmission fragment (part 1) showing relationships between Network Termination Point, Managed Entity, Pipe, and Alarm Severity Assignment Profile. + +Figure 28 – ER diagram of transmission fragment (part 1) + +![ER diagram of transmission fragment (part 2)](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +This ER diagram shows the relationships between several network object classes. At the top, a **Connection** class (solid outline) has two associations with **Trail** classes (solid outlines): **#serverTrailList** (multiplicity 0..\*) and **#clientTrail** (multiplicity 0..\*). These are linked via relations **relation-Connection-server\_Trail** and **relation-Connection-client\_Trail**. Below the **Connection** class, there are four classes with dotted outlines: **Circuit Pack**, **Topological Link**, **Link Connection**, and **Sub Network Connection**. These are associated with **Trail** classes through relations **relation-CircuitPack-Trail**, **relation-TopologicalLink-Trail**, **relation-LinkConnection-server\_Trail**, and **relation-Trail-SubNetworkConnection**. There are also associations between **Trail** and **Circuit Pack** (**#portAssociation**), **Trail** and **Topological Link** (**#serverTrail**), **Trail** and **Link Connection** (**#serverTrailList**), and **Trail** and **Sub Network Connection** (**#clientTrail**). A note at the bottom indicates that object classes in dotted outlines are found in other fragments. + +ER diagram of transmission fragment (part 2) + +Figure 29 – ER diagram of transmission fragment (part 2) + +#### 7.2.2.10 ER diagram of cross-connection fragment + +The ER diagram of the cross-connection fragment is presented in Figure 30. + +![ER diagram of cross-connection fragment](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +This ER diagram illustrates the cross-connection fragment. At the top, a **Fabric** class (solid outline) is associated with a **Managed Entity** class (dotted outline) via **relation-Fabric-ManagedEntity** (**#supportedByObjectList**, multiplicity 0..\*). Below **Managed Entity** is a **TP\_or\_GTP** class (dotted outline). A **Cross Connection** class (solid outline) is associated with **TP\_or\_GTP** via **relation-CrossConnection-from\_TP\_or\_GTP** (**#fromTermination**, multiplicity 0..\*). Another **TP\_or\_GTP** class (dotted outline) is associated with **Cross Connection** via **relation-CrossConnection-to\_TP\_or\_GTP** (**#toTermination**, multiplicity 1). Below this is a **Termination Point** class (dotted outline). A **Group Termination Point** class (solid outline) is associated with **Termination Point** via **relation-GroupTerminationPoint-TerminationPoint** (**#tpsInGtpList**, multiplicity 0..\*). **Group Termination Point** is also associated with **Fabric** via **relation-GroupTerminationPoint-Fabric** (**#crossConnectionObjectPointer**, multiplicity 0..1). **Group Termination Point** is associated with **Termination Point Pool** (solid outline) via **relation-TerminationPointPool-GroupTerminationPoint** (**#tpsInTpPoolList**, multiplicity 0..1). **Termination Point Pool** is associated with **Termination Point** via **relation-TerminationPointPool-TerminationPoint** (multiplicity 0..1). A note indicates that **TP\_or\_GTP** can be an instance of CTP Sink, CTP Bidirectional, TTP Source, TTP Bidirectional, or GTP. Another note states that object classes in dotted outlines are found in other fragments. A third note indicates that **Termination Point \*** includes its subclasses. + +ER diagram of cross-connection fragment + +Figure 30 – ER diagram of cross-connection fragment + +#### 7.2.2.11 ER diagram of organization fragment + +The ER diagram of the organization fragment is presented in Figure 31. + +![ER diagram of organization fragment showing Geographical Area, Operator, and Cross-Coupling Site relationships.](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) + +The diagram shows three main object classes: **Geographical Area** (solid box), **Operator** (solid box), and **Cross-Coupling Site** (dotted box). + - **Geographical Area** (multiplicity 1) is associated with **Cross-Coupling Site** (multiplicity 0..\*) via the relationship **relation-CrossCouplingSite-GeographicalAre**. The role on the Geographical Area side is **#siteList**. + - **Operator** (multiplicity 1) is associated with **Cross-Coupling Site** (multiplicity 0..\*) via the relationship **relation-Operator-Cross-CouplingSite**. The role on the Operator side is **#controlledSiteList**. + - **Operator** (multiplicity 0..\*) is associated with **Trail (M.1401)** (dotted box, multiplicity 0..\*) via the relationship **relation-Operator-Trail**. The role on the Operator side is **#controlledTrailList**. + - A note indicates: "Object classes shown in dotted outlines are found in other fragment". + +ER diagram of organization fragment showing Geographical Area, Operator, and Cross-Coupling Site relationships. + +Figure 31 – ER diagram of organization fragment + +#### 7.2.2.12 ER diagram of connectionless network fragment + +The ER diagram of the connectionless network fragment is presented in Figures 32, 33 and 34. + +![ER diagram of connectionless network fragment (part 1) showing various network-related object classes and their relationships.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +This complex diagram includes the following elements: + - **End of FPPLink** (Proxy Class, multiplicity \*\*) is at the top, with a note: "\*\* Can be an instance Flow Domain, Flow Point Pool, or Access Group." + - **Flow Point Pool Link** (Information Object Class, multiplicity 0..\*) is central. It has relationships: + - **relation-FlowPointPoolLink-a\_EndoffPPLink** to **End of FPPLink** (role **#aEndoffPPLink**). + - **relation-FlowPointPoolLink-z\_EndoffPPLink** to **End of FPPLink** (role **#zEndoffPPLink**). + - **relation-FlowPointPool-FlowPointPoolLink** to **Flow Point Pool** (role **#linkPointer**). + - **relation-FlowDomain-FlowPointPoolLink-1** to **Flow Domain** (role **#containedInFlowDomainList**). + - **relation-AccessGroup-FlowPointPoolLink** to **Access Group** (role **#linkPointerList**). + - **Flow Point Pool** (Information Object Class, multiplicity 0..\*) is associated with **Flow Point Pool Link** (role **#containedInFlowDomainList**). + - **Flow Domain** (Information Object Class, multiplicity 0..\*) is associated with **Flow Point Pool Link** (role **#linkPointerList**). It also has relationships: + - **relation-FlowDomain-FlowPointPoolLink-2** to **Flow Point Pool Link** (role **#serverTrail**). + - **relation-FlowDomain-AccessGroup** to **Access Group** (role **#containedAccessGroupList**). + - **relation-FlowDomain-FlowDomain** (self-relationship, role **#containedFlowDomainList**). + - **relation-FlowDomain-ManagedEntity** to **Managed Entity** (role **#supportedByObjectList**). + - **Access Group** (Information Object Class, dotted box, multiplicity 0..\*) is associated with **Flow Point Pool Link** (role **#linkPointerList**) and **Flow Domain** (role **#containedInFlowDomainList**). + - **Connectionless Trail** (Information Object Class, multiplicity 0..1) is associated with **Flow Point Pool Link** (role **#clientLinkPointerList**). + - **Managed Entity** (Proxy Class, dotted box, multiplicity \*\*) is at the bottom, with a note: "\*\* Represent the IOCs that can be able to support the Flow Domain IOC." + - A note indicates: "Object classes shown in dotted outlines are found in other fragment". + +ER diagram of connectionless network fragment (part 1) showing various network-related object classes and their relationships. + +Figure 32 – ER diagram of connectionless network fragment (part 1) + +![ER diagram of the connectionless network (part 2)](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +classDiagram + class FlowDomainFragment { + <> + #outputFPList + #inputFPList + } + class ManagedEntity { + <> + } + class FlowPointPool { + <> + #flowPointList + } + class GenericTransportTTP { + <> + #clientFlowPointPoolList + #serverTTPPointer + } + class ConnectionlessPoint { + <> + #alarmSeverityAssignmentProfilePointer + } + class FlowPoint { + <> + #serverFTPPointer + } + class FlowDomain { + <> + #containedConnectionlessPointList + } + class AlarmSeverityAssignmentProfile { + <> + } + class FlowTerminationPoint { + <> + #clientFPList + } + class AccessGroup { + <> + #accessPointList + } + + FlowDomainFragment "0..1" -- "0..*" ConnectionlessPoint : relation-FlowDomainFragment-input_ConnectionlessPoint + FlowDomainFragment "0..1" -- "0..*" ConnectionlessPoint : relation-FlowDomainFragment-output_ConnectionlessPoint + ManagedEntity "0..*" -- "1..*" ConnectionlessPoint : relation-ConnectionlessPoint-ManagedEntity + FlowPointPool "0..*" -- "0..*" ManagedEntity : relation-FlowPointPool-ManagedEntity + FlowPointPool "0..1" -- "0..*" GenericTransportTTP : relation-FlowPointPool-GenericTransportTTP + FlowPointPool "0..1" -- "0..*" FlowPoint : relation-FlowPointPool-FlowPoint + ConnectionlessPoint "0..*" -- "0..1" FlowDomain : relation-FlowDomain-ConnectionlessPoint + ConnectionlessPoint "0..*" -- "0..1" AlarmSeverityAssignmentProfile : relation-ConnectionlessPoint-AlarmSeverityAssignmentProfile + FlowPoint "0..*" -- "0..*" FlowTerminationPoint : relation-FlowPoint-FlowTerminationPoint + FlowTerminationPoint "0..1" -- "0..*" AccessGroup : relation-AccessGroup-FlowTerminationPoint + +``` + +Notes in Figure 33: +\* include its subclasses +\*\* Represent the IOCs that can be able to support the Flow Domain IOC, or the Flow Point Pool IOC. +\*\* Can be an instance of Flow Point Sink, or Flow Point Source. +\*\* Can be an instance of Flow Termination Point Sink, or Flow Termination Point Source. +\* Includes its subclasses. Can be an instance of Flow Termination Point Source, Flow Termination Point Sink, Flow Point Source, Flow Point Sink. +Object classes shown in dotted outlines are found in other fragment. + +ER diagram of the connectionless network (part 2) + +**Figure 33 – ER diagram of the connectionless network (part 2)** + +![ER diagram of the connectionless network (part 3)](dcb5711d118ae6753b0e12f86eda37db_img.jpg) + +``` + +classDiagram + class ConnectionlessTrail { + <> + #aEndFTPList + #zEndFTPList + } + class FlowTerminationPointSource { + <> + #connectionlessTrailPointer + #downstreamFPPointer + } + class FlowTerminationPointSink { + <> + #connectionlessTrailPointer + #upstreamFPPointer + } + class FlowPointSource { + <> + #upstreamFPPointer + } + class FlowPointSink { + <> + #downstreamFPPointer + } + + ConnectionlessTrail "1" -- "1..*" FlowTerminationPointSource : relation-ConnectionlessTrail-FlowTerminationPointSource + ConnectionlessTrail "1" -- "1..*" FlowTerminationPointSink : relation-ConnectionlessTrail-FlowTerminationPointSink + FlowTerminationPointSource "0..*" -- "0..*" FlowTerminationPointSink : relation-FlowTerminationPointSource-FlowTerminationPointSink + FlowTerminationPointSource "0..*" -- "0..*" FlowPointSource : relation-FlowTerminationPointSource-FlowPointSource + FlowTerminationPointSink "0..*" -- "0..*" FlowPointSink : relation-FlowPointSink-FlowTerminationPointSink + FlowPointSource "0..*" -- "0..*" FlowPointSink : relation-FlowPointSink-FlowPointSource + +``` + +ER diagram of the connectionless network (part 3) + +**Figure 34 – ER diagram of the connectionless network (part 3)** + +### **7.2.3 Inheritance** + +#### **7.2.3.1 Network fragment** + +The inheritance diagrams of the network fragment are presented in Figures 35 and 36. + +![Inheritance diagram of network fragment (part 1)](dd5771673aececa53d42ece89218299d_img.jpg) + +This diagram shows the inheritance hierarchy for network-related information object classes. At the top is the base class **<> Top**. Below it, **<> Network** and **<> Sub Network** inherit from **Top**. Further down, **<> Layer Network Domain** inherits from **Network**. + +``` +graph BT; Network[<> Network] --|> Top[<> Top]; SubNetwork[<> Sub Network] --|> Top; LayerNetworkDomain[<> Layer Network Domain] --|> Network; +``` + +Inheritance diagram of network fragment (part 1) + +**Figure 35 – Inheritance diagram of network fragment (part 1)** + +![Inheritance diagram of network fragment (part 2)](7d2d1d3870cd224c4430d19334557716_img.jpg) + +This diagram shows a more complex inheritance hierarchy for network-related information object classes. At the top is the base class **<> Top**. Below it, eight classes inherit from **Top**: **Address**, **Cross-Coupling Site**, **Equipment Identity**, **Exchange**, **Association**, **Component Item**, **Equipment Item**, and **Location**. These are followed by **Position**, **Physical Link**, **Site Relationship**, and **Trail (M.1401)**. The next level includes **Port Item**, **Physical Link Connection**, **Termination**, and **Trail Multiplex Channel**. Finally, at the bottom, **Multipoint Trail** and **Trail Section** inherit from the classes above them. + +``` +graph BT; Address[<> Address] --|> Top[<> Top]; CrossCouplingSite[<> Cross-Coupling Site] --|> Top; EquipmentIdentity[<> Equipment Identity] --|> Top; Exchange[<> Exchange] --|> Top; Association[<> Association] --|> Top; ComponentItem[<> Component Item] --|> Top; EquipmentItem[<> Equipment Item] --|> Top; Location[<> Location] --|> Top; Position[<> Position] --|> Association; PhysicalLink[<> Physical Link] --|> ComponentItem; SiteRelationship[<> Site Relationship] --|> EquipmentItem; TrailM1401[<> Trail (M.1401)] --|> Location; PortItem[<> Port Item] --|> Position; PhysicalLinkConnection[<> Physical Link Connection] --|> PhysicalLink; Termination[<> Termination] --|> SiteRelationship; TrailMultiplexChannel[<> Trail Multiplex Channel] --|> TrailM1401; MultipointTrail[<> Multipoint Trail] --|> PortItem; TrailSection[<> Trail Section] --|> Termination; +``` + +Inheritance diagram of network fragment (part 2) + +**Figure 36 – Inheritance diagram of network fragment (part 2)** + +#### 7.2.3.2 Managed element fragment + +The inheritance diagram of the network element fragment is presented in Figure 37. + +![Inheritance diagram of managed element fragment](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) + +``` +classDiagram + class Top["<> Top"] + class ManagedElementComplex["<> Managed Element Complex"] + class ManagedElement["<> Managed Element"] + class Equipment["<> Equipment"] + Top <|-- ManagedElementComplex + Top <|-- ManagedElement + Top <|-- Equipment +``` + +The diagram shows a hierarchy of information object classes. At the top is a class labeled "<> Top". Below it, three classes are shown: "<> Managed Element Complex", "<> Managed Element", and "<> Equipment". Arrows with open triangle heads point from each of these three classes up to the "Top" class, indicating inheritance. + +Inheritance diagram of managed element fragment + +Figure 37 – Inheritance diagram of managed element fragment + +#### 7.2.3.3 Physical equipment fragment + +The inheritance diagram of the physical equipment fragment is presented in Figure 38. + +![Inheritance diagram of physical equipment fragment](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +``` +classDiagram + class Top["<> Top"] + class Equipment["<> Equipment"] + class EquipmentHolder["<> Equipment Holder"] + class CircuitPack["<> Circuit Pack"] + Top <|-- Equipment + Equipment <|-- EquipmentHolder + Equipment <|-- CircuitPack +``` + +The diagram shows a hierarchy of information object classes. At the top is a class labeled "<> Top". Below it is a class labeled "<> Equipment". Below that, two classes are shown: "<> Equipment Holder" and "<> Circuit Pack". Arrows with open triangle heads point from the "Equipment" class up to the "Top" class, and from both the "Equipment Holder" and "Circuit Pack" classes up to the "Equipment" class, indicating inheritance. + +Inheritance diagram of physical equipment fragment + +Figure 38 – Inheritance diagram of physical equipment fragment + +#### 7.2.3.4 Logical equipment fragment + +The inheritance diagram of the logical equipment fragment is presented in Figure 39. + +![Inheritance diagram of logical equipment fragment](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +``` +classDiagram + class Top["<> Top"] + class Software["<> Software"] + Top <|-- Software +``` + +The diagram shows a hierarchy of information object classes. At the top is a class labeled "<> Top". Below it is a class labeled "<> Software". An arrow with an open triangle head points from the "Software" class up to the "Top" class, indicating inheritance. + +Inheritance diagram of logical equipment fragment + +Figure 39 – Inheritance diagram of logical equipment fragment + +#### 7.2.3.5 Termination point fragment – Network element view + +The inheritance diagram of the termination point fragment for the element view is presented in Figure 40. + +![Inheritance diagram of termination point fragment – Network element view](14252bcd35912bd656e98b16b2ee51c0_img.jpg) + +``` +graph BT; CTPS[<> Connection Termination Point Source] --|> Top[<> Top]; TTPS[<> Trail Termination Point Source] --|> Top; CTSP[<> Connection Termination Point Sink] --|> CTPS; TTSP[<> Trail Termination Point Sink] --|> TTPS; CTPB[<> Connection Termination Point Bidirectional] --|> CTSP; TTPB[<> Trail Termination Point Bidirectional] --|> TTSP; CTSP --|> Top; TTSP --|> Top +``` + +The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it is 'Trail Termination Point', which inherits from 'Top'. Below 'Trail Termination Point' are 'Connection Termination Point Source' and 'Trail Termination Point Source', both of which inherit from 'Trail Termination Point'. Below 'Connection Termination Point Source' is 'Connection Termination Point Sink', which inherits from it. Below 'Trail Termination Point Source' is 'Trail Termination Point Sink', which inherits from it. Below 'Connection Termination Point Sink' is 'Connection Termination Point Bidirectional', which inherits from it. Below 'Trail Termination Point Sink' is 'Trail Termination Point Bidirectional', which inherits from it. Additionally, 'Connection Termination Point Sink' and 'Trail Termination Point Sink' both inherit directly from 'Top'. + +Inheritance diagram of termination point fragment – Network element view + +Figure 40 – Inheritance diagram of termination point fragment – Network element view + +#### 7.2.3.6 Termination point fragment – Network view + +The inheritance diagram of the termination point fragment for the network view is presented in Figure 41. + +![Inheritance diagram of termination point fragment – Network view](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +``` +graph BT; Top[<> Top] --|> TP[<> Termination Point]; TP --|> NTP[<> Network Termination Point]; NTP --|> NCTPSink[<> Network CTP Sink]; NTP --|> NCTPSource[<> Network CTP Source]; NTP --|> NTTPSink[<> Network TTP Sink]; NTP --|> NTTPSource[<> Network TTP Source]; NCTPBidirectional[<> Network CTP Bidirectional] --|> NCTPSink; NCTPBidirectional --|> NCTPSource; NTTPBidirectional[<> Network TTP Bidirectional] --|> NTTPSink; NTTPBidirectional --|> NTTPSource +``` + +The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it is 'Termination Point', which inherits from 'Top'. Below 'Termination Point' is 'Network Termination Point', which inherits from it. Below 'Network Termination Point' are four classes: 'Network CTP Sink', 'Network CTP Source', 'Network TTP Sink', and 'Network TTP Source', all of which inherit from 'Network Termination Point'. Below 'Network CTP Sink' and 'Network CTP Source' is 'Network CTP Bidirectional', which inherits from both. Below 'Network TTP Sink' and 'Network TTP Source' is 'Network TTP Bidirectional', which inherits from both. + +Inheritance diagram of termination point fragment – Network view + +Figure 41 – Inheritance diagram of termination point fragment – Network view + +#### 7.2.3.7 Topology and connectivity fragment – Network view + +The inheritance diagram of the topology and connectivity fragment is presented in Figure 42. + +![Inheritance diagram of topology and connectivity fragment](318886a86a1dcc59e1fc83db6f157c60_img.jpg) + +``` +graph BT + Top["<> +Top"] + AbstractLink["<> +Abstract Link"] + SubNetwork["<> +Sub Network"] + AccessGroup["<> +Access Group"] + Pipe["<> +Pipe"] + AbstractLinkEnd["<> +Abstract Link End"] + LogicalLink["<> +Logical Link"] + TopologicalLink["<> +Topological Link"] + SubNetworkConnection["<> +Sub Network Connection"] + LinkConnection["<> +Link Connection"] + LogicalLinkEnd["<> +Logical Link End"] + TopologicalLinkEnd["<> +Topological Link End"] + + AbstractLink --|> Top + SubNetwork --|> Top + AccessGroup --|> Top + Pipe --|> Top + LogicalLink --|> AbstractLink + TopologicalLink --|> AbstractLink + SubNetworkConnection --|> SubNetwork + LinkConnection --|> Pipe + LogicalLinkEnd --|> AbstractLinkEnd + TopologicalLinkEnd --|> AbstractLinkEnd + AbstractLinkEnd --|> TopologicalLink +``` + +The diagram shows the inheritance hierarchy for the topology and connectivity fragment. At the top is the **Top** class. Below it are four classes: **Abstract Link**, **Sub Network** (indicated with a dashed border), **Access Group** (indicated with a dashed border), and **Pipe**. **Abstract Link** is further specialized into **Logical Link** and **Topological Link**. **Sub Network** is specialized into **Sub Network Connection**. **Pipe** is specialized into **Link Connection**. There is also an **Abstract Link End** class which is a superclass for **Logical Link End** and **Topological Link End**, and it appears to inherit from or be associated with **Topological Link**. + +Inheritance diagram of topology and connectivity fragment + +Figure 42 – Inheritance diagram of topology and connectivity fragment + +#### 7.2.3.8 Telemetry fragment + +The inheritance diagram of the telemetry fragment is presented in Figure 43. + +![Inheritance diagram of telemetry fragment](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +``` +graph BT + Top["<> +Top"] + ExternalPoint["<> +External Point"] + ScanPoint["<> +Scan Point"] + ControlPoint["<> +Control Point"] + + ExternalPoint --|> Top + ScanPoint --|> ExternalPoint + ControlPoint --|> ExternalPoint +``` + +The diagram shows the inheritance hierarchy for the telemetry fragment. The **Top** class is the root. **External Point** inherits from **Top**. Both **Scan Point** and **Control Point** inherit from **External Point**. + +Inheritance diagram of telemetry fragment + +Figure 43 – Inheritance diagram of telemetry fragment + +#### 7.2.3.9 Transmission fragment + +The inheritance diagram of the transmission fragment is presented in Figure 44. + +![Inheritance diagram of transmission fragment showing Top, Pipe, Connection, and Trail classes.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +``` + +classDiagram + class Top["<> Top"] + class Pipe["<> Pipe"] + class Connection["<> Connection"] + class Trail["<> Trail"] + Pipe --|> Top + Connection --|> Pipe + Trail --|> Pipe + +``` + +Inheritance diagram of transmission fragment showing Top, Pipe, Connection, and Trail classes. + +**Figure 44 – Inheritance diagram of transmission fragment** + +#### **7.2.3.10 Cross-connection fragment** + +The inheritance diagram of the cross-connection fragment is presented in Figure 45. + +![Inheritance diagram of cross-connection fragment showing Top, Group Termination Point, Fabric, Termination Point Pool, Multipoint Cross Connection, and Cross Connection classes.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` + +classDiagram + class Top["<> Top"] + class GroupTerminationPoint["<> Group Termination Point"] + class Fabric["<> Fabric"] + class TerminationPointPool["<> Termination Point Pool"] + class MultipointCrossConnection["<> Multipoint Cross Connection"] + class CrossConnection["<> Cross Connection"] + Top <|-- GroupTerminationPoint + Top <|-- Fabric + Top <|-- TerminationPointPool + GroupTerminationPoint <|-- MultipointCrossConnection + Fabric <|-- CrossConnection + +``` + +Inheritance diagram of cross-connection fragment showing Top, Group Termination Point, Fabric, Termination Point Pool, Multipoint Cross Connection, and Cross Connection classes. + +**Figure 45 – Inheritance diagram of cross-connection fragment** + +#### **7.2.3.11 Organization fragment** + +The inheritance diagram of the organization fragment is presented in Figure 46. + +![Inheritance diagram of organization fragment showing Top, Geographical Area, Operator, and Country classes.](836b0790cef5469a167fa8931df4e408_img.jpg) + +``` + +classDiagram + class Top["<> Top"] + class GeographicalArea["<> Geographical Area"] + class Operator["<> Operator"] + class Country["<> Country"] + Top <|-- GeographicalArea + Top <|-- Operator + Top <|-- Country + +``` + +Inheritance diagram of organization fragment showing Top, Geographical Area, Operator, and Country classes. + +**Figure 46 – Inheritance diagram of organization fragment** + +#### **7.2.3.12 Connectionless network fragment** + +The inheritance diagrams of the connectionless network fragment are presented in Figures 47 and 48. + +![Inheritance diagram for connectionless network fragment (part 1) - Network view. The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it are three classes: 'Connectionless Trail', 'Flow Point Pool', and 'Flow Point Pool Link'. Below 'Connectionless Trail' is 'Flow Domain'. Below 'Flow Point Pool' is 'Flow Domain Fragment'.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` + +classDiagram + class Top + class ConnectionlessTrail["<> Connectionless Trail"] + class FlowPointPool["<> Flow Point Pool"] + class FlowPointPoolLink["<> Flow Point Pool Link"] + class FlowDomain["<> Flow Domain"] + class FlowDomainFragment["<> Flow Domain Fragment"] + + Top <|-- ConnectionlessTrail + Top <|-- FlowPointPool + Top <|-- FlowPointPoolLink + ConnectionlessTrail <|-- FlowDomain + FlowPointPool <|-- FlowDomainFragment + +``` + +Inheritance diagram for connectionless network fragment (part 1) - Network view. The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it are three classes: 'Connectionless Trail', 'Flow Point Pool', and 'Flow Point Pool Link'. Below 'Connectionless Trail' is 'Flow Domain'. Below 'Flow Point Pool' is 'Flow Domain Fragment'. + +**Figure 47 – Inheritance diagram of connectionless network fragment (part 1) – Network view** + +![Inheritance diagram for connectionless network fragment (part 2) - NE view. The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it is 'Connectionless Point'. Below 'Connectionless Point' are 'Flow Point Source' and 'Flow Termination Point Source'. Below 'Flow Point Source' is 'Flow Point Sink'. Below 'Flow Termination Point Source' is 'Flow Termination Point Sink'.](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) + +``` + +classDiagram + class Top + class ConnectionlessPoint["<> Connectionless Point"] + class FlowPointSource["<> Flow Point Source"] + class FlowTerminationPointSource["<> Flow Termination Point Source"] + class FlowPointSink["<> Flow Point Sink"] + class FlowTerminationPointSink["<> Flow Termination Point Sink"] + + Top <|-- ConnectionlessPoint + ConnectionlessPoint <|-- FlowPointSource + ConnectionlessPoint <|-- FlowTerminationPointSource + FlowPointSource <|-- FlowPointSink + FlowTerminationPointSource <|-- FlowTerminationPointSink + +``` + +Inheritance diagram for connectionless network fragment (part 2) - NE view. The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it is 'Connectionless Point'. Below 'Connectionless Point' are 'Flow Point Source' and 'Flow Termination Point Source'. Below 'Flow Point Source' is 'Flow Point Sink'. Below 'Flow Termination Point Source' is 'Flow Termination Point Sink'. + +**Figure 48 – Inheritance diagram of connectionless network fragment (part 2) – NE view** + +#### 7.2.3.13 Common objects fragment + +The inheritance diagram of the common information objects fragment is presented in Figure 49. + +![Inheritance diagram for common information objects fragment. The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it are 'Agent' and 'Generic Interface'. Below 'Generic Interface' is 'Generic Managed Interface'.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +``` + +classDiagram + class Top + class Agent + class GenericInterface["<> Generic Interface"] + class GenericManagedInterface["<> Generic Managed Interface"] + + Top <|-- Agent + Top <|-- GenericInterface + GenericInterface <|-- GenericManagedInterface + +``` + +Inheritance diagram for common information objects fragment. The diagram shows a hierarchy of information object classes. At the top is 'Top'. Below it are 'Agent' and 'Generic Interface'. Below 'Generic Interface' is 'Generic Managed Interface'. + +**Figure 49 – Inheritance diagram of common information objects fragment** + +## 7.3 Information object class definitions + +### 7.3.1 Abstract Link + +#### 7.3.1.1 Definition + +The abstract link IOC gives a topological description of the capacity between two adjacent Subnetworks, or two Link Ends; or a Subnetwork and an Access Group when Network trail termination points lie outside the boundary of the largest subnetwork. + +#### 7.3.1.2 Attributes + +Table 1 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEnd | M | M | – | M | | +| availableLinkCapacity | M | M | – | – | | +| signalId | M | M | – | M | | +| usageCost | O | M | – | – | | +| userLabel | O | M | M | M | | +| zEnd | M | M | – | M | | + +#### 7.3.1.3 Notifications + +Table 2 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.2 Abstract Link End + +#### 7.3.2.1 Definition + +The Abstract Link End IOC is a class of managed objects which contains Network Connection Termination Points for the purpose of representing topology. The use made of individual attributes and notification is detailed below: + +- available link end capacity: represents the spare capacity of the link end; +- link pointer: is a distinguished name of the related link managed object instance; +- contained in subnetwork list: is a distinguished name that represents the parent subnetwork of the logical link. + +An attribute value change notification shall be emitted when the value of the availableLinkEndCapacity or the containedInSubNetworkList is changed. + +#### 7.3.2.2 Attributes + +Table 3 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------|-------------------|----------------|-----------------|------------------|------------------| +| availableLinkEndCapacity | M | M | – | – | | +| containedInSubNetworkList | O | M | M | M | | +| linkPointer | M | M | – | – | | +| signalId | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.2.3 Notifications + +Table 4 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.3 Access Group + +#### 7.3.3.1 Definition + +The Access Group IOC is a class of objects which groups Network Trail Termination Points of connection-oriented networks, or Flow Termination Points of connectionless network, for management purposes. + +#### 7.3.3.2 Attributes + +Table 5 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| accessGroupId | M | M | – | – | | +| accessPointList | M | M | M | M | | +| containedInSubNetworkList | O | M | M | M | | +| containedInFlowDomainList | O | M | M | M | | +| linkPointerList | O | M | – | – | | +| signalId | M | M | – | – | | +| topologicalEndDirectionality | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.3.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.4 Account + +#### 7.3.4.1 Definition + +The Account IOC is a class of objects that provides information on agreed and delivered payments from a Customer. + +#### 7.3.4.2 Attributes + +Table 6 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------|-------------------|----------------|-----------------|------------------|------------------| +| accountContactList | O | M | M | M | | +| accountName | M | M | – | – | | +| additionalText | M | M | M | M | | +| contactObjectPtrList | O | M | M | M | | + +#### 7.3.4.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.5 Address + +#### 7.3.5.1 Definition + +An Address identifies a geographic location, which may contain a Cross-coupling site. + +#### 7.3.5.2 Attributes + +Table 7 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| siteList | M | M | – | – | | + +Table 8 + +| Name | Type | Description | +|----------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| siteList | LIST of ObjectInstance | An Address' subordinate Site is a role of a Cross-coupling site that is placed at the Address.
An Address may have several Sites. | + +#### 7.3.5.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.6 Agent + +For further study. + +### 7.3.7 Alarm Severity Assignment Profile + +#### 7.3.7.1 Definition + +The alarm severity assignment profile IOC is a class of management support object that specifies the alarm severity assignment for managed objects. + +#### 7.3.7.2 Attributes + +Table 9 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| alarmSeverityAssignmentList | M | M | M | M | | +| alarmSeverityAssignmentProfileId | M | M | – | M | | + +#### 7.3.7.3 Notifications + +Table 10 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | + +### 7.3.8 Alarm reporting control (ARC) interval profile + +#### 7.3.8.1 Definition + +This IOC defines the default alarm reporting control (ARC) intervals for the ARC states that support time-based transitions. An interval profile is only applicable for ARC states that automatically transition within an agent with time being a factor (but not necessarily the only factor) in the transition criteria from a mode of inhibited alarm reporting to a mode of allowed alarm reporting. Automatic agent state transitions from a mode of allowed alarm reporting to a mode of inhibited alarm reporting is prohibited. Support for this object is required only when settable intervals for the related ARC states are required. + +#### 7.3.8.2 Attributes + +Table 11 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------|-------------------|----------------|-----------------|------------------|------------------| +| arcDefaultNALMCDInterval | M | M | M | M | | +| arcDefaultNALMTIInterval | M | M | M | M | | +| arcIntervalProfileId | M | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.8.3 Notifications + +Table 12 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | + +### 7.3.9 Association + +#### 7.3.9.1 Definition + +An Association defines an ordered or unordered relationship between a Trail and some other Trails. The ordering is indicated by the Superior trail reference. + +#### 7.3.9.2 Attributes + +Table 13 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| kind | M | M | – | – | | +| superiorTrail | O | M | – | – | | +| trailList | M | M | – | – | | + +Table 14 + +| Name | Type | Description | +|---------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| kind | Kind ::= STRING (SIZE(2)) | Kind indicates the usage of the Association. Kind is a 2-character field, adjusted to the left. S indicates reserve. In this case, Superior trail indicates the main trail, and Trail indicates the reserve trail. | +| superiorTrail | PointerOrNull | An Association's subordinate Superior trail is a role of a Trail that controls the Association. In case of an ordered relationship, the Association will have one and only one Superior trail. In case of an unordered relationship, the Association will have no Superior trail. | +| trailList | LIST of ObjectInstance | An Association's subordinate Trail is a role of a Trail being controlled by the Association. An Association must have one or more Trails. In case of an unordered relationship, the Association will have two or more Trails. | + +#### 7.3.9.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.10 Attribute Ranges + +#### 7.3.10.1 Definition + +The Attribute Ranges IOC allows the managed system to report the minimum and maximum values accepted by a certain attribute, as well as the granularity, or step increments, of the range. + +Each Attribute Ranges instance contains ranges for attributes belonging to one IOC. + +For each ManagedElement instance representing a network element, one or more Attribute Ranges instances may be created. Ranges are defined per ManagedElement instance. This allows for an attribute to have different ranges when it belongs to different network elements. + +#### 7.3.10.2 Attributes + +Table 15 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-------------------|-------------------|----------------|-----------------|------------------|------------------| +| attributeRangesId | M | M | – | – | | +| kind | M | M | – | – | | +| ranges | M | M | – | – | | + +#### 7.3.10.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.11 Circuit end point subgroup + +#### 7.3.11.1 Definition + +A set of circuit end points that directly interconnects one exchange with another, having common values for the attributes listed in this package. Note that the term exchange includes PBX where applicable. + +Annex A of [ITU-T E.410] contains additional information on circuit subgroup. + +#### 7.3.11.2 Attributes + +Table 16 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| circuitDirectionality | M | M | – | – | | +| circuitEndPointSubgroupId | M | M | – | – | | +| informationTransferCapabilities | M | M | – | – | | +| labelOfFarEndExchange | M | M | – | – | | +| numberOfCircuits | M | M | – | – | | +| signallingCapabilities | M | M | – | – | | +| transmissionCharacteristics | M | M | – | – | | +| userLabel | M | M | M | M | | + +#### 7.3.11.3 Notifications + +Table 17 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.12 Circuit Pack + +#### 7.3.12.1 Definition + +The Circuit Pack IOC is a class of objects that represents a plug-in replaceable unit that can be inserted into or removed from the equipment holder of the network element. + +Examples of plug-in cards include: + +- line cards +- processors +- power supply units + +The textType attribute (inherited from equipment) is used to indicate the type of the circuit pack. The value of this attribute should match one of the values of the acceptableCircuitPackTypeList attribute of the containing EquipmentHolder object. + +The Circuit Pack may contain additional Circuit Pack objects. + +#### 7.3.12.2 Attributes + +**Table 18** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| acceptableCircuitPackTypeList | O | M | M | M | | +| administrativeState | M | M | M | M | | +| affectedObjectList | O | M | – | – | | +| alarmSeverityAssignmentProfilePointer | M | M | M | M | | +| alarmStatus | M | M | – | – | | +| availabilityStatus | M | M | – | – | | +| availableSignalRateList | O | M | – | – | | +| currentProblemList | M | M | – | – | | +| equipmentId | M | M | – | M | | +| locationName | O | M | M | M | | +| numberOfPorts | O | M | – | – | | +| operationalState | M | M | – | – | | +| replaceable | M | M | – | M | | +| portAssociations | O | M | – | – | | +| portSignalRateAndMappingList | O | M | M | M | | +| serialNumber | M | M | – | – | | +| supportedByObjectList | M | M | M | M | | +| typeText | M | M | – | M | | +| userLabel | O | M | M | M | | +| vendorName | O | M | M | M | | +| version | O | M | M | M | | + +#### 7.3.12.3 Notifications + +**Table 19** + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| environmentalAlarm | O | | +| equipmentAlarm | M | | +| objectCreation | M | | +| objectDeletion | M | | +| processingErrorAlarm | O | | +| stateChange | M | | + +### 7.3.13 Component Item + +#### 7.3.13.1 Definition + +A Component item is a separate unit, e.g., a circuit card, within an Equipment item. A Component item has a specified Location, and a Component item has one or more Port items, which may provide inputs, outputs or both. + +#### 7.3.13.2 Attributes + +**Table 20** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| uniqueItemIdentification | M | M | – | – | | +| equipmentIdentity | M | M | – | – | | +| location | M | M | – | – | | + +**Table 21** + +| Name | Type | Description | +|--------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | STRING | A Component item is assigned a unique Identifier within the scope of the superior Equipment item. | +| uniqueItemIdentification | STRING | The manufacturer may assign a Unique item identification (UID) to a Component item. | +| equipmentIdentity | ObjectInstance | A Component item's subordinate Equipment identity is a role of an Equipment identity to which the Component item belongs. | +| location | ObjectInstance | A Component item's subordinate Location is a role of a Location subordinate to the Location of the Equipment item containing the Component item. Each Component item shall be assigned exactly one Location placement where the Component item can be found. | + +#### 7.3.13.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.14 Connection + +#### 7.3.14.1 Definition + +The Connection IOC is a class of objects responsible for the transparent transfer of information between connection termination points. A connection is a component of a trail. Several connections can be bundled into a higher rate trail. A sequence of one or more connections are linked together to form a trail. A connection may be either uni- or bidirectional. + +#### 7.3.14.2 Attributes + +Table 22 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| a-TPInstance | M | M | – | M | | +| administrativeState | M | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientTrail | O | M | – | M | | +| connectionId | M | M | – | M | | +| currentProblemList | O | M | – | – | | +| directionality | M | M | – | – | | +| operationalState | M | M | – | – | | +| protected | O | M | – | M | | +| serverTrailList | O | M | – | M | | +| userLabel | O | M | M | M | | +| z-TPInstance | M | M | – | M | | + +#### 7.3.14.3 Notifications + +Table 23 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.15 Connectionless Point + +#### 7.3.15.1 Definition + +The Connectionless Point IOC represents the termination of a transport entity, such as an instance representing a Connectionless Trail or a Flow Domain Fragment. Connectionless Point is the base class of Flow Point Source/Sink and Flow Termination Point Source/Sink. Connectionless Point is an abstract IOC used for inheritance purpose, and should not be instantiated. Connectionless Point provides a combined view of network level and network element level for the abstraction of commonalities of flow points. + +#### 7.3.15.2 Attributes + +Table 24 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| locationName | O | M | M | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| supportedByObjectList | M | M | – | M | | +| signalId | M | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.15.3 Notifications + +Table 25 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.16 Connectionless Trail + +#### 7.3.16.1 Definition + +Connectionless Trail represents the transfer of monitored adapted characteristic information of the client layer network between flow termination points. It is delimited by two flow termination points, one at each end of the connectionless trail. It represents the association between a source and destination on a per traffic unit or datagram basis. A connectionless trail is formed by associating flow terminations with a traffic unit or datagram. The aEndFTP attribute points to the instance of Flow Termination Point Source which sends the characteristic information, and the zEndFTP attribute Points to the instance of Flow Termination Point Sink which receives the characteristic information. A Connectionless Trail can only be unidirectional from the source to the sink. + +#### 7.3.16.2 Attributes + +Table 26 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| aEndFTPList | M | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| clientLinkPointerList | O | M | – | – | | +| connectionlessTrailId | M | M | – | M | | +| currentProblemList | O | M | – | – | | +| operationalState | O | M | – | – | | +| userLabel | O | M | M | M | | +| signalId | M | M | – | M | | +| supportedByObjectList | O | M | M | M | | +| trafficDescriptor | O | M | M | M | | +| zEndFTPList | M | M | M | M | | + +#### 7.3.16.3 Notifications + +Table 27 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| communicationsAlarm | O | | +| stateChange | O | | + +### 7.3.17 Connection Termination Point Bidirectional + +#### 7.3.17.1 Definition + +This IOC represents a termination point where a trail is both originated and terminated, i.e., the combined behaviour of the Connection Termination Point Sink and the Connection Termination Point Source object classes. + +#### 7.3.17.2 Attributes + +Table 28 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| cTPId | O | M | – | M | | +| channelNumber | O | M | – | M | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| downstreamConnectivityPointer | M | M | – | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| upstreamConnectivityPointer | M | M | – | M | | + +#### 7.3.17.3 Notifications + +Table 29 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.18 Connection Termination Point Sink + +#### 7.3.18.1 Definition + +This IOC terminates a link connection. The downstream connectivity pointer attribute points to the termination point managed object, within the same managed element, that receives information (traffic) from this termination point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Trail Termination Point Sink, Trail Termination Point Bidirectional, Connection Termination Point Source, Connection Termination Point Bidirectional. The downstream connectivity pointer may identify one or more objects depending on whether the signal is connected to one or more termination point objects. + +#### 7.3.18.2 Attributes + +Table 30 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| cTPId | O | M | – | M | | +| channelNumber | O | M | – | M | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| downstreamConnectivityPointer | M | M | – | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | + +#### 7.3.18.3 Notifications + +Table 31 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.19 Connection Termination Point Source + +#### 7.3.19.1 Definition + +This IOC originates a link connection. The upstream connectivity pointer attribute points to the termination point managed object, within the same managed element, that sends information (traffic) to this termination point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Trail Termination Point Source, Trail Termination Point Bidirectional, Connection Termination Point Sink, Connection Termination Point Bidirectional. + +#### 7.3.19.2 Attributes + +Table 32 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| cTPId | O | M | – | M | | +| channelNumber | O | M | – | M | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| upstreamConnectivityPointer | M | M | – | M | | + +#### 7.3.19.3 Notifications + +Table 33 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.20 Control Point + +#### 7.3.20.1 Definition + +This IOC is used to control external devices associated with the managed system, such as relay closure for bell, lamp, generator, heater, or air conditioner. Each instance of this class represents one control point. + +The current state of a control point can be either closed (i.e., activate) or open (i.e., released). A control point may optionally have a normal state (i.e., closed or open, one or the other). + +The external device represented by a control point can be remotely operated through the 'control' action. A control operation can be momentary (i.e., momentarily close or open) or continuous (continuously close or open). + +Valid control type of a control point may be momentary only, continuous only, or both. A control action will be denied if the control action type (continuous or momentary) is not valid for the control point. + +### 7.3.21 Contact + +#### 7.3.21.1 Definition + +This IOC refers to a person or organization having responsibility for one or more managed object instances. + +Attributes whose values are names of other managed object instances (e.g., locationPointer) must have names of managed objects which actually exist. + +The attributeValueChange notification is emitted when any of the following attributes change in value: contactDetails and telephoneNumberList. All attributeValueChange notifications shall include the Attribute Identifier List parameter. Conditions under which an attributeValueChange notification is emitted are stated in the behaviour of the appropriate package or attribute. In the absence of such a statement in the behaviour, the attribute does not cause an attributeValueChange notification to be emitted. + +A value for the contactID attribute can only be provided when the object is created. Furthermore, once the object is created, the value of contactID may not be modified (i.e., the instance cannot be renamed). The contact object is created locally by the agent. + +#### 7.3.21.2 Attributes + +Table 34 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| contactDetails | M | M | M | M | | +| contactCompany | O | M | M | M | | +| contactFunction | O | M | M | M | | +| contactID | M | M | – | M | | +| contactNames | O | M | M | M | | +| contactType | O | M | M | M | | +| electronicMailAddress | O | M | M | M | | +| facsimileTelephoneNumberList | O | M | M | M | | +| locationName | O | M | M | M | | +| telephoneNumberList | M | M | M | M | | +| typeText | O | M | M | M | | +| userLabel | O | M | M | M | | + +#### 7.3.21.3 Notifications + +Table 35 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.22 Country + +#### 7.3.22.1 Definition + +A Country with its Name and Country Code as defined in [ISO 3166-1]. + +#### 7.3.22.2 Attributes + +**Table 36** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| code | M | M | – | – | | +| name | O | M | M | M | | + +**Table 37** + +| Name | Type | Description | +|------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| code | STRING (SIZE(3)) | The Country Code is a 3-character globally unique code that identifies each Country according to [ISO 3166-1]. | +| name | STRING | The Country Name identifies a Country, dependency, or other area of particular geopolitical interest. Countries are assigned a globally unique Name in [ISO 3166-1]. | + +#### 7.3.22.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.23 Cross-connection + +#### 7.3.23.1 Definition + +A managed object of this class represents an assignment relationship between the termination point or GTP object listed in the From Termination attribute and the termination point or GTP objects listed in the To Termination attribute of this managed object: + +- The To Termination attribute will always be non-NULL. +- The From Termination attribute will only be NULL in the case of point-to-multipoint configurations. + +If the From Termination attribute has a value of NULL, the assignment relationship is between the termination point object or the GTP object listed in the From Termination attribute of the containing Multipoint Cross-Connection managed object and the termination point object or GTP object listed in the To Termination attribute of this managed object. + +A point-to-point cross-connection can be established between: one of CTP Sink, CTP Bidirectional, TTP Source, TTP Bidirectional, or GTP; and one of CTP Source, CTP Bidirectional, TTP Sink, TTP Bidirectional, or GTP. + +In a unidirectional cross-connection, the termination or GTP object pointed to by the From Termination and the termination point or GTP object pointed to by the To Termination attribute (in this object or the containing mpCrossConnection) are related in such a way that traffic can flow between the termination points represented by these managed objects. In a bidirectional cross-connection, information flows in both directions. + +If the objects listed in the From Termination and To Termination attributes are GTPs, the nth element of the From Termination GTP is related to the nth element of the To Termination GTP (for every n). + +If the fromTermination attribute has a value of NULL, the directionality attribute must have the value 'unidirectional'. + +The total rate of the From Terminations must be equal to the total rate of To Terminations. + +The attribute Signal Type describes the signal that is cross-connected, and the termination points or GTPs that are cross-connected must have signal types that are compatible. + +If an instance of this object class is contained in a multipoint cross-connection and the operational state of the containing multipoint cross-connection is 'disabled', the operational state of this object will also be 'disabled'. + +The following are the definitions of the administrative state and the operational state attributes: + +Administrative State: + +- Unlocked: The Cross-Connection object is administratively unlocked. Traffic is allowed to pass through the connection. +- Locked: No traffic is allowed to pass through the Cross-Connection. + +Operational State: + +- Enabled: The Cross-Connection is performing its normal function. +- Disabled: The Cross-Connection is incapable of performing its normal cross-connection function. + +#### 7.3.23.2 Attributes + +Table 38 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| crossConnectionId | M | M | – | – | | +| directionality | M | M | – | – | | +| fromTermination | M | M | – | – | | +| operationalState | M | M | – | – | | +| redline | O | M | M | M | | +| signalType | M | M | – | – | | +| toTermination | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.23.3 Notifications + +Table 39 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.24 Cross-Coupling Site + +#### 7.3.24.1 Definition + +The Cross-coupling site allows termination of a Trail, e.g., in an exchange, at a subscriber's premises or other. In case of termination of the Trail, e.g., at the subscriber's premises or in an international transmission centre, the Operator's network is considered to exist at one side of the Cross-coupling site only, i.e., the Operator's network may not include the connection between the Cross-coupling site and the customer's equipment. + +The Cross-coupling site allows cross-couplings to route a Trail through that node, and the Cross-coupling site allows cross-couplings between Trails within that Cross-coupling site. The cross-coupling may use internal equipment, termination points and internal Trails which are associated to the routed Trail. + +The cross-couplings may be provided by automated management, e.g., in digital cross-connect or SDH network matrixes, or the cross-connect can be made manually as in a fibre matrix. However, a Cross-coupling site typically may contain more than a single piece of such Equipment items, and the individual Equipment item should not be registered as a Cross-coupling site. + +A Cross-coupling site can be a transmission station, a radio station, a base station, an earth station, a distribution frame, or a junction box, which, as a special case, can be an end junction box. + +A control station or sub-control station can be registered as a Cross-coupling site even if it may not provide for cross-couplings within that site. + +A Cross-coupling site cannot be geographically distributed over more than one building. However, it is also permissible to define several Cross-coupling sites at the same Address. In this case, separate Trails and other resources shall be defined to route Trails between these Cross-coupling sites at the same Address. + +A cross-coupling within a Cross-coupling site is typically made on the basis of a cross-coupling or routing order. Hence, the cross-couplings are considered to be semi-permanent. Junctions which contain permanent cross-couplings or permanently installed equipment are not Cross-coupling sites. Note that this permanently installed equipment outside Cross-coupling sites may still be subject to automatic surveillance by management functions. + +A Cross-coupling site may contain one or more Exchanges, concentrators, routers and other equipment. + +Cross-Coupling Sites of different Operators, e.g., in the same room, shall be defined as separate Cross-Coupling Sites. However, if the place is managed by one Operator only, the place should be defined as one Cross-Coupling Site locally to that Operator. The other Operator's Equipment items, Exchanges and Locations shall then be identified locally to this Operator's Cross-Coupling Site. Hence, registration of ownership of Equipment items is distinguished from naming of the Equipment items within the Cross-Coupling Site. + +Aliases of Cross-Coupling Site identifiers are not permitted for communication between Operators of different Countries. However, Operators may exchange localIdentifiers that are local to a specific Operator, country or region. + +Note that some Operators may use the Geographical Area name or an abbreviation for this, as a part of the Cross-Coupling Site identifier or for some of their Cross-Coupling Site Identifiers, while other Operators may not. Use of Geographical Area names may be useful for international Trails terminating in Geographical Areas, but may not be appropriate for Trails terminating in rural areas or even for local terminations in a Geographical Area. The name of the GeographicalArea, if any, will additionally be provided in the Cross-Coupling Site's subordinate Address. + +An Operator is not required to limit the uniqueness of a siteDetail designation to a GeographicalArea or Operator, e.g., it could be globally unique. + +Use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400]. + +#### 7.3.24.2 Attributes + +**Table 40** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| identifier | M | M | – | – | | +| localIdentifier | M | M | – | – | | +| address | M | M | M | – | | +| a-EndSiteRelationshipList | M | M | M | – | | +| b-EndSiteRelationshipList | M | M | M | – | | +| currentOperator | M | M | M | – | | +| geographicalArea | M | M | M | – | | +| terminationList | M | M | M | – | | + +**Table 41** + +| Name | Type | Description | +|---------------------------|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | Cross-CouplingSiteIdentifier ::= SEQUENCE {
geographicalArea String,
siteDetail String
} |

The Identifier uniquely identifies the Cross-coupling site within the scope of an Operator. Cross-coupling sites of different Operators, e.g., in the same room, shall be defined as separate Cross-coupling sites. However, if the place is managed by one Operator only, the place should be defined as one Cross-coupling site locally to that Operator. The other Operator's Equipment items, Exchanges and Locations shall then be identified locally to this Operator's Cross-coupling site. Hence, registration of ownership of Equipment items is distinguished from naming of the Equipment items within the Cross-coupling site.

Aliases of Cross-coupling site Identifiers are not permitted for communication between Operators of different Countries. However, Operators may exchange Local identifiers that are local to a specific Operator, country or region.

Note that some Operators may use the name of the Geographical area, or an abbreviation for this, as a part of the Cross-coupling site Identifier or for some of their Cross-coupling site Identifiers, while other Operators may not. The name of the Geographical area, if any, will additionally be provided in the Cross-coupling site's subordinate Address.

The identifier contains the following two fields:

  • – geographicalArea : The Name of the Geographical area being referenced in the Cross-coupling site's subordinate Geographical area. See field length and use of characters in this Name.
  • – siteDetail : An identifier of the Cross-coupling site that is at least unique within a Geographical area and an Operator. This requirement does not prohibit that someone choose to make the identifier independent of Geographical area or Operator. The identifier has up to six characters. Symbols that may be included are hyphen (-), underscore (_) and space ( ).
| +| localIdentifier | LocalIdentifier ::= String (SIZE (18)) |

An identifier of the Cross-coupling site that is unique within an Operator, having up to 18 alphabetic and/or numeric characters. A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400].

| +| address | ObjectInstance |

A Cross-coupling site's subordinate Address is a role of an Address denoting a geographical location. A Cross-coupling site has one Address only, which is the physical location address of the Cross-coupling site.

Note that the Cross-coupling site's subordinate Exchanges, Locations and Equipment items do not have separate references to Addresses, but their detailed addresses may be provided in address notes.

| +| a-EndSiteRelationshipList | SEQUENCE OF ObjectInstance |

A Cross-coupling site's A-end site relationship is a role of a Site relationship, of which the Cross-coupling site is referenced as an A-end site. A Cross-coupling site may have multiple A-end site relationships.

| + +**Table 41** + +| Name | Type | Description | +|---------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| b-EndSiteRelationshipList | SEQUENCE OF
ObjectInstance | A Cross-coupling site's B-end site relationship is a role of a Site relationship, of which the Cross-coupling site is referenced as a B-end site. A Cross-coupling site may have multiple B-end site relationships. | +| currentOperator | ObjectInstance | A Cross-coupling site's subordinate Current operator is a role of an Operator who is currently responsible for the Cross-coupling site. A Cross-coupling site may have one Current operator only. If the Current operator deviates from the superior Operator of the Cross-coupling site, it has to be explicitly provided. | +| geographicalArea | ObjectInstance | A Cross-coupling site's subordinate Geographical area is a role of a Geographical area subordinate to Country. The Name of this Geographical area is used as a part of the Cross-coupling site Identifier. | +| terminationList | SEQUENCE OF
ObjectInstance | A Cross-coupling site's subordinate Termination is a role of a Trail's subordinate Termination. A Trail may have two Terminations, and a Cross-coupling site may have one or two Terminations for each Trail. | + +#### 7.3.24.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.25 Current Alarm Summary Control + +#### 7.3.25.1 Definition + +The Current Alarm Summary Control IOC is a class of support objects that provide the criteria for generation of current alarm summary reports. An object is included in a current alarm summary report if: + +- the object is included in the Object List (if the list is non-empty); +- the object has an Alarm Status that is present in the Alarm Status List (if the list is non-empty); +- the object has an alarm (or potential alarm) with a Perceived Severity and Probable Cause matching members of the Perceived Severity List (if non-empty) and Probable Cause List (if non-empty), respectively. + +If the Object List is empty, then the criteria in the Current Alarm Summary Control are applied to all objects in the Managed System. If any of the other criteria are empty, then they are not used in selecting objects that will appear in the current alarm summary report. + +A single object may appear in a report multiple times if it has multiple outstanding alarm conditions that match the Perceived Severity List and Probable Cause List criteria. + +The semantics of associated attributes are as follows: + +##### a) *Alarm Status List* + +The Alarm Status List attribute type describes criteria for inclusion in a current alarm summary report. The Alarm Status List consists of a set of possible Alarm Status. In order to be included in a current alarm summary report, an object shall have an Alarm Status that matches one of the states in the Alarm Status List. + +If the Alarm Status List has a null value, the Alarm Status of the objects in the Object List is not used as a criterion for inclusion in the current alarm summary report. + +##### b) *Object List* + +The Object List attribute type describes a set of object instances. + +##### c) *Perceived Severity List* + +The Perceived Severity List attribute type describes criteria for inclusion in a current alarm summary report. It consists of a set of possible Perceived Severities. In order to be included in a current alarm summary report, an object must have an outstanding alarm (or potential alarm) that has a Perceived Severity that matches one of the elements in the Perceived Severity List. + +If the Perceived Severity List has a null value, the Perceived Severity of the objects in the object list is not used as a criterion for inclusion in the current alarm summary report. + +##### d) *Probable Cause List* + +The Probable Cause List attribute type describes criteria for inclusion in a current alarm summary report, consisting of a set of possible Probable Causes. In order to be included in a current alarm summary report, an object must have an outstanding alarm (or potential alarm) that has a Probable Cause that matches one of the elements in the Probable Cause List. + +If the Probable Cause List has a null value, the Probable Cause of the objects in the object list is not used as a criterion for inclusion in the current alarm summary report. + +#### 7.3.25.2 Attributes + +Table 42 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| alarmStatusList | M | M | M | M | | +| currentAlarmSummaryControlId | M | M | – | – | | +| objectList | M | M | M | M | | +| perceivedSeverityList | M | M | M | M | | +| probableCauseList | M | M | M | M | | + +#### 7.3.25.3 Notifications + +Table 43 + +| Name | Qualifier | Notes | +|---------------------------|-----------|-------| +| currentAlarmSummaryReport | M | | + +### 7.3.26 Equipment + +#### 7.3.26.1 Definition + +The equipment IOC is a class of managed objects that represent physical components of a managed element, including replaceable components. An instance of this object class is present in a single geographic location. An equipment may be nested within another equipment, thereby creating a containment relationship. + +#### 7.3.26.2 Attributes + +Table 44 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| affectedObjectList | O | M | – | – | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| equipmentId | M | M | – | M | | +| locationName | O | M | M | M | | +| operationalState | O | M | – | – | | +| replaceable | M | M | – | M | | +| serialNumber | M | M | – | – | | +| supportedByObjectList | M | M | M | M | | +| typeText | M | M | – | M | | +| userLabel | O | M | M | M | | +| vendorName | O | M | M | M | | +| version | O | M | M | M | | + +#### 7.3.26.3 Notifications + +Table 45 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| environmentalAlarm | O | | +| equipmentAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| processingErrorAlarm | O | | +| stateChange | O | | + +### 7.3.27 Equipment Identity + +#### 7.3.27.1 Definition + +A category of equipment instances that may be characterized by a combination of: + +- manufacturer name; +- manufacturer part number; +- manufacturer equipment version number; +- equipment category number; +- substitutability (upward/downward compatible replacement). + +An Equipment identity may categorize a set of Equipment items, Component items, Port items, or Locations, but an Equipment identity cannot categorize items belonging to more than one of these classes simultaneously. + +#### 7.3.27.2 Attributes + +Table 46 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| componentItemList | M | M | – | – | | +| equipmentItemList | M | M | – | – | | +| locationList | M | M | – | – | | +| portItemList | M | M | – | – | | + +Table 47 + +| Name | Type | Description | +|-------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | A code that uniquely identifies a type of manufactured telecommunications network equipment or an assignable entity within a type of equipment. This code is assigned on behalf of the manufacturer. | +| componentItemList | SEQUENCE OF ObjectInstance | An Equipment identity's subordinate Component item is a role of a Component item belonging to the Equipment identity. An Equipment identity may relate to several Component items, and one Component item may relate to only one Equipment identity. | +| equipmentItemList | SEQUENCE OF ObjectInstance | An Equipment identity's subordinate Equipment item is a role of an Equipment item belonging to the Equipment identity. An Equipment identity may relate to several equipment items, and one Equipment item may relate to only one Equipment identity. | +| locationList | SEQUENCE OF ObjectInstance | An Equipment identity's subordinate Location is a role of a Location belonging to the Equipment identity. An Equipment identity may relate to several Locations, and one Location may relate to only one Equipment identity. | +| portItemList | SEQUENCE OF ObjectInstance | An Equipment identity's subordinate Port item is a role of a Port item belonging to the Equipment identity. An Equipment identity may relate to several Port items, and one Port item may relate to only one Equipment identity. | + +#### 7.3.27.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.28 Equipment Item + +#### 7.3.28.1 Definition + +An Equipment item provides a collection of functions and is considered as a unit from a placement point of view in a Location. + +An Equipment item may be an Exchange, taking up a whole room, and it may be an individual circuit card. + +#### 7.3.28.2 Attributes + +Table 48 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| uniqueItemIdentification | M | M | – | – | | +| equipmentIdentity | M | M | – | – | | +| exchange | M | M | – | – | | +| location | M | M | – | – | | + +Table 49 + +| Name | Type | Description | +|--------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | An Equipment item is assigned a unique Identifier within the scope of its superior Cross-coupling site. Room identification may or may not be a part of the Equipment item Identifier. The Operator of the Cross-coupling site assigns the Equipment item Identifier, and different pieces of Equipment items within a Cross-coupling site may be owned or used by different entities.
Aliases of Equipment item Identifiers are not permitted for communication between Operators. However, Operators may exchange additional Equipment item identifiers that are local to a specific Operator. | +| uniqueItemIdentification | String | The manufacturer may assign a Unique item identification (UID) to an Equipment item. | +| equipmentIdentity | ObjectInstance | An Equipment item's subordinate Equipment identity is a role of an Equipment identity to which the Equipment item belongs. | +| exchange | ObjectInstance | An Equipment item's subordinate Exchange is a role of an Exchange that is implemented by the Equipment item. | +| location | ObjectInstance | An Equipment item's subordinate Location is a role of a Location subordinate to the superior Cross-coupling site or a recursively subordinate Location. Each Equipment item shall be assigned exactly one Location placement where the Equipment item can be found. | + +#### 7.3.28.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.29 Equipment Holder + +#### 7.3.29.1 Definition + +The equipment holder IOC is a class of objects that represent physical resources of a network element that are capable of holding other physical resources. Examples of resources represented by instances of this object class are equipment bay, shelf and slot. + +#### 7.3.29.2 Attributes + +Table 50 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| acceptableCircuitPackTypeList | O | M | M | M | | +| administrativeState | O | M | M | M | | +| affectedObjectList | O | M | – | – | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| equipmentHolderAddress | M | M | – | M | | +| equipmentHolderType | M | M | – | M | | +| equipmentId | M | M | – | M | | +| holderStatus | O | M | – | – | | +| locationName | O | M | M | M | | +| operationalState | O | M | – | – | | +| replaceable | M | M | – | M | | +| serialNumber | M | M | – | – | | +| subordinateCircuitPackSoftwareLoad | O | M | M | M | | +| supportedByObjectList | M | M | M | M | | +| typeText | M | M | – | M | | +| userLabel | O | M | M | M | | +| vendorName | O | M | M | M | | +| version | O | M | M | M | | + +#### 7.3.29.3 Notifications + +Table 51 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| environmentalAlarm | O | | +| equipmentAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| processingErrorAlarm | O | | +| stateChange | O | | + +### 7.3.30 Exchange + +#### 7.3.30.1 Definition + +An Exchange is an entity that directs individual calls, packages or cells. + +Exchanges can be switches, concentrators or routers. Exchanges can be customer exchanges or transit exchanges. Intelligent Network servers and Operations Support System servers are not Exchanges and are not Cross-coupling sites. A Cross-coupling site may contain several Exchanges of various types. + +#### 7.3.30.2 Attributes + +Table 52 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| no | M | M | – | – | | +| equipmentItem | M | M | – | – | | + +Table 53 + +| Name | Type | Description | +|---------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| no | String | The number No uniquely identifies an Exchange within the scope of a Cross-coupling site. The managing Operator of the superior Cross-coupling site decides the numbering. Note that it is permissible to define a Cross-coupling site for each Exchange or a set of Exchanges at the same Address. In this case, separate Trails and other resources are required to route Trails between these Cross-coupling sites at the same Address. See also under Cross-coupling site. | +| equipmentItem | ObjectInstance | An Exchange's subordinate Equipment item is a role of an Equipment item subordinate to a Cross-coupling site. The Exchange object class role is provided due to the specific identification of Exchanges different from identification of Equipment item in general. The reference via Equipment item provides a reference to the placement of the Exchange in a specific Location, e.g., in a room. | + +#### 7.3.30.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.31 External Point + +#### 7.3.31.1 Definition + +The External Point IOC is a superclass for Control Point and Scan Point IOCs which are used to control external devices or monitor external conditions respectively. This object class contains common aspects of Control Point and Scan Point object classes. The operational state and administrative state represent the state of the control and scan functions, i.e., not the state of the external entity. + +#### 7.3.31.2 Attributes + +Table 54 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| externalPointId | M | M | – | M | | +| externalPointMessage | M | M | M | M | | +| locationName | O | M | M | M | | +| operationalState | M | M | – | – | | +| supportedByObjectList | M | M | – | – | | + +#### 7.3.31.3 Notifications + +Table 55 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | M | | + +### 7.3.32 Fabric + +#### 7.3.32.1 Definition + +The fabric IOC represents the function of managing the establishment and release of cross-connections. It also manages the assignment of termination points to TP Pools and GTPs. + +Administrative State: + +- Unlocked: The fabric is allowed to perform its normal functions. Operations will be accepted to set up or remove cross-connections, to rearrange TP Pools, to add/remove termination points to/from GTPs. +- Locked: The fabric is not allowed to perform its normal functions. No operations will be accepted. No new cross-connection can be setup or removed, no TP Pool can be rearranged, and no termination points can be added/removed to/from GTPs. + +Operational State: + +- Enabled: When the fabric is in the enabled operational state, it may be fully-operational or partially-operational (partially operational is indicated by the availability status attribute), e.g.: + - a) set up or remove any cross-connection; + - b) rearrange TP Pools; and + - c) add/remove termination points to/from GTPs. +- Disabled: The fabric is incapable of performing its normal function. + +#### 7.3.32.2 Attributes + +Table 56 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| availabilityStatus | M | M | – | – | | +| fabricId | M | M | – | M | | +| listOfCharacteristicInfo | M | M | – | M | | +| operationalState | M | M | – | – | | +| supportedByObjectList | M | M | M | M | | + +#### 7.3.32.3 Notifications + +Table 57 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.33 Flow Domain + +#### 7.3.33.1 Definition + +The Flow Domain IOC represents the logical collections of flow (termination) points that are available for the purpose of transferring information. A Flow Domain instance exists within a single layer network. The attribute containedFlowDomainList will be null if there are no contained Flow Domains. The attribute containedInFlowDomainList will also be null if there are no containing (parent) Flow Domains. + +#### 7.3.33.2 Attributes + +Table 58 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| containedAccessGroupList | O | M | M | M | | +| containedFlowDomainList | O | M | M | M | | +| containedFlowPointPoolList | O | M | M | M | | +| containedFPList | O | M | M | M | | +| containedFPPLinkList | O | M | M | M | | +| containedInFlowDomainList | O | M | M | M | | +| flowDomainId | M | M | – | – | | +| linkPointerList | O | M | – | – | | +| operationalState | O | M | – | – | | + +**Table 58** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| signalId | M | M | – | M | | +| supportedByObjectList | O | M | M | M | | +| usageState | O | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.33.3 Notifications + +**Table 59** + +| Name | Qualifier | Notes | +|----------------------|------------------|--------------| +| attributeValueChange | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.34 Flow Domain Fragment + +#### 7.3.34.1 Definition + +The Flow Domain Fragment IOC represents a transport entity which transfers a grouping of traffic units (information) transparently across a flow domain. The Flow Domain Fragment is a class of objects that associate the flow point object(s) at the boundary of a flow domain, which are identified in the inputFPList attribute and the flow point object(s) listed in the outputFPList attribute of this managed object. + +#### 7.3.34.2 Attributes + +**Table 60** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| administrativeState | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| fDFrConnectionType | O | M | – | M | | +| fDFrId | M | M | – | – | | +| inputFPList | M | M | M | M | | +| operationalState | O | M | – | – | | +| outputFPList | M | M | M | M | | +| protected | O | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.34.3 Notifications + +Table 61 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | +| stateChange | O | | + +### 7.3.35 Flow Point Pool + +#### 7.3.35.1 Definition + +The Flow Point Pool IOC represents a subset of the Flow Points at the edge of one Flow Domain that are associated through the FPP Link with a corresponding subset of Flow points at the edge of another Flow Domain or access group for the purpose of transferring characteristic information. + +This IOC is used to represent the termination of an FPP Link at a network layer. Flow Point Pools are managed entities that may represent certain kind of interfaces, such as UNI or NNIs, at a given layer. Flow Point Pools terminate FPPLinks for the purpose of representing topology. FPPs also contain Flow Points of the Flow Domain Fragment that are terminated on or traverse the interface. + +#### 7.3.35.2 Attributes + +Table 62 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| containedInFlowDomainList | O | M | – | M | | +| currentProblemList | O | M | – | – | | +| flowPointList | O | M | M | M | | +| flowPointPoolId | M | M | – | M | | +| linkPointer | M | M | – | M | | +| fppDirectionality | M | M | – | M | | +| maxFPPAssignbleCapacity | M | M | – | M | | +| operationalState | O | M | – | – | | +| serverTTPPointer | O | M | – | M | | +| supportedByObjectList | O | M | – | M | | +| totalFPPCapacity | M | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.35.3 Notifications + +Table 63 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | + +### 7.3.36 Flow Point Pool Link (FPPLink) + +#### 7.3.36.1 Definition + +The Flow Point Pool Link IOC represents the topological relationship and available capacity between a pair of flow domains, or a flow domain and an access group, or a pair of access groups. + +The serverTrail attribute is a pointer to the trail in the server layer network domain that supports this FPP Link. The serverTrail attribute may be null if the trail in the server layer network domain that supports this topological link is not assigned. + +The totalFPPLinkCapacity attribute indicates the total amount of bandwidth available (both ingress and egress). + +#### 7.3.36.2 Attributes + +Table 64 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEndofFPPLink | M | M | M | M | | +| fPPLinkId | M | M | M | – | | +| serverTrail | M | M | – | – | | +| signalId | M | M | – | M | | +| totalFPPLinkCapacity | O | M | – | – | | +| usageCost | O | M | – | – | | +| userLabel | O | M | M | M | | +| zEndofFPPLink | M | M | M | M | | + +#### 7.3.36.3 Notifications + +Table 65 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | + +### 7.3.37 Flow Point Sink + +#### 7.3.37.1 Definition + +The Flow Point Sink IOC terminates link flows and/or originates flow domain flows. The resource receives information (traffic), via a link flow, from an instance representing Flow Point Source, and sends it on, via a flow domain flow, to instances representing either Flow Point Sources or a Flow Termination Point Sink in the same Flow Domain. This IOC inherits from IOC Connectionless Point. + +The downstream FP pointer attribute points to the Connectionless Point IOC instances, within the same managed element, that receive information (traffic) from this flow point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Flow Termination Point Sink, Flow Point Source. The downstream FP pointer may identify one or more objects depending on whether the signal is pointed to one or more connectionless point objects. + +#### 7.3.37.2 Attributes + +Table 66 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| fpId | C:M
(Note) | M | – | M | | +| locationName | O | M | M | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| serverFTPPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | M | | +| signalId | M | M | – | M | | +| upstreamFPPointer | M | M | – | M | | +| userLabel | O | M | M | M | | +| NOTE – The condition is if this IOC has an instance. | | | | | | + +#### 7.3.37.3 Notifications + +Table 67 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | +| stateChange | O | | +| communicationsAlarm | O | | + +### 7.3.38 Flow Point Source + +#### 7.3.38.1 Definition + +The Flow Point Source IOC originates link flows and/or terminates flow domain flows. The resource sends information (traffic), via a line flow, to instances representing Flow Point Sink, and receives it, via a flow domain flow, from an instance representing either a Flow Point Sink or a Flow Termination Point Source in the same Flow Domain. This IOC inherits from IOC Connectionless Point. + +The upstream FP pointer attribute points to the Connectionless Point IOC instances, within the same managed element, that send information (traffic) to this flow point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Flow Termination Point Source, Flow Point Sink. + +#### 7.3.38.2 Attributes + +Table 68 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| serverFTPPointer | O | M | – | – | | +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| downstreamFPPointer | M | M | – | M | | +| fpId | C:M
(Note) | M | – | M | | +| locationName | O | M | M | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| serverFTPPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | M | | +| signalId | M | M | – | M | | + +NOTE – The condition is if this IOC has an instance. + +#### 7.3.38.3 Notifications + +Table 69 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | +| stateChange | O | | +| communicationsAlarm | O | | + +### 7.3.39 Flow Termination Point Sink + +#### 7.3.39.1 Definition + +The Flow Termination Point Sink IOC represents a class of managed objects that terminates connectionless trails. It represents the access point in a layer network which is a focus for both the trail relationship and the client/server relationship. This IOC inherits from IOC Connectionless Point. + +The operational state reflects the perceived ability to receive a valid signal. If the flow termination point detects that a signal received has failed or it is unable to process the incoming signal, then the operational state will have the value disabled. + +When the administrative state is locked, the flow termination point is administratively removed from service. When the administrative state is unlocked, the flow termination point is administratively in service. Changes to the administrative state have no effect on the connectionless trail pointer. + +A change in the operational state shall cause a state change notification. If the administrative state is present in an instance of flow termination point sink IOC, it shall not emit a state change notification. However, subclasses of flow termination point sink IOC may modify this behaviour to require this notification. Subclasses of flow termination point sink shall specify the attributes for which attribute value change notifications should be generated. + +The upstream FP pointer attribute points to the connectionless point IOC, within the same managed element, which sends information (traffic) to this flow termination point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Flow Point Sink (single or a concatenated sequence) or Flow Termination Point Source. + +#### 7.3.39.2 Attributes + +Table 70 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientFPList | O | M | – | – | | +| connectionlessTrailPointer | O | M | M | – | | + +**Table 70** + +| | | | | | | +|------------------------------------------------------|---------------|---|---|---|--| +| ftpId | C:M
(Note) | M | – | M | | +| locationName | O | M | M | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | M | | +| upstreamFPPointer | M | M | – | M | | +| userLabel | O | M | M | M | | +| NOTE – The condition is if this IOC has an instance. | | | | | | + +#### 7.3.39.3 Notifications + +**Table 71** + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | +| stateChange | O | | +| communicationsAlarm | O | | + +### 7.3.40 Flow Termination Point Source + +#### 7.3.40.1 Definition + +The Flow Termination Point Source IOC represents a class of managed objects that originates connectionless trails. It represents the access point in a layer network which is a focus for both the trail relationship and the client/server relationship. This IOC inherits from IOC Connectionless Point. + +The operational state reflects the perceived ability to generate a valid signal. If the flow termination point detects that a valid signal cannot be generated, then the operational state will have the value disabled. + +When the administrative state is locked, the flow termination point is administratively removed from service. When the administrative state is unlocked, the flow termination point is administratively in service. Changes to the administrative state have no effect on the connectionless trail pointer. + +A change in the operational state shall cause a state change notification. If the administrative state is present in an instance of flow termination point source IOC, it shall not emit a state change notification. However, subclasses of flow termination point source IOC may modify this behaviour to require this notification. Subclasses of flow termination point source shall specify the attributes for which attribute value change notifications should be generated. + +The downstream FP pointer attribute points to the Connectionless Point Flow Point Source or Flow Termination Point Sink IOC, within the same managed element, which receives information (traffic) from this flow termination point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Flow Point Source (single or a concatenated sequence or a set if pointed to more than one flow point source objects) or Flow Termination Point Sink (single or a set if pointed to more than one flow termination point sink objects). + +#### 7.3.40.2 Attributes + +Table 72 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientFPList | O | M | – | – | | +| connectionlessTrailPointer | O | M | M | – | | +| downstreamFPPointer | M | M | – | M | | +| ftpId | C:M
(Note) | M | – | M | | +| locationName | O | M | M | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| supportedByObjectList | M | M | – | M | | +| userLabel | O | M | M | M | | +| clientFPList | O | M | – | – | | + +NOTE – The condition is if this IOC has an instance. + +#### 7.3.40.3 Notifications + +Table 73 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | +| attributeValueChange | O | | +| stateChange | O | | +| communicationsAlarm | O | | + +### 7.3.41 Generic interface + +For further study. + +### 7.3.42 Generic management interface + +For further study. + +### 7.3.43 Generic transport TTP + +#### 7.3.43.1 Definition + +The Generic Transport TTP IOC is used to represent a physical port or endpoints of transport connections. It may be used by technology-specific models as an abstraction of an underlying transport layer. + +#### 7.3.43.2 Attributes + +Table 74 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientFlowPointPoolList | O | M | M | M | | +| clientLinkEndPointerList | M | M | M | M | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| potentialCapacity | O | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| ttpPortID | O | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.43.3 Notifications + +Table 75 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.44 Geographical area + +#### 7.3.44.1 Definition + +The Geographical Area IOC defines a geographical or administrative area defined by the authorities of that Country. + +Different spellings dependent on the user are not permissible. In case the spelling given by the authorities exceeds 12 characters, or is not unique with 12 characters only, the Administration in that Country is responsible for assigning a unique identifier. + +#### 7.3.44.2 Attributes + +Table 76 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| name | M | M | – | – | | +| siteList | M | M | – | – | | + +Table 77 + +| Name | Type | Description | +|----------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| name | String(SIZE(1..12)) | Name of the Geographical area as spelled by the authorities in that Country, i.e., in a national language of that Country. Note that different spellings dependent on the user are not permissible. Geographical area Name has up to 12 characters. Upper- and lower-case letters are permitted. Symbols that may be included in Geographical area Name are hyphen (-), underscore (_ ) and space ( ). In case the spelling given by the authorities exceeds 12 characters or is not unique with 12 characters only, the Administration in that Country is responsible for assigning a unique identifier. | +| siteList | SEQUENCE OF ObjectInstance | A Geographical area's subordinate Site is a role of a Cross-coupling site subordinate to Operator. This referenced Cross-coupling site's Identifier contains the Geographical area Name. | + +#### 7.3.44.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.45 Group Termination Point (gtp) + +#### 7.3.45.1 Definition + +This IOC represents a group of termination points treated as a single unit for management purposes such as cross-connections. The *signalType* attribute describes the composition of the GTP. When a termination point is involved in a GTP, it cannot be cross-connected independently of that GTP. + +#### 7.3.45.2 Attributes + +Table 78 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| crossConnectionObjectPointer | M | M | – | – | | +| gtpId | M | M | – | – | | +| signalType | M | M | – | – | | +| tpsInGtpList | M | M | – | – | | + +#### 7.3.45.3 Notifications + +Table 79 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | O | | +| objectDeletion | O | | + +### 7.3.46 Layer Network Domain + +#### 7.3.46.1 Definition + +This IOC represents a transport administrative domain in which all resources pertain to the same ITU-T G.805 layer. It represents the topological aspects of the transport network layer. The *signalId* can be set upon creation of an instance of the Layer Network Domain to support the following typical operations: + +- set the *signalId* value upon creation of the layer network domain; +- set the *signalId* attribute of a subnetwork (or abstract link, etc.) based on the value of the layer network domain instance referenced in the create request. + +#### 7.3.46.2 Attributes + +Table 80 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| networkId | M | M | – | – | | +| signalId | M | M | – | M | | +| systemTitle | M | M | M | M | | +| userLabel | O | M | M | M | | + +#### 7.3.46.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.47 Link Connection + +#### 7.3.47.1 Definition + +The Link Connection IOC is a class of objects responsible for the transparent transfer of information between Network Connection Termination Points. A Link Connection may be a component of a Trail. A sequence of one or more Link Connections (and subnetwork connections) may be linked together to form a Trail. + +A Link Connection may be either uni- or bidirectional. + +A point-to-point unidirectional Link Connection can be established between a Network connection termination point source or Network connection termination point bidirectional; and a Network connection termination point sink or Network connection termination point bidirectional. + +A point-to-point bidirectional Link Connection can be established between a Network connection termination point bidirectional; and a Network connection termination point bidirectional. + +An operation to create a Link Connection will not be successful and will fail with an invalid TP type if a requested endpoint is a Network Trail Termination Point. For all types of Link Connection, the network termination point(s) pointed to by the A End attribute is related to the network termination point(s) pointed to by the Z End attribute in such a way that traffic can flow between the network termination points represented by these managed objects in a unidirectional or bidirectional manner as indicated by the directionality attribute. + +#### 7.3.47.2 Attributes + +Table 81 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEndNetworkTPList | M | M | – | M | | +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| clientTrail | O | M | – | M | | +| compositePointer | O | M | – | – | | +| connectionId | M | M | – | – | | +| currentProblemList | O | M | – | – | | +| directionality | M | M | – | – | | +| operationalState | O | M | – | – | | +| protected | O | M | – | M | | +| qualityOfConnectivityService | O | M | – | – | | +| serverTrailList | O | M | – | M | | +| signalId | M | M | – | M | | +| supportedByObjectList | O | M | M | M | | +| userLabel | O | M | M | M | | +| zEndNetworkTPList | M | M | – | M | | + +**Table 82** + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.48 Location + +#### 7.3.48.1 Definition + +A Location is a subdivision of a Cross-coupling site. It is an object in which resources, such as Exchanges, Equipment items and termination points, are placed. It should be noted that the term "Location" is here given a particular meaning local to Cross-coupling site, and that this definition may not apply for the generic term location. + +A Location can be a room, a frame, a rack, a block, a shelf or a slot in a shelf, and these may contain subordinate Locations recursively, with the following structure: + +- S<> 'Location' Location: The recursion is indicated by the subordinate Location class inheriting properties by the S(chema) reference to its superior Location class. + +#### 7.3.48.2 Attributes + +**Table 83** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| uniqueItemIdentification | M | M | – | – | | +| componentItem | M | M | – | – | | +| equipmentIdentity | M | M | – | – | | +| equipmentItem | M | M | – | – | | + +**Table 84** + +| Name | Type | Description | +|--------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | The Identifier of a Location uniquely identifies a Location within a superior Location or Cross-coupling site. The Identifier may consist of both digits and letters. The Location Identifier is assigned by the Operator of the Cross-coupling site. | +| uniqueItemIdentification | String | The manufacturer may assign a Unique item identification (UID) to a Location. | +| componentItem | ObjectInstance | A Location's subordinate Component item is a role of a Component item of an Equipment item in this Location. | +| equipmentIdentity | ObjectInstance | A Location's subordinate Equipment identity is a role of an Equipment identity to which the Location belongs. | +| equipmentItem | ObjectInstance | A Location's subordinate Equipment item is a role of an Equipment item being placed in this Location. | + +#### 7.3.48.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.49 Logical link + +#### 7.3.49.1 Definition + +A logical link IOC represents a link that may be administratively composed of link connections or bandwidth that may be provided by one or more topological links or other logical links. + +#### 7.3.49.2 Attributes + +Table 85 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEnd | M | M | – | M | | +| availableLinkCapacity | M | M | – | – | | +| linkConnectionPointerList | O | M | M | M | | +| linkDirectionality | M | M | – | – | | +| linkId | M | M | – | – | | +| signalId | M | M | – | M | | +| usageCost | O | M | – | – | | +| userLabel | O | M | M | M | | +| zEnd | M | M | – | M | | + +#### 7.3.49.3 Notifications + +Table 86 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.50 Logical Link End + +#### 7.3.50.1 Definition + +The Logical Link End IOC represents the end of a logical link. When present, the Network CTPs In Link End List Package identifies the network CTPs that are present in the Logical Link End. + +#### 7.3.50.2 Attributes + +Table 87 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------|-------------------|----------------|-----------------|------------------|------------------| +| availableLinkEndCapacity | M | M | – | – | | +| containedInSubNetworkList | O | M | M | M | | +| linkEndId | M | M | – | – | | +| linkPointer | M | M | – | – | | +| logicalEndDirectionality | M | M | – | – | | +| networkCTPsInLinkEndList | O | M | – | – | | +| signalId | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.50.3 Notifications + +Table 88 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.51 Managed element + +#### 7.3.51.1 Definition + +The managed element IOC is a class of objects representing telecommunications equipment or TMN entities (either groups or parts) within the telecommunications network that performs managed element functions, i.e., provides support and/or service to the subscriber. Managed elements may or may not additionally perform mediation/OS functions. A managed element communicates with the manager (directly or indirectly) over one or more standard Q-interfaces for the purpose of being monitored and/or controlled. A managed element contains equipment that may or may not be geographically distributed. + +#### 7.3.51.2 Attributes + +Table 89 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | M | M | – | – | | +| currentProblemList | O | M | – | – | | +| externalTime | O | M | M | M | | +| locationName | O | M | M | M | | +| managedElementId | M | M | – | – | | +| managedElementType | M | M | – | – | | +| modelCode | M | M | – | – | | +| neAliases | O | M | – | – | | +| operationalState | M | M | – | – | | +| systemTimingSource | O | M | M | M | | +| systemTitle | M | M | M | M | | +| usageState | M | M | – | – | | +| userLabel | O | M | M | M | | +| vendorName | O | M | M | M | | +| version | O | M | M | M | | + +#### 7.3.51.3 Notifications + +Table 90 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | M | | +| environmentalAlarm | M | | +| equipmentAlarm | M | | +| objectCreation | O | | +| objectDeletion | O | | +| processingErrorAlarm | M | | +| stateChange | O | | + +### 7.3.52 Managed Element Complex + +#### 7.3.52.1 Definition + +The Managed Element Complex IOC is a class of managed objects that represent a collection of network elements. A manager can reference and manage one or more NEs belonging to the complex represented by an instance of this object class. + +#### 7.3.52.2 Attributes + +Table 91 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-------------------------|-------------------|----------------|-----------------|------------------|------------------| +| managedElementComplexId | M | M | – | – | | +| systemTitle | M | M | M | M | | + +#### 7.3.52.3 Notifications + +Table 92 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.53 Multipoint cross-connection + +#### 7.3.53.1 Definition + +The multipoint cross-connection IOC represents an assignment relationship between the termination point or GTP object listed in the fromTermination attribute and the termination point or GTP objects listed in the toTermination attributes of the contained cross-connection object instances. + +A multipoint cross-connection can be established between one of CTP Sink, CTP Bidirectional, TTP Source, TTP Bidirectional, or GTP; and a set whose members are CTP Source, CTP Bidirectional, TTP Sink, TTP Bidirectional, or GTP. + +The fromTermination attribute will always be non-NULL. The termination point or GTP object pointed to by the fromTermination attribute is related to all the termination point or GTP objects pointed to by the toTermination attribute of the contained crossConnection managed objects in such a way that traffic can flow between the termination points represented by these managed objects. Information flows from the From Termination to the To Termination of the contained cross-connection objects. + +If the objects listed in the fromTermination attribute and in the toTermination attribute of the contained crossConnection objects are GTPs, the nth element of the From Termination GTP is related to the nth element of the To Termination GTP (for every n). The total rate of the fromTerminations must be equal to the total rate of toTerminations in each contained cross-connection object. The attribute Signal Type describes the signal that is cross-connected. The termination points or GTPs that are cross-connected must have signal types that are compatible. The following are the definitions of the administrative state and the operational state attributes: + +Administrative State: + +- Unlocked: The mpCrossConnection object is administratively unlocked. It allows traffic to pass through each contained connection depending on its administrative state. +- Locked: No traffic is allowed to pass through the Cross-Connection between the cross-connected termination points. The effect of this value overrides the effect of the administrative state of each contained cross-connection. + +Operational State: The operational state of a Multipoint Cross-Connection object reflects the overall health of the cross-connection including all the Cross-Connection objects contained in the Multipoint Cross-Connection. + +- Enabled: The Cross-Connection performs its normal function. Note that some (but not all) of the cross-connection objects contained in the Multipoint Cross-Connection may be disabled. +- Disabled: The Cross-Connection is incapable of performing its normal cross-connection function. All the cross-connection objects contained in the Multipoint Cross-Connection are disabled. + +Availability Status: + +The supported values for this attribute are: + +- In test +- Degraded: +The Multipoint Cross-Connection is degraded in some respect. For instance, if one or more (but not all) Cross-Connection objects contained in the Multipoint Cross-Connection are disabled, the Multipoint Cross-Connection will be considered as degraded. The Multipoint Cross-Connection remains available for service (i.e., its operational state is enabled) while it is degraded. +- Empty SET. + +When the attribute value change notification is present, the attributeValueChange notification shall be emitted when userLabel or redline changes value (when the attributes are present). When the state change notification package is present, the stateChange notification shall be emitted when operationalState or administrativeState changes value. + +#### 7.3.53.2 Attributes + +Table 93 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| availabilityStatus | M | M | – | – | | +| fromTermination | M | M | – | – | | +| mpCrossConnectionId | M | M | – | – | | +| operationalState | M | M | – | – | | +| redline | O | M | M | M | | +| signalType | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.53.3 Notifications + +Table 94 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.54 Multipoint Trail + +#### 7.3.54.1 Definition + +A Multipoint trail is a connected set of Trails that are connecting three or more endpoints. A Multipoint trail can reside within one Cross-coupling site, or it may connect two or more Cross-coupling sites. + +#### 7.3.54.2 Attributes + +Table 95 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| localIdentifier | M | M | – | M | | +| trailList | M | M | M | M | | + +Table 96 + +| Name | Type | Description | +|-----------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | The Identifier uniquely identifies the Multipoint trail within the scope of an Operator. This means that if the resources of a Multipoint trail are shared between Operators, each Operator may assign its local Identifier to the Multipoint trail. This scheme is different from Identifiers of Trails within the Multipoint trail, as they are identified locally to Site relations. | +| localIdentifier | String(SIZE(1..26)) | An identifier of a Multipoint trail that is unique within an Operator, having up to 26 alphabetic and/or numeric characters. A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400]. | +| trailList | SEQUENCE OF ObjectInstance | A Multipoint trail's subordinate Trail is a role of a Trail that is contained in the Multipoint trail. | + +#### 7.3.54.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.55 Named cross-connection + +#### 7.3.55.1 Definition + +The Named Cross-Connection IOC is a subclass of Cross-Connection with two (additional) mandatory attributes: + +- Redline: This attribute identifies whether the associated object instance is red lined, e.g., identified as being part of a sensitive circuit; +- CrossConnectionName: This attribute is a descriptive name for the cross-connection object instance. + +#### 7.3.55.2 Attributes + +Table 97 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| crossConnectionId | M | M | – | – | | +| crossConnectionName | M | M | M | M | | +| directionality | M | M | – | – | | +| fromTermination | M | M | – | – | | +| operationalState | M | M | – | – | | +| redline | M | M | M | M | | +| signalType | M | M | – | – | | +| toTermination | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.55.3 Notifications + +Table 98 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.56 Named multipoint cross-connection + +#### 7.3.56.1 Definition + +The Named Multipoint Cross-Connection IOC is a subclass of Multipoint Cross-Connection with two (additional) mandatory attributes: + +- Redline: This attribute identifies whether the associated object instance is red lined, e.g., identified as being part of a sensitive circuit; +- CrossConnectionName: This attribute is a descriptive name for the multipoint cross-connection object instance. + +#### 7.3.56.2 Attributes + +Table 99 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| availabilityStatus | M | M | – | – | | +| crossConnectionName | M | M | M | M | | +| fromTermination | M | M | – | – | | +| mpCrossConnectionId | M | M | – | – | | +| operationalState | M | M | – | – | | +| redline | M | M | M | M | | +| signalType | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.56.3 Notifications + +Table 100 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.57 Network + +#### 7.3.57.1 Definition + +The Network IOC is a class of objects that are collections of interconnected telecommunications and management objects (logical or physical) capable of exchanging information. These objects have one or more common characteristics, for example, they may be owned by a single customer or provider, or associated with a specific service network. + +A network may be nested within another (larger) network, thereby forming a containment relationship. + +An example of a network that is contained in another network is a transmission sub-network. It is owned by a single Administration and can only perform transmission functions. + +#### 7.3.57.2 Attributes + +Table 101 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| networkId | M | M | – | – | | +| systemTitle | M | M | M | M | | +| userLabel | O | M | M | M | | + +#### 7.3.57.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.58 Network CTP Bidirectional + +#### 7.3.58.1 Definition + +This IOC represents a termination point where a Link Connection or a Subnetwork Connection is both originated and terminated, i.e., the combined behaviour of the Network CTP Source and Network CTP Sink IOCs. + +#### 7.3.58.2 Attributes + +Table 102 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| channelNumber | O | M | – | M | | +| characteristicInformation | O | M | – | M | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| cTPId | O | M | – | M | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| serverTTPPointer | O | M | – | – | | + +**Table 102** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| sub-partitionPointer | O | M | – | – | | +| superPartitionPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.58.3 Notifications + +**Table 103** + +| Name | Qualifier | Notes | +|----------------------|------------------|--------------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.59 Network CTP Sink + +#### 7.3.59.1 Definition + +The Network CTP Sink IOC is a class of objects that terminates Link connections and/or originates Subnetwork Connections. The resource receives information (traffic), via a Link connection, from an instance representing a NetworkConnection Termination Point, and sends it on, via a Subnetwork Connection, to instances representing either NWCTP Sources or a NWTTP Sink in the same Subnetwork. + +An instance of this class may only have connectivity relationships (link connection or subnetwork connection) with instances that represent Network Connection Termination Points, Source or Bidirectional, which are at the same layer. + +An instance of this class may be subnetwork connected, via a Subnetwork Connection, to a single instance which represents a Network Trail Termination Point, Sink or Bidirectional, at the same layer. + +The Subnetwork Connection Pointer attribute points to the managed object representing the relationship with the network termination point(s), within the same Subnetwork, that receive(s) information (traffic) from this network termination point, or is null. + +The referenced managed object shall represent a Subnetwork Connection. Where the NWCTP sink participates in many subnetwork connections for different subnetworks, the Subnetwork Connection Pointer is null. Any network termination points identified by the related Subnetwork Connection indicate that a relationship exists, but this does not indicate that information can flow between the network termination points. This capability is indicated by a combination of the State Attributes including the Operational State. + +The Connectivity Pointer attribute points to the managed object representing the Connection which relates this instance to the instance representing the Network Connection Termination Point, Source or Bidirectional, that sends information (traffic) to this network termination point, or is null. + +#### 7.3.59.2 Attributes + +Table 104 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| channelNumber | O | M | – | M | | +| characteristicInformation | O | M | – | M | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| cTPId | O | M | – | M | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| serverTPPointer | O | M | – | – | | +| sub-partitionPointer | O | M | – | – | | +| superPartitionPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.59.3 Notifications + +Table 105 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.60 Network CTP Source + +#### 7.3.60.1 Definition + +The Network CTP Source IOC is a class of objects that originates Link connections and/or terminates Subnetwork Connections. The resource sends information (traffic), via a Link connection, to instances representing Network Connection Termination Points, and receives it, via a Subnetwork Connection, from an instance representing either a NWCTP Sink or a NWTTP Source in the same Subnetwork. + +An instance of this class may only have connectivity relationships (link connection or subnetwork connection) with instances that represent Network Connection Termination Points, Sink or Bidirectional, which are at the same layer. + +An instance of this class may be subnetwork connected, via a Subnetwork Connection, to a single instance which represents a Network Trail Termination Point, Source or Bidirectional, at the same layer. + +The Subnetwork Connection Pointer attribute points to the managed object representing the relationship with the network termination point, within the same Subnetwork, that sends information (traffic) to this network termination point, or is null. The referenced managed object shall represent a Subnetwork Connection. + +Where the NWCTP source participates in many subnetwork connections for different subnetworks, the Subnetwork Connection Pointer is null. Any network termination points identified by the related Subnetwork Connection indicate that a relationship exists, but this does not indicate that information can flow between the network termination points. This capability is indicated by a combination of the State Attributes, including the Operational State. + +The Connectivity Pointer attribute points to the managed object representing the Connection which relates this instance to the instance representing the Network Connection Termination Point, Sink or Bidirectional, that receives information (traffic) from this network termination point, or is null. + +#### 7.3.60.2 Attributes + +Table 106 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| channelNumber | O | M | – | M | | +| characteristicInformation | O | M | – | M | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| cTPId | O | M | – | M | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | + +**Table 106** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| serverTTPPointer | O | M | – | – | | +| sub-partitionPointer | O | M | – | – | | +| superPartitionPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.60.3 Notifications + +**Table 107** + +| Name | Qualifier | Notes | +|----------------------|------------------|--------------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.61 Network Termination Point + +#### 7.3.61.1 Definition + +The Network Termination Point IOC represents the network termination of a transport entity, such as an instance representing a Trail or a Link Connection. The sncPointer is used to point to a Subnetwork Connection. However, not all network termination points will have a flexible connection, and it may be more appropriate to point to another network termination point, for example, in a regenerator the two network connection termination points would point to each other as there is no flexibility between them. In this instance, the networkTPPointer shall be used. Both pointers are conditional. + +The Connectivity Pointer attribute points to the object instance that represents the Link connection or Trail which relates this instance to other instance(s) representing the Network Termination Point(s). + +#### 7.3.61.2 Attributes + +Table 108 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.61.3 Notifications + +Table 109 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.62 Network TTP Bidirectional + +#### 7.3.62.1 Definition + +The Network TTP Bidirectional IOC represents a termination point where a network viewpoint Trail or Subnetwork Connection is both originated and terminated, i.e., the combined behaviour of the Network TTP Source and Network TTP Sink IOCs. + +#### 7.3.62.2 Attributes + +Table 110 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientCTPList | O | M | – | – | | +| clientLinkEndPointerList | O | M | – | – | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | – | | +| tTPId | O | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.62.3 Notifications + +Table 111 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.63 Network TTP Sink + +#### 7.3.63.1 Definition + +The Network TTP Sink IOC is a class of objects that terminate Trails and Subnetwork Connections in the Network viewpoint. An instance of this class may only have Trail relationships with Network Trail Termination Points, Source or Bidirectional, which are at the same layer. An instance of this class may be subnetwork connected, via a Subnetwork Connection, to a single Network Connection Termination Point Sink or Bidirectional, or a Network Trail Termination Point Source at the same layer. + +The Subnetwork Connection Pointer attribute points to the managed object representing the relationship with one or more Network Connection Termination Points, within the same Subnetwork, that send information (traffic) to this network termination point, or is null. + +Any network termination point identified by the related Subnetwork Connection indicates that a relationship exists, but this does not indicate that information can flow between the network termination points. This capability is indicated in a combination of the State attributes, including the Operational State. + +The Connectivity Pointer attribute points to the managed object representing the Trail which relates this instance to the instances representing the Network Trail Termination Points, that send information (traffic) to this network termination point at the same layer, or is null. + +This managed object represents the network termination of a transport entity, such as an instance representing a Trail or a Link Connection. The sncPointer is used to point to a Subnetwork Connection. However, not all network termination points will have a flexible connection, and it may be more appropriate to point to another network termination point, for example, in a regenerator the two network connection termination points would point to each other as there is no flexibility between them. In this instance, the networkTPPointer shall be used. Both pointers are conditional. + +The Connectivity Pointer attribute points to the object instance that represents the Link connection or Trail which relates this instance to other instance(s) representing the Network Termination Point(s). + +This managed object represents the termination of a transport entity, such as a trail or a connection. The characteristic information attribute is used to identify equivalence between subclasses of termination points in order to determine whether cross-connection or connectivity is possible. + +The operational state reflects the perceived ability to generate and/or receive a valid signal. Subclasses of termination point shall specify the attributes and states for which attribute value change and state change notifications will be generated. + +#### 7.3.63.2 Attributes + +Table 112 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientCTPList | O | M | – | – | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | – | | +| tTPId | O | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.63.3 Notifications + +Table 113 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.64 Network TTP Source + +#### 7.3.64.1 Definition + +The Network TTP Source IOC is a class of objects that originate Trails and Subnetwork Connections in the Network viewpoint. + +An instance of this class may only have Trail relationships with Network Trail Termination Points, Sink or Bidirectional, which are at the same layer. + +An instance of this class may be subnetwork connected, via a Subnetwork Connection, to a single Network Connection Termination Point Source or Bidirectional, or a Network Trail Termination Point Sink at the same layer. It may also be connected, via a Subnetwork Connection, to multiple instances of Network CTPs at the same layer when it is operating in the broadcast mode in order to transmit multiple copies of the same signal. + +The Subnetwork Connection Pointer attribute points to the managed object representing the relationship with one or more Network Connection Termination Points, within the same Subnetwork, that receive information (traffic) from this network termination point, or is null. + +Any network termination point identified by the related Subnetwork Connection indicates that a relationship exists, but this does not indicate that information can flow between the network termination points. This capability is indicated by a combination of the State Attributes, including the Operational State. + +The Connectivity Pointer attribute points to the managed object representing the Trail which relates this instance to the instances representing the Network Trail Termination Points, that receive information (traffic) from this network termination point at the same layer, or is null. + +#### 7.3.64.2 Attributes + +Table 114 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| clientCTPList | O | M | – | – | | +| clientLinkEndPointerList | O | M | – | – | | +| configuredConnectivity | O | M | – | – | | +| connectivityPointer | O | M | – | – | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| locationName | O | M | M | M | | +| neAssignmentPointer | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| networkTPPointer | O | M | – | – | | +| operationalState | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkConnectionPointer | O | M | – | – | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | – | | +| tTPId | O | M | – | M | | +| userLabel | O | M | M | M | | + +#### 7.3.64.3 Notifications + +**Table 115** + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.65 Operator + +#### 7.3.65.1 Definition + +Operator is an organization responsible for identification and management of telecommunication resources. + +The Operator must be legally recognized by the telecommunication Administration of the Country, or delegation thereof. An Operator may or may not correspond to a trading partner. An Operator can be a network operator or service provider. + +Both the national authority and the Operators should note that each Operator would be registered as a separate entity in each Country in which it operates, and is required to report country-specific information to each national authority. This may or may not imply a need for a multinational Operator to use different ICCs in each Country. + +Multinational Operators are encouraged to ensure that they are registered in each Country in which they operate. + +#### 7.3.65.2 Attributes + +**Table 116** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| icc | M | M | – | – | | +| controlledSiteList | M | M | M | M | | +| controlledTrailList | M | M | M | M | | + +**Table 117** + +| Name | Type | Description | +|---------------------|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| icc | ICC ::= String(SIZE (1..6)) |

The ITU Carrier Code provides a unique identifier of an Operator within a Country. The assignment of ICCs may be delegated to a lower-level regional administration (for example, a province).

The ICC is used as an indispensable part in the assignment of identifiers for interworking between Operators. It is permissible that an operator uses one ICC for assignment of identifiers, while other operator codes are used for ordering, billing, etc.

ICC is a 1- to 6-character alphanumeric field.

| +| controlledSiteList | SEQUENCE OF ObjectInstance |

An Operator's subordinate Controlled site is a role of a Cross-coupling site that is currently owned by the Operator, but not identified locally to this Operator. If the Operator owns Cross-coupling sites that are not identified locally to this Operator, this reference has to be explicitly provided.

| +| controlledTrailList | SEQUENCE OF ObjectInstance |

An Operator's subordinate Controlled trail is a role of a Trail being controlled by the Operator. An Operator may have many Controlled trails. Note that Controlled trail indicates responsibility for maintenance and not ownership.

| + +#### 7.3.65.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.66 Physical Link + +#### 7.3.66.1 Definition + +A Physical Link represents a set of parallel physical transport resources between two Cross-coupling sites. The physical transport resources are called Physical link connections. + +All Physical Link connections in a Physical Link shall be routed in the same cable branches. A cable branch connects either two Cross-Coupling Sites or two junctions where the pairs of the cable branch are split into pairs of cable branches leading to two or more different Cross-Coupling Sites. Cable branches represent one layer of the physical network, and Physical Links represent the layer at which resources are allocated to route Trails of multiplex groups or other usages. + +A Physical Link is terminated in exactly two Cross-Coupling Sites, which allow for termination of or cross-couplings between Physical link connections. A Physical Link cannot terminate in a junction that requires construction work to provide the couplings. Note that attributes of physical resources are different from attributes of logical resources and trail notions. + +Note that Physical Links are identified independently from Trail identifiers within the same Site Relationship. This allows cable and radio resources to be identified independently from Trails and the concerns of customers in the use of Trail identifiers. + +#### 7.3.66.2 Attributes + +**Table 118** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| identifier | M | M | – | – | | + +**Table 119** + +| Name | Type | Description | +|------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | The Identifier of a Physical link uniquely identifies the Physical link within the Site relationship. Note that Physical links are identified independently from Trail Identifiers within the same Site relationship. This allows cable and radio resources to be identified independently from Trails and the concerns of customers in the use of Trail Identifiers. | + +#### **7.3.66.3 Notifications** + +There are no notifications defined for this IOC. + +### **7.3.67 Physical Link Connection** + +#### **7.3.67.1 Definition** + +A Physical link connection represents a physical resource between two Cross-coupling sites and can be allocated to a single Trail. The resource may represent a single fibre, a pair, a set of two pairs or other, which is planned to be used as a section of a Trail. + +#### **7.3.67.2 Attributes** + +**Table 120** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | — | — | | +| position | M | M | — | — | | +| trailSection | M | M | — | — | | + +**Table 121** + +| Name | Type | Description | +|--------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | The Identifier of a Physical link connection uniquely identifies the Physical link connection within the Physical link. The syntax of the Identifier may indicate that it represents a single branch (e.g., 3a), a pair (3), a set of two pairs (3-) or other. | +| position | ObjectInstance | A Physical link connection's subordinate Position is a role of a Position on which the Physical link connection is terminated. | +| trailSection | ObjectInstance | A Physical link connection's subordinate Trail section is a role of a Trail section in a Trail. | + +#### **7.3.67.3 Notifications** + +There are no notifications defined for this IOC. + +### **7.3.68 Pipe** + +#### **7.3.68.1 Definition** + +The pipe IOC is a class of objects which ensure the transfer of information between two or more termination points. The directionality attribute indicates whether transmission is unidirectional or bidirectional. The Signal Id attribute describes the signal that is transferred across a Connectivity instance. The managed objects representing the network termination points that are related by this instance must have signal Ids that are compatible. + +If an instance of this class is bidirectional, the a- and z-termination points shall also be bidirectional. If an instance of this class is unidirectional, the a-point shall be the source TP or bidirectional TP and the z-termination point shall be the sink TP or bidirectional TP. + +For unidirectional connections, the aEndNWTPList attribute shall identify the source end. The operational state indicates the capability to carry a signal. + +#### 7.3.68.2 Attributes + +Table 122 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEndNetworkTPList | M | M | – | M | | +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| directionality | M | M | – | – | | +| operationalState | O | M | – | – | | +| protected | O | M | – | M | | +| qualityOfConnectivityService | O | M | – | – | | +| signalId | M | M | – | M | | +| supportedByObjectList | O | M | M | M | | +| userLabel | O | M | M | M | | +| zEndNetworkTPList | M | M | – | M | | + +#### 7.3.68.3 Notifications + +Table 123 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.69 Port Item + +#### 7.3.69.1 Definition + +A Port item defines a functional unit of a Component item of an Equipment item. The Port item can be sender, receiver, or bidirectional. It may also be possible to modify the function of a Port item. + +#### 7.3.69.2 Attributes + +Table 124 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| equipment identity | M | M | – | – | | +| position | M | M | – | – | | +| trailSection | M | M | – | – | | + +Table 125 + +| Name | Type | Description | +|-------------------|----------------|-----------------------------------------------------------------------------------------------------------------| +| identifier | String | A Port item is assigned a unique Identifier within the scope of its superior Component item. | +| equipmentIdentity | ObjectInstance | A Port item's subordinate Equipment identity is a role of an Equipment identity to which the Port item belongs. | +| position | ObjectInstance | A Port item's subordinate Position is a role of a Position that terminates the Port item. | +| trailSection | ObjectInstance | A Port item's subordinate Trail section is a role of a Trail section in a Trail. | + +#### 7.3.69.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.70 Position + +#### 7.3.70.1 Definition + +A Position is a unit that is used to enter terminations and cross-couplings. The Position can be an individual pin, a pair of pins or a group of pins, depending on the design, planned or actual use of the Position. + +#### 7.3.70.2 Attributes + +Table 126 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| physicalLinkConnectionList | M | M | – | – | | +| portItemList | M | M | – | – | | +| position | M | M | – | – | | +| trailList | M | M | – | – | | +| trailMultiplexChannelList | M | M | – | – | | +| trailSectionList | M | M | – | – | | + +**Table 127** + +| Name | Type | Description | +|----------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | A Position is assigned a unique Identifier within the scope of its superior Location. The Identifier may, e.g., indicate a group of pins (3), or an individual pin (3a). | +| physicalLinkConnectionList | SEQUENCE OF ObjectInstance | A Position's subordinate Physical link connection is a role of a Physical link connection being terminated on this Position. | +| portItemList | SEQUENCE OF ObjectInstance | A Position's subordinate Port item is a role of a Port item being terminated on this Position.
Note that the Position can be on the slot of the shelf. This allows cables to be terminated on the slot of the shelf and not on the card, and thus allows the card to be easily replaceable. | +| position | ObjectInstance | A Position's subordinate Position is a role of another Position that is connected by Cross-coupling or termination to this Position.
Note that the Cross-coupling or termination is assigned no direction. This means, e.g., that if the termination is from a position (i.e., a connector) on a slot in a shelf to a pin group on a block, only the names of the two Positions indicate the direction. | +| trailList | SEQUENCE OF ObjectInstance | A Position's subordinate Trail is a role of a Trail being terminated on this Position. | +| trailMultiplexChannelList | SEQUENCE OF ObjectInstance | A Position's subordinate Trail multiplex channel is a role of a Trail multiplex channel being terminated on this Position. | +| trailSectionList | SEQUENCE OF ObjectInstance | A Position's subordinate Trail section is a role of a Trail section in a Trail. | + +#### 7.3.70.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.71 Protection Group + +#### 7.3.71.1 Definition + +The Protection Group contains zero or more Protection Unit objects for defining a protection switching relationship where one or more standby (i.e., backup) entities provide protection for one or more working (i.e., more regular or preferred) entities. + +The invokeProtection action can be used to request a lockout, a forced switch, or a manual switch (i.e., normal switch) on one or more protectionUnit instances contained in the protectionGroup object. The releaseProtection action can be used to release a lockout, a forced switch, or a manual switch (i.e., normal switch) on one or more protectionUnit instances contained in the protectionGroup object. + +The protectionSwitchReporting notification is emitted from the Protection Group object to report any protection switch events, such as protection switching (forced switch, manual switch, or automatic switch), protection release (release of forced switch, manual switch, or automatic switch), lockout or release of lockout. + +If the attributeValueChangeNotification package is present, then changes to the protectionGroupType attribute, the revertive attribute or the waitToRestoreTime attribute shall cause an attributeValueChange notification to be emitted. + +The protectionGroupType attribute shall have the value 'colon' when more than one Protection Unit is protected. Changing the value of this attribute between 'plus' and 'colon' is allowed when only one + +protected protectionUnit and one protecting Protection Unit are contained by the Protection Group. The change from 'plus' to 'colon' is only allowed if the underlying resources support M:N protection. + +This object class is used for representing a protection system. The invokeProtection action switches always from protected unit to protecting unit. Either all or none of the Protection Unit instances within a Protection Group object shall have the priorityPkg package. It is to be noted that, before the creation of the Protection Group object, the supported by object list (sbol) attribute of a reliable resource such as termination point object may point to an unreliable resource object such as circuit pack. But once the protection group object is created, the sbol attribute would start pointing at the protection group object + +#### 7.3.71.2 Attributes + +Table 128 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|-------------------|----------------|-----------------|------------------|------------------| +| availabilityStatus | M | M | – | – | | +| currentProblemList | O | M | – | – | | +| lockedInCondition | M | M | M | M | | +| operationalState | M | M | – | – | | +| protectionGroupId | M | M | – | – | | +| protectionGroupType | M | M | M | M | | +| revertive | M | M | M | M | | +| supportedByObjectList | M | M | – | – | | +| waitToRestoreTime | M | M | M | M | | + +#### 7.3.71.3 Notifications + +Table 129 + +| Name | Qualifier | Notes | +|---------------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| protectionAlarm | O | | +| protectionSwitchReporting | M | | +| stateChange | M | | + +### 7.3.72 Protection Unit + +#### 7.3.72.1 Definition + +The Protection Unit IOC is used to represent the protected (i.e., working, regular, or preferred) or protecting (i.e., backup or standby) resource in a protection system. Instances of this IOC are instantiated according to the protection schemes adopted by the NE. A Protection Unit instance is deleted when the resource object instance pointed to by the Unreliable Resource Pointer attribute is deleted, and may be created automatically when the associated resource object is created. + +Instances of this IOC may also be created and deleted in order to reflect local modifications in the protection schemes. The `attributeValueChange` notification is used to notify changes of the Reliable Resource Pointer, Protection Status, and Priority attributes. + +#### 7.3.72.2 Attributes + +Table 130 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| priority | O | M | M | M | | +| protecting | M | M | – | – | | +| protectionStatusR1 | M | M | – | – | | +| protectionUnitId | M | M | – | – | | +| reliableResourcePointerR1 | M | M | – | – | | +| unreliableResourcePointerR1 | M | M | – | – | | + +#### 7.3.72.3 Notifications + +Table 131 + +| Name | Qualifier | Notes | +|-----------------------------------|-----------|-------| +| attributeValueChange | O | | + +### 7.3.73 Scan Point + +#### 7.3.73.1 Definition + +The Scan Point IOC is used to monitor external conditions related to the managed element, for that, events of external devices (such as power failure, fire alarm, door open, humidity, etc.) are monitored. Each instance of this object class represents one scan point. + +Environmental alarm will be emitted if a scan point detects an abnormal condition. + +The text message specified in the `externalPointMessage` attribute is to be included in the `additionalText` field of the `environmentalAlarm` notification when an alarm is emitted for the scan point. The severity of such alarms can be configured using the `alarmSeverityAssignmentProfilePointer`. + +The `currentProblemList` represents the current problems of the external entity being monitored, i.e., not current problems with the scan function itself. The probable cause of the `currentProblemList` is by itself not a precise indicator of service affecting alarms (e.g., due to standby resources) and the `serviceAffected` attribute is used as a unifying indicator of service affecting conditions. + +#### 7.3.73.2 Attributes + +Table 132 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| currentProblemList | M | M | – | – | | +| externalPointId | M | M | – | M | | +| externalPointMessage | M | M | M | M | | +| locationName | O | M | M | M | | +| operationalState | M | M | – | – | | +| serviceAffected | M | M | – | – | | +| supportedByObjectList | M | M | – | – | | + +#### 7.3.73.3 Notifications + +Table 133 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | M | | +| environmentalAlarm | M | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | M | | + +### 7.3.74 Service + +#### 7.3.74.1 Definition + +The Service IOC is a class of objects that represent offerings from a provider that supplies specific network functionality to one or more customers. A service may or may not be tariffed. Services may be nested, thereby creating a containment relationship. The Service Type identifies the distinguishing characteristics of the Service. The Supported Service Name List identifies other Services supported by the Service, and the Supported By Object List identifies the objects that support the Service. + +#### 7.3.74.2 Attributes + +Table 134 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| operationalState | O | M | – | – | | +| serviceID | M | M | – | – | | + +**Table 134** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------|-------------------|----------------|-----------------|------------------|------------------| +| serviceType | M | M | M | M | | +| supportedByObjectList | O | M | M | M | | +| supportedServiceNameList | O | M | M | M | | +| usageState | O | M | – | – | | + +#### 7.3.74.3 Notifications + +**Table 135** + +| Name | Qualifier | Notes | +|-----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| qualityOfServiceAlarm | M | | +| stateChange | O | | + +### 7.3.75 Service Access Domain + +#### 7.3.75.1 Definition + +This IOC represents a Service Access Domain consisting of Service Access Groups having similar characteristics (e.g., supporting the same bandwidths). + +#### 7.3.75.2 Attributes + +**Table 136** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aliasName | O | M | – | M | | +| listOfSags | M | M | M | M | | +| providerRequestNumber | M | M | – | – | | +| sadId | M | M | – | M | | +| serviceCustomerContact | M | M | M | M | | +| serviceDescription | O | M | – | M | | +| serviceProviderContact | M | M | – | – | | +| serviceType | M | M | – | M | | + +#### 7.3.75.3 Notifications + +Table 137 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.76 Service Access Group + +#### 7.3.76.1 Definition + +This IOC represents a Service Access Group consisting of Service Access Points having similar characteristics (e.g., supporting the same bandwidths). If the administrative state is locked, then all the SAPs in the SAG are locked + +#### 7.3.76.2 Attributes + +Table 138 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| aliasName | O | M | – | M | | +| listOfSaps | M | M | M | M | | +| sagId | M | M | – | M | | +| sagLocation | M | M | – | M | | + +#### 7.3.76.3 Notifications + +Table 139 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.77 Service Access Equipment View + +#### 7.3.77.1 Definition + +The Service Access Equipment View IOC represents customer-owned equipment that terminates Services. The SC updates information in this IOC to correctly reflect the actual state of the service access equipment in the SC's premises. + +#### 7.3.77.2 Attributes + +Table 140 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| dateOfInstallation | O | M | – | – | | +| equipmentId | M | M | – | M | | +| equipmentManufacturer | O | M | M | M | | +| equipmentType | O | M | M | M | | +| expectedDateOfInstallation | O | M | M | M | | +| listOfSaps | M | M | M | M | | +| locationAddress | M | M | – | M | | +| modelType | O | M | M | M | | +| operationalState | O | M | M | M | | +| procedure | O | M | M | M | | + +#### 7.3.77.3 Notifications + +Table 141 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.78 Service Modify Request + +#### 7.3.78.1 Definition + +This IOC represents SC's request to modify an existing service. It is a superclass from which service-specific subclasses are derived. When changes to the service occur as a result of such a modification request, or for any other reason, the object representing the affected service will issue the appropriate attribute value change notifications. After all the modifications requested by the SC through this object have been resolved, this object will be deleted and a notification of its deletion shall be sent to the SC. + +#### 7.3.78.2 Attributes + +Table 142 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|-------------------|----------------|-----------------|------------------|------------------| +| aliasName | O | M | – | M | | +| availabilityStatus | O | M | – | – | | +| intervalsOfDay | O | M | – | M | | +| providerRequestNumber | M | M | – | – | | +| requestReceptionTime | M | M | – | – | | + +**Table 142** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------|-------------------|----------------|-----------------|------------------|------------------| +| schedulerName | O | M | M | M | | +| serviceCustomerContact | O | M | – | M | | +| serviceInstance | M | M | – | M | | +| serviceRequestState | M | M | – | – | | +| weekMask | O | M | – | M | | + +#### 7.3.78.3 Notifications + +**Table 143** + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.79 Service Request History Record + +#### 7.3.79.1 Definition + +This IOC represents a history record of the content of a service (update) request by the SC to a service request. The Service Request History Record is created when the service customer issues an updateService towards a Current Service Request (and subclasses) and contains a record of the attribute values specified in the request. The service provider also creates a Service Request History Record of the initial service request values (when the SC creates the currentServiceRequest). + +#### 7.3.79.2 Attributes + +**Table 144** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aliasName | O | M | – | – | | +| intervalsOfDay | O | M | – | – | | +| requestReceptionTime | M | M | – | – | | +| requestSequenceNumber | M | M | – | – | | +| requestedInitialServiceAdministrativeState | O | M | – | – | | +| schedulerName | O | M | – | – | | +| serviceAvailabilityDate | O | M | – | – | | +| serviceCustomerContact | O | M | – | M | | +| serviceDescription | O | M | – | – | | +| serviceTerminationDate | O | M | – | – | | +| serviceType | O | M | – | – | | +| weekMask | O | M | – | – | | + +#### 7.3.79.3 Notifications + +Table 145 + +| Name | Qualifier | Notes | +|----------------|-----------|-------| +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.80 Site Relationship + +#### 7.3.80.1 Definition + +A Site relationship is a combination of exactly two Cross-coupling sites. + +The two Cross-Coupling Sites may be different or the same. The last case is used in case of identification of internal Trails within a Cross-Coupling Site. The scope of the SiteRelationship identifier may be global in case of international Trails, which means that all fields are required to be filled in. The scope may be a Country in case of inter-operator Trails within that Country, which means that the two countryCodes may be left out. The scope may be the Operator in case of intra-operator Trails, which means that the two iccs may be left out, and only the two Cross-Coupling Site Identifiers are filled in. + +A Cross-Coupling Site localIdentifier is specific to an Operator, country or region. Such use of localIdentifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400]. Aliases of Cross-Coupling Site identifiers are not permitted for communication between Operators of different Countries. However, Operators may exchange localIdentifiers that are local to a specific Operator, country or region. + +#### 7.3.80.2 Attributes + +Table 146 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| localIdentifier | M | M | – | – | | +| a-EndSite | M | M | – | – | | +| b-EndSite | M | M | – | – | | + +**Table 147** + +| Name | Type | Description | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| identifier |
 SiteRelationshipId ::= SEQUENCE {     a-End  EndSiteId,     b-End  EndSiteId } EndSiteId ::= SEQUENCE {     countryCode  CountryCode,     icc          ICC,     site         SiteId } CountryCode ::= String (SIZE 3) ICC ::= String(SIZE 1..6) SiteId ::= String 
|

An Identifier of a Site relationship is an attribute group that uniquely identifies the Site relationship. The scope of the identification may be global in case of international Trails, which means that all fields are required to be filled in. The scope may be a Country in case of inter-operator Trails within that Country, which means that the two Country Codes may be left out. The scope may be the Operator in case of intra-operator Trails, which means that the two ICCs may be left out, and only the two Cross-coupling site Identifiers are filled in. This last case is outside the scope of this Recommendation.

| +| localIdentifier |
 SiteRelationshipLocalId ::= SEQUENCE {     a-End  EndSiteLocalId,     b-End  EndSiteLocalId } EndSiteLocaleId ::= String 
|

The Local identifier of a Site relationship is an attribute group that uniquely identifies the Site relationship.

A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400].

Aliases of Cross-coupling site Identifiers are not permitted for communication between Operators of different Countries. However, Operators may exchange Local identifiers that are local to a specific Operator, country or region.

| +| a-EndSite | EndSiteId |

The A-end site is a role of the Cross-coupling site having the distinguished name that comes first in the alphabet. The distinguished name consists of Country Code, ICC and Cross-coupling site Identifier, in that sequence.

| +| b-EndSite | EndSiteId |

The B-end site is a role of the Cross-coupling site having the distinguished name that comes last in the alphabet. The distinguished name consists of Country Code, ICC and Cross-coupling site Identifier, in that sequence.

| + +#### 7.3.80.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.81 Software + +#### 7.3.81.1 Definition + +The Software IOC is a class of objects that represent logical information stored in equipment, including programs and data tables. + +Software may be nested within other software, thereby creating a containment relationship. + +#### 7.3.81.2 Attributes + +Table 148 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| affectedObjectList | O | M | – | – | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| operationalState | O | M | – | – | | +| softwareId | M | M | – | M | | +| userLabel | O | M | M | M | | +| vendorName | O | M | M | M | | +| version | O | M | M | M | | + +#### 7.3.81.3 Notifications + +Table 149 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | O | | +| objectDeletion | O | | +| processingErrorAlarm | O | | +| stateChange | O | | + +### 7.3.82 Sub Network + +#### 7.3.82.1 Definition + +The Sub Network IOC represents logical collections of network termination points. + +If present, the attribute containedSubNetworkList will be null if there are no contained Subnetworks. + +The attribute containedInSubNetworkList will also be null if there are no containing (parent) Subnetworks. + +#### 7.3.82.2 Attributes + +Table 150 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| availabilityStatus | O | M | – | – | | +| containedAccessGroupList | O | M | M | M | | +| containedInSubNetworkList | O | M | M | M | | +| containedLinkEndList | O | M | M | M | | +| containedLinkList | O | M | M | M | | +| containedNetworkTPList | O | M | M | M | | +| containedSubNetworkList | O | M | M | M | | +| linkPointerList | O | M | – | – | | +| operationalState | O | M | – | – | | +| signalId | M | M | – | M | | +| subNetworkId | M | M | – | – | | +| supportedByObjectList | O | M | M | M | | +| usageState | O | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.82.3 Notifications + +Table 151 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | M | | +| objectDeletion | M | | +| stateChange | O | | + +### 7.3.83 Sub Network Connection + +#### 7.3.83.1 Definition + +The Subnetwork Connection IOC is a class of objects that associate the network termination point object identified in the A end attribute and the network termination point object(s) listed in the Z end attribute of this managed object. + +The Subnetwork Connection may be set up between network termination points (or groups of network termination points) specified explicitly, or implicitly between managed objects acting as containers of network termination point managed object instances from which any idle network termination point or group may be used. + +If the managed objects listed in the A End and Z End attributes represent groups, the nth element of the A end group is related to the nth element of every Z end group (for every n). There shall be n elements in each group involved in the Subnetwork Connection. For a group with n elements, the Signal Id shall be taken to be a bundle of n times the characteristic information of the individual elements, all of which are the same. + +A point-to-point unidirectional Subnetwork Connection can be established between one of Network connection termination point sink, Network connection termination point bidirectional, Network trail termination point source, Network trail termination point bidirectional or Network group termination point; and one of Network connection termination point source, Network connection termination point bidirectional, Network trail termination point sink, Network trail termination point bidirectional or Network group termination point. + +A point-to-point bidirectional Subnetwork Connection can be established between one of Network connection termination point bidirectional, Network trail termination point bidirectional or Network group termination point; and one of Network connection termination point bidirectional, Network trail termination point bidirectional or Network group termination point. + +A point-to-multipoint unidirectional Subnetwork Connection can be established between one of Network connection termination point sink, Network connection termination point bidirectional, Network trail termination point source, Network trail termination point bidirectional or Network group termination point; and a set whose members are Network connection termination point sources, Network connection termination point bidirectionals, Network trail termination point sinks, Network trail termination point bidirectional or Network group termination point. + +A point-to-multipoint bidirectional Subnetwork Connection can be established between one of Network connection termination point bidirectional, Network trail termination point bidirectional or Network group termination; and a set whose members are Network connection termination point bidirectionals, Network trail termination point bidirectionals or Network group termination points. The componentPackage is supported where the Subnetwork Connection is made up of a number of component Subnetwork Connections, and Link Connections, within the same layer. + +#### 7.3.83.2 Attributes + +Table 152 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEndNetworkTPList | M | M | – | M | | +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | +| componentPointers | O | M | – | – | | +| compositePointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| directionality | M | M | – | – | | +| operationalState | O | M | – | – | | +| protected | O | M | – | M | | +| qualityOfConnectivityService | O | M | – | – | | +| signalId | M | M | – | M | | +| supportedByObjectList | O | M | M | M | | +| relatedRoutingProfile | O | M | – | – | | +| subNetworkConnectionId | M | M | – | – | | +| userLabel | O | M | M | M | | +| zEndNetworkTPList | M | M | – | M | | + +#### 7.3.83.3 Notifications + +Table 153 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.84 Termination + +#### 7.3.84.1 Definition + +A Trail's subordinate Termination indicates termination in a Cross-coupling site. A Trail will normally have two Terminations. + +#### 7.3.84.2 Attributes + +Table 154 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------|-------------------|----------------|-----------------|------------------|------------------| +| direction | M | M | – | – | | +| cross-couplingSite | M | M | – | – | | + +Table 155 + +| Name | Type | Description | +|--------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| direction | IA5String
(WITH COMPONENTS {"S", "R", "T"})(SIZE(1)) | A Termination's Direction indicates transmission direction of the Trail. The Direction can be S(ender), R(eceiver) or T(wo-way). If the Direction is S(ender), then the Direction of the other Termination is R(eceiver) and vice versa. If the D(irection) is T(wo-way), then the Direction of the other Termination is T(wo-way), as well. | +| cross-couplingSite | ObjectInstance | A Termination's subordinate Cross-coupling site is a role of a Cross-coupling site. A Termination has just one Cross-coupling site, and a Cross-coupling site may have one or two Terminations for a Trail. | + +#### 7.3.84.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.85 Termination Point + +#### 7.3.85.1 Definition + +This IOC represents the termination of a transport entity, such as a trail or a connection. The characteristic information attribute is used to identify equivalence between subclasses of termination points in order to determine whether cross-connection or connectivity is possible. The operational state reflects the perceived ability to generate and/or receive a valid signal. Subclasses + +of termination point shall specify the attributes and states for which attribute value change and state change notifications will be generated. + +#### 7.3.85.2 Attributes + +Table 156 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| networkLevelPointer | O | M | M | M | | +| operationalState | O | M | – | – | | +| supportedByObjectList | M | M | – | – | | + +#### 7.3.85.3 Notifications + +Table 157 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.86 Termination Point Pool (tpPool) + +#### 7.3.86.1 Definition + +The TerminationPoint Pool IOC represents a set of termination points or GTPs that are used for some management purpose, such as routing. A termination point that is a member of a GTP cannot be a member of a tpPool independent of the remainder of the GTP. + +#### 7.3.86.2 Attributes + +Table 158 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------|-------------------|----------------|-----------------|------------------|------------------| +| connectedTpCount | M | M | – | – | | +| idleTpCount | M | M | – | – | | +| totalTpCount | M | M | – | – | | +| tpPoolId | M | M | – | – | | +| tpsInTpPoolList | M | M | – | – | | + +#### 7.3.86.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.87 Top + +For further study. + +### 7.3.88 Topological Link + +#### 7.3.88.1 Definition + +The Topological Link IOC represents a link in a client layer provided by one and only one server trail. The serverTrail attribute is a pointer to the trail in the server layer network domain that supports this topological link. The serverTrail attribute may be null if the trail in the server layer network domain that supports this topological link is not assigned. + +The use made of the individual attributes and notifications is detailed below: + +- total link capacity: the total number of Link Connections or bandwidth available; +- maximum link connection count: the maximum number of link connections available on connection with flexible bandwidth management; +- potential link capacity: the number of potential Link Connections or potential bandwidth that could be provisioned; +- provisioned link capacity: the number of provisioned Link Connections or the provisioned bandwidth; +- provisioned link connection count: the number of link connections assigned using flexible bandwidth management. + +An attribute value change notification shall be emitted when the value of the totalLinkCapacity, maximumLinkConnectionCount, potentialLinkCapacity, provisionedLinkCapacity or provisionedLinkConnectionCount is changed. + +#### 7.3.88.2 Attributes + +Table 159 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|--------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| aEnd | M | M | – | M | | +| availableLinkCapacity | M | M | – | – | | +| directionality | M | M | – | – | | +| linkId | M | M | – | – | | +| maximumLinkConnectionCount | O | M | – | – | | +| potentialLinkCapacity | O | M | – | – | | +| provisionedLinkCapacity | O | M | – | – | | +| provisionedLinkConnectionCount | O | M | – | – | | +| serverTrail | M | M | – | – | | +| signalId | M | M | – | M | | +| totalLinkCapacity | O | M | – | – | | +| usageCost | O | M | – | – | | +| userLabel | O | M | M | M | | +| zEnd | M | M | – | M | | + +#### 7.3.88.3 Notifications + +Table 160 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.89 Topological Link End + +#### 7.3.89.1 Definition + +The Topological Link End object class represents the end of a topological link when viewed from the point perspective. The Topological Link End object is related to one and only one network TTP in the server layer. + +The use made of the individual attributes and notifications is detailed below: + +- total link end capacity: the total number of network CTPs or the bandwidth available; +- maximum network CTP count: the maximum number of network CTPs available at the LinkEnd when using flexible bandwidth management; +- potential link end capacity: the number of potential network CTPs or potential bandwidth that could be provisioned; +- provisioned link end capacity: the number of provisioned network CTPs or the provisioned bandwidth; +- provisioned network CTP count: the number of network CTP assigned to the link end when using flexible bandwidth management. + +An attribute value change notification shall be emitted when the value of the totalLinkEndCapacity, maximumNetworkCTPCount, potentialLinkEndCapacity, provisionedLinkEndCapacity or provisionedNetworkCTPCount is changed. + +#### 7.3.89.2 Attributes + +Table 161 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------------|-------------------|----------------|-----------------|------------------|------------------| +| availableLinkEndCapacity | M | M | – | – | | +| containedInSubNetworkList | O | M | M | M | | +| linkEndId | M | M | – | – | | +| linkPointer | M | M | – | – | | +| maximumNetworkCTPCount | O | M | – | – | | +| pointDirectionality | M | M | – | – | | +| potentialLinkEndCapacity | O | M | – | – | | +| provisionedLinkEndCapacity | O | M | – | – | | +| provisionedNetworkCTPCount | O | M | – | – | | +| serverTTPPointer | M | M | – | – | | + +**Table 161** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| signalId | M | M | – | – | | +| totalLinkEndCapacity | O | M | – | – | | +| userLabel | O | M | M | M | | + +#### 7.3.89.3 Notifications + +**Table 162** + +| Name | Qualifier | Notes | +|----------------------|------------------|--------------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | + +### 7.3.90 Trail + +#### 7.3.90.1 Definition + +The Trail IOC is responsible for the integrity of transfer of characteristic information from one or more other layer networks. + +A Trail is composed of two or more Network Trail Termination Points and one or more Link Connections or Subnetwork Connections, and associated Network Connection Termination Points. + +A point-to-point unidirectional Trail can be established between a Network TTP source or Network TTP bid; and a Network TTP sink or Network TTP bid. + +A point-to-point bidirectional Trail can be established between a Network TTP bid; and a Network TTP bid. For all types of Trail, the termination point(s) pointed to by the A End attribute is related to the network termination point(s) pointed to by the Z End attribute in such a way that traffic can flow between the network termination points represented by these managed objects in a unidirectional or bidirectional manner as indicated by the directionality attribute. + +The layerConnectionList attribute, when present, lists the subnetwork connections and link connections (in the same layer) which compose the trail. This represents a single partitioned view of the decomposition of a trail into its component subnetwork connections and link connections. + +#### 7.3.90.2 Attributes + +**Table 163** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|--------------------------|-----------------------|------------------------|-------------------------|-------------------------| +| aEndNetworkTPTList | M | M | – | M | | +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| availabilityStatus | O | M | – | – | | + +**Table 163** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| clientLinkConnectionPointerList | O | M | – | – | | +| clientLinkPointerList | O | M | – | – | | +| connectionList | O | M | – | M | | +| currentProblemList | O | M | – | – | | +| directionality | M | M | – | – | | +| operationalState | O | M | – | – | | +| protected | O | M | – | M | | +| qualityOfConnectivityService | O | M | – | – | | +| signalId | M | M | – | M | | +| supportedByObjectList | O | M | M | M | | +| trafficDescriptor | O | M | M | M | | +| trailId | M | M | – | M | | +| userLabel | O | M | M | M | | +| zEndNetworkTPList | M | M | – | M | | + +#### 7.3.90.3 Notifications + +**Table 164** + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.91 Trail [ITU-T M.1401] + +#### 7.3.91.1 Definition + +A Trail provides a transport of signals between two Cross-coupling sites. + +The Cross-Coupling Site terminations of a Trail may be located in Cross-Coupling Sites within different Countries, by different Operators, the same Operator, or within one and the same Cross-Coupling Site – in case of internal Trails. Also, the Trail may be terminated at the customer premises, i.e., outside the Cross-Coupling Site. + +The Trail may be routed via several connected Cross-Coupling Sites. The routing and involved cross-couplings of the Trail are established on a semi-permanent basis based on a coupling order. However, switching to alternate Trails may be provided dynamically. + +A Trail may be routed on other Trails, e.g., each Operator may define a separate Trail identifier for the routing within its domain, while a common inter-operator Trail is defined for the total routing. Also, the detailed routing within a Cross-Coupling Site may be defined in a separate internal Trail. + +A Trail may be involved as a part of a multipoint Trail, e.g., a ring. In this case, no Trail should be defined to pass the branching points. However, Trails routed on subordinate Trail multiplex channels may be routed through the branching points. + +The Trail may be established as a means to configure the Operator's network or be established to provide a service or product to a customer. + +The Trail may provide: + +- a transmission system functionality, e.g., a coax system between two pieces of line termination equipments; +- a multiplex group capacity, e.g., an SDH link; +- a reserve functionality, e.g., an alternate routing for a multiplex group; +- a traffic capacity, e.g., for routing of traffic between two (neighbouring) Exchanges; +- a user functionality, e.g., a leased line between two customers. + +Note that Trails are semi-permanent, which means that Trails do not comprise temporary dialled circuits, which directs traffic over a series of Trails. Also, Trails are not permanent cable resources between two (neighbouring) junction boxes. Dialled circuits are switched dynamically, and cable resources are installed permanently. Dialled circuits are established on the basis of a call attempt per call, per file transfer or per packet and are not established based on a coupling order. Cable resources are established based on construction plans and not on coupling orders. + +The identifier of the Trail's superior Site Relationship is independent of the identifiers of the Exchanges, Locations or Equipments in which the Trail is terminated. Note also that the identifier of the superior Site Relationship is independent of traffic or transmission direction of the Trail. + +- Size is a 5-character field of decimal digits adjusted to the right without leading zeros. +- Unit is given in an alphanumeric 4-character field and is adjusted to the left. +- This field must be provided if size is provided, or size may be a multiple of a default unit. +- Signalling is a 20-character alphanumeric field adjusted to the left. The permissible values are for further study. +- The priority field length is 1 character, and the permissible values are 1, 2 and 3, or the field may be left blank. +- The hours specified by limit are counted from the moment when the limit is given. The field length is 2 decimal digits, with leading zeros, or the field may be left blank. + +When transferred between time zones, the deadline shall be given in standard GMT. When communicating within a time zone, two operators may agree to use local time. Each of the four fields (i.e., day, month, year and hour) is given by 2 decimal numbers with leading zeros. Either all fields are filled in or all are left blank. The fields may be calculated automatically from limit and entering time when entered, be transformed to GMT when transferred and recalculated to local time at the receiving end if the communicating users are made aware of this conversion. + +- Deadline has the substructure (day, month, year and hour) and the fields may be separated by punctuation marks (.). +- A localIdentifier has up to 26 alphabetic and/or numeric characters. Use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400]. + +#### 7.3.91.2 Attributes + +Table 165 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------------------|-------------------|----------------|-----------------|------------------|------------------| +| bandwidth | M | M | – | – | | +| identifier | M | M | – | – | | +| localIdentifier | M | M | – | – | | +| signalling | M | M | – | – | | +| urgency | M | M | – | – | | +| associationList | M | M | – | – | | +| controllerList | M | M | – | – | | +| multipointTrail | M | M | – | – | | +| position | M | M | – | – | | +| routingTrailSection | M | M | – | – | | +| subordinateAssociationList | M | M | – | – | | + +Table 166 + +| Name | Type | Description | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bandwidth |
 TrailBandwidth ::= SEQUENCE {   actual  Bandwidth,   maximum Bandwidth, } Bandwidth ::= SEQUENCE {   size  String(SIZE (5)),   unit  String(SIZE (5)) }           
|

This attribute group defines the capacity of the medium.

It can provide the actual bandwidth allocated to this trail and the maximum available capacity of the medium.

For either actual or maximum bandwidth, two fields are contained:

  • – Size: the Size of the bandwidth as a multiple of the unit being given in the Unit field. This is a 5-character field of decimal digits adjusted to the right without leading zeros.
  • – Unit: the unit being used to give the Size of the bandwidth. The Unit is given in an alphanumeric 4-character field and is adjusted to the left. (NOTE – This field must be provided if Size is provided, or Size may be a multiple of a default unit.)
| +| identifier | String |

The Identifier of a Trail uniquely identifies the Trail within the Site relationship.

Note that the Identifier of the Trail's superior Site relationship is independent of the identifiers of the Exchanges, Locations or Equipments in which the Trail is terminated.

Note also that the Identifier of the superior Site relationship is independent of traffic or transmission direction of the Trail.

| + +**Table 166** + +| Name | Type | Description | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| localIdentifier | String(SIZE(1..26)) | An identifier of a Trail that is unique within an Operator, having up to 26 alphabetic and/or numeric characters. A Local identifier is specific to an Operator, country or region. Such use of Local identifiers would be subject to national regulation and/or bilateral agreement between Operators, as stated in [ITU-T M.1400]. | +| signalling | String(SIZE(20)) | This attribute indicates the signalling system or signalling type being used on the Trail.
The attribute is a 20-character alphanumeric field adjusted to the left. The permissible values are for further study. | +| urgency | Urgency ::= SEQUENCE {
deadline DateAndTime,
limit
String(SIZE(2)),
priority IA5String
}
DateAndTime ::= SEQUENCE {
date    Date,
time    Time
}
Date ::= SEQUENCE {
day    String(SIZE(2)),
month
String(SIZE(2)),
year    String(SIZE(2))
}
Time ::= SEQUENCE {
hour    String(SIZE(2))
} | Urgency defines priority of restoration and may define a deadline for the restoration.
Urgency has the following three fields:
– Deadline: defines date and hour for completion of the restoration.
When transferred between time zones, the Deadline shall be given in standard GMT.
When communicating within a time zone, two operators may agree to use local time.
Each of the four fields is given by 2 decimal numbers with leading zeros. Either all fields are filled in or all are left blank.
The fields may be calculated automatically from Limit and entering time when entered, be transformed to GMT when transferred and recalculated to local time at the receiving end if the communicating users are made aware of this conversion.
The attribute has the substructure given below, and the fields may be separated by punctuation marks (,).
– Limit: defines number of hours for the restoration to be completed. The hours are counted from the moment when the Limit is given. The field length is 2 decimal digits, with leading zeros, or the field may be left blank.
– Priority: defines priority classes for restoration. The field length is 1 character, and the permissible values are 1, 2 and 3, or the field may be left blank. | +| associationList | SEQUENCE OF ObjectInstance | A Trail's subordinate Association is a role of an Association. A Trail may be involved in several Associations. | +| controllerList | SEQUENCE OF ObjectInstance | A Trail's subordinate Controller is a role of an Operator. A Trail may have several Controllers listed in falling priority. Note that Controller indicates responsibility for maintenance and not ownership. | +| multipointTrail | ObjectInstance | A Trail's subordinate Multipoint trail is a role of a Multipoint trail that is supported by the Trail. | + +**Table 166** + +| Name | Type | Description | +|----------------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| position | ObjectInstance | A Trail's subordinate Position is a role of a Position that terminates the Trail. | +| routingTrailSection | ObjectInstance | A Trail's subordinate Routing trail section is a role of a Trail section in the routing of another Trail, which is routed on the current Trail. | +| subordinateAssociationList | SEQUENCE OF ObjectInstance | A Trail's subordinate Subordinate association is a role of an Association. A Trail may have several Subordinate associations. | + +#### 7.3.91.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.92 Trail Multiplex Channel + +#### 7.3.92.1 Definition + +A Trail may be split into several parallel Trail multiplex channels. The Trail multiplex channels in a Trail may have different capacities. All Trail multiplex channels in a Trail have the same routing, as the routing is assigned to Trails only, and not to Trail multiplex channels. + +Each Trail multiplex channel is terminated in the same multiplex Equipment item as the superior Trail. The Trail may be terminated at the higher capacity side of the Equipment item, while the Trail multiplex channels are terminated at the lower capacity side. Also, Trail multiplex channels and Trails may be terminated at Connection termination points or Trail termination points inside the Equipment item, as may be the case in SDH network matrixes. + +Trail multiplex channels may be implemented by different technologies, like frequency multiplexing, pulse code multiplexing, etc. + +#### 7.3.92.2 Attributes + +**Table 167** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|----------------|-------------------|----------------|-----------------|------------------|------------------| +| number | M | M | – | – | | +| position | M | M | – | – | | +| trailSection | M | M | – | – | | + +**Table 168** + +| Name | Type | Description | +|--------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| number | String | Trail multiplex channels are numbered within their superior Trail.
Note that this naming scheme is different from naming of linkConnections within links within layerNetworkDomains. However, the scheme does not prohibit definition of a Trail for each link, as long as all linkConnections have the same routing. | +| position | ObjectInstance | A Trail multiplex channel's subordinate Position is a role of a Position on which the Trail multiplex channel is terminated. | +| trailSection | ObjectInstance | A Trail multiplex channel's subordinate Trail section is a role of a Trail section in the routing of the Trail. | + +#### 7.3.92.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.93 Trail Section + +#### 7.3.93.1 Definition + +A Trail section is any element that makes up the routing of a Trail [ITU-T M.1401]. + +Normally, Trail sections are connected in series to define the routing. + +However, a Trail section may also define parallel elements. + +Example of a two-pair circuit: The Trail is defined as a series of Trail sections, each of these Trail sections is split into two parallel Trail sections, representing individual cable pair. + +Example of diverse routing of a two-pair circuit: The Trail is split into two parallel Trail sections representing a circuit pair, each Trail section is defined as a series of Trail sections, representing individual cable pairs. A more comprehensive registration can be obtained by letting the two parallel Trail sections represent one individual Trail each, with separate Identifiers, each of these Trails is defined as a series of Trail sections, representing individual cable pairs. + +There is no defined hierarchy between Trail sections by containment or references. However, the subordinate Trail sections are immediately following their superior Trail section, and information in each Trail section indicates if they represent an individual fibre, a pair, or a set of pairs. + +Users may do both selection and projection of Trail sections within a Trail. Selection means that only Trail sections within a geographical area may be listed. Projection means that only Trail sections connecting different Cross-coupling sites may be listed, etc. + +#### 7.3.93.2 Attributes + +**Table 169** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------|-------------------|----------------|-----------------|------------------|------------------| +| identifier | M | M | – | – | | +| physicalLinkConnection | M | M | – | – | | +| portItem | M | M | – | – | | +| position | M | M | – | – | | +| trail | M | M | – | – | | +| trailMultiplexChannel | M | M | – | – | | + +**Table 170** + +| Name | Type | Description | +|------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| identifier | String | A Trail section may have an Identifier that uniquely identifies the Trail section within the Trail. | +| physicalLinkConnection | ObjectInstance | A Trail section's subordinate Physical link connection is a role of a Physical link connection that is included in the routing of the Trail. | +| portItem | ObjectInstance | A Trail section's subordinate Port item is a role of a Port item that is included in the routing of the Trail. | +| position | ObjectInstance | A Trail section's subordinate Position is a role of a Position that is included in the routing of the Trail. | +| trail | ObjectInstance | A Trail section's subordinate Trail is a role of a Trail that is included in the routing of the Trail. | +| trailMultiplexChannel | ObjectInstance | A Trail section's subordinate Trail multiplex channel is a role of a Trail multiplex channel that is included in the routing of the Trail. | + +#### 7.3.93.3 Notifications + +There are no notifications defined for this IOC. + +### 7.3.94 Trail Termination Point Bidirectional + +#### 7.3.94.1 Definition + +This managed object represents a termination point where a trail is both originated and terminated, i.e., the combined behaviour of the trailTerminationPointSink and the trailTerminationPointSource object classes. + +#### 7.3.94.2 Attributes + +**Table 171** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| downstreamConnectivityPointer | M | M | – | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | M | M | – | – | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | – | | +| tTPId | O | M | – | M | | +| upstreamConnectivityPointer | M | M | – | M | | + +#### 7.3.94.3 Notifications + +Table 172 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.95 Trail Termination Point Sink + +#### 7.3.95.1 Definition + +The Trail Termination Point Sink IOC represents a termination point where a trail is terminated. It represents the access point in a layer network which is a focus for both the trail relationship and the client/server relationship: + +- The operational state reflects the perceived ability to receive a valid signal. If the termination point detects that a signal received has failed or it is unable to process the incoming signal, then the operational state will have the value disabled. +- When the administrative state is locked, the termination point is administratively removed from service. When the administrative state is unlocked, the termination point is administratively in service. Changes to the administrative state have no effect on the connectivity pointer. +- A change in the operational state shall cause a state change notification. If administrative state is present in an instance of trail termination point sink class, it shall not emit a state change notification. However, subclasses of trail termination point sink class may modify this behaviour to require this notification. +- Subclasses of trail termination point sink shall specify the attributes for which attribute value change notifications should be generated. +- The upstream connectivity pointer attribute points to the termination point managed object, within the same managed element, that sends information (traffic) to this termination point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Connection Termination Point Sink or Bidirectional (single or a concatenated sequence) or Trail Termination Point Source or Bidirectional. + +#### 7.3.95.2 Attributes + +Table 173 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | + +**Table 173** + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|-----------------------------|-------------------|----------------|-----------------|------------------|------------------| +| networkLevelPointer | O | M | M | M | | +| operationalState | M | M | – | – | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | – | | +| tTPId | O | M | – | M | | +| upstreamConnectivityPointer | M | M | – | M | | + +#### 7.3.95.3 Notifications + +**Table 174** + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.96 Trail Termination Point Source + +#### 7.3.96.1 Definition + +The Trail Termination Point Source IOC represents a termination point where a trail is originated. It represents the access point in a layer network which is a focus for both the trail relationship and the client/server relationship: + +- The operational state reflects the perceived ability to generate a valid signal. If the termination point detects that a valid signal cannot be generated, then the operational state will have the value disabled. +- When the administrative state is locked, the termination point is administratively removed from service. When the administrative state is unlocked, the termination point is administratively in service. Changes to the administrative state have no effect on the connectivity pointer. +- A change in the operational state shall cause a state change notification. If administrative state is present in an instance of trail termination point source class, it shall not emit a state change notification. However, subclasses of trail termination point source class may modify this behaviour to require this notification. +- Subclasses of trail termination point source shall specify the attributes for which attribute value change notifications should be generated. +- The downstream connectivity pointer attribute points to the termination point managed object, within the same managed element, that receives information (traffic) from this termination point at the same layer, or is null. The referenced object shall be an instance of one of the following classes or its subclasses: Connection Termination Point Source or Bidirectional (single or a concatenated sequence or a set if connected to more than one connection termination point source objects) or Trail Termination Point Sink or + +Bidirectional (single or a set if connected to more than one trail termination point sink objects). + +#### 7.3.96.2 Attributes + +Table 175 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|---------------------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | O | M | M | M | | +| alarmSeverityAssignmentProfilePointer | O | M | M | M | | +| alarmStatus | O | M | – | – | | +| characteristicInformation | O | M | – | M | | +| crossConnectionObjectPointer | O | M | – | – | | +| currentProblemList | O | M | – | – | | +| downstreamConnectivityPointer | M | M | – | M | | +| networkLevelPointer | O | M | M | M | | +| operationalState | M | M | – | – | | +| supportableClientList | O | M | – | M | | +| supportedByObjectList | M | M | – | – | | +| tTPId | O | M | – | M | | + +#### 7.3.96.3 Notifications + +Table 176 + +| Name | Qualifier | Notes | +|----------------------|-----------|-------| +| attributeValueChange | O | | +| communicationsAlarm | O | | +| objectCreation | O | | +| objectDeletion | O | | +| stateChange | O | | + +### 7.3.97 Transport Service + +#### 7.3.97.1 Definition + +This IOC represents a transport service that cannot be instantiated; service-specific subclasses of this class can be instantiated. + +Values of attributes of subclasses of this IOC can be set through management operations or through the creation of an instance of a service-specific subclass of the Service Modify Request IOC. + +If an attribute is supported by the SLA, and it can be set by the SC, and the SC has not specified its value in the service request, then it shall have its default value when this MO is instantiated. + +#### 7.3.97.2 Attributes + +Table 177 + +| Attribute Name | Support Qualifier | Read Qualifier | Write Qualifier | Create Qualifier | Requirements IDs | +|------------------------|-------------------|----------------|-----------------|------------------|------------------| +| administrativeState | M | M | M | M | | +| aliasName | O | M | – | M | | +| availabilityStatus | O | M | – | – | | +| bandwidth | M | M | M | M | | +| intervalsOfDay | O | M | M | M | | +| operationalState | M | M | – | – | | +| schedulerName | O | M | – | – | | +| serviceCustomerContact | M | M | M | M | | +| serviceDescription | O | M | – | M | | +| serviceID | M | M | – | M | | +| serviceProviderContact | M | M | – | – | | +| serviceTerminationDate | M | M | M | M | | +| weekMask | O | M | M | M | | + +#### 7.3.97.3 Notifications + +Table 178 + +| Name | Qualifier | Notes | +|-----------------------|-----------|-------| +| attributeValueChange | M | | +| objectCreation | M | | +| objectDeletion | M | | +| qualityOfServiceAlarm | M | | +| stateChange | M | | + +## 7.4 Information relationship definitions + +| Relationship | Support Qualifier | Requirement IDs | +|-----------------------------------------------------|-------------------|-----------------| +| Relation-AbstractLink-a_EndofLink | M | | +| Relation-AbstractLink-z_EndofLink | M | | +| Relation-AbstractLinkEnd-AbstractLink | M | | +| Relation-AccessGroup-AbstractLink | O | | +| Relation-AccessGroup-FlowPointPoolLink | O | | +| Relation-AccessGroup-NetworkTTP | M | | +| Relation-AccessGroup-FlowTerminationPoint | M | | +| Relation-Association-superior_Trail | O | | +| Relation-Association-Trail | M | | +| Relation-CircuitPack-AlarmSeverityAssignmentProfile | M | | + +| Relationship | Support Qualifier | Requirement IDs | +|-------------------------------------------------------------|--------------------------|------------------------| +| Relation-CircuitPack-Trail | O | | +| Relation-ComponentItem-EquipmentIdentity | M | | +| Relation-ComponentItem-Location | M | | +| Relation-Connection-client_Trail | O | | +| Relation-Connection-server_Trail | O | | +| Relation-ConnectionlessPoint-AlarmSeverityAssignmentProfile | O | | +| Relation-ConnectionlessPoint-ManagedEntity | M | | +| Relation-ConnectionlessTrail-AlarmSeverityAssignmentProfile | O | | +| Relation-ConnectionlessTrail-FlowTerminationPointSink | M | | +| Relation-ConnectionlessTrail-FlowTerminationPointSource | M | | +| Relation-ConnectionTerminationPointSink-TerminationPoint | M | | +| Relation-ConnectionTerminationPointSource-TerminationPoint | M | | +| Relation-CrossConnection-from_TP_or_GTP | M | | +| Relation-CrossConnection-to_TP_or_GTP | M | | +| Relation-CrossCouplingSite-Operator | M | | +| Relation-CrossCouplingSite-GeographicalArea | M | | +| Relation-Equipment-AlarmSeverityAssignmentProfile | O | | +| Relation-Equipment-ManagedEntity-1 | O | | +| Relation-Equipment-ManagedEntity-2 | M | | +| Relation-EquipmentHolder-Software | O | | +| Relation-EquipmentItem-EquipmentIdentity | M | | +| Relation-EquipmentItem-Location | M | | +| Relation-Exchange-EquipmentItem | M | | +| Relation-ExternalPoint-ManagedEntity | M | | +| Relation-Fabric-ManagedEntity | M | | +| Relation-FlowDomain-AccessGroup | O | | +| Relation-FlowDomain-ConnectionlessPoint | O | | +| Relation-FlowDomain-FlowDomain | O | | +| Relation-FlowDomain-FlowPointPool | O | | +| Relation-FlowDomain-FlowPointPoolLink-1 | O | | +| Relation-FlowDomain-FlowPointPoolLink-2 | O | | +| Relation-FlowDomain-ManagedEntity | O | | +| Relation-FlowDomainFragment-input_ConnectionlessPoint | M | | +| Relation-FlowDomainFragment-output_ConnectionlessPoint | M | | +| Relation-FlowPoint-FlowTerminationPoint | O | | +| Relation-FlowPointPool-FlowPoint | M | | +| Relation-FlowPointPool-FlowPointPoolLink | M | | +| Relation-FlowPointPool-GenericTransportTTP | O | | +| Relation-FlowPointPool-ManagedEntity | O | | +| Relation-FlowPointPoolLink-AlarmSeverityAssignmentProfile | O | | + +| Relationship | Support Qualifier | Requirement IDs | +|--------------------------------------------------------------|-------------------|-----------------| +| Relation-FlowPointPoolLink-a_EndofFPPLink | M | | +| Relation-FlowPointPoolLink-z_EndofFPPLink | M | | +| Relation-FlowPointPoolLink-ConnectionlessTrail | O | | +| Relation-FlowPointSink-FlowPointSource | M | | +| Relation-FlowPointSink-FlowTerminationPointSink | M | | +| Relation-FlowTerminationPointSource-FlowPointSource | M | | +| Relation-FlowTerminationPointSource-FlowTerminationPointSink | M | | +| Relation-GroupTerminationPoint-CrossConnection | M | | +| Relation-GroupTerminationPoint-Fabric | M | | +| Relation-GroupTerminationPoint-GroupTerminationPoint | M | | +| Relation-GroupTerminationPoint-TerminationPoint | M | | +| Relation-LinkConnection-client_Trail | O | | +| Relation-LinkConnection-server_Trail | O | | +| Relation-Location-EquipmentIdentity | M | | +| Relation-LogicalLinkEnd-NetworkCTP | O | | +| Relation-LogicalLink-LinkConnection | O | | +| Relation-ManagedElement-AlarmSeverityAssignmentProfile | O | | +| Relation-MultipointTrail-Trail [ITU-T M.1401] | M | | +| Relation-NetworkCTP-NetworkCTP | O | | +| Relation-NetworkCTP-NetworkTTP | O | | +| Relation-NetworkTerminationPoint-NE_TerminationPoint | O | | +| Relation-NetworkTerminationPoint-NetworkTerminationPoint | O | | +| Relation-NetworkTerminationPoint-SubNetworkConnection | O | | +| Relation-NetworkTerminationPoint-Trail_or_LinkConnection | O | | +| Relation-Operator-Trail [ITU-T M.1401] | M | | +| Relation-PhysicalLinkConnection-Position | M | | +| Relation-Pipe-AlarmSeverityAssignmentProfile | O | | +| Relation-Pipe-ManagedEntity | O | | +| Relation-Pipe-aEnd_NetworkTerminationPoint | M | | +| Relation-Pipe-zEnd_NetworkTerminationPoint | M | | +| Relation-PortItem-EquipmentIdentity | M | | +| Relation-PortItem-Position | M | | +| Relation-Position-Position | M | | +| Relation-ScanPoint-AlarmSeverityAssignmentProfile | O | | +| Relation-SiteRelationship-aEnd_CrossCouplingSite | M | | +| Relation-SiteRelationship-bEnd_CrossCouplingSite | M | | +| Relation-Software-AlarmSeverityAssignmentProfile | O | | +| Relation-Software-ManagedEntity | O | | +| Relation-SubNetwork-AbstractLink-1 | O | | +| Relation-SubNetwork-AbstractLink-2 | O | | + +| Relationship | Support Qualifier | Requirement IDs | +|----------------------------------------------------------|-------------------|-----------------| +| Relation-SubNetwork-AbstractLinkEnd | O | | +| Relation-SubNetwork-AccessGroup | O | | +| Relation-SubNetwork-ManagedEntity | O | | +| Relation-SubNetwork-NetworkTerminationPoint | O | | +| Relation-SubNetwork-SubNetwork | O | | +| Relation-SubNetworkConnection-LinkConnection | O | | +| Relation-SubNetworkConnection-SubNetworkConnection | O | | +| Relation-Termination-Cross-CouplingSite | M | | +| Relation-TerminationPoint-AlarmSeverityAssignmentProfile | O | | +| Relation-TerminationPoint-ManagedEntity | M | | +| Relation-TerminationPointPool-GroupTerminationPoint | M | | +| Relation-TerminationPointPool-TerminationPoint | M | | +| Relation-TopologicalLink-Trail | M | | +| Relation-TopologicalLinkEnd-NetworkTTP | M | | +| Relation-Trail-SubNetworkConnection | O | | +| Relation-Trail [ITU-T M.1401]-Position | M | | +| Relation-TrailMultiplexChannel-Position | M | | +| Relation-TrailSection-PhysicalLinkConnection | M | | +| Relation-TrailSection-PortItem | M | | +| Relation-TrailSection-Position | M | | +| Relation-TrailSection-Trail [ITU-T M.1401] | M | | +| Relation-TrailSection-TrailMultiplexChannel | M | | +| Relation-TrailTerminationPointSink-TerminationPoint | M | | +| Relation-TrailTerminationPointSource-TerminationPoint | M | | + +### 7.4.1 Relation-AbstractLink-a\_EndofLink (M) + +#### 7.4.1.1 Definition + +This represents a unidirectional relation from the IOC `AbstractLink` (including its subclasses `Topological Link` and `Logical Link`) to the ProxyClass `End of Link` (can be child classes of `Abstract Link End`, `Sub Network`, and `Access Group`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.1.2 Roles + +| Name | Definition | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aEnd | This role (when present) represents the Abstract Link (including its subclasses) capability to identify one End of Link (the starting point for a unidirectional link). When this role is present, the AbstractLink.aEnd shall carry the DN of one of the following IOCs: child classes of Abstract Link End , Sub Network , and Access Group . | + +#### 7.4.1.3 Constraint + +| Name | Definition | +|----------------------------------------|----------------------------------------------------------------------------------------------------------| +| fromEnd_for_unidirectional_Link | When the Abstract Link is a unidirectional link, the aEnd shall point to the starting point of the link. | + +### 7.4.2 Relation-AbstractLink-z\_EndofLink (M) + +#### 7.4.2.1 Definition + +This represents a unidirectional relation from the IOC `AbstractLink` (including its subclasses `Topological Link` and `Logical Link`) to the ProxyClass `End of Link` (can be child classes of `Abstract Link End`, `Sub Network`, and `Access Group`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.2.2 Roles + +| Name | Definition | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| zEnd | This role (when present) represents the Abstract Link (including its subclasses) capability to identify the other End of Link (the ending point for a unidirectional link). When this role is present, the AbstractLink.zEnd shall carry the DN of one of the following IOCs: child classes of Abstract Link End , Sub Network , and Access Group . | + +#### 7.4.2.3 Constraint + +| Name | Definition | +|--------------------------------------|--------------------------------------------------------------------------------------------------------| +| toEnd_for_unidirectional_Link | When the Abstract Link is a unidirectional link, the zEnd shall point to the ending point of the link. | + +### 7.4.3 Relation-AbstractLinkEnd-AbstractLink (M) + +#### 7.4.3.1 Definition + +This represents a unidirectional relation from the IOC `Abstract Link End` (including its child classes `Topological Link End` and `Logical Link End`) to the IOC `Abstract Link` (including its child classes `Topological Link` and `Logical Link`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.3.2 Roles + +| Name | Definition | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| linkPointer | This role (when present) represents the Abstract Link End (including its subclasses) capability to identify the Abstract Link (including its subclasses) that is terminated by this Link End . When this role is present, the AbstractLinkEnd.linkPointer shall carry the DN of Abstract Link or one of its subclasses Topological Link , Logical Link . | + +#### 7.4.3.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.4 Relation-AccessGroup-AbstractLink (O) + +#### 7.4.4.1 Definition + +This represents a unidirectional relation from the IOC Access Group to the IOC Abstract Link (including its subclasses Topological Link and Logical Link). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.4.2 Roles + +| Name | Definition | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| linkPointerList | This role (when present) represents the Access Group capability to identify the list of Abstract Links (including its subclasses) that are terminated by this Access Group. When this role is present, the AccessGroup.linkPointerList shall carry the set of DN(s) of child classes of Abstract Link (Topological Link, Logical Link). | + +#### 7.4.4.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.5 Relation-AccessGroup-FlowPointPoolLink (O) + +#### 7.4.5.1 Definition + +This represents a unidirectional relation from the IOC Access Group to the IOC Flow Point Pool Link. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.5.2 Roles + +| Name | Definition | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fppLinkPointerList | This role (when present) represents the Access Group capability to identify the list of Flow Point Pool Links that are terminated by this Access Group. When this role is present, the AccessGroup.fppLinkPointerList shall carry the set of DN(s) of Flow Point Pool Link. | + +#### 7.4.5.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.6 Relation-AccessGroup-FlowTerminationPoint (M) + +#### 7.4.6.1 Definition + +This represents a unidirectional relation from the IOC Access Group to the ProxyClass Flow Termination Point (can be Flow Termination Point Source and Flow Termination Point Sink). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.6.2 Roles + +| Name | Definition | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| accessPointList | This role (when present) represents the Access Group capability to identify the list of connectionless access points that are administratively grouped by this Access Group. When this role is present, the AccessGroup.accessPointList shall carry the set of DN(s) of the following IOCs: Flow Termination Point Source, Flow Termination Point Sink. | + +#### 7.4.6.3 Constraint + +| Name | Definition | +|--------------------------------------------------------------|-----------------------------------------------------------------------------| +| mutually_exclusive_to_Relation-AccessGroup-NetworkTTP | This relation is mutually exclusive to the Relation-AccessGroup-NetworkTTP. | + +### 7.4.7 Relation-AccessGroup-NetworkTTP (M) + +#### 7.4.7.1 Definition + +This represents a unidirectional relation from the IOC Access Group to the ProxyClass Network TTP (can be Network TTP Source, Network TTP Sink and Network TTP Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.7.2 Roles + +| Name | Definition | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| accessPointList | This role (when present) represents the Access Group capability to identify the list of Network TTPs that are administratively grouped by this AccessGroup. When this role is present, the AccessGroup.accessPointList shall carry the set of DN(s) of the following IOCs: Network TTP Source, Network TTP Sink or Network TTP Bidirectional. | + +#### 7.4.7.3 Constraint + +| Name | Definition | +|------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| mutually_exclusive_to_Relation-AccessGroup-FlowTerminationPoint | This relation is mutually exclusive to the Relation-AccessGroup-FlowTerminationPoint. | + +### 7.4.8 Relation-Association-superior\_Trail (O) + +#### 7.4.8.1 Definition + +This represents a bidirectional relation between the IOC Association and the IOC Trail [ITU-T M.1401]. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.8.2 Roles + +| Name | Definition | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| superiorTrail | This role (when present) represents the Association capability to identify the Trail [ITU-T M.1401] that controls this Association. When this role is present, the Association.superiorTrail shall carry the DN of Trail [ITU-T M.1401]. | +| subordinateAssociationList | This role (when present) represents the Trail [ITU-T M.1401] capability to identify the Association that is subordinate to this Trail. When this role is present, the Trail [ITU-T M.1401].subordinateAssociationList shall carry the set of DN(s) of Association. | + +#### 7.4.8.3 Constraint + +| Name | Definition | +|-----------------------------|-----------------------------------------------------------------------| +| Ordered-relationship | This relation exists when the association is an ordered relationship. | + +### 7.4.9 Relation-Association-Trail (M) + +#### 7.4.9.1 Definition + +This represents a bidirectional relation between the IOC Association and the IOC Trail [ITU-T M.1401]. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.9.2 Roles + +| Name | Definition | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| trailList | This role (when present) represents the Association capability to identify the Trail [ITU-T M.1401] that is controlled by this Association. When this role is present, the Association.trailList shall carry the set of DN(s) of Trail [ITU-T M.1401]. | +| associationList | This role (when present) represents the Trail [ITU-T M.1401] capability to identify the Associations that this Trail is involved in. When this role is present, the Trail [ITU-T M.1401].associationList shall carry the set of DN(s) of Association. | + +#### 7.4.9.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.10 Relation-CircuitPack-AlarmSeverityAssignmentProfile (M) + +#### 7.4.10.1 Definition + +This represents a unidirectional relation from the IOC Circuit Pack to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.10.2 Roles + +| Name | Definition | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Circuit Pack capability to identify the Alarm Severity Assignment Profile that is associated with this Equipment. When this role is present, the CircuitPack.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +#### 7.4.10.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.11 Relation-CircuitPack-Trail (O) + +#### 7.4.11.1 Definition + +This represents a unidirectional relation from the IOC Circuit Pack to the IOC Trail. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.11.2 Roles + +| Name | Definition | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| portAssociations | This role (when present) represents the Circuit Pack capability to identify the list of Trails that is associated with the ports of this Circuit Pack. When this role is present, the CircuitPack.portAssociations shall carry the set of pairs of port Number and the DN of the associated Trail. | + +#### 7.4.11.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.12 Relation-ComponentItem-EquipmentIdentity (M) + +#### 7.4.12.1 Definition + +This represents a bidirectional relation between the IOC Component Item and the IOC Equipment Identity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.12.2 Roles + +| Name | Definition | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| equipmentIdentity | This role (when present) represents the Component Item capability to identify the Equipment Identity to which the Component Item belongs. When this role is present, the ComponentItem.equipmentIdentity shall carry the DN of Equipment Identity. | +| componentItemList | This role (when present) represents the Equipment Identity capability to identify the Component Item(s) belonging to this Equipment identity. When this role is present, the EquipmentIdentity.componentItemList shall carry the set of DN(s) of ComponentItem. | + +#### 7.4.12.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.13 Relation-ComponentItem-Location (M) + +#### 7.4.13.1 Definition + +This represents a bidirectional relation between the IOC `Component Item` and the IOC `Location`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.13.2 Roles + +| Name | Definition | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| location | This role (when present) represents the Component Item capability to identify the Location subordinate to the Location of the EquipmentItem containing the ComponentItem , where this Component Item can be found. When this role is present, the ComponentItem.location shall carry the DN of Location . | +| componentItem | This role (when present) represents the Location capability to identify the Component Item of an Equipment Item in this Location . When this role is present, the Location.componentItem shall carry the DN of ComponentItem . | + +#### 7.4.13.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.14 Relation-Connection-client\_Trail (O) + +#### 7.4.14.1 Definition + +This represents a unidirectional relation from the IOC `Connection` to the IOC `Trail`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.14.2 Roles + +| Name | Definition | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| clientTrail | This role (when present) represents the Connection capability to identify the Trail in the same network layer as the connection served by this Connection object. When this role is present, the Connection.clientTrail shall carry the DN of Trail . | + +#### 7.4.14.3 Constraint + +| Name | Definition | +|--------------------------------|---------------------------------------| +| connection_serves_trail | The connection serves a client trail. | + +### 7.4.15 Relation-Connection-server\_Trail (O) + +#### 7.4.15.1 Definition + +This represents a unidirectional relation from the IOC `Connection` to the IOC `Trail`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.15.2 Roles + +| Name | Definition | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTrailList | This role (when present) represents the Connection capability to identify the list of Trails in a lower order network layer which may be used in parallel to serve this Connection. When this role is present, the Connection.serverTrailList shall carry the set of DN(s) of Trail. | + +#### 7.4.15.3 Constraint + +| Name | Definition | +|--------------------------------------|-----------------------------------------| +| connection_supported_by_trail | The connection is supported by a trail. | + +### 7.4.16 Relation-ConnectionlessPoint-AlarmSeverityAssignmentProfile (O) + +#### 7.4.16.1 Definition + +This represents a unidirectional relation from the IOC Connectionless Point (including its child classes Flow Termination Point Source, Flow Termination Point Sink, Flow Point Source, Flow Point Sink) to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.16.2 Roles + +| Name | Definition | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Connectionless Point (including its child classes Flow Termination Point Source, Flow Termination Point Sink, Flow Point Source, Flow Point Sink) capability to identify the Alarm Severity Assignment Profile that is associated with this Connectionless Point. When this role is present, the ConnectionlessPoint.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +#### 7.4.16.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.17 Relation-ConnectionlessPoint-ManagedEntity (M) + +#### 7.4.17.1 Definition + +This represents a unidirectional relation from the IOC Connectionless Point (including its child classes Flow Point Source/Sink, and Flow Termination Point Source/Sink) to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.17.2 Roles + +| Name | Definition | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Connectionless Point (including its child classes Flow Point Source/Sink, and Flow Termination Point Source/Sink) capability to identify the list of Managed Entities that are capable of directly affecting this Connectionless Point. When this role is present, the ConnectionlessPoint.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.17.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.18 Relation-ConnectionlessTrail-AlarmSeverityAssignmentProfile (O) + +#### 7.4.18.1 Definition + +This represents a unidirectional relation from the IOC Connectionless Trail to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.18.2 Roles + +| Name | Definition | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Connectionless Trail capability to identify the Alarm Severity Assignment Profile that is associated with this Connectionless Trail. When this role is present, the ConnectionlessTrail.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +#### 7.4.18.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.19 Relation-ConnectionlessTrail-FlowTerminationPointSink (M) + +#### 7.4.19.1 Definition + +This represents a bidirectional relation between the IOC Connectionless Trail and the IOC Flow Termination Point Sink. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.19.2 Roles + +| Name | Definition | +|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| zEndFTP | This role (when present) represents the Connectionless Trail capability to identify the Flow Termination Point Sink where this connectionless trail is terminated. When this role is present, the ConnectionlessTrail.zEndFTP shall carry the DN of Flow Termination Point Sink. | +| connectionlessTrailPointer | This role (when present) represents the Flow Termination Point Sink capability to identify the Connectionless Trail that is terminated by this Flow Termination Point Sink. When this role is present, the FlowTerminationPointSink.connectionlessTrailPointer shall carry the DN of Connectionless Trail. | + +#### 7.4.19.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.20 Relation-ConnectionlessTrail-FlowTerminationPointSource (M) + +#### 7.4.20.1 Definition + +This represents a bidirectional relation between the IOC Connectionless Trail and the IOC Flow Termination Point Source. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.20.2 Roles + +| Name | Definition | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aEndFTP | This role (when present) represents the Connectionless Trail capability to identify the Flow Termination Point Source where this connectionless trail is started. When this role is present, the ConnectionlessTrail.aEndFTP shall carry the DN of Flow Termination Point Source. | +| connectionlessTrailPointer | This role (when present) represents the Flow Termination Point Source capability to identify the Connectionless Trail that starts from this Flow Termination Point Source. When this role is present, the FlowTerminationPointSource.connectionlessTrailPointer shall carry the DN of Connectionless Trail. | + +#### 7.4.20.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.21 Relation-ConnectionTerminationPointSink-TerminationPoint (M) + +#### 7.4.21.1 Definition + +This represents a unidirectional relation from the IOC Connection Termination Point Sink to the IOC Termination Point (including its child classes Trail Termination Point Sink, Trail Termination Point Bidirectional, Connection Termination Point Source, Connection Termination Point Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.21.2 Roles + +| Name | Definition | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamConnectivityPointer | This role (when present) represents the Connection Termination Point Sink capability to identify the Termination Point within the same ME, which receives information (traffic) from this termination point at the same layer, or is null. When this role is present, the ConnectionTerminationPointSink.downstreamConnectivityPointer shall carry the set of DN(s) of the following IOCs: Trail Termination Point Sink, Trail Termination Point Bidirectional, Connection Termination Point Source, Connection Termination Point Bidirectional. | + +#### 7.4.21.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.22 Relation-ConnectionTerminationPointSource-TerminationPoint (M) + +#### 7.4.22.1 Definition + +This represents a unidirectional relation from the IOC Connection Termination Point Source to the IOC Termination Point (including its child classes Trail Termination Point Source, Trail Termination Point Bidirectional, Connection Termination Point Sink, Connection Termination Point Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.22.2 Roles + +| Name | Definition | +|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| upstreamConnectivityPointer | This role (when present) represents the Connection Termination Point Source capability to identify the Termination Point within the same ME, which sends information (traffic) to this termination point at the same layer, or is null. When this role is present, the ConnectionTerminationPointSource.upstreamConnectivityPointer shall carry the set of DN(s) of the following IOCs: Trail Termination Point Source, Trail Termination Point Bidirectional, Connection Termination Point Sink, Connection Termination Point Bidirectional. | + +#### 7.4.22.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.23 Relation-CrossConnection-from\_TP\_or\_GTP (M) + +#### 7.4.23.1 Definition + +This represents a unidirectional relation from the IOC Cross Connection to the ProxyClass TP\_or\_GTP (can be Connection Termination Point Sink, Connection Termination Point Bidirectional, Trail Termination Point Source, Trail Termination Point Bidirectional, or Group Termination Point composed of members of one of these categories). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.23.2 Roles + +| Name | Definition | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fromTermination | This role (when present) represents the Cross Connection capability to identify one Termination Point or Group Termination Point for the assignment relationship between a pair of Termination Points or Group Termination Points (the starting point for a unidirectional cross-connection). When this role is present, the CrossConnection.fromTermination shall carry the DN of one of the following IOCs: Connection Termination Point Sink, Connection Termination Point Bidirectional, Trail Termination Point Source, Trail Termination Point Bidirectional, or Group Termination Point composed of members of one of these categories), or can be NULL. | + +#### 7.4.23.3 Constraint + +| Name | Definition | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| null_fromTermination_value | If the fromTermination attribute has a value of NULL, the assignment relationship is between the termination point or the GTP listed in the fromTermination attribute of the containing Multipoint Cross-Connection, and the termination point or GTP listed in the ToTermination attribute of this Cross-Connection. | + +### 7.4.24 Relation-CrossConnection-to\_TP\_or\_GTP (M) + +#### 7.4.24.1 Definition + +This represents a unidirectional relation from the IOC Cross Connection to the ProxyClass TP\_or\_GTP (can be Connection Termination Point Source, Connection Termination Point Bidirectional, Trail Termination Point Sink, Trail Termination Point Bidirectional, or Group Termination Point composed of members of one of these categories). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.24.2 Roles + +| Name | Definition | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| toTermination | This role (when present) represents the Cross Connection capability to identify one Termination Point or Group Termination Point for the assignment relationship between a pair of Termination Points or Group Termination Points (the ending point for a unidirectional cross-connection). When this role is present, the CrossConnection.toTermination shall carry the DN of one of the following IOCs: Connection Termination Point Source, Connection Termination Point Bidirectional, Trail Termination Point Sink, Trail Termination Point Bidirectional, or Group Termination Point composed of members of one of these categories). | + +#### 7.4.24.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.25 Relation-CrossCouplingSite-Operator (M) + +#### 7.4.25.1 Definition + +This represents a bidirectional relation between the IOC Cross-Coupling Site and the IOC Operator. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.25.2 Roles + +| Name | Definition | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| currentOperator | This role (when present) represents the Cross-Coupling Site capability to identify the Operator that is currently responsible for this Cross-Coupling Site. When this role is present, the Cross-CouplingSite.currentOperator shall carry the DN of Operator. | +| controlledSiteList | This role (when present) represents the Operator capability to identify the Cross-Coupling Site(s) that is currently owned by this Operator. When this role is present, the Operator.controlledSiteList shall carry the set of DN(s) of Cross-Coupling Site. | + +#### 7.4.25.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.26 Relation-CrossCouplingSite-GeographicalArea (M) + +#### 7.4.26.1 Definition + +This represents a bidirectional relation between the IOC Cross-Coupling Site and the IOC Geographical Area. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.26.2 Roles + +| Name | Definition | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| geographicalArea | This role (when present) represents the Cross-Coupling Site capability to identify the Geographical Area that this Cross-Coupling Site belongs to. When this role is present, the Cross-CouplingSite.geographicalArea shall carry the DN of Geographical Area. | +| siteList | This role (when present) represents the Geographical Area capability to identify the Cross-Coupling Site that belongs to this Geographical Area. When this role is present, the GeographicalArea.siteList shall carry the set of DN(s) of Cross-Coupling Site. | + +#### 7.4.26.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.27 Relation-Equipment-AlarmSeverityAssignmentProfile (O) + +#### 7.4.27.1 Definition + +This represents a unidirectional relation from the IOC Equipment to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.27.2 Roles + +| Name | Definition | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Equipment (including its child classes: Equipment Holder and Circuit Pack) capability to identify the Alarm Severity Assignment Profile that is associated with this Equipment. When this role is present, the Equipment.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +#### 7.4.27.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.28 Relation-Equipment-ManagedEntity-1 (O) + +#### 7.4.28.1 Definition + +This represents a unidirectional relation from the IOC Equipment to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.28.2 Roles + +| Name | Definition | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| affectedObjectList | This role (when present) represents the Equipment (including its child classes: Equipment Holder and Circuit Pack) capability to identify the list of Managed Entities that can be directly affected by a change in state or deletion of this Equipment. When this role is present, the Equipment.affectedObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.28.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.29 Relation-Equipment-ManagedEntity-2 (M) + +#### 7.4.29.1 Definition + +This represents a unidirectional relation from the IOC Equipment Holder to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.29.2 Roles + +| Name | Definition | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Equipment (including its child classes: Equipment Holder and Circuit Pack ) capability to identify the list of Managed Entities that are capable of directly affecting this Equipment . When this role is present, the Equipment.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.29.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.30 Relation-EquipmentHolder-Software (O) + +#### 7.4.30.1 Definition + +This represents a unidirectional relation from the IOC `EquipmentHolder` to the IOC `Software`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.30.2 Roles + +| Name | Definition | +|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| subordinateCircuitPackSoftwareLoad | This role (when present) represents the EquipmentHolder capability to identify the Software , if any, that is currently designated as the one to be loaded to the containing circuit pack whenever automatic reload of software is needed. When this role is present, the EquipmentHolder.subordinateCircuitPackSoftwareLoad may carry the ordered set of DN(s) of Software . | + +#### 7.4.30.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.31 Relation-EquipmentItem-EquipmentIdentity (M) + +#### 7.4.31.1 Definition + +This represents a bidirectional relation between the IOC `Equipment Item` and the IOC `Equipment Identity`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.31.2 Roles + +| Name | Definition | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| equipmentIdentity | This role (when present) represents the Equipment Item capability to identify the Equipment Identity to which the Equipment Item belongs. When this role is present, the EquipmentItem.equipmentIdentity shall carry the DN of Equipment Identity . | +| equipmentItemList | This role (when present) represents the Equipment Identity capability to identify the Equipment Item(s) belonging to this Equipment Identity . When this role is present, the EquipmentIdentity.equipmentItemList shall carry the set of DN(s) of Equipment Item . | + +#### 7.4.31.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.32 Relation-EquipmentItem-Location (M) + +#### 7.4.32.1 Definition + +This represents a bidirectional relation between the IOC `Equipment Item` and the IOC `Location`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.32.2 Roles + +| Name | Definition | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| location | This role (when present) represents the Equipment Item capability to identify the Location subordinate to the superior Cross-coupling site or a recursively subordinate Location , where this Equipment Item can be found. When this role is present, the EquipmentItem.location shall carry the DN of Location . | +| equipmentItem | This role (when present) represents the Location capability to identify the Equipment Item being placed in this Location . When this role is present, the Location.equipmentItem shall carry the DN of EquipmentItem . | + +#### 7.4.32.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.33 Relation-Exchange-EquipmentItem (M) + +#### 7.4.33.1 Definition + +This represents a bidirectional relation between the IOC `Exchange` and the IOC `Equipment Item`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.33.2 Roles + +| Name | Definition | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| equipmentItem | This role (when present) represents the Exchange capability to identify the Equipment Item which provides a reference to the placement of the Exchange in a specific Location . When this role is present, the Exchange.equipmentItem shall carry the set of DN of Port Item . | +| exchange | This role (when present) represents the Equipment Item capability to identify the Exchange that is implemented by this Equipment Item . When this role is present, the EquipmentItem.exchange shall carry the DN of Exchange . | + +#### 7.4.33.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.34 Relation-ExternalPoint-ManagedEntity (M) + +#### 7.4.34.1 Definition + +This represents a unidirectional relation from the IOC `External Point` to the `ProxyClass Managed Entity`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.34.2 Roles + +| Name | Definition | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the External Point capability to identify the list of Managed Entities that are capable of directly affecting this External Point . When this role is present, the ExternalPoint.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.34.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.35 Relation-Fabric-ManagedEntity (M) + +#### 7.4.35.1 Definition + +This represents a unidirectional relation from the IOC `Fabric` to the `ProxyClass Managed Entity`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.35.2 Roles + +| Name | Definition | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Fabric capability to identify the list of Managed Entities that are capable of directly affecting this Fabric . When this role is present, the fabric.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.35.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.36 Relation-FlowDomain-AccessGroup (O) + +#### 7.4.36.1 Definition + +This represents a bidirectional relation between the IOC `Flow Domain` and the IOC `Access Group`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.36.2 Roles + +| Name | Definition | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedAccessGroupList | This role (when present) represents the Flow Domain capability to identify the list of Access Groups that are contained in this Flow Domain. When this role is present, the FlowDomain.containedAccessGroupList shall carry the set of DNs of Access Group. | +| containedInFlowDomainList | This role (when present) represents the Access Group capability to identify the list of parent Flow Domains that contain this Access Group. When this role is present, the AccessGroup.containedInFlowDomainList shall carry the set of DN(s) of Flow Domain. | + +#### 7.4.36.3 Constraint + +| Name | Definition | +|-------------------------------|------------------------------------------------------------------------------| +| partitioning_supported | This relation is present when an Access Group is contained in a Flow Domain. | + +### 7.4.37 Relation-FlowDomain-ConnectionlessPoint (O) + +#### 7.4.37.1 Definition + +This represents a unidirectional relation from the IOC Flow Domain to the IOC Network Connectionless Point (including its child classes Flow (Termination) Point Source/Sink). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.37.2 Roles + +| Name | Definition | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedConnectionlessPointList | This role (when present) represents the Flow Domain capability to identify the list of Connectionless Points that are contained in this Flow Domain. When this role is present, the FlowDomain.containedConnectionlessPointList shall carry the set of DN(s) of child classes of Connectionless Point (Flow (Termination) Point Source/Sink). | + +#### 7.4.37.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.38 Relation-FlowDomain-FlowDomain (O) + +#### 7.4.38.1 Definition + +This represents a bidirectional relation between the IOC Flow Domain and the IOC Flow Domain. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.38.2 Roles + +| Name | Definition | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedFlowDomainList | This role (when present) represents the Flow Domain capability to identify the list of Flow Domains that are contained in this Flow Domain. When this role is present, the FlowDomain.containedFlowDomainList shall carry the set of DN(s) of Flow Domain. | +| containedInFlowDomainList | This role (when present) represents the Flow Domain capability to identify the list of parent Flow Domains that contain this Flow Domain. When this role is present, the FlowDomain.containedInFlowDomainList shall carry the set of DN(s) of Flow Domain. | + +#### 7.4.38.3 Constraint + +| Name | Definition | +|-------------------------------|------------------------------------------------------------------------------| +| partitioning_supported | This relation is present when an Access Group is contained in a Flow Domain. | + +### 7.4.39 Relation-FlowDomain-FlowPointPool (O) + +#### 7.4.39.1 Definition + +This represents a bidirectional relation between the IOC Flow Domain and the IOC Flow Point Pool. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.39.2 Roles + +| Name | Definition | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedFlowPointPoolList | This role (when present) represents the Flow Domain capability to identify the list of Flow Point Pools that are contained in this Flow Domain. When this role is present, the FlowDomain.containedFlowPointPoolList shall carry the set of DN(s) of Flow Point Pool. | +| containedInFlowDomainList | This role (when present) represents the Flow Point Pool capability to identify the list of parent Flow Domains that contain this Flow Point Pool. When this role is present, the FlowPointPool.containedInFlowDomainList shall carry the set of DN(s) of Flow Domain. | + +#### 7.4.39.3 Constraint + +| Name | Definition | +|-------------------------------|--------------------------------------------------------------------------------| +| partitioning_supported | This relation is present when a Flow Point Pool is contained in a Flow Domain. | + +### 7.4.40 Relation-FlowDomain-FlowPointPoolLink-1 (O) + +#### 7.4.40.1 Definition + +This represents a unidirectional relation from the IOC Flow Domain to the IOC Flow Point Pool Link. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.40.2 Roles + +| Name | Definition | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fppLinkPointerList | This role (when present) represents the Flow Domain capability to identify the list of Flow Point Pool Links that are terminated by this Flow Domain. When this role is present, the FlowDomain.fppLinkPointerList shall carry the set of DN(s) of Flow Point Pool Link. | + +#### 7.4.40.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.41 Relation-FlowDomain-FlowPointPoolLink-2 (O) + +#### 7.4.41.1 Definition + +This represents a unidirectional relation from the IOC Flow Domain to the IOC Flow Point Pool Link. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.41.2 Roles + +| Name | Definition | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedFppLinkList | This role (when present) represents the Flow Domain capability to identify the list of Flow Point Pool Links that are contained in this Flow Domain through partitioning. When this role is present, the FlowDomain.containedFppLinkList shall carry the set of DN(s) of Flow Point Pool Link. | + +#### 7.4.41.3 Constraint + +| Name | Definition | +|-------------------------------|------------------------------------------------------------------------------| +| partitioning_supported | There are contained FPPLinks in the flow Domain (partitioning is supported). | + +### 7.4.42 Relation-FlowDomain-ManagedEntity (O) + +#### 7.4.42.1 Definition + +This represents a unidirectional relation from the IOC Flow Domain to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.42.2 Roles + +| Name | Definition | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Flow Domain capability to identify the list of Managed Entities that are capable of directly affecting this Flow Domain. When this role is present, the FlowDomain.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.42.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.43 Relation-FlowDomainFragment-input\_ConnectionlessPoint (M) + +#### 7.4.43.1 Definition + +This represents a unidirectional relation between the IOC Flow Domain Fragment to the IOC Connectionless Point (including its child classes: Flow (Termination) Point Source/Sink). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.43.2 Roles + +| Name | Definition | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| inputFPList | This role (when present) represents the Flow Domain Fragment capability to identify one or more input Connectionless Points that terminate this Flow Domain Fragment. When this role is present, the FlowDomain.inputFPList shall carry the set of DN(s) of Connectionless Point (including its child classes: Flow (Termination) Point Source/Sink). | + +#### 7.4.43.3 Constraint + +| Name | Definition | +|--------------------------|-----------------------------------------------| +| none_empty_FPList | The value of the inputFPList cannot be empty. | + +### 7.4.44 Relation-FlowDomainFragment-output\_ConnectionlessPoint (M) + +#### 7.4.44.1 Definition + +This represents a unidirectional relation between the IOC Flow Domain Fragment to the IOC Connectionless Point (including its child classes: Flow (Termination) Point Source/Sink). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.44.2 Roles + +| Name | Definition | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| outputFPList | This role (when present) represents the Flow Domain Fragment capability to identify one or more output Connectionless Points that terminate this Flow Domain Fragment. When this role is present, the FlowDomain.outputFPList shall carry the set of DN(s) of Connectionless Point (including its child classes: Flow (Termination) Point Source/Sink). | + +#### 7.4.44.3 Constraint + +| Name | Definition | +|--------------------------|------------------------------------------------| +| none_empty_FPList | The value of the outputFPList cannot be empty. | + +### 7.4.45 Relation-FlowPoint-FlowTerminationPoint (O) + +#### 7.4.45.1 Definition + +This represents a bidirectional relation between the ProxyClass Flow Point (can be Flow Point + +Sink/Source) and the ProxyClass Flow Termination Point (can be Flow Termination Point Sink/Source). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.45.2 Roles + +| Name | Definition | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverFTPPointer | This role (when present) represents the Flow Point capability to identify the Flow Termination Points that may serve this Flow Point in another layer. When this role is present, the FlowPoint (Sink/Source).serverFTPPointer shall carry the set of DN(s) of FlowTerminationPoint(Sink/Source). | +| clientFPList | This role (when present) represents the Flow Termination Point capability to identify the list of Flow Points (including Sink/Source) which are clients of this Flow Point in another layer. When this role is present, the FlowPoint (Sink/Source).clientFPList shall carry the set of DN(s) of the Flow Point(Sink/Source). | + +#### 7.4.45.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.46 Relation-FlowPointPool-FlowPoint (M) + +#### 7.4.46.1 Definition + +This represents a unidirectional relation from the IOC Flow Point Pool to the ProxyClass Flow Point (can be Flow Point Source or Flow Point Sink). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.46.2 Roles + +| Name | Definition | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| flowPointList | This role (when present) represents the Flow Point Pool capability to identify the Flow Points that are present in this Flow Point Pool. When this role is present, the FlowPointPool.flowPointList shall carry the set of DN(s) of Flow Point Source or Flow Point Sink. | + +#### 7.4.46.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.47 Relation-FlowPointPool-GenericTransportTTP (O) + +#### 7.4.47.1 Definition + +This represents a bidirectional relation between the IOC Flow Point Pool and the IOC Generic Transport TTP. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.47.2 Roles + +| Name | Definition | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTTPPointer | This role (when present) represents the Flow Point Pool capability to identify the Generic Transport TTPs that may serve this Flow Point Pool in another layer. When this role is present, the FlowPointPool.serverTTPPointer shall carry the set of DN(s) of the IOC: Network Generic Transport TTP or its child classes. | +| clientFlowPointPoolList | This role (when present) represents the Generic Transport TTP capability to identify the list of Flow Point Pools in the client layer network domain(s) that are supported by this Generic Transport TTP. When this role is present, the GenericTransportTTP.clientFlowPointPoolList shall carry the set of DN(s) of the Flow Point Pool. | + +#### 7.4.47.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.48 Relation-FlowPointPool-ManagedEntity (O) + +#### 7.4.48.1 Definition + +This represents a unidirectional relation from the IOC Flow Point Pool to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.48.2 Roles + +| Name | Definition | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Flow Point Pool capability to identify the list of Managed Entities that are capable of directly affecting this Flow Point Pool. When this role is present, the FlowPointPool.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.48.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.49 Relation-FlowPointPool-FlowPointPoolLink (M) + +#### 7.4.49.1 Definition + +This represents a unidirectional relation from the IOC Flow Point Pool to the IOC Flow Point Pool Link. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.49.2 Roles + +| Name | Definition | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| linkPointer | This role (when present) represents the Flow Point Pool capability to identify the Flow Point Pool Link that is terminated by this Flow Point Pool. When this role is present, the FlowPointPool.linkPointer shall carry the DN of Flow Point Pool Link. | + +#### 7.4.49.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.50 Relation-FlowPointPoolLink-AlarmSeverityAssignmentProfile (O) + +#### 7.4.50.1 Definition + +This represents a unidirectional relation from the IOC Flow Point Pool Link to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.50.2 Roles + +| Name | Definition | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Flow Point Pool Link capability to identify the Alarm Severity Assignment Profile that is associated with this Flow Point Pool Link. When this role is present, the FlowPointPoolLink.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +#### 7.4.50.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.51 Relation-FlowPointPoolLink-a\_EndofFPPLink (M) + +#### 7.4.51.1 Definition + +This represents a unidirectional relation from the IOC Flow Point Pool Link to the ProxyClass End of FPPLink (can be Flow Point Pool, Flow Domain, and Access Group). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.51.2 Roles + +| Name | Definition | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aEndofFPPLink | This role (when present) represents the Flow Point Pool Link capability to identify one End of the FPPLink (the starting point for a unidirectional link). When this role is present, the PointPool.aEndofFPPLink shall carry the DN of one of the following IOCs: Flow Point Pool, Flow Domain, and Access Group. | + +#### 7.4.51.3 Constraint + +| Name | Definition | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| fromEnd_for_unidirectional_Link | When the Flow Point Pool Link is a unidirectional link, the aEndofFPPLink shall point to the starting point of the link. | + +### 7.4.52 Relation-FlowPointPoolLink-z\_EndofFPPLink (M) + +#### 7.4.52.1 Definition + +This represents a unidirectional relation from the IOC Flow Point Pool Link to the ProxyClass End of FPPLink (can be Flow Point Pool, Flow Domain, and Access Group). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.52.2 Roles + +| Name | Definition | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| zEndofFPPLink | This role (when present) represents the Flow Point Pool Link capability to identify the other End of the FPPLink (the ending point for a unidirectional link). When this role is present, the FlowPointPool.zEndofFPPLink shall carry the DN of one of the following IOCs: Flow Point Pool, Flow Domain, and Access Group. | + +#### 7.4.52.3 Constraint + +| Name | Definition | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| toEnd_for_unidirectional_Link | When the Flow Point Pool Link is a unidirectional link, the zEndofFPPLink shall point to the ending point of the FPPLink. | + +### 7.4.53 Relation-FlowPointPoolLink-ConnectionlessTrail (O) + +#### 7.4.53.1 Definition + +This represents a bidirectional relation from the IOC Flow Point Pool Link to the IOC Connectionless Trail. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.53.2 Roles + +| Name | Definition | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTrail | This role (when present) represents the Flow Point Pool Link capability to identify the Connectionless Trail in the server layer that supports the Flow Point Pool Link in a client layer. When this role is present, the FlowPointPoolLink.serverTrail shall carry the DN of Connectionless Trail. | +| clientLinkPointerList | This role (when present) represents the Connectionless Trail capability to identify the list of Flow Point Pool Links that reflect the capacity of the Trail in the client layer network domain(s). When this role is present, the ConnectionlessTrail.clientLinkPointerList shall carry the set of DN(s) of Flow Point Pool Link. | + +#### 7.4.53.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.54 Relation-FlowPointSink-FlowPointSource (M) + +#### 7.4.54.1 Definition + +This represents a bidirectional relation between the IOC Flow Point Sink and the IOC Flow Point Source. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.54.2 Roles + +| Name | Definition | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamFPPointer | This role (when present) represents the Flow Point Sink capability to identify the list of Flow Point Source within the same ME, which receives information (traffic) from this Flow Point Sink at the same layer, or is null. When this role is present, the FlowPointSink.downstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Sink, Flow Point Source. | +| upstreamFPPointer | This role (when present) represents the Flow Point Source capability to identify the list of Flow Point Sinks within the same ME, which send information (traffic) to this Flow Point Source at the same layer, or is null. When this role is present, the FlowPointSource.upstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Source, Flow Point Sink. | + +#### 7.4.54.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.55 Relation-FlowPointSink-FlowTerminationPointSink (M) + +#### 7.4.55.1 Definition + +This represents a bidirectional relation between the IOC Flow Point Sink and the IOC Flow Termination Point Sink. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.55.2 Roles + +| Name | Definition | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamFPPointer | This role (when present) represents the Flow Point Sink capability to identify the list of Flow Termination Point Sink within the same ME, which receives information (traffic) from this Flow Point Sink at the same layer, or is null. When this role is present, the FlowPointSink.downstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Sink, Flow Point Source. | +| upstreamFPPointer | This role (when present) represents the Flow Termination Point Sink capability to identify the list of Flow Point Sink within the same ME, which sends information (traffic) to this Flow Termination Point Sink at the same layer, or is null. When this role is present, the FlowTerminationPointSink.upstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Source, Flow Point Sink. | + +#### 7.4.55.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.56 Relation-FlowTerminationPointSource-FlowPointSource (M) + +#### 7.4.56.1 Definition + +This represents a bidirectional relation between the IOC Flow Termination Point Source and the IOC Flow Point Source. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.56.2 Roles + +| Name | Definition | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamFPPointer | This role (when present) represents the Flow Termination Point Source capability to identify the list of Flow Point Source within the same ME, which receives information (traffic) from this Flow Termination Point Source at the same layer, or is null. When this role is present, the FlowTerminationPointSource.downstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Sink, Flow Point Source. | +| upstreamFPPointer | This role (when present) represents the Flow Point Source capability to identify the list of Flow Termination Point Source within the same ME, which sends information (traffic) to this Flow Point Source at the same layer, or is null. When this role is present, the FlowPointSource.upstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Source, Flow Point Sink. | + +#### 7.4.56.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.57 Relation-FlowTerminationPointSource-FlowTerminationPointSink (M) + +#### 7.4.57.1 Definition + +This represents a bidirectional relation between the IOC Flow Termination Point Source and the IOC Flow Termination Point Sink. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.57.2 Roles + +| Name | Definition | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamFPPointer | This role (when present) represents the Flow Termination Point Source capability to identify the list of Flow Termination Point Sink within the same ME, which receives information (traffic) from this Flow Termination Point Source at the same layer, or is null. When this role is present, the FlowTerminationPointSource.downstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Sink, Flow Point Source. | +| upstreamFPPointer | This role (when present) represents the Flow Termination Point Sink capability to identify the list of Flow Termination Point Source within the same ME, which sends information (traffic) to this Flow Termination Point Sink at the same layer, or is null. When this role is present, the FlowTerminationPointSink.upstreamFPPointer shall carry the set of DN(s) of the following IOCs: Flow Termination Point Source, Flow Point Sink. | + +#### 7.4.57.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.58 Relation-GroupTerminationPoint-CrossConnection (M) + +#### 7.4.58.1 Definition + +This represents a unidirectional relation from the IOC Group Termination Point to the IOC Cross Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.58.2 Roles + +| Name | Definition | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| crossConnectionObjectPointer | This role (when present) represents the Group Termination Point capability to identify the Cross Connections that this Group Termination Point points to. When this role is present, the GroupTerminationPoint.crossConnectionObjectPointer shall carry the DN of Cross Connection, or set of DN(s) of Cross Connection for multiple cross connections. | + +#### 7.4.58.3 Constraint + +| Name | Definition | +|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| mutually_exclusive_to_Relation-GroupTerminationPoint-CrossConnection_and_Relation-GroupTerminationPoint-GroupTerminationPoint | This relation is mutually exclusive to the relation-GroupTerminationPoint-CrossConnection and Relation-GroupTerminationPoint-GroupTerminationPoint. | + +### 7.4.59 Relation-GroupTerminationPoint-Fabric (M) + +#### 7.4.59.1 Definition + +This represents a unidirectional relation from the IOC Group Termination Point to the IOC Fabric. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.59.2 Roles + +| Name | Definition | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| crossConnectionObjectPointer | This role (when present) represents the Group Termination Point capability to identify the Fabric that this Group Termination Point points to. When this role is present, the GroupTerminationPoint.crossConnectionObjectPointer shall carry the DN of Fabric. | + +#### 7.4.59.3 Constraint + +| Name | Definition | +|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| mutually_exclusive_to_Relation-GroupTerminationPoint-CrossConnection_and_Relation-GroupTerminationPoint-GroupTerminationPoint | This relation is mutually exclusive to the relation-GroupTerminationPoint-CrossConnection and Relation-GroupTerminationPoint-GroupTerminationPoint. | + +### 7.4.60 Relation-GroupTerminationPoint-GroupTerminationPoint (M) + +#### 7.4.60.1 Definition + +This represents a unidirectional relation from the IOC Group Termination Point to the IOC Group Termination Point. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.60.2 Roles + +| Name | Definition | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| crossConnectionObjectPointer | This role (when present) represents the Group Termination Point capability to identify the GroupTermination Points that this Group Termination Point points to for multiple cross-connections. When this role is present, the GroupTerminationPoint.crossConnectionObjectPointer shall carry a pair of DNs of Group Termination Point for upstream and downstream. | + +#### 7.4.60.3 Constraint + +| Name | Definition | +|-----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| mutually_exclusive_to_Relation-GroupTerminationPoint-CrossConnection_and_Relation-GroupTerminationPoint-Fabric | This relation is mutually exclusive to the relation-GroupTerminationPoint-CrossConnection and Relation-GroupTerminationPoint-Fabric. | + +### 7.4.61 Relation-GroupTerminationPoint-TerminationPoint (M) + +#### 7.4.61.1 Definition + +This represents a unidirectional relation from the IOC Group Termination Point to the IOC Termination Point (including its child classes). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.61.2 Roles + +| Name | Definition | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tpsInGtpList | This role (when present) represents the Group Termination Point capability to identify the Termination Points that are represented by this Group Termination Point. When this role is present, the GroupTerminationPoint.tpsInGtpList shall carry the set of DN(s) of child classes of Termination Points. | + +#### 7.4.61.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.62 Relation-LinkConnection-client\_Trail (O) + +#### 7.4.62.1 Definition + +This represents a bidirectional relation between the IOC Link Connection and the IOC Trail. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.62.2 Roles + +| Name | Definition | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| clientTrail | This role (when present) represents the Link Connection capability to identify the Trail in the same network layer as the connection served by this Link Connection object. When this role is present, the LinkConnection.clientTrail shall carry the DN of Trail. | +| connectionList | This role (when present) represents the Trail capability to identify the list of Link Connections and Sub Network Connections in a given layer which may compose the Trail in the same layer. When this role is present, the Trail.connectionList shall carry the ordered set of DN(s) of Link Connection and Sub Network Connection. | + +#### 7.4.62.3 Constraint + +| Name | Definition | +|--------------------------------|--------------------------------------------| +| connection_serves_trail | The link connection serves a client trail. | + +### 7.4.63 Relation-LinkConnection-server\_Trail (O) + +#### 7.4.63.1 Definition + +This represents a bidirectional relation between the IOC Link Connection and the IOC Trail. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.63.2 Roles + +| Name | Definition | +|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTrailList | This role (when present) represents the Link Connection capability to identify the list of Trails in a lower order network layer which may be used in parallel to serve this Link Connection. When this role is present, the LinkConnection.serverTrailList shall carry the set of DN(s) of Trail. | +| clientLinkConnectionPointerList | This role (when present) represents the Trail capability to identify the list of Link Connections in the client layer network domain(s) that are supported by the Trail. When this role is present, the Trail.clientLinkConnectionPointerList shall carry the set of DN(s) of Link Connection. | + +#### 7.4.63.3 Constraint + +| Name | Definition | +|--------------------------------------|----------------------------------------------| +| connection_supported_by_trail | The link connection is supported by a trail. | + +### 7.4.64 Relation-Location-EquipmentIdentity (M) + +#### 7.4.64.1 Definition + +This represents a bidirectional relation between the IOC Location and the IOC Equipment Identity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.64.2 Roles + +| Name | Definition | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| equipmentIdentity | This role (when present) represents the Location capability to identify the Equipment Identity to which the Location belongs. When this role is present, the Location.equipmentIdentity shall carry the DN of Equipment Identity. | +| locationList | This role (when present) represents the Equipment Identity capability to identify the Location(s) belonging to this Equipment Identity. When this role is present, the EquipmentIdentity.locationList shall carry the set of DN(s) of Location. | + +#### 7.4.64.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.65 Relation-LogicalLinkEnd-NetworkCTP (O) + +#### 7.4.65.1 Definition + +This represents a unidirectional relation from the IOC Logical Link End to the ProxyClass Network CTP (can be Network CTP Source, Network CTP Sink, Network CTP Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.65.2 Roles + +| Name | Definition | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| networkCTPsInLinkEndList | This role (when present) represents the Logical Link End capability to identify the list of Network CTPs that are represented by this Logical Link End. When this role is present, the LogicalLinkEnd.networkCTPsInLinkEndList shall carry the set of DN(s) of one kind of Network CTPs (including Network CTP Source, Network CTP Sink, Network CTP Bidirectional). | + +#### 7.4.65.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.66 Relation-LogicalLink-LinkConnection (O) + +#### 7.4.66.1 Definition + +This represents a unidirectional relation from the IOC Logical Link and the IOC Link Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.66.2 Roles + +| Name | Definition | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| linkConnectionPointerList | This role (when present) represents the Logical Link capability to identify the list of Link Connections in a given layer which may compose this Logical Link in the same layer. When this role is present, the LogicalLink.linkConnectionPointerList shall carry the set of DN(s) of Link Connection . | + +#### 7.4.66.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.67 Relation-ManagedElement-AlarmSeverityAssignmentProfile (O) + +#### 7.4.67.1 Definition + +This represents a unidirectional relation from the IOC `Managed Element` to the IOC `Alarm Severity Assignment Profile`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.67.2 Roles + +| Name | Definition | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Managed Element capability to identify the Alarm Severity Assignment Profile that is associated with this Managed Element . When this role is present, the ManagedElement.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile . | + +#### 7.4.67.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.68 Relation-MultipointTrail-Trail [ITU-T M.1401] (M) + +#### 7.4.68.1 Definition + +This represents a bidirectional relation between the IOC `Multipoint Trail` and the IOC `Trail` [ITU-T M.1401]. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.68.2 Roles + +| Name | Definition | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| trailList | This role (when present) represents the Multipoint Trail capability to identify the Trail(s) [ITU-T M.1401] that is contained in this Multipoint Trail. When this role is present, the MultipointTrail.trailList shall carry the set of DN(s) of Trail [ITU-T M.1401]. | +| multipointTrail | This role (when present) represents the Trail [ITU-T M.1401] capability to identify the Multipoint Trail that is supported by this Trail [ITU-T M.1401]. When this role is present, the Trail [ITU-T M.1401].multipointTrail shall carry the DN of Multipoint Trail. | + +#### 7.4.68.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.69 Relation-NetworkCTP-NetworkCTP (O) + +#### 7.4.69.1 Definition + +This represents a bidirectional relation between the ProxyClass Network CTP (Source/Sink/Bidirectional) and the ProxyClass Network CTP (Source/Sink/Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.69.2 Roles + +| Name | Definition | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sub-partitionPointer | This role (when present) represents the Network CTP (Source/Sink/Bidirectional) capability to identify the Network CTP (Source/Sink/Bidirectional) which is in a lower level partition. When this role is present, the NetworkCTP (Source/Sink/Bidirectional).sub-partitionPointer shall carry the DN of Network CTP (Source/Sink/Bidirectional). | +| superPartitionPointer | This role (when present) represents the Network CTP (Source/Sink/Bidirectional) capability to identify the Network CTP (Source/Sink/Bidirectional) which is in a higher level partition. When this role is present, the NetworkCTP (Source/Sink/Bidirectional).superPartitionPointer shall carry the DN of Network CTP (Source/Sink/Bidirectional). | + +#### 7.4.69.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.70 Relation-NetworkCTP-NetworkTTP (O) + +#### 7.4.70.1 Definition + +This represents a bidirectional relation between the ProxyClass Network CTP (Source/Sink/Bidirectional) and the ProxyClass Network TTP (Source/Sink/Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +## 7.4.70.2 Roles + +| Name | Definition | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTTPPointer | This role (when present) represents the Network CTP capability to identify the Network TTPs which may serve this Network CTP (Source/Sink/Bidirectional) in another layer. When this role is present, the NetworkCTP(Source/Sink/Bidirectional).serverTTPPointer shall carry the set of DN(s) of Network CTP(Source/Sink/Bidirectional). | +| clientCTPList | This role (when present) represents the Network TTP capability to identify the list of Network CTPs (including Source/Sink/Bidirectional) which are clients of this Network TTP (can be Source/Sink/Bidirectional) in another layer. When this role is present, the NetworkTTP(Source/Sink/Bidirectional).clientCTPList shall carry the set of DN(s) of Network CTP (Source/Sink/Bidirectional). | + +## 7.4.70.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 7.4.71 Relation-NetworkTerminationPoint-NE\_TerminationPoint (O) + +### 7.4.71.1 Definition + +This represents a unidirectional relation from the IOC Network Termination Point (including its child classes `Network CTP/TTP Source/Sink/Bidirectional`) to the ProxyClass `NE Termination Point` (NE level Termination Point, including its child classes `Trail/Connection Termination Point Source/Sink/Bidirectional`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.71.2 Roles + +| Name | Definition | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| neTerminationPoint | This role (when present) represents the Network Termination Point (including its child classes Network CTP/TTP Source/Sink/Bidirectional ) capability to identify the NE Termination Point which represents the functionality which supports this lowest level Termination Points ( TTP/CTP Source/Sink/Bidirectional ). When this role is present, the NetworkTerminationPoint(Source/Sink/Bidirectional).neTerminationPoint shall carry the DN of NE Termination Point (including its child classes Trail/Connection Termination Point Source/Sink/Bidirectional ). | + +### 7.4.71.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 7.4.72 Relation-NetworkTerminationPoint-NetworkTerminationPoint (O) + +### 7.4.72.1 Definition + +This represents a unidirectional relation between the IOC Network Termination Point (including its child classes `Network CTP/TTP Source/Sink/Bidirectional`) and the IOC Network Termination Point (including its child classes `Network CTP/TTP Source/Sink/Bidirectional`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.72.2 Roles + +| Name | Definition | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| networkTPPointer | This role (when present) represents the Network Termination Point (including its child classes Network CTP/TTP Source/Sink/Bidirectional) capability to identify the Network Termination Point (including its child classes Network CTP/TTP Source/Sink/Bidirectional) which is associated with this Network TP. When this role is present, the NetworkTerminationPoint (Source/Sink/Bidirectional).networkTPPointer shall carry the DN of Network Termination Point (including its child classes Network CTP/TTP Source/Sink/Bidirectional). | + +#### 7.4.72.3 Constraint + +| Name | Definition | +|-----------------------|------------------------------------------------------------------------------------| +| no_flexibility | There is no flexibility between network termination points (degenerate case only). | + +### 7.4.73 Relation-NetworkTerminationPoint-SubNetworkConnection (O) + +#### 7.4.73.1 Definition + +This represents a unidirectional relation from the IOC Network Termination Point (including its child classes: Network CTP/TTP Source/Sink/Bidirectional) to the IOC Sub Network Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.73.2 Roles + +| Name | Definition | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| subNetworkConnectionPointer | This role (when present) represents the Network Termination Point (including its child classes) capability to identify the ordered list of Sub Network Connection(s) which have a relationship with the Network Termination Point. When this role is present, the Network Termination Point.subNetworkConnectionPointer shall carry the ordered set of DN(s) of SubNetwork, or can be null. | + +#### 7.4.73.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.74 Relation-NetworkTerminationPoint-Trail\_or\_LinkConnection (O) + +#### 7.4.74.1 Definition + +This represents a unidirectional relation from the IOC Network Termination Point (including its child classes: Network CTP/TTP Source/Sink/Bidirectional) to the ProxyClass Trail\_or\_LinkConnection (can be Trail or Link Connection). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.74.2 Roles + +| Name | Definition | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| connectivityPointer | This role (when present) represents the Network Termination Point (including its child classes) capability to identify the Trail or Link Connection which is terminated by the Network Termination Point. When this role is present, the NetworkTerminationPoint.connectivityPointer shall carry the DN of the following IOCs: Trail, Link Connection. | + +#### 7.4.74.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.75 Relation-Operator-Trail [ITU-T M.1401] (M) + +#### 7.4.75.1 Definition + +This represents a bidirectional relation between the IOC Operator and the IOC Trail [ITU-T M.1401]. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.75.2 Roles + +| Name | Definition | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| controlledTrailList | This role (when present) represents the Operator capability to identify the Trail(s) that is currently owned by this Operator. When this role is present, the Operator.controlledTrailList shall carry the set of DN(s) of Trail [ITU-T M.1401]. | +| controllerList | This role (when present) represents the Trail capability to identify the Operator that is currently responsible for this Trail. When this role is present, the Trail [ITU-T M.1401].controllerList shall carry the list of DN(s) of Operator. | + +#### 7.4.75.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.76 Relation-PhysicalLinkConnection-Position (M) + +#### 7.4.76.1 Definition + +This represents a bidirectional relation between the IOC Physical Link Connection and the IOC Position. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.76.2 Roles + +| Name | Definition | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | This role (when present) represents the Physical Link Connection capability to identify the Position that terminates the Physical Link Connection . When this role is present, the PhysicalLinkConnection.position shall carry the DN of Position . | +| physicalLinkConnectionList | This role (when present) represents the Position capability to identify the Physical Link Connection(s) being terminated on this Position . When this role is present, the Position.physicalLinkConnectionList shall carry the set of DN(s) of Physical Link Connection . | + +#### 7.4.76.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.77 Relation-PortItem-EquipmentIdentity (M) + +#### 7.4.77.1 Definition + +This represents a bidirectional relation between the IOC `Port Item` and the IOC `Equipment Identity`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.77.2 Roles + +| Name | Definition | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| equipmentIdentity | This role (when present) represents the Port Item capability to identify the Equipment Identity to which the Port Item belongs. When this role is present, the PortItem.equipmentIdentity shall carry the DN of Equipment Identity . | +| portItemList | This role (when present) represents the Equipment Identity capability to identify the Port Item(s) belonging to this Equipment Identity . When this role is present, the EquipmentIdentity.portItemList shall carry the set of DN(s) of Port Item . | + +#### 7.4.77.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.78 Relation-PortItem-Position (M) + +#### 7.4.78.1 Definition + +This represents a bidirectional relation between the IOC `Port Item` and the IOC `Position`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.78.2 Roles + +| Name | Definition | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | This role (when present) represents the Port Item capability to identify the Position that terminates this Port Item. When this role is present, the PortItem.position shall carry the DN of Position. | +| portItemList | This role (when present) represents the Position capability to identify the Port Item(s) being terminated on this Position. When this role is present, the Position.portItemList shall carry the set of DN(s) of Port Item. | + +#### 7.4.78.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.79 Relation-Position-Position (M) + +#### 7.4.79.1 Definition + +This represents a bidirectional relation between the IOC Position and the IOC Position. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.79.2 Roles + +| Name | Definition | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | This role (when present) represents the Position capability to identify another Position that is connected by cross-coupling or termination to this Position. When this role is present, the Position.position shall carry the DN of Position. | +| position | The same as above. | + +#### 7.4.79.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.80 Relation-Pipe-AlarmSeverityAssignmentProfile (O) + +#### 7.4.80.1 Definition + +This represents a unidirectional relation from the IOC Pipe (including its child classes Connection, Link Connection, Sub Network Connection, and Trail) to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.80.2 Roles + +| Name | Definition | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Pipe (including its child classes Connection, Link Connection, Sub Network Connection, and Trail) capability to identify the Alarm Severity Assignment Profile that is associated with this Pipe. When this role is present, the Pipe.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +### 7.4.80.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 7.4.81 Relation-Pipe-ManagedEntity (O) + +### 7.4.81.1 Definition + +This represents a unidirectional relation from the IOC `Pipe` (including its child classes `Connection`, `Link Connection`, `Sub Network Connection`, and `Trail`) to the `ProxyClass Managed Entity`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.81.2 Roles + +| Name | Definition | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Pipe (including its child classes Connection , Link Connection , Sub Network Connection , and Trail ) capability to identify the list of Managed Entities that are capable of directly affecting this Pipe . When this role is present, the Pipe.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +### 7.4.81.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 7.4.82 Relation-Pipe-aEnd\_NetworkTerminationPoint (M) + +### 7.4.82.1 Definition + +This represents a unidirectional relation from the IOC `Pipe` (including its child classes `Connection`, `Link Connection`, `Sub Network Connection`, and `Trail`) to the IOC `Network Termination Point` (including its child classes `Network TTP Source`, `Network TTP Bidirectional`, `Network CTP Source`, and `Network CTP Bidirectional`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.82.2 Roles + +| Name | Definition | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aEndNetworkTPList | This role represents the Pipe (including its child classes Connection , Link Connection , Sub Network Connection , and Trail ) capability to identify the list of source or bidirectional Network Termination Points that this Pipe points to. When this role is present, the Pipe.aEndNetworkTPList shall carry the set of DN(s) of child classes of Network Termination Point (including Network TTP Source , Network TTP Bidirectional , Network CTP Source , and Network CTP Bidirectional ). | + +### 7.4.82.3 Constraint + +| Name | Definition | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| source_or_bidirectional_TPs | If the Pipe is bidirectional, the aEndNetworkTPList shall also be bidirectional. If the Pipe is unidirectional, the aEndNetworkTPList shall be the source TPs or bidirectional TPs. For unidirectional connections, the aEndNetworkTPList attribute shall identify the source end. | + +## 7.4.83 Relation-Pipe-zEnd\_NetworkTerminationPoint (M) + +### 7.4.83.1 Definition + +This represents a unidirectional relation from the IOC `Pipe` (including its child classes `Connection`, `Link Connection`, `Sub Network Connection`, and `Trail`) to the IOC `Network Termination Point` (including its child classes `Network TTP Sink`, `Network TTP Bidirectional`, `Network CTP Sink`, and `Network CTP Bidirectional`). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.83.2 Roles + +| Name | Definition | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| zEndNetworkTPList | This role represents the Pipe (including its child classes Connection , Link Connection , Sub Network Connection , and Trail ) capability to identify the list of sink or bidirectional Network Termination Points that this Pipe points to. When this role is present, the Pipe.zEndNetworkTPList shall carry the set of DN(s) of child classes of Network Termination Point (including Network TTP Sink , Network TTP Bidirectional , Network CTP Sink , and Network CTP Bidirectional ). | + +### 7.4.83.3 Constraint + +| Name | Definition | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| source_or_bidirectional_TPs | If the Pipe is bidirectional, the zEndNetworkTPList shall also be bidirectional. If the Pipe is unidirectional, the zEndNetworkTPList shall be the source TPs or bidirectional TPs. For unidirectional connections, the zEndNetworkTPList attribute shall identify the source end. | + +## 7.4.84 Relation-ScanPoint-AlarmSeverityAssignmentProfile (O) + +### 7.4.84.1 Definition + +This represents a unidirectional relation from the IOC `Scan Point` to the IOC `Alarm Severity Assignment Profile`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.84.2 Roles + +| Name | Definition | +|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Scan Point capability to identify the Alarm Severity Assignment Profile that is associated with this Scan Point . When this role is present, the ScanPoint.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile . | + +#### 7.4.84.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.85 Relation-SiteRelationship-aEnd\_CrossCouplingSite (M) + +##### 7.4.85.1 Definition + +This represents a bidirectional relation between the IOC Site Relationship and the IOC Cross-Coupling Site. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.85.2 Roles + +| Name | Definition | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| a-EndSite | This role (when present) represents the Site Relationship capability to identify one Cross-Coupling Site that this Site Relationship points to using the a-EndSite. When this role is present, the SiteRelationship.a-EndSite shall carry the DN of Cross-Coupling Site. | +| a-EndSiteRelationshipList | This role (when present) represents the Cross-Coupling Site capability to identify the list of Site Relationships whose a-EndSite points to this Cross-Coupling Site. When this role is present, the Cross-CouplingSite.a-EndSiteRelationshipList shall carry the set of DN(s) of Site Relationship. | + +##### 7.4.85.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.86 Relation-SiteRelationship-bEnd\_CrossCouplingSite (M) + +##### 7.4.86.1 Definition + +This represents a bidirectional relation between the IOC Site Relationship and the IOC Cross-Coupling Site. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.86.2 Roles + +| Name | Definition | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| b-EndSite | This role (when present) represents the Site Relationship capability to identify the other Cross-Coupling Site that this Site Relationship points to using the b-EndSite. When this role is present, the SiteRelationship.b-EndSite shall carry the DN of Cross-Coupling Site. | +| b-EndSiteRelationshipList | This role (when present) represents the Cross-Coupling Site capability to identify the list of Site Relationships whose b-EndSite points to this Cross-Coupling Site. When this role is present, the Cross-CouplingSite.b-EndSiteRelationshipList shall carry the set of DN(s) of Site Relationship. | + +#### 7.4.86.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.87 Relation-Software-AlarmSeverityAssignmentProfile (O) + +##### 7.4.87.1 Definition + +This represents a unidirectional relation from the IOC Software to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.87.2 Roles + +| Name | Definition | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Software capability to identify the Alarm Severity Assignment Profile that is associated with this Software. When this role is present, the Software.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +##### 7.4.87.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.88 Relation-Software-ManagedEntity (O) + +##### 7.4.88.1 Definition + +This represents a unidirectional relation from the IOC Software to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.88.2 Roles + +| Name | Definition | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| affectedObjectList | This role (when present) represents the Software capability to identify the list of Managed Entities that can be directly affected by a change in state or deletion of this Software. When this role is present, the Software.affectedObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +##### 7.4.88.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.89 Relation-SubNetwork-AbstractLink-1 (O) + +##### 7.4.89.1 Definition + +This represents a unidirectional relation from the IOC Sub Network to the IOC Abstract Link (including its subclasses Topological Link and Logical Link). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.89.2 Roles + +| Name | Definition | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedLinkList | This role (when present) represents the Sub Network capability to identify the list of Abstract Links (including its child classes) that are contained in this Sub Network through partitioning. When this role is present, the SubNetwork.containedLinkList shall carry the set of DN(s) of child classes of Abstract Link (Topological Link, Logical Link). | + +##### 7.4.89.3 Constraint + +| Name | Definition | +|-------------------------------|---------------------------------------------------------------------------| +| partitioning_supported | There are contained links in the Sub Network (partitioning is supported). | + +#### 7.4.90 Relation-SubNetwork-AbstractLink-2 (O) + +##### 7.4.90.1 Definition + +This represents a unidirectional relation from the IOC Sub Network to the IOC Abstract Link (including its subclasses Topological Link and Logical Link). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.90.2 Roles + +| Name | Definition | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| linkPointerList | This role (when present) represents the Sub Network capability to identify the list of Abstract Links (including its subclasses) that are terminated by this Sub Network. When this role is present, the SubNetwork.linkPointerList shall carry the set of DN(s) of child classes of Abstract Link (Topological Link, Logical Link). | + +##### 7.4.90.3 Constraint + +| Name | Definition | +|--------------------------------------|-------------------------------------------| +| link_terminated_by_SubNetwork | A link is terminated by this sub network. | + +#### 7.4.91 Relation-SubNetwork-AbstractLinkEnd (O) + +##### 7.4.91.1 Definition + +This represents a bidirectional relation between the IOC Sub Network to the IOC Abstract Link End (including its child classes Topological Link End and Logical Link End). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.91.2 Roles + +| Name | Definition | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedLinkEndList | This role (when present) represents the Sub Network capability to identify the list of Abstract Link Ends (including its subclasses) that are contained in this Sub Network through partitioning. When this role is present, the SubNetwork.containedLinkEndList shall carry the set of DN(s) of child classes of Abstract Link End (Topological Link End, Logical Link End). | +| containedInSubNetworkList | This role (when present) represents the Abstract Link End capability to identify the list of parent Sub Networks that contain this Abstract Link End. When this role is present, the Abstract Link End.containedInSubNetworkList shall carry the set of DN(s) of Sub Network. | + +#### 7.4.91.3 Constraint + +| Name | Definition | +|-------------------------------|---------------------------------------------------------------------------------------| +| partitioning_supported | There are contained link ends in the subnetwork instance (partitioning is supported). | + +### 7.4.92 Relation-SubNetwork-AccessGroup (O) + +#### 7.4.92.1 Definition + +This represents a bidirectional relation between the IOC `Sub Network` and the IOC `Access Group`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.92.2 Roles + +| Name | Definition | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedAccessGroupList | This role (when present) represents the Sub Network capability to identify the list of Access Groups that are contained in this Subnetwork. When this role is present, the SubNetwork.containedAccessGroupList shall carry the set of DN(s) of Access Group . | +| containedInSubNetworkList | This role (when present) represents the Access Group capability to identify the list of parent Sub Networks that contain this Access Group . When this role is present, the AccessGroup.containedInSubNetworkList shall carry the set of DN(s) of Sub Network . | + +#### 7.4.92.3 Constraint + +| Name | Definition | +|-------------------------------|---------------------------------------------------------------------------------------------------------| +| partitioning_supported | This relation is present when an Access Group is contained in a Sub Network . | + +### 7.4.93 Relation-SubNetwork-ManagedEntity (O) + +#### 7.4.93.1 Definition + +This represents a unidirectional relation from the IOC `Sub Network` to the `ProxyClass Managed Entity`. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.93.2 Roles + +| Name | Definition | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Sub Network capability to identify the list of Managed Entities that are capable of directly affecting this Sub Network. When this role is present, the SubNetwork.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.93.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.94 Relation-SubNetwork-NetworkTerminationPoint (O) + +#### 7.4.94.1 Definition + +This represents a unidirectional relation from the IOC Sub Network to the IOC Network Termination Point (including its child classes Network CTP Source, Network CTP Sink, Network CTP Bidirectional, Network TTP Source, Network TTP Sink, and Network TTP Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.94.2 Roles + +| Name | Definition | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedNetworkTPList | This role (when present) represents the Sub Network capability to identify the list of Network Termination Points that are contained in this Sub Network. When this role is present, the SubNetwork.containedNetworkTPList shall carry the set of DN(s) of child classes of Network Termination Point (Network CTP Source, Network CTP Sink, Network CTP Bidirectional, Network TTP Source, Network TTP Sink, and Network TTP Bidirectional). | + +#### 7.4.94.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.95 Relation-SubNetwork-SubNetwork (O) + +#### 7.4.95.1 Definition + +This represents a bidirectional relation between the IOC Sub Network and the IOC Sub Network. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.95.2 Roles + +| Name | Definition | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedSubNetworkList | This role (when present) represents the Sub Network capability to identify the list of Sub Networks that are contained in this Sub Network through partitioning. When this role is present, the SubNetwork.containedSubNetworkList shall carry the set of DN(s) of Sub Network. | +| containedInSubNetworkList | This role (when present) represents the Sub Network capability to identify the list of parent Sub Networks that contain this Sub Network. When this role is present, the SubNetwork.containedInSubNetworkList shall carry the set of DN(s) of Sub Network. | + +#### 7.4.95.3 Constraint + +| Name | Definition | +|-------------------------------|----------------------------------------------------------------------------------| +| partitioning_supported | This relation is present when a Sub Network is contained in another Sub Network. | + +### 7.4.96 Relation-SubNetworkConnection-LinkConnection (O) + +#### 7.4.96.1 Definition + +This represents a bidirectional relation between the IOC Sub Network Connection and the IOC Link Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.96.2 Roles + +| Name | Definition | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| componentPointers | This role (when present) represents the Sub Network Connection capability to identify the list of Link Connections that are components of the Sub Network Connection, within a given layer. When this role is present, the SubNetworkConnection.componentPointers shall carry the ordered set of DN(s) of Link Connection and Sub Network Connection. | +| compositePointer | This role (when present) represents the Link Connection capability to identify a Sub Network Connection that is composed of a sequence of Link Connections or Sub Network Connections in the same layer, including this Link Connection. When this role is present, the LinkConnection.compositePointer shall carry the DN of Sub Network Connection. | + +#### 7.4.96.3 Constraint + +| Name | Definition | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| composed_SubNetworkConnection | This relation is present when a Sub Network Connection is composed of other SubNetwork Connections and Link Connections in the same layer. | + +### 7.4.97 Relation-SubNetworkConnection-SubNetworkConnection (O) + +#### 7.4.97.1 Definition + +This represents a bidirectional relation between the IOC Sub Network Connection and the IOC Sub Network Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.97.2 Roles + +| Name | Definition | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| componentPointers | This role (when present) represents the Sub Network Connection capability to identify the list of Sub Network Connections that are components of this Sub Network Connection, within a given layer. When this role is present, the SubNetworkConnection.componentPointers shall carry the ordered set of DN(s) of Sub Networks and Link Connections. | +| compositePointer | This role (when present) represents the Sub Network Connection capability to identify a Sub Network Connection that is composed of a sequence of Sub Network Connections or Link Connections in the same layer, including this Sub Network Connection. When this role is present, the SubNetworkConnection.compositePointer shall carry the DN of Sub Network Connection. | + +#### 7.4.97.3 Constraint + +| Name | Definition | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| composed_SubNetworkConnection | This relation is present when a Sub Network Connection is composed of other SubNetwork Connections and Link Connections in the same layer. | + +### 7.4.98 Relation-Termination-Cross-CouplingSite (M) + +#### 7.4.98.1 Definition + +This represents a bidirectional relation between the IOC Termination and the IOC Cross-Coupling Site. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.98.2 Roles + +| Name | Definition | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cross-couplingSite | This role (when present) represents the Termination capability to identify the Cross-Coupling Site that this Termination belongs to. When this role is present, the Termination.cross-couplingSite shall carry the DN of Cross-Coupling Site. | +| terminationList | This role (when present) represents the Cross-Coupling Site capability to identify the list of Terminations that this Cross-Coupling Site has for each trail. When this role is present, the Cross-CouplingSite.terminationList shall carry the set of DN(s) of Termination. | + +#### 7.4.98.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.99 Relation-TerminationPoint-AlarmSeverityAssignmentProfile (O) + +#### 7.4.99.1 Definition + +This represents a unidirectional relation from the IOC Termination Point (including its child classes Trail/Connection Termination Point Source/Sink/Bidirectional, Network CTP/TTP Source/Sink/Bidirectional) to the IOC Alarm Severity Assignment Profile. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.99.2 Roles + +| Name | Definition | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentProfilePointer | This role (when present) represents the Termination Point (including its child classes Trail/Connection Termination Point Source/Sink/Bidirectional, Network CTP/TTP Source/Sink/Bidirectional) capability to identify the Alarm Severity Assignment Profile that is associated with this Termination Point. When this role is present, the TerminationPoint.alarmSeverityAssignmentProfilePointer shall carry the DN of Alarm Severity Assignment Profile. | + +#### 7.4.99.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.100 Relation-TerminationPoint-ManagedEntity (M) + +#### 7.4.100.1 Definition + +This represents a unidirectional relation from the IOC Termination Point (including its child classes Trail/Connection Termination Point Source/Sink/Bidirectional, Network CTP/TTP Source/Sink/Bidirectional) to the ProxyClass Managed Entity. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.100.2 Roles + +| Name | Definition | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedByObjectList | This role (when present) represents the Termination Point (including its child classes Trail/Connection Termination Point Source/Sink/Bidirectional, Network CTP/TTP Source/Sink/Bidirectional) capability to identify the list of Managed Entity that is capable of directly affecting this Termination Point. When this role is present, the TerminationPoint.supportedByObjectList shall carry the set of DN(s) of Managed Entity (to be replaced by the actual IOCs). | + +#### 7.4.100.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.101 Relation-TerminationPointPool-GroupTerminationPoint (M) + +#### 7.4.101.1 Definition + +This represents a unidirectional relation from the IOC Termination Point Pool to the IOC Group Termination Point. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.101.2 Roles + +| Name | Definition | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tpsInTpPoolList | This role (when present) represents the Termination Point Pool capability to identify the Termination Points and Group Termination Points that are represented by this Termination Point Pool. When this role is present, the TerminationPointPool.tpsInTpPoolList shall carry the set of DN(s) of Group Termination Points or child classes of Termination Points. | + +#### 7.4.101.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.102 Relation-TerminationPointPool-TerminationPoint (M) + +#### 7.4.102.1 Definition + +This represents a unidirectional relation from the IOC Termination Point Pool to the IOC Termination Point (including its child classes). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.102.2 Roles + +| Name | Definition | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tpsInTpPoolList | This role (when present) represents the Termination Point Pool capability to identify the Termination Points and Group Termination Points that are represented by this Termination Point Pool. When this role is present, the TerminationPointPool.tpsInTpPoolList shall carry the set of DN(s) of Group Termination Points or child classes of Termination Points. | + +#### 7.4.102.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.103 Relation-TopologicalLink-Trail (M) + +#### 7.4.103.1 Definition + +This represents a bidirectional relation between the IOC Topological Link and the IOC Trail. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.103.2 Roles + +| Name | Definition | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTrail | This role (when present) represents the Topological Link capability to identify the Trail in the server layer that supports the Topological Link in a client layer. When this role is present, the TopologicalLink.serverTrail shall carry the DN of Trail. | +| clientLinkPointerList | This role (when present) represents the Trail capability to identify the Topological Links that reflect the capacity of the Trail in the client layer network domain(s). When this role is present, the Trail.clientLinkPointerList shall carry the set of DN(s) of Topological Link. | + +### 7.4.103.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 7.4.104 Relation-TopologicalLinkEnd-NetworkTTP (M) + +### 7.4.104.1 Definition + +This represents a unidirectional relation from the IOC Topological Link End to the ProxyClass Network TTP (can be Network TTP Source, Network TTP Sink, and Network TTP Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.104.2 Roles + +| Name | Definition | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serverTTPPointer | This role (when present) represents the Topological Link End capability to identify the list of Network TTPs that may serve this Topological Link End in another layer. When this role is present, the TopologicalLinkEnd.serverTTPPointer shall carry the set of DN(s) of the following IOCs: Network TTP Source, Network TTP Sink or Network TTP Bidirectional. | + +### 7.4.104.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 7.4.105 Relation-Trail-SubNetworkConnection (O) + +### 7.4.105.1 Definition + +This represents a unidirectional relation from the IOC Trail to the IOC Sub Network Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +### 7.4.105.2 Roles + +| Name | Definition | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| connectionList | This role (when present) represents the Trail capability to identify the list of Sub Network Connections and Link Connections in a given layer which may compose the Trail in the same layer. When this role is present, the Trail.connectionList shall carry the ordered set of DN(s) of Link Connection and Sub Network Connection. | + +### 7.4.105.3 Constraint + +| Name | Definition | +|--------------------------------|---------------------------------------------------| +| connection_serves_trail | The sub network connection serves a client trail. | + +## 7.4.106 Relation-Trail [ITU-T M.1401]-Position (M) + +### 7.4.106.1 Definition + +This represents a bidirectional relation between the IOC Trail and the IOC Position. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.106.2 Roles + +| Name | Definition | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | This role (when present) represents the Trail [ITU-T M.1401] capability to identify the Position that terminates the Trail. When this role is present, the Trail [ITU-T M.1401].position shall carry the DN of Position. | +| trailList | This role (when present) represents the Position capability to identify the Trail(s) being terminated on this Position. When this role is present, the Position.trailList shall carry the set of DN(s) of Trail [ITU-T M.1401]. | + +#### 7.4.106.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.107 Relation-TrailMultiplexChannel-Position (M) + +#### 7.4.107.1 Definition + +This represents a bidirectional relation between the IOC Trail Multiplex Channel and the IOC Position. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.107.2 Roles + +| Name | Definition | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | This role (when present) represents the Trail Multiplex Channel capability to identify the Position on which the Trail multiplex channel is terminated. When this role is present, the TrailMultiplexChannel.position shall carry the DN of Position. | +| trailMultiplexChannelList | This role (when present) represents the Position capability to identify the Trail Multiplex Channel(s) being terminated on this Position. When this role is present, the Position.trailMultiplexChannelList shall carry the set of DN(s) of Trail Multiplex Channel. | + +#### 7.4.107.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.108 Relation-TrailSection-PhysicalLinkConnection (M) + +#### 7.4.108.1 Definition + +This represents a bidirectional relation between the IOC Trail Section and the IOC Physical Link Connection. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.108.2 Roles + +| Name | Definition | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physicalLinkConnection | This role (when present) represents the Trail Section capability to identify the Physical Link Connection that is included in the routing of the Trail. When this role is present, the TrailSection.physicalLinkConnection shall carry the DN of Physical Link Connection. | +| trailSection | This role (when present) represents the Physical Link Connection capability to identify the Trail Section whose routing of the Trail includes the Physical Link Connection. When this role is present, the PhysicalLinkConnection.trailSection shall carry the DN of Trail Section. | + +#### 7.4.108.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.109 Relation-TrailSection-PortItem (M) + +##### 7.4.109.1 Definition + +This represents a bidirectional relation between the IOC Trail Section and the IOC Port Item. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +##### 7.4.109.2 Roles + +| Name | Definition | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| portItem | This role (when present) represents the Trail Section capability to identify the Port Item that is included in the routing of the Trail. When this role is present, the TrailSection.portItem shall carry the DN of Port Item. | +| trailSection | This role (when present) represents the Port Item capability to identify the Trail Section in a Trail. When this role is present, the PortItem.trailSection shall carry the DN of Trail Section. | + +##### 7.4.109.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +#### 7.4.110 Relation-TrailSection-Position (M) + +##### 7.4.110.1 Definition + +This represents a bidirectional relation between the IOC Trail Section and the IOC Position. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.110.2 Roles + +| Name | Definition | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| position | This role (when present) represents the Trail Section capability to identify the Position that is included in the routing of the Trail. When this role is present, the TrailSection.position shall carry the DN of Position. | +| trailSectionList | This role (when present) represents the Position capability to identify the Trail Section(s) whose routing of the Trail includes the Position. When this role is present, the Position.trailSectionList shall carry the set of DN(s) of Trail Section. | + +#### 7.4.110.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.111 Relation-TrailSection-Trail [ITU-T M.1401] (M) + +#### 7.4.111.1 Definition + +This represents a bidirectional relation between the IOC Trail Section and the IOC Trail [ITU-T M.1401]. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.111.2 Roles + +| Name | Definition | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| trail | This role (when present) represents the Trail Section capability to identify the Trail [ITU-T M.1401] that is included in the routing of the Trail. When this role is present, the TrailSection.trail shall carry the DN of Trail [ITU-T M.1401]. | +| routingTrailSection | This role (when present) represents the Trail [ITU-T M.1401] capability to identify the Trail Section in the routing of another Trail, which is routed on the current Trail [ITU-T M.1401]. When this role is present, the Trail.routingTrailSection shall carry the DN of Trail Section. | + +#### 7.4.111.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.112 Relation-TrailSection-TrailMultiplexChannel (M) + +#### 7.4.112.1 Definition + +This represents a bidirectional relation between the IOC Trail Section and the IOC Trail Multiplex Channel. + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.112.2 Roles + +| Name | Definition | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| trailMultiplexChannel | This role (when present) represents the Trail Section capability to identify the Trail Multiplex Channel that is included in the routing of the Trail. When this role is present, the TrailSection.trailMultiplexChannel shall carry the DN of Trail Multiplex Channel. | +| trailSection | This role (when present) represents the Trail Multiplex Channel capability to identify the Trail Section in the routing of the Trail. When this role is present, the TrailMultiplexChannel.trailSection shall carry the DN of Trail Section. | + +#### 7.4.112.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.113 Relation-TrailTerminationPointSink-TerminationPoint (M) + +#### 7.4.113.1 Definition + +This represents a unidirectional relation from the IOC Trail Termination Point Sink to the IOC Termination Point (including its child classes Trail Termination Point Source, Trail Termination Point Bidirectional, Connection Termination Point Sink, Connection Termination Point Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.113.2 Roles + +| Name | Definition | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| upstreamConnectivityPointer | This role (when present) represents the Trail Termination Point Sink capability to identify the Termination Point within the same ME, which sends information (traffic) to this Termination Point at the same layer, or is null. When this role is present, the TrailTerminationPointSink.upstreamConnectivityPointer shall carry the set of DN(s) of the following IOCs: Trail Termination Point Source, Trail Termination Point Bidirectional, Connection Termination Point Sink, Connection Termination Point Bidirectional. | + +#### 7.4.113.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +### 7.4.114 Relation-TrailTerminationPointSource-TerminationPoint (M) + +#### 7.4.114.1 Definition + +This represents a unidirectional relation from the IOC Trail Termination Point Source to the IOC Termination Point (including its child classes Trail Termination Point Sink, Trail Termination Point Bidirectional, Connection Termination Point Source, Connection Termination Point Bidirectional). + +The role of the relation shall be mapped to a reference attribute of the IOC. The name of the reference attribute shall be the role name. + +#### 7.4.114.2 Roles + +| Name | Definition | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamConnectivityPointer | This role (when present) represents the Trail Termination Point Source capability to identify the Termination Point within the same ME, which receives information (traffic) from this Termination Point at the same layer, or is null. When this role is present, the TrailTerminationPointSource.downstreamConnectivityPointer shall carry the set of DN(s) of the following IOCs: Trail Termination Point Sink, Trail Termination Point Bidirectional, Connection Termination Point Source, Connection Termination Point Bidirectional. | + +#### 7.4.114.3 Constraint + +| Name | Definition | +|------|------------| +| – | – | + +## 8 Common information definitions + +### 8.1 Attributes + +Table 179 + +| Name | Type | Description | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| accessGroupId |
NameType ::= CHOICE {     numericName    INTEGER,     pString        String } String ::= GraphicString
| This attribute is the identifier of an instance of this managed object class. | +| accessPointList |
TPList ::= SET OF DistinguishedName
| The Access Point List attribute lists all the Network Trail Termination Points or Flow Termination Points within an instance of the IOC Access Group. | +| acceptableCircuitPackTypeList |
AcceptableCircuitPackTypeList ::= SET OF String
| This attribute indicates the types of the circuit packs that can be contained in an equipment holder object. | +| accountContactList |
AccountContactList ::= SET OF PersonReach PersonReach ::= SEQUENCE {     number    PersonNumber,     name      PersonName,     phone     PersonPhone OPTIONAL,     loc       PersonLocation OPTIONAL,     email     PersonEmail OPTIONAL,     fax       PersonFax OPTIONAL,     respon    PersonRespon OPTIONAL,     ... } PersonEmail ::= String (SIZE(0..64)) PersonFax ::= String (SIZE(0..64)) PersonLocation ::= PremisesAddress PersonName ::= String (SIZE(0..64)) PersonNumber ::= String (SIZE(0..64)) PersonPhone ::= String (SIZE(0..64)) PersonRespon ::= String (SIZE(0..64))
| The Account Contact List attribute specifies the individuals in the manager's organization, who can be contacted regarding the account. | + +**Table 179** + +| Name | Type | Description | +|---------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| accountName | AccountName ::= String(SIZE(0..64)) | The Account Name attribute is the name given to an account by the customer, where an account is a customer or agency entity that may be billed by the service provider or that may take responsibility for performing network management services for the customer. The Account Name is the RDN of the Account object. | +| additionalText | AdditionalText ::= String(SIZE (0..256)) | The Additional Text attribute contains additional pertinent enterprise information that describes the Account. This enterprise information pertains to the way the customer and the service provider interact when conducting business. | +| administrativeState | AdministrativeState ::= ENUMERATED {
locked,
unlocked,
shuttingDown
} | This attribute is to indicate the administrative state of the managed entity, which has three possible values: locked, unlocked, and shuttingDown. See [ITU-T X.731] for details. | +| aEnd | ObjectInstance ::= DistinguishedName | This attribute is a pointer to a subnetwork, a link end or an access group in the same network layer domain. | +| aEndFTPLIST | ObjectList ::= SET OF DistinguishedName | The value of this attribute identifies one or more Flow Termination Point instances, which represents the source end of a connectionless Trail. This attribute cannot be null. | +| aEndNetworkTPList | ObjectList | The value of this attribute identifies one or more network termination points of an instance of a subclass of the Connectivity object class. This attribute cannot be null. | +| aEndofFPPLink | ObjectInstance | This attribute is a pointer to a flow domain, a flow point pool or an access group in the same network layer domain. This attribute identifies the end of the FPP link at one extremity. | +| affectedObjectList | ObjectList | The Affected Object List attribute type specifies the object instances which can be directly affected by a change in state or deletion of a given managed object. The attribute does not force internal details to be specified, but only the necessary level of detail required for management. | + +Table 179 + +| Name | Type | Description | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmSeverityAssignmentList |
 AlarmSeverityAssignmentList ::=     SET OF AlarmSeverityAssignment AlarmSeverityAssignment ::= SEQUENCE {     problem     ProbableCause,     severityAssignedServiceAffecting         AlarmSeverityCode OPTIONAL,     severityAssignedNonServiceAffecting         AlarmSeverityCode OPTIONAL,     severityAssignedServiceIndependent         AlarmSeverityCode OPTIONAL } AlarmSeverityCode ::= ENUMERATED {     non-alarmed(0),     minor(1),     major(2),     critical(3),     warning(4) } ProbableCause ::= CHOICE {     globalValue     OBJECT IDENTIFIER,     localValue      INTEGER } 
|

The Alarm Severity Assignment List is an attribute type whose value provides a listing of all abnormal conditions that may exist in instances of an object class, and shows the assigned alarm severity information (minor, major, etc.) for each condition.

| +| alarmSeverityAssignmentProfilePointer |
 PointerOrNull ::= CHOICE {     pointer     DistinguishedName,     null        NULL } 
|

This attribute identifies an Alarm Severity Assignment Profile object.

| + +Table 179 + +| Name | Type | Description | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmStatus |
AlarmStatus ::= ENUMERATED {     cleared,     activeReportable-Indeterminate,     activeReportable-Warning,     activeReportable-Minor,     activeReportable-Major,     activeReportable-Critical,     activePending }
|

The Alarm Status attribute type indicates the occurrence of an abnormal condition relating to an object. This attribute may also function as a summary indicator of alarm conditions associated with a specific resource. It is used to indicate the existence of an alarm condition, a pending alarm condition such as threshold situations, or (when used as a summary indicator) the highest severity of active alarm conditions. When used as a summary indicator, the order of severity (from highest to lowest) is:
activeReportable-Critical
activeReportable-Major
activeReportable-Minor
activeReportable-Indeterminate
activeReportable-Warning
activePending
cleared.

| +| alarmStatusList |
AlarmStatusList ::= SET OF AlarmStatus
|

The Alarm Status List attribute type describes criteria for inclusion in a current alarm summary report. The Alarm Status List consists of a set of possible Alarm Status. In order to be included in a current alarm summary report, an object shall have an Alarm Status that matches one of the states in the Alarm Status List.
If the Alarm Status List has null value, the Alarm Status of the objects in the Object List is not used as a criterion for inclusion in the current alarm summary report.

| +| aliasName |
AliasName ::= String
|

Customer supplied alias identifier for an IOC instance.

| +| allomorphs |
Allomorphs ::= SET OF ObjectClass
| | +| arcDefaultNALMCDInterval |
ArcDefaultNALMCDInterval ::= ArcTime ArcTime ::= CHOICE {     noAdjustment    NULL,     time            ArcInterval -- minutes } ArcInterval ::= INTEGER (0..5940) -- minutes (max of 99 hours)
|

This attribute defines the default/initial value for the ARC interval timer of the ARC nalm-ti state if another interval is not specified in the management request to transition to the state.

| + +Table 179 + +| Name | Type | Description | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| arcDefaultNALMTIInterval | ArcDefaultNALMTIInterval ::= ArcTime | This attribute defines the default/initial value for the ARC interval timer of the ARC nalm-ti state if another interval is not specified in the management request to transition to the state. | +| a-TPInstance | RelatedObjectInstance ::= CHOICE {
notAvailable NULL,
relatedObject DistinguishedName
} | The A-Termination Point Instance attribute type identifies one of the two termination points of an instance of the connectivity object class or one of its subclasses. | +| availabilityStatus | AvailabilityStatus ::= SET OF INTEGER {
inTest(0),
failed(1),
powerOff(2),
offline(3),
offDuty(4),
dependency(5),
degraded(6),
notInstalled(7),
logFull(8)
} | This attribute indicates the availability status of instances of the IOC. | +| availableLinkCapacity | Capacity ::= CHOICE {
numberOfLinkConnections INTEGER,
bandwidth Bandwidth
}
Bandwidth ::= SEQUENCE OF SEQUENCE {
ingress INTEGER,
egress INTEGER
} -- (Units: kbit/s) | This attribute indicates the available capacity of a link expressed as either the number of link connections that are available or the bandwidth that is available to that link. | +| availableLinkEndCapacity | PointCapacity ::= CHOICE {
numberOfTPs INTEGER,
bandwidth Bandwidth
} | This attribute indicates the number of Network CTPs associated with a Link End that has spare capacity or the amount of spare bandwidth associated with a Link End. | +| availableSignalRateList | AvailableSignalRateList ::= SET OF SignalRate
SignalRate ::= CHOICE {
objectClass OBJECT IDENTIFIER,
characteristicInformation CharacteristicInformation
} | This attribute identifies the signal rates supported by the circuit pack entity. | + +Table 179 + +| Name | Type | Description | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bandwidth | M3108-1-Bandwidth ::= CHOICE {
bitsPerSecond       Number,
kiloBitsPerSecond   Number,
megaBitsPerSecond   Number,
gigaBitsPerSecond   Number,
teraBitsPerSecond   Number
}
Number ::= INTEGER | | +| channelNumber | ChannelNumber ::= INTEGER | | +| characteristicInformation | CharacteristicInformation ::= OBJECT IDENTIFIER | The value of this attribute is used to verify the connectability of instances of the termination point subclasses. | +| circuitDirectionality | CircuitDirectionality ::= ENUMERATED {
onewayOut,
onewayIn,
twoway
} | The attribute type specifies the directionality of the circuits in the circuit subgroup. | +| clientCTPList | ObjectList | This attribute defines the CTP or list of CTPs which are clients of a TTP or TTPs in another layer. Usually a single TTP in a higher order layer will support a number of CTPs in a lower order layer. Alternatively, where concatenation is used, a number of TTPs in a lower order layer may serve a CTP or CTPs in a higher order layer. | +| clientFlowPointPoolList | ObjectList | This attribute is a set of pointers to the Flow Point Pools in the client that are supported later by the TTP instance. | +| clientFPList | ObjectList | This attribute defines the FP or list of FPs which are clients of a FTP or FTPs in another layer. Usually a single FTP in a higher order layer will support a number of FPs in a lower order layer. Alternatively, where concatenation is used, a number of FTPs in a lower order layer may serve a FP or FPs in a higher order layer. | +| clientLinkConnectionPointerList | ObjectList | This attribute is a set of pointers to the link connections in the client layer network domain(s) that are supported by the trail. | + +Table 179 + +| Name | Type | Description | +|--------------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| clientLinkEndPointerList | ObjectList | This attribute is a set of pointers to the link ends that reflect the properties of a network trail termination point in the client layer network domain(s). | +| clientLinkPointerList | ObjectList | This attribute is a set of pointers to the topological links (also including FPP Links) that reflect the capacity of a trail in the client layer network domain(s). | +| clientTrail | ObjectInstance | The value of this attribute identifies the trail object instance in the same network layer as the connection served by a connection object. | +| componentPointers | ObjectList | This attribute is used where the Sub Network Connection is made up of a number of component Sub Network Connections and Link Connections within the same layer. | +| compositePointer | RelatedObjectInstance | This attribute is used where the connectivity instance is a component of a Subnetwork Connection within the same layer. | +| configuredConnectivity | ConfiguredConnectivity ::= ENUMERATED {
sourceConnect,
sinkConnect,
bidirectionalConnect,
noConnect
} | This attribute indicates the configured connectivity of a Network Termination Point managed object (or subclass). The possible values for this attribute are sourceConnect, sinkConnect, bidirectionalConnect and noConnect. For a Network Termination Point managed object with pointDirectionality equal to sink, the allowed values for this attribute are noConnect and sinkConnect. For a Network Termination Point managed object with pointDirectionality equal to source, the allowed values for this attribute are noConnect and sourceConnect. For a Network Termination Point managed object with pointDirectionality equal to bidirectional, the allowed values for this attribute are noConnect and bidirectionalConnect. For some technologies, sinkConnect and sourceConnect may also be allowed for a bidirectional Network Termination Point managed object. | +| connectedTpCount | Count ::= INTEGER | This attribute indicates the total number of termination points associated with a tpPool that have been connected. | + +Table 179 + +| Name | Type | Description | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| connectionlessTrailId | NameType | This attribute is the identifier of an instance of Connectionless Trail IOC. | +| connectionlessTrailPointer | ObjectInstance | This attribute points to the connectionless trail terminated by a flow termination point source/sink. | +| connectionList | ObjectList | This attribute defines the list of Link Connections and subnetwork connections in a given layer which may compose a Trail in the same layer. This composition of Connectivity instances may be a simple sequence or, in the multipoint case, a tree structure. | +| connectivityPointer | ConnectivityPointer ::= CHOICE {
none            NULL,
single          DistinguishedName,
concatenated  SET OF DistinguishedName
} | This attribute points to the Link connection or Trail terminated by the Network Termination Point. | +| contactDetails | ContactDetails ::= String(SIZE(0..128)) | The detailed contact information. | +| contactID | SimpleNameType ::= CHOICE {
number        INTEGER,
string        String
} | The identifier of the Contact object. | +| contactCompany | ContactCompany ::= String(SIZE(64)) | This attribute specifies the company name that a specific contact works for or is associated with. | +| contactFunction | ContactFunction ::= ENUMERATED {
other,
customerMaintenanceManager,
providerMaintenanceManager,
customerAccountManager,
providerAccountManager,
fieldServiceManager,
repairman,
tester,
screener} | This attribute provides information about the work function performed by the contact person. | + +Table 179 + +| Name | Type | Description | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| contactNames | Names ::= SET OF Name
Name ::= CHOICE {
null                            NULL,
classAndInstance    SEQUENCE {
managedObjectClass    ObjectClass,
managedObjectInstance  ObjectInstance,
...
},
...
} | The contact names. | +| contactObjectPtrList | ContactObjectPtrList ::= SET OF ObjectInstance | The Contact Object Pointer List attribute points to instances of the Contact object that represents individuals in the agent's or manager's organization. | +| contactType | ContactType ::= ENUMERATED {
other,
contacts-for-equipment-related-activities,
contacts-for-location-related-activities,
contacts-for-circuit-related-activities,
contacts-for-provider-related-activities,
contacts-for-service-related-activities,
contacts-for-facility-related-activities,
contacts-for-customer-related-activities,
contacts-for-vendor-related-activities,
contacts-for-manufacturer-related-activities,
contacts-for-software-related-activities,
contacts-for-function-related-activities
} | This attribute provides information about the type of contact. | +| containedAccessGroupList | ObjectList | This attribute defines the list of Access Group instances which are contained in a Sub Network or a Flow Domain. | +| containedFlowDomainList | ObjectList | This attribute is used to describe the internal topology of a flow domain (in a given layer). This topology comprises FPP links and flow domains. The flow domains are listed in this attribute. | + +Table 179 + +| Name | Type | Description | +|----------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| containedFlowPointPoolList | ObjectList | This attribute is used to describe the internal topology of a subnetwork from the point perspective (in a given layer). This topology comprises Flow Point Pool and FPP Link. The Flow Point Pools are listed in this attribute. | +| containedFPList | ObjectList | This attribute is a list of pointers to Flow (Termination) Point instances that are contained in the Flow Domain instance. | +| containedFPPLinkList | ObjectList | This attribute is used to describe the internal topology of a flow domain (in a given layer). This topology comprises FPP links and flow domains. The FPP links are listed in this attribute. | +| containedInFlowDomainList | ObjectList | This attribute defines the list of parent Flow Domains which contain the instance of the corresponding IOC. | +| containedInSubNetworkList | ObjectList | This attribute defines the list of parent Subnetworks which contain the Access Group, Link End, or Subnetwork in a given layer. | +| containedLinkEndList | ObjectList | This attribute is used to describe the internal topology of a subnetwork from the point perspective (in a given layer). This topology comprises link ends and subnetworks. The link ends are listed in this attribute. | +| containedLinkList | ObjectList | This attribute is used to describe the internal topology of a subnetwork (in a given layer). This topology comprises links and subnetworks. The links are listed in this attribute. | +| containedNetworkTPList | ObjectList | This attribute is a list of pointers to network TPs that are contained in a subnetwork. | +| containedSubNetworkList | ObjectList | This attribute is used to describe the internal topology of a subnetwork (in a given layer). This topology comprises links and subnetworks. The subnetworks are listed in this attribute. | +| crossConnectionName | CrossConnectionName ::= String | This attribute is a descriptive name for a cross-connection or multipoint cross-connection managed object. | + +Table 179 + +| Name | Type | Description | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| crossConnectionObjectPointer |
 CrossConnectionObjectPointer ::=CHOICE {     notConnected      ObjectInstance,         -- Fabric object     connected         ObjectInstance,         -- Cross-connection object     multipleConnections MultipleConnections } MultipleConnections ::= SET OF CHOICE {     downstreamNotConnected    ObjectInstance,     downstreamConnected       ObjectInstance,     upstreamNotConnected      ObjectInstance,     upstreamConnected         ObjectInstance } 
| This attribute points to a managed object such as a Cross-connection, a GTP or a Fabric. When a termination point is neither connected nor reserved for connection, its crossConnectionObjectPointer points to the Fabric object responsible for its connection. | +| currentAlarmSummaryControlId | NameType | This current Alarm Summary Control Id is an attribute type whose distinguished value can be used as a Relative Distinguished Name (RDN) when naming an instance of the Current Alarm Summary Control managed object class. | +| currentControlState |
 ControlState ::= ENUMERATED {     closed,     open } 
| This attribute indicates the current state of the control point. | +| currentProblemList |
 CurrentProblemList ::= SET OF CurrentProblem CurrentProblem ::= SEQUENCE {     problem      ProbableCause,     alarmStatus  AlarmStatus } 
| The Current Problem List attribute type identifies the current existing problems, with severity, associated with the managed object. | +| dateOfInstallation |
 Time ::= GeneralizedTime -- without fractions of seconds, -- with time zone indication. 
| | +| directionality |
 Directionality ::= ENUMERATED {     unidirectional,     bidirectional } 
| The Directionality attribute type specifies whether the associated managed object is uni- or bidirectional. | + +**Table 179** + +| Name | Type | Description | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| downstreamConnectivityPointer | DownstreamConnectivityPointer ::= CHOICE {
none                    NULL,
single                DistinguishedName,
concatenated        SEQUENCE OF ObjectInstance,
broadcast            SET OF ObjectInstance,
broadcastConcatenated
SET OF SEQUENCE OF ObjectInstance
} | The matching for equality is applicable for all choices of the syntax. The set operations are permitted only when the choice of the syntax correspond to either broadcast or concatenated broadcast. | +| downstreamFPPointer | DownstreamFPPointer ::= CHOICE {
none                    NULL,
single                ObjectInstance,
broadcast            SET OF ObjectInstance
} | The downstream connectivity pointer attribute points to the connectionless point managed object, within the same managed element that receives information (traffic) from this connectionless point instance at the same layer, or is null. | +| electronicMailAddress | ElectronicMailAddress ::= SET OF
String(SIZE(0..64)) | This attribute specifies the electronic mail address associated with an object. | +| | EquipmentHolderAddress ::= SET OF String | This attribute indicates the physical location of the resource represented by the equipmentHolder instance. Depending on the containment hierarchy of the equipmentHolder in the managed system, the value of this attribute may vary. For example, if a system has three levels of equipment holders representing Bay, Shelf and Slot respectively (i.e., the managed Element contains multiple Bay equipment holders, each Bay equipment holder contains multiple Shelf equipment holders and each Shelf equipment holder contains multiple Slot equipment holders), then: | + +Table 179 + +| Name | Type | Description | +|------------------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |
  • – for the equipmentHolder representing a Bay, the Frame Identification code may be used as the value of this attribute;
  • – for the equipmentHolder representing a Shelf, the Bay Shelf code may be used as the value of this attribute;
  • – for the equipmentHolder representing a Slot, the position code may be used as the value of this attribute.

If the system uses only one level of equipment holder that represents the Shelves (i.e., the managedElement contains multiple Shelf equipment holders, and each Shelf equipment holder contains a circuit pack), then the value of this attribute is a sequence of the Frame Identification code and the Bay Shelf Code.

| +| equipmentHolderType | EquipmentHolderType ::= String | The equipment holder type attribute indicates the type of equipment holder using a character string. The example values for the character string may be bay, shelf, drawer, slot and rack. | +| equipmentManufacturer | EquipmentManufacturer ::= String | | +| equipmentType | EquipmentType ::= String | | +| expectedDateOfInstallation | Time | | +| externalPointId | INTEGER | This attribute identifies the port number where the monitored or controlled external device is attached. It also serves as the naming attribute for the managed object. | +| externalPointMessage | ExternalPointMessage ::= String | This attribute can provide some textual definition of the external point. It can also be used for identifying the location of the external point. | +| externalTime | ExternalTime ::= GeneralizedTime | The External time attribute provides time-of-day system time. The attribute functions as a reference for all time stamp activities in the managed element. | +| facsimileTelephoneNumberList | TelephoneNumberList ::= SET OF
TelephoneNumber (SIZE (0..64))
TelephoneNumber ::= String (SIZE (0..32)) | This attribute specifies telephone numbers for facsimile terminals associated with an object. | + +Table 179 + +| Name | Type | Description | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fDFrConnectionType |
FDFrConnectionType ::= ENUMERATED {     point-to-point,     point-to-multipoint,     multipoint-to-multipoint }
|

This attribute describes the Connection type of the FDFr instance, the possible type can be:

  • – multipoint-to-multipoint
  • – point-to-point
  • – point-to-multipoint
| +| fPList | ObjectList | This attribute lists the Flow Points (Source/Sink) represented by this managed entity. | +| fPPLinkId | NameType | This attribute is the identifier of an instance of the IOC: Flow Point Pool Link. | +| fromTermination | PointerOrNull | This attribute identifies a TTP (source or bidirectional), a CTP (sink or bidirectional) or a GTP composed of members of one of these categories. | +| holderStatus |
HolderStatus ::= CHOICE {     holderEmpty           NULL,     inTheAcceptableList   CircuitPackType,     notInTheAcceptableList CircuitPackType,     unknownType           NULL } CircuitPackType ::= PrintableString
|

The holderStatus attribute indicates the status of the physical holder. It specifies if the holder is empty or has a circuitPack of specific type (that may or not be acceptable to the holder) or has an indeterminate type.

| +| idleTpCount | Count | This attribute indicates the total number of termination points associated with a tpPool that are in an operational state of enabled and that are available for Cross-Connection. | + +Table 179 + +| Name | Type | Description | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| informationTransferCapabilities | InformationTransferCapabilities ::= ENUMERATED {
speech,
audio3pt1,
audio7,
audioComb,
digitalRestricted56,
digitalUnrestricted64
-- "..." these ellipses defined in ASN.1 amendment
-- are used here to indicate that this is
-- an extensible type and additional enumerations
-- may be added in the future
} | The attribute type specifies the different service types such as speech, 64 kbits unrestricted data supported by the circuit subgroup. | +| inputFPList | ObjectList | This attribute identifies the list of input flow (termination) points of a flow domain fragment instance. | +| intervalsOfDay | IntervalsOfDay ::= SET OF SEQUENCE {
intervalStart    Time24,
intervalEnd      Time24
}
Time24 ::= SEQUENCE {
hour          INTEGER (0..23),
minute      INTEGER (0..59)
} | See [ITU-T X.734] for details. | +| kind | Kind ::= String | This attribute holds a string representing the name of an object class for which the AttributeRanges instance is defining attribute ranges. | +| labelOfFarEndExchange | UserLabel ::= String | This attribute type assigns a user friendly name to the Far End Exchange terminating this circuit subgroup. | +| linkConnectionPointerList | ObjectList | This attribute defines the list of Link Connections in a given layer which may compose a Logical Link in the same layer. | +| linkDirectionality | LinkDirectionality ::= ENUMERATED {
unidirectional,
bidirectional,
undefined
} | The Link Directionality attribute type specifies whether the associated link managed object is uni- or bidirectional, or undefined | + +Table 179 + +| Name | Type | Description | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| linkPointer | RelatedObjectInstance | The Link Pointer attribute points to a link from a link end for connection-oriented network; or points to a FPP link from a flow point pool for connectionless network. | +| linkPointerList | ObjectList | This attribute points to the links terminated by the subnetwork or the link terminated by an access group for connection-oriented networks; or the FPP links terminated by the flow domain or the FPP link terminated by an access group for connectionless networks. | +| listOfCharacteristicInfo | ListOfCharacteristicInformation ::= SET OF CharacteristicInformation | This attribute lists the characteristic information types that can be cross-connected by a Fabric. | +| listOfSags | ListOfSags ::= SET OF SagId
SagId ::= NameType | | +| listOfSaps | ListOfSaps ::= SET OF Sap
Sap ::= String | | +| locationAddress | LocationAddress ::= SEQUENCE {
premisesName    PremisesName,
premisesAddress PremisesAddress,
...
}
PremisesName ::= String(SIZE(0..64))
PremisesAddress ::= SEQUENCE {
civicAddress    String(SIZE(0..64)),
city            String(SIZE(0..64)),
state           String(SIZE(0..64)),
zip             String(SIZE(0..64)),
...
} | | +| locationName | LocationName ::= String | The Location Name attribute type identifies a location. | + +Table 179 + +| Name | Type | Description | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| lockedInCondition |
LockedInCondition ::= SEQUENCE {     settingWindowTime    INTEGER,     -- number of seconds     releasingWindowTime  INTEGER,     -- number of seconds     hitsCount            INTEGER }
| This read-write attribute specifies the criteria of the locked-in condition. The criteria includes the automatic protection switching (APS) rate and the associated setting and releasing time windows. If the number of APS of a Protection Unit reaches the value specified in the hitsCount field within a moving time window of specified length, the Protection Unit will enter the locked-in condition. Each switch to protection and its subsequent release is considered as one hit. The length of the time window for entering the locked-in condition is specified in the settingWindowTime field. Once a Protection Unit is in the locked-in condition, future request of APS will be denied until the locked-in condition is released. The release criterion is no APS request within another moving time window. The length of this time window is specified in the releasingWindowTime field. | +| logicalEndDirectionality |
PointDirectionality ::= ENUMERATED {     sink,     source,     bidirectional }
| The Logical End Directionality attribute type specifies whether the associated link end managed object is sink, source, or bidirectional. | +| managedElementType |
ManagedElementType ::= SET OF CHOICE {     meTypeString    String,     meTypeOID       OBJECT IDENTIFIER }
| This attribute holds a set of either textual strings or values from a predefined set (Object Identifiers) that describe the generic type of the Network Element modelled by the ManagedElementR2 instance. Multiple managed element type values may be used to describe hybrid equipment. | +| maxFPPAssignbleCapacity | Bandwidth | This attribute indicates the maximum amount of bandwidth assignable to the flow point pool link, in both the ingress and egress directions. | +| maximumLinkConnectionCount | Count | This attribute indicates the maximum number of link connections associated with a link when flexible bandwidth allocation is supported. | +| maximumNetworkCTPCount | Count | This attribute indicates the maximum number of Network CTPs associated with a Link End. | + +Table 179 + +| Name | Type | Description | +|--------------------------|------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| modelCode | ModelCode ::= String | This attribute stores the product model code of the Network Element. The product model code is the manufacturer's model identification information. It is vendor-provided information that the vendor uses to distinguish the network element among a family of products. This attribute is useful for OSSs performing equipment discovery and inventory processes. | +| modelType | ModelType ::= String | | +| nameBinding | NameBinding | | +| neAliases | NeAliases ::= SET OF String | This attribute is used to hold aliases given by the EMS to a certain Managed Element instance. Having such aliases available via the EMS/NMS interface is useful for relating Network Element names entered at the EMS, via the Graphical User Interface or otherwise, to those found on the NMS user interface. More importantly, these aliases may appear in alarms sent by certain EMS software outside the interface. Thus, it would be crucial for the NMS to recognize such aliases in order to perform alarm correlation or other fault and performance functions. | +| neAssignmentPointer | NeAssignmentPointer ::= CHOICE {
notAvailable NULL,
relatedObject DistinguishedName,
string String
} | The NE Assignment Pointer attribute points from the lowest level Network TP in the partitioning hierarchy to a NE TP which represents the functionality which supports the Network TP. The sub-partition pointer for a NWCTP which utilizes the NE assignment pointer will be NULL. | +| networkCTPsInLinkEndList | TPList | This attribute lists the NetworkCTPs that are represented by a Link End. | +| networkLevelPointer | ObjectInstance | The network level pointer identifies a network level object. The value of the network level pointer shall only be modified by the managing system. | +| networkTPPointer | RelatedObjectInstance | The Network TP Pointer attribute points to a network termination point. | + +Table 179 + +| Name | Type | Description | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| normalControlState | ControlState | This attribute indicates the normal state of the control point. | +| numberOfCircuits | NumberOfCircuits ::= INTEGER | The number of circuits in a circuit subgroup. | +| numberOfPorts | Count | This attribute indicates the total number of ports supported by the circuit pack. | +| objectClass | | | +| objectList | ObjectList | The Object List attribute type describes a set of object instances. | +| operationalState | OperationalState ::= ENUMERATED {
enabled,
disabled
} | This attribute is to indicate the operability of the managed entity, which has two possible values: disabled and enabled. See [ITU-T X.731] for details. | +| outputFPList | ObjectList | This attribute identifies the list of output flow (termination) points of a flow domain fragment instance. | +| packages | Packages | | +| perceivedSeverityList | PerceivedSeverityList ::= SET OF PerceivedSeverity
PerceivedSeverity ::= ENUMERATED {
indeterminate(0),
-- used when it is not possible to assign
-- the following values:
critical(1),
major(2),
minor(3),
warning(4),
cleared(5)
} | The Perceived Severity List attribute type describes criteria for inclusion in a current alarm summary report. It consists of a set of possible Perceived Severities. In order to be included in a current alarm summary report, an object must have an outstanding alarm (or potential alarm) that has a Perceived Severity that matches one of the elements in the Perceived Severity List.

If the Perceived Severity List has null value, the Perceived Severity of the objects in the object list is not used as a criterion for inclusion in the current alarm summary report. | +| pointDirectionality | PointDirectionality | This attribute indicates the directionality of a networkTP or Connectionless Point managed object instance. For a Connectionless Point, only the "source" or "sink" can be used as the attribute value. | + +Table 179 + +| Name | Type | Description | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| portAssociations |
 PortAssociations ::= SET OF PortAssociation PortAssociation ::= SEQUENCE {     portId          NameType,     portTrail       PointerOrNull     -- the choice of NULL means unassigned } 
| This attribute is a sequence of pairs that relate a port on the multiport circuit pack with the associated entity. | +| portSignalRateAndMappingList |
 PortSignalRateAndMappingList ::= SET OF SEQUENCE {     portId          NameType,     signalRate      SignalRate,     mappingList     MappingList OPTIONAL } MappingList ::= SEQUENCE OF PayloadLevel PayloadLevel ::= CharacteristicInformation 
| This attribute identifies the signal rate associated with a circuit pack port (e.g., port = 0, rate = stm1) and its payload mapping (e.g., au3 or au4). The signal rate and payload mapping is provisionable. For example, a port with signal rate stm4 may have a payload mapping of au4-4. Another possible mapping of this rate is a sequence of four individual au4 (i.e., au4, au4, au4, au4) or a sequence of mixed au3 and au4 (e.g., au3, au3, au3, au4, au4, au3, au3, au3). | +| potentialCapacity | Capacity | This attribute indicates the number of link connections or the amount of bandwidth that has not yet been assigned to a Link but that could be assigned to the Link from the server trail. | +| potentialLinkCapacity | Capacity | This attribute indicates the number of link connections or the amount of bandwidth that has not yet been assigned to a Link but that could be assigned to the Link from the server trail. | +| potentialLinkEndCapacity | PointCapacity | This attribute indicates the number of Network CTP or the amount of bandwidth that has not yet been assigned to a Link End but that could be assigned to the Link End from the server trail termination point. | +| priority | INTEGER |

This attribute specifies the priority of the service (e.g., traffic) carried on the resource associated with the protected protectionUnit instance. Valid values for this attribute are integers, where the value 1 indicates the highest priority, and a larger value indicates a lower priority.

For a protecting protectionUnit, the value of this attribute indicates the priority of choice of the protecting protectionUnit relative to other available protecting protectionUnit(s) within the same protectionGroup. The lower the value, the more preferred the protectionUnit is relative to other protectionUnits.

| + +Table 179 + +| Name | Type | Description | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| probableCauseList | ProbableCauseList ::= SET OF ProbableCause |

The Probable Cause List attribute type describes criteria for inclusion in a current alarm summary report, consisting of a set of possible Probable Causes. In order to be included in a current alarm summary report, an object must have an outstanding alarm (or potential alarm) that has a Probable Cause that matches one of the elements in the Probable Cause List.

If the Probable Cause List has a null value, the Probable Cause of the objects in the object list is not used as a criterion for inclusion in the current alarm summary report.

| +| procedure | Procedure ::= CHOICE {
name    String,
number  INTEGER
} | | +| protected | Boolean | This attribute identifies whether the associated managed object is protected or not. The value TRUE implies it is protected. | +| protecting | Boolean | This attribute specifies the type of the protectionUnit. A value of TRUE indicates that the protectionUnit is a protecting (i.e., backup or standby) unit. A value of FALSE indicates that the protectionUnit is a protected (i.e., a regular, working, or preferred) unit. | +| protectionGroupType | ProtectionGroupType ::= ENUMERATED {
plus, -- 1+1 (1 plus 1) or hot-standby
colon -- M:N (M for N)
} | This attribute specifies whether the protection scheme used is 1 + 1 (plus) or M:N (colon). M:N includes the cases where M = 1 and/or N = 1. | +| protectionStatusR1 | ProtectionStatusR1 ::= SET OF CHOICE {
noRequest    NULL,
doNotRevert  NULL,
manualSwitch ManualSwitch,
autoSwitch   AutoSwitch,
forcedSwitch ForcedSwitch,
lockout      Lockout,
releaseFailed NULL,
resourceFailed NULL,
lockedIn    NULL
} | | + +Table 179 + +| Name | Type | Description | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
 ManualSwitch ::= SEQUENCE {     switchStatus    SwitchStatus,     relatedUnit     FromAndToProtectionUnit } AutoSwitch ::= SEQUENCE {     switchStatus    SwitchStatus,     relatedUnit     FromAndToProtectionUnit,     autoSwitchReason    AutoSwitchReason } ForcedSwitch ::= SEQUENCE {     switchStatus    SwitchStatus,     relatedUnit     FromAndToProtectionUnit } Lockout ::= CHOICE {     switchStatus    SwitchStatus,     releaseFailed   NULL } SwitchStatus ::= ENUMERATED {     pending,     completed,     operateFailed } FromAndToProtectionUnit ::= CHOICE {     fromProtectionUnitNumber    RDNSequence,     toProtectionUnitNumber      RDNSequence } AutoSwitchReason ::= ENUMERATED {     waitToRestore,     resourceDegrade,     resourceFailed } 
| | +| providerRequestNumber |
 RequestNumber ::= INTEGER 
|

This attribute is a unique identifier provided by the SP to identify the request. The providerRequestNumber attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the current service request and service modify request object class.

| +| provisionedLinkCapacity |
 Capacity 
|

This attribute indicates the number of link connections assigned to a Link or the amount of bandwidth assigned to a Link.

| + +Table 179 + +| Name | Type | Description | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| provisionedLinkConnectionCount | Count | This attribute indicates the number of link connections assigned to that link when flexible bandwidth allocation is supported. | +| provisionedLinkEndCapacity | PointCapacity | This attribute indicates the number of network CTPs assigned to a LinkEnd or the amount of bandwidth assigned to a LinkEnd. | +| provisionedNetworkCTPCount | Count | This attribute indicates the number of Network CTPs associated with a Link End that has been assigned. | +| qualityOfConnectivityService | ObjectInstance | This attribute indicates the quality of service for Connectivity and its subclasses, and requires further definition. | +| ranges |
 Ranges ::= SET OF CHOICE {     integerRange    AttributeChoiceInteger,     realRange       AttributeChoiceReal } AttributeChoiceInteger ::= SEQUENCE {     attributeName     String,     minimumValue      INTEGER,     maximumValue      INTEGER,     granularity       INTEGER } AttributeChoiceReal ::= SEQUENCE {     attributeName     String,     minimumValue      REAL,     maximumValue      REAL } 
| This attribute stores the ranges for attributes. Ranges may be defined for attributes of type INTEGER or type REAL. The 'attributeName' field specifies the name of the attribute for which a range is being defined. The range is then defined using the 'minimum', 'maximum', and 'granularity' fields. | +| redline | Boolean | This attribute identifies whether the associated managed object is red lined, e.g., identified as being part of a sensitive circuit. | +| relatedRoutingProfile | ObjectInstance | | +| reliableResourcePointerR1 |
 ResourcePointer ::= CHOICE{     null            NULL,     objectInstances SET OF ObjectInstance } 
| The value of the reliableResourcePointerR1 attribute points to the reliable resource(s) (e.g., the functional objects) that is/are associated with the Protection Unit instance. | + +Table 179 + +| Name | Type | Description | +|---------------------------------------------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| replaceable | Replaceable | The Replaceable attribute type indicates whether the associated managed object is replaceable or non-replaceable. | +| requestReceptionTime | Time | The year, month, day, hour, minute and seconds fields are compared in order to determine whether the specified value is greater or less than the value of the attribute. The values for the year, month, day, hour, minute and seconds are determined from their character string representation. The year value is first compared. If equal, the month value is compared and soon until the compared fields are not equal. | +| requestedInitialService-AdministrativeState | RequestedInitialService-AdministrativeState ::= AdministrativeState | This attribute represents Service Administrative State, Link Connection Service Administrative State. | +| requestSequenceNumber | RequestNumber | The requestSequenceNumber attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service request history record object class. | +| revertive | Boolean | This attribute indicates whether the protection scheme is revertive or not. If the value of this attribute is TRUE, the traffic is returned to the protected protectionUnit instance that initiated the switch after the fault clears and the waitToRestoreTime interval (if any) has expired. If the value of this attribute is FALSE, then after the fault has cleared, traffic does not revert to the protectionUnit that initiated the switch. | +| sadId | SadId ::= NameType | The sadID attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service access domain object class. | +| sagId | SagId | The sagID attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service access group object class. | +| sagLocation | SagLocation ::= LocationAddress | | +| schedulerName | ObjectInstance | See [ITU-T X.734] for details. | + +Table 179 + +| Name | Type | Description | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serialNumber | SerialNumber ::= String | The serial number attribute type identifies the serial number of the physical resource. | +| serverFTPPointer | ObjectList | This attribute defines the FTP which may serve a FP in another layer. Usually a FTP or FTPs in a higher order layer will serve a FP or FPs in a lower order layer. | +| serverTTPPointer | ObjectList | This attribute defines the TTP which may serve a CTP and/or link End in another layer. Usually a TTP or TTPs in a higher order layer will serve a CTP or CTPs in a lower order layer. | +| serverTrail | RelatedObjectInstance | This attribute points to a trail (including a connectionless trail) in the server layer that supports the link (include FPPlink) in a client layer. | +| serverTrailList | ObjectList | The value of this attribute identifies the trail objects (in most cases one) in a lower order network layer which may be used in parallel to serve a connection object. | +| serviceAffected | Boolean | This attribute indicates whether the alarm condition for monitored external device is service affecting or not. | +| serviceAvailabilityDate | Time | Date the service is due to be provisioned and placed in the requested Service Administrative State. | +| serviceCustomerContact | Contact ::= CHOICE {
person           PersonReach,
contactObject   ObjectInstance
-- the ObjectInstance points to an instance
-- of a X.790 Contact object.
} | The Customer contact person who may be called by the SP, who is knowledgeable and may be called for problems or questions concerning the service that has been ordered. | +| serviceDescription | ServiceDescription ::= String(SIZE(0..256)) | The name of a profile of service characteristics (associated with the service type) defined and supported by the SP. Examples of the service characteristics that may be included in the profile are directionality, channelization, signalling options, protection, quality of service objectives, application, etc. Service values of this attribute are not subject to standardization and are defined by the contract. | + +Table 179 + +| Name | Type | Description | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| serviceID | ServiceId ::= NameType | The Service ID is an attribute type whose distinguished value can be used as an RDN when naming an instance of the Management Operations Schedule object class. | +| serviceInstance | ObjectInstance | This attribute represents Circuit Number, Link Connection Identifier. | +| serviceProviderContact | Contact | The provider contact information for use by the SC in resolving questions or problems with the service. | +| serviceRequestState | ServiceRequestState ::= ENUMERATED {
pre-processing,
open-active,
pending,
closed
} |

This parameter indicates that the request is in progress. Valid values are:

Pre-processing – Indicates that the service request is currently being checked for validity of request parameters.

Open/active – Indicates that the service request is open and is being actively processed.

Pending – Indicates that the service request is deactivated for reasons such as waiting for additional information, completion of other supporting tasks. Activation from this pending state is required before processing can be continued.

Closed – Indicates that the service request is closed either as a result of successful completion or error or because the request was cancelled.

| +| serviceTerminationDate | ServiceTerminationDate ::= CHOICE {
time                    Time,
continuous            NULL
}
-- continuous means that no termination date
-- has been specified, this is the default value
-- for ServiceTerminationDate | The year, month, day, hour, minute and seconds fields are compared in order to determine whether the specified value is greater or less than the value of the attribute. The values for the year, month, day, hour, minute and seconds are determined from their character string representation. The year value is first compared. If equal, the month value is compared and soon until the compared fields are not equal | +| serviceType | ServiceType ::=CHOICE{
serviceTypeNumber    INTEGER,
string                    String,
oid                        OBJECT IDENTIFIER,
...
} | The service Type attribute identifies the distinguishing characteristics of a Service. | + +Table 179 + +| Name | Type | Description | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| signalId |
SignalId := CHOICE {     simple      CharacteristicInformation,     bundle      Bundle,     complex     SEQUENCE OF Bundle } Bundle := SEQUENCE {     characteristicInfoType         CharacteristicInformation,     bundlingFactor      INTEGER }
|

This attribute defines the characteristic information of the layer (in the G.805 sense) to which the entity under consideration belongs. It is used to determine whether subnetwork connection/connectivity is possible. The signal Id may be a simple rate and format, a bundle of entities with the same characteristic information which forms an aggregate signal, or a complex type containing groupings of different bundles. The complex type may be applicable to certain multimedia applications involving multiple parallel connections between endpoint locations.

| +| signalType |
SignalType := CHOICE {     simple      CharacteristicInformation,     bundle      Bundle,     complex     SEQUENCE OF Bundle }
|

This attribute uniquely identifies the signal type of a cross-connection, TP pool or GTP. The signal type can either be simple, bundle, or complex. If the signal type is simple, it consists of a single type of characteristic information. If the signal type is bundle, it is made up of a number of signal types all of the same characteristic information. If the signal type is complex, it consists of a sequence of bundle signal type. The order in the complex signal type represents the actual composition of the signal.

| +| signallingCapabilities |
SignallingCapabilities := ENUMERATED {     isup,     isup92,     itu-tNo5,     r2,     itu-tNo6,     tup     -- this is an extensible type and additional     -- enumerations may be added in the future }
|

The attribute type specifies the signalling types supported by the circuit subgroup.

| +| subNetworkConnectionPointer |
SubNetworkConnectionPointerList :=     SEQUENCE OF RelatedObjectInstance
|

The Subnetwork Connection Pointer attribute points to the ordered list of subnetwork Connection(s) which have a relationship with the network termination point. When no subnetwork connection is present, this pointer points to a subnetwork or is NULL. This list has a single entry for point-to-point applications, and may have multiple entries for point-to-multipoint applications.

| + +Table 179 + +| Name | Type | Description | +|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| subordinateCircuitPackSoftwareLoad | SubordinateCircuitPackSoftwareLoad ::= CHOICE {
    notApplicable                    NULL,
    softwareInstances                SEQUENCE OF
    ObjectInstance,
    softwareIdentifiers                SEQUENCE OF String
}
|

This attribute indicates the software, if any, which is currently designated as the one to be loaded to the containing circuit pack whenever automatic reload of software is needed. The values of this attribute may be one of the following: sequence of printable string, sequence of object instance or NULL. The NULL choice is used when the contained circuit pack is not software loadable, or no software load has been designated. The choice of sequence of ObjectInstance identifies an ordered set of software instances. This ordered set can be used to specify the order in which the software is to be downloaded. It is recommended to note in the ICS if the ordering is significant. When the choice of PrintableString is used, the semantics is a local matter.

| +| sub-partitionPointer | RelatedObjectInstance |

The Sub-partition Pointer is a pointer to a Network CTP which is in a lower level partition. Where the lowest level of NWCTP points to a NE CTP via the NE Assignment Pointer, the value of the Sub-partition Pointer is null.

| +| superPartitionPointer | RelatedObjectInstance |

The Super Partition Pointer is a pointer to a Network CTP which is in a higher level partition. It will only be present for those Network CTPs in the lower partition which has a direct correspondence to the Network CTPs at the higher level. It can be null.

| +| supportableClientList | SupportableClientList ::= SET OF ObjectClass |

The value of this attribute is the list of object classes representing the clients that the particular managed object is capable of supporting. This may be a subset of the client layers identified in [b-ITU-T G.803] by the particular server layer managed object.

| +| supportedByObjectList | ObjectList |

The Supported By Object List is an attribute type whose value identifies a set of object instances which are capable of directly affecting a given managed object. The object instances include both physical and logical objects. This attribute does not force internal details to be specified, but only the necessary level of detail required for management. If the object instances supporting the managed object are unknown to that object, then this attribute is an empty set.

| + +Table 179 + +| Name | Type | Description | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedServiceNameList | ObjectList | This attribute specifies the services supported by a given managed object. | +| systemTimingSource |
 SystemTimingSource ::= SEQUENCE {     primaryTimingSource    SystemTiming,     secondaryTimingSource SystemTiming OPTIONAL } SystemTiming ::= SEQUENCE {     sourceType SourceType,     sourceID   ObjectInstance OPTIONAL     -- not needed for internal source } SourceType ::= ENUMERATED {     internalTimingSource,     remoteTimingSource,     slavedTimingTerminationSignal } 
| The System Timing Source attribute is used to specify the primary and secondary managed element timing source for synchronization. | +| systemTitle |
 SystemTitle ::= CHOICE {     distinguishedName    DistinguishedName,     oid                  OBJECT IDENTIFIER,     nothing              NULL } 
| This attribute may be used in naming instances of System managed object class. | +| telephoneNumberList | TelephoneNumberList | A list of contact telephone numbers. | +| toTermination | Pointer ::= ObjectInstance | This attribute identifies a CTP (source or bidirectional), a TTP (sink or bidirectional) or a GTP composed of members of one of these categories. | +| topologicalEndDirectionality |
 TopologicalEndDirectionality ::= ENUMERATED {     undefined,     sink,     source,     bidirectional } 
| The Topological End Directionality attribute type specifies whether the associated link end managed object is sink, source, bidirectional, or undefined. | +| totalFPPLinkCapacity | Bandwidth | This attribute identifies the total bandwidth that is available to the FPP link. | + +Table 179 + +| Name | Type | Description | +|-----------------------------|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| totalFPPCapacity | BandWidth | This attribute indicates the total amount of bandwidth supported on the flow point pool, including both assigned and unassigned bandwidth, based on the amount of bandwidth provided by the underlying server layer link. | +| totalLinkCapacity | Capacity | This attribute indicates the total capacity of a Link which may be the number of Link connections contained in a Link or the total bandwidth available to the Link. | +| totalLinkEndCapacity | PointCapacity | This attribute indicates the total capacity of a Link End which is either the total number of NetworkCTPs associated with a Link End or the total bandwidth of the Link End. | +| totalTpCount | Count | This attribute indicates the total number of termination points associated with a tpPool. | +| tpsInGtpList | TpsInGtpList ::= SET OF ObjectInstance | This attribute lists the termination points that are represented by a GTP. | +| tpsInTpPoolList | ListOfTPs ::= SET OF ObjectInstance | This attribute lists the termination points that are represented by a TP Pool. | +| trafficDescriptor | TrafficDescriptor ::= ObjectInstance | This attribute contains the traffic descriptor of a trail (connection-oriented or connectionless). It is to be used with flexible bandwidth allocation. | +| transmissionCharacteristics | TransmissionCharacteristics ::= BIT STRING {
satellite(0),
dCME(1),
echoControl(2)
} | This attribute type specifies the different transmission characteristics such as satellite, echo control supported or not supported by the circuit subgroup. The bit positions are set to indicate if a particular characteristic is supported. | + +Table 179 + +| Name | Type | Description | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ttpPortID | PortIDType ::= SEQUENCE {
managedElement String,
bay String OPTIONAL,
shelf String OPTIONAL,
drawer String OPTIONAL,
slot String OPTIONAL,
port String
} | This attribute stores references to the Physical Port that supports this generic transport TTP. | +| typeText | TypeText ::= String | This attribute gives a textual description of the type of the resource. | +| unreliableResourcePointerR1 | ResourcePointer | The value of the unreliableResourcePointerR1 attribute points to the unreliable resource(s) (e.g., circuit pack) that is/are associated with the Protection Unit instance. | +| upstreamConnectivityPointer | ConnectivityPointer | The matching for equality is applicable for all the choices of the syntax. | +| upstreamFPPointer | UpstreamFPPointer ::= CHOICE {
none NULL,
single ObjectInstance,
broadcast SET OF ObjectInstance
} | The upstream FP pointer attribute points to the connectionless point managed object, within the same managed element, that sends information (traffic) to this connectionless point instance at the same layer, or is null. | +| usageCost | UsageCost ::= INTEGER(0..255) | This attribute contains the costs for a transport entity. It is to be used as selection/routing criteria. | +| usageState | UsageState ::= ENUMERATED {
idle,
active,
busy
} | See [ITU-T X.731] for details. | +| userLabel | UserLabel | The User Label attribute type assigns a user friendly name to the associated object. | + +Table 179 + +| Name | Type | Description | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| validControlType | ValidControlType ::= ENUMERATED {
momentaryOnly,
continuousOnly,
both
} | This attribute indicates the valid type of control signal for this control point. | +| vendorName | VendorName ::= String | The Vendor Name attribute type identifies the vendor of the associated managed object. | +| version | Version ::= String | The Version attribute type identifies the version of the associated managed object. | +| waitToRestoreTime | INTEGER | This attribute specifies the amount of time, in seconds, to wait after a fault clears before restoring traffic to the protected protectionUnit that initiated the switching. | +| weekMask | WeekMask ::= SET OF SEQUENCE {
daysOfWeek    DaysOfWeek,
intervalsOfDay  IntervalsOfDay
}
DaysOfWeek ::= BIT STRING {
sunday(0),
monday(1),
tuesday(2),
wednesday(3),
thursday(4),
friday(5),
saturday(6)
} (SIZE(7)) | See [ITU-T X.734] for details. | +| zEnd | ObjectInstance | This attribute is a pointer to a subnetwork, a link end, or access group in the same network layer domain. | +| zEndFTPLIST | ObjectList | The value of this attribute identifies one or more Flow Termination Point instances, which represents the sink end of a connectionless Trail. This attribute cannot be null. | + +Table 179 + +| Name | Type | Description | +|---------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ObjectList | The value of this attribute identifies one or more network termination points of an instance of a subclass of the Connectivity object class. | +| zEndofFPPLink | ObjectInstance | This attribute is a pointer to a flow domain, a flow point pool or an access group in the same network layer domain. This attribute identifies the link end at the other extremity. | +| z-TPInstance | RelatedObjectInstance | The Z-Termination Point Instance attribute type identifies one of the two termination points of an instance of the connectivity object class. | + +## 8.2 Notifications + +Table 180 + +| Name | Type | Description | +|-----------------------------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attributeValueChange | AttributeValueChangeInfo | This notification type is used to report changes to the attribute such as addition or deletion of members to one or more set valued attributes, replacement of the value of one or more attributes and setting attribute values to their defaults. | +| communicationsAlarm | AlarmInfo | This notification type is used to report when the object detects a communications error. | +| currentAlarmSummaryReport | AlarmSummaryData | | +| environmentalAlarm | AlarmInfo | This notification type is used to report a problem in the environment. | +| equipmentAlarm | AlarmInfo | This notification type is used to report a failure in the equipment. | +| objectCreation | ObjectInfo | This notification type is used to report the creation of a managed object to another open system. | +| objectDeletion | ObjectInfo | This notification type is used to report the deletion of a managed object to another open system. | +| processingErrorAlarm | AlarmInfo | This notification type is used to report processing failure in a managed object. | +| protectionAlarm | ProtectionAlarmInfo | | +| protectionSwitchReportingR1 | ProtectionSwitchReportingInfo | The protectionSwitchReporting notification is emitted from the protectionGroup object to report any protection switch events. | +| qualityofServiceAlarm | AlarmInfo | This notification type is used to report a failure in the quality of service of the managed object. | +| stateChange | StateChangeInfo | This notification type is used to report the change in the value of one or more state attributes of a managed object that result through either internal operation of the managed object or via management operation. | + +## Appendix I + +(This appendix does not form an integral part of this Recommendation) + +The larger part of the IOCs defined in this Recommendation is based on existing protocol-specific managed objects as shown in Table I.1. + +**Table I.1 – IOC mapping with protocol-specific managed object classes** + +| M.3160 | M.3100 | M.3108.1 | Q.821 | X.790 | +|------------------------------------------------|------------------------------------------|----------|----------------------------|---------| +| Abstract Link | AbstractLink | | | | +| Abstract Link End | AbstractLinkEndR1 | | | | +| Access Group | AccessGroup | | | | +| Account | | | | Account | +| Alarm Severity Assignment Profile | AlarmSeverityAssignmentProfile | | | | +| Alarm Reporting Control (Arc) Interval Profile | ArcIntervalProfile | | | | +| Attribute Ranges | AttributeRanges | | | | +| Circuit End Point Subgroup | CircuitEndPointSubgroup | | | | +| Circuit Pack | CircuitPackR1 | | | | +| Connection | ConnectionR1 | | | | +| Connection Termination Point Bidirectional | ConnectionTermination-PointBidirectional | | | | +| Connection Termination Point Sink | ConnectionTerminationPointSink | | | | +| Connection Termination Point Source | ConnectionTerminationPointSource | | | | +| Control Point | ControlPoint | | | | +| Cross Connection | CrossConnectionR1 | | | | +| Contact | | | | Contact | +| Current Alarm Summary Control | | | CurrentAlarmSummaryControl | | +| Equipment | EquipmentR2 | | | | +| Equipment Holder | EquipmentHolder | | | | +| External Point | ExternalPoint | | | | +| Fabric | FabricR4 | | | | +| Generic Transport TTP | GenericTransportTTPR1 | | | | +| Group Termination Point (gtp) | gtpR1 | | | | +| Layer Network Domain | LayerNetworkDomainR1 | | | | +| Link Connection | LinkConnection | | | | +| Logical Link | LogicalLink | | | | +| Logical Link End | LogicalLinkEndR1 | | | | + +**Table I.1 – IOC mapping with protocol-specific managed object classes** + +| M.3160 | M.3100 | M.3108.1 | Q.821 | X.790 | +|-----------------------------------|---------------------------|------------------------------|--------------|--------------| +| Managed Element | ManagedElementR2 | | | | +| Managed Element Complex | ManagedElementComplex | | | | +| Multipoint Cross Connection | mpCrossConnectionR1 | | | | +| Named Cross Connection | NamedCrossConnection | | | | +| Named Multipoint Cross Connection | NamedMpCrossConnection | | | | +| Network CTP Bidirectional | NetworkCTPBidirectional | | | | +| Network CTP Sink | NetworkCTPSink | | | | +| Network CTP Source | NetworkCTPSource | | | | +| Network | NetworkR1 | | | | +| Network Termination Point | NetworkTerminationPoint | | | | +| Network TTP Bidirectional | NetworkTTPBidirectionalR1 | | | | +| Network TTP Sink | NetworkTTPSinkR1 | | | | +| Network TTP Source | NetworkTTPSource | | | | +| Pipe | PipeR2 | | | | +| Protection Group | ProtectionGroupR2 | | | | +| Protection Unit | ProtectionUnitR1 | | | | +| Scan Point | ScanPoint | | | | +| Service | | | | Service | +| Service Access Domain | | ServiceAccessDomainR1 | | | +| Service Access Group | | ServiceAccessGroup | | | +| Service Access Equipment View | | ServiceAccessEquipment View | | | +| Service Modify Request | | ServiceModifyRequest | | | +| Service Request History Record | | ServiceRequestHistory Record | | | +| Software | SoftwareR1 | | | | +| Sub Network | SubNetwork | | | | +| Sub Network Connection | SubNetworkConnection | | | | +| Termination Point | TerminationPoint | | | | +| Termination Point Pool (tpPool) | TpPool | | | | +| Topological Link | TopologicalLink | | | | +| Topological Link End | TopologicalLinkEndR1 | | | | +| Trail | TrailR2 | | | | + +**Table I.1 – IOC mapping with protocol-specific managed object classes** + +| M.3160 | M.3100 | M.3108.1 | Q.821 | X.790 | +|---------------------------------------|------------------------------------|------------------|--------------|--------------| +| Trail Termination Point Bidirectional | TrailTerminationPointBidirectional | | | | +| Trail Termination Point Sink | TrailTerminationPointSink | | | | +| Trail Termination Point Source | TrailTerminationPointSource | | | | +| Transport Service | | TransportService | | | + +## Bibliography + +- [b-ITU-T G.774.3] Recommendation ITU-T G.774.3 (2001), *Synchronous digital hierarchy (SDH) – Management of multiplex-section protection for the network element view.* +- [b-ITU-T G.803] Recommendation ITU-T G.803 (2000), *Architecture of transport networks based on the synchronous digital hierarchy.* +- [b-ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks.* +- [b-ITU-T G.809] Recommendation ITU-T G.809 (2003), *Functional architecture of connectionless layer networks.* +- [b-ITU-T G.8010] Recommendation ITU-T G.8010/Y.1306 (2004), *Architecture of Ethernet layer networks.* +- [b-ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network.* +- [b-ITU-T M.3100] Recommendation ITU-T M.3100 (2005), *Generic network information model.* +- [b-ITU-T M.3108.1] Recommendation ITU-T M.3108.1 (1999), *TMN management services for dedicated and reconfigurable circuits network: Information model for management of leased circuit and reconfigurable services.* +- [b-ITU-T Q.821] Recommendation ITU-T Q.821 (2000), *Stage 2 and Stage 3 description for the Q3 interface – Alarm surveillance.* +- [b-ITU-T X.721] Recommendation ITU-T X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- [b-ITU-T X.790] Recommendation ITU-T X.790 (1995), *Trouble management function for ITU-T applications.* +- [b-Fowler] Fowler Martin, *Analysis Patterns – Reusable Object Models* ISBN 0-201-89542-0, + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf4fcd45778c9aa015560b803e58b505668e484 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b94b7e2f510aab0bda5f180706df0438ed8a0a9efa4eb6e486a8fa5ded1ba8 +size 60559 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a61b05b8c360726257efb6ba9743b718cb6805f --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e7db875e7f6f4c2e33852ed2d49bc7ccf4297ed6ca8e76e1bc8d7f4b49c6a39 +size 9348 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6421d802bc75d2753bf66dcdb4ce6bdd55101b8d --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:530a5a078b58eabb822910762ea54bee4ea70a22f64a73f72c210e095fb2a064 +size 63994 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eab6c72738e5af477b420cf22fbc9c42990afbf7 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afa95ae540203f5b66ef0e03051ff1b0463ff98cd196d94a74e7bd305bac9de1 +size 15025 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f2297017a63b9bea14800661e85c81370a1fb7f --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63f0601213b272656aae3891234365db5c8ea24b96c0ca62796539f01a5e26cb +size 14031 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96b61b1889429ad0fff48928f74d831c83d61ded --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d280a4c8f4b44e63edb068badfcaed44d11b98c6d081395a4060063b0f76f7d +size 17247 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63313c9d1c796d1bb95fc8516083ade1ebfa5478 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79c21820d8baa2e1fc7279b7708a4bc76a2688a78e983087069db3050fc6c62e +size 11244 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1557ecfa302daa877a787f9231f9f6b21edcf70 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d742ca3f918d6d4293ca794f78a6723c2a0fd8d4229cd493a7293f9fa65b991 +size 11853 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04189f6b86d5746140d3b661afbe1f4fe6a829b5 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f4cc969f1fe965ceae27d0352d663dfaa8b6de7e33aac7ab426267614329970 +size 9830 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8e1c3718c87f35d9b21300a129c818e30814125 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acea10cb844b638019d461004cecb58469565f0854b17320180001e92cd1699b +size 15366 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3abcd9467e6370175437194146fa01a86f626215 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a255a94a04c8193581eef8a42bb148f4c5d73557cab41aebd704292d33e2a1b +size 48362 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60f4c743310a6cb0ab5741465a4596c8b835be8c --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac6e30f697e323e52dc7a1631a01db324bf16affcb4a6cba3a1f744bcca72258 +size 12023 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff524418d11e12e82f430fb710f4ca35b667f466 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3830176c7cae6a5a615c87da9fb2a4192d3439ab17fa3ffc9cefa9b1b63ced8 +size 46944 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ab8e08b94c579348a9059c7c9d5fd24dbcad61 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:973c04c5c1c7712e4c3352f0bfc5f96fd4095fd25ba693f276538299e650e50c +size 101572 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a34c9bf04d32aaeb58cff6d6d5d859bebc3cdf8c --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3d5736cb79a610cb3418920aea4e1eb6aca1afcbb11fffca197305466cb6a13 +size 28645 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b884f6093edc61cd4d6e6f48f2badfd67e3ef5b8 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ef339fb5e7fe0ce7ab4f61ec41441c45326017c39243707520bacecdde3a17b +size 52528 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c9e34cf8188a1391f4c98ebb9814581eb39ecb8 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1da841098f9a69f5fb21f06abc604e6b84d0171b19fb9ea8423d79158f90cafb +size 12730 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a713c9d3a38a0b0ded423795a4e6fb9889f1cf7e --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ac2e2cf21c51a63df761924b63730e9562d1cb9210d5b37a96e62976d508279 +size 4125 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..503e729e9371e089d0d2821c6d750143d76abea1 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a65220522b1be14036b48500ae1fb0aa0942a193d297f505c53d8aaf23a401 +size 10389 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c1b03a5fb604e95e06318350eb65b8b2129ba6f --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf8a840aabdf29c2ad8b2c25419885133a99fc0302753d391b1833d46ab7c244 +size 17087 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48ec609c71c40a86fc74449b0a84445447fa37bf --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21e5e921b0a288fe134238b0ad976cd08ee50c71ab6e059cfb932b5273e363a6 +size 14443 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae7e8129cecbcbf73525b27fa13d8b95e9824ccf --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0824cda7be169ef223b68a5530f3b826d4814ee768daa6db9677335751d2a3c7 +size 28164 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca6842d3c337fc27c3576d0cd45308bdb0727101 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:995c645ec23b6b2be6913b867d8860995b53cee059782410251905fa26c84749 +size 38144 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..775dc59131da76c36aee06a89b56c9b9eeb22e4e --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:049f0b30653bb0788fdf97503a79ca1a9342051c325f02e895f6b80a5fa10b21 +size 14103 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca55458370631f3229f008002b01d5a06b528cd3 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5e42dd699601d69ea28cb265198d3ece2c1f8e82596963e2525190384419a68 +size 16784 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/M/T-REC-M.3164-202007-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06e18117d4823709a1b704acee40f5598b17f748 --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a4c054795a55264c64a75e9b4765235e1e89ccbbdfe8d7a4c30036efce93aa2 +size 11851 diff --git a/marked/M/T-REC-M.3164-202007-I_PDF-E/raw.md b/marked/M/T-REC-M.3164-202007-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c15177f6e7bd3cee22698c45c757f0bf8fdbb9ca --- /dev/null +++ b/marked/M/T-REC-M.3164-202007-I_PDF-E/raw.md @@ -0,0 +1,2263 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3164** + +(07/2020) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Generic information model for on-site telecommunication smart maintenance** + +Recommendation ITU-T M.3164 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3164 + +# Generic information model for on-site telecommunication smart maintenance + +## Summary + +Recommendation ITU-T M.3164 introduces the generic information model for on-site telecommunication smart maintenance. In this Recommendation, the definition and description of the generic information object classes, attributes and the relationships between object classes are provided. This Recommendation also provides examples of each information object class and a diagram of all the example instances. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.3164 | 2020-07-14 | 2 | 11.1002/1000/14319 | + +## Keywords + +Information model, telecommunication smart maintenance. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Information model for telecommunication smart maintenance..... | 2 | +| 6.1 Top-level object class relationship diagram ..... | 2 | +| 6.2 Resource management information model..... | 3 | +| 6.3 On-site patrol information model ..... | 3 | +| 6.4 On-site overhaul information model ..... | 9 | +| 6.5 On-site troubleshooting information model ..... | 11 | +| 6.6 Service activation information model ..... | 17 | +| 6.7 Maintenance knowledge base information model..... | 22 | +| 6.8 Maintenance work evaluation information model..... | 25 | +| 6.9 Smart maintenance assistant toolkit management information model ..... | 27 | +| Appendix I – Examples of instances for information object classes ..... | 35 | +| I.1 Overview of all the instances ..... | 35 | +| I.2 Examples related to on-site patrol information model ..... | 35 | +| I.3 Examples related to on-site overhaul information model..... | 37 | +| I.4 Examples related to on-site troubleshooting information model ..... | 38 | +| I.5 Examples related to service activation information model ..... | 39 | +| I.6 Examples related to maintenance knowledge base information model..... | 40 | +| I.7 Examples related to maintenance work evaluation information model ..... | 41 | +| I.8 Examples related to smart maintenance assistant toolkit management information model ..... | 41 | + + + +# Recommendation ITU-T M.3164 + +## Generic information model for on-site telecommunication smart maintenance + +# 1 Scope + +This Recommendation builds a generic information model for on-site telecommunication smart maintenance. It identifies object classes that are common to telecommunication smart maintenance systems, or that are of a generic type that can be used in telecommunication smart maintenance systems at a technology-independent level. The main content in this Recommendation includes the definition and description of generic information model object classes, attributes and the relationship between object classes. + +This Recommendation addresses generically the abstractions of those aspects related to telecommunication smart maintenance systems. + +The generic information model provided in this Recommendation follows the [ITU-T M.3020] interface specification methodology on the analysis phase, and is developed in a protocol-neutral manner, which can be mapped to multiple protocol-specific information models. + +This Recommendation applies to the design and development of telecommunication smart maintenance systems. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; user of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3020] Recommendation ITU-T M.3020 (2017), *Management interface specification methodology*. + +[ITU-T M.3040] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 information object class** [ITU-T M.3020]: Describes the information that can be passed/used in management interfaces and is modelled using the stereotype "Class" in the UML meta-model. + +**3.1.2 telecommunication smart maintenance** [ITU-T M.3040]: The maintenance carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system, which can provide strong human-computer interaction capabilities and online guidance to personnels, to achieve higher efficiency and precision of actions. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 attribute property:** Specification attribute qualification and value range. + +NOTE – Based on [ITU-T M.3020]. + +**3.2.2 class diagram:** A diagram that describes classes, interfaces, collaborations, and relationships between them to show the static structure of each class in the system. + +NOTE – Based on [ITU-T M.3020]. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------------| +| ID | Identifier | +| MAC | Media Access Control | +| RAM | Random Access Memory | +| ROM | Read Only Memory | +| SMAT | Smart Maintenance Assistant Toolkit | +| TSMS | Telecommunication Smart Maintenance System | +| UML | Unified Modeling Language | + +# 5 Conventions + +None. + +# 6 Information model for telecommunication smart maintenance + +## 6.1 Top-level object class relationship diagram + +![Relationship class diagram between the top-level object classes. The diagram shows ResourceInfo as a ProxyClass, which represents all resource entities. It is connected to eight InformationObjectClass boxes: OnsitePatrolInfo, OnsiteOverhaulInfo, OnsiteTroubleshootingInfo, ServiceActivationInfo, MaintenanceKnowledgeBaseInfo, MaintenanceWorkEvaluationInfo, SmartMaintenanceAssistToolkitInfo, and M.3164(20)_F01.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +The diagram illustrates the top-level object class relationship. At the top, a box labeled **<> ResourceInfo** is connected to a note box containing the text "It represents all resource entities." Below this, there are two rows of boxes. The first row contains four boxes: **<> OnsitePatrolInfo**, **<> OnsiteOverhaulInfo**, **<> OnsiteTroubleshootingInfo**, and **<> ServiceActivationInfo**. The second row contains three boxes: **<> MaintenanceKnowledgeBaseInfo**, **<> MaintenanceWorkEvaluationInfo**, and **<> SmartMaintenanceAssistToolkitInfo**. All boxes have a dashed line at the bottom. The text "M.3164(20)\_F01" is located in the bottom right corner. + +Relationship class diagram between the top-level object classes. The diagram shows ResourceInfo as a ProxyClass, which represents all resource entities. It is connected to eight InformationObjectClass boxes: OnsitePatrolInfo, OnsiteOverhaulInfo, OnsiteTroubleshootingInfo, ServiceActivationInfo, MaintenanceKnowledgeBaseInfo, MaintenanceWorkEvaluationInfo, SmartMaintenanceAssistToolkitInfo, and M.3164(20)\_F01. + +**Figure 1 – Relationship class diagram between the top-level object classes** + +As shown in Figure 1, the top level classes of the information model for the telecommunication smart maintenance system (TSMS) include ResourceInfo, OnsitePatrolInfo, OnsiteOverhaulInfo, OnsiteTroubleshootingInfo, ServiceActivationInfo, MaintenanceKnowledgeBaseInfo, MaintenanceWorkEvaluationInfo, SmartMaintenanceAssistToolkitInfo, and these top-level classes contain concrete information object classes. + +## 6.2 Resource management information model + +Referring to [ITU-T M.3020], this Recommendation defines the top-level class about resource management (ResourceInfo) as a proxy class "ProxyClass", which represents all resource entity classes "InformationObjectClass". The proxy class encapsulates the properties, methods (or notifications) that exist in the entity class it represents, and all its behavior appears in the entity class it represents. Since the proxy class is just a representation of other classes, this class cannot define its own behavior except for the classes that have been defined by the indicated "InformationObjectClass". So, this Recommendation defines properties and methods about resource proxy class. The information model related to the top-level class about resource management is shown in Figure 2, where the Note is a comment for the proxy class. + +![UML class diagram for ResourceInfo proxy class.](562f471e8153729557e6a4ee6343c32c_img.jpg) + +A UML class diagram showing a single class box labeled <> ResourceInfo. A note box with the text "It represents all resource entities." is connected to the class by a line. The diagram is labeled M.3164(20)\_F02 at the bottom right. + +UML class diagram for ResourceInfo proxy class. + +Figure 2 – Information model related to ResourceInfo + +The information model about network resources of a specific network refers to relevant existing standards. + +## 6.3 On-site patrol information model + +#### 6.3.1 Relationship class diagram between object classes + +The Relationship class diagram between object classes related to on-site patrol is shown in Figure 3. + +![UML class diagram showing relationships between OnsitePatrolInfo, OnsitePatrolTask, OnsitePatrolRecord, OnsitePatrolPoint, and ResourceInfo.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +A UML class diagram showing five classes and their relationships. OnsitePatrolInfo (InformationObjectClass) has a 1:n relationship with OnsitePatrolTask (InformationObjectClass) labeled <>. OnsitePatrolTask has a 1:n relationship with OnsitePatrolRecord (InformationObjectClass) labeled <>. OnsitePatrolTask has a 1:n relationship with OnsitePatrolPoint (InformationObjectClass) labeled +OnsitePatrolPoint. OnsitePatrolRecord has a 1:1 relationship with OnsitePatrolPoint labeled +OnsitePatrolPoint. ResourceInfo (ProxyClass) has a 1:n relationship with OnsitePatrolTask labeled +ResourceInfo. A note box with the text "It represents all resource entities." is connected to ResourceInfo. The diagram is labeled M.3164(20)\_F03 at the bottom right. + +UML class diagram showing relationships between OnsitePatrolInfo, OnsitePatrolTask, OnsitePatrolRecord, OnsitePatrolPoint, and ResourceInfo. + +Figure 3 – Relationship class diagram between object classes related to on-site patrol + +In Figure 3, the information object classes related to on-site patrol include OnsitePatrolTask, OnsitePatrolPoint, and OnsitePatrolRecord. The patrol activity is related to patrol multiple + +resources, and these resources are at different sites, so that OnsitePatrolTask and OnsitePatrolPoint and ResourceInfo are many-to-many and one-way association relationships. On-site maintenance personnel records information about and generates patrol records when performing patrol activity at each patrol point, so that OnsitePatrolTask and OnsitePatrolRecord are a one-to-many containment relationship, and OnsitePatrolRecord and OnsitePatrolPoint is a one-to-one and one-way association relationship. + +#### 6.3.2 Object class information model and attribute description + +#### 6.3.2.1 Information object class related to on-site patrol (OnsitePatrolInfo) + +##### 6.3.2.1.1 Definition + +The *OnsitePatrolInfo* management entity describes basic information related to the top-level class about on-site patrol. + +##### 6.3.2.1.2 Attributes + +Table 1 describes the attribute properties related to OnsitePatrolInfo: + +**Table 1** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| patrolInfoID | M | M | – | – | M | +| patrolTaskList | M | M | M | O | M | + +Table 2 shows the specific description of the attributes related to OnsitePatrolInfo: + +**Table 2** + +| Attribute name | Type | Explanation | +|----------------|--------------------|-----------------------------------------------| +| patrolInfoID | String | Unique identifier related to OnsitePatrolInfo | +| patrolTaskList | SEQUENCE OF String | List of on-site patrol activities | + +##### 6.3.2.1.3 Notifications + +Table 3 shows the specific description of notifications related to OnsitePatrolInfo: + +**Table 3** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.3.2.2 Information object class related to patrol activity (OnsitePatrolTask) + +The information model related to OnsitePatrolTask is shown in Figure 4. + +![UML Class diagram for OnsitePatrolTask. The class name is OnsitePatrolTask, and it inherits from InformationObjectClass. The attributes listed are: taskID, taskType, patrolExecutor, startTime, endTime, pointSequence, recordList, orderID, and resourceSet.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +classDiagram + class OnsitePatrolTask { + -taskID + -taskType + -patrolExecutor + -startTime + -endTime + -pointSequence + -recordList + -orderID + -resourceSet + } + OnsitePatrolTask <|-- InformationObjectClass + +``` + +UML Class diagram for OnsitePatrolTask. The class name is OnsitePatrolTask, and it inherits from InformationObjectClass. The attributes listed are: taskID, taskType, patrolExecutor, startTime, endTime, pointSequence, recordList, orderID, and resourceSet. + +M.3164(20)\_F04 + +**Figure 4 – Information model related to OnsitePatrolTask** + +##### 6.3.2.2.1 Definition + +This management entity describes relevant information related to patrol activity. The use made of individual attributes and notification is detailed below: + +- taskType: The patrol activities are divided into multiple types according to different situations, and the attribute indicates the type of the activity; +- taskStatus: Representing the state in which the patrol activity is located; +- pointSequence: It consists of the location where patrol objects are located, and represents the order of patrol in this activity; +- orderID: The order is the information related to maintenance tasks sent from TSMS, including maintenance task types, maintenance objects, serial numbers, etc. OrderID represents the serial number of the order about the patrol activity; +- resourceSet: Representing equipment related to patrol activity. + +An attribute value change notification shall be emitted when the value of the taskID, the taskType, the taskStatus, the patrolExecutor, the pointSequence, the recordList, the orderID or the resourceSet is changed. + +##### 6.3.2.2.2 Attributes + +Table 4 describes the attribute properties related to OnsitePatrolTask: + +**Table 4** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| taskID | M | M | – | – | M | +| taskType | M | M | M | O | M | +| taskStatus | M | M | M | O | M | +| patrolExecutor | M | M | M | O | M | +| startTime | O | M | M | O | – | +| endTime | O | M | M | O | – | +| pointSequence | M | M | M | O | M | +| recordList | M | M | M | O | M | +| orderID | M | M | M | O | M | +| resourceSet | M | M | M | O | M | + +Table 5 shows the specific description of the attributes related to OnsitePatrolTask: + +**Table 5** + +| Attribute name | Type | Explanation | +|----------------|--------------------|--------------------------------------------------------------------------------| +| taskID | String | Unique identifier, Patrol activity number | +| taskType | ENUM | [routine temporary else] | +| taskStatus | ENUM | [notready ready doing finished] | +| patrolExecutor | String | Personnel ID, drone number, robot number, etc. responsible for patrol activity | +| startTime | Date | The start time of patrol activity | +| endTime | Date | The end time of patrol activity | +| pointSequence | SEQUENCE OF String | List of location to be patrolled | +| recordList | SEQUENCE OF String | List of record while patrolling | +| orderID | String | Order number related to patrol activity | +| resourceSet | SET OF String | Equipment related to patrol activity | + +##### **6.3.2.2.3 Notifications** + +Table 6 shows the specific description of notifications of the site patrol activity: + +**Table 6** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### **6.3.2.3 Information object class related to patrol point (OnsitePatrolPoint)** + +The information model related to OnsitePatrolPoint is shown in Figure 5. + +![UML class diagram for OnsitePatrolPoint showing attributes: pointID, pointType, patrolDes, coordinates, and pointLabel. The diagram is titled '<> OnsitePatrolPoint'.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` + +classDiagram + class OnsitePatrolPoint { + -pointID + -pointType + -patrolDes + -coordinates + -pointLabel + } + +``` + +M.3164(20)\_F05 + +UML class diagram for OnsitePatrolPoint showing attributes: pointID, pointType, patrolDes, coordinates, and pointLabel. The diagram is titled '<> OnsitePatrolPoint'. + +**Figure 5 – Information model related to OnsitePatrolPoint** + +##### **6.3.2.3.1 Definition** + +This management entity describes relevant information related to patrol point. The use made of individual attributes and notification is detailed below: + +- pointType: Patrol points are divided into multiple types according to different patrol objects, and the attribute indicates the type about patrol point; +- patrolDes: Specifies the specific content about patrol to patrol point; +- coordinates: The spatial position coordinates of patrol points, include latitude, longitude, altitude and coordinate system. Among them, the coordinate system indicates the "geodetic coordinate system" that the coordinates are using, such as WGS84, IIRS, Krasovsky\_1940, GCS\_CN\_2000, etc. + +– pointLabel: Represents special mark about patrol point; + +An attribute value change notification shall be emitted when the value of the pointID, the pointType, the patrolDes, the coordinates or the pointLabel is changed. + +##### 6.3.2.3.2 Attributes + +Table 7 describes the attribute properties related to OnsitePatrolPoint: + +**Table 7** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| pointID | M | M | - | - | M | +| pointType | M | M | M | O | M | +| patrolDes | M | M | M | O | M | +| coordinates | M | M | M | O | M | +| pointLabel | M | M | M | O | M | + +Table 8 shows the specific description of the attributes related to OnsitePatrolPoint: + +**Table 8** + +| Attribute Name | Type | Explanation | +|----------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pointID | String | Unique identifier, patrol point number | +| pointType | ENUM | [building device else] | +| patrolDes | String | Patrol point detail description | +| coordinates | SET OF
CoordinateType | The spatial position coordinates of patrol point, include latitude, longitude, altitude and coordinate system.
CoordinateType ::= SET
{ latitude REAL,
longitude REAL,
altitude REAL,
coordinateSystem String } | +| pointLabel | String | Patrol point label | + +##### 6.3.2.3.3 Notifications + +Table 9 shows the specific description of notifications related to OnsitePatrolPoint: + +**Table 9** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.3.2.4 Information object class related to patrol record (OnsitePatrolRecord) + +The information model related to OnsitePatrolRecord is shown in Figure 6. + +![UML class diagram for OnsitePatrolRecord. The class name is OnsitePatrolRecord, and it has attributes: recordID, recordExecutor, recordTime, status, recordInfo, and pointID.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +classDiagram + class OnsitePatrolRecord { + -recordID + -recordExecutor + -recordTime + -status + -recordInfo + -pointID + } + +``` + +UML class diagram for OnsitePatrolRecord. The class name is OnsitePatrolRecord, and it has attributes: recordID, recordExecutor, recordTime, status, recordInfo, and pointID. + +M.3164(20)\_F06 + +**Figure 6 – Information model related to OnsitePatrolRecord** + +##### 6.3.2.4.1 Definition + +This management entity describes record information related to an on-site patrol process. The use made of individual attributes and notification is detailed below: + +- pointID: Represents the patrol point to which the record information belongs; +- status: Represents the status about recorded patrol point; +- recordExecutor: Represents the executor who made the patrol record; +- recordInfo: Represents important information recorded by the on-site patrol executor during the patrol process. + +An attribute value change notification shall be emitted when the value of the recordID, the pointID, the status or the recordInfo is changed. + +##### 6.3.2.4.2 Attributes + +Table 10 describes the attribute properties related to OnsitePatrolRecord: + +**Table 10** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| recordID | M | M | – | – | M | +| recordExecutor | O | M | M | O | – | +| recordTime | O | M | M | O | – | +| status | M | M | M | O | M | +| recordInfo | M | M | M | O | M | +| pointID | M | M | M | O | M | + +Table 11 shows the specific description of the attributes related to OnsitePatrolRecord: + +**Table 11** + +| Attribute Name | Type | Explanation | +|----------------|--------|---------------------------------------------------------------------| +| recordID | String | Unique identifier, patrol record number | +| recordExecutor | String | Personnel ID, drone number, robot number, etc. for recording | +| recordTime | Date | Patrol record time | +| status | ENUM | Status about recorded patrol point [normal abnormal notCheck] | +| recordInfo | String | Specific information about record | +| pointID | String | The patrol record corresponds to identifier related to patrol point | + +##### 6.3.2.4.3 Notifications + +Table 12 shows the specific description of notifications related to OnsitePatrolRecord: + +**Table 12** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +## 6.4 On-site overhaul information model + +### 6.4.1 Relationship class diagram between object classes + +The Relationship class diagram between object classes related to on-site overhaul is shown in Figure 7. + +![UML class diagram showing relationships between ResourceInfo, OnsiteOverhaulInfo, and OnsiteOverhaulTask classes. ResourceInfo is a ProxyClass. OnsiteOverhaulTask is an InformationObjectClass contained within OnsiteOverhaulInfo. There is a many-to-many association between ResourceInfo and OnsiteOverhaulTask, and a one-to-many composition relationship between OnsiteOverhaulInfo and OnsiteOverhaulTask.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` + +classDiagram + class ResourceInfo { + <> + } + class OnsiteOverhaulInfo { + <> + } + class OnsiteOverhaulTask { + <> + } + OnsiteOverhaulInfo "1" *-- "n" OnsiteOverhaulTask : <> + ResourceInfo "n" -- "n" OnsiteOverhaulTask : +ResourceInfo + note for ResourceInfo "It represents all resource entities." + M.3164(20)_F07 + +``` + +UML class diagram showing relationships between ResourceInfo, OnsiteOverhaulInfo, and OnsiteOverhaulTask classes. ResourceInfo is a ProxyClass. OnsiteOverhaulTask is an InformationObjectClass contained within OnsiteOverhaulInfo. There is a many-to-many association between ResourceInfo and OnsiteOverhaulTask, and a one-to-many composition relationship between OnsiteOverhaulInfo and OnsiteOverhaulTask. + +**Figure 7 – Relationship class diagram between object classes related to on-site overhaul** + +In Figure 7, the information object classes related to on-site overhaul include OnsiteOverhaulTask, OnsiteOverhaulTask is contained in OnsiteOverhaulInfo. The overhaul object contains one or more resources, so that OnsiteOverhaulTask and ResourceInfo are many-to-many and one-way association relationships. + +#### 6.4.2 Object class information model and attribute description + +#### 6.4.2.1 Information object class related to on-site overhaul (OnsiteOverhaulInfo) + +##### 6.4.2.1.1 Definition + +The *OnsiteOverhaulInfo* management entity describes basic information related to top-level class about on-site overhaul. + +##### 6.4.2.1.2 Attributes + +Table 13 describes the attribute properties related to OnsiteOverhaulInfo: + +**Table 13** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|------------------|-------------------|----------------|-----------------|---------------------|----------------| +| overhaulInfoID | M | M | – | – | M | +| overhaulTaskList | M | M | M | O | M | + +Table 14 shows the specific description of the attributes related to OnsiteOverhaulInfo: + +**Table 14** + +| Attribute name | Type | Explanation | +|------------------|--------------------|-------------------------------------------------| +| overhaulInfoID | String | Unique identifier related to OnsiteOverhaulInfo | +| overhaulTaskList | SEQUENCE OF String | List of on-site overhaul activities | + +##### 6.4.2.1.3 Notifications + +Table 15 shows the specific description of notifications related to OnsiteOverhaulInfo: + +**Table 15** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.4.2.2 Information object class related to overhaul activity (OnsiteOverhaulTask) + +The information model related to OnsiteOverhaulTask is shown in Figure 8. + +![UML class diagram for OnsiteOverhaulTask. The class name is OnsiteOverhaulTask, with a stereotype <>. The attributes listed are: - taskID, - overhaulExecutor, - overhaulStatus, - overhaulDes, - timeInfo, - orderID, and - resourceSet. A dashed line separates the attributes from the rest of the class. Below the diagram is the text M.3164(20)_F08.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +``` + +classDiagram + class OnsiteOverhaulTask { + <> + - taskID + - overhaulExecutor + - overhaulStatus + - overhaulDes + - timeInfo + - orderID + - resourceSet + } + +``` + +M.3164(20)\_F08 + +UML class diagram for OnsiteOverhaulTask. The class name is OnsiteOverhaulTask, with a stereotype <>. The attributes listed are: - taskID, - overhaulExecutor, - overhaulStatus, - overhaulDes, - timeInfo, - orderID, and - resourceSet. A dashed line separates the attributes from the rest of the class. Below the diagram is the text M.3164(20)\_F08. + +**Figure 8 – Information model related to OnsiteOverhaulTask** + +##### 6.4.2.2.1 Definition + +This management entity describes basic information related to on-site overhaul activity. The use made of individual attributes and notification is detailed below: + +- overhaulStatus: Represents implementation about on-site overhaul activity; +- overhaulDes: Represents specific content about overhaul; +- orderID: The order is the information related to maintenance task sent from TSMS, including maintenance task types, maintenance objects, serial numbers, etc. OrderID represents the serial number of the order about the overhaul activity; +- resourceSet: Represents equipment about overhaul activity. + +An attribute value change notification shall be emitted when the value of the taskID, the overhaulStatus, the overhaulDes, the orderID or the resourceSet is changed. + +##### 6.4.2.2.2 Attributes + +Table 16 describes the attribute properties related to OnsiteOverhaulTask: + +**Table 16** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|------------------|-------------------|----------------|-----------------|---------------------|----------------| +| taskID | M | M | – | – | M | +| overhaulExecutor | O | M | M | O | – | +| overhaulStatus | M | M | M | O | M | +| overhaulDes | M | M | M | O | M | +| timeInfo | O | M | M | O | – | +| orderID | M | M | M | O | M | +| resourceSet | M | M | M | O | M | + +Table 17 shows the specific description of the attributes related to OnsiteOverhaulTask: + +**Table 17** + +| Attribute name | Type | Explanation | +|------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| taskID | String | Unique identifier, overhaul activity number | +| overhaulExecutor | String | Personnel ID or robot number responsible for overhaul activity | +| overhaulStatus | ENUM | [notStart doing finished] | +| overhaulDes | String | Specific overhaul content description | +| timeInfo | SEQUENCE OF TimeInfoType | Start time and end time of overhaul activity.
TimeInfoType ::= SEQUENCE
{ startTime GeneralizedTime,
endTime GeneralizedTime } | +| orderID | String | Task order number related to overhaul activity | +| resourceSet | SET OF String | Equipment related to overhaul activity | + +##### 6.4.2.2.3 Notifications + +Table 18 shows the specific description of notifications related to OnsiteOverhaulTask: + +**Table 18** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +## 6.5 On-site troubleshooting information model + +### 6.5.1 Relationship class diagram between object classes + +The relationship class diagram between object classes related to on-site troubleshooting is shown in Figure 9. + +![Relationship class diagram between object classes related to on-site troubleshooting. The diagram shows four classes: OnsiteTroubleshootingInfo (InformationObjectClass), OnsiteTroubleshootingTask (InformationObjectClass), ResourceInfo (ProxyClass), TroubleType (InformationObjectClass), and Expert (InformationObjectClass). OnsiteTroubleshootingInfo has a 1:n relationship with OnsiteTroubleshootingTask (named <>). OnsiteTroubleshootingTask has a 0..1 relationship with TroubleType (named +TroubleType). OnsiteTroubleshootingTask has an n:n relationship with ResourceInfo (named +ResourceInfo). A note points to ResourceInfo stating 'It represents all resource entities.'. TroubleType has a n:n relationship with Expert (named +Expert). A note at the bottom right indicates 'M.3164(20)_F09'.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +classDiagram + class OnsiteTroubleshootingInfo { + <> + } + class OnsiteTroubleshootingTask { + <> + } + class ResourceInfo { + <> + } + class TroubleType { + <> + } + class Expert { + <> + } + + OnsiteTroubleshootingInfo "1" *-- "n" OnsiteTroubleshootingTask : <> + OnsiteTroubleshootingTask "n" -- "0..1" TroubleType : +TroubleType + OnsiteTroubleshootingTask "n" -- "n" ResourceInfo : +ResourceInfo + TroubleType "n" -- "n" Expert : +Expert + Note for ResourceInfo "It represents all resource entities." + Note right of Expert "M.3164(20)_F09" + +``` + +Relationship class diagram between object classes related to on-site troubleshooting. The diagram shows four classes: OnsiteTroubleshootingInfo (InformationObjectClass), OnsiteTroubleshootingTask (InformationObjectClass), ResourceInfo (ProxyClass), TroubleType (InformationObjectClass), and Expert (InformationObjectClass). OnsiteTroubleshootingInfo has a 1:n relationship with OnsiteTroubleshootingTask (named <>). OnsiteTroubleshootingTask has a 0..1 relationship with TroubleType (named +TroubleType). OnsiteTroubleshootingTask has an n:n relationship with ResourceInfo (named +ResourceInfo). A note points to ResourceInfo stating 'It represents all resource entities.'. TroubleType has a n:n relationship with Expert (named +Expert). A note at the bottom right indicates 'M.3164(20)\_F09'. + +**Figure 9 – Relationship class diagram between object classes related to on-site troubleshooting** + +In Figure 9, the information object classes related to on-site troubleshooting include OnsiteTroubleshootingTask, TroubleType and Expert. The object related to the trouble is a resource, and the trouble handling tasks are classified according to the known trouble type, and a trouble handling task belongs to a certain type or a currently unknown type. At the same time, experts can solve one or more types of trouble based on their expertise. Therefore, OnsiteTroubleshootingTask and ResourceInfo are many-to-many and one-way association relationships, and TroubleType are many-to-zero or one and one-way association relationships, and TroubleType and Expert are many-to-many and two-way association relationships. + +### 6.5.2 Object class information model and attribute description + +#### 6.5.2.1 Information object class related to on-site troubleshooting (OnsiteTroubleshootingInfo) + +##### 6.5.2.1.1 Definition + +The *OnsiteTroubleshootingInfo* management entity describes basic information related to top-level class about on-site troubleshooting. + +##### 6.5.2.1.2 Attributes + +Table 19 describes the attribute properties related to OnsiteTroubleshootingInfo: + +**Table 19** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-------------------------|-------------------|----------------|-----------------|---------------------|----------------| +| troubleshootingInfoID | M | M | – | – | M | +| troubleshootingTaskList | M | M | M | O | M | + +Table 20 shows the specific description of the attributes related to OnsiteTroubleshootingInfo: + +**Table 20** + +| Attribute Name | Type | Explanation | +|-------------------------|--------------------|--------------------------------------------------------| +| troubleshootingInfoID | String | Unique identifier related to OnsiteTroubleshootingInfo | +| troubleshootingTaskList | SEQUENCE OF String | List of on-site troubleshooting activities | + +##### 6.5.2.1.3 Notifications + +Table 21 shows the specific description of notifications of the on-site troubleshooting top-level class: + +**Table 21** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.5.2.2 Information object class related to troubleshooting task (OnsiteTroubleshootingTask) + +The information model related to OnsiteTroubleshootingTask is shown in Figure 10. + +![UML class diagram for OnsiteTroubleshootingTask. The class name is OnsiteTroubleshootingTask, with a stereotype <>. The attributes listed are: - taskID, - occurTime, - status, - troubleDes, - confirmInfo, - maintenanceInfo, - troubleTypeID, - orderID, and - resourceSet. A dashed line separates the attributes from the bottom of the class box. Below the diagram is the label M.3164(20)_F10.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +``` + +classDiagram + class OnsiteTroubleshootingTask { + <> + -taskID + -occurTime + -status + -troubleDes + -confirmInfo + -maintenanceInfo + -troubleTypeID + -orderID + -resourceSet + } + +``` + +M.3164(20)\_F10 + +UML class diagram for OnsiteTroubleshootingTask. The class name is OnsiteTroubleshootingTask, with a stereotype <>. The attributes listed are: - taskID, - occurTime, - status, - troubleDes, - confirmInfo, - maintenanceInfo, - troubleTypeID, - orderID, and - resourceSet. A dashed line separates the attributes from the bottom of the class box. Below the diagram is the label M.3164(20)\_F10. + +**Figure 10 – Information model related to OnsiteTroubleshootingTask** + +##### 6.5.2.2.1 Definition + +This management entity describes basic information related to on-site troubleshooting activity. The use made of individual attributes and notification is detailed below: + +- status: Represents execution about on-site troubleshooting activity; +- troubleDes: This attribute describes specific information about trouble, such as the location information; +- troubleTypeID: Represents the type to which the trouble belongs; +- orderID: The order is the information related to maintenance task sent from TSMS, including maintenance tasks types, maintenance objects, serial numbers, etc. OrderID represents the serial number of the order about the on-site troubleshooting activity; +- resourceSet: Represents equipment about on-site troubleshooting activity. + +An attribute value change notification shall be emitted when the value of the taskID, the status, the troubleDes, the troubleTypeID, the orderID or the resourceSet is changed. + +##### 6.5.2.2.2 Attributes + +Table 22 describes the attribute properties related to OnsiteTroubleshootingTask: + +**Table 22** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-----------------|-------------------|----------------|-----------------|---------------------|----------------| +| taskID | M | M | – | – | M | +| occurTime | O | M | M | O | – | +| status | M | M | M | O | M | +| troubleDes | M | M | M | O | M | +| confirmInfo | O | M | M | O | – | +| maintenanceInfo | O | M | M | O | – | +| troubleTypeID | M | M | M | O | M | +| orderID | M | M | M | O | M | +| resourceSet | M | M | M | O | M | + +Table 23 shows the specific description of the attributes related to OnsiteTroubleshootingTask: + +**Table 23** + +| Attribute name | Type | Explanation | +|-----------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| taskID | String | Unique identifier, troubleshooting activity number | +| occurTime | Date | Time of occurrence | +| status | ENUM | [notstart doing finished] | +| troubleDes | String | Description about trouble | +| confirmInfo | SET OF ConfirmInfoType | Including name about confirmer, confirmation time.
ConfirmInfoType ::= SET
{ confirmer String,
confirmTime GeneralizedTime } | +| maintenanceInfo | SET OF ConfirmInfoType | Including name about maintenance personnel, maintenance plan, maintenance time.
MaintenanceInfoType ::= SET
{ maintainExecutor String,
maintainPlan String,
maintainTime GeneralizedTime } | +| troubleTypeID | String | Identifier of the type of trouble number, if the association can be established. | +| orderID | String | Activity order number of the source related to troubleshooting activity | +| resourceSet | SET OF String | Equipment related to troubleshooting activity | + +##### 6.5.2.2.3 Notifications + +Table 24 shows the specific description of notifications related to OnsiteTroubleshootingTask: + +**Table 24** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.5.2.3 Information object class related to type of trouble (TroubleType) + +The information model related to TroubleType is shown in Figure 11. + +![UML class diagram for TroubleType. The class is named 'TroubleType' and is of type 'InformationObjectClass'. It has five attributes: - troubleTypeID, - troubleLevel, - troubleTypeDes, - solution, and - expertSet. The diagram is labeled M.3164(20)_F11.](a3472689858b068ef469213682965325_img.jpg) + +``` + +classDiagram + class TroubleType { + -troubleTypeID + -troubleLevel + -troubleTypeDes + -solution + -expertSet + } + note for TroubleType "<>" + +``` + +UML class diagram for TroubleType. The class is named 'TroubleType' and is of type 'InformationObjectClass'. It has five attributes: - troubleTypeID, - troubleLevel, - troubleTypeDes, - solution, and - expertSet. The diagram is labeled M.3164(20)\_F11. + +**Figure 11 – Information model related to TroubleType** + +##### 6.5.2.3.1 Definition + +This management entity describes basic information related to the type of trouble. The use made of individual attributes and notification is detailed below: + +- troubleLevel: Troubles are classified into different levels according to severity about trouble. This attribute represents trouble level; +- troubleTypeDes: This attribute specifies specific information about type of trouble; +- solution: This attribute describes specific processing solution about trouble; +- expertSet: Represents these experts with the ability to process the trouble; + +An attribute value change notification shall be emitted when the value of the troubleTypeID, the troubleLevel, the troubleDes, the solution or the expertSet is changed. + +##### 6.5.2.3.2 Attributes + +Table 25 describes the attribute properties related to TroubleType: + +**Table 25** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| troubleTypeID | M | M | – | – | M | +| troubleLevel | M | M | M | O | M | +| troubleTypeDes | M | M | M | O | M | +| solution | M | M | M | O | M | +| expertSet | M | M | M | O | M | + +Table 26 shows the specific description of the attributes related to TroubleType: + +**Table 26** + +| Attribute name | Type | Explanation | +|----------------|---------------|-----------------------------------------------| +| troubleTypeID | String | Unique identifier, The type of trouble number | +| troubleLevel | ENUM | [urgent serious warn common] | +| troubleTypeDes | String | Trouble description | +| solution | String | Troubleshooting solution | +| expertSet | SET OF String | Remotely assisted expert identification set | + +##### 6.5.2.3.3 Notifications + +Table 27 shows the specific description of notifications related to TroubleType: + +**Table 27** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.5.2.4 Information object class related to expert (Expert) + +The information model related to Expert is shown in Figure 12. + +![UML class diagram for Expert information object class. The class name is 'Expert' with the stereotype '<>'. The attributes listed are: expertID, expertAddtionInfo, expertGroup, expertDepartment, email, skillArea, and availableRate. The diagram is labeled M.3164(20)_F12.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +classDiagram + class Expert { + <> + -expertID + -expertAddtionInfo + -expertGroup + -expertDepartment + -email + -skillArea + -availableRate + } + +``` + +M.3164(20)\_F12 + +UML class diagram for Expert information object class. The class name is 'Expert' with the stereotype '<>'. The attributes listed are: expertID, expertAddtionInfo, expertGroup, expertDepartment, email, skillArea, and availableRate. The diagram is labeled M.3164(20)\_F12. + +**Figure 12 – Information model related to Expert** + +##### 6.5.2.4.1 Definition + +This management entity describes basic information related to an expert who can remotely assist with troubleshooting. The use made of individual attributes and notification is detailed below: + +- expertGroup: Represents expert group to which expert belongs; +- email: Represents contact method about the expert; +- skillArea: Represents a special field about the expert, corresponding to type of maintenance task; + +An attribute value change notification shall be emitted when the value of the expertID, the expertGroup, the email, the skillArea or the availableRate is changed. + +##### 6.5.2.4.2 Attributes + +Table 28 describes the attribute properties related to Expert: + +**Table 28** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-------------------|-------------------|----------------|-----------------|---------------------|----------------| +| expertID | M | M | – | – | M | +| expertAddtionInfo | O | M | M | O | – | +| expertGroup | M | M | M | O | M | +| expertDepartment | O | M | M | O | – | +| email | M | M | M | O | M | +| skillArea | M | M | M | O | M | +| availableRate | M | M | M | O | M | + +Table 29 shows the specific description of the attributes related to Expert: + +**Table 29** + +| Attribute Name | Type | Explanation | +|-------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| expertID | String | Unique identifier, Expert number | +| expertAddtionInfo | SET OF String | Including the name, gender and birth year.
ExpertAddtionInfoType ::= SET
{ name String,
gender ENUMERATED,
birthYear GeneralizedTime } | +| expertGroup | String | Name of expert group | +| expertDepartment | String | Expert department | +| email | String | Contact method is mainly mailbox | +| skillArea | String | On-site maintenance personnel match the expert's special field according to type of trouble | +| availableRate | Double | The probability that the expert can provide online services.
An on-site maintenance executor may select experts with high availableRate | + +##### 6.5.2.4.3 Notifications + +Table 30 shows the specific description of notifications related to Expert: + +**Table 30** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +## 6.6 Service activation information model + +### 6.6.1 Relationship class diagram between object classes + +The relationship class diagram between object classes related to service activation is shown in Figure 13. + +![Relationship class diagram between object classes related to service activation. The diagram shows ServiceActivationInfo at the top, ServiceActivationTask in the middle, ServiceActivationRecord at the bottom, and ResourceInfo to the right. ServiceActivationInfo has a 1:n relationship with ServiceActivationTask labeled '<>'. ServiceActivationTask has a 1:n relationship with ServiceActivationRecord labeled '<>'. ServiceActivationTask has a many-to-many association with ResourceInfo labeled '+ResourceInfo'. A note above ResourceInfo states 'It represents all resource entities.' The diagram is labeled M.3164(20)_F13.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +classDiagram + class ServiceActivationInfo { + <> + } + class ServiceActivationTask { + <> + } + class ServiceActivationRecord { + <> + } + class ResourceInfo { + <> + } + ServiceActivationInfo "1" *-- "n" ServiceActivationTask : <> + ServiceActivationTask "1" *-- "n" ServiceActivationRecord : <> + ServiceActivationTask "n" -- "n" ResourceInfo : +ResourceInfo + note for ResourceInfo "It represents all resource entities." + M.3164(20)_F13 + +``` + +Relationship class diagram between object classes related to service activation. The diagram shows ServiceActivationInfo at the top, ServiceActivationTask in the middle, ServiceActivationRecord at the bottom, and ResourceInfo to the right. ServiceActivationInfo has a 1:n relationship with ServiceActivationTask labeled '<>'. ServiceActivationTask has a 1:n relationship with ServiceActivationRecord labeled '<>'. ServiceActivationTask has a many-to-many association with ResourceInfo labeled '+ResourceInfo'. A note above ResourceInfo states 'It represents all resource entities.' The diagram is labeled M.3164(20)\_F13. + +**Figure 13 – Relationship class diagram between object classes related to service activation** + +In Figure 13, the information object classes related to service activation include *ServiceActivationTask* and *ServiceActivationRecord*. The object related to service activation activities is one or more resources. On-site maintenance executor will record relevant information when performing service activation activities. Therefore, *ServiceActivationTask* and *ResourceInfo* are many-to-many and one-way association relationships. *ServiceActivationTask* contains a number of *ServiceActivationRecord*. + +#### 6.6.2 Object class information model and attribute description + +#### 6.6.2.1 Information object class related to service activation (*ServiceActivationInfo*) + +##### 6.6.2.1.1 Definition + +The *ServiceActivationInfo* management entity describes basic information related to the top-level class about service activation. + +##### 6.6.2.1.2 Attributes + +Table 31 describes the attribute properties related to *ServiceActivationInfo*: + +**Table 31** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|---------------------------|-------------------|----------------|-----------------|---------------------|----------------| +| serviceActInfoID | M | M | – | – | M | +| serviceActTaskList | M | M | M | O | M | + +Table 32 shows the specific description of the attributes related to *ServiceActivationInfo*: + +**Table 32** + +| Attribute Name | Type | Explanation | +|---------------------------|--------------------|-----------------------------------------------------------| +| serviceActInfoID | String | Unique identifier related to ServiceActivationInfo | +| serviceActTaskList | SEQUENCE OF String | List of Service activation tasks | + +##### 6.6.2.1.3 Notifications + +Table 33 shows the specific description of notifications related to ServiceActivationInfo: + +**Table 33** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.6.2.2 Information object class related to service activation activity (ServiceActivationTask) + +The information model related to ServiceActivationTask is shown in Figure 14. + +![UML class diagram for ServiceActivationTask. The class name is ServiceActivationTask, with a stereotype <>. The attributes listed are: - taskID, - serviceActDes, - executeInfo, - recordList, - orderID, and - resourceSet. A dashed line separates the attributes from the rest of the class box. Below the diagram is the text M.3164(20)_F14.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +<> +**ServiceActivationTask** + +- taskID +- serviceActDes +- executeInfo +- recordList +- orderID +- resourceSet + +M.3164(20)\_F14 + +UML class diagram for ServiceActivationTask. The class name is ServiceActivationTask, with a stereotype <>. The attributes listed are: - taskID, - serviceActDes, - executeInfo, - recordList, - orderID, and - resourceSet. A dashed line separates the attributes from the rest of the class box. Below the diagram is the text M.3164(20)\_F14. + +**Figure 14 – Information model related to ServiceActivationTask** + +##### 6.6.2.2.1 Definition + +This managed entity describes basic information related to service activation activity. The use made of individual attributes and notification is detailed below: + +- serviceActDes: This attribute records details about service activation activity; +- executeInfo: Document relevant information about execution; +- recordList: Represents information records of the service activation activity execution process; +- orderID: The order is the information related to maintenance task sent from TSMS, including maintenance tasks types, maintenance objects, serial numbers, etc. OrderID represents the serial number of the order about the service activation activity; +- resourceSet: Represents equipment about service activation activity. + +An attribute value change notification shall be emitted when the value of the taskID, the serviceActDes, the executeInfo, the recordList, the orderID or the resourceSet is changed. + +##### 6.6.2.2.2 Attributes + +Table 34 describes the attribute properties related to ServiceActivationTask: + +**Table 34** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| taskID | M | M | – | – | M | +| serviceActDes | M | M | M | O | M | +| executeInfo | M | M | M | O | M | +| recordList | M | M | M | O | M | +| orderID | M | M | M | O | M | +| resourceSet | M | M | M | O | M | + +Table 35 shows the specific description of the attributes related to ServiceActivationTask: + +**Table 35** + +| Attribute Name | Type | Explanation | +|----------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| taskID | String | Unique identifier, service activation activity number | +| serviceActDes | String | Description of specific contents about service activation activity | +| executeInfo | SET OF ExecuteInfoType | Including executor, execution time, execution results.
ExecuteInfoType ::= SET
{ executor String,
executionTime GeneralizedTime,
executionResults String } | +| recordList | SEQUENCE OF String | List of record identifiers for activity execution process | +| orderID | String | Task order number of the source related to service activation activity | +| resourceSet | SET OF String | Equipment related to service activation activity | + +##### 6.6.2.2.3 Notifications + +Table 36 shows the specific description of notifications related to ServiceActivationTask: + +**Table 36** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.6.2.3 Information object class related to record of Service activation (ServiceActivationRecord) + +The information model related to ServiceActivationRecord is shown in Figure 15. + +![UML Class Diagram for ServiceActivationRecord](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` + +classDiagram + class ServiceActivationRecord { + -recordID + -recordInfo + -submitExecutor + -submitTime + } + +``` + +UML Class Diagram for ServiceActivationRecord + +M.3164(20)\_F15 + +**Figure 15 – Information model related to ServiceActivationRecord** + +##### 6.6.2.3.1 Definition + +This management entity describes information about record of service activation. The use made of individual attributes and notification is detailed below: + +- recordInfo: This attribute records details about service activation activity; + +An attribute value change notification shall be emitted when the value of the recordID or the recordInfo is changed. + +##### 6.6.2.3.2 Attributes + +Table 37 describes the attribute properties related to ServiceActivationRecord: + +**Table 37** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| recordID | M | M | – | – | M | +| recordInfo | M | M | M | O | M | +| submitExecutor | O | M | M | O | – | +| submitTime | O | M | M | O | – | + +Table 38 shows the specific description of the attributes related to ServiceActivationRecord: + +**Table 38** + +| Attribute Name | Type | Explanation | +|----------------|--------|---------------------------------------------------------| +| recordID | String | Unique identifier, record of service activation number | +| recordInfo | String | Specific content about record | +| submitExecutor | String | Personnel ID, robot number, etc. for submitting records | +| submitTime | Date | Time of submission about records | + +##### 6.6.2.3.3 Notifications + +Table 39 shows the specific description of notifications related to ServiceActivationRecord: + +**Table 39** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +## 6.7 Maintenance knowledge base information model + +### 6.7.1 Relationship class diagram between object classes + +The relationship class diagram between object classes related to maintenance knowledge base is shown in Figure 16. + +![UML Class Diagram showing relationships between MaintenanceKnowledgeBaseInfo, MaintenanceKnowledgeBaseItem, and TroubleType.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +classDiagram + class MaintenanceKnowledgeBaseInfo { + <> + } + class MaintenanceKnowledgeBaseItem { + <> + } + class TroubleType { + <> + } + MaintenanceKnowledgeBaseInfo "1" *-- "n" MaintenanceKnowledgeBaseItem : <> + MaintenanceKnowledgeBaseItem "1" -- "0..1" TroubleType + +``` + +The diagram shows three classes: **MaintenanceKnowledgeBaseInfo**, **MaintenanceKnowledgeBaseItem**, and **TroubleType**. **MaintenanceKnowledgeBaseInfo** has a composition relationship with **MaintenanceKnowledgeBaseItem** (1 to n, labeled <>). **MaintenanceKnowledgeBaseItem** has an association relationship with **TroubleType** (1 to 0..1). + +UML Class Diagram showing relationships between MaintenanceKnowledgeBaseInfo, MaintenanceKnowledgeBaseItem, and TroubleType. + +**Figure 16 – Relationship class diagram between object classes related to maintenance knowledge base** + +In Figure 16, the information object classes related to maintenance knowledge base include **MaintenanceKnowledgeBaseItem**. Maintenance knowledge items can be organized by operating steps that are more efficient in processing maintenance activities, including on-site patrol, on-site overhaul, on-site troubleshooting, service activation, etc. At the same time, relevant guidance may be obtained from the maintenance knowledge base when dealing with maintenance activities. Therefore, **MaintenanceKnowledgeBaseItem** and **TroubleType** are one-to-zero or one and two-way association relationship. + +### 6.7.2 Object class information model and attribute description + +#### 6.7.2.1 Information object class related to maintenance knowledge base (MaintenanceKnowledgeBaseInfo) + +##### 6.7.2.1.1 Definition + +The **MaintenanceKnowledgeBaseInfo** management entity describes basic information related to top-level class about maintenance knowledge base. + +##### 6.7.2.1.2 Attributes + +Table 40 describes the attribute properties related to **MaintenanceKnowledgeBaseInfo**: + +**Table 40** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------------------------|-------------------|----------------|-----------------|---------------------|----------------| +| maintenanceKnowledgeBaseInfoID | M | M | – | – | M | +| maintenanceKnowledgeBaseItemList | M | M | M | O | M | + +Table 41 shows the specific description of the attributes related to **MaintenanceKnowledgeBaseInfo**: + +**Table 41** + +| Attribute name | Type | Explanation | +|----------------------------------|--------------------|-----------------------------------------------------------| +| maintenanceKnowledgeBaseInfoID | String | Unique identifier related to MaintenanceKnowledgeBaseInfo | +| maintenanceKnowledgeBaseItemList | SEQUENCE OF String | List of Maintenance knowledge base items | + +##### **6.7.2.1.3 Notifications** + +Table 42 shows the specific description of notifications related to MaintenanceKnowledgeBaseInfo: + +**Table 42** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### **6.7.2.2 Information object class related to maintenance knowledge item (MaintenanceKnowledgeBaseItem)** + +The information model related to MaintenanceKnowledgeBaseItem is shown in Figure 17. + +![UML class diagram for MaintenanceKnowledgeBaseItem. The class is labeled <> MaintenanceKnowledgeBaseItem. It contains attributes: itemID, knowledgeDes, knowledgeType, knowledgeStatus, submitInfo, and checkInfo. The diagram is labeled M.3164(20)_F17.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +classDiagram + class MaintenanceKnowledgeBaseItem { + -itemID + -knowledgeDes + -knowledgeType + -knowledgeStatus + -submitInfo + -checkInfo + } + MaintenanceKnowledgeBaseItem <> + +``` + +M.3164(20)\_F17 + +UML class diagram for MaintenanceKnowledgeBaseItem. The class is labeled <> MaintenanceKnowledgeBaseItem. It contains attributes: itemID, knowledgeDes, knowledgeType, knowledgeStatus, submitInfo, and checkInfo. The diagram is labeled M.3164(20)\_F17. + +**Figure 17 – Information model related to MaintenanceKnowledgeBaseItem** + +##### **6.7.2.2.1 Definition** + +This management entity describes basic information related to maintenance knowledge item. The use made of individual attributes and notification is detailed below: + +- knowledgeDes: Describe specific content about knowledge; +- knowledgeType: Represents type of maintenance knowledge item; +- knowledgeStatus: Represents check status about knowledge. + +An attribute value change notification shall be emitted when the value of the itemID, the knowledgeDes, the knowledgeType or the knowledgeStatus is changed. + +##### **6.7.2.2.2 Attributes** + +Table 43 describes the attribute properties related to MaintenanceKnowledgeBaseItem: + +**Table 43** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-----------------------|--------------------------|-----------------------|------------------------|----------------------------|-----------------------| +| itemID | M | M | – | – | M | +| knowledgeDes | M | M | M | O | M | +| knowledgeType | M | M | M | O | M | +| knowledgeStatus | M | M | M | O | M | +| submitInfo | O | M | M | O | – | +| checkInfo | O | M | M | O | – | + +Table 44 shows the specific description of the attributes related to MaintenanceKnowledgeBaseItem: + +**Table 44** + +| Attribute name | Type | Explanation | +|-----------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| itemID | String | Unique identifier, Maintenance knowledge item | +| knowledgeDes | String | Description of knowledge content. For example, it describes a specific high-efficiency process for a certain type of trouble. | +| knowledgeType | ENUM | [patrol overhaul troubleshoo serviceAct] | +| knowledgeStatus | ENUM | [submitting notCheck checking checkedOK checkedFail] | +| submitInfo | SET OF SubmitInfoType | Information about the submission of knowledge, including the submitter and the time of submission.
SubmitInfoType ::= SET
{ submitterID String,
submitTime GeneralizedTime} | +| checkInfo | SET OF CheckInfoType | Information about the check of knowledge, including the checker and the time of check.
CheckInfoType ::= SET
{ checkerID String,
checkerTime GeneralizedTime} | + +##### 6.7.2.2.3 Notifications + +Table 45 shows the specific description of notifications related to MaintenanceKnowledgeBaseItem: + +**Table 45** + +| Name | Qualifier | Description | +|----------------------|------------------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +## 6.8 Maintenance work evaluation information model + +### 6.8.1 Relationship class diagram between object classes + +The relationship class diagram between object classes related to maintenance work evaluation is shown in Figure 18. + +![UML class diagram showing relationships between MaintenanceWorkEvaluationInfo, MaintenanceWorkEvaluationItem, and four task classes: OnsitePatrolTask, OnsiteOverhaulTask, OnsiteTroubleshootingTask, and ServiceActivationTask.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +classDiagram + class MaintenanceWorkEvaluationInfo { + <> + } + class MaintenanceWorkEvaluationItem { + <> + } + class OnsitePatrolTask { + <> + } + class OnsiteOverhaulTask { + <> + } + class OnsiteTroubleshootingTask { + <> + } + class ServiceActivationTask { + <> + } + + MaintenanceWorkEvaluationInfo "1" *-- "n" MaintenanceWorkEvaluationItem : <> + MaintenanceWorkEvaluationItem "1" -- "0..1" OnsitePatrolTask : +OnsitePatrolTask + MaintenanceWorkEvaluationItem "1" -- "0..1" OnsiteOverhaulTask : +OnsiteOverhaulTask + MaintenanceWorkEvaluationItem "1" -- "0..1" OnsiteTroubleshootingTask : +OnsiteTroubleshootingTask + MaintenanceWorkEvaluationItem "1" -- "0..1" ServiceActivationTask : +ServiceActivationTask + +``` + +M.3164(20)\_F18 + +UML class diagram showing relationships between MaintenanceWorkEvaluationInfo, MaintenanceWorkEvaluationItem, and four task classes: OnsitePatrolTask, OnsiteOverhaulTask, OnsiteTroubleshootingTask, and ServiceActivationTask. + +**Figure 18 – Relationship class diagram between the object classes related to maintenance work evaluation** + +In Figure 18, the information object classes related to maintenance work evaluation include *MaintenanceWorkEvaluationItem* and objects related to maintenance work evaluation, that is, on-site patrol activities, on-site overhaul activities, on-site troubleshooting activities, and service activation activities. Each evaluation item corresponds to an activity, therefore, *MaintenanceWorkEvaluationItem* and *OnsitePatrolTask*, *OnsiteOverhaulTask*, *OnsiteTroubleshootingTask*, *ServiceActivationTask* are one-to-one and one-way relationships. + +### 6.8.2 Object class information model and attribute description + +#### 6.8.2.1 Top-level class about maintenance work evaluation (*MaintenanceWorkEvaluationInfo*) + +##### 6.8.2.1.1 Definition + +The *MaintenanceWorkEvaluationInfo* management entity describes basic information related to top-level class about maintenance work evaluation. + +##### 6.8.2.1.2 Attributes + +Table 46 describes the attribute properties related to *MaintenanceWorkEvaluationInfo*: + +**Table 46** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|------------------------------------|-------------------|----------------|-----------------|---------------------|----------------| +| maintenanceWorkEvalInfoID | M | M | – | – | M | +| maintenanceWorkEvalItemList | M | M | M | O | M | + +Table 47 shows the specific description of the attributes related to MaintenanceWorkEvaluationInfo: + +**Table 47** + +| Attribute name | Type | Explanation | +|-----------------------------|--------------------|-----------------------------------------------------------| +| maintenanceWorkEvalInfoID | String | Unique identifier related to MaintenanceworkEvalutionInfo | +| maintenanceWorkEvalItemList | SEQUENCE OF String | List of maintenance work evaluation items | + +##### 6.8.2.1.3 Notifications + +Table 48 shows the specific description of notifications related to MaintenanceWorkEvaluationInfo: + +**Table 48** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.8.2.2 Information object class related to maintenance work evaluation item (MaintenanceWorkEvaluationItem) + +The information model related to MaintenanceWorkEvaluationItem is shown in Figure 19. + +![UML class diagram for MaintenanceWorkEvaluationItem. The class is labeled <> MaintenanceWorkEvaluationItem. It contains five attributes: - itemID, - evaluateResult, - evaluateTime, - evaluateExecutor, and - taskID. A dashed line separates the attributes from the bottom of the class box. Below the diagram is the text M.3164(20)_F19.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` + +classDiagram + class MaintenanceWorkEvaluationItem { + -itemID + -evaluateResult + -evaluateTime + -evaluateExecutor + -taskID + } + MaintenanceWorkEvaluationItem <> + +``` + +M.3164(20)\_F19 + +UML class diagram for MaintenanceWorkEvaluationItem. The class is labeled <> MaintenanceWorkEvaluationItem. It contains five attributes: - itemID, - evaluateResult, - evaluateTime, - evaluateExecutor, and - taskID. A dashed line separates the attributes from the bottom of the class box. Below the diagram is the text M.3164(20)\_F19. + +**Figure 19 – Information model related to MaintenanceWorkEvaluationItem** + +##### 6.8.2.2.1 Definition + +This management entity describes basic information about evaluating maintenance work. The use made of individual attributes and notification is detailed below: + +- evaluateResult: Represents results about evaluation of maintenance work; +- taskID: Represents task objects to be evaluated. + +An attribute value change notification shall be emitted when the value of the itemID, the evaluateResult or the taskID is changed. + +##### 6.8.2.2.2 Attributes + +Table 49 describes the attribute properties related to MaintenanceWorkEvaluationItem: + +**Table 49** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|------------------|-------------------|----------------|-----------------|---------------------|----------------| +| itemID | M | M | – | – | M | +| evaluateResult | M | M | M | O | M | +| evaluateTime | M | M | M | O | M | +| evaluateExecutor | M | M | M | O | M | +| taskID | O | M | M | O | – | + +Table 50 shows the specific description of the attributes related to MaintenanceWorkEvaluationItem: + +**Table 50** + +| Attribute name | Type | Explanation | +|------------------|--------|----------------------------------------------------------------------------------------------------------------------------| +| itemID | String | Unique identifier, Maintenance work evaluation item | +| evaluateResult | String | Result of evaluation, expressed in stars | +| evaluateTime | Date | Time of evaluation | +| evaluateExecutor | String | Personnel ID, robot number, etc. for evaluation | +| taskID | String | Corresponding activity identification for evaluation, can be patrol, overhaul, troubleshooting, or service activation task | + +##### 6.8.2.2.3 Notifications + +Table 51 shows the specific description of notifications related to MaintenanceWorkEvaluationItem: + +**Table 51** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +## 6.9 Smart maintenance assistant toolkit management information model + +### 6.9.1 Relationship class diagram between object classes + +The relationship class diagram between object classes related to management of smart maintenance assistant toolkit (SMAT) is shown in Figure 20. + +![UML class diagram showing relationships between SmartMaintenanceAssistToolkitInfo, SmartApplication, SmartDevice, MaintenanceLog, and MaintenanceRecord. SmartMaintenanceAssistToolkitInfo (1) contains (n) SmartDevice via a composition relationship named 'names'. SmartApplication (n) and SmartDevice (n) have a many-to-many association. SmartDevice (1) contains (1) MaintenanceLog via a composition relationship named 'MaintenanceLog'. MaintenanceLog (1) contains (n) MaintenanceRecord via a composition relationship named 'names'. All classes are labeled as <>.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +``` + +classDiagram + class SmartMaintenanceAssistToolkitInfo { + <> + } + class SmartApplication { + <> + } + class SmartDevice { + <> + } + class MaintenanceLog { + <> + } + class MaintenanceRecord { + <> + } + SmartMaintenanceAssistToolkitInfo "1" *-- "n" SmartDevice : names + SmartApplication "n" -- "n" SmartDevice : +SmartApplication + SmartDevice "1" *-- "1" MaintenanceLog : +MaintenanceLog + MaintenanceLog "1" *-- "n" MaintenanceRecord : names + +``` + +M.3164(20)\_F20 + +UML class diagram showing relationships between SmartMaintenanceAssistToolkitInfo, SmartApplication, SmartDevice, MaintenanceLog, and MaintenanceRecord. SmartMaintenanceAssistToolkitInfo (1) contains (n) SmartDevice via a composition relationship named 'names'. SmartApplication (n) and SmartDevice (n) have a many-to-many association. SmartDevice (1) contains (1) MaintenanceLog via a composition relationship named 'MaintenanceLog'. MaintenanceLog (1) contains (n) MaintenanceRecord via a composition relationship named 'names'. All classes are labeled as <>. + +**Figure 20 – Relationship class diagram between the object classes related to management of SMAT** + +In Figure 20, the information object classes related to management of SMAT include SmartDevice, SmartApplication, MaintenanceLog and MaintenanceRecord. Multiple smart applications are installed on smart devices. Each smart device is associated with a maintenance log. Each time smart device is maintained, one or more records are added to the log. Therefore, SmartDevice and SmartApplication are many-to-many and one-way association relationships, and SmartDevice and MaintenanceLog are one-to-one and one-way association relationship. MaintenanceLog and MaintenanceRecord are one-to-many contain relationships. + +### 6.9.2 Object class information model and attribute description + +#### 6.9.2.1 Information object class related to smart maintenance assistant toolkit management (SmartMaintenanceAssistToolkitInfo) + +##### 6.9.2.1.1 Definition + +The *SmartMaintenanceAssistToolkitInfo* management entity describes basic information related to the top-level class about SMAT management. + +##### 6.9.2.1.2 Attributes + +Table 52 describes the attribute properties related to *SmartMaintenanceAssistToolkitInfo*: + +**Table 52** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| smartMATInfoID | M | M | – | – | M | +| deviceSet | M | M | M | O | M | + +Table 53 shows the specific description of the attributes related to SmartMaintenanceAssistToolkitInfo: + +**Table 53** + +| Attribute name | Type | Explanation | +|----------------|---------------|----------------------------------------------------------------| +| smartMATInfoID | String | Unique identifier related to SmartMaintenanceAssistToolkitInfo | +| deviceSet | SET OF String | Smart device set contained in SMAT | + +##### 6.9.2.1.3 Notifications + +Table 54 shows the specific description of notifications related to SmartMaintenanceAssistToolkitInfo: + +**Table 54** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.9.2.2 Information object class related to smart devices (SmartDevice) + +The information model related to SmartDevice is shown in Figure 21. + +![UML class diagram for SmartDevice information object class. The class box is titled '<> SmartDevice' and lists attributes: deviceID, devType, devName, devModele, devAddress, devSerialnum, devStorage, systemVersion, currentStatus, logID, and applicationSet. A dashed line separates the attributes from the bottom of the class box. Below the diagram is the text 'M.3164(20)_F21'.](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) + +``` + +classDiagram + class SmartDevice { + <> + - deviceID + - devType + - devName + - devModele + - devAddress + - devSerialnum + - devStorage + - systemVersion + - currentStatus + - logID + - applicationSet + } + +``` + +M.3164(20)\_F21 + +UML class diagram for SmartDevice information object class. The class box is titled '<> SmartDevice' and lists attributes: deviceID, devType, devName, devModele, devAddress, devSerialnum, devStorage, systemVersion, currentStatus, logID, and applicationSet. A dashed line separates the attributes from the bottom of the class box. Below the diagram is the text 'M.3164(20)\_F21'. + +**Figure 21 – Information model related to SmartDevice** + +##### 6.9.2.2.1 Definition + +This managed entity describes basic information related to smart devices. + +An attribute value change notification shall be emitted when the value of the deviceID, the devType, the devName, the devModele, the devAddress, the devSerialnum, the systemVersion, the currentStatus, the logID or applicationSet is changed. + +##### 6.9.2.2.2 Attributes + +Table 55 describes the attribute properties related to SmartDevice: + +**Table 55** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-----------------------|--------------------------|-----------------------|------------------------|----------------------------|-----------------------| +| deviceID | M | M | – | – | M | +| devType | M | M | M | O | M | +| devName | M | M | M | O | M | +| devModele | M | M | M | O | M | +| devAddress | M | M | M | O | M | +| devSerialnum | M | M | M | O | M | +| devStorage | M | M | M | O | M | +| systemVersion | M | M | M | O | M | +| currentStatus | M | M | M | O | M | +| logID | M | M | M | O | M | +| applicationSet | M | M | M | O | M | + +Table 56 shows the specific description of the attributes related to SmartDevice: + +**Table 56** + +| Attribute name | Type | Explanation | +|-----------------------|---------------|-----------------------------------------------| +| deviceID | String | Unique identifier, Device number | +| devType | ENUM | [handhold headwear else] | +| devName | String | Name of smart device | +| devModele | String | Modele of smart device | +| devAddress | String | Address of smart device, such as MAC | +| devSerialnum | String | Serial number of smart device | +| devStorage | String | Includes device RAM, ROM and storage capacity | +| systemVersion | ENUM | [android ios linux windowMobile else] | +| currentStatus | ENUM | [used unused] | +| logID | String | Maintenance log ID of smart device | +| applicationSet | SET OF String | Application set in smart device | + +##### 6.9.2.2.3 Notifications + +Table 57 shows the specific description of notifications related to SmartDevice: + +**Table 57** + +| Name | Qualifier | Description | +|----------------------|------------------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.9.2.3 Information object class related to smart application (SmartApplication) + +The information model related to SmartApplication is shown in Figure 22. + +![UML class diagram for SmartApplication. The class name is SmartApplication, which inherits from InformationObjectClass. The attributes listed are applicationID, appType, versionNum, operatingSystem, and downloadLink.](f57c7b37d7a05a99618104f390089f03_img.jpg) + +``` + +classDiagram + class SmartApplication { + - applicationID + - appType + - versionNum + - operatingSystem + - downloadLink + } + SmartApplication <> + +``` + +UML class diagram for SmartApplication. The class name is SmartApplication, which inherits from InformationObjectClass. The attributes listed are applicationID, appType, versionNum, operatingSystem, and downloadLink. + +M.3164(20)\_F22 + +**Figure 22 – Information model related to SmartApplication** + +##### 6.9.2.3.1 Definition + +This managed entity describes basic information related to smart application. + +An attribute value change notification shall be emitted when the value of the applicationID, the appType, the versionNum, the operatingSystem or the downloadLink is changed. + +##### 6.9.2.3.2 Attributes + +Table 58 describes the attribute properties related to SmartApplication: + +**Table 58** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-----------------|-------------------|----------------|-----------------|---------------------|----------------| +| applicationID | M | M | – | – | M | +| appType | M | M | M | O | M | +| versionNum | M | M | M | O | M | +| operatingSystem | M | M | M | O | M | +| downloadLink | M | M | M | O | M | + +Table 59 shows the specific description of the attributes related to SmartApplication: + +**Table 59** + +| Attribute Name | Type | Explanation | +|-----------------|--------|-----------------------------------------------| +| applicationID | String | Unique identifier, Application number | +| appType | ENUM | [handhold headwear else] | +| versionNum | String | Major version number | +| operatingSystem | ENUM | [android ios linux windowMobile else] | +| downloadLink | String | Download link address of installation package | + +##### 6.9.2.3.3 Notifications + +Table 60 shows the specific description of notifications related to SmartApplication: + +**Table 60** + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.9.2.4 Information object class related to maintenance log of smart devices (MaintenanceLog) + +The information model related to MaintenanceLog is shown in Figure 23. + +![UML Class Diagram for MaintenanceLog](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) + +``` + +classDiagram + class MaintenanceLog { + - logID + - recordList + } + +``` + +The diagram shows a class box for 'MaintenanceLog' under the stereotype '<>'. It contains two private attributes: 'logID' and 'recordList'. Below the attributes is a dashed line. The diagram is labeled 'M.3164(20)\_F23' at the bottom right. + +UML Class Diagram for MaintenanceLog + +Figure 23 – Information model related to MaintenanceLog + +##### 6.9.2.4.1 Definition + +This managed entity describes information related to the log for maintaining smart devices. The use made of individual attributes and notification is detailed below: + +- recordList: Represents items in log. + +An attribute value change notification shall be emitted when the value of the logID or the recordList is changed. + +##### 6.9.2.4.2 Attributes + +Table 61 describes the attribute properties related to MaintenanceLog: + +Table 61 + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| logID | M | M | – | – | M | +| recordList | M | M | M | O | M | + +Table 62 shows the specific description of the attributes related to MaintenanceLog: + +Table 62 + +| Attribute name | Type | Explanation | +|----------------|--------------------|----------------------------------------------| +| logID | String | Unique identifier, Log of maintenance number | +| recordList | SEQUENCE OF String | List of records | + +##### 6.9.2.4.3 Notifications + +Table 63 shows the specific description of notifications related to MaintenanceLog: + +Table 63 + +| Name | Qualifier | Description | +|----------------------|-----------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +#### 6.9.2.5 Information object class related to maintenance record of smart devices (MaintenanceRecord) + +The information model related to MaintenanceRecord is shown in Figure 24. + +![UML class diagram for MaintenanceRecord. The class name is 'MaintenanceRecord' with the stereotype '<>'. It lists four attributes: - recordID, - recordInfo, - recordTime, and - recordExecutor. A dashed line separates the attributes from the rest of the class box. Below the diagram is the text 'M.3164(20)_F24'.](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) + +UML class diagram for MaintenanceRecord. The class name is 'MaintenanceRecord' with the stereotype '<>'. It lists four attributes: - recordID, - recordInfo, - recordTime, and - recordExecutor. A dashed line separates the attributes from the rest of the class box. Below the diagram is the text 'M.3164(20)\_F24'. + +Figure 24 – Information model related to MaintenanceRecord + +##### 6.9.2.5.1 Definition + +This managed entity describes information about the record for maintaining smart devices. The use made of individual attributes and notification is detailed below: + +- recordInfo: Represents specific record information. + +An attribute value change notification shall be emitted when the value of the recordID or the recordInfo is changed. + +##### 6.9.2.5.2 Attributes + +Table 64 describes the attribute properties related to MaintenanceRecord: + +Table 64 + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| recordID | M | M | – | – | M | +| recordInfo | M | M | M | O | M | +| recordTime | O | M | M | O | – | +| recordExecutor | O | M | M | O | – | + +Table 65 shows the specific description of the attributes related to MaintenanceRecord: + +Table 65 + +| Attribute name | Type | Explanation | +|----------------|--------|------------------------------------------------| +| recordID | String | Unique identifier, Maintenance record number | +| recordInfo | String | Recorded specific information | +| recordTime | Date | Time of record | +| recordExecutor | String | Personnel ID, robot number, etc. for recording | + +##### 6.9.2.5.3 Notifications + +Table 66 shows the specific description of notifications related to MaintenanceRecord: + +**Table 66** + +| Name | Qualifier | Description | +|----------------------|------------------|-------------------------------| +| objectCreation | M | create object | +| objectDeletion | M | delete object | +| attributeValueChange | O | change the value of attribute | + +# Appendix I + +## Examples of instances for information object classes + +(This appendix does not form an integral part of this Recommendation.) + +According to the definition of objects in each module in clause 6, examples of instances for each information object class are provided in the following clauses. + +### I.1 Overview of all the instances + +Figure I.1 gives an overview of the relationships among all the example instances. + +![Relationship diagram for all the example instances. The diagram shows various information object classes and their relationships. A central yellow box labeled '<> ResourceInfo' is connected to several other classes. On the left, 'MaintenanceWorkEvaluationItem' (itemID:MWE-2001110001) is connected to 'MaintenanceWorkInfo' (maintenanceWorkInfoID:MWE-200111) and 'OnsitePatrolPoint' (pointID:QH-0001). 'OnsitePatrolPoint' is connected to 'OnsitePatrolRecord' (recordID:OPT-2001110001-RD-0001). 'OnsitePatrolRecord' is connected to 'OnsitePatrolTask' (taskID:OP-200111-0001). 'OnsitePatrolTask' is connected to 'OnsitePatrolInfo' (patrolInfoID:OP-200111) and 'ResourceInfo'. 'OnsitePatrolInfo' is connected to 'OnsiteOverhaulInfo' (overhaulInfoID:OO-200111) and 'ResourceInfo'. 'OnsiteOverhaulInfo' is connected to 'OnsiteOverhaulTask' (taskID:OO-200111-0001). 'OnsiteOverhaulTask' is connected to 'ResourceInfo'. 'ResourceInfo' is connected to 'OnsiteTroubleshootingInfo' (troubleshootingInfoID:OT-200111) and 'ServiceActivationInfo' (serviceActivInfoID:SA-200111). 'OnsiteTroubleshootingInfo' is connected to 'TroubleType' (troubleTypeID:Electricity-failure-001). 'TroubleType' is connected to 'Expert' (expertID:ex001) and 'MaintenanceKnowledgeBaseInfo' (maintenanceWorkEvalInfoID:MKB-200111). 'MaintenanceKnowledgeBaseInfo' is connected to 'MaintenanceKnowledgeBaseItem' (itemID:MKB-2001110001). 'ServiceActivationInfo' is connected to 'ServiceActivationTask' (taskID:SA-200111-0001). 'ServiceActivationTask' is connected to 'ServiceActivationRecord' (recordID:SA-2001110001-RD-0001). 'ServiceActivationRecord' is connected to 'SmartApplication' (applicationID:SA-SG-0001). 'SmartApplication' is connected to 'SmartDevice' (deviceID:SD-SG-0001). 'SmartDevice' is connected to 'MaintenanceLog' (logID:ML-200111-0001). 'MaintenanceLog' is connected to 'MaintenanceRecord' (recordID:MR-2001110001-RD-0001). 'SmartMaintenanceAssistToolKitInfo' (smartMATInfoID:SMAT-200111) is connected to 'SmartDevice'.](8c880d6b715587bd710a9ba8414469b1_img.jpg) + +Relationship diagram for all the example instances. The diagram shows various information object classes and their relationships. A central yellow box labeled '<> ResourceInfo' is connected to several other classes. On the left, 'MaintenanceWorkEvaluationItem' (itemID:MWE-2001110001) is connected to 'MaintenanceWorkInfo' (maintenanceWorkInfoID:MWE-200111) and 'OnsitePatrolPoint' (pointID:QH-0001). 'OnsitePatrolPoint' is connected to 'OnsitePatrolRecord' (recordID:OPT-2001110001-RD-0001). 'OnsitePatrolRecord' is connected to 'OnsitePatrolTask' (taskID:OP-200111-0001). 'OnsitePatrolTask' is connected to 'OnsitePatrolInfo' (patrolInfoID:OP-200111) and 'ResourceInfo'. 'OnsitePatrolInfo' is connected to 'OnsiteOverhaulInfo' (overhaulInfoID:OO-200111) and 'ResourceInfo'. 'OnsiteOverhaulInfo' is connected to 'OnsiteOverhaulTask' (taskID:OO-200111-0001). 'OnsiteOverhaulTask' is connected to 'ResourceInfo'. 'ResourceInfo' is connected to 'OnsiteTroubleshootingInfo' (troubleshootingInfoID:OT-200111) and 'ServiceActivationInfo' (serviceActivInfoID:SA-200111). 'OnsiteTroubleshootingInfo' is connected to 'TroubleType' (troubleTypeID:Electricity-failure-001). 'TroubleType' is connected to 'Expert' (expertID:ex001) and 'MaintenanceKnowledgeBaseInfo' (maintenanceWorkEvalInfoID:MKB-200111). 'MaintenanceKnowledgeBaseInfo' is connected to 'MaintenanceKnowledgeBaseItem' (itemID:MKB-2001110001). 'ServiceActivationInfo' is connected to 'ServiceActivationTask' (taskID:SA-200111-0001). 'ServiceActivationTask' is connected to 'ServiceActivationRecord' (recordID:SA-2001110001-RD-0001). 'ServiceActivationRecord' is connected to 'SmartApplication' (applicationID:SA-SG-0001). 'SmartApplication' is connected to 'SmartDevice' (deviceID:SD-SG-0001). 'SmartDevice' is connected to 'MaintenanceLog' (logID:ML-200111-0001). 'MaintenanceLog' is connected to 'MaintenanceRecord' (recordID:MR-2001110001-RD-0001). 'SmartMaintenanceAssistToolKitInfo' (smartMATInfoID:SMAT-200111) is connected to 'SmartDevice'. + +Figure I.1 – Relationship diagram for all the example instances + +### I.2 Examples related to on-site patrol information model + +#### I.2.1 OnsitePatrolInfo + +Table I.1 shows an instance of OnsitePatrolInfo: + +Table I.1 + +| OnsitePatrolInfo | | +|------------------|------------------------------------| +| Attribute name | Attribute value | +| patrolInfoID | OP-200111 | +| patrolTaskList | [OPT-200111-0001, OPT-200111-0002] | + +#### I.2.2 OnsitePatrolTask + +Table I.2 shows an instance of OnsitePatrolTask: + +**Table I.2** + +| OnsitePatrolTask | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| taskID | OPT-200111-0001 | +| taskType | routine | +| taskStatus | finished | +| patrolExecutor | czl0001 | +| startTime | 2020-01-11 09:17 | +| endTime | 2020-01-11 09:30 | +| pointSequence | [Qionghai Station, Wenchang Station] | +| recordList | [OPT-200111-0001-RD-0001, OPT-200111-0001-RD-0002] | +| orderID | TQX-HN-SY-2001110001 | +| resourceSet | {Intermediate adjustment 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2), intermediate adjustment battery room at Wenchang station (rack: 4-A-05, network element code: ATC Communication power cabinet)} | + +#### I.2.3 OnsitePatrolPoint + +Table I.3 shows an instance of OnsitePatrolPoint: + +**Table I.3** + +| OnsitePatrolPoint | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| pointID | Qh-0001 | +| pointType | device | +| patrolDes | Patrol the power status of the equipment in the 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2) to ensure the normal link between Qionghai Station and Wenchang Station | +| coordinates | {19.2273, 110.4690, 13.0000, GCS_CN_2000} | +| pointLabel | The QR code of rack (3-B-06) | + +#### I.2.4 OnsitePatrolRecord + +Table I.4 shows an instance of OnsitePatrolRecord: + +**Table I.4** + +| OnsitePatrolRecord | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| recordID | OPT-200111-0001-RD-0001 | +| recordExecutor | czl0001 | +| recordTime | 2020-01-11 09:20 | +| status | normal | +| recordInfo | Intermediate adjustment 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2): when the device is in operation and the power switch on the PIU power board is turn off, the voltage values viewed are within the allowed range | +| pointID | Qh-0001 | + +### **I.3 Examples related to on-site overhaul information model** + +#### **I.3.1 OnsiteOverhaulInfo** + +Table I.5 shows an instance of OnsiteOverhaulInfo: + +**Table I.5** + +| OnsiteOverhaulInfo | | +|---------------------------|------------------------------------| +| Attribute name | Attribute value | +| overhaulInfoID | OO-200111 | +| overhaulTaskList | [OOT-200111-0001, OOT-200111-0002] | + +#### **I.3.2 OnsiteOverhaulTask** + +Table I.6 shows an instance of OnsiteOverhaulTask: + +**Table I.6** + +| OnsiteOverhaulTask | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| taskID | OOT-200111-0001 | +| overhaulExecutor | czl0001 | +| overhaulStatus | finished | +| overhaulDes | Overhaul the abnormal power state of the equipment in the intermediate adjustment 1705 computer room at Qionghai Station (rack: 3-B-06, network element code: intermediate adjustment 2) to restore the normal link between Qionghai Station and Wenchang Station | +| timeInfo | {2020-01-11 10:00, 2020-01-11 10:30} | +| orderID | TQX-HN-SY-2001110002 | +| resourceSet | {Intermediate adjustment 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2), intermediate adjustment battery room at Wenchang station (rack: 4-A-05, network element code: ATC Communication power cabinet)} | + +### I.4 Examples related to on-site troubleshooting information model + +#### I.4.1 OnsiteTroubleshootingInfo + +Table I.7 shows an instance of OnsiteTroubleshootingInfo: + +**Table I.7** + +| OnsiteTroubleshootingInfo | | +|----------------------------------|------------------------------------| +| Attribute name | Attribute value | +| troubleshootingInfoID | OT-200111 | +| troubleshootingTaskList | [OTT-200111-0001, OTT-200111-0002] | + +#### I.4.2 OnsiteTroubleshootingTask + +Table I.8 shows an instance of OnsiteTroubleshootingTask: + +**Table I.8** + +| OnsiteTroubleshootingTask | | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| taskID | OTT-200111-0001 | +| occurTime | 2020-01-11 10:00 | +| status | finished | +| troubleDes | Intermediate adjustment 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2): Power is disconnected and business is interrupted | +| confirmInfo | {lxm, 2020-01-11 10:10} | +| maintenanceInfo | {czl0001, Disconnect the power switch to check the internal power supply equipment and cables, 2020-01-11 10:30} | +| troubleTypeID | electricity failure-001 | +| orderID | TQX-HN-SY-2001110003 | +| resourceSet | {Intermediate adjustment 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2), intermediate adjustment battery room at Wenchang station (rack: 4-A-05, network element code: ATC Communication power cabinet)} | + +#### I.4.3 TroubleType + +Table I.9 shows an instance of TroubleType: + +**Table I.9** + +| TroubleType | | +|-----------------------|----------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| troubleTypeID | Electricity-failure-001 | +| troubleLevel | common | +| troubleTypeDes | The power supply fuse is damaged | +| solution | Turn off the power, find out the reason for the fuse and replace with a new fuse | +| expertSet | {ex001, ex002} | + +#### **I.4.4 Expert** + +Table I.10 shows an instance of Expert: + +**Table I.10** + +| Expert | | +|-----------------------|-------------------------| +| Attribute name | Attribute value | +| expertID | ex001 | +| expertAddtionInfo | {Wang Gang, male, 1976} | +| expertGroup | OT group | +| expertDepartment | power supply department | +| email | Wanggang123@163.com | +| skillArea | power supply area | +| availableRate | 0.85 | + +### **I.5 Examples related to service activation information model** + +#### **I.5.1 ServiceActivationInfo** + +Table I.11 shows an instance of ServiceActivationInfo: + +**Table I.11** + +| ServiceActivationInfo | | +|------------------------------|------------------------------------| +| Attribute name | Attribute value | +| serviceActInfoID | SA-200111 | +| serviceActTaskList | [SAT-200111-0001, SAT-200111-0002] | + +#### **I.5.2 ServiceActivationTask** + +Table I.12 shows an instance of ServiceActivationTask: + +**Table I.12** + +| ServiceActivationTask | | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| taskID | SAT-200111-0001 | +| serviceActDes | unplug and insert fiber | +| executeInfo | {czl0001, 2020-01-11 10:30, finished} | +| recordList | [SAT-2001110001-RD-0001: Pull out the fiber jumper, SAT-2001110001-RD-0002: Insert fiber jumper] | +| orderID | TQX-HN-SY-2001110004 | +| resourceSet | {Intermediate adjustment 1705 computer room at Qionghai station (rack: 3-B-06, network element code: intermediate adjustment 2), intermediate adjustment battery room at Wenchang station (rack: 4-A-05, network element code: ATC Communication power cabinet)} | + +#### **I.5.3 ServiceActivationRecord** + +Table I.13 shows an instance of ServiceActivationRecord: + +**Table I.13** + +| ServiceActivationRecord | | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| recordID | SAT-2001110001-RD-0001 | +| recordInfo | Intermediate adjustment 1705 computer room at Qionghai Station (rack: 3-B-06, network element code: middle transfer 2): Unplug and insert the optical fiber of the relevant equipment | +| submitExecutor | czl0001 | +| submitTime | 2020-01-11 11:00 | + +### **I.6 Examples related to maintenance knowledge base information model** + +#### **I.6.1 MaintenanceKnowledgeBaseInfo** + +Table I.14 shows an instance of MaintenanceKnowledgeBaseInfo: + +**Table I.14** + +| MaintenanceKnowledgeBaseInfo | | +|-------------------------------------|--------------------------------------| +| Attribute name | Attribute value | +| maintenanceKnowledgeBaseInfoID | MKB-200111 | +| maintenanceKnowledgeBaseItemList | [MKBI-200111-0001, MKBI-200111-0002] | + +#### **I.6.2 MaintenanceKnowledgeBaseItem** + +Table I.15 shows an instance of MaintenanceKnowledgeBaseItem: + +**Table I.15** + +| MaintenanceKnowledgeBaseInfo | | +|-------------------------------------|-------------------------------------------------------------| +| Attribute name | Attribute value | +| itemID | MKBI-200111-0001 | +| knowledgeDes | This knowledge item is suitable for power failure detection | +| knowledgeType | troubleshoot | +| knowledgeStatus | checkedOK | +| submitInfo | {czl0001, 2020-01-11 10:25} | +| checkInfo | {zs00001, 2020-01-11 13:00} | + +### I.7 Examples related to maintenance work evaluation information model + +#### I.7.1 MaintenanceWorkEvaluationInfo + +Table I.16 shows an instance of MaintenanceWorkEvaluationInfo: + +**Table I.16** + +| MaintenanceWorkEvaluationInfo | | +|--------------------------------------|--------------------------------------| +| Attribute name | Attribute value | +| maintenanceWorkEvalInfoID | MWE-200111 | +| maintenanceWorkEvalItemList | [MWEI-200111-0001, MWEI-200111-0002] | + +#### I.7.2 MaintenanceWorkEvaluationItem + +Table I.17 shows an instance of MaintenanceWorkEvaluationItem: + +**Table I.17** + +| MaintenanceWorkEvaluationItem | | +|--------------------------------------|------------------------| +| Attribute name | Attribute value | +| itemID | MWEI-200111-0001 | +| evaluateResult | **** | +| evaluateTime | 2020-01-11 12:00 | +| evaluateExecutor | ls0001 | +| taskID | OPT-200111-0001 | + +## I.8 Examples related to smart maintenance assistant toolkit management information model + +#### I.8.1 SmartMaintenanceAssistToolkitInfo + +Table I.18 shows an instance of SmartMaintenanceAssistToolkitInfo: + +**Table I.18** + +| SmartMaintenanceAssistToolkitInfo | | +|------------------------------------------|--------------------------------------------------| +| Attribute name | Attribute value | +| smartMATInfoID | SMAT-200111 | +| deviceSet | {SD-SG-0001, SD-SG-0002, SD-SG-0003, SD-SG-0004} | + +#### **I.8.2 SmartDevice** + +Table I.19 shows an instance of SmartDevice: + +**Table I.19** + +| SmartDevice | | +|-----------------------|-----------------------------------------| +| Attribute name | Attribute value | +| deviceID | SD-SG-0001 | +| devType | headwear | +| devName | smart glasses | +| devModele | AR Smart Model | +| devAddress | MAC: 08:00:20:0A:8C:6D | +| devSerialNum | 074416Z31580093AE | +| devStorage | RAM:4GB ROM:32GB storage capability:32G | +| systemVersion | android | +| currentStatus | used | +| logID | ML-200111-0001 | +| applicationSet | {SA-SG-0001, SA-SG-0002} | + +#### **I.8.3 SmartApplication** + +Table I.20 shows an instance of SmartApplication: + +**Table I.20** + +| SmartApplication | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Attribute name | Attribute value | +| applicationID | SA-SG-0001 | +| appType | headwear | +| versionNum | 2.0 | +| operatingSystem | android | +| downloadLink | https://ai.baidu.com/easydl/lite?track=cp:ainsem pf:pc pp:easyDL pu:easyDL-tuxiang-tuozhan ci:kw:10001404 | + +### **I.8.4 MaintenanceLog** + +Table I.21 shows an instance of MaintenanceLog: + +**Table I.21** + +| MaintenanceLog | | +|-----------------------|-----------------------------------------------------| +| Attribute name | Attribute value | +| logID | ML-200111-0001 | +| recordList | [ML-200111-0001-RD-0001,
ML-200111-0001-RD-0002] | + +### **I.8.5 MaintenanceRecord** + +Table I.22 shows an instance of MaintenanceRecord: + +**Table I.22** + +| MaintenanceRecord | | +|--------------------------|-----------------------------------------------------------| +| Attribute name | Attribute value | +| recordID | ML-200111-0001-RD-0001 | +| recordInfo | Smart glasses take pictures of the device and upload them | +| recordTime | 2020-01-11 13:00 | +| recordExecutor | czl0001 | + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7260a08c79fad39d7f644f63f981a874b184b728 --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c897080ae2812e116e9adb32058916bb0b3f6f095c9780759dea9459f44edb7 +size 40543 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12c0d96d6933ba4eab79625e07c21d184244d77a --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9769deb6addec764220860fa27cedc54b6999fd95fd70eed5128580157cb4d39 +size 34541 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6ae3b774dc3641e3b857ee8d2cf1ff2f8c03445 --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f7deef509c7a2a12aa8a57e0dc5ace18ff08f02b88d20ab8e684d55c7fb7748 +size 38332 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6383c7552d1e0268a4282eaa514330d45dbe68d4 --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:472603e3ace3a30c1ba9821ac42e4b5edef938839fe0d218cb023c507c5c80af +size 46234 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ba921475177635f4ab37add2a3412205353367b --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d6cd2a59af625ea2b58227fd13e1c2c06527b8812fc72ecd9e2bb9082fbcd32 +size 6960 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..973f7890a062e11a7885744c7bcdaf01cb20a332 --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0373becf17c9b8e1cd67c43cf0263700a3e155a46e49ab701ba7142314bdb30 +size 33985 diff --git a/marked/M/T-REC-M.3164.1-202408-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e65809b637b00f8a4b738b885adbaf99cfbff0b --- /dev/null +++ b/marked/M/T-REC-M.3164.1-202408-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:709ede2387c0aa1e76dcc96e957c8972e959167dbcc5ba8338901e8daa558fe6 +size 24300 diff --git a/marked/M/T-REC-M.3164.2-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3164.2-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30d4bc9edd02d463a452fa930b82ff2dfd368c24 --- /dev/null +++ b/marked/M/T-REC-M.3164.2-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bdea22ddbf01b83f16dbc58bc0c9e4b409b0baae46bf6dede68381ee2f7df83 +size 7130 diff --git a/marked/M/T-REC-M.3164.2-202408-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/M/T-REC-M.3164.2-202408-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9792d2f086a1dd5b392965098a74f59b871920c2 --- /dev/null +++ b/marked/M/T-REC-M.3164.2-202408-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f219dcf7cd5972b4e2ea69b02ee4fb1509d2ccab3ec4e8364af6e8ca1a43d0d4 +size 70555 diff --git a/marked/M/T-REC-M.3164.2-202408-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3164.2-202408-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2f073f079150dc81646e1433e3c9843a948fbe4 --- /dev/null +++ b/marked/M/T-REC-M.3164.2-202408-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ce5364a87021daa09c6d8b6be188f6b97fdfb033d083babae5ac5289db5d58e +size 68320 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aba49900099f480d75d9f85d518b5e495514f50 --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa9942be58aebc32162799b94764791fff889d181183478d582a13ca39b05cf1 +size 73458 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9587337fc8619d9fcd220cf9539eb5cf6f75dbfe --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82cec5243524296ecdb52f6a0ee2763681648bc7885ccbee87b29396ad0b232a +size 72118 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec97750f20c2f7c05b1eeae5213c58bd1181aac7 --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81366214a0651a4539e4137e4d347ca0eb6b570619e49fe08dff14cd14f4661f +size 57402 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..984ff119334e43865febf1054c63889b10f1803b --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94fb034a1e2728d023571b1acc783dab5a425325612e217945ce7c84b8dda54e +size 43179 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edb195068afbc35ff8b8b746fb4afaa11e2bdb47 --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7080aea893e0107c60455a14c634b44416b8cff606288179b44227e9c7d8ec7 +size 73795 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c572a83938b27e70b4fc695c9d8bacf15b59b5ca --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41ebfc3c18d21944b22579cd155a85cdd0ce15e162a5b19804bff1c42e91534d +size 72158 diff --git a/marked/M/T-REC-M.3164.3-202510-I_PDF-E/raw.md b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..536929790cf0949ffb87e30cff1780127358990b --- /dev/null +++ b/marked/M/T-REC-M.3164.3-202510-I_PDF-E/raw.md @@ -0,0 +1,4124 @@ + + +# Recommendation**ITU-T M.3164.3 (10/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **Interface for on-site generic telecommunication smart maintenance – REST-based design** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +# **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3164.3 + +## Interface for on-site generic telecommunication smart maintenance – REST-based design + +## Summary + +Recommendation ITU-T M.3164.3 specifies the design phase of the interface specification for on-site generic telecommunication smart maintenance (TSM) at the protocol-specific level. It describes the interface specification guidelines using Representational State Transfer (REST) technology and also defines the interactive control information exchanged through this TSM interface in YAML Ain't Markup Language (YAML)/JavaScript Object Notation (JSON) format. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3164.3 | 2025-10-14 | 2 | 11.1002/1000/16465 | + +## Keywords + +On-site generic telecommunication smart maintenance, REST-based design, smart maintenance assistant toolkit, telecommunication smart maintenance system. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview..... | 3 | +| 7 Interface design..... | 4 | +| 7.1 Overview ..... | 4 | +| 7.2 REST-based entity definitions..... | 4 | +| 7.3 Definitions of the REST-based interface operations provided by SMAT..... | 15 | +| 7.4 Definitions of the REST-based interface operations provided by TSMS ..... | 27 | +| 7.5 Definitions of the attributes and data types ..... | 37 | +| Annex A – Formal YAML schema definitions for the on-site TSM interface between SMAT and TSMS ..... | 43 | +| A.1 YAML schema definition for information object classes and common data types ..... | 43 | +| A.2 YAML schema definition for interface operations provided by SMAT ..... | 62 | +| A.3 YAML schema definition for interface operations provided by TSMS..... | 73 | +| Bibliography..... | 85 | + + + +# Recommendation ITU-T M.3164.3 + +## Interface for on-site generic telecommunication smart maintenance – REST-based design + +# 1 Scope + +This Recommendation provides the representational state transfer (REST) based interface design for on-site generic telecommunication smart maintenance (TSM). It describes the interface specification guidelines for the on-site generic TSM at a REST technology-specific level (protocol-specific). It also provides the interactive control information exchanged through this TSM interface using the YAML Ain't Markup Language (YAML)/JavaScript Object Notation (JSON) language. + +The maintenance information and interactions provided in this Recommendation follows [ITU-T M.3020] management interface specification methodology in the interface design phase. It follows the protocol-neutral requirements and analysis provided in Recommendations [ITU-T M.3164.1] and [ITU-T M.3164.2], respectively. The development is carried out in a protocol-specific manner, representing a mapping from the protocol-neutral information model to this REST-based, protocol-specific interface design. + +This Recommendation applies to the design, development, inter-connection and inter-operation of on-site generic telecommunication smart maintenance. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2023), *Management interface specification methodology*. +- [ITU-T M.3164] Recommendation ITU-T M.3164 (2020), *Generic information model for on-site telecommunication smart maintenance*. +- [ITU-T M.3164.1] Recommendation ITU-T M.3164.1 (2024), *Interface for on-site generic telecommunication smart maintenance – Protocol neutral requirements*. +- [ITU-T M.3164.2] Recommendation ITU-T M.3164.2 (2024), *Interface for on-site generic telecommunication smart maintenance - Protocol neutral analysis*. +- [ITU-T Q.819] Recommendation ITU-T Q.819 (2022), *REST-based management services*. +- [ITU-T X.785] Recommendation ITU-T X.785 (2021), *Guidelines for defining REST-based managed objects and management interfaces*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 information object class** [ITU-T M.3020]: Describes the information that can be passed/used in management interfaces and is modelled using the stereotype "Class" in the UML meta-model. + +**3.1.2 on-site overhaul** [b-ITU-T M.3040]: A kind of on-demand preventive maintenance performed at a facility site in the condition of natural disasters or major events. + +**3.1.3 on-site patrol** [b-ITU-T M.3040]: A kind of routine preventive maintenance periodically performed at a facility site. + +**3.1.4 on-site troubleshooting** [b-ITU-T M.3040]: A kind of corrective maintenance performed at a facility site when the quality of equipment degrades. + +**3.1.5 telecommunication smart maintenance** [b-ITU-T M.3040]: The maintenance carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system, which can provide strong human-computer interaction capabilities and online guidance to personnels, to achieve higher efficiency and precision of actions. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------------| +| API | Application Programming Interface | +| CRUD | Create, Read, Update and Delete | +| FUN | Function | +| HTTP | Hypertext Transfer Protocol | +| ID | Identifier | +| IOC | Information Object Class | +| IP | Internet Protocol | +| JSON | JavaScript Object Notation | +| REST | Representational State Transfer | +| SMAT | Smart Maintenance Assistant Toolkit | +| TE | Task Evaluation | +| TSM | Telecommunication Smart Maintenance | +| TSMS | Telecommunication Smart Maintenance System | +| UML | Unified Modelling Language | +| YAML | YAML Ain't Markup Language | + +# **5 Conventions** + +A few conventions are followed in this Recommendation to make the reader aware of the purpose of the text. Two qualifiers are used, which are: + +**M**, which stands for mandatory and means that the attribute or field is mandatory for an operation or notification. + +**O**, which stands for optional and means that the attribute or field is optional for an operation or notification. + +Examples of YAML and JSON are included in this Recommendation and normative YAML or JSON schema examples specifying the data types, base classes and other modelling constructs of the framework are included in Annex A. The JSON/YAML schemas are written in a 10-point courier typeface: + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------| +| A JSON schema example | {
"title": "root",
"items": {
"title": "array item"
}
} | +| A YAML schema example | SomeType:
type: object
properties:
attr1:
type: string
attr2:
type: string
enum:
- e1
- e2 | + +# 6 Overview + +[ITU-T M.3020] defines the unified management interface specification methodology, including three phases, which are requirements phase, analysis phase and design phase. The requirements and analysis phases can be protocol neutral, which are independent from the implementation technologies. The design phase is protocol specific and can be mapped to multiple implementation technologies. This Recommendation follows the management interface specification methodology from [ITU-T M.3020] to define the protocol-specific design phase specification of this interface. + +[ITU-T M.3164.1] defines the interface position and the protocol neutral requirements of interface I1 (between smart maintenance assistant toolkit (SMAT) and telecommunication smart maintenance system (TSMS)) for on-site telecommunication smart maintenance (TSM). Based on the requirements information, [ITU-T M.3164.2] provides the protocol neutral analysis specification of the interface, which supports the main functions of on-site TSM. + +[ITU-T M.3164] provides the general information model for TSM, and the information object classes (IOCs) will be reused in the interface interactions in this Recommendation. + +[b-OAI-OAS3] provides a standard, programming language-agnostic interface description for hypertext transfer protocol (HTTP) application programming interfaces (APIs), which is followed by the JSON/YAML schema examples in this Recommendation. + +Following the guidelines and templates from [ITU-T M.3020], along with the protocol neutral interface requirements and analysis provided in [ITU-T M.3164.1] and [ITU-T M.3164.2], as well as the general entities information models defined in [ITU-T M.3164], this Recommendation defines the REST-based design specification for the TSM interface I1. It adheres to the REST-based management framework guidelines specified in [ITU-T X.785] and [ITU-T Q.819]. + +# 7 Interface design + +## 7.1 Overview + +[ITU-T X.785] sets out a framework for defining how interfaces supported by management systems and network elements should be modelled using JSON/YAML schemas, and including the generic accessing methods for managed objects, guidelines for defining accessing methods for specific resources, the information modelling guidelines for REST-based managed objects and management interfaces, and some common data type definitions. These guidelines will be followed by this Recommendation, and the common managed objects and data type will be reused. + +The interface design for I1 between the TSMS and the SMAT are divided into two parts, one part is the entity definitions that are involved in the interface, the other part is the interface interaction definitions for the operations across this interface. For the first part, some of generic entities from [ITU-T M.3164] will be reused and mapped to REST-based resource and data types; for the second part, the interface operations will be mapped to REST-based interface methods. + +## 7.2 REST-based entity definitions + +This clause provides the REST definitions of the IOCs that are used in this Recommendation. The basic create, read, update and delete (CRUD) operations for the defined IOCs will reuse the common object accessing methods in clause A.2 in [ITU-T X.785], or clause 10 in [ITU-T Q.819]. + +### 7.2.1 On-site patrol related entities definitions + +Clause 6.3 of [ITU-T M.3164] provides the protocol neutral information model for on-site patrol related IOCs, including OnsitePatrolInfo, OnsitePatrolTask, OnsitePatrolPoint and OnsitePatrolRecord. The inheritance diagram of the above IOCs can be found in Figure 1. The containment and association relationship for them can be found in Figure 3 of [ITU-T M.3164]. + +![Inheritance diagram showing ManagedObject (ITU-T X.785) as the base class for OnsitePatrolInfo, OnsitePatrolTask, OnsitePatrolPoint, and OnsitePatrolRecord.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +``` +classDiagram + class ManagedObject { + <> + ManagedObject (ITU-T X.785) + -objectClass + -objectInstance + -creationSource + } + class OnsitePatrolInfo { + <> + OnsitePatrolInfo + -patrolInfoID + -patrolTaskList + } + class OnsitePatrolTask { + <> + OnsitePatrolTask + -taskID + -taskType + -taskStatus + -patrolExecutor + -startTime + -endTime + -pointSequence + -recordList + -orderID + -resourceSet + } + class OnsitePatrolPoint { + <> + OnsitePatrolPoint + -pointID + -pointType + -patrolDes + -coordinates + -pointLabel + } + class OnsitePatrolRecord { + <> + OnsitePatrolRecord + -recordID + -recordExecutor + -recordTime + -status + -recordInfo + -pointID + } + ManagedObject <|-- OnsitePatrolInfo + ManagedObject <|-- OnsitePatrolTask + ManagedObject <|-- OnsitePatrolPoint + ManagedObject <|-- OnsitePatrolRecord +``` + +The diagram illustrates the inheritance hierarchy for on-site patrol related IOCs. At the top is the base class **ManagedObject (ITU-T X.785)**, which defines attributes: `-objectClass`, `-objectInstance`, and `-creationSource`. Below it, four specific IOCs inherit from **ManagedObject**: **OnsitePatrolInfo**, **OnsitePatrolTask**, **OnsitePatrolPoint**, and **OnsitePatrolRecord**. Each IOC box lists its specific attributes: **OnsitePatrolInfo** has `-patrolInfoID` and `-patrolTaskList`; **OnsitePatrolTask** has `-taskID`, `-taskType`, `-taskStatus`, `-patrolExecutor`, `-startTime`, `-endTime`, `-pointSequence`, `-recordList`, `-orderID`, and `-resourceSet`; **OnsitePatrolPoint** has `-pointID`, `-pointType`, `-patrolDes`, `-coordinates`, and `-pointLabel`; and **OnsitePatrolRecord** has `-recordID`, `-recordExecutor`, `-recordTime`, `-status`, `-recordInfo`, and `-pointID`. + +Inheritance diagram showing ManagedObject (ITU-T X.785) as the base class for OnsitePatrolInfo, OnsitePatrolTask, OnsitePatrolPoint, and OnsitePatrolRecord. + +M.3164.3(25) + +**Figure 1 – Inheritance diagram of the on-site patrol related IOCs** + +The above four IOCs are mapped to JSON/YAML data types in the REST-based interface design, and the IOC **ManagedObject** from [ITU-T X.785] will be the base class for all of them. + +Their YAML definitions are given in Tables 1 to 4. + +**Table 1 – YAML schema definition of OnsitePatrolInfo** + +``` +OnsitePatrolInfo_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + patrolInfoID: + type: string + patrolTaskList: + $ref: '#/components/schemas/PatrolTaskListType' + required: + - patrolInfoID + - patrolTaskList +``` + +**Table 2 – YAML schema definition of OnsitePatrolTask** + +``` +OnsitePatrolTask_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + taskType: + type: string + enum: + - routine + - temporary + - else + taskStatus: + type: string + enum: + - notready + - ready + - doing + - finished + patrolExecutor: + type: string + startTime: + type: string + format: date-time + endTime: +``` + +``` +type: string +format: date-time +pointSequence: + $ref: '#/components/schemas/PointSequenceListType' +recordList: + $ref: '#/components/schemas/RecordListType' +orderID: + type: string +resourceSet: + $ref: '#/components/schemas/ResourceSetType' +required: +- taskID +- taskType +- taskStatus +- patrolExecutor +- pointSequence +- recordList +- orderID +- resourceSet +``` + +**Table 3 – YAML schema definition of OnsitePatrolPoint** + +``` +OnsitePatrolPoint_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + pointID: + type: string + pointType: + type: string + enum: + - building + - device + - else + patrolDes: + type: string + coordinates: + $ref: '#/components/schemas/CoordinateSetType' + pointLabel: + type: string + required: + - pointID + - pointType + - patrolDes + - coordinates + - pointLabel +``` + +**Table 4 – YAML schema definition of OnsitePatrolRecord** + +``` +OnsitePatrolRecord_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + recordID: + type: string + recordExecutor: + type: string + recordTime: + type: string + format: date-time + status: +``` + +``` + +type: string +enum: + - normal + - abnormal + - notCheck +recordInfo: + type: string +pointID: + type: string +required: + - recordID + - status + - recordInfo + - pointID + +``` + +### 7.2.2 On-site overhaul related entities definitions + +Clause 6.4 of [ITU-T M.3164] provides the protocol neutral information model for on-site overhaul related IOCs, including OnsiteOverhaulInfo, OnsiteOverhaulTask. The inheritance diagram of the above IOCs can be found in Figure 2. The containment and association relationship for them can be found in Figure 7 of [ITU-T M.3164]. + +![Inheritance diagram showing ManagedObject as the base class for OnsiteOverhaulInfo and OnsiteOverhaulTask. ManagedObject has attributes: -objectClass, -objectInstance, -creationSource. OnsiteOverhaulInfo has attributes: -overhaulInfoID, -overhaulTaskList. OnsiteOverhaulTask has attributes: -taskID, -overhaulExecutor, -overhaulStatus, -overhaulDes, -timeInfo, -orderID, -resourceSet.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +classDiagram + class ManagedObject { + <> + -objectClass + -objectInstance + -creationSource + } + class OnsiteOverhaulInfo { + <> + -overhaulInfoID + -overhaulTaskList + } + class OnsiteOverhaulTask { + <> + -taskID + -overhaulExecutor + -overhaulStatus + -overhaulDes + -timeInfo + -orderID + -resourceSet + } + ManagedObject <|-- OnsiteOverhaulInfo + ManagedObject <|-- OnsiteOverhaulTask + +``` + +M.3164.3(25) + +Inheritance diagram showing ManagedObject as the base class for OnsiteOverhaulInfo and OnsiteOverhaulTask. ManagedObject has attributes: -objectClass, -objectInstance, -creationSource. OnsiteOverhaulInfo has attributes: -overhaulInfoID, -overhaulTaskList. OnsiteOverhaulTask has attributes: -taskID, -overhaulExecutor, -overhaulStatus, -overhaulDes, -timeInfo, -orderID, -resourceSet. + +**Figure 2 – Inheritance diagram of the on-site overhaul related IOCs** + +The above two IOCs are mapped to JSON/YAML data types in the REST-based interface design, and IOC ManagedObject from [ITU-T X.785] will be the base class for all of them. + +Their YAML definitions are given in Tables 5 and 6. + +**Table 5 – YAML schema definition of OnsiteOverhaulInfo** + +``` +OnsiteOverhaulInfo_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + overhaulInfoID: + type: string + overhaulTaskList: + $ref: '#/components/schemas/OverhaulTaskListType' + required: + - overhaulInfoID + - overhaulTaskList +``` + +**Table 6 – YAML schema definition of OnsiteOverhaulTask** + +``` +OnsiteOverhaulTask_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + overhaulExecutor: + type: string + overhaulStatus: + type: string + enum: + - notStart + - doing + - finished + overhaulDes: + type: string + timeInfo: + $ref: '#/components/schemas/TimeInfoListType' + orderID: + type: string + resourceSet: + $ref: '#/components/schemas/ResourceSetType' + required: +``` + +``` + +- taskID +- overhaulStatus +- overhaulDes +- orderID +- resourceSet + +``` + +### **7.2.3 On-site troubleshooting related entities definitions** + +Clause 6.5 of [ITU-T M.3164] provides the protocol neutral information model for on-site troubleshooting related IOCs, including OnsiteTroubleshootingInfo, OnsiteTroubleshootingTask, TroubleType, Expert. The inheritance diagram of the above IOCs can be found in Figure 3. The containment and association relationship for them can be found in Figure 9 of [ITU-T M.3164]. + +![Inheritance diagram showing ManagedObject (ITU-T X.785) as the base class for OnsiteTroubleshootingInfo, OnsiteTroubleshootingTask, TroubleType, and Expert. Each class box lists its attributes.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +classDiagram + class ManagedObject { + <> + -objectClass + -objectInstance + -creationSource + } + class OnsiteTroubleshootingInfo { + <> + -troubleshootingInfoID + -troubleshootingTaskList + } + class OnsiteTroubleshootingTask { + <> + -taskID + -occurTime + -status + -troubleDes + -confirmInfo + -maintenanceInfo + -troubleTypeID + -orderID + -resourceSet + } + class TroubleType { + <> + -troubleTypeID + -troubleLevel + -troubleTypeDes + -solution + -expertSet + } + class Expert { + <> + -expertID + -expertAdditionInfo + -expertGroup + -expertDepartment + -email + -skillArea + -availableRate + } + ManagedObject <|-- OnsiteTroubleshootingInfo + ManagedObject <|-- OnsiteTroubleshootingTask + ManagedObject <|-- TroubleType + ManagedObject <|-- Expert + +``` + +Inheritance diagram showing ManagedObject (ITU-T X.785) as the base class for OnsiteTroubleshootingInfo, OnsiteTroubleshootingTask, TroubleType, and Expert. Each class box lists its attributes. + +M.3164.3(25) + +**Figure 3 – Inheritance diagram of the on-site troubleshooting related IOCs** + +The above four IOCs are mapped to into JSON/YAML data types in the REST-based interface design, and IOC ManagedObject from [ITU-T X.785] will be the base IOC for all of them. + +Their YAML definitions are given in Tables 7 to 10. + +**Table 7 – YAML schema definition of OnsiteTroubleshootingInfo** + +``` + +OnsiteTroubleShootingInfo_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + troubleshootingID: + type: string + troubleshootingTaskList: + $ref: '#/components/schemas/TroubleshootingTaskListType' + required: + +``` + +``` +- troubleshootingID +- troubleshootingTaskList +``` + +**Table 8 – YAML schema definition of OnsiteTroubleshootingTask** + +``` +OnsiteTroubleShootingTask_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + occurTime: + type: string + format: date-time + status: + type: string + enum: + - notStart + - doing + - finished + troubleDes: + type: string + confirmInfo: + $ref: '#/components/schemas/ConfirmInfoSetType' + miaintenanceInfo: + $ref: '#/components/schemas/MaintenanceInfoSetType' + troubleTypeID: + type: string + format: uri + orderID: + type: string + resourceSet: + $ref: '#/components/schemas/ResourceSetType' + required: + - taskID + - status + - troubleDes + - troubleTypeID + - orderID + - resourceSet +``` + +**Table 9 – YAML schema definition of TroubleType** + +``` +TroubleType_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + troubleTypeID: + type: string + troubleLevel: + type: string + enum: + - urgent + - serious + - warn + - common + troubleTypeDes: + type: string + solution: + type: string + expertSet: + $ref: '#/components/schemas/ExpertSetType' + required: + - troubleTypeID + - troubleLevel + - troubleTypeDes + - solution + - expertSet +``` + +**Table 10 – YAML schema definition of Expert** + +``` +Expert_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + expertID: + type: string + expertAddtionInfo: + $ref: '#/components/schemas/ExpertAddtionInfoSetType' + expertGroup: + type: string + expertDepartment: +``` + +``` + +type: string +email: + type: string +skillArea: + type: string +availableRate: + type: number + format: double +required: + - expertID + - expertGroup + - email + - skillArea + - availableRate + +``` + +### 7.2.4 On-site service activation related entities definitions + +Clause 6.6 of [ITU-T M.3164] provides the protocol neutral information model for service activation related IOCs, including ServiceActivationInfo, ServiceActivationTask, ServiceActivationRecord. The inheritance diagram of the above IOCs can be found in Figure 4. The containment and association relationship for them can be found in Figure 13 of [ITU-T M.3164]. + +![Inheritance diagram showing ManagedObject as the base class for ServiceActivationInfo, ServiceActivationTask, and ServiceActivationRecord. ManagedObject has attributes: -objectClass, -objectInstance, -creationSource. ServiceActivationInfo has attributes: -serviceActInfoID, -serviceActTaskList. ServiceActivationTask has attributes: -taskID, -serviceActDes, -executeInfo, -recordList, -orderID, -resourceSet. ServiceActivationRecord has attributes: -recordID, -recordInfo, -submitExecutor, -submitTime.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +classDiagram + class ManagedObject { + <> + -objectClass + -objectInstance + -creationSource + } + class ServiceActivationInfo { + <> + -serviceActInfoID + -serviceActTaskList + } + class ServiceActivationTask { + <> + -taskID + -serviceActDes + -executeInfo + -recordList + -orderID + -resourceSet + } + class ServiceActivationRecord { + <> + -recordID + -recordInfo + -submitExecutor + -submitTime + } + ManagedObject <|-- ServiceActivationInfo + ManagedObject <|-- ServiceActivationTask + ManagedObject <|-- ServiceActivationRecord + +``` + +Inheritance diagram showing ManagedObject as the base class for ServiceActivationInfo, ServiceActivationTask, and ServiceActivationRecord. ManagedObject has attributes: -objectClass, -objectInstance, -creationSource. ServiceActivationInfo has attributes: -serviceActInfoID, -serviceActTaskList. ServiceActivationTask has attributes: -taskID, -serviceActDes, -executeInfo, -recordList, -orderID, -resourceSet. ServiceActivationRecord has attributes: -recordID, -recordInfo, -submitExecutor, -submitTime. + +M.3164.3(25) + +**Figure 4 – Inheritance diagram of the service activation related IOCs** + +The above three IOCs are mapped to into JSON/YAML data types in the REST-based interface design, and IOC ManagedObject from [ITU-T X.785] will be the base IOC for all of them. + +Their YAML definitions are given in Tables 11 to 13. + +**Table 11 – YAML schema definition of ServiceActivationInfo** + +``` +ServiceActivationInfo_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + serviceActInfoID: + type: string + serviceActTaskList: + $ref: '#/components/schemas/ServiceActTaskListType' + required: + - serviceActInfoID + - serviceActTaskList +``` + +**Table 12 – YAML schema definition of ServiceActivationTask** + +``` +ServiceActivationTask_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + serviceActDes: + type: string + executeInfo: + $ref: '#/components/schemas/ExecuteInfoSetType' + recordList: + $ref: '#/components/schemas/RecordListType' + orderID: + type: string + resourceSet: + $ref: '#/components/schemas/ResourceSetType' + required: + - taskID + - serviceActDes + - executeInfo + - recordList + - orderID + - resourceSet +``` + +**Table 13 – YAML schema definition of ServiceActivationRecord** + +``` + +ServiceActivationRecord_C: + allOf: + - $ref: '#/components/schemas/ManagedObject_C' + type: object + properties: + recordID: + type: string + recordInfo: + type: string + submitExecutor: + type: string + submitTime: + type: string + format: date-time + required: + - recordID + - recordInfo + +``` + +## **7.3 Definitions of the REST-based interface operations provided by SMAT** + +Figure 5 provides the class diagram for SMAT\_IRP IOC of [ITU-T M.3164.2], which contains several interface objects that define the interface operations provided by SMAT to TSMS. + +![UML Class diagram for SMAT_IRP IOC. SMAT_IRP (InformationObjectClass) realizes SMAT_IRPOperations (Interface). SMAT_IRPOperations includes PatrolTaskOperations, OnsiteTroubleShootingOperations, OnsiteOverhaulOperations, and ServiceActivationOperations. PatrolTaskOperations includes pushPatrolTasks(), pushPatrolRoute(), and pushSmartIdentificationData(). OnsiteTroubleShootingOperations includes pushTroubleShootingTasks(), pushTroubleShootingGuidance(), and pushTroubleAnalysisResult(). OnsiteOverhaulOperations includes pushMaintenanceJob() and pushOverhaulGuidanceInfo(). ServiceActivationOperations includes pushServiceActivationJob().](a3472689858b068ef469213682965325_img.jpg) + +``` + +classDiagram + class SMAT_IRP { + <> + } + class SMAT_IRPOperations { + <> + } + class PatrolTaskOperations { + <> + +pushPatrolTasks() + +pushPatrolRoute() + +pushSmartIdentificationData() + } + class OnsiteTroubleShootingOperations { + <> + +pushTroubleShootingTasks() + +pushTroubleShootingGuidance() + +pushTroubleAnalysisResult() + } + class OnsiteOverhaulOperations { + <> + +pushMaintenanceJob() + +pushOverhaulGuidanceInfo() + } + class ServiceActivationOperations { + <> + +pushServiceActivationJob() + } + + SMAT_IRP --> SMAT_IRPOperations : <> + SMAT_IRPOperations <|-- PatrolTaskOperations : <> + SMAT_IRPOperations <|-- OnsiteTroubleShootingOperations : <> + SMAT_IRPOperations <|-- OnsiteOverhaulOperations : <> + SMAT_IRPOperations <|-- ServiceActivationOperations : <> + +``` + +UML Class diagram for SMAT\_IRP IOC. SMAT\_IRP (InformationObjectClass) realizes SMAT\_IRPOperations (Interface). SMAT\_IRPOperations includes PatrolTaskOperations, OnsiteTroubleShootingOperations, OnsiteOverhaulOperations, and ServiceActivationOperations. PatrolTaskOperations includes pushPatrolTasks(), pushPatrolRoute(), and pushSmartIdentificationData(). OnsiteTroubleShootingOperations includes pushTroubleShootingTasks(), pushTroubleShootingGuidance(), and pushTroubleAnalysisResult(). OnsiteOverhaulOperations includes pushMaintenanceJob() and pushOverhaulGuidanceInfo(). ServiceActivationOperations includes pushServiceActivationJob(). + +**Figure 5 – Class diagram for SMAT\_IRP IOC** + +The protocol neutral analyses for the above operations have already been specified in [ITU-T M.3164.2], and they will be mapped to resources and the corresponding interface methods in the REST-based interface design. + +The interface operations provided by the SMAT to the TSMS are mapped from [ITU-T M.3164.2] operations to the paths (resources) and corresponding HTTP methods in this Recommendation. The mapping is summarized in Table 14. + +**Table 14 – Mapping table of interface operations provided by SMAT** + +| [ITU-T M.3164.2] | | [ITU-T M.3164.3] | | +|---------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------| +| Interface | Operation | Path | HTTP method | +| PatrolTaskOperations | pushPatrolTask | /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C | POST | +| | pushPatrolRoute | /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/pushPatrolRoute | POST | +| | pushSmartIdentification | /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/pushSmartIDData | POST | +| OnsiteOverhaulOperations | pushMaintenanceJob | /OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C | POST | +| | pushOverhaulGuidanceInfo | /OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/pushOverhaulGuidanceInfo | POST | +| OnsiteTroubleShootingOperations | pushTroubleShootingTasks | /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask_C | POST | +| | pushTroubleShootingGuidance | /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask_C={taskID}/pushTroubleShootingGuidance | POST | +| | pushTroubleAnalysisResult | /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask_C={taskID}/pushTroubleAnalysisResult | POST | +| ServiceActivationOperations | pushServiceActivationJob | /ServiceActivationInfo_C={serviceActInfoID}/ServiceActivationTask_C | POST | + +### 7.3.1 REST-based resource and method definition for PatrolTaskOperations + +The OnsitePatrolTask IOC is mapped to a OnsitePatrolTask\_C in the REST-based design, and the operations defined in PatrolTaskOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.3.1.1 Mapping of the pushPatrolTasks operation + +Clause 7.2.1.1 of [ITU-T M.3164.2] provides the detailed definitions for pushPatrolTasks operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushPatrolTasks operation can be found in Table 15. + +**Table 15 – YAML schema definition of pushPatrolTasks operation** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +|
 paths:   /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C:     parameters:       - \$ref: '#/components/parameters/patrolInfoID'      post: 
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------| + +``` + +tags: + - PatrolTask-SMAT +summary: send an on-site patrol task to the designated SMAT +operationId: pushPatrolTasks +requestBody: + description: the content of patrol tasks list needs to be pushed to the +designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + patrolTasksList: + type: array + items: + $ref: '#/components/schemas/OnsitePatrolTask_C' + required: true +responses: + 200: + description: "The patrol tasks have been successfully sent to the +SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +``` + +#### 7.3.1.2 Mapping of the pushPatrolRoute operation + +Clause 7.2.1.2 of [ITU-T M.3164.2] provides the detailed definitions for pushPatrolRoute operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushPatrolRoute operation can be found in Table 16. + +**Table 16 – YAML schema definition of pushPatrolRoute operation** + +``` + +paths: + + /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/pushPatrolRoute + : + +``` + +``` + +parameters: + - $ref: '#/components/parameters/patrolInfoID' + - $ref: '#/components/parameters/taskID' + +post: + tags: + - PatrolTask-SMAT + summary: push the on-site patrol route to the designated SMAT + operationId: pushPatrolRoute + requestBody: + description: the content of the patrol route needs to be pushed to the + designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + patrolRoute: + type: array + items: + $ref: '#/components/schemas/OnsitePatrolPoint_C' + required: true + responses: + 200: + description: "The patrol route has been successfully sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +``` + +#### 7.3.1.3 Mapping of the pushSmartIdentificationData operation + +Clause 7.2.1.3 of [ITU-T M.3164.2] provides the detailed definitions for pushSmartIdentificationData operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushSmartIdentificationData operation can be found in Table 17. + +**Table 17 – YAML schema definition of pushSmartIdentificationData operation** + +``` +Paths: + +/OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/pushSmartIDData +: + parameters: + - $ref: '#/components/parameters/patrolInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - PatrolTask-SMAT + summary: push the smart identification data of the patrol object to the +designated SMAT + operationId: pushSmartIDData + requestBody: + description: the smart identification data of the patrol object needs +to be pushed to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + smartIDData: + type: array + items: + $ref: '#/components/schemas/ObjectImageListType' + required: true + responses: + 200: + description: "The smart identification data has been successfully sent +to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} +``` + +### 7.3.2 REST-based resource and method definition for OnsiteOverhaulOperations + +The OnsiteOverhaulTask IOC is mapped to a OnsiteOverhaulTask\_C in the REST-based design, and the operations defined in OnsiteOverhaulOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.3.2.1 Mapping of the pushMaintenanceJob operation + +Clause 7.2.2.1 of [ITU-T M.3164.2] provides the detailed definitions for pushMaintenanceJob operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushMaintenanceJob operation can be found in Table 18. + +**Table 18 – YAML schema definition of pushMaintenanceJob operation** + +``` +paths: + /OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + + post: + tags: + - OnsiteOverhaul-SMAT + summary: push an on-site overhaul maintenance job to the designated SMAT + operationId: pushMaintenanceJob + requestBody: + description: the content of overhaul maintenance job needs to be pushed + to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + overhaulTaskList: + type: array + items: + $ref: '#/components/schemas/OnsiteOverhaulTask_C' + required: true + responses: + 200: + description: "The overhaul maintenance job has been successfully sent + to the SMAT" + content: + application/json: + schema: +``` + +``` + + $ref: '#/components/schemas/OpStatusType' +400: + description: "Input parameters invalid" + content: {} +500: + description: "An internal problem occurs" + content: {} + +``` + +#### 7.3.2.2 Mapping of the pushOverhaulGuidanceInfo operation + +Clause 7.2.2.2 of [ITU-T M.3164.2] provides the detailed definitions for pushOverhaulGuidanceInfo operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushOverhaulGuidanceInfo operation can be found in Table 19. + +**Table 19 – YAML schema definition of pushOverhaulGuidanceInfo operation** + +``` + +paths: +/OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/pushOverh +aulGuidanceInfo: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteOverhaul-SMAT + summary: push the on-site overhaul guidance information to the designated +SMAT + operationId: pushOverhaulGuidanceInfo + requestBody: + description: guidance information for on-site overhaul tasks needs to +be pushed to the designated the SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + guidanceInfo: + type: string + required: true + responses: + 200: + description: "The on-site overhaul guidance information has been +successfully sent to the SMAT" + +``` + +``` + +content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' +400: + description: "Input parameters invalid" + content: {} +500: + description: "An internal problem occurs" + content: {} + +``` + +### 7.3.3 REST-based resource and method definition for OnsiteTroubleShootingOperations + +The OnsiteTroubleShootingTask IOC is mapped to a OnsiteTroubleShootingTask\_C in the REST-based design, and the operations defined in OnsiteTroubleShootingOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.3.3.1 Mapping of the pushTroubleShootingTasks operation + +Clause 7.2.3.1 of [ITU-T M.3164.2] provides the detailed definitions for pushTroubleShootingTasks operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushTroubleShootingTasks operation can be found in Table 20. + +**Table 20 – YAML schema definition of pushTroubleShootingTasks operation** + +``` + +paths: + /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask + _C: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + + post: + tags: + - OnsiteTroubleShooting-SMAT + summary: push the information of on-site troubleshooting tasks to the + designated SMAT + operationId: pushTroubleShootingTasks + requestBody: + description: the content of on-site troubleshooting tasks needs to be + pushed to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + troubleShootingTaskList: + +``` + +``` + +type: array +items: + $ref: '#/components/schemas/OnsiteTroubleShootingTask_C' +required: true +responses: + 200: + description: "The on-site troubleshooting tasks have been successfully +sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +``` + +#### 7.3.3.2 Mapping of the pushTroubleShootingGuidance operation + +Clause 7.2.3.2 of [ITU-T M.3164.2] provides the detailed definitions for pushTroubleShootingGuidance operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushTroubleShootingGuidance operation can be found in Table 21. + +**Table 21 – YAML schema definition of pushTroubleShootingGuidance operation** + +``` + +paths: + /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C={taskID}/pushTroubleShootingGuidance: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteTroubleShooting-SMAT + summary: push the troubleShooting guidance information to the SMAT + operationId: pushTroubleShootingGuidance + requestBody: + description: guidance information for on-site troubleShooting tasks +needs to be pushed to the designated SMAT + content: + application/json: + +``` + +``` + +schema: + type: object + properties: + SMAT_ID: + type: string + operationGuidanceInfo: + type: string + required: true +responses: + 200: + description: "The on-site troubleShooting guidance information has + been successfully sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +``` + +#### 7.3.3.3 Mapping of the pushTroubleAnalysisResult operation + +Clause 7.2.3.3 of [ITU-T M.3164.2] provides the detailed definitions for pushTroubleAnalysisResult operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushTroubleAnalysisResult operation can be found in Table 22. + +**Table 22 – YAML schema definition of pushTroubleAnalysisResult operation** + +``` + +paths: + /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask + _C={taskID}/pushTroubleAnalysisResult: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteTroubleShooting-SMAT + summary: push the trouble analysis result to the SMAT + operationId: pushTroubleAnalysisResult + requestBody: + +``` + +``` + +description: the content of on-site trouble analysis result needs to be +pushed to the designated SMAT +content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + troubleTypeID: + type: string + format: uri + causeList: + type: array + items: + $ref: '#/components/schemas/CauseListType' + imagesList: + type: array + items: + $ref: '#/components/schemas/ImagesListType' + required: true +responses: + 200: + description: "The trouble analysis result has been successfully sent +to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +``` + +### 7.3.4 REST-based resource and method definition for ServiceActivationOperations + +The ServiceActivationTask IOC is mapped to a ServiceActivationTask\_C in the REST-based design, and the operations defined in ServiceActivationOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.3.4.1 Mapping of the pushServiceActivationJob operation + +Clause 7.2.4.1 of [ITU-T M.3164.2] provides the detailed definitions for pushServiceActivationJob operation provided by SMAT, including input parameters, out parameters, exceptions. The YAML schema definitions of pushServiceActivationJob operation can be found in Table 23. + +**Table 23 – YAML schema definition of pushServiceActivationJob operation** + +``` +paths: + /ServiceActivationInfo_C={serviceActInfoID}/ServiceActivationTask_C: + parameters: + - $ref: '#/components/parameters/serviceActInfoID' + + post: + tags: + - ServiceActivation-SMAT + summary: push the information of the service activation job to the SMAT + operationId: pushServiceActJob + requestBody: + description: the content of service activation jobs list needs to be + pushed to the designated SMAT. + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + serviceActTaskList: + type: array + items: + $ref: '#/components/schemas/ServiceActivationTask_C' + required: true + responses: + 200: + description: "The service activation job has been successfully sent + to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} +``` + +``` + +500: + description: "An internal problem occurs" + content: {} + +``` + +## 7.4 Definitions of the REST-based interface operations provided by TSMS + +Figure 6 provides the class diagram for TSM\_IRP IOC in [ITU-T M.3164.2], which contains several interface objects that define the interface operations provided by TSMS to SMAT. + +![Class diagram for TSM_IRP IOC. TSM_IRP (InformationObjectClass) realizes TSM_IRPOperations (Interface). TSM_IRPOperations includes PatrolTaskOperations, OnsiteTroubleShootingOperations, OnsiteOverhaulOperations, and ServiceActivationOperations. PatrolTaskOperations includes +findSmartIdentificationData() and +uploadPatrolRecord. OnsiteTroubleShootingOperations includes +uploadTroubleShootingResult() and +requestForRemoteAssistance(). OnsiteOverhaulOperations includes +uploadOverhaulProcessRecord() and +requestForRemoteAssistance(). ServiceActivationOperations includes +uploadServiceActivationRecord().](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +classDiagram + class TSM_IRP { + <> + } + class TSM_IRPOperations { + <> + } + class PatrolTaskOperations { + <> + +findSmartIdentificationData() + +uploadPatrolRecord + } + class OnsiteTroubleShootingOperations { + <> + +uploadTroubleShootingResult() + +requestForRemoteAssistance() + } + class OnsiteOverhaulOperations { + <> + +uploadOverhaulProcessRecord() + +requestForRemoteAssistance() + } + class ServiceActivationOperations { + <> + +uploadServiceActivationRecord() + } + TSM_IRP --> TSM_IRPOperations : <> + TSM_IRPOperations <> PatrolTaskOperations + TSM_IRPOperations <> OnsiteTroubleShootingOperations + TSM_IRPOperations <> OnsiteOverhaulOperations + TSM_IRPOperations <> ServiceActivationOperations + +``` + +Class diagram for TSM\_IRP IOC. TSM\_IRP (InformationObjectClass) realizes TSM\_IRPOperations (Interface). TSM\_IRPOperations includes PatrolTaskOperations, OnsiteTroubleShootingOperations, OnsiteOverhaulOperations, and ServiceActivationOperations. PatrolTaskOperations includes +findSmartIdentificationData() and +uploadPatrolRecord. OnsiteTroubleShootingOperations includes +uploadTroubleShootingResult() and +requestForRemoteAssistance(). OnsiteOverhaulOperations includes +uploadOverhaulProcessRecord() and +requestForRemoteAssistance(). ServiceActivationOperations includes +uploadServiceActivationRecord(). + +Figure 6 – Class diagram for TSM\_IRP IOC + +The protocol neutral analyses for the above operations have already been specified in [ITU-T M.3164.2], and they will be mapped to resources and the corresponding interface methods in the REST-based interface design. + +The interface operations provided by TSMS to SMAT are mapped from [ITU-T M.3164.2] operations to the paths (resources) and corresponding HTTP methods in this Recommendation. The mapping is summarized in Table 24. + +Table 24 – Mapping table of interface operations provided by TSMS + +| [ITU-T M.3164.2] | | [ITU-T M.3164.3] | | +|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------|-------------| +| Interface | Operation | Path | HTTP method | +| PatrolTaskOperations | findSmartIdentification Data | /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/findSmartIDData | GET | +| | uploadPatrolRecord | /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/OnsitePatrolRecord_C | POST | +| OnsiteOverhaulOperations | uploadOverHaulProcessRecord | /OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/uploadOverhaulProcessRecord | POST | +| | requestForRemoteAssistance | /OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/requestForRemoteAssistance | GET | + +**Table 24 – Mapping table of interface operations provided by TSMS** + +| [ITU-T M.3164.2] | | [ITU-T M.3164.3] | | +|---------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------|------| +| OnsiteTroubleShootingOperations | uploadTroubleShootingResult | /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask_C={taskID}/uploadTroubleShootingResult | POST | +| | requestForRemoteAssistance | /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask_C={taskID}/requestForRemoteAssistance | GET | +| ServiceActivationOperations | uploadServiceActivationRecord | /ServiceActivationInfo_C={serviceActInfoID}/ServiceActivationTask_C={taskID}/ServiceActivationRecord_C | POST | + +### **7.4.1 REST-based resource and method definition for PatrolTaskOperations** + +The OnsitePatrolTask IOC is mapped to a OnsitePatrolTask\_C in the REST-based design, and the operations defined in PatrolTaskOperations are mapped to corresponding HTTP operations under this resource. + +#### **7.4.1.1 Mapping of the findSmartIdentificationData operation** + +Clause 7.3.1.1 of [ITU-T M.3164.2] provides the detailed definitions for findSmartIdentificationData operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of findSmartIdentificationData operation can be found in Table 25. + +**Table 25 – YAML schema definition of findSmartIdentificationData operation** + +``` + +paths: + /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/findSmartIDData: + get: + parameters: + - $ref: '#/components/parameters/patrolInfoID' + - $ref: '#/components/parameters/taskID' + - $ref: '#/components/parameters/SMAT_ID' + get: + tags: + - PatrolTask-TSMS + summary: get smart identification data of the patrol information from the TSMS + operationId: findSmartIDData + responses: + 200: + description: "The smart identification data is successfully returned from the TSMS" + content: + application/json: + +``` + +``` + + schema: + type: object + properties: + opStatus: + $ref: '#/components/schemas/OpStatusType' + smartIdentificationData: + type: array + items: + $ref: '#/components/schemas/ObjectImageListType' + 400: + description: "Input parameters invalid" + content: {} + 404: + description: "Patrol info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +``` + +#### **7.4.1.2 Mapping of the uploadPatrolRecord operation** + +Clause 7.3.1.2 of [ITU-T M.3164.2] provides the detailed definitions for uploadPatrolRecord operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of uploadPatrolRecord operation can be found in Table 26. + +**Table 26 – YAML schema definition of uploadPatrolRecord operation** + +``` + +paths: +/OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/OnsitePatrolRec +ord_C: + parameters: + - $ref: '#/components/parameters/patrolInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - PatrolTask-TSMS + summary: upload a patrol record to the TSMS + operationId: uploadPatrolRecord + requestBody: + description: the content of patrol record needs to be uploaded to the +TSMS + +``` + +``` + +content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + patrolRecord: + type: array + items: + $ref: '#/components/schemas/OnsitePatrolRecord_C' + required: true +responses: + 200: + description: "The patrol record information is successfully received +by the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 404: + description: "patrol Info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +``` + +### 7.4.2 REST-based resource and method definition for OnsiteOverhaulOperations + +The OnsiteOverhaulTask IOC is mapped to a OnsiteOverhaulTask\_C in the REST-based design, and the operations defined in OnsiteOverhaulOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.4.2.1 Mapping of the uploadOverHaulProcessRecord operation + +Clause 7.3.2.1 of [ITU-T M.3164.2] provides the detailed definitions for uploadOverHaulProcessRecord operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of uploadOverHaulProcessRecord operation can be found in Table 27. + +**Table 27 – YAML schema definition of uploadOverHaulProcessRecord operation** + +``` +paths: +/OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/uploadOverhaulProcessRecord: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteOverhaul-TSMS + summary: upload an overhaul process record to the TSMS + operationId: uploadOverhaulProcessRecord + requestBody: + description: the content of the overhaul process record needs to be uploaded to the TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + overhaulExecutor: + type: string + status: + type: string + enum: + - normal + - abnormal + - notCheck + timeInfo: + type: string + orderID: + type: string + recordInfo: + type: string + required: true + responses: + 200: + description: "The overhaul process record information is successfully received by the TSMS" + content: +``` + +``` + + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' +400: + description: "Input parameters invalid" + content: {} +404: + description: "overhaul info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' +500: + description: "Internal Server Error" + content: {} + +``` + +#### 7.4.2.2 Mapping of the requestForRemoteAssistance operation + +Clause 7.3.2.2 of [ITU-T M.3164.2] provides the detailed definitions for requestForRemoteAssistance operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of requestForRemoteAssistance operation can be found in Table 28. + +**Table 28 – YAML schema definition of requestForRemoteAssistance operation** + +``` + +paths: + /OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/requestForRemoteAssistance: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + - $ref: '#/components/parameters/taskID' + - $ref: '#/components/parameters/SMAT_ID' + - $ref: '#/components/parameters/requestDes' + + get: + tags: + - OnsiteOverhaul-TSMS + summary: request remote assistance from the TSMS for an overhaul task + operationId: requestForOverhaulRemoteAssistance + responses: + 200: + description: "The remote assistance information is successfully received by the TSMS" + content: + application/json: + +``` + +``` + +schema: + type: object + properties: + opStatus: + $ref: '#/components/schemas/OpStatusType' + expertInfoList: + type: array + items: + $ref: '#/components/schemas/Expert_C' + assistanceLink: + type: string +400: + description: "Input parameters invalid" + content: {} +404: + description: "overhaul info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' +500: + description: "Internal Server Error" + content: {} + +``` + +### 7.4.3 REST-based resource and method definition for OnsiteTroubleShootingOperations + +The OnsiteTroubleShootingTask IOC is mapped to a OnsiteTroubleShootingTask\_C in the REST-based design, and the operations defined in OnsiteTroubleShootingOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.4.3.1 Mapping of the uploadTroubleShootingResult operation + +Clause 7.3.3.1 of [ITU-T M.3164.2] provides the detailed definitions for uploadTroubleShootingResult operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of uploadTroubleShootingResult operation can be found in Table 29. + +**Table 29 – YAML schema definition of uploadTroubleShootingResult operation** + +``` + +paths: + /OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask_C={taskID}/uploadTroubleShootingResult: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + post: + +``` + +``` + +tags: + - OnsiteTroubleShooting-TSMS +summary: upload the troubleshooting result to the TSMS +operationId: uploadTroubleShootingResult +requestBody: + description: the content of troubleShooting result needs to be uploaded +to the TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + troubleShootingExecutor: + type: string + status: + type: string + enum: + - normal + - abnormal + - notCheck + timeInfo: + type: string + orderID: + type: string + troubleTypeID: + type: string + format: uri + troubleshootingResult: + type: string + required: true +responses: + 200: + description: "The trouble shooting result record information is +successfully received by the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + +``` + +``` + +content: {} +404: + description: "troubleShooting Info ID or SMAT ID cannot be found in +the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' +500: + description: "Internal Server Error" + content: {} + +``` + +#### 7.4.3.2 Mapping of the requestForRemoteAssistance operation + +Clause 7.3.3.2 of [ITU-T M.3164.2] provides the detailed definitions for requestForRemoteAssistance operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of requestForRemoteAssistance operation can be found in Table 30. + +**Table 30 – YAML schema definition of requestForRemoteAssistance operation** + +``` + +paths: +/OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C={taskID}/requestForRemoteAssistance: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + - $ref: '#/components/parameters/SMAT_ID' + - $ref: '#/components/parameters/requestDes' + + get: + tags: + - OnsiteTroubleShooting-TSMS + summary: request remote assistance from the TSMS for a troubleshooting +task + operationId: requestForTroubleShootingRemoteAssis + responses: + 201: + description: "The remote assistance information is successfully +received by the TSMS" + content: + application/json: + schema: + type: object + properties: + opStatus: + +``` + +``` + + $ref: '#/components/schemas/OpStatusType' + expertInfoList: + type: array + items: + $ref: '#/components/schemas/Expert_C' + assistanceLink: + type: string +400: + description: "Input parameters invalid" + content: {} +404: + description: "Patrol info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' +500: + description: "Internal Server Error" + content: {} + +``` + +### 7.4.4 REST-based resource and method definition for ServiceActivationOperations + +The ServiceActivationTask IOC is mapped to a ServiceActivationTask\_C in the REST-based design, and the operations defined in ServiceActivationOperations are mapped to corresponding HTTP operations under this resource. + +#### 7.4.4.1 Mapping of the uploadServiceActivationRecord operation + +Clause 7.3.4.1 of [ITU-T M.3164.2] provides the detailed definitions for uploadServiceActivationRecord operation provided by TSMS, including input parameters, out parameters, exceptions. The YAML schema definitions of uploadServiceActivationRecord operation can be found in Table 31. + +**Table 31 – YAML schema definition of uploadServiceActivationRecord operation** + +``` + +paths: + /ServiceActivationInfo_C={serviceActInfoID}/ServiceActivationTask_C={taskID}/ServiceActivationRecord_C: + parameters: + - $ref: '#/components/parameters/serviceActInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - ServiceActivation-TSMS + summary: upload a service activation record to the TSMS + operationId: uploadServiceActivationRecord + +``` + +``` + +requestBody: + description: the content of service activation record needs to be +uploaded to the TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + serviceActivationRecord: + type: array + items: + $ref: '#/components/schemas/ServiceActivationRecord_C' + required: true +responses: + 200: + description: "The service activation record information is +successfully received by the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 404: + description: "Patrol info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +``` + +## 7.5 Definitions of the attributes and data types + +The YAML schema definitions for the attributes and specific data types mentioned above can be found in Table 32. Some generic IOC ManagedObject classes (e.g., ManagedObject\_C and SourceIndicatorType) can be found in clause A.1 of [ITU-T X.785]. + +**Table 32 – YAML schema definition of common attributes data types** + +``` +components: + schemas: + PatrolTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + + TaskIDType: + type: string + format: uri + + PointSequenceListType: + type: array + items: + $ref: '#/components/schemas/PointNameType' + + PointNameType: + type: string + + RecordListType: + type: array + items: + $ref: '#/components/schemas/RecordIDType' + + RecordIDType: + type: string + format: uri + + ResourceSetType: + type: array + items: + $ref: '#/components/schemas/ResourceNameType' + + ResourceNameType: + type: string + format: uri + + CoordinateSetType: + type: array + items: +``` + +``` +$ref: '#/components/schemas/CoordinateType' + +CoordinateType: + type: object + properties: + latitude: + type: number + longitude: + type: number + altitude: + type: number + coordinateSystem: + type: string + required: + - latitude + - longitude + - altitude + - coordinateSystem + +OverhaulTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +TimeInfoListType: + type: array + items: + $ref: '#/components/schemas/TimeInfoType' + +TimeInfoType: + type: object + properties: + startTime: + type: string + format: date-time + endTime: + type: string + format: date-time + required: + - startTime + - endTime +``` + +``` +TroubleshootingTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +ConfirmInfoSetType: + type: array + items: + $ref: '#/components/schemas/ConfirmInfoType' + +ConfirmInfoType: + type: object + properties: + confirmer: + type: string + confirmTime: + type: string + format: date-time + required: + - confirmer + - confirmTime + +MaintenanceInfoSetType: + type: array + items: + $ref: '#/components/schemas/MaintenanceInfoType' + +MaintenanceInfoType: + type: object + properties: + maintainExecutor: + type: string + maintainPlan: + type: string + maintainTime: + type: string + format: date-time + required: + - maintainExecutor + - maintainPlan +``` + +``` + + - maintainTime + +ExpertSetType: + type: array + items: + $ref: '#/components/schemas/ExpertIDType' + +ExpertIDType: + type: string + format: uri + +ExpertAddtionInfoSetType: + type: array + items: + $ref: '#/components/schemas/ExpertAddtionInfoType' + +ExpertAddtionInfoType: + type: object + properties: + name: + type: string + gender: + type: string + enum: + - male + - female + birthYear: + type: string + format: full-date + example: 1975-08-11 + required: + - name + +ServiceActTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +ExecuteInfoSetType: + type: array + items: + +``` + +``` +$ref: '#/components/schemas/ExecuteInfoType' + +ExecuteInfoType: + type: object + properties: + executor: + type: string + executionTime: + type: string + format: date-time + executionResult: + type: string + required: + - executor + - executionTime + - executionResult +``` + +# Annex A + +## Formal YAML schema definitions for the on-site TSM interface between SMAT and TSMS + +(This annex forms an integral part of this Recommendation.) + +This annex presents the YAML schema definitions for the generic information objects specified in [ITU-T M.3164], the interface operations for the on-site TSM interface between SMAT and TSMS, and common data types in YAML schema format. + +### A.1 YAML schema definition for information object classes and common data types + +[ITU-T M.3164] provides the protocol-neutral information model for on-site TSM. Table A.1 presents the complete YAML schema definitions for all the information object classes defined in [ITU-T M.3164], as well as the relevant common data types, some of which are reused in this Recommendation. The definitions for generic IOC ManagedObject classes (e.g., `ManagedObject_C` and `SourceIndicatorType`) are reused from [ITU-T X.785] and implemented in the `X.785.yaml` file. To enable reuse of the on-site TSM information model, the definitions from Table A.1 are also implemented in the `M.3164.3-Common.yaml` file. + +**Table A.1 – YAML schema definitions for IOCs and common data types +(M.3164.3-Common.yaml)** + +``` +components: + schemas: + #The following are IOC definitions. + OnsitePatrolInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + patrolInfoID: + type: string + patrolTaskList: + $ref: '#/components/schemas/PatrolTaskListType' + required: + - patrolInfoID + - patrolTaskList + + OnsitePatrolTask_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string +``` + +``` + +taskType: + type: string + enum: + - routine + - temporary + - else +taskStatus: + type: string + enum: + - notready + - ready + - doing + - finished +patrolExecutor: + type: string +startTime: + type: string + format: date-time +endTime: + type: string + format: date-time +pointSequence: + $ref: '#/components/schemas/PointSequenceListType' +recordList: + $ref: '#/components/schemas/RecordListType' +orderID: + type: string +resourceSet: + $ref: '#/components/schemas/ResourceSetType' +required: + - taskID + - taskType + - taskStatus + - patrolExecutor + - pointSequence + - recordList + - orderID + - resourceSet + +OnsitePatrolPoint_C: + allOf: + +``` + +``` + +- $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' +type: object +properties: + pointID: + type: string + pointType: + type: string + enum: + - building + - device + - else + patrolDes: + type: string + coordinates: + $ref: '#/components/schemas/CoordinateSetType' + pointLabel: + type: string +required: + - pointID + - pointType + - patrolDes + - coordinates + - pointLabel + +OnsitePatrolRecord_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + recordID: + type: string + recordExecutor: + type: string + recordTime: + type: string + format: date-time + status: + type: string + enum: + - normal + - abnormal + +``` + +``` + + - notCheck + recordInfo: + type: string + pointID: + type: string + required: + - recordID + - status + - recordInfo + - pointID + +OnsiteOverhaulInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + overhaulInfoID: + type: string + overhaulTaskList: + $ref: '#/components/schemas/OverhaulTaskListType' + required: + - overhaulInfoID + - overhaulTaskList + +OnsiteOverhaulTask_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + overhaulExecutor: + type: string + overhaulStatus: + type: string + enum: + - notStart + - doing + - finished + overhaulDes: + type: string + +``` + +``` + +timeInfo: + $ref: '#/components/schemas/TimeInfoListType' +orderID: + type: string +resourceSet: + $ref: '#/components/schemas/ResourceSetType' +required: + - taskID + - overhaulStatus + - overhaulDes + - orderID + - resourceSet + +OnsiteTroubleShootingInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + troubleshootingID: + type: string + troubleshootingTaskList: + $ref: '#/components/schemas/TroubleshootingTaskListType' + required: + - troubleshootingID + - troubleshootingTaskList + +OnsiteTroubleShootingTask_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + occurTime: + type: string + format: date-time + status: + type: string + enum: + - notStart + - doing + +``` + +``` + + - finished +troubleDes: + type: string +confirmInfo: + $ref: '#/components/schemas/ConfirmInfoSetType' +miantenanceInfo: + $ref: '#/components/schemas/MaintenanceInfoSetType' +troubleTypeID: + type: string + format: uri +orderID: + type: string +resourceSet: + $ref: '#/components/schemas/ResourceSetType' +required: + - taskID + - status + - troubleDes + - troubleTypeID + - orderID + - resourceSet + +TroubleType_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + troubleTypeID: + type: string + troubleLevel: + type: string + enum: + - urgent + - serious + - warn + - common + troubleTypeDes: + type: string + solution: + type: string + expertSet: + +``` + +``` + + $ref: '#/components/schemas/ExpertSetType' + required: + - troubleTypeID + - troubleLevel + - troubleTypeDes + - solution + - expertSet + +Expert_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + expertID: + type: string + expertAddtionInfo: + $ref: '#/components/schemas/ExpertAddtionInfoSetType' + expertGroup: + type: string + expertDepartment: + type: string + email: + type: string + skillArea: + type: string + availableRate: + type: number + format: double + required: + - expertID + - expertGroup + - email + - skillArea + - availableRate + +ServiceActivationInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + serviceActInfoID: + +``` + +``` + + type: string + serviceActTaskList: + $ref: '#/components/schemas/ServiceActTaskListType' + required: + - serviceActInfoID + - serviceActTaskList + +ServiceActivationTask_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + taskID: + type: string + serviceActDes: + type: string + executeInfo: + $ref: '#/components/schemas/ExecuteInfoSetType' + recordList: + $ref: '#/components/schemas/RecordListType' + orderID: + type: string + resourceSet: + $ref: '#/components/schemas/ResourceSetType' + required: + - taskID + - serviceActDes + - executeInfo + - recordList + - orderID + - resourceSet + +ServiceActivationRecord_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + recordID: + type: string + recordInfo: + type: string + +``` + +``` + + submitExecutor: + type: string + submitTime: + type: string + format: date-time + required: + - recordID + - recordInfo + +MaintenanceKnowledgeBaseInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + maintenanceKnowledgeBaseInfoID: + type: string + maintenanceKnowledgeBaseItemList: + $ref: '#/components/schemas/MaintenanceKnowledgeBaseItemListType' + required: + - maintenanceKnowledgeBaseInfoID + - maintenanceKnowledgeBaseItemList + +MaintenanceKnowledgeBaseItem_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + itemID: + type: string + knowledgeDes: + type: string + knowledgeType: + type: string + enum: + - patrol + - overhaul + - troubleshooting + - serviceActivation + knowledgeStatus: + type: string + enum: + +``` + +``` + + - submitting + - notCheck + - checking + - checkedOK + - checkedFail + submitInfo: + $ref: '#/components/schemas/SubmitInfoSetType' + checkInfo: + $ref: '#/components/schemas/CheckInfoSetType' + required: + - itemID + - knowledgeDes + - knowledgeType + - knowledgeStatus + +MaintenanceWorkEvaluationInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + maintenanceWorkEvalInfoID: + type: string + maintenanceWorkEvalItemList: + $ref: '#/components/schemas/MaintenanceWorkEvalItemListType' + required: + - maintenanceWorkEvalInfoID + - maintenanceWorkEvalItemList + +MaintenanceWorkEvaluationItem_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + itemID: + type: string + evaluateResult: + type: string + evaluateTime: + type: string + format: date-time + evaluateExecutor: + +``` + +``` + + type: string + taskID: + type: string + required: + - itemID + - evaluateResult + - evaluateTime + - evaluateExecutor + +SmartMaintenanceAssistToolkitInfo_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + smartMATInfoID: + type: string + deviceSet: + $ref: '#/components/schemas/DeviceSetType' + required: + - smartMATInfoID + - deviceSet + +SmartDevice_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + deviceID: + type: string + devType: + type: string + enum: + - handhold + - headwear + - else + devName: + type: string + devModel: + type: string + devAddress: + type: string + +``` + +``` + +devSerialNum: + type: string +devStorage: + type: string +systemVersion: + type: string + enum: + - android + - ios + - linux + - windowsMobile + - else +currentStatus: + type: string + enum: + - used + - unused +logID: + type: string + format: uri +applicationSet: + $ref: '#/components/schemas/ApplicationSetType' +required: + - deviceID + - devType + - devName + - devModel + - devAddress + - devSerialNum + - devStorage + - systemVersion + - currentStatus + - logID + - applicationSet + +SmartApplication_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + applicationID: + +``` + +``` + + type: string +appType: + type: string + enum: + - handhold + - headwear + - else +versionNum: + type: string +operatingSystem: + type: string + enum: + - android + - ios + - linux + - windowsMobile + - else +downloadLink: + type: string + format: uri +required: + - applicationID + - appType + - versionNum + - operatingSystem + - downloadLink + +MaintenanceLog_C: + allOf: + - $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' + type: object + properties: + logID: + type: string + recordList: + $ref: '#/components/schemas/RecordListType' + required: + - logID + - recordList + +MaintenanceRecord_C: + +``` + +``` + +allOf: +- $ref: 'X.785.yaml#/components/schemas/ManagedObject_C' +type: object +properties: + recordID: + type: string + recordInfo: + type: string + recordTime: + type: string + format: date-time + recordExecutor: + type: string +required: +- recordID +- recordInfo + +#The following are common data type definitions. +PatrolTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +TaskIDType: + type: string + format: uri + +PointSequenceListType: + type: array + items: + $ref: '#/components/schemas/PointNameType' + +PointNameType: + type: string + +RecordListType: + type: array + items: + $ref: '#/components/schemas/RecordIDType' + +RecordIDType: + +``` + +``` +type: string +format: uri + +ResourceSetType: + type: array + items: + $ref: '#/components/schemas/ResourceNameType' + +ResourceNameType: + type: string + format: uri + +CoordinateSetType: + type: array + items: + $ref: '#/components/schemas/CoordinateType' + +CoordinateType: + type: object + properties: + latitude: + type: number + longitude: + type: number + altitude: + type: number + coordinateSystem: + type: string + required: + - latitude + - longitude + - altitude + - coordinateSystem + +OverhaulTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +TimeInfoListType: + type: array +``` + +``` + +items: + $ref: '#/components/schemas/TimeInfoType' + +TimeInfoType: + type: object + properties: + startTime: + type: string + format: date-time + endTime: + type: string + format: date-time + required: + - startTime + - endTime + +TroubleshootingTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +ConfirmInfoSetType: + type: array + items: + $ref: '#/components/schemas/ConfirmInfoType' + +ConfirmInfoType: + type: object + properties: + confirmer: + type: string + confirmTime: + type: string + format: date-time + required: + - confirmer + - confirmTime + +MaintenanceInfoSetType: + type: array + items: + +``` + +``` + +$ref: '#/components/schemas/MaintenanceInfoType' + +MaintenanceInfoType: + type: object + properties: + maintainExecutor: + type: string + maintainPlan: + type: string + maintainTime: + type: string + format: date-time + required: + - maintainExecutor + - maintainPlan + - maintainTime + +ExpertSetType: + type: array + items: + $ref: '#/components/schemas/ExpertIDType' + +ExpertIDType: + type: string + format: uri + +ExpertAddtionInfoSetType: + type: array + items: + $ref: '#/components/schemas/ExpertAddtionInfoType' + +ExpertAddtionInfoType: + type: object + properties: + name: + type: string + gender: + type: string + enum: + - male + - female + +``` + +``` + +birthYear: + type: string + format: full-date + example: 1975-08-11 +required: + - name + +ServiceActTaskListType: + type: array + items: + $ref: '#/components/schemas/TaskIDType' + +ExecuteInfoSetType: + type: array + items: + $ref: '#/components/schemas/ExecuteInfoType' + +ExecuteInfoType: + type: object + properties: + executor: + type: string + executionTime: + type: string + format: date-time + executionResult: + type: string + required: + - executor + - executionTime + - executionResult + +MaintenanceKnowledgeBaseItemListType: + type: array + items: + $ref: '#/components/schemas/ItemIDType' + +ItemIDType: + type: string + format: uri + +``` + +``` +SubmitInfoSetType: + type: array + items: + $ref: '#/components/schemas/SubmitInfoType' + +SubmitInfoType: + type: object + properties: + submitterID: + type: string + submitTime: + type: string + format: date-time + required: + - submitterID + - submitTime + +CheckInfoSetType: + type: array + items: + $ref: '#/components/schemas/CheckInfoType' + +CheckInfoType: + type: object + properties: + checkerID: + type: string + checkTime: + type: string + format: date-time + required: + - checkerID + - checkTime + +MaintenanceWorkEvalItemListType: + type: array + items: + $ref: '#/components/schemas/ItemIDType' + +DeviceSetType: + type: array +``` + +``` + +items: + $ref: '#/components/schemas/DeviceIDType' + +DeviceIDType: + type: string + format: uri + +ApplicationSetType: + type: array + items: + $ref: '#/components/schemas/ApplicationIDType' + +ApplicationIDType: + type: string + format: uri + +``` + +### A.2 YAML schema definition for interface operations provided by SMAT + +Table A.2 provides the complete definition of interface operations provided by SMAT. The common IOCs and common data types used in this clause are defined in file of M.3164.3-Common.yaml. The definitions in Table A.2 are independently implemented in the M.3164.3-A.2.yaml file. + +**Table A.2 – Complete definition of interface operations provided by SMAT +(M.3164.3-A.2.yaml)** + +``` + +openapi: 3.0.0 +info: + title: Interface Operations provided by SMAT + description: This is the formal Definitions of the REST-based interface +operations provided by SMAT + termsOfService: https://www.itu.int/en/ITU-T/about/Pages/default.aspx + contact: + email: zhangzmx8848@gmail.com + license: + name: Apache 2.0 + url: http://www.apache.org/licenses/LICENSE-2.0.html + version: 1.0.0 +tags: + - name: PatrolTask-SMAT + - name: OnsiteOverhaul-SMAT + - name: OnsiteTroubleShooting-SMAT + - name: ServiceActivation-SMAT + +paths: + /OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C: + +``` + +``` + +parameters: +- $ref: '#/components/parameters/patrolInfoID' + +post: + tags: + - PatrolTask-SMAT + summary: send an on-site patrol task to the designated SMAT + operationId: pushPatrolTasks + requestBody: + description: the content of patrol tasks list needs to be pushed to the +designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + patrolTasksList: + type: array + items: + $ref: 'M.3164.3-Common.yaml#/components/schemas/OnsitePatrolTask_C' + required: true + responses: + 200: + description: "The patrol tasks have been successfully sent to the +SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/pushPatrolRoute +: + parameters: + +``` + +``` + +- $ref: '#/components/parameters/patrolInfoID' +- $ref: '#/components/parameters/taskID' + +post: + tags: + - PatrolTask-SMAT + summary: push the on-site patrol route to the designated SMAT + operationId: pushPatrolRoute + requestBody: + description: the content of the patrol route needs to be pushed to the +designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + patrolRoute: + type: array + items: + $ref: 'M.3164.3- +Common.yaml#/components/schemas/OnsitePatrolPoint_C' + required: true + responses: + 200: + description: "The patrol route has been successfully sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/pushSmartIDData +: + parameters: + - $ref: '#/components/parameters/patrolInfoID' + +``` + +``` + +- $ref: '#/components/parameters/taskID' + +post: + tags: + - PatrolTask-SMAT + summary: push the smart identification data of the patrol object to the +designated SMAT + operationId: pushSmartIDData + requestBody: + description: the smart identification data of the patrol object needs +to be pushed to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + smartIDData: + type: array + items: + $ref: '#/components/schemas/ObjectImageListType' + required: true + responses: + 200: + description: "The smart identification data has been successfully sent +to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + +post: + +``` + +``` + +tags: + - OnsiteOverhaul-SMAT +summary: push an on-site overhaul maintenance job to the designated SMAT +operationId: pushMaintenanceJob +requestBody: + description: the content of overhaul maintenance job needs to be pushed +to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + overhaulTaskList: + type: array + items: + $ref: 'M.3164.3-Common.yaml#/components/schemas/OnsiteOverhaulTask_C' + required: true + responses: + 200: + description: "The overhaul maintenance job has been successfully sent +to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/pushOverhaulGuidanceInfo: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + - $ref: '#/components/parameters/taskID' + +post: + +``` + +``` + +tags: + - OnsiteOverhaul-SMAT +summary: push the on-site overhaul guidance information to the designated +SMAT +operationId: pushOverhaulGuidanceInfo +requestBody: + description: guidance information for on-site overhaul tasks needs to +be pushed to the designated the SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + guidanceInfo: + type: string + required: true +responses: + 200: + description: "The on-site overhaul guidance information has been +successfully sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + + post: + tags: + - OnsiteTroubleShooting-SMAT + summary: push the information of on-site troubleshooting tasks to the +designated SMAT + +``` + +``` + +operationId: pushTroubleShootingTasks +requestBody: + description: the content of on-site troubleshooting tasks needs to be +pushed to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + troubleShootingTaskList: + type: array + items: + $ref: 'M.3164.3-Common.yaml#/components/schemas/OnsiteTroubleShootingTask_C' + required: true + responses: + 200: + description: "The on-site troubleshooting tasks have been successfully +sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C={taskID}/pushTroubleShootingGuidance: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteTroubleShooting-SMAT + summary: push the troubleShooting guidance information to the SMAT + +``` + +``` + +operationId: pushTroubleShootingGuidance +requestBody: + description: guidance information for on-site troubleShooting tasks +needs to be pushed to the designated SMAT + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + operationGuidanceInfo: + type: string + required: true +responses: + 200: + description: "The on-site troubleShooting guidance information has +been successfully sent to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C={taskID}/pushTroubleAnalysisResult: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteTroubleShooting-SMAT + summary: push the trouble analysis result to the SMAT + operationId: pushTroubleAnalysisResult + requestBody: + +``` + +``` + +description: the content of on-site trouble analysis result needs to be +pushed to the designated SMAT +content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + troubleTypeID: + type: string + format: uri + causeList: + type: array + items: + $ref: '#/components/schemas/CauseListType' + imagesList: + type: array + items: + $ref: '#/components/schemas/ImagesListType' + required: true +responses: + 200: + description: "The trouble analysis result has been successfully sent +to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +/ServiceActivationInfo_C={serviceActInfoID}/ServiceActivationTask_C: +parameters: +- $ref: '#/components/parameters/serviceActInfoID' + +post: +tags: + +``` + +``` + +- ServiceActivation-SMAT + summary: push the information of the service activation job to the SMAT + operationId: pushServiceActJob + requestBody: + description: the content of service activation jobs list needs to be +pushed to the designated SMAT. + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + serviceActTaskList: + type: array + items: + $ref: 'M.3164.3-Common.yaml#/components/schemas/ServiceActivationTask_C' + required: true + responses: + 200: + description: "The service activation job has been successfully sent +to the SMAT" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 500: + description: "An internal problem occurs" + content: {} + +components: + schemas: + OpStatusType: + type: object + properties: + opStatus: + type: string + enum: + - successful + +``` + +``` +- failed + +ObjectImageListType: + type: array + items: + $ref: '#/components/schemas/ObjectImageType' + +ObjectImageType: + type: object + properties: + objectID: + type: string + image: + type: string + format: byte + +CauseListType: + type: array + items: + type: string + +ImagesListType: + type: array + items: + type: string + format: byte + +parameters: + patrolInfoID: + name: patrolInfoID + in: path + required: true + description: ID of the on-site patrol task information + schema: + type: string + + taskID: + name: taskID + in: path + description: ID of an on-site patrol task, or an on-site overhaul task, +or an on-site troubleshooting task, or a service activation task +``` + +``` + + required: true + schema: + type: string + +overhaulInfoID: + name: overhaulInfoID + in: path + description: ID of the on-site overhaul maintenance job information + required: true + schema: + type: string + +troubleShootingInfoID: + name: troubleShootingInfoID + in: path + description: ID of the on-site troubleshooting task information + required: true + schema: + type: string + +serviceActInfoID: + name: serviceActInfoID + in: path + description: ID of the service activation job information + required: true + schema: + type: string + +``` + +### A.3 YAML schema definition for interface operations provided by TSMS + +Table A.3 provides the complete definition of interface operations provided by TSMS. The common IOCs and common data types used in this clause are defined in file of M.3164.3-Common.yaml. The definitions in Table A.3 are independently implemented in the M.3164.3-A.3.yaml file. + +**Table A.3 – Complete definition of interface operations provided by TSMS +(M.3164.3-A.3.yaml)** + +``` + +openapi: 3.0.0 +info: + title: Interface Operations provided by TSMS + description: This is the formal Definitions of the REST-based interface +operations provided by TSMS + termsOfService: https://www.itu.int/en/ITU-T/about/Pages/default.aspx + contact: + email: zhangzmx8848@gmail.com + +``` + +``` + +license: + name: Apache 2.0 + url: http://www.apache.org/licenses/LICENSE-2.0.html + version: 1.0.0 +tags: + - name: PatrolTask-TSMS + - name: OnsiteOverhaul-TSMS + - name: OnsiteTroubleShooting-TSMS + - name: ServiceActivation-TSMS + +paths: + +/OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/findSmartIDData +: + parameters: + - $ref: '#/components/parameters/patrolInfoID' + - $ref: '#/components/parameters/taskID' + - $ref: '#/components/parameters/SMAT_ID' + + get: + tags: + - PatrolTask-TSMS + summary: get smart identification data of the patrol information from the +TSMS + operationId: findSmartIDData + responses: + 200: + description: "The smart identification data is successfully returned +from the TSMS" + content: + application/json: + schema: + type: object + properties: + opStatus: + $ref: '#/components/schemas/OpStatusType' + smartIdentificationData: + type: array + items: + $ref: '#/components/schemas/ObjectImageListType' + 400: + description: "Input parameters invalid" + content: {} + +``` + +``` + +404: + description: "Patrol info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + +500: + description: "Internal Server Error" + content: {} + +/OnsitePatrolInfo_C={patrolInfoID}/OnsitePatrolTask_C={taskID}/OnsitePatrolRecord_C: + parameters: + - $ref: '#/components/parameters/patrolInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - PatrolTask-TSMS + summary: upload a patrol record to the TSMS + operationId: uploadPatrolRecord + requestBody: + description: the content of patrol record needs to be uploaded to the +TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + patrolRecord: + type: array + items: + $ref: 'M.3164.3- +Common.yaml#/components/schemas/OnsitePatrolRecord_C' + required: true + responses: + 200: + description: "The patrol record information is successfully received +by the TSMS" + content: + +``` + +``` + + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' +400: + description: "Input parameters invalid" + content: {} +404: + description: "patrol Info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' +500: + description: "Internal Server Error" + content: {} + +/OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/uploadOverhaulProcessRecord: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteOverhaul-TSMS + summary: upload an overhaul process record to the TSMS + operationId: uploadOverhaulProcessRecord + requestBody: + description: the content of the overhaul process record needs to be uploaded to the TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + overhaulExecutor: + type: string + status: + type: string + enum: + +``` + +``` + + - normal + - abnormal + - notCheck + timeInfo: + type: string + orderID: + type: string + recordInfo: + type: string + required: true + responses: + 200: + description: "The overhaul process record information is successfully +received by the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 404: + description: "overhaul info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +/OnsiteOverhaulInfo_C={overhaulInfoID}/OnsiteOverhaulTask_C={taskID}/requestFo +rRemoteAssistance: + parameters: + - $ref: '#/components/parameters/overhaulInfoID' + - $ref: '#/components/parameters/taskID' + - $ref: '#/components/parameters/SMAT_ID' + - $ref: '#/components/parameters/requestDes' + + get: + tags: + - OnsiteOverhaul-TSMS + +``` + +``` + +summary: request remote assistance from the TSMS for an overhaul task +operationId: requestForOverhaulRemoteAssis +responses: + 200: + description: "The remote assistance information is successfully +received by the TSMS" + content: + application/json: + schema: + type: object + properties: + opStatus: + $ref: '#/components/schemas/OpStatusType' + expertInfoList: + type: array + items: + $ref: 'M.3164.3-Common.yaml#/components/schemas/Expert_C' + assistanceLink: + type: string + 400: + description: "Input parameters invalid" + content: {} + 404: + description: "overhaul info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +/OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C={taskID}/uploadTroubleShootingResult: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - OnsiteTroubleShooting-TSMS + +``` + +``` + +summary: upload the troubleshooting result to the TSMS +operationId: uploadTroubleShootingResult +requestBody: + description: the content of troubleShooting result needs to be uploaded +to the TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + troubleShootingExecutor: + type: string + status: + type: string + enum: + - normal + - abnormal + - notCheck + timeInfo: + type: string + orderID: + type: string + troubleTypeID: + type: string + format: uri + troubleshootingResult: + type: string + required: true +responses: + 200: + description: "The trouble shooting result record information is +successfully received by the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 404: + +``` + +``` + + description: "troubleShooting Info ID or SMAT ID cannot be found in +the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +/OnsiteTroubleShootingInfo_C={troubleShootingInfoID}/OnsiteTroubleShootingTask +_C={taskID}/requestForRemoteAssistance: + parameters: + - $ref: '#/components/parameters/troubleShootingInfoID' + - $ref: '#/components/parameters/taskID' + - $ref: '#/components/parameters/SMAT_ID' + - $ref: '#/components/parameters/requestDes' + + get: + tags: + - OnsiteTroubleShooting-TSMS + summary: request remote assistance from the TSMS for a troubleshooting +task + operationId: requestForTroubleShootingRemoteAssis + responses: + 201: + description: "The remote assistance information is successfully +received by the TSMS" + content: + application/json: + schema: + type: object + properties: + opStatus: + $ref: '#/components/schemas/OpStatusType' + expertInfoList: + type: array + items: + $ref: 'M.3164.3- +Common.yaml#/components/schemas/Expert_C' + assistanceLink: + type: string + + 400: + +``` + +``` + +description: "Input parameters invalid" +content: {} +404: + description: "Patrol info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' +500: + description: "Internal Server Error" + content: {} + +/ServiceActivationInfo_C={serviceActInfoID}/ServiceActivationTask_C={taskID}/ServiceActivationRecord_C: + parameters: + - $ref: '#/components/parameters/serviceActInfoID' + - $ref: '#/components/parameters/taskID' + + post: + tags: + - ServiceActivation-TSMS + summary: upload a service activation record to the TSMS + operationId: uploadServiceActivationRecord + requestBody: + description: the content of service activation record needs to be uploaded to the TSMS + content: + application/json: + schema: + type: object + properties: + SMAT_ID: + type: string + serviceActivationRecord: + type: array + items: + $ref: 'M.3164.3-Common.yaml#/components/schemas/ServiceActivationRecord_C' + required: true + responses: + 200: + +``` + +``` + + description: "The service activation record information is +successfully received by the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/OpStatusType' + 400: + description: "Input parameters invalid" + content: {} + 404: + description: "Patrol info ID or SMAT ID cannot be found in the TSMS" + content: + application/json: + schema: + $ref: '#/components/schemas/InfoNotExist' + 500: + description: "Internal Server Error" + content: {} + +components: + schemas: + OpStatusType: + type: object + properties: + opStatus: + type: string + enum: + - successful + - failed + + ObjectImageListType: + type: array + items: + $ref: '#/components/schemas/ObjectImageType' + + ObjectImageType: + type: object + properties: + objectID: + type: string + image: + type: string + +``` + +``` +format: byte + +InfoNotExist: + type: object + properties: + code: + type: string + enum: + - no_info_ID + - no_SMAT_ID + - no_task_ID + +parameters: + patrolInfoID: + name: patrolInfoID + in: path + description: ID of the on-site patrol task information + required: true + schema: + type: string + + taskID: + name: taskID + in: path + description: ID of an on-site patrol task, or an on-site overhaul task, +or an on-site troubleshooting task, or a service activation task + required: true + schema: + type: string + + SMAT_ID: + name: SMAT_ID + in: query + description: ID of the designated SMAT + required: true + schema: + type: string + + overhaulInfoID: + name: overhaulInfoID + in: path + description: ID of the on-site overhaul maintenance job information +``` + +``` + required: true + schema: + type: string + +requestDes: + name: requestDes + in: query + description: text description of the request + required: true + schema: + type: string + +troubleShootingInfoID: + name: troubleShootingInfoID + in: path + description: ID of the on-site troubleshooting task information + required: true + schema: + type: string + +serviceActInfoID: + name: serviceActInfoID + in: path + description: ID of the service activation job information + required: true + schema: + type: string +``` + +# Bibliography + +- [b-ITU-T M.3040] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. +- [b-ITU-T M.3160] Recommendation ITU-T M.3160 (2008), *Generic, protocol-neutral management information model*. +- [b-ITU-T M.3364] Recommendation ITU-T M.3364 (2020), *Requirements for on-site telecommunication smart maintenance management function*. +- [b-OAI-OAS3] OAI-OAS3 (2017), OpenAPI Initiative, *OpenAPI Specification Version 3.0.0*. + + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba7ad9f0e07d256e81672048589e36f0d321a5a8 --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d66728c1ffd2ce1c397f9396727c2ef09d86a72bdc55fa3aae8532880050bb77 +size 48620 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32c8a97342366c44aa05cf5ab66de54fb7714ce2 --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa03f71f9c64d5e76ddaf44cdd25768fc57e350eb1fe2ee54a2a6222c7a92caa +size 23395 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98995425b38bddeeb010dde89c4e374de91a67c1 --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9d071494aeef627b3738e4aa53b763f9e5f65a1ec3643b0b2d18aadb76c9201 +size 54088 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..912acc65ceac332403fb53433443bab9b50faa9f --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9b9db6a970b2a1bd37495ad2405164f618c0035e61ed5dba0604e076bb1dac +size 25842 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f15fc90a9ed4fd214bde86b927a7c5bf77399c91 --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a05d2b6c3eae7379f9d074f73612d618985be13d0109c8e4cd9b599bda5c285 +size 42941 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ead6187fa3991009f13bf4cf1f3eca6b177a57a --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8097b133daae38db7827c519f68ad92a88128732f6256ad4feeee57894ba56c +size 37051 diff --git a/marked/M/T-REC-M.3166.1-202510-I_PDF-E/raw.md b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2a9ee037361d726a16037e091008ed75a50e5046 --- /dev/null +++ b/marked/M/T-REC-M.3166.1-202510-I_PDF-E/raw.md @@ -0,0 +1,874 @@ + + +# Recommendation**ITU-T M.3166.1 (10/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +# **Interface for a blockchain management system – Protocol neutral requirements** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3166.1 + +# Interface for a blockchain management system – Protocol neutral requirements + +## Summary + +Recommendation ITU-T M.3166.1 proposes the protocol-neutral requirements for the management interface between a blockchain management system and blockchain systems. It defines the interface's position and specifies management requirements across key functional areas, including configuration management, performance management, fault management, and log management. This Recommendation aims to standardize the design, development, and application of blockchain system management interfaces to ensure efficient operation, monitoring, and troubleshooting. Key features include querying and modifying configurations, creating and managing performance measurement jobs, handling alarms, and managing logs. This Recommendation also provides detailed use cases, definitions, and references to existing ITU-T Recommendations, ensuring alignment with broader telecommunications management standards. This series of Recommendations is intended to enhance the stability, transparency, and interoperability of blockchain systems in diverse applications. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3166.1 | 2025-10-14 | 2 | 11.1002/1000/16466 | + +## Keywords + +Blockchain node, blockchain system, distributed ledger, interface protocol. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Convention..... | 3 | +| 6 Overview for management interface of blockchain system ..... | 3 | +| 7 Business level requirements ..... | 4 | +| 7.1 Requirements ..... | 4 | +| 7.2 Actor roles ..... | 5 | +| 7.3 Telecommunication resources ..... | 5 | +| 7.4 High level use case diagrams ..... | 5 | +| 8 Specification-level requirements ..... | 7 | +| 8.1 Requirements ..... | 7 | +| 8.2 Actor roles ..... | 7 | +| 8.3 Telecommunication resources ..... | 7 | +| 8.4 Use cases ..... | 7 | +| Bibliography..... | 23 | + + + +# Recommendation ITU-T M.3166.1 + +## Interface for a blockchain management system – Protocol neutral requirements + +# 1 Scope + +This Recommendation specifies the position and requirements for the management interface of blockchain management system. The main contents of this Recommendation include the definition and description of the interface position, the definition and description of the requirements for the management interface. + +This Recommendation is applicable to the design, development and application of blockchain system management interfaces. + +The information and interactions provided in this Recommendation follow [ITU-T M.3020] management interface specification methodology in the interface requirements phase in a protocol-neutral manner. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [[ITU-T F.751.0](#)] Recommendation ITU-T F.751.0 (2020), *Requirements for distributed ledger systems*. +- [[ITU-T M.3020](#)] Recommendation ITU-T M.3020 (2023), *Management interface specification methodology*. +- [[ITU-T M.3366](#)] Recommendation ITU-T M.3366 (2023), *Requirements for management of blockchain systems*. +- [[ITU-T M.3700](#)] Recommendation ITU-T M.3700 (2010), *Common management services – Object management – Protocol neutral requirements and analysis*. +- [[ITU-T M.3703](#)] Recommendation ITU-T M.3703 (2010), *Common management services – Alarm management – Protocol neutral requirements and analysis*. +- [[ITU-T M.3704](#)] Recommendation ITU-T M.3704 (2010), *Common management service – Performance management – Protocol neutral requirements and analysis*. +- [[ITU-T M.3705](#)] Recommendation ITU-T M.3705 (2013), *Common management services – Log management – Protocol neutral requirements and analysis*. +- [[ITU-T X.1034](#)] Recommendation ITU-T X.1034 (2011), *Guidelines on extensible authentication protocol based authentication and key management in a data communication network*. +- [[ITU-T X.1400](#)] Recommendation ITU-T X.1400 (2020), *Terms and definitions for distributed ledger technology*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 blockchain** [ITU-T X.1400]: A type of distributed ledger which is composed of digitally recorded data arranged as a successively growing chain of blocks with each block cryptographically linked and hardened against tampering and revision. + +**3.1.2 blockchain system** [b-ISO/DIS 22739]: A system that implements a blockchain. + +**3.1.3 consensus** [ITU-T X.1400]: Agreement that a set of transactions is valid. + +**3.1.4 node** [ITU-T X.1400]: Device or process that participates in a distributed ledger network. + +NOTE – Nodes can store a complete or partial replica of the distributed ledger. + +**3.1.5 smart contract** [ITU-T X.1400]: A program written on the distributed ledger system which encodes the rules for specific types of distributed ledger system transactions in a way that can be validated, and triggered by specific conditions. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-------------------------------------| +| BGP | Border Gateway Protocol | +| BTF | Byzantine Fault Tolerance | +| C/S | Client/Server | +| CM | Configuration Management | +| DLT | Distributed Ledger Technology | +| DPoS | Delegated Proof of Stake | +| FM | Fault Management | +| GPU | Graphics Processing Unit | +| HTTP | HyperText Transfer Protocol | +| I/O | Input/Output | +| ID | Identifier | +| JVM | Java Virtual Machine | +| LM | Log Management | +| M | Mandatory | +| O | Optional | +| OOM | Out Of Memory | +| P2P | Peer-to-Peer | +| PBFT | Practical Byzantine Fault Tolerance | +| PM | Performance Management | +| POS | Proof of Stake | + +| | | +|--------|-----------------------------------------| +| POW | Proof of Work | +| SR-IOV | Single Root Input/Output Virtualization | +| TPS | Transactions Per Second | +| vCPU | Virtual Central Processing Unit | + +# 5 Convention + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +For the qualifiers of a use case in the Specification-level requirements, "M" standards for Mandatory, and "O" standards for Optional. + +# 6 Overview for management interface of blockchain system + +Blockchain enables large groups of nodes in a distributed ledger system to reach an agreement and record information without the need for a central authority, as specified in [ITU-T X.1400]. Blockchain systems may have problems such as node data being out of synchronization, smart contract disputes, consensus node anomalies, cross-chain inconsistency, etc. + +Among them, the blockchain system is a comprehensive operating platform that manages the operation of the blockchain, consensus mechanism, data storage, network communication, etc. The functions of the blockchain system involve node management, transaction verification, block generation, consensus algorithm execution, smart contract execution, data consistency assurance and many other aspects. The blockchain is the data storage mechanism inside the blockchain system, which is mainly responsible for the storage, verification and transmission of data. The blockchain itself does not care about the processing of transactions or communication between nodes but instead focuses on providing a secure and transparent distributed ledger. + +[ITU-T M.3366] gives the requirements for the management of blockchain systems. The interface position for a blockchain management system is shown in Figure 1. The blockchain system has some distributed ledger technology (DLT) nodes networked together. The blockchain management system fulfils the management function of the blockchain system and manages the blockchain system through the management interface. + +![Diagram showing the interface position for a blockchain management system. A 'Blockchain management system' box is at the top, connected by a double-headed arrow labeled 'Management interface' to a 'Blockchain system' box below. The 'Blockchain system' box contains three 'Node' boxes connected by dashed lines in a ring.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph TD + BMS[Blockchain management system] <--> |Management interface| BS[Blockchain system] + subgraph BS + N1[Node] -.- N2[Node] + N2 -.- N3[Node] + N3 -.- N1 + end + M3166125[M.3166.1(25)] + +``` + +Diagram showing the interface position for a blockchain management system. A 'Blockchain management system' box is at the top, connected by a double-headed arrow labeled 'Management interface' to a 'Blockchain system' box below. The 'Blockchain system' box contains three 'Node' boxes connected by dashed lines in a ring. + +**Figure 1 – The interface position for blockchain management system** + +# 7 Business level requirements + +## 7.1 Requirements + +Managing the blockchain system through the management interface is one of the key functions of blockchain system management. The blockchain management system function is used to manage the blockchain system through the management interface. These interface requirements can be grouped into the following aspects: + +- Configuration management, e.g., including querying configuration, modifying configuration; +- Performance management, e.g., including creating measurement job, querying measurement job, suspending measurement job, resuming measurement job, stopping measurement job; +- Fault management, e.g., including creating alarm filter, querying alarm filter, modifying alarm filter, deleting alarm filter, alarm notification, notification of alarm change, getting alarm list, clearing alarm; +- Log management, e.g., including creating log, modifying log criteria, querying log, delete log, backup log. + +### 7.1.1 Configuration management + +The agent is required to provide the following functions to the manager to: + +- REQ-CM-FUN-01 Query the configuration of the blockchain system, including topology, ledger, account, smart contract, etc. +- REQ-CM-FUN-02 Modify the configuration of the blockchain system, including node, block, consensus, etc. + +### 7.1.2 Performance management + +The manager shall be able to request the agent to: + +- REQ-PM-FUN-01 Create an instance of the blockchain system performance measurement job. +- REQ-PM-FUN-02 Query an instance of the blockchain system performance measurement job. +- REQ-PM-FUN-03 Suspend an instance of the blockchain system performance measurement job. +- REQ-PM-FUN-04 Resume an instance of the blockchain system performance measurement job. + +- REQ-PM-FUN-05 Stop an instance of the blockchain system performance measurement job. +- REQ-PM-FUN-06 Query the performance data of the blockchain system performance measurement job. + +### 7.1.3 Fault management (FM) + +The manager shall be able to request the agent to: + +- REQ-FM-FUN-01 Create a blockchain system operation alarm filter to send an alarm notification when the monitoring result triggers the alarm filter. +- REQ-FM-FUN-02 Query a blockchain system operation alarm filter. +- REQ-FM-FUN-03 Modify a blockchain system operation alarm filter. +- REQ-FM-FUN-04 Delete a blockchain system alarm filter. +- REQ-FM-FUN-05 Send a blockchain system alarm notification. +- REQ-FM-FUN-06 Notify a blockchain system alarm change. +- REQ-FM-FUN-07 Query a blockchain system alarm information. +- REQ-FM-FUN-08 Clear a blockchain system alarm information. + +### 7.1.4 Log management (LM) + +The manager shall be able to request the agent to: + +- REQ-LM-FUN-01 Create a log collection task to collect the operation logs of the blockchain system. +- REQ-LM-FUN-02 Modify a log collection task to activate or deactivate a log collection task. +- REQ-LM-FUN-03 Query a log collection task. +- REQ-LM-FUN-04 Delete a log collection task. +- REQ-LM-FUN-05 Query a log object in order to analyse the relevant situation. +- REQ-LM-FUN-06 Backup a log object in the local storage in the node in blockchain system. + +## 7.2 Actor roles + +The capabilities described in this Recommendation are available and relevant to all agents and managers. + +Agents refer to a piece of software or service that performs certain operations or tasks on behalf of a user. These agents in this Recommendation are the blockchain system. Managers are the blockchain management system responsible for monitoring and configuring the blockchain system. + +## 7.3 Telecommunication resources + +The management functionality is applicable to all types of telecommunication resources. + +## 7.4 High level use case diagrams + +The first overview use-case diagram in Figure 2 shows the overall interaction of all management functions. + +![UML Use Case Diagram for Figure 2: The management function set. The diagram shows a 'Manager' actor connected to a 'Blockchain management function set' use case. This use case includes five other use cases via '<>' relationships: 'Configuration management function set', 'Performance management function set', 'Fault management function set', 'Log management function set', and an unlabeled use case at the bottom. The diagram is labeled M.3166.1(25).](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +usecaseDiagram + actor Manager + usecase Blockchain_management_function_set [Blockchain management function set] + usecase Configuration_management_function_set [Configuration management function set] + usecase Performance_management_function_set [Performance management function set] + usecase Fault_management_function_set [Fault management function set] + usecase Log_management_function_set [Log management function set] + usecase Unlabeled_Use_Case [ ] + + Manager --> Blockchain_management_function_set + Blockchain_management_function_set -.->|<>| Configuration_management_function_set + Blockchain_management_function_set -.->|<>| Performance_management_function_set + Blockchain_management_function_set -.->|<>| Fault_management_function_set + Blockchain_management_function_set -.->|<>| Log_management_function_set + Blockchain_management_function_set -.->|<>| Unlabeled_Use_Case + +``` + +UML Use Case Diagram for Figure 2: The management function set. The diagram shows a 'Manager' actor connected to a 'Blockchain management function set' use case. This use case includes five other use cases via '<>' relationships: 'Configuration management function set', 'Performance management function set', 'Fault management function set', 'Log management function set', and an unlabeled use case at the bottom. The diagram is labeled M.3166.1(25). + +**Figure 2 – The management function set** + +Figure 3 shows the functions involved in the configuration management function set. + +![UML Use Case Diagram for Figure 3: The configuration management function set. The diagram shows a 'Manager' actor connected to a 'Configuration management function set' use case. This use case includes two other use cases via '<>' relationships: 'Query configuration' and 'Modify configuration'. The diagram is labeled M.3166.1(25).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +usecaseDiagram + actor Manager + usecase Configuration_management_function_set [Configuration management function set] + usecase Query_configuration [Query configuration] + usecase Modify_configuration [Modify configuration] + + Manager --> Configuration_management_function_set + Configuration_management_function_set -.->|<>| Query_configuration + Configuration_management_function_set -.->|<>| Modify_configuration + +``` + +UML Use Case Diagram for Figure 3: The configuration management function set. The diagram shows a 'Manager' actor connected to a 'Configuration management function set' use case. This use case includes two other use cases via '<>' relationships: 'Query configuration' and 'Modify configuration'. The diagram is labeled M.3166.1(25). + +**Figure 3 – The configuration management function set** + +Figure 4 shows the functions involved in the performance management function set. + +![UML Use Case Diagram for Figure 4: The performance management function set. The diagram shows a 'Manager' actor connected to a 'Performance management function set' use case. This use case includes six other use cases via '<>' relationships: 'Create measurement job', 'Query measurement job', 'Suspend measurement job', 'Resume measurement job', 'Stop measurement job', and 'Query performance information'. The diagram is labeled M.3166.1(25).](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +usecaseDiagram + actor Manager + usecase Performance_management_function_set [Performance management function set] + usecase Create_measurement_job [Create measurement job] + usecase Query_measurement_job [Query measurement job] + usecase Suspend_measurement_job [Suspend measurement job] + usecase Resume_measurement_job [Resume measurement job] + usecase Stop_measurement_job [Stop measurement job] + usecase Query_performance_information [Query performance information] + + Manager --> Performance_management_function_set + Performance_management_function_set -.->|<>| Create_measurement_job + Performance_management_function_set -.->|<>| Query_measurement_job + Performance_management_function_set -.->|<>| Suspend_measurement_job + Performance_management_function_set -.->|<>| Resume_measurement_job + Performance_management_function_set -.->|<>| Stop_measurement_job + Performance_management_function_set -.->|<>| Query_performance_information + +``` + +UML Use Case Diagram for Figure 4: The performance management function set. The diagram shows a 'Manager' actor connected to a 'Performance management function set' use case. This use case includes six other use cases via '<>' relationships: 'Create measurement job', 'Query measurement job', 'Suspend measurement job', 'Resume measurement job', 'Stop measurement job', and 'Query performance information'. The diagram is labeled M.3166.1(25). + +**Figure 4 – The performance management function set** + +Figure 5 shows the functions involved in the fault management function set. + +![UML Use Case Diagram for the Fault Management Function Set](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +A UML Use Case Diagram for the Fault Management Function Set. At the top center is an oval labeled "Fault management function set". To its left is an actor icon labeled "Manager" with a solid arrow pointing to the central oval. Below the central oval are eight smaller ovals, each connected to it by a dashed arrow labeled "<>". These ovals are: "Create alarm policy", "Query alarm policy", "Modify alarm policy", "Delete alarm filter", "Report alarm notification", "Notify alarm change", "Get alarm list", and "Clear alarm". The text "M.3166.1(25)" is located in the bottom right corner of the diagram area. + +UML Use Case Diagram for the Fault Management Function Set + +**Figure 5 – The fault management function set** + +Figure 6 shows the functions involved in the log management function set. + +![UML Use Case Diagram for the Log Management Function Set](cab0834804fb031b43865554cc8d06ab_img.jpg) + +A UML Use Case Diagram for the Log Management Function Set. At the top center is an oval labeled "Log management function set". To its left is an actor icon labeled "Manager" with a solid arrow pointing to the central oval. Below the central oval are seven smaller ovals, each connected to it by a dashed arrow labeled "<>". These ovals are: "Create log collection task", "Modify log collection task", "Query log collection task", "Delete log collection task", "Backup log", "Query log", and "Query log collection task" (repeated). The text "M.3166.1(25)" is located in the bottom right corner of the diagram area. + +UML Use Case Diagram for the Log Management Function Set + +**Figure 6 – The log management function set** + +# **8 Specification-level requirements** + +## **8.1 Requirements** + +There are no specification-level requirements. + +## **8.2 Actor roles** + +See clause 7.2. + +## **8.3 Telecommunication resources** + +See clause 7.3. + +## **8.4 Use cases** + +The general exceptions (e.g., communication error, processing error) related to all use cases will not be described in the following use cases and will only be handled in the design phase. + +### 8.4.1 Configuration management + +#### 8.4.1.1 Query configuration (M) + +This use case is about the operation of querying the relevant configurations in the blockchain system. The contents mainly refer to clause 6.1.4.1 of [ITU-T M.3700]. + +NOTE 1 – The manager can request the agent to query the parameter values of the configuration of the blockchain system through the management interface, including topology, node, block, consensus, ledger, account, smart contract, etc. Please see Table 1 for the detailed requirements. + +**Table 1 – Configuration management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|----------|----------------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| topology | node distribution | deployment location | Specify the physical or logical distribution of different types of nodes in a blockchain network. | +| | | connection mode | Specify how data is transmitted over the network. Common connection methods include peer-to-peer (P2P) connections, client server (C/S) connections, and hybrid connections. | +| | network architecture | – | Specify the overall architecture of blockchain networks, including centralized, decentralized, and hybrid structures. | +| | link configuration | connection types | Specify how data is transmitted between nodes, with common connection types including hypertext transfer protocol (HTTP) and WebSocket. | +| | | bandwidth | Specify the measurement of the ability or capacity of a communication link or network to transmit data in a unit of time. | +| node | node type | – | Specify the differentiation of nodes based on their functional roles within the network, resource consumption, data storage capacity, and level of participation. A distributed ledger system is recommended to support different node types, e.g., light, full and full archiving [ITU-T F.751.0]. | +| | node identifier (ID) | – | Specify the unique identifier for precise node differentiation in a blockchain network. | +| | node status | online status | Specify whether the node is currently connected and active in the network. | +| | | synchronization indicator | Specify whether the node has the latest transaction records and block information, ensuring data accuracy and consistency. | + +**Table 1 – Configuration management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|---------------------|--------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | consensus participation status | Specify whether the node is eligible to participate in transaction verification and new block generation in the blockchain network. | +| | resource configuration | calculating capacity | Specify the computing power required for nodes to process blockchain transactions and consensus algorithms. | +| | | storage | Specify the blockchain data volume that a node can retain, including historical transaction records, block information, and metadata. | +| block | block size | – | Specify how much transaction data a single block can store. | +| | time interval | – | Specify the transaction confirmation speed of blockchain. | +| | branching strategy | – | Specify how to handle fork situations and determine the selection strategy for inconsistent blocks in the chain. | +| | validation rules | Hash consistence | Specify whether the currently calculated hash value of the block matches the hash value recorded in the blockchain. | +| | | transaction verification | Specify whether the transaction has successfully passed all critical security and integrity checks. | +| consensus mechanism | consensus algorithm type | – | Specify consensus mechanisms suitable for application scenarios, such as proof of work (POW), proof of stake (POS), practical byzantine fault tolerance (PBFT), delegated proof of stake (DPoS), etc. | +| | consensus rule | – | Specify the behaviour rules of each node in the consensus process, such as voting, verification, block packing, and other operations. | +| | fault tolerance | – | Specify the fault-tolerant mechanism used. | +| ledger | ledger format | – | Specify the data storage format for the ledger. | +| | synchronous mode | – | Specify how to synchronize ledger data between nodes to ensure that all nodes hold consistent copies of the ledger. | +| | backup frequency | – | Specify the backup frequency for ledger data to prevent data loss. | + +**Table 1 – Configuration management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|-----------------|--------------------|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| account | account type | – | Specify functions and operational scope, such as regular accounts, smart contract accounts, etc. | +| | key management | public key management policy | Specify policies for generating, storing, and backing up public keys. See [ITU-T X.1034] for more details. | +| | | private key management policy | Specify policies for generating, storing, and backing up private keys. See [ITU-T X.1034]. | +| | permission control | – | Specify the operational permissions for different accounts, such as which accounts can initiate transactions, call smart contracts, etc. | +| smart contracts | writing language | – | Specify the language used to write smart contracts. | +| | deployment mode | publication method | Specify how to publish contracts on the blockchain. | +| | | Update indicator | Specify whether it is allowed to upgrade the contract or not. | +| | permission control | – | Specify which accounts can call specific functions of the contract. | +| | invocation mode | – | Specify supported contract calling methods, including direct calling, event listening, etc. | + +NOTE 2 – The traceability of this use case is REQ-CM-FUN-01. + +#### 8.4.1.2 Modify configuration (O) + +This use case is about the operation of modifying the relevant configurations in the blockchain system. The content mainly refers to clause 6.1.4.5 of [ITU-T M.3700]. + +NOTE 1 – The manager is recommended to request an agent to modify the configuration of the blockchain system, including node, block, consensus, etc. + +NOTE 2 – The traceability of this use case is REQ-CM-FUN-02. + +### 8.4.2 performance management + +#### 8.4.2.1 Create measurement job (M) + +This use case is about the operation of creating a performance measurement job in the blockchain system. the content mainly refers to clause 6.3.4.1 of [ITU-T M.3704]. + +NOTE 1 – The manager requests an agent to create a performance measurement job of the blockchain system, mainly about blockchain systems, blocks, peer-to-peer networks, nodes, node operating environments, and transactions, etc. Please see Table 2 for the detailed requirements. + +**Table 2 – Performance management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|----------------------|---------------------------------|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| blockchain systems | efficiency | throughput | Specify the number of transactions per second (TPS) that a blockchain system can process per second, which is the basis for measuring the processing power of the system. | +| | | latency | Specify the period from the time a transaction is initiated to the time it is confirmed. | +| block | block generation time | – | Specify the period it takes for a new block is created and added to the blockchain. Different consensus mechanisms (such as PoW, PoS, etc.) affect the timing of block generation. | +| | block size | – | Specify how many transactions each block can hold, and the size of the block directly affects the transaction throughput. | +| | block validation time | – | Specify the validation period for the node to validate the newly generated block. | +| | chain reorganization efficiency | reorganization time | Specify how long it takes the system to complete chain rollback and new block reorganization after detecting a change in the main chain switch or fork priority. | +| | | reorganization depth | Specify the depth of blocks that need to be rolled back when chain reorganization occurs, i.e. the number of blocks that need to be revoked and reorganized. | +| | | transaction retention rate | Specify how many previously confirmed transactions can be repackaged into the new main chain during the chain reorganization process. | +| Peer-to-peer network | network topology connection | node connection change rate | Specify the frequency of node connections being established or disconnected within a unit of time (e.g., times per second), used to measure the intensity of network topology fluctuations. | +| | | topology convergence time | Specify the self-organizing ability of the network. The time (in milliseconds) required for the network to reach a stable connection state after a new node is added. | + +**Table 2 – Performance management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|----------|-------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | node discovery and connection speed | effective neighbour discovery ratio | Specify the proportion of high-quality neighbouring nodes that meet the delay/bandwidth requirements among the total number of theoretically possible connected nodes. | +| | | connection establishment speed | Specify the time required to establish a stable communication connection. | +| | network latency and bandwidth | network latency | Specify the time it takes for data to be transmitted from one node to another, usually in milliseconds (ms), which is an important performance indicator to measure the efficiency and real-time performance of network communication. | +| | | network bandwidth | Specify the amount of data that can be transferred between nodes per unit time, usually measured in Mbit/s (megabits per second) or Gbit/s (gigabits per second), which is one of the key performance indicators to measure the network's transmission capacity and data processing efficiency. | +| node | node processing capacity | processing throughput | Specify the measurement of the number of transactions or data that a node is able to process per unit time, usually expressed as transactions per second (TPS) or operations. | +| | | latency | Specify the time required by a node after receiving a request or transaction from the start of processing to the completion of the response, usually measured in milliseconds (ms). | +| | | computational resource consumption | Specify computing resources consumed by a node during tasks, including CPU usage, memory usage, and disk input/output (I/O). | +| | node synchronization time | – | Specify the time between a node joining the network and synchronizing the full blockchain data. Longer synchronization times can cause delays in generating new blocks. | +| | node load balancing | – | Specify what kind of load distribution policy the node uses. | + +**Table 2 – Performance management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|-----------------------|-------------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operating environment | hardware resource usage | CPU utilization | Specify the percentage of CPU resources consumed by a node during its running, usually expressed as a percentage. | +| | | memory utilization | Specify the percentage of memory used by a node during operation, usually expressed as a percentage. | +| | | disk I/O utilization | Specify the disk I/O wait time for a node to read and write data. | +| | operating system performance | system load | Specify the load of the operating system in a specific period, which reflects the ratio of the number of tasks running on the system to the CPU processing capacity. | +| | | process scheduling efficiency | Specify the efficiency of the operating system in allocating CPU resources to each process is mainly related to the frequency of process switching and the cost of context switching. | +| | | memory management efficiency | Specify the efficiency of the operating system in allocating and managing memory resources. | +| | virtualization and containerization performance | virtualization resource overhead ratio | Specify when a virtual machine runs an application, the percentage of physical resources consumed by the virtualization layer exceeds the total resources allocated to the virtual machine. | +| | | startup time | Specify the time it takes for a virtual machine or container to go from startup to full operation. | +| transaction | transaction processing time | – | Specify the time it takes for a transaction to go from submission to confirmation. Shorter processing times can improve user experience and increase system throughput. | +| | transaction verification speed | – | Specify the time a node validates a transaction or request. This metric measures the efficiency of processing transaction requests and directly affects the throughput and response time of the network. | +| | transaction pool management | transaction pool size | Specify the total number of pending transactions per unit time. | + +**Table 2 – Performance management attributes of the blockchain system** + +| Category | Item | Sub-item | Description | +|----------|-------------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | transaction retention time | Specify the time it takes for a transaction to be confirmed (or removed) in the trading pool from the time it is entered. | +| | deduplication mechanism | duplicate detection rate | Specify the proportion of the number of duplicate transactions successfully identified by the system in a certain period to the total number of duplicate transactions. | +| | | deduplication latency | Specify the time from the receipt of a duplicate transaction to the completion of de-processing by the system. | +| | | negative rate | Specify the proportion of non-repeated transactions that are misjudged by a deduplication mechanism as repeated or normal. | + +NOTE 2 – The traceability of this use case is REQ-PM-FUN-01. + +#### 8.4.2.2 Query measurement job (O) + +This use case is about the operation of querying a performance measurement job in the blockchain system. The content mainly refers to clause 6.3.4.4 of [ITU-T M.3704]. + +NOTE 1 – The manager is recommended to request an agent to create a performance measurement job of the blockchain system + +NOTE 2 – The precondition of this use case is use case 8.4.2.1. + +NOTE 3 – The traceability of this use case is REQ-PM-FUN-02. + +#### 8.4.2.3 Suspend measurement job (M) + +This use case is about the operation of suspending a performance measurement job in the blockchain system. The content mainly refers to clause 6.3.4.2 of [ITU-T M.3704]. + +NOTE 1 – The manager requests an agent to suspend a performance measurement job of the blockchain system. + +NOTE 2 – The precondition of this use case is use case 8.4.2.1. + +NOTE 3 – The traceability of this use case is REQ-PM-FUN-03. + +#### 8.4.2.4 Resume measurement job (M) + +This use case is about the operation of resuming a performance measurement job in the blockchain system. The content mainly refers to clause 6.3.4.3 of [ITU-T M.3704]. + +NOTE 1 – The manager requests an agent to resume a performance measurement job of the blockchain system. + +NOTE 2 – The precondition of this use case is use case 8.4.2.3. + +NOTE 3 – The traceability of this use case is REQ-PM-FUN-04. + +#### 8.4.2.5 Stop measurement job (M) + +This use case is about the operation of stopping a performance measurement job in the blockchain system. The content mainly refers to clause 6.3.4.5 of [ITU-T M.3704]. + +NOTE 1 – The manager requests an agent to stop a performance measurement job of the blockchain system. + +NOTE 2 – The precondition of this use case is use case 8.4.2.1. + +NOTE 3 – The traceability of this use case is REQ-PM-FUN-05. + +##### 8.4.2.6 Query the performance values of measurement job (M) + +Table 3 shows the performance values of measurement job (M). + +**Table 3 – Performance values of measurement job (M)** + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | A manager can query the information about the performance values of a measurement job through the management interface. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecommunication resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified measurement job exists in the agent. | | +| Begins when | The manager sends a request to query the information of a measurement job. | | +| Step 1 | The manager sends a request to the agent to query the attribute information of a measurement job, which includes:
  • – the ID of the measurement job;
  • – the list of parameter names;
  • – the filtering criteria for performance data (record);
  • – the start time of the performance values to be queried (optional);
  • – the end time of the performance values to be queried (optional).
| | +| Step 2.1 | If the operation succeeds, the agent will return the performance values of the performance measurement job to the manager. | | +| Step 2.2 | If the operation fails, the agent will return error information to the manager. | | +| Ends when | The requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions |
  • – Unknown measurement job
  • – Invalid parameter
| | +| Post conditions | The corresponding performance data information generated by the measurement job is returned by the agent. | | +| Traceability | REQ-PM-FUN-06 | | + +### 8.4.3 Fault management + +#### 8.4.3.1 Create alarm filter (M) + +This use case is about the operation of setting an alarm filter in the blockchain system. The content mainly refers to clause 6.3.4.1 of [ITU-T M.3703]. + +NOTE 1 – The manager requires the agent to set the alarm filter of the blockchain system, and the alarm objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The preconditions of this use case are the manager needs to pre-specify alert severities for a set of issues that may exist in the blockchain system in order to ensure the stable operation of the blockchain system. The manager needs to specify alert severities for a set of issues so that when an agent reports an alert, it can refer to these pre-specified severities in the corresponding alert notification. + +NOTE 3 – The traceability of this use case is REQ-FM-FUN-01. + +##### 8.4.3.2 Query alarm filter (O) + +Table 4 shows the stages of the query alarm filter use case. + +**Table 4 – Query alarm filter** + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | A manager is recommended to query the information of an alarm filter through the management interface. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecommunication resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified alarm filter has been successfully created and exists in the agent. | Use case 8.4.3.1 | +| Begins when | The manager sends a request to query the information of an alarm filter. | | +| Step 1 | The manager sends a request to the agent to query the attribute information of an alarm filter, which includes the ID of the alarm filter, the list of the problem and the corresponding severity, and the list of managed entities that have been associated with this alarm filter. | | +| Step 2.1 | If the operation succeeds, the agent will return the information of an alarm filter to the manager. | | +| Step 2.2 | If the operation fails, the agent will return error information to the manager. | | +| Ends when | The requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – Unknown alarm filter | | +| Post conditions | The corresponding alarm filter information is returned by the agent. | | +| Traceability | REQ-FM-FUN-02 | | + +#### 8.4.3.3 Modify alarm filter (M) + +Table 5 shows the stages of the modify alarm filter use case. + +**Table 5 – Modify alarm filter** + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | A manager requests that an agent modify, add, or delete table entries (problem and the corresponding alarm severity) of an alarm filter. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecommunication resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified alarm filter has been successfully created and exists in the agent.
The manager needs to change the table entries of the alarm severity assignment of an alarm filter. | Use case 8.4.3.1 | +| Begins when | The manager sends a request to an agent to modify an alarm filter. | | +| Step 1 | The manager sends a request to the agent to modify an alarm filter. The request parameter is the new list of problems and their corresponding severity to be modified. | | +| Step 2.1 | If the modification operation succeeds, the agent will send success information to the manager. | | +| Step 2.2 | If the operation fails, the agent will send back error information to the manager. | | +| Ends when | The requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – Unknown alarm filter
– Invalid parameter | | +| Post conditions | An alarm filter on the agent is successfully modified according to the request. | | +| Traceability | REQ-FM-FUN-03 | | + +#### **8.4.3.4 Delete alarm filter (O)** + +Table 6 shows the stages of the delete alarm filter use case. + +**Table 6 – Delete alarm filter** + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------------|--------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The manager is recommended to delete the alarm filter from the agent. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecommunication resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent of the blockchain system is available. | | + +**Table 6 – Delete alarm filter** + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Preconditions | The alarm filter that the manager chooses to delete has already been created and exists in the alarm list. | Use case 8.4.3.1 | +| Begins when | The manager sends a request to the agent to delete an alarm filter. | | +| Step 1 | The manager sends a request to the agent to delete an alarm filter. The request parameter is the new list of problems and their corresponding severity to be deleted. | | +| Step 2.1 | If the delete operation succeeds, the agent will send success information. | | +| Step 2.2 | If the operation fails, the agent will send back error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – Unknown alarm filter
– Invalid parameter | | +| Post conditions | An alarm filter on the agent is successfully deleted according to the request. | | +| Traceability | REQ-FM-FUN-04 | | + +#### 8.4.3.5 Report alarm notification (M) + +This use case is about the alarm notification in the blockchain system. The content mainly refers to clause 6.3.4.2 of [ITU-T M.3703]. + +NOTE 1 – The manager requires the agent to send the alarm report notification of the blockchain system, and the alarm objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The traceability of this use case is REQ-FM-FUN-05. + +##### 8.4.3.6 Notification of alarm change (M) + +This use case is about the operation of notifying the change of an alarm in the blockchain system. The content mainly refers to clause 6.3.4.3 of [ITU-T M.3703]. + +NOTE 1 – The manager requires the agent to notify the change of an alarm of the blockchain system, and the alarm objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The traceability of this use case is REQ-FM-FUN-06. + +##### 8.4.3.7 Get alarm list (O) + +This use case is about the operation of getting alarm list in the blockchain system. The content mainly refers to clause 6.3.4.5 of [ITU-T M.3703]. + +The manager is recommended to get alarm list of the blockchain system from the agent, and the alarm objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. Please see Table 7 for the detailed requirements. + +**Table 7 – Fault management attributes of the blockchain system** + +| Category | Item | Sub-item | Description (Probable causes) | +|-----------------------|-----------------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| blockchain systems | consensus failure | – |
  • – Over 1/3 consensus nodes down.
  • – Byzantine fault tolerance (BFT) parameter misconfigured.
| +| | cross-chain communication failure | relay chain failure |
  • – Cross-chain gateway certificate has expired.
  • – Relay node CPU overload.
| +| blockchain | chain sync delay | – |
  • – A 51% attack attempt.
  • – Block propagation congestion due to topology imbalance.
| +| | smart contract timeout | – |
  • – Unbounded loop exhausting execution resources.
  • – Off-chain data source timeout.
| +| Peer-to-peer network | neighbour connection failure | firewall block | Gossip protocol port blocked | +| | | routing oscillation | Border gateway protocol (BGP) route flapping causing regional disconnection. | +| | excessive neighbour failure | – |
  • – No dynamic neighbour reselection.
  • – Local connection pool overflow.
| +| node | node disk space exhausted | – |
  • – Storage space for status data abnormally expanded.
  • – No log rotation.
| +| | node out of memory (OOM) crash | – |
  • – Transaction queue backlog.
  • – Java virtual machine (JVM) heap misconfigured.
  • – Native memory leak.
| +| | node process crash | – |
  • – Graphics processing unit (GPU) pre-emption blocking core threads.
  • – Dependency version conflict.
| +| operating environment | container isolation failure | Cgroup misconfig | – Docker CPU set binding failed. | +| | | resource overcommit | – Resource quota overcommitment. | +| | virtualization degradation | – |
  • – Virtual central processing unit (vCPU) binding failure.
  • – Single root input/output virtualization (SR-IOV) passthrough driver failure.
| +| block | Block verification failure spike | – |
  • – Invalid transactions in block.
  • – State root hash mismatch.
| +| | Abnormal block interval | – |
  • – Consensus node clock skew.
  • – Empty block triggering mechanism flaw.
| +| transaction | Transaction endorsement rejection | – |
  • – State dependency changed.
  • – Endorsement policy error.
| + +**Table 7 – Fault management attributes of the blockchain system** + +| Category | Item | Sub-item | Description (Probable causes) | +|----------|--------------------------|----------|-------------------------------------------------------------------------------------------------------------| +| | Transaction Pool Backlog | – | – Network latency causes the transaction synchronization speed to slow down.
– Transaction flood attack. | + +NOTE – The traceability of this use case is REQ-FM-FUN-07. + +##### **8.4.3.8 Clear alarm (M)** + +This use case is about the operation of clearing alarms in the blockchain system. The content mainly refers to clause 6.3.4.4 of [ITU-T M.3703]. + +NOTE 1 – The manager requires the agent to clear alarms of the blockchain system, and the alarm objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The traceability of this use case is REQ-FM-FUN-08. + +#### **8.4.4 log management** + +##### **8.4.4.1 Create log collection task (M)** + +This use case is about the operation of creating a log in the blockchain system. The content mainly refers to clause 6.1.4.4 of [ITU-T M.3705]. + +NOTE 1 – The manager requires the agent to create a log of the blockchain system, and the log record related objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The traceability of this use case is REQ-LM-FUN-01. + +##### **8.4.4.2 Modify log collection task (M)** + +This use case is about the operation of modifying logging criteria in the blockchain system. The content mainly refers to clause 6.1.4.1 of [ITU-T M.3705]. + +NOTE 1 – The manager requires the agent to modify logging criteria of the blockchain system, and the log objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The precondition of this use case is use case 8.4.4.1. + +NOTE 3 – The traceability of this use case is REQ-LM-FUN-02. + +##### **8.4.4.3 Delete log collection task (O)** + +This use case is about the operation of deleting logs in the blockchain system. The content mainly refers to clause 6.1.4.5 of [ITU-T M.3705]. + +NOTE 1 – The manager is recommended to require the agent to delete logs of the blockchain system, and the log objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The precondition of this use case is use case 8.4.4.1. + +NOTE 3 – The traceability of this use case is REQ-LM-FUN-04. + +#### **8.4.4.4 Query log collection task (O)** + +This use case is about the operation of querying the list of logs in the blockchain system. The content mainly refers to clause 6.1.4.6 of [ITU-T M.3705]. + +NOTE 1 – The manager is recommended to require the agent to query the list of logs of the blockchain system, and the log objects mainly involve blockchain systems, blockchains, peer-to-peer networks, nodes, node operating environments, blocks, and transactions, etc. + +NOTE 2 – The precondition of this use case is use case 8.4.4.1. + +NOTE 3 – The traceability of this use case is REQ-LM-FUN-03. + +#### 8.4.4.5 Query log records (M) + +Table 8 shows the stages of the query log records (M) use case. + +**Table 8 – Query log records (M)** + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal |

The manager may query log records in order to analyse the relevant situation, including administrative state, timestamp, log level, source component, log content, associated transaction or block ID, event type, and error codes.

The manager retrieves records of a specific log or a set of logs (the logs are stored in separate files based on their type and time) from the agent of the blockchain system, based on filtering criteria such as time range, node ID, module name, severity level, or keyword matching, to support troubleshooting, auditing, or behaviour analysis.

| | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecommunication resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of querying a log object. | | +| Preconditions | The specified log exists in the agent. | Use case 8.4.4.1 | +| Begins when | The manager sends the request to the agent. | | +| Step 1 |

The manager sends a request to query log records. The parameters in the request are:

  • – the specific log ID to be queried;
  • – filtering conditions (optional), such as timestamp range, log level, source component, or keyword.
| | +| Step 2.1 |

The agent receives and validates the request parameters. If invalid, skip to Step 2.2 with an error code.

Search the corresponding log storage using validated parameters. If the search succeeds, the agent filters and extracts the log records that match the given parameters and then returns the log record data to the manager for further analysis.

| | +| Step 2.2 | If the operation fails, the agent will return error information to the manager. | | +| Ends when | The agent returns the queried log record data or an error response to the manager. | | +| Exceptions |
  • – Invalid parameters
  • – Agent processing error
  • – Communication error
| | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|----------------------------------------------------------------------------------------------------------------------|-------------------------| +| Post conditions | The manager obtains the requested log record data for analysis or receives an error indicating the query has failed. | | +| Traceability | REQ-LM-FUN-05 | | + +##### 8.4.4.6 Backup log (M) + +Table 9 shows the stages of the backup log (M) use case. + +**Table 9 – Backup log (M)** + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager may backup a log object, including administrative state, operational state, max log size, current log size, log full action, number of records, alarm status, capacity alarm threshold, filtering criteria, and so on.
The manager backs up a specific log or all log objects in the agent of the blockchain system. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecommunication resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of backing up a log. | | +| Preconditions | The specified log exists in the agent. | Use case 8.4.4.1 | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager sends a request to backup a log. The parameters in the request are:
– the specific object name ID of the log to be backed up. | | +| Step 2 | If the operation succeeds, the agent will return the successful indication. Otherwise, the agent will return an exception. | | +| Ends when | The backup response is sent. | | +| Exceptions | – Invalid parameters
– Agent processing error
– Communication error | | +| Post conditions | A backup log record is generated. | | +| Traceability | REQ-LM-FUN-06 | | + +## Bibliography + +[b-ISO/DIS 22739] ISO DIS 22739:2024, *Blockchain and distributed ledger technologies – Vocabulary*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3167.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3167.1-202503-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..357bf60e91f9e236d8fbc98bf81f3641856499d6 --- /dev/null +++ b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2e3d3f6c2af2292978c5fe257809a8054530bb849aa737b3f8016d0269a0644 +size 47448 diff --git a/marked/M/T-REC-M.3167.1-202503-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e453fa7996dbcade02dfcc7fcbf16b7dc627f3bd --- /dev/null +++ b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29c4c20277a80c8033c9d1f66b0d47f23c5b238057ff399b5d0d35b0f3368e93 +size 47473 diff --git a/marked/M/T-REC-M.3167.1-202503-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f70c709f2909ffab66bbee91f354cb1699d5e90 --- /dev/null +++ b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c917ad95c416d728162dc4a6afab1128161ec7a3fa31117b24cda8d4e3db6ef +size 8416 diff --git a/marked/M/T-REC-M.3167.1-202503-I_PDF-E/raw.md b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c0d7f68497049eea508135f8d6b3fef21e32a505 --- /dev/null +++ b/marked/M/T-REC-M.3167.1-202503-I_PDF-E/raw.md @@ -0,0 +1,449 @@ + + +# Recommendation**ITU-T M.3167.1 (03/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **Interface for robot-based on-site smart patrol of telecommunication networks – Protocol neutral requirements** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3167.1 + +## Interface for robot-based on-site smart patrol of telecommunication networks – Protocol neutral requirements + +## Summary + +With the continuous development of Internet of things (IoT) technology, the application of intelligent maintenance robots (IMRs) in the field of telecommunication smart maintenance (TSM) is increasing. Recommendation ITU-T M.3167.1 provides the requirements for the interface between the IMR-based smart patrol system (IbSPS) and the telecommunication smart maintenance system (TSMS) at a protocol-neutral level. It describes the position of the relevant interface and specifies the high-level requirements for interface interaction, as well as specification level use cases for each requirement. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3167.1 | 2025-03-29 | 2 | 11.1002/1000/16280 | + +## Keywords + +Intelligent maintenance robots, interface requirements, robot-based on-site smart patrol, telecommunication smart maintenance. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Concepts and background..... | 2 | +| 7 Business level requirements ..... | 3 | +| 7.1 Requirements ..... | 3 | +| 7.2 Actor roles ..... | 4 | +| 7.3 Telecommunication resources ..... | 4 | +| 7.4 High-level use cases ..... | 4 | +| 8 Specification level requirements..... | 5 | +| 8.1 Requirements ..... | 5 | +| 8.2 Actor roles ..... | 5 | +| 8.3 Telecommunication resources ..... | 5 | +| 8.4 Use cases ..... | 5 | +| Bibliography..... | 11 | + + + +## Recommendation ITU-T M.3167.1 + +## Interface for robot-based on-site smart patrol of telecommunication networks – Protocol neutral requirements + +## 1 Scope + +This Recommendation provides protocol neutral requirements for the interface between the robot-based smart patrol system and the telecommunication smart maintenance system (TSMS), including: + +- Concepts and background, +- Business level requirements, +- Specification level requirements. + +The requirements and management information and interactions provided in this Recommendation follow [ITU-T M.3020] management interface specification methodology (MISM) in the requirements phase, and are developed in a protocol-neutral manner. + +This Recommendation is applicable to the design and development for the interface between the robot-based smart patrol system and the TSMS. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [[ITU-T M.3020](#)] Recommendation ITU-T M.3020 (2023), *Management interface specification methodology*. +- [[ITU-T M.3040](#)] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. +- [[ITU-T M.3164.1](#)] Recommendation ITU-T M.3164.1 (2024), *Interface for on-site generic telecommunication smart maintenance – Protocol neutral requirements*. +- [[ITU-T M.3364](#)] Recommendation ITU-T M.3364 (2020), *Requirements for on-site telecommunication smart maintenance management function*. +- [[ITU-T M.3367](#)] Recommendation ITU-T M.3367 (2023), *Requirements for robot-based on-site smart patrol of telecommunication networks*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 intelligent maintenance robot** [ITU-T M.3367]: A kind of smart wearable maintenance assistant toolkit, a smart information collection device that integrates infrared, visual, sound and other multi-functional sensors, uses the autonomous navigation and positioning function to follow the patrol route, and uses visible image analysis, infrared temperature measurement and other + +technologies to carry out on-site patrol, information collection and dispatch of reports to a telecommunication smart maintenance system. + +**3.1.2 F interface** [b-ITU-T M.3010]: An interface applied at f reference points. + +**3.1.3 f reference points** [b-ITU-T M.3010]: A reference point that is located between the workstation function block (WSF) and the operations systems function block (OSF). + +**3.1.4 robot** [b-ISO 8373]: Programmed actuated mechanism with a degree of autonomy to perform locomotion, manipulation or positioning. + +**3.1.5 telecommunication smart maintenance** [ITU-T M.3040]: The maintenance carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system, which can provide strong human-computer interaction capabilities and online guidance to personnel, to achieve higher efficiency and precision of actions. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------------------| +| AI | Artificial Intelligence | +| AR | Augmented Reality | +| IbSPS | IMR-based Smart Patrol System | +| IMR | Intelligent Maintenance Robot | +| IoT | Internet of Things | +| MISM | Management Interface Specification Methodology | +| SMAT | Smart Maintenance Assistant Toolkit | +| TSM | Telecommunication Smart Maintenance | +| TSMS | Telecommunication Smart Maintenance System | + +## 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement needs not be present to claim conformance. + +For the qualifiers of a use case in the specification-level requirements, "M" stands for "Mandatory" and "O" stands for "Optional". + +## 6 Concepts and background + +With advancements in related technologies, on-site patrol based on smart robots is becoming increasingly prevalent in telecommunication smart maintenance (TSM). This approach leverages the integration of Internet of things (IoT) and artificial intelligence (AI) technologies for TSM, aiming to significantly enhance the efficiency and effectiveness of TSM practices. + +[ITU-T M.3364] has provided requirements for generic on-site TSM functions in which the requirements for on-site patrol are defined. Based on this, [ITU-T M.3367] further defines the requirements for intelligent maintenance robot (IMR)-based on-site smart patrol, in which the IMR-based smart patrol system (IbSPS) is one specific case of the smart maintenance assistant toolkit (SMAT) function defined in [ITU-T M.3040]. + +Based on the information provided in [ITU-T M.3367], this Recommendation addresses the F interface between the IbSPS and the telecommunication smart maintenance system (TSMS), as shown in Figure 1. + +![Diagram showing the interface between IbSPS and TSMS. Two rounded rectangular boxes, labeled 'IbSPS' and 'TSMS', are connected by a horizontal dashed line. Above the dashed line is the text 'F interface'. Below the 'TSMS' box is the text 'M.3167.1(25)'.](562f471e8153729557e6a4ee6343c32c_img.jpg) + +``` +graph LR; IbSPS[IbSPS] -.->|F interface| TSMS[TSMS]; +``` + +Diagram showing the interface between IbSPS and TSMS. Two rounded rectangular boxes, labeled 'IbSPS' and 'TSMS', are connected by a horizontal dashed line. Above the dashed line is the text 'F interface'. Below the 'TSMS' box is the text 'M.3167.1(25)'. + +**Figure 1 – Interface between IbSPS and TSMS** + +[ITU-T M.3020] defines the management interface specification methodology (MISM) in which three phases are included: requirements phase, analysis phase and design phase. The requirements and analysis phase are protocol neutral, which are independent with implementation techniques. The design phase is protocol dependent and can be mapped to multiple techniques. + +This Recommendation defines the protocol neutral requirements for the interface between the IbSPS and the TSMS. The interface analysis part and the design part will be provided in other separate Recommendations. + +[ITU-T M.3164.1] specifies the protocol neutral requirements of the interface between the SMAT and the TSMS for on-site generic TSM. Since the IbSPS is a special case of the SMAT and on-site patrol is a special case of the on-site generic TSM, some common use cases defined in [ITU-T M.3164.1] are reused in this Recommendation. + +## **7 Business level requirements** + +## **7.1 Requirements** + +The IbSPS is required to provide the following functions across the interface for the TSMS to: + +- REQ-OP-FUN-01 Distribute on-site patrol tasks to the IbSPS. +- REQ-OP-FUN-02 Distribute the patrol route information of a patrol task to the IbSPS. +- REQ-OP-FUN-03 Distribute the smart identification data to the IbSPS. +- REQ-OP-FUN-04 Modify the existing on-site patrol tasks previously assigned to the IbSPS. +- REQ-OP-FUN-05 Distribute administrative commands to the IbSPS, such as suspending or resuming the current task. + +The TSMS is required to provide the following functions across the interface for the IbSPS to: + +- REQ-OP-FUN-11 Find the smart identification data from the TSMS. +- REQ-OP-FUN-12 Upload the patrol record to the TSMS. +- REQ-OP-FUN-13 Report the real-time status of the IMR to the TSMS. +- REQ-OP-FUN-14 Report the real-time status of the patrol task to the TSMS. + +The TSMS is recommended to provide the following function across the interface for the IbSPS to: + +- REQ-OP-FUN-15 Report emergency incidents to the TSMS, such as IMR encountering obstacles or component malfunctions. + +## 7.2 Actor roles + +The capabilities described in this Recommendation are available and relevant to all agents and managers. In this Recommendation, the TSMS acts as a manager and the IbSPS acts as an agent. + +## 7.3 Telecommunication resources + +The smart maintenance functionality is applicable to all types of telecommunication resources involved in the IMR-based smart patrol. + +## 7.4 High-level use cases + +The high-level use cases for the interface between the IbSPS and the TSMS are shown in Figure 2 and Figure 3. + +![Diagram showing high-level use cases from the TSMS perspective. A TSMS actor is connected to five use cases: push_patrol_tasks, push_patrol_route, push_smart_identification_data, modify_patrol_tasks, and send_administrative_command.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +The diagram illustrates the high-level use cases from the TSMS perspective. On the left, an actor icon labeled "TSMS" is shown. To the right, a rectangular box titled "Interface between the IbSPS and the TSMS" contains five oval-shaped use cases. Lines connect the TSMS actor to each of these use cases: "push\_patrol\_tasks", "push\_patrol\_route", "push\_smart\_identification\_data", "modify\_patrol\_tasks", and "send\_administrative\_command". The reference code "M.3167.1(25)" is located at the bottom right of the box. + +Diagram showing high-level use cases from the TSMS perspective. A TSMS actor is connected to five use cases: push\_patrol\_tasks, push\_patrol\_route, push\_smart\_identification\_data, modify\_patrol\_tasks, and send\_administrative\_command. + +Figure 2 – The high-level use cases from the TSMS perspective + +![Diagram showing high-level use cases from the IbSPS perspective. An IbSPS actor is connected to five use cases: upload_patrol_record, find_smart_identification_data, report_imr_status, report_task_status, and report_emergency.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +The diagram illustrates the high-level use cases from the IbSPS perspective. On the left, an actor icon labeled "IbSPS" is shown. To the right, a rectangular box titled "Interface between the IbSPS and the TSMS" contains five oval-shaped use cases. Lines connect the IbSPS actor to each of these use cases: "upload\_patrol\_record", "find\_smart\_identification\_data", "report\_imr\_status", "report\_task\_status", and "report\_emergency". The reference code "M.3167.1(25)" is located at the bottom right of the box. + +Diagram showing high-level use cases from the IbSPS perspective. An IbSPS actor is connected to five use cases: upload\_patrol\_record, find\_smart\_identification\_data, report\_imr\_status, report\_task\_status, and report\_emergency. + +Figure 3 – The high-level use cases from the IbSPS perspective + +## 8 Specification level requirements + +### 8.1 Requirements + +There are no specification level requirements. + +## 8.2 Actor roles + +See clause 7.2. + +## 8.3 Telecommunication resources + +See clause 7.3. + +## 8.4 Use cases + +The general exceptions (e.g., communication error, processing error) related to all use cases are not supposed to be described in the following clauses and will only be handled in the design phase. + +The exception "Invalid input parameter" in the following sections indicates that there is some syntactic error(s) in the input parameters, which does not involve semantic issues. + +The exception "Specified patrol Info ID not existing in TSMS" (for example) indicates that the specified patrol Info ID in the input parameter is syntactically correct, but it cannot be found in the TSMS database, which is considered as a semantic error. + +### 8.4.1 Push patrol tasks (M) + +This use case is compliant with clause 7.3.4.1.1 of [ITU-T M.3164.1], in which the IbSPS is considered as a special case of the SMAT during the patrol task distribution. This use case can be traced back to the requirement REQ-OP-FUN-01. + +### 8.4.2 Push patrol route (M) + +This use case is compliant with clause 7.3.4.1.2 of [ITU-T M.3164.1], in which the IbSPS is considered as a special case of the SMAT during the patrol route distribution. This use case can be traced back to the requirement REQ-OP-FUN-02. + +#### 8.4.3 Push smart identification data (M) + +This use case is compliant with clause 7.3.4.1.3 of [ITU-T M.3164.1], in which the IbSPS is considered as a special case of the SMAT during the smart identification data distribution. This use case can be traced back to the requirement REQ-OP-FUN-03. + +#### 8.4.4 Modify patrol tasks (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TSMS can send a request to the IbSPS to modify the information of one or more specific previously assigned patrol task(s). | | +| Actors and roles | The TSMS invokes the operation on the IbSPS. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the TSMS and the IbSPS is available. | | +| Pre-conditions | The route information of the patrol tasks has been generated in the TSMS.
The TSMS has already pushed the on-site patrol tasks information to the IbSPS. | Use case 8.4.1 | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Begins when | The TSMS sends a request to the IbSPS to modify the information of one or more previously assigned patrol task(s). | | +| Step 1 | The TSMS sends a request to the IbSPS with the updated on-site patrol task modification information. The information contains the following:
  • – the IbSPS ID
  • – the patrol Info ID
  • – the list of patrol task IDs whose information is to be modified
  • – the list of detailed modification information for each patrol task in the above list
| | +| Step 2.1 | If the modified patrol tasks information is successfully received by the IbSPS without any problems, the IbSPS will inform the TSMS with a success indication, and the corresponding information are updated for the specific patrol task(s). | | +| Step 2.2 | If the modified patrol task information cannot be successfully resolved by the IbSPS, the IbSPS will inform the TSMS with a failure indication, and the information for the patrol task will not be updated. | | +| Ends when | Requested information or an exception is returned to the TSMS. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
  • – Specified IbSPS ID not existing in the IbSPS
  • – Specified patrol Info ID not existing in the IbSPS
  • – Specified patrol task ID not existing in the IbSPS
| | +| Post-conditions | The new on-site patrol task information is successfully updated in the IbSPS. | | +| Traceability | REQ-OP-FUN-04 | | + +#### 8.4.5 Send administrative command (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The TSMS can send a particular administrative command to the IbSPS to control the progress of on-site patrol tasks remotely on the IMR. | | +| Actors and roles | The TSMS invokes the operation on the IbSPS. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the TSMS and the IbSPS is available. | | +| Pre-conditions | The TSMS has already pushed the on-site patrol tasks information to the IbSPS. | Use case 8.4.1 | +| Begins when | The TSMS sends a particular administrative command to the IbSPS. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 1 | The TSMS sends a particular administrative command to the IbSPS, which includes:
  • – the IbSPS ID
  • – the script of a specific administrative command, which can be one of the following options (but not limited to):
    • • to suspend the current on-site patrol task
    • • to resume the current on-site patrol task
    • • to abort the current on-site patrol task and jump to the next one
    • • to abort and clear all the unperformed assigned on-site patrol tasks
    • • to reboot the IMR
    • • to execute a self-diagnostic program in the IMR
| | +| Step 2.1 | If the administrative command is successfully received and executed, the IbSPS will inform the TSMS with a success indication | | +| Step 2.2 | If the administrative command cannot be successfully resolved or executed, the IbSPS will inform the TSMS with a failure indication | | +| Ends when | A successful indication or an exception is returned to the TSMS. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
  • – Specified IbSPS ID not existing in the IbSPS
| | +| Post-conditions | The administrative command is successfully received and executed in the IbSPS. | | +| Traceability | REQ-OP-FUN-05 | | + +#### 8.4.6 Find smart identification data (M) + +This use case is compliant with clause 7.3.4.1.4 of [ITU-T M.3164.1], in which the IbSPS is considered as a special case of the SMAT during the smart identification data requisition. This use case can be traced back to the requirement REQ-OP-FUN-11. + +#### 8.4.7 Upload patrol record (M) + +This use case is compliant with clause 7.3.4.1.5 of [ITU-T M.3164.1], in which the IbSPS is considered as a special case of the SMAT during the patrol record reporting. This use case can be traced back to the requirement REQ-OP-FUN-12. + +#### 8.4.8 Report IMR status (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IbSPS sends a notification to the TSMS to report the real-time status of the IMR at a regular interval, with a default reporting period pre-configured in the IMR. | | +| Actors and roles | The IbSPS invokes the operation on the TSMS. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the IbSPS and the TSMS is available. | | +| Pre-conditions | The reporting interval is pre-configured in the IMR. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Begins when | The IbSPS sends a notification to the TSMS to report the real-time status of the IMR. | | +| Step 1 | The IbSPS sends a notification to the TSMS with the IMR status information, which contains:
  • – the IbSPS ID
  • – the coordinate information
  • – the IMR status (idle/patrolling/investigating/docked/fault)
  • – the IMR system load (percentage from 0 to 100)
  • – the battery level (percentage from 0 to 100)
| | +| Step 2.1 | If the IMR status information is successfully received and resolved by the TSMS, the TSMS will inform the IbSPS with a success indication. | | +| Step 2.2 | If the IMR status information cannot be successfully resolved, the TSMS will inform the IbSPS with a failure indication. | | +| Ends when | The TSMS successfully receives the IMR status information from the IbSPS. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
  • – Specified IbSPS ID not existing in the TSMS
| | +| Post-conditions | The real-time status information of the IMR is successfully received and stored in the TSMS. | | +| Traceability | REQ-OP-FUN-13 | | + +#### 8.4.9 Report task status (M) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | The IbSPS sends a notification to the TSMS to report the real-time execution status of the patrol tasks assigned in the IMR at a regular interval, with a default reporting period pre-configured in the IMR. | | +| Actors and roles | The IbSPS invokes the operation on the TSMS. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the IbSPS and the TSMS is available. | | +| Pre-conditions | The patrol tasks have been distributed from the TSMS to the IbSPS.
The reporting interval is pre-configured in the IMR. | Use case 8.4.1 | +| Begins when | The IbSPS sends a notification to the TSMS to report the execution status of patrol tasks. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 1 | The IbSPS sends a notification to the TSMS with the execution status information of patrol tasks, which contains:
  • – the IbSPS ID
  • – the patrol Info ID
  • – the task ID list
  • – the list of the execution status (scheduled/ in progress/ completed/ failed)
  • – the list of the execution progress of each task (completion percentage of the patrol task, from 0 to 100)
| | +| Step 2.1 | If the task status information is successfully received and resolved, the TSMS will inform the IbSPS with a success indication | | +| Step 2.2 | If the task status information cannot be successfully resolved, the TSMS will inform the IbSPS with a failure indication. | | +| Ends when | The TSMS successfully receives the task status information from the IbSPS. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
  • – Specified IbSPS ID not existing in the TSMS
  • – Specified patrol information ID not existing in the TSMS
  • – Specified patrol task ID not existing in the TSMS
| | +| Post-conditions | The real-time execution status of the patrol tasks is successfully received and stored in the TSMS. | | +| Traceability | REQ-OP-FUN-14 | | + +#### 8.4.10 Report emergency (O) + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Goal | When an emergency incident occurs in the IbSPS or in the IMR, the IbSPS sends a notification to the TSMS to report the emergency incident, such as IMR encountering obstacles or component malfunctions. | | +| Actors and roles | The IbSPS invokes the operation on the TSMS. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the IbSPS and the TSMS is available. | | +| Pre-conditions | An emergency incident occurs in the IbSPS or in the IMR. | | +| Begins when | The IbSPS sends a notification to the TSMS to report the emergency incident. | | + +| Use case stage | Evolution/Specification | <>
Related use case(s) | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Step 1 | The IbSPS sends a notification to the TSMS with the emergency information, which contains:
  • – the IbSPS ID
  • – the patrol Info ID
  • – the ongoing patrol task ID (optional)
  • – the emergency incident type (e.g., encountering obstacles, component malfunctions, etc.)
  • – the coordinate information
  • – additional photography of the emergency incident, if available (optional).
| | +| Step 2.1 | If the emergency information is successfully received and resolved, the TSMS will inform the IbSPS with a success indication. | | +| Step 2.2 | If the emergency information cannot be successfully resolved, the TSMS will inform the IbSPS with a failure indication. | | +| Ends when | The TSMS successfully receives the emergency information from the IbSPS. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
  • – Specified IbSPS ID not existing in the TSMS
  • – Specified patrol Info ID not existing in the TSMS
  • – Specified patrol task ID not existing in the TSMS
| | +| Post-conditions | The emergency information of the IbSPS is successfully received by the TSMS, and corresponding actions related to the emergency may be taken. (For example, the TSMS may send corresponding administrative commands to the IbSPS. If the current emergency situation cannot be solved, on-site human intervention will be carried out.) | Use case 8.4.5 | +| Traceability | REQ-OP-FUN-15 | | + +## Bibliography + +- [b-ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [b-ISO 8373] ISO 8373:2021, *Robotics – Vocabulary*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3170.0-200703-I_PDF-E/raw.md b/marked/M/T-REC-M.3170.0-200703-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bb2a9ad7d0c8f491bfb2538ca2fd077a09930989 --- /dev/null +++ b/marked/M/T-REC-M.3170.0-200703-I_PDF-E/raw.md @@ -0,0 +1,627 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3170.0** + +(03/2007) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Multi-technology network management – +Introduction and supporting documentation** + +ITU-T Recommendation M.3170.0 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Multi-technology network management – Introduction and supporting documentation** + +## **Summary** + +The TM Forum's multi-technology network management (MTNM) solution suite realizes a TMN interface between the NML and EML according to ITU-T Recommendation M.3010 for the FCAPS management of multi-technology fixed transport, access and aggregation telecommunications networks. + +This Recommendation provides a physical and logical overview of the MTNM solution suite where the logical overview focuses on the MTNM business objectives and the suite of MTNM supporting documents. This Recommendation also explains the chosen approach to reference the TMF MTNM deliverables in ITU-T Recommendations such that they get hooked into ITU-T's management architectures and frameworks without the need to change any TM Forum deliverable. + +## **Source** + +ITU-T Recommendation M.3170.0 was approved on 16 March 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Common Object Request Broker Architecture (CORBA), element management (EM), EM layer (EML), EM system (EMS), enhanced Telecom Operations Map (eTOM), FCAPS (fault, configuration, accounting, performance and security) management, interface, management interface specification methodology (MISM), multi-technology network management (MTNM), network element (NE), NE layer (NEL), network management (NM), NM layer (NML), NM system (NMS), next generation network(s) (NGN), NGN management (NGNM), operations system (OS), Q interface, requirements, analysis and design (RAD) (and conformance), service-oriented CORBA, tele(com(munications)) management (TM), TM Forum (TMF), TM network (TMN). + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 2 | +| 3 Definitions ..... | 4 | +| 3.1 Terms defined elsewhere ..... | 4 | +| 4 Abbreviations and acronyms ..... | 4 | +| 5 Conventions ..... | 6 | +| 6 MTNM overview ..... | 6 | +| 6.1 MTNM deliverables ..... | 6 | +| 6.2 MTNM business objectives ..... | 8 | +| 6.3 MTNM supporting documentation (SD) ..... | 9 | +| 6.4 MTNM CORBA IDL files ..... | 12 | +| 7 Referencing the TM Forum MTNM document set in ITU-T Recommendations ..... | 15 | +| Bibliography..... | 19 | + +# Introduction + +This Recommendation provides an overview of the M.3170-series of ITU-T Recommendations, which relate TM Forum's MTNM v3.0 specifications to ITU-T's TMN and NGNM architectures and frameworks and prove that MTNM is TMN compliant, TMN interface protocol conformant, and *Level B* TMN interface information conformant according to [ITU-T M.3010]. + +## **Multi-technology network management – Introduction and supporting documentation** + +# **1 Scope** + +This Recommendation provides a physical and logical overview of the TeleManagement Forum's multi-technology network management (MTNM) solution suite v3.0 [TMF MTNM v3.0] where the logical overview focuses on the MTNM business objectives and the suite of MTNM supporting documents. This Recommendation also explains the chosen approach to referencing the MTNM deliverables in ITU-T Recommendations such that they get hooked into ITU-T's management architectures and frameworks without the need to change any TM Forum deliverable. + +The MTNM solution suite v3.0, a TM Forum-approved document set ([TMF513], [TMF608], [TMF814], [TMF814A]), is an implementation standard of a TMN interface between the NML and the EML according to [ITU-T M.3010] for the FCAPS management of multi-technology fixed transport, access and aggregation networks. The MTNM implementation view specifies a CORBA-based TMN Q interface between an NMS (CORBA client or TMN manager) and an EMS (CORBA server or TMN agent which is in contact to the NEL). + +This Recommendation is a part of a series of Recommendations dealing with MTNM, and which has the following structure: + +- M.3170.0 Multi-technology network management: Introduction and supporting documentation. +- M.3170.1 Multi-technology network management: Business agreement (TMF513). +- M.3170.2 Multi-technology network management: Information agreement (TMF608). +- M.3170.3 Multi-technology network management: CORBA IDL solution set (TMF814) with implementation statement templates and guidelines (TMF814A). + +The MTNM specifications fulfil the very strong industry demand for a full-featured, commercially available, scaleable and non-proprietary element and network management interface implementation standard, which allows multi-vendor, multi-technology and multi-domain management systems to interoperate easily and seamlessly in an open architecture environment, thereby distinctly reducing the integration tax and overall operational expenses. As widely recognized achievements, the TM Forum's multi-company MTNM project has: + +- first, created a UML-based interface between the TMN network management layer (NML) and element management layer (EML), which provides the protocol-neutral foundation of such a "commercial out of the box integration" element and network management solution; and +- secondly, developed the UML model of the system view into a CORBA-based, highly interoperable implementation view that allows for low cost integration of MTNM systems. + +This Recommendation provides an overview of the MTNM solution suite and presents the chosen approach to relate the MTNM deliverables to ITU-T's TMN and NGNM architectures and frameworks in such a way that the MTNM NML-EML interface and the MTNM document set can be shown to be TMN conformant and compliant according to [ITU-T M.3010]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.805] ITU-T Recommendation G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.809] ITU-T Recommendation G.809 (2003), *Functional architecture of connectionless layer networks*. +- [ITU-T G.852.2] ITU-T Recommendation G.852.2 (1999), *Enterprise viewpoint description of transport network resource model*. +- [ITU-T M.3010] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3013] ITU-T Recommendation M.3013 (2000), *Considerations for a telecommunications management network*. +- [ITU-T M.3020] ITU-T Recommendation M.3020 (2007), *TMN interface specification methodology*. +- [ITU-T M.3050.x] ITU-T Recommendations M.3050.x (2004), *Enhanced Telecom Operations Map (eTOM)*. + +NOTE 1 – This series of Recommendations has the following structure: + +M.3050.0 (2004), eTOM – Introduction. + +M.3050.1 (2004), eTOM – The business process framework. + +M.3050.2 (2004), eTOM – Process decompositions and descriptions. + +M.3050.3 (2004), eTOM – Representative process flows. + +M.3050.4 (2004), eTOM – B2B integration: Using B2B inter-enterprise integration with the eTOM. + +M.3050 Supplement 1 (2004), eTOM – ITIL application note. + +M.3050 Supplement 2 (2004), eTOM – Public B2B Business Operations Map (BOM). + +M.3050 Supplement 3 (2004), eTOM to M.3400 mapping. + +- [ITU-T M.3060] ITU-T Recommendation M.3060/Y.2401 (2006), *Principles for the Management of Next Generation Networks*. + +- [ITU-T M.3100] ITU-T Recommendation M.3100 (2005), *Generic network information model*. + +- [ITU-T Q.816.x] ITU-T Recommendations Q.816.x (2001-2007), *CORBA-based TMN services*. + +NOTE 2 – This series of Recommendations has the following structure: + +Q.816 (2001), *CORBA-based TMN services*. + +Q.816.1 (2001), *CORBA-based TMN services: Extensions to support coarse-grained interfaces*. + +Q.816.2 (2007), *CORBA-based TMN services: Extensions to support service-oriented interfaces*. + +- [ITU-T X.735] ITU-T Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems Management – Log control function.* +- [ITU-T X.780.x] ITU-T Recommendations X.780.x (2001-2007), *TMN guidelines for defining CORBA managed objects.* +- NOTE 3 – This series of Recommendations has the following structure: +X.780 (2001), *TMN guidelines for defining CORBA managed objects.* +X.780.1 (2001), *TMN guidelines for defining coarse-grained CORBA managed object interfaces.* +X.780.2 (2007), *TMN guidelines for defining service-oriented CORBA managed objects and façade objects.* +- [ITU-T X.781] ITU-T Recommendation X.781 (2001), *Requirements and guidelines for Implementation Conformance Statements proformas associated with CORBA-based systems.* +- [ITU-T Y.110] ITU-T Recommendation Y.110 (1998), *Global Information Infrastructure principles and framework architecture.* +- [ITU-T Y.2011] ITU-T Recommendation Y.2011 (2004), *General principles and general reference model for Next Generation Networks.* +- [ITU-T Y.2012] ITU-T Recommendation Y.2012 (2006), *Functional requirements and architecture of the NGN release 1.* +- [TMF MTNM v2.1] TM Forum, *Multi-Technology Network Management (MTNM) Solution Suite Version 2.1* (2002) (consisting of [TMF513], [TMF608], [TMF814], TMF814A v2.1), except for the tables of references contained in Appendix B of [TMF513 v2.1] and Appendix B of [TMF608 v.2.1]. +- NOTE 4 – Refer to Notes 6 and 7 for an explanation of this exception. +- [TMF MTNM v3.0] TM Forum, *Multi-Technology Network Management (MTNM) Solution Suite Version 3.0* (2004) (consisting of [TMF513], [TMF608], [TMF814] and [TMF814A] and the MTNM Documentation Guide), except for the tables of references contained in Appendix B of [TMF513] and Appendix B of [TMF608]. +- NOTE 5 – Refer to Notes 6 and 7 for an explanation of this exception. +- [TMF513] TM Forum TMF513 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: The Business Agreement*, except for the table of references contained in Appendix B. +- NOTE 6 – This table of references consists of the columns "reference", "description" and "brief use summary". Whilst the last column is meant to clearly indicate for each reference (i.e., row) whether the reference is needed for the implementation of the specification (a normative reference) or was used for the development of the specification (a non-normative reference), it turned out that this goal was not reached unambiguously in all cases. Therefore, this Recommendation does not reference this table. Instead, the truly normative references of [TMF513], namely [TMF608], [ITU-T G.805] and [ITU-T X.735], are added to this clause while the useful and available non-normative references are added to the bibliography (see [b-TMF044] and [b-TMF402]). +- [TMF608] TM Forum TMF608 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: Information Agreement*, Rational Rose™ (UML) version and generated HTML version, except for the table of references contained in Appendix B. + +NOTE 7 – This Recommendation does not reference this table for the same reasons explained for TMF513 in Note 1. Instead, the truly normative references of [TMF608], namely [TMF513], [ITU-T G.805] and [ITU-T X.735], are added to this clause while the useful and available non-normative references are added to the bibliography (see [b-TMF044], [b-TMF045] and [b-TMF404]). + +- [TMF814] TM Forum TMF814 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set.* +- [TMF814A] TM Forum TMF814A Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: Implementation Statement Templates and Guidelines.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **analysis phase:** [ITU-T M.3020]. +- 3.1.2 **design phase:** [ITU-T M.3020]. +- 3.1.3 **element management layer (EML):** [ITU-T M.3010]. +- 3.1.4 **interface:** [ITU-T M.3010]. +- 3.1.5 **network element layer (NEL):** [ITU-T M.3010]. +- 3.1.6 **network management layer (NML):** [ITU-T M.3010]. +- 3.1.7 **operations system (OS):** [ITU-T M.3010]. +- 3.1.8 **Q interface:** [ITU-T M.3010]. +- 3.1.9 **requirements phase:** [ITU-T M.3020]. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +- ATM Asynchronous Transfer Mode +- BA Business Agreement +- CLI Command Line Interface +- CORBA Common Object Request Broker Architecture +- CTP Connection Termination Point +- DSL Digital Subscriber Line +- DWDM Dense Wavelength Division Multiplexing +- EM Element Management +- EML Element Management Layer +- EMS Element Management System +- eTOM enhanced Telecom Operations Map +- FCAPS Fault, Configuration, Accounting, Performance and Security +- FRA Functional Requirements and Architecture + +| | | +|------|--------------------------------------------------------------------------------------------------------| +| FTP | Floating Termination Point | +| GCT | Graphical User Interface Cut-Through | +| GDMI | Guidelines for the Definition of Management Interface | +| GTP | Group Termination Point | +| GUI | Graphical User Interface | +| HTML | HyperText Markup Language | +| IA | Information Agreement | +| IDL | Interface Definition Language | +| IMA | Inverse Multiplexing for ATM | +| IPR | Intellectual Property Rights | +| IRP | Integration Reference Point | +| IS | Implementation Statement | +| IS | Information Service | +| MIB | Management Information Base | +| MISM | Management Interface Specification Methodology | +| MLSN | Multi-Layer SubNetwork | +| MOC | Managed Object Class | +| MTNM | Multi-Technology Network Management | +| NE | Network Element | +| NEF | Network Element Function block | +| NEL | Network Element Layer | +| NG | Next Generation | +| NGN | Next Generation Network | +| NGNM | Next Generation Network Management | +| NM | Network Management | +| NML | Network Management Layer | +| NMS | Network Management System | +| OMG | Object Management Group (see http://www.omg.org/index.htm ) | +| OOAD | Object-Oriented Analysis and Design | +| ORB | Object Request Broker | +| OS | Operations System | +| OSF | Operations System Function block | +| OTH | Optical Transport Hierarchy | +| PDH | Plesiochronous Digital Hierarchy | +| PTP | Physical Termination Point | + +| | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Q | type of interface applied at q reference points (i.e., between NEF and OSF, or OSF and OSF, or Q Adaptation Function block and OSF) (see [ITU-T M.3010], [ITU-T M.3013] and [ITU-T M.3060]) | +| RAD | Requirements, Analysis and Design (and conformance) | +| SD | Supporting Document(ation) | +| SDH | Synchronous Digital Hierarchy | +| SM | Service Management | +| SNC | SubNetwork Connection | +| SNMP | Simple Network Management Protocol | +| SOA | Service-Oriented Approach/Architecture | +| SONET | Synchronous Optical Network | +| SS | Solution Set | +| TL1 | Transaction Language 1 | +| TM | Telecommunications Management | +| TM | TeleManagement | +| TMF | TeleManagement Forum (see http://www.tmforum.org/browse.aspx ) | +| TMN | Telecommunications Management Network | +| TP | Termination Point | +| UML | Unified Modelling Language | +| VCAT | Virtual Concatenation | + +# 5 Conventions + +This Recommendation does not use any particular notational or other conventions. + +# 6 MTNM overview + +This clause introduces the four MTNM views according to the popular RAD paradigm and relates them to the MTNM deliverables, provides an overview of the file structure of these deliverables including the numerous supporting documents and CORBA IDL files, and summarizes the business objectives that initiated the multi-company effort to develop the MTNM specifications. + +## 6.1 MTNM deliverables + +MTNM specifies an NML-EML interface according to [ITU-T M.3010] for the FCAPS management of multi-technology fixed networks. The specifications use TM Forum templates and MTNM-specific templates. Methodology and templates follow the widespread requirements, analysis and design (RAD) paradigm and comply with [ITU-T M.3020] and the template-based guidelines for the definition of management interface (GDMI) that are progressed in the [ITU-T M.3020.x]. + +Object-oriented analysis and design (OOAD) principles, but also service-oriented design principles, and an iterative three-phase process, namely the RAD methodology, have been applied to develop and progress the MTNM specifications, which provide four views of the NML-EML interface: + +- Requirements – the *business view*; +- Analysis – the *system view*; +- Design and conformance – the *implementation view* and the *deployment view*. + +### 6.1.1 Deliverables of the MTNM Solution Suite v3.0 + +The companion ITU-T Recs M.3170.1, M.3170.2 and M.3170.3 introduce the corresponding MTNM deliverables each of which consists of a set of files: + +- The MTNM business view is specified through requirements and use cases in the *Business Agreement* (BA) [TMF513], which is introduced by ITU-T Rec. M.3170.1. +- The MTNM system view is specified in UML in the *Information Agreement* (IA) [TMF608], which is introduced by ITU-T Rec. M.3170.2. +- From the beginning, the MTNM project has chosen CORBA as the interface language and communication technology for implementing and deploying the system view; the CORBA-based implementation and deployment views of MTNM are specified in the HTML-documented *Solution Set* (SS) [TMF814] and associated *Implementation Statement* (IS) *Templates and Guidelines* [TMF814A], which are introduced by ITU-T Rec. M.3170.3. +- The MTNM *Supporting Documentation* (SD) [TMF MTNM v3.0] not only guides and lightens the practical work with the MTNM views but also includes normative parts of the interface such as name/value pairs; it is introduced in this Recommendation and referred to from the rest of the M.3170-series of ITU-T Recommendations. + +### 6.1.2 File structure of the MTNM Solution Suite v3.0 + +The entire MTNM Solution Suite v3.0 [TMF MTNM v3.0] consists of the following files: + +- Documentation Guide: + - (6 pages) MTNM\_v3.0\_DocumentationGuide.pdf (90 kbit/s). +- Business Agreement: + - (565 pages) TMF513\TMF513\_V3.0.pdf (5260 kbit/s). + - (310 pages) 14 supporting documents (see clause 6.3). +- Information Agreement – Rational Rose™ (UML) version: + - (26 pages) TMF608-MDL\TMF608v3.0-MDL\_2004\_04.pdf (85 kbit/s). + - (389 pages) 24 supporting documents (see clause 6.3). + - UML model TMF608-MDL\TMF608v3.0-2004\_04.mdl (2899 kbit/s). +- Information Agreement – HTML version: + - (26 pages) TMF608-HTML\TMF608v3.0-HTML\_2004\_04.pdf (85 kbit/s). + - (389 pages) 24 supporting documents (see clause 6.3). + - HTML documentation folder (generated by Rational Rose™) TMF608-HTML\TMF608v3.0-html\ (2694 files). + +- CORBA Solution Set: + - (1 page) TMF814\_Version\_3.0\INSTALL\_ReadMe.txt (1 kbit/s). + - (1 page) TMF814\_Version\_3.0\ReadMe.txt (1 kbit/s). + - (17 pages) TMF814\_Version\_3.0\TMF814InterfaceVersion3.0.pdf (76 kbit/s). + - (564 pages) 37 supporting documents (see clause 6.3). + - (234 pages) 26 TMF CORBA IDL files (see clause 6.4). + - (61 pages) 13 OMG CORBA IDL files (see clause 6.4). + - HTML documentation folder (generated by Doxygen™) +TMF814\_Version\_3.0\TMF814\_Documentation\html\ (1587 files). +- Implementation Statement for CORBA: + - (103 pages) TMF814A\TMF814A-Version3.doc (1450 kbit/s). + - (30 pages) 2 supporting documents (see clause 6.3). + +These files are not part of the M.3170-series of ITU-T Recommendations but are available from the TM Forum. It should be noted that the TM Forum may change this file structure in subsequent releases of MTNM. + +## 6.2 MTNM business objectives + +The composition of today's telecommunication networks has contributed to the complexity of managing these networks. The networks are commonly composed of network elements (NEs) provided by various equipment vendors. The task of interoperation extends beyond the network element layer up to the TMN management layers, to include interoperability between multi-vendor element and network (and service) management systems provided by the equipment vendors or third party companies. + +Service providers have also taken advantage of technological advancements in transport network equipment. It is not uncommon for service providers to deploy next generation, multi-technology, high-density network elements, or "hybrid NEs" also known as "multi-service provisioning platforms", as these network elements provide new services and optimal equipment and network resource utilization. However, network management (NM) solutions very often apply only to a single, specific network technology and are based on technology-specific (or even vendor-specific) SNMP MIBs, CLI interfaces or TL1 interfaces. + +While equipment vendors become able to deliver more and more powerful multi-service networks, the management tasks have become much more complex due to the volatile service portfolio and personalization that they need to support. The lack of a common management framework results in high operational and development cost to the service providers due to the intensive manual customizations required per customer and per network technology, and the system integration tax to develop interoperable point-to-point solutions among vendor products. + +Service providers have become concerned that the increase in network capabilities will also increase the complexity, unnecessary variety and duplication of the network management systems and underlying NM models, in particular in multi-vendor environments. This would result in an integration tax – a cost that must be paid but that returns little in business value and that may still result in data islands. As a consequence, there is a very strong industry demand for a full-featured but lightweight, commercially available, scaleable and non-proprietary element and network management interface implementation standard that allows multi-vendor, multi-technology and multi-domain management systems to interoperate easily and seamlessly in an open architecture environment, thereby distinctly reducing the integration tax and overall operational expenses. + +The objective of the TM Forum's *MTNM project* is, in the first place, to create an UML-based interface between the TMN network management layer (NML) and element management layer + +(EML), which provides the protocol-neutral foundation of such a "commercial out of the box integration" element and network management solution, and, secondly, to develop the UML model of the system view into a CORBA-based implementation view that is very efficient, very easy-to-use and highly interoperable, and therefore allows for low cost integration of MTNM systems. + +The MTNM interface model supports the FCAPS and eTOM [ITU-T M.3050.x] management of multi-technology fixed networks with wireline and wireless physical layers. [TMF MTNM v3.0] includes PDH, SONET/SDH, ATM, frame relay, DWDM/OTH, DSL and point-to-point Ethernet. MTNM progression aims to gradually cover the unified management of all proven or emerging, fixed circuit-switched or packet-switched transport, access and aggregation network technologies (e.g., Ethernet bridging, control plane management) but is not concerned with mobile network management. + +The MTNM NML-EML interface supports a wide variety of element and network management business scenarios from the configuration of ports and provisioning of connections to the retrieval of alarm, equipment inventory and NE and network performance information. Key areas of the business scenarios that are supported by MTNM include, but are not limited to: + +- inventory discovery; +- fault management; +- port configuration (with profile mechanisms); +- connectivity provisioning (with protection and restoration capabilities); +- equipment provisioning (NEs, equipment holders, equipment units); +- performance management; +- maintenance management; +- security management. + +Service providers will benefit from the common multi-technology network management interface that is able to translate the service definitions made in service management (SM) systems into technology-specific implementations in a uniform way. Such benefits include, for example: + +- Rapid service delivery by decreasing service creation and activation time. +- Fast introduction of new technologies in the network without causing major changes to the interfaces at the network management level. +- Increased operating efficiency through automation and smart integration of element and network management systems and solutions. +- Enabling smooth and standardized multi-vendor interoperability that affords service providers the option of choosing various vendor products according to competitive differentiation. +- Allowing equipment and software vendors to offer vendor-specific extensions and diversifications in an interoperable and easy-to-implement way. + +Refer to [b-Siemens AG] and the companion ITU-T Rec. M.3170.3 for technical details on the CORBA-based MTNM NML-EML interface that support these business objectives. + +## **6.3 MTNM supporting documentation (SD)** + +As shown in clause 6.1.2 the four main MTNM deliverables are packaged together with a number of so-called supporting documents. Such supporting documents provide normative and/or informative information on the MTNM interface in support of the main deliverables. Examples of normative information are interface parameters in the form of name/value pairs and details on managed object attributes, examples of informative documents are tutorial and background material on specific technologies such as DSL or IMA or the SDH and SONET multiplexing hierarchies. + +Table 6-1 provides an overview of MTNM v3.0's SD with short descriptions and with indications of which SDs are bundled together with the individual deliverables of clause 6.1.2. + +The files listed in Table 6-1 are not part of the M.3170-series of ITU-T Recommendations but are available from the TM Forum together with the MTNM deliverables listed in clause 6.1.2. It should be noted that the TM Forum may change structure and contents of the MTNM SD in subsequent releases of MTNM. + +NOTE – Some SD descriptions in Table 6-1 refer to companion documents thereby indicating that there are relationships between some SDs. Refer to the companion ITU-T Recs M.3170.1, M.3170.2 and M.3170.3 for an overview of the dependencies between supporting documents. + +**Table 6-1 – Overview of supporting documentation of MTNM v3.0** + +| File name of supporting document | TMF513 | TMF608 | TMF814 | TMF814A | Description of supporting document | +|----------------------------------------------------|--------|--------|--------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalInfoUsage.pdf | | | X | | A mechanism is provided to apply additional information (name/value pairs) to operations and responses from the managed resources. Any additional information is optional: the EMS need not make available this information and the NMS need not interpret it. When the EMS wants to implement a feature that is predefined by additional info parameters, it SHALL use the predefined names and values to achieve multi-vendor interoperability, and when the EMS implements vendor-specific additional info parameters subject to bilateral agreements with NMS vendors, the NMSs SHOULD interpret these parameters. | +| AVC_SC_Notifications.pdf | | | X | | Provides a list of the attribute value and state change notifications along with the data that should be conveyed over the interface. | +| BundledSNC.pdf | | X | X | | The MTNM interface supports simultaneous operations on SNCs grouped in bundles. This SD explains the concept and usage of bundled SNCs. | +| Changes_to_Version 2-1.pdf | | X | | | This SD summarizes the changes that were applied to migrate the UML model of MTNM v2.1 to the UML model of MTNM v3.0. | +| conformanceDefinitions.pdf | X | X | X | | Provides ATM service category and conformance definitions. | +| ContainedTPs.pdf | | X | X | | This supporting document provides specific naming details for a number of cases of TP containment using the layered model and is a companion SD to the supporting documents objectNaming.pdf and layers.pdf. | +| DSLOverview.pdf | | | X | | Provides an overview of DSL technology as a companion SD to layers.pdf. | +| encodingX731M3100.pdf | | X | X | | Explains how to provide ITU-T Rec. X.731 and [ITU-T M.3100] state and status information in the event fields defined in the MTNM interface. | +| encodingX733.pdf | | | X | | Explains how to provide ITU-T Rec. X.733 alarm information in the event fields defined in the MTNM interface. | +| EquipmentModel.pdf | | X | X | | Specifies the MTNM equipment model and states, and provides examples. | +| featuresMatrix.xls
• sheet v2.1
• sheet v3.0 | | | | X | Provides feature lists for MTNM v2.1 and MTNM v3.0, relates the features to the CORBA IDL operations and managed object classes (i.e., the MTNM interface capabilities) and makes a number of comments. | +| FeatureSummaryVersion3.pdf | X | X | X | X | Provides an overview of the features of the MTNM interface release 3.0 that are additional to those of the MTNM interface release 2.1. | +| guiCutThrough.pdf | | | X | | Explains the NMS to EMS GUI cut-through. | +| IMOOverview.pdf | | | X | | Provides an overview of inverse multiplexing technologies (VCAT, IMA, etc.) and their use with the MTNM interface. | + +**Table 6-1 – Overview of supporting documentation of MTNM v3.0** + +| File name of supporting document | TMF513 | TMF608 | TMF814 | TMF814A | Description of supporting document | +|----------------------------------|--------|--------|--------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| iterators.pdf | | | X | | Iterators are used extensively. This SD explains their usage. | +| LayeredParameters.pdf | X | X | X | | The MTNM interface is built around a layered transmission model (see SD layers.pdf). This supporting document provides a normative specification and explanation of the parameters (name/value pairs) that may be reported and configured in the context of the layered TP model. | +| LayerRates.pdf | X | X | X | | Provides a normative list of supported transport layers (e.g., PDH, SDH /SONET, DSL, ATM) along with their naming and proposes a method for adding new layers where they are currently not supported. | +| layers.pdf | X | X | X | | The MTNM interface extends the layered model identified by [ITU-T G.805] and [ITU-T G.852.2]. This document explains the MTNM layered model, the extensions to ITU-T and their usage, from both a nodal and a network perspective and includes many examples. It provides guidelines for modelling the traffic capabilities of network elements. | +| LocationIdentification.pdf | | X | X | | Provides location and direction identification for PM parameters, probable causes and layered parameters, and includes examples. | +| maintenanceCommands.pdf | | X | X | | Maintenance operations are supported by the MTNM interface for certain technologies. This document summarizes and explains these maintenance commands and the corresponding signal flows. | +| MappingIASS.pdf | | | X | | Provides a mechanism to relate the details of the implementation in the CORBA Solution Set [TMF814] to the UML model provided in the Implementation Agreement [TMF608]. | +| modelDiagramComponents.ppt | | | X | | This SD is a companion to the SD layers.pdf that provides the diagram model components used in the layers document to aid in the production of compatible layers-like diagrams that represent a specific solution. | +| modesOfOperation.pdf | | X | X | | There are several ways that an NMS may choose to use the SNC concept. This document explains these various modes of operation. | +| NativeEMSName.pdf | X | | | | This document contains the rules to be used for determining the values for the native EMS name and user label attributes. | +| objectNaming.pdf | X | X | X | | Provides an overview and specification of the managed object naming used across the MTNM interface. | +| OMGservicesUsage.pdf | | | X | | The MTNM interface makes use of both the notification service and the telecom log service from the OMG. This normative document explains their usage in detail and defines the notification types of MTNM v3.0. | +| overview_NML-EML_Interface.pdf | | | X | | This supporting document provides an overview of the TMF814 CORBA Solution Set of the TM Forum's MTNM NML-EML interface version 3.0, which has been constructed as a result of collaboration between equipment and OS vendors and service providers. | +| PerformanceParameters.pdf | X | X | X | | Provides a specification and explanation of the performance parameters. | +| PGPParameters.pdf | | X | X | | Specifies and explains the protection group parameters. | +| PMExample.txt | X | X | X | | This is a companion supporting document to PMFileFormat.pdf that provides an example of a performance monitoring and measurement (PM) file in both plain text and Excel formats. | +| PMExample.xls | X | X | X | | | +| PMFileFormat.pdf | X | X | X | | The interface supports the reporting of bulk PM data. This document provides a normative definition of the PM file format. | + +**Table 6-1 – Overview of supporting documentation of MTNM v3.0** + +| File name of supporting document | TMF513 | TMF608 | TMF814 | TMF814A | Description of supporting document | +|----------------------------------|-----------|-----------|-----------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ProbableCauses.pdf | X | X | X | | Provides a specification of the standard probable causes that shall be used when reporting an alarm. | +| protectionSwitch.pdf | | | X | | Provides an overview of the protection switching model and operations for trail protection and applies it to a number of example scenarios. | +| SNCStateDiagram.pdf | | | X | | Provides an explanation and specification of the various states of an SNC. | +| SNCTypes.pdf | X | X | X | | The SNC is a fundamental component in the provision of connectivity across the network. This document defines the SNC types and provides examples of their usage. | +| TCAs.pdf | X | X | X | | Provides a graphical representation of the threshold crossing alert types and corresponding trigger and clear values. | +| TPPoolRelationship.pdf | | X | X | | Explains the relationship between TP pools and their associated TPs. | +| trafficParameters.pdf | | X | X | | Provides a specification and explanation of ATM traffic parameters. | +| versioning.pdf | | | X | | Provides details and examples on how to operate new and old versions of the MTNM interface. | +| 40 supporting documents | 14 | 24 | 37 | 2 | | + +## 6.4 MTNM CORBA IDL files + +Tables 2 and 3 present an overview of the IDL files provided with the CORBA Solution Set TMF814 of [TMF MTNM v3.0]. There are two types of IDL files: *TMF files* and *OMG files*. The TMF files were developed as part of the MTNM project (see clause 6.2) whilst the OMG files are publicly available IDL specifications of the Object Management Group. The IDL files of [TMF MTNM v3.0] are fully backward compatible extensions of the IDL files of [TMF MTNM v2.1]. As a rule, each IDL file consists of a single CORBA module whose name equals the file name. + +**Table 6-2 – Overview of TMF CORBA IDL files of MTNM v3.0** + +| File name of CORBA IDL file | Description of CORBA IDL file | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| aSAP.idl | The CORBA module aSAP contains the definition of the alarm severity assignment profiles of the MTNM interface. | +| common.idl | The CORBA module common contains the definition of the Common_I interface of the MTNM interface. | +| CosNotifyComm.idl | The CORBA module CosNotifyComm is a copy from OMGidl\CosNotifyComm.idl (see Table 6-3) where EventType has been replaced by _EventType. | +| emsMgr.idl | The CORBA module emsMgr contains the definitions of the EMS_T managed object class and the EMS Manager interface EMSMgr_I of the MTNM interface. | +| emsSession.idl | The CORBA module emsSession contains the definitions of the EmsSession_I interface and the potentially supported manager names of the MTNM interface. | + +**Table 6-2 – Overview of TMF CORBA IDL files of MTNM v3.0** + +| File name of CORBA IDL file | Description of CORBA IDL file | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| emsSessionFactory.idl | The module emsSessionFactory contains the definition of the EmsSessionFactory_I interface of the MTNM interface. | +| equipment.idl | The CORBA module equipment contains the definitions of the equipment and equipment holder managed object classes and the Equipment Manager interface EquipmentInventoryMgr_I. | +| globaldefs.idl | The CORBA module globaldefs defines common types used by other CORBA modules of the MTNM interface. It is intended as a common repository for definitions that need to be exported across modules. | +| guiCutThrough.idl | The CORBA module guiCutThrough contains the definition of the GUI Cut-Through Manager interface GuiCutThroughMgr_I of the MTNM interface, with related IDL types. | +| maintenanceOps.idl | The CORBA module maintenanceOps contains the definition of the Maintenance Manager interface MaintenanceMgr_I of the MTNM interface, with related IDL type and interface definitions. | +| managedElement.idl | The CORBA module managedElement contains the definition of the managed element managed object class ManagedElement_T of the MTNM interface, which is an SO management abstraction of an NE. | +| managedElementManager.idl | The CORBA module managedElementManager contains the definition of the Managed Element Manager interface ManagedElementMgr_I of the MTNM interface. | +| mtnmVersion.idl | The CORBA module mtnmVersion contains the definition of the version interface Version_I of the MTNM interface. | +| multiLayerSubnetwork.idl | The CORBA module multiLayerSubnetwork contains the definitions of the MLSN MOC MultiLayerSubnetwork_T with related IDL types and interfaces, and the MLSN Manager interface MultiLayerSubnetworkMgr_I. | +| nmsSession.idl | The CORBA module nmsSession contains the definition of the NmsSession_I interface of the MTNM interface. | +| notifications.idl | The CORBA module notifications contains the definitions of the notification portions of the MTNM interface that are to be used in structured event push notifications and on-demand pull notifications. | +| performance.idl | The CORBA module performance contains the definitions of the performance management types, structures and MOCs of the MTNM interface. It also contains the definition of the Performance Management Manager interface PerformanceManagementMgr_I of the MTNM interface, which is used to gain access to operations dealing with performance monitoring and measurement (PM). | +| protection.idl | The CORBA module protection contains the definitions of the protection and equipment protection management structures, with related IDL types and interfaces, and the Protection Manager interface ProtectionMgr_I of the MTNM interface. | + +**Table 6-2 – Overview of TMF CORBA IDL files of MTNM v3.0** + +| File name of CORBA IDL file | Description of CORBA IDL file | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| session.idl | The CORBA module session contains the definition of the Session_I interface of the MTNM interface. | +| softwareAndDataManager.idl | The CORBA module softwareAndDataManager contains the definition of the Software and Data Manager interface SoftwareAndDataMgr_I and associated IDL types and interfaces. | +| subnetworkConnection.idl | The CORBA module subnetworkConnection contains the definition of the SNC managed object class SubnetworkConnection_T of the MTNM interface and associated IDL types and interfaces. | +| terminationPoint.idl | The CORBA module terminationPoint contains the definition of the TP and GTP managed object classes TerminationPoint_T and GTP_T of the MTNM interface and associated IDL types and interfaces. | +| topologicalLink.idl | The CORBA module topologicalLink contains the definition of the topological link managed object class TopologicalLink_T of the MTNM interface and associated IDL types and interfaces. | +| trafficDescriptor.idl | The CORBA module trafficDescriptor contains the definitions of the traffic descriptor managed object class with related types and interfaces and the Traffic Descriptor Manager interface TrafficDescriptorMgr_I of the MTNM interface. | +| transmissionDescriptor.idl | The CORBA module transmissionDescriptor contains the definitions of the transmission descriptor managed object class with related types and interfaces, and the Transmission Descriptor Manager interface TransmissionDescriptorMgr_I of the MTNM interface. | +| transmissionParameters.idl | The CORBA module transmissionParameters contains various definitions common to PTPs, CTPs, FTPs, GTPs, SNCs and MLSNs of the MTNM interface (e.g., layered parameters). | +| 26 TMF CORBA IDL files | | + +**Table 6-3 – Overview of OMG CORBA IDL files of MTNM v3.0** + +| File name of CORBA IDL file | Description of CORBA IDL file | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OMGidl\CosEventChannelAdmin.idl | The OMG module CosEventChannelAdmin defines the proxy and admin interfaces that inherit from the CosEventComm interfaces, and the EventChannel interface of the event service. | +| OMGidl\CosEventComm.idl | The OMG module CosEventComm defines the interfaces PushConsumer , PushSupplier , PullSupplier and PullConsumer that support the event service communication styles. | +| OMGidl\CosNaming.idl | The OMG module CosNaming defines the interfaces and associated IDL types of the naming service. | + +**Table 6-3 – Overview of OMG CORBA IDL files of MTNM v3.0** + +| File name of CORBA IDL file | Description of CORBA IDL file | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OMGidL\CosNotification.idl | The OMG module CosNotification defines the QoSAdmin and AdminPropertiesAdmin interfaces and the basic types of the notification service such as StructuredEvent and the standard QoS and admin properties. | +| OMGidL\CosNotifyChannelAdmin.idl | The OMG module CosNotifyChannelAdmin defines the proxy and admin interfaces that inherit from the CosNotifyComm interfaces and the EventChannel and EventChannelFactory interfaces of the notification service. | +| OMGidL\CosNotifyComm.idl | The OMG module CosNotifyComm extends the CosEventComm interfaces to define the interfaces PushConsumer , PushSupplier , PullSupplier and PullConsumer that support the corresponding notification service communication styles. It also defines the interfaces for the structured and event batch communication styles. | +| OMGidL\CosNotifyFilter.idl | The OMG module CosNotifyFilter defines the interfaces supported by the filter (and mapping filter) objects used by the notification service. | +| OMGidL\CosTrading.idl | The OMG module CosTrading defines the interfaces and associated IDL types of the trading service. | +| OMGidL\DsEventLogAdmin.idl | The OMG module DsEventLogAdmin defines the EventLog and EventLogFactory interfaces. | +| OMGidL\DsLogAdmin.idl | The OMG module DsLogAdmin defines the Log and LogMgr interfaces and associated IDL types. | +| OMGidL\DsNotifyLogAdmin.idl | The OMG module DsNotifyLogAdmin defines the NotifyLog and NotifyLogFactory interfaces. | +| OMGidL\orb.idl | This file contains the dummy ORB module CORBA needed for generating the HTML documentation. | +| OMGidL\TimeBase.idl | The OMG module TimeBase of the time service defines IDL types used by the telecom log service. | +| 13 OMG CORBA IDL files | | + +The files listed in Tables 6-2 and 6-3 are not part of the M.3170-series of ITU-T Recommendations but are available from the TM Forum together with [TMF814] and [TMF MTNM v3.0] (see also clause 6.1.2). It should be noted that the TM Forum may change structure and contents of the IDL files in subsequent releases of MTNM. + +# 7 Referencing the TM Forum MTNM document set in ITU-T Recommendations + +The M.3170-series of ITU-T Recommendations normatively reference TM Forum approved documents and point to further in-force ITU-T Recommendations in order to relate the TM Forum documents to ITU-T's key management and functional frameworks and architectures, specifically: + +- M.3170.0 references the MTNM Solution Suite [TMF MTNM v3.0]; +- M.3170.1 references the MTNM Business Agreement (BA) [TMF513]; +- M.3170.2 references the MTNM Information Agreement (IA) [TMF608]; + +- M.3170.3 references the MTNM CORBA Solution Set (SS) [TMF814] and the MTNM Implementation Statement (IS) for CORBA [TMF814A]. + +The referenced MTNM v3.0 deliverables have been described in detail in clause 6. Figure 7-1 provides a graphical overview of the M.3170-series of ITU-T Recommendations and the MTNM v3.0 deliverables. + +That way the MTNM interface and the MTNM document set can be shown to be: + +- TMN interface protocol conformant; +- Level B TMN interface information conformant; and +- TMN compliant; + +according to [ITU-T M.3010] and so they get hooked into the ITU-T TMN frameworks and architectures without changing the original TM Forum deliverables. + +![Figure 7-1: Overview of M.3170-series and MTNM v3.0 deliverables. The diagram shows four main components arranged around a central 'Supporting documentation' circle (M.3170.0). Top-left: 'Protocol-neutral interface specification' (M.3170.1) with 'Requirements: Business Agreement (TMF513)' and a PDF version of TMF513. Top-right: 'Object model: Information Agreement (TMF608)' (M.3170.2) with PDF, HTML, and UML versions of TMF608. Bottom-left: 'Protocol-specific interface specification' (M.3170.3) with 'Conformance: Implementation Statement (TMF814A)' and a Word version of TMF814A. Bottom-right: 'CORBA IDL: Solution Set (TMF814)' (M.3170.3) with Introduction, Overview, HTML version, and IDL source files of TMF814. Arrows labeled 'Refer to' point from each component to the central documentation. Red double-headed arrows labeled 'Traceability' connect the top and bottom components, and the left and right components.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +M.3170.0(07)F\_7.1 + +Figure 7-1: Overview of M.3170-series and MTNM v3.0 deliverables. The diagram shows four main components arranged around a central 'Supporting documentation' circle (M.3170.0). Top-left: 'Protocol-neutral interface specification' (M.3170.1) with 'Requirements: Business Agreement (TMF513)' and a PDF version of TMF513. Top-right: 'Object model: Information Agreement (TMF608)' (M.3170.2) with PDF, HTML, and UML versions of TMF608. Bottom-left: 'Protocol-specific interface specification' (M.3170.3) with 'Conformance: Implementation Statement (TMF814A)' and a Word version of TMF814A. Bottom-right: 'CORBA IDL: Solution Set (TMF814)' (M.3170.3) with Introduction, Overview, HTML version, and IDL source files of TMF814. Arrows labeled 'Refer to' point from each component to the central documentation. Red double-headed arrows labeled 'Traceability' connect the top and bottom components, and the left and right components. + +**Figure 7-1 – Overview of M.3170-series and MTNM v3.0 deliverables** + +The certifications of the TMN interface protocol and information conformances depend on the *TMN guidelines for defining CORBA managed objects* specified by [ITU-T X.780.x], [ITU-T X.781] and [ITU-T Q.816.x], in particular on the novel concepts of *service-oriented CORBA managed objects*, façade objects and TMN support services, which were developed by ITU-T's former MTNM Focus Group [b-MTNMFG]. The ITU-T NGN Management Focus Group (NGNMFG), a group sponsored by ITU-T Study Group 4, identified the MTNM specifications as relevant to NGN management in the context of its specification architecture (see [ITU-T Roadmap]). + +Figure 7-2 shows how this Recommendation points to the MTNM Solution Suite and to the related ITU-T Recommendations on TMN and functional architectures. + +![Diagram showing the relationship between ITU-T Recommendations and TM Forum documents linked by M.3170.0. The diagram features a cloud of ITU-T Recommendations (M.3020, M.3100, Y.2011, Y.110, M.3010, G.805, Y.2012, M.3013, G.852.2, M.3050, G.809, M.3060) pointing to a central box 'MTNM NML-EML Interface solution Suite v3.0'. This box points to a sequence of TM Forum documents: MTNM Documentation Guide, SD, TMF513, TMF608, TMF814, and TMF814A. A separate box on the right lists 'ITU-T Recs on TMN (NGNM) and functional (NG) network architectures'.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +The diagram illustrates the relationships between ITU-T Recommendations and TM Forum documents as defined in the MTNM framework. At the top, a yellow cloud labeled 'ITU-T Recs on TMN (NGNM) and functional (NG) network architectures' contains several ITU-T Recommendations: M.3020, M.3100, Y.2011, Y.110, M.3010, G.805, Y.2012, M.3013, G.852.2, M.3050, G.809, and M.3060. An arrow from the cloud points to a central box labeled 'MTNM NML-EML Interface solution Suite v3.0'. Below this box, a sequence of TM Forum documents is shown: 'MTNM Documentation Guide', 'SD', 'TMF513', 'TMF608', 'TMF814', and 'TMF814A'. Arrows indicate dependencies between these documents, with 'SD' pointing to 'TMF513', 'TMF513' pointing to 'TMF608', 'TMF608' pointing to 'TMF814', and 'TMF814' pointing to 'TMF814A'. Dashed lines connect 'MTNM Documentation Guide' to 'SD' and 'TMF513'. A separate blue box on the right contains the text 'ITU-T Recs on TMN (NGNM) and functional (NG) network architectures'. The diagram is labeled 'M.3170.0(07)F\_7.2' at the bottom right. + +Diagram showing the relationship between ITU-T Recommendations and TM Forum documents linked by M.3170.0. The diagram features a cloud of ITU-T Recommendations (M.3020, M.3100, Y.2011, Y.110, M.3010, G.805, Y.2012, M.3013, G.852.2, M.3050, G.809, M.3060) pointing to a central box 'MTNM NML-EML Interface solution Suite v3.0'. This box points to a sequence of TM Forum documents: MTNM Documentation Guide, SD, TMF513, TMF608, TMF814, and TMF814A. A separate box on the right lists 'ITU-T Recs on TMN (NGNM) and functional (NG) network architectures'. + +**Figure 7-2 – ITU-T and TM Forum documents linked by M.3170.0** + +The TM Forum documents are depicted in a network view with dependency links while the ITU-T Recommendations are depicted in a non-linked NE view ("ITU-T Recommendation cloud") since it is considered within the responsibility of the referencing Recommendations to explain dependencies between TM Forum documents but not considered within their responsibility to point out dependencies between ITU-T documents. Each of the companion Recommendations of the M.3170-series of ITU-T Recommendations includes a similar diagrammatic presentation of the referencing role of the respective Recommendation, namely: + +- M.3170.1 references the *MTNM BA*; at the TM Forum side it explains the BA structure and contents, looks inside the SD box (BA-relevant supporting documents) and relates the BA to other key TM Forum documents; at the ITU-T side it depicts an ITU-T Recommendation cloud with the BA-relevant ITU-T Recommendations. +- M.3170.2 references the *MTNM IA*; at the TM Forum side it explains the IA structure and contents, looks inside the SD box (IA-relevant supporting documents) and relates the IA to other key TM Forum documents; at the ITU-T side it depicts an ITU-T Recommendation cloud with the IA-relevant ITU-T Recommendations. +- M.3170.3 references the *MTNM CORBA SS* and the *MTNM IS for CORBA*; at the TM Forum side it explains the SS and IS structures and contents, looks inside the SD box (SS- and IS-relevant supporting documents according to Table 6-1), and relates the SS and IS to other key TM Forum documents; at the ITU-T side it depicts an ITU-T Recommendation cloud with the SS- and IS-relevant ITU-T Recommendations, which encompasses the ITU-T framework for CORBA-based TMN interfaces [ITU-T X.780.x], [ITU-T X.781] and [ITU-T Q.816]. + +The M.3170-series of ITU-T Recommendations are considered to be light documents. They do not provide a full tutorial on MTNM but may well be considered a sort of crash course on MTNM. A more detailed *TM Forum/ITU-T documentation model* is for further study. Its essential parts would be first an "equivalence document", that mediates between the MTNM TMN framework fragments and details of the ITU-T TMN framework thereby making more MTNM details more easily readable, and secondly a version-specific (delta) "interface document" that instructs in + +MTNM interface usage from an ITU-T point of view, thereby providing a course on new MTNM details. The referencing of MTNM from the M.3170-series of ITU-T Recommendations as well as the design guidelines of the service-oriented CORBA framework for TMN interfaces [ITU-T X.780.x] and [ITU-T X.781] are first steps in this direction. As a consequence of the TM Forum/ITU-T documentation model, it will not be necessary to develop very detailed mappings between TMN items of the TM Forum MTNM specifications and related ITU-T Recommendations. + +# Bibliography + +The following references contain information that was used in the development of the M.3170-series of ITU-T Recommendations. + +- [b-ITU-T Roadmap] ITU-T Study Group 4, *NGN Management Specification Roadmap*, +[www.itu.int/ITU-T/studygroups/com04/roadmap.html](http://www.itu.int/ITU-T/studygroups/com04/roadmap.html) +- [b-MTNMFG] ITU-T Study Group 4, *Telecommunication Management Collaboration Focus Group – for MTNM*, +[www.itu.int/ITU-T/studygroups/com04/tmc/mtnm/index.html](http://www.itu.int/ITU-T/studygroups/com04/tmc/mtnm/index.html) +- [b-Siemens AG] Siemens AG (2003), *Using CORBA for MTNM*, TM Forum MTNM Contribution, +[www.tmforum.org/browse.asp?catID=2014](http://www.tmforum.org/browse.asp?catID=2014) +- [b-TMF044] TM Forum TMF044 v2.0 (2003), *TM Forum Glossary*, +[www.tmforum.org/browse.aspx?catid=860&linkID=28087](http://www.tmforum.org/browse.aspx?catid=860&linkID=28087) +- [b-TMF045] TM Forum TMF045 v1.1 (2000), *Common Information Structure (CIS)*, +[www.tmforum.org/browse.aspx?catid=860&linkID=25111](http://www.tmforum.org/browse.aspx?catid=860&linkID=25111) +- [b-TMF402] TM Forum TMF402 v5.10 (2005), *TMF Business Agreement Template*, +[www.tmforum.org/browse.aspx?catID=866&linkID=24300](http://www.tmforum.org/browse.aspx?catID=866&linkID=24300) +- [b-TMF404] TM Forum TMF404 v2.8 (2005), *TMF Information Agreement Template*, +[www.tmforum.org/browse.aspx?catID=866&linkID=24299](http://www.tmforum.org/browse.aspx?catID=866&linkID=24299) + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3170.1-200703-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adee0db0e36fe08d703a5774caf4083701b66613 --- /dev/null +++ b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bc4fbdfb01e06ddbe3204ff43129263ad7c008a2452500fa5b98c4e8b382454 +size 139732 diff --git a/marked/M/T-REC-M.3170.1-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3170.1-200703-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a29b17598eb267f72b8fd87b95f66a87778c7306 --- /dev/null +++ b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baac51ab6686b33f2106e2f59e6f194f6df5ae39ebc25a5000316e7fbd7d9ba4 +size 50419 diff --git a/marked/M/T-REC-M.3170.1-200703-I_PDF-E/raw.md b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2a2f7cbd9051f05f405f1e5013c291b901944ec7 --- /dev/null +++ b/marked/M/T-REC-M.3170.1-200703-I_PDF-E/raw.md @@ -0,0 +1,302 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3170.1** + +(03/2007) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Multi-technology network management: +Business agreement (TMF513)** + +ITU-T Recommendation M.3170.1 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3170.1** + +## **Multi-technology network management: Business agreement (TMF513)** + +## **Summary** + +The multi-technology network management (MTNM) solution suite realizes a TMN interface between the NML and EML according to ITU-T Recommendation M.3010 for the FCAPS management of multi-technology fixed transport, access and aggregation networks. + +This Recommendation explains the structure of the MTNM business agreement (TMF513) and relates its components to key Recommendations on TMN functionality for q reference points between the NML and EML. It wraps TMF513 and associated supporting documents by referencing them normatively and relating them to identified Recommendations on TMN (NGNM) and principles of functional (NG) network architectures (such as transmission layering without adaptation details). This Recommendation can also be used as a lead-in to the MTNM business agreement. + +###### **Source** + +ITU-T Recommendation M.3170.1 was approved on 16 March 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2007 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 4 Abbreviations..... | 3 | +| 5 Conventions ..... | 3 | +| 6 TMF513 overview – A lead-in to the MTNM business agreement..... | 3 | +| 6.1 Relationship to other M.3170-series Recommendations..... | 4 | +| 6.2 Relationship to other TMN Recommendations..... | 4 | +| 6.3 Relationship to other TM Forum specifications..... | 5 | +| 7 Referencing TMF513..... | 6 | +| Bibliography..... | 8 | + + + +## Multi-technology network management: Business agreement (TMF513) + +# 1 Scope + +The multi-technology network management (MTNM) solution suite is an implementation standard of a TMN interface between the NML and EML according to [ITU-T M.3010] for the FCAPS management of multi-technology fixed transport, access and aggregation networks. The MTNM implementation view specifies a CORBA-based TMN Q interface between an NMS (CORBA client or TMN manager) and an EMS (CORBA server or TMN agent which is in contact to the NEL). + +The MTNM solution suite consists of the following deliverables: + +- The MTNM business view is specified in the business agreement (BA) TMF513. +- The MTNM system view is specified in UML in the information agreement (IA) TMF608. +- The MTNM CORBA-based implementation and deployment views are specified in the CORBA IDL solution set (SS) TMF814 (with HTML documentation) and associated implementation statement (IS) templates and guidelines TMF814A. +- The MTNM supporting documentation (SD) guides and lightens the work with the MTNM views and also includes normative parts of the interface such as name/value pairs. + +This Recommendation outlines the structure of TMF513 and describes its relationship to the other M.3170-series Recommendations, other TMN Recommendations and other TM Forum specifications. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.805] ITU-T Recommendation G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.852.2] ITU-T Recommendation G.852.2 (1999), *Enterprise viewpoint description of transport network resource model*. +- [ITU-T M.3010] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3013] ITU-T Recommendation M.3013 (2000), *Considerations for a telecommunications management network*. +- [ITU-T M.3020] ITU-T Recommendation M.3020 (2007), *Management interface specification methodology*. +- [ITU-T M.3050.x] ITU-T Recommendations M.3050.x (2004), *Enhanced Telecom Operations Map (eTOM)*. + +NOTE – This series of Recommendations has the following structure: + +M.3050.0 – eTOM – Introduction. + +M.3050.1 – eTOM – The business process framework. + +- M.3050.2 – eTOM – Process decompositions and descriptions. +- M.3050.3 – eTOM – Representative process flows. +- M.3050.4 – eTOM – B2B integration: Using B2B inter-enterprise integration with the eTOM. +- M.3050/Supplement 1 – eTOM – ITIL application note. +- M.3050/Supplement 2 – eTOM – Public B2B Business Operations Map (BOM). +- M.3050/Supplement 3 – eTOM to M.3400 mapping. +- [ITU-T M.3170.0] ITU-T Recommendation M.3170.0 (2007), *Multi-technology network management: Introduction and supporting documentation*. +- [ITU-T M.3170.2] ITU-T Recommendation M.3170.2 (2007), *Multi-technology network management: Information agreement (TMF608)*. +- [ITU-T M.3170.3] ITU-T Recommendation M.3170.3 (2007), *Multi-technology network management: CORBA IDL solution set (TMF814) with implementation statement templates and guidelines (TMF814A)*. +- [ITU-T M.3200] ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. +- [ITU-T M.3400] ITU-T Recommendation M.3400 (2000), *TMN management functions*. +- [ITU-T X.735] ITU-T Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems Management: Log control function*. +- [TMF513 v3.0] TM Forum TMF513 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: Business Agreement*, except for the table of references contained in Appendix B. +- NOTE – This table of references consists of the columns "reference", "description" and "brief use summary". Whilst the last column is meant to clearly indicate for each reference (i.e., row) whether the reference is needed for the implementation of the specification (a normative reference) or was used for the development of the specification (a non-normative reference), it turned out that this goal was not reached unambiguously in all cases. Therefore this Recommendation does not reference this table. Instead the truly normative references of [TMF513 v3.0], namely [TMF608], [ITU-T G.805] and [ITU-T X.735], are added to the references clause of this Recommendation while the useful and available non-normative references are added to the bibliography of this Recommendation (see [b-TMF044 v2.0] and [b-TMF402 v5.10]). +- [TMF608 v3.0] TM Forum TMF608 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: Information Agreement*, Rational Rose™ (UML) version and generated HTML version, except for the table of references contained in Appendix B. +- NOTE – This Recommendation does not reference this table for the same reasons explained in the Note for [TMF513 v3.0]. Instead the truly normative references of [TMF608 v3.0], namely [TMF513 v3.0], [ITU-T G.805] and [ITU-T X.735], are added to the references clause of this Recommendation while the useful and available non-normative references are added to the Bibliography of this Recommendation (see [b-TMF044 v2.0] and [b-TMF404 v2.8]). + +# 3 Definitions + +Refer to clause 3 of [ITU-T M.3170.0]. + +# 4 Abbreviations + +Refer to clause 4 of [ITU-T M.3170.0]. + +# 5 Conventions + +This Recommendation does not use any particular notational or other conventions. + +# 6 TMF513 overview – A lead-in to the MTNM business agreement + +This business agreement defines the business problem statement and business requirement model for the information exchange or interface between network management systems (NMSs) and element management systems (EMSs) enabling unified management of SONET/SDH, OTN, DSL, ATM and point-to-point Ethernet transport and access networks. + +The business problem statement is described in two parts: + +- **Business problem description, project scope and objectives** which identify the business problem regarding the management of a variety of transport network equipment, including the scope, objectives, business scenarios and the benefits to be gained through the solution. +- **Business processes** which describe the related business processes and proposed improvements in terms of the enhanced telecom operations map [ITU-T M.3050.x] [b-GB921 v7.0] [b-GB921D v6.1] [b-TMF517 v1.1]. For MTNM the focus is on the resource management and operations business processes (RM&O grouping) in support of the management of multi-technology transport network equipment. + +The business requirement model is described in four parts: + +- **Requirements** which list the functional and non-functional requirements to be fulfilled by the EML-NML interface for each business scenario as described in the problem statement. The main requirements for the NML-EML interface have been specified in terms of the entities (managed objects) that are visible across the interface (see Table 4.1 of [TMF513 v3.0] and Figure 6-1 of [ITU-T M.3170.3] for an overview) and the operations that may be performed on these objects. These entities are defined in two categories according to the TM Forum business agreement template [b-TMF402 v5.10]: static and structural requirements; normal sequences, dynamic requirements. Additional requirements are defined for the remaining categories of [b-TMF402 v5.10]: abnormal or exception conditions, dynamic requirements; expectations and non-functional requirements; system administration requirements. +- **Use cases** which present use case descriptions and diagrams to define the interactions across each of the process interfaces covered in the business agreement. Use cases are defined in several categories (or management function sets): NMS-EMS session management, EMS-NE session management, discovery and inventory, provisioning, connection management, protection management, fault management, equipment, craft-related, performance management, GUI cut-through, ATM provisioning, and ATM connection management. Use case details include the following components: use case ID; use case name, summary, actor(s), preconditions, begins when, description, ends when, exceptions, post conditions and traceability. The use case template is similar to the use case template of [ITU-T M.3020]. +- **Business requirement model UML diagrams** which contain a summary of the business requirement UML model along with the traceability to the requirements. This serves as the starting point for developing an information agreement and solution set(s). + +The model is divided into a static model (complete class dictionary with mapping to static and dynamic requirements but no UML diagram fragments – these are part of TMF608) and a dynamic model (i.e., the collaboration and state diagrams of TMF608). + +- **Traceability matrices** which provide matrices that show traceability for: + - use cases to requirements; + - UML classes to requirements; + - UML classes to use cases; + - static requirements to UML classes; + - dynamic requirements to use cases and UML class operations; and + - the remaining additional requirements (exceptional, non-functional, administrative). + +The detailed static requirements, normal and exceptional dynamic requirements, use cases, business requirement UML model and traceability matrices for the MTNM NML-EML interface shall be in accordance with [TMF513 v3.0], which extends [b-TMF513 v2.1]. + +NOTE – [TMF513 v3.0] incorporates [b-TMF513 v2.1] (though with certain well-documented changes), and so [b-TMF513 v2.1] is not a formal prerequisite for [TMF513 v3.0]. However, knowledge of the more readily accessible v2.1 may greatly simplify the approach to and understanding of v3.0. + +## 6.1 Relationship to other M.3170-series Recommendations + +M.3170.1/TMF513 defines the requirements for the interface both in terms of the objects and operations that the interface is required to support and the overall behaviour of the interface. It contains a mapping to M.3170.2/TMF608 which links the requirements to the classes, attributes and operations specified in the UML information model. [ITU-T M.3170.2] specifies the details of the classes, their relationships and their operations' behaviour that are required to support the requirements of the MTNM NML-EML Interface. It also provides UML diagram fragments and state diagrams. Hence M.3170.1 and [ITU-T M.3170.2] are mutually traceable and fully define the interface. + +M.3170.3/TMF814 presents the CORBA IDL specification of the MTNM NML-EML interface. In defining a protocol-specific implementation that meets the specification defined in M.3170.1 and [ITU-T M.3170.2], it is necessary to consider protocol-specific issues such as efficiency and interoperability. This results in a service-oriented UML model (as opposed to a fine-grained model) and a corresponding service-oriented CORBA IDL model as outlined in [ITU-T M.3170.2] and detailed in [ITU-T M.3170.3]. + +## 6.2 Relationship to other TMN Recommendations + +The following relationships to other TMN Recommendations exist: + +- The MTNM NML-EML interface is based on M.3010 functional architecture, including logical layered architecture (LLA) and physical architecture defined in [ITU-T M.3010] and [ITU-T M.3013]. +- The M.3170-series Recommendations address the problems arising in the resource management and operations (RM&O) business processes defined in [ITU-T M.3050.x] which in turn are mapped to the TMN management functions in [ITU-T M.3400] that categorizes the management function sets and their members (according to FCAPS application) and specifies them together with generic end-to-end flow scenarios, thereby relating them to TMN management services and TMN managed areas according to [ITU-T M.3200]. +- The M.3170.1 business agreement, the M.3170.2 information agreement and the M.3170.3 CORBA IDL solution set are defined using the TM Forum's methodological analogues (in particular the BA and IA templates [b-TMF402 v5.10] [b-TMF404 v2.8] and the MTNM use case template) to the requirements, analysis and design (RAD) phases and templates defined in [ITU-T M.3020]. + +Refer to clause 7 for a few more details. + +## 6.3 Relationship to other TM Forum specifications + +The following relationships to other TM Forum specifications exist: + +- The relationship of the M.3170-series to the M.3050-series Recommendations implies a relationship to the equivalent eTOM suite specifications, in particular [b-TMF921 v7.0] [b-TMF921D v6.1], and to the eTOM precursors TOM and NM DOM (network management detailed operations map). + +NOTE – Historically, the eTOM was developed from the TOM which was developed, together with the NM DOM, based on [ITU-T M.3010], [ITU-T M.3400] and [ITU-T M.3200]. The LLA of [ITU-T M.3010] is a horizontal grouping of TMN management services/functions and a vertical grouping into functional customer-to-network flow-through areas. The LLA layers map intuitively to the TOM process groupings. Whilst the TOM mediates via flow-through processes according to the FAB breakdown between the customer and the telecom network ("NE management processes" and "physical network and IT" process groupings with details in NM DOM), the eTOM mediates between the customer and the suppliers/partners. When viewing (in the context of detailed NM process specification) the TOM as a part of the eTOM, the telecom network is really in a third eTOM dimension, hidden behind the RM&O process grouping. These currently invisible TOM and NM DOM processes are known as technology resources integration processes (TRIP). Some of these processes reappeared in the context of the eTOM/M.3400 and M.3400/eTOM mappings specified in Supplement 3 to [ITU-T M.3050] and its counterpart GB921T. + +- The TM Forum has developed the new generation operations systems and software (NGOSS) lifecycle and methodology (GB927) as the guideline for service providers, equipment and software vendors as well as system integrators to analyse, design, develop, procure and deploy modular and interoperable NGOSS solutions that support dynamic requirements being imposed by a more business-driven service portfolio. The NGOSS lifecycle and methodology is based on the four key NGOSS frameworks eTOM (GB921 suite), SID (GB922 suite), TNA (TMF053 suite) and TAM [b-GB929 v.2.0] shown in Figure 6-1. In this context the M.3170-series Recommendations on MTNM are seen as a pre-built NGOSS-compliant interface ready to be used in OSS development projects. MTNM progression in the context of the evolution of the NGOSS frameworks (for example, towards service delivery framework (SDF) management) is for further study. + +![Diagram of the four key NGOSS frameworks](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates the four key NGOSS frameworks within the TM Forum lean operator program. It is titled "New generation OSS technical roadmap" and is structured as a 2x2 grid. The top-left box is "Business process framework (enhanced telecom operations Map – eTOM)". The top-right box is "Enterprise-wide information framework (shared information and data model – SID)". The bottom-left box is "Applications framework (telecom applications map – TAM)". The bottom-right box is "Systems integration framework (technology-neutral architecture – TNA)". The entire grid is enclosed in a pink rectangle, which is set against a blue background labeled "TM Forum lean operator program" at the bottom. + +Diagram of the four key NGOSS frameworks + +M.3170.1(07)F\_01 + +**Figure 6-1 – The four key NGOSS frameworks** + +- Historically, MTNM is related to the TM Forum projects SSIM, ATMIM, CaSMIM, IPNM, MTOSI [b-TMF517 v1.1], and the mTOP (multi-technology OSS program) community [b-TMFC5800]. + +Refer to clause 7 for a few more details. + +Further information on the development of MTNM specifications within the TM Forum can be found in an accompanying MTNM users' guide, for further study. + +## 7 Referencing TMF513 + +This Recommendation normatively references the TM Forum approved MTNM business agreement (BA) v3.0 [TMF513 v3.0] which extends the MTNM BA V2.1 [b-TMF513 v2.1], as well as the associated MTNM supporting documents and points to a number of MTNM-related in-force ITU-T Recommendations specifying TMN principles and considerations, TMN interface specification methodology, TMN features and principles of functional network architectures. + +Figure 7-1 shows how M.3170.1 points to TM Forum-approved documents and to related ITU-T Recommendations on TMN and functional network architecture principles: + +![Diagram showing the relationships between ITU-T Recommendation M.3170.1 and various TM Forum and ITU-T documents. M.3170.1 points to a cloud of ITU-T Recommendations (M.3010, M.3013, M.3020, G.805, G.852.2, M.3050-series, M.3200, M.3400), which in turn point to a box describing ITU-T Rec. on TMN. M.3170.1 also points to TMF402, TMF044, TMF513, and TMF608-UML. TMF513 points to GB921, GB910, GB908, GB929, and TMF513 supporting documentation. TMF513 supporting documentation points to a dashed box containing FeaturesSummaryVersion3, objectNaming, NativeEMSSName, layers, LayerRates, LayeredParameters, Probable Causes, SNCTypes, conformanceDefinitions, PerformanceParameters, PMFileFormat, PMExample.txt/.xls, and TCAs.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +The diagram illustrates the referencing structure of ITU-T Recommendation M.3170.1. At the top, a yellow cloud contains several ITU-T Recommendations: M.3010, M.3013, M.3020, G.805, G.852.2, M.3050-series, M.3200, and M.3400. An arrow from this cloud points to a blue box on the right containing the text: "ITU-T Rec. on TMN (principles, interface specification methodology, business processes, management function sets, management services) and principles of functional network architectures". Below the cloud, M.3170.1 has arrows pointing to TMF402, TMF044, TMF513, and TMF608-UML (with a note "(see Figure 7-1 /M.3170.2)"). TMF513 has arrows pointing to GB921, GB910, GB908, GB929, and TMF513 supporting documentation. TMF513 supporting documentation has an arrow pointing to a dashed box containing the following items: FeaturesSummaryVersion3, objectNaming, NativeEMSSName, layers, LayerRates, LayeredParameters, Probable Causes, SNCTypes, conformanceDefinitions, PerformanceParameters, PMFileFormat, PMExample.txt/.xls, and TCAs. The diagram is labeled "M.3170.1(07)F\_02" at the bottom right. + +Diagram showing the relationships between ITU-T Recommendation M.3170.1 and various TM Forum and ITU-T documents. M.3170.1 points to a cloud of ITU-T Recommendations (M.3010, M.3013, M.3020, G.805, G.852.2, M.3050-series, M.3200, M.3400), which in turn point to a box describing ITU-T Rec. on TMN. M.3170.1 also points to TMF402, TMF044, TMF513, and TMF608-UML. TMF513 points to GB921, GB910, GB908, GB929, and TMF513 supporting documentation. TMF513 supporting documentation points to a dashed box containing FeaturesSummaryVersion3, objectNaming, NativeEMSSName, layers, LayerRates, LayeredParameters, Probable Causes, SNCTypes, conformanceDefinitions, PerformanceParameters, PMFileFormat, PMExample.txt/.xls, and TCAs. + +Figure 7-1 – ITU-T and TM Forum documents linked by M.3170.1 + +At the TM Forum side, Figure 7-1 shows the business agreement reference structure with regard to other key TM Forum documents [b-GB921 v7.0] [b-GB92D v6.1] [b-GB929 v2.0] [b-TMF402 v5.10] [b-TMF044 v2.0] (non-exhaustive – see clause 6.3), and looks inside the SD box (BA-relevant supporting documents according to Table 6-1 of [ITU-T M.3170.0]). Refer to clause 6.3 of [ITU-T M.3170.0] for an overview of the supporting documentation. Supporting documents that are only packaged with TMF513 are underlined in blue. + +A more comprehensive description of the relationship of M.3170.1/TMF513 to other TM Forum specifications is for further study (see also clause 6.3). + +At the ITU-T side, Figure 7-1 depicts an "ITU-T Recommendation cloud" with the BA-relevant ITU-T Recommendations. The cloud encompasses TMN-related Recommendations. (TMN principles and considerations [ITU-T M.3010] [ITU-T M.3013], interface specification methodology [ITU-T M.3020], business processes [ITU-T M.3050.x], management function sets [ITU-T M.3400], management services [ITU-T M.3200]) and Recommendations on functional network architecture principles (such as transmission layering without adaptation details) [ITU-T G.805] [ITU-T G.852.2]. Since TMF513 is concerned with requirements and use cases for the MTNM NML-EML interface, it is mainly related to TMN Recommendations and refers only in a minimalistic way to Recommendations on functional network architectures. The details of functional network and management architecture modelling are of interest for the MTNM service-oriented CORBA IDL solution set (see [ITU-T M.3170.3]). However, by referencing the supported transmission layer rates with their associated layered parameters, TMF513 already brings the MTNM multi-technology capability to the requirements phase of the specification process. + +Relationships of TM Forum's TMF513 to further in-force and in-progress ITU-T Recommendations are for further study. Candidates may be found in the M.3020-series revision and amendment work on management interface specification methodology (MISM) and in the X.730-series and X.740-series of ITU-T Recommendations on common management services (such as Object, State, Alarm, Notification, Log, Test and Performance Management) and their progression. For example, TMF513 specifies fairly lightweight but nevertheless complete approaches to fault management and performance management. + +## Bibliography + +The following references contain information that was used in the development of the M.3170-series Recommendations. + +- [b-GB921 v7.0] TM Forum GB921 v7.0 (2007), *Enhanced Telecom Operations Map (eTOM) – The Business Process Framework for the ICS Industry*. [www.tmforum.org/page32701.aspx](http://www.tmforum.org/page32701.aspx) +- [b-GB921D v6.1] TM Forum GB921D v6.1 (2005), *eTOM Addendum D, Process Decompositions and Descriptions (Level 2 and Level 3)*. [www.tmforum.org/browse.aspx?catID=860&linkID=31101](http://www.tmforum.org/browse.aspx?catID=860&linkID=31101) +- [b-GB929 v2.0] TM Forum GB929 v2.0 (2006), *Telecom Applications Map, The BSS/OSS Systems Landscape*. [www.tmforum.org/browse.aspx?catID=860&linkID=32352](http://www.tmforum.org/browse.aspx?catID=860&linkID=32352) +- [b-TMF044 v2.0] TM Forum TMF044 v2.0 (2003), *TM Forum Glossary*. [www.tmforum.org/browse.aspx?catid=860&linkID=28087](http://www.tmforum.org/browse.aspx?catid=860&linkID=28087) +- [b-TMF402 v5.10] TM Forum TMF402 v5.10 (2005), *TMF Business Agreement Template*. [www.tmforum.org/browse.aspx?catID=866&linkID=24300](http://www.tmforum.org/browse.aspx?catID=866&linkID=24300) +- [b-TMF404 v2.8] TM Forum TMF404 v2.8 (2005), *TMF Information Agreement Template*. [www.tmforum.org/browse.aspx?catID=866&linkID=24299](http://www.tmforum.org/browse.aspx?catID=866&linkID=24299) +- [b-TMF513 Version 2.1] TM Forum TMF513 Version 2.1 (2002), *Multi-Technology Network Management (MTNM) NML-EML Interface: Business Agreement*. [www.tmforum.org/browse.aspx?catid=860&linkID=24195](http://www.tmforum.org/browse.aspx?catid=860&linkID=24195) +- [b-TMF517 Version 1.1] TM Forum TMF517 Version 1.1 (2006), *Multi-Technology Operations System Interface (MTOSI): Business Agreement*. [www.tmforum.org/browse.aspx?catID=860&linkID=32469](http://www.tmforum.org/browse.aspx?catID=860&linkID=32469) +- [b-TMF608 Version 2.1] TM Forum TMF608 Version 2.1 (2002), *Multi-Technology Network Management (MTNM) NML-EML Interface: Information Agreement*, PDF version and generated HTML version. [www.tmforum.org/browse.aspx?catid=860&linkID=20309](http://www.tmforum.org/browse.aspx?catid=860&linkID=20309) +- [b-TMFC5800] TM Forum TMFC5800 (2007), *A Very Short History of mTOP*. [www.tmforum.org/browse.aspx?catID=2590&docID=5800](http://www.tmforum.org/browse.aspx?catID=2590&docID=5800) + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3170.2-200703-I_PDF-E/raw.md b/marked/M/T-REC-M.3170.2-200703-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2b2011cf169a4da9cef1c1b7523000f4547c6070 --- /dev/null +++ b/marked/M/T-REC-M.3170.2-200703-I_PDF-E/raw.md @@ -0,0 +1,404 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3170.2** + +(03/2007) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Multi-technology network management: +Information agreement (TMF608)** + +ITU-T Recommendation M.3170.2 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3170.2** + +# **Multi-technology network management: Information agreement (TMF608)** + +## **Summary** + +The multi-technology network management (MTNM) solution suite realizes a TMN interface between the NML and EML according to ITU-T Recommendation M.3010 for the FCAPS management of multi-technology fixed transport, access and aggregation networks. + +This Recommendation explains the structure of the MTNM information agreement (TMF608) and relates its components to the M.3020 methodology for TMN interface specification. It wraps TMF608 and associated supporting documents by referencing them normatively and relating them to identified Recommendations on TMN functionality (FCAPS-based) and TMN interface specification methodology but not to Recommendations on TMN interface analysis models. This Recommendation can also be used as a first lead-in to the MTNM information agreement. + +###### **Source** + +ITU-T Recommendation M.3170.2 was approved on 16 March 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2008 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 3 | +| 4 Abbreviations..... | 3 | +| 5 Conventions ..... | 3 | +| 6 TMF608 overview – A lead-in to the MTNM information agreement ..... | 3 | +| 6.1 Relationship to other M.3170-series Recommendations..... | 5 | +| 6.2 Relationship to other TMN Recommendations..... | 5 | +| 6.3 Relationship to other TM Forum specifications..... | 5 | +| 6.4 Overview of UML diagram fragments and state diagrams ..... | 6 | +| 6.5 Mapping the fine-grained UML to a service-oriented UML..... | 8 | +| 7 Referencing TMF608..... | 10 | +| Bibliography..... | 12 | + + + +## Multi-technology network management: Information agreement (TMF608) + +# 1 Scope + +The multi-technology network management (MTNM) solution suite is an implementation standard of a TMN interface between the NML and EML according to [ITU-T M.3010] for the FCAPS management of multi-technology fixed transport, access and aggregation networks. The MTNM implementation view specifies a CORBA-based TMN Q interface between an NMS (CORBA client or TMN manager) and an EMS (CORBA server or TMN agent which is in contact to the NEL). + +The MTNM solution suite consists of the following deliverables: + +- The MTNM business view is specified in the business agreement (BA) TMF513. +- The MTNM system view is specified in UML in the information agreement (IA) TMF608. +- The MTNM CORBA-based implementation and deployment views are specified in the CORBA IDL solution set (SS) TMF814 (with HTML documentation) and associated implementation statement (IS) templates and guidelines TMF814A. +- The MTNM supporting documentation (SD) guides and lightens the work with the MTNM views and also includes normative parts of the interface such as name/value pairs. + +This Recommendation outlines the structure of TMF608 and describes its relationship to the other M.3170-series Recommendations and to other TMN Recommendations. + +This Recommendation emphasizes that the M.3170-series Recommendations go for *Level B* TMN interface information conformance (as defined by [ITU-T M.3010]): the managed object classes supported by the MTNM NML-EML Interface are specified in approved standards of the *de facto* standards body TM Forum ([TMF608 v3.0], [b-TMF608 v2.1], [TMF814 v3.0], [TMF814 v2.1] and [ITU-T M.3170.3] – see clauses 6.4 and 6.5). This Recommendation provides a coarse overview of the UML diagram fragments and state diagrams of TMF608 and presents some principles for mapping the MTNM fine-grained UML [TMF608 v3.0] and [b-TMF608 v2.1] to a service-oriented UML [TMF814 v3.0 SD] that forms a starting point for any service-oriented solution set construction such as the service-oriented CORBA IDL of [TMF814 v3.0], [TMF814 v2.1] and [ITU-T M.3170.3]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.805] ITU-T Recommendation G.805 (2000), *Generic functional architecture of transport networks*. +- [ITU-T G.852.2] ITU-T Recommendation G.852.2 (1999), *Enterprise viewpoint description of transport network resource model*. +- [ITU-T M.3010] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. + +- [ITU-T M.3013] ITU-T Recommendation M.3013 (2000), *Considerations for a telecommunications management network*. +- [ITU-T M.3020] ITU-T Recommendation M.3020 (2007), *Management interface specification methodology*. +- [ITU-T M.3050.x] ITU-T Recommendations M.3050.x (2004), *Enhanced Telecom Operations Map (eTOM)*. + NOTE – This series of Recommendations has the following structure: + M.3050.0 – *eTOM – Introduction*. + M.3050.1 – *eTOM – The business process framework*. + M.3050.2 – *eTOM – Process decompositions and descriptions*. + M.3050.3 – *eTOM – Representative process flows*. + M.3050.4 – *eTOM – B2B integration: Using B2B inter-enterprise integration with the eTOM*. + M.3050/Supplement 1 – *eTOM – ITIL application note*. + M.3050/Supplement 2 – *eTOM – Public B2B Business Operations Map (BOM)*. + M.3050/Supplement 3 – *eTOM to M.3400 mapping*. +- [ITU-T M.3170.0] ITU-T Recommendation M.3170.0 (2007), *Multi-technology network management – Introduction and supporting documentation*. +- [ITU-T M.3170.1] ITU-T Recommendation M.3170.1 (2007), *Multi-technology network management – Business agreement (TMF513)*. +- [ITU-T M.3170.3] ITU-T Recommendation M.3170.3 (2007), *Multi-technology network management – CORBA IDL solution set (TMF814) with implementation statement templates and guidelines (TMF814A)*. +- [ITU-T M.3200] ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. +- [ITU-T M.3400] ITU-T Recommendation M.3400 (2000), *TMN management functions*. +- [ITU-T X.735] ITU-T Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems Management: Log control function*. +- [TMF513 v3.0] TM Forum TMF513 Version 3.0 (2004), *Multi-technology network management (MTNM) NML-EML Interface: Business agreement*, except for the table of references contained in Appendix B. + NOTE – This Recommendation does not reference this table for the same reasons explained in the note of [TMF608 v3.0]. Instead the truly normative references of [TMF513 v3.0], namely [TMF608 v3.0], [ITU-T G.805] and [ITU-T X.735], are added to the references clause of this Recommendation while the useful and available non-normative references are added to the bibliography of this Recommendation (see [TMF044 v2.0] and [b-TMF402 v5.10]). +- [TMF608 v3.0] TM Forum TMF608 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: Information Agreement*, Rational Rose™ (UML) version and generated HTML version, except for the table of references contained in Appendix B. + NOTE – This table of references consists of the columns "reference", "description" and "brief use summary". Whilst the last column is meant to clearly indicate for each reference (i.e., row) whether the reference is needed for the implementation of the specification (a normative reference) or was used for the development of the + +specification (a non-normative reference), it turned out that this goal was not reached unambiguously in all cases. Therefore, this Recommendation does not reference this table. + +Instead the truly normative references of [TMF608 v3.0], namely [TMF513 v3.0], [ITU-T G.805] and [ITU-T X.735], are added to the references clause of this Recommendation while the useful and available non-normative references are added to the bibliography of this Recommendation (see [b-TMF044 v2.0] and [b-TMF404 v2.8]). + +- [TMF814 v2.1] TM Forum TMF814 Version 2.1 (2002), *Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set.* +- [TMF814 v3.0] TM Forum TMF814 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set.* +- [TMF814 v3.0 SD] TM Forum TMF814 Version 3.0 (2004), *Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set*, Supporting Document "Traceability between IA and SS", file "MappingIASS.pdf". + +# 3 Definitions + +Refer to clause 3 of [ITU-T M.3170.0]. + +# 4 Abbreviations + +Refer to clause 4 of [ITU-T M.3170.0]. + +# 5 Conventions + +This Recommendation does not use any particular notational or other conventions. + +# 6 TMF608 overview – A lead-in to the MTNM information agreement + +This information agreement specifies the MTNM NML-EML interface information model for the management of multi-technology networks including transport networks based SONET/SDH, OTN, ATM, DSL and point-to-point Ethernet technologies. The interface information model is essentially defined in terms of M.3170.1/TMF513 business agreement specifications followed by the interface information model specifications themselves. + +The referenced business agreement specifications include: + +- **Project scope and objectives** which provide an executive summary by identifying the Interface being addressed and describing the benefits gained by the problem's solution. +- **Interface information requirements** which reference M.3170.1/TMF513 to list the functional and non-functional interface information requirements to be fulfilled by the interface information model described in this information agreement. +- **Interface information use cases** which reference M.3170.1/TMF513 to identify the interface information use case diagrams and descriptions needed to describe the way actors use the interface and the interactions across the interface covered in this information agreement. +- **Requirement traceability matrices** which refer to M.3170.1/TMF513 to show the traceability of use cases to requirement statements, of object classes to use cases, etc. See clause 6 of [ITU-T M.3170.1] and [TMF513 v3.0] for the various types of traceability matrices. + +NOTE 1 – Traceability between the information agreement (IA) and the CORBA IDL solution set (SS) is provided by the supporting document "Traceability between IA and SS" [TMF814 v3.0 SD] (contained in the solution set [TMF814 v3.0]). This document lists all classes, attributes, relationships, operations, enums, strings and structs defined in the IA and associates them with the respective IDL definitions in the SS. + +The interface information model specifications provide a protocol-neutral description of the interface that cover the business agreement specifications. The TM Forum MTNM team has been using UML and the Rational Rose™ modelling tool to develop the MTNM interface information model. The complete protocol-neutral master specification is contained in the Rational Rose™ version of [TMF608 v3.0] (file "TMF608v3.0\_2004\_04.mdl"). A generated HTML version of [TMF608 v3.0] is also available (see Figure 6-1 below). The interface information model specifications include: + +- **Interface information model UML diagrams** which provide complete UML fragments for all managed object classes of the interface and state diagrams for the states (see clause 6.4). +- **Interface information model UML class dictionary** which describes the object classes with attributes, relationships and operations, the enums, the strings and the structs of the interface. + +![Figure 6-1: Structure of the HTML version of TMF608. The diagram shows a file explorer view on the left and a 'Logical View' tree on the right. Arrows indicate navigation: 'to start HTML' points to 'TMF608v3.0_2004_04.htm', and 'to get an overview' points to 'Main Objects'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the structure of the HTML version of TMF608. On the left, a file explorer view shows the directory structure for 'TMF608v3.0-html'. A red circle highlights the file 'TMF608v3.0\_2004\_04.htm', with an arrow labeled 'to start HTML' pointing to it. Another red circle highlights the 'supportingdocuments' folder. On the right, a 'Logical View' tree displays the contents of the specification. A red circle highlights the 'Main Objects' folder, with an arrow labeled 'to get an overview' pointing to it. Other folders and files listed in the Logical View include Enums, Strings, Structs, EMS Class Diagram, ME Class Diagram, Equipment Class Diagram, TP's Class Diagram, SNC Class Diagram, TopologicalLink Class Diagram, Events Class Diagram, Object Creation/Deletion Producers, AVC Producers, State Change Producers, Alarm Producers, Protection Group Class Diagram, SessionFactory Class Diagram, Notification Class Diagram, PM Class Diagram, Subnetwork Class Diagram, Common Resource Info Class Diagram, Equipment Protection Group Class Diagram, Alarm Severity Assignment Class Diagram, TPPool Class Diagram, Inventory Events Object Diagram, Protection Group Object Diagram, ATM CTPs Object Diagram, Version, PhysicalTerminationPoint, TrafficDescriptor, Route, and Filter. + +Figure 6-1: Structure of the HTML version of TMF608. The diagram shows a file explorer view on the left and a 'Logical View' tree on the right. Arrows indicate navigation: 'to start HTML' points to 'TMF608v3.0\_2004\_04.htm', and 'to get an overview' points to 'Main Objects'. + +M.3170.2(07)F\_6-1 + +**Figure 6-1 – Structure of the HTML version of TMF608** + +The detailed business agreement specifications for the MTNM NML-EML interface shall be in accordance with [ITU-T M.3170.1], which references [TMF513 v3.0]. + +The detailed static interface information UML model with class diagrams and class dictionary and the detailed dynamic interface information UML model with state diagrams for the MTNM NML-EML interface shall be in accordance with [TMF608 v3.0], which extends [b-TMF608 v2.1]. + +NOTE 2 – [TMF608 v3.0] incorporates [b-TMF608 v2.1] (though with certain well-documented changes) and so [b-TMF608 v2.1] is not a formal prerequisite for [TMF608 v3.0]. However, knowledge of the more readily accessible (although superseded) v2.1 may greatly simplify the approach to and understanding of v3.0. + +## 6.1 Relationship to other M.3170-series Recommendations + +M.3170.1/TMF513 defines the requirements for the interface both in terms of the objects and operations that the interface is required to support and the overall behaviour of the interface. It contains a mapping to M.3170.2/TMF608 which links the requirements to the classes, attributes and operations specified in the UML information model. This Recommendation specifies the details of the classes, their relationships and their operations behaviour that are required to support the requirements of the MTNM NML-EML interface. It also provides UML diagram fragments and state diagrams. Hence [ITU-T M.3170.1] and this Recommendation are mutually traceable and fully define the interface. + +M.3170.3/TMF814 presents the CORBA IDL specification of the MTNM NML-EML interface. In defining a protocol-specific implementation that meets the specification defined in [ITU-T M.3170.1] and this Recommendation, it is necessary to consider protocol-specific issues such as efficiency and interoperability. This results in a service-oriented UML model (as opposed to a fine-grained model) and a corresponding service-oriented CORBA IDL model as outlined in clause 6.5 and detailed in [ITU-T M.3170.3]. + +## 6.2 Relationship to other TMN Recommendations + +The following relationships to other TMN Recommendations exist: + +- The MTNM NML-EML interface is based on M.3010 functional architecture, including logical layered architecture and physical architecture defined in [ITU-T M.3010] and [ITU-T M.3013], and meets the Level B TMN interface information conformance defined in Amendment 1 to [ITU-T M.3010]. +- The M.3170-series Recommendations address the problems arising in the resource management and operations (RM&O) business processes defined in [ITU-T M.3050.x] which in turn are mapped to the TMN management functions in [ITU-T M.3400] that categorizes the management function sets and their members (according to FCAPS application) and specifies them together with generic end-to-end flow scenarios that relate them to TMN management services and TMN managed areas according to [ITU-T M.3200]. +- The M.3170.1 business agreement, the M.3170.2 information agreement and the M.3170.3 CORBA IDL Solution Set are defined using the TM Forum's methodological analogues (in particular the BA and IA templates [b-TMF402 v5.10], [b-TMF404 v2.8] and the MTNM use case template) to the requirements, analysis and design (RAD) phases and templates defined in [ITU-T M.3020]. + +Refer to clause 7 for a few more details. + +## 6.3 Relationship to other TM Forum specifications + +Refer to clause 6.3 of [ITU-T M.3170.1]. + +## 6.4 Overview of UML diagram fragments and state diagrams + +The interface information model UML diagrams of TMF608 encompass the following diagram fragments for MTNM managed object classes (class diagrams and collaboration diagrams) + +EMS, managed element, equipment, termination points (see Figure 6-2), SNC, topological link, events, object creation/deletion producers, attribute value change producers, state change producers, alarm producers, protection group, session factory, notifications, performance management classes, subnetwork, main classes, common resource info, equipment protection group, alarm severity assignment classes, TP pool, inventory events, protection groups, ATM CTPs. + +And the following state diagrams for MTNM states: + +Equipment holder state, SNC state (pending supported), SNC state (pending not supported), SNC modification (without SNC name preservation), SNC modification (with SNC name preservation), SNC modification (with multiple routes and SNC name preservation), TMD state (see Figure 6-3). + +![UML diagram fragment showing various network elements and their relationships, centered around TerminationPoint and its subclasses.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the following classes and relationships: + +- CommonResourceInfo**: Base class with attributes like name, userLabel, owner, nativeEMSName, and additionalInfo. Methods include setNativeEMSName(), setOwner(), setUserLabel(), setNetworkAccessDomain(), and setAdditionalInfo(). +- TCAParameter**: Associated with **TCAParameterProfile** (0..n to 0..n). +- TCAParameterProfile**: Associated with **TransmissionParameters** (0..n to 1..n). +- TransmissionParameters**: Contains attributes layerRate and transmissionParameters. Method: setTransmissionParameters(). +- PerformanceMonitoringPoint**: Associated with **SwitchData** (0..n to 0..1) and **PMData** (0..n to n). +- SwitchData**: Associated with **PMData** (0..1 to n). +- PMData**: Associated with **SwitchData** (n to 0..1). +- TerminationPoint**: Base class with attributes like direction, protectionAssociation, edgePoint, networkAccessDomain, equipmentProtected, egressTMDState, and ingressTMDState. Methods include getContainedPotentialCTP(), getContainedPotentialCTPNames(), getContainedInUseCTP(), getContainedInUseCTPNames(), getContainedCurrentCTP(), getContainedCurrentCTPNames(), performMaintenanceOperation(), getActiveMaintenanceOperation(), getTCAParameter(), getTCAParameterProfilePoint(), getITPGroupingRelationships(), preventTMDAssignment(), getTransmissionDescriptorAssociation(), and getPotentialFixedCC(). +- TransmissionDescriptor**: Associated with **TerminationPoint** (1 to 0..1 for ingress, 1 to 0..1 for egress). +- TopologicalLink**: Associated with **TerminationPoint** (0..2 to 0..n). +- Subnetwork**: Associated with **TerminationPoint** (1..n to 0..n). +- TPPool**: Associated with **TerminationPoint** (1 to 0..n). +- CommonTransmissionParameters**: Associated with **TerminationPoint** (0..n to 0..1). +- ObjectInformation**: Associated with **TerminationPoint** (0..n to 0..n). +- ManagedElement**: Associated with **PhysicalTerminationPoint** (0..n to 1..n). +- PhysicalTerminationPoint**: Associated with **Equipment** (0..n to 1..n) and **CrossConnect** (0..n to 1..n). +- Equipment**: Associated with **PhysicalTerminationPoint** (1..n to 0..n). +- CrossConnect**: Associated with **PhysicalTerminationPoint** (1..n to 0..n). +- FloatingTerminationPoint**: Associated with **PhysicalTerminationPoint** (0..1 to 0..1). +- ProtectionGroup**: Associated with **PhysicalTerminationPoint** (0..2 to 2..\*). +- ConnectionTerminationPoint**: Associated with **PhysicalTerminationPoint** (0..n to 1..n). +- GroupTerminationPoint**: Associated with **PhysicalTerminationPoint** (0..n to 1..n). +- TrafficDescriptor**: Associated with **TerminationPoint** (0..1 to 0..1 for egress, 0..1 to 0..1 for ingress). +- SubnetworkConnection**: Associated with **TerminationPoint** (0..n to 0..n). + +UML diagram fragment showing various network elements and their relationships, centered around TerminationPoint and its subclasses. + +Figure 6-2 – TMF608 v3.0 UML diagram fragment: Termination points + +![State diagram for Transmission descriptor (TMD) state showing four states: NOT_APPLICABLE, MISMATCH, PENDING, and APPLIED, with transitions between them based on setTransmissionParameters and setAdditionalInfo operations.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NOT_APPLICABLE + NOT_APPLICABLE --> PENDING : setTransmissionParameters with TMD + NOT_APPLICABLE --> MISMATCH : setTransmissionParameters without TMD + NOT_APPLICABLE --> APPLIED : setTransmissionParameters with null TMD + MISMATCH --> MISMATCH : setAdditionalInfo + MISMATCH --> PENDING : setTransmissionParameters with TMD + MISMATCH --> APPLIED : setTransmissionParameters without TMD, setAdditionalInfo + PENDING --> APPLIED : TP configuration in progress + APPLIED --> MISMATCH : setTransmissionParameters without TMD, setAdditionalInfo + APPLIED --> NOT_APPLICABLE : setTransmissionParameters with null TMD + APPLIED --> TMD_MISSING : deleteTransmissionDescriptor or internal fault + APPLIED --> MISMATCH : setTransmissionParameters without TMD, setAdditionalInfo + +``` + +State diagram for Transmission descriptor (TMD) state showing four states: NOT\_APPLICABLE, MISMATCH, PENDING, and APPLIED, with transitions between them based on setTransmissionParameters and setAdditionalInfo operations. + +M.3170.2(07)F\_6-3 + +**Figure 6-3 – TMF608 v3.0 state diagram: Transmission descriptor (TMD) state** + +Refer to the "logical view" tree of the HTML version of [TMF608 v3.0] (see Figure 6-1) for more details. + +## 6.5 Mapping the fine-grained UML to a service-oriented UML + +The service-oriented approach to information modelling requires the separation of the state and behaviour of managed objects. A service-oriented managed object is a managed object whose state and behaviour are distributed in the interface definition; its state is left with the object while its behaviour (operations and notifications) is delegated to a steward object. + +In case of MTNM, these steward objects are CORBA interfaces called service-oriented façades, managing objects or object managers, while the managed objects themselves are CORBA structs. Service orientation therefore results in a two-part information model whose parts can be progressed independently. Figure 6-4 provides an overview of the MTNM CORBA interfaces in UML notation. These interfaces include the façades for managed object behaviour, iterator interfaces per object class and the session service interfaces. Refer to [ITU-T M.3170.3] for details. Figure 6-2 of [ITU-T M.3170.3] provides an equivalent overview but without showing the operations. + +The mapping is accompanied by the supporting document "Traceability between IA and SS" [TMF814 v3.0 SD] which lists all UML artefacts defined in TMF608 and associates them with the respective IDL definitions in TMF814. This SD also specifies generic rules which have to be taken into account when creating any protocol-specific specification (such as the CORBA IDL SS) based on the IA. + +Service-oriented MTNM v3.0 (and v2.1) model + +![Service-oriented UML diagram of MTNM v3.0 (and v2.1) model. The diagram shows a hierarchy of interfaces for network management. At the top is 'Common_I' with methods like getCapabilities(), getOwner(), getUserLabel(), getNativeEMSName(), and getAdditionalInfo(). Below it are 'MaintenanceMgr_I', 'GuiCutThroughMgr_I', 'ManagedElementMgr_I', 'PerformanceManagementMgr_I', 'TrafficDescriptorMgr_I', and 'SoftwareAndDataMgr_I'. 'ManagedElementMgr_I' is a central interface with many methods for managing network elements, connections, and alarms. 'PerformanceManagementMgr_I' includes methods for monitoring and reporting performance data. 'TrafficDescriptorMgr_I' handles traffic descriptors. 'SoftwareAndDataMgr_I' manages software and data. Other interfaces include 'EMSMgr_I', 'MultiLayerSubnetworkMgr_I', 'ProtectionMgr_I', 'EquipmentInventoryMgr_I', 'EmsSession_I', 'NMSSession_I', 'Version_I', 'EmsSessionFactory_I', 'EquipmentOrHolderIterator_I', 'NamingAttributesIterator_I', 'CurrentMaintenanceOperationIterator_I', 'ManagedElementIterator_I', 'SubnetworkIterator_I', 'EventIterator_I', 'ASAPIterator_I', 'BackupIterator_I', 'EProtectionGroupIterator_I', 'PMDataIterator_I', 'ProtectionGroupIterator_I', 'CCIterator_I', 'SNCIterator_I', 'TerminationPointIterator_I', 'TopologicalLinkIterator_I', 'TrafficDescriptorIterator_I', 'PMPIterator_I', 'TCAPParameterProfileIterator_I', 'TransmissionDescriptorIterator_I', and 'GTPIterator_I'. Most iterator interfaces have 'destroy()', 'getLength()', and 'next_n()' methods. Version 2.1 interfaces are in black, and Version 3.0 interfaces and operations are in blue.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +Service-oriented UML diagram of MTNM v3.0 (and v2.1) model. The diagram shows a hierarchy of interfaces for network management. At the top is 'Common\_I' with methods like getCapabilities(), getOwner(), getUserLabel(), getNativeEMSName(), and getAdditionalInfo(). Below it are 'MaintenanceMgr\_I', 'GuiCutThroughMgr\_I', 'ManagedElementMgr\_I', 'PerformanceManagementMgr\_I', 'TrafficDescriptorMgr\_I', and 'SoftwareAndDataMgr\_I'. 'ManagedElementMgr\_I' is a central interface with many methods for managing network elements, connections, and alarms. 'PerformanceManagementMgr\_I' includes methods for monitoring and reporting performance data. 'TrafficDescriptorMgr\_I' handles traffic descriptors. 'SoftwareAndDataMgr\_I' manages software and data. Other interfaces include 'EMSMgr\_I', 'MultiLayerSubnetworkMgr\_I', 'ProtectionMgr\_I', 'EquipmentInventoryMgr\_I', 'EmsSession\_I', 'NMSSession\_I', 'Version\_I', 'EmsSessionFactory\_I', 'EquipmentOrHolderIterator\_I', 'NamingAttributesIterator\_I', 'CurrentMaintenanceOperationIterator\_I', 'ManagedElementIterator\_I', 'SubnetworkIterator\_I', 'EventIterator\_I', 'ASAPIterator\_I', 'BackupIterator\_I', 'EProtectionGroupIterator\_I', 'PMDataIterator\_I', 'ProtectionGroupIterator\_I', 'CCIterator\_I', 'SNCIterator\_I', 'TerminationPointIterator\_I', 'TopologicalLinkIterator\_I', 'TrafficDescriptorIterator\_I', 'PMPIterator\_I', 'TCAPParameterProfileIterator\_I', 'TransmissionDescriptorIterator\_I', and 'GTPIterator\_I'. Most iterator interfaces have 'destroy()', 'getLength()', and 'next\_n()' methods. Version 2.1 interfaces are in black, and Version 3.0 interfaces and operations are in blue. + +Version 2.1 interfaces and operations are shown in black, +new Version 3.0 interfaces and operations are shown in blue. + +M.3170.2(07)F\_6-4 + +**Figure 6-4 – Service-oriented UML diagram of MTNM v3.0 (and v2.1)** + +Mapping the fine-grained UML to a service-oriented UML includes assignment of steward interfaces to managed object classes. Figure 6-5 summarizes this mapping for MTNM v2.1. + +| TMF814 Manager
(CORBA façade
object with IOR) | MTNM v2.1 Managed Object
managed by, or used by ,
CORBA façade object | +|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ME Manager | managed element ( ME ), termination point (TP) ( PTP , CTP , TPPool ), alarm, AID, cross-connect (XC), TD , MLSN | +| MLSN Manager | multi-layer sub-network ( MLSN ) (includes singleton), sub-network connection ( SNC ) (includes cross-connection), topological link ( TL ), TPPool , CTP , PTP , route , TD | +| EQP Manager | equipment ( EQP ), equipment holder ( EQPH ) (various types), PTP | +| EMS Manager | element management system ( EMS ) object, TL , alarm, AID, MLSN | +| TD Manager | traffic descriptor ( TD ), TP | +| PM Manager | performance management (PM) object (PM location, granularity, PM parameter, TCA parameter, PM data), TP , ME | +| Protection Manager | protection group ( PGP ), TP | +| Maintenance Mgr | maintenance operation, TP | +| GCT Manager | GUI cut-through (GCT) widget data, GCT launch command data | +| root interfaces
(are not façades) | EMS session factory (entry point to EMS), user name , password , EMS session, NMS session, event channel | + +M.3170.2(07)F\_6-5 + +**Figure 6-5 – TMF814 v2.1 managers and managed objects** + +The extension of Figure 6-5 to [TMF814 v3.0] is for further study but see Figures 6-1 and 6-2 of [ITU-T M.3170.3] for an overview of the managers and managed object classes of MTNM v3.0. + +# 7 Referencing TMF608 + +This Recommendation normatively references the TM Forum approved MTNM information agreement (IA) v3.0 [TMF608 v3.0] which extends the MTNM IA v2.1 [b-TMF608 v2.1], as well as the associated MTNM supporting documents, and points to a number of MTNM-related in-force ITU-T Recommendations specifying TMN functionality (FCAPS-based) and TMN interface specification methodology, including UML repertoire and UML templates, but not TMN interface analysis models since the M.3170-series Recommendations go for Level B and not for Level A TMN interface information conformance (as defined by Amendment 1 to [ITU-T M.3010]) (see clause 9 of [ITU-T M.3170.3] for details). + +Figure 7-1 shows how this Recommendation points to TM Forum-approved documents and to related ITU-T Recommendations on TMN functionality (according to TMF513) and TMN methodology. + +![Diagram showing the information agreement reference structure for ITU-T M.3170.2. At the top, a cloud labeled 'ITU-T Recs. on TMN functionality and TMN interface specification methodology' contains ITU-T Recommendations M.3010, M.3013, M.3020, M.3020-series Progression, M.3050-series, M.3200, and M.3400. Below the cloud, M.3170.2 points to TMF608-UML. TMF608-UML points to TMF404, TMF405, and TMF44. TMF608-UML and TMF513 are bidirectionally linked, with a note '(See Figure 7-1/M.3170.1)'. TMF608-UML points to TMF608 Supporting Documentation, which in turn points to a dashed box containing various supporting documents. TMF608-HTML also points to TMF608 Supporting Documentation. The dashed box contains: FeaturesSummaryVersion3, Changes_to_Version 2.1 (blue), objectNaming, EquipmentModel, modesOfOperation, maintenanceCommands, ContainedTPs, layers, LayerRates, LayeredParameters, Probable Causes, SNCTypes, conformanceDefinitions, trafficParameters, PerformanceParameters, PMFileFormat, PMExample.txt/.xls, TCAs, PGPParameters, encodingX731M3100, BundledSNC, LocationIdentification, and TTPoolRelationship.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +Diagram showing the information agreement reference structure for ITU-T M.3170.2. At the top, a cloud labeled 'ITU-T Recs. on TMN functionality and TMN interface specification methodology' contains ITU-T Recommendations M.3010, M.3013, M.3020, M.3020-series Progression, M.3050-series, M.3200, and M.3400. Below the cloud, M.3170.2 points to TMF608-UML. TMF608-UML points to TMF404, TMF405, and TMF44. TMF608-UML and TMF513 are bidirectionally linked, with a note '(See Figure 7-1/M.3170.1)'. TMF608-UML points to TMF608 Supporting Documentation, which in turn points to a dashed box containing various supporting documents. TMF608-HTML also points to TMF608 Supporting Documentation. The dashed box contains: FeaturesSummaryVersion3, Changes\_to\_Version 2.1 (blue), objectNaming, EquipmentModel, modesOfOperation, maintenanceCommands, ContainedTPs, layers, LayerRates, LayeredParameters, Probable Causes, SNCTypes, conformanceDefinitions, trafficParameters, PerformanceParameters, PMFileFormat, PMExample.txt/.xls, TCAs, PGPParameters, encodingX731M3100, BundledSNC, LocationIdentification, and TTPoolRelationship. + +**Figure 7-1 – ITU-T and TM Forum documents linked by M.3170.2** + +At the TM Forum side, Figure 7-1 shows the information agreement reference structure with regard to other key TM Forum-approved documents, mainly by referring to TMF513 (see clause 6.3 of [ITU-T M.3170.1]), and looks inside the SD box (IA-relevant supporting documents according to Table 6-1 of [ITU-T M.3170.0]). Refer to clause 6.3 of the companion Recommendation [ITU-T M.3170.0] for a detailed overview of the supporting documentation. Supporting documents that are only packaged with TMF608 are coloured in blue. Supporting documents that are not packaged with TMF513 are shaded in gray. + +At the ITU-T side, Figure 7-2 depicts an "ITU-T Recommendation cloud" with the IA-relevant ITU-T Recommendations. The cloud encompasses the TMN-related Recommendations from TMF513 and the M.3020-series progression. This progression will, in particular, adopt at a high level 3GPP's UML modelling framework [b-TS 132 151 v6.3.0], [b-TS 132 152 v6.3.0] which is based on their fundamental IRP concept [b-TS 132 150 v6.5.0]. Harmonization of the MTNM UML modelling principles (see also [TMF814 v3.0 SD]), repertoire and templates with 3GPP's UML modelling approach and the M.3020-series progression is for further study. + +# Bibliography + +The following references contain information that was used in the development of the M.3170-series Recommendations. + +- [b-TMF044 v2.0] TM Forum TMF044 Version 2.0 (2003), *TM Forum Glossary*. +[www.tmforum.org/browse.aspx?catid=860&linkID=28087](http://www.tmforum.org/browse.aspx?catid=860&linkID=28087) +- [b-TMF402 v5.10] TM Forum TMF402 Version 5.10 (2005), *TMF Business Agreement Template*. +[www.tmforum.org/browse.aspx?catID=866&linkID=24300](http://www.tmforum.org/browse.aspx?catID=866&linkID=24300) +- [b-TMF404 v2.8] TM Forum TMF404 Version 2.8 (2005), *TMF Information Agreement Template*. +[www.tmforum.org/browse.aspx?catID=866&linkID=24299](http://www.tmforum.org/browse.aspx?catID=866&linkID=24299) +- [b-TMF513 v2.1] TM Forum TMF513 Version 2.1 (2002), *Multi-Technology Network Management (MTNM) NML-EML Interface: Business Agreement*. +[www.tmforum.org/browse.aspx?catid=860&linkID=24195](http://www.tmforum.org/browse.aspx?catid=860&linkID=24195). +- [b-TMF608 v2.1] TM Forum TMF608 Version 2.1 (2002), *Multi-Technology Network Management (MTNM) NML-EML Interface: Information Agreement*, PDF version and generated HTML version. +[www.tmforum.org/browse.aspx?catid=860&linkID=20309](http://www.tmforum.org/browse.aspx?catid=860&linkID=20309). +- [b-TS 132 150] ETSI TS 132 150 Version 6.5.0 (2006), *Digital cellular telecommunications system (Phase 2+); UMTS; Telecommunication management; Integration Reference Point (IRP) Concept and definitions*. +- [b-TS 132 151] ETSI TS 132 151 Version 6.3.0 (2006), *Digital cellular telecommunications system (Phase 2+); UMTS; Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template*. +- [b-TS 132 152] ETSI TS 132 152 Version 6.3.0 (2005), *Digital cellular telecommunications system (Phase 2+); UMTS; Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3170.4-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/M/T-REC-M.3170.4-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/M/T-REC-M.3170.4-201504-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/M/T-REC-M.3173.1-202401-I_PDF-E/raw.md b/marked/M/T-REC-M.3173.1-202401-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f626d10687ca97630bb92e6dccf8a68b6124479f --- /dev/null +++ b/marked/M/T-REC-M.3173.1-202401-I_PDF-E/raw.md @@ -0,0 +1,816 @@ + + +# Recommendation**ITU-T M.3173.1 (01/2024)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **Interface for synergy management of cloud and software-defined networking-based networks – Protocol neutral requirements** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +### **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3173.1 + +## Interface for synergy management of cloud and software-defined networking-based networks – Protocol neutral requirements + +## Summary + +Recommendation ITU-T M.3173.1 specifies interface requirements for synergy management of cloud and networks based on software-defined networking (SDN). Recommendation ITU-T M.3173.1 describes the interface position for the synergy management system, and synergy management scenarios for cloud and SDN-based networks. Recommendation ITU-T M.3173.1 also specifies the management interface requirements and the related use cases for the synergy management interface at a technology independent level (protocol neutral). + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3173.1 | 2024-01-13 | 2 | 11.1002/1000/15771 | + +## Keywords + +Cloud, interface, protocol neutral requirements, SDN, synergy management. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Concepts and background..... | 2 | +| 7 Business-level requirements ..... | 3 | +| 7.1 Requirements ..... | 3 | +| 7.2 Actor roles ..... | 4 | +| 7.3 Telecommunication resources ..... | 4 | +| 7.4 High-level use cases ..... | 5 | +| 8 Specification-level requirements ..... | 7 | +| 8.1 Requirements ..... | 7 | +| 8.2 Actor roles ..... | 7 | +| 8.3 Telecommunication resources ..... | 7 | +| 8.4 Use cases ..... | 7 | +| Appendix I – Associations between function requirements and the corresponding interfaces..... | 21 | +| Bibliography..... | 22 | + + + +# Recommendation ITU-T M.3173.1 + +## Interface for synergy management of cloud and software-defined networking-based networks – Protocol neutral requirements + +## 1 Scope + +This Recommendation specifies interface requirements for synergy management of cloud and networks based on software-defined networking (SDN). This Recommendation describes the interface position for the synergy management system (SMS), and the synergy management scenarios of cloud and SDN-based networks. The main content in this Recommendation specifies the management interface requirements and the related use cases for the synergy management interface at a technology independent level (protocol neutral). + +The management interface requirements provided in this Recommendation follows the ITU-T M.3020 interface specification methodology in the requirements phase, and is developed in a protocol neutral manner. + +This Recommendation applies to the design, development and inter-operation of SMSs of cloud and SDN-based networks. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2023), *Management interface specification methodology*. +- [ITU-T M.3372] Recommendation ITU-T M.3372 (2018), *Requirements for resource management in cloud-aware telecommunication management systems*. +- [ITU-T M.3373] Recommendation ITU-T M.3373 (2020), *Requirements for synergy management of cloud and SDN-based networks*. + +## 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 cloud service** [b-ITU-T Y.3500]: One or more capabilities offered via cloud computing (see clause 3.2.5 of [b-ITU-T Y.3500]) invoked using a defined interface. +- 3.1.2 private network** [b-ITU-T Q.1290]: A network which provides services to a specific set of users only. + +### 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------------------------| +| CMS | Cloud Management System | +| FM | Fulfilment Management | +| FS | Function Set | +| FUN | Function | +| ID | Identifier | +| PM | Policy Management | +| REQ | Requirement | +| RM | Resource Management | +| SbNMS | Software-defined networking-based Network Management System | +| SDN | Software-Defined Networking | +| SMS | Synergy Management System | + +## 5 Conventions + +In this Recommendation: + +- The phrase "**is required**" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. +- The phrase "**is recommended**" indicates a requirement that is recommended but which is not absolutely required. Thus this requirement needs not be present to claim conformance. +- For the qualifiers of a use case in the specification-level requirements, "**M**" stands for mandatory, and "**O**" stands for optional. + +## 6 Concepts and background + +Traditionally, an SDN-based network has its own management system and provides SDN network management functions, while a cloud also has its own management system. Telecommunication operators use the two systems to provide services to their customers. Some improvements have been made to each system, such as functional requirements for resource management proposed in [ITU-T M.3372]. However, when an operator needs to provide a synergy service (containing both a cloud service and the related network service for customer use), it needs to use the two management systems jointly, and coordinate manually, which suffers from low efficiency, high time consumption and proneness to errors. In this context, requirements for synergy management of cloud and SDN-based networks are proposed in [ITU-T M.3373]. + +Based on the information provided in [ITU-T M.3373], the logical architecture of synergy management of cloud and SDN-based networks can be found in Figure 1, which mainly shows two interfaces between the management systems. + +Interface I1 is the interface between the SMS and the software-defined networking-based network management system (SbNMS). + +Interface I2 is the interface between the SMS and the cloud management system (CMS). + +The purpose of this Recommendation is to provide detailed interface requirements for both interfaces I1 and I2. + +![Diagram showing the interface position among synergy management related systems. At the top is a box labeled 'Synergy management system of cloud and SDN-based networks'. Below it, two boxes are connected via dashed lines labeled 'Interface I1' and 'Interface I2'. The left box is 'SDN-based network management system' and the right box is 'Cloud management system'. Below the SDN-based network management system is a cloud labeled 'SDN network resources'. Below the Cloud management system is a cloud labeled 'Cloud resources'. A small text 'M.3137.1(24)' is at the bottom right.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph TD + SMS[Synergy management system of cloud and SDN-based networks] + SbNMS[SDN-based network management system] + CMS[Cloud management system] + SDN_Net[SDN network resources] + Cloud_Resources[Cloud resources] + + SMS ---|Interface I1| SbNMS + SMS ---|Interface I2| CMS + SbNMS --- SDN_Net + CMS --- Cloud_Resources + +``` + +Diagram showing the interface position among synergy management related systems. At the top is a box labeled 'Synergy management system of cloud and SDN-based networks'. Below it, two boxes are connected via dashed lines labeled 'Interface I1' and 'Interface I2'. The left box is 'SDN-based network management system' and the right box is 'Cloud management system'. Below the SDN-based network management system is a cloud labeled 'SDN network resources'. Below the Cloud management system is a cloud labeled 'Cloud resources'. A small text 'M.3137.1(24)' is at the bottom right. + +**Figure 1 – Interface position among synergy management related systems** + +The purpose of the synergy management of cloud and SDN-based network is for both SbNMS and CMS to perform functions for SMS to configure the related resources, thereby synergy services of cloud and the corresponding SDN-based networks can be easily fulfilled and managed. Clauses 7 and 8 specify requirements for interfaces I1 and I2 to support such functionalities. + +## 7 Business-level requirements + +## 7.1 Requirements + +Synergy management functions of cloud and SDN-based networks are the key emerging features for the network management interfaces between the SMS and the SbNMS or between the SMS and the CMS, as shown in Figure 1, where the SMS takes the manager role, and the SbNMS or the CMS the agent role. The manager should be able to request an agent to perform synergy service management functions, either to configure certain cloud resources or network resources. The synergy management interface requirements (REQs) are a subset of the requirements mentioned in [ITU-T M.3373], those functions that do not involve interaction across interface I1 or I2 are not addressed in this Recommendation (e.g., service order management can be done within the SMS itself). These interface REQs can be grouped into the following aspects. + +- Synergy service fulfilment management (FM) of resource reservation for a service; creation, update, suspension, resumption, query and deletion of a service; network bandwidth adjustment; and service status monitoring. +- Synergy service policy management (PM), including: creation; query; deletion; and modification of service policy information for cloud service or private network service. +- Synergy resource management (RM), including: management of end-to-end cloud resources; related network resources; connection management of cloud data centres and private networks; dynamic resource update; and resource query, etc. + +### 7.1.1 Synergy service fulfilment management + +The agent is required to provide the following functions (FUNs) across the management interface for the manager to: + +- REQ-FM-FUN-01 check for resource reservation of a synergy service; +- REQ-FM-FUN-02 create a synergy service, which will be mapped to a network service across interface I1 or a cloud service across interface I2; +- REQ-FM-FUN-03 query the basic information about a synergy service; +- REQ-FM-FUN-04 suspend a synergy service; +- REQ-FM-FUN-05 resume a synergy service; + +REQ-FM-FUN-06 delete a synergy service; + +REQ-FM-FUN-07 query the running status of a synergy service. + +The agent is recommended to provide the following functions across the management interface for the manager to: + +REQ-FM-FUN-08 update the information about a synergy service; + +REQ-FM-FUN-09 adjust the bandwidth of a synergy service. + +### **7.1.2 Synergy service policy management** + +The agent is required to provide the following functions across the management interface for the manager to: + +REQ-PM-FUN-11 query the information about an existing service policy that is supported by an SbNMS (across interface I1) or a CMS (across interface I2); + +REQ-PM-FUN-12 query the information about all the existing service policies that are supported by an SbNMS (across interface I1) or a CMS (across interface I2); + +REQ-PM-FUN-13 create a new synergy service policy (which will be mapped to a private network service policy across interface I1 or a cloud service policy across interface I2); + +REQ-PM-FUN-14 delete an existing service policy. + +The agent is recommended to provide the following functions across the management interface for the manager to: + +REQ-SM-FUN-15 update the service policy information stored in an SbNMS (across interface I1), or a CMS (across interface I2). + +### **7.1.3 Synergy resource management** + +The agent is required to provide the following functions across the management interface for the manager to: + +REQ-RM-FUN-21 query the information about a specific existing SDN-based network element across interface I1; + +REQ-RM-FUN-22 query the information about all the existing SDN-based network elements across interface I1; + +REQ-RM-FUN-23 query the information about all the physical links among SDN-based network elements and their relations across interface I1; + +REQ-RM-FUN-24 query the information about a specific existing cloud resource (node) across interface I2; + +REQ-RM-FUN-25 query the information about all the existing cloud resources (nodes) across interface I2. + +The associations between the preceding function requirements and the two related interfaces is further explained in Appendix I. + +## **7.2 Actor roles** + +The capabilities described in this Recommendation are available and relevant to all agents and managers. In this Recommendation, SMS acts as a manager; SbNMS and CMS act as agents. + +## **7.3 Telecommunication resources** + +The synergy management functionality is applicable to all types of telecommunication resource involved in the synergy service of both clouds and SDN-based networks. + +## 7.4 High-level use cases + +The synergy management function set (FS) contains: synergy FM FS, synergy PM FS, and synergy RM FS. Figure 2 shows the top level use case. + +The synergy FM FS contains the following functions: reserve service resource; create synergy service; query synergy service; suspend synergy service; resume synergy service; delete synergy service; and update synergy service. Figure 3 shows the details. + +The synergy PM FS contains the following functions: query synergy service policy; query all synergy service policy list; create synergy service policy; delete synergy service policy; and update synergy service policy. Figure 4 shows the details. + +The synergy RM FS contains the following functions: query SDN network element; query all SDN network element list; query all SDN link list; query cloud resource; and query all cloud resource list. Figure 5 shows the details. + +Figures 2 to 5 show the functions involved in the synergy management FS. Figure 2 is the overview use case diagram of synergy management FS; Figure 3 is the synergy service FM FS use case diagram; Figure 4 is the synergy service PM FS use case diagram; Figure 5 is the synergy RM FS use case diagram. + +![UML Use Case Diagram showing the Synergy Management FS overview. The diagram features an actor labeled 'Manager' connected to a central use case 'Synergy_Management_FS'. This central use case includes three other use cases via dashed arrows labeled '<>': 'Synergy_Service_Fulfilment_Management_FS', 'Synergy_Service_Policy_Management_FS', and 'Synergy_Resource_Management_FS'.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` +graph TD; Manager((Manager)) --> SMFS(Synergy_Management_FS); SMFS -.->|<>| SSFMS(Synergy_Service_Fulfilment_Management_FS); SMFS -.->|<>| SSPMS(Synergy_Service_Policy_Management_FS); SMFS -.->|<>| SRMFS(Synergy_Resource_Management_FS); +``` + +UML Use Case Diagram showing the Synergy Management FS overview. The diagram features an actor labeled 'Manager' connected to a central use case 'Synergy\_Management\_FS'. This central use case includes three other use cases via dashed arrows labeled '<>': 'Synergy\_Service\_Fulfilment\_Management\_FS', 'Synergy\_Service\_Policy\_Management\_FS', and 'Synergy\_Resource\_Management\_FS'. + +M.3137.1(24) + +**Figure 2 – Synergy management FS overview** + +![UML Use Case Diagram for Synergy Service Fulfilment Management FS. The diagram shows a Manager actor connected to a central use case 'Synergy_Service_Fulfilment_Management_FS'. This central use case includes seven other use cases via <> relationships: 'reserve_service_resource', 'create_synergy_service', 'query_synergy_service', 'suspend_synergy_service', 'resume_synergy_service', 'delete_synergy_service', and 'update_synergy_service'.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +usecaseDiagram + actor Manager + usecase Synergy_Service_Fulfilment_Management_FS + usecase reserve_service_resource + usecase create_synergy_service + usecase query_synergy_service + usecase suspend_synergy_service + usecase resume_synergy_service + usecase delete_synergy_service + usecase update_synergy_service + + Manager --> Synergy_Service_Fulfilment_Management_FS + Synergy_Service_Fulfilment_Management_FS -.->|<>| reserve_service_resource + Synergy_Service_Fulfilment_Management_FS -.->|<>| create_synergy_service + Synergy_Service_Fulfilment_Management_FS -.->|<>| query_synergy_service + Synergy_Service_Fulfilment_Management_FS -.->|<>| suspend_synergy_service + Synergy_Service_Fulfilment_Management_FS -.->|<>| resume_synergy_service + Synergy_Service_Fulfilment_Management_FS -.->|<>| delete_synergy_service + Synergy_Service_Fulfilment_Management_FS -.->|<>| update_synergy_service + +``` + +M.3137.1(24) + +UML Use Case Diagram for Synergy Service Fulfilment Management FS. The diagram shows a Manager actor connected to a central use case 'Synergy\_Service\_Fulfilment\_Management\_FS'. This central use case includes seven other use cases via <> relationships: 'reserve\_service\_resource', 'create\_synergy\_service', 'query\_synergy\_service', 'suspend\_synergy\_service', 'resume\_synergy\_service', 'delete\_synergy\_service', and 'update\_synergy\_service'. + +**Figure 3 – Performance measurement management FS** + +![UML Use Case Diagram for Synergy Service Policy Management FS. The diagram shows a Manager actor connected to a central use case 'Synergy_Service_Policy_Management_FS'. This central use case includes five other use cases via <> relationships: 'query_synergy_service_policy', 'query_all_synergy_service_policy_list', 'create_synergy_service_policy', 'delete_synergy_service_policy', and 'update_synergy_service_policy'.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +``` + +usecaseDiagram + actor Manager + usecase Synergy_Service_Policy_Management_FS + usecase query_synergy_service_policy + usecase query_all_synergy_service_policy_list + usecase create_synergy_service_policy + usecase delete_synergy_service_policy + usecase update_synergy_service_policy + + Manager --> Synergy_Service_Policy_Management_FS + Synergy_Service_Policy_Management_FS -.->|<>| query_synergy_service_policy + Synergy_Service_Policy_Management_FS -.->|<>| query_all_synergy_service_policy_list + Synergy_Service_Policy_Management_FS -.->|<>| create_synergy_service_policy + Synergy_Service_Policy_Management_FS -.->|<>| delete_synergy_service_policy + Synergy_Service_Policy_Management_FS -.->|<>| update_synergy_service_policy + +``` + +M.3137.1(24) + +UML Use Case Diagram for Synergy Service Policy Management FS. The diagram shows a Manager actor connected to a central use case 'Synergy\_Service\_Policy\_Management\_FS'. This central use case includes five other use cases via <> relationships: 'query\_synergy\_service\_policy', 'query\_all\_synergy\_service\_policy\_list', 'create\_synergy\_service\_policy', 'delete\_synergy\_service\_policy', and 'update\_synergy\_service\_policy'. + +**Figure 4 – Synergy service policy management FS** + +![UML Use case diagram for Synergy Resource Management FS. An actor labeled 'Manager' is connected to the central use case 'Synergy_Resource_Management_FS'. This central use case includes five other use cases via dashed arrows labeled '<>': 'query_SDN_network_element', 'query_all_SDN_network_element_list', 'query_all_SDN_link_list', 'query_cloud_resource', and 'query_all_cloud_resource_list'. A reference code 'M.3137.1(24)' is located in the bottom right corner of the diagram area.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +UML Use case diagram for Synergy Resource Management FS. An actor labeled 'Manager' is connected to the central use case 'Synergy\_Resource\_Management\_FS'. This central use case includes five other use cases via dashed arrows labeled '<>': 'query\_SDN\_network\_element', 'query\_all\_SDN\_network\_element\_list', 'query\_all\_SDN\_link\_list', 'query\_cloud\_resource', and 'query\_all\_cloud\_resource\_list'. A reference code 'M.3137.1(24)' is located in the bottom right corner of the diagram area. + +**Figure 5 – Synergy resource management FS** + +## **8 Specification-level requirements** + +## **8.1 Requirements** + +There are no specification-level requirements. + +## **8.2 Actor roles** + +See clause 7.2. + +## **8.3 Telecommunication resources** + +See clause 7.3. + +## **8.4 Use cases** + +The general exceptions (e.g., communication error, processing error) related to all use cases are not described in clauses 8.4.1 to 8.4.3, and will only be handled in the design phase. + +### **8.4.1 Synergy service fulfilment management related use cases** + +##### **8.4.1.1 Reserve resources for a synergy service (M)** + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to check whether there are enough resources available to create a synergy service through management interfaces I1 and I2. If they are sufficient, resource reservation is required for a period of time. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The manager receives a request to provide a new synergy service to its customer. | | +| Begins when | The manager sends a request to each of the two agents to check whether there are enough resources for this synergy service. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 | The manager sends a request to each of the two agents to check whether there are enough resources for this synergy service. The parameters may contain:
  • – the identifier (ID) of the synergy service;
  • – the start time of the synergy service;
  • – the stop time of the synergy service (optional);
  • – the requests for cloud resources from the synergy service (CMS only);
  • – the requests for private network resources from the synergy service (SbNMS only).
| | +| Step 2.1 | For CMS, if there are enough cloud resources for this synergy service, the agent reserves the required cloud resources for a while and gives the manager a reservation successful response. | | +| Step 2.2 | Otherwise, the agent gives the manager a reservation failed response indicating that there are insufficient resources for this service. | | +| Step 3.1 | For SbNMS, if there are enough network resources for this synergy service, the agent reserves the required network resources for a while and gives the manager a successful response. | | +| Step 3.2 | Otherwise, the agent gives the manager a "reservation failed response" indicating that there are insufficient resources for this service. | | +| Ends when | A reservation successful or failed response, or an exception is returned to the manager. | | +| Exceptions |
  • – Insufficient resources
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The required cloud resources are reserved by the CMS, and the network resources are reserved by the SbNMS. | | +| Traceability | REQ-FM-FUN-01 | | + +##### 8.4.1.2 Create a synergy service (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to create a synergy service through management interfaces I1 and I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The responses for "reserve synergy service resource" from both CMS and SbNMS are successful. | Use case 8.4.1.1 | +| Begins when | The manager sends a request to each of the two agents to create the synergy service, based on the resources that have been reserved. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 | The manager sends a request to each of the two agents. The parameters may contain:
  • – the ID of the synergy service to be created;
  • – the start time of the synergy service;
  • – the stop time of the synergy service (optional);
  • – the requests for cloud resources from the synergy service (CMS only);
  • – the requests for private network resources from the synergy service (SbNMS only).
| | +| Step 2.1 | For CMS, if the requested new service can be created, it allocates the reserved cloud resources to this synergy service and gives the manager a service creation successful response, the allocated cloud resource information is also returned. | | +| Step 2.2 | Otherwise (due to some abnormal reasons, reservation timeout or resource unavailability), the agent gives the manager a service creation failed response; the reserved resources are released. | | +| Step 3.1 | For SbNMS, if the requested new service can be created, the manager allocates the reserved network resources to this synergy service and gives the manager a service creation successful response; the allocated private network resource information is also returned. | | +| Step 3.2 | Otherwise (due to some abnormal reason), the agent gives the manager a service creation failed response; the reserved resources are released. | | +| Ends when | A service creation successful or failed response, or an exception is returned to the manager. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The synergy service information is returned to manager successfully. | | +| Traceability | REQ-FM-FUN-02 | | + +##### 8.4.1.3 Query a synergy service (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to query the information about a synergy service through management interfaces I1 and I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service has been successfully created and the information is stored in both CMS and SbNMS. | Use case 8.4.1.2 | +| Begins when | The manager sends a request to each of the two agents to query the information about the synergy service. | | +| Step 1 | The manager sends a request to each of the two agents. The parameters may contain:
  • – the ID of the synergy service that is already created.
| | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 2 | For CMS, if the specified synergy service exists, it returns the information about the services, which may include:
  • – the ID of the synergy service;
  • – the start time of the synergy service;
  • – the stop time of the synergy service (optional);
  • – the requests for cloud from the synergy service (CMS only);
  • – the cloud resources allocated for this service. (CMS only);
  • – the running status of the cloud-side synergy service (CMS only).
| | +| Step 3 | For SbNMS, if the specified synergy service exists, the manager returns the information about the services, which may include:
  • – the ID of the synergy service;
  • – the start time of the synergy service;
  • – the stop time of the synergy service (optional);
  • – the requests for network from the synergy service (SbNMS only);
  • – the network resources allocated for this service (SbNMS only);
  • – the running status of the cloud-side synergy service (SbNMS only).
| | +| Ends when | A synergy service information response or an exception is returned to the manager. | | +| Exceptions |
  • – Synergy service ID does not exist
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The synergy service information is returned to the manager. | | +| Traceability | REQ-FM-FUN-03, REQ-FM-FUN-09 | | + +##### 8.4.1.4 Suspend a synergy service (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to suspend a synergy service through management interfaces I1 and I2. When suspended, the synergy service does not provide cloud or network services to the customer temporarily. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service has been created in both CMS and SbNMS. | Use case 8.4.1.2 | +| Begins when | The manager sends a request to each of the two agents to suspend the synergy service. | | +| Step 1 | The manager sends a request to each of the two agents. The parameters may contain:
  • – the ID of the synergy service to be suspended.
| | +| Step 2.1 | For CMS, if the specified synergy service exists, the CMS suspends the corresponding cloud-side synergy service and gives the manager a successful service suspension response. | | +| Step 2.2 | For CMS, if the suspension fails, the CMS gives the manager a failed service suspension response. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 3.1 | For SbNMS, if the specified synergy service exists, the SbNMS suspends the corresponding network-side synergy service and gives the manager a successful service suspension response. | | +| Step 3.2 | For SbNMS, if the suspension fails, the SbNMS gives the manager a failed service suspension response. | | +| Ends when | A service suspension successful or failed response, or an exception is returned to the manager. | | +| Exceptions |
  • – Synergy service ID does not exist
  • – Synergy service already suspended
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The synergy service is suspended successfully. | | +| Traceability | REQ-FM-FUN-04 | | + +##### 8.4.1.5 Resume a synergy service (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to resume a suspended synergy service through management interfaces I1 and I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service has been suspended in both CMS and SbNMS. | Use case 8.4.1.4 | +| Begins when | The manager sends a request to each of the two agents to resume the suspended synergy service. | | +| Step 1 | The manager sends a request to each of the two agents. The parameters may contain:
  • – the ID of the synergy service that is already suspended.
| | +| Step 2.1 | For CMS, if the specified synergy service exists and suspended, the CMS resumes the corresponding cloud-side synergy service and gives the manager a successful service resumption response. | | +| Step 2.2 | For CMS, if the resumption fails, the CMS gives the manager a failed service resumption response. | | +| Step 3.1 | For SbNMS, if the specified synergy service exists and suspended, the SbNMS resumes the corresponding network-side synergy service and gives the manager a successful service resumption response. | | +| Step 3.2 | For SbNMS, if the resumption fails, the SbNMS gives the manager a failed service resumption response. | | +| Ends when | A service resumption successful or failed response, or an exception is returned to the manager. | | +| Exceptions |
  • – Synergy service ID does not exist
  • – Synergy service not suspended
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The synergy service is resumed successfully. | | +| Traceability | REQ-FM-FUN-05 | | + +##### 8.4.1.6 Delete a synergy service (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to delete a suspended synergy service through management interfaces I1 and I2. When the service is deleted, the corresponding resources are also released. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service has been suspended in both CMS and SbNMS. | Use case 8.4.1.4 | +| Begins when | The manager sends a request to each of the two agents to delete the suspended synergy service. | | +| Step 1 | The manager sends a request to each of the two agents.
The parameters may contain:
– the ID of the synergy service to be deleted. | | +| Step 2.1 | For CMS, if the specified synergy service exists and suspended, the CMS deletes the corresponding cloud-side synergy service, releases the corresponding cloud resources and gives the manager a successful service deletion response. | | +| Step 2.2 | For CMS, if the deletion fails, the CMS gives the manager a failed service deletion response. | | +| Step 3.1 | For SbNMS, if the specified synergy service exists and suspended, the SbNMS deletes the corresponding network-side synergy service, releases the corresponding cloud resources and gives the manager a successful service deletion response. | | +| Step 3.2 | For SbNMS, if the deletion fails, the SbNMS gives the manager a failed service deletion response. | | +| Ends when | A service deletion successful or failed response, or an exception is returned to the manager. | | +| Exceptions | – Synergy service ID does not exist
– Synergy service not suspended
– Invalid input parameter
– Operation failed due to internal problem | | +| Post-conditions | The synergy service is deleted successfully. | | +| Traceability | REQ-FM-FUN-06 | | + +##### 8.4.1.7 Update synergy service (O) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | When the customer requirement for an existing synergy service is changed, the manager can request the agents to update a suspended synergy service through management interfaces I1 or interface I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of telecommunication resource. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service has been suspended in both CMS and SbNMS. | Use case 8.4.1.4 | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Begins when | The manager sends a request to each of the two agents to update the suspended synergy service. | | +| Step 1 |

The manager sends a request to the agent to modify the attribute values of a synergy service. The following attributes can be modified:

  • – the start time of the synergy service;
  • – the stop time of the synergy service;
  • – the requests for cloud resources from the synergy service (CMS only);
  • – the requests for private network resources from the synergy service (SbNMS only).

In the update request, the input parameters may contain all or part of the following:

  • – the ID of the synergy service to be updated (M);
  • – the new start time of the synergy service (O);
  • – the new stop time of the synergy service (O);
  • – the new requests for the cloud resources from the synergy service (CMS only) (O);
  • – the new requests for the SDN-based network resources from the synergy service (SbNMS only). (O)

If the information about the synergy services to be updated only affects the cloud resources part, this request is only sent to CMS; if the information about the synergy services to be updated only affects the SDN-based network resources part, this request is only sent to SbNMS.

| | +| Step 2.1 | For CMS, if the new request to update this synergy service is acceptable, and there are enough cloud resources to support this update, the CMS performs the required resources allocation (if needed), updates the synergy service according to the update request and returns the service update successful response to the manager. | | +| Step 2.2 | For CMS, if the update fails, the CMS gives the manager a failed service policy update response. | | +| Step 3.1 | For SbNMS, if the new request to update this synergy service is acceptable, and there are enough network resources to support this update, the SbNMS performs the required resources allocation (if needed), updates the synergy service according to the update request and returns the service update successful response to the manager. | | +| Step 3.2 | For SbNMS, if the update fails, the SbNMS gives the manager a failed service policy update response. | | +| Exceptions |
  • – Synergy service update not supported
  • – Synergy service ID does not exist
  • – Synergy service not suspended
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The synergy service is updated successfully. | | +| Traceability | REQ-FM-FUN-07, REQ-FM-FUN-08 | | + +#### 8.4.2 Synergy service policy management related use cases + +##### 8.4.2.1 Query a synergy service policy (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to query the information about an existing service policy through management interfaces I1 and I2. The CMS returns the cloud service-related policy information, and SbNMS returns the network service-related policy information. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | – | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service policy exists in CMS or SbNMS. | | +| Begins when | The manager sends a request to each of the two agents to query the information about the synergy service. | | +| Step 1 | The manager sends a request to each of the two agents.
The parameters may contain:
  • – the ID of the cloud service policy to be queried (for CMS);
  • – the ID of the network service policy to be queried (for SbNMS).
| | +| Step 2 | For CMS, if the specified service policy exists, it returns the information about the service policy, which may include:
  • – the ID of the cloud service policy;
  • – the name of the service policy;
  • – the type of the service policy;
  • – detailed description of the service policy.
| | +| Step 3 | For SbNMS, if the specified service policy exists, it returns the information about the service policy, which may include:
  • – the ID of the network service policy;
  • – the name of the service policy;
  • – the type of the service policy;
  • – detailed description of the service policy.
| | +| Ends when | A service policy information response or an exception is returned to the manager. | | +| Exceptions |
  • – Service policy ID does not exist
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The service policy information is returned to the manager. | | +| Traceability | REQ-PM-FUN-11 | | + +##### 8.4.2.2 Query all service policy list (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to query the information about all existing service policies through management interfaces I1 and I2. The CMS returns the cloud service-related policies information and SbNMS returns the network service-related policy information. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | – | | +| Assumptions | Communication between the manager and the agent is available. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Pre-conditions | – | | +| Begins when | The manager sends a request to each of the two agents to query the information about the synergy service. | | +| Step 1 | The manager sends a request to each of the two agents. There is no need to provide input parameters in this use case. | | +| Step 2 | For CMS, it returns the list information about all the applicable cloud service policies, and each policy information may include:
  • – the ID of the cloud service policy;
  • – the name of the service policy;
  • – the type of the service policy;
  • – detailed description of the service policy.
| | +| Step 3 | For SbNMS, the manager returns the list information about all the applicable network service policies, and each policy information may include:
  • – the ID of the network service policy;
  • – the name of the service policy;
  • – the type of the service policy;
  • – detailed description of the service policy.
| | +| Ends when | A service policy list information response or an exception is returned to the manager. | | +| Exceptions |
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The service policy list information is returned to the manager. | | +| Traceability | REQ-PM-FUN-12 | | + +##### 8.4.2.3 Create a service policy (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to create a new service policy through management interface I1 for network service policy, and management interface I2 for cloud service policy. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | – | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The agent supports the function of service policy creation. | | +| Begins when | The manager sends a request to the agent to create a service policy. | | +| Step 1 | The manager sends a request to the agent to create a service policy. The input parameter may include:
  • – the ID of the service policy (for cloud or network service policy);
  • – the name of the service policy;
  • – the type of the service policy;
  • – detailed description of the service policy.
| | +| Step 2.1 | If the request is sent to the CMS, it will check the existing cloud service policies to ensure there are no conflicts. If the new policy can be created, the CMS applies the new policy in the cloud system and gives the manager a service policy creation successful response. | | +| Step 2.2 | Otherwise, the CMS gives the manager a service policy creation failed response. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 3.1 | If the request is sent to the SbNMS, it will check the existing network service policies to ensure there are no conflicts. If the new policy can be created, the SbNMS applies the new policy in the network system and gives the manager a service policy creation successful response. | | +| Step 3.2 | Otherwise, the SbNMS gives the manager a service policy creation failed response. | | +| Ends when | A service policy creation successful or failed response, or an exception is returned to the manager. | | +| Exceptions |
  • – Service policy already exists
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The new service policy is created in the CMS or SbNMS. | | +| Traceability | REQ-PM-FUN-13 | | + +##### 8.4.2.4 Delete a synergy service policy (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to delete an existing service policy through management interfaces I1 and I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | – | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified synergy service policy exists in CMS or SbNMS. | | +| Begins when | The manager sends a request to the agent to delete an existing service policy. | | +| Step 1 | The manager sends a request to the agent to delete a policy.
The parameters may contain:
  • – the ID of the cloud service policy to be deleted (for CMS);
  • – the ID of the network service policy to be deleted (for SbNMS).
| | +| Step 2.1 | For CMS, if the specified service policy exists and can be deleted, it returns a policy deletion successful response to the manager. | | +| Step 2.2 | For CMS, if the deletion fails, the CMS gives the manager a failed service policy deletion response. | | +| Step 3.1 | For SbNMS, if the specified service policy exists and can be deleted, it returns a policy deletion successful response to the manager. | | +| Step 3.2 | For SbNMS, if the deletion fails, the SbNMS gives the manager a failed service policy deletion response. | | +| Ends when | A service policy deletion successful or failed response, or an exception is returned to the manager. | | +| Exceptions |
  • – Service policy ID does not exist
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The synergy service is deleted successfully. | | +| Traceability | REQ-PM-FUN-14 | | + +##### 8.4.2.5 Update a synergy service policy (O) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to update a service policy through management interfaces I1 and I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | – | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified service policy exists in the CMS or the SbNMS. | | +| Begins when | The manager sends a request to the agent to update an existing service policy. | | +| Step 1 |

The manager sends a request to the agent (either CMS or SbNMS) to modify the attribute values of a service policy. The following attributes of the service policy can be modified:

  • – the name of the service policy;
  • – the type of the service policy;
  • – detailed description of the service policy.

In the update request, the input parameters may contain all or part of the following:

  • – the ID of the service policy to be updated (for a cloud or network service policy);
  • – the new name of the service policy(O);
  • – the new type of the specified service policy(O);
  • – the new description of the specified service policy (O).

According to the request, the agent modifies the corresponding service policy.

| | +| Step 2.1 | For CMS, if the specified service policy exists and can be updated, it returns the policy update successful response to the manager. | | +| Step 2.2 | For CMS, if the update fails, the CMS gives the manager a failed service policy update response. | | +| Step 3.1 | For SbNMS, if the specified service policy exists and can be updated, it returns the policy update successful response to the manager. | | +| Step 3.2 | For SbNMS, if the update fails, the SbNMS gives the manager a failed service policy update response. | | +| Exceptions |
  • – Service policy update not supported
  • – Service policy ID does not exist
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The service policy is updated successfully. | | +| Traceability | REQ-PM-FUN-15 | | + +#### 8.4.3 Synergy resource management related use cases + +##### 8.4.3.1 Query an SDN network element (M) + +| Use case stage | Evolution/specification | <>
Related use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent in SbNMS to query the information about an existing SDN network element through the management interface I1. | | +| Actors and roles | The manager invokes operation on the agent. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Telecommunication resources | All types of network resources. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified network element exists in the SbNMS. | | +| Begins when | The manager sends a request to the agent in SbNMS to query the information about a network element. | | +| Step 1 | The manager sends a query request to the agent in SbNMS. The input parameters may contain:
  • – the type of network element;
  • – the ID of the network element to be queried.
| | +| Step 2 | If the specified network element exists in the SbNMS, it returns the information about the network element, which may include:
  • – the type of network element;
  • – the ID of the network element;
  • – the list of attribute name and value pairs of the specified network element.
| | +| Ends when | A network element information response or an exception is returned to the manager. | | +| Exceptions |
  • – Network element ID does not exist
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The network element information is returned to the manager. | | +| Traceability | REQ-RM-FUN-21 | | + +##### 8.4.3.2 Query all SDN network element list (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent in SbNMS to query the information about all the existing SDN network elements through the management interface I1. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of network resources. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | – | | +| Begins when | The manager sends a request to the agent in SbNMS to query the information about all the network elements. | | +| Step 1 | The manager sends a query request to the agent in SbNMS. There is no need to provide input parameters in this use case. | | +| Step 2 | SbNMS returns the list information about all the existing network elements, and each network element description may include:
  • – the type of network element;
  • – the ID of the network element;
  • – the list of attribute name and value pairs of the specified network resource.
| | +| Ends when | A network element list information response or an exception is returned to the manager. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|--------------------------------------------------------------|-------------------------| +| Exceptions | – Operation failed due to internal problem | | +| Post-conditions | The network resource information is returned to the manager. | | +| Traceability | REQ-RM-FUN-22 | | + +##### 8.4.3.3 Query the list of all SDN physical links (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent in SbNMS to query the information about all the physical links among SDN-based network elements and their relations, through the management interface I1. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of network resources. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | – | | +| Begins when | The manager sends a request to the agent in SbNMS to query the information about all the physical links among SDN-based network elements and their relations. | | +| Step 1 | The manager sends a query request to the agent in SbNMS. There is no need to provide input parameters in this use case. | | +| Step 2 | SbNMS will return the list information about all the existing physical links among SDN-based network elements and their relations, and each item in the list may include:
  • – the ID of the physical link;
  • – the type of the physical link;
  • – the maximum bandwidth of the physical link;
  • – the IDs of the two network elements that the physical link connects.
| | +| Ends when | The list of all network physical links information or an exception is returned to the manager. | | +| Exceptions | – Operation failed due to internal problem | | +| Post-conditions | The list of all network physical links information is returned to the manager. | | +| Traceability | REQ-RM-FUN-23 | | + +##### 8.4.3.4 Query a cloud resource (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent in CMS to query the information about an existing cloud resource (e.g., node) through the management interface I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of cloud resources. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | The specified cloud resource exists in the CMS. | | +| Begins when | The manager sends a request to the agent in CMS to query the information about a cloud resource. | | + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 | The manager sends a query request to the agent in CMS. The input parameters may contain:
  • – the type of the cloud resource;
  • – the ID of the cloud resource to be queried.
| | +| Step 2 | If the specified cloud resource exists in the CMS, it returns the information about the cloud resource, which may include:
  • – the type of the cloud resource;
  • – the ID of the cloud resource;
  • – the list of attribute name and value pairs of the specified cloud resource.
| | +| Ends when | A cloud resource information response or an exception is returned to the manager. | | +| Exceptions |
  • – Cloud resource ID does not exist
  • – Invalid input parameter
  • – Operation failed due to internal problem
| | +| Post-conditions | The cloud resource information is returned to the manager. | | +| Traceability | REQ-RM-FUN-24 | | + +##### 8.4.3.5 Query all cloud resource list (M) + +| Use case stage | Evolution/specification | <>
Related use | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent in CMS to query the information about all the existing cloud resources through the management interface I2. | | +| Actors and roles | The manager invokes operation on the agent. | | +| Telecommunication resources | All types of cloud resources. | | +| Assumptions | Communication between the manager and the agent is available. | | +| Pre-conditions | – | | +| Begins when | The manager sends a request to the agent in CMS to query the information about all the cloud resources. | | +| Step 1 | The manager sends a query request to the agent in CMS. There is no need to provide input parameters in this use case. | | +| Step 2 | CMS will return the list information about all the existing cloud resources, and each cloud resource information may include:
  • – the type of the cloud resource;
  • – the ID of the cloud resource;
  • – the list of attribute name and value pairs of the specified cloud resource.
| | +| Ends when | A cloud resource list information response or an exception is returned to the manager. | | +| Exceptions |
  • – Operation failed due to internal problem
| | +| Post-conditions | All the existing cloud resources information is returned to the manager. | | +| Traceability | REQ-RM-FUN-25 | | + +## Appendix I + +### Associations between function requirements and the corresponding interfaces + +(This appendix does not form an integral part of this Recommendation.) + +This appendix presents the associations between each function requirement and the corresponding interfaces. + +Synergy service FM and synergy service PM, according to the description in [ITU-T M.3373], are included in synergy service management. Synergy service FM decomposes service requirements according to business logic and distributes them to the SbNMS and the CMS. Synergy service PM provides a set of service conditions and service actions to optimize the synergy services required of cloud and SDN-based networks. In the context, the function requirements are associated with both interfaces I1 and I2. + +By contrast, synergy RM supports resource information management and resource querying. Resource queries on SDN-based network elements are associated with interface I1, while the queries on cloud resource (node) are associated with interface I2. + +The associations between each function requirement and the corresponding interfaces (I1 or I2) are summarized in Table I.1. + +**Table I.1 – Associations between function requirements and the corresponding interfaces** + +| Category | Function requirements | Corresponding interfaces | +|---------------------------------------|-----------------------|--------------------------| +| Synergy service fulfilment management | REQ-FM-FUN-01 | I1, I2 | +| | REQ-FM-FUN-02 | | +| | REQ-FM-FUN-03 | | +| | REQ-FM-FUN-04 | | +| | REQ-FM-FUN-05 | | +| | REQ-FM-FUN-06 | | +| | REQ-FM-FUN-07 | | +| | REQ-FM-FUN-08 | | +| | REQ-FM-FUN-09 | | +| Synergy service policy management | REQ-PM-FUN-11 | | +| | REQ-PM-FUN-12 | | +| | REQ-PM-FUN-13 | | +| | REQ-PM-FUN-14 | | +| | REQ-PM-FUN-15 | | +| Synergy resource management | REQ-RM-FUN-21 | I1 | +| | REQ-RM-FUN-22 | | +| | REQ-RM-FUN-23 | | +| | REQ-RM-FUN-24 | I2 | +| | REQ-RM-FUN-25 | | + +## Bibliography + +- [b-ITU-T Q.1290] Recommendation Q.1290 (1998), *Glossary of terms used in the definition of intelligent networks.* +- [b-ITU-T Y.3500] Recommendation Y.3500 (2014) | ISO/IEC 17788:2014, *Information technology – Cloud computing – Overview and vocabulary.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3180-199210-I_PDF-E/raw.md b/marked/M/T-REC-M.3180-199210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..481bda981ca8dad5b323af79f660a0b3c1a15720 --- /dev/null +++ b/marked/M/T-REC-M.3180-199210-I_PDF-E/raw.md @@ -0,0 +1,731 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**M.3180** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +(10/92) + +**MAINTENANCE: TELECOMMUNICATIONS +MANAGEMENT NETWORK** + +--- + +**CATALOGUE OF TMN MANAGEMENT +INFORMATION** + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +**Recommendation M.3180** + +--- + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation M.3180 was prepared by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. + +# --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency. + +# CONTENTS + +| | | Page | +|-----|-----------------------------------------------------------------------------|-------------| +| 1 | Introduction ..... | 1 | +| 2 | Definitions..... | 1 | +| 3 | Catalogue overview..... | 1 | +| 4 | Techniques for specifying management information ..... | 2 | +| 5 | Relationships among CCITT management information Recommendations ..... | 2 | +| 5.1 | Generic Network Information Model ..... | 2 | +| 5.2 | Management information for switching and signalling equipment ..... | 2 | +| 5.3 | Management information for transmission equipment ..... | 2 | +| 5.4 | Management information for OSI..... | 3 | +| 5.5 | Management information for modems ..... | 3 | +| 6 | Management information supporting telecommunication network resources ..... | 3 | +| 6.1 | Network fragment..... | 3 | +| 6.2 | Managed element fragment ..... | 3 | +| 6.3 | Termination point fragment..... | 3 | +| 6.4 | Transmission fragment ..... | 6 | +| 6.5 | Cross-connection fragment..... | 6 | +| 7 | Management information supporting protocol machine resources ..... | 6 | +| 7.1 | OSI Protocols..... | 6 | +| 7.2 | ISDN Protocols..... | 6 | +| 7.3 | SS7 Protocols..... | 6 | +| 8 | Management information supporting functional areas..... | 6 | +| 8.1 | Common ..... | 7 | +| 8.2 | Fault management..... | 7 | +| 8.3 | Performance management ..... | 7 | +| 8.4 | Configuration management ..... | 7 | +| 8.5 | Accounting management ..... | 7 | +| 8.6 | Security management..... | 7 | +| | Annex A – Alphabetical index of management information..... | 7 | +| | Annex B – Inheritance Relationships ..... | 11 | + + + +# **CATALOGUE OF TMN MANAGEMENT INFORMATION** + +(1992) + +## *Abstract* + +This Recommendation is one of a series of Recommendations on the Telecommunications Management Network (TMN). It defines the scope of TMN management information, identifies related specification techniques, describes the relationships among CCITT Recommendations defining management information, and references definitions of currently available management information. + +## *Keywords* + +- fragment; +- managed object; +- model; +- OSI management; +- resource. + +# **1 Introduction** + +This Recommendation provides a catalogue of TMN management information involved in communications across the TMN interfaces defined in Recommendation M.3010 [1]. It does not define these management information, but rather identifies each by name and points to the Recommendation which contains its definition. The purpose of the Recommendation is to provide a “roadmap” to assist the reader in identifying the source of TMN management information. It also provides a listing of documents describing techniques and guidelines available to assist in the uniform definition of management information. + +For the purposes of this Recommendation, management information includes managed object classes, attributes, name bindings, conditional packages, actions, notifications and behaviours as described in Recommendation X.722 [2], the Guidelines for the Definition of Managed Objects (GDMO). Only managed object classes are identified initially. + +# **2 Definitions** + +This Recommendation depends on the definitions of the following terms from Recommendations X.701 [3] and X.722 [2]: managed object class, management support object, attributes, name bindings, conditional packages, actions, and notifications. + +# **3 Catalogue overview** + +This section provides a summary of the information contained in the remaining sections of this Recommendation. + +Section 4 contains a list of references to key documents which describe techniques for specifying management information as they apply to the TMN. + +Section 5 lists the associated CCITT management information documents and describes the relationships among them. + +Section 6 lists management information related to Recommendation M.3100 [4], the Generic Network Information Model (GNIM), and is categorized according to five fragments. GNIM extensions defined in other Recommendations are also included. + +Section 7 lists management information associated with protocol machine resources. + +Section 8 lists management information required to support common and specific functional areas. + +Annex A provides an alphabetical index of management information + +Annex B identifies the superclasses of managed object classes in §§ 6, 7, and 8. + +# 4 Techniques for specifying management information + +The Recommendations listed in this section describe the techniques which have been used in specifying TMN management information. + +The following four CCITT/ISO texts from OSI Management are broad in scope and are provided to encourage consistency between managed object definitions. + +| | | +|------------------------------------|---------------------------------------------------| +| Recommendation X.701 [ISO 10040] | Systems Management Overview; | +| Recommendation X.720 [ISO 10165-1] | Management Information Model; | +| Recommendation X.721 [ISO 10165-2] | Definition of Management Information; | +| Recommendation X.722 [ISO 10165-4] | Guidelines for the Definition of Managed Objects. | + +In addition the following two Recommendations provide guidelines for specifying management information specific to the TMN management area. + +| | | +|-----------------------|-----------------------------------------| +| Recommendation M.3020 | (TMN methodology); | +| Recommendation Q.8 | (Switching and signalling methodology). | + +# 5 Relationships among CCITT management information Recommendations + +## 5.1 *Generic Network Information Model* + +The Generic Network Information Model (GNIM) defined in Recommendation M.3100 [4] reflects the common elements from the many telecommunication resources within the scope of TMN. + +A generic telecommunications network information model is essential to the generation of uniform fault, configuration, performance, security, and accounting management standards. A common network model, identifying the generic resources that exist in a network and their associated attribute types, events, actions, and behaviours, provides a foundation for understanding the interrelationships between these resources and attributes, and may, in turn, promote uniformity in dealing with the various aspects of managing these resources and attributes. + +## 5.2 *Management information for switching and signalling equipment* + +The GNIM is expected to be refined by subclassing and extended in a non-generic manner in Recommendation Q.810 [5] to cover specific requirements for switching and signalling equipment. The management information for CCSS No. 7 protocol machine resources *will be* specified in draft Recommendation Q.751. The management information for ISDN is expected to be produced in the near future. + +## 5.3 *Management information for transmission equipment* + +The GNIM is refined by subclassing and extended in a non-generic manner in Recommendation G.774 [6] to cover specific requirements for SDH transmission equipment. Plans also exist to cover PDH transmission equipment. + +## 5.4 *Management information for OSI* + +The OSI Management Information described in Recommendation X.721 [7] [ISO 10165-2] primarily supports the management of the OSI protocol layers and is also available to complement other management information definitions. The management information for OSI protocol layers are expected to be specified in X-Series Recommendations. + +## 5.5 *Management information for modems* + +The management information for V-Series DCEs is under study. + +# 6 **Management information supporting telecommunication network resources** + +The following sections identify and categorize the TNM managed object classes supporting telecom network resources. Unless stated to the contrary, their definitions are found in Recommendation M.3 100 [4]. + +*Note* – The need for a Service Fragment is for further study. + +## 6.1 *Network fragment* + +Network + +## 6.2 *Managed element fragment* + +Equipment + +Managed Element + +Software + +The following managed object class is specified in Recommendation G. 774 [6]: + +SDH Network Element + +## 6.3 *Termination point fragment* + +Connection Termination Point Bidirectional + +Connection Termination Point Sink + +Connection Termination Point Source + +Termination Point + +Trail Termination Point Bidirectional + +Trail Termination Point Sink + +Trail Termination Point Source + +The following managed object classes are specified in Recommendation G. 774 [6]: + +Administrative Unit 3 Connection Termination Point Bidirectional + +Administrative Unit 3 Connection Termination Point Sink + +Administrative Unit 3 Connection Termination Point Source + +Administrative Unit 4 Connection Termination Point Bidirectional + +Administrative Unit 4 Connection Termination Point Sink + +Administrative Unit 4 Connection Termination Point Source + +Administrative Unit Group Bidirectional +Administrative Unit Group Sink +Administrative Unit Group Source +Electrical SPI Trail Termination Point Bidirectional +Electrical SPI Trail Termination Point Sink +Electrical SPI Trail Termination Point Source +Indirect Adaptor Bidirectional +Indirect Adaptor Sink +Indirect Adaptor Source +Multiplex Section Connection Termination Point Bidirectional +Multiplex Section Connection Termination Point Sink +Multiplex Section Connection Termination Point Source +Multiplex Section Data Communications Channel Connection Termination Point Bidirectional +Multiplex Section Data Communications Channel Connection Termination Point Sink +Multiplex Section Data Communications Channel Connection Termination Point Source +Multiplex Section Orderwire Connection Termination Point Bidirectional +Multiplex Section Orderwire Connection Termination Point Sink +Multiplex Section Orderwire Connection Termination Point Source +Multiplex Section Trail Termination Point Bidirectional +Multiplex Section Trail Termination Point Sink +Multiplex Section Trail Termination Point Source +Optical SDH Physical Interface Trail Termination Point Bidirectional +Optical SDH Physical Interface Trail Termination Point Sink +Optical SDH Physical Interface Trail Termination Point Source +Regenerator Section Connection Termination Point Bidirectional +Regenerator Section Connection Termination Point Sink +Regenerator Section Connection Termination Point Source +Regenerator Section Data Communications Channel Connection Termination Point Bidirectional +Regenerator Section Data Communications Channel Connection Termination Point Sink +Regenerator Section Data Communications Channel Connection Termination Point Source +Regenerator Section Orderwire Connection Termination Point Bidirectional +Regenerator Section Orderwire Connection Termination Point Sink +Regenerator Section Orderwire Connection Termination Point Source +Regenerator Section Trail Termination Point Bidirectional + +Regenerator Section Trail Termination Point Sink +Regenerator Section Trail Termination Point Source +Regenerator Section User Channel Connection Termination Point Bidirectional +Regenerator Section User Channel Connection Termination Point Sink +Regenerator Section User Channel Connection Termination Point Source +Tributary Unit 2 Connection Termination Point Bidirectional +Tributary Unit 2 Connection Termination Point Sink +Tributary Unit 2 Connection Termination Point Source +Tributary Unit 3 Connection Termination Point Bidirectional +Tributary Unit 3 Connection Termination Point Sink +Tributary Unit 3 Connection Termination Point Source +Tributary Unit 11 Connection Termination Point Bidirectional +Tributary Unit 11 Connection Termination Point Sink +Tributary Unit 11 Connection Termination Point Source +Tributary Unit 12 Connection Termination Point Bidirectional +Tributary Unit 12 Connection Termination Point Sink +Tributary Unit 12 Connection Termination Point Source +Tributary Unit Group 2 Bidirectional +Tributary Unit Group 2 Sink +Tributary Unit Group 2 Source +Tributary Unit Group 3 Bidirectional +Tributary Unit Group 3 Sink +Tributary Unit Group 3 Source +VC-n User Channel Connection Termination Point Bidirectional +VC-n User Channel Connection Termination Point Sink +VC-n User Channel Connection Termination Point Source +Virtual Container 2 Trail Termination Point Bidirectional +Virtual Container 2 Trail Termination Point Sink +Virtual Container 2 Trail Termination Point Source +Virtual Container 3 Trail Termination Point Bidirectional +Virtual Container 3 Trail Termination Point Sink +Virtual Container 3 Trail Termination Point Source +Virtual Container 4 Trail Termination Point Bidirectional + +Virtual Container 4 Trail Termination Point Sink +Virtual Container 4 Trail Termination Point Source +Virtual Container 11 Trail Termination Point Bidirectional +Virtual Container 11 Trail Termination Point Sink +Virtual Container 11 Trail Termination Point Source +Virtual Container 12 Trail Termination Point Bidirectional +Virtual Container 12 Trail Termination Point Source +Virtual Container 12 Trail Termination Point Sink + +## 6.4 *Transmission fragment* + +Connection +Connectivity +Trail + +## 6.5 *Cross-connection fragment* + +Cross-connection +Fabric +Group Termination Point +Multipoint Cross-connection +Named Cross-connection +Named Multipoint Cross-connection +Termination Point Pool + +# 7 **Management information supporting protocol machine resources** + +The following sections identify the managed object classes supporting protocol machine resources. + +## 7.1 *OSI Protocols* + +## 7.2 *ISDN Protocols* + +## 7.3 *SS7 Protocols* + +# 8 **Management information supporting functional areas** + +The following sections identify managed object classes supporting the TMN functional areas defined in Recommendation M.3400 [8]. Managed object classes common to these functional areas are also identified. These managed objects are also called management support objects. + +- 8.1 *Common* + The following management support objects are specified in Recommendation X.721 [7]: + Discriminator + Event Forwarding Discriminator + Event Log Record + Log + Log Record + Top +- 8.2 *Fault management* +- 8.2.1 *Alarm surveillance* + The following management support object is specified in Recommendation X.721[7]: + Alarm Record + The following management support objects are specified in Recommendation Q.821 [9]: + Current Alarm Summary Control + Management Operations Schedule +- 8.3 *Performance management* +- 8.4 *Configuration management* +- 8.4.1 *Object management* + The following management support objects are specified in Recommendation X.721 [7]: + Attribute Value Change Record + Object Creation Record + Object Deletion Record + State Change Record +- 8.5 *Accounting management* +- 8.6 *Security management* + +# ANNEX A (to Recommendation M.3180) + +## **Alphabetical Index of Management Information** + +| Managed Object Classes | Section | +|------------------------------------------------------------------|----------------| +| Administrative Unit 3 Connection Termination Point Bidirectional | 6.3 | +| Administrative Unit 3 Connection Termination Point Sink | 6.3 | +| Administrative Unit 3 Connection Termination Point Source | 6.3 | +| Administrative Unit 4 Connection Termination Point Bidirectional | 6.3 | +| Administrative Unit 4 Connection Termination Point Sink | 6.3 | +| Administrative Unit 4 Connection Termination Point Source | 6.3 | + +| | | +|------------------------------------------------------------------------------------------|-------| +| Administrative Unit Group Bidirectional | 6.3 | +| Administrative Unit Group Sink | 6.3 | +| Administrative Unit Group Source | 6.3 | +| Alarm Record | 8.2.1 | +| Attribute Value Change Record | 8.4.1 | +| Connection | 6.4 | +| Connection Termination Point | 6.3 | +| Cross-connection | 6.5 | +| Current Alarm Summary Control | 8.2.1 | +| Discriminator | 8.1 | +| Electrical SPI Trail Termination Point Bidirectional | 6.3 | +| Electrical SPI Trail Termination Point Sink | 6.3 | +| Electrical SPI Trail Termination Point Source | 6.3 | +| Equipment | 6.2 | +| Event Forwarding Discriminator | 8.1 | +| Event Log Record | 8.1 | +| Fabric | 6.5 | +| Group Termination Point | 6.5 | +| Indirect Adaptor Bidirectional | 6.3 | +| Indirect Adaptor Sink | 6.3 | +| Indirect Adaptor Source | 6.3 | +| Log | 8.1 | +| Log Record | 8.1 | +| Managed Element | 6.2 | +| Management Operations Schedule | 8.2.1 | +| Multiplex Section Connection Termination Point Bidirectional | 6.3 | +| Multiplex Section Connection Termination Point Sink | 6.3 | +| Multiplex Section Connection Termination Point Source | 6.3 | +| Multiplex Section Data Communications Channel Connection Termination Point Bidirectional | 6.3 | +| Multiplex Section Data Communications Channel Connection Termination Point Sink | 6.3 | +| Multiplex Section Data Communications Channel Connection Termination Point Source | 6.3 | +| Multiplex Section Orderwire Connection Termination Point Bidirectional | 6.3 | +| Multiplex Section Orderwire Connection Termination Point Sink | 6.3 | +| Multiplex Section Orderwire Connection Termination Point Source | 6.3 | +| Multiplex Section Trail Termination Point Bidirectional | 6.3 | + +| | | +|--------------------------------------------------------------------------------------------|-------| +| Multiplex Section Trail Termination Point Sink | 6.3 | +| Multiplex Section Trail Termination Point Source | 6.3 | +| Multipoint Cross-connection | 6.5 | +| Named Cross-connection | 6.5 | +| Named Multipoint Cross-connection | 6.5 | +| Network | 6.1 | +| Object Creation Record | 8.4.1 | +| Object Deletion Record | 8.4.1 | +| Optical SDH Physical Interface Trail Termination Point Bidirectional | 6.3 | +| Optical SDH Physical Interface Trail Termination Point Sink | 6.3 | +| Optical SDH Physical Interface Trail Termination Point Source | 6.3 | +| Regenerator Section Connection Termination Point Bidirectional | 6.3 | +| Regenerator Section Connection Termination Point Sink | 6.3 | +| Regenerator Section Connection Termination Point Source | 6.3 | +| Regenerator Section Data Communications Channel Connection Termination Point Bidirectional | 6.3 | +| Regenerator Section Data Communications Channel Connection Termination Point Sink | 6.3 | +| Regenerator Section Data Communications Channel Connection Termination Point Source | 6.3 | +| Regenerator Section Orderwire Connection Termination Point Bidirectional | 6.3 | +| Regenerator Section Orderwire Connection Termination Point Sink | 6.3 | +| Regenerator Section Orderwire Connection Termination Point Source | 6.3 | +| Regenerator Section Trail Termination Point Bidirectional | 6.3 | +| Regenerator Section Trail Termination Point Sink | 6.3 | +| Regenerator Section Trail Termination Point Source | 6.3 | +| Regenerator Section User Channel Connection Termination Point Bidirectional | 6.3 | +| Regenerator Section User Channel Connection Termination Point Sink | 6.3 | +| Termination Point Source Software | 6.2 | +| State Change Record | 8.4.1 | +| Termination Point | 6.3 | +| Termination Point Pool | 6.5 | +| Top | 8.1 | +| Trail | 6.4 | +| Trail Termination Point | 6.3 | +| Tributary Unit 11 Connection Termination Point Bidirectional | 6.3 | +| Tributary Unit 11 Connection Termination Point Sink | 6.3 | + +| | | +|--------------------------------------------------------------|-----| +| Tributary Unit 11 Connection Termination Point Source | 6.3 | +| Tributary Unit 12 Connection Termination Point Bidirectional | 6.3 | +| Tributary Unit 12 Connection Termination Point Sink | 6.3 | +| Tributary Unit 12 Connection Termination Point Source | 6.3 | +| Tributary Unit 2 Connection Termination Point Bidirectional | 6.3 | +| Tributary Unit 2 Connection Termination Point Sink | 6.3 | +| Tributary Unit 2 Connection Termination Point Source | 6.3 | +| Tributary Unit 3 Connection Termination Point Bidirectional | 6.3 | +| Tributary Unit 3 Connection Termination Point Sink | 6.3 | +| Tributary Unit 3 Connection Termination Point Source | 6.3 | +| Tributary Unit Group 2 Bidirectional | 6.3 | +| Tributary Unit Group 2 Sink | 6.3 | +| Tributary Unit Group 2 Source | 6.3 | +| Tributary Unit Group 3 Bidirectional | 6.3 | +| Tributary Unit Group 3 Sink | 6.3 | +| Tributary Unit Group 3 Source | 6.3 | +| VC-n User Channel Connection Termination Point Bidirectional | 6.3 | +| VC-n User Channel Connection Termination Point Sink | 6.3 | +| VC-n User Channel Connection Termination Point Source | 6.3 | +| Regenerator Section User Channel Connection | 6.3 | +| Virtual Container 11 Trail Termination Point Bidirectional | 6.3 | +| Virtual Container 11 Trail Termination Point Sink | 6.3 | +| Virtual Container 11 Trail Termination Point Source | 6.3 | +| Virtual Container 12 Trail Termination Point Bidirectional | 6.3 | +| Virtual Container 12 Trail Termination Point Source | 6.3 | +| Virtual Container 12 Trail Termination Point Sink | 6.3 | +| Virtual Container 2 Trail Termination Point Bidirectional | 6.3 | +| Virtual Container 2 Trail Termination Point Sink | 6.3 | +| Virtual Container 2 Trail Termination Point Source | 6.3 | +| Virtual Container 3 Trail Termination Point Bidirectional | 6.3 | +| Virtual Container 3 Trail Termination Point Sink | 6.3 | +| Virtual Container 3 Trail Termination Point Source | 6.3 | +| Virtual Container 4 Trail Termination Point Bidirectional | 6.3 | +| Virtual Container 4 Trail Termination Point Sink | 6.3 | +| Virtual Container 4 Trail Termination Point Source | 6.3 | + +## **Inheritance Relationships** + +This annex identifies within brackets [ ] the *immediate* superclasses of the managed object classes identified in §§ 6, 7, and 8. For example, the entry “Trail Termination Point [termination point]” indicates that “Termination Point” is the superclass for the “Trail Termination Point” managed object class. Where more than one superclass is included within the bracket multiple inheritance is indicated. For example, the entry “Administrative Unit 3 Connection Termination Point Bidirectional [connection termination point bidirectional, administrative unit 3 connection termination point sink, administrative unit 3 connection termination point source]” indicates that “Connection Termination Point Bidirectional”, “Administrative Unit 3 Connection Termination Point Sink”, and “Administrative Unit 3 Connection Termination Point Source” are superclasses for the “Administrative Unit 3 Connection Termination Point Bidirectional” managed object class. + +## *Managed Object Class [superclass]* + +Administrative Unit 3 Connection Termination Point Bidirectional [connection termination point bidirectional, administrative unit 3 connection termination point sink, *administrative unit 3 connection termination point source*] + +Administrative Unit 3 Connection Termination Point Sink [connection termination point sink] + +Administrative Unit 3 Connection Termination Point Source [connection termination point source] + +Administrative Unit 4 Connection Termination Point Bidirectional [connection termination point bidirectional, administrative unit 3 connection termination point sink, *administrative unit 3 connection termination point source*] + +Administrative Unit 4 Connection Termination Point Sink [connection termination point sink] + +Administrative Unit 4 Connection Termination Point Source [connection termination point source] + +Administrative Unit Group Bidirectional [indirect adaptor bidirectional, administrative unit group sink, *administrative unit group source*] + +Administrative Unit Group Sink [indirect adaptor sink] + +Administrative Unit Group Source [indirect adaptor source] + +Alarm Record [event log record] + +Attribute Value Change Record [event log record] + +Connection [connectivity] + +Connection Termination Point Bidirectional [connection termination point source *connection termination point sink*] + +Connection Termination Point Sink [termination point] + +Connection Termination Point Source [termination point] + +Connectivity [top] + +Cross-connection [top] + +Current Alarm Summary Control [top] + +Discriminator [top] + +Electrical SPI Trail Termination Point Bidirectional [trail termination point bidirectional, electrical spi trail termination point sink, *electrical spi trail termination point* source] + +Electrical SPI Trail Termination Point Sink [trail termination point sink] + +Electrical SPI Trail Termination Point Source [trail termination point source] + +Equipment [top] + +Event Forwarding Discriminator [discriminator] + +Event Log Record [log record] + +Fabric [top] + +Group Termination Point [top] + +Indirect Adaptor Bidirectional [indirect adaptor sink, *indirect adaptor* source] + +Indirect Adaptor Sink [top] + +Indirect Adaptor Source [top] + +Log [top] + +Log Record [top] + +Managed Element [top] + +Management Operations Schedule [top] + +Multiplex Section Connection Termination Point Bidirectional [connection termination point bidirectional, multiplex section connection termination point sink, multiplex section connection termination point source] + +Multiplex Section Connection Termination Point Sink [connection termination point sink] + +Multiplex Section Connection Termination Point Source [connection termination point source] + +Multiplex Section Data Communications Channel Connection Termination Point Bidirectional [connection termination point bidirectional, multiplex section data communications channel connection termination point sink, *multiplex section data communications channel connection termination point* source] + +Multiplex Section Data Communications Channel Connection Termination Point Sink [connection termination point sink] + +Multiplex Section Data Communications Channel Connection Termination Point Source [connection termination point source] + +Multiplex Section Orderwire Connection Termination Point Bidirectional [connection termination point bidirectional, multiplex section orderwire connection termination point sink, *multiplex section orderwire connection termination point* source] + +Multiplex Section Orderwire Connection Termination Point Sink [connection termination point sink] + +Multiplex Section Orderwire Connection Termination Point Source [connection termination point source] + +Multiplex Section Trail Termination Point Bidirectional [trail termination point bidirectional, multiplex section trail termination point sink, *multiplex section trail termination point source*] + +Multiplex Section Trail Termination Point Sink [trail termination point sink] + +Multiplex Section Trail Termination Point Source [trail termination point source] + +Multipoint Cross-connection [top] + +Named Cross-connection [cross-connection] + +Named Multipoint Cross-connection [multipoint cross-connection] + +Network [top] + +Object Creation Record [event log record] + +Object Deletion Record [event log record] + +Optical SDH Physical Interface Trail Termination Point Bidirectional [trail termination point bidirectional, optical SDH physical interface trail termination point sink, *optical SDH physical interface trail termination point source*] + +Optical SDH Physical Interface Trail Termination Point Sink [trail termination point sink] + +Optical SDH Physical Interface Trail Termination Point Source [trail termination point source] + +Regenerator Section Connection Termination Point Bidirectional [connection termination point bidirectional, regenerator section connection termination point sink, *regenerator section connection termination point source*] + +Regenerator Section Connection Termination Point Sink [connection termination point sink] + +Regenerator Section Connection Termination Point Source [connection termination point source] + +Regenerator Section Data Communications Channel Connection Termination Point Bidirectional [connection termination point bidirectional, regenerator section data communication channel sink, *regenerator section data communication channel source*] + +Regenerator Section Data Communications Channel Connection Termination Point Sink [connection termination point sink] + +Regenerator Section Data Communications Channel Connection Termination Point Source [connection termination point source] + +Regenerator Section Orderwire Connection Termination Point Bidirectional [connection termination point bidirectional, regenerator section orderwire connection termination point sink, *regenerator section orderwire connection termination point source*] + +Regenerator Section Orderwire Connection Termination Point Sink [connection termination point sink] + +Regenerator Section Orderwire Connection Termination Point Source [connection termination point source] + +Regenerator Section Trail Termination Point Bidirectional [trail termination point bidirectional, regenerator section trail termination point sink, *regenerator section trail termination point source*] + +Regenerator Section Trail Termination Point Sink [trail termination point sink] + +Regenerator Section Trail Termination Point Source [trail termination point source] + +Regenerator Section User Channel Connection Termination Point Bidirectional [connection termination point bidirectional, regenerator section user channel connection termination point sink, *regenerator section user channel connection termination point source*] + +Regenerator Section User Channel Connection Termination Point Sink [connection termination point sink] + +Regenerator Section User Channel Connection Termination Point Source [connection termination point source] + +SDH Network Element [managed element] + +Software [top] + +State Change Record [event log record] + +Termination Point [top] + +Termination Point Pool [top] + +Top + +Trail [connectivity] + +Trail Termination Point Bidirectional [trail termination point source, *trail termination point sink*] + +Trail Termination Point Sink [termination point] + +Trail Termination Point Source [termination point] + +Tributary Unit 2 Connection Termination Point Bidirectional [connection termination point bidirectional, Tributary unit 2 connection termination point sink, *tributary unit 2 connection termination point source*] + +Tributary Unit 2 Connection Termination Point Sink [connection termination point sink] + +Tributary Unit 2 Connection Termination Point Source [connection termination point source] + +Tributary Unit 3 Connection Termination Point Bidirectional [connection termination point bidirectional, tributary unit 3 connection termination point sink , *tributary unit 3 connection termination point source*] + +Tributary Unit 3 Connection Termination Point Sink [connection termination point sink] + +Tributary Unit 3 Connection Termination Point Source [connection termination point source] + +Tributary Unit 11 Connection Termination Point Bidirectional [connection termination point bidirectional, tributary unit 11 connection termination point sink, *tributary unit 11 connection termination point source*] + +Tributary Unit 11 Connection Termination Point Sink [connection termination point sink] + +Tributary Unit 11 Connection Termination Point Source [connection termination point source] + +Tributary Unit 12 Connection Termination Point Bidirectional [connection termination point bidirectional, tributary unit 12 connection termination point sink, *tributary unit 12 connection termination point source*] + +Tributary Unit 12 Connection Termination Point Sink [connection termination point sink] + +Tributary Unit 12 Connection Termination Point Source [connection termination point source] + +Tributary Unit Group 2 Bidirectional [indirect adaptor bidirectional, tributary unit group 2 sink, *tributary unit group 2 source*] + +Tributary Unit Group 2 Sink [indirect adaptor sink] + +Tributary Unit Group 2 Source [indirect adaptor source] + +Tributary Unit Group 3 Bidirectional [indirect adaptor bidirectional, tributary unit group 3 sink, *tributary unit group 3 source*] + +Tributary Unit Group 3 Sink [indirect adaptor sink] + +Tributary Unit Group 3 Source [indirect adaptor source] + +VC-n User Channel Connection Termination Point Bidirectional [connection termination point bidirectional, vc-n user channel connection termination point sink, *vc-n user channel connection termination point source*] + +VC-n User Channel Connection Termination Point Sink [connection termination point sink] + +VC-n User Channel Connection Termination Point Source [connection termination point source] + +Virtual Container 2 Trail Termination Point Bidirectional [trail termination point bidirectional, virtual container 2 trail termination point sink, *virtual container 2 trail termination point source*] + +Virtual Container 2 Trail Termination Point Sink [trail termination point sink] + +Virtual Container 2 Trail Termination Point Source [trail termination point source] + +Virtual Container 3 Trail Termination Point Bidirectional [trail termination point bidirectional, virtual container 3 trail termination point sink, *virtual container 3 trail termination point source*] + +Virtual Container 3 Trail Termination Point Sink [trail termination point sink] + +Virtual Container 3 Trail Termination Point Source [trail termination point source] + +Virtual Container 4 Trail Termination Point Bidirectional [trail termination point bidirectional, virtual container 4 trail termination point sink, *virtual container 4 trail termination point source*] + +Virtual Container 4 Trail Termination Point Sink [trail termination point sink] + +Virtual Container 4 Trail Termination Point Source [trail termination point source] + +Virtual Container 11 Trail Termination Point Bidirectional [trail termination point bidirectional, virtual container 11 trail termination point sink, *virtual container 11 trail termination point source*] + +Virtual Container 11 Trail Termination Point Sink [trail termination point sink] + +Virtual Container 11 Trail Termination Point Source [trail termination point source] + +Virtual Container 12 Trail Termination Point Bidirectional [trail termination point bidirectional, virtual container 12 trail termination point sink, *virtual container 12 trail termination point source*] + +Virtual Container 12 Trail Termination Point Sink [trail termination point sink] + +Virtual Container 12 Trail Termination Point Source [trail termination point source] + +# References + +- [1] CCITT Recommendation M.3010 *Principles for a telecommunication management network.* +- [2] CCITT Recommendation X.722 *Information technology – Open systems interconnection – Structure of management information: guidelines for the definitions of managed objects.* +- [3] CCITT Recommendation X.701 *Information technology – Open systems interconnection – Systems management overview.* +- [4] CCITT Recommendation M.3100 *Generic network information model.* +- [5] CCITT Recommendation Q.810 *Managed Object Library (MOL) for switching and signalling.* +- [6] CCITT Recommendation G.774 *SDH management information model.* +- [7] CCITT Recommendation X.721 *Information technology – Open systems interconnection – Structure of management information: definition of management information.* +- [8] CCITT Recommendation M.3400 *TMN management functions.* +- [9] CCITT Recommendation Q.821 *Stage 2 and stage 3 description for the Q3 interface.* \ No newline at end of file diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e684168b1a4780cacf9da87634d6d8e861e686fd --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaeddeb031b02f1858361aca8a3398795b1c884835810c74d215e8c7691c1be6 +size 14641 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f476d2a2f484b2bc99195cb1cfad6977fe55616 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49724743a959dd4af8c3fe0144a03dd1fbd3f1ee3b1ac72af9ce5c94814fd08d +size 16558 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07df569a29590c8a06580fb4352e2efacd26f953 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae285bf0c27f3379782a1e3f9825c7897687e97f75df857c15f1b9186ed6715a +size 48103 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34895c9f2239b8474264009870c8712ecdb38132 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c3f9ab91caa22cc9b1f234d180704bf5830cabee5393ad0bc400f87346df2e2 +size 15353 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98862edf71ea656d9d9fabc15cd67e087da569ed --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42b34a0cc499ac0a0b2c8b191a3d5fc48e1edcc0e7afe01363015e66a2652efe +size 16793 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd2e71f06db3868eae3dc4ab26e37ec116631572 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7010cbd8decdbd32e6e078c26fc13c32931987f9bb85d707f1ddc79640fa0b80 +size 36955 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2399a08f8ed7f8a0fdc4962dd069b5c13a25c794 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ec36683a1f7a78bc76a50e29f46fc1565052518173d0feb70e305f54afe2840 +size 10495 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c46e960f397aa589070601598871d476fba152ca --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d57db18278e4f2eaec4ea8a212bf64e0825292d52ea6c5a4a658d6b972548af9 +size 9152 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08747375d0179d4fbf24dd314530d1b0ac84dbfc --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c79723fa3bc1f48739166e7d2a9efa11479ec6d1a72227de830f544a1747d5a1 +size 47317 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/8be52e8ae172cee527c14d299d386f3c_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/8be52e8ae172cee527c14d299d386f3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd3b9ebd6a3a614f4d24d502e4eadcfe2d138aae --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/8be52e8ae172cee527c14d299d386f3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e60bf7517acdcb30d30feb993c4fa38ddc501e8009cec6fbb7dadd199ca8f153 +size 11082 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f1fed3631274bc5fdcf8f4b13a93738408aaef1 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:867a3f0c1b83cf9295217d0a54c271576385ec35f29206be06b588cc75583b95 +size 16065 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff9c136bf4bfbf22dc1fce49538bc0e3c8bc690b --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d02aa8a63b228b1fedf9fe3faf3825c5d51b901f53df71c2ea92fa4a35bfcdd6 +size 18355 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff8e4f8d098f729edce8f623a70f60d045a5d1b --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476d9d024e5b0d6e2e301d951579d2b4277d69319e218cfaa53b0f01b072de11 +size 14405 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b721313b51e75e308045f9ed11a4278ba11fc47 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/b2ddf2a678bd20b1b491023eb1db6458_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4156948ee3f7949e768303d75b34291915c746b6b40cf1f8ac55ab6593c5785a +size 16325 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daeccc4713b282e39ab2ef258cbfabb9476e5aa1 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd1b459fcf83dfce4b3ab9b4b83f4cb8091363cf4ffc98bb009f9f106ffabc34 +size 10632 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45355e5cf1f79fe6d178c0f7ed6078153b7fffff --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eed6d3470ae8129aea6ce059a435083ed107deea14430affb6564df1c50e5b55 +size 17451 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fb0cff4fbf1abb17cb810824408b4f0a089de94 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf89aeeca84cf1fb1a2620a2d9b37f29c9d51faf6a92e111d72c9179bb6b3a53 +size 27898 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..809079931c2e02016c49576d0d76fa517d927ad4 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ebd399793adcd52b24bd48333f1fc6e85c675cf9d99a1c068515d9ce1039626 +size 14937 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..967af4a6337c567c2da40753bf40dd1c1deb2ec3 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5081ba3936d32de4b5481ea411493a0e8e74f0e7da0e2b4f4ea241b1e816564f +size 15754 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57e5a546a2d57cf37c256a437aad4430989970fb --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5d848d629838944c2b558c682a09c66f341af3b17a31541e330d610d57f314a +size 92754 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d747855e70bbb44f4d5d2b30588d868e92581a --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/dcb5711d118ae6753b0e12f86eda37db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:351edf1843bc2862d567be9dbeb2100535a335e574e404a0fa5231ca0cd3a143 +size 12612 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d2a453b7565ab21fd44a0f0e3ced42b615d0f7c --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ac9ff9fc747e1cb698edad990ac853a14f5c98d037948b862c2ac928e139f8a +size 43247 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54f0d6d83291bc137f364324f08ccfce729b2d53 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4b6359da06c80f578c3c9f4bf7a78c4d90e8a45d4f7bd2f8b8258b87b9f50a1 +size 7292 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..910eb3dcc512534efe1d353658492fecc21c220d --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64202b42006a379c3cb0941212ba912f8e7fd15ed29fff858bc85611de277793 +size 12576 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90b0bc81513c00ce49f43051b37c1099297fa579 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d353a8f9e0c0b4e38e06bbd7683056bc35d1d13381a0222360859421e5a7269 +size 16471 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3186-202408-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1533f8d223913197fbdad9014c9f83c5307fe085 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c143969ee20007d4743b84e8c8ab0ad9e6d091d42ffd84cbb964df2301ddf32 +size 53639 diff --git a/marked/M/T-REC-M.3186-202408-I_PDF-E/raw.md b/marked/M/T-REC-M.3186-202408-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..106c71393d1357001f37a06a9784018a78fd6a25 --- /dev/null +++ b/marked/M/T-REC-M.3186-202408-I_PDF-E/raw.md @@ -0,0 +1,1716 @@ + + +# Recommendation**ITU-T M.3186 (08/2024)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **Shared information and data model (SID) for network operation cost management** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a white grid pattern, overlaid by the letters 'ITU' in a bold, blue, sans-serif font. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3186 + +## Shared information and data model (SID) for network operation cost management + +## Summary + +Recommendation ITU-T M.3186 provides the "Shared information and data model (SID) for network operation cost management". It covers the following aspects: + +- 1) The overall framework of the SID for network operation cost management. +- 2) The specific definition of information object classes and their attributes in the SID for network operation cost management. +- 3) The definition and description of related properties and relationships between information object classes. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3186 | 2024-08-13 | 2 | 11.1002/1000/16016 | + +## Keywords + +Network operation cost, shared information and data model (SID). + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview ..... | 2 | +| 7 Information model for network operation cost management ..... | 3 | +| 7.1 The top-level classes relationship diagram..... | 3 | +| 7.2 Network operation cost information related entities ..... | 4 | +| 7.3 Resource management information related entities ..... | 5 | +| 7.4 On-site maintenance cost related entities ..... | 5 | +| 7.5 IAT cost related entities..... | 9 | +| 7.6 Spare parts cost related entities ..... | 14 | +| 7.7 Consumable material cost related entities ..... | 19 | +| 7.8 Maintenance support service cost related entities ..... | 23 | +| Bibliography..... | 31 | + + + +## Recommendation ITU-T M.3186 + +## Shared information and data model (SID) for network operation cost management + +# 1 Scope + +This Recommendation builds the shared information and data model (SID) for network operation cost management based on the classification of network operation cost management. The main content includes the definition and description of SID object classes, attributes and the relationship between object classes. + +This Recommendation is applicable to the design, development and application of network operation cost management related systems. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2017), *Management interface specification methodology*. +- [ITU-T M.3164] Recommendation ITU-T M.3164 (2020), *Generic information model for on-site telecommunication smart maintenance*. +- [ITU-T M.3386] Recommendation ITU-T M.3386 (2024), *Requirements for the management of network operation cost within AI enhanced Telecom Operation and Management (AITOM) in telecommunication operational aspects*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 consumable material** [ITU-T M.3386]: All supplies used in the performance of maintenance work that are disposable after use and must be replaced regularly to continue with the performance of maintenance work. + +NOTE – Some typical consumable materials are patch cords, pigtail, connector, registered jack, etc. + +**3.1.2 maintenance support service** [ITU-T M.3386]: Service provided by the original equipment manufacturer or provider to support the operator's maintenance work according to the maintenance contract. + +NOTE – Maintenance support services include technical support in case of operational failures, regular inspection and repairing of the device, etc. + +**3.1.3 network operation cost** [ITU-T M.3386]: Human and other resources spent during operation and maintenance of a network. + +**3.1.4 on-site overhaul** [b-ITU-T M.3040]: A kind of on-demand preventive maintenance performed at a facility site in the condition of natural disasters or major events. + +**3.1.5 on-site patrol** [b-ITU-T M.3040]: A kind of routine preventive maintenance periodically performed at a facility site. + +**3.1.6 on-site troubleshooting** [b-ITU-T M.3040]: A kind of corrective maintenance performed at a facility site when the quality of equipment degrades. + +**3.1.7 spare parts** [ITU-T M.3386]: Extra components or devices prepared in advance for replacing the ones in use according to maintenance work needs. + +NOTE – Some typical consumable materials are patch cords, pigtail, connector, registered jack, etc. + +**3.1.8 telecommunications managed area** [b-ITU-T M.3200]: A set of telecommunications resources, logically and/or physically involved with the telecommunications services, that makes it possible to provide, partly or completely, these services to the customers and is chosen to be managed as a whole. + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +IAT Installation and Acceptance Testing + +ID Identifier + +IOC Information Object Class + +SID Shared Information and Data model + +TMA Telecommunications Managed Area + +# 5 Conventions + +In this Recommendation: + +- For the qualifiers of an operation or a parameter in the analysis template, "M" standards for Mandatory, and "O" standards for Optional. +- Text in the font of Courier New indicates it is an abstract data type as indicated in [ITU-T M.3020] and will be mapped to a protocol-specific data type in the design phase. + +# 6 Overview + +The SID for network operation cost management and the information entities provided in this Recommendation follow the [ITU-T M.3020] interface specification methodology, which refer to the related information object classes (IOCs) defined in [ITU-T M.3164]. + +The classification of network operation costs is mainly composed of telecommunications managed areas (TMAs) and network operation cost expenditure categories as described in [ITU-T M.3386]. The TMAs include fixed broadband network, radio access network, core network, transport network, infrastructure, etc. The network operation cost expenditure categories include on-site patrol, on-site overhaul, on-site trouble shooting, installation and acceptance testing (IAT), spare parts, consumable material, maintenance support service, etc. + +This Recommendation introduces the information entities related to the SID for network operation cost management as shown in Table 1. + +**Table 1 – Information entities in the SID for network operation cost management** + +| Information entity category | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Network operation cost information entities | The information entities about all the network operation cost record information, involved in on-site patrol, on-site overhaul, on-site troubleshooting, IAT, spare parts, consumable material, maintenance support service, etc. | +| Resource management information entities | The information entities about specific network resources. | +| Maintenance labour related information entities:
– On-site maintenance information entities
– Installation and acceptance testing information entities | These information entities are abstraction of the maintenance action information, mainly containing maintenance labour information, involved in on-site patrol work tasks, on-site overhaul work tasks, on-site troubleshooting work tasks, installation and acceptance testing work tasks. | +| Other maintenance action information entities:
– Spare parts usage information entities
– Consumable material usage information entities
– Maintenance support service information entities | These information entities are abstraction of the maintenance information, mainly containing maintenance non-labour information, involved in spare parts usage, consumable material usage and maintenance support service. | +| Maintenance price related entities:
– Maintenance labour price information entities
– Spare parts price information entities
– Consumable material price information entities
– Maintenance support service price information entities | These information entities are maintenance price information corresponding to the maintenance action. | + +# 7 Information model for network operation cost management + +## 7.1 The top-level classes relationship diagram + +![Entity relationship diagram between the top-level IOCs. The diagram shows a central class 'NetworkOperationCostInfo' at the top. Below it are five subclasses: 'OnsiteMaintenanceCostInfo', 'IATCostInfo', 'SparePartsCostInfo', 'ConsumableCostInfo', and 'ServiceCostInfo'. Arrows indicate relationships from the top class to each subclass with specific role names and multiplicities.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +``` + +classDiagram + class NetworkOperationCostInfo { + <> + } + class OnsiteMaintenanceCostInfo { + <> + } + class IATCostInfo { + <> + } + class SparePartsCostInfo { + <> + } + class ConsumableCostInfo { + <> + } + class ServiceCostInfo { + <> + } + + NetworkOperationCostInfo "1" -- "0..1" OnsiteMaintenanceCostInfo : OnsiteMaintenanceCostInfo + NetworkOperationCostInfo "1" -- "0..1" IATCostInfo : +IATCostInfo + NetworkOperationCostInfo "1" -- "0..1" SparePartsCostInfo : +SparePartsCostInfo + NetworkOperationCostInfo "1" -- "0..1" ConsumableCostInfo : +ConsumableCostInfo + NetworkOperationCostInfo "1" -- "0..1" ServiceCostInfo : +ServiceCostInfo + +``` + +M.3186(24) + +Entity relationship diagram between the top-level IOCs. The diagram shows a central class 'NetworkOperationCostInfo' at the top. Below it are five subclasses: 'OnsiteMaintenanceCostInfo', 'IATCostInfo', 'SparePartsCostInfo', 'ConsumableCostInfo', and 'ServiceCostInfo'. Arrows indicate relationships from the top class to each subclass with specific role names and multiplicities. + +**Figure 1 – Entity relationship diagram between the top-level IOCs** + +As shown in Figure 1, the top-level classes of the information model for network operation include NetworkOperationCostInfo, OnsiteMaintenanceCostInfo, IATCostInfo, SparePartsCostInfo, ConsumableCostInfo and ServiceCostInfo, and these top-level classes contain concrete IOCs. + +## 7.2 Network operation cost information related entities + +### 7.2.1 Object class information model and attribute description (NetworkOperationCostInfo) + +#### 7.2.1.1 Network operation cost information model and attribute description + +The information model related to NetworkOperationCostInfo is shown in Figure 2. + +![UML class diagram for NetworkOperationCostInfo. The class name is NetworkOperationCostInfo, and it inherits from InformationObjectClass. The attributes are nOCostInfoID, costExpenditureCategory, tMA, regionID, costUnit, nOCostAmount, and costInfoIDList.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +``` +classDiagram + class NetworkOperationCostInfo { + -nOCostInfoID + -costExpenditureCategory + -tMA + -regionID + -costUnit + -nOCostAmount + -costInfoIDList + } + NetworkOperationCostInfo <|-- InformationObjectClass +``` + +UML class diagram for NetworkOperationCostInfo. The class name is NetworkOperationCostInfo, and it inherits from InformationObjectClass. The attributes are nOCostInfoID, costExpenditureCategory, tMA, regionID, costUnit, nOCostAmount, and costInfoIDList. + +M.3186(24) + +**Figure 2 – Information model related to NetworkOperationCostInfo** + +This Recommendation defines the IOC about network operation cost information as "NetworkOperationCostInfo". NetworkOperationCostInfo is the sum of all subjects of network operation cost, including on-site patrol cost, on-site overhaul cost, on-site troubleshooting cost, installation and acceptance testing cost, spare parts cost, consumable material cost and maintenance support service cost. + +##### 7.2.1.1.1 Definition + +This management entity describes relevant information related to network operation cost management. The detailed individual attributes are listed below: + +- nOCostInfoID: Representing the unique identifier related to network operation cost information. +- costExpenditureCategory: Represents network cost expenditure categories generated by different maintenance action, such as on-site patrol, on-site overhaul, on-site troubleshooting, etc. +- tMA: Represents telecommunications managed areas, such as Fixed broadband network, Radio access network, Core network, etc. +- regionID: Represents the administrative region of the network operation event. +- costUnit: Represents the monetary unit of network operation cost. +- nOCostAmount: Represents the amount of the corresponding network operation costs. +- costInfoIDList: Represents the list of cost information IDs corresponding to the network operation costs, which can be on-site maintenance cost, IAT, spare parts cost, consumable material cost and maintenance support service cost. + +##### 7.2.1.1.2 Attributes + +Table 2 describes the attribute properties related to NetworkOperationCostInfo: + +**Table 2 – Attribute properties related to NetworkOperationCostInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-------------------------|-------------------|----------------|-----------------|---------------------|----------------| +| nOCostInfoID | M | M | – | – | M | +| costExpenditureCategory | M | M | M | O | M | +| tMA | M | M | M | O | M | +| regionID | M | M | M | O | M | +| costUnit | M | M | M | O | M | +| nOCostAmount | M | M | M | O | M | +| costInfoIDList | M | M | M | O | M | + +## 7.3 Resource management information related entities + +Referring to [ITU-T M.3020], this Recommendation defines the top-level class about resource management (ResourceInfo) as a proxy class "ProxyClass", which represents all resource entity classes "InformationObjectClass". The proxy class encapsulates the properties, methods (or notifications) that exist in the entity class it represents, and all its behaviour appears in the entity class it represents. Since the proxy class is just a representation of other classes, this class cannot define its behaviour except for the classes that have been defined by the indicated "InformationObjectClass". So, this Recommendation defines properties and methods of the resource proxy class. The information model related to the top-level class about resource management is shown in Figure 3, where the Note is a comment for the proxy class. + +![UML class diagram showing ResourceInfo as a ProxyClass with a note stating 'It represents all resource entities'.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram shows a class box for **ResourceInfo** with the stereotype **<>**. A dashed line connects the class box to a note box containing the text "It represents all resource entities". Below the diagram is the reference code M.3186(24). + +UML class diagram showing ResourceInfo as a ProxyClass with a note stating 'It represents all resource entities'. + +**Figure 3 – Information model related to ResourceInfo** + +## 7.4 On-site maintenance cost related entities + +### 7.4.1 Entity relationship diagram between object classes + +On-site maintenance cost related entities are based on the on-site patrol, on-site overhaul and on-site troubleshooting related information entities defined in clauses 6.3, 6.4 and 6.5 of [ITU-T M.3164]. The Relationship class diagram between object classes related to on-site maintenance cost is shown in Figure 4. + +![Figure 4: Entity relationship diagram between object classes related to on-site maintenance. The diagram shows MaintenanceLaborPriceInfo (n) related to OnsiteMaintenanceCostInfo (1). OnsiteMaintenanceCostInfo (1) is related to OnsitePatrolTask (n), OnsiteOverhaulTask (n), and OnsiteTroubleShootingTask (n). OnsitePatrolTask, OnsiteOverhaulTask, and OnsiteTroubleShootingTask are all related to ResourceInfo (n). Annotations include 'It represents all resource entities' for ResourceInfo and 'IOCs shown in dotted outline should be IOCs defined in [ITU-T M.3164]' for the three task classes.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +classDiagram + class MaintenanceLaborPriceInfo + class OnsiteMaintenanceCostInfo + class OnsitePatrolTask + class OnsiteOverhaulTask + class OnsiteTroubleShootingTask + class ResourceInfo + + MaintenanceLaborPriceInfo "n" -- "1" OnsiteMaintenanceCostInfo + OnsiteMaintenanceCostInfo "1" -- "n" OnsitePatrolTask : +OnsitePatrolTask + OnsiteMaintenanceCostInfo "1" -- "n" OnsiteOverhaulTask : +OnsiteOverhaulTask + OnsiteMaintenanceCostInfo "1" -- "n" OnsiteTroubleShootingTask : +OnsiteTroubleShootingTask + OnsitePatrolTask "n" -- "n" ResourceInfo : +ResourceInfo + OnsiteOverhaulTask "n" -- "n" ResourceInfo : +ResourceInfo + OnsiteTroubleShootingTask "n" -- "n" ResourceInfo : +ResourceInfo + +``` + +Figure 4: Entity relationship diagram between object classes related to on-site maintenance. The diagram shows MaintenanceLaborPriceInfo (n) related to OnsiteMaintenanceCostInfo (1). OnsiteMaintenanceCostInfo (1) is related to OnsitePatrolTask (n), OnsiteOverhaulTask (n), and OnsiteTroubleShootingTask (n). OnsitePatrolTask, OnsiteOverhaulTask, and OnsiteTroubleShootingTask are all related to ResourceInfo (n). Annotations include 'It represents all resource entities' for ResourceInfo and 'IOCs shown in dotted outline should be IOCs defined in [ITU-T M.3164]' for the three task classes. + +**Figure 4 – Entity relationship diagram between object classes related to on-site maintenance** + +In Figure 4, the IOCs related to on-site maintenance include OnsiteMaintenanceCostInfo, OnsitePatrolTask, OnsiteOverhaulTask, OnsiteTroubleshootingTask, MaintenanceLaborPriceInfo and ResourceInfo. OnsiteMaintenanceCostInfo includes multiple cost related information derived from OnsitePatrolTask, OnsiteOverhaulTask and OnsiteTroubleshootingTask, so that OnsiteMaintenanceCostInfo has the same relationships with OnsitePatrolTask, OnsiteOverhaulTask and OnsiteTroubleShootingTask, which are one-to-many and one-way association relationships. Onsite maintenance activity is related to different types of maintenance labour cost, so that OnsiteMaintenanceCostInfo and MaintenanceLaborPriceInfo are one-to-many and one-way association relationships. + +### 7.4.2 Object class information model and attribute description + +#### 7.4.2.1 IOC related to On-site maintenance cost (OnsiteMaintenanceCostInfo) + +The IOC related to on-site maintenance is shown in Figure 5. + +![Figure 5: Information model related to OnsiteMaintenanceCostInfo. The diagram shows the OnsiteMaintenanceCostInfo class with its attributes: costInfoID, taskIDList, priceIDList, laborHour, deviceType, regionID, costUnit, and costAmount.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +classDiagram + class OnsiteMaintenanceCostInfo { + -costInfoID + -taskIDList + -priceIDList + -laborHour + -deviceType + -regionID + -costUnit + -costAmount + } + +``` + +Figure 5: Information model related to OnsiteMaintenanceCostInfo. The diagram shows the OnsiteMaintenanceCostInfo class with its attributes: costInfoID, taskIDList, priceIDList, laborHour, deviceType, regionID, costUnit, and costAmount. + +**Figure 5 – Information model related to OnsiteMaintenanceCostInfo** + +##### 7.4.2.1.1 Definition + +This management entity describes relevant information related to maintenance activity. The detailed attributes are listed below: + +- costInfoID: Represents the unique identifier related to OnsiteMaintenanceCostInfo. +- taskIDList: Represents the list of on-site maintenance tasks, which can be on-site patrol task, on-site overhaul task and on-site troubleshooting task. +- priceIDList: Represents the list of price information IDs related to on-site maintenance activities. +- laborHour: Represents the effective labour time in the process of patrol, overhaul and troubleshooting activities. +- deviceType: Represents the type of the device involved in the on-site maintenance activity, such as handheld device, headwear device, etc. +- regionID: Represents the administrative region of the network operation event. +- costUnit: Represents monetary unit of on-site maintenance cost. +- costAmount: Represents the total amount of on-site maintenance cost. + +##### 7.4.2.1.2 Attributes + +Table 3 describes the attribute properties related to OnsiteMaintenanceCostInfo: + +**Table 3 – Attribute properties related to OnsiteMaintenanceCostInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| costInfoID | M | M | – | – | M | +| taskIDList | M | M | M | O | M | +| priceIDList | M | M | M | O | M | +| laborHour | M | M | M | O | M | +| deviceType | M | M | M | O | M | +| regionID | M | M | M | O | M | +| costUnit | M | M | M | O | M | +| costAmount | M | M | M | O | M | + +Table 4 shows the specific description of the attributes related to OnsiteMaintenanceCostInfo: + +**Table 4 – Attributes related to OnsiteMaintenanceCostInfo** + +| Attribute Name | Type | Explanation | +|----------------|--------------------|-----------------------------------------------------------------------------------------| +| costInfoID | String | Unique identifier related to OnsiteMaintenanceCostInfo | +| taskIDList | SEQUENCE OF String | List of on-site maintenance tasks | +| priceIDList | SEQUENCE OF String | List of price information IDs related to on-site maintenance activities | +| laborHour | Integer | Effective labour time in the process of patrol, overhaul and troubleshooting activities | +| deviceType | SET OF String | Device related to maintenance activities | +| regionID | String | Unique identifier related to administrative region | + +**Table 4 – Attributes related to OnsiteMaintenanceCostInfo** + +| Attribute Name | Type | Explanation | +|----------------|--------|-------------------------------------------| +| costUnit | String | Monetary unit of on-site maintenance cost | +| costAmount | REAL | Total amount of on-site maintenance cost | + +#### 7.4.2.2 IOC related to maintenance labour price (MaintenanceLaborPriceInfo) + +The IOC related to maintenance labour price is shown in Figure 6. + +![UML class diagram for MaintenanceLaborPriceInfo. The class name is MaintenanceLaborPriceInfo, and it lists attributes: priceID, maintenanceLaborType, maintenanceLaborPriceType, laborTechnicalClass, laborHourPrice, laborHourPriceAdjCoe, maintenanceItemCategory, maintenanceItemPrice, maintenanceItemPriceAdjCoe, and regionID.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +classDiagram + class MaintenanceLaborPriceInfo { + - priceID + - maintenanceLaborType + - maintenanceLaborPriceType + - laborTechnicalClass + - laborHourPrice + - laborHourPriceAdjCoe + - maintenanceItemCategory + - maintenanceItemPrice + - maintenanceItemPriceAdjCoe + - regionID + } + +``` + +M.3186(24) + +UML class diagram for MaintenanceLaborPriceInfo. The class name is MaintenanceLaborPriceInfo, and it lists attributes: priceID, maintenanceLaborType, maintenanceLaborPriceType, laborTechnicalClass, laborHourPrice, laborHourPriceAdjCoe, maintenanceItemCategory, maintenanceItemPrice, maintenanceItemPriceAdjCoe, and regionID. + +**Figure 6 – Information model related to MaintenanceLaborPriceInfo** + +##### 7.4.2.2.1 Definition + +This management entity describes relevant information related to maintenance labour price. The detailed attributes are listed below: + +- priceID: Represents unique identifier related to on-site maintenance activities price. +- maintenanceLaborType: Represents the type of the maintenance activity, including on-site patrol, on-site overhaul, on-site troubleshooting, IAT. +- maintenanceLaborPriceType: Represents the type of the maintenance labour price, including labour hour price (commonly correspond to on-site patrol, on-site overhaul and on-site troubleshooting) and maintenance item price (commonly correspond to IAT). +- laborTechnicalClass: Represents the technical class of the maintenance personnel, including senior technicians, intermediate technicians and general technicians. +- laborHourPrice: Represents the price of the maintenance labour. +- laborHourPriceAdjCoe: Represents the price adjustment coefficient of the maintenance labour in different region. +- maintenanceItemCategory: Represents the categories of the maintenance item, different item with different prices, such as home broadband installation, enterprise broadband installation etc. +- maintenanceItemPrice: Represents the price of the maintenance item. +- maintenanceItemPriceAdjCoe: Represents the price adjustment coefficient of the maintenance item in different regions. +- regionID: Represents the administrative region of the network operation event. + +##### 7.4.2.2.2 Attributes + +Table 5 describes the attribute properties related to MaintenanceLaborPriceInfo: + +**Table 5 – Attribute properties related to MaintenanceLaborPriceInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------------------|-------------------|----------------|-----------------|---------------------|----------------| +| priceID | M | M | – | – | M | +| maintenanceLaborType | M | M | M | O | M | +| maintenanceLaborPriceType | M | M | M | O | M | +| laborTechnicalClass | M | M | M | O | M | +| laborHourPrice | M | M | M | O | M | +| laborHourPriceAdjCoe | M | M | M | O | M | +| maintenanceItemCategory | M | M | M | O | M | +| maintenanceItemPrice | M | M | M | O | M | +| maintenanceItemPriceAdjCoe | M | M | M | O | M | +| regionID | M | M | M | O | M | + +Table 6 shows the specific description of the attributes related to MaintenanceLaborPriceInfo: + +**Table 6 – Attributes related to MaintenanceLaborPriceInfo** + +| Attribute Name | Type | Explanation | +|----------------------------|--------|--------------------------------------------------------------------------------| +| priceID | String | Unique identifier related to MaintenanceLaborPriceInfo | +| maintenanceLaborType | ENUM | [patrol overhaul troubleshooting IAT] | +| maintenanceLaborPriceType | ENUM | [laborHourPrice maintenanceItemPrice] | +| laborTechnicalClass | String | Technical class of the maintenance personnel | +| laborHourPrice | REAL | Price of the maintenance labour | +| laborHourPriceAdjCoe | REAL | The price adjustment coefficient of the maintenance labour in different region | +| maintenanceItemCategory | String | Categories of the maintenance item | +| maintenanceItemPrice | REAL | Price of the maintenance item | +| maintenanceItemPriceAdjCoe | REAL | Price adjustment coefficient of the maintenance item in different region | +| regionID | String | Unique identifier related to administrative region | + +## 7.5 IAT cost related entities + +### 7.5.1 Entity relationship diagram between object classes + +The relationship class diagram between object classes related to IAT cost is shown in Figure 7. + +![Figure 7: Entity relationship diagram between object classes related to IAT. The diagram shows five classes: IATCostInfo, MaintenanceLaborPriceInfo, ResourceInfo, IATInfo, and IATTask, and IATRecord. IATCostInfo (1) is associated with (n) MaintenanceLaborPriceInfo and (n) IATInfo. IATInfo (1) is associated with (n) IATTask via a 'names' relationship. IATTask (n) is associated with (n) ResourceInfo via a '+ResourceInfo' relationship. IATTask (1) is associated with (n) IATRecord via a 'names' relationship. A note indicates that ResourceInfo represents all resource entities. The diagram is labeled M.3186(24).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +classDiagram + class IATCostInfo + class MaintenanceLaborPriceInfo + class ResourceInfo + class IATInfo + class IATTask + class IATRecord + + IATCostInfo "1" --> "n" MaintenanceLaborPriceInfo + IATCostInfo "1" --> "n" IATInfo + IATInfo "1" --> "n" IATTask : names + IATTask "n" --> "n" ResourceInfo : +ResourceInfo + IATTask "1" --> "n" IATRecord : names + note for ResourceInfo "It represents all resource entities" + +``` + +Figure 7: Entity relationship diagram between object classes related to IAT. The diagram shows five classes: IATCostInfo, MaintenanceLaborPriceInfo, ResourceInfo, IATInfo, and IATTask, and IATRecord. IATCostInfo (1) is associated with (n) MaintenanceLaborPriceInfo and (n) IATInfo. IATInfo (1) is associated with (n) IATTask via a 'names' relationship. IATTask (n) is associated with (n) ResourceInfo via a '+ResourceInfo' relationship. IATTask (1) is associated with (n) IATRecord via a 'names' relationship. A note indicates that ResourceInfo represents all resource entities. The diagram is labeled M.3186(24). + +**Figure 7 – Entity relationship diagram between object classes related to IAT** + +In Figure 7, the IOCs related to IAT cost include IATCostInfo, IATInfo, IATTask, IATRecord and MaintenanceLaborPriceInfo. The object related to IAT activities is one or more resources. The overall cost of IAT activity depends on the effective labour hours and maintenance labour price according to different conditions. On-site maintenance executor will record relevant information when performing IAT activities. Therefore, IATTask and ResourceInfo are many to many and one-way association relationships. IATTask contains a number of IATRecord. + +### 7.5.2 Object class information model and attribute description + +#### 7.5.2.1 IOC related to IAT cost (IATCostInfo) + +The IOC related to IAT task is shown in Figure 8. + +![Figure 8: Information model related to IATCostInfo. The diagram shows the IATCostInfo class with its attributes: costInfoID, laborHour, deviceType, regionID, costUnit, costAmount, and iATInfoIDList. The diagram is labeled M.3186(24).](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +``` + +classDiagram + class IATCostInfo { + -costInfoID + -laborHour + -deviceType + -regionID + -costUnit + -costAmount + -iATInfoIDList + } + +``` + +Figure 8: Information model related to IATCostInfo. The diagram shows the IATCostInfo class with its attributes: costInfoID, laborHour, deviceType, regionID, costUnit, costAmount, and iATInfoIDList. The diagram is labeled M.3186(24). + +**Figure 8 – Information model related to IATCostInfo** + +##### 7.5.2.1.1 Definition + +This management entity describes basic cost information related to class about IAT. The detailed attributes are listed below: + +- costInfoID: Represents the unique identifier related to IATCostInfo. +- laborHour: Represents the effective labour time in the process of IAT activity. +- deviceType: Represents the device type involved in the IAT activity, such as handhold device, headwear device, etc. +- regionID: Represents the administrative region of the IAT activity. +- costUnit: Represents the monetary unit of IAT cost. +- costAmount: Represents the total amount of IAT cost. +- iATInfoIDList: Represents the list of IDs related to IATInfo. + +##### 7.5.2.1.2 Attributes + +Table 7 describes the attribute properties related to IATCostInfo: + +**Table 7 – Attribute properties related to IATCostInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| costInfoID | M | M | – | – | M | +| laborHour | M | M | M | O | – | +| deviceType | M | M | M | O | M | +| regionID | M | M | M | O | M | +| costUnit | M | M | M | O | M | +| costAmount | M | M | M | O | M | +| iATInfoIDList | M | M | M | O | M | + +Table 8 shows the specific description of the attributes related to IATCostInfo: + +**Table 8 – Attributes related to IATCostInfo** + +| Attribute Name | Type | Explanation | +|----------------|---------------|----------------------------------------------------| +| costInfoID | String | Unique identifier related to IATCostInfo | +| laborHour | Integer | Effective labour time in the process of IAT | +| deviceType | SET OF String | The device involved in the IAT activities | +| regionID | String | Unique identifier related to administrative region | +| costUnit | String | Monetary unit of IAT cost | +| costAmount | REAL | Amount of IAT cost | +| iATInfoIDList | String | Identifier related to IATInfo | + +#### 7.5.2.2 IOC related to IAT (IATInfo) + +The IOC related to IATInfo is shown in Figure 9. + +![UML class diagram for IATInfo. The class name is IATInfo, with the stereotype <>. It has two attributes: - iATInfoID and - iATTaskList. The diagram is labeled M.3186(24).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +classDiagram + class IATInfo { + <> + - iATInfoID + - iATTaskList + } + +``` + +UML class diagram for IATInfo. The class name is IATInfo, with the stereotype <>. It has two attributes: - iATInfoID and - iATTaskList. The diagram is labeled M.3186(24). + +**Figure 9 – Information model related to IATInfo** + +##### **7.5.2.2.1 Definition** + +The IATInfo management entity describes basic information related to class about IAT. The detailed attributes are listed below: + +- iATInfoID: Represents the unique identifier related to IATInfo. +- iATTasklist: Represents the task list related to the IAT activity. + +##### **7.5.2.2.2 Attributes** + +Table 9 describes the attribute properties related to IATInfo: + +**Table 9 – Attribute properties related to IATInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| iATInfoID | M | M | – | – | M | +| iATTaskList | M | M | M | O | M | + +#### **7.5.2.3 IOC related to IAT task (IATTask)** + +The IOC related to IAT task is shown in Figure 10. + +![UML class diagram for IATTask. The class name is IATTask, with the stereotype <>. It has six attributes: - taskID, - taskDes, - executeInfo, - recordList, - orderID, and - resourceSet. The diagram is labeled M.3186(24).](e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg) + +``` + +classDiagram + class IATTask { + <> + - taskID + - taskDes + - executeInfo + - recordList + - orderID + - resourceSet + } + +``` + +UML class diagram for IATTask. The class name is IATTask, with the stereotype <>. It has six attributes: - taskID, - taskDes, - executeInfo, - recordList, - orderID, and - resourceSet. The diagram is labeled M.3186(24). + +**Figure 10 – Information model related to IATTask** + +##### **7.5.2.3.1 Definition** + +This managed entity describes basic information related to IAT activity. The detailed attributes are listed below: + +- taskID: Unique identifier related to IATTask. +- taskDes: This attribute records details about IAT activity. +- executeInfo: Document relevant information about execution. +- recordList: Represents information records of the IAT process. + +- orderID: The order is the information related to maintenance task sent from TSMS, including maintenance tasks types, maintenance objects, serial numbers, etc. OrderID represents the serial number of the order about the IAT activity. +- resourceSet: Represents equipment about IAT activity. + +An attribute value change notification shall be emitted when the value of the taskID, the IATDes, the executeInfo, the recordList, the orderID or the resourceSet are changed. + +##### 7.5.2.3.2 Attributes + +Table 10 describes the attribute properties related to IATTask: + +**Table 10 – Attribute properties related to IATTask** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| taskID | M | M | – | – | M | +| taskDes | M | M | M | O | M | +| executeInfo | O | M | M | O | – | +| recordList | M | M | M | O | M | +| orderID | M | M | M | O | M | +| resourceSet | M | M | M | O | M | + +Table 11 shows the specific description of the attributes related to IATTask: + +**Table 11 – Attributes related to IATTask** + +| Attribute Name | Type | Explanation | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| +| taskID | String | Unique identifier related to IATTask activity number | +| taskDes | String | Description of specific contents about IAT | +| executeInfo | SET OF ExecuteInfoType
ExecuteInfoType ::= SET
{executor String,
executionTime GeneralizedTime,
executionResults String} | Including executor, execution time, execution results | +| recordList | SEQUENCE OF String | List of record identifiers for activity execution process | +| orderID | String | Task order number of the source related to IAT | +| resourceSet | SET OF String | Equipment related to IAT | + +#### 7.5.2.4 IOC related to IAT record (IATRecord) + +The IOC related to IATRecord is shown in Figure 11. + +![UML class diagram for IATRecord. The class name is IATRecord, with a stereotype <>. The attributes listed are - recordID, - recordInfo, - submitExecutor, and - submitTime.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +classDiagram + class IATRecord { + <> + -recordID + -recordInfo + -submitExecutor + -submitTime + } + +``` + +UML class diagram for IATRecord. The class name is IATRecord, with a stereotype <>. The attributes listed are - recordID, - recordInfo, - submitExecutor, and - submitTime. + +M.3186(24) + +**Figure 11 – Information model related to IATRecord** + +##### 7.5.2.4.1 Definition + +This management entity describes information about IAT record. The detailed attributes are listed below: + +- recordID: Unique identifier of IAT record. +- recordInfo: This attribute records details about IAT activity. +- submitExecutor: Personnel ID, robot number, etc. for submitting records. +- submitTime: Time of records submission. + +An attribute value change notification shall be emitted when the value of the recordID or the recordInfo is changed. + +##### 7.5.2.4.2 Attributes + +Table 12 describes the attribute properties related to IATRecord: + +**Table 12 – Attribute properties related to IATRecord** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| recordID | M | M | – | – | M | +| recordInfo | M | M | M | O | M | +| submitExecutor | O | M | M | O | – | +| submitTime | O | M | M | O | – | + +Table 13 shows the specific description of the attributes related to IATRecord: + +**Table 13 – Attributes related to IATRecord** + +| Attribute Name | Type | Explanation | +|----------------|----------|---------------------------------------------------------| +| recordID | String | Unique identifier of IAT record | +| recordInfo | String | Specific content about record | +| submitExecutor | String | Personnel ID, robot number, etc. for submitting records | +| submitTime | DateTime | Time of submission about records | + +## 7.6 Spare parts cost related entities + +### 7.6.1 Entity relationship diagram between object classes + +The relationship class diagram between object classes related to spare parts cost is shown in Figure 12. + +![Figure 12: Entity relationship diagram between object classes related to spare parts cost. The diagram shows four classes: SparePartsCostInfo (InformationObjectClass), SparePartsInfo (InformationObjectClass), SparePartsPriceInfo (InformationObjectClass), and ResourceInfo (Proxyclass). SparePartsCostInfo (1) is associated with SparePartsInfo (n) via a relationship labeled '<>'. SparePartsCostInfo (1) is also associated with SparePartsPriceInfo (1). SparePartsInfo (n) is associated with ResourceInfo (n) via a relationship labeled '+ResourceInfo'. A callout box next to ResourceInfo states 'It represents all resource entities'. The diagram is labeled M.3186(24).](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +classDiagram + class SparePartsCostInfo { + <> + } + class SparePartsInfo { + <> + } + class SparePartsPriceInfo { + <> + } + class ResourceInfo { + <> + } + SparePartsCostInfo "1" --> "n" SparePartsInfo : <> + SparePartsCostInfo "1" --> "1" SparePartsPriceInfo + SparePartsInfo "n" --> "n" ResourceInfo : +ResourceInfo + note right of ResourceInfo: It represents all resource entities + +``` + +Figure 12: Entity relationship diagram between object classes related to spare parts cost. The diagram shows four classes: SparePartsCostInfo (InformationObjectClass), SparePartsInfo (InformationObjectClass), SparePartsPriceInfo (InformationObjectClass), and ResourceInfo (Proxyclass). SparePartsCostInfo (1) is associated with SparePartsInfo (n) via a relationship labeled '<>'. SparePartsCostInfo (1) is also associated with SparePartsPriceInfo (1). SparePartsInfo (n) is associated with ResourceInfo (n) via a relationship labeled '+ResourceInfo'. A callout box next to ResourceInfo states 'It represents all resource entities'. The diagram is labeled M.3186(24). + +**Figure 12 – Entity relationship diagram between object classes related to spare parts cost** + +In Figure 12, the IOCs related to spare parts cost include SparePartsCostInfo, SparePartsPriceInfo and SparePartsInfo. The object related to spare parts is a resource. Therefore, SparePartsInfo and ResoureInfo are many-to-many and one-way association relationships. + +### 7.6.2 Object class information model and attribute description + +#### 7.6.2.1 IOC related to spare parts cost (SparePartsCostInfo) + +The IOC related to SparePartsCostInfo is shown in Figure 13. + +![Figure 13: Information model related to SparePartsCostInfo. The diagram shows a single class box for SparePartsCostInfo (InformationObjectClass) with the following attributes: - costInfoID, - sparePartsInfoIDList, - sparePartsPriceID, - quantityInfo, - regionID, - costUnit, and - costAmount. The diagram is labeled M.3186(24).](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` + +classDiagram + class SparePartsCostInfo { + <> + - costInfoID + - sparePartsInfoIDList + - sparePartsPriceID + - quantityInfo + - regionID + - costUnit + - costAmount + } + +``` + +Figure 13: Information model related to SparePartsCostInfo. The diagram shows a single class box for SparePartsCostInfo (InformationObjectClass) with the following attributes: - costInfoID, - sparePartsInfoIDList, - sparePartsPriceID, - quantityInfo, - regionID, - costUnit, and - costAmount. The diagram is labeled M.3186(24). + +**Figure 13 – Information model related to SparePartsCostInfo** + +##### 7.6.2.1.1 Definition + +The SparePartsCostInfo management entity describes basic cost information related to spare parts. + +The detailed attributes are listed below: + +- costInfoID: Represents the unique identifier related to SparePartsCostInfo. +- sparePartsInfoIDList: Represents the list of IDs related to SparePartsInfo. +- sparePartsPriceID: Represents Unique identifier related to SparePartsPriceInfo. +- quantityInfo: Represents quantitative information related to spare parts. +- regionID: Represents the unique identifier related to administrative region. +- costUnit: Represents the monetary unit of spare parts cost. + +– costAmount: Represents the total amount of spare parts cost. + +##### 7.6.2.1.2 Attributes + +Table 14 describes the attribute properties related to SparePartsCostInfo: + +**Table 14 – Attribute properties related to SparePartsCostInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------------|-------------------|----------------|-----------------|---------------------|----------------| +| costInfoID | M | M | – | – | M | +| sparePartsInfoIDList | M | M | M | O | M | +| sparePartsPriceID | M | M | – | – | M | +| quantityInfo | M | M | M | O | M | +| regionID | M | M | M | O | M | +| costUnit | M | M | M | O | M | +| costAmount | M | M | M | O | M | + +Table 15 shows the specific description of the attributes related to SparePartsCostInfo: + +**Table 15 – Attributes related to SparePartsCostInfo** + +| Attribute Name | Type | Explanation | +|----------------------|--------------------|----------------------------------------------------| +| costInfoID | String | Unique identifier related to SparePartsCostInfo | +| sparePartsInfoIDList | SEQUENCE OF String | List of spare parts related information | +| sparePartsPriceID | String | Unique identifier related to SparePartsPriceInfo | +| quantityInfo | SET OF String | Quantitative information related to spare parts | +| regionID | String | Unique identifier related to administrative region | +| costUnit | String | Monetary unit of spare parts cost | +| costAmount | REAL | Amount of spare parts cost | + +#### 7.6.2.2 IOC class related to spare parts (SparePartsInfo) + +The IOC related to SparePartsInfo is shown in Figure 14. + +![UML class diagram for SparePartsInfo. The class name is 'SparePartsInfo' with the stereotype '<>'. The attributes listed are: - sparePartsInfoID, - sparePartsType, - sparePartsDes, - resourceSet, - timeInfo, and - regionID. A dashed line is at the bottom of the class box.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +classDiagram + class SparePartsInfo { + <> + - sparePartsInfoID + - sparePartsType + - sparePartsDes + - resourceSet + - timeInfo + - regionID + } + +``` + +M.3186(24) + +UML class diagram for SparePartsInfo. The class name is 'SparePartsInfo' with the stereotype '<>'. The attributes listed are: - sparePartsInfoID, - sparePartsType, - sparePartsDes, - resourceSet, - timeInfo, and - regionID. A dashed line is at the bottom of the class box. + +**Figure 14 – Information model related to SparePartsInfo** + +##### 7.6.2.2.1 Definition + +The SparePartsInfo management entity describes basic information related to spare parts. The detailed attributes are listed below: + +- sparePartsInfoID: Represents the unique identifier related to SparePartsInfo. +- sparePartsType: Represents the spare parts type, such as malfunctioning, periodic, etc. +- sparePartsDes: Represents the information about spare parts, which includes executor, execution time, execution results. +- resourceSet: Represents specific equipment related to spare parts. +- timeInfo: Represents the valid time and period of replacement for spare parts. +- regionID: Represents the unique identifier related to administrative region. + +##### 7.6.2.2.2 Attributes + +Table 16 describes the attribute properties related to SparePartsInfo: + +**Table 16 – Attribute properties related to SparePartsInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|------------------|-------------------|----------------|-----------------|---------------------|----------------| +| sparePartsInfoID | M | M | – | – | M | +| sparePartsType | M | M | M | O | M | +| sparePartsDes | M | M | M | O | M | +| resourceSet | M | M | M | O | M | +| timeInfo | O | M | M | O | – | +| regionID | M | M | M | O | M | + +Table 17 shows the specific description of the attributes related to SparePartsInfo: + +**Table 17 – Attributes related to SparePartsInfo** + +| Attribute Name | Type | Explanation | +|------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| sparePartsInfoID | String | Unique identifier related to spare parts | +| sparePartsType | ENUM | [malfunctioning periodic other] | +| sparePartsDes | SET OF String SEQUENCE
{executor String;
executionTime DateTime;
executionResults String;} | Including executor, execution time, execution results | +| resourceSet | SET OF String | Equipment related to spare parts | +| timeInfo | SET OF SEQUENCE
{startTime DateTime;
endTime DateTime;
period String} | Including valid time and period of replacement | +| regionID | String | Unique identifier related to administrative region | + +#### 7.6.2.3 IOC related to spare parts price (SparePartsPriceInfo) + +The IOC related to SparePartsPriceInfo is shown in Figure 15. + +![UML Class Diagram for SparePartsPriceInfo](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +classDiagram + class SparePartsPriceInfo { + - sparePartsPriceID + - sparePartsType + - sparePartsName + - sparePartsPrice + - priceAdjCoe + - regionID + } + +``` + +M.3186(24) + +UML Class Diagram for SparePartsPriceInfo + +**Figure 15 – Information model related to SparePartsPriceInfo** + +##### **7.6.2.3.1 Definition** + +The SparePartsPriceInfo management entity describes basic price information related to spare parts. The detailed attributes are listed below: + +- sparePartsPriceID: Represents the unique identifier related to SparePartsPriceInfo. +- sparePartsType: Represents the spare parts type, such as malfunctioning, periodic, etc. +- sparePartsName: Represents the name and specification of spare parts. +- sparePartsPrice: Represents the price of the spare parts. +- priceAdjCoe: Represents price adjustment coefficient of the spare parts in different regions. +- regionID: Represents the unique identifier related to administrative region. + +##### **7.6.2.3.2 Attributes** + +Table 18 describes the attribute properties related to SparePartsPriceInfo: + +**Table 18 – Attribute properties related to SparePartsPriceInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-------------------|-------------------|----------------|-----------------|---------------------|----------------| +| sparePartsPriceID | M | M | – | – | M | +| sparePartsType | M | M | M | O | M | +| sparePartsName | M | M | M | O | M | +| sparePartsPrice | M | M | M | O | M | +| priceAdjCoe | M | M | M | O | M | +| regionID | M | M | M | O | M | + +Table 19 shows the specific description of the attributes related to SparePartsPriceInfo: + +**Table 19 – Attributes related to SparePartsPriceInfo** + +| Attribute Name | Type | Explanation | +|-------------------|--------|---------------------------------------------------------------------| +| sparePartsPriceID | String | Unique identifier related to SparePartsPriceInfo | +| sparePartsType | ENUM | [malfunctioning periodic other] | +| sparePartsName | String | The name and specification of the spare parts | +| sparePartsPrice | REAL | Price of the spare parts | +| priceAdjCoe | REAL | Price adjustment coefficient of the spare parts in different region | +| regionID | String | Unique identifier related to administrative region | + +## 7.7 Consumable material cost related entities + +### 7.7.1 Entity relationship diagram between object classes + +The relationship class diagram between object classes related to consumable material cost is shown in Figure 16. + +![Entity relationship diagram between object classes related to consumable material cost. The diagram shows five classes: ConsumableCostInfo, ConsumableRecord, ConsumableInfo, ConsumablePriceInfo, and ResourceInfo. ConsumableCostInfo has a 1-to-n relationship with ConsumableInfo and a 1-to-1 relationship with ConsumablePriceInfo. ConsumableRecord has an aggregation relationship with ConsumableInfo. ConsumableInfo has a many-to-many relationship with ResourceInfo.](26d664119ad25250780f554633444e54_img.jpg) + +``` +classDiagram + class ConsumableCostInfo { + <> + } + class ConsumableRecord { + <> + } + class ConsumableInfo { + <> + } + class ConsumablePriceInfo { + <> + } + class ResourceInfo { + <> + } + + ConsumableCostInfo "1" --> "n" ConsumableInfo : <> + ConsumableCostInfo "1" --> "1" ConsumablePriceInfo + ConsumableInfo "1" o-- "n" ConsumableRecord : <> + ConsumableInfo "n" --> "n" ResourceInfo : +ResourceInfo + note for ResourceInfo "It represents all resource entities" +``` + +Entity relationship diagram between object classes related to consumable material cost. The diagram shows five classes: ConsumableCostInfo, ConsumableRecord, ConsumableInfo, ConsumablePriceInfo, and ResourceInfo. ConsumableCostInfo has a 1-to-n relationship with ConsumableInfo and a 1-to-1 relationship with ConsumablePriceInfo. ConsumableRecord has an aggregation relationship with ConsumableInfo. ConsumableInfo has a many-to-many relationship with ResourceInfo. + +**Figure 16 – Entity relationship diagram between object classes related to consumable material** + +In Figure 16, the IOCs related to consumable material cost include ConsumableCostInfo, ConsumableInfo, ConsumableRecord and ConsumablePriceInfo. The object related to consumable material is one or more resources. Executor will record relevant information when performing network operation activities. Therefore, ConsumableInfo and ResourceInfo are many-to-many and one-way association. ConsumableInfo contains a number of ConsumableRecord. + +### 7.7.2 Object class information model and attribute description + +#### 7.7.2.1 IOC related to consumable material cost (ConsumableCostInfo) + +The IOC related to consumable material cost is shown in Figure 17. + +![Information model related to ConsumableCostInfo showing its attributes.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +``` +classDiagram + class ConsumableCostInfo { + <> + - costInfoID + - consumableInfoIDList + - consumablePriceID + - quantityInfo + - regionID + - costUnit + - costAmount + } +``` + +Information model related to ConsumableCostInfo showing its attributes. + +**Figure 17 – Information model related to ConsumableCostInfo** + +##### 7.7.2.1.1 Definition + +The ConsumableCostInfo management entity describes basic cost information related to consumable material. The detailed attributes are listed below: + +- costInfoID: Represents the unique identifier related to ConsumableCostInfo. +- consumableInfoIDList: Represents the list of IDs related to ConsumableInfo. +- consumablePriceID: Represents Unique identifier related to ConsumablePriceInfo. +- quantityInfo: Represents quantitative information related consumable material. +- regionID: Represents the unique identifier related to administrative region. +- costUnit: Represents the monetary unit of consumable material cost. +- costAmount: Represents the total amount of consumable material cost. + +##### 7.7.2.1.2 Attributes + +Table 20 describes the attribute properties related to ConsumableCostInfo: + +**Table 20 – Attribute properties related to ConsumableCostInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------------|-------------------|----------------|-----------------|---------------------|----------------| +| costInfoID | M | M | – | – | M | +| consumableInfoIDList | M | M | M | O | M | +| consumablePriceID | M | M | – | – | M | +| quantityInfo | M | M | M | O | – | +| regionID | M | M | M | O | M | +| costUnit | M | M | M | O | M | +| costAmount | M | M | M | O | M | + +Table 21 shows the specific description of the attributes related to ConsumableCostInfo: + +**Table 21 – Attributes related to ConsumableCostInfo** + +| Attribute Name | Type | Explanation | +|----------------------|--------------------|---------------------------------------------------------| +| costInfoID | String | Unique identifier related to ConsumableCostInfo | +| consumableInfoIDList | SEQUENCE OF String | List of consumable material related information | +| consumablePriceID | String | Unique identifier related to ConsumablePriceInfo | +| quantityInfo | SET OF String | Quantitative information related to consumable material | +| regionID | String | Unique identifier related to administrative region | +| costUnit | String | Monetary unit of consumable material cost | +| costAmount | REAL | Total amount of consumable material cost | + +#### 7.7.2.2 IOC related to consumable material (ConsumableInfo) + +The IOC related to consumable material is shown in Figure 18. + +![UML class diagram for ConsumableInfo. The class name is ConsumableInfo, and it inherits from InformationObjectClass. The attributes listed are consumableInfoID, consumableRecordList, consumableType, resourceSet, and regionID. The diagram is labeled M.3186(24).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` + +classDiagram + class ConsumableInfo { + - consumableInfoID + - consumableRecordList + - consumableType + - resourceSet + - regionID + } + ConsumableInfo <|-- InformationObjectClass + +``` + +M.3186(24) + +UML class diagram for ConsumableInfo. The class name is ConsumableInfo, and it inherits from InformationObjectClass. The attributes listed are consumableInfoID, consumableRecordList, consumableType, resourceSet, and regionID. The diagram is labeled M.3186(24). + +**Figure 18 – Information model related to ConsumableInfo** + +##### **7.7.2.2.1 Definition** + +The ConsumableInfo management entity describes basic information related to consumable material. The detailed attributes are listed below: + +- consumableInfoID: Represents the unique identifier related to consumableInfo. +- consumableRecordList: Represents the record list of consumable material. +- consumableType: Represents the type of consumable material, such as patch cords, pigtail, connector, registered jack, etc. +- resourceSet: Represents specific equipment related to consumable material. +- regionID: Represents the unique identifier related to administrative region. + +##### **7.7.2.2.2 Attributes** + +Table 22 describes the attribute properties related to ConsumableInfo: + +**Table 22 – Attribute properties related to ConsumableInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------------|-------------------|----------------|-----------------|---------------------|----------------| +| consumableInfoID | M | M | – | – | M | +| consumableRecordList | M | M | M | O | M | +| consumableType | M | M | M | O | M | +| resourceSet | M | M | M | O | M | +| regionID | M | M | M | O | M | + +Table 23 shows the specific description of the attributes related to ConsumableInfo: + +**Table 23 – Attributes related to ConsumableInfo** + +| Attribute Name | Type | Explanation | +|----------------------|--------------------|------------------------------------------------------------------------------------| +| consumableInfoID | String | Unique identifier related to ConsumableCostInfo | +| consumableRecordList | SEQUENCE OF String | List of records | +| consumableType | String | The consumable type such as patch cords, pigtail, connector, registered jack, etc. | +| resourceSet | SET OF String | Equipment related to consumable materials | +| regionID | String | Unique identifier related to administrative region | + +#### **7.7.2.3 IOC related to consumable material price (ConsumablePriceInfo)** + +The IOC related to consumable material price is shown in Figure 19. + +![UML Class diagram for ConsumablePriceInfo. The class name is ConsumablePriceInfo, and it inherits from InformationObjectClass. The attributes listed are consumablePriceID, consumableType, consumableName, consumablePrice, priceAdjCoe, and regionID. The diagram is labeled M.3186(24).](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +``` + +classDiagram + class ConsumablePriceInfo { + - consumablePriceID + - consumableType + - consumableName + - consumablePrice + - priceAdjCoe + - regionID + } + ConsumablePriceInfo <|-- InformationObjectClass + +``` + +M.3186(24) + +UML Class diagram for ConsumablePriceInfo. The class name is ConsumablePriceInfo, and it inherits from InformationObjectClass. The attributes listed are consumablePriceID, consumableType, consumableName, consumablePrice, priceAdjCoe, and regionID. The diagram is labeled M.3186(24). + +**Figure 19 – Information model related to ConsumablePriceInfo** + +##### **7.7.2.3.1 Definition** + +The ConsumablePriceInfo management entity describes basic price information related to consumable material. The detailed attributes are listed below: + +- consumablePriceID: Represents the unique identifier related to consumablePriceInfo. +- consumableType: Represents the type of consumable material, such as patch cords, pigtail, connector, registered jack, etc. +- consumableName: Represents the name and specification of consumable material. +- consumablePrice: Represents the price of the consumable. +- priceAdjCoe: Represents price adjustment coefficient of the consumable in different regions. +- regionID: Represents the unique identifier related to administrative region. + +##### **7.7.2.3.2 Attributes** + +Table 24 describes the attribute properties related to consumable ConsumablePriceInfo: + +**Table 24 – Attribute properties related to consumable ConsumablePriceInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-------------------|-------------------|----------------|-----------------|---------------------|----------------| +| consumablePriceID | M | M | – | – | M | +| consumableType | M | M | M | O | M | +| consumableName | M | M | M | O | M | +| consumablePrice | M | M | M | O | M | +| priceAdjCoe | M | M | M | O | M | +| regionID | M | M | M | O | M | + +Table 25 shows the specific description of the attributes related to ConsumablePriceInfo: + +**Table 25 – Attributes related to ConsumablePriceInfo** + +| Attribute Name | Type | Explanation | +|-------------------|--------|---------------------------------------------------------------------| +| consumablePriceID | String | Unique identifier related to ConsumablePriceInfo | +| consumableType | String | Type of the consumable material | +| consumableName | String | The name of the consumable material | +| consumablePrice | REAL | Price of the consumable material | +| priceAdjCoe | REAL | Price adjustment coefficient of the consumable in different region. | +| regionID | String | Unique identifier related to administrative region. | + +#### 7.7.2.4 IOC related to record of consumable material (ConsumableRecord) + +The IOC related ConsumableRecord is shown in Figure 20. + +![UML class diagram for ConsumableRecord. The class name is ConsumableRecord, with a stereotype <>. The attributes listed are - recordID, - recordInfo, - submitExecutor, and - submitTime. The diagram is labeled M.3186(24) at the bottom right.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) + +``` +classDiagram + class ConsumableRecord { + -recordID + -recordInfo + -submitExecutor + -submitTime + } + note for ConsumableRecord "<>" +``` + +UML class diagram for ConsumableRecord. The class name is ConsumableRecord, with a stereotype <>. The attributes listed are - recordID, - recordInfo, - submitExecutor, and - submitTime. The diagram is labeled M.3186(24) at the bottom right. + +**Figure 20 – Information model related to ConsumableRecord** + +##### 7.7.2.4.1 Definition + +This management entity describes information about record of consumable material. The detailed attributes are listed below: + +- recordID: Unique identifier of the consumable material record. +- recordInfo: This attribute records consumable material related to network operation. +- submitExecutor: Personnel ID, robot number, etc. of the executor that submits this record. +- submitTime: Time of the record submission. + +An attribute value change shall be emitted when the value of the recordID or the recordInfo is changed. + +##### 7.7.2.4.2 Attributes + +Table 26 describes the attribute properties related to ConsumableRecord: + +**Table 26 – Attribute properties related to ConsumableRecord** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| recordID | M | M | – | – | M | +| recordInfo | M | M | M | O | M | +| submitExecutor | O | M | M | O | – | +| submitTime | O | M | M | O | – | + +Table 27 shows the specific description of the attributes related to ConsumableRecord: + +**Table 27 – Attributes related to ConsumableRecord** + +| Attribute Name | Type | Explanation | +|----------------|----------|---------------------------------------------------------| +| recordID | String | Unique identifier, record of service activation number | +| recordInfo | String | Specific content about record | +| submitExecutor | String | Personnel ID, robot number, etc. for submitting records | +| submitTime | DateTime | Time of submission about records | + +## 7.8 Maintenance support service cost related entities + +### 7.8.1 Entity relationship diagram between object classes + +The relationship class diagram between object classes related to maintenance support service cost is shown in Figure 21. + +![Entity relationship diagram between object classes related to maintenance support service cost. The diagram shows ServiceCostInfo (1) associated with ServiceInfo (n) via +ServiceInfo, ServiceCostInfo (1) associated with ServicePriceInfo (n), ServiceInfo (1) associated with MaintenanceLog (1) via +MaintenanceLog, and MaintenanceLog (1) containing MaintenanceRecord (n) via <>.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` +classDiagram + class ServiceCostInfo + class ServiceInfo + class ServicePriceInfo + class MaintenanceLog + class MaintenanceRecord + + ServiceCostInfo "1" --> "n" ServiceInfo : +ServiceInfo + ServiceCostInfo "1" --> "n" ServicePriceInfo + ServiceInfo "1" --> "1" MaintenanceLog : +MaintenanceLog + MaintenanceLog "1" o--> "n" MaintenanceRecord : <> +``` + +Entity relationship diagram between object classes related to maintenance support service cost. The diagram shows ServiceCostInfo (1) associated with ServiceInfo (n) via +ServiceInfo, ServiceCostInfo (1) associated with ServicePriceInfo (n), ServiceInfo (1) associated with MaintenanceLog (1) via +MaintenanceLog, and MaintenanceLog (1) containing MaintenanceRecord (n) via <>. + +M.3186(24) + +**Figure 21 – Entity relationship diagram between object classes related to maintenance support service cost** + +In Figure 21, the IOCs related to maintenance support service cost include ServiceCostInfo, ServiceInfo, ServicePriceInfo, MaintenanceLog and MaintenanceRecord. Each maintenance support service carried by the original manufacturer is associated with a maintenance log. Each time device is maintained or software is updated, one or more records are added to the log. Therefore, ServiceInfo and MaintenanceLog are one-to-one and one-way association relationships. MaintenanceLog and MaintenanceRecord are one-to-many contain relationships. + +### 7.8.2 Object class information model and attribute description + +#### 7.8.2.1 IOC related to maintenance support service (ServiceCostInfo) + +The IOC related to maintenance support service cost is shown in Figure 22. + +![UML class diagram for ServiceCostInfo. The class name is ServiceCostInfo, and it contains the following attributes: costInfoID, serviceInfoIDList, servicePriceIDList, quantityInfo, regionID, costUnit, and costAmount.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +``` + +classDiagram + class ServiceCostInfo { + -costInfoID + -serviceInfoIDList + -servicePriceIDList + -quantityInfo + -regionID + -costUnit + -costAmount + } + +``` + +UML class diagram for ServiceCostInfo. The class name is ServiceCostInfo, and it contains the following attributes: costInfoID, serviceInfoIDList, servicePriceIDList, quantityInfo, regionID, costUnit, and costAmount. + +M.3186(24) + +**Figure 22 – Information model related to ServiceCostInfo** + +##### **7.8.2.1.1 Definition** + +The ServiceCostInfo management entity describes basic cost information related to maintenance support service. The detailed attributes are listed below: + +- costInfoID: Represents the unique identifier related to ServiceCostInfo. +- serviceInfoIDList: Represents the list of IDs related to ServiceInfo. +- servicePriceIDList: Represents the list of IDs related to ServicePriceInfo. +- quantityInfo: Represents the quantity information of the maintenance support service. +- regionID: Represents the administrative region of the maintenance support service. +- costUnit: Represents the monetary unit of maintenance support service cost. +- costAmount: Represents the total amount of maintenance support cost. + +##### **7.8.2.1.2 Attributes** + +Table 28 describes the attribute properties related to ServiceCostInfo: + +**Table 28 – Attribute properties related to ServiceCostInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|--------------------|-------------------|----------------|-----------------|---------------------|----------------| +| costInfoID | M | M | – | – | M | +| serviceInfoIDList | M | M | M | O | M | +| servicePriceIDList | M | M | M | O | M | +| quantityInfo | M | M | M | O | M | +| regionID | M | M | M | O | M | +| costUnit | M | M | M | O | M | +| costAmount | M | M | M | O | M | + +Table 29 shows the specific description of the attributes related to ServiceCostInfo: + +**Table 29 – Attributes related to ServiceCostInfo** + +| Attribute Name | Type | Explanation | +|------------------------|--------------------|----------------------------------------------------------------------| +| costInfoID | String | Unique identifier related to ServiceCostInfo | +| serviceInfoIDList | SEQUENCE OF String | List of information IDs related to maintenance support service | +| servicePriceInfoIDList | SEQUENCE OF String | List of price information IDs related to maintenance support service | +| quantityInfo | SET OF String | Quantitative information related to maintenance support service | +| regionID | String | Unique identifier related to administrative region | +| costUnit | String | Monetary unit of maintenance support service | +| costAmount | REAL | Amount of maintenance support service cost | + +#### 7.8.2.2 IOC related to maintenance support service (ServiceInfo) + +The information object class related to maintenance support service is shown in Figure 23. + +![UML class diagram for ServiceInfo. The class name 'ServiceInfo' is in a grey box at the top, preceded by '<>'. Below the box is a list of attributes: - serviceInfoID, - serviceType, - serviceClass, - serviceDes, - regionID, - systemOs, - softwareVersion, - currentStatus, - resourceSet, - logID. At the bottom right of the diagram is the text 'M.3186(24)'.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` + +classDiagram + class ServiceInfo { + -serviceInfoID + -serviceType + -serviceClass + -serviceDes + -regionID + -systemOs + -softwareVersion + -currentStatus + -resourceSet + -logID + } + <> ServiceInfo + M.3186(24) + +``` + +UML class diagram for ServiceInfo. The class name 'ServiceInfo' is in a grey box at the top, preceded by '<>'. Below the box is a list of attributes: - serviceInfoID, - serviceType, - serviceClass, - serviceDes, - regionID, - systemOs, - softwareVersion, - currentStatus, - resourceSet, - logID. At the bottom right of the diagram is the text 'M.3186(24)'. + +**Figure 23 – Information model related to ServiceInfo** + +##### 7.8.2.2.1 Definition + +The ServiceInfo management entity describes basic information related to maintenance support service. The detailed attributes are listed below: + +- serviceInfoID: Represents the unique identifier related to serviceInfo. +- serviceType: Represents the type of maintenance support service, such as hardware service, software, etc. +- serviceClass: Represents the class of maintenance support service, such as senior service, intermediate service and general service. +- serviceDes: Represents the specific content of maintenance support service. +- regionID: Represents the unique identifier related to administrative region. +- systemOs: Represents the operating system related to the maintenance support service. +- softwareVersion: Represents the major version number of application involved in the maintenance support service. +- currentStatus: Represents current status of the maintenance support service. +- resourceSet: Represents the equipment involved in the maintenance support service. +- logID: Represents the corresponding log ID of maintenance support service. + +##### 7.8.2.2.2 Attributes + +Table 30 describes the attribute properties related to ServiceInfo: + +**Table 30 – Attribute properties related to ServiceInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-----------------|-------------------|----------------|-----------------|---------------------|----------------| +| serviceInfoID | M | M | – | – | M | +| serviceType | M | M | M | O | M | +| serviceClass | M | M | M | O | M | +| serviceDes | M | M | M | O | M | +| regionID | M | M | M | O | M | +| systemOS | M | M | M | O | M | +| softwareVersion | M | M | M | O | M | +| currentStatus | M | M | M | O | M | +| resourceSet | M | M | M | O | M | +| logID | M | M | M | O | M | + +Table 31 shows the specific description of the attributes related to ServiceInfo: + +**Table 31 – Attributes related to ServiceInfo** + +| Attribute name | Type | Explanation | +|-----------------|---------------|-------------------------------------------------------------------------------------| +| serviceInfoID | String | Unique identifier related to maintenance support service | +| serviceType | ENUM | [software hardware other] | +| serviceClass | String | Class of service | +| serviceDes | SET OF String | The specific content of maintenance support service | +| regionID | String | Address of device | +| systemOS | ENUM | [android ios linux windowMobile other] | +| softwareVersion | String | The major version number of application involved in the maintenance support service | +| currentStatus | ENUM | [unfinished finished] | +| resourceSet | String | The specific equipment involved in the maintenance support service | +| logID | String | Maintenance log ID of maintenance support service | + +#### 7.8.2.3 IOC related to maintenance log of maintenance support service (MaintenanceLog) + +The IOC related to MaintenanceLog is shown in Figure 24. + +![UML class diagram for MaintenanceLog. The class name 'MaintenanceLog' is shown in a box with the stereotype '<>'. Below the class name, the attributes '- logID' and '- recordList' are listed. A dashed line is drawn below the attributes.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +``` + +classDiagram + class MaintenanceLog { + <> + - logID + - recordList + } + +``` + +UML class diagram for MaintenanceLog. The class name 'MaintenanceLog' is shown in a box with the stereotype '<>'. Below the class name, the attributes '- logID' and '- recordList' are listed. A dashed line is drawn below the attributes. + +M.3186(24) + +**Figure 24 – Information model related to MaintenanceLog** + +##### 7.8.2.3.1 Definition + +This managed entity describes information related to the log for maintaining hardware and software. The detailed attributes are listed detailed below. + +- logID: Represents item in log. +- recordList: Represents the record list about maintenance support service. + +An attribute value change notification shall be emitted when the value of logID or the recordList is changed. + +##### 7.8.2.3.2 Attributes + +Table 32 describes the attribute properties related to MaintenanceLog: + +**Table 32 – Attribute properties related to MaintenanceLog** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| logID | M | M | – | – | M | +| recordList | M | M | M | O | M | + +Table 33 shows the specific description of the attributes related to MaintenanceLog: + +**Table 33 – Attributes related to MaintenanceLog** + +| Attribute name | Type | Explanation | +|----------------|--------------------|----------------------------------------------------------| +| logID | String | Unique identifier of the maintenance support service log | +| recordList | SEQUENCE OF String | List of record IDs | + +#### 7.8.2.4 IOC related to maintenance record of maintenance support service (MaintenanceRecord) + +The IOC related to MaintenanceRecord is shown in Figure 25. + +![UML class diagram for MaintenanceRecord. The class name 'MaintenanceRecord' is in a grey box at the top, preceded by '<>'. Below the name, the attributes are listed: - recordID, - recordInfo, - recordTime, and - RecordExecutor. A dashed line separates the top section from the bottom section.](8be52e8ae172cee527c14d299d386f3c_img.jpg) + +``` + +classDiagram + class MaintenanceRecord { + <> + -recordID + -recordInfo + -recordTime + -RecordExecutor + } + +``` + +UML class diagram for MaintenanceRecord. The class name 'MaintenanceRecord' is in a grey box at the top, preceded by '<>'. Below the name, the attributes are listed: - recordID, - recordInfo, - recordTime, and - RecordExecutor. A dashed line separates the top section from the bottom section. + +M.3186(24) + +**Figure 25 – Information model related to MaintenanceRecord** + +##### 7.8.2.4.1 Definition + +This managed entity describes information about the record for maintaining smart devices. The detailed attributes are listed below: + +- recordID: Represents unique identifier of maintenance service record. +- recordInfo: Represents specific record information. +- recordTime: Represents the time of this record. +- recordExecutor: Personnel ID, robot number, etc. for recording. + +##### 7.8.2.4.2 Attributes + +Table 34 describes the attribute properties related to MaintenanceRecord: + +**Table 34 – Attribute properties related to MaintenanceRecord** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|----------------|-------------------|----------------|-----------------|---------------------|----------------| +| recordID | M | M | – | – | M | +| recordInfo | M | M | M | O | M | +| recordTime | O | M | M | O | – | +| recordExecutor | O | M | M | O | – | + +Table 35 shows the specific description of the attributes related to MaintenanceRecord: + +**Table 35 – Attributes related to MaintenanceRecord** + +| Attribute name | Type | Explanation | +|----------------|----------|------------------------------------------------| +| recordID | String | Unique identifier, Maintenance record number | +| recordInfo | String | Recorded specific information | +| recordTime | DateTime | Time of record | +| recordExecutor | String | Personnel ID, robot number, etc. for recording | + +#### 7.8.2.5 IOC related to the price of maintenance support service (ServicePriceInfo) + +The IOC related to maintenance service price is shown in Figure 26. + +![UML class diagram for ServicePriceInfo. The class name is ServicePriceInfo, with a stereotype <>. The attributes listed are: - servicePriceID, - serviceType, - serviceName, - servicePrice, - serviceProvider, - priceAdjCoe, and - regionID. A dashed line is at the bottom of the class box.](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) + +``` + +classDiagram + class ServicePriceInfo { + <> + - servicePriceID + - serviceType + - serviceName + - servicePrice + - serviceProvider + - priceAdjCoe + - regionID + } + +``` + +M.3186(24) + +UML class diagram for ServicePriceInfo. The class name is ServicePriceInfo, with a stereotype <>. The attributes listed are: - servicePriceID, - serviceType, - serviceName, - servicePrice, - serviceProvider, - priceAdjCoe, and - regionID. A dashed line is at the bottom of the class box. + +**Figure 26 – Information model related to ServicePriceInfo** + +##### 7.8.2.5.1 Definition + +The ServicePriceInfo management entity describes basic price information related to maintenance support service. The detailed attributes are listed below: + +- servicePriceID: Represents the unique identifier related to servicePriceInfo. +- serviceType: Represents the type of maintenance support service. +- serviceName: Represents the name of maintenance support service. +- servicePrice: Represents the price of maintenance support service. +- serviceProvider: Represents the provider of maintenance support service. +- priceAdjCoe: Represents price adjustment coefficient of the maintenance support service in different regions. + +– regionID: Represents the unique identifier related to administrative region. + +##### 7.8.2.5.2 Attributes + +Table 36 describes the attribute properties related to ServicePriceInfo: + +**Table 36 – Attribute properties related to ServicePriceInfo** + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Invariant qualifier | Note qualifier | +|-----------------|-------------------|----------------|-----------------|---------------------|----------------| +| servicePriceID | M | M | – | – | M | +| serviceType | M | M | M | O | M | +| serviceName | M | M | M | O | M | +| servicePrice | M | M | M | O | M | +| serviceProvider | M | M | M | O | M | +| priceAdjCoe | M | M | M | O | M | +| regionID | M | M | M | O | M | + +Table 37 shows the specific description of the attributes related to ServicePriceInfo: + +**Table 37 – Attributes related to ServicePriceInfo** + +| Attribute Name | Type | Explanation | +|-----------------|--------|-------------------------------------------------------------------------------------| +| servicePriceID | String | Unique identifier related to ServicePriceInfo | +| serviceType | ENUM | [software hardware other] | +| serviceName | String | The name of maintenance support service | +| servicePrice | REAL | Price of maintenance support service | +| serviceProvider | String | The provider of the maintenance support service | +| priceAdjCoe | REAL | Price adjustment coefficient of the maintenance support service in different region | +| regionID | String | Unique identifier related to administrative region | + +# Bibliography + +- [b-ITU-T M.3040] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. +- [b-ITU-T M.3200] Recommendation ITU-T M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39802a155e64dd9627201afbb8d86295b68431ac --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:777495b3ce401da096a230fe5331d26eea525deddc7d1d421561646fe77edb3c +size 79787 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24b214263bab4142643453a604fb5196f9397e2500c675cde79d53ce5e5d8e +size 3645 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db5be89bee58e928e6f70dfd67d0de0965230f6 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f2bf2bdf45104dd242f36f3e816b58f208dbd78b64bcebea6fa85499ab7e372 +size 238128 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f1d2346ff6766372d1c9b867452582a5c06b330 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57f2dabeaf0c0e67d85aa9b297185a58ef4e93582bbb45904da4f4a3b804beef +size 36792 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8ddf636229a35d12e018a8625836ef802044cf4 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e28bf522eb44ec06b39a927e89aa4ed9d2a66efe080c5519b84a4620d8af1a2 +size 178830 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec576ca8cc33d808f147deaa00ee4569b7c76490 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ded023ec972961ba7d748c7b2824e4fddb6732a71c4c9347849a9543a5eccae5 +size 110006 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8f0fba152b60b1c56500ce94abc145bf310dff9 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a965b0d1798dac9438d990c7d2fa11312ff520bf75b91f4ed5ce38f9c2b65cf +size 50085 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a763ec62e47452a2e8a569d6fa8e3af3fe289b66 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d47eca7e0e2789c417f1b1228fbba9bd979a5307e03e73f3b9652881732eb7f +size 102966 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a25e9cc85c0e60df53d1e90f913a81107319124f --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:942a7cf3b8da383e157fd2034deba8815f28cdfcc8f3c6116ef83f02854a8990 +size 79703 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5577d2e0c27517615446c5f1eb7a423cdb94b22a --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ccc8b986753e26e6fbbc6fce972e9c8fa164c2899e7883682b45c0c7e93f3b7 +size 35948 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ade26b2fe63b527eb551a72bb363f263e39bb7d0 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a2d6e1b00187ad73db0b4349465377470259a89b496828ce3af282aa778dcae +size 21487 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f49db24b7bdfb74909f824967e5ad046028805ca --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dfb0f1dc1a26905ad422afbb17f446e5b8eeab09b6b98b3da2a4cf6277deb0a +size 49990 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ab87a452d847bbb406e00e014ff471bb9591322 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e42436cd136677d2c2121c8ce62eddc875ec8bd075b93039d35ffa17c7a7b85 +size 86430 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..491dc78a3d93237f57c931981058c83b8340b8a5 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb302a7d76df6f9120b1b85f13070a8f3ee91fe94698aac188f8f424e561e38a +size 93067 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f73ae333e4aa9d0be31d43ab21b0da74420ec053 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beb3ea8ba2fb89049f940dec8d083bfaf27b4098ce52a3d040ff8b715f6b2df8 +size 72300 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20414c7efe51fc5a9df3777755ae07c49b9bb54e --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e213669820b351a2f1c8fba0a1229f6f94702fb3f1759de482bcd76d5f300e95 +size 103531 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/M/T-REC-M.3190-200807-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..139d0d0bcfc4524151dcdd278e6ba6f31c3ebfcf --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bb4aa159de822f48e1422c28f71947b4327a37cec339c2402e3a6d9d218519f +size 30497 diff --git a/marked/M/T-REC-M.3190-200807-I_PDF-E/raw.md b/marked/M/T-REC-M.3190-200807-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8708422e071664119831172a51c314ad2b2ba064 --- /dev/null +++ b/marked/M/T-REC-M.3190-200807-I_PDF-E/raw.md @@ -0,0 +1,1262 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3190** + +(07/2008) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Shared information and data model (SID)** + +Recommendation ITU-T M.3190 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T M.3190** + +## **Shared information and data model (SID)** + +## **Summary** + +Recommendation ITU-T M.3190 is an introduction to the TM Forum SID analysis model and a specification through reference of the ITU-T subset of SID (the product and service business entities). The SID analysis model scope covers the information required to implement use cases based on the eTOM processes. The SID analysis model is implementation independent, focusing on what the information is and what its relationships are, not on how these are to be implemented. + +The SID applies primarily to service providers' businesses and engaged stakeholders, e.g., system integrators, independent software vendors and network equipment providers. + +## **Source** + +Recommendation ITU-T M.3190 was approved on 14 July 2008 by ITU-T Study Group 4 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Data model, information model, methodology, TM Forum, UML. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|-------|-------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Conventions ..... | 3 | +| 6 | SID introduction ..... | 3 | +| 6.1 | SID as an information model..... | 3 | +| 6.2 | Document structure ..... | 5 | +| 6.3 | Relationship with other Recommendations..... | 6 | +| 7 | SID Framework ..... | 7 | +| 7.1 | SID framework – Level 1 ABEs ..... | 8 | +| 7.2 | ABE categorization ..... | 9 | +| 8 | Product domain..... | 10 | +| 9 | Service domain ..... | 12 | +| | Appendix I – Analysis patterns used in SID ..... | 16 | +| I.1 | Specification ..... | 16 | +| I.2 | Abstract superclass ..... | 16 | +| I.3 | Composite..... | 18 | +| I.4 | Role entity ..... | 18 | +| I.5 | Temporal state entity ..... | 19 | +| I.6 | Self-relationship ..... | 20 | +| I.7 | Entity specification characteristic/entity characteristic ..... | 21 | +| | Appendix II – SID document structure ..... | 24 | +| | Appendix III – SID use of UML..... | 25 | +| III.1 | UML overview ..... | 25 | +| III.2 | Goals of UML..... | 25 | +| III.3 | Why use UML? ..... | 25 | +| III.4 | UML diagrams..... | 25 | +| III.5 | UML diagram classification – Static, dynamic, and implementation ..... | 26 | +| | Appendix IV – SID and the NGOSS views ..... | 28 | +| IV.1 | SID life cycle..... | 28 | +| IV.2 | SID logical and physical perspective ..... | 30 | +| | Appendix V – Positioning SID to the ITU-T M.1400-series Recommendations ..... | 31 | +| | Bibliography..... | 32 | + + + +## Recommendation ITU-T M.3190 + +## Shared information and data model (SID) + +# 1 Scope + +This Recommendation is an introduction to the TM Forum SID analysis model and a specification through reference of the ITU-T subset of SID. The SID analysis model scope covers all of the information required to implement use cases based on the eTOM processes [ITU-T M.3050.x]; in effect, this means that the SID covers a large proportion of the information needs for a service provider. However, the SID is still being developed and while the documents available today cover a substantial part of a service provider's core information needs, they do not cover all of them. + +The SID analysis model is implementation independent, focusing on *what* the information is and *what* its relationships are, not on *how* these are to be implemented. + +The SID applies primarily to service providers' businesses and engaged stakeholders: system integrators (SI), independent software vendors (ISV) and network equipment providers (NEP). + +Parts of the SID may also apply directly to, or be adaptable to, other non-Telco service provider enterprise businesses. + +The focus of this Recommendation is the product and service business entities. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2007), *Management interface specification methodology*. <> +- [ITU-T M.3050.x] Recommendations ITU-T M.3050.x-series (2007), *Enhanced Telecom Operations Map (eTOM)*. <> +- [ITU-T M.3100] Recommendation ITU-T M.3100 (2005), *Generic network information model*. <> +- [TMF GB922] TM Forum GB922, *Shared Information/Data (SID) Model. Concepts, Principles, and Domains, Release 7.5*. <> +- [TMF GB922A3] TM Forum GB922, *Shared Information/Data (SID) Model. Addendum 3 – Product Business Entity Definitions, Release 7.5*. <> +- [TMF GB922A4SO] TM Forum GB922, *Shared Information/Data (SID) Model. Addendum 4SO – Service Overview Business Entity Definitions, Release 7.5*. <> + +[OMG UML]            OMG, *Unified Modelling Language Specification, Version 1.5.* +<> + +Additional non-normative references can be found in the Bibliography. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 aggregate business entity** [TMF GB922]: An Aggregate Business Entity (ABE) is a well-defined set of information and operations that characterize a highly cohesive, loosely coupled set of business entities. + +**3.1.2 attribute** [TMF GB922]: An attribute is a fact that describes a business entity. + +**3.1.3 business entity** [TMF GB922]: A Business Entity represents something of interest to the business that may be tangible things (such as a Customer), active things (such as a Customer Order), or conceptual things (such as a Customer Account). Business entities are characterized by attributes and participate in relationships with other business entities. Business entity instances typically move through a well-defined life cycle. + +**3.1.4 domain** [TMF GB922]: A Domain is a collection of Aggregate Business Entities associated with a specific management area. Domains that make up the SID Framework are consistent with eTOM level 0 concepts. + +**3.1.5 relationship** [TMF GB922]: A relationship is an association of business interest between two business entities, or between a business entity and itself. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 information model:** An information model for a problem space represents all relevant things, i.e., objects in that problem space along with all of their relevant attributes, and relationships. + +- There may be a number of different relevant viewpoints represented for different purposes. + +An information model is *independent* of implementation, i.e., independent of platform, language, protocol, etc. + +- For example, it does not represent whether it is defined using CORBA IDL or a XML schema. + +Not all things (objects) in the information model will result in implementation forms. + +- For example, an information model view may be specified for the purpose of communication across management interfaces. However, not all things (objects, attributes, relationships) in that model will be visible across a management interface. +- The things to be encoded in an implementation form will be identified in the information model. + +**3.2.2 data model:** A data model is an encoded form of relevant parts of the information model for a *specific* platform, language and/or protocol, i.e., this is an implementation view. + +- A data model adds no problem space specific properties, it only applies encoding and augments the information model with encoding directives. +- The relevant parts to be encoded for a specific application will be identified in the information model. + +A single information model may give rise to one or more data models. + +- Data models are typically designed with respect to the characteristics of the platform, language or protocol. +- For example, an information model may be represented via a data model defined in CORBA IDL and also a data model defined using a XML schema. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|---------------------------------------------------------------------| +| ABE | Aggregate Business Entity | +| CMIP | Common Management Information Protocol | +| eTOM | Enhanced Telecom Operations Map | +| MISM | Management Interface Specification Methodology (see [ITU-T M.3020]) | +| NgOSS | New Generation Operations Systems and Software | +| QoS | Quality of Service | +| SID | Shared Information and Data model | +| SLA | Service Level Agreement | +| UML | Unified Modelling Language | +| VPN | Virtual Private Network | + +# 5 Conventions + +SID is described using UML [OMG UML] as described in Appendix III. + +An analysis pattern describes a problem which occurs over and over again, and describes the core of the solution to that problem. Key analysis patterns that have been applied for the modelling of SID are described in Appendix I. + +# 6 SID introduction + +## 6.1 SID as an information model + +### 6.1.1 What it is + +A common information model will streamline the processes associated with information exchange, both within an enterprise and between the enterprise and its external stakeholders. + +Having a standard information model provides the following benefits: + +- it allows for simplification of information management, by providing a common terminology and reducing unnecessary variation; +- it allows for unification of information both within an enterprise and between enterprises; +- it provides a bridge between the business and information technology groups by providing definitions that are understandable by the business, but are rigorous enough to be used for software development. + +These benefits then enable business benefits relating to cost, quality, timeliness and adaptability of enterprise operations, allowing an enterprise to focus on value creation for their customers. + +An information model should model fundamental concepts and not be affected by minor business environment changes like organization restructures. + +The information model should be an enabler of change (new products, processes and ways of doing business), not a blocker to progress. + +An information model (as opposed to a data model) is an abstraction and only provides a high level view of things of interest to the business. It aids in understanding the scope and breadth of the business, rather than the depth. + +An information model is a way of representing and structuring information that has advantages over other common artifacts, as described in Table 1. + +**Table 1 – Information model comparison to other artifacts** + +| Artefact | Artefact limitations | Information model advantage | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Glossary | Hard to understand how the concepts relate | An information model links concepts together and provides a visual overview. | +| Descriptive document | Often rambling & inconsistent with overlapping terminologies used | An information model is more precise, using the power of UML to ensure that the information is represented in a consistent manner. | +| Database model or source code | Too detailed to get a feel of the big picture. Hard to match to business requirements. Hard to convert from a particular language/platform/environment. | A database model is a solution, but it may not map to your problem. A business is likely to have many database models and these need to be understood against a common view of the business (e.g., for EAI integration, business intelligence, etc.). The SID documents a unifying view: the basis for decisions, not just the results. | + +There are many views as to what an information model is and does. For the SID, the initial work has focused on creating a conceptual or analysis model, (also known as a domain model [b-Patterns-1] [b-Patterns-2] or a semantic model [b-Zachman]). The model is a representation of real world objects in which there is interest from the business. + +An analysis model includes: + +- things in which the business is interested (domain entities); +- how they are related to one another (associations); +- key details about those things which help to define them unambiguously (domain-level attributes). + +An information model is useful: + +- as a starting point for internal modelling work, applications and messages between software components or database schemas; +- to help in defining a common business terminology, e.g., for integration activities; +- to help in business transformation programs; +- to help in understanding business concepts and their relationships; +- as a source of inspiration – for a new view on traditional practices. + +### 6.1.2 What it is not + +An information model – and SID – is not: + +- a database model; +- a definition of how software will be written; +- an implementation of software classes; +- a software API (application programming interface); + +- a set of component messaging definitions. + +The analysis model will, however, provide business definitions that should be a major input to the definition of the above items. + +The SID analysis model is not: + +- a definition of software classes; +- enough to do an implementation on its own; +- a definition of platforms, protocols, software languages or software products to be used for developing software components. + +The SID is not a "magic bullet" but should be seen as a key component of an integrated information architecture (model framework + methodology) within an overall enterprise architecture. + +Other parts of an information architecture are typically: + +- Information policy – Directs information management within a business. +- Communication policy – Information maintenance and publishing standards (model downloads, data glossary/dictionary definitions, interface definitions, data translations, etc.). +- Governance processes – Managing separate component models within the overarching framework principles including interface design; managing data definitions within process design; managing data definition within applications design. + +To achieve maximum business benefits, businesses need to consider how to integrate the use of the SID into their existing processes and procedures, especially those relating to IT definition & development. + +## 6.2 Document structure + +The SID is organized in a number of Addenda. The following documents are normative parts of this Recommendation. + +| Reference | Title | Included aggregate business entities | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| GB922
[TMF GB922] | Business View Concepts, Principles, and Domains describing the organizing structure of the SID Business View shared information/data, the relationship to other TMF deliverables, and views of the contents of the model. | | +| GB922 Addendum 3
[TMF GB922A3] | Product | Product Specification, Product Offering, Product, Product Offering Price | +| GB922 Addendum 4SO
[TMF GB922A4SO] | Service | Service Specification, Service | + +NOTE – Only the service and product ABEs [TMF GB922A3] [TMF GB922A4SO] are normatively referenced by this Recommendation. The complete set of ABEs can be found in Appendix II. + +The SID Addenda use a mixture of descriptive text, UML diagrams and tables which formally define the entities and attributes. This provides concise and precise definitions with background reasoning and explanations. + +## 6.3 Relationship with other Recommendations + +### 6.3.1 Relationship with [ITU-T M.3020] + +The management interface specification methodology (MISM) defined by [ITU-T M.3020] specifies a three-phase process with features that allow traceability across the three phases. The three phases apply industry-accepted techniques using object-oriented analysis and design principles. The three phases are requirements, analysis and design. + +The requirements and analysis phases produce UML specifications. The design phase uses network management paradigm specific notation. The outputs of the 3 phases are: + +- Requirements phase – Requirements. +- Analysis phase – Implementation-independent specification. +- Design phase – Technology-specific specification. + +The SID as a conceptual model is an implementation-independent specification. Given the historic background, the SID has not been developed based on the methodology of [ITU-T M.3020], but the result maps well to the outcome of the analysis phase. A distinction between the SID and [ITU-T M.3020] is that the SID is limited to the conceptual information model and without the interface (operations and notifications) aspects also covered by [ITU-T M.3020]. However, SID can be used as an input to the specification of concrete interfaces based on the methodology. + +### 6.3.2 Relationship with eTOM ([ITU-T M.3050.x]) + +The SID and eTOM [ITU-T M.3050.x] model the same subject matter from different points of view. The eTOM focuses on the business processes; the dynamic aspects of the business. + +The SID analysis model focuses on the static aspects of the business; the things that the business processes act on, their characteristics and relationships. + +The SID analysis model is organized using the SID framework. + +The top level of grouping, called a SID domain, aligns with the eTOM level 0 definitions of: + +- Market/Sales +- Product +- Customer +- Service +- Resource +- Supplier/Partner. + +The framework also represents common business entities (e.g., party, location, policy) and has a placeholder domain for Enterprise entities which have not yet been fully defined (e.g., Financial information). + +The SID framework is extensively documented in the main GB922 document [TMF GB922] with an overview given in clause 7. + +### 6.3.3 Relationship with [ITU-T M.3100] + +[ITU-T M.3100] is a generic information model focused on modelling of equipment and network resources. [ITU-T M.3100] is structured into fragments: + +- Network fragment +- Managed element fragment +- Physical equipment fragment +- Logical equipment fragment + +- Termination point fragment – Network element view +- Termination point fragment – Network view +- Topology and connectivity fragment – Network view +- Telemetry fragment +- Transmission fragment +- Cross-connection fragment +- Functional area fragment + +The products and service domains defined by SID can be considered as complements to the current content of [ITU-T M.3100], i.e., there is no direct overlap between the two models. + +The current [ITU-T M.3100] is based on the GDMO notation. As a result, [ITU-T M.3100] can be considered a data model (see definitions). GDMO is a flexible notation that need not be supported by CMIP. The result is that [ITU-T M.3100] today is a combination of an information model (the conceptual aspects) and a specific data model for use with CMIP. + +### **6.3.4 Relationship with [b-ITU-T M.1400.x]** + +The [b-ITU-T M.1400.x] series Recommendations focus on the specification of the terminology and grammar as perceived by the end users. The specification requirements may include requirements to support end-user interaction at their human-computer interfaces. + +A detailed description of the relationship and differences can be found in Appendix V. + +# **7 SID Framework** + +This clause describes the SID framework that is used to organize the SID model. The SID framework provides a high-level view into the SID entities, as well as providing an organizing structure in which the SID business entities reside. Additional details can be found in [TMF GB922]. + +Figure 1 below shows how the domains contained within the SID framework align with eTOM level one domains/concepts. Whether taking a process or information perspective, it is important to be viewing the same set of concepts. The alignment is also a necessary enabler when mapping eTOM processes to SID business entities. + +![Diagram of eTOM level 1 process groupings showing the relationship between Customer, Supplier/partner, and Enterprise management domains, with Business view domains on the right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the eTOM level 1 process groupings, organized into three main horizontal layers: + +- Customer (Top Layer):** A yellow oval at the top. +- Strategy, infrastructure and product (Left Column):** Contains three sub-processes: + - Strategy and commit + - Infrastructure lifecycle management + - Product lifecycle management +- Operations (Right Column):** Contains four sub-processes: + - Operations support and readiness + - Fulfillment + - Assurance + - Billing +- Enterprise management (Bottom Layer):** A grey box containing: + - Strategic and enterprise planning + - Enterprise risk management + - Enterprise effectiveness management + - Knowledge and research management + - Financial and asset management + - Stakeholder and external relations management + - Human resources management +- Internal Processes (Middle Section):** Four rows of boxes connecting the left and right columns: + - Marketing and offer management (left) ↔ Customer relationship management (right) + - Service development and management (left) ↔ Service management and operations (right) + - Resource development and management (left) ↔ Resource management and operations (right) + - Supply chain development and management (left) ↔ Supplier/partner relationship management (right) +- Stakeholders (Bottom Layer):** Three ovals at the bottom: + - Shareholders + - Employees + - Other stakeholders +- Business view domains (Right Side):** A dashed box containing seven colored rectangles, each with an arrow pointing to a specific process grouping: + - Market/sales (red) points to Marketing and offer management + - Product (yellow) points to Product lifecycle management + - Customer (light green) points to Customer relationship management + - Service (green) points to Service management and operations + - Resource (teal) points to Resource management and operations + - Supplier/partner (blue) points to Supplier/partner relationship management + - Enterprise (grey) points to Enterprise management + - Common business (pink) points to the bottom stakeholder area + +M.3190(08)\_F01 + +**eTOM level 1 process groupings** + +Diagram of eTOM level 1 process groupings showing the relationship between Customer, Supplier/partner, and Enterprise management domains, with Business view domains on the right. + +**Figure 1 – eTOM/SID concepts/domains** + +## 7.1 SID framework – Level 1 ABEs + +Figure 2 shows the SID framework. The framework depicts the domains and level 1 aggregate business entities (ABE) contained within each domain. + +![SID business view framework diagram showing seven domains: Market/sales, Product, Customer, Service, Resource, Supplier/partner, and Enterprise. Each domain is a colored box containing a grid of business entities. The Enterprise domain is marked as 'Under construction'.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +| | | | | | +|--------------------------|----------------------------------|-------------------------|-------------------------------|--------------------------| +| Market/sales | | | | | +| Market strategy and plan | Marketing campaign | Contact/lead/prospect | | | +| Market segment | Competitor | Sales statistic | Sales channel | | +| Product | | | | | +| Product | Strategic product portfolio plan | Product performance | | | +| Product specification | Product offering | Product usage statistic | | | +| Customer | | | | | +| Customer | Customer Order | Customer problem | Applied customer billing rate | Customer bill collection | +| Customer interaction | Customer statistic | Customer SLA | Customer bill | Customer bill inquiry | +| Service | | | | | +| Service | Service applications | Service performance | Service strategy and plan | | +| Service specification | Service configuration | Service usage | Service trouble | Service test | +| Resource | | | | | +| Resource | Resource topology | Resource performance | Resource strategy and plan | | +| Resource specification | Resource configuration | Resource usage | Resource Trouble | Resource Test | +| Supplier/partner | | | | | +| Supplier/partner | S/P interaction | S/P order | S/P performance | S/P bill | +| S/P plan | S/P product | S/P SLA | S/P problem | S/P bill inquiry | +| | | | S/P statistic | S/P payment | +| Enterprise | | Common business | | | +| (Under construction) | | Party | Business interaction | | +| | | Location | Policy | Agreement | + +SID business view framework diagram showing seven domains: Market/sales, Product, Customer, Service, Resource, Supplier/partner, and Enterprise. Each domain is a colored box containing a grid of business entities. The Enterprise domain is marked as 'Under construction'. + +M.3190(08)\_F02 + +**Figure 2 – SID business view framework** + +As the development of the SID model has progressed, subsequent levels of ABEs have been identified. + +## 7.2 ABE categorization + +The ABE content and structure within each domain should be consistent. To ensure this, each ABE is aligned with a categorization pattern as described below. The pattern can also be used to confirm the completeness of each domain's ABE. + +ABE categories include: + +- Strategy and plan +- Managed entity +- Managed entity specification – A description of a ManagedEntity that might allow it to be built. +- Interaction – A communication with a ManagedEntity. This is a type of BusinessInteraction. +- Configuration – The internal structure of a ManagedEntity. +- Performance – The measure of ManagedEntity quality. +- Test – A means of interrogating a ManagedEntity in order to understand its state(s). +- Trouble – A problem associated with a ManagedEntity. Alarms, outages and faults are examples. + +- Price – The cost of a ManagedEntity. +- Usage – A period of time during which a ManagedEntity is in use. + +NOTE – ABEs in market/sales and common business domains have not yet been categorized. + +# 8 Product domain + +This clause is an introduction to the product domain; detailed specifications can be found in [TMF GB922A3]. + +The product domain is concerned with the life cycle of products and information and contract operations related to the products' life cycle. The domain contains aggregate business entities that deal with the strategic portfolio plans, products offered, product performance, product usage statistics, as well as the product instances delivered to a customer. + +**Table 2 – Relationship of product ABEs to eTom processes** + +| Product ABEs | Primary vertical eTOM process groupings | Primary eTOM Level 2 processes | Secondary eTOM Level 2 processes | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------|----------------------------------------------| +| Strategic product portfolio plan
Is concerned with the plans of the product portfolio, which product offerings to make available to each market segment and the plans to development and deploy product offerings, as well as retirement of products. | M&OM – SC | Product & offer portfolio planning | Market strategy & policy | +| | | | Product & offer development & retirement | +| Product specification
Defines the functionality and characteristics of product offerings made available to the market. | M&OM – PLM | Product & offer development & retirement | Product & offer capability delivery | +| | | | Service configuration & activation | +| | | | SM&O support & readiness | +| Product offering
Represents tangible and intangible goods and services made available for a certain price to the market in the form of product catalogues. This ABE is also responsible for targeting market segments based on the appropriate market strategy. | M&OM – PLM | Product & offer development & retirement | Marketing fulfillment response | +| | | | Product marketing communications & promotion | +| | | | Product & offer capability delivery | +| | | | Selling | +| | | | Order handling | + +**Table 2 – Relationship of product ABEs to eTom processes** + +| Product ABEs | Primary vertical eTOM process groupings | Primary eTOM Level 2 processes | Secondary eTOM Level 2 processes | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------|------------------------------------------| +| Product
Represents an instance of a product offering subscribed to by a party, such as a customer, the place where the product is in use, as well as configuration characteristics, such as assigned telephone numbers and internet addresses. The Product ABE also tracks the services and/or resources through which the product is realized. | CRM – F | Order handling | Selling | +| | | | Service configuration & activation | +| | | | Problem handling | +| | | | Customer QoS/SLA management | +| | | | Billing & collections management | +| | | | Service problem management | +| | | | Service quality management | +| | | | Service & specific instance rating | +| | | | SM&O support & readiness | +| Product usage statistic
Represents usage trends of products associated with various demographics, such as market segment. | CRM – OSR | CRM support & readiness | Product & offer development & retirement | +| | | | Problem handling | +| | | | Customer QoS/SLA management | +| | | | Enterprise performance assessment | + +**Table 2 – Relationship of product ABEs to eTom processes** + +| Product ABEs | Primary vertical eTOM process groupings | Primary eTOM Level 2 processes | Secondary eTOM Level 2 processes | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------|------------------------------------------| +| Product performance
The product performance ABE handles product performance goals, the results of end-to-end product performance assessments, and the comparison of assessments against goals. The results may include the identification of potential capacity issues. | CRM – OSR | CRM support & readiness | Product & offer development & retirement | +| | | | Customer QoS/SLA management | +| | | | Service quality management | +| | | | Resource performance management | +| | | | Enterprise performance assessment | + +# 9 Service domain + +This clause is an introduction to the service domain; detailed specifications can be found in [TMF GB922A4SO]. + +The service domain consists of a set of layered ABEs that are used to manage the definition, development, and operational aspects of services provided by a management system. Entities in this domain support various eTOM processes that deal with the definition, development and management of services offered by an enterprise. This includes agreement on service levels to be offered, deployment and configuration of services, management of problems in service installation, deployment, usage, or performance, quality analysis, and rating. Finally, this domain also includes entities to perform planning for future offerings, service enhancement or retirement, and capacity. + +**Table 3 – Relationship of service ABEs to eTOM processes** + +| Service ABEs | Primary vertical eTOM process groupings | Primary eTOM level 2 processes | Secondary eTOM level 2 processes | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------|----------------------------------| +|

Service specification

The service specification ABE contains entities that define the invariant characteristics and behaviour of both types of service entities. This enables multiple instances to be derived from a single specification entity. In this derivation, each instance will use the invariant characteristics and behaviour defined in its associated template.

Entities in this ABE focus on adherence to standards, distinguishing features of a service, dependencies (both physical and logical, as well as on other services), quality, and cost. In general, entities in this ABE enable services to be bound to products and run using resources.

| SD&M – PLM | Service development & retirement | Service capability delivery | +| Service configuration & activation | | | | +| Service problem management | | | | +| Service quality management | | | | +| Service & specific instance rating | | | | +| SM&O support & readiness | | | | +|

Service

The service ABE contains entities that are used to represent both customer-facing and resource-facing types of services. Entities in this ABE provide different views to examine, analyze, configure, monitor and repair services of all types. Entities in this ABE are derived from service specification entities.

| SM&O – F | Service configuration & activation | Service capability delivery | +| Service problem management | | | | +| Service development & retirement | | | | +| SM&O support & readiness | | | | +| Service quality management | | | | +| Service & specific instance rating | | | | + +**Table 3 – Relationship of service ABEs to eTom processes** + +| Service ABEs | Primary vertical eTOM process groupings | Primary eTOM level 2 processes | Secondary eTOM level 2 processes | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------|----------------------------------| +| Service applications
The service applications ABE contains entities that define different types of services implemented as applications. There are at least three different types of entities in this domain, which form a hierarchy of applications. The simplest is a coordinated set of service mechanisms, such as the ability to fine-tune QoS. The next level of application is a type of transport, such as a VPN, that uses one or more service mechanisms to provide basic functionality to a PartyRole. The highest level of application is a management application that uses transport(s) and mechanisms to provide an end-to-end manageable application, such as distance learning or VoIP. | SM&O – F | Service configuration & activation | Service problem management | +| Service capability delivery | | | | +| Service development & retirement | | | | +| Service quality management | | | | +| Service & specific instance rating | | | | +| Service configuration
The service configuration ABE contains entities that are used to represent and manage configurations of CustomerFacingService and ResourceFacingService entities. This set of entities also provides details on how the configuration of each of these types of services can be changed. The entities in this ABE depend on entities in the resource domain, which provide the physical and logical infrastructure for implementing a service. They all define dependencies between a higher-level service and any sub-services that are used by the higher-level service. | SM&O – F | Service configuration & activation | Service capability delivery | +| SM&O support & readiness | | | | +| Resource provisioning | | | | +| Service performance
The service performance ABE collects, correlates, consolidates, and validates various performance statistics and other operational characteristics of customer and resource facing service entities. It provides a set of entities that can monitor and report on performance. Each of these entities also conducts network performance assessment against planned goals, performs various aspects of trend analysis, including error rate and cause analysis and service degradation.

Entities in this ABE also manage the traffic generated by a service, as well as traffic trend analysis. This is important for newer technologies that separate data, control and management functions for a given service. | SM&O – A | Service quality management | Service problem management | +| SM&O support & readiness | | | | +| Service development & retirement | | | | +| Resource performance management | | | | + +**Table 3 – Relationship of service ABEs to eTom processes** + +| Service ABEs | Primary vertical eTOM process groupings | Primary eTOM level 2 processes | Secondary eTOM level 2 processes | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------|---------------------------------------| +| Service test
The service test ABE contains entities that are used to test customer and resource facing service entities. These entities are usually invoked during installation, as a part of trouble diagnosis, or after trouble repair has been completed. | SM&O – F | Service configuration & activation | Service problem management | +| | | | Service quality management | +| Service trouble
The service trouble ABE manages faults, alarms, and outages from a service point-of-view. This is then correlated to trouble tickets, regardless of whether the cause is physical or logical.
Other entities in this ABE are used to direct the recovery from each of these three types of problems. They provide the ability to associate resource faults and alarms to degradation and outages of services that run on those resources. These functions are independent of the resources and technologies used to build the service.
A third set of entities in this ABE is used to differentiate between customer-reported problems and network-induced problems. | SM&O – A | Service problem management | SM&O support & readiness | +| | | | Problem handling | +| | | | Service quality management | +| | | | Resource trouble management | +| Service usage
The service usage ABE collects service consumption data, and generates service usage records, for use by other business entities. The entities in this ABE provide physical, logical, and network usage information. | SM&O – B | Service & specific instance rating | Resource data collection & processing | +| | | | Service quality management | +| | | | Service development & retirement | +| Service strategy & plan
The service strategy and plan ABE contains entities that are used to address the need for enhanced or new services, as well as the retirement of existing services, by the enterprise. These entities have a strong dependency to both entities in the resource and product domains. Resulting efforts, such as deciding what resources to use to host a service, or what services are used to support new product specifications, are also supported, as are service demand forecasts. | SD&M – SC | Service strategy & planning | Product & offer portfolio planning | +| | | | Service capability delivery | +| | | | Service development & retirement | +| | | | Resource strategy & planning | + +# Appendix I + +## Analysis patterns used in SID + +(This appendix does not form an integral part of this Recommendation) + +NOTE – The content of this appendix is based on the SID primer [b-TMF GB922 primer]. + +This appendix introduces patterns that have emerged as we modelled the eTOM processes in the SID analysis model. We use these patterns to improve the quality of the SID model, in particular coupling & cohesion [b-Design]. + +Since the primary focus of this primer is not on patterns, only a brief overview will be given and a reference given to more detailed definitions. + +A pattern can be described as follows [b-Language]: + +*"Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice".* + +### I.1 Specification + +The specification pattern [b-Patterns-2] is used in the SID when: + +*"There needs to be a description about an item or service, independent of the current existence of any examples of those items or services".* + +The specification entity does not represent a concept or thing, but *information about* a concept or thing. Specification entities are found in business concepts such as catalogs, manufacturing specifications, recipes and other documentation that relate to types of things rather than individual instances. + +This pattern is used in the SID Product Addendum (*Product & ProductSpecification Entities*) and most other SID addenda. + +![UML diagram of the Specification pattern](8ed7f57cc317f6574bec781d01ae6ad2_img.jpg) + +The diagram illustrates the Specification pattern in a UML class diagram. It features three classes: **AnEntitySpec**, **AnEntity**, and **AnotherEntity**. **AnEntitySpec** is connected to **AnEntity** via a directed association labeled *SpecificationDescribes*. The multiplicity at the **AnEntitySpec** end is 1, and at the **AnEntity** end is \*. **AnEntity** is shown as a superclass for **AnotherEntity**. Two callout boxes provide additional information: one points to **AnEntitySpec** with the text "Attributes common to the type of entity", and the other points to **AnEntity** with the text "Attributes related to identity". The diagram is labeled M.3190(08)\_Fl.1. + +UML diagram of the Specification pattern + +Figure I.1 – Specification pattern + +### I.2 Abstract superclass + +We use the abstract superclass pattern [b-Abstract] to add superclass entities to allow us to group similar entities together. We make the parent entity abstract to show that it will not occur in the real world, but is a modelling construct. + +The abstract superclass pattern helps make the SID more general and easier to extend. This pattern helps us improve the modularity (coupling & cohesion [b-Design]) of the SID model. + +This pattern is used extensively in the SID (e.g., the *Party Entity* is an abstract superclass of the *Individual Entity* and the *Organization Entity*). + +![Diagram of the abstract superclass pattern. It shows a box labeled 'AnotherEntity' connected by a line to a box labeled 'AnAbstractEntity' (in italics). A callout bubble above 'AnotherEntity' says 'Another entity can link to this or that'. A callout bubble above 'AnAbstractEntity' says 'Note name is in italics'. Below 'AnAbstractEntity', two boxes labeled 'ThisEntity' and 'ThatEntity' have inheritance arrows pointing up to it. The box 'AnAbstractEntity' contains the attribute 'aCommonAttribute'. A small label 'M.3190(08)_FI.2' is at the bottom right.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +Diagram of the abstract superclass pattern. It shows a box labeled 'AnotherEntity' connected by a line to a box labeled 'AnAbstractEntity' (in italics). A callout bubble above 'AnotherEntity' says 'Another entity can link to this or that'. A callout bubble above 'AnAbstractEntity' says 'Note name is in italics'. Below 'AnAbstractEntity', two boxes labeled 'ThisEntity' and 'ThatEntity' have inheritance arrows pointing up to it. The box 'AnAbstractEntity' contains the attribute 'aCommonAttribute'. A small label 'M.3190(08)\_FI.2' is at the bottom right. + +**Figure I.2 – Abstract superclass pattern** + +We will now go through a simple example of how the abstract entity pattern can be used to improve a model. + +We may be asked to model a piece of business information: "We sell bookshelves, chairs and desks to charities, individuals, companies and government departments". If we just model this directly, then we will produce a model that will be complex and hard to extend. If we add two new abstract entities, we can now say: "We sell furniture to BusinessParties". The new concepts show a more fundamental understanding of the business. Note that Furniture is a placeholder for the "Concrete Entities" Chair, Desk & Bookshelf. Furniture is abstract because when we sell something to a particular customer we do not say: "I just sold a furniture to John Brown", instead we use one of the specific (concrete) entities. + +![Diagram illustrating the abstract superclass pattern example. On the left, a complex web of relationships connects 'Bookshelf', 'Chair', and 'Desk' to 'Charity', 'Individual', 'Company', and 'Govt Department'. A large arrow points to the right, where the model is simplified. On the right, 'Furniture' (in italics) is an abstract superclass for 'Chair', 'Desk', and 'Bookshelf'. 'Furniture' has a 'soldTo' relationship to 'Business Party' (in italics). 'Business Party' is an abstract superclass for 'Charity', 'Company', 'Govt Department', and 'Individual'. Callouts explain the simplification: 'We sell bookshelves, chairs and desks to Charities, Individuals, Companies and Government departments' on the left, and 'We sell furniture to Business Parties' on the right. A small label 'M.3190(08)_FI.3' is at the bottom right.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +Diagram illustrating the abstract superclass pattern example. On the left, a complex web of relationships connects 'Bookshelf', 'Chair', and 'Desk' to 'Charity', 'Individual', 'Company', and 'Govt Department'. A large arrow points to the right, where the model is simplified. On the right, 'Furniture' (in italics) is an abstract superclass for 'Chair', 'Desk', and 'Bookshelf'. 'Furniture' has a 'soldTo' relationship to 'Business Party' (in italics). 'Business Party' is an abstract superclass for 'Charity', 'Company', 'Govt Department', and 'Individual'. Callouts explain the simplification: 'We sell bookshelves, chairs and desks to Charities, Individuals, Companies and Government departments' on the left, and 'We sell furniture to Business Parties' on the right. A small label 'M.3190(08)\_FI.3' is at the bottom right. + +**Figure I.3 – Abstract superclass pattern example** + +### I.3 Composite + +The composite pattern [b-Patterns-3] is usually thought of as a design pattern [b-IBM]: + +*"Assemble objects into tree structures. COMPOSITE simplifies clients by letting them treat individual objects and assemblies of objects uniformly."* + +In the SID, we use the composite pattern when there is a business concept where a single thing or a collection of those things can be used interchangeably. For example, in a warehouse, the concept of a "stock item" may include parts, sub-assemblies and complete items. + +This pattern is used extensively in the SID (e.g., *Party, Individual & Organization Entities*). + +![UML class diagram for the Composite pattern and two network diagrams illustrating tree and DAG structures.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +The diagram illustrates the Composite pattern in the SID. It features a class hierarchy where **AnEntity** is the superclass, and **ASimpleEntity** and **ACompoundEntity** are subclasses. **AnotherEntity** is shown with a relationship to **AnEntity**. A callout box indicates that another entity can link to a single node, a sub-network, or the whole network. A note specifies the cardinality: 0..1 if a Tree, \* if a DAG. Below the class diagram, two network diagrams are shown. The left diagram, labeled 'A tree is a directed network with no loops (each node has only one parent)', shows a hierarchical tree structure. The right diagram, labeled 'A directed acyclic graph (DAG) is a directed network with no loops (in the arrow direction)', shows a more complex network where nodes can have multiple parents. The label 'M.3190(08)\_FI.4' is present in the bottom right corner. + +UML class diagram for the Composite pattern and two network diagrams illustrating tree and DAG structures. + +**Figure I.4 – Composite pattern** + +Note that when we form composites of physical things, these often form tree structures. Composites of logical things and composites of specifications often form directed acyclic graphs. In effect, this is just common sense. If there is a specific hard drive, it can only be plugged into a single computer at a time. A *type* of hard drive, however, may be able to be plugged into many different types of computers (PCs, Macintoshes, sun workstations, etc.). + +### I.4 Role entity + +The role entity pattern [b-Roles] allows us to represent behaviour with respect to a given context, e.g., "a person who is a witness in the context of a legal trial". + +![UML Class Diagram illustrating the Role entity pattern. AnEntity (with intrinsicAttribute) has a 1..* relationship with AnEntityRole (with validFor : TimePeriod). ThisRole (with contextualAttribute1) and ThatRole (with contextualAttribute2) inherit from AnEntityRole. AnotherEntity is associated with ThatRole. A callout box states: 'Another entity can link to the entity directly, or via its roles (as shown here)'. The diagram is labeled M.3190(08)_FI.5.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +``` + +classDiagram + class AnEntity { + intrinsicAttribute + } + class AnEntityRole { + validFor : TimePeriod + } + class ThisRole { + contextualAttribute1 + } + class ThatRole { + contextualAttribute2 + } + class AnotherEntity { + } + + AnEntity "1" *-- "*" AnEntityRole + ThisRole <|-- AnEntityRole + ThatRole <|-- AnEntityRole + ThatRole -- AnotherEntity + Note right of AnotherEntity: Another entity can link to the entity directly, or via its roles (as shown here) + M.3190(08)_FI.5 + +``` + +UML Class Diagram illustrating the Role entity pattern. AnEntity (with intrinsicAttribute) has a 1..\* relationship with AnEntityRole (with validFor : TimePeriod). ThisRole (with contextualAttribute1) and ThatRole (with contextualAttribute2) inherit from AnEntityRole. AnotherEntity is associated with ThatRole. A callout box states: 'Another entity can link to the entity directly, or via its roles (as shown here)'. The diagram is labeled M.3190(08)\_FI.5. + +**Figure I.5 – Role entity pattern** + +Use of roles is a fundamental pattern that helps us simplify a model, and make it more closely represent the real world. + +Intrinsic attributes are those that a thing always has. Contextual attributes are those that relate to a thing in certain situations. + +When modelling a thing, question whether it has different behaviours in different circumstances, i.e., how it is being used, not just what it is. If so, the role pattern may be useful. + +Representing the concept and its roles using two entities makes the SID model more robust to change and reduces duplication. + +### I.5 Temporal state entity + +We use the temporal state entity pattern [b-Patterns-3] when we wish to be able to show the states of an entity, the attributes for each state and the temporal or life cycle aspects of an entity. An entity's state will change over time and we may wish to keep only the current state or a complete history, depending on the business requirements. + +Separating the characteristics that we need to monitor over time into a separate entity allows us to show this more clearly, than if it was shown as attributes in the entity. + +Note that this pattern looks similar to the "Role Entity" pattern but represents a different concept. + +The articles "Patterns for things that change with time" on Martin Fowler's [b-Patterns-1] website give a good understanding of time-related issues and are well worth reading. + +![UML Class diagram and UML State chart diagram for the Temporal state entity pattern. The class diagram shows AnotherEntity, AnEntity (with timeInvariantAttribute), and AnEntityState (with timeVaryingAttribute and validFor: TimePeriod). The state chart shows states: Ready, Activating, Active, Aborting, Completing, Cancelled, Aborted, and Completed with various transitions.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +The diagram illustrates the Temporal state entity pattern. It consists of two parts: a UML Class diagram and a UML State chart diagram. + +**UML Class diagram:** + +- AnotherEntity**: A class box at the top left. +- AnEntity**: A class box below AnotherEntity, containing an attribute `timeInvariantAttribute`. It has a 1-to-many association with AnEntityState. +- AnEntityState**: A class box to the right of AnEntity, containing attributes `timeVaryingAttribute` and `validFor : TimePeriod`. + +Callout boxes indicate: "States can change over time. May limit to one state at any one time" and "A UML state chart diagram". + +**UML State chart diagram:** + +- Starts with an initial state (black dot) leading to **Ready** (yellow state). +- Ready** has a horizontal transition to **Cancelled** (yellow state) and a vertical transition down to **Activating** (purple state). +- Activating** has a horizontal transition to **Aborting** (purple state) and a vertical transition down to **Active** (green state). +- Active** has a horizontal transition to **Completing** (purple state) and a diagonal transition up-right to **Aborting**. +- Completing** has a horizontal transition to **Completed** (yellow state) and a diagonal transition up-right to **Aborting**. +- Cancelled**, **Aborted**, and **Completed** all have transitions leading to a final state (bullseye symbol). + +M.3190(08)\_FI.6 + +UML Class diagram and UML State chart diagram for the Temporal state entity pattern. The class diagram shows AnotherEntity, AnEntity (with timeInvariantAttribute), and AnEntityState (with timeVaryingAttribute and validFor: TimePeriod). The state chart shows states: Ready, Activating, Active, Aborting, Completing, Cancelled, Aborted, and Completed with various transitions. + +**Figure I.6 – Temporal state entity pattern** + +### **I.6 Self-relationship** + +The self-relationship pattern is [b-ISO 19108] used when an instance of an entity may have a relationship to other instances of the same entity. For instance, a family tree could be formed by linking individuals to their parents. + +This pattern is used in the SID Project analysis model (e.g., *Project Element Entity*). + +**Table I.1 – Self-relationship types** + +| Relationship type | Description | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Dependency | This is where the two entities have some starting or finishing dependency, e.g., Activity 2 cannot start until Activity 1 is complete. | +| Succession | This is where one or more entities are replaced by one or more other entities. This is an abstract relationship and one of the concrete types listed below must be used. | +| Substitution | This is a one for one replacement, e.g., Activity 1 is no longer valid and has been replaced by Activity 1A. | +| Division | This is a one for many replacement, e.g., Activity 1 is no longer valid and has been replaced by Activities 1A, 1B and 1C. | +| Fusion | This is a many for one replacement, e.g., Activities 1A, 1B and 1C are no longer valid and have been replaced by Activity 1Z. | + +Note how the model uses an association entity, allowing us to define attributes for the association. + +![UML Class Diagram for Figure I.7: Self-relationship pattern. The diagram shows a hierarchy of entity relationship types. At the top is 'anEntityRelationship'. Below it are 'anEntitySuccession' and 'anEntityDependency', which inherit from 'anEntityRelationship'. Below 'anEntitySuccession' are 'anEntitySubstitution', 'anEntityFusion', and 'anEntityDivision', which also inherit from 'anEntityRelationship'. A self-association on 'AnEntity' (multiplicity *) points to 'anEntityRelationship' (multiplicity *).](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +``` + +classDiagram + class anEntityRelationship + class AnEntity + class anEntitySuccession + class anEntityDependency + class anEntitySubstitution + class anEntityFusion + class anEntityDivision + + anEntitySuccession --|> anEntityRelationship + anEntityDependency --|> anEntityRelationship + anEntitySubstitution --|> anEntitySuccession + anEntityFusion --|> anEntitySuccession + anEntityDivision --|> anEntitySuccession + AnEntity "*" -- "*" anEntityRelationship + +``` + +UML Class Diagram for Figure I.7: Self-relationship pattern. The diagram shows a hierarchy of entity relationship types. At the top is 'anEntityRelationship'. Below it are 'anEntitySuccession' and 'anEntityDependency', which inherit from 'anEntityRelationship'. Below 'anEntitySuccession' are 'anEntitySubstitution', 'anEntityFusion', and 'anEntityDivision', which also inherit from 'anEntityRelationship'. A self-association on 'AnEntity' (multiplicity \*) points to 'anEntityRelationship' (multiplicity \*). + +M.3190(08)\_FI.7 + +**Figure I.7 – Self-relationship pattern** + +### I.7 Entity specification characteristic/entity characteristic + +When constructing any model, it is almost impossible to discover all the possible attributes, such as configurable and/or static properties and features, which characterize a business entity. Even if all the attributes can be found when the model is constructed, additional attributes will be found as a model is extended. Additionally, certain attributes characterize different types of business entities, represented by entity specifications in the SID. + +For example, an instance of a mobile device product specification may be characterized by configurable colour and static size, while hi-speed Internet is characterized by configurable bandwidth. The EntitySpecificationCharacteristic/EntityCharacteristic pattern provides this type of extensibility and characterization for different instances of specifications and their related entity instances. The pattern is shown in Figure I.8. + +![UML Class Diagram for Figure I.8: Entity specification characteristic/entity characteristic pattern. The diagram shows relationships between EntitySpecification, Entity, EntitySpecCharacteristic, EntitySpecCharacteristicValue, and EntityCharacteristicValue. EntitySpecification (from Root Business Entities ABE) has a 0..n association with Entity (0..1) labeled 'EntitySpecificationDescribes'. EntitySpecification has a 0..n association with EntitySpecCharacteristic (0..n) labeled 'EntitySpecCharacterizedBy'. EntitySpecCharacteristic (from Root Business Entities ABE) has a 0..1 association with EntitySpecCharacteristicValue (0..n) labeled 'EntitySpecCharEnumeratedBy'. EntitySpecCharacteristic has a 0..1 association with Entity (0..n) labeled 'EntitySpecCharacteristicDescribes'. EntitySpecCharacteristicValue (from Root Business Entities ABE) has a 0..1 association with Entity (0..n) labeled 'EntitySpecCharValueDescribes'. EntityCharacteristicValue (from Root Business Entities ABE) has a 1 association with Entity (0..n) labeled 'EntityDefinedBy'.](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` + +classDiagram + class EntitySpecification["EntitySpecification (from Root Business Entities ABE)"] + class Entity["Entity (from Root Business Entities ABE)"] + class EntitySpecCharacteristic["EntitySpecCharacteristic (from Root Business Entities ABE)"] + class EntitySpecCharacteristicValue["EntitySpecCharacteristicValue (from Root Business Entities ABE)"] + class EntityCharacteristicValue["EntityCharacteristicValue (from Root Business Entities ABE)"] + + EntitySpecification "0..n" -- "0..1" Entity : EntitySpecificationDescribes + EntitySpecification "0..n" -- "0..n" EntitySpecCharacteristic : EntitySpecCharacterizedBy + EntitySpecCharacteristic "0..1" -- "0..n" EntitySpecCharacteristicValue : EntitySpecCharEnumeratedBy + EntitySpecCharacteristic "0..1" -- "0..n" Entity : EntitySpecCharacteristicDescribes + EntitySpecCharacteristicValue "0..1" -- "0..n" Entity : EntitySpecCharValueDescribes + EntityCharacteristicValue "0..n" -- "1" Entity : EntityDefinedBy + EntitySpecification "0..n" -- "0..n" EntitySpecCharacteristicValue : EntitySpecDescribedBy + +``` + +UML Class Diagram for Figure I.8: Entity specification characteristic/entity characteristic pattern. The diagram shows relationships between EntitySpecification, Entity, EntitySpecCharacteristic, EntitySpecCharacteristicValue, and EntityCharacteristicValue. EntitySpecification (from Root Business Entities ABE) has a 0..n association with Entity (0..1) labeled 'EntitySpecificationDescribes'. EntitySpecification has a 0..n association with EntitySpecCharacteristic (0..n) labeled 'EntitySpecCharacterizedBy'. EntitySpecCharacteristic (from Root Business Entities ABE) has a 0..1 association with EntitySpecCharacteristicValue (0..n) labeled 'EntitySpecCharEnumeratedBy'. EntitySpecCharacteristic has a 0..1 association with Entity (0..n) labeled 'EntitySpecCharacteristicDescribes'. EntitySpecCharacteristicValue (from Root Business Entities ABE) has a 0..1 association with Entity (0..n) labeled 'EntitySpecCharValueDescribes'. EntityCharacteristicValue (from Root Business Entities ABE) has a 1 association with Entity (0..n) labeled 'EntityDefinedBy'. + +M.3190(08)\_FI.8 + +**Figure I.8 – Entity specification characteristic/entity characteristic pattern** + +In this pattern, instances of EntitySpecCharacteristic represent the various features/properties specific to an instance of an EntitySpecification. For example, one characteristic may be the title + +and start time for a video on demand (VoD) product offering. Instances of *EntitySpecCharacteristicValue* represent the values that features/properties can take on. For example, the titles of the VoD can be SuperMan I, SuperMan II, Mission Impossible I, and so forth. + +Both *EntitySpecCharacteristic* and *EntitySpecCharacteristicValues* can be shared by multiple *EntitySpecifications*. That is the reason for the many-to-many association. For example, colour may be an option for many types of mobile devices. The association between *EntitySpecCharacteristicValue* and *EntitySpecification* exists because there may be a subset of all colours available for a particular instance of an *EntitySpecification*. For example, the entire set of colours may be red, green, blue, black, and silver, but for a particular instance of a mobile device, the colour options may be limited to red, black, and silver. Other features/properties, such as the start time for a VoD, are not constrained by a finite set of values, and therefore would not have associated instances of *EntitySpecCharacteristicValue*. + +When an instance of an *Entity* described by an instance of an *EntitySpecification* is created, instances of *EntityCharacteristic* are created based on the *EntitySpecCharacteristic*. For example, when an instance of VoD is created a title selection is made, such as SuperMan II, and the start time is specified for the VoD, such as 12AM on the 21st. + +Some features/properties are configurable, while others are not. For example, the title and start time are configuration for VoD. For other instances of *EntitySpecification*, a property, such as weight, may not be configurable. In this case, there may not be an instance of *EntityCharacteristic* as an entity. + +Figures I.9 and I.10 show the use of this pattern within the product specification ABE. Figure I.9 shows the use of the entity specification component of the pattern. Figure I.10 shows the use of the entity component of the pattern. + +![UML Class Diagram for Product Spec Characteristic](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +``` + +classDiagram + class ProductSpecCharRelationship { + charRelationshipType : string + validFor : TimePeriod + } + class ProductSpecification { + } + class ProductSpecCharacteristic { + ID : String + name : String + description : String + valueType : String + derivationFormula : String + presence : String + validFor : TimePeriod + } + class ProductSpecCharacteristicValue { + valueType : String + default : Boolean + value : String + valueFrom : String + valueTo : String + validFor : TimePeriod + } + class ConfigurableProductSpecCharacteristic { + } + + ProductSpecCharacteristic "0..n" -- "0..n" ProductSpecCharacteristic : ProdSpecCharacteristicReferences + (ProductSpecCharacteristic, ProductSpecCharacteristic) .. ProductSpecCharRelationship + ProductSpecCharacteristic "0..n" -- "0..n" ProductSpecification : ProdSpecCharacteristicDescribes + ProductSpecCharacteristic "1" -- "0..n" ProductSpecCharacteristicValue : ProdSpecCharacteristicTakesOn + ProductSpecification "0..n" -- "0..n" ProductSpecCharacteristicValue : ProdSpecDescribedBy + ConfigurableProductSpecCharacteristic --|> ProductSpecCharacteristic + +``` + +The diagram illustrates the relationships between four main classes: *ProductSpecCharRelationship*, *ProductSpecification*, *ProductSpecCharacteristic*, and *ProductSpecCharacteristicValue*. *ProductSpecCharRelationship* is an association class for a self-association on *ProductSpecCharacteristic* called *ProdSpecCharacteristicReferences* (0..n to 0..n). *ProductSpecCharacteristic* (0..n) is associated with *ProductSpecification* (0..n) via *ProdSpecCharacteristicDescribes*. *ProductSpecCharacteristic* (1) is associated with *ProductSpecCharacteristicValue* (0..n) via *ProdSpecCharacteristicTakesOn*. *ProductSpecification* (0..n) is associated with *ProductSpecCharacteristicValue* (0..n) via *ProdSpecDescribedBy*. *ConfigurableProductSpecCharacteristic* inherits from *ProductSpecCharacteristic*. Attributes for each class are listed within their respective boxes. The diagram is labeled M.3190(08)\_FI.9. + +UML Class Diagram for Product Spec Characteristic + +**Figure I.9 – Product spec characteristic** + +![UML Class Diagram showing relationships between ProductOffering, ProductSpecCharacteristicValue, ProductCharacteristicValue, ProductSpecCharacteristic, Product, ProductBundle, and ProductComponent.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +``` + +classDiagram + class ProductOffering { + <> + } + class ProductSpecCharacteristicValue { + <> + } + class ProductCharacteristicValue { + value : String + validFor : TimePeriod + } + class ProductSpecCharacteristic { + <> + } + class Product { + name : String + description : String + productStatus : String + productSerialNumber : String + validFor : TimePeriod + } + class ProductBundle + class ProductComponent + + ProductOffering "1" -- "0..n" Product : ProdOfferDescribes + ProductOffering "1" -- "0..n" ProductSpecCharacteristicValue : ProdSpecCharValueInstantiatedAsProductCharacteristicV... + ProductSpecCharacteristicValue "0..n" -- "0..1" ProductSpecCharacteristic : ProdSpecCharDescribesProdCharacteristicV... + ProductCharacteristicValue "0..n" -- "1" Product : ProdCharValueDefinesTheConfigurationOf + ProductBundle "0..1" -- "0..n" Product : ProductBundleComprisedOf + ProductComponent --|> Product + +``` + +The diagram illustrates the following classes and relationships: + +- ProductOffering** (from Product Offering ABE): + - Associated with **Product** (0..n) via **ProdOfferDescribes**. + - Associated with **ProductSpecCharacteristicValue** (0..n) via **ProdSpecCharValueInstantiatedAsProductCharacteristicV...**. +- ProductSpecCharacteristicValue** (from Product Specification ABE): + - Associated with **ProductSpecCharacteristic** (0..1) via **ProdSpecCharDescribesProdCharacteristicV...**. +- ProductCharacteristicValue**: + - Attributes: `value : String`, `validFor : TimePeriod`. + - Associated with **Product** (1) via **ProdCharValueDefinesTheConfigurationOf**. +- ProductSpecCharacteristic** (from Product Specification ABE): + - Associated with **ProductCharacteristicValue** (0..n) via **ProdSpecCharDescribesProdCharacteristicV...**. +- Product**: + - Attributes: `name : String`, `description : String`, `productStatus : String`, `productSerialNumber : String`, `validFor : TimePeriod`. + - Generalized by **ProductComponent**. + - Associated with **ProductBundle** (0..1) via **ProductBundleComprisedOf**. +- ProductBundle**: + - Associated with **Product** (0..n) via **ProductBundleComprisedOf**. +- ProductComponent**: + - Generalizes **Product**. + +M.3190(08)\_FI.10 + +UML Class Diagram showing relationships between ProductOffering, ProductSpecCharacteristicValue, ProductCharacteristicValue, ProductSpecCharacteristic, Product, ProductBundle, and ProductComponent. + +**Figure I.10 – Product spec characteristic and product characteristic** + +Alternatives to this pattern do exist. For example, entities, such as hi-speed Internet, can be explicitly added to the model. + +# Appendix II + +## SID document structure + +(This appendix does not form an integral part of this Recommendation) + +The complete set of SID specifications is listed in Table II.1. + +**Table II.1 – SID document structure** + +| Reference | Title | Included aggregate business entities | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| GB922 [TMF GB922] | Business View Concepts, Principles, and Domains describing the organizing structure of the SID business view shared information/data, the relationship to other TMF deliverables, and views of the contents of the model. | | +| GB922 Addendum 3 [TMF GB922A3] | Product | Product specification, product offering, product, product offering price | +| GB922 Addendum 4SO [TMF GB922A4SO] | Service | Service specification, service | +| GB922 Addendum 4-QoS | Service quality of service | Quality of service | +| GB922 Addendum 5PR | Physical resource | Physical resource | +| GB922 Addendum 5LR | Logical resource | Logical resource | +| GB922 Addendum 1P | Party | Party | +| GB922 Addendum 1L | Location | Location | +| GB922 Addendum 1BI | Business interaction | Business interaction | +| GB922 Addendum 1A | Agreement (including service level agreement) | Agreement | +| GB922 Addendum 1BT | Base types | Base types | +| GB922 Addendum 1T | Calendar | Calendar | +| GB922 Addendum 1J | Project | Project | +| GB922 Addendum 1POL | Policy | Policy | +| GB922 Addendum 1R | Root business entities | Root business entities | +| GB922 Addendum 2 | Customer | Customer, customer order, customer SLA | + +SID can be applied in parts, i.e., there is no need to implement all domains in order to make use of SID. As an example, the Location domain is referenced by the Product and Service domains, but other means of supporting address requirements are also allowed. + +# Appendix III + +## SID use of UML + +(This appendix does not form an integral part of this Recommendation) + +### III.1 UML overview + +The unified modelling language (UML) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modelling and other non-software systems. The UML represents a collection of best engineering practices that have proven successful in the modelling of large and complex systems. The UML is a very important part of developing object-oriented software and software development process. The UML uses mostly graphical notations to express the design of software projects. Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the software. + +### III.2 Goals of UML + +The primary goals in the design of the UML are: + +- Provide users with a ready-to-use, expressive visual modelling language so they can develop and exchange meaningful models +- Provide extensibility and specialization mechanisms to extend the core concepts +- Be independent of particular programming languages and development processes +- Provide a formal basis for understanding the modelling language +- Encourage the growth of the OO tools market +- Support higher-level development concepts such as collaborations, frameworks, patterns and components +- Integrate best practices. + +### III.3 Why use UML? + +As the strategic value of software increases for many companies, the industry looks for techniques to automate the production of software and to improve quality and reduce cost and time-to-market. These techniques include component technology, visual programming, patterns and frameworks. Businesses also seek techniques to manage the complexity of systems as they increase in scope and scale. In particular, they recognize the need to solve recurring architectural problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance. Additionally, the development for the World Wide Web, while making some things simpler, has exacerbated these architectural problems. The Unified modelling language (UML) was designed to respond to these needs. + +### III.4 UML diagrams + +The underlying premise of UML is that no one diagram can capture the different elements of a system in its entirety. Hence, UML is made up of nine diagrams that can be used to model a system at different points of time in the software life cycle of a system. The nine UML diagrams are: + +**Use case diagram:** The use case diagram is used to identify the primary elements and processes that form the system. The primary elements are termed as "actors", and the processes are called "use cases". The use case diagram shows which actors interact with each use case. + +**Class diagram:** The class diagram is used to refine the use case diagram and define a detailed design of the system. The class diagram classifies the actors defined in the use case diagram into a + +set of interrelated classes. The relationship or association between the classes can be either an "is-a" or "has-a" relationship. Each class in the class diagram may be capable of providing certain functionalities. These functionalities provided by the class are termed "methods" of the class. Apart from this, each class may have certain "attributes" that uniquely identify the class. + +**Object diagram:** The object diagram is a special kind of class diagram. An object is an instance of a class. This essentially means that an object represents the state of a class at a given point of time while the system is running. The object diagram captures the state of different classes in the system and their relationships or associations at a given point of time. + +**State diagram:** A state diagram, as the name suggests, represents the different states that objects in the system undergo during their life cycle. Objects in the system change states in response to events. In addition to this, a state diagram also captures the transition of the object's state from an initial state to a final state in response to events affecting the system. + +**Activity diagram:** The process flows in the system are captured in the activity diagram. Similar to a state diagram, an activity diagram also consists of activities, actions, transitions, initial and final states, and guard conditions. + +**Sequence diagram:** A sequence diagram represents the interaction between different objects in the system. The important aspect of a sequence diagram is that it is time-ordered. This means that the exact sequence of the interactions between the objects is represented step by step. Different objects in the sequence diagram interact with each other by passing "messages". + +**Collaboration diagram:** A collaboration diagram groups together the interactions between different objects. The interactions are listed as numbered interactions that help to trace the sequence of the interactions. The collaboration diagram helps to identify all the possible interactions that each object has with other objects. + +**Component diagram:** The component diagram represents the high-level parts that make up the system. This diagram depicts, at a high level, what components form part of the system and how they are interrelated. A component diagram depicts the components culled after the system has undergone the development or construction phase. + +**Deployment diagram:** The deployment diagram captures the configuration of the runtime elements of the application. This diagram is by far most useful when a system is built and ready to be deployed. + +### III.5 UML diagram classification – Static, dynamic, and implementation + +A software system can be said to have two distinct characteristics: a structural, "static" part and a behavioural, "dynamic" part. In addition to these two characteristics, an additional characteristic that a software system possesses is related to implementation: + +**Static:** The static characteristic of a system is essentially the structural aspect of the system. The static characteristics define what parts the system is made up of. + +**Dynamic:** The behavioural features of a system; for example, the ways a system behaves in response to certain events or actions are the dynamic characteristics of a system. + +**Implementation:** The implementation characteristic of a system is an entirely new feature that describes the different elements required for deploying a system. + +The UML diagrams that fall under each of these categories are: + +- *Static* + - Use case diagram + - Class diagram + +- *Dynamic* + - Object diagram + - State diagram + - Activity diagram + - Sequence diagram + - Collaboration diagram +- *Implementation* + - Component diagram + - Deployment diagram + +# Appendix IV + +## SID and the NGOSS views + +(This appendix does not form an integral part of this Recommendation) + +The NGOSS approach to developing SID in support of business applications can be characterized by the four NGOSS views, as shown in Figure IV.1. Each view exposes the aspects of the SID required to make decisions at various stages of the SID's development life cycle. + +The information models of the SID are limited to the business view, but can be transformed into systems views and implementation views. The SID remains at the conceptual level. + +![Figure IV.1 – NGOSS views diagram](a4b963a07cc368283154762c4b156fe7_img.jpg) + +The diagram illustrates the four NGOSS views in a clockwise cycle. It consists of four circular nodes arranged in a square layout, connected by thick black arrows. The top-left node is labeled 'Business view'. A horizontal arrow points from 'Business view' to the top-right node, labeled 'System view'. A vertical arrow points from 'System view' down to the bottom-right node, labeled 'Implementation view'. A horizontal arrow points from 'Implementation view' to the bottom-left node, labeled 'Deployment view'. A vertical arrow points from 'Deployment view' up to the 'Business view' node, completing the cycle. Below the diagram, the text 'M.3190(08)\_FIV.1' is displayed. + +Figure IV.1 – NGOSS views diagram + +Figure IV.1 – NGOSS views + +Development progresses from one view to the next. Each view has a different focus on a common set of SID artifacts that evolve from one view to the next. + +The business view describes the conceptual, or logical, design of an information architecture from the business perspective. The system view adds behavioural aspects to the conceptual design beginning to define how the entities within an ABE function together as a unit. The implementation view describes the actual implementation of the information architecture in the form of a database definition or API interfaces. The deployment view describes the roll-out of the information architecture as a functioning database or functioning APIs. + +## IV.1 SID life cycle + +The focus of the SID's development in the business view is on the discovery of business entities, their associations with other business entities, attributes that describe the entities, and types of entities. + +For example, suppose there is a requirement to develop an application that supports an enterprise's Product Catalog. This is the first step in gathering information requirements. At this point, a Product Catalog may be an aggregate business entity (ABE) or a single entity. By defining Product Catalog, more aspects of its make-up can be ascertained. The definition of a Product Catalog is "A list of ProductOfferings for sale, with prices and illustrations, for example in book form or on the web. ProductCatalogs can be used by Customers during a self-care ordering process and may be used across one or more DistributionChannels". From this definition, an initial model for Product Catalog can be constructed as shown in Figure IV.2. + +![UML Class Diagram showing the Initial product catalog model. Entities include GeographicArea, SalesChannel, ProductCatalogSpecification, ProductCatalog, ProductOffering, ProductCatalogProdOffer, and ProductOfferingPrice. Associations show relationships like ProdCatPublishedInGeoArea, ProdCatalogAvailableViaSalesChannel, ProdCatalogSpecDescribes, ProdOfferingPublishedInProdCatalog, ProdOfferValuedByPrice, and ProdOfferPriceAdvertisedAs.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +``` + +classDiagram + class GeographicArea { + <> + (from Geographic Place) + } + class SalesChannel { + <> + (from Sales Channel ABE) + } + class ProductCatalogSpecification { + name : String + description : String + validFor : TimePeriod + } + class ProductCatalog { + ID : string + type : string + validFor : TimePeriod + } + class ProductOffering { + <> + (from Product Offering ABE) + } + class ProductCatalogProdOffer { + validFor : TimePeriod + } + class ProductOfferingPrice { + <> + (from Product Offering Price ABE) + } + + ProductCatalogSpecification "1" -- "0..n" ProductCatalog : ProdCatalogSpecDescribes + ProductCatalog "0..n" -- "0..n" GeographicArea : ProdCatPublishedInGeoArea + ProductCatalog "0..n" -- "0..n" SalesChannel : ProdCatalogAvailableViaSalesChannel + ProductCatalog "0..n" -- "0..n" ProductOffering : ProdOfferingPublishedInProdCatalog + ProductCatalog "0..n" -- "0..n" ProductCatalogProdOffer : ProdOfferingPublishedInProdCatalog + ProductOffering "0..n" -- "0..n" ProductOfferingPrice : ProdOfferValuedByPrice + ProductOffering "0..n" -- "0..n" ProductOfferingPrice : ProdOfferPriceAdvertisedAs + +``` + +M.3190(08)\_FIV.2 + +UML Class Diagram showing the Initial product catalog model. Entities include GeographicArea, SalesChannel, ProductCatalogSpecification, ProductCatalog, ProductOffering, ProductCatalogProdOffer, and ProductOfferingPrice. Associations show relationships like ProdCatPublishedInGeoArea, ProdCatalogAvailableViaSalesChannel, ProdCatalogSpecDescribes, ProdOfferingPublishedInProdCatalog, ProdOfferValuedByPrice, and ProdOfferPriceAdvertisedAs. + +**Figure IV.2 – Initial product catalog model (example)** + +Additional requirements gathered specified that the Product Catalog is particular to one or more geographical areas and to one or more sales channels. When building the model, the SID EntitySpecification/Entity pattern was employed resulting in a specification for the ProductCatalog as shown in Figure IV.2. Based on this model, it is assumed that ProductCatalog represents a cohesive collection of business entities. Therefore, it is classified as a second level ABE within the Product Offering ABE within the SID business view. This example also shows how an ABE can be identified using a bottom-up discovery process, as initially it was not known whether ProductCatalog was an entity or an ABE. + +As development progresses, system view characteristics are discovered that further describe the Product Catalog ABE. Figure IV.3 shows several examples of system view characteristics, including the introduction of the ProdCatalogProdOffer association class and the operations on the ProductCatalog and ProdCatalogProdOffer entities. + +![UML Class diagram for Product catalog system view. It includes four classes: ProductCatalog, ProductOffering (from Product Offering ABE), ProdCatalogProdOffer, and ProductOfferingPrice (from Product Offering Price ABE). ProductCatalog has attributes ID (string), type (string), and validFor (TimePeriod). It has methods issueProductCatalog(), recallProductCatalog(), and discontinueProductCatalog(). ProductOffering has a 0..n association with ProductCatalog labeled ProdOfferingPublishedInProdCatalog. ProdCatalog has a 0..n association with ProdCatalogProdOffer labeled ProdOfferingPublishedInProdCatalog. ProdCatalog has a 0..n association with ProductOffering labeled ProdOfferValuedByPrice. ProdCatalogProdOffer has an attribute validFor (TimePeriod) and methods insertProductOffering() and removeProductOffering(). ProdCatalogProdOffer has a 0..n association with ProductOfferingPrice labeled ProdOfferPriceAdvertisedAs. ProductOffering has a 0..n association with ProductOfferingPrice labeled ProdOfferValuedByPrice. The diagram is labeled M.3190(08)_FIV.3.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +UML Class diagram for Product catalog system view. It includes four classes: ProductCatalog, ProductOffering (from Product Offering ABE), ProdCatalogProdOffer, and ProductOfferingPrice (from Product Offering Price ABE). ProductCatalog has attributes ID (string), type (string), and validFor (TimePeriod). It has methods issueProductCatalog(), recallProductCatalog(), and discontinueProductCatalog(). ProductOffering has a 0..n association with ProductCatalog labeled ProdOfferingPublishedInProdCatalog. ProdCatalog has a 0..n association with ProdCatalogProdOffer labeled ProdOfferingPublishedInProdCatalog. ProdCatalog has a 0..n association with ProductOffering labeled ProdOfferValuedByPrice. ProdCatalogProdOffer has an attribute validFor (TimePeriod) and methods insertProductOffering() and removeProductOffering(). ProdCatalogProdOffer has a 0..n association with ProductOfferingPrice labeled ProdOfferPriceAdvertisedAs. ProductOffering has a 0..n association with ProductOfferingPrice labeled ProdOfferValuedByPrice. The diagram is labeled M.3190(08)\_FIV.3. + +**Figure IV.3 – Product catalog system view (example)** + +Once the system view is stabilized, definition of the implementation view commences. This view is the purview of other NGOSS teams, such as multi-technology operations system interfaces (MTOSI), and other TM Forum technical teams, such as the OSS through Java. + +## IV.2 SID logical and physical perspective + +While the four NGOSS views are important in understanding the development of the SID model, the separation of the SID between a logical perspective and a physical perspective is crucial to implementing the SID. The reason is that multiple physical implementations of the SID can be derived either manually or automatically from a single logical model. This separation is shown in Figure IV.4. + +![Diagram showing the separation of SID logical and physical perspectives. The top row, labeled 'Logical perspective', contains 'Business view' and 'System view' connected by a right arrow. The bottom row, labeled 'Physical perspective', contains 'Deployment view' and 'Implementation view' connected by a left arrow. A vertical dashed line separates the two rows, with a downward arrow from 'System view' to 'Implementation view'. The diagram is labeled M.3190(08)_FIV.4.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +Diagram showing the separation of SID logical and physical perspectives. The top row, labeled 'Logical perspective', contains 'Business view' and 'System view' connected by a right arrow. The bottom row, labeled 'Physical perspective', contains 'Deployment view' and 'Implementation view' connected by a left arrow. A vertical dashed line separates the two rows, with a downward arrow from 'System view' to 'Implementation view'. The diagram is labeled M.3190(08)\_FIV.4. + +**Figure IV.4 – SID logical and physical perspectives** + +At some point during the development of the SID logical perspective, implementation-specific modifications may or may not be made depending on how close a SID modeler wants to keep to a pure logical perspective. These changes may also be made during the initial development of the implementation view. + +# Appendix V + +## Positioning SID to the ITU-T M.1400-series Recommendations + +(This appendix does not form an integral part of this Recommendation) + +Since the initial SID submission includes the SID service and product addenda, it is considered necessary to "position" this submission relative to [b-ITU-T M.1402], *Formalization of data for service management*, in particular, and to the [b-ITU-T M.1400.x] series Recommendations in general. In providing such a positioning function, this appendix explains, at a high level, the relationship of the SID, as a conceptual information model, to the external terminology schemas of the [b-ITU-T M.1400.x] series Recommendations. + +In terms of Appendix III of [ITU-T M.3020], *Comparison with Rec. ITU-T Z.601*, the requirements underlying a conceptual information model and the requirements underlying an external terminology schema fall into two classes: business requirements and specification requirements. SID, as a common information framework, is a member of the first class. As such, the SID model is organized into a taxonomy, or classification of business entities at various levels and associations between these. The scope of the SID business view is to cover a large portion of the information needs of a service provider that can be used as a reference for data that must be shared in implementing eTOM processes. According to [b-ITU-T Z.601], *Data Architecture of one software system*, the SID model would be an example of a concept schema to which multiple external terminology schemas could be mapped. + +As a member of the specification class, the [b-ITU-T M.1400.x] series Recommendations focus on specification of the external terminology and grammar as perceived by the end users. The specification requirements may include requirements to support end-user interaction at their human-computer interfaces. Some of these requirements may specify syntactical requirements to be supported over any management interface. Syntactical requirements correspond to external terminology schemata of the data architecture as described in [b-ITU-T Z.601]. + +External terminology schemas define identifiers, name spaces, name bindings and other data that are to be efficient in use for the end users. This may lead to new object classes and relationships between object classes as compared to a pure conceptual approach. Hence, conceptual definitions of the information to be conveyed by management interfaces are not sufficient, as data syntax requirements may lead to additions and modifications of the conceptual definitions. (Methods for design of efficient end user data are found in [b-ITU-T Z.352], *Data oriented human-machine interface specification technique – Scope, approach and reference model*.) + +Given this high level distinction between conceptual models and external terminology schemas, and their different usages, it is not considered to be essential that the current SID model be harmonized with the [b-ITU-T M.1400.x] series Recommendations. There is evidence that an attempt to informally map ITU-T M.1401 to the SID model revealed far more differences than similarities between the two, as one would expect of specifications developed in different environments for different purposes. A true harmonization effort would require that the SID model be revised to include new object classes and relationships between object classes as specified in the [b-ITU-T M.1400.x] series Recommendations and vice versa. + +## Bibliography + +- [b-ITU-T M.1400.x] Recommendation ITU-T M.1400.x-series, *Designations for interconnections among operators' networks*. +<> +- [b-ITU-T M.1402] Recommendation ITU-T M.1402 (2007), *Formalization of data for service management*. <> +- [b-ITU-T Z.352] Recommendation ITU-T Z.352 (1993), *Data oriented human-machine interface specification technique – Scope, approach and reference model*. <> +- [b-ITU-T Z.601] Recommendation ITU-T Z.601 (2007), *Data architecture of one software system*. <> +- [b-Abstract] Woolf, Bobby, *The Abstract Class Pattern* +<> +- [b-ACIA] Alliance Common Information Architecture (AT&T, BT & Concert) version 3.1, 15 Dec. 2000. +- [b-Distilled] Fowler, M., *UML Distilled: A Brief Guide to the Standard Object Modeling Language*. +- [b-DDD] Evans, Eric, *Domain-Driven Design: Tackling Complexity in the Heart of Software*, ISBN: 0321125215 (Aug. 2003 release). +- [b-DEN] Directory Enabled Networks (DEN). Strassner, J., *Directory Enabled Networks*, Macmillan Technical Publishing, ISBN 1-57870-140-6. +- [b-Design] Stevens, WP, Myers, GJ & Constantine, LL (1974), *Structured Design*, IBM Systems Journal, Vol. 13, No. 2. +- [b-FEA] US Government Federal Enterprise Architecture. +<> +- [b-IBM] IBM Research Design Patterns Web Pages. +<> +- [b-ISO 19108] ISO 19108:2002, *Geographic information – Temporal schema*. +<[http://www.iso.org/iso/iso\\_catalogue/catalogue\\_tc/catalogue\\_detail.htm?csnumber=26013](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=26013)> +- [b-Java] Coad, Peter, Lefebvre, Eric, De Luca, Jeff (1999), *Java Modeling in Color with UML*, Prentice Hall PTR. +- [b-Language] Christopher Alexander, *A Pattern Language: Towns, Buildings, Construction* Sara Ishikawa, Murray Silverstein. +- [b-Patterns-1] Fowler, Martin, *Analysis Patterns – Reusable Object Models*, ISBN 0-201-89542-0 <> +- [b-Patterns-2] Larman, Craig, *Applying UML and Patterns*, Second Edition ISBN 0-13-095004-1. +<[http://www.craiglarman.com/book\\_applying\\_2nd/Applying\\_2nd.htm](http://www.craiglarman.com/book_applying_2nd/Applying_2nd.htm)> +- [b-Patterns-3] Gamma, E., Helm, R., Johnson, R. and Vlissides, J. (Oct. 1994), *Design Patterns: Elements of Reusable Object-Oriented Software*, Addison Wesley, Reading, MA. + +- [b-Roles] Fowler, Martin, *Dealing with Roles*. +<> +- [b-Rules] Moriarty, Terry, *The Grammar of Business Rules (3 parts)*. +<> +- [b-TMF GB922 primer] TM Forum GB922, *Shared Information/Data (SID) Model*. +Addendum 0 – SID Primer, Version 1.1. +<> +- [b-UML] Booch, Rumbaugh & Jacobson, *The Unified Modeling Language User Guide*. +- [b-Zachman] Zachman Framework . Various Articles +by John A Zachman . + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.32-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.32-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.32-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.32-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.32-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ab035c8f49f154d7edbd1473085361956918afc7 --- /dev/null +++ b/marked/M/T-REC-M.32-198811-I_PDF-E/raw.md @@ -0,0 +1,183 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt and the letters 'ITU'. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.32** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **MAINTENANCE: INTRODUCTION AND GENERAL PRINCIPLES** + +## --- **PRINCIPLES FOR USING ALARM INFORMATION FOR MAINTENANCE OF INTERNATIONAL TRANSMISSION SYSTEMS AND EQUIPMENT** + +**ITU-T Recommendation M.32** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation M.32 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **PRINCIPLES FOR USING ALARM INFORMATION FOR MAINTENANCE OF INTERNATIONAL TRANSMISSION SYSTEMS AND EQUIPMENT** + +### **1 General** + +1.1 This Recommendation presents the general principles for employing those maintenance features and capabilities of international transmission systems and equipment which are based on alarm information. + +It describes a set of strategies, in addition to the maintenance philosophy in Recommendation M.20, to use these alarm-based features and capabilities in an effective and efficient manner. This Recommendation is also intended to address the interactions between alarms of digital and analogue transmission systems and equipments. + +Alarm interactions for mixed analogue/digital transmission systems and equipment are under study. + +1.2 While this Recommendation discusses the strategy to employ these features and capabilities, the actual arrangements to provide and use them are left to the discretion of the Administrations. + +### **2 Types of alarms and related messages** + +Alarm information may be categorized as follows: + +- a) Prompt maintenance alarm (PMA); +- b) Deferred maintenance alarm (DMA); +- c) Maintenance event information (MEI). + +Definitions of PMA, DMA and MEI are found in Recommendation M.20, § 5.4.1. + +### **3 Guidance for using alarm information** + +#### **3.1 Hierarchy** + +The alarm information from transmission systems and equipment is based on a hierarchy of: + +- a) alarms and indications displayed on failed equipment or systems, +- b) office audible/visual alarms which alert local staff, and +- c) remote information which appears on a display monitored by centralized maintenance staff which is not collocated with the failed equipment or systems. + +This alarm hierarchy is used in failure localization, either for a maintenance entity, or for specific equipment within a maintenance entity. + +#### **3.2 Display** + +Alarm information can be displayed to help in localization in different ways, such as: + +- a) locally – on the equipment, +- b) on site – in the same building as the equipment, or +- c) remotely – at a building not collocated with the equipment. + +Both localized and on-site displays are used by on-site maintenance staff. Remote displays are normally used either for coverage during periods when a building is not staffed or to obtain a wider maintenance perspective from a single location on a possibly large number of systems. + +For example, the remote maintenance strategy of § 3.5 can be used first to localize a trouble to a maintenance entity. Then, maintenance staff can obtain further remote (or otherwise made available) information to localize the failure to specific equipment. After this, the maintenance staff can use the local alarm maintenance strategy of § 3.7 to isolate and correct the failure. + +#### 3.3 *Considerations for local or remote alarm monitoring* + +Alarm information may be displayed locally on equipment, or on-site in the same building as the monitored equipment using external monitoring equipment. Use of such displays implies that maintenance staff must be present or visit the site to observe the information. + +Remote alarm monitoring provides a means for staff at a centralized location, not collocated with the transmission systems and equipment, to monitor them. + +The choice between local and remote monitoring and the degree of centralization and automation employed depends on a number of factors, including the type of maintenance organization, the expected failure rates and the physical locations involved. + +#### 3.4 *Reducing unnecessary maintenance activity* + +When an equipment failure requiring some maintenance activity occurs, alarms should, if possible, be generated by the maintenance entity of which the equipment is part. The general rule is that maintenance activities should be directed only at the maintenance entity in which the failure exists. Thus, techniques should be used which prevent unwanted alarms (and the resulting unnecessary maintenance activity) beyond the maintenance entity in which a failure exists. Also, maintenance entities downstream of the failed maintenance entity should have a means of recognizing that a failure has occurred upstream, as part of the aim of reducing maintenance activity. Provision may be made at a maintenance entity to indicate an upstream failure and/or inhibit unnecessary actions. For example, in digital transmission systems and equipment, this may be accomplished by the use of: + +- alarm indication signal (AIS); +- service alarm (SA); +- upstream failure indication (UFI). + +For definition of AIS, SA and UFI see Recommendation M.20, § 5.4.2. + +#### 3.5 *Considerations for remote maintenance alarm information* + +Remote maintenance alarm information provides a means for staff not collocated with transmission systems and equipment to nonetheless monitor and control them. The monitored equipment may be located in unstaffed locations. This section recommends the principles which should be followed if remote alarm information is provided. + +3.5.1 Identification and localization are required to determine what the response should be: start restoration of service by using alternate routes, dispatch for maintenance of failed equipment, or wait and gather further information to better identify the nature and/or seriousness of the problem. + +3.5.2 The decision to send maintenance staff is based upon the maintenance philosophy in Recommendation M.20, § 1.1. + +#### 3.6 *Maintenance alarm arrangements* + +Maintenance alarm arrangements are based on the use of audible/visual alarm systems. These systems provide alarms which direct on-site staff to the location of the failed equipment. The objective when providing audible/visual alarm indications is that they should permit on-site maintenance staff to detect and locate the source of failure in a timely fashion in line with other priorities. Note that distinctive sounds may be used to differentiate audible alarms. Also, visual signals should be able to direct maintenance staff to the failed equipment or to a point where the location of the failure can be determined. + +#### 3.7 *Use of local alarm information* + +3.7.1 Local alarm information is concerned with alerting on-site maintenance staff to equipment failures. The local maintenance activities usually entail the location and correction of the failure. To carry this out effectively and efficiently, information which helps direct the maintenance staff to the failure should be provided directly from the failed equipment. + +3.7.2 Local alarm information is derived from local failure indications, together with the maintenance staff use of tests and relevant documentation. This should be sufficient to localize the failure within the failed equipment. + +3.7.3 Note that a further purpose of local failure indications is to provide a backup for remote indications, in the event that there is a failure in communications between monitored equipment and a central monitoring location. + +### 4 **General considerations** + +#### 4.1 *Monitoring* + +In general, failures of equipment should be detected by continuous (or nearly continuous) automatic monitoring, as opposed to monitoring or testing involving human intervention. Note that shared, but automatic, monitoring is considered nearly continuous. Continuous (or nearly continuous) monitoring is often made feasible by virtue of advances in technology, and by virtue of the large number of circuits affected or jeopardized by a transmission system failure. In addition, continuous (or nearly continuous) monitoring is faster, more reliable, and less labor intensive than alternative monitoring strategies. + +#### 4.2 *Uses of PMA, DMA and MEI* + +4.2.1 When reporting or displaying alarms either locally or remotely, it is important to distinguish between PMA/DMA indications and MEI indications. PMA/DMA indications are those which cause maintenance staff to be alerted (e.g., by ringing a bell), and MEI indications are those which are displayed in response to staff interrogations or in conjunction with other indications (e.g., alarms) which are spontaneously generated. + +4.2.2 These distinctions should be defined for each transmission system and equipment in order for alarm indications to be properly processed. These distinctions may be of particular importance when using remote alarm surveillance systems, where large numbers of PMA, DMA and MEI indications must be dealt with by maintenance staff. + +4.2.3 MEI indications may be used as aids in failure localization or verification of remote operations (such as remote control of protection switching) under manual control. The information conveyed by MEI indications may also be used to supplement that conveyed by PMA/DMA indications. + +4.2.4 Note that detection of failures is accomplished by having suitable monitors associated with each maintenance entity. The criteria for activating alarm indications at a maintenance entity should generally be based on limits on the maintenance entities, which will generally be related to the performance objectives of the transmission systems. + +4.2.5 To aid in the dispatch of personnel, remote indications should include the following information: + +- a) identification of the failed transmission system or equipment and nature of trouble condition, +- b) distinction between service-affecting failures and non- service-affecting failures where such a distinction is possible, and +- c) severity of the failure which has occurred. + +#### 4.3 *Transmission and presentation of alarm information* + +4.3.1 There are two basic interface arrangements for transferring alarm information between monitored and monitoring equipment: + +- a) discrete, parallel, and +- b) serial data. + +The parallel method of data gathering and control uses discrete wires for implementing each function. The serial data method of gathering and control uses a single pair of wires to carry serial (in time) data points, rather than individual wires for each point. Much new telecommunications equipment is “intelligent”, that is, it employs microprocessor circuit design, which lends itself more readily to serial data transfer rather than to parallel. + +4.3.2 The presentation of alarm information can be: + +- a) visual (lamp, LED, printer or display indication), and/or +- b) audible (bell, tones or voice). + +The alarm information may be presented as: + +- a) an indication at an alarm interface (e.g., contact function, d.c. signal) and/or +- b) an alarm message on the man-machine interface. + +This alarm message may contain: + +- i) heading (name of maintenance entity, date, time, etc.), +- ii) category of failure (PMA, DMA, MEI), +- iii) description of failure, which may include the cause of failure, location of the failed item(s) and other information which can be useful in locating the failed item(s), +- iv) possible consequences of the failure, and +- v) automatic actions performed by the network (internal protection and service actions). + +#### 4.4 *Possible use of MEIs* + +Administrations using MEI may desire to alert maintenance staff by means of a PMA or DMA. The criteria and arrangements1) for generating PMA or DMA based on analysis of MEI are left to their discretion. + +#### 4.5 *Considerations for protection switching and control* + +To meet transmission system availability objectives or maintenance criteria, transmission systems may be provided with protection equipment. Such equipment, if provided, may have the following capabilities: + +- a) automatic protection switching of service from failed regular equipment to working standby equipment, +- b) automatic protection switching of service to overcome transmission degradation caused, for example, by radio path fading, +- c) remotely controlled protection switching of service between regular equipment and standby equipment, and/or +- d) locally controlled protection switching of service between regular equipment and standby equipment. + +--- + +1) The arrangements to generate such information may take place in the transmission system or in auxiliary supervision systems. \ No newline at end of file diff --git a/marked/M/T-REC-M.320-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.320-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..437c54d5eef2295987ccc3f17a5cc30278679cd2 --- /dev/null +++ b/marked/M/T-REC-M.320-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305c3556781849c830e959cc999ddbad84b953253da5e0b6761c2735b83a773d +size 7362 diff --git a/marked/M/T-REC-M.320-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg b/marked/M/T-REC-M.320-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a703548cb0f1b4767f79989ad430f66fa99c98c --- /dev/null +++ b/marked/M/T-REC-M.320-198811-I_PDF-E/5d92d5c9cc01a262b0389d138caa9aea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:417b1c479f84238092ec317d2c173afb8fcfdb0e73973ee93dd73c2fc56168dd +size 27292 diff --git a/marked/M/T-REC-M.320-198811-I_PDF-E/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg b/marked/M/T-REC-M.320-198811-I_PDF-E/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c45c72d040a72bcae1a2322d313279d2a4947fd2 --- /dev/null +++ b/marked/M/T-REC-M.320-198811-I_PDF-E/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5755a2e14ef3fc982933b2ed3235f21294282415efc5933eab342e84b7c5157 +size 31551 diff --git a/marked/M/T-REC-M.320-198811-I_PDF-E/de10b5831c09191aadec04dfe0f9e7c3_img.jpg b/marked/M/T-REC-M.320-198811-I_PDF-E/de10b5831c09191aadec04dfe0f9e7c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e88b06af28efca1d56202af647717856ad8bda9 --- /dev/null +++ b/marked/M/T-REC-M.320-198811-I_PDF-E/de10b5831c09191aadec04dfe0f9e7c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9afd79828573eb46153fdd8f0cc55a49342009276374c775c5cbc6998e2d1073 +size 23879 diff --git a/marked/M/T-REC-M.320-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.320-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d0d5f24e3e1abd9edb756ff15db20af52a9706a1 --- /dev/null +++ b/marked/M/T-REC-M.320-198811-I_PDF-E/raw.md @@ -0,0 +1,110 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.320** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**NUMBERING OF THE CHANNELS +IN A GROUP** + +**ITU-T Recommendation M.320** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.320 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## NUMBERING OF THE CHANNELS IN A GROUP + +### 1 General + +The position of a channel within a group is identified by a number starting from 1, the numbers of the different channels being taken in order of frequency in the basic group frequency band. + +A channel is said to be *erect* within a group when the frequencies in the group-frequency band corresponding to the audio-frequencies in the channels *ascend* in the same relative order as those in the channels forming the group. + +Similarly, a channel is said to be *inverted* within a group when the frequencies in the group-frequency band descend in the same relative order as the ascending order of the frequencies in the channels. + +A group, supergroup, etc., is said to be *erect* when all of its channels are *erect* and is said to be *inverted* when all of its channels are *inverted*. + +### 1.1 8 channel group + +Basic group B is *inverted*. The channels will be numbered from 1 to 8 in descending order of frequency within the group-frequency range. (See the recommended arrangement in Recommendation G.234 [1].) + +The numbering is as shown in Figure 1/M.320. + +### 1.2 12 channel group + +Basic group B is *inverted*. The channels will be numbered from 1 to 12 in descending order of frequency within the group-frequency range. + +The numbering is as shown in Figure 2/M.320. + +### 1.3 16 channel group + +Channels of a 16 channel group are normally assembled in the basic group B frequency range. The channels are numbered from 1 to 16 in descending order of frequency within the basic group B frequency band, the odd-numbered channels being *erect* and the even-numbered channels being *inverted*. It is therefore not possible in this case to speak of an *erect* or *inverted* group. + +The numbering is as shown in Figure 3/M.320. + +![Figure 1/M.320: Numbering of channels in 8 channel group. The diagram shows a frequency spectrum from 60 kHz to 108 kHz. A bracket labeled 'Basic group B' spans from 66 kHz to 102 kHz. Below the spectrum, 'Channel No.' is labeled with numbers 8, 7, 6, 5, 4, 3, 2, 1 from left to right. Below that, 'Frequency kHz' is labeled with values 60, 66, 72, 78, 84, 90, 96, 102, 108. The channels are represented by sawtooth-like shapes between the frequency lines.](de10b5831c09191aadec04dfe0f9e7c3_img.jpg) + +Figure 1/M.320: Numbering of channels in 8 channel group. The diagram shows a frequency spectrum from 60 kHz to 108 kHz. A bracket labeled 'Basic group B' spans from 66 kHz to 102 kHz. Below the spectrum, 'Channel No.' is labeled with numbers 8, 7, 6, 5, 4, 3, 2, 1 from left to right. Below that, 'Frequency kHz' is labeled with values 60, 66, 72, 78, 84, 90, 96, 102, 108. The channels are represented by sawtooth-like shapes between the frequency lines. + +FIGURE 1/M.320 + +CCITT - 36660 +d01-sc + +Numbering of channels in 8 channel group + +![Diagram of a 12-channel group showing channel numbers 12 down to 1 and their corresponding frequencies in kHz (60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100, 104, 108).](5d92d5c9cc01a262b0389d138caa9aea_img.jpg) + +The diagram shows a series of 12 sawtooth-like shapes, each representing a channel. Above the shapes is a bracket labeled "Basic group B". Below the bracket, "Channel No." is followed by numbers 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1. Below the numbers, "Frequency kHz" is followed by the values 60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100, 104, 108. Each number in the "Channel No." row is positioned above the start of a sawtooth wave, and each frequency value is positioned below the end of the corresponding sawtooth wave. + +Diagram of a 12-channel group showing channel numbers 12 down to 1 and their corresponding frequencies in kHz (60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100, 104, 108). + +CCITT - 36670 +d02-sc + +FIGURE 2/M.320 + +Numbering of channels in 12 channel group + +![Diagram of a 16-channel group showing channel numbers 16 down to 1 and their corresponding frequencies in kHz (60, 63, 66, 69, 72, 75, 78, 81, 84, 87, 90, 93, 96, 99, 102, 105, 108).](b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg) + +The diagram shows a series of 16 sawtooth-like shapes, each representing a channel. Above the shapes is a bracket labeled "Basic group B". Below the bracket, "Channel No." is followed by numbers 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1. Below the numbers, "Frequency kHz" is followed by the values 60, 63, 66, 69, 72, 75, 78, 81, 84, 87, 90, 93, 96, 99, 102, 105, 108. Each number in the "Channel No." row is positioned above the start of a sawtooth wave, and each frequency value is positioned below the end of the corresponding sawtooth wave. + +Diagram of a 16-channel group showing channel numbers 16 down to 1 and their corresponding frequencies in kHz (60, 63, 66, 69, 72, 75, 78, 81, 84, 87, 90, 93, 96, 99, 102, 105, 108). + +CCITT - 36680 +d03-sc + +FIGURE 3/M.320 + +Numbering of channels in 16 channel group + +## **Reference** + +- [1] CCITT Recommendation *8-channel terminal equipments*, Orange Book, Vol. III-1, Rec. G.234, ITU, Geneva, 1977. \ No newline at end of file diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/M/T-REC-M.3200-199704-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ba61033910c2a87546f51aa6ffcd730e1ffdd96 --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b099e757282a302743c3cc2eee95561d1d57ebfb1b2507cc8c6df8f31d1ae15 +size 67153 diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3200-199704-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef217a35c606f996aec24fcc6d998d1acd256f8 --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:247ac7e691d9b397de6c25536f4e75ec7745dc147c743ea9971188d8020f638a +size 8239 diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/M/T-REC-M.3200-199704-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e325f41d9dec1d0eb1356e08e495dcd1b91ef221 --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64cf618474a44029fb58f27961f21ec70f3171e05ccffa7ea5eb65e9a04f57d7 +size 110277 diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/M/T-REC-M.3200-199704-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14da8f84867980af4a6dd7fe878489395cbaded3 --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07af0cc14468713cf19931e69c73bb34ec7067d0fa58c168459826e99304ec87 +size 66255 diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3200-199704-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5343acc99f85ad70db497b98171e45debbe8f57c --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e36224a5d1c1f87ef958e757f0759cc4f16bc843265abd2aee4ca467ea8a6c49 +size 54325 diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3200-199704-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec1032288b2fd0eef5e855a491567991e7710f23 --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4503d27e685af55533ce842fe56cbc514fb1481da9040da9e0eaf08b51fa8ad +size 72941 diff --git a/marked/M/T-REC-M.3200-199704-I_PDF-E/raw.md b/marked/M/T-REC-M.3200-199704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..60eaa8dcc19ccee85ed1319600588553964b15aa --- /dev/null +++ b/marked/M/T-REC-M.3200-199704-I_PDF-E/raw.md @@ -0,0 +1,827 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3200** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/97) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**TMN management services and +telecommunications managed areas: overview** + +ITU-T Recommendation M.3200 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.3200** + +# **TMN MANAGEMENT SERVICES AND TELECOMMUNICATIONS MANAGED AREAS: OVERVIEW** + +## **Summary** + +This Recommendation provides an overview of the M.3200-Series. It describes the structuring principles of the M.3200-Series and lists the currently agreed Recommendations. + +The concepts of "Telecommunications Managed Area" and "Telecommunications Management" are introduced. A summary description of each is provided, as well as a matrix defining their relationships. These Recommendations are intended as the basis for the corresponding modelling and protocol work on the TMN interfaces. They also provide a basis from which an Administration might plan the evolution of its Telecommunications Management as defined in 3.2 of this Recommendation. + +The Recommendation is completed through a summary of a hypothetical example of the management context of a matrix crosspoint, i.e. Maintenance Management of Switched Telephone Network. + +### **Source** + +ITU-T Recommendation M.3200 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 19th of April 1997. + +### **Keywords** + +Object Modelling, Telecommunications Managed Areas, Telecommunications Management, Telecommunications Management Network, Management Service, Task Information Base. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|------|-------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 2.1 | CCITT and ITU-T Recommendations ..... | 1 | +| 2.2 | ITU-R Recommendation..... | 2 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations..... | 3 | +| 5 | Telecommunications Managed Areas..... | 4 | +| 5.1 | Switched Telephone Network..... | 4 | +| 5.2 | Mobile Communications Network..... | 5 | +| 5.3 | Switched Data Network..... | 5 | +| 5.4 | Intelligent Network..... | 6 | +| 5.5 | Common Channel Signalling System No. 7 Network ..... | 6 | +| 5.6 | N-ISDN..... | 7 | +| 5.7 | B-ISDN ..... | 8 | +| 5.8 | Dedicated and Reconfigurable Circuits Network ..... | 8 | +| 5.9 | TMN..... | 8 | +| 5.10 | IMT-2000 (formerly FPLMTS) ..... | 9 | +| 5.11 | Access and Terminal Equipment Network ..... | 10 | +| 5.12 | Transport Network..... | 10 | +| 5.13 | Infrastructure..... | 10 | +| 6 | TMN Management Services ..... | 10 | +| 6.1 | Customer Administration..... | 11 | +| 6.2 | Network Provisioning Management ..... | 11 | +| 6.3 | Work Force Management ..... | 12 | +| 6.4 | Tariff, Charging and Accounting Management..... | 12 | +| 6.5 | Quality of Service and Network Performance Management ..... | 12 | +| 6.6 | Traffic Measurements and Analysis Administration ..... | 13 | +| 6.7 | Traffic Management..... | 13 | +| 6.8 | Routing and Digit Analysis Administration ..... | 13 | +| 6.9 | Maintenance Management..... | 14 | +| 6.10 | Security Administration..... | 14 | +| 6.11 | Logistics Management..... | 14 | + +| | Page | | +|--------------|----------------------------------------------------------------------------|----| +| 7 | Management Services × Telecommunications Managed Areas Matrix ..... | 15 | +| 7.1 | Relationship between this Recommendation and Recommendation M.3020 ..... | 15 | +| 7.2 | M.3200-Series..... | 16 | +| 8 | Relationships between TMN Management Services and existing Recommendations | 16 | +| Appendix I – | Example of GDMS application..... | 16 | +| I.1 | Management Service Description..... | 17 | +| I.2 | Management goals ..... | 17 | +| I.3 | Management Context Description ..... | 17 | +| I.3.1 | Dynamic view of Management Context..... | 17 | +| I.3.2 | Resources..... | 17 | +| I.3.3 | Roles ..... | 18 | +| I.3.4 | TMN Management Functions Sets and Set Groups ..... | 19 | +| I.4 | Architecture..... | 19 | +| I.5 | Scenarios ..... | 21 | + +# **TMN MANAGEMENT SERVICES AND TELECOMMUNICATIONS MANAGED AREAS: OVERVIEW** + +*(1992; revised in 1997)* + +# **1 Scope** + +This Recommendation is intended to provide an overview of Telecommunications Management Network (TMN) Management Services and Telecommunications Managed Areas. It provides the framework for the specification of protocols, messages, management information, etc. for TMN interfaces. The TMN Management Services are described from the TMN users' perspective and are independent of the protocols, messages and information models chosen. They will therefore assist in the smooth transition from a non-TMN to a TMN environment. + +It should be noted that flexibility will be required in the definition of TMN Management Services to enable additional requirements to be accommodated as they are identified. + +To avoid discrepancies and duplications, this Recommendation establishes the structuring principles (e.g. numbering, naming, etc.) for the M.3200-Series of Recommendations. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +## **2.1 CCITT and ITU-T Recommendations** + +- E.410 through E.414, *International network management*. +- E.420 through E.428, *Checking the quality of the international telephone service*. +- E.500 through E.721, *Traffic engineering*. +- E.800 through E.880, *Quality of telecommunication services: concepts, models, objectives, dependability planning*. +- ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network*. +- ITU-T Recommendation M.3020 (1995), *TMN interface specification methodology*. +- ITU-T Recommendation M.3100 (1995), *Generic network information model*. +- ITU-T Recommendation M.3400 (1997), *TMN management functions*. +- CCITT Recommendation Q.500 (1988), *Digital local, combined, transit and international exchanges, introduction and field of application*. +- ITU-T Recommendation Q.512 (1995), *Digital exchange interfaces for subscriber access*. +- ITU-T Recommendation Q.513 (1993), *Digital exchange interfaces for operations, administration and maintenance*. + +- ITU-T Recommendation Q.521 (1993), *Digital exchange functions*. +- ITU-T Recommendation Q.541 (1993), *Digital exchange design objectives – General*. +- ITU-T Recommendation Q.542 (1993), *Digital exchange design objectives – Operations and maintenance*. +- ITU-T Recommendation Q.750 (1997), *Overview of Signalling System No. 7 management*. +- ITU-T Recommendation Q.751.1 (1995), *Network element management information model for the Message Transfer Part*. +- ITU-T Recommendation Q.752 (1997), *Monitoring and measurements for Signalling System No. 7 networks*. +- ITU-T Recommendation Q.753 (1997), *Signalling System No. 7 management functions MRVT, SRVT and CVT and definition of the the OMASE-user*. +- ITU-T Recommendation Q.754 (1997), *Signalling System No. 7 management Application Service Element (ASE) definitions*. +- ITU-T Recommendation Q.821 (1993), *Stage 2 and stage 3 description for the Q3 interface – Alarm surveillance*. + +## 2.2 ITU-R Recommendation + +- M.817, *Basic Functional Model for IMT-2000*. + +# 3 Definitions + +This Recommendation defines the following terms. + +**3.1 telecommunications managed area:** Telecommunications Managed Area is a set of telecommunications resources, logically and/or physically involved with the telecommunications services, that makes it possible to provide, partly or completely, these services to the customers and is chosen to be managed as a whole. + +Examples: Switched Data Network + +Switched Telephone Network + +**3.2 telecommunications management:** Telecommunications Management, overall, is the result of integrating the management of the several Telecommunications Managed Areas of a company in order to maximize the quality to the telecommunications customers and the telecommunications resources productivity of a specific company, through performing the Management Services needed. The business objective of Telecommunications Management is to continually improve quality to the customer and operational productivity. Measures of continual improvement include: + +- faster response to customers services demand; +- faster elimination of root causes of productivity degradation; +- improved accuracy of the bills and faster reception of them. + +The objectives of Management Services are to support, through re-engineered processes and automation, these business objectives. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|----------|----------------------------------------------------------| +| AAL | ATM Adaptation Layer | +| ADM | Add-Drop Multiplex | +| ASE | Application Service Element | +| ATM | Asynchronous Transfer Mode | +| BS | Base Station | +| FPLMTS | Future Public Land Mobile Telephone System | +| HTR | Hard-to-Reach | +| IDF | Intermediate Distribution Frame | +| IMT-2000 | International Mobile Telecommunications-2000 | +| IP | Intelligent Peripheral | +| ISUP | ISDN User Part | +| ME | Maintenance Entity | +| MIL-STD | Military Standard | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MTBF | Mean Time Between Failures | +| MTP | Message Transfer Part | +| OMAP | Operations, Maintenance, Administration and Provisioning | +| QOS | Quality of Service | +| RBS | Radio Base Stations | +| SCCP | Signalling Connection Control Part | +| SCE | Switching and Control Exchanges | +| SCP | Service Control Point | +| SDH | Synchronous Digital Hierarchy | +| SMDS | Switched Multimegabyte Digital System | +| SPC | Stored Program Control | +| SP | Signalling Points | +| SSP | Service Switching Point | +| STP | Signalling Transfer Points | +| TUP | Telephone User Part | +| VOD | Voice on Demand | + +# **5       Telecommunications Managed Areas** + +Although almost all the Managed Area names have the word "Network" attached to them, the management requirements must include Business, Service, Network and Network Element management needs. The boundaries established through 5.1 up to 5.13 do not exclude the need of the integration established in the definition of Telecommunications Management, given in clause 3. The following are examples of the needed integration: + +- a)       All Telecommunications Services use resources of: Access and Terminal Equipment Network, Transport Network and Infrastructure. +- b)       Packet Switched Data Services use Switched Telephone Network as part of their access. +- c)       Freephone (e.g. 800 Service) use IN, Switched Telephone Network and ISDN resources to be accomplished. +- d)       Cellular Telephone Services are highly integrated with Switching Telephone Services. + +The management integration of the different Managed Areas and Management Services, within the OS's of a given TMN, is not subject of standardization. + +A Telecommunications Managed Area can range from a single piece of telecommunications equipment up to a very complex network. Depending on its network complexity, each company will organize its Telecommunications Management in a different way. This means that there is no standard to define which will be the Telecommunications Managed Areas of a specific company, when considered from a Management standpoint. The list below is a possible example. + +## **List of Telecommunications Managed Areas** + +- 1)       Switched Telephone Network; +- 2)       Mobile Communications Network; +- 3)       Switched Data Network; +- 4)       Intelligent Network; +- 5)       Common Channel Signalling System No. 7 Network; +- 6)       N-ISDN; +- 7)       B-ISDN; +- 8)       Dedicated and Reconfigurable Circuits Network; +- 9)       TMN; +- 10)       IMT-2000 (formerly FPLMTS); +- 11)       Access and Terminal Equipment Network; +- 12)       Transport Network; +- 13)       Infrastructure. + +NOTE – The above list is intended to apply to public and private networks. It is not intended to be exhaustive. Further revisions of this Recommendation may have additions. + +## **5.1       Switched Telephone Network** + +The Switched Telephone Network is the set of telephone exchanges or telephone switching nodes or simply switches that support the telephone service. These are switched circuit nodes. Nowadays, a number of different voice and data services flow through the Switched Telephone Network. To + +exemplify, we can mention circuit switched access to: Packet Switched Data Network, Fax, Intelligent Network Services, etc. + +The distribution frames do not belong to the Switched Telephone Network. They are part of Access and Terminal Equipment Network or part of the Transport Network. The boundaries of the exchanges are the switching part connected to the transmission facilities. The physical resources that constitute an exchange can receive different names, depending on the manufacturer, but there are some common designations such as: incoming trunks, outgoing trunks, registers, senders, receivers, switching matrix, controllers, markers, signalling bus, O&M, etc. The same happens when we consider the logical resources. There is a trend for the exchanges to be more and more software-based. The set of software modules depends on the exchange architecture that can be more or less distributed. Independent from the physical or logical architecture, there is a number of common functionalities, needed for call routing, transmission, signalling, charging and management, etc. + +The exchanges that are connected to the Access and Terminal Equipment Network are called Local Exchanges. The switching nodes used to interconnect other switches are called tandem or transit switches. The exchanges can be analogue or digital, depending on the nature of the switched signal. A number of different technologies have been applied in the field and among them we can mention: Step-by-Step, Rotary, Crossbar, Crosspoint, Analogue-SPC (Stored Program Controlled) and Digital-SPC. + +## **5.2 Mobile Communications Network** + +The Mobile Communications Network is the set of dedicated or non-dedicated switching nodes and some associated RBS (Radio Base Stations or Cell Sites) needed for providing voice and data Mobile Services. In the case of non-dedicated nodes, they are part of the switched network involved. + +The switching nodes associated with Mobile Services are usually named Switching and Control Exchanges (SCE) and as they are digital equipment they should be connected to the Switched Telephone Network by digital links (e.g. PCM, fibre-optics, etc.). The RBS cover a limited physical area or region known as "CELL". The roaming signalling and handoff resources belong to this managed area. + +Depending on the adopted technology for the Mobile Communications Network, the connection between SCE and RBS may use optical fibre or radio links. The RBS should use radio links to connect themselves to mobile stations. There is a limited number of radio frequencies available for each RBS. + +## **5.3 Switched Data Network** + +The Switched Data Network is the set of switching nodes needed for the Data Switching Business. The distributing frames do not belong to Data Switched Network. They are part of Access and Terminal Equipment Network or part of the Transport Network. The boundaries of the nodes are the switching part connected to the transmission facilities. The physical resources that constitute a node can receive different names, depending on the manufacturer, but Processor Element (PE) and Peripheral Interface (PI) are somewhat common designations. The same happens when we consider the logical resources. Most of the capabilities are software-implemented. The set of software modules depends on the node manufacturer, although most of them have adopted a distributed architecture. Independent from the physical or logical architecture, there is a number of common capabilities, because of the commonality in services. For instance, we can mention the following access services and protocols: + +ITU-T Recommendations X.25, X.32, X.75, X.28, X.29, ISDN (X.31) and frame relay. + +## 5.4 Intelligent Network + +Intelligent Network (IN) is an architectural concept for the operation and provision of new services which is characterized by: + +- centralized service logic; +- extensive use of information processing techniques; +- efficient use of network resources; +- modularization and reusability of network functions; +- integrated services creation and implementation by means of modularized reusable network functions; +- flexible allocation of network functions to physical entities; +- portability of network functions among physical entities; +- standardized communication between network functions via service independent interfaces; +- some user-specific service attributes that can be controlled by the users themselves; +- some subscriber-specific service attributes that can be controlled by the subscribers themselves; +- standardized management of service logic. + +IN is applicable to a wide variety of networks, including but not limited to: switched telephone network, mobile communications network, switched data network and integrated services digital network. IN supports a wide variety of services such as: freephone, calling credit card, and virtual private network, and utilizes bearer services. + +The design and description of the IN architecture have a framework given by its IN Conceptual Model, which consists of four abstract view planes: Service plane, Global Functional plane, Distributed Functional plane and Physical plane. IN physical architecture is based upon building blocks such as Service Control Point (SCP), Service Switching Point (SSP), Intelligent Peripheral (IP), etc. + +## 5.5 Common Channel Signalling System No. 7 Network + +Common Channel Signalling System (CCSS) No. 7 Network is a signalling network interconnecting Signalling Points (SP) and Signalling Transfer Points (STP), by means of signalling link-sets. The SPs are the originating and destination points. The STPs act as transit exchanges for signalling purposes. A link set is a number of signalling links that directly interconnect two signalling points. A group of links within a link-set that have identical characteristics is called a link group. All these resources are normally within the telephone exchanges and the transport network, and through them the CCSS is optimised for operation in digital telecommunication networks with stored program controlled (SPCs) exchanges. They form a special signalling network that can support applications such as: PSTN, ISDN, Interaction with Network Databases, Intelligent Network, Public Land Mobile Network and Telecommunications Management Network (TMN). Common Channel Signalling System No. 7 can be regarded as a form of switched data network, which is specialised for various types of application and information transfer between processors in the telecommunications network. + +The logical resources are the implementation of the functional blocks, as shown in Figure 1. The term "users" in this figure refers to any functional entity that utilises the transport capability provided by the Message Transfer Part. Only the resources dedicated to MTP and SCCP belong to CCSS. The physical and logical resources do not belong to CCSS and are covered by the other blocks of the related Telecommunications Managed Areas. + +![Architecture of S.S. No. 7 diagram showing layers from Users of S.S. No. 7 down to MTP.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the architecture of S.S. No. 7. At the top is a box labeled "Users of S.S. No. 7". Below this, three vertical paths are shown. The left path consists of three stacked boxes: "TC user", "Transaction Capabilities (TC)", and "Signalling Connection Control Part (SCCP)". The middle path is a single box labeled "ISDN User Part (ISDN-UP)". The right path is a single box labeled "Telephone User Part (TUP)". All three paths converge into a single wide box at the bottom labeled "MTP". To the left of the MTP box, an arrow points left labeled "Other MTP users". In the bottom right corner of the diagram, the text "T0407100-96" is present. + +Architecture of S.S. No. 7 diagram showing layers from Users of S.S. No. 7 down to MTP. + +**Figure 1/M.3200 – Architecture of S.S. No. 7** + +## 5.6 N-ISDN + +N-ISDN is a narrow-band integrated services network that has evolved from the Public Switched Telephone Network (PSTN), and provides digital connections between user-network interfaces in support of a range of different telecommunications services, maintenance and network management functions. Figure 2 presents the basic concept of ISDN architecture. + +![Basic concept of ISDN architecture diagram showing connections between Terminal Equipment, Local Exchange, and Service Provider through various switching capabilities.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +The diagram shows the basic concept of ISDN architecture. On the left, a box labeled "TERMINAL EQUIPMENT (TE)" is connected to a box labeled "LOCAL EXCHANGE (LE)". This connection is labeled "B-channels" and "D-channel". A dashed line labeled "User-Network signalling" connects the TE and the LE. The LE is connected to three cloud-shaped boxes: "Packet-Switched Capabilities", "Circuit-Switched Capabilities", and "Common Channel Signalling Capabilities". The "Circuit-Switched Capabilities" cloud is connected to another box labeled "LOCAL EXCHANGE (LE)". This second LE is connected to a box labeled "TE or SERVICE PROVIDER". This connection is also labeled "B-channels" and "D-channel". A dashed line labeled "User-Network signalling" connects this LE and the TE or SERVICE PROVIDER. A long dashed line at the bottom, labeled "User-User (end-to-end) data and signalling", connects the first TE and the TE or SERVICE PROVIDER. In the bottom right corner of the diagram, the text "T0407110-96" is present. + +Basic concept of ISDN architecture diagram showing connections between Terminal Equipment, Local Exchange, and Service Provider through various switching capabilities. + +**Figure 2/M.3200 – Basic concept of ISDN architecture** + +The terminal equipment, network terminations and connections to the exchange do not belong to N-ISDN Managed Area. They are part of Access and Terminal Equipment Network. Packet/Circuit Switched Capabilities and MTP of the Common Channel Signalling Capability are also outside the scope of N-ISDN, since they are covered by specific Managed Areas, but logical and physical resources, dedicated to ISUP, belong to N-ISDN. + +Specific functionalities of N-ISDN include: + +- User-network signalling control; +- Activation/Deactivation progress control; +- Messages exchanged and processed through Embedded Operation Channel (EOC); +- Handling of interactive types of data communication through the use of D-channel; +- Handling of simultaneous speech and data services on a single line. + +## 5.7 B-ISDN + +B-ISDN is a concept of switched integrated network to transport different kinds of Telecommunication services (voice, data, image and video) in a standard digital format through fixed length cells (53 bytes), based mainly on SDH and ATM technologies. + +The integration of different services is possible through ATM Adaptation Layers (AALs) that allow different kinds of services to be adapted and transmitted in the same cell format. Part of the services that can be integrated through the B-ISDN are, for instance, LAN, SMDS, Frame Relay and Multimedia Services (VOD, Telecommuting, Telemedicine, desk-top publishing, etc.) + +The equipment used in B-ISDN includes ATM concentrators and ATM nodes that perform adaptation or switching functions, depending on its capabilities. The adaptation of existing services can also be performed outside concentrators through network terminals and terminal adapters that are not included in B-ISDN Managed Area because they belong to the Access and Terminal Equipment Network. + +The offered services that need Servers (VOD, SMDS, etc.) are usually provided by Servers Systems that, because of their architectural concept, belong to Intelligent Network. The Transport Network of B-ISDN can be built up of SDH technology and uses the regular transmission means and equipment between nodes and concentrators (IDF, ADM, etc.), which can not be included in B-ISDN because they belong to the Transport Network. + +## 5.8 Dedicated and Reconfigurable Circuits Network + +The Dedicated and Reconfigurable Circuits Network is a set of Leased and Special Circuits resources necessary for voice, data, image and video communication in a customized network. + +This network can be reconfigured and managed by the customer and/or by the operator. + +Part of the network elements that composes this network is already covered by resources of other Managed Areas such as Transport Network and Access and Terminal Equipment Network, which are not included in this managed area. Resources such as routers and bridges can be dedicated to this area, as we can find, for instance, in networks that uses X.50 or X.51 protocols. + +## 5.9 TMN + +TMN is the network which supports management activities associated with telecommunication networks in order to fulfil the requirements to plan, provision, install, maintain, operate and administer telecommunication networks and services. + +TMN provides an organized architecture that allows the necessary interconnection among various types of Operation Systems and/or telecommunication equipments. TMN must provide a high degree of flexibility to meet the various topological conditions of the telecommunications network itself and the organization of the administration. + +There are three basic TMN architectures that should be considered: functional, information and physical. The TMN functional architecture provides the means to transport and process information related to the management of telecommunication networks. It is based on a number of function blocks which enables TMN to perform the TMN management functions. + +The TMN information architecture is basically an object-oriented approach for information exchanges. The TMN physical architecture is based upon building blocks such as Operation Systems (OS), Mediation Devices (MD), Q Adaptor (QA), Data Communication Network (DCN), Network Element (NE) and Workstations (WS). + +The exchange of information between blocks is made possible through the implementation of interoperable interfaces concept and the use of TMN standard interfaces such as Q3, Qx, F and X. + +The TMN is logically distinct from the networks and services being managed, which allows operators to perform management of a wide range of distributed equipment, networks and services from a number of management systems. + +It is also possible to interconnect different TMNs. + +## **5.10 IMT-2000 (formerly FPLMTS)** + +IMT-2000 (International Mobile Telecommunications-2000) (formerly FPLMTS) is the third generation of mobile telecommunications system which aims at providing global service portability by means of Personal Mobility (PM), Terminal Mobility (TM) and Service Mobility (SM). + +It will provide access, by means of one or more radio links, to a wide range of telecommunication services supported by the fixed telecommunication networks, and to other services which are specific to mobile users. + +Key features of IMT-2000 are high degree of commonality of design worldwide, compatibility of services within IMT-2000 and with the fixed networks, high quality, and use of a small pocket-terminal with worldwide roaming capability. + +IMT-2000 may be implemented as a stand-alone network with gateways and interworking units connecting it to the supporting networks, in particular PSTN, ISDN, and B-ISDN. + +It may also be integrated with the fixed networks by means of other networks. + +The physical architecture for IMT-2000 is based on several building blocks such as: Mobile Station (MS), Base Station (BS) and Mobile Switching Centre (MSC). The Mobile Station belongs to the Access and Terminal Equipment Network. The Base Station (BS) belongs to IMT-2000 and the Mobile Switching Centre (MSC) belongs to IMT-2000 when dedicated exclusively to it. + +The basic functional model outlines the types of functional entities required to provide IMT-2000 services irrespective of environment (microcells, macrocells, satellite spots, etc.). The model also shows the functional relationships between these functional entities. + +The basic functional model for IMT-2000 can be found in ITU-R Recommendation M.817. All the logical resources, dedicated to implement this model, belong to IMT-2000. + +## **5.11 Access and Terminal Equipment Network** + +Access and Terminal Equipment Network is the part of the local network that extends from the network terminating equipment up to, and including, the exchange termination. This must take into account any equipment associated with the customer access including multiplex equipment, network terminating units etc., regardless of whether they are narrowband or broadband, analogue or digital and must include terminal equipment. + +Because of its complexity, Access and Terminal Equipment Network can no longer be regarded as consisting of copper wires and network terminating equipment. It may now consist of copper wires or optical fibre or radio links along with complex electronic equipment whose functions may need to be updated or changed by the network provider. + +## **5.12 Transport Network** + +Transport Network is the set of transmission paths linking two distributing frames, to which terminal equipments or switching nodes are connected. The transmission means used to connect the terminal equipments with the distributing frame are not included in the Transport Network because they belong to the Access and Terminal Equipment Network. The equipments used in Transport Network can be analogue or digital and can include multiplexers, line transmitters/receivers, transponders, radios, repeaters/regenerators, satellites, echo cancellors/suppressors, etc. The Transport Network provides the transmission means to all telecommunications services and networks, such as PSTN, PSPDN, VSAT, IN, CCSS, Cellular, etc. This means that within each transmission path, we can have telephone circuits, data circuits, TV channels, CCSS channels, etc. The main technologies used to build the Transport Network are FDM, PDH, SDH, copper wires, coaxial cables, optical cables, satellite, digital cross-connect and ATM. + +The Transport Network can also be considered as a set of trails. The trail is a "transport entity", in a server layer, responsible for the integrity of transfer of "characteristic information" from one or more client network layers, between server layer "access points". It defines the association between "access points" in the same "transport network layer". It is formed by combining a near-end "trail termination" function, a "network connection" and a far-end "trail termination" function. Trail termination functions provide information related to the integrity of information transfer in a trail. In SDH, a trail could be defined as a lower-order path or a higher-order path. Adaptation functions could be done by a digital multiplex and connection functions by a digital cross-connect. In PDH, a trail could be defined as a path. Adaptation functions could be done by a multiplex or a line system. In ATM, a trail could be defined as virtual channel or a virtual path. + +## **5.13 Infrastructure** + +Infrastructure Managed Area is the set of resources not directly involved in the telecommunications services, although that set supports all telecommunications services. Infrastructure includes resources such as: buildings, air conditioning, access roads, power plant, etc. + +# **6 TMN Management Services** + +TMN Management Service is defined in Recommendation M.3020. The interface requirements for TMN Management Service are the result of performing Task 1 and Task 2 of the interface specification methodology, using the GDMS, which are documented in Recommendation M.3020. The TMN Management Services are the support for the management of a certain Telecommunication Managed Area. + +The list of Management Services which have been identified is presented below. The Functions and/or Management Function Sets used to accomplish each of these Management Services belong to some or to all Management Functional Areas presented in Recommendation M.3400. + +## **List of Management Services** + +- 1) Customer Administration; +- 2) Network Provisioning Management; +- 3) Work Force Management; +- 4) Tariff, Charging and Accounting Administration; +- 5) Quality of Service and Network Performance Administration; +- 6) Traffic Measurement and Analysis Administration; +- 7) Traffic Management; +- 8) Routing and Digit Analysis Administration; +- 9) Maintenance Management; +- 10) Security Administration; +- 11) Logistics Management. + +The above list is only meant as a guide and is not intended to be exhaustive. Further revisions of this Recommendation may have additions. + +NOTE 1 – This list of TMN Management Services should be refined with the help of the Working Parties and Study Groups which have expertise in specific areas covered by these TMN Management Services (e.g. in Study Groups 2, 4, 11, 15). + +NOTE 2 – Some TMN Management Services which are identified above may be too large in scope to be treated as a single service. The possible subdivision of these services is for further study. + +Management Services are supported by interactions across all TMN Interfaces (X, F and Q) unless explicitly noted otherwise for a given Management Service. + +The following Management Service descriptions are prose descriptions intended to capture the overall telecommunications processes involved for each. These descriptions are not detailed and it is expected that individual recommendations, addressing these Management Services, provide, as reference, detailed requirement and processes directed by Recommendation M.3020. + +## **6.1 Customer Administration** + +Customer Administration is a management activity that the network operator performs in order to exchange with the customer management data and functions required to offer a telecommunications service and to exchange with the network all the customer-related management data and functions necessary for the network to produce that telecommunications service. This could include interactions for the purpose of Service Provision Management, Configuration Administration, Fault Administration, Charging (including detailed billing) Administration, Complaints Administration, Quality of Service Administration, Traffic Measurement Administration etc. Here, however, only Customer Administration in the more traditional sense of service provisioning, service configuration and complaints management has been included. + +## **6.2 Network Provisioning Management** + +Everyday, new customers in a telecommunication Administration demand several telecommunication services. The minimum time to respond, from the customers' standpoint, should be calculated when all the needed facilities are available at the nearest point to customers' premises. + +The length of time needed depends on how proactive is the telecom Administration in providing all the network facilities. The process starts with the Strategic Planning and continues up to the installation of the needed resources for the traditional services and for those created proactively. The goal of this Management Service is to provide the most cost-effective network possible and the most competitive set of services, new and traditional, through the available network resources. + +## **6.3 Work Force Management** + +The history of telecommunication operations shows examples of how actions and omissions of technical people can cause small and catastrophic productivity degradations. Trouble-ticket data processing is needed to obtain very important information to enhance human resources development in order to avoid or reduce such undue actions and omissions. Besides, the quality of telecommunication services offered to customers depends very much on the network operator's staff. Although this Management Service has no direct influence on Network Elements, it should be considered that effective staff work scheduling helps to keep the staff effort at an economic level. + +Accordingly, staff work scheduling is a management activity of the network operator in order to facilitate dispatching the appropriate staff member for the work to be performed. This is valid not only for OAM of the NEs, but also for the maintenance and installation work to be carried out at the customers' premises. Furthermore, the staff has to be scheduled for installation or repair work in the field, e.g. for cables, microwaves, etc. + +## **6.4 Tariff, Charging and Accounting Management** + +Every time a new telecommunication service is created, a corresponding change/addition should be made in tariff, charging and accounting. Every month, or every fifteen days or so, Administrations start new accounts receivable and deal with old ones, not yet received. Unpaid bills may lead to blocking of service and the subsequent payment may lead to deblocking. Changes in customers' traffic pattern can indicate a source of fraud and a customer traffic blocking can be done. Claim about error in the bill asks for testing. Changes in tariff to be charged require equipment reconfiguration. Bills receiving process, beginning when the right is obtained, ends normally by the bill receiving. Exceptions imply several functionalities to take care of them. + +## **6.5 Quality of Service and Network Performance Management** + +Quality of Service degradation can be produced by a lot of root causes: failures, undersized resources, design error, etc. When no effective means of detection for some of these root causes can be implemented by any specific test or performance monitoring, the only way to discover them is by end-to-end QOS monitoring or through customer's claim. Sometimes, important QOS degradation takes several years to be solved and involves a number of experts. The most common QOS degradations are steady Hard-to-Reach (HTR) directions and poor transmission quality. Recommendations E.420 through E.428 and E.800 through E.880 cover this field of management. The QOS Management process starts with the detection of degradation and should finish with the corresponding root cause elimination, passing through intermediate stages of investigations, analysis, interviews, testing, etc. + +Both network operators and equipment manufacturers have identified that increasing software and hardware complexity cause different and new system dependability problems. Design reliability models have recently been developed and it has been possible to improve Design Reliability Management. The process is similar to that described by Recommendation M.20 and is intended to remove the root cause of design reliability degradation. The symptoms appear in hardware design or in software design, but the root causes might have been existing in specification, system design, software design or hardware design phases. + +A call that is lost at the terminating point is certainly the worst root cause of productivity degradation in a Telecommunication Network because the call crossed the entire network to be lost at the other end, mainly when we consider a Packet Switched Network. A number of root causes has been identified: wrong routing, wrong called-customer status, line defect, called customer doesn't answer or is busy. These last two proved to be the strongest offender of this class of root causes of productivity degradation. Whenever an abnormal loss of this kind is detected, a new process to eliminate the corresponding root cause is started. + +Administrations have large experience with the consequences of bad behaviour of calling customers such as: automatic routing to a disconnected terminal, wrong dialling, interruption of dialling, etc. It was also discovered that some of the problems can be produced by customers device, or line, or line stage defects. Whenever an abnormal loss is found in this area, a new process of Loss on Calling Part Management is started. Some Administrations have a set of proactive actions to avoid this kind of abnormal loss. + +## **6.6 Traffic Measurements and Analysis Administration** + +Sometimes, real steady traffic is bigger or smaller than the planned. This may cause a strong steady overload and sometimes a strong underload. Both situations imply productivity degradation. They need to be corrected. It is also possible to forecast the future situation and implement proactive actions in order to avoid expected problems. When a current or future traffic problem is detected, a Traffic Administration process is started in order to eliminate the actual root cause of congestion or to avoid it in the future. Recommendations E.500 through E.721 and some of their Supplements are the ITU-T Recommendations in this field. + +## **6.7 Traffic Management** + +A number of events may arise which can have serious effects on the telecommunications services. Among these events are: + +- failures of transmission systems and switching nodes; +- planned outages of telecommunications resources; +- abnormal increases in traffic demand. The events which give rise to such traffic demand may be foreseen (e.g. national or religious holidays, sporting events) or unforeseen (e.g. natural disasters, political crises, the death of a very important person); +- focused overload, and in particular, mass-calling" (this text was derived from Recommendation E.410). + +Any of such events can start Traffic Management process to eliminate the sudden overload root cause. The end of it could be an expansive action or a protective action as stated by Recommendation E.411. + +Traffic Management is the object of the Recommendations E.410 through E.414. + +## **6.8 Routing and Digit Analysis Administration** + +The purpose of management of routing information in an exchange is to allow either a traffic or a routing manager to change the static routing information dynamically. + +In specifying the management object classes for routing, certain requirement must be met: + +- It must be possible to verify routing information in an exchange, with a minimal distortion in the normal operation of an exchange. +- It must be possible to switch between routing tables according to a pre-defined timing schedule, e.g. by introducing scheduling for routing tables. + +- Functionality must be defined in such a way that routing tables may be changed easily. +- Redundant information must be avoided by making use of objects which exist during run time. +- It must be possible to expand the model with future requirements and therefore the specification of object classes for routing purposes. + +## **6.9 Maintenance Management** + +Every physical resource of telecommunications network has a specific MTBF (Mean Time Between Failures) parameter. New failures are always happening at some points of the networks. When detected, each failure, opening a specific trouble ticket, starts a new maintenance process as described in Recommendation M.20 (clause 5), to achieve the fault elimination. M-Series Recommendations have a wide approach to maintenance, covering analogue, digital and mixed networks. + +By monitoring real field MTBF maximum likelihood estimate, two kinds of hardware reliability problems were found: MTBF estimate worse than that predicted by using MIL-STD failure rates, and a problem with the MTBF only for some specific field installations. By monitoring availability of switching systems, more than two hours of unavailability out of forty years were found. Whenever such problems are detected by Hardware Reliability Management, a new process is started in order to remove the specific root cause. + +## **6.10 Security Administration** + +(For further study.) + +## **6.11 Logistics Management** + +Materials management for stores, exchanges, transmission equipment and other parts of a telecommunications network enables the network operator to do the required installation work and maintenance. It allows calculation of the cost of a service offered to the customers and an improvement in the planning of a telecommunication network. + +# 7 **Management Services × Telecommunications Managed Areas Matrix** + +| TMN Users | | | | | | | | | | | | | | +|-------------------------------------------------------------|----------------------------------|------------------------------------|----------------------------|--------------------------|-----------------|-------------|-------------|------------------------------------------------|----------|-------------------------|------------------------------------|-------------------------|----------------------| +| Telecommunications Managed Areas

Management Services | Switching Telephone Network
1 | Mobile Communications Network
2 | Switched Data Network
3 | Intelligent Network
4 | CCSS No. 7
5 | N-ISDN
6 | B-ISDN
7 | Dedicated and Reconfigurable Circuits Net
8 | TMN
9 | IMT-2000 (FPLMTS)
10 | Access and Terminal eq. Net.
11 | Transport Network
12 | Infrastructure
13 | +| Customer Administration | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | | +| Network Provisioning Management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Work Force Management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Tariff, Charging and Accounting Administration | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ | ✓ | | ✓ | | | | +| Quality of Service and Network Performance Administration | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | +| Traffic Measures and Analysis Administration | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ | | ✓ | | +| Traffic Management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ | | ✓ | | +| Routing and Digit Analysis Administration | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | | | +| Maintenance Management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Security Administration | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Logistics Management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | + +T0407120-96 + +**Figure 3/M.3200** + +The ✓ sign in each crosspoint only means that the Telecommunications Managed Area in the column needs the Management Service indicated in the row. The set of signs in a column defines which Management Services could be used to accomplish the management of the correspondent Telecommunications Managed Area. + +## **7.1 Relationship between this Recommendation and Recommendation M.3020** + +Recommendation M.3020 describes the TMN interface specification methodology and provides guidelines for the definition of TMN Management Services. This Recommendation identifies a number of TMN Management Services and introduces the concept of Telecommunications Managed Areas. Clause 5 of the present Recommendation identifies the areas of management, by giving a brief description of each of them. Clause 6 provides a generic list of TMN Management Services and + +gives a short description of each. It shows the generic TMN management goals for each Management Service and presents benefits that TMN users obtain from these goals. The matrix of clause 7 provided the indications of Management Services, needed for each Telecommunications Managed Area. + +## 7.2 M.3200-Series + +The series of the TMN Management Services Recommendations is numbered according to the following template: + +- M.32XX.y = (TMN Management Services for XX Managed Area.y sequential number that identifies one or more crosspoint of the matrix for the XX Telecommunications Managed Area). The XX number is determined, according to list of Telecommunications Managed Areas of clause 5 of this Recommendation. The y number will be assigned in a chronological basis by the Study Group 4. + +### *Example* + +M.3201.1: + +M.32 TMN Management Service; + +01 Switched Telephone Network (refer to the matrix); + +.1 the chronological number for the Recommendation covering one or several management services under the column for Switched Telephone Network (refer to the matrix), + +i.e. TMN Management Services for Switched Telephone Network: Traffic Management, Traffic Measurements and Analysis Administration, Quality of Service and Network Performance Administration. + +# 8 Relationships between TMN Management Services and existing Recommendations + +TMN Management Services will replace human responsibilities of a pre-TMN environment, or create new capabilities of communications between organizations. Therefore, TMN Management Services and TMN Management Functions will have an impact on existing Recommendations. The development of new Recommendations for human operators in a TMN environment will sometimes be necessary in order to use TMN in an appropriate manner. + +Study Groups/Working Parties within ITU-T which use a TMN Recommendation as a tool to realize their management applications, should take into account the impact of existing Recommendations on the introduction of TMN and initiate appropriate feedback if needed. This impact should be reflected when describing TMN Management Services. + +# APPENDIX I + +## Example of GDMS application + +This appendix provides a reduced GDMS application to a matrix crosspoint to give users an example of M.3020 Task 1 and Task 2, producing TIB-A and TIB-B of the Maintenance Management of Switched Telephone Network. We will consider a very small number of resources to maintain this Recommendation as an overview document. + +## I.1 Management Service Description + +Every physical resource of the Switched Telephone Network has a specific MTBF (Mean Time Between Failures) parameter. New failures are always happening at some points of the network. When detected, each failure, opening a specific trouble ticket, starts a new maintenance process as described in 5/M.20, which continues until the Maintenance Entity (ME) recovery. + +By monitoring real field MTBF maximum likelihood estimate, it is possible to find two main classes of hardware reliability problems: MTBF estimate worse than that predicted by using MIL-STD failure rates, or problems with the MTBF for some specific field installations only. By monitoring the switching systems availability, it is possible to find more than two hours of unavailability out of 40 years. Whenever such problems are detected, a new process is started in order to remove the specific root cause. + +## I.2 Management goals + +We know well that faulty ME recovery causes gain of QOS. The benefit can range from a very small quality improvement up to the recovery of a switch or sub-network after an outage. The elimination of abnormal MTBF reduces failure rates and gives customers better QOS, besides reducing maintenance and spares inventory costs. + +## I.3 Management Context Description + +### I.3.1 Dynamic view of Management Context + +When a Role is performed, TMN users and TMN are involved alternately through interactions between them. A sequence of Roles is the realization of a specific TMN Management Service. A Role is performed through human actions and Management Application Functions (MAF). MAFs are the automated part of a Role. When considering a TMN Management Service as a key business process, a Role is a subprocess (business viewpoint). When we consider a TMN Management Service as a complete life cycle, a Role is a phase (R,D&E viewpoint, e.g. the phases described in Recommendation M.20 in the case of Maintenance Management). When we consider a TMN Management Service as a birth and death process, again a Role is a subprocess (mathematical modelling viewpoint). Under the three viewpoints, a Role remains what is defined in Recommendation M.3020, i.e. "the activities which are expected of the staff/system to perform telecommunications management". During the performance of each Role, **operations** and **notifications** will take place and several messages will flow through TMN interfaces, using TMN Management Functions. Operations are generated by TMN users to produce actions over managed objects (e.g. the command to block a killer trunk). Notifications are generated by the managed objects to inform something to TMN users (e.g. the alarm of frame alignment lost, produced by Recommendation G.732 when the limit of error bit rate is reached). Each message can cross several TMN interfaces to reach their end points (e.g. Qx, Q3, X and F for a notification and F, Q3 and Qx for an operation). Although operations reach managed objects and notifications are generated by managed objects, the correspondent sink/source point are the physical or logical or human resources of Telecommunications. + +### I.3.2 Resources + +We have chosen for this exercise a hypothetical switch that is implemented as proprietary local area network, i.e. network of computers, having a switching matrix and being a digital exchange. Although the MEs are physical, we will also consider logical resources, represented by the software that is loaded in the computers and occupies a certain memory area. Each software module has services implemented in a client/server approach. The degradation of a service can possibly indicate a physical fault in the computer where it is loaded. + +#### **I.3.2.1 Physical Resources** + +This example considers a very small part of a switch, i.e. a digital circuit group connecting two digital exchanges. The circuit group is the last choice in the routing plan. The exchanges involved belong to different Administrations, having both their own TMN. The circuit group contain four 2 Mbit/s links of PDH technology. Under this environment, the resources to be managed are: + +- the circuit group; +- each 2 Mbit/s link with the following ME: Power Source, Microcomputer, Digital Circuit Terminal and Switching Matrix Access; +- each 64 kbit/s digital circuit, having read/write memories as ME. + +#### **I.3.2.2 Logical Resources** + +There is a software implementing the switching and signalling functions for the digital circuits within each 2 Mbit/s link. The circuit group is R2-MFC signalling and line signalling is e/m pulse. + +### **I.3.3 Roles** + +#### **I.3.3.1 Performance measuring and alarm monitoring** + +It is the continuous or periodic (routine) checking of functions. + +The performance of each Circuit Group is supervised through the following robust estimates: Peg Count, Mean Holding Time, Mean Conversation Time and Call Completion Rate. There are two stochastic objectives for each of this variables, established by the Operating Company. Whenever one of them crosses a severe or normal performance exception, a notification is issued. The confidence level of each notification is 99.9999%. + +There are the following alarms concerning the 2 Mbit/s links: Loss of Power Supply, Microcomputer out of service, Recommendation G.732 alarms and Switching Matrix Access out of service. The performance is supervised by the same robust estimates of Circuit Group, considering only the circuits of the link. + +There are the following alarms to monitor each circuit: sign bit stuck at abnormal signal-to-noise ratio and successive short holding time. + +The performance is supervised through the maximum likelihood estimates of the following variables of each circuit: Peg Count, Mean Holding Time, Mean Conversation Time and Call Completion Rate. An exception is determined using a 99.9999% two-sided confidence interval and using a null hypothesis based on the robust estimate of the circuit group. + +#### **I.3.3.2 Failure detection** + +Whenever an alarm condition is reached or a performance exception is established, a malfunction or possible malfunction is detected. A prompt or deferred maintenance alarm or a maintenance event is generated by the Maintenance Entity (ME). Any alarm or performance exception message must be routed to the OS of the following Management Services: Maintenance Management, Work Force Management, Traffic Management and Traffic Measurement and Analysis Administration. This must be done by addressing the messages to the OS of both Operating Companies involved, i.e. the OSs of the two TMNs. + +#### **I.3.3.3 System protection** + +By blocking the ME or by rerouting, the effect of failure is minimized, i.e. by excluding the faulty ME from operation or bypassing the faulty physical resource. + +#### **I.3.3.4 Analysis** + +Interactions involving Staff/TMN are performed, through alarm correlations and other techniques, to determine the smallest region containing the root cause, obtaining in this way the most effective dispatch. + +#### **I.3.3.5 Fault localization** + +When fault information is insufficient, the determination of faulty ME is performed with the help of internal test systems or external test systems, automated, automated or not, and after that the exact root cause is localized. + +#### **I.3.3.6 Fault correction** + +As the root cause is localized, the correction of the faulty ME can be done through repair or replacement of the faulty part by a spare. + +#### **I.3.3.7 Verification** + +The correction is not always well done. The check of ME after fault correction is performed, using a fault localization similar procedure, to ensure that malfunction of the ME was eliminated. + +#### **I.3.3.8 Restoration** + +Through unblocking or the end of changeover, the restoration of ME normal function is attempted. After succeeding the attempt, the ME returns to service or to standby mode. + +### **I.3.4 TMN Management Functions Sets and Set Groups** + +As the Roles presented in the previous subclauses are being developed, flow of messages through the TMN interfaces will be required. Having in mind the resources listed above, the next items present the needed TMN Management Functions Sets (refer to Recommendation M.3400). + +#### **I.3.4.1 Performance Management** + +Under the Performance Management Control group we will need the following TMN Management Function Sets: Generic function set; Detection, storage, counting and reporting function set; Traffic status function set; Traffic performance function set and Performance monitoring policy function set. Under the Performance Analysis group we will need the Exception threshold policy function set. + +#### **I.3.4.2 Fault Management** + +We will need the following TMN Management Function Set Groups: Alarm Surveillance, Fault Localization, Fault Correction and Trouble Administration. + +#### **I.3.4.3 Configuration Management** + +We will need the following TMN Management Function Sets: Loading NE software function set, NE configuration function set, Circuit inventory function set and Circuit inventory query function set. + +## **I.4 Architecture** + +The functional and physical architectures are presented in Figures 4 and 5. They are designed addressing some of the needed TMN Management Functions as follows: + +- successive short holding time circuit (killer trunk) **alarm report** – N1; +NOTE 1 – At the same time the NE blocks the faulty circuit. +- **request circuit and circuit group PM data** – O1; + +- circuit and circuit group **PM data report** – N2; +- **connect test access** – O2; +- **Measure E1 Signals** – O3; +- **Terminate Test Measurements** – O4; +- **Request Test Results** – O5; +- **Test Results Reporting** – N3; +- Unblock the circuit – O6. + +NOTE 2 – The bold texts are TMN Management Functions captured from Recommendation M.3400. NX means X-order notification and OX means X-order operation. + +This set of TMN Management Functions is divided into the following subgroups of messages that flow at the related reference points/interfaces: + +GROUP1 = (N1, O1, N2, O2, O3, O4, O5, N3, O6); + +GROUP2 = (N1, O1, N2, O2, ..., O6); + +GROUP3 = (N1, O1, N2). + +NOTE 3 – In this example, the functions for the f/x reference points and F/X interfaces are subsets of the functions for the q3/Q3. In other cases, the functions for the f/F and x/X may be a superset of the q3/Q3 functions, or may be different functions. Also note that functions may be implemented differently on the F interface than on the Q. The functions, information models and protocols are under study. + +![Functional architecture diagram showing two TMNs (TMN-A and TMN-B) with their internal components and interconnections. TMN-A includes WSF1, OSF1, NEF, WSF3, and OSF3. TMN-B includes WSF2 and OSF2. Reference points f, g, x, and q3 are indicated between components and between the two TMNs.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +The diagram illustrates the functional architecture of two TMNs, TMN-A and TMN-B, under Administration A and Administration B respectively. + +- TMN-A (Administration A):** + - Contains components: WSF1, OSF1, NEF, WSF3, and OSF3. + - WSF1 is connected to Administration A via reference point 'g'. + - OSF1 is connected to WSF1 via reference point 'f' (GROUP2). + - NEF is connected to OSF1 via reference point 'q3' (GROUP1). + - OSF3 is connected to OSF1 via reference point 'q3' (GROUP3). + - WSF3 is connected to OSF3 via reference point 'f' (GROUP3). +- TMN-B (Administration B):** + - Contains components: WSF2 and OSF2. + - WSF2 is connected to Administration B via reference point 'g'. + - OSF2 is connected to WSF2 via reference point 'f' (GROUP3). +- Inter-TMN Connections:** + - OSF1 (TMN-A) and OSF2 (TMN-B) are connected via a zigzag line representing an interface. + - Reference point 'x' (GROUP3) is indicated on this interface. +- Legend:** A solid black circle represents 'Reference points'. + +Functional architecture diagram showing two TMNs (TMN-A and TMN-B) with their internal components and interconnections. TMN-A includes WSF1, OSF1, NEF, WSF3, and OSF3. TMN-B includes WSF2 and OSF2. Reference points f, g, x, and q3 are indicated between components and between the two TMNs. + +T0407130-96 + +Figure 4/M.3200 – Functional architecture + +![Diagram of physical architecture showing two administrations, Administration A and Administration B, connected via a central DCN. Administration A includes WS1, WS3, OS1, OS3, and an NE connected to the DCN. Administration B includes WS2 and OS2 connected to the DCN. Various interfaces (GROUP1, GROUP2, GROUP3, F, Q3, X/F) are shown between the components and the DCN. A legend at the bottom left indicates that a circle with a cross symbol represents 'Interfaces'.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +T0407140-96 + +⊕ Interfaces + +Diagram of physical architecture showing two administrations, Administration A and Administration B, connected via a central DCN. Administration A includes WS1, WS3, OS1, OS3, and an NE connected to the DCN. Administration B includes WS2 and OS2 connected to the DCN. Various interfaces (GROUP1, GROUP2, GROUP3, F, Q3, X/F) are shown between the components and the DCN. A legend at the bottom left indicates that a circle with a cross symbol represents 'Interfaces'. + +**Figure 5/M.3200 – Physical architecture** + +## I.5 Scenarios + +Figure 6 provides an example of management interactions using the information defined above, the CMIS services and CMIP protocol. + +![Diagram of Management interactions (Figure 6/M.3200) showing the architecture of a Telecommunications Network Management (TMN) system. It includes two administrations (A and B), Work Stations (WS), Operating Systems (OS1, OS2), and Network Elements (NE).](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +The diagram illustrates the management interactions in a Telecommunications Network Management (TMN) system, divided into two administrations: Administration A (TMN-A) and Administration B (TMN-B). + +**Administration A (TMN-A):** + +- WS (Work Station):** Contains an 'A' (Application) block. It is connected to OS1 via interfaces N1, O1, N2, O2, O3, O4, N3, and O6. +- OS1 (Operating System 1):** Contains 'CMIS' (Common Management Information Service) blocks with 'M' (Manager) and 'A' (Agent) components. It is connected to the NE via a 'CMIP' (Common Management Information Protocol) interface and interfaces N1, O1, N2, O2, O3, O4, N3, and O6. +- NE (Network Element):** Contains a 'Managed Objects' block with a 'MIB' (Management Information Base) and a 'Circuit Group'. The circuit group consists of '2 Mbit/s links' and a '64 kbit/s circuit'. It is connected to the TMN via a 'Resources' and 'Circuit Group' block. + +**Administration B (TMN-B):** + +- WS (Work Station):** Contains an 'A' (Application) block. It is connected to OS2 via interfaces N2, O2, and N1. +- OS2 (Operating System 2):** Contains 'CMIS' blocks with 'M' (Manager) and 'A' (Agent) components. It is connected to the TMN via a 'Resources' and 'Circuit Group' block. + +**TMN (Telecommunications Network Management):** + +- The TMN is represented by a dashed line separating the administrations from the network elements. +- It contains 'Resources' and 'Circuit Group' blocks. +- Below these, there is an 'NE' block with four '2 Mbit/s' links. + +**Interactions:** + +- Between WS and OS1/OS2: Management messages (N1, O1, N2, O2, O3, O4, N3, O6 for OS1; N2, O2, N1 for OS2). +- Between OS1/OS2 and NE: CMIP and CMIS interactions. +- Between NE and TMN: Management of resources and circuit groups. + +Diagram of Management interactions (Figure 6/M.3200) showing the architecture of a Telecommunications Network Management (TMN) system. It includes two administrations (A and B), Work Stations (WS), Operating Systems (OS1, OS2), and Network Elements (NE). + +T0407150-96 + +64 kbit/s circuit + +OS1 Maintenance and Work Force Management + +OS2 Traffic measurements and analysis administration/traffic management + +**Figure 6/M.3200 – Management interactions** + +# ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.3207.1-199605-I_PDF-E/raw.md b/marked/M/T-REC-M.3207.1-199605-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f248de641d6b2f14a7c4afc9076f98001c96b6ec --- /dev/null +++ b/marked/M/T-REC-M.3207.1-199605-I_PDF-E/raw.md @@ -0,0 +1,349 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3207.1** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(05/96) + +SERIES M: MAINTENANCE: INTERNATIONAL +TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, +TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**TMN management service: maintenance +aspects of B-ISDN management** + +ITU-T Recommendation M.3207.1 + +(Previously «CCITT Recommendation») + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation M.3207.1 was prepared by ITU-T Study Group 4 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 12th of May 1996. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|----------------------------------------------------------|-------------| +| 1 Scope ..... | 1 | +| 2 References ..... | 1 | +| 3 Abbreviations ..... | 1 | +| 4 TMN management service description based on GDMS ..... | 2 | +| 4.1 Management service description..... | 2 | +| 4.2 Management goals ..... | 2 | +| 4.3 Management context description ..... | 2 | +| 4.4 Architecture ..... | 9 | + +# **SUMMARY** + +This Recommendation describes the TMN management service for the maintenance aspect of B-ISDN management with using GDMS (Guideline for the Definition of TMN Management Services). + +# **KEYWORDS** + +B-ISDN, Telecommunications Management Network (TMN), TMN management service. + +# **TMN MANAGEMENT SERVICE: MAINTENANCE ASPECTS OF B-ISDN MANAGEMENT** + +*(Geneva, 1996)* + +# **1 Scope** + +This Recommendation describes the TMN management service for the maintenance aspect of B-ISDN management. + +# **2 References** + +The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation M.3610 (1996), *Principles for applying the TMN concept to the management of B-ISDN*. +- [2] ITU-T Recommendation I.311 (1993), *B-ISDN general network aspects*. +- [3] ITU-T Recommendation G.803 (1993), *Architectures of transport networks based on the Synchronous Digital Hierarchy (SDH)*. +- [4] CCITT Recommendation M.3400 (1992), *TMN management functions*. +- [5] CCITT Recommendation M.1400 (1992), *Designations for international networks*. +- [6] ITU-T Recommendation I.610 (1995), *B-ISDN operation and maintenance principles and functions*. +- [7] ITU-T Recommendation M.3020 (1995), *TMN interface specification methodology*. +- [8] CCITT Recommendation M.3200 (1992), *TMN management services: Overview*. +- [9] ITU-T Recommendation I.326 (1995), *Functional architecture of transport networks based on ATM*. + +# **3 Abbreviations** + +For the purposes of this Recommendation, the following abbreviations apply: + +| | | +|------|----------------------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| GDMS | Guidelines for the Definition of TMN Management Services | +| MSP | Management Service Provider | +| NEF | Network Element Function | +| OAM | Operation, Administration and Maintenance | +| OSF | Operations System Function | +| TIB | Task Information Base | + +TMN      Telecommunications Management Network + +UNI/NNI   User Network Interface/Network Node Interface + +VP/VC      Virtual Path/Virtual Channel + +# **4      TMN management service description based on GDMS** + +This clause presents the TMN management service based on GDMS, which is specified in Recommendation M.3020 [7]. + +The GDMS makes use of references to the functions in Recommendation M.3400 [4]. The references in this Recommendation are referring to the published 1992 version of Recommendation M.3400. Best efforts have been made to accommodate current developments in Recommendation M.3400. + +In general in this Recommendation, OSF and NEF take manager and agent roles respectively. + +## **4.1      Management service description** + +This TMN management service deals with the maintenance aspect of the management of B-ISDN by the TMN in the functional areas of: + +- fault management including alarm surveillance and testing; +- performance management in terms of performance monitoring functions associated with the ATM layer; +- configuration management needed to handle virtual connections; and +- security management. + +## **4.2      Management goals** + +Using the B-ISDN Telecommunications Managed Area (see [8]), TMN users, including network operators and B-ISDN customers, can provide and maintain physical/logical resources constructing B-ISDN efficiently. The objective of this managed area is to supply B-ISDN customers with a high quality service through such provisioning and maintenance activities. The architecture, to which the B-ISDN Telecommunications Managed Area is applied, is shown in Figures 1/M.3610 to 4/M.3610 [1]. + +The architecture of Recommendation M.3610 supports TMN users of the B-ISDN Telecommunications Managed Area and allows: + +- 1) a network operator to manage his/her own B-ISDN network; +- 2) MSP-OSF (see Recommendation M.3610 [1]) to request OAM-OSF for managing services; and +- 3) TMNs of multiple interconnected B-ISDNs to exchange management information for the purpose of management of customer end-to-end connections. + +This TMN Management Service addresses the maintenance aspects of B-ISDN management. + +## **4.3      Management context description** + +### **4.3.1      Roles** + +The roles described here include maintenance (including testing, performance monitoring and alarm surveillance) and some aspects of service provisioning. Network provider uses the service described below to support B-ISDN maintenance and some aspects of B-ISDN provisioning. + +### 4.3.2 Resources + +The resources to be managed are logical and physical resources constructing B-ISDN. These resources are identified in Recommendation I.311 "B-ISDN general network aspects" [2]. They include virtual paths/channels as well as VP/VC cross-connections/switches, etc. + +The resources are abstracted as architectural components, which are defined in clause 3/G.803 [3]. The B-ISDN architectural components are described as follows: + +- The set of the access points for virtual channels constructs virtual channel layer network. +- The set of the access points for virtual paths constructs virtual path layer network. +- The set of the access points for transmission paths constructs transmission paths layer network. +- Trails are provided between the access points that are connected by a virtual channel, virtual path, or transmission path in the associated layer network. +- A trail supported by a virtual channel (virtual channel trail) is formed by trail termination functions, a virtual channel network connection and its TCPs (Termination Connection Points) in the virtual channel layer network. The virtual channel trail termination function is placed between the access point of the trail and the TCP of the network connection. The trail termination source function inserts and the trail termination sink function drops the end-to-end F5 OAM flow (see Recommendation I.610 [6]) to obtain information related to the integrity of virtual channel information transfer. +- A trail supported by a virtual path (virtual path trail) is formed by trail termination functions, a virtual path network connection and its TCPs in the virtual path layer network. The virtual path trail termination function is placed between the access point of the trail and the TCP of the network connection. The trail termination source function inserts and the trail termination sink function drops the end-to-end F4 OAM flow (see Recommendation I.610 [6]) to obtain information related to the integrity of virtual path information transfer. +- A trail supported by a transmission path (transmission path trail) is formed by trail termination functions, a transmission path network connection and its TCPs in the transmission path layer network. The transmission path trail termination function is placed between the access point of the trail and the TCP of the network connection. The trail termination source function inserts and the trail termination sink drops the F3 OAM (see Recommendation I.610 [6]) flow to obtain information related to the integrity of transmission path information transfer. +- A virtual channel network connection consists of the concatenation of virtual channel subnetwork connections and virtual channel links. Typically, a virtual channel subnetwork connection is a cross-connection. +- A virtual path network connection consists of the concatenation of virtual path subnetwork connections and virtual path links. Typically, a virtual path subnetwork connection is a cross-connection. +- A transmission path consists of the concatenation of virtual path subnetwork connections and transmission path links. +- The virtual channel layer network and the virtual path layer network form the client/server association: the virtual channel layer network is the client while the virtual path layer network is the server. Thus, a virtual channel link is provided by adaptation functions and a virtual path trail. +- The adaptation functions between the virtual channel layer network and the virtual path network include multiplexing, demultiplexing, Usage Parameter Control (UPC) and capacity management. +- The virtual path layer network and the transmission path layer network form the client/server association: the virtual path layer network is the client while the transmission path layer network is the server. Thus, a virtual path link is provided by adaptation functions and a transmission path trail. +- The adaptation functions between the virtual path layer network and the transmission path network include multiplexing, demultiplexing, cell delineation, Usage Parameter Control (UPC), and capacity management. + +Figure 1 illustrates these resources. + +![Diagram of B-ISDN resources to be managed, showing layers for VC, VP, and TP with various components like Access Points, Connection Points, Adaptations, and OAM Flows.](2ee59e629035d641140e55f4d215b0d7_img.jpg) + +The diagram illustrates the hierarchy of B-ISDN resources. At the top, a **VC Trail** is shown between two **VC-AP** (Access Point) units. This trail contains an **F5 OAM Flow** and **VC Trail Termination** points. Below this is a **VC Network Connection** which connects to a **VC Link**. The **VC Link** involves **VC-TCP** (Termination Connection Point), **VC to VP Adaptation**, **VC-CP** (Connection Point), and a **VC** (Virtual Channel) within a **Subnetwork Connection**. Below the VC layer is the **VP Trail** layer, which includes **VP-AP**, **VP Trail Termination**, an **F4 OAM Flow**, and a **VP Network Connection**. This connects to a **VP Link** involving **VP-TCP**, **VP to TP Adaptation**, **VP-CP**, and a **VP** (Virtual Path) within a **Subnetwork Connection**. The bottom layer is the **TP Trail** layer, which includes **TP-AP**, **TP Trail Termination**, an **F3 OAM Flow**, and a **TP Network Connection**. This connects to a **TP Link** involving **TP-TCP** units. A legend at the bottom defines the symbols: **VC** (Virtual Channel), **VP** (Virtual Path), **TP** (Transmission Path), **AP** (Access Point), **CP** (Connection Point), **TCP** (Termination Connection Point), a circle with a vertical line for **Access Point**, a circle with a horizontal line for **Connection Point/Termination Connection Point**, a trapezoid for **Adaptation**, and a triangle for **Termination**. The code **T0405750-95/d01** is also present. + +Diagram of B-ISDN resources to be managed, showing layers for VC, VP, and TP with various components like Access Points, Connection Points, Adaptations, and OAM Flows. + +T0405750-95/d01 + +FIGURE 1/M.3207.1 +B-ISDN resources to be managed + +### **4.3.3 TMN management functions** + +#### **4.3.3.1 TMN management function sets found in Recommendation M.3400 [4]** + +##### **4.3.3.1.1 Alarm surveillance** + +All management function sets in 3.1/M.3400 “Alarm surveillance” [4] may be applied to this failure information: + +- 1) VPC – AIS/RDI including alarm location from the location identification fields in OAM cells and continuity check failure is reported from NEF to OSF. See Recommendation M.1400 [5] on how the location identification field is determined. The report has to include the identification of the virtual path/channel trail termination function that detects AIS/RDI including alarm location identification fields in OAM cell and continuity check failure. When this optional location information is not available the report will so indicate. +- 2) VCC – AIS/RDI including optional alarm location may be reported from NEF to OSF. +- 3) NEF reports failure of restoration taken for a particular virtual path/channel connection. + +##### **4.3.3.1.2 Testing** + +The following are performed using the testing function sets in 3.4/M.3400 “Testing” [4]: + +- 1) OSF requests NE to execute ATM non-intrusive loopback test. + +The test request has to include: + +- loopback location (see Recommendation M.1400) or indication for end-to-end measurement; and + - the identification of the trail termination function or the connection point that inserts and analyses the loopback OAM cell. +- 2) NEF reports the results of non-intrusive loopback tests. The report has to include the results as well as the identification of the trail termination functions or the connection points of the subnetwork connection that perform the test. + - 3) OSF requests NEF to insert or drop test cells for ATM performance testing in the in-service, out-of-service, or drop-insert measurement mode. The request has to include the identification of the insertion or drop point for test signal. Such a point corresponds to a trail termination function or a connection point of the subnetwork connection of the virtual path/channel to be tested. + - 4) OSF requests NEF to execute ATM performance testing, and NEF reports the results of ATM performance testing. + +##### **4.3.3.1.3 Fault correction** + +The following are performed using the fault correction function sets in 3.3/M.3400 “Fault correction” [4]: + +- 1) NEF reports the result of change over function on a particular virtual path/channel connection; +- 2) OSF requests NEF to send back information or records associated with change over function. + +##### **4.3.3.1.4 Performance management control** + +The following are performed using the performance management control function sets in 2.1/M.3400 “Performance Monitoring (PM)” [4]: + +- 1) NEF reports the status of performance monitoring on a particular virtual path/channel connection or a particular segment of a virtual path/channel connection. The report has to include the performance parameter values as well as the identification of the trail termination functions or the connection points of the subnetwork connection that perform monitoring. The monitored performance parameters are identified in Recommendation I.610 [6]. + +- 2) OSF sets/clears control parameters of performance monitoring including a monitoring block size, threshold for the reporting of performance degradation, etc. The request has to include the performance monitoring control parameter values as well as the identification of the trail termination functions or the connection points of the subnetwork connection that perform monitoring. +- 3) NEF reports degradations in performance parameters, including errored blocks and misinserted/dropped cells. + +##### **4.3.3.1.5 NE configuration** + +The following are performed using the NE configuration function set in clause 4/M.3400 “Configuration management” [4]: + +- 1) OSF sets/clears segment endpoints for virtual path/channel level in NE. +- 2) OSF requests NEFs to constitute cross-connections to establish a particular virtual path/channel connection. The request must include the identifications of the virtual path/channel connection points. +- 3) NEF reports the results of cross-connection establishment. + +##### **4.3.3.1.6 Security management** + +The following are performed using the security management function sets in clause 6/M.3400 “Security management” [4]: + +- 1) OSF requests NEF to report security audit on a particular VPC/VCC manipulation; +- 2) OSF sets/clears a security level of operations to a particular virtual path/channel connection; +- 3) NEF reports security violation alarm on a particular virtual path/channel connection on which security level of operations is set. + +#### **4.3.3.2 Newly defined TMN management function sets and function set groups [TIB B]** + +##### **4.3.3.2.1 Virtual channel connection alarm generation control function set** + +###### **4.3.3.2.1.1 Management requirements** + +In Recommendation I.610 [6], a limited number of virtual channel connections can be alarmed. Therefore, the TMN must be able to manage which virtual channel should be alarmed. This TMN management service provides such management of alarms on virtual channel connections. + +###### **4.3.3.2.1.2 Functional model** + +This TMN management function set enables the TMN user to allow or inhibit the generation of the alarms for specified virtual channel connections. Control of alarm generation should not be confused with control of alarm reporting, which is found in M.3400 alarm reporting function set [4]. Thus, the TMN user can obtain alarm information from only a limited number of the virtual channels, which he/she specified. + +###### **4.3.3.2.1.3 TMN management functions** + +- 1) OSF requests NEFs to enable the alarm generation on a particular virtual channel connection; +- 2) OSF requests NEF to disable the alarm generation on a particular virtual channel connection; +- 3) OSF requests NEF to report the status of alarm generation on a particular virtual channel; +- 4) OSF requests NEF to report the remaining capacity for the alarm generation on a particular virtual path. + +##### **4.3.3.2.2 Continuity check control** + +###### **4.3.3.2.2.1 Management requirements** + +This TMN management function set provides the ability to control the virtual path/channel connection continuity check specified in Recommendation I.610 [6]. By invoking continuity check on a virtual path/channel connection, the TMN user can obtain information about the correctness of the connectivity in the case that the connection is not loaded with traffic. The management function set allows the TMN user to activate and deactivate continuity check for a particular connection/segment as well as to ask whether continuity check is activated or not on a particular connection/segment. + +This function is used to manage an optional ATM capability. If this capability is not available, then managed resources are required to indicate the absence of this function. + +###### **4.3.3.2.2.2 Functional model** + +When continuity check is executed on the end-to-end basis, this TMN management function set controls the virtual path/channel trail termination function, which inserts or drops the end-to-end F4/F5 OAM cells. The trail termination function source transmits the continuity check fault management OAM cell when no user cell has been sent for a period of $t$ , where $T_s < t < 2T_s$ , and no failure is indicated. If the trail termination function sink receives no cells within a time interval $T_r$ ( $T_r > 2T_s$ ), it concludes the disconnection of the virtual path/channel trail. At activation and deactivation of continuity check, the trail termination functions exchange the activation/deactivation OAM cells. + +When continuity check is executed on the segment basis, this TMN management function set controls specified connection points of the virtual path/channel subnetwork connection. The connection points delimit the virtual path/channel connection segment to be checked. The connection points work in a similar way as the termination functions do in end-to-end continuity check except for exchanging the segment OAM cells instead of the end-to-end OAM cells. The functionalities of the termination functions/connection points include: + +- exchange of the activation/deactivation OAM cells; +- start/stop of OAM cell insertion/drop; +- detection and reporting of disconnection. + +The resource that is subject to continuity check is a virtual path/channel connection or a virtual path/channel connection segment, which is delimited by the specified connection points and composed of the concatenation of virtual path/channel links and subnetwork connections. + +###### **4.3.3.2.2.3 TMN management functions** + +The following are the TMN management functions that allow the TMN user to control continuity check: + +- 1) OSF requests NEF to activate/deactivate continuity check on a particular virtual path/channel connection with indicating the identification of the associated trail termination function. The request must include the information showing that continuity check is performed on the end-to-end basis. NEF reports whether the activation/deactivation was confirmed or denied. +- 2) OSF requests NEF to activate/deactivate continuity check on a particular virtual path/channel connection segment with indicating the identification of the associated connection point. The request must include the information showing that continuity check is performed on the segment basis. NEF reports whether the activation/deactivation was confirmed or denied. +- 3) OSF requests NEF to set the parameter values $T_r$ , $T_s$ (see Recommendation I.610 [6]). The request has to include the parameter values as well as the identification of the associated trail termination function or connection point. Whether $T_s/T_r$ is set per connection or per NE is for further study. +- 4) OSF asks NEF whether continuity check is activated or not on a particular virtual path/channel connection or connection segment. The request has to include the identification of the associated trail termination function or connection point. + +##### **4.3.3.2.3 ATM performance monitoring control** + +###### **4.3.3.2.3.1 Management requirements** + +This TMN management function set provides the ability to activate and deactivate the virtual path/channel connection performance monitoring specified in Recommendation I.610 [6]. The performance monitoring is carried out on a certain number of selected virtual path/channel connections per UNI/NNI (see Recommendation I.610). The management service allows the TMN user to select the virtual path/channel connection that is subject to monitoring and start/stop the monitoring. By activating the monitoring, the TMN user can obtain information as to the virtual path/channel performance, which is described through parameters such as errored blocks, loss/misinsertion of cells, etc. The TMN user can also know whether performance monitoring is activated or not on a particular connection/segment. + +This function is used to manage an optional ATM capability. If this capability is not available, then managed resources are required to indicate the absence of this function. + +###### **4.3.3.2.3.2 Functional model** + +When performance monitoring is executed on the end-to-end basis, this TMN management function set controls the virtual path/channel trail termination function, which inserts or drops the end-to-end F4/F5 OAM cells. The trail termination source function transmits the performance management OAM cell while performance monitoring is activated. Meanwhile, the trail termination sink function drops and analyses the received cells. At activation and deactivation of performance monitoring, the trail termination functions exchange the activation/deactivation OAM cells. By exchanging the activation OAM cell, the block size used in monitoring is determined. + +When performance monitoring is executed on the segment basis, this TMN management function set controls specified connection points of the virtual path/channel subnetwork connection. The connection points delimit the virtual path/channel connection segment to be monitored. The connection points work in a similar way as the termination points do in end-to-end performance monitoring except for exchanging the segment OAM cells instead of the end-to-end OAM cells. + +The functionalities of the termination functions/connection points include: + +- exchange of the activation/deactivation OAM cells; +- start/stop of OAM cell insertion/drop; +- analysis of performance. + +The resource that is subject to performance monitoring is a virtual path/channel connection or a virtual path/channel connection segment, which is delimited by the specified connection points and composed of the concatenation of virtual path/channel links and subnetwork connections. + +###### **4.3.3.2.3.3 TMN management functions** + +The following are the TMN management functions that allow the TMN user to control performance monitoring: + +- 1) OSF requests NEF to activate/deactivate performance monitoring on a particular virtual path/channel connection with indicating the identification of the associated trail termination function as well as the value of the performance monitoring block size. The request must include the information showing that performance monitoring is performed on the end-to-end basis. NEF reports whether the activation/deactivation was confirmed or denied. +- 2) OSF requests NEF to activate/deactivate performance monitoring on a particular virtual path/channel connection segment with indicating the identification of the associated connection points as well as the value of the performance monitoring block size. The request must include the information showing that performance monitoring is performed on the segment basis. NEF reports whether the activation/deactivation was confirmed or denied. +- 3) OSF asks NEF whether performance monitoring is activated or not on a particular virtual path/channel connection or connection segment. The request has to include the identification of the associated termination function. + +##### **4.3.3.2.4 ATM test control** + +###### **4.3.3.2.4.1 Management requirements** + +This TMN management function set provides the ability to control the non-intrusive loopback test and the ATM layer performance test in addition to testing function sets (see 4.3.3.1.2), which supports the test request and report. By employing the management function, the TMN user can flexibly control the tests depending on the circumstance. Examples of the control include setting of the threshold, suspension/resumption, termination, etc. The management service is concerned with the performance test based on the test equipment and the non-intrusive loopback test specified in Recommendation I.610 [6]. + +###### **4.3.3.2.4.2 Functional model** + +This TMN management function set affects the test cell insertion/drop point: the virtual path/channel trail termination function or the connection point of virtual path/channel subnetwork connection. The management function utilises the following functionalities of such a resource: + +- start/stop of OAM cell insertion/drop; +- the analysis/storage of intermediate test results; +- setting of the threshold for the measured performance parameters; +- reporting the test result. + +The resource that is subject to testing is a virtual path/channel connection or a virtual path/channel connection segment, which is delimited by the specified connection points and composed of the concatenation of virtual path/channel links and subnetwork connections. + +###### **4.3.3.2.4.3 TMN management functions** + +The following are the TMN management functions that allow the TMN user to control testing in addition to testing function set group: + +- 1) OSF request NEF to set conditions for the non-intrusive loopback test including duration, reporting frequency, etc. The request has to include the parameter values and the identification of the associated termination function or connection point. +- 2) OSF requests NEF to suspend/resume the ATM layer performance test on a particular virtual path/channel connection. The request has to include the test invocation identifier and the identification of the associated termination function or connection point. +- 3) OSF requests NEF to set the threshold for the ATM layer performance test on a particular virtual path/channel connection. The request has to include the threshold values, the test invocation identifier and the identification of the associated termination function or connection point. +- 4) OSF requests NEF to terminate the ATM layer performance test on a particular virtual path/channel connection. The request has to include the test invocation identifier and the identification of the associated termination function or connection point. +- 5) OSF asks NEF if the test is going on and requests NEF to report the status of the current test. + +## **4.4 Architecture** + +The architecture, to which this TMN management service is applied, is found in Recommendation M.3610 [1]. \ No newline at end of file diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/061a752e081b43db4964482b0349f751_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/061a752e081b43db4964482b0349f751_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d282b210cdb938a1e3e13b4539272876cfd5417e --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/061a752e081b43db4964482b0349f751_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781f605928ac0144b8d87768ecafc0376e5a88e9700f0ca60cb46a4421671d66 +size 18326 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/070352b751dd0711b8ac6ddfa6df1d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2721c167ec077ee2ac431dbeca13fac55756f85c --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/070352b751dd0711b8ac6ddfa6df1d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ebc5108bdac82444646a39f0fd8123dba5b85d64fdf5d3174705f8f09851c4d +size 13383 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..478cd86855a56097211de4afe3a9bbc66537f01d --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd271455c7437339027d182d733c6325bbf55349112e3207ffcb6e90da898720 +size 31339 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e186719d474aede84ea694125a2c97e489d69fe --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:907f56718e72972f53505a574a32aab6ca374f3fd513d1bc2a3e9c18e870b6d5 +size 100736 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2682c99ba91dea883a15a048cf4f476e48a23df6 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9acdc36b0404fff44224d63f1031489ff675761f8155134b4e426f8df1c24d72 +size 72223 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56475b91439a86c8c79854ef9dea390c01ed2380 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06260fb49f515bc6e98755a98e25789ecfbea68fee3fa6bb90168369b7256bcc +size 47788 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4aeaa51a3999fab21171224e238cb571_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4aeaa51a3999fab21171224e238cb571_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8a34026f9a43932a65835dcc897494bbbb9604d --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4aeaa51a3999fab21171224e238cb571_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad84deebccecd74478c7dde82a849114efcfb74338a040e7bea0f3ac6274c65d +size 18655 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..270d6f3910a96861b90c245844afc0c311eca359 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd9136dfdbf82d19522012437f3b56ca4f69876372024744badff3d47750c1fb +size 42457 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aac964b80792425f646a33a1e249289e878016d9 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0b6537bc941cf2e6a2ca61497451d6ea34b4ac6bec0b797f0db4073eb70ba23 +size 31139 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/79aaab5889060cf8264226764a109cdb_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/79aaab5889060cf8264226764a109cdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b95185669a3322223df6a1af33c91d3f8ed50475 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/79aaab5889060cf8264226764a109cdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0e069ec71f576e4aacd42910165aedb09bafab7d5d34d48ab7fd54d6f4a896d +size 27490 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/832a0ce332e784fe80289e9f00f56574_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/832a0ce332e784fe80289e9f00f56574_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b311081aa7ba0479c652f38be443e3a969d9a6c --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/832a0ce332e784fe80289e9f00f56574_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:976f2f059a9b2e92028a9c53c3cb0d48b7d7f68a8bcbf284e329493ce3370b38 +size 51296 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e96fe10e2b1ce56dd9edd9172a94346bd98d098 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1085fe2bad312eff29c977dd8818e277a2a3154dce88b503c4e1eaa3e785a8f1 +size 65985 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d58c31b2bb18400625995e8bf8d989d1592944c --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b35ea3e304aad7d350a9902270413930_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a71d354236408b856b4989e008514e4d6ebf18b379db1e1107597bc13cf67922 +size 18088 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b76d1b06cf06e1c28f844e68507b40ed_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b76d1b06cf06e1c28f844e68507b40ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33159e8aed619f0f69cf3d263ad34e3bf1b42b11 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b76d1b06cf06e1c28f844e68507b40ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9705759ab38b164a90f6bd617727b9b6a02f3abd075c57399d7bce496a5f5305 +size 23060 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39ed73c5fa9abffc60173de1b739b8a009afa1af --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f482aaf152202f92db8ac343af310a54135c592189c845b92ae75b985c21063d +size 38067 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80e73a8f52476456ff9066d84493407dd886925f --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d72feeb22ed898b89bf8b35be4a517a995c42e4706ef0ebd20f1b1f531160fd3 +size 44379 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00813237def021ddc843700fcb4716c05d8411b1 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/c3254408eadbf152632a8faf16310722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95dd1b18baa7c2e6db337aa65e085477ee63a29b3f1c744b9d16e6f5900c7aca +size 80635 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f14f0843f9944e61124817d06809d7ad_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f14f0843f9944e61124817d06809d7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c3c35bc49acdf45c31b5d93e2773e0fcfdb81c5 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f14f0843f9944e61124817d06809d7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a7fb776942df700d1e6db3b04cc1c61c56e5492fcf17a155ba93759cbf2f276 +size 16192 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3fe747617414a9281cc6c4488179b3a171225a9 --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62aea6785cab3292be96002f4e42edb630f0db3ab369d6ab4c84bf6d35f306ac +size 44361 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6f595819d9d2bdb82aab147c8497fa0bc0078bb --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31904a70140c495c81f9c8a656decb2c7e1efa4221ea061bcccfe8e54fe556f9 +size 55912 diff --git a/marked/M/T-REC-M.3208.1-199710-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5335fb06f7d0249a234f01bb72a327c65e3dbfb --- /dev/null +++ b/marked/M/T-REC-M.3208.1-199710-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:135ab36c3cb4a80f3c1768005d8221c7bd2ab6ecb2ce66c05d29ab83b3318ce6 +size 44550 diff --git a/marked/M/T-REC-M.3208.2-199903-I_PDF-E/raw.md b/marked/M/T-REC-M.3208.2-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7c5bef1d8c45aae0e502c3561163775612e731a9 --- /dev/null +++ b/marked/M/T-REC-M.3208.2-199903-I_PDF-E/raw.md @@ -0,0 +1,1236 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3208.2** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(03/99) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**TMN management services for dedicated and +reconfigurable circuits network: Connection +management of pre-provisioned service link +connections to form a leased circuit service** + +ITU-T Recommendation M.3208.2 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **TMN MANAGEMENT SERVICES FOR DEDICATED AND RECONFIGURABLE CIRCUITS NETWORK: CONNECTION MANAGEMENT OF PRE-PROVISIONED SERVICE LINK CONNECTIONS TO FORM A LEASED CIRCUIT SERVICE** + +## **Summary** + +This Recommendation is one of the series of M.3200 TMN management service Recommendations that provide descriptions of management services, goals and context for the dedicated and reconfigurable circuits network. This Recommendation provides a profile of Recommendation M.3208.1 for customer administration of leased circuit services using pre-provisioned resources (link connections). This is done by using existing function sets, functions and parameters from Recommendation M.3208.1 and adding additional semantics and restrictions. + +## **Source** + +ITU-T Recommendation M.3208.2 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999. + +## **Keywords** + +Connection management, Dedicated and reconfigurable circuits network, Leased circuits, Leased circuit services, Telecommunications Management Network (TMN), TMN Management service. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1999 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References and related Recommendations ..... | 1 | +| 2.1 | References..... | 1 | +| 2.2 | Related Recommendations ..... | 2 | +| 3 | Definitions ..... | 2 | +| 3.1 | Service-related definitions ..... | 2 | +| 3.2 | Role-related definitions ..... | 3 | +| 3.3 | Transport network resource definitions ..... | 3 | +| 4 | Abbreviations..... | 4 | +| 5 | Conventions ..... | 4 | +| 5.1 | Legend for the information flow tables ..... | 4 | +| 5.2 | Format of function sets follows Recommendation M.3208.1 ..... | 5 | +| 6 | Connection management service security..... | 5 | +| 7 | Customer administration management service ..... | 6 | +| 7.1 | Management service description ..... | 6 | +| 7.2 | Management goals ..... | 6 | +| 7.2.1 | High-level service customer requirements for connection management..... | 6 | +| 7.2.2 | Specific functional requirement..... | 6 | +| 7.2.3 | Relationship with Recommendation M.3208.1 ..... | 7 | +| 7.3 | Management context description ..... | 8 | +| 7.3.1 | Roles ..... | 8 | +| 7.3.2 | Telecommunications services and resources ..... | 8 | +| 7.3.3 | Management functions ..... | 13 | +| 8 | Management scenarios..... | 28 | +| 8.1 | Scenarios for connection management functions ..... | 28 | +| 8.1.1 | Scenarios for CM leased circuit service creation ..... | 28 | +| 8.1.2 | Scenarios for CM leased circuit service deletion ..... | 29 | +| 8.1.3 | Scenarios for CM leased circuit service modification..... | 29 | +| 8.2 | Scenarios for CM leased circuit service status administration ..... | 29 | +| 8.2.1 | Scenarios for report deletion of CM leased circuit service to service customer..... | 29 | +| 8.2.2 | Scenario for loopback creation ..... | 30 | +| 8.2.3 | Scenario for loopback deletion ..... | 30 | + +| | Page | +|---------------------------------------------------------------------|-------------| +| 8.2.4 Scenario for loopback modification ..... | 30 | +| 8.2.5 Scenario for locked LCSs identifying ..... | 30 | +| 8.2.6 Scenario for failed LCS restoration..... | 31 | +| 9 Architecture ..... | 31 | +| 9.1 Functional architecture ..... | 31 | +| 9.2 Physical architecture ..... | 31 | +| Appendix I – A SONET private line service example..... | 32 | +| Appendix II – Ordering processes for service link connections ..... | 33 | + +# Introduction + +Recommendation M.3208.1 specifies customer management of leased circuit services. This Recommendation builds upon the management services of M.3208.1 in the case of pre-provisioned resources. Hence, the pre-service phase (from initiation of customer request to create service until service creation is completed) only involves connecting existing, pre-provisioned resources, and normally will be completed within a short period of time (nearly instantaneous). + +This Recommendation builds upon the dedicated LCS create function defined in Recommendation M.3208.1 by requiring that all of the service link connections which support the LCS exist prior to the submission of the create request. Future work will address additional connection management functions. + +This Recommendation supports the relationship between services and enabling transport technologies described in Recommendation M.3208.1. For convenience, the M.3208.1 statement of this relationship is quoted here. "In general, the definition of a service should be independent of the particular network used to transport the service. This allows multiple technologies to support the service. Therefore, network level information should not be presented to the service layer. However, specific service features may be defined which allow network or network element information to be presented to a service customer. In this case, an abstraction of the information appropriate to the service feature is transferred." + +This X interface at the TMN service management layer allows service customers to manage pre-provisioned link connection services without a detailed knowledge of the service provider's network elements and network topology. The connection management LCS may be offered by one or more Service Providers (SP). The CM LCS is defined between a single SC and a single SP. The Service Customer (SC) may have different levels of visibility to the technology used to provide the service link connections. + +Clause 6 provides the requirements for security of the CM LCS. + +Clause 7 provides the requirements for customer administration. This includes configuration, status administration and testing function sets. + +Appendix I shows a SONET private line service example. + +Appendix II shows a North American specific ordering process for the service link connections. + + + +###### **TMN MANAGEMENT SERVICES FOR DEDICATED AND RECONFIGURABLE CIRCUITS NETWORK: CONNECTION MANAGEMENT OF PRE-PROVISIONED SERVICE LINK CONNECTIONS TO FORM A LEASED CIRCUIT SERVICE** + +*(Geneva, 1999)* + +# **1 Scope** + +This Recommendation describes a subset of TMN management services for dedicated and reconfigurable leased circuits network identified in Recommendation M.3200 as a TMN managed area. Its main focus is on the real-time connection management of pre-provisioned service link connections. These management services may also be applicable for interactions between management systems of different service providers or within a service provider. + +TMN management services in this Recommendation specify interface requirements between Operation Systems (OS) to perform customer management of LCS using pre-provisioned resources. The interfaces addressed by the TMN management services in this Recommendation are applicable to both the X interface and the Q3 interface. Support for the services described in this Recommendation is at the discretion of the service provider. + +The TMN management services in this Recommendation are described using the GDMS template contained in Recommendation M.3020 and build on the management services defined in Recommendation M.3208.1. + +# **2 References and related Recommendations** + +## **2.1 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation G.805 (1995), *Generic functional architecture of transport networks*. +- CCITT Recommendation M.125 (1988), *Digital loopback mechanisms*. +- ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network*. +- ITU-T Recommendation M.3020 (1995), *TMN interface specification methodology*. +- ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: Overview*. +- ITU-T Recommendation M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*. + +- ITU-T Recommendation M.3320 (1997), *Management requirements for the TMN X-interface*. +- ITU-T Recommendation M.3400 (1997), *TMN management functions*. +- CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information*. +- CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1993, *Information technology – Open Systems Interconnection – Systems Management: State management function*. + +## 2.2 Related Recommendations + +- CCITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, *Information technology – Open Systems Interconnection – Systems Management: Event report management function*. +- CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems Management: Log control function*. + +# 3 Definitions + +## 3.1 Service-related definitions + +This Recommendation makes use of the following terms defined and/or specialized in Recommendation M.3208.1: + +- connection point; +- dedicated leased circuit service; +- diversity; +- layer network; +- leased circuit service; +- link connection; +- network connection; +- reconfigurable leased circuit service; +- service access group; +- service access point; +- service characteristic; +- service customer; +- service node; +- service provider; +- subnetwork connection; +- subnetwork; +- termination connection point. + +This Recommendation defines the following terms: + +**3.1.1 route:** A sequence of transport architectural entities, e.g. connection points, links, link connections, subnetworks, over which an LCS is provided. See Recommendation G.805 for the basis of this definition. + +NOTE – This usage of route is not defined in the definitions clause of Recommendation M.3208.1, but only in the definition of a parameter there. That usage does not include the concept of link connection. There is a fundamental need for that concept in CM. + +**3.1.2 CM schedule:** A list of time periods during which a CM LCS has an availability status of on-duty (not off-duty). The definition of availability status can be found in Recommendation X.731. + +**3.1.3 service link connection:** A link connection used by connection management to construct a CM LCS. + +**3.1.4 dedicated service link connection:** A service link connection which is reserved for the exclusive use of a single SC. + +**3.1.5 shared service link connection1:** A service link connection which can be used by a predefined set of SCs. That is, during a specific time period, only one SC can use the SLC, and the right to use the SLC is assigned on a first come, first served basis or other priority scheme defined by a SLA. + +## **3.2 Role-related definitions** + +This Recommendation makes use of the following terms defined or specialized in Recommendation M.3208.1: + +- service customer – alternate term for "customer" in Recommendation M.3208.1; +- service provider; +- diversity; +- service characteristic. + +## **3.3 Transport network resource definitions** + +This Recommendation makes use of the following terms defined in the transport network architecture, Recommendation G.805 or specialized in Recommendation M.3208.1: + +- layer network; +- subnetwork; +- link; +- access group; +- access point; +- trail; +- connection point; +- termination connection point; +- link connection; +- subnetwork connection; +- network connection; +- service node. + +--- + +1 The extent to which service customers using shared service link connections know the identities of other SCs using these shared service link connections is outside of the scope of this Recommendation. This matter is expected to be addressed in the service contract between the SP and SC. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|----------|-------------------------------------------------------| +| ADM | Add Drop Multiplexer | +| ATM | Asynchronous Transfer Mode | +| BLSR | Bidirectional Line Switched Ring | +| CM | Connection Management | +| CP | Connection Point | +| CPE | Customer Premise Equipment | +| DSn | Digital Signal Level n | +| EAO | Electronic Access Ordering | +| EB | Electronic Bonding | +| ECCKT ID | Exchange Carrier Circuit ID | +| GDMS | Guidelines for the Definition of TMN Managed Services | +| LCS | Leased Circuit Service | +| NE | Network Element | +| NML | Network Management Layer | +| PDH | Plesiochronous Digital Hierarchy | +| POP | Point of Presence | +| SAD | Service Access Domain | +| SAG | Service Access Group | +| SAP | Service Access Point | +| SC | Service Customer | +| SLA | Service Level Agreement | +| SLC | Service Link Connection | +| SML | Service Management Layer | +| SONET | Synchronous Optical Network | +| SP | Service Provider | +| TCP | Termination Connection Point | +| TMN | Telecommunications Management Network | +| UPSR | Unidirectional Path Switched Ring | + +# 5 Conventions + +## 5.1 Legend for the information flow tables + +The entry "See Recommendation M.3208.1" in the Notes column of an information flow table means that the entry is identical to the equivalent entry in Recommendation M.3208.1. In cases where the entry is a modified version of the M.3208.1 entry, the changes are shown using the + +underscore/strikethrough editing convention. If the Notes column is blank, refer to the previous usage of the same parameter in a previous table in this Recommendation. + +m Mandatory. + +m(=) The SP must provide the same value in the response as provided in the request by the SC. + +o Optional. Optionality is subject to definition according to the service level agreement or contract between the SC and SP, i.e. a parameter listed as optional may be made mandatory by the contract. + +o(=) Return of the value by the SP is optional; however, if the SP elects to return the value, it must be the same value supplied by the SC in the request. SP is not allowed to alter this field. + +c Conditional parameter, definition of the condition will be specified in the Notes column. A numeric suffix is used to enable reuse of the conditional statements. + +c(=) If the value is provided in the request by the SC, the SP must provide the same value in the response. + +Dash A dash implies that the parameter is not applicable. + +## 5.2 Format of function sets follows Recommendation M.3208.1 + +For ease of comparison, all of the functions for the function sets analogous to those in Recommendation M.3208.1 are included, although some of them are not used at all in this Recommendation. For example, the subclauses of 7.3.3.2 in this Recommendation correspond to the subclauses of 3.3.3.2 in Recommendation M.3208.1. + +# 6 Connection management service security + +This clause specializes the requirements for security found in Recommendation M.3016. + +Security is defined between a single SC and SP. Several security services are required to assure the proper functioning of LCS CM. + +The following services are mandatory services for CM: + +- a) Peer entity authentication and data origin authentication are needed to prevent spoofing attacks and uniquely identify the SC. +- b) Integrity is needed to prevent unauthorized modification of data in transit. +- c) Access control is needed to assure that one service customer does not gain access, maliciously or accidentally, to other customers' data. The SP may use the authenticated identity of the SC to provide access control. + +The following three services are optional services for connection management: + +- a) Confidentiality may be needed if private information is being exchanged. This security service may not be needed for all LCS management messages. +- b) Non-repudiation of origin may be needed, e.g. when a SC requests a service that may cause the service provider to invest labour and/or materials. This security service may not be needed for all LCS management messages. +- c) Non-repudiation of delivery may be needed, e.g. when a SC reports a problem. This security service may not be needed for all LCS management messages. + +In addition, security management functions, per Recommendation M.3400, are needed to manage the security-related information needed to support the security services described above. The exact + +nature of the security management functions depends on the selection of security mechanisms used to provide the security services. Security management is outside the scope of this Recommendation. + +# **7 Customer administration management service** + +## **7.1 Management service description** + +This management service addresses the management interface between the SP domain and the SC domain. It is based on an abstract view of the resources underlying a particular service, a view that shields the service user from knowledge of the specific technical implementation that supports the service. + +Service Customers (SCs) want mechanized, error-free, reject-free, rapid provisioning of LCSs. SCs want to go beyond the traditional service ordering process and directly reconfigure their LCSs in real-time or near real-time. One way to accomplish this (assumed in this Recommendation) is for SCs to lease service link connections from their Points of Presence (POP), their access terminals, or their end-user locations to subnetworks in the Service Provider's (SP) network. SCs would also lease service link connections between appropriate SP's subnetworks. SCs would then use the connection management functions defined in this Recommendation to create in real-time or near real-time, LCSs composed of these pre-provisioned service link connections. + +A specific service link connection can be dedicated to a specific SC, or it can be sharable among a specified group of SCs. The service link connections can be ordered using existing service ordering processes or future ordering processes (for further study)2. + +## **7.2 Management goals** + +The goal of this management service is to provide the SC with the capability to create, modify, or delete a CM LCS using pre-provisioned link connections. This also supplements the services defined in M.3208.1 by allowing a CM LCS user to create a CM LCS by explicitly specifying the ordered set of link connections that comprise the end-to-end service, in near real-time. + +### **7.2.1 High-level service customer requirements for connection management** + +- 1) An X interface at the TMN service management layer is required so that SCs can create CM LCSs without a detailed knowledge of the SP's network elements and network topology. +- 2) Because CM is not a stand-alone interface, it is required to be compatible with other leased circuit service level functions such as trouble management, service provisioning, configuration management, alarm reporting and performance monitoring. +- 3) The secure use of CM requires that unauthorized users cannot affect the management of, or obtain information concerning, CM services. +- 4) There is a requirement for dedicated service link connections between SP subnetworks or for a pool of first-come, first-served service link connections which can be shared among SCs using CM. + +### **7.2.2 Specific functional requirement** + +The goal of this management service is to provide the SC with the capability to create, modify, or delete a LCS. Service providers may support a subset of the requirements addressed by this Recommendation. + +--- + +2 See Appendix II for a discussion of a process for ordering service link connections. + +Not all of the following specific functional requirements are within the scope of this Recommendation. See Table 1 for the identification of the requirements addressed herein. The following functional requirements are applicable to customer management of leased circuit services: + +**Table 1/M.3208.2 – CM functions supported in this Recommendation** + +| Requirement | Supported by this Recommendation | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| 1) Access to an inventory of dedicated and shared pre-provisioned service link connections with which to build CM LCS. | Yes | +| 2) A service to specify service link connections and schedule a CM LCS for future use. | Yes | +| 3) A service to assign various types of priorities to LCS. An example of a priority type is backup priority, i.e. the order in which a CM LCS should be used as a backup in case of an LCS failure. | Yes | +| 4) A service to specify CM LCS by a sequence of service access points, connection points, and service link connections. A specific specification may, but is not required to, contain all of these elements. | Specified as a pair of SAPs or a sequence of service link connections | +| 5) A service to select the "best" service link connection from a set of locked link connections. For example, the best link connection may be defined as one with the highest or lowest value for a specific priority type. | No | +| 6) A service to modify LCS characteristics. LCSs should be modifiable in at least two ways, i.e. turning automatic restoration on/off and changing the value of the priority parameter. | Priority parameter is supported | +| 7) A service to delete CM LCSs. | Yes | +| 8) Subject to service link connection availability, a service to specify time periods during which a CM LCS will be available for use. | Yes | +| 9) A service to restore LCSs, e.g. "automatically" restore a failed CM LCS with the "best" available locked pre-provisioned LCS. | No | +| 10) A service to establish and terminate loopbacks on service link connections, where supported, for pre-use testing and trouble localization | Yes | +| 11) A service to determine, for a specified CM LCS, the earliest time at which the pre-provisioned service link connections comprising this CM LCS are available to support this CM LCS. | No | +| 12) Support for point-to-point, point-to-multipoint, and multipoint-to-multipoint services. | Point-to-point only | +| 13) Support for unidirectional and bidirectional symmetric (same bandwidth in both directions) and asymmetric services | Symmetric services only | +| 14) Support for CM LCS based on subrate services. | No | +| NOTE – The capabilities not addressed in this Recommendation are for further study. | | + +### 7.2.3 Relationship with Recommendation M.3208.1 + +The relationship with Recommendation M.3208.1 includes the following ten concepts: + +- 1) The link connection configuration service function set in Recommendation M.3208.1 or some other service has been used to pre-provision link connections for use in the CM LCS service. + +- 2) As noted in the definitions (clause 3, Definitions), the route has been defined to include the possibility that it might be specified in terms of link connections. +- 3) The service access domain configuration function set in Recommendation M.3208.1 or some other services may be used to manage service access domain configuration. +- 4) Creating a CM LCS is an instant service. Consequently, there is no need for the concept of a service request, the associated state model and the status administration function set, nor the link connection status administration function set. +- 5) The CM LCS involves creating and deleting a dedicated service. The extension provided here is to allow the service customer to specify the pre-provisioned dedicated link connections that are required to create the service. +- 6) There is no atomic reconfiguration function defined in the reconfigurable LCS function set in Recommendation M.3208.1. This Recommendation does not specify such a function either, but instead, uses the mechanism of create and delete identified in Recommendation M.3208.1 to assemble pre-provisioned link connections within a service access domain. Explicitly, this Recommendation permits the specification of mid-link connections in addition to the end-link connections. +- 7) Groups of end points are dedicated to a customer, and end-links can only be chosen from within that domain. However, the mid-links might be shared among several customers as provided by a Service Level Agreement (SLA). +- 8) Every instance of a CM LCS is an instance of a dedicated LCS for the period during which it is up. It is possible to share the service link connections among CM LCS if the scheduled usage does not overlap. +- 9) Scheduling link connections for use by in CM LCS is the responsibility of the service customer, because CM LCS uses pre-provisioned link connections. +- 10) In Recommendation M.3208.1, any access point may be connected to any other access point in the SC's Service Access Domain (SAD) to form an LCS. In CM, access points are bound to service link connections (end-links). In the typical case considered in CM, LCSs can only be created between a subset of the set of SAP pairs defined for a SAD because the appropriate mid-links may not be available. In CM, unrestricted connectivity between an arbitrary pair of SAPs at any time would require the SC to purchase the number of service link connections required to insure that such LCSs could be created. + +## 7.3 Management context description + +### 7.3.1 Roles + +The following roles defined in Recommendation M.3208.1 apply: + +- service customer; +- service provider. + +### 7.3.2 Telecommunications services and resources + +#### Link + +The link represents a topological relationship. It also represents the availability of transport capacity of a specific service characteristic (e.g. capacity, quality of service) between the two subnetworks or between a subnetwork and an access group. + +#### End-link + +For the purpose of this Recommendation, links can be divided into two topological types: end-links and mid-links. An end-link is an association between a subset of a Service Access Group (SAG), i.e. a set of SAPS, and a subset of ports at the edge of a subnetwork. + +#### End-link connection + +The end-link connection is an association between a termination connection point and a connection point. + +#### Mid-link + +A mid-link is an association between subsets of ports at the edge of two subnetworks. Figure 3 illustrates a service layer network partitioned into two subnetworks with end-links and mid-links identified. + +#### Mid-link connection + +A mid-link connection is an association between two connection points on different subnetworks + +Figure 1 is a reproduction of Figure 6/M.3208.1 which illustrates the topology of the reconfigurable LCS. The legend has been added to clarify the figure. The concepts of service access group and service access domain have general application, despite the fact that they are introduced in the reconfigurable LCS portions of Recommendation M.3208.1. See that Recommendation for a detailed discussion of these concepts. + +Figure 2 illustrates the CM perspective described in this Recommendation. It provides a general topology view of a network of link connections and introduces the idea that link connections might be divided between those that touch the edge of a SP's network and those that are totally internal. Definitions for the links and link connections follow. + +The service access points shown in Figure 1 are further decomposed in Figure 2 to indicate the termination of a link connection in a TCP. + +Figure 3 shows a service layer network, with service access groups and subnetworks, along with the links connecting them. Again, it shows that links can be classified as end-links and mid-links. These links are the carriers of the link connections (shown in Figure 2) that are the focus of this Recommendation. + +In order to create CM LCSs, the SC need not be aware of the details of the SP's network. The specific transport systems, cross-connect elements, multiplexers, etc., are replaced by the concept of contiguous service link connections and a set of compatibility requirements on adjacent link connections. + +Figure 4 illustrates these concepts. It expands Figure 3 by showing the link connections that comprise the links. This example assumes that the link connections shown are pre-provisioned link connections which the SC has leased or purchased and that the subnetwork connections can be made and broken by management processes. In Figure 4, a CM LCS between a SAP in Service Access Group 1 and one in Service Access Group 3 is composed of the following sequence of entities: + +- 1) the service link connection between TCP1 and CP1; +- 2) the service subnetwork connection between CP1 and CP2; +- 3) the service link connection between CP2 and CP3; +- 4) the service subnetwork connection between CP3 and CP4; +- 5) the service link connection between CP4 and TCP2. + +In CM, the same LCS can be specified by a sequence of service link connections or by the SAPs at the end points of the LCS. For example, the sequence of service link connections which correspond to the LCS highlighted in Figure 4 are: + +- 1) End-link connection 1; +- 2) Mid-link connection 1; +- 3) End-link connection 2. + +The SC is unaware of the nature of Subnetworks 1 and 2 and does not explicitly request subnetwork connections. + +Two alternative specifications for a CM LCS between SAG 1 and SAG 3 are: + +- 1) TCP1; +- 2) TCP2; + +or + +- 1) TCP1; +- 2) ; +- 3) TCP2. + +Pre-provisioned service link connections are the building blocks from which service customers can construct a CM LCS. Appendix II discusses a process by which SCs obtain pre-provisioned service link connections. + +As indicated in Figures 1 to 4, pre-provisioned end-link connections are dedicated to a particular SC. Pre-provisioned mid-link connections can be dedicated to a particular SC or can be in a shared pool of resources which are used by SCs on a first-come, first-served basis. + +The service level link connection model applies equally well a number of network technologies, e.g. ATM, SDH, or PDH-based LCS, or services that are a hybrid of two or more. + +![Topology diagram of a reconfigurable leased circuit service (LCS) showing four locations (A, B, C, D) connected to a central SP subnetwork. Each location has a service access group with four service access points (SAP A, B, C, D). Connections are shown between these SAPs and the central subnetwork via sets of connection points. Solid lines represent subnetwork connections, while dashed lines represent alternative subnetwork connections. The entire system is enclosed in a dashed box labeled 'Customer reconfigurable leased circuit service SAD'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Topology diagram of a reconfigurable leased circuit service (LCS) showing four locations (A, B, C, D) connected to a central SP subnetwork. Each location has a service access group with four service access points (SAP A, B, C, D). Connections are shown between these SAPs and the central subnetwork via sets of connection points. Solid lines represent subnetwork connections, while dashed lines represent alternative subnetwork connections. The entire system is enclosed in a dashed box labeled 'Customer reconfigurable leased circuit service SAD'. + +T0409960-98 + +![Service access group symbol: an oval containing four dots. Set of connection points symbol: an oval. Service access point symbol: a small dot. SP subnetwork symbol: a circle. Subnetwork connection symbol: a circle with a horizontal line through it. Alternative subnetwork connection symbol: a dashed circle.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +| | | | | +|--|--------------------------|-----|-----------------------------------| +| | Service access group | SAP | Service access point | +| | Set of connection points | SAD | Service access domain | +| | Service access point | | SP subnetwork | +| | Subnetwork connection | | Alternative subnetwork connection | + +Service access group symbol: an oval containing four dots. Set of connection points symbol: an oval. Service access point symbol: a small dot. SP subnetwork symbol: a circle. Subnetwork connection symbol: a circle with a horizontal line through it. Alternative subnetwork connection symbol: a dashed circle. + +**Figure 1/M.3208.2 – Example topology of the reconfigurable LCS** + +![Figure 2/M.3208.2 – Example topology for the CM LCS. This diagram shows a central shaded area containing two subnetworks, Subnetwork 1 and Subnetwork 2. Subnetwork 1 contains four 'CP' (Control Point) nodes, and Subnetwork 2 contains five 'CP' nodes. A dashed line labeled 'Mid-link connection (between subnetworks)' connects a 'CP' in Subnetwork 1 to a 'CP' in Subnetwork 2. Outside the shaded area are four locations: Location A (top right) with four 'TCP' nodes, Location B (top left) with four 'TCP' nodes, Location C (left) with two 'TCP' nodes, and Location D (bottom) with one 'TCP' node. Dashed lines labeled 'End-link connection' connect 'TCP' nodes to 'CP' nodes: Location A to a 'CP' in Subnetwork 1, Location B to a 'CP' in Subnetwork 1, Location C to a 'CP' in Subnetwork 2, and Location D to a 'CP' in Subnetwork 2. A legend at the bottom left shows a 'CP' connected to a 'TCP' as an 'End-link connection' and two 'CP' nodes connected as a 'Mid-link connection (between subnetworks)'. The text 'T0409970-98' is in the bottom right.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Figure 2/M.3208.2 – Example topology for the CM LCS. This diagram shows a central shaded area containing two subnetworks, Subnetwork 1 and Subnetwork 2. Subnetwork 1 contains four 'CP' (Control Point) nodes, and Subnetwork 2 contains five 'CP' nodes. A dashed line labeled 'Mid-link connection (between subnetworks)' connects a 'CP' in Subnetwork 1 to a 'CP' in Subnetwork 2. Outside the shaded area are four locations: Location A (top right) with four 'TCP' nodes, Location B (top left) with four 'TCP' nodes, Location C (left) with two 'TCP' nodes, and Location D (bottom) with one 'TCP' node. Dashed lines labeled 'End-link connection' connect 'TCP' nodes to 'CP' nodes: Location A to a 'CP' in Subnetwork 1, Location B to a 'CP' in Subnetwork 1, Location C to a 'CP' in Subnetwork 2, and Location D to a 'CP' in Subnetwork 2. A legend at the bottom left shows a 'CP' connected to a 'TCP' as an 'End-link connection' and two 'CP' nodes connected as a 'Mid-link connection (between subnetworks)'. The text 'T0409970-98' is in the bottom right. + +**Figure 2/M.3208.2 – Example topology for the CM LCS** + +![Figure 3/M.3208.2 – Illustration of the topology of a service layer network. This diagram shows a 'Service layer network' represented by a large rectangle. Inside, there are two subnetworks, 'Subnetwork 1' and 'Subnetwork 2', connected by a vertical dashed 'Mid-link'. Five 'Service Access Groups' are shown: Group 1 (left), Group 2 (top right), Group 3 (middle right), Group 4 (bottom right), and Group 5 (bottom). Dashed lines labeled 'End-link' connect these groups to the subnetworks: Group 1 to Subnetwork 1, Group 2 to Subnetwork 1, Group 3 to Subnetwork 1, Group 4 to Subnetwork 2, and Group 5 to Subnetwork 2. A legend at the bottom left shows a dashed line labeled 'Service link'. The text 'T0409980-98' is in the bottom right.](5445597cceefaca1ac89e710fe339325_img.jpg) + +Figure 3/M.3208.2 – Illustration of the topology of a service layer network. This diagram shows a 'Service layer network' represented by a large rectangle. Inside, there are two subnetworks, 'Subnetwork 1' and 'Subnetwork 2', connected by a vertical dashed 'Mid-link'. Five 'Service Access Groups' are shown: Group 1 (left), Group 2 (top right), Group 3 (middle right), Group 4 (bottom right), and Group 5 (bottom). Dashed lines labeled 'End-link' connect these groups to the subnetworks: Group 1 to Subnetwork 1, Group 2 to Subnetwork 1, Group 3 to Subnetwork 1, Group 4 to Subnetwork 2, and Group 5 to Subnetwork 2. A legend at the bottom left shows a dashed line labeled 'Service link'. The text 'T0409980-98' is in the bottom right. + +**Figure 3/M.3208.2 – Illustration of the topology of a service layer network** + +![Diagram showing the relationship between link services and leased circuit services. It features two subnetworks (Subnetwork 1 and Subnetwork 2) connected by a mid-link connection. Subnetwork 1 is connected to Service Access Group 2 and Service Access Group 3. Subnetwork 2 is connected to Service Access Group 1, Service Access Group 4, and Service Access Group 5. Various connection points (CP, TCP) are labeled throughout the diagram.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +The diagram illustrates the network architecture for leased circuit services. At the top, **Subnetwork 1** (a white oval) has connection points **CP**, **CP3**, and **CP4**. **CP** connects via an **End-link connection** (dashed line) to a **TCP** (double oval) which leads to **Service Access Group 2** (grey oval). **CP4** connects via **End-link connection 2** to a **TCP2** leading to **Service Access Group 3** (grey oval). **CP3** connects via **Mid-link connection 1** (dashed line) to **Subnetwork 2** (white oval). **Subnetwork 2** has connection points **CP1**, **CP2**, and **CP**. **CP1** connects via **End-link connection 1** to a **TCP1** leading to **Service Access Group 1** (grey oval). **CP2** is the interface with **Mid-link connection 1**. **CP** connects via an **End-link connection** to a **TCP** leading to **Service Access Group 4** (grey oval). Below **Subnetwork 2**, another **CP** connects via an **End-link connection** to a **TCP** leading to **Service Access Group 5** (grey oval). A legend at the bottom left defines the symbols: dashed line for **Link connection**, dashed line with an arrow for **Subnetwork connection**, **CP** for **Connection point**, **SN** for **Subnetwork**, **TCP** for **Termination connection point**, grey oval for **Service customer access group**, and white oval for **Service provider subnetwork**. The code **T0409990-98** is in the bottom right. + +Diagram showing the relationship between link services and leased circuit services. It features two subnetworks (Subnetwork 1 and Subnetwork 2) connected by a mid-link connection. Subnetwork 1 is connected to Service Access Group 2 and Service Access Group 3. Subnetwork 2 is connected to Service Access Group 1, Service Access Group 4, and Service Access Group 5. Various connection points (CP, TCP) are labeled throughout the diagram. + +**Figure 4/M.3208.2 – Relationship between link services and leased circuit services** + +### **7.3.3 Management functions** + +Table 2 contains the management functions sets specified in Recommendation M.3208.1 for the customer administration management service and indicates which function sets contain functions specialized in this Recommendation. + +**Table 2/M.3208.2 – M.3208.1 function sets specialized in CM** + +| M.3208.1 function sets | Function sets specialized in this Recommendationa) | +|-------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| Dedicated LCS configuration function set | See 7.3.3.1 | +| Dedicated LCS status administration function set | See 7.3.3.2 | +| Link connection configuration service function set | Outside the scope of this Recommendation | +| Link connection status administration function set | Outside the scope of this Recommendation | +| Reconfigurable LCS configuration function set | Outside the scope of this Recommendation | +| Reconfigurable LCS function set | Outside the scope of this Recommendation | +| Service access domain configuration function set | Outside the scope of this Recommendation | +| Reconfigurable LCS administration function set | Outside the scope of this Recommendation | +| Access equipment status administration function set | Outside the scope of this Recommendation | +| a) Not all of the functions contained in the indicated function sets are specialized or required in this Recommendation. | | + +In addition to the function sets specialized from Recommendation M.3208.1, the following functions and function sets in Table 3 are used in this Recommendation. + +**Table 3/M.3208.2 – New function sets and functions** + +| M.3208.1 function sets | Reference | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| Dedicated LCS configuration function set:
Replace a failed CM LCS function | See 7.3.3.1.5 | +| Dedicated LCS status administration function set:
Identify locked LCS function | See 7.3.3.2.10 | +| Leased circuit service test function set:
Initiate loopback of end-of-link connection function
Terminate loopback of end-of-link connection function | See 7.3.3.4 | + +#### **7.3.3.1 CM leased circuit service configuration function set** + +The SC must be able to request the creation and deletion of a CM LCS, as well as the modification of the dedicated leased circuits, and be notified of the completion or rejection of the creation, deletion, or modification request. The functions in this set are: + +- 1) Create CM leased circuit service; +- 2) Delete CM leased circuit service; +- 3) Modify CM leased circuit service; +- 4) (Not applicable for CM) Cancel CM leased circuit service request. + +##### **7.3.3.1.1 Create CM leased circuit service function** + +###### **7.3.3.1.1.1 Summary** + +Recommendation M.3208.1 provides the SC a general mechanism to request the creation of dedicated LCS from the SP. According to Recommendation M.3208.1, the response from the SP must be one of the following three types: + +- 1) The create request has been rejected with a reason code indicating probable cause. + +- 2) A completion response indicating that the create function request has been processed coincident with receipt of the request. All information required to be provided to the SC is contained in the completion response. +- 3) An acknowledgement to the SC that the request has been received, is being processed, and that completion of the request will be reported to the SC at a later time. + +One of the requirements of this Recommendation is that the SC can create LCS in real-time or near real-time. Consequently, the SC is required to have pre-provisioned service link connections which are used to create the CM LCS. Given this requirement, only responses 1 and 2 are possible in this Recommendation. For this reason the service request state model is not used. + +###### 7.3.3.1.1.2 Information flow + +**Table 4/M.3208.2 – Information flow for create CM leased circuit service function** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|------------------------------|------------------|------------------|---------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Service name | m | o | m | o | See Recommendation M.3208.1. | +| Service class | o | c | o | c | See Recommendation M.3208.1. | +| Bandwidth | o | c | o | c | o – Support of bandwidth specification is subject to SLA.
c – If the requested bandwidth cannot be provided by the SP, the SP shall return the value together with a reason code indicating that the bandwidth is not available. If the response is not indicating a completion, the SP, may report an error condition with a reason code indicating that the available service differs from the customers initial service request. | +| Quantity | o | c | – | – | At most one CM LCS is created per Create command. | +| Service termination date | o | c | o | c | See Recommendation M.3208.1. | +| Schedule | o | c | o | c | See Recommendation M.3208.1. | +| Service availability date | o | m | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Service request state | – | c | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Service administrative state | o | o(=) | o | o(=) | See Recommendation M.3208.1. | + +**Table 4/M.3208.2 – Information flow for create CM leased circuit service function (continued)** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|------------------------------------|------------------|------------------|---------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Service operational state | – | o | – | o | See Recommendation M.3208.1. | +| Diversity | o | c | – | – | The complexity of the diversity arrangements can be handled in the original provisioning of the link connections. | +| Link connection selection criteria | – | – | c1 | cl(=) |

c1 – This parameter is only valid when the CM LCS is requested with SAPs and the route is specified by the SP. If the SC specifies all the components of the CM LCS, there is no freedom for the SP to try to find diverse link connections. The SC may specify constraints on the pre-provisioned service link connections to be used:

  1. 1) No restrictions;
  2. 2) Survivable link connections only;
  3. 3) Survivable and dedicated link connections only;
  4. 4) Dedicated link connections only and survivable link connections preferred;
  5. 5) Dedicated and survivable link connections preferred.
| +| Route | o | o | c2 | c2(=) | c2 – Either the route or the originating and terminating SAPs must be present in the service request. If pre-provisioned link connections are specified, this is the field that contains the ordered set-of-link connections. | +| Originating location | m | o(=) | – | – | The requirement that pre-provisioned SAPs or a route must be specified precludes asking for service to a street address. | + +**Table 4/M.3208.2 – Information flow for create CM leased circuit service function (continued)** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|-------------------------------------------|------------------|------------------|---------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Terminating location | m | o(=) | – | – | The requirement that pre-provisioned SAPs or a route must be specified precludes asking for service to a street address. | +| Originating location CPE type | o | o(=) | o | o(=) | See Recommendation M.3208.1. | +| Terminating location CPE type | o | o(=) | o | o(=) | See Recommendation M.3208.1. | +| Customer contact | m | o(=) | m | o(=) | See Recommendation M.3208.1. | +| Provider request number | – | m | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Customer request number | o | o(=) | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Alias name | o | o(=) | o | o(=) | Customer supplied circuit identifier. | +| Originating location service access point | o | o | c2 | m(=) | If a value is specified for this attribute, then this value is returned. If no value is specified, then the value of the SAP associated with an end-link connection is returned. | +| Terminating location service access point | o | o | c2 | m(=) | If a value is specified for this attribute, then this value is returned. If no value is specified, then the value of the SAP associated with an end-link connection is returned. | +| Circuit number | – | c | – | m | This is the reference number that the service customer will use to manage the CM LCS. Because this is a real-time service, the circuit number must be returned if the request is successful. If the CM LCS is specified in terms of the SAPs, the circuit number returned may be that of a previously created, but locked CM LCS. | +| SP contact | – | m | – | m | See Recommendation M.3208.1. | + +**Table 4/M.3208.2 – Information flow for create CM leased circuit service function (concluded)** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|-----------------------|------------------|------------------|---------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Selection priority | – | – | o | o(=) | Specifies the SC's relative ranking of CM LCSs between the same set of SAPs. Priority can only be assigned if the intermediate link connections are specified. The criteria for assignment of priority are an SC matter. For example, priority might be assigned based on relative cost, quality of service, or physical length of the CM LCS. | +| Error and reason code | | c | | c | c – This parameter is present if the request is rejected because of one or more of the following reasons:
– Unknown service class;
– Unknown service name;
– Requested bandwidth not available;
– Resources unavailable;
– Underlying link connection operational state disabled;
– Invalid schedule conflict;
– Contract violation;
– Invalid parameter value;
– Required parameter not supplied;
– Non-existent SAP. | + +##### **7.3.3.1.2 Delete CM leased circuit service function** + +###### **7.3.3.1.2.1 Summary** + +This function permits the SC to delete a CM LCS. Before this can be done, the service administrative state of the CM LCS must be locked using the modify function in 7.3.3.1.3. The SC shall identify the circuit number of the CM LCS to be deleted in the request. When the CM LCS is deleted, it will disappear. + +###### 7.3.3.1.2.2 Information flow + +**Table 5/M.3208.2 – Information flow for delete CM leased circuit service function** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|--------------------------|------------------|------------------|---------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Circuit number | m | c | m | c | See Recommendation M.3208.1. | +| Service request state | – | c | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Service provider contact | – | o | – | o | See Recommendation M.3208.1. | +| Service termination date | o | o(=) | – | – | This parameter is not required as the delete function is provided in real-time or near real-time. | +| Provider request number | – | c | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Customer request number | o | o(=) | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Error | | c | | c |

c – This parameter is present if the request is rejected. Valid error codes are:

  • – Already deleted;
  • – Invalid circuit number;
  • – Not being in appropriate service administrative state;
  • – Contract violation.
| + +##### 7.3.3.1.3 Modify CM leased circuit service function + +The modify CM LCS function enables an SC to request the modification of a number of applicable parameters of the established CM LCS. + +###### 7.3.3.1.3.1 Summary + +Table 6 summarizes the information flows associated with modifying CM LCS parameters. + +Whenever the administrative state attribute of a CM LCS is changed to locked, this condition should be reflected in the relationship with the underlying link connections supporting the service. However, the link connections are still reserved for the use of the CM LCS, according to its schedule, as long as it continues to exist. + +###### 7.3.3.1.3.2 Information flow + +**Table 6/M.3208.2 – Information flow for modify CM leased circuit service function** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|-------------------------------------------|------------------|------------------|---------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Originating location CPE type | o | o(=) | o | o(=) | | +| Terminating location CPE type | o | o(=) | o | o(=) | | +| Customer contact | o | o(=) | o | o(=) | | +| Originating location service access point | c | o | – | – | This was changeable in Recommendation M.3208.1 because the information might have been added to a pending request. This parameter is not applicable because services are provided in real-time or near real-time. | +| Terminating location service access point | c | o | – | – | This was changeable in Recommendation M.3208.1 because the information might have been added to a pending request. This parameter is not applicable because services are provided in real-time or near real-time. | +| Circuit number | c | o | m | m(=) | This is different from Recommendation M.3208.1 because the M.3208.1 Provider Request Number is not a possible choice in this Recommendation. | +| Provider request number | c1 | c2 | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Request sequence number | – | c | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Bandwidth | c3 | o(=) | c3 | o(=) | See Recommendation M.3208.1. | +| Route | c3 | c | – | – | Once the CM LCS is established by using pre-provisioned link connections, changing the route is not valid. | + +**Table 6/M.3208.2 – Information flow for modify CM leased circuit service function (concluded)** + +| Information element | Rec. M.3208.1 | | This Recommendation | | Notes | +|------------------------------|------------------|------------------|---------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Service customer | Service provider | Service customer | Service provider | | +| Schedule | c3 | c | c3 | o(=) | c3 – The presence of this optional parameter is controlled by the value specified in Service Name and Service Class.

If the requested schedule is not available, the modify request will be rejected with a reason code. | +| Service request state | – | c | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Service termination date | o | o | o | o(=) | If the requested service termination date cannot be met, the modify request will be rejected with a reason. If the service termination date is changed to the present date or a date in the past, the service will be deleted. | +| Service availability date | c | c | – | – | This parameter is not required as services are provided in real-time or near real-time. | +| Service administrative state | o | o | o | o | See Recommendation M.3208.1. | +| Alias name | o | o(=) | o | o(=) | See Recommendation M.3208.1. | +| Error | | c | | c | c – This parameter is present if the request is rejected.
Valid error codes are:
– Invalid CPE type.
– Required bandwidth not available.
– Invalid schedule.
– Invalid circuit number.
– Contract violation.
– Resource unavailable.
– Invalid alias name.
– Service link connection(s) unavailable for the requested schedule. | + +##### **7.3.3.1.4 Cancel CM leased circuit service request function** + +This function is not applicable within the scope of this Recommendation as LCS are provided in real-time or near real-time. + +##### **7.3.3.1.5 Replace a failed CM leased circuit service function** + +This function is newly introduced in this Recommendation. + +###### **7.3.3.1.5.1 Summary** + +The SC may choose to restore a failed CM LCS. To restore a failed CM LCS, the administrative state of the failed CM LCS must be locked and the administrative state of a backup CM LCS must be changed to unlocked. This assumes that the SC has created a set of locked CM LCSs which can be used to restore the failed CM LCS. In the event that no such set exists, the SC must create a new CM LCS. The existence of a replacement CM LCS is not guaranteed, but depends on the SC's pre-provisioned service link connections and their schedules. + +The requirement for a function to identify the best locked CM LCS based on values of the Selection Priority attribute of the eligible CM LCSs, and to unlock that CM LCS is for further study. + +###### **7.3.3.1.5.2 Information flow** + +The information flow defined for the modify function in Recommendation 7.3.3.1.3 is applicable here. However, the only parameter that can be changed is the administrative state of the failed and backup CM LCS. See Table 6 for details. + +#### **7.3.3.2 CM leased circuit service status administration function set** + +This function set includes functions that allow the service provider to inform the service customer of service administrative functions and for the service customer to monitor administrative information related to the requested CM LCS. This function set contains status administration functions from Recommendation M.3400 and augments them with additional new functions. + +- 1) (Not applicable for CM.) Report creation of CM leased circuit service to service customer function. +- 2) Report deletion of CM leased circuit service to service customer function. +- 3) (This function is needed to report parameter changes, but there is no specialization from Recommendation M.3208.1.) Report configuration changes of CM leased circuit service parameters to service customer function. +- 4) (Not applicable for CM.) Report change of CM leased circuit service: service request parameters function. +- 5) (Not applicable for CM.) Control the service administrative state of the CM leased circuit service by the service customer function. +- 6) (This function is needed to retrieve parameter information, but there is no specialization from Recommendation M.3208.1.) Retrieve service parameter values function. +- 7) (Not applicable for CM.) Monitor progress of the service request function. +- 8) (Not applicable for CM.) Report the progress of the leased circuit service request function. +- 9) (Not applicable for CM.) Retrieve leased circuit service request parameters function. +- 10) (This is a new function not in Recommendation M.3208.1.) Identifying locked CM leased circuit service function. + +##### **7.3.3.2.1 Report creation of CM leased circuit service to service customer function** + +###### **7.3.3.2.1.1 Summary** + +There is a requirement for confirmation of the creation, not for a separate notification of the completion of a delayed request. The requirement for confirmation appears to be contained in the completion response requirement of Recommendation 7.3.3.1.1. The function described here is not needed. + +##### **7.3.3.2.2 Report deletion of CM leased circuit service to service customer function** + +###### **7.3.3.2.2.1 Summary** + +This function is used to report the deletion of a CM LCS to the service customer. This function is used in conjunction with the request to delete the service in Recommendation M.3208.1, and is not needed here for that purpose. However, this function is used to report the deletion of a CM LCS resulting from the expiration of a service termination date parameter. + +###### **7.3.3.2.2.2 Information flow** + +**Table 7/M.3208.2 – Information flow for report deletion of CM leased circuit service to service customer function** + +| Information element | Rec. M.3208.1 | This Recommendation | Notes | +|----------------------------|----------------------|----------------------------|--------------| +| Circuit number | m | m | | +| Service provider contact | m | m | | +| Service termination date | o | o | | + +##### **7.3.3.2.3 Report configuration changes of leased circuit service parameters to service customer** + +There is no specialization here of the analogous function in Recommendation M.3208.1. + +##### **7.3.3.2.4 Report change of leased circuit service: service request parameters** + +This function is not applicable within the scope of this Recommendation as CM LCSs are provided and managed in real-time or near real-time. + +##### **7.3.3.2.5 Control administrative state of the CM leased circuit service by the service customer function** + +There is no specialization here of the analogous function in Recommendation M.3208.1. + +###### **7.3.3.2.5.1 Summary** + +This function is used by the service customer to control the availability of the CM LCS or the ability of a CM LCS to be modified. + +##### **7.3.3.2.6 Retrieve service parameters by the service customer** + +###### **7.3.3.2.6.1 Summary** + +There is no specialization here of the analogous function in Recommendation M.3208.1. + +##### **7.3.3.2.7 Monitor progress of the service request** + +This function is not applicable within the scope of this Recommendation as LCSs are provided and managed in real-time or near real-time. + +##### **7.3.3.2.8 Report progress of the service request** + +This function is not applicable within the scope of this Recommendation as LCSs are provided and managed in real-time or near real-time. + +##### **7.3.3.2.9 Retrieve service request parameters by the service customer** + +This function is not applicable within the scope of this Recommendation as LCSs are provided and managed in real-time or near real-time. + +##### **7.3.3.2.10 Identify locked LCS function** + +This function is not inherited from Recommendation M.3208.1. + +###### **7.3.3.2.10.1 Summary** + +This function is used whenever an SC creates an inventory of locked CM leased circuit services. They serve as a collection of unused pre-provisioned CM LCSs which can be activated, by the SC with a minimum amount of effort and analysis. The inventoried pre-provisioned LCSs may also be used by the SC to restore service to a failed CM LCS subsection. + +The selection priority values will be returned for all CM LCSs that were created by specifying intermediate link connections. A locked CM LCS can be unlocked if there is no conflict between its scheduled on-duty times and the periods during which the service link connections comprising the CM LCS are scheduled to be used by existing CM LCSs. + +This function is the same as retrieval using the retrieve service parameter values function in 7.3.3.2.6. There are special requirements on the selection criteria here. The minimum criterion is that the service administrative state must be locked. Any of the attributes that can be retrieved using the retrieve service parameter values function can be retrieved here. + +#### **7.3.3.3 Link connection status administration function set** + +The link connection status administration function set as defined in Recommendation M.3208.1 can be used by the CM LCS customer to manage the link connections. + +There is no specialization of this function set from Recommendation M.3208.1. + +#### **7.3.3.4 Leased circuit service test function set** + +This function set will be added to Recommendation M.3400 in future work, and will contain a number of other functions related to testing LCS. Recommendation M.125 defines loopback mechanisms. + +##### **7.3.3.4.1 Initiate and terminate loopback of end of link connection function** + +CM allows the service customer to control the creation of LCSs. However, the SC may also wish to test the LCS before it is used. The SC needs the ability to loopback service link connections at either end to do pre-use testing and to do a limited amount of problem segmentation. Since loopback is an optional feature of many NEs, this capability will be available only if supported by the equipment. + +###### **7.3.3.4.1.1 Summary** + +The loopback function assumes that a service link connection is composed of two complementary unidirectional link connections. For a specified LCS and for a specified SLC within this LCS, a + +loopback request is a request to bind the unidirectional output port of the specified SLC to its corresponding unidirectional input port. Figure 5 illustrates these concepts. When such a binding has been accomplished, the LCS is said to be looped back at the specified SLC. + +The means for specifying the location of a loopback within a LCS are discussed in 7.3.3.4.1.1.2. + +![Figure 5/M.3208.2: Top: LCS without loopback; Bottom: LCS with loopback. The diagram shows two horizontal lines representing signal paths. Each path contains four connection points (CPs) labeled CP11, CP21, CP31, CP41 on the top line and CP12, CP22, CP32, CP42 on the bottom line. Each CP is represented by a small rectangle with two black bars inside. In the top diagram (without loopback), the paths are continuous. In the bottom diagram (with loopback), a dashed line connects the output of CP21 to the input of CP22, creating a loopback at CP21. A legend at the bottom left shows a CP symbol and a dashed line symbol labeled 'Subnetwork connection'. The text 'T0410000-98' is in the bottom right corner.](318886a86a1dcc59e1fc83db6f157c60_img.jpg) + +Figure 5/M.3208.2: Top: LCS without loopback; Bottom: LCS with loopback. The diagram shows two horizontal lines representing signal paths. Each path contains four connection points (CPs) labeled CP11, CP21, CP31, CP41 on the top line and CP12, CP22, CP32, CP42 on the bottom line. Each CP is represented by a small rectangle with two black bars inside. In the top diagram (without loopback), the paths are continuous. In the bottom diagram (with loopback), a dashed line connects the output of CP21 to the input of CP22, creating a loopback at CP21. A legend at the bottom left shows a CP symbol and a dashed line symbol labeled 'Subnetwork connection'. The text 'T0410000-98' is in the bottom right corner. + +**Figure 5/M.3208.2 – Top: LCS without loopback; Bottom: LCS with loopback** + +###### 7.3.3.4.1.1.1 Uses and support for the loopback function + +Some of the uses a SC may make of the loopback function are to: + +- 1) test LCSs prior to their use; +- 2) measure the performance of segments of the LCS; +- 3) support fault isolation within the LCS; +- 4) assess the suitability of an LCS to support new SC needs. + +Support for the loopback function is a SP option. When supported, a SP is not required to support the loopback function for all SLCs and for all LCSs. + +The loopback function is directed at a SLC contained within a specified LCS. The use of the loopback function requires that the LCS be in an unlocked state. Except for the receipt of the loopback request, the SP has no information from which to determine if a SC is using a LCS to carry SC traffic or if the SC is using it to carry SC selected test and evaluation signals3. The loopback request does not require the SP to perform any actions for the SC beyond establishing the loopback. + +3 The test and evaluation signals used by the SC are limited to the payload segment of the transmitted signal. + +###### 7.3.3.4.1.1.2 Loopback specification + +All LCSs within the scope of this Recommendation contain two end-link connections and zero or more mid-link connections. Consequently, any LCSs within the scope of this Recommendation can be represented as a sequence of contiguous, compatible SLCs which begin and finish with end-link connections. For example, in Figure 6, LCS1 consists of SLC1, SLC5, SLC2, SLC3, and SLC4 where SLC1 and SLC5 are end-link connections and SLC2, SLC3, and SLC4 are mid-link connections. In this case, SLCn and SLCm are contiguous, compatible link connection for $n - m = \pm 1$ . + +![Diagram of Figure 6/M.3208.2 showing LCS1 defined in terms of SLCs. The diagram shows a sequence of five SLCs (SLC1, SLC2, SLC3, SLC4, SLC5) connected in a line. SLC1 and SLC5 are end-links, while SLC2, SLC3, and SLC4 are mid-links. A bracket labeled LCS1 spans the entire sequence from SLC1 to SLC5. The diagram is labeled T0410010-98.](cfb98c691c1af5befe32ff9442eea511_img.jpg) + +The diagram illustrates a sequence of five SLCs (SLC1, SLC2, SLC3, SLC4, SLC5) connected in a line. SLC1 and SLC5 are end-links, while SLC2, SLC3, and SLC4 are mid-links. A bracket labeled LCS1 spans the entire sequence from SLC1 to SLC5. The diagram is labeled T0410010-98. + +Diagram of Figure 6/M.3208.2 showing LCS1 defined in terms of SLCs. The diagram shows a sequence of five SLCs (SLC1, SLC2, SLC3, SLC4, SLC5) connected in a line. SLC1 and SLC5 are end-links, while SLC2, SLC3, and SLC4 are mid-links. A bracket labeled LCS1 spans the entire sequence from SLC1 to SLC5. The diagram is labeled T0410010-98. + +Figure 6/M.3208.2 – LCS defined in terms of SLCs + +The terms defined in the following paragraphs are used to specify loopbacks. + +*Ordered SLC list* – An ordered SLC list is a list of the contiguous SLC which comprise the LCS. The first and last items in the list are end-links. + +*Orienting SLC* – An orienting SLC is an end-link connection which defines the first SLC in an ordered LCS list. + +Because two ordered SLC lists may be constructed for any LCS, an orienting SLC is used to uniquely specify an ordered SLC list. For example, in Figure 6, when SLC1 is the orienting SLC, the resulting ordered LCS list is: + +SLC1, SLC2, SLC3, SLC4, SLC5. + +When SLC5 specifies the orienting SLC, the resulting ordered SLC list is: + +SLC5, SLC4, SLC3, SLC2, SLC1. + +###### 7.3.3.4.1.1.3 Location of the loopback + +For a given LCS, the location of the loopback is specified by means of an orienting SLC and an SLC where the loopback is to be applied. By definition, the location of the loopback is found from the ordered SLC list by dividing the SLC list into two parts, where one part contains the orienting SLC, and the SLC to be looped back. This part is called the primary sublist. The other part of the list, called the secondary sublist, contains the remaining SLCs. The loopback is applied at the tail end of the primary sublist. + +One additional aspect of the loopback function requires definition, namely the loopback status of the segment of the LCS represented by the secondary sublist. For this segment of the LCS, a loopback may be established at the head end of the secondary sublist. The head end is that end of the LCS contained in the secondary sublist which was contiguous to the looped back SLC in the specified ordered SLC list. + +Two options are possible. In option 1, the SP determines whether or not a loopback at the head end of the secondary sublist is established. The choice may be made each time a loopback is requested. That is, for a given loopback request, the SP's decision to provide a loopback at the head end of the secondary sublist is independent of the choice made by the SP for the previous request. + +In option 2 the SP performs, for all loopback requests on a given LCS, a pre-defined action at the head end of the secondary sublist. That is, the SP will always create a loopback in the secondary sublist or the SP will never establish these loopbacks. + +###### 7.3.3.4.1.1.4 Loopback time out + +There are two proposed options for specifying the time period during which a loopback is to remain in place. In option 1, the loopback remains in place until the SC requests that it be removed. In option 2, the loopback request will contain a time period during which the loopback is to be in place. At the end of this period, the loopback will automatically be removed by the SP. + +###### 7.3.3.4.1.2 Information flow + +**Table 8/M.3208.2 – Information flow for delete loopback of end of link connection function** + +| Information element | Service customer | Service provider | Notes | +|---------------------------|------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Circuit number | m | m(=) | | +| Loopback primary sublist | m | m(=) | An ordered list of link connections leading from the orienting SLC to the SLC to be looped back. | +| Loopback termination time | o | c(=) | If a termination time is not provided, the SP may choose to provide one. Otherwise the absence of a termination time means that the loopback will remain until it is deleted by the SC. | +| SP contact | – | m | This may be a different contact from the SP contact. | +| Error messages | – | c | c – This parameter is present if the request is rejected. Valid error codes are:
– LCS unavailable;
– LCS is off-duty;
– Loopback not supported by equipment. | + +###### 7.3.3.4.1.3 Information flow + +**Table 9/M.3208.2 – Information flow for delete loopback of end of link connection function** + +| Information element | Service customer | Service provider | Notes | +|--------------------------|------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Circuit number | m | m(=) | | +| Loopback primary sublist | o | c(=) | An ordered list of link connections leading from the orienting SLC to the SLC to be looped back.

The SC must distinguish between the two possible loopbacks that might exist from both ends of the CM LCS. A delete request with no loopback primary sublist will cause any loopbacks on the CM LCS to be restored to normal operation. | +| SP contact | – | m | This may be a different contact from the SP contact. | +| Error messages | – | c | c – This parameter is present if the request is rejected. Valid error codes are:
– No loopback available for deletion. | + +# 8 Management scenarios + +Management scenarios are described for examination of the relationships among roles, resources and functions of which management context are composed. For this purpose, scenarios show interactions between the service customer role and the service provider role, using the telecommunications services or resources and functions. Based on the purpose of examining the relationships among management context, management scenarios only show representative examples of interactions between service customer role and service provider role, but do not cover whole of cases. + +## 8.1 Scenarios for connection management functions + +### 8.1.1 Scenarios for CM leased circuit service creation + +The SC shall identify the service to be provisioned, the service name and the customer contact within the organization, which are mandatory information. + +![](409498e57b1f988b2b604d12cd997002_img.jpg) + +SC —————→ SP + +Request to create a CM leased circuit service +{with service name, customer contact} + +If the service is established as requested, the SP may inform the SC of the SP contact, circuit number that is unique for the duration of the leased circuit service and, if any, other customer requested parameters for the confirmation. + +![](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +SC ←———— SP + +Respond with success of the creation request of a CM leased circuit service +{with SP contact, circuit number and other customer requested parameters} + +### 8.1.2 Scenarios for CM leased circuit service deletion + +The SC shall uniquely identify an existing dedicated leased circuit service, which is desired to be released. + +![Sequence diagram for CM leased circuit service deletion request](145d00f59802048185303f15937ea65c_img.jpg) + +A sequence diagram showing a Service Controller (SC) sending a request to a Service Provider (SP). The SC is on the left and the SP is on the right. A horizontal arrow points from the SC to the SP. Below the arrow, the text reads: "Request to delete a CM leased circuit service {with circuit number}" + +Sequence diagram for CM leased circuit service deletion request + +When the deletion request is completed and the leased circuit service instance was terminated, the SP notifies the SC of the deletion. + +![Sequence diagram for CM leased circuit service deletion response](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +A sequence diagram showing a Service Provider (SP) sending a response to a Service Controller (SC). The SC is on the left and the SP is on the right. A horizontal arrow points from the SP to the SC. Below the arrow, the text reads: "Respond with success of the deletion request of a CM leased circuit service {with circuit number}" + +Sequence diagram for CM leased circuit service deletion response + +### 8.1.3 Scenarios for CM leased circuit service modification + +The SC may request to modify the service parameters such as customer contact, alias name, originating location CPE type, and terminating location CPE type, bandwidth, schedule, service termination date and service administrative state, depending on service name, service class and the contract. These can be also technology specific. In the case the SC would modify the parameters of the activated leased circuit service, the SC uses circuit number to identify the leased circuit service. + +![Sequence diagram for CM leased circuit service modification request](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +A sequence diagram showing a Service Controller (SC) sending a request to a Service Provider (SP). The SC is on the left and the SP is on the right. A horizontal arrow points from the SC to the SP. Below the arrow, the text reads: "Request to modify a CM leased circuit service {with circuit number and the parameters to be modified and their values}" + +Sequence diagram for CM leased circuit service modification request + +If the modification request is done as requested, the SP informs the SC of the circuit number and customer requested parameters for confirmation. + +![Sequence diagram for CM leased circuit service modification response](9ff1b32449ea068bba9647d71904bd59_img.jpg) + +A sequence diagram showing a Service Provider (SP) sending a response to a Service Controller (SC). The SC is on the left and the SP is on the right. A horizontal arrow points from the SP to the SC. Below the arrow, the text reads: "Respond with success of the modification request of a CM leased circuit service {with circuit number and customer requested parameters}" + +Sequence diagram for CM leased circuit service modification response + +## 8.2 Scenarios for CM leased circuit service status administration + +Scenarios for CM leased circuit service status administration are described by using the following TMN management roles, telecommunication services and TMN management functions. + +Those TMN management roles are: + +- service customer role; and +- service provider role. + +That telecommunication service is: + +- leased circuit service. + +Those TMN management functions are identified in 7.3.3.2. + +The functions identified in 7.3.3.1 may also be referred. + +The following examples show administration flows for CM leased circuit service. + +### 8.2.1 Scenarios for report deletion of CM leased circuit service to service customer + +A management scenario using the report deletion of leased circuit service to service customer is described in 3.4.1.2 and others. Refer to those subclauses. + +![Sequence diagram for report deletion of CM leased circuit service](54e4bda94c608845a162d52a75e67ce4_img.jpg) + +A sequence diagram showing a Service Provider (SP) sending a report to a Service Controller (SC). The SC is on the left and the SP is on the right. A horizontal arrow points from the SP to the SC. Below the arrow, the text reads: "Report deletion of a dedicated leased circuit service {with circuit number and SP contact}" + +Sequence diagram for report deletion of CM leased circuit service + +### 8.2.2 Scenario for loopback creation + +The SC may request the SP to loopback a LCS. The SC shall identify a LCS, the location of the loopback and optionally the duration of the loopback. + +![Sequence diagram for loopback creation request](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) + +SC → SP +Request to create a loopback a LCS +{with location of the loopback} + +Sequence diagram for loopback creation request + +If the loopback is established as requested the SP informs the SC of the circuit number and the loopback conformation. + +![Sequence diagram for loopback creation response](04cfca33e3fc26513abe649d7474f733_img.jpg) + +SC ← SP +Respond with success of a create loopback request +{with circuit number and SP contact} + +Sequence diagram for loopback creation response + +### 8.2.3 Scenario for loopback deletion + +The SC may request the SP to delete a loopback on a LCS. The SC shall identify a LCS and the location of the loopback. + +![Sequence diagram for loopback deletion request](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +SC → SP +Request to delete a loopback on a LCS +{with location of the loopback} + +Sequence diagram for loopback deletion request + +If the loopback is deleted as requested, the SP informs the SC of the circuit number and the delete loopback conformation. + +![Sequence diagram for loopback deletion response](a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg) + +SC ← SP +Respond with success of a delete loopback request +{with circuit number} + +Sequence diagram for loopback deletion response + +### 8.2.4 Scenario for loopback modification + +The SC may request the SP to modify the time period where the loopback is in place. The SC shall identify a loopback and the new duration of the loopback. + +![Sequence diagram for loopback modification request](1b2ad37940c441d410002c05ff71c7c5_img.jpg) + +SC → SP +Request to modify a loopback on an LCS +{with location of the loopback and new duration} + +Sequence diagram for loopback modification request + +If the new loopback duration is established as requested, the SP informs the SC of the circuit number and the loopback conformation. + +![Sequence diagram for loopback modification response](6c6d2bce2630f62fb3a5345c9ec84f68_img.jpg) + +SC ← SP +Respond with success of a modify loopback request +{with circuit number and SP contact} + +Sequence diagram for loopback modification response + +### 8.2.5 Scenario for locked LCSs identifying + +The SC may request the SP to provide an inventory of locked CM LCSs. The SC shall identify the service name and the administrative state. + +![Sequence diagram for locked LCSs identifying request](82755aa51734b65461f50bf3361c8ab2_img.jpg) + +SC → SP +Request to provide an inventory of locked +{with service name, administrative state and other optional things} + +Sequence diagram for locked LCSs identifying request + +When the processing is completed, the SP shall inform the SC about administrative state, all dedicated SLCs, schedule, selection priority, service customer contact, service class, service name, start time and stop time. + +![Sequence diagram showing a response from SP to SC with success of provision of an inventory of locked LCSs.](cc72b4769f15fe33763025416c1e274d_img.jpg) + +SC ←————— SP + +Respond with success of provision of an inventory of locked LCSs +{with administrative state, all dedicated SLCs, schedule, selection priority, service customer contact, service class, +service name, start time and stop time} + +Sequence diagram showing a response from SP to SC with success of provision of an inventory of locked LCSs. + +### 8.2.6 Scenario for failed LCS restoration + +The SC may request to restore a failed CM LCS. First, the SC has to request the SP to lock the administrative state of the failed LCS. + +![Sequence diagram showing a request from SC to SP to lock the failed CM LCS.](b58cedaf15ad4f0edee5621820865ccc_img.jpg) + +SC —————→ SP + +Request to lock the failed CM LCS +{with circuit number and the administrative state} + +Sequence diagram showing a request from SC to SP to lock the failed CM LCS. + +In the response the SP informs the SC of the circuit number and administrative state. + +![Sequence diagram showing a response from SP to SC with success of the lock failed CM LCS.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +SC ←————— SP + +Respond with success of the lock failed CM LCS +{with circuit number and the administrative state} + +Sequence diagram showing a response from SP to SC with success of the lock failed CM LCS. + +If a backup CM LCS is available, the SC requests the SP to unlock CM LCS. + +![Sequence diagram showing a request from SC to SP to unlock the backup CM LCS.](f1091147d93cee4dfa88498610e395a7_img.jpg) + +SC —————→ SP + +Request to unlock the backup CM LCS +{with circuit number and the administrative state} + +Sequence diagram showing a request from SC to SP to unlock the backup CM LCS. + +In the response the SP informs the SC of the circuit number and administrative state of the backup CM LCS. + +![Sequence diagram showing a response from SP to SC with success of the unlock backup CM LCS.](b560268ea8f6526970f23f0da225b099_img.jpg) + +SC ←————— SP + +Respond with success of the unlock backup CM LCS +{with circuit number and the administrative state} + +Sequence diagram showing a response from SP to SC with success of the unlock backup CM LCS. + +If no backup CM LCS the SC must request the SP to create a new CM LCS. (See 8.1.1.) + +# 9 Architecture + +## 9.1 Functional architecture + +The architecture is described in Recommendation M.3010. Applicable reference points are x, and q3, between SML and SML, and q3 between SML and NML. + +## 9.2 Physical architecture + +The architecture is described in Recommendation M.3010. Applicable interfaces are X and Q3. + +# APPENDIX I + +## A SONET private line service example + +A SONET Bidirectional Line Switched Ring (BLSR) can be modelled as a series of link connections across the ring. A SONET Unidirectional Path Switched Ring (UPSR) can be modelled as a set of link connections between two ADMs on the ring. A typical SONET-based private line service is shown in Figure I.1. + +![Figure I.1/M.3208.2 – CM model for SONET-based services. The diagram shows a network topology with a central WB DCS connected to two rings: a BLSR and a UPSR. The BLSR ring contains ADMs B1 through B6, with two IC POPs (I1, I2) connected to B1 and B2. The UPSR ring contains ADMs U1 through U6, with a 'Customer site' connected to U5. Mid-link connections DM1 and DM2 connect the BLSR and UPSR rings via ADMs B4, B5, U1, and U2. Labels M1 and M2 are shown above the WB DCS.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Figure I.1/M.3208.2 – CM model for SONET-based services. The diagram shows a network topology with a central WB DCS connected to two rings: a BLSR and a UPSR. The BLSR ring contains ADMs B1 through B6, with two IC POPs (I1, I2) connected to B1 and B2. The UPSR ring contains ADMs U1 through U6, with a 'Customer site' connected to U5. Mid-link connections DM1 and DM2 connect the BLSR and UPSR rings via ADMs B4, B5, U1, and U2. Labels M1 and M2 are shown above the WB DCS. + +## End-link connections + +I1 +I2 +I1/I2 + +### Mid-link connections + +B1-B2      M1 +B2-B3      M2 +B3-B4    DM1/DM2 +B4-B5 +B5-B6 +B6-B1 +. +. +. + +## End-link connections + +U1-U2-U3-U4-U5-U6-U1 +. +. +. + +**Figure I.1/M.3208.2 – CM model for SONET-based services** + +Figure I.1 illustrates the following service link connections. The first is a service level end-link connection, e.g. I1, which is dedicated to the service customer. Next, there are the service level mid-link connections, e.g. B1-B6, B6-B5, which are supported by a shared inter-office SONET BLSR ring. Following these are additional service level mid-link connections, e.g. M1 and M2, or DM1/DM2. Lastly, there is a service level end-link connection, e.g. U1-U2-U3-U4-U5-U6, supported by a shared customer access SONET UPSR ring. + +NOTE – Since one connection consumes its allocated bandwidth around the entire UPSR ring, UPSR service level link connections must be modelled as virtual links with multiple termination points. BLSR service link connections can be modelled as independent service link connections, e.g. B1-B2, B2-B3, B3-B4, except for B4-B5 which is consumed to support dual ring interconnection. + +# APPENDIX II + +## **Ordering processes for service link connections** + +The ordering function being defined for the Electronic Access Ordering (EAO) process is a function that provides SCs with a mechanized service ordering and inquiry interface which will, when complete, permit SCs to directly request service link connections. + +Currently, SCs order service capacity between their POPs and multiplexer locations in the SP network. Today this service capacity is commonly provided on DS1 and DS3 facilities. In the future the service capacity is expected to include high-capacity SONET facilities. SCs also order end-to-end, i.e. POP to Ultimate End User, services that use a SC-specified channel supported by the provisioned service capacity. However, the SC has no control over the SP's facilities between the multiplexer location and the end user location. + +The EAO ordering function is a new EB functional area designed to mechanize the service capacity ordering process. When used with connection management, SCs can use the EAO ordering function to provision the service link connection used by connection management. + +In the case the provisioned service capacity represents a channelized DS3 service and the channels support DS1 services, a SC would use CM to create LCSs using the service link connections which represent the DS1 services as well as using other service link connections. If the SC's DS1 service was partitioned into DS0 services by the SC, the DS0 services would be considered a subrate service. The use of subrate services as CM service link connections is for further study. + +The Exchange Carrier Circuit ID (ECCKT ID) is commonly used today for a service name or identifier. When used, the ECCKT ID is assigned by the service provider when the service order/service activation process is completed. + +The ECCKT ID is a very important parameter in electronic bonding. In addition to naming service objects created via the EAO ordering function, it may be used to report troubles, to identify alarm reporting, protection switching event, threshold crossing, and alert notifications, and to retrieve historical performance monitoring data. The ECCKT ID may be used for the serviceID attribute defined for CM. + + + +# ITU-T RECOMMENDATIONS SERIES + +- Series A Organization of the work of the ITU-T +- Series B Means of expression: definitions, symbols, classification +- Series C General telecommunication statistics +- Series D General tariff principles +- Series E Overall network operation, telephone service, service operation and human factors +- Series F Non-telephone telecommunication services +- Series G Transmission systems and media, digital systems and networks +- Series H Audiovisual and multimedia systems +- Series I Integrated services digital network +- Series J Transmission of television, sound programme and other multimedia signals +- Series K Protection against interference +- Series L Construction, installation and protection of cables and other elements of outside plant +- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits** +- Series N Maintenance: international sound programme and television transmission circuits +- Series O Specifications of measuring equipment +- Series P Telephone transmission quality, telephone installations, local line networks +- Series Q Switching and signalling +- Series R Telegraph transmission +- Series S Telegraph services terminal equipment +- Series T Terminals for telematic services +- Series U Telegraph switching +- Series V Data communication over the telephone network +- Series X Data networks and open system communications +- Series Y Global information infrastructure and Internet protocol aspects +- Series Z Languages and general software aspects for telecommunication systems \ No newline at end of file diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffcf6a73c261ecb5365cfbd455da2592aa4766dd --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e6e2602922838c998aad1e95ae9220ea48755e7826d332ba3d69d7a7c0ac4e1 +size 71596 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4688212ab9725e92945db490cafe0c88d9ea55a --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a4f458fc319c90b628c2f086094321e1b7af670f7095b037aa14ce41a33cce7 +size 37751 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c +size 8232 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aed196b42ae3e4301b9e694e3e2acdfbcf4f3e25 --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/366a77fdefb0097b3289b4a011911390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bdb824e33b789bafa282c5c078baa0fbe49f04ea6d696c5dba83b05702318a5 +size 37204 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e205cc9b0e1cc7984318c5ce35b75f101e2b4e75 --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc2af98a55b56470c415769a5012f72bfce23c964af4a07544e6a7b394568778 +size 105279 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da1337a931877ecad26ed3efef5c9096955a484e --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ca6d9fdc1c5e4ae57c69d0d9696bea9c83a0b4823eb3e3e691782effb3a638a +size 21727 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..301e97f2b9143fd79b8f8cdde744ea1e9473025e --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eabf437f180bfe82dae0d669d03e9183bf675f7464f1bfc24426e244da855b4c +size 52591 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..571afcafabd04f013913d10b3a6c30e285a34b22 --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d597b3a0ffe803debc6fc66db3dfb83738168f367e5a5c71e793fae7973cdb7 +size 24666 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2b10c5f6a0abb266a843e9aa1acee211a18a12e --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61b20764bef1b7ad6bee220f0424cdc7fa0c146208b31b265df9e559d49b1a8d +size 37102 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dcb306052f7d2dd216f4eae9bce7415a5d70e18 --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16c8c85ed4ee9b1209b566450cc76d088a9a5de7a710bd015744923253e7145b +size 36326 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eba37c9c3567442d225febdd78bc6b4e4b7aa954 --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc5b5839a7e8644ad2dda4abf2e008a80292595a342c2d4f52ec285c83688c69 +size 67706 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7657c6d628f711597888a5335b75a95f05d9edac --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a68aee0beda1755b882c6fe7dc86d5e69de55afd9bb86f0f4c87b03f5636a3d0 +size 37356 diff --git a/marked/M/T-REC-M.3210.1-200101-I_PDF-E/raw.md b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..33844d178784fdd5db1db334ed02586f8ebfae44 --- /dev/null +++ b/marked/M/T-REC-M.3210.1-200101-I_PDF-E/raw.md @@ -0,0 +1,837 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3210.1** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(01/2001) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**TMN management services for IMT-2000 +security management** + +ITU-T Recommendation M.3210.1 + +(Formerly CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **TMN management services for IMT-2000 security management** + +## **Summary** + +This Recommendation is one of the series of M.3200 Recommendations on TMN Management Services that provide description of management services, goals and context for management aspects of IMT-2000 networks. This Recommendation provides a profile for fraud management in an IMT-2000 mobile network. This Recommendation builds on the function sets identified in ITU-T M.3400 by defining new function sets, functions and parameters and adding additional semantics and restrictions. + +## **Source** + +ITU-T Recommendation M.3210.1 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. + +## **Keywords** + +Telecommunications Management Network (TMN), TMN Management Service, International Mobile Telecommunications: IMT-2000, Security Management, Fraud Detection and Containment, Third Generation Wireless – 3G Systems. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2001 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|-------------------------------------------------------------------|----| +| 1 | Introduction..... | 1 | +| 1.1 | Purpose and scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.5 | Role-related definitions..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 4.1 | Conventions ..... | 2 | +| 5 | Security Management Service ..... | 3 | +| 5.1 | Security issues..... | 3 | +| 5.2 | Management Service description..... | 3 | +| 6 | Management high-level requirements ..... | 4 | +| 6.1 | Management Service overview..... | 6 | +| 6.2 | Telecommunication resources ..... | 6 | +| 6.2.1 | Fraud Information Gathering System (FIGS)..... | 6 | +| 6.2.2 | Visited Network..... | 7 | +| 6.2.3 | Home Network Fraud Detection System (HN-FDS)..... | 7 | +| 6.3 | Fraud Information Gathering use cases ..... | 7 | +| 6.3.1 | Fraud Alert use case ..... | 8 | +| 6.3.2 | Activate Information Gathering use case ..... | 8 | +| 6.3.3 | Report FIGS use case ..... | 9 | +| 6.3.4 | Deactivate Information Gathering use case..... | 9 | +| 6.3.5 | Modify FIGS Report use case ..... | 10 | +| 6.3.6 | Advise Suspend FIGS Monitoring use case ..... | 10 | +| 6.3.7 | Advise Resume FIGS Monitoring use case..... | 11 | +| 7 | Management Functions analysis..... | 11 | +| 7.1 | Fraud Information Gathering Function set ..... | 11 | +| 7.2 | Object Classes and State Chart ..... | 11 | +| 7.3 | Fraud Information Gathering functions and sequence diagrams ..... | 13 | +| 7.3.1 | Fraud Alert function ..... | 13 | +| 7.3.2 | Activate Information Gathering function ..... | 13 | +| 7.3.3 | Report FIGS function ..... | 14 | +| 7.3.4 | Deactivate Information Gathering function..... | 15 | +| 7.3.5 | Modify FIGS Report function ..... | 16 | +| 7.3.6 | Advise Suspend FIGS Monitoring function ..... | 18 | +| 7.3.7 | Advise Resume FIGS Monitoring function..... | 19 | + +| | | +|----------------------------------------------------------------|----| +| Annex A – Fraud Management criteria..... | 20 | +| Annex B – Information transferred by the Visited Network ..... | 21 | + +## **TMN management services for IMT-2000 security management** + +# **1 Introduction** + +This Recommendation provides requirements and analysis of the security management (administration) of IMT-2000. The emphasis is on the X interface between two service providers and the management services needed between the two service providers to detect and prevent fraud. The methodology used in this Recommendation is based on ITU-T M.3020. + +## **1.1 Purpose and scope** + +This Recommendation describes a subset of security management services, identified in ITU-T M.3200 as a TMN managed area, for IMT-2000 management. It describes the requirements and analysis of operating the Fraud Information Gathering System (FIGS) between service providers. FIGS provides the means for the wireless service provider to monitor a defined set of subscriber activities. The aim is to enable service providers/network operators to use FIGS to limit their financial exposure to large unpaid bills produced on subscriber accounts whilst the subscriber is roaming outside their home areas. + +Verification of the authenticity of the Home Network-FDS and the Visited Service Provider is beyond the scope of this management service. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions, which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Q.1701 (1999), *Framework of IMT-2000 Networks*. +- [2] ITU-T Q.1711 (1999), *Network functional model for IMT-2000*. +- [3] ITU-T Q.1721 (2000), *Information flows for IMT-2000 capability set 1*. +- [4] ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [5] ITU-T M.3020 (2000), *TMN interface specification methodology*. +- [6] ITU-T M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. +- [7] ITU-T M.3400 (2000), *TMN management functions*. + +# **3 Definitions** + +This Recommendation defines the following terms: + +**3.1 visited network:** The foreign or Visited Network which provides subscriber with roaming service. + +**3.2 home network:** The Home Network to which the wireless subscriber contracts service. + +**3.3 home network-FDS:** The Fraud Detection System operated by the Home Network. + +**3.4 fraud report:** A Fraud Report is the set of potential violations that the subscriber has performed that may indicate potential fraud. This typically captures threshold violations from the subscribers' normal patterns or criteria (like calling countries, high usage limits). + +## **3.5 Role-related definitions** + +This Recommendation makes use of the following roles defined in ITU-T M.3208.1: + +- service customer; +- network operator. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|----------|-----------------------------------------------------------| +| FDS | Fraud Detection System | +| FIGS | Fraud Information Gathering System | +| GDMI | Guidelines for the Definition of TMN Management Interface | +| IMT-2000 | International Mobile Telecommunications 2000 | +| ITU | International Telecommunication Union | +| MS | Management Services | +| N/A | Not Applicable | +| NML | Network Management Layer | +| SML | Service Management Layer | +| TMN | Telecommunications Management Network | + +## **4.1 Conventions** + +| Symbol | Explanation | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M | Mandatory | +| m(=) | The recipient must provide the same value in the response as provided in the request by the requestor. | +| O | Optional: Optionality is subject to definition according to the agreement between the two service providers, i.e. a parameter listed as optional may be made mandatory. | +| o(=) | Return of the value by the responder is optional; however, if the responder elects to return the value, it must be the same value supplied by the requestor in the request. Responder is not allowed to alter this field. | +| C | Conditional parameter: Definition of the Condition will be specified in the Notes column. A numeric suffix is used to enable reuse of the conditional statements. | +| c(=) | If the value is provided in the request by the requestor, the responder must provide the same value in the response. | +| Blank | A blank implies that the parameter is not applicable. | + +# 5 Security Management Service + +## 5.1 Security issues + +Modern telecommunication networks, particularly mobile networks, provide the potential for fraudsters to make use of telecommunication services (voice, data, fax, etc.) without the intent to pay. A number of different scenarios are exploited and it is up to the network operator or service provider to detect misuse where it occurs and to stop it at the earliest possible opportunity. + +The scale of frauds (per day on a single account) can be substantial, especially when international or premium rate numbers are called. The most common types of fraud that affect 3G networks are related to the ability to sell calls at below market price using stolen air-time/equipment where the user of the equipment does not intend to pay the network operator or the service provider. Fraudulent subscribers often avoid payment by obtaining a handset and a subscription to a network by fraudulently giving details and justifications to the network operators/service provider. If there are not good controls within the network, the subscriber can make a large volume of calls to expensive destinations and accumulate a large bill. + +## 5.2 Management Service description + +With wireless subscribers roaming from one network operator to another (and with multiple service providers), Security Management Service becomes of paramount importance. This Recommendation specifies the Security Management related information exchanged over the x reference point between two TMN Operating System (OS)s (the Visited Network and the Home Network). + +TMN relationships for IMT-2000 Security Management Service: Fraud Information Gathering are depicted in Figure 1. It shows the wireless subscriber roaming to a network of a visited service provider. + +![Figure 1/M.3210.1 – IMT-2000 Security Management Service: Fraud Information Gathering collaboration diagrams. The figure contains two diagrams, (a) and (b), showing interactions between a Fraud Detection System (FDS), Home Network, and Visited Networks across an 'x' reference point. Diagram (a) shows FDS invocation and FIGS monitoring requests. Diagram (b) shows Fraud Suspicion Information exchange and FIGS monitoring requests. Mobile phones are shown connected to the Visited Networks.](0b87abe67b21a93777287649c33e755d_img.jpg) + +**Diagram a)** + +- 0 FDS invocation from outside +- 1 Request for FIGS (Fraud Information Gathering System) monitoring +- 2 Request for FIGS monitoring +- 3 FIGS Data +- 4 FIGS Data + +**Diagram b)** + +- 1 Fraud Suspicion Information +- 2 Fraud Suspicion Information +- 3 Fraud Suspicion Information +- 4 Request FIGS monitoring +- 5 Request FIGS monitoring +- 6 FIGS Data +- 7 FIGS Data + +T0414780-00 + +Figure 1/M.3210.1 – IMT-2000 Security Management Service: Fraud Information Gathering collaboration diagrams. The figure contains two diagrams, (a) and (b), showing interactions between a Fraud Detection System (FDS), Home Network, and Visited Networks across an 'x' reference point. Diagram (a) shows FDS invocation and FIGS monitoring requests. Diagram (b) shows Fraud Suspicion Information exchange and FIGS monitoring requests. Mobile phones are shown connected to the Visited Networks. + +**Figure 1/M.3210.1 – IMT-2000 Security Management Service: Fraud Information Gathering collaboration diagrams** + +In Figure 1 a), The Home Network Fraud Detection System (HN-FDS) requests the Visited Network to supply certain information about a subscriber from the time the subscriber registers in that Visited Network to the time the last of the monitored activities is finished in that Visited Network, which can be after the subscriber's deregistration from the Visited Network. The information received by the Home Network shall be passed to the Home Network-FDS. Analysis of this information may lead to further instructions transmitted to the Visited Network to act in an appropriate way. + +Figure 1 b) actions are comparable to those of Figure 1 a) except that invocation of the activities is initiated by the visited service provider. + +# 6 Management high-level requirements + +The Home Network-FDS or the Visited Network can take preventive actions to control and prevent fraudulent activities, according to the security policies. The security management services described in this Recommendation are applicable across different service providers operating different or similar wireless networks. This management service provides the Visited Network and the Home Network-FDS with the capability to exchange and to control the exchange of information related to potential fraudulent activities in the Visited Network. + +The Fraud Information Gathering System capabilities are categorized in Table 1: + +**Table 1/M.3210.1 – Minimum capabilities required for Fraud Information Gathering System** + +| Scope | Reference | Requirement | +|---------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System-wide capabilities | 1 | FIGS Monitoring should be activated by:
  1. 1 The Visited Network obtains requests from the Home Network-FDS for monitoring suspicious subscriber activities.
  2. 2 The Home Network-FDS receives unsolicited subscriber alerts from the Visited Network, especially if the roaming subscriber continues to obtain service from the Visited Network for extended periods of time.
| +| | 2 | FIGS should not modify the Visited Network service. | +| | 3 | FIGS should not alter any standard 3G Wireless functionality seen by the customer or affect the service quality. | +| | 4 | FIGS Monitoring feature applies to all subscribed Bearer Services (e.g. Circuit, IP, etc.), TeleServices and Supplementary Services of the subscriber. It is not possible to apply FIGS independently to individual services. | +| | 5 | The information should be transferred from the Visited to the Home Network-FDS over existing communication links (e.g. TMN X interface, SS7 signalling links). | +| | 6 | A mechanism is required whereby a Visited Network can charge a Home Network-FDS for the bulk data transfer made to that Home Network-FDS. | + +**Table 1/M.3210.1 – Minimum capabilities required for +Fraud Information Gathering System (concluded)** + +| Scope | Reference | Requirement | +|-------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Home Network capabilities | 7 | Fraud information gathering is controlled by the Home Network-FDS and can be activated and deactivated by the Home Network-FDS only. | +| | 8 | The Home Network shall indicate the level of fraud monitoring required:
Level 1 accelerated accounting procedure, associated with a mechanism such as real time/near real time Billing.
Level 2 partial call information is gathered, but only at the beginning and the end of the call.
Level 3 full call information on subscriber activities, i.e. call start and end times, and partial call records. Notification of the invocation of Explicit Call Transfer, Call Deflection, Call Forwarding, Call Hold and Multi Party Service is also given. | +| | 9 | The Home Network-FDS shall be able to specify whether it would like call information on Mobile-Originated sessions, on Mobile-Terminated sessions, or on both. | +| | 10 | The Home Network should not permit the marking of new subscribers if the support of FIGS is causing overload within the Visited Network. The Visited Network should therefore handle up to a realistic limit any requests for marking of subscribers and should be able to support the associated data transfer. The setting of this limit is outside the scope of this Recommendation. | +| | 11 | The Home Network should mark a subscriber as being under FIGS monitoring. | +| | 12 | The Home Network should receive FIGS Data from the Visited Network. | +| | 13 | The Home Network ceases the FIGS monitoring of a subscriber's activities. | +| Visited Network capabilities | 14 | Based on roaming agreements, the Visited Network should advise the Home Network-FDS of information that suggests fraudulent activities. | +| | 15 | If the Visited Network does not have the resources to support a FIGS request, it should respond accordingly to the Home Network-FDS. | +| | 16 | Each Visited Network should limit the number of subscribers that each Home Network-FDS may request to be monitored using FIGS. Otherwise, a Home Network-FDS may take more than its "fair share" of the FIGS processing capability of a Visited Network. | +| | 17 | Information should be transferred from the Visited Network to the Home Network-FDS within two minutes of the occurrence of a FIGS-monitored event. This is because up-to-date information is a critical part of any fraud information system. The sooner data is transferred to the Home Network-FDS, the sooner fraud can be stopped. | +| | 18 | Based on roaming agreements, to transmit FIGS Data to the Home Network-FDS based on:
1 frequency requested by Home Network-FDS;
2 events specified by Home Network-FDS; and/or
3 on demand. | + +## **6.1 Management Service overview** + +Security Management includes the following function set groups according to ITU-T M.3400: + +- Prevention; +- Detection; +- Containment and recovery; +- Security Administration. + +Among the function set groups of ITU-T M.3400, this Recommendation only addresses aspects of Detection Function Set Groups in order to detect wireless fraud. + +A key list of management requirements for "Security – Audits: Counts of Fraudulent Use" includes the following: + +- Determination of security-related events; +- Recording of security-related events; +- Reporting of security-related events. + +Several sources of detecting security violations in a wireless network exist. The processes in place in Home Network-FDS and the Visited Network use various factors such as billing usage and pattern analysis to produce security reports. The reports and events that are exchanged between the two service providers form the basis of the detection aspects of this Recommendation. The potential information contained in these reports may include: Time and date stamp, Deviation usage data, Usage data records, Alarm event reports, and Subscriber information. + +## **6.2 Telecommunication resources** + +### **6.2.1 Fraud Information Gathering System (FIGS)** + +The Home Network-FDS is provided with data on the activities of subscribers in a Visited Network by way of using the Fraud Information Gathering System. The Home Network-FDS can make inferences about what the subscriber is doing and then take decisions on what the subscriber should be allowed to do. The following operations may be invoked in FIGS as described in the use cases: + +- 1) Fraud Alert: The Visited Network invokes this operation when fraud is suspected. +- 2) Activate Information Gathering: This operation starts up the process of monitoring particular subscriber activities. +- 3) Report FIGS: This operation is invoked by the Visited Network to relay gathered information. +- 4) Deactivate Information Gathering: This operation concludes the process of monitoring the subscriber's activities. +- 5) Modify FIGS Report: This operation alters the monitoring level and/or schedule of delivering subscriber activities. +- 6) Advice Suspend FIGS Monitoring: This operation is invoked by the Visited Network to inform the Home Network-FDS that information gathering has been suspended. +- 7) Advise Resume FIGS Monitoring: This operation is invoked by the Visited Network to inform the Home Network-FDS that information gathering has been resumed after it was suspended. + +### 6.2.2 Visited Network + +A Visited Network (Visited Service Provider) can receive FIGS monitoring requests. A Visited Network can then perform some of the following actions: + +- Activate FIGS monitoring for the requested roaming subscriber. The Home Network-FDS is then notified with reports as a result of the monitoring activities. +- The Visited Network may be overloaded, the request is suspended until monitoring capacity is restored and then FIGS monitoring is activated for the roaming subscriber requested. + +### 6.2.3 Home Network Fraud Detection System (HN-FDS) + +The Home Network-FDS requests FIGS monitoring from Visited Networks to start collecting data about particular subscriber activities. + +The HN-FDS then schedules receipt of security event reports, as specified in an agreed-upon time interval. Alternatively, the Home Network-FDS requests security event reports at any time from the Visited Network. In either case, security information should be delivered in as close to real time as possible. + +## 6.3 Fraud Information Gathering use cases + +![Diagram of FIGS use cases showing interactions between Home Network Fraud Detection System, Visited Network, and Fraud Information Gathering System.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +The diagram illustrates the use cases for FIGS, showing interactions between the Home Network Fraud Detection System (HN-FDS), the Visited Network, and the Fraud Information Gathering System (FIGS). The FIGS is represented by a large rectangular box containing seven use case bubbles: 'Fraud Alert', 'Activate Information on Gathering', 'Report FIGS', 'Deactivate Information Gathering', 'Modify FIGS Report', 'Advise Suspend FIGS Monitoring', and 'Advise Resume FIGS Monitoring'. The HN-FDS (represented by a stick figure on the left) and the Visited Network (represented by a stick figure on the right) both have lines connecting them to each of these seven use cases, indicating that both entities can initiate or be affected by these actions. The text 'T0414790-00' is located at the bottom right of the diagram box. + +Diagram of FIGS use cases showing interactions between Home Network Fraud Detection System, Visited Network, and Fraud Information Gathering System. + +Figure 2/M.3210.1 – FIGS use cases + +### 6.3.1 Fraud Alert use case + +| Name | Fraud Alert | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Summary | This operation is invoked by the Visited Network suspecting fraud to inform Home Network-FDS of need to initiate FIGS monitoring. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions | Subscriber fraud suspected. | +| Begins When | Subscriber roams to Visited Network. | +| Description | After a particular subscriber roam in a Visited Network, the Visited Network may inform the subscriber Home Network-FDS that it suspects fraudulent use. This alert may be the result of the roaming subscriber following an unusual usage pattern, for example. | +| Ends When | N/A | +| Exceptions | N/A | +| Post-Conditions | FIGS Monitoring requested.
Fraud no longer suspected.
Subscriber device deactivated. | +| Traceability | This use case fulfils the following requirements: 1 (Table 1) | + +### 6.3.2 Activate Information Gathering use case + +| Name | Activate Information Gathering | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Summary | This operation initiates the request to start up the process of monitoring particular subscriber activities. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions | Subscriber fraud suspected. | +| Begins When | Receive request from either:
– Home Network-FDS, or
– Visited Network request | +| Description | The Home Network-FDS may find it necessary to monitor a particular subscriber. This decision may be in response to the Visited Network Fraud Alert message. | +| Ends When | Home Network-FDS request to terminate subscriber monitoring. | +| Exceptions | Visited Network is unable to initiate monitoring. | +| Post-Conditions | Fraud no longer suspected.
Subscriber device deactivated. | +| Traceability | This use case fulfils the following requirements: 1, 8, 9, 10, 12 and 15 (Table 1) | + +### 6.3.3 Report FIGS use case + +| Name | Report FIGS | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Summary | This operation is invoked by the Visited Network to relay gathered information to the Home Network-FDS. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions | Subscriber fraud suspected. | +| Begins When | Subscriber roams to Visited Network. | +| Description | The Visited Network accumulates information about roaming subscriber usage for the Home Network-FDS. This information is only gathered based on the Home Network request to activate the subscriber monitoring. This information is then transmitted to the home network based on the set criteria. | +| Ends When | When FIGS monitoring is deactivated or FIGS is suspended because of Visited Network overload. | +| Exceptions | N/A | +| Post-Conditions | Fraud no longer suspected.
Subscriber device deactivated. | +| Traceability | This use case fulfils the following requirements: 2, 3, 4, 5, 6, 7, 12, 13, 14, 15, 17 and 18 (Table 1) | + +### 6.3.4 Deactivate Information Gathering use case + +| Name | Deactivate Information Gathering | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Summary | This operation is invoked by the Home Network-FDS to request terminating the process of monitoring the visiting subscriber's activities. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions | Either case is reached:
  • • Subscriber fraud not suspected.
  • • Subscriber finished roaming.
| +| Begins When | Receive request from the Home Network-FDS. | +| Description | Request is accepted and passed to the Visited Network. | +| Ends When | N/A | +| Exceptions | N/A | +| Post-Conditions | Fraud no longer suspected.
Subscriber device deactivated. | +| Traceability | This use case fulfils the following requirements: 7, and 13 (Table 1) | + +### 6.3.5 Modify FIGS Report use case + +| Name | Modify schedule for delivering Fraud Information | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Summary | The Home Network-FDS sends request to the Visited Network asking to modify the frequency of delivering monitoring reports. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions |
  • FIGS monitoring is in progress for a subscriber.
  • Home FDS requires subscriber activities to be monitored at a different level or on a different schedule than those identified in the roaming agreement.
| +| Begins When | Receive request from the Home Network-FDS. | +| Description | The Home Network-FDS may find it necessary to change:
a) the schedule of delivering the monitoring reports of a particular subscriber;
b) the level of fraud monitoring required. | +| Ends When | Request is accepted and passed to the Visited Network. | +| Exceptions | Visited System cannot process request. | +| Post-Conditions | New delivery schedule or monitoring level is established. | +| Traceability | This use case fulfils the following requirements: 8 and 18 (Table 1) | + +### 6.3.6 Advise Suspend FIGS Monitoring use case + +| Name | Advise Suspend FIGS Monitoring | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Summary | This operation is invoked by the Visited Network to inform the Home Network-FDS of suspending the collection of FIGS information because of resource shortage. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions | Subscriber fraud suspected and Visited Network resources are short. | +| Begins When | Visited Network resources cannot meet the demand to monitor existing roaming subscribers. | +| Description | The Visited Network monitoring resources may suffer from resource shortage. This may be the result of increased activities of a large number of roamers being monitored, for example. Consequently, a message is sent to some of the subscribers' Home Network informing them that monitoring is being suspended. | +| Ends When | Visited Network normal condition is restored and a message advising the Home Network of resuming the monitoring gets sent. | +| Exceptions | N/A | +| Post-Conditions | Fraud no longer suspected.
Subscriber device deactivated. | +| Traceability | This use case fulfils the following requirements: 10, 15 and 16 (Table 1) | + +### 6.3.7 Advise Resume FIGS Monitoring use case + +| Name | Advise Resume FIGS Monitoring | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------| +| Summary | This operation is invoked by the Visited Network to inform the Home Network-FDS of the resumption of collecting FIGS information. | +| Actor(s) | 1) Home Network-FDS
2) Visited Network | +| Pre-Conditions | Subscriber Fraud suspected. | +| Begins When | Subscriber roams to Visited Network. | +| Description | Visited Network resources are restored and can resume monitoring existing tagged roaming subscribers. | +| Ends When | Subscriber monitoring is ended or Visited Network FIGS System overload reoccurs. | +| Exceptions | N/A | +| Post-Conditions | Fraud no longer suspected.
Subscriber device deactivated. | +| Traceability | This use case fulfils the following requirements: 10, 15 and 16 (Table 1) | + +# 7 Management Functions analysis + +This clause provides the high-level description for the FIGS Security Management service. That is, it provides the messages needed to support the management functions for requesting and collecting security-related information between service providers. + +## 7.1 Fraud Information Gathering Function set + +FIGS Function set supports a service provider request and reporting of usage data from other service provider. Table 2 lists FIGS functions to illustrate the management activity originator and recipient. + +**Table 2/M.3210.1 – FIGS function sets interactions** + +| | Function | Originator | Responder | +|---|-------------------------------------------|------------------|------------------| +| 1 | Fraud Alert function | Visited Network | Home Network-FDS | +| 2 | Activate Information Gathering function | Home Network-FDS | Visited Network | +| 3 | Report FIGS function | Visited Network | Home Network-FDS | +| 4 | Deactivate Information Gathering function | Home Network-FDS | Visited Network | +| 5 | Modify FIGS reporting schedule function | Home Network-FDS | Visited Network | +| 6 | Advise Suspend FIGS Monitoring function | Visited Network | Home Network-FDS | +| 7 | Advise Resume FIGS Monitoring function | Visited Network | Home Network-FDS | + +## 7.2 Object Classes and State Chart + +The state machine describing FIGS related interaction is illustrated in the diagram in Figure 3. As messages are exchanged between the Visited Network and the Home Fraud Detection System, the message link between them may be situated in one of the states listed (see Figure 4). + +![FIGS state diagram showing states: FIGS Request Pending, FIGS Monitoring in Progress (Information Gathered), Send FIGS Data, Deactivate FIGS Pending, FIGS Suspended, and Failure: Visited System Busy. Transitions include self-loops and paths between these states leading to an end state.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +``` + +stateDiagram-v2 + [*] --> FIGS Request Pending + FIGS Request Pending --> FIGS Monitoring in Progress (Information Gathered) + FIGS Request Pending --> Failure: Visited System Busy + FIGS Monitoring in Progress (Information Gathered) --> FIGS Monitoring in Progress (Information Gathered) + FIGS Monitoring in Progress (Information Gathered) --> Send FIGS Data + FIGS Monitoring in Progress (Information Gathered) --> Deactivate FIGS Pending + FIGS Monitoring in Progress (Information Gathered) --> FIGS Suspended + Send FIGS Data --> FIGS Monitoring in Progress (Information Gathered) + Send FIGS Data --> Deactivate FIGS Pending + Deactivate FIGS Pending --> [*] + FIGS Suspended --> FIGS Monitoring in Progress (Information Gathered) + FIGS Suspended --> Failure: Visited System Busy + Failure: Visited System Busy --> FIGS Monitoring in Progress (Information Gathered) + Failure: Visited System Busy --> FIGS Suspended + Failure: Visited System Busy --> [*] + +``` + +T0414800-00 + +FIGS state diagram showing states: FIGS Request Pending, FIGS Monitoring in Progress (Information Gathered), Send FIGS Data, Deactivate FIGS Pending, FIGS Suspended, and Failure: Visited System Busy. Transitions include self-loops and paths between these states leading to an end state. + +Figure 3/M.3210.1 – FIGS state diagram + +![FIGS class diagram showing classes: Home Service Provider, Visited Service Provider, Fraud Detection System, Service Provider Agreement, Subscriber Fraud Information, Subscriber FIGS Data, and FIGS Transmission Schedule. Associations are shown between Home Service Provider and Visited Service Provider, and between Service Provider Agreement and the other three classes.](dfe556fea00682b09a59427aaf72051c_img.jpg) + +``` + +classDiagram + class HomeServiceProvider["Home Service Provider"] + class VisitedServiceProvider["Visited Service Provider"] + class FraudDetectionSystem["Fraud Detection System"] + class ServiceProviderAgreement["Service Provider Agreement"] + class SubscriberFraudInformation["Subscriber Fraud Information"] + class SubscriberFIGSData["Subscriber FIGS Data"] + class FIGSTransmissionSchedule["FIGS Transmission Schedule"] + + HomeServiceProvider -- VisitedServiceProvider : -End11 -End12 + HomeServiceProvider *-- FraudDetectionSystem : -End8 -End7 + FraudDetectionSystem *-- SubscriberFraudInformation : -End9 -End10 + ServiceProviderAgreement *-- SubscriberFIGSData : -End1 -End2 + ServiceProviderAgreement *-- FIGSTransmissionSchedule : -End3 -End4 + ServiceProviderAgreement *-- VisitedServiceProvider : -End5 -End6 + +``` + +T0414810-00 + +FIGS class diagram showing classes: Home Service Provider, Visited Service Provider, Fraud Detection System, Service Provider Agreement, Subscriber Fraud Information, Subscriber FIGS Data, and FIGS Transmission Schedule. Associations are shown between Home Service Provider and Visited Service Provider, and between Service Provider Agreement and the other three classes. + +Figure 4/M.3210.1 – FIGS class diagram + +## 7.3 Fraud Information Gathering functions and sequence diagrams + +### 7.3.1 Fraud Alert function + +After a particular subscriber roam in a Visited Network, the Visited Network may inform the subscriber Home Network-FDS that it suspects fraudulent use. This alert may be the result of the roaming subscriber following an unusual usage pattern, for example, as in Figure 5: + +![Sequence diagram showing the alert message flow from Visited Network to Home Network-FDS. The diagram consists of two vertical lifelines: 'Home Network-FDS' on the left and 'Visited Network' on the right. A horizontal arrow labeled 'Fraud Alert Message' points from the Visited Network lifeline to the Home Network-FDS lifeline. A small text label 'T0414820-00' is located in the bottom right corner of the diagram area.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Sequence diagram showing the alert message flow from Visited Network to Home Network-FDS. The diagram consists of two vertical lifelines: 'Home Network-FDS' on the left and 'Visited Network' on the right. A horizontal arrow labeled 'Fraud Alert Message' points from the Visited Network lifeline to the Home Network-FDS lifeline. A small text label 'T0414820-00' is located in the bottom right corner of the diagram area. + +**Figure 5/M.3210.1 – Alert Message flow** + +Consequently, the Home Network-FDS is informed. In the scenario shown in Figure 5, the Visited Network informs the Visited Network of a particular roaming subscriber. + +#### 7.3.1.1 Information flow + +The information exchanged for Fraud Alert is detailed in Table 3. + +**Table 3/M.3210.1 – Fraud Alert exchanged information** + +| | Home Network-FDS | Visited Network | Notes | +|-----------------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | | m | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number). | +| Electronic Serial Number | | m | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards. | + +### 7.3.2 Activate Information Gathering function + +The Home Network-FDS may find it necessary to monitor a particular subscriber. This decision may be in response to the Visited Network Fraud Alert message for example. In this scenario, the Home Network-FDS requests from the Visited Network to monitor a particular roaming subscriber. The Visited Network is required to acknowledge the receipt of this request. + +The request to activate information gathering is only initiated by the Home Network-FDS and transmitted to the Visited Network as shown in Figure 6. + +![Sequence diagram showing message flow to activate FIGS between Home Network-FDS and Visited Network. The Home Network-FDS sends an 'Activate Information Gathering' message to the Visited Network. The Visited Network responds with either a 'Positive Acknowledgement' or a 'Generic Error'.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +sequenceDiagram + participant Home Network-FDS + participant Visited Network + Note right of Visited Network: T0414830-00 + Home Network-FDS->>Visited Network: Activate Information Gathering + Visited Network-->>Home Network-FDS: Positive Acknowledgement + Visited Network-->>Home Network-FDS: Generic Error + +``` + +Sequence diagram showing message flow to activate FIGS between Home Network-FDS and Visited Network. The Home Network-FDS sends an 'Activate Information Gathering' message to the Visited Network. The Visited Network responds with either a 'Positive Acknowledgement' or a 'Generic Error'. + +**Figure 6/M.3210.1 – Message flow to activate FIGS** + +#### 7.3.2.1 Information flow + +The information exchanged for Activate FIGS is detailed in Table 4. + +**Table 4/M.3210.1 – Activate FIGS exchanged information** + +| | Home Network-FDS | Visited Network | Notes | +|------------------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | m | | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number). | +| Electronic Serial Number | m | | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards. | +| Activate FIGS reason | c | | Reason Code:
– Fraud is suspected;
– Other. | +| Level of Monitoring Required | m | | Level of Monitoring:
Level 1 – (near) real time billing;
Level 2 – partial call records;
Level 3 – full call records. | +| Confirmation | | m | Result code:
R0: other;
R1: success;
R2: unknown subscriber(s). | + +### 7.3.3 Report FIGS function + +The Visited Network accumulates information about roaming subscriber usage for the Home Network-FDS. This information is only gathered based on the Home Network request to activate the subscriber monitoring. + +In this scenario, shown in Figure 7, the Visited Network sends the Home Network-FDS particular roaming subscriber information periodically. + +![Sequence diagram showing a 'FIGS Report' message flow from the Visited Network to the Home Network-FDS. The diagram consists of two vertical lifelines: 'Home Network-FDS' on the left and 'Visited Network' on the right. A horizontal arrow labeled 'FIGS Report' points from the Visited Network lifeline to the Home Network-FDS lifeline.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Sequence diagram showing a 'FIGS Report' message flow from the Visited Network to the Home Network-FDS. The diagram consists of two vertical lifelines: 'Home Network-FDS' on the left and 'Visited Network' on the right. A horizontal arrow labeled 'FIGS Report' points from the Visited Network lifeline to the Home Network-FDS lifeline. + +T0414840-00 + +**Figure 7/M.3210.1 – Message flow to send information** + +#### **7.3.3.1 Information flow** + +The Report FIGS information is detailed in Table 5. + +**Table 5/M.3210.1 – Report FIGS information** + +| | Home Network-FDS | Visited Network | Notes | +|-----------------------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | m | | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number) | +| Electronic Serial Number | m | | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards. | +| FIGS Report | c | | Reason code:
– Fraud is suspected;
– Other. | +| Confirmation | | m | Result code:
R0: other;
R1: success;
R2: unknown subscriber(s). | + +### **7.3.4 Deactivate Information Gathering function** + +The Home Network-FDS may find it necessary to terminate monitoring a particular subscriber. This decision may be a result of determining that a subscriber usage pattern is verified to be ordinary. In this scenario, the Home Network-FDS requests from the Visited Network to terminate the monitoring of a particular roaming subscriber. The Visited Network is required to acknowledge the receipt of this request and to terminate the monitoring. + +The request to deactivate information gathering is only initiated by the Home Network-FDS and transmitted to the Visited Network as shown in Figure 8. + +![Sequence diagram showing message flow to deactivate FIGS between Home Network-FDS and Visited Network. The Home Network-FDS sends a 'Deactivate Information Gathering' message to the Visited Network. The Visited Network responds with either a 'Positive Acknowledgement' or a 'Generic Error'.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +sequenceDiagram + participant Home Network-FDS + participant Visited Network + Note right of Visited Network: T0414850-00 + Home Network-FDS->>Visited Network: Deactivate Information Gathering + Visited Network-->>Home Network-FDS: Positive Acknowledgement + Visited Network-->>Home Network-FDS: Generic Error + +``` + +Sequence diagram showing message flow to deactivate FIGS between Home Network-FDS and Visited Network. The Home Network-FDS sends a 'Deactivate Information Gathering' message to the Visited Network. The Visited Network responds with either a 'Positive Acknowledgement' or a 'Generic Error'. + +**Figure 8/M.3210.1 – Message flow to deactivate FIGS** + +#### 7.3.4.1 Information flow + +The Deactivate FIGS information exchanged is detailed in Table 6. + +**Table 6/M.3210.1 – Deactivate FIGS exchanged information** + +| | Home Network-FDS | Visited Network | Notes | +|-----------------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | m | | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number). | +| Electronic Serial Number | m | | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards. | +| Deactivate FIGS reason | c | | Reason code:
– Fraud is detected – Subscriber suspended.
– No Fraud is concluded. | +| Confirmation | | m | Result code:
R0: other;
R1: success;
R2: unknown subscriber(s). | + +### 7.3.5 Modify FIGS Report function + +The Home Network-FDS may find it necessary to change the schedule of delivering the monitoring reports of a particular subscriber. This decision may be a result of overload condition. + +In this scenario, shown in Figure 9, the Home Network-FDS requests from the Visited Network to change the reporting schedule. The Visited Network is required to acknowledge the receipt of this request and to alter the reporting schedule. + +![Sequence diagram showing message flow between Home Network-FDS and Visited Network. The flow consists of: 1. Home Network-FDS sends 'Modify FIGS Report' to Visited Network. 2. Visited Network sends 'Positive Acknowledgement' back to Home Network-FDS. 3. Alternatively, Visited Network sends a dashed 'Generic Error' message back to Home Network-FDS.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +sequenceDiagram + participant Home Network-FDS + participant Visited Network + Note right of Visited Network: T0414860-00 + Home Network-FDS->>Visited Network: Modify FIGS Report + Visited Network-->>Home Network-FDS: Positive Acknowledgement + Visited Network-->>Home Network-FDS: Generic Error + +``` + +Sequence diagram showing message flow between Home Network-FDS and Visited Network. The flow consists of: 1. Home Network-FDS sends 'Modify FIGS Report' to Visited Network. 2. Visited Network sends 'Positive Acknowledgement' back to Home Network-FDS. 3. Alternatively, Visited Network sends a dashed 'Generic Error' message back to Home Network-FDS. + +**Figure 9/M.3210.1 – Message flow to change reporting schedule** + +#### **7.3.5.1 Information flow** + +The Modify FIGS Reporting exchanged information is detailed in Table 7. + +**Table 7/M.3210.1 – Modify FIGS Reporting exchanged information** + +| | Home Network FDS | Visited Network | Notes | +|-----------------------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | m | | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number) | +| Electronic Serial Number | m | | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards | +| New Schedule | c | | If the modification request is for a change of schedule, this element is mandatory Choice of:
– Time Interval;
– Absolute times. | +| New Monitoring Level | c | | If the modification request is for a change of monitoring level, this element is mandatory. Choice of:
– Level 1;
– Level 2;
– Level 3. | +| Confirmation | | m | Result code:
R0: other;
R1: success;
R2: unknown subscriber(s). | + +### 7.3.6 Advise Suspend FIGS Monitoring function + +The Visited Network monitoring resources may suffer from shortage. This may result in the increased activities of a large number of roamers being monitored, for example, as in Figure 10: + +![Sequence diagram showing message flow between Home Network-FDS and Visited Network. The Home Network-FDS sends a 'Suspend FIGS Monitoring' message to the Visited Network. The Visited Network responds with an 'Acknowledgement' or a 'Generic Error'.](366a77fdefb0097b3289b4a011911390_img.jpg) + +``` + +sequenceDiagram + participant Home Network-FDS + participant Visited Network + Note right of Visited Network: T0414870-00 + Home Network-FDS->>Visited Network: Suspend FIGS Monitoring + Visited Network-->>Home Network-FDS: Acknowledgement + Visited Network-->>Home Network-FDS: Generic Error + +``` + +Sequence diagram showing message flow between Home Network-FDS and Visited Network. The Home Network-FDS sends a 'Suspend FIGS Monitoring' message to the Visited Network. The Visited Network responds with an 'Acknowledgement' or a 'Generic Error'. + +Figure 10/M.3210.1 – Message flow to suspend FIGS + +Consequently, as shown in Figure 10, selected subscribers' monitoring may be suspended and the Home Network-FDS is informed. In this scenario, the Home Network-FDS informs the Visited Network of its decision to suspend the monitoring of particular roaming subscriber information. + +#### 7.3.6.1 Information flow + +The information exchanged between the Home Network-FDS and the Visited Network to suspend the monitoring of a roaming subscriber is detailed in Table 8. + +Table 8/M.3210.1 – Advise Suspend FIGS exchanged information + +| | Home Network FDS | Visited Network | Notes | +|-----------------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | m | m= | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number). | +| Electronic Serial Number | m | m= | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards. | +| Suspend service code | m | | Reason code:
– System Problems;
– Other. | +| Confirmation | | m | Confirmation code:
R0: other;
R1: success;
R2: unknown subscriber. | + +### 7.3.7 Advise Resume FIGS Monitoring function + +When the Visited Network monitoring resources are restored after shortage, monitoring of suspended roaming subscribers is resumed. The Home Network-FDS is informed. + +In this scenario, as shown in Figure 11, the Visited Network informs the Home Network-FDS of its decision to resume monitoring of the previously suspended roaming subscriber. + +![Sequence diagram showing message flow between Home Network-FDS and Visited Network for resuming FIGS monitoring. The Visited Network sends a 'Resume FIGS Monitoring' message to the Home Network-FDS. The Home Network-FDS responds with an 'Acknowledgement'. A 'Generic Error' message is shown as a dashed line from the Visited Network to the Home Network-FDS.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant Visited Network + participant Home Network-FDS + Note right of Visited Network: T0414880-00 + Visited Network->>Home Network-FDS: Resume FIGS Monitoring + Home Network-FDS-->>Visited Network: Acknowledgement + Visited Network-->>Home Network-FDS: Generic Error + +``` + +Sequence diagram showing message flow between Home Network-FDS and Visited Network for resuming FIGS monitoring. The Visited Network sends a 'Resume FIGS Monitoring' message to the Home Network-FDS. The Home Network-FDS responds with an 'Acknowledgement'. A 'Generic Error' message is shown as a dashed line from the Visited Network to the Home Network-FDS. + +Figure 11/M.3210.1 – Message flow to resume FIGS + +#### 7.3.7.1 Information flow + +The Advise Resume FIGS exchanged information is detailed in Table 9. + +Table 9/M.3210.1 – Advise Resume FIGS exchanged information + +| | Home Network FDS | Visited Network | Notes | +|-----------------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G User Identification List | m | m= | List of unique identification of the wireless subscriber, e.g. (International Mobile Subscriber Identity (IMSI) or Universal Personal Telecommunications Number). | +| Electronic Serial Number | m | m= | The Electronic Serial Number of the subscriber terminal as defined in the wireless signalling standards. | +| Resume service code | m | | Reason code:
– System restored;
– Other. | +| Confirmation | | m | Confirmation code:
R0: other;
R1: success;
R2: unknown subscriber. | + +# ANNEX A + +## **Fraud Management criteria** + +Telecommunications Management Networks need to provide the management means to detect and analyse security violations and include security aspects that evolve from the mobility of customers. Examples of detecting fraudulent use may be the result of: + +- analysis of collected subscriber information on a customer suspected of security violations such as simple MIN/ESN cloning; +- analysis of collected network information on the network to detect a suspected security violation; +- customer usage pattern analysis indicating a significant variation from normal usage patterns; +- internal traffic and activity pattern analysis that results in the detection of a customer or user (external or internal) security violation. + +Fraudulent use may or may not be a consequence of the following detected failures: + +- network failure to decrypt customer-encrypted messages; +- customer failure to produce correct responses to authentication challenges; +- mismatches in the customer-reported value of the "call-count" parameter; +- failure reports indicating difficulty in updating users, Shared Secret Data (SSD). + +# ANNEX B + +## Information transferred by the Visited Network + +| Information | Description | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Dialled digits | The Dialled digits are required as these are an important indicator in deciding if a call is fraudulent or not – certain call destinations are more likely to be called fraudulently than others. | +| A subscriber | A subscriber can be used to identify the subscriber. | +| B, C subscriber | B, C subscribers are relevant as some call destinations are more subject to fraud than others. | +| CGI | Cell Global Identifier (CGI) is relevant as some cells in a PLMN are more subject to fraud than others. | +| IMSI | The IMSI is used to reference the subscriber. | +| IMEI | The IMEI can be used to check if a stolen handset has been used. | +| Call Start Time/Date | The Call Start Time/Date is required so that the call duration can be calculated (if the call end time and not call duration is given at call conclusion) and because the call start time can also be an important indicator of fraudulency. | +| Call Duration | The Call Duration gives the duration of the call at the sending of the partial call information – call duration can be an important indicator of fraudulency. If call end is sent instead, the duration can be calculated using the call start and end times. | +| Call Reference | The Call Reference is used to reference a particular call. | +| MO/MT indicator | The MO/MT indicator is required because call charging is different for MO and MT calls. | +| Visited MSC address | The Visited MSC address gives the PLMN on which the call was made. | +| Type of SS event | The Type of SS event record is sent if the "call" start is actually the invocation of a supplementary service, e.g. ECT. The Type of SS event is required as this can help to indicate if the mobile is being fraudulently used or not. | +| Type of Basic Service | The Type of Basic Service indicates whether a teleservice or bearer service is being used and which sort of teleservice or bearer service is being used and is sent if the event is a call and not a supplementary service. The Type of Basic Service is required as this can help to indicate if the mobile station is being fraudulently used or not. | + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure and Internet protocol aspects | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3211.1-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3211.1-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e86be364c2e70dc0688295c12b1f0dfde871be1 --- /dev/null +++ b/marked/M/T-REC-M.3211.1-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f5a9bf4a6fdd6b2b1432e4a58154012788a8fe0b6a49989a97624d32d6d507c +size 8198 diff --git a/marked/M/T-REC-M.330-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.330-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..858f816b53ad535a7329109d7309f2f645233027 --- /dev/null +++ b/marked/M/T-REC-M.330-198811-I_PDF-E/raw.md @@ -0,0 +1,65 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.330** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**NUMBERING OF GROUPS +WITHIN A SUPERGROUP** + +**ITU-T Recommendation M.330** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.330 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# NUMBERING OF GROUPS WITHIN A SUPERGROUP + +The position occupied by a group within a supergroup is identified by a number in the series from 1 to 5, the numbers being allocated in ascending order of frequency in the basic supergroup 312 kHz to 552 kHz and in descending order of frequency in the other supergroups. (See Figure 1/M.330.) + +If all the groups comprising the supergroup are erect: + +- the basic supergroup is said to be *erect*; +- the other supergroups are said to be *inverted*. + +![Diagram showing the numbering of 12 circuit groups and channels in supergroups. It displays three supergroups (1, 2, and 3) with their respective group numbers (1-5) and channel numbers (1-12) across a frequency range from 60 kHz to 804 kHz. Supergroup 1 is the 'Basic supergroup' (312-552 kHz) and is 'erect' (groups 1-5 in ascending order). Supergroups 2 and 3 are 'inverted' (groups 5-1 in ascending order).](af191c691aa1282801a350dbb14c7925_img.jpg) + +| Supergroup No. | 1 | | | | | (Basic supergroup) 2 | | | | | 3 | | | | | | | | +|----------------|----|-----|-----|-----|-----|----------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| Group No. | 5 | 4 | 3 | 2 | 1 | 1 | 2 | 3 | 4 | 5 | 5 | 4 | 3 | 2 | 1 | | | | +| Channel No. | 12 | 1 | 12 | 1 | 12 | 1 | 12 | 1 | 12 | 1 | 12 | 1 | 12 | 1 | 12 | | | | +| Frequency kHz | 60 | 108 | 156 | 204 | 252 | 300 | 312 | 360 | 408 | 456 | 504 | 552 | 564 | 612 | 660 | 708 | 756 | 804 | + +Diagram showing the numbering of 12 circuit groups and channels in supergroups. It displays three supergroups (1, 2, and 3) with their respective group numbers (1-5) and channel numbers (1-12) across a frequency range from 60 kHz to 804 kHz. Supergroup 1 is the 'Basic supergroup' (312-552 kHz) and is 'erect' (groups 1-5 in ascending order). Supergroups 2 and 3 are 'inverted' (groups 5-1 in ascending order). + +CCITT - 36690 +d01-sc + +FIGURE 1/M.330 + +Numbering of 12 circuit groups and channels in supergroups \ No newline at end of file diff --git a/marked/M/T-REC-M.3300-199806-I_PDF-E/raw.md b/marked/M/T-REC-M.3300-199806-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c11aef493575c156c10503d4474ab841d49a6a5e --- /dev/null +++ b/marked/M/T-REC-M.3300-199806-I_PDF-E/raw.md @@ -0,0 +1,990 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3300** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(06/98) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +# --- **TMN F interface requirements** + +ITU-T Recommendation M.3300 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +# **ITU-T RECOMMENDATION M.3300** + +# **TMN F INTERFACE REQUIREMENTS** + +## **Summary** + +This Recommendation provides requirements for the TMN F interface. The F interface is between a Workstation and other TMN physical blocks: an Operations Systems (OS), Mediation Device (MD), or Network Element (NE). + +### **Source** + +ITU-T Recommendation M.3300 was revised by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of June 1998. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +### NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +### INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1998 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +*Page* + +| | | | +|----|-------------------------------------------------------------------|----| +| 1 | Scope ..... | 1 | +| 2 | References ..... | 1 | +| 3 | Definitions ..... | 1 | +| | 3.19 Definitions imported from other Recommendations..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions..... | 4 | +| 6 | Introduction to the F interface ..... | 4 | +| | 6.1 Why Is The F interface needed? ..... | 4 | +| 7 | F interface architecture ..... | 5 | +| | 7.1 The F interface within the TMN architecture..... | 5 | +| | 7.2 TMN functional architecture and the F interface ..... | 5 | +| | 7.3 TMN Physical architecture and the F interface..... | 7 | +| | 7.4 TMN information architecture and the F interface ..... | 8 | +| | 7.5 F interface/f reference point and the g reference point ..... | 8 | +| | 7.6 Summary of architectural implications for requirements..... | 9 | +| 8 | TMN user's requirements impacting the F interface ..... | 9 | +| | 8.1 General requirements ..... | 10 | +| | 8.2 Task-related user requirements ..... | 10 | +| 9 | Initialization requirements ..... | 11 | +| 10 | Object management requirements ..... | 11 | +| | 10.1 Relationships between WOs and MOs..... | 12 | +| | 10.1.1 UMO/MO cardinality ..... | 13 | +| | 10.2 Naming..... | 15 | +| | 10.3 Retrieval services ..... | 15 | +| | 10.4 Modification services..... | 15 | +| | 10.5 Notification services..... | 16 | +| | 10.6 Create services ..... | 16 | +| | 10.7 Destruction services ..... | 16 | +| 11 | Shared Management Knowledge requirements ..... | 17 | +| | 11.1 Roles ..... | 17 | +| | 11.2 Establishment of Shared Management Knowledge..... | 17 | +| 12 | Event registration/notification requirements ..... | 18 | +| | 12.1 Receiving event notifications..... | 18 | +| | 12.2 Controlling event notification ..... | 18 | +| 13 | Location transparencies requirements ..... | 18 | +| 14 | Data consistency requirements ..... | 19 | +| 15 | Quality, performance, and OA&M requirements ..... | 19 | +| | 15.1 Initialization performance ..... | 19 | +| | 15.2 Message transfer ..... | 19 | +| | 15.3 Reliability, availability, survivability..... | 19 | +| | 15.4 Software management..... | 19 | +| | 15.5 Real-time message management ..... | 20 | + +| | | | +|------|----------------------------------------------------------|----| +| 16 | Security requirements ..... | 20 | +| 16.1 | User identification requirements ..... | 20 | +| 16.2 | Authentication..... | 20 | +| 16.3 | Access control ..... | 20 | +| 16.4 | Data integrity..... | 20 | +| 16.5 | Privacy ..... | 20 | +| 16.6 | Auditing ..... | 20 | +| 17 | Physical implementation requirements..... | 21 | +| 18 | What's part of WSF but not part of the F interface ..... | 21 | +| | Appendix I – Recommendation M.3300 (1992) ..... | 21 | +| | Appendice II – Bibliography ..... | 22 | + +# TMN F INTERFACE REQUIREMENTS + +*(revised in 1998)* + +## 1 Scope + +This Recommendation defines the functional requirements for the TMN interface to the Workstation. The F interface requirements imply certain capabilities in Workstations. Note that a Workstation may have capabilities in addition to those that are relevant to the F interface. + +The functionality specified at the interface implies there are applications that need that functionality. However, any particular application may not use all of the requirements for this interface. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other reference listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network*. + +## 3 Definitions + +This Recommendation defines the following terms: + +- 3.1 user, TMN user:** Recommendation M.3020 defines a TMN user as "that which requires the TMN management services in support of its activities. It may be a human user applying for the use of services via some human-machine communication or it may be some computer-based organizational system requiring the capabilities of the TMN." Within this Recommendation, the terms "TMN user" and "user" refer to *a human user at a Workstation* accessing TMN functionality. +- 3.2 user interface:** Human-computer interface or human-machine interface. +- 3.3 F interface:** An interface applied at f reference points. The F interface is between a Workstation and other TMN physical blocks: an Operations System (OS), Mediation Device (MD), or Network Element (NE). +- 3.4 Workstation:** A physical block that performs the workstation function. +- 3.5 workstation function:** A function block that interprets TMN information for the user, and vice versa. +- 3.6 f reference point:** A reference point that is located between the workstation function block and the operations system function block or mediation function block. +- 3.7 g reference point:** A reference point located outside the TMN, between the human user and the workstation function block. +- 3.8 user interface support function:** A functional component that translates information held in TMN information models to a displayable format for the human-machine interface and that translates user input to TMN information models. +- 3.9 workstation support function:** A functional component that provides support for the workstation function block, including data access and manipulation, invocation and confirmation of actions, transmittal of notifications, and that hides the existence of other function blocks from the user. + +**3.10 display client:** A "managing" Workstation that makes requests to a display server (another Workstation) to display information in a specific layout and format on the display server's screen. + +**3.11 display server:** A Workstation that fulfils requests made by a display client (another Workstation) to display information in a specific layout and format on its screen. + +**3.12 F interface instance:** An association between a user and an OS that is characterized uniquely by the combination of the instance of communication, the endpoints (specific WS and OS), and the portion of the agent's MIB made visible. + +**3.13 managed objects:** A management view of a resource that may be managed through the use of management protocol(s). + +**3.14 management information base:** The visible management information exposed on the F interface by an agent (an OS or WS currently assuming an agent role). + +**3.15 Workstation objects:** Objects in the Workstation that have F interface interactions. + +**3.16 user-management objects:** Workstation objects that represent managed objects in the Operations System. + +**3.17 Workstation support objects** (in this Recommendation, also referred to as **support objects**): Workstation objects that are not user-management objects. + +**3.18 OS:** As defined in Recommendation M.3010, with the following addition: Since WSF may communicate with OSF or MF in an OS, MD, or NE, the term "OS" is used for conciseness to represent "OS, MD, or NE" throughout this Recommendation. + +### **3.19 Definitions imported from other Recommendations** + +This Recommendation uses terms defined in Recommendation M.3010: + +- Telecommunications Management Network (TMN); +- TMN physical block; +- TMN function block; +- TMN reference point; +- TMN functional component; +- TMN management service; +- TMN managed area; +- TMN management function; +- operations system; +- mediation device; +- network element; +- operations system function; +- mediation function; +- security function; +- directory access function; +- directory system function; +- message communication function; +- information conversion function. + +This Recommendation uses the following terms defined in Recommendations X.701 and X.703: + +- manager; +- agent; +- shared management knowledge. + +This Recommendation uses the following term defined in Recommendation X.200: + +- association. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations: + +| | | +|---------------|----------------------------------------------------------------| +| DAF | Directory Access Function | +| DSF | Directory System Function | +| EFD | Event Forwarding Discriminator | +| ICF | Information Conversion Function | +| IT | Information Technology | +| MCF | Message Communication Function | +| MD | Mediation Device | +| MF | Mediation Function | +| MIB | Management Information Base | +| MO | Managed Object | +| NE | Network Element | +| NEF | Network Element Function | +| OS | Operations System | +| OSF | Operations System Function | +| OSF-MAF (A/M) | OSF-Management Application Function (in agent or manager role) | +| OSI | Open Systems Interconnection | +| SF | Security Function | +| SMK | Shared Management Knowledge | +| TMN | Telecommunications Management Network | +| UI | User Interface | +| UISF | User Interface Support Function | +| UMO | User-Management Object | +| WO | Workstation Object | +| WS | Workstation | +| WSF | Workstation Function | +| WSSF | Workstation Support Function | + +## 5 Conventions + +The following conventions apply: + +- Initial capitalization of names is used when introducing terms that are familiar to readers by their acronyms. +- Uppercase letters (F, Q in "Q3", and X) identify TMN physical interfaces. +- Lowercase letters (f, g, q in "q3" and x) identify TMN reference points. + +In figures, the following conventions apply: + +- Open circles represent TMN physical interfaces. +- Filled circles represent TMN reference points. +- Boxes with labels inside them represent TMN physical blocks. +- Ovals with labels inside them represent TMN function blocks or functional components. + +## 6 Introduction to the F interface + +This Recommendation provides requirements for the TMN F interface. The F interface is between a Workstation (WS) and a TMN physical block containing Operations System Functions (OSFs) or Mediation Functions (MFs). Operations Systems (OSs), Mediation Devices (MDs), and Network Elements (NEs) may contain OSF or MF. F interface requirements are independent of which TMN physical block supports them, so this Recommendation will use the term "Operations System" or "OS" to refer to OSs, MDs and NEs alike. + +### 6.1 Why Is The F interface needed? + +Recommendation M.3010, *Principles for a Telecommunications Management Network*, introduces the F interface. To enable human operators to interact with the TMN, a Workstation Function (WSF) must be present. When the WSF is implemented on a system physically distinct from an Operations System Function (OSF), those systems communicate via an F interface. + +The F interface is needed: + +- for TMN interactions between a user and an OS; +- to allow for the interoperability of different systems within a TMN, including systems developed by different suppliers; +- to facilitate work centre re-engineering/consolidation that is taking place in the telecommunications industry; +- to allow for modular implementation of a TMN: an organization can change and upgrade various modules providing specified functionalities; +- to support efficient systems integration in a TMN; +- to allow User Interface (UI) software to be left alone when changes or rearrangements are made to OS functionality; +- to allow OS software to be left alone and changes made to UI software, taking advantage of advances in UI technology; +- to allow UI customization for an individual service provider, supporting a common look and feel. + +## 7 F interface architecture + +### 7.1 The F interface within the TMN architecture + +The TMN architecture is defined in Recommendation M.3010. This Recommendation summarizes some of the architecture relevant to the WS and the F interface as an aid to the reader of this Recommendation M.3010 is the authoritative definition of the TMN architecture. + +Figure 1 illustrates the relationship between some configurations of workstations and OSs in the physical and functional aspects. Workstation functionality can be distributed (see subclause 7.2, TMN functional architecture and the F interface) as illustrated for the display client and server in Figure 1. + +![Figure 1/M.3300 – Example TMN F interface configurations. The diagram shows various configurations of Workstations (WS) and Operating Systems (OS) connected via F,f reference points. On the left, a 'distributed WS' (dotted box) contains two 'display server' blocks, each connected to a 'WSF' (Workstation Function) block, which in turn connects to a 'display client' block. This 'display client' connects to an 'F,f' reference point. This 'F,f' point is connected to an 'OSF' (Operations Systems Function) block within an 'OS' (Operating System) block. To the right, another 'F,f' reference point connects a 'WSF' block within a 'WS' (Workstation) block to an 'OSF' block within an 'OS' block. Further right, a third 'F,f' reference point connects a 'WSF' block within a 'WS' block to an 'OSF' block within a 'NE' (Network Element) block. The 'NE' block also contains a 'NEF' (Network Element Function) block connected to the 'OSF' block via a 'q' reference point. Ellipses indicate additional configurations and components.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Figure 1/M.3300 – Example TMN F interface configurations. The diagram shows various configurations of Workstations (WS) and Operating Systems (OS) connected via F,f reference points. On the left, a 'distributed WS' (dotted box) contains two 'display server' blocks, each connected to a 'WSF' (Workstation Function) block, which in turn connects to a 'display client' block. This 'display client' connects to an 'F,f' reference point. This 'F,f' point is connected to an 'OSF' (Operations Systems Function) block within an 'OS' (Operating System) block. To the right, another 'F,f' reference point connects a 'WSF' block within a 'WS' (Workstation) block to an 'OSF' block within an 'OS' block. Further right, a third 'F,f' reference point connects a 'WSF' block within a 'WS' block to an 'OSF' block within a 'NE' (Network Element) block. The 'NE' block also contains a 'NEF' (Network Element Function) block connected to the 'OSF' block via a 'q' reference point. Ellipses indicate additional configurations and components. + +NOTE – The dotted box represents a "distributed WS" that supports the WSF with functionality distributed over multiple physical boxes. + +Figure 1/M.3300 – Example TMN F interface configurations + +TMN architecture is defined in three aspects: functional architecture, physical architecture, and information architecture. + +### 7.2 TMN functional architecture and the F interface + +TMN function blocks provide the TMN with groupings of functions that allow the TMN to perform the TMN management functions. Pairs of TMN function blocks that need to exchange management information are separated by reference points. If the reference points become external, that is, the TMN function blocks are implemented in separate TMN physical blocks, the reference point is implemented as a TMN interface; the f reference point is implemented as an F interface. + +The TMN function blocks that exchange information over an f reference point are the Workstation Function (WSF) block and the Operations Systems Function (OSF) block. The f reference point defines the service boundary between the OSF and the WSF. + +Each function block contains several functional components, which are the units that provide a coherent set of TMN functionality. Functional components that may be found in a WSF are: + +- User Interface Support Function (UISF); +- Security Function (SF); + +- Message Communications Function (MCF); +- Directory Access Function (DAF). + +Functional components that may be found in an OSF, that may interact with the functional components in the WSF, are: + +- Workstation Support Function (WSSF); +- Security Function (SF); +- Message Communications Function (MCF); +- Directory System Function (DSF); +- Operations Systems Function – Management Application Function in manager or agent role (OSF-MAF (A/M)). + +Figure 2 shows the functional components that are relevant for the f reference point, and indicates for each whether it is required or optional (from the point of view of the f reference point). + +![Diagram of the f reference point within the TMN functional architecture. It shows two main functional blocks, WSF (Workstation Function) and OSF (Operations System Function), connected by a reference point 'f'. The WSF block contains four functional components: UISF (User Interface Support Function), SF (Security Function), MCF (Message Communications Function), and DAF (Directory Access Function). The OSF block contains five functional components: MCF (Message Communications Function), SF (Security Function), WSSF (Workstation Support Function), DSF (Directory System Function), and OSF-MAF (A/M) (Operations System Function – Management Application Function in manager or agent role). A legend at the bottom indicates that solid ovals represent 'required (for the f reference point)' and dashed ovals represent 'optional (for the f reference point)'. In the WSF block, UISF, SF, and MCF are solid ovals, while DAF is a dashed oval. In the OSF block, MCF, SF, and WSSF are solid ovals, while DSF and OSF-MAF (A/M) are dashed ovals. The reference point 'f' is marked with a solid dot on the line connecting the two blocks.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Diagram of the f reference point within the TMN functional architecture. It shows two main functional blocks, WSF (Workstation Function) and OSF (Operations System Function), connected by a reference point 'f'. The WSF block contains four functional components: UISF (User Interface Support Function), SF (Security Function), MCF (Message Communications Function), and DAF (Directory Access Function). The OSF block contains five functional components: MCF (Message Communications Function), SF (Security Function), WSSF (Workstation Support Function), DSF (Directory System Function), and OSF-MAF (A/M) (Operations System Function – Management Application Function in manager or agent role). A legend at the bottom indicates that solid ovals represent 'required (for the f reference point)' and dashed ovals represent 'optional (for the f reference point)'. In the WSF block, UISF, SF, and MCF are solid ovals, while DAF is a dashed oval. In the OSF block, MCF, SF, and WSSF are solid ovals, while DSF and OSF-MAF (A/M) are dashed ovals. The reference point 'f' is marked with a solid dot on the line connecting the two blocks. + +**Figure 2/M.3300 – f reference point within the TMN functional architecture** + +The functional components unique to the F interface are the Workstation Support Function (WSSF), provided in OSF to support the WS, and the User Interface Support Function (UISF), provided in WSF to support the User Interface (UI). The WSSF and the UISF exchange management information in support of their TMN function blocks. The WSSF within OSF provides support for the WSF by: + +- allowing data access, data manipulation; +- invocation and confirmation of actions; +- transmittal of notifications; +- hiding existence of Network Element Function(s) (NEFs), OSFs, MFs from WSF user communication with a specific OSF or MF; + +- provides administrative support for WSF and access for administering the OSF. + +The UISF within the WSF: + +- translates information held in an information model to a displayable format for the Human-Machine Interface (HMI) or User Interface (UI); +- translates user input to a form used for information models; +- is responsible for integrating information from one or more sessions with one or more OSs such that information is presented in a correct and consistent form at the UI; +- functions similar to MAFs may be provided; +- functions similar to ICFs may be provided. + +These WSSF and UISF functions impact F interface requirements as will be described in later subclauses of this Recommendation. As an example, the first three UISF functions enumerated above suggest the need for information structures within the WSF to allow the appropriate information to flow towards the user, appropriate information to flow towards the management system, and for management information to be retrievable in such a manner that its source is transparent to the user. See clause 10, Object management requirements, for requirements for such information structures. + +The DSF is a local or globally available distributed directory system, which may be in any function block except WSF. It contains some portion of the directory information base. The DAF may be found in all function blocks; it is used to access TMN information in directory information bases. This interaction between DAF and DSF must also take place over a physical interface between a WSF and an OSF in separate TMN physical blocks. See clause 13, Location transparencies requirements, for more details. + +There is an MCF associated with every function block with a physical interface. It generates application protocol messages, receives replies, receives events, matches up requests and replies, and knows the difference between a reply and an event. The implementation of the MCF is specific to the type of protocol exchanged over the interface. Communications across the F interface may be transaction-oriented or file transfer; the need for other communications styles is for further study. + +The SF may be found in both WSF and OSF. See clause 16, Security requirements, for more details. + +The WSF can be distributed such that different parts of the WSF can reside on different hardware. For example, detailed layout information (colours, pixels, etc.) can be sent to a terminal by a more powerful managing workstation. In this case the managing workstation acts as a "display client", issuing requests to update the display, and the terminal acts as a "display server" that responds to those requests. Examples of distributed WSF are provided in Appendix III/M.3010. + +### 7.3 TMN Physical architecture and the F interface + +The F interface is a physical interface that is manifested between two TMN physical blocks, i.e. a WS physical block containing a WSF and a TMN physical block containing at least one OSF. Note that if a physical block contains OSF as well as WSF, the physical block is not a WS, but an OS (or NE or MD). + +In Recommendation M.3010 a WS is defined as a terminal that has sufficient data storage, data processing, and interface support to translate the information between f and g reference points. The terminal provides the user with the capability to manipulate objects in a TMN Management Information Base (MIB), along with many other capabilities. + +A WS can access several OSs and an OS may serve several WSs. + +A WS communicates with another physical block (providing OSF) within a TMN. If a WS communicates with a TMN physical block it is by an F interface. This does not preclude a specific WS from participating in different TMNs in different instances of communications. + +A WS may use both transaction-oriented and file-transfer styles in communicating with other TMN physical blocks. Most communication between the WS and other blocks is transaction-oriented. + +Figure 3 illustrates the F interface physical architecture. (Note that the Q3 Interface is not shown.) + +![Diagram of the F interface physical architecture showing WS, OS, DCN, and NEa connected via F interfaces.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +The diagram illustrates the F interface physical architecture. At the top is a rectangular block labeled 'WS'. Below it is a vertical line connecting to a small circle labeled 'F'. This 'F' interface connects to a large oval labeled 'DCN'. To the left of the 'DCN' oval is another rectangular block labeled 'OS', connected to the oval by a horizontal line with a small circle labeled 'F'. Below the 'DCN' oval is another vertical line connecting to a small circle labeled 'F'. This 'F' interface connects to a rectangular block labeled 'NEa)'. To the right of the 'NEa)' block is the text 'T0408840-98/d03'. + +Diagram of the F interface physical architecture showing WS, OS, DCN, and NEa connected via F interfaces. + +a) An NE may communicate with a WS over an F interface, if the NE contains OSF. + +**Figure 3/M.3300 – F interface within the TMN physical architecture** + +### 7.4 TMN information architecture and the F interface + +There is management information exposed on the F interface by the OS and there may be, in some cases, management information exposed on the F interface by the WS. The latter is for further study. + +This Recommendation will discuss manager/agent requirements on the WS and OS sides of the F interface. Manager/agent terminology is used in the discussion of Network and Systems Management. Managers make requests for operations of agents, and receive notifications from agents. + +In this Recommendation, the term Management Information Base (MIB) is used to represent the visible management information exposed on the F interface by an agent. Management information and its representation in the WS or in the OS may be involved in exchanges over other interfaces or reference points. These uses are beyond the scope of this Recommendation. + +The OS predominantly assumes an agent role, and the WS predominantly assumes the manager role, at the F interface. The system assuming the agent role at the F interface makes a MIB visible at the F interface. The system assuming the manager role at the F interface presents requests to the agent and receives notifications from the agent. + +The information entities relevant at the F interface are discussed in clause 10, and illustrated in Figure 4. + +### 7.5 F interface/f reference point and the g reference point + +The g reference point represents an information exchange between a WS and a human user at the UI. It is outside the TMN. The g reference point conveys a translation of the information in a form that can be delivered to the user, and also brings input from the user. Layout of the data, colour, fonts, pictures, graphs, lists, etc, as UI objects are important. Also, + +providing different representations of the same data based on user's requests is important. + +Standardizing and optimizing the presentation of data to users is dependent on a multitude of parameters where each parameter can take on different values depending on the current situations. Some of the parameters involved are: UI software packages, Workstation hardware, user task requirements, user preferences, user training/expertise (in the task and also with the UI), user multitasking, software and hardware costs, etc. Therefore, it is not feasible to fully standardize the information exchange over the g reference point. + +In contrast, the data involved in the management information exchange at the F interface is still at an internal representation level (not in human-usable form), being exchanged between an OS and a WS. The requirements for this internal representation level may be standardized and possibly the mechanisms of exchanging data in this internal representation between physical blocks may be standardized as well. + +Language, character sets, culturally defined conventions, dynamic switching between languages/cultural conventions, turn-of-the-century dates and formats are all seen as important activities within the UI of a system. All of these information transformations will occur over the g reference point. The internal representation of data will be impacted only by requirements necessary to maintain that data in the most efficient manner. Converting that data to multiple display representations is most efficiently done in the UI of the WS and involves the g reference point. + +### 7.6 Summary of architectural implications for requirements + +The information on the F interface is object-oriented. The OSF, and the F interface, do not know what kind of user interface is used; it may be graphical, menu-based, command-line, etc. Therefore the information at the F interface is not the detailed specification of layout, colour, pixels, etc. provided by some graphical windowing capabilities. (The role of such a detailed presentation specification in the TMN architecture is described in *Distributed Workstation Function* in 6.8/M.3010 and III.1.3/M.3010.) + +The F interface must allow the WS to access and manipulate data, issue commands and receive confirmation, receive notifications, access location transparency services, etc. (See lists in subclause 7.2, TMN functional architecture and the F interface.) + +The F interface must support distinct associations between a workstation and one or more physical blocks containing OSF in one or more TMNs, and between a physical block containing OSF and one or more workstations. + +## 8 TMN user's requirements impacting the F interface + +Recommendation M.3020 defines a TMN user as "that which requires the TMN management services in support of its activities. It may be a human user applying for the use of services via some human-machine communication or it may be some computer-based organizational system requiring the capabilities of the TMN". For the purposes of this Recommendation, the TMN user is a human user. The requirements in this clause are based on the human users' needs which need to be supported via the F interface. + +The TMN user exerts control over processes in the TMN; feedback must also be provided indicating the results/status. The functions required by the TMN user must be available at the workstation. But not all TMN tasks require the involvement of a human user. The F interface is not used in cases where there is no need for interaction between a human user and an OS. + +In addition, work centre consolidation and re-engineering issues will significantly affect the F interface, since the sources of network management functionality will vary and content of network management functionality will vary. It is not productive to rebuild user interfaces to OSs with every work centre consolidation or re-engineering. It is also not productive to have human users interacting with multiple user interfaces either on separate workstations or on the same workstation. + +Hence, it is desirable to present the TMN user with allowable services which the TMN user requests over an external interface. This permits modularization of OSs providing those services. Modification of the services can also be provided without a need to change the TMN user's UI software. + +The TMN user's interests as a manager are embodied in the WS. The services that the TMN user requests will be those necessary to perform the tasks for which the TMN user is responsible. + +### 8.1 General requirements + +The TMN user needs a mechanism to generate a view of the physical and logical resources upon which the TMN user will make requests for services to be provided by those resources. The TMN user shall be able to request a view of the resources of interest on the WS. + +The TMN user shall be able to request a view of resources that are physically or logically contained within a selected resource currently represented on the workstation (zoom function). + +The TMN user shall be able to request the view of resources which have an explicit relationship with a resource currently represented on the workstation (e.g. retrieve resources that are explicitly supporting the represented resource). + +The WS must allow the TMN user to set up at least one association with an OS. Some WSs may also support the ability to set up associations with more than one OS. Each of these associations is an F interface instance. + +The TMN user shall be able to initiate and terminate an F interface instance. + +The TMN user must be able to send a request for an operation, and to receive a response, across the F interface. + +The TMN user must be able to receive event notifications (e.g. state changes) from the OS. The OS must be able to make event notifications available to the WS. + +The TMN user needs to be able to request notification if certain events occur, e.g. creation of new objects that fit a certain pattern, alarms, state changes, etc. + +The TMN user must be able to control the event notification mechanisms residing in the OS. + +The TMN user needs a set of scheduling services to manage activities such as generating reports and testing activities. Scheduling services should minimally include creating, displaying, modifying, listing, and cancelling schedules or schedule entries. + +The TMN user needs the ability to define and control the delivery of various reports. Report services should minimally include creating, displaying, modifying, listing, and deleting reports. Controlling the delivery of reports may be handled by scheduling services. + +WS and OS Administration requirements are for further study. + +The TMN user needs access to help facilities and on-line documentation. Whether this is a capability that crosses or impacts the F interface, or instead is more like access to screen definitions (which is not typical "management information" but may be a WS Administration issue), requires further study. + +The WS may have capabilities that allow it to directly access the emergency action capabilities built into NEs. This capability is not necessarily within the scope of the F interface. + +### 8.2 Task-related user requirements + +There is a need to minimize management reaction times to network events; therefore, information needs to flow over the F interface in both directions most efficiently. This impacts event notification requirements, message transfer requirements, etc. + +There is a need to minimize management traffic load on the telecommunications network. + +There is a need to allow distribution of control over the network and control over portions of the network. Note, for example: + +- Users can be in different geographical locations. + +- Different users can be controlling different geographical portions of the network, or different technologies/services of the network, or applying different management functions to the network or portions thereof. +- Different users may also need to control the same set of resources. + +There is a need to be able to locate and contain network faults. + +There is a need to improve service assistance and interaction with customers. + +There is a need to allow management of heterogeneous networks, equipment, and services. + +Any TMN user may need access to any TMN management service for any TMN managed area. To execute these TMN management services, the TMN user will need to invoke TMN management functions as defined in Recommendation M.3400. + +The UI software may use higher-level functions representing aggregations or sequences of TMN management functions, or may use TMN management functions directly. This does not imply that any single implementation of a TMN F interface must support all services and functions, but the F interface definition must encompass all such access. + +## 9 Initialization requirements + +At initiation of each instance of communication over the F interface, there may be an initial exchange of SMK (see Recommendation X.701). The ongoing exchange of SMK over the F interface is dynamic rather than static. + +Associations must be established and terminated in real time and at the direction of the user. + +## 10 Object management requirements + +As noted in Recommendation M.3010, the information flowing across the F interface is object-oriented. There are Managed Objects (MOs) in the TMN that represent resources. These MOs themselves may be represented in the WS by additional objects which are referred to in this Recommendation as *User-Management Objects (UMOs)*. The UMOs, along with support objects in the WS, are *Workstation objects (WOs)*; objects in the WS that have F interface interactions). Wos: communicate with MOs by operation invocations/responses sent/received over the F interface. + +WOs, which may be thought of as application objects in the WS, are not subject to standardization. A WO may support multiple interfaces. The interface between the WOs and objects in the OS is subject to standardization. All other WO interfaces are not subject to TMN standardization. + +The human user of the TMN, at the WS, interacts with a UI which may be graphical or character-based. The UI software interacts with WOs, translating user inputs to the WOs and translating WOs' information to a displayable form for the human user. WOs in turn interact across the F interface with the MOs in one or more physical blocks. + +The concept of WOs in the WS must not require extensive information modelling comparable to that which has already been done for the Q3 interface. The WS must understand the information that already exists elsewhere in the TMN (in the OS). Therefore the critical definition is how the WOs relate to, how they are derived from, and how they create, MOs in the managed systems in the TMN. + +The nature of the UMOs is critical to understanding the F interface requirements. From the point of view of the TMN user, they are managed objects (that is, they are managed by the UI software). From the point of view of the f reference point, they are managers (or manager-side objects). From the latter point of view, these are a new kind of object for the TMN, although objects that can both make requests and fulfil requests are in widespread use in other IT domains. + +The factors that differentiate between UMOs and MOs, including their respective attributes and especially behaviours, as well as cardinality, are discussed in the following subclauses. + +### 10.1 Relationships between WOs and MOs + +![A complex diagram showing object relationships between WS, OS, and NE layers. The WS layer contains Cache control, UMO-SO, UMO-TT, and UMO-ME. The OS layer contains Sev. Order, Troub. Ticket, and Work Order. The NE layer contains ME, EFD, EH, LOG, TTP, CP, and LR. Relationships are shown via solid and dashed lines, with labels like 'Primary Management Relationship' and 'Additional Management Relationship'. A UI-API is shown at the top of the WS layer.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +The diagram illustrates the object relationships between three layers: WS (Work Station), OS (Operating System), and NE (Network Element). + +- WS (Work Station) Layer:** + - Contains a UI-API at the top with a message box: "This is your work list for today. Have a nice day." + - Below the UI-API, there are four objects: Cache control, UMO-SO, UMO-TT, and UMO-ME. + - Cache control is connected to UMO-SO by a dashed line. + - UMO-SO, UMO-TT, and UMO-ME are connected to each other by dashed lines. + - UMO-SO, UMO-TT, and UMO-ME are connected to the UI-API by dashed lines. +- OS (Operating System) Layer:** + - Contains three objects: Sev. Order, Troub. Ticket, and Work Order. + - Sev. Order, Troub. Ticket, and Work Order are connected to a central Manager Process (represented by an oval) by dashed lines. +- NE (Network Element) Layer:** + - There are two sub-diagrams for the NE layer. The left one is labeled "NE" and the right one is labeled "NE with OSF". + - Both sub-diagrams show the same internal structure: + - ME is at the top, receiving arrows from EFD, EH, and LOG. + - TTP, CP, and LR are at the bottom. TTP and CP are connected by a double-headed arrow labeled "affected" and "supported by". + - EH is connected to CP by an arrow. + - LOG is connected to LR by an arrow. +- Inter-layer Relationships:** + - A solid line labeled "Primary Management Relationship" connects UMO-SO (WS) to Sev. Order (OS). + - A solid line labeled "Primary Management Relationship" connects UMO-TT (WS) to Troub. Ticket (OS). + - A solid line labeled "Additional Management Relationship" connects UMO-TT (WS) to Work Order (OS). + - A long solid line labeled "Primary Management Relationship" connects UMO-ME (WS) to ME (NE). + - Dashed lines connect the Manager Process (OS) to ME (NE) in both sub-diagrams. + +A complex diagram showing object relationships between WS, OS, and NE layers. The WS layer contains Cache control, UMO-SO, UMO-TT, and UMO-ME. The OS layer contains Sev. Order, Troub. Ticket, and Work Order. The NE layer contains ME, EFD, EH, LOG, TTP, CP, and LR. Relationships are shown via solid and dashed lines, with labels like 'Primary Management Relationship' and 'Additional Management Relationship'. A UI-API is shown at the top of the WS layer. + +T0408850-98/d04 + +Figure 4/M.3300 – Object relationships between WS, OS and NE + +Figure 4 illustrates a typical UI screen, interacting with some typical WOs in the WS, which interact with some common MOs in an OS and an NE; a manager process in the OS also interacts with MOs in the NE. Several of the possible relationships among these object types are shown. + +In Figure 4, the light or dashed lines are for clarification only; they are outside the scope of the F interface requirements. The heavy lines represent interactions over the F interface. + +The labels in Figure 4 are interpreted as follows: + +In WS: + +UI-API: the Application Programming Interface between UI software and the WOs. + +Cache control: an object or process that controls caching behaviour (see below). + +UMO-SO: a manager UMO representing a Service Order object in the OS. + +UMO-TT: a manager UMO representing a Trouble Ticket object in the OS. + +UMO-ME: a manager UMO representing a Managed Element object in the NE. + +In OS: + +Service Order: an agent MO representing a Service Order. + +Trouble Ticket: an agent MO representing a Trouble Ticket. + +Work Order: an agent MO representing a Work Order. + +Manager process: a process in the OS that acts as manager to Agent MOs in the NE. + +In NE: + +ME: an agent MO representing a Managed Element resource. + +EFD: an agent MO providing an Event Forwarding Discriminator. + +TTP: an agent MO representing a Trail Termination Point resource. + +EH: an agent MO representing an Equipment Holder. + +CP: an agent MO representing a Circuit Pack resource. + +Log: an agent MO providing a Log. + +LR: an agent MO providing a Log Record. + +NOTE – Some UMOs have a one-to-one relationship with MOs. The UMOs may have all the same attributes as their MOs. UMOs may also have more or fewer or different attributes than their MOs, but this relationship requires further study. In the simplest case a UMO represents its corresponding MO with the same attributes. But often, to meet the needs of the human user and support the UI, UMOs will have different behaviours than their MOs. For example, an MO may represent a work order. A UMO represents the same work order, but may include a behaviour that "reloads" or refreshes the information, either on-demand (requested by the user at the UI) or autonomously after the information has reached a specified "age" in the WS. + +Some UMOs will not have a one-to-one relationship with MOs. For example, one UMO might represent all the MOs that meet a certain criteria, such as "all the switches in Kansas City". A UMO must have a means of identifying which MO(s) it represents. + +#### 10.1.1 UMO/MO cardinality + +Some possible cardinalities of UMOs and their related MOs are shown in Figure 5. + +In the One-to-One illustration in Figure 5, the UMO and MO are one-to-one. This may be the most common case where UMOs are used. This relationship is shown in Figure 4 between the SO-UMO and the SO-MO. + +In the One-to-Many Primary/Secondary illustration in Figure 5, one UMO maps to many MOs. In this case the UMO is most directly related to, and representative of, one of the MOs. In Figure 4, this is illustrated by the Trouble Ticket UMO's relationship to the Trouble Ticket MO. The TT-UMO might be created by the user, and cause the TT-MO to be created; or if the TT-MO is created by some other agency it might cause the TT-UMO to be created, or the UMO might be created by a user's request to view a Trouble Ticket. The TT-UMO is also related to another MO. In Figure 4 this is + +illustrated by the TT- UMO's relationship to the Work Order MO. If the user's creation of the TT-UMO caused the TT-MO to be created, the TT-UMO might also cause a corresponding Work Order MO to be created. The Work Order MO is not the primary relationship of the TT-UMO but a relationship does exist. + +![Figure 5/M.3300 – UMO/MO relationships. The diagram illustrates four types of relationships between UMOs and MOs: One-to-One, One-to-Many (Primary/Secondary), One-to-Many Grouping, and Many-to-One. It also includes illustrations for 'No UMO' and 'No MO'.](83852ec55d4802521a727926336bedab_img.jpg) + +The diagram illustrates various UMO/MO relationships: + +- One-to-One:** A single UMO is connected to a single MO. +- No UMO:** A single MO exists without a corresponding UMO. +- One-to-Many (Primary/Secondary):** A single UMO is connected to multiple MOs. One relationship is labeled 'Primary' and another 'Secondary'. +- No MO:** A single UMO exists without a corresponding MO. +- One-to-Many Grouping:** A single UMO is connected to a primary MO, which in turn contains other MOs via 'part of' relationships. The primary MO and its contained MOs are grouped within an oval. +- Many-to-One:** Multiple UMOs are connected to a single MO. + +T0408860-98/d05 + +Figure 5/M.3300 – UMO/MO relationships. The diagram illustrates four types of relationships between UMOs and MOs: One-to-One, One-to-Many (Primary/Secondary), One-to-Many Grouping, and Many-to-One. It also includes illustrations for 'No UMO' and 'No MO'. + +**Figure 5/M.3300 – UMO/MO relationships** + +In the One-to-Many Grouping illustration in Figure 5, again one UMO maps to many MOs. However, in this case the relationship is hierarchical: the UMO's primary relationship is to one particular MO, but encompasses other MOs contained by the primary MO. This is illustrated in Figure 4 by the relationship of the ME-UMO to the ME-MO (in an NE with OSF functionality). In this case, the ME-UMO may provide a view of other MOs (EH-MOs, CP-MOs, etc.) contained in the ME-MO. + +In the Many-to-One illustration in Figure 5, multiple UMOs map to a single MO. An obvious case of this situation is when multiple users, on independent WSs, have views of the same MO. However it may also occur within a single WS for design and implementation reasons (as discussed below). + +In the No-UMO illustration in Figure 5, an MO exists without any UMO being related to it. This may be the most common case with respect to MOs. At any given time, most of the MOs in a system need no representation in anyone's WS, and many MOs may never need a representation in a WS. + +In the No-MO illustration in Figure 5, a UMO exists without any corresponding MO. This occurs in the case of UMOs that do not correspond to MOs, but are needed to interact with other UMOs or other software in the WS or OS. Examples of these UMOs include test control objects, scheduling objects, and user access privilege objects. + +The decisions regarding the appropriate relationships, when multiple UMOs or single UMO-to-multiple-MOs or other options are needed, are design and implementation decisions. Important factors in this decision include: + +- the user tasks being supported; +- the structure of the MOs (the MIB) in the managed system. + +When the WS receives a notification of interest, one or more UMOs may be created or modified. In some cases, such as a state change notification regarding an alarm or element, the UMO could maintain a "handle" or pointer to additional relevant information (such as a detailed alarm report) because it is likely the human user will shortly request the additional information. Whether a handle is maintained permanently or for a specified time is a design issue that should be driven by the expected demand for the handle's target. + +### 10.2 Naming + +There must be methods to map between names present within the WS manager and resources that can be managed. + +There must be support for the introduction of objects associated with new versions of software. + +The WS must support functionality that allows access to the MOs that are represented by UMOs. + +Names must be appropriate for use by automated equipment/systems. + +### 10.3 Retrieval services + +The manager role can request of the agent role (which may require more than one interaction across the F interface): + +- all data on a named object instance; +- all data on object instances related to the named object instance on the basis of a well-formed query. Examples of such queries include: + - all data on next level of contained object instances of a named object instance (logical zoom or telescoping); + - all data on n levels of contained object instances of a named object instance (discovery). +- attribute(s) values of named object instance(s); +- a named object to perform a chosen operation from a set of revealed operations/behaviours retrieved with the data on the named object instance. + +The agent role responds to the manager role with at least one of the following: + +- the requested data; +- request failed message with reason; +- an acknowledgement of the request along with a status of the request (e.g. still working on it). + +### 10.4 Modification services + +The manager role can request of the agent role: + +- the named object's data be changed according to the manager's request. + +The agent role responds to the manager role: + +- Acknowledgement that the named object's data was changed accordingly + +This information could be used in the WS to maintain data integrity in its UMO: only upon receipt of this acknowledgement would the manager make the change in its representation of the management information (in its UMO). + +- Request failed message with reason + +This information could be used in the WS to maintain data integrity in its UMO: the manager would make no change in its representation of management information (in its UMO). + +### 10.5 Notification services + +The agent role communicates spontaneously with the manager role to report notifications of events, alarms, state changes, etc.: + +- Any changes in managed objects encompassed by the F interface instance that are registered with a notification service (e.g. an Event Forwarding Discriminator (EFD), in the OSI systems management paradigm) associated with the F interface instance. + +Requirements for manager acknowledgement of receipt of the notification are for further study. + +### 10.6 Create services + +There are two categories of create services. + +In the first case the creation of objects (MOs) is requested by the manager. + +The manager role can request of the agent role: + +- to create managed object(s) with the appropriate attributes. + +The agent role responds to the manager role, either: + +- acknowledgement that the object was created with the appropriate attributes; +- request failed message with reason. + +An example of the first case will occur if the user requests the creation of logical objects to implement service for a customer over existing physical resources in the network being managed. + +In the second case the creation of objects (MOs) has occurred in a managed system and the agent notifies the manager that the new objects (MOs) have been created. + +The agent role communicates asynchronously to the manager role (if the manager has previously indicated a desire to receive these notifications that meet certain criteria): + +- notifications that a new object has been created. + +The manager role responds to the agent role, either: + +- requests retrieval services on the new object(s) for the purpose of creating a UMO; +- makes note of the existence of the new object so that retrieval can be requested at a later time if needed. + +An example of the second case will occur if a new circuit pack is put into service. A notification is sent over the appropriate F interface, if the manager role has requested notifications of new resources being made available that match whatever criteria the manager has specified, such as the identity and status of equipment within some geographical area. The agent is obligated to inform the manager only of the existence of the new object; the manager will determine what to do with the information. + +NOTE – There is an additional create service that needs to be mentioned, where the user requests the creation of a UMO which will not in turn cause a request for the creation of an MO over the F interface. The UMO may be created to facilitate display purposes, to enable the storage of object relationship data, or to represent attributes and functionality of support resources needed within the workstation e.g. timers, schedulers, etc. These UMOs may certainly make requests to MOs over the F interface. How the UMOs are created is not subject to standardization at the F interface. + +### 10.7 Destruction services + +As with creation, destruction services can be initiated on either side of the F interface depending on different circumstances. + +In the first case, the manager role requests destruction of MO(s). + +The agent role responds to the manager role, either: + +- acknowledgement that the object was destroyed. The manager may await receipt of this acknowledgement before updating its representation of the management information (destroy the corresponding UMO). +- request failed message with reason. Manager makes no change in its representation of management information (UMO not destroyed). + +In the second case, the agent role communicates asynchronously to the manager role notifications that an object(s) has been destroyed, with reason if provided. + +The manager role may respond by destroying the corresponding UMO(s) if they exist. + +Destruction of MOs and the UMOs representing them involves destroying all subordinate objects, cancelling event notifications; all other references to objects in models are deleted. + +NOTE – There is another case where UMOs are destroyed at the request of the user, but there is no request made of the agent over the F interface. The user may delete the UMO(s) if the user has no more need of a management view of the objects at the current time. The user requests closing that view of resources. The resources continue to exist and may be viewed by other users currently or by the same user at some future time. How the deletion is accomplished is not subject to standardization at the F interface. + +## 11 Shared Management Knowledge requirements + +### 11.1 Roles + +The possible relationships between WS and a TMN physical block containing OSF are manager and agent. The roles may reverse between WS and OS depending on task. + +One manager may be involved in information exchange with more than one agent. A separate manager role for each information exchange is needed. A TMN system may play the manager role to many systems seeing as many different information models; therefore, coordination and access issues are critical. + +One agent may be involved in information exchange with more than one manager. A separate agent role for each information exchange is needed. A system in a TMN may play an agent role to many systems presenting different information models to each; therefore, coordination and access issues are critical. + +An F interface instance must have a unique manager role and a unique agent role associated with it. + +Shared Management Knowledge must exist between a manager role and an agent role. + +The shared management knowledge can consist only of the functional view of objects present in the agent system which are visible over the interface and thus are visible to the managing system. + +### 11.2 Establishment of Shared Management Knowledge + +Shared Management Knowledge can be established and updated for an interface at the following times: + +- prior to communication (system design or build time, or remembered from a previous association); +- during the interface instantiation phase; +- during the lifetime of the interface instance (discovery). + +Prior to communication: Examples of shared management knowledge that can be present before the initialization of an F interface instance include: + +- WO and/or MO version of support object classes (e.g. timers, schedulers, test control objects, etc.) may exist as templates; +- MIB schema information (e.g. class templates, relationships between object classes); +- support information (e.g. addressing/location information). + +During the interface initialization phase: for example, UMOs within the manager role in the WS may be created representing resources or abstractions of resources or data/information synthesis objects within the agent role. + +During the lifetime of the interface instance (discovery): + +- requests by the manager role – initially by location transparency services or by retrieval of a containment hierarchy; +- events passed asynchronously to the manager role by the agent role. + +Manipulating these UMOs will cause activity over the F interface so that the appropriate activity will occur on MOs, if it is allowed, based on access permissions. + +Location transparency services (see clause 13) will allow for additional SMK to be obtained from the agent role over the life of the F interface instance. + +## 12 Event registration/notification requirements + +Event notification services must be provided by the F interface protocols to allow asynchronous communications between managed resources found in the MIB of the agent role and the corresponding manager role. Event notification services are a major mechanism in managing data consistency between different TMN physical blocks. + +### 12.1 Receiving event notifications + +Events will be passed to UMOs from MOs by some event distribution mechanism, if necessary, over the F interface if the UMO has been instantiated and is registered for/subscribed to the events. Examples of events include autonomous notification of configuration changes, state changes, and alarms. + +Once the UMO has been created in the WS, it continues to receive event notifications, if registered for them, until the UMO is destroyed (this destruction does not imply the destruction of the MO). Distribution of subscribed events may occur within the WS; the managed object triggering the event does not need to know what objects (UMOs or other MOs) are going to receive the events. + +### 12.2 Controlling event notification + +Control of event notification should be similar to the usage described in Recommendation X.734. + +UMOs must be available in the WS to manage event notification functions located in the agent. + +Management of event notification management functions involves the following: + +- begin, terminate, suspend, resume event forwarding; +- modify event forwarding conditions, retrieve event forwarding conditions; +- scheduling (on-duty/off-duty). + +## 13 Location transparencies requirements + +Since TMN architecture allows for distribution of TMN functions over multiple TMN physical blocks, it is necessary to provide mechanisms for locating essential information about network resources and their attributes. TMN systems need to know which other systems to associate with in order to accomplish their management functions. This information will need to flow between a WS and an OS via the F interface. These mechanisms need to provide: + +- Naming/Addressing Support: the capability to refer to managed resources by name rather than address, the ability to determine the TMN elements involved in the management subsystem, the ability to identify an NE based on specific attributes. + +- Association Resolution: determining the application entity title (or application binding handle) of an entity with which a management association may be established, presentation address of the entity, given a managed resource and the name of the management capability – being able to find the management agent that can provide the management functions. + +These services can be provided using a request/reply communications model. + +Some form of directory services will meet these needs. In this Recommendation, references to directory services (lower case) are generic and do not imply that X.500 Directory Services need to be employed. + +## 14 Data consistency requirements + +Over an F interface instance, the values of attributes in representations of the same resource (UMO versus MO) either physical or logical should be logically equivalent. Attribute synchronization is needed at the time of object creation, modification and destruction. Event notification requirements should handle some cases of modifications. + +In addition, audit functions are usually provided in systems where it is necessary to verify that inherited or related data are in synchronization. Further study is needed to define the appropriate audit requirements for the F interface. + +## 15 Quality, performance, and OA&M requirements + +The items discussed in this clause represent some areas that need to be considered in architecting an F interface. Some examples include: performance, reliability, robustness, throughput, transit delay, scalability, software failure, backup/restoration/recovery, time stamping, dynamic software upgrades, other WS software management. It is not clear at this time whether any or all of these items will be requirements on the F interface. + +### 15.1 Initialization performance + +It is an objective that the initialization of SMK should occur within one minute. + +### 15.2 Message transfer + +The following items may affect F interface message transfer. + +- Frequency – how often data is transferred across the interface boundary; +- Quantity – amount of data that is transferred over the interface at a given time; +- Throughput – how many simultaneous requests/responses can be handled; +- Transit delay – how long does it take for a user request to occur; determine buffering that may be tolerable; +- Accurate time stamping – time stamps should be accurate within five (5) seconds. + +Data that is defined by application requirements (by human factors/ergonomics requirements, systems engineers, etc.) to require "immediate" availability, such as alarms in a critical monitoring situation, should have a latency (delay after occurrence in the agent) of no more than ten (10) seconds. + +All data that is currently being "viewed" on the WS (whether a window is open or iconified; that is, when a UMO is alive and responsible for the user's access to that data) should have a latency (delay after its occurrence in the agent) of no more than one (1) minute. Note that a UI may indicate that data is "static" (i.e. a "snapshot") and give the user a means to refresh the data. + +### 15.3 Reliability, availability, survivability + +For further study. + +### 15.4 Software management + +For further study. + +### **15.5 Real-time message management** + +For further study. + +## **16 Security requirements** + +Security for the F interface is intra-TMN security. Physical equipment security, environmental threats and other security issues are not addressed. + +The following subclauses present partial lists of security requirements but more may be appropriate. + +### **16.1 User identification requirements** + +The TMN must provide a mechanism to uniquely identify all human users (user ID) within the TMN. + +The TMN user's user ID is linked to all the user's auditable actions for an audit trail. + +### **16.2 Authentication** + +Authentication services are necessary when initializing an F interface instance. + +Authentication information is accessible only by privileged users such as security administrators. + +During an authentication procedure no feedback other than valid or invalid will be provided over the F interface. + +Further study is needed to identify the type(s) of authentication mechanisms to employ. + +### **16.3 Access control** + +A TMN user cannot access any TMN physical block over the F interface unless the TMN user has been successfully identified and authenticated. + +Access control is the responsibility of the TMN physical block serving in the agent role. Note that the WS may act as the "agent" to the UI software. + +The TMN needs to provide access control to various classes of TMN users, where the class of TMN user is determined by the TMN user role. + +Access control of resources is needed at different levels of granularity. There should be control over access to an individual attribute or operation on a specific resource. + +### **16.4 Data integrity** + +The TMN must be able to reliably associate any communication over an interface with the origin of the communication. + +### **16.5 Privacy** + +The TMN must provide confidentiality of information communicated over the F interface. + +The TMN must support secure distribution of authentication material (e.g. keying material). + +### **16.6 Auditing** + +The TMN must provide capabilities to track potentially unauthorized user activities after their occurrence. These capabilities are usually provided by the generation of security logs and audit trail reports. + +## 17 Physical implementation requirements + +If an f reference point becomes an F interface, the physical implementation of the WSF shall not affect the F interface. (It could be a distributed client server architecture or there may be multiple F interfaces to a WS.) + +## 18 What's part of WSF but not part of the F interface + +The interaction between the WOs and the UI software is beyond the scope of the F interface and this Recommendation. + +Services to build relationships between WOs, that form part of the same F interface instance or form parts of different F interface instances, may be needed but are not the responsibility of the F interface. + +The F interface is not responsible for integrating the information from more than one session/association. + +The F interface requirements do not ensure that the user is accessing the correct set of managed objects (e.g. if one resource is affected, which results in an impact on another resource, will the object representing the affected resource appear on the user's screen?) + +There are no F interface requirements on the relationship or dependency between F interface instances terminating on the same WS. (e.g. the user could be performing tasks in two completely disjoint OSs or areas of the network: alarm surveillance on subnetwork A and traffic studies on subnetwork Z.) + +The user's view of objects and the user's desired interface to an object on the WS depends on the task context of the interaction between the user and the object. + +## Appendix I + +### Recommendation M.3300 (1992) + +This Recommendation has evolved in scope and content since the previous version was published. To aid the reader, a mapping from M.3300 (1992) to this revised version is provided. + +| Previous clause | Revised version | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 – Introduction | Introductory material is provided in a new clause, Introduction to the F interface. | +| 2 – Scope | Present in revised version | +| 3 – Functional architecture | TMN architecture is defined in Recommendation M.3010. For the convenience of the reader and to highlight some implications on requirements, it is summarized in a new clause F interface architecture. | +| 4 – Management capabilities | Discussed in a new clause, TMN user's requirements impacting the F interface. | +| 5 – Management services | Discussed in a new clause. TMN user's requirements impacting the F interface. | +| Annex A – Management capabilities | TMN capabilities supported by management functions are identified in Recommendation M.3400. In this revision, no attempt is made to describe all the M.3400 capabilities (> 200) as they are reflected at the F interface. | + +## Appendice II + +## Bibliography + +ITU-T Recommendation M.3020 (1995), *TMN interface specification methodology*. + +ITU-T Recommendation M.3400 (1997), *TMN management functions*. + +ITU-T Recommendation X.200 (1994), *Information technology – Open Systems Interconnection – Basic reference model: The basic model*. + +ITU-T Recommendation X.500 (1997), *Information technology – Open Systems Interconnection – The Directory: Overview of concepts, models and services*. + +ITU-T Recommendation X.701 (1997), *Information technology – Open Systems Interconnection – Systems management overview*. + +ITU-T Recommendation X.703 (1997), *Information technology – Open Distributed Management Architecture*. + +CCITT Recommendation X.734 (1992). *Information technology – Open Systems Interconnection – Systems Management: Event report management function*. + +## ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.3341-200312-I_PDF-E/raw.md b/marked/M/T-REC-M.3341-200312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9b247fc62dbbed4ed5c1f33ac24d57da18cde00b --- /dev/null +++ b/marked/M/T-REC-M.3341-200312-I_PDF-E/raw.md @@ -0,0 +1,753 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3341** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(12/2003) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Telecommunications management network + +--- + +**Requirements for QoS/SLA management over +the TMN X-interface for IP-based services** + +ITU-T Recommendation M.3341 + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3341** + +# **Requirements for QoS/SLA management over the TMN X-interface for IP-based services** + +## **Summary** + +This Recommendation addresses end-to-end Quality of Service (QoS) information collection, aggregation and exchange between Service Customers, Service Providers and Network Operators. In the context of this Recommendation, Service Providers (SPs) include Telecom SPs, Internet SPs, Application SPs and Content SPs. Service Customers include end-Customers and other SPs. Functions and interfaces required to ensure end-to-end QoS classes are specified for the complete service life cycle. + +## **Source** + +ITU-T Recommendation M.3341 was approved on 14 December 2003 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +End-to-end, IP, Management, Measurement Point, Network Operator, Observation, Quality of Service (QoS), Service Customer, Service Provider, X-interface. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|--------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Terms and definitions ..... | 2 | +| 4 Abbreviations and Acronyms ..... | 3 | +| 5 Service life cycle and QoS..... | 4 | +| 5.1 Service product planning and development ..... | 4 | +| 5.2 Negotiation and sales..... | 4 | +| 5.3 Implementation..... | 5 | +| 5.4 Execution..... | 5 | +| 5.5 Assessment ..... | 5 | +| 6 QoS classes and traffic types ..... | 5 | +| 7 QMS functional requirements ..... | 5 | +| 7.1 QMS framework..... | 5 | +| 7.2 Basic requirements ..... | 6 | +| 7.3 Business level requirements (use cases)..... | 8 | +| 7.4 Specification level requirements ..... | 10 | +| 8 Interface requirements ..... | 18 | +| Annex A – QMS management scenarios ..... | 19 | +| A.1 Implementation phase (service orders and provision)..... | 20 | +| A.2 Execution phase (monitor, surveillance) ..... | 20 | + + + +# **Requirements for QoS/SLA management over the TMN X-interface for IP-based services** + +# **1 Scope** + +This Recommendation addresses end-to-end quality of service (QoS) information collection, aggregation and exchange between service customers, service providers and network operators for IP-based services. In the context of this Recommendation, service providers (SPs) include telecom SPs, Internet SPs, application SPs and content SPs. Service customers include end-customers and other SPs. Functions and interfaces required to manage end-to-end QoS are specified for the complete service life cycle. This Recommendation provides requirements in the form of use cases and preliminary information related to the analysis phase. This Recommendation also recognizes the business need to manage QoS across multiple SPs. + +# **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation + +- [1] ITU-T Recommendation G.1010 (2001), *End-user multimedia QoS categories*. +- [2] ITU-T Recommendation M.1530 (1999), *Network maintenance information*. +- [3] ITU-T Recommendation M.1532 (2000), *Network maintenance service performance agreement (MSPA)*. +- [4] ITU-T Recommendation M.1535 (1996), *Principles for maintenance information to be exchanged at customer contact point (MICC)*. +- [5] ITU-T Recommendation M.1537 (1997), *Definition of maintenance information to be exchanged at customer contact point (MICC)*. +- [6] ITU-T Recommendation M.1539 (1999), *Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC)*. +- [7] ITU-T Recommendation M.2301 (2002), *Performance objectives and procedures for provisioning and maintenance of IP-based networks*. +- [8] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [9] ITU-T Recommendation M.3020 (2000), *TMN Interface Specification Methodology*. +- [10] ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: overview*. +- [11] ITU-T Recommendation M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*. +- [12] ITU-T Recommendation M.3350 (Draft) (2004), *TMN service management requirements for information interchange across the TMN X-interface to support provisioning of telecommunication capabilities for disaster relief operations and mitigation*. + +- [13] ITU-T Recommendation M.3400 (2000), *TMN management functions*. +- [14] ITU-T Recommendation Q.822 (1994), *Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management*. +- [15] ITU-T Recommendation X.730 (1992), *Information technology – Open Systems Interconnection – Systems Management: Object management function*. +- [16] ITU-T Recommendation Y.1001 (2000), *IP framework – A framework for convergence of telecommunications network and IP network technologies*. +- [17] ITU-T Recommendation Y.1221 (2002), *Traffic control and congestion control in IP-based networks*. +- [18] ITU-T Recommendation Y.1540 (2002), *Internet protocol data communication service – IP packet transfer and availability performance parameters*. +- [19] ITU-T Recommendation Y.1541 (2002), *Network performance objectives for IP-based services*. +- [20] TeleManagement Forum GB 917 (2001), *SLA Management Handbook – GB 917, Ver. 1.5*. +- [21] OMG Document formal/2003-03-01, *Unified Modeling Language (UML), Version 1.5*. + +# 3 Terms and definitions + +This Recommendation defines the following terms: + +**3.1 measurement point:** The physical or logical point at which measurements can be made and to which the data obtained is related, e.g., a measurement point in a network or a step in the business process dependant upon the service life cycle. In the implementation phase of the service life cycle, it could be the time that an order is received by the service provider. + +**3.2 observation:** An observation is used by the service customer to monitor the QoS of the telecommunication service provided to the SC by the SP. An observation is associated with exactly two measurement points. + +**3.3 end-to-end QoS:** The QoS service level metrics relevant to the service being delivered as perceived by the SC. + +![Diagram illustrating measurement points and observation in a network. The diagram shows a sequence of nodes: SC connected to NO, which is connected to TSP, which is connected to ISP, which is connected to another TSP, which is connected to another NO, which is connected to another SC. Measurement points (MP-a through MP-h) are indicated by dashed arrows pointing to the interfaces between nodes. An 'Observation' is indicated by a bracket spanning from MP-a to MP-h. A legend at the bottom left defines 'MP' as 'Measurement Point'.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +graph LR + SC1((SC)) <--> NO1((NO)) + NO1 <--> TSP1((TSP)) + TSP1 <--> ISP((ISP)) + ISP <--> TSP2((TSP)) + TSP2 <--> NO2((NO)) + NO2 <--> SC2((SC)) + + subgraph Observation + MP-a -.-> SC1_NO1[Interface] + MP-b -.-> NO1_TSP1[Interface] + MP-c -.-> TSP1_ISP[Interface] + MP-d -.-> ISP_TSP2[Interface] + MP-e -.-> ISP_TSP2[Interface] + MP-f -.-> TSP2_NO2[Interface] + MP-g -.-> NO2_SC2[Interface] + MP-h -.-> SC2_End[Interface] + end + +``` + +The diagram illustrates a network path consisting of several entities connected in series. From left to right, the entities are: SC (Service Customer), NO (Network Operator), TSP (Telecommunication Service Provider), ISP (Internet Service Provider), another TSP, another NO, and finally another SC. Double-headed arrows indicate bidirectional communication between adjacent entities. Below the chain of entities, dashed arrows point to the interfaces between them, labeled as Measurement Points: MP-a (between SC and NO), MP-b (between NO and TSP), MP-c (between TSP and ISP), MP-d and MP-e (at the ISP boundaries), MP-f (between ISP and TSP), MP-g (between TSP and NO), and MP-h (between NO and SC). A horizontal bracket labeled "Observation" spans the entire distance from MP-a to MP-h. A legend at the bottom left specifies "MP Measurement Point". The figure is identified as M.3341\_F3-1. + +Diagram illustrating measurement points and observation in a network. The diagram shows a sequence of nodes: SC connected to NO, which is connected to TSP, which is connected to ISP, which is connected to another TSP, which is connected to another NO, which is connected to another SC. Measurement points (MP-a through MP-h) are indicated by dashed arrows pointing to the interfaces between nodes. An 'Observation' is indicated by a bracket spanning from MP-a to MP-h. A legend at the bottom left defines 'MP' as 'Measurement Point'. + +**Figure 3-1/M.3341 – Measurement points and observation** + +Figure 3-1 shows an example of Measurement Points (MP) and an Observation (Ob) in a typical network. The Internet Service Provider (ISP) receives telecommunication services from two Telecommunication Service Providers (TSPs). + +Network Operators (NOs) define the Measurement Points (MPs) at each end of their responsible part of the network. They have responsibilities to observe their part of the network. MP-a and MP-b + +are defined at the ingress and egress of one NO's network. Likewise, MP-g and MP-h are defined at the ingress and egress of another NO's network. + +Each TSP receives services from two Network Operators (NOs). TSPs have responsibilities to observe their part of the networks, in Figure 3-1, spanning across two NO's networks. + +The ISP, which has a primary contract with the Service Customer (SC), has the responsibility to observe end-to-end QoS of the entire network, not merely a part of one TSP, and also has the responsibility to provide the observation data to SC. The SC is able to define an observation between the measurement points MP-a and MP-h. The observation provides QoS measurements from the ingress to the egress of the ISP's network regardless of the service providers or network operators involved. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| 3GPP | Third Generation Partnership Project | +| C | Customer | +| ID | Identifier | +| IP | Internet Protocol | +| ISP | Internet Service Provider | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| MP | Measurement Point | +| NO | Network Operator | +| NP | Network Performance | +| Ob | Observation | +| OMG | Object Management Group | +| P | Provider | +| PM | Performance Management | +| QMS | QoS/SLA Management Service | +| QoS | Quality of Service | +| QoSMS | QoS management in a multi-service provider environment | +| SC | Service Customer | +| SLA | Service Level Agreement | +| SP | Service Provider | +| TMF | TeleManagement Forum | +| TMN | Telecommunications management network | +| TSP | Telecommunication Service Provider | +| VoIP | Voice over IP | +| XML | eXtensible Markup Language | + +# 5 Service life cycle and QoS + +Management of QoS and associated SLAs require interaction between many telecom operations business processes and TMN management services as defined in ITU-T Rec. M.3200 and TMN management function sets as defined in ITU-T Rec. M.3400. In order to understand and analyse these interactions, there are at least five phases of the service life cycle that should be considered. These five phases are shown in Figure 5-1: + +- Service product planning and development; +- Negotiation and sales of a service product; +- Implementation (configuration, provisioning and commissioning) of a service product; +- Operation and maintenance of a service product; +- Periodic assessment of the QoS of a service and whether it meets the SLA. + +![Figure 5-1/M.3341 – Service life cycle (Figure 5-1/GB917). A flow diagram showing five sequential phases: Product/service development, Negotiation and sales, Implementation, Execution, and Assessment. Each phase is represented by a colored box with a right-pointing arrow. Below each box is a description of the activity. A large blue arrow at the bottom points from left to right, indicating the flow of the life cycle.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` +graph LR; A[Product/service development] --> B[Negotiation and sales]; B --> C[Implementation]; C --> D[Execution]; D --> E[Assessment]; A --- A_desc[Develop templates and parametric boundaries]; B --- B_desc[Negotiate individual contracts]; C --- C_desc[Take line/service orders and provision]; D --- D_desc[Monitor, surveillance, maintain, bill]; E --- E_desc[Reassess]; +``` + +The diagram illustrates the service life cycle as a five-step process. The steps are: 1. Product/service development (Develop templates and parametric boundaries), 2. Negotiation and sales (Negotiate individual contracts), 3. Implementation (Take line/service orders and provision), 4. Execution (Monitor, surveillance, maintain, bill), and 5. Assessment (Reassess). The steps are connected by arrows, and a large blue arrow at the bottom indicates the overall flow from left to right. The label M.3341\_F5-1 is present in the bottom right corner of the diagram. + +Figure 5-1/M.3341 – Service life cycle (Figure 5-1/GB917). A flow diagram showing five sequential phases: Product/service development, Negotiation and sales, Implementation, Execution, and Assessment. Each phase is represented by a colored box with a right-pointing arrow. Below each box is a description of the activity. A large blue arrow at the bottom points from left to right, indicating the flow of the life cycle. + +**Figure 5-1/M.3341 – Service life cycle (Figure 5-1/GB917)** + +The following subclauses describe those aspects of each phase related to QoS and SLA management across the X-interface between two TMN domains, but not all of the aspects involved in each phase within a single TMN domain. Furthermore, in some cases e.g., leased circuit services, the negotiation and sales phase is sometimes split into two phases: pre-ordering and ordering. Descriptions of these five phases are described in detail in GB 917. + +## 5.1 Service product planning and development + +When planning and developing a service product, consideration must be given to a number of QoS and SLA aspects. In addition to the generic parameters there are technology-specific parameters. For example, in the case of IP-based services, these parameters and limits should be based on ITU-T Recs Y.1540, Y.1541 and M.2301. These Recommendations define QoS classes and the Network Performance (NP) parameters and limits designed to support certain applications e.g., VoIP, streaming video, etc. However, if the service is a pure packet delivery service, the QoS parameters and limits will be the same as the NP. Further information is given in 6. + +## 5.2 Negotiation and sales + +During this phase, the service provider must negotiate and agree with the customer technical details of specific instances of the service product offered. The QoS parameters and limits may be the same as those offered in the standard template or customized to a specific service instance. The format of conveying this information across the X-interface is outside the scope of this Recommendation, but it may well be XML in the case of eCommerce. However, the content should be defined according to the QoS parameters and limits specified in ITU-T Recommendations. + +## 5.3 Implementation + +Service implementation is the phase when the service is configured, activated (commissioned or brought into service) and operation begins. Detailed descriptions of the procedures for the "bringing into service" are contained in ITU-T Recs M.1530, M.1532, M.1535, M.1537, and M.1539. Many of these functions may be implemented via TMN management function sets defined in ITU-T Rec. M.3400 and procedures and performance limits defined in the M.2xxx-series Recommendations. + +## 5.4 Execution + +This phase covers all normal operations of the services and service instances covered by the SLA. This includes normal in-service monitoring and operation, real-time QoS reporting and service quality validation, and real-time SLA violation handling. The emphasis on real-time is deliberate because increasingly, the customer requires continuous monitoring, reporting and guarantees of QoS offered, especially in an eCommerce environment. Many ITU-T Recommendations in the M.2xxx-series and M.3xxx-series Recommendations cover the functions and procedures to be used in this phase. + +## 5.5 Assessment + +Assessment of QoS and SLA is scheduled during a single customer SLA contract period where the assessment is related to the delivered QoS against the SLA parameter values and limits, and the levels of customer satisfaction with the service product. This may include potential service improvement with possibly increased charges depending on market pricing, as well as responding to changing customer requirements. The QMS is relevant to this part of the assessment phase. + +The second time-frame is related more to the service provider's internal overall quality goals, objectives and risk management and is considered out of the scope of this Recommendation. + +# 6 QoS classes and traffic types + +It is important to note that there is a distinct difference between the user/service QoS requirements defined in the SLA, and the network-level QoS/NP and QoS-enabling mechanisms. As mentioned in 5.1, QoS classes and the Network Performance (NP) parameters and limits designed to support certain applications e.g., VoIP, streaming video etc., are defined by ITU-T Rec. Y.1541. Table 2/Y.1541 provides the mapping between QoS classes and traffic types (i.e., applications). Additional information may be found in ITU-T Rec. G.1010. GB 917 section 4.1.4 (NP/QoS Requirements and QoS Classes) gives additional explanation of the relationship between NP and QoS. + +# 7 QMS functional requirements + +## 7.1 QMS framework + +An SP provides a telecommunication service1 to an SC. An SLA is an agreement by the SP to provide a particular QoS (in terms of measurable parameters) to the SC pertaining to this telecommunication service. The QMS provides the SC with a flexible approach to monitoring (i.e., observing) the QoS associated with this telecommunication service on a continuous basis. QMS interactions occur over the TMN X-interface as shown on Figure 7-1. + +--- + +1 The term "telecommunication service" is used throughout this clause in order to make a distinction from the "management service", however, the concepts portrayed in this clause are also applicable to other types of "services" that an SP might sell, i.e., those that may be provided by Internet SPs, Application SPs, and Content SPs. + +![Figure 7-1/M.3341 – Reference interface diagram showing three stacked boxes: Service customer operations system, QoS/SLA service management system, and Network management system. The interface between the top two boxes is labeled 'X'.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph TD + A[Service customer operations system] -- X --- B[QoS/SLA service management system] + B --- C[Network management system] + +``` + +M.3341\_F7-1 + +Figure 7-1/M.3341 – Reference interface diagram showing three stacked boxes: Service customer operations system, QoS/SLA service management system, and Network management system. The interface between the top two boxes is labeled 'X'. + +**Figure 7-1/M.3341 – Reference interface** + +Note that the performance management functions found in ITU-T Rec. Q.822, are foundational to QMS. Many of the Q.822 concepts and detailed descriptions can be applied to QMS for the X-interface. + +## 7.2 Basic requirements + +The SP provides MPs from which the SC constructs Obs. Obs are used by the SC to monitor the QoS associated with the telecommunication service provided to the SC by the SP. At a minimum, MPs will be provided at the telecommunication service ingress and egress points. The SP may also choose to provide MPs at points intermediate to these as well. Each MP will have a fixed set of measurable PM parameters associated with it. When the SC constructs an Ob, the PM parameters that can be monitored via the Ob are those that are common to the MPs that are used to construct the Ob. + +In terms of the performance management model found in ITU-T Rec. Q.822, the QMS Ob is considered to be a "monitored object" as shown on Figure 7-2. In this way, the detailed performance management functions and descriptions found in ITU-T Rec. Q.822 may be directly applied to the QMS X-interface. + +![Figure 7-2/M.3341 – Naming hierarchy diagram showing a hierarchy of objects. Monitored object is at the top, with arrows pointing to it from currentData and historyData. currentData is in the middle, with arrows pointing to it from historyData and thresholdData. Managed element is at the top right, with an arrow pointing to it from thresholdData.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +graph TD + MO[Monitored object] + CD[currentData] + HD[historyData] + TD[thresholdData] + ME[Managed element] + + HD --> MO + CD --> MO + HD --> CD + TD --> CD + TD --> ME + +``` + +M.3341\_F7-2 + +Figure 7-2/M.3341 – Naming hierarchy diagram showing a hierarchy of objects. Monitored object is at the top, with arrows pointing to it from currentData and historyData. currentData is in the middle, with arrows pointing to it from historyData and thresholdData. Managed element is at the top right, with an arrow pointing to it from thresholdData. + +**Figure 7-2/M.3341 – Naming hierarchy (Figure 3/Q.822)2** + +2 The arrow between currentData and thresholdData is a defect in ITU-T Rec. Q.822 and should be removed. The thresholdDataId attribute within the currentData object is used to identify the relationship between the thresholdData object and currentData object. + +### 7.2.1 Management interactions + +Table 7-1 lists service management interactions that could be converted across the QMS interface between SCs and SPs. This is the TMN X-interface for service management as defined by M.3010. Those interactions that are defined in ITU-T Rec. Q.822 and are being applied to QMS at the X-interface are depicted using ***Bold Italic*** font. + +**Table 7-1/M.3341 – QoS/SLA management interactions across QMS interface** + +| Initiator | QoS/SLA management interactions | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Customer | Retrieve MPs
Retrieve Obs
Configure Ob (Note 1)
Assign PM data collection interval (Note 2)
Suspend/Resume PM data collection (Note 1)
Reset PM data (Note 1)
Assign PM history duration (Notes 1 and 2)
Assign PM threshold (including severity) (Notes 1 and 2)
Request PM data (current or history) | +| Service Provider | Report MP configuration changes
Report SP suspension of PM data collection
Report PM threshold violation | + +NOTE 1 – It is assumed that this action would be confirmed by the SP either via a response to the requested action or through the issuance of a report that the action took place. Since the original initiator of the action is the SC via its request, the potential issuance of a corresponding report by the SP is not listed separately as a "SP-initiated" interaction. + +NOTE 2 – Although not explicitly called out as separate functions in ITU-T Rec. Q.822, the ability to retrieve, i.e., "get" any of these data items (in addition to assigning, i.e., "setting" them) is implicitly supported within the Q.822 performance management model. + +### 7.2.2 Interactions initiated by service customer + +The following provides a narrative description of requests initiated by the SC and sent across the X-interface to the SP for action: + +- Retrieve MPs** – The SC queries the SP to find out what MPs are being provided corresponding to the telecommunication service that is being provided to the SC. The SC may also query for the detailed attribute values associated with a specific MP. +- Retrieve Obs** – The SC queries the SP to find out what Obs currently exist corresponding to the telecommunication service that is being provided to the SC. The SC may also query for the detailed attribute values associated with a specific Ob. +- Configure Ob** – The SC may create a new Ob or delete an existing Ob. In order to account for the case where the SC may want to cancel the creation of a new Ob, it is suggested that Obs be created in a "suspended" state, i.e., the Ob object gets created but does not perform any functionality until the SC performs the "resume PM data collection" function. Therefore, if the SC decides that the Ob creation should have been cancelled, the SC may simply delete this Ob object while it is in the "suspended" state, which in effect "cancels" the original creation request. +- Assign PM data collection interval** – The SC instructs the SP about the duration of the PM data collection interval for a given Ob or set of Obs. This information (i.e., the duration of the PM data collection interval) may also be queried from the SP by the SC. + +- e) **Suspend/Resume PM data collection** – The SC instructs the SP to suspend/resume the performance monitoring data collection activity for a given Ob or set of Obs. +- f) **Reset PM data** – The SC instructs the SP to reset the performance monitoring counters for a given Ob or set of Obs. +- g) **Assign PM history duration** – The SC instructs the SP to establish the duration during which to maintain a specific record of PM historical data. This information (i.e., the duration which to maintain a specific record of PM historical data) may also be queried from the SP by the SC. +- h) **Assign PM threshold (including severity)** – The SC instructs the SP to establish the threshold criteria for PM data of a given Ob or set of Obs. Each threshold setting consists of the attribute identifier of the PM parameter, the threshold value and (optionally) the severity of the threshold-exceeding event. This information (i.e., the threshold criteria for PM data) may also be queried from the SP by the SC. +- i) **Request PM data (current or history)** – The SC issues a spontaneous request to the SP for current or historical PM data information on a given Ob or set of Obs. + +### 7.2.3 Management interactions initiated or provided by service provider + +The following provides a narrative description of reports provided by the SP based upon the administered schedule or triggers. The reports are sent by the SP across the X-interface to the SC: + +- a) **Report MP configuration changes** – If the SP makes a change to the MPs provided to the SC, then the SP would send a report to the SC to inform them of such a change. The reported change could be the addition of a new MP, the deletion of an existing MP, or a change in the PM parameters that can be monitored from the MP. +- b) **Report SP suspension of PM data collection** – In unusual circumstances (e.g., SP PM data collection system failure), it may be necessary for the SP to suspend PM data collection corresponding to an Ob that the SC has established without obtaining permission from the SC to do so. If the SP suspends PM data collection, then the SP would send a report to the SC to inform them of this event. +- c) **Report PM threshold violation** – The SP informs the SC of a PM parameter threshold violation having occurred in a specific Ob. + +## 7.3 Business level requirements (use cases) + +Basic requirements (in text form) for QMS are provided in 7.2, 7.3 and 7.4 and identify the associated use cases with actor/role and resources. The goal of these clauses is to define system requirements for the QoS/SLA service management system shown on Figure 7-1. The requirements of the system under development, that is, what functionality must be provided by the system, is documented in a use case model that illustrates the system's intended functions (use cases), its surroundings (actors), and the relationships between the use cases and actors (use case diagrams). Note that actors are not part of the system – they represent anyone or anything that must interact with the system. Additional information on use case conventions may be found in OMG – *Unified Modeling Language, Version 1.5* (March 2003). + +### 7.3.1 Actors + +The only actor defined is that of the Service Customer (SC) as identified in Figure 7-1. The role of the SC actor is analogous to the role of the performance manager actor shown on Figure 7-3. Note that the use cases associated with the traffic manager actor (also shown on Figure 7-3) are currently beyond the scope of this Recommendation. + +![Figure 7-3/M.3341 – Use cases for performance measurement. This diagram shows two actors, 'Traffic manager' and 'Performance manager', interacting with several use cases represented by ovals. The Traffic manager is associated with 'Administer traffic report', 'Report traffic' (via 'request traffic report'), and 'Periodic report traffic' (via 'traffic report'). The Performance manager is associated with 'Administer PM', 'Report PM data' (via 'get historical PM data'), and 'Monitor performance' (via 'QoS threshold crossed').](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Figure 7-3/M.3341 – Use cases for performance measurement. This diagram shows two actors, 'Traffic manager' and 'Performance manager', interacting with several use cases represented by ovals. The Traffic manager is associated with 'Administer traffic report', 'Report traffic' (via 'request traffic report'), and 'Periodic report traffic' (via 'traffic report'). The Performance manager is associated with 'Administer PM', 'Report PM data' (via 'get historical PM data'), and 'Monitor performance' (via 'QoS threshold crossed'). + +**Figure 7-3/M.3341 – Use cases for performance measurement (Figure 1/Q.822.1)** + +The administer PM and report PM data use cases shown in Figure 7-3 have been expanded into more granular use cases and are shown on Figure 7-4. The monitor performance use case is expanded as shown on Figure 7-5. + +![Figure 7-4/M.3341 – SC-initiated use cases. This diagram shows a single actor, 'Service customer', interacting with eight granular use cases represented by ovals. The use cases are: 'Retrieve MPs', 'Retrieve Obs', 'Configure Ob', 'Assign PM data collection interval', 'Suspend/Resume PM data collection', 'Reset PM data', 'Assign PM threshold (including severity)', and 'Request PM data (current or history)'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 7-4/M.3341 – SC-initiated use cases. This diagram shows a single actor, 'Service customer', interacting with eight granular use cases represented by ovals. The use cases are: 'Retrieve MPs', 'Retrieve Obs', 'Configure Ob', 'Assign PM data collection interval', 'Suspend/Resume PM data collection', 'Reset PM data', 'Assign PM threshold (including severity)', and 'Request PM data (current or history)'. + +**Figure 7-4/M.3341 – SC-initiated use cases** + +The use cases shown in Figure 7-4 are expansions of the high-level use cases called Administer PM and Report PM Data in Figure 7-3. + +![Figure 7-5/M.3341 – SP-initiated use cases. A diagram showing a 'Service customer' actor on the left connected by arrows to three use cases on the right: 'Report MP configuration changes', 'Report SP suspension of PM data collection', and 'Report PM threshold violation'. The use cases are represented by yellow ovals with horizontal stripes. Below the use cases is the text 'M.3341_F7-5'.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 7-5/M.3341 – SP-initiated use cases. A diagram showing a 'Service customer' actor on the left connected by arrows to three use cases on the right: 'Report MP configuration changes', 'Report SP suspension of PM data collection', and 'Report PM threshold violation'. The use cases are represented by yellow ovals with horizontal stripes. Below the use cases is the text 'M.3341\_F7-5'. + +**Figure 7-5/M.3341 – SP-initiated use cases** + +The use case shown in Figure 7-5 is an expansion of the high-level use case called Monitor Performance in Figure 7-3. + +### 7.3.2 Telecommunication resources + +The relevant resources required to support the use cases found in this clause are described in ITU-T Rec. M.2301. ITU-T Rec. M.2301 provides performance objectives and procedures for provisioning and maintenance of IP-based networks owned by different operators. This is regardless of the transport technology supporting the IP network and the higher layers to be implemented over IP. + +### 7.3.3 High-level use case diagrams + +This clause contains high-level use case diagrams that summarize the functionality and interfaces of the QoS/SLA service management system as shown in Figure 7-1. The use case diagrams are organized along the lines shown in Table 7-1, i.e., use cases initiated by the SC are depicted first followed by use cases initiated by the SP. In some cases there may be specific use cases mentioned on more than one high-level diagram. The reason for such duplication is to aid in completing the characterization of behaviour and functionality. Use case descriptions are provided in 7.4 for every use case pictured in these high-level diagrams. + +## 7.4 Specification level requirements + +This clause contains textual details for each of the use cases shown in the high-level use case diagrams of 7.3. The details are provided to clarify the roles of external actors and telecommunication resources and to refine the previous high-level use case diagrams to a specification level. Use case details include the following components: + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Name | The name of the use case (matches all drawing names) | +| Summary | A summary of the use case's purpose and content | +| Actor(s) | The names of actors involved in the use case including role characteristic for each actor | +| Assumptions | A description of the environment providing a context for the use case | +| Pre-conditions | A list of all system and environmental conditions that must be true before the use case can be triggered | +| Begins when | The name of the single event that triggers the start of the use case | +| Description | The various tasks that make up the use case, not necessarily in sequence. The description should reference any reuse of TMN functionality | +| Ends when | The event(s) that signals that the use case has terminated | + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------| +| Exceptions | A summary list of all exception conditions and faults detected by the use case during its operation | +| Post-conditions | A list of all system and environmental conditions that must be true if the use case has terminated without internal error | + +### 7.4.1 Retrieve MPs + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Retrieve Measurement Points (MPs) | +| Summary | In order for an SC to fully utilize QMS, the SC needs to have knowledge of the MPs provided by the SP that are being made available to the SC to use as part of the QMS.
For a given telecommunication service that is being provided by the SP to the SC, the SC queries the SP and the SP responds with a listing of all MPs available to the SC corresponding to that particular telecommunication service. | +| Actor(s) | Service Customer (SC) | +| Assumptions | Each telecommunication service that the SP provides to the SC will have a specific set of MPs corresponding to that service. The available set of MPs is fixed by the SP according to an SLA describing QMS capabilities that will be available to the SC. | +| Pre-conditions | The SP is providing a telecommunication service to the SC.
The SP has established a specific set of MPs corresponding to this telecommunication service.
The SP has agreed to provide QMS to the SC in accordance with a specific SLA. | +| Begins when | The SC issues a request to retrieve MPs. | +| Description | The SC issues a request to retrieve MPs associated with a specific telecommunication service. In the request, the SC must identify the specific instance of telecommunication service for which MP information is being requested.
The SP responds with a listing of the names of all MPs corresponding to that particular instance of telecommunication service.
Once the SC has knowledge of the MP names, the SC can also use the generic operations getAttributes and/or getAllAttributes defined in Annex C/M.3020 to find out more information about specific MPs (e.g., what parameters they are capable of measuring). | +| Ends when | The SP responds with a listing of the names of all MPs corresponding to the particular instance of telecommunication service. | +| Exceptions | Invalid telecommunication service instance ID | +| Post-conditions | The SC has knowledge of the MPs available corresponding to a particular instance of telecommunication service that can be used as part of the QMS. | + +### 7.4.2 Retrieve Obs + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Retrieve Observations (Obs) | +| Summary | The SC can create and delete Obs via the "Configure Obs" use case (see 7.4.3). In order for the SC to synchronize its view of what Obs currently exist (and/or the attributes associated with these Obs), the SC queries the SP to find out what Obs currently exist corresponding to a given telecommunication service. | +| Actor(s) | Service Customer (SC) | +| Assumptions | Obs are created, deleted, and modified by the SC via the "Configure Obs" use case (see 7.4.3). | +| Pre-conditions | The SP has agreed to provide QMS to the SC in accordance with a specific SLA. | +| Begins when | The SC issues a request to retrieve Obs. | + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description |

The SC issues a request to retrieve Obs associated with a specific telecommunication service. In the request, the SC must identify the specific instance of telecommunication service for which Ob information is being requested.

The SP responds with a listing of the names of all Obs corresponding to that particular instance of telecommunication service. Note that a "null" response is allowed if no Obs currently exist for that specific instance of telecommunication service.

Once the SC has knowledge of the Ob names, the SC can also use the generic operations getAttributes and/or getAllAttributes defined in Annex C/M.3020 to find out more information about specific Obs (e.g., what parameters they are measuring).

| +| Ends when | The SP responds with a listing of all Obs corresponding to the particular instance of telecommunication service. | +| Exceptions | Invalid telecommunication service instance ID | +| Post-conditions | The SC has knowledge of the Obs that currently exist corresponding to a particular instance of telecommunication service. | + +### 7.4.3 Configure Ob + +| | | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Configure Observation (Ob) | +| Summary | The SC may create a new Ob or delete an existing Ob. | +| Actor(s) | Service Customer (SC) | +| Assumptions |

In the context of QMS, each Ob instance is represented by a managed object. The SC needs to have the ability to create and delete Ob instances, and to examine the value of attributes of Ob instances.

When an Ob object is created, a currentData object (contained by the Ob object) will also implicitly be created (see 7.2).

The attributes of an Ob instance must identify (at a minimum) an ingress MP, an egress MP, the QoS parameter(s) being measured by the Ob, and whether the measurements are being made for unidirectional or bidirectional traffic.

Once an Ob is created, its attribute values remain fixed for the duration of the Ob object instance lifetime (i.e., until the Ob is deleted).

| +| Pre-conditions |

The SP has agreed to provide QMS to the SC in accordance with a specific SLA.

The SC has knowledge of the MPs available corresponding to a particular instance of telecommunication service that can be used as part of the QMS (see 7.4.1).

The SC has knowledge of the Obs that currently exist corresponding to a particular instance of telecommunication service (see 7.4.2).

| +| Begins when | The SC initiates a request to create or delete an Ob managed object. | +| Description |

The following management service described in ITU-T Rec. X.730 applies to this use case:

  • the creation and deletion of managed objects

This use case is satisfied by applying the management service procedures defined in ITU-T Rec. X.730 to the Ob managed object.

| +| Ends when | The SP informs the SC that the request has been completed. | +| Exceptions | Defined by ITU-T Rec. X.730 | +| Post-conditions | Depending on what the SC requested, the post-condition will either be the creation of a new Ob, or the deletion of an existing Ob. | + +### 7.4.4 Assign PM data collection interval + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Assign PM data collection interval | +| Summary | The SC instructs the SP about the duration of the PM data collection interval for a given Ob or set of Obs. This information (i.e., the duration of the PM data collection interval) may also be queried from the SP by the SC. | +| Actor(s) | Service Customer (SC) | +| Assumptions | As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes.
Each Ob will contain a specific instance of the currentData managed object.
The PM data collection interval is specified via the granularityTime attribute of the currentData object. | +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | The SC either requests the current value, or assigns a new value, for the PM data collection interval being used for a specific Ob (or set of Obs). | +| Description | The management service to support the " assign PM data collection " function is defined in ITU-T Rec. Q.822.
This use case is satisfied by applying the Q.822 procedures to the currentData managed object contained by the Ob managed object. | +| Ends when | The SP informs the SC that the request has been completed. | +| Exceptions | None beyond those defined by ITU-T Rec. Q.822 | +| Post-conditions | The SC will know the value of the PM data collection interval corresponding to the Ob and, if assigned by the SC in the request, the PM data collection interval will reflect this new assigned value. | + +### 7.4.5 Suspend/Resume PM data collection + +| | | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Suspend/Resume PM data collection | +| Summary | The SC instructs the SP to suspend/resume the performance monitoring data collection activity for a given Ob or set of Obs. | +| Actor(s) | Service Customer (SC) | +| Assumptions | As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes.
Each Ob will contain a specific instance of the currentData managed object.
PM data collection is suspended and resumed by modifying the value of the administrativeState attribute of the currentData object (i.e., attribute value of "locked" suspends PM data collection, and attribute value of "unlocked" resumes PM data collection). | +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | The SC issues a request to either suspend or resume PM data collection for a specific Ob (or set of Obs). | +| Description | The management service to support the " suspend/resume PM data collection " function is defined in ITU-T Rec. Q.822.
This use case is satisfied by applying the Q.822 procedures to the currentData managed object contained by the Ob managed object. | +| Ends when | The SP informs the SC that the request has been completed. | + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Exceptions |
  • • Exceptions defined by ITU-T Rec. Q.822
  • • Cannot resume due to SP-initiated suspend (see 7.4.11)
| +| Post-conditions | As requested by the SC, PM data collection for the Ob will be suspended or resumed. | + +### 7.4.6 Reset PM data + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Reset PM data | +| Summary | The SC instructs the SP to reset the performance monitoring counters for a given Ob or set of Obs. | +| Actor(s) | Service Customer (SC) | +| Assumptions |

As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes.

Each Ob will contain a specific instance of the currentData managed object.

A reset of PM data is accomplished by modifying the value of the counter attribute of the currentData object (i.e., setting the value to zero).

| +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | The SC issues a request to reset PM data for a specific Ob (or set of Obs). | +| Description |

The management service to support the "reset PM data" function is defined in ITU-T Rec. Q.822.

This use case is satisfied by applying the Q.822 procedures to the currentData managed object contained by the Ob managed object.

| +| Ends when | The SP informs the SC that the request has been completed. | +| Exceptions | None beyond those defined by ITU-T Rec. Q.822 | +| Post-conditions | The PM data counter for the Ob (or set of Obs) is reset to zero. | + +### 7.4.7 Assign PM history duration + +| | | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Assign PM history duration | +| Summary | The SC instructs the SP to establish the duration during which to maintain a specific record of PM historical data. This information (i.e., the duration which to maintain a specific record of PM historical data) may also be queried from the SP by the SC. | +| Actor(s) | Service Customer (SC) | +| Assumptions |

As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes. At the end of each PM data collection interval, a historyData object instance is created. Once the new historyData object is created, it will be retained for at least the duration equivalent to the number of intervals specified in the historyRetention attribute of the currentData object.

Each Ob will contain a specific instance of the currentData managed object.

The SC can assign PM history duration by modifying the value of the historyRetention attribute of the currentData object.

| +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | The SC either requests the current value, or assigns a new value, for the PM history duration being used for a specific Ob. | + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description |

The management service to support the "assign PM history duration" function is defined in ITU-T Rec. Q.822.

This use case is satisfied by applying the Q.822 procedures to the currentData managed object contained by the Ob managed object.

| +| Ends when | The SP informs the SC that the request has been completed. | +| Exceptions | None beyond those defined by ITU-T Rec. Q.822 | +| Post-conditions | The SC will know the value of the PM history duration corresponding to the Ob, and if assigned by the SC in the request, the PM history duration will reflect this new assigned value. | + +### 7.4.8 Assign PM threshold (including severity) + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Assign PM threshold (including severity) | +| Summary |

The SC instructs the SP to establish the threshold criteria for PM data of a given Ob or set of Obs. Each threshold setting consists of the attribute identifier of the PM parameter, the threshold value and (optionally) the severity of the threshold-exceeding event. This information (i.e., the threshold criteria for PM data) may also be queried from the SP by the SC.

| +| Actor(s) | Service Customer (SC) | +| Assumptions |

As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes. Additionally, a thresholdData managed object will be identified by the thresholdDataId attribute of the currentData managed object and will provide values of the threshold settings for the PM parameters.

Each Ob will contain a specific instance of the currentData managed object.

The SC can assign PM threshold (including severity) data by modifying the value of the counterThresholdList attribute of the thresholdData object.

| +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | The SC either requests the current value, or assigns a new value, for the PM threshold data (which includes severity of the threshold-exceeded event) being used for a specific Ob (or set of Obs). | +| Description |

The management service to support the "assign PM threshold" function is defined in ITU-T Rec. Q.822. Severity is included as part of the PM threshold definition.

This use case is satisfied by applying the Q.822 procedures to the thresholdData managed object contained by the currentData managed object contained by the Ob managed object.

| +| Ends when | The SP informs the SC that the request has been completed. | +| Exceptions | None beyond those defined by ITU-T Rec. Q.822 | +| Post-conditions | The SC will know the value of the PM threshold data (including severity) corresponding to the Ob, and if assigned by the SC in the request, the PM threshold data will reflect this new assigned value. | + +### 7.4.9 Request PM data (current or history) + +| | | +|----------|--------------------------------------------------------------------------------------------------------------------------| +| Name | Request PM data (current or history) | +| Summary | The SC issues a spontaneous request to the SP for current or historical PM data information on a given Ob or set of Obs. | +| Actor(s) | Service Customer (SC) | + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Assumptions | As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes. At the end of each PM data collection interval, a historyData object instance is created. Once the new historyData object is created, it will be retained for at least the duration equivalent to the number of intervals specified in the historyRetention attribute of the currentData object.
Each Ob will contain a specific instance of the currentData managed object and multiple instances of the historyData managed object.
The SC can request PM data (current or history) by reading the attributes of the currentData and historyData managed objects. | +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | The SC issues a request for PM data (current or history) associated with a specific Ob (or set of Obs). | +| Description | The management service to support the " request PM data " function is defined in ITU-T Rec. Q.822. This function includes requests for current or historical PM data information.
This use case is satisfied by applying the Q.822 procedures to the currentData and/or historyData managed object(s) contained by the Ob managed object. | +| Ends when | The SP informs the SC that the request has been completed. | +| Exceptions | None beyond those defined by ITU-T Rec. Q.822 | +| Post-conditions | The SC is in receipt of the requested PM data (current or history). | + +### 7.4.10 Report MP configuration changes + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Report Measurement Point (MP) configuration changes | +| Summary | If the SP makes a change to the MPs provided to the SC, then the SP would send a report to the SC to inform them of such a change. The reported change could be the addition of a new MP, the deletion of an existing MP, or a change in the PM parameters that can be monitored from the MP. | +| Actor(s) | Service Customer (SC) | +| Assumptions | Each telecommunication service that the SP provides to the SC will have a specific set of MPs corresponding to that service. The available set of MPs is fixed by the SP, according to an SLA describing QMS capabilities that will be available to the SC.
Once MPs have been established for a QMS being provided to a specific SC, configuration changes to these MPs would not normally be expected but may occur on an exceptional basis.
Configuration changes to MPs that are currently in use for an Ob (i.e., the Ob ingress MP or the Ob egress MP) should not be allowed. | +| Pre-conditions | The SP is providing a telecommunication service to the SC.
The SP has established a specific set of MPs corresponding to this telecommunication service.
The SP has agreed to provide QMS to the SC in accordance with a specific SLA.
An exceptional condition has occurred that necessitates a need for the SP to make a MP configuration change. | +| Begins when | The SP issues an MP configuration change report. | + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description |

The following management services described in ITU-T Rec. X.730 apply to this use case:

  • • the reporting of creation and deletion of managed objects;
  • • the reporting of changes to attribute values of managed objects.

This use case is satisfied by applying the management service procedures defined in ITU-T Rec. X.730 to the MP managed object.

| +| Ends when | The SC receives the MP configuration change report. | +| Exceptions | None beyond those defined by ITU-T Rec. X.730 | +| Post-conditions | The SC is informed of the MP configuration change. | + +### 7.4.11 Report SP suspension of PM data collection + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Name | Report Service Provider (SP) suspension of PM Data Collection | +| Summary | In unusual circumstances (e.g., SP PM data collection system failure), it may be necessary for the SP to suspend PM data collection corresponding to an Ob that the SC has established without obtaining permission from the SC to do so. If the SP suspends PM data collection, then the SP would send a report to the SC to inform them of this event. | +| Actor(s) | Service Customer (SC) | +| Assumptions |

As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes.

Each Ob will contain a specific instance of the currentData managed object.

PM data collection is suspended by modifying the value of the administrativeState attribute of the currentData object to that of "locked".

| +| Pre-conditions |

An Ob and its contained currentData object are being used to collect PM data.

The SP experiences an unusual condition (e.g., SP PM data collection system failure) that causes the SP to intervene and suspend PM data collection.

| +| Begins when | The SP issues an SP suspension of PM data collection report. | +| Description |

The following management service described in ITU-T Rec. X.730 applies to this use case:

  • • the reporting of changes to attribute values of managed objects.

This use case is satisfied by applying the management service procedures defined in ITU-T Rec. X.730 to the currentData object.

| +| Ends when | The SC receives the SP suspension of PM data collection report. | +| Exceptions | Defined by ITU-T Rec. X.730 | +| Post-conditions | The SC is informed of the SP suspension of PM data collection. | + +### 7.4.12 Report PM threshold violation + +| | | +|----------|-----------------------------------------------------------------------------------------------| +| Name | Report PM threshold violation | +| Summary | The SP informs the SC of a PM parameter threshold violation having occurred in a specific Ob. | +| Actor(s) | Service Customer (SC) | + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Assumptions | As defined by ITU-T Rec. Q.822, a currentData managed object will be used to record the current performance data for monitoring purposes. Additionally, a thresholdData managed object will be contained by the currentData managed object and will provide the values of the threshold settings for the PM parameters.
Each Ob will contain a specific instance of the currentData managed object.
If any of the thresholds (defined in the contained thresholdData object) are violated, a Quality of Service (QoS) alarm notification is emitted by the currentData object. | +| Pre-conditions | The SC has created and properly configured one or more Obs for a specific telecommunication service instance (see 7.4.3). | +| Begins when | A threshold violation occurs corresponding to a specific Ob. | +| Description | The management service to support the " report PM threshold violation " function is defined in ITU-T Rec. Q.822.
This use case is satisfied by applying the Q.822 procedures to the currentData managed object contained by the Ob managed object. | +| Ends when | The SC receives the PM threshold violation report. | +| Exceptions | None beyond those defined by ITU-T Rec. Q.822 | +| Post-conditions | The SC is informed of the PM threshold violation. | + +# 8 Interface requirements + +QoS is defined as the set of parameters which define the properties of media streams. The notion of QoS is different for the various system layers; e.g., the description of QoS at the application layer is usually at a higher level than that at the network layer of a communication system. The required QoS depends on various factors such as the used media (video, audio, etc.), the coding format used to encode the data, the application and the type of the application. For instance, the QoS of a videoconference is different from that of a video retrieval application, since the dialogue-mode communication of a conference requires a short delay which is not as important for playback applications. + +Support for configurable, realizable and maintainable QoS is expected by numerous distributed applications. As such, it must necessarily be provided on an end-to-end basis from the source of data to the final perception of the data by the consuming user. This means that all hardware and software components involved in the overall tasks of the applications must provide appropriate methods and handle the data accordingly, from the local resources at the sender side via the transport system and networks, to the local resources at the receiving side. This applies to end-systems, servers and networks as well as to system software and applications. + +Most of the participating resources are shared among users and various processes. One approach would be to (over-) design them based on peak demands such that no collisions between demands of different applications can ever occur. Then it would not be necessary to provide any resource management functionality. Yet, such a scenario would result in huge costs and low resource utilization and, hence, is typically not realizable. So, if we have limited resources, we may use filtering and scaling mechanisms, which adapt the generated workload to the available resources by changing the characteristics of the transmitted data stream, e.g., lowering the frame rate of a video stream. Yet, these techniques cannot offer a reliable, constant QoS during the run-time of an application. We believe that typical distributed computer systems still are, and will be so for a considerable amount of time, in the "window of scarcity". Thus, to provide a constant QoS during the run-time of an application, resource reservation and scheduling techniques must be applied. + +There are still different perspectives on QoS as observed by service providers and service users whereby, for the former, efficiency of resource utilization is the focal point of QoS while, to the latter, the completeness of parameterization of the service is most important. These different + +perspectives have led to different service models, which in the past did not allow for quantitative mappings between them. Hence, a goal to be strived for must be an integral view of QoS for both providers and users of a service. This can be achieved if both components are integrated into one system as, for example, when the operating system offers services to the applications like process scheduling, but has been very difficult when multiple parties have to cooperate, as in the case of a network services provider and an application program, which naturally pursue very different objectives. However, by using the QMS services as described in clause 7, an integral view of QoS for both providers and users of a service can be achieved, even in an environment that necessitates the cooperation of multiple parties. The specification for the interface requirements (i.e., the interface that QMS services will be carried across) is a subject of other ITU-T Recommendations. + +QoS is inherently an end-to-end requirement since, for the user, the whole concept of QoS is only attractive if the presentation at the user interface satisfies his/her needs. This means that an overall approach to QoS provisioning is necessary. Another critical factor for establishing an efficient and effective interface for interchange of service and network management information between TMNs across the X-interface, is standardization of data elements that represent appropriate information associated with QoS. Standardized data elements for management information interchange need to be identified for application to QoS provisioning and management. In addition, specialized data elements may need to be defined and standardized that would apply uniquely to specialized application types (e.g., Telecommunication for Disaster Relief). The definition of the appropriate data elements to be conveyed using QMS services will be specified by other ITU-T Recommendations. + +# Annex A + +## QMS management scenarios + +This annex describes multiple scenarios, which utilize the QoSMS to manage QoS in a multi-service provider environment. Figure A.1 is taken from Figure 3-1 and represents a mapping into the supply-chain model. P and C in the figure represent the role associations in the supply-chain model. P is the Provider role. C is the Customer role. The ISP acts in both a Provider (P) role and Customer (C) role. The ISP acts in the P role to the SC, and acts in the C role to the TSPs from which he acquires telecommunication services. Likewise, the TSP acts in the P role to the ISP, to which he supplies telecommunication services, and the C role to the NOs who in turn provide telecommunication services to the TSP. + +![Figure A.1/M.3341 – X-interface generic model. The diagram shows a chain of four entities connected by X-interfaces. From left to right: 1. Service customer (green hatched box) with a 'C' (Customer) role on its right side. 2. ISP (cross-hatched box) with a 'P' (Provider) role on its left side and a 'C' (Customer) role on its right side. 3. TSP (yellow hatched box) with a 'P' (Provider) role on its left side and a 'C' (Customer) role on its right side. 4. NO (blue hatched box) with a 'P' (Provider) role on its left side. The connections are labeled 'X-interface'.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +``` + +graph LR + SC[Service customer] ---|X-interface| ISP + ISP ---|X-interface| TSP + TSP ---|X-interface| NO + style SC fill:#90EE90,stroke:#333,stroke-width:1px + style ISP fill:#D3D3D3,stroke:#333,stroke-width:1px + style TSP fill:#FFD700,stroke:#333,stroke-width:1px + style NO fill:#ADD8E6,stroke:#333,stroke-width:1px + +``` + +Figure A.1/M.3341 – X-interface generic model. The diagram shows a chain of four entities connected by X-interfaces. From left to right: 1. Service customer (green hatched box) with a 'C' (Customer) role on its right side. 2. ISP (cross-hatched box) with a 'P' (Provider) role on its left side and a 'C' (Customer) role on its right side. 3. TSP (yellow hatched box) with a 'P' (Provider) role on its left side and a 'C' (Customer) role on its right side. 4. NO (blue hatched box) with a 'P' (Provider) role on its left side. The connections are labeled 'X-interface'. + +Figure A.1/M.3341 – X-interface generic model + +While most QMS management scenarios may be inferred directly from the use cases described in clause 7, this annex describes additional QMS management scenarios that involve the combination of multiple use cases. These examples pertain to the implementation and execution phases of the service life cycle (see clause 5). + +## A.1 Implementation phase (service orders and provision) + +Figure A.1 shows the relationships between peer entities in the supply-chain model. In this figure, the ISP provides an SLA to the SC. The TSP provides an SLA to the ISP and so on down the supply-chain. The ISP has a contract with the TSP whereby the TSP provides MPs into its own internal business processes. While the SP business process of the TSP is out of scope of this Recommendation, the announcement of MPs like: + +- time stamp of receipt of order (acknowledgement of receipt of order), +- firm order commitment date (time), +- and the time service is actually provided, + +provide MPs to the SC to enable the SC to measure the performance (QoS) of the SPs ordering and provisioning services. These MPs are typically predefined in the contract but may be prescribed by regulatory oversight. The SC is able to derive Obs by computing the time difference between the MPs and comparing these results with the SLA guarantees using the QMS defined in this Recommendation. + +## A.2 Execution phase (monitor, surveillance) + +Two example scenarios are described for the execution phase. + +#### A.2.1 Cancel an observation request + +Looking at Figure 3-1 as an example, suppose that the ISP, acting as the QMS SC, requests the creation of an observation between MP-a and MP-c using the configure Ob use case (see 7.4.3) and the corresponding X.730 creation of managed object management service. Immediately after sending this creation request, the ISP realizes that a more meaningful observation would be between MP-a and MP-d. + +Note that when an Ob object is created, a currentData object (contained by the Ob object) also gets implicitly created. It is recommended that when an Ob object and its corresponding currentData object are created, the initial value of the administrativeState attribute of the currentData object always be set to "locked", i.e., PM data collection for this Ob and its contained currentData object would not begin until a subsequent "resume PM data collection" was sent from the SC to the SP using the Suspend/Resume PM data collection use case (see 7.4.5). + +Therefore, for the scenario described above, the SC may send a second request to create an observation, this time specifying that the observation occur between MP-a and MP-d. Since the SC never sent a "resume PM data collection" corresponding to the initial observation request, no PM data actually gets collected for this initial *incorrect* observation. The SC can then send a "resume PM data collection" corresponding to the second observation request (i.e., the *correct* one) and meaningful PM data collection begins. Finally, the SC can send a request to the SP to delete the initial *incorrect* observation using the configure Ob use case (see 7.4.3) and the corresponding X.730 deletion of managed object management service. + +#### A.2.2 Modify parameters being monitored within an observation + +As a continuation of the previous scenario, suppose that the ISP (i.e., the QMS SC) has been using the *correct* observation to collect PM data based on QoS parameters "x" and "y". Further, suppose that the QoS requirements for the SC's application change so that PM data based on QoS parameters "x" and "z" are now more relevant to the SC than PM data based on QoS parameters "x" and "y". Thus the SC would like its observation to continue between MP-a and MP-d, however, it would now like to collect QoS data in terms of parameters "x" and "z" rather than in terms of parameters "x" and "y". It is assumed that both MP-a and MP-d support PM data collection in terms of any or all of the QoS parameters "x", "y", and "z". + +Note that according to the configure observation (Ob) use case (see 7.4.3), once an Ob managed object has been created, the attributes of the Ob object are fixed for the lifetime of the Ob object, i.e., they cannot be modified by the SC. + +Therefore, for the scenario described above, the SC may send a request to create a new observation with attributes defined for monitoring QoS parameters "x" and "z". The SC can then send a "resume PM data collection" corresponding to this new observation and PM data collection in terms of QoS parameters "x" and "z" begins. Finally, the SC can send a "suspend PM data collection" request to the SP corresponding to the old Ob object so that PM data collection in terms of QoS parameters "x" and "y" ceases. Once a sufficient amount of PM history data has been established using the new observation, the SC may choose to delete the old Ob managed object (with attributes corresponding to QoS parameters "x" and "y") using the configure Ob use case (see 7.4.3) and the corresponding X.730 deletion of managed object management service. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communications | +| Series Y | Global information infrastructure, Internet protocol aspects and Next Generation Networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3342-200607-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/M/T-REC-M.3342-200607-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ff472bf04c7dfce4e8b3da787ca63f7cdd57b04 --- /dev/null +++ b/marked/M/T-REC-M.3342-200607-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:837e2ffe45f2ff17ad0726aefb3e1a2a6e509891dc186c891ebaa2527354cf26 +size 26992 diff --git a/marked/M/T-REC-M.3342-200607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3342-200607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3342-200607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3342-200607-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/M/T-REC-M.3342-200607-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8a561bd0e0cc69c5be196000db37fe9097e8b34 --- /dev/null +++ b/marked/M/T-REC-M.3342-200607-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4dd640ac4c018f0199d57f0b0e573062224f3f8333053824944c0267190dd35 +size 109732 diff --git a/marked/M/T-REC-M.3342-200607-I_PDF-E/raw.md b/marked/M/T-REC-M.3342-200607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..968d1ea8954323582f2d9f7fc0f4f02c1c79a934 --- /dev/null +++ b/marked/M/T-REC-M.3342-200607-I_PDF-E/raw.md @@ -0,0 +1,1347 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3342** + +(07/2006) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Guidelines for the definition of SLA representation templates** + +ITU-T Recommendation M.3342 + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **ITU-T Recommendation M.3342** + +# **Guidelines for the definition of SLA representation templates** + +## **Summary** + +This Recommendation mainly deals with SLA Representation Templates used for Service Customers and Service Providers. It briefly introduces the overview and characteristics of SLA representation templates, and describes the detailed classification of SLA content, and provides the guidelines for the definition of SLA representation templates in detail, including the instructions for completing SLA templates. In Appendix I a simple example of SLA Representation Templates and instances of them are illustrated for reference. + +## **Source** + +ITU-T Recommendation M.3342 was approved on 14 July 2006 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. + +## **Keywords** + +Key performance indicator, KPI, key quality indicator, KQI, service level agreement, SLA, template. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2006 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | | Page | +|------|-----------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 3.1 | Definitions imported from ITU-T Rec. E.860..... | 2 | +| 3.2 | Definitions imported from ITU-T Rec. M.3208.1..... | 2 | +| 3.3 | Definitions imported from ITU-T Rec. E.419..... | 2 | +| 3.4 | Definitions imported from TMF GB917-2..... | 2 | +| 3.5 | Definitions imported from ITU-T Rec. M.3050.1..... | 3 | +| 3.6 | Other definitions in this Recommendation..... | 3 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Overview of SLA representation templates..... | 4 | +| 5.1 | Background..... | 4 | +| 5.2 | What are SLA representation templates ..... | 4 | +| 5.3 | Characteristics of standardized SLA representation templates ..... | 5 | +| 5.4 | What is GDSRT..... | 5 | +| 6 | Compositions of SLA representation templates ..... | 5 | +| 6.1 | SLA contents ..... | 5 | +| 6.2 | Basic composition of SLA representation templates..... | 6 | +| 6.3 | Extended composition of SLA representation templates ..... | 7 | +| 7 | Guidelines for the definition of SLA Representation Templates ..... | 10 | +| 7.1 | SLA profile..... | 10 | +| 7.2 | SLA Representation Templates proformas for business part..... | 11 | +| 7.3 | SLA Representation Template proformas for service part..... | 16 | +| 7.4 | SLA Representation Template Proformas for Technology Part..... | 18 | +| 7.5 | SLA Representation Template Proformas for QoS Report ..... | 22 | +| | Appendix I – Examples of SLA Representation Templates for VLL service ..... | 24 | +| | Appendix II – Lists of QoS Parameters to be selected in a SLA ..... | 30 | +| II.1 | A List of QoS Parameters from TMF GB917 ..... | 30 | +| II.2 | A List of QoS Parameters from ITU-T Rec. E.802 ..... | 31 | + + + +# Guidelines for the definition of SLA representation templates + +# 1 Scope + +The emerging new service and its QoS management requirements are challenging the NGN service management, demanding extendibility and scalability. The most important characteristic of NGN different from the current network is the QoS guarantee for services. SLAs are considered an effective way of solving the problems of QoS guarantee between Service Customers (SCs) and Service Providers (SPs). + +Guidelines for the Definitions of SLA Representation Templates (GDSRT) are the instructional explanations about service level, quality of service, priorities and duties in the SLA content. Four parts, business part, service part, technology part, and QoS report, are defined in the guidelines and the content of each part is described in detail. On the basis of the guidelines, the specific SLA representation template instances can be developed according to the specific service features. + +This Recommendation provides the guidelines and instructions for the definition and composition of SLA representation templates in order to manage QoS and service guarantee of telecommunication services effectively. It is the scope of this Recommendation to provide an overview of: + +- the definition and characteristics of SLA representation templates, based on the requirements of QoS management for emerging new services; +- guidelines for the definition of SLA representation templates, in order to standardize the representation methods of SLAs; +- proformas of SLA representation templates and instructions for completing the proformas to allow defining any specific templates meeting the requirements for different services; and +- some SLA Representation Templates examples. + +Although the guidelines for the definition are proposed in the context of NGN QoS requirements, it can be adapted to any telecommunication service and is not just limited to NGN services. + +It is out of the scope of this Recommendation to provide the definition and concept of each specific Key Performance Indicator (KPI) or Key Quality Indicator (KQI); only the abstraction for how to represent QoS Parameters, KPIs and KQIs are addressed in this Recommendation. The definitions of KPIs and KQIs can be imported into SLA Representation Templates from other ITU-T Recommendations or specifications from other organizations. + +By following the templates and the filling instructions provided in this Recommendation, a specific SLA can be created for a specific service. Some more detailed information can be captured from TMF GB917 Volume 2 [15] and Volume 3 [16], and ITU-T Rec. E.802 [3]. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation E.800 (1994), *Terms and definitions related to quality of service and network performance including dependability*. +- [2] ITU-T Recommendation E.801 (1996), *Framework for Service Quality Agreement*. +- [3] ITU-T Recommendation E.802 (Draft), *Framework and methodologies for the determination and application of QoS parameters*. +- [4] ITU-T Recommendation E.860 (2002), *Framework of a service level agreement*. +- [5] ITU-T Recommendation G.1010 (2001), *End-user multimedia QoS categories*. +- [6] ITU-T Recommendation M.1532 (2000), *Network maintenance service performance agreement (MSPA)*. +- [7] ITU-T Recommendation M.2301 (2002), *Performance objectives and procedures for provisioning and maintenance of IP-based networks*. +- [8] ITU-T Recommendation M.3010 (2000), *Principles for a telecommunications management network*. +- [9] ITU-T Recommendation M.3050.1 (2004), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. +- [10] ITU-T Recommendation M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*. +- [11] ITU-T Recommendation Y.1001 (2000), *IP Framework – A framework for convergence of telecommunications network and IP network technologies*. +- [12] ITU-T Recommendation Y.1221 (2002), *Traffic control and congestion control in IP-based networks*. +- [13] ITU-T Recommendation Y.1540 (2002), *Internet protocol data communication service – IP packet transfer and availability performance parameters*. +- [14] ITU-T Recommendation Y.1541 (2006), *Network performance objectives for IP-based services*. +- [15] TeleManagement Forum GB917-2 Version 2.5 (2005), *SLA Management Handbook – Volume 2 – Concepts and Principles*. +- [16] TeleManagement Forum GB917-3 Version 2.1 (2005), *SLA Management Handbook – Volume 3 – Service and Technology Examples*. + +# 3 Definitions + +## 3.1 Definitions imported from ITU-T Rec. E.860 + +- Service Level Agreement (SLA) + +## 3.2 Definitions imported from ITU-T Rec. M.3208.1 + +- Service Customer (SC) +- Service Provider (SP) + +## 3.3 Definitions imported from ITU-T Rec. E.419 + +- Key Performance Indicators (KPI) + +## 3.4 Definitions imported from TMF GB917-2 + +- Key Quality Indicator (KQI) + +## **3.5 Definitions imported from ITU-T Rec. M.3050.1** + +- End User (EU) +- Enterprise +- Customer1 + +## **3.6 Other definitions in this Recommendation** + +This Recommendation defines the following terms: + +**3.6.1 SLA representation templates:** SLA representation templates are the canonical representation method and format of a SLA for a specific service. It is composed of several proformas to contain the SLA contents for a specific service. It provides the structures and the organization method for the SLA content. When the SLA templates for a specific service are filled in with concrete information, they become a practical SLA instance. + +**3.6.2 guideline for the definition of SLA representation templates (GDSRT):** GDSRT are the instructional explanations about how SLA content of a specific service can be organized and represented. It provides a directive profile about the canonical definitions and expressions of generic SLA representation templates. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations: + +| | | +|-------|----------------------------------------------------------------------------------| +| BBER | Background Block Error Ratio | +| BER | Bit Error Ratio | +| ES | Error Seconds | +| EU | End User | +| GDSRT | Guidelines for the Definition of SLA Representation Templates | +| ID | Identifier | +| IP | Internet Protocol | +| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector | +| KPI | Key Performance Indicator | +| KQI | Key Quality Indicator | +| MSPT | Multiplex Section Protection Termination | +| MTBF | Mean Time Between Failures | +| MTBO | Mean Time Between Outages | +| MTPS | Mean Time to Provide Service | +| MTRS | Mean Time to Restore Service | +| MTTR | Mean Time To Repair | +| MTU | Maximum Transmission Unit | +| NGN | Next Generation Network | + +--- + +1 The concept of "Customer" from ITU-T Rec. M.3050.1 [9] (which is originated by TMForum) and that of "Service Customer" from ITU-T Rec. M.3208.1 [10] (which is originated by ITU-T) are used as equivalent terms within this Recommendation. + +| | | +|------|---------------------------------------| +| NP | Network Performance | +| OI | Outage Intensity | +| OMG | Object Management Group | +| PM | Performance Monitoring | +| QoS | Quality of Service | +| RFS | Ready For Service | +| RFSD | Ready For Service Date | +| SA | Service Availability | +| SDF | Service Degradation Factor | +| SLA | Service Level Agreement | +| SA | Service Availability | +| SC | Service Customer | +| SES | Severely Errored Seconds | +| SP | Service Provider | +| SUA | Service UnAvailability | +| TMF | TeleManagement Forum | +| TMN | Telecommunications Management Network | +| UAS | UnAvailable Seconds | +| VLL | Virtual Leased Line | + +# 5 Overview of SLA representation templates + +## 5.1 Background + +The goal of the SLA is to create a healthy relationship between the SP and the SC, and to protect the legal rights of both the SP and the SC. Because of different SPs, different services and different definitions of SLA clauses, there is no standardized SLA representation and expression during the service negotiation and QoS guarantee phase. It is necessary to define standardized and generic guidelines of SLA representation templates to solve this problem. + +## 5.2 What are SLA representation templates + +SLA is a long-term guarantee of SCs' satisfaction. Both the SC's and the SP's interests are served by a simplified SLA negotiation and standardized contract process. + +SLA representation templates are the canonical representation method and format of a SLA for a specific service. It is composed of several proformas that contain the SLA content for a specific service. It provides the structures and the organization method for the SLA content. When the SLA templates for a specific service are filled in with concrete information, they become a practical SLA instance. + +## **5.3 Characteristics of standardized SLA representation templates** + +The characteristics of standardized SLA representation templates defined by this Recommendation should at least be: + +- accordant with the current criteria; +- definition self-contained; +- extensible; +- realizable; and +- comprehensible. + +## **5.4 What is GDSRT** + +Guidelines for the Definitions of SLA Representation Templates (GDSRT) are the instructional explanations about how SLA content of a specific service can be organized and represented. GDSRT provides the format of each proforma that may be involved in SLA representation templates, the structures about how SLA content is organized, which proformas to select in order to form a complete set of templates for a specific service, and the instructions about how the proformas can be filled in. On the basis of the guidelines, specific SLA representation templates for a specific service can be developed accordingly. Based on the SLA Representation Templates, the SLA negotiation between SCs and SPs can be carried out, and the agreed results can be captured in the SLA representation templates, thus forming a practical SLA instance. + +# **6 Compositions of SLA representation templates** + +## **6.1 SLA contents** + +TMF GB917-3 [16] has specified that a SLA may contain the following: + +- Points of Contact; +- Services Provided; +- System Design Information; +- Supporting Equipment; +- Level and Quality of Service; +- Monitoring and Reporting; +- Service Center; +- SP Backup and Disaster Recovery Mechanisms; +- Terms and Conditions; +- Network and Delivery Upgrades; +- Change Procedures; +- Service Violations and Remedies; +- Tariffs and Billing; +- Service Termination. + +This Recommendation imports the above content into SLA Representation Templates, and the detailed information of each item can be found in clause 4 of GB917-3 [16]. In this Recommendation, additional details extend the above content list. + +## 6.2 Basic composition of SLA representation templates + +![Diagram showing the basic composition of SLA content. A central box labeled 'SLA contents' branches out to four boxes: 'Business part', 'Service part', 'Technology part', and 'QoS report'. The text 'M.3342(06)_F01' is located to the right of the 'Technology part' box.](007b053fe94a8348f75128a584503fd0_img.jpg) + +``` +graph TD; SLA[SLA contents] --> Business[Business part]; SLA --> Service[Service part]; SLA --> Technology[Technology part]; SLA --> QoS[QoS report]; +``` + +M.3342(06)\_F01 + +Diagram showing the basic composition of SLA content. A central box labeled 'SLA contents' branches out to four boxes: 'Business part', 'Service part', 'Technology part', and 'QoS report'. The text 'M.3342(06)\_F01' is located to the right of the 'Technology part' box. + +**Figure 1/M.3342 – Basic composition of SLA content** + +Figure 1 gives the basic composition of the SLA content, regardless of the services provided. Generally, the content of a SLA include the following four parts, which can be used to categorize the above SLA content listed in 6.1. + +### 1) *Business part* + +This part describes the general business information and business procedures related to the service provided by the SP to the SC. It may describe the information about contact information, general terms, help desk center, service violation processing and billing information, etc. This part covers the following items that are listed in 6.1: + +- Points of Contact; +- Terms and Conditions; +- Service Center; +- Change Procedures; +- Service Violations and Remedies; +- Tariffs and Billing; +- Service Termination. + +### 2) *Service part* + +This part describes the detailed information about the service provided to the SC. It includes the negotiated service content and the agreed service level. This part covers the following items that are listed in 6.1: + +- Services Provided; +- Service Level. + +### 3) *Technology part* + +This part gives the detailed information about QoS parameters, metrics set, and some technical supporting infrastructure, such as supporting equipments and system design information, etc. This part covers the following items that are listed in 6.1: + +- QoS Parameters; +- Supporting Equipments; +- System Design Information; +- SP Backup and Disaster Recovery Mechanisms; +- Network and Delivery Upgrades. + +### 4) *QoS report* + +This part includes the QoS report information provided to the SC and the SP in order to evaluate service level negotiated in the SLA. This part covers the following item that is listed in 6.1: + +- Monitoring and Reporting. + +## 6.3 Extended composition of SLA representation templates + +Based on the content of SLA and the basic composition of SLA representation templates, Figure 2 shows an extended composition of SLA representation templates using UML class diagram. The defined templates are general and neutral, which is service-independent and technology-independent. It can last for the lifetime of a SLA. + +![UML class diagram showing the extended composition of SLA representation templates. The root class is 'SLA representation templates', which has a composition relationship with 'SLA Profile' proforma, 'Service Identification' proforma, 'Business part', 'QoS Report' proforma, 'Service part', and 'Technology part'. 'Business part' has a composition relationship with 'Points of Contact' proforma, 'Terms and Conditions' proforma, 'Change Procedures' proforma, 'Service Violations and Remedies' proforma, 'Service Center' proforma, 'Tariffs and Billing' proforma, and 'Service Termination' proforma. 'Service part' has a composition relationship with 'Service Level' proforma and 'Service Provided' proforma. 'Technology part' has a composition relationship with 'System Design Information' proforma, 'Network and Delivery Upgrades' proforma, 'SP Backup and Recovery Mechanisms' proforma, 'QoS parameters', and 'Supporting Equipment Profile' proforma. 'QoS parameters' has a composition relationship with 'QoS Metrics' proforma, 'KPI Definitions' proforma, and 'KQI Definitions' proforma. 'Supporting Equipment Profile' proforma has a composition relationship with 'Supporting Equipment' proforma. Multiplicity indicators are shown on the relationships.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` + +classDiagram + SLA_representation_templates["SLA representation templates"] + SLA_Profile_proforma["\"SLA Profile\" proforma"] + Service_Identification_proforma["\"Service Identification\" proforma"] + Business_part["Business part"] + QoS_Report_proforma["\"QoS Report\" proforma"] + Service_part["Service part"] + Technology_part["Technology part"] + Points_of_Contact_proforma["\"Points of Contact\" proforma"] + Terms_and_Conditions_proforma["\"Terms and Conditions\" proforma"] + Change_Procedures_proforma["\"Change Procedures\" proforma"] + Service_Violations_and_Remedies_proforma["\"Service Violations and Remedies\" proforma"] + Service_Center_proforma["\"Service Center\" proforma"] + Tariffs_and_Billing_proforma["\"Tariffs and Billing\" proforma"] + Service_Termination_proforma["\"Service Termination\" proforma"] + Service_Level_proforma["\"Service Level\" proforma"] + Service_Provided_proforma["\"Service Provided\" proforma"] + System_Design_Information_proforma["\"System Design Information\" proforma"] + Network_and_Delivery_Upgrades_proforma["\"Network and Delivery Upgrades\" proforma"] + SP_Backup_and_Recovery_Mechanisms_proforma["\"SP Backup and Recovery Mechanisms\" proforma"] + QoS_parameters["QoS parameters"] + Supporting_Equipment_Profile_proforma["\"Supporting Equipment Profile\" proforma"] + QoS_Metrics_proforma["\"QoS Metrics\" proforma"] + KPI_Definitions_proforma["\"KPI Definitions\" proforma"] + KQI_Definitions_proforma["\"KQI Definitions\" proforma"] + Supporting_Equipment_proforma["\"Supporting Equipment\" proforma"] + + SLA_representation_templates "1" o-- "1" SLA_Profile_proforma + SLA_representation_templates "1" o-- "1" Service_Identification_proforma + SLA_representation_templates "1" o-- "1" Business_part + SLA_representation_templates "1" o-- "1..*" QoS_Report_proforma + SLA_representation_templates "1" o-- "1" Service_part + SLA_representation_templates "1" o-- "1" Technology_part + Business_part "1" o-- "1..*" Points_of_Contact_proforma + Business_part "1" o-- "0..1" Terms_and_Conditions_proforma + Business_part "1" o-- "0..1" Change_Procedures_proforma + Business_part "1" o-- "1" Service_Violations_and_Remedies_proforma + Business_part "1" o-- "0..1" Service_Center_proforma + Business_part "1" o-- "1" Tariffs_and_Billing_proforma + Business_part "1" o-- "0..1" Service_Termination_proforma + Service_part "1" o-- "1" Service_Level_proforma + Service_part "1" o-- "1" Service_Provided_proforma + Technology_part "1" o-- "0..1" System_Design_Information_proforma + Technology_part "1" o-- "0..1" Network_and_Delivery_Upgrades_proforma + Technology_part "1" o-- "0..1" SP_Backup_and_Recovery_Mechanisms_proforma + Technology_part "1" o-- "1" QoS_parameters + Technology_part "1" o-- "0..1" Supporting_Equipment_Profile_proforma + QoS_parameters "1" o-- "1..*" QoS_Metrics_proforma + QoS_parameters "1" o-- "1..*" KPI_Definitions_proforma + QoS_parameters "1" o-- "0..*" KQI_Definitions_proforma + Supporting_Equipment_Profile_proforma "1" o-- "1..*" Supporting_Equipment_proforma + +``` + +UML class diagram showing the extended composition of SLA representation templates. The root class is 'SLA representation templates', which has a composition relationship with 'SLA Profile' proforma, 'Service Identification' proforma, 'Business part', 'QoS Report' proforma, 'Service part', and 'Technology part'. 'Business part' has a composition relationship with 'Points of Contact' proforma, 'Terms and Conditions' proforma, 'Change Procedures' proforma, 'Service Violations and Remedies' proforma, 'Service Center' proforma, 'Tariffs and Billing' proforma, and 'Service Termination' proforma. 'Service part' has a composition relationship with 'Service Level' proforma and 'Service Provided' proforma. 'Technology part' has a composition relationship with 'System Design Information' proforma, 'Network and Delivery Upgrades' proforma, 'SP Backup and Recovery Mechanisms' proforma, 'QoS parameters', and 'Supporting Equipment Profile' proforma. 'QoS parameters' has a composition relationship with 'QoS Metrics' proforma, 'KPI Definitions' proforma, and 'KQI Definitions' proforma. 'Supporting Equipment Profile' proforma has a composition relationship with 'Supporting Equipment' proforma. Multiplicity indicators are shown on the relationships. + +Figure 2/M.3342 – Extended compositions of SLA Representation Templates + +The supporting proformas for the above SLA Representation Templates are described from 6.3.1 to 6.3.5. + +### 6.3.1 SLA profile + +The proformas related to the SLA profile include the following: + +#### 1) *"Service Identification" proforma* + +The "Service Identification" proforma is used to describe the basic identification information about the service, the SC and the SP involved in this SLA. There is one and only one instance of this proforma in a specific SLA. + +#### 2) *"SLA Profile" proforma* + +The "SLA Profile" proforma provides a summary and list of all the proformas (table) that are used in a specific SLA, and the indexes for them will also be included. There is one and only one instance of this proforma in a specific SLA. + +### 6.3.2 Business part + +The proformas related to the Business part include the following: + +#### 1) *"Points of Contact" proforma* + +The "Points of Contact" proforma is used to specify the contact information about the SP and the SC. The information should be kept both in the SC and the SP. There are one or more instances of this proforma in a specific SLA. + +#### 2) *"Terms and Conditions" proforma* + +The "Terms and Conditions" proforma is used to specify some terms and conditions that both the SP and the SC should follow during the lifecycle of the SLA. There may be zero or one instance of this proforma in a specific SLA. + +#### 3) *"Service Center" proforma* + +The "Service Center" proforma is used to specify the information related to the Service Help Center that the SP provides to the SC. There may be zero or one instance of this proforma in a specific SLA. + +#### 4) *"Change Procedures" proforma* + +The "Change Procedures" proforma is used to specify the general procedures when there is a need for the SC to change the requirements of the service. There may be zero or one instance of this proforma in a specific SLA. + +#### 5) *"Service Violations and Remedies" proforma* + +The "Service Violations and Remedies" proforma is used to specify the service commitments and the remedies when the SP cannot deliver the agreed service levels. There is one and only one instance of this proforma in a specific SLA. + +#### 6) *"Tariffs and Billing" proforma* + +The "Tariffs and Billing" proforma is used to specify the billing information about the service. There is one and only one instance of this proforma in a specific SLA. + +#### 7) *"Service Termination" proforma* + +The "Service Termination" proforma is used to specify the information related to service termination, such as termination period or data transfer process. There may be zero or one instance of this proforma in a specific SLA. + +### 6.3.3 Service Part + +The proformas related to the Service part include the following: + +#### 1) *"Service Provided" proforma* + +The "Service Provided" proforma is used to specify the detailed information about the service that the SP provided to the SC, such as the service description, the Service Access Point List, etc. There is one and only one instance of this proforma in a specific SLA. + +#### 2) *"Service Level" proforma* + +The "Service Level" proforma is used to specify the information about the agreed service level in the overall viewpoint. (Details about the Quality of Service parameters can be found in "QoS Proformas" in the Technology Part). There is one and only one instance of this proforma in a specific SLA. + +### 6.3.4 Technology part + +The proformas related to the Technology part include the following: + +#### 1) *"QoS Parameters" related proformas* + +The proformas for "QoS Parameters" are composed of the following three parts: + +- "QoS Metrics" proforma; +- "KPI Definition" proforma; and +- "KQI Definition" proforma. + +The first "QoS Metrics" proforma is used to specify the detailed information of each QoS parameters for the service, which can be viewed as an extension for the "Service Level" proforma. There are one or more instances of the "QoS Metrics" proforma in a specific SLA, for example, one for technology-independent QoS metrics, and another for technology-specific QoS Parameter. + +The second "KPI Definition" proforma and the third "KQI Definition" proforma are used to provide the detailed definition information for each KPI and KQI specified in the "QoS Metrics" proforma. There are one or more instances of the "KPI Definition" proforma and may be zero or more instances of "KQI Definition" proforma in a specific SLA. + +#### 2) *"Supporting Equipments" related proformas* + +The proformas for "Supporting Equipments" are composed of the following two parts: + +- "Supporting Equipment Profile" proforma; and +- "Supporting Equipment" proforma. + +The first "Supporting Equipment Profile" proforma is used to specify the list of SP equipments that are located in the SC Premises; the second "Supporting Equipment" proforma is used to describe the details about each individual equipment listed in the first table. There may be zero or one instance of "Supporting Equipment Profile" proforma, and zero or more instances of the "Supporting Equipment" proforma in a specific SLA. When there is SP's equipment(s) located at the SC's Premises, there is one and only one instance of "Supporting Equipment Profile" proforma, and one or more instances of "Supporting Equipment" proforma. + +#### 3) *"System Design Information" proforma* + +The "System Design Information" proforma can be used to specify the concerns about the design of service infrastructure if needed. There may be zero or one instance of this proforma in a specific SLA. + +#### 4) *"Backup and Recovery Mechanisms" proforma* + +The "Backup and Recovery Mechanisms" proforma is used to specify some backup and recovery mechanisms in case of disasters. There may be zero or one instance of this proforma in a specific SLA. + +#### 5) *"Network and Delivery Upgrades" proforma* + +The "Network and Delivery Upgrades" proforma is used to specify the items that need to be addressed when there are changes in SP's network or delivery mechanisms. There may be zero or one instance of this proforma in a specific SLA. + +### 6.3.5 QoS report + +The proforma related to QoS Reporting include the following: + +#### 1) *"QoS Report" proforma* + +QoS Report is the service report provided to both the SC and SP. Its data comes from the Business part, the Service part and the Technology part. QoS data statistic outputs are the important proof to evaluate and improve service levels negotiated in SLA. The "QoS Report" proforma is used to specify the detailed information related QoS report. There are one or more instances of this proforma in a specific SLA. + +# 7 Guidelines for the definition of SLA Representation Templates + +In this clause, main proformas for SLA Representation Templates are shown and explained. According to the proformas, specific templates meeting the requirements of different services can be developed. + +This clause is organized based on the composition for SLA Representation Templates shown in 6.3, and will cover the SLA content listed in 6.1. + +## 7.1 SLA profile + +### 7.1.1 Proforma for "Service Identification" + +The proforma for "Service Identification" is shown in Table 1: + +**Table 1/M.3342 – The "Service Identification" proforma** + +| | SC | SP | +|-------------------------------------------|----|----| +| Full Name | | | +| ID | | | +| Service Identification Information | | | +| Service Full Name | | | +| Service Identifier | | | +| Service Instance ID | | | +| Service Start Time | | | +| Service Termination Time | | | + +Where: + +- **Full Name:** This field contains the full name of the SC or SP in the corresponding column. +- **ID:** The assigned identifier specified for the SC or the SP. It can be used as a reference in order to search the corresponding information about the SC or the SP. +- **Service Full Name:** The full name of the service provided to the SC. An abbreviation can also be specified in this field. +- **Service Identifier:** The service number assigned by the SP. +- **Service Instance ID:** The unique Identifier assigned by the SP to each instance of the service provided to a SC. +- **Service Start Time:** This field is used to indicate when the service will be provided to the SC. +- **Service Termination Time:** This field is used to indicate when the service provided to the SC will be terminated. + +### 7.1.2 Proforma for "SLA Profile" + +The structure of the "SLA Profile" proforma is shown in Table 2: + +**Table 2/M.3342 – The "SLA Profile" proforma** + +| Proforma Index | Proforma Categories | Proforma Summary* | +|----------------|---------------------|-------------------| +| | | | +| | | | + +Where: + +- **Proforma Index:** The index of proformas selected in the SLA Representation Template list. Usually the table number can be used. +- **Proforma Categories:** This indicates the kind of proforma from 7.1.1 to 7.4.1. +- **Proforma Summary:** This gives a short summary of the specified proforma. This item is optional and can be left empty. + +## 7.2 SLA Representation Templates proformas for business part + +NOTE – In all the following tables, the items marked with a "\*" sign indicates that they are optional items and can be left empty. Items without the "\*" mark are mandatory. This convention is applicable for the entire Recommendation. + +### 7.2.1 Proformas for "Points of Contact" + +The structure of the "Points of Contact" proforma is shown in Table 3. In a specific SLA, there are one or more instances of the "Points of Contact" proforma. Generally, there are often two "Points of Contact" tables: one for the administrative matters and the other for the technical matters. + +**Table 3/M.3342 – The "Points of Contact" proforma** + +| | Service Customer | Service Provider | +|--------------------------------|------------------|------------------| +| Responsibility | | | +| Name of Contact | | | +| Work Title* | | | +| Description* | | | +| Telephone Number(s) | | | +| Fax Number(s)* | | | +| E-mail Address(es)* | | | +| Postal Address(es)* | | | +| Additional Information* | | | + +Where: + +- **Responsibility:** This field is used to specify what the contact person is responsible for, and the possible values to be filled in this field are "Technical matter" and "Administrative matter". Based on the contact person's actually responsibility, the allowed values can also be extended. + +- **Name of Contact:** The full name of the contact person for this Service. +- **Work Title:** The work title for the contact person. This field can be left empty. +- **Description:** The short description of the scope or the responsibility of the contact person. This field can be left empty. +- **Telephone Numbers(s):** The contact telephone number of the contact person. At least one number is specified. It is recommended that both the office telephone number and the mobile numbers be filled in this field, in case of an emergency. +- **Fax Number(s):** The contact fax number of the contact person. If there are more than one fax number, e.g., one for backup purpose, they can also be filled in this field. This field can also be left empty if there are no contact fax numbers. +- **E-mail Address(es):** The contact e-mail address(es) of the contact person. If there is more than one e-mail address, e.g., one for backup purpose, they can also be filled in this field. This field can also be left empty if there are no contact e-mail addresses for this person. +- **Postal Address(es):** The postal address of the contact person (including the postal code information). If there is more than one postal address, e.g., one for backup purpose, they can also be filled in this field. This field can also be left empty if there are no contact postal addresses. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to this contact person. This field can be left empty. + +NOTE – The information of the SC contact person should be filled in the corresponding "Service Customer" column, and the information of the SP contact person should be filled in the corresponding "Service Provider" column. + +### 7.2.2 Proformas for "Terms and Conditions" + +The structure of the "Terms and Conditions" proforma is shown in Table 4. When there is no specific information to specify for terms and conditions, this proforma can be ignored. + +**Table 4/M.3342 – The "Terms and Conditions" proforma** + +| | | +|---------------------------------------------------------|--| +| Subjection Indication* | | +| Acquisition or Merger Declaration* | | +| SC's Indemnify Description* | | +| SP Ownership Declaration* | | +| SC Information Ownership Declaration* | | +| Responsibility for Software Licensing/Ownership* | | +| SP's Indemnify Description* | | +| Dissemination Declaration* | | +| Additional information* | | + +Where: + +- **Subjection Indication:** The indication of the fact that the SLA is subject to "Terms and Conditions" of other agreements between the SP and SC. Note that if the SLA is subject to other agreements between the parties, certain legal provisions may be inherited by this SLA. This field can be left empty. + +- **Acquisition or Merger Declaration:** A description of any contract or service-level impacts of an acquisition or merger. This field can be left empty. +- **SC's Indemnify Description:** A specification of the extent, if any, to which the SC will indemnify the SP for third-party claims against the SP as a result of the SP's activities. This field can be left empty. +- **SP Ownership Declaration:** Descriptions of the SP's ownership or interest in patents trademarks, trade names, inventions, copyrights and trade secrets related to SP offerings. This field can be left empty. +- **SC Information Ownership Declaration:** Description of the SC's information data ownership. This field can be left empty. +- **Responsibility for Software Licensing/Ownership:** Specification of the responsibility for software licensing and/or ownership. This field can be left empty. +- **SP's Indemnify Description:** A specification of the extent, if any, to which the SP will indemnify the SC for claims that services infringe upon the Intellectual Property of others. This field can be left empty. +- **Dissemination Declaration:** Description of the information that may be disseminated openly. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the terms and conditions. This field can be left empty. + +### 7.2.3 Proformas for "Service Center" + +The structure of the "Service Center" proforma is shown in Table 5. When there is no Service Center provided to the SC, this proforma can be ignored. + +**Table 5/M.3342 – The "Service Center" proforma** + +| | | +|--------------------------------------------|--| +| Services Scope | | +| Authorized SC Staff | | +| Service Periods | | +| Contact Means | | +| Request Leveling* | | +| Escalation Process* | | +| Response/Resolution Times* | | +| Resolution Notifications | | +| SC's responsibility for Resolution* | | +| Training* | | +| Systematic Errors Identifying* | | +| Additional Information* | | + +Where: + +- **Services Scope:** Description of the scope of services offered by the SP's Service Center. +- **Authorized SC Staff:** Identification of the SC staff members that are authorized to use the Service Center. Usually, this field should be filled with the list of staff members of SC. In the case where anyone from SC is authorized staff to ask the Service Center, this field should be filled with "Anybody". + +- **Service Periods:** Specification of the periods when the service center is accessible to SC, including evening, week-end, and holiday coverage. +- **Contact Means:** Description of the means of contacting the service center, e.g., telephone, e-mail, etc. The contact telephone number or e-mail address should also be filled in this field. +- **Request Leveling:** Description of the mechanisms for assigning severity levels to customer help requests or problem reports, e.g., 1, 2, etc. This field can be left empty. +- **Escalation Process:** Description of the escalation process to be followed to change severity levels. This field can be left empty. +- **Response/Resolution Times:** Description of response times and resolutions times. This field can be left empty. +- **Resolution Notifications:** Description of how the SC will be notified of the problem resolution. +- **SC's responsibility for Resolution:** Description of SC's responsibilities resolving reported problems. This field can be left empty. +- **Training:** Description of training required by SC staff. This field can be left empty. +- **Systematic Errors Identifying:** Description of the mechanisms and/or procedures for identifying systematic errors based on help desk analysis. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the Service Center. This field can be left empty. + +### 7.2.4 Proformas for "Change Procedures" + +The structure of the "Change Procedures" proforma is shown in Table 6. When no changing procedures are allowed for the SC, or there are no such requirement changing cases for this service, this proforma can be ignored in a specific SLA. + +**Table 6/M.3342 – The "Change Procedures" proforma** + +| | | +|--------------------------------|--| +| Permitted Changes | | +| Specifying Method | | +| Change Time | | +| Additional Information* | | + +Where: + +- **Permitted Changes:** Description of any changes that the SC is permitted to make such as additional software. +- **Specifying Method:** Description of the method for specifying changes to requirements. +- **Change Time:** Description of the time required to change user requirements, such as notice and response times. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the Change Procedures. This field can be left empty. + +### 7.2.5 Proformas for "Service Violations and Remedies" + +The structure of the "Service Violations and Remedies" proforma is shown in Table 7: + +**Table 7/M.3342 – The "Service Violations and Remedies" proforma** + +| | | +|---------------------------------------|--| +| Violation | | +| | | +| | | +| Performance Bonuses* | | +| Disputes Resolution Procedures | | +| Additional Information* | | + +Where: + +- **Violation:** Description of the performance penalties in the event that SP fails to execute agreed service levels. Performance penalties could be administrative actions by the SP, monthly percentage fee rebates, correlated to the degree of underperformance, specific fee reductions or rebates, or contract termination if the underperformance is chronic. Violations can be described in different rows for different details or aspects if needed. +- **Performance Bonuses:** Description of the performance bonuses in the event that the SP exceeds the agreed service levels. This field can be left empty. +- **Disputes Resolution Procedures:** Description of the procedures to resolve disputes, e.g., arbitration procedures. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to Service Violations and Remedies. This field can be left empty. + +### 7.2.6 Proformas for "Tariffs and Billing" + +The structure of the "Tariffs and Billing" proforma is shown in Table 8. The following items are expected to be mutually agreed between the SC and the SP. + +**Table 8/M.3342 – The "Tariffs and Billing" proforma** + +| | | +|--------------------------------|--| +| Billing Details | | +| | | +| | | +| Billing Frequency | | +| Bill Delivery | | +| Additional Information* | | + +Where: + +- **Billing Details:** Description of the level of detail included in the bills. Billing details can be described in different rows for different aspects if needed. +- **Billing Frequency:** Description of the frequency of billing. +- **Bill Delivery:** Description of the media used to deliver the bill, e.g., suitable for use with software applications. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to Tariffs and Billing. This field can be left empty. + +### 7.2.7 Proformas for "Service Termination" + +The structure of the "Service Termination" proforma is shown in Table 9: + +**Table 9/M.3342 – The "Service Termination" proforma** + +| | | +|--------------------------------|--| +| Time Period | | +| Data Transfer Process | | +| Unilateral Termination | | +| Additional Information* | | + +Where: + +- **Time Period:** Specification of applicable time period for the return of data. +- **Data Transfer Process:** Specification of the process for data transfer. +- **Unilateral Termination:** Description of the process for unilateral termination. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the Service Termination. This field can be left empty. + +## 7.3 SLA Representation Template proformas for service part + +### 7.3.1 Proformas for "Service Provided" + +The structure of the "Service Provided" proforma is shown in Table 10: + +**Table 10/M.3342 – The "Service Provided" proforma** + +| | | +|-----------------------------------------|--| +| Service Identifier* | | +| Service Name | | +| Service Description | | +| SAP List | | +| Service Interfaces Requirements* | | +| Ready-for-Service Date(s) | | +| SC Notification Process | | +| Additional Information* | | + +Where: + +- **Service Identifier:** An identifier assigned by the SP for identification of the specific service; the identifier can be used as a reference for searching the detailed information about the service. This field can be left empty if SP does not use Service Identifiers. +- **Service Name:** The full name of the service. It is a user-friendly name of the service and can be used as a nickname for the Service Identifier. +- **Service Description:** A description of the service in terms meaningful to the SC and the SP. +- **SAP List:** A description of the service access points at the SC's sites. +- **Service Interfaces Requirements:** A specification of the service interfaces requirements, e.g., electrical and mechanical specifications, data link layer protocols, etc. This field can be left empty. + +- **Ready-for-Service Date(s):** A specification of the Ready-for-Service (RFS) dates and, if appropriate, the lead times required for service provisioning. It is expected that the service will be available on or before the date specified, at the cost agreed, and performing to the specifications contained within the SLA. +- **SC Notification Process:** A description of the process for SC notification in the event that the agreed RFS date cannot be met. Lead times for such notification may also be specified. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the provided services. This field can be left empty. + +### 7.3.2 Proformas for "Service Level" + +The structure of the "Service Level" proforma is shown in Table 11: + +**Table 11/M.3342 – The "Service Level" proforma** + +| | | +|------------------------------------------------|--| +| Service Class* | | +| Out-of-Service Times | | +| Force Majeure | | +| SC-Caused Outages* | | +| Restoration Priority* | | +| Restoration Times* | | +| Planned Outage Notification Procedures* | | +| Additional Information* | | + +Where: + +- **Service Class:** This field is used to specify the overall class of the service level. SPs usually use "Platinum", "Gold" or "Silver", etc. to categorize their provided service levels. Also, a number can be used in this field. This field can be left empty if there is no classification assigned for this SC. +- **Out-of-Service Times:** Out-of-service times such as the time required for routine maintenance. The process used to communicate changes in scheduled maintenance outages. Outages may also be defined. Lead times for such notices may also be specified. +- **Force Majeure:** Description of force majeure and other events beyond the SP's control when service may not be provided. +- **SC-Caused Outages:** Description of customer-caused outages that may impact the service. This field can be left empty +- **Restoration Priority:** Specification of the priority/precedence for restoration of service. This field can be left empty. +- **Restoration Times:** Specification of restoration times. This field can be left empty. +- **Planned Outage Notification Procedures:** Description of the notification procedures for planned outages. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the Service Level. This field can be left empty. + +## 7.4 SLA Representation Template Proformas for Technology Part + +### 7.4.1 Proformas for "QoS Parameters" + +The "QoS Parameters" related proformas include the following three parts: the "QoS Metrics" proforma, the "KPI Definition" proforma and the "KQI Definition" proforma. + +The structure of the "QoS Metrics" proforma is shown in Table 12: + +**Table 12/M.3342 – The "QoS Metrics" proforma** + +| Technology Dependency | | | | | | | +|-----------------------|----------------|-----------|----------------------|----------|--|--| +| QoS Parameter Area | | | | | | | +| Parameter ID | Parameter Name | | | | | | +| Value Range | Value Units | Qualifier | Definition Reference | SC Check | | | +| | | | | | | | +| | | | | | | | + +Where: + +- **Technology Dependency:** This indicates whether the QoS metrics in this table is technology dependent or independent. +- **QoS Parameter Area:** This indicates which area this QoS Parameter is dealing with. The possible categories to be filled in this field can be "Network Performance Metrics", "Traffic Metrics" and "Service Metrics". +- **Parameter ID:** It is assigned for each Parameter for reference and identification purpose. +- **Parameter Name:** This is field is used to specify the full name and the abbreviation of the specified QoS Parameter. +- **Value Range:** This field can be filled with the agreed value range (it can be negotiated between the SC and the SP, or the SC can select the value range from a list that SP provides), indicating the possible values that the QoS parameter should be in the range in order to be conformed to the agreed service level. +- **Value Units:** This indicates the units that are used by this parameter. When no units are used for this QoS parameter (such as a ratio), this field is filled with "--", indicating "not applicable". +- **Qualifier:** This indicates whether this QoS Parameter is mandatory, optional or conditional for this service. +- **Definition Reference:** This field should be filled in the index for the detailed definitions that can be found somewhere in Table 13 or 14. +- **SC Check:** This field should be filled in by the SC, indicating whether the SC wants this QoS Parameter to be included the SLA or not. When the "Qualifier" field is filled with "mandatory", this field is filled with "--", indicating "not applicable", which means that there is no need for the SC to specify. If the "Qualifier" field is filled with "optional", the SC can specify in this field whether this QoS parameter is required for this service or not, using "√" or "X". + +The structure of the "KQI Definition" proforma is shown in Table 13: + +**Table 13/M.3342 – The "KPI Definition" proforma** + +| Index | KPI ID | KPI Name | Source* | Definition* | +|----------------------------------------------------------------------------------------------------------|---------------|-----------------|----------------|--------------------| +| | | | | | +| | | | | | +| NOTE – Either "Source" or "Definition" field can be optional, but at least one of them should be filled. | | | | | + +Where: + +- **Index:** This field is used for reference purpose, and it can be used by other table items to locate this QoS Parameter. +- **KPI ID:** The Identifier assigned for each KPI. +- **KPI Name:** This field is used to specify the full name and the abbreviation of the specified KPI. +- **Source:** This field can be used to fill in the information about which Recommendation or specification the KPI is defined in. If the KPI is new, and cannot be found in any specifications, this field can be filled with "--", indicating "not applicable". +- **Definition:** This field can be used to provide the detailed definition about the KPI. It can be captured from the Recommendation or specification where this KPI is defined in. This field can be left empty if the source field is filled, and the source can be publicly accessed. When no definitions can be found in any specifications, the KPI definition is provided. + +The structure of the "KQI Definition" proforma is shown in Table 14: + +**Table 14/M.3342 – The "KQI Definition" proforma** + +| Index | KQI ID | KQI Name | Source* | Included KPI List | | Definition* | +|----------------------------------------------------------------------------------------------------------|---------------|-----------------|----------------|--------------------------|-----------------|--------------------| +| | | | | KPI ID | KPI Name | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| | | | | | | | +| NOTE – Either "Source" or "Definition" field can be optional, but at least one of them should be filled. | | | | | | | + +Where: + +- **Index:** This field is used for reference purposes, and it can be used by other table items to locate this QoS Parameter. +- **KQI ID:** It is assigned for each KQI for reference and identification purposes. +- **KQI Name:** This field is used to specify the full name and the abbreviation of the specified KQI. +- **Source:** This field can be used to provide information about the source that defines the KQI. If the KQI is new, and cannot be found in any Recommendation or specification, this field is filled with "--", indicating "not applicable". +- **Definition:** This field can be used to provide the detailed definition about the KQI. It can be captured from the Recommendation or specification where this KQI is defined. This field can be left empty if the source field is filled, and the source can be publicly accessed. When no definitions can be found in any specifications, the KQI definition is provided. + +### 7.4.2 Proformas for "Supporting Equipments" + +The structure of "Supporting Equipment Profile" proforma is shown in Table 15, and the "Supporting Equipment" proforma is shown in Table 16. When there are no SP equipment located in the SC Premises, these two proformas can be ignored in a specific SLA. + +**Table 15/M.3342 – The "Supporting Equipment Profile" proforma** + +| | Equipment Identifiers | Equipment Names | +|------------------------------------|------------------------------|------------------------| +| SP Equipment on SC Premises | | | +| | | | + +Where: + +- **Equipment Identifiers:** The Identifier of the SP's Equipment to be located on SC premises. The identifier can be used as an index to search the specified equipment. +- **Equipment Names:** The user-friendly name of the SP equipment to be located on SC premises. + +**Table 16/M.3342 – The "Supporting Equipment" proforma** + +| | | +|-----------------------------------------|--| +| Equipment Identifier | | +| Equipment Name | | +| Equipment Description | | +| Space Requirements | | +| Power Requirements | | +| Environment Control Requirements | | +| Maintenance Access Procedures | | +| Additional information* | | + +Where: + +- **Equipment Identifier:** The identifier of the SP equipment to be located on SC premises. +- **Equipment Name:** The user-friendly name of the SP equipment to be located on SC premises. +- **Equipment Description:** The description of the SP equipment to be located on SC premises. +- **Space Requirements:** The space requirements for this equipment. +- **Power Requirements:** The power requirements for this equipment. +- **Environment Control Requirements:** The environmental control requirements for this equipment. +- **Maintenance Access Procedures:** The access procedures for SP maintenance and installation staff. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to this supporting equipment. This field can be left empty. + +### 7.4.3 Proformas for "System Design Information" + +The structure of the "System Design Information" proforma is shown in Table 17. If the SC does not need the system design information, this table can be ignored in a specific SLA. + +**Table 17/M.3342 – The "System Design Information" proforma** + +| | | +|------------------------------------------|--| +| General System Design* | | +| Routing Details* | | +| SC Access for Design Information* | | +| Configuration Techniques* | | +| Scalability Design* | | +| Additional Information* | | + +Where: + +- **General System Design:** A description of how the system design will meet the following types of criteria: the absence of common failure points, the redundancy level required, alternative routing of facilities, transmission media restrictions, and restrictions on services that may be provided by other parties. This field can be left empty. +- **Routing Details:** A description of transmission media routing details that may be required along with a requirement that the routing and/or the media will not be changed without prior discussion and agreement. This field can be left empty. +- **SC Access for Design Information:** Description of the process whereby the SC may access the design information for periodic review or to review modifications. This field can be left empty. +- **Configuration Techniques:** Specification of the techniques to be used for recording configuration and for configuration change control. This field can be left empty. +- **Scalability Design:** A description of how the system design meets the stated scalability requirements. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the design of the service infrastructure. This field can be left empty. + +### **7.4.4 Proformas for "Backup and Recovery Mechanisms"** + +The structure of the "SP Backup and Recovery Mechanisms" proforma is shown in Table 18. If the SP does not provide such mechanisms in the service, this table can be ignored in a specific SLA. + +**Table 18/M.3342 – The "SP Backup and Recovery Mechanisms" proforma** + +| | | +|---------------------------------------|--| +| Backup Procedures* | | +| System Redundancy* | | +| Recovery Parameters* | | +| SP Disaster Recovery Priority* | | +| SC Support* | | +| Additional Information* | | + +Where: + +- **Backup Procedures:** Description of the procedures for data and application backups. This field can be left empty. +- **System Redundancy:** Description of the service delivery system redundancy. This field can be left empty. +- **Recovery Parameters:** Description of recovery parameters, i.e., how quickly can data be restored. This field can be left empty. + +- **SP Disaster Recovery Priority:** Description of the priority and process for SP disaster recovery. This field can be left empty. +- **SC Support:** Description of the SC support required to assist with disaster recovery. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the backup and recovery mechanisms. This field can be left empty. + +### 7.4.5 Proformas for "Network and Delivery Upgrades" + +The structure of the "Network and Delivery Upgrades" proforma is shown in Table 19. When there will not be any changes in the network or delivery mechanism, this table can be ignored in a specific SLA. + +**Table 19/M.3342 – The "Network and Delivery Upgrades" proforma** + +| | | +|-----------------------------------------------|--| +| Upgrade Procedures | | +| Recovery Procedures in Upgrade Failure | | +| Procedures for minor upgrades* | | +| SP Changes Implementation* | | +| Additional Information* | | + +Where: + +- **Upgrade Procedures:** Specification of the upgrade expectations and procedures, including provisions to meet the SC critical service availability requirements. +- **Recovery Procedures in Upgrade Failure:** Description of the recovery or back-out procedures in the event of an upgrade failure. +- **Procedures for minor upgrades:** Description of the procedures for releasing and installing patches and other minor upgrades. This field can be left empty. +- **SP Changes Implementation:** Description of how the SP will implement changes, e.g., over-the-air software upgrades, on-site installation, etc. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to the changes in network and delivery mechanisms. This field can be left empty. + +## 7.5 SLA Representation Template Proformas for QoS Report + +### 7.5.1 Proformas for "QoS Report" + +The structure of the "QoS Report" proforma is shown in Table 20: + +**Table 20/M.3342 – The "QoS Report" proforma** + +| | | +|----------------------------------|--| +| Content of Reports | | +| Reporting Frequency | | +| Report Delivery Mechanism | | +| Ad hoc Support* | | +| Time Points and Intervals | | +| Report Presentation | | + +**Table 20/M.3342 – The "QoS Report" proforma** + +| | | +|--------------------------------|--| +| Monitoring Approach* | | +| Detecting Mechanisms* | | +| SC Auditing Process* | | +| Performance Assessment* | | +| Additional Information* | | + +Where: + +- **Content of Reports:** Specifications of the content of performance reports. +- **Reporting Frequency:** Specifications of the frequency of performance reports. +- **Report Delivery Mechanism:** Specification of the performance report delivery mechanism, e.g., e-mail, postal delivery, electronic retrieval, report distribution lists, and the number of copies. +- **Ad hoc Support:** Specification of ad hoc reporting support. This field can be left empty. +- **Time Points and Intervals:** Definitions of the time points or intervals associated with performance events, and data aggregation intervals. +- **Report Presentation:** Specifications of the method for performance report data presentation, e.g., tables histograms, charts, etc. +- **Monitoring Approach:** Specification of the approach and extent to which the SP will monitor all necessary services e.g., network devices, circuits, services and applications, to prevent service unavailability. This field can be left empty. +- **Detecting Mechanisms:** Description of the mechanisms and processes the SP will use to detect and track downtime. This field can be left empty. +- **SC Auditing Process:** Description of the process that the SC may use to audit the SP's tracking and reporting mechanisms. This field can be left empty. +- **Performance Assessment:** Specification of when and how SC service monitoring data will be used to assess service performance. This field can be left empty. +- **Additional Information:** This field is reserved for extensions, and can be used to specify any other additional information that is related to QoS reporting. This field can be left empty. + +# Appendix I + +## Examples of SLA Representation Templates for VLL service + +VLL (Virtual Leased Line) is a common telecommunication service. In this appendix, instances of SLA representation template for a specific VLL service are described as an example of applying the definition guidelines. According to the GDSRT, SLA representation templates of VLL service can be created. When instantiated templates are filled with the SC and SP information, it becomes a concrete SLA. + +The SP or the SC can specify these attributes' values of this instance. Attribute values provided by SP are marked as [P]. Attribute values provided by the SC are marked as [C]. Attribute values selected by the SC from a set of values provided by the SP are marked as [P→C]. Attribute values marked with "UNSPECIFIED" can be replaced by some specific values in a real SLA. Items that are filled with "..." indicates that it is ignored only for example purpose, and in practice, some information should be filled in for that field. + +The examples listed in this appendix are used for the purpose of showing how the information is represented in template instances. The examples are not complete and it is not the purpose for readers to use this example in practice directly. + +**Table I.1/M.3342 – "Service Identification"** + +| | SC | SP | +|-------------------------------------------|----------------------------|-------------| +| Full Name | Customer1 [C] | SP1 [P] | +| ID | BJ00123 [P] | CH11236 [P] | +| Service Identification Information | | | +| Service Full Name | Virtual Leased Line [P→C] | | +| Service Identifier | S_1003 [P] | | +| Service Instance ID | BJ_0005 [P] | | +| Service Start Time | March 1st, 2006, 08:00 [C] | | +| Service Termination Time | March 1st, 2007, 08:00 [C] | | + +**Table I.2/M.3342 – "SLA Profile"** + +| Proforma Index | Proforma Categories | Proforma Summary* | +|----------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Table I.1 | "Service Identification" | This table provides the overall information about the SC and the SP, and provides the overview of the VLL service. | +| Table I.2 | "SLA Profile" | This table provides a list of tables that are used in this SLA instance. | +| Table I.3 | "Points of Contact" | The table provides the administrative contact person's information. | +| Table I.4 | "Terms and Conditions" | ... | +| Table I.5 | "Service Center" | ... | +| Table I.6 | "Service Violations and Remedies" | ... | +| Table I.7 | "Tariffs and Billing" | ... | +| Table I.8 | "Service Termination" | ... | +| Table I.9 | "Service Provided" | ... | +| Table I.10 | "Service Level" | ... | +| Table I.11 | "QoS Metrics" | Technology-independent Service QoS Metrics | +| Table I.12 | "QoS Metrics" | Technology-specific Traffic QoS Metrics | +| Table I.13 | "QoS Metrics" | Technology-independent Network Performance QoS Metrics | +| Table I.14 | "KPI Definition" | ... | +| Table I.15 | "KQI Definition" | ... | +| Table I.16 | "QoS Report" | ... | + +**Table I.3/M.3342 – "Points of Contact"** + +| | Service Customer | Service Provider | +|--------------------------------|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Responsibility | Administrative matter [C] | Administrative matter [P] | +| Name of Contact | ZHANG San [C] | LI Si [P] | +| Work Title* | CEO [C] | Help Desk Manager [P] | +| Description* | ... | ... | +| Telephone Number(s) | +86 10 6666 8888 (Office) [C]
+86 13966668888 (Mobile) [C] | +86 10 8888 6666 (Office) [P]
+86 13388886666 (Mobile) [P] | +| Fax Number(s)* | +86 10 6666 1234 [C] | +86 10 8888 4321 (Office) [P] | +| E-mail Address(es)* | Zhang.san@scl.com [C]
-- | Li.si@spl.com
Li.si@hotmail.com | +| Postal Address(es)* | -- | Mail box 111, No. 10, Service Provider Road, Beijing, China, (Postal Code: 100234) | +| Additional Information* | -- | -- | + +**Table I.4/M.3342 – "Terms and Conditions"***Example not shown.***Table I.5/M.3342 – "Service Center"***Example not shown.***Table I.6/M.3342 – "Service Violations and Remedies"***Example not shown.***Table I.7/M.3342 – "Tariffs and Billing"** + +| | | +|--------------------------------|----------------------------------------------------------------------------| +| Billing Details | Every Available hour will be charged for \$ 5. | +| | Degraded Service will be charged for \$ 5 × SDF per hour. | +| | Hours when the Service Available is under the SDF will not be charged. | +| Billing Frequency | The bill will be sent to the SC every month on the 30th day of that month. | +| Bill Delivery | The bill will be sent through FAX to the SC contact person's fax number. | +| Additional Information* | | + +**Table I.8/M.3342 – "Service Termination"** + +| | | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time Period | There will be a period of 5 working days for the return of data. | +| Data Transfer Process | ... | +| Unilateral Termination | The SC can unilaterally terminate the service before the planned service termination time; but the SC should notify the SP about the Unilateral Termination 5 working days ahead of time. The five days will also be charged. | +| Additional Information* | | + +**Table I.9/M.3342 – "Service Provided"** + +| | | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Service Identifier* | S_1003 | +| Service Name | Virtual Leased Line (VLL) | +| Service Description | The SP will provide 622M virtual leased line service to the SC during the agreed service period. | +| SAP List | SAP 1: Beijing Plaza A
SAP 2: Shanghai Plaza B | +| Service Interfaces Requirements* | SDH STM-2 interface | +| Ready-for-Service Date(s) | March 1st, 2006 | +| SC Notification Process | The SC will call the SP contact person one day before the delivered service date, when the agreed service cannot be delivered. | +| Additional Information* | | + +**Table I.10/M.3342 – "Service Level"** + +| | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Class* | Silver | +| Out-of-Service Times | 5 (1 is the highest) | +| Force Majeure | The Services Unavailable caused by Earthquake, Flood, or Tornado shall not be counted as SP service outage. | +| SC-Caused Outages* | The service outages caused by the power off of the SC Premises or by the SC unplugging the interface equipment are counted as SC-caused outages, which will still be charged. | +| Restoration Priority* | 3 (5 is the highest) | +| Restoration Times* | 5 times | +| Planned Outage Notification Procedures* | -- | +| Additional Information* | | + +**Table I.11/M.3342 – "QoS Metrics 1"** + +| | | | | | | | +|------------------------------------------------------------------------------------------------|----------------------------|--------------------|--------------------|---------------------------|-----------------------------|-----------------| +| Technology Dependency | Technology independent | | | | | | +| QoS Parameter Area | Service Metrics | | | | | | +| Parameter ID | Parameter Name | Value Range | Value Units | Qualifier | Definition Reference | SC Check | +| 200-001 | SA | ≥99.95%[C] | -- | Mandatory | I.15-1 | √ | +| 100-009 | SDF | 0.1 | -- | Mandatory | I.15-2 | √ | +| 100-104 | Fulfillment Period | 5 | days | Conditional a) | I.14-4 | √ | +| 100-105 | Express Fulfillment Period | 2 | days | Conditional a) | I.14-5 | X | +| ... | MTTR | 4 | hours | Mandatory | ... | √ | +| ... | MTBO | 60 | days | Optional | ... | √ | +| 100-206 | MTBF | 120 | days | Optional | I.14-6 | √ | +| ... | MSPT | 5 | working days | Optional | ... | X | +| a) Either "Fulfillment Period" or "Express Fulfillment Period" should be specified. | | | | | | | + +**Table I.12/M.3342 – "QoS Metrics 2"** + +| | | | | | | | +|------------------------------|-----------------------|--------------------|--------------------|------------------|-----------------------------|-----------------| +| Technology Dependency | Technology specific | | | | | | +| QoS Parameter Area | Traffic Metrics | | | | | | +| Parameter ID | Parameter Name | Value Range | Value Units | Qualifier | Definition Reference | SC Check | +| 100-003 | Bandwidth | 622 | Megabyte/s | Mandatory | I.14-3 | √ | +| ... | MTU Size | UNSPECIFIED | byte/s | Optional | ... | X | +| ... | Mean Rate | UNSPECIFIED | byte/s | Optional | ... | X | +| ... | Max Rate | UNSPECIFIED | byte/s | Optional | ... | X | +| ... | Burst Size | UNSPECIFIED | byte/s | Optional | ... | X | + +**Table I.13/M.3342 – "QoS Metrics 3"** + +| Technology Dependency | Technology independent | | | | | | +|------------------------------|-----------------------------|--------------------|--------------------|------------------|-----------------------------|-----------------| +| QoS Parameter Area | Network Performance Metrics | | | | | | +| Parameter ID | Parameter Name | Value Range | Value Units | Qualifier | Definition Reference | SC Check | +| ... | Mean Delay | 75 | ms | Mandatory | ... | √ | +| ... | Delay Priority | UNSPECIFIED | -- | Optional | ... | X | +| ... | Mean Jitter | 15 | ms | Optional | ... | √ | +| ... | Loss Rate | UNSPECIFIED | -- | Optional | ... | √ | +| 100-001 | BER | UNSPECIFIED | -- | Mandatory | I.14-1 | √ | +| ... | UAS | UNSPECIFIED | s | Optional | ... | √ | +| 100-002 | ES | UNSPECIFIED | s | Optional | I.14-2 | X | +| ... | SES | UNSPECIFIED | s | Optional | ... | X | + +**Table I.14/M.3342 – The "KPI Definition" proforma** + +| Index | KPI ID | KPI Name | Source* | Definition* | +|--------------|---------------|----------------------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| I.14.1 | 100-001 | BER (Bit Error Rate) | ITU-T Rec. E.800 | The ratio of the number of bit errors to the total number of bits transmitted in a given time interval. | +| I.14.2 | 100-002 | ES (Error Seconds ) | ... | ... | +| I.14-3 | 100-003 | Bandwidth | ... | This parameter provides the total capacity that is provided to the SC for a communication service. | +| I.14-4 | 100-104 | Fulfillment Period | -- | This KPI indicates the time period for the SP to fulfil an ordinary service. The units for the KPI are days. | +| I.14-5 | 100-105 | Express Fulfillment Period | -- | This KPI indicate the time period for the SP to fulfil an express service. It is usually much less than ordinary service fulfillment time period. The units for this KPI are days. | +| I.14-6 | 100-206 | MTBF | TMF GB917-2 | See TMF GB917-2 Annex A for details. | +| I.14-7 | 100-307 | Outage interval | ... | ... | +| I.14-8 | 100-308 | Active time | ... | ... | +| I.14-9 | 100-309 | SDF (Service Degradation Factor) | TMF GB917-2 | See TMF GB917-2 clause 3.1.20 for details. | +| ... | ... | ... | ... | ... | + +**Table I.15/M.3342 – The "KQI Definition" proforma** + +| Index | KQI ID | KQI Name | Source* | Included KPI List | | Definition* | +|--------|---------|---------------------------|------------------------------------|-------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | KPI ID | KPI Name | | +| I.15-1 | 200-001 | SA (Service Availability) | TMF GB917-2 clauses 3.1.9 & 3.1.20 | 100-307 | Outage interval | The unavailability of a service at the SAP is defined as an outage. The duration of this specific event is the outage interval. These concepts are used in the Service unavailability percentage (SUA%) and Service Availability percentage (SA%) calculation given below:
$SA\% = 100\% - SUA\%$ where Service UnAvailability $SUA\% = \sum(\text{Outage interval} \times \text{SDF}) / (\text{active time}) \times 100\%$ | +| | | | | 100-308 | active time | | +| | | | | 100-309 | SDF | | +| | | | | | | | + +**Table I.16/M.3342 – "QoS Report"** + +| | | +|----------------------------------|----------------------------------------------------------------------------------------| +| Content of Reports | Each QoS Parameter listed from Tables I.11 to I.13 will be reported in the QoS Report. | +| Reporting Frequency | Every working day. | +| Report Delivery Mechanism | Through e-mail. It will be sent to the contact person of the SC. | +| Ad hoc Support* | -- | +| Time Points and Intervals | Hourly from 9:00 to 17:00. A QoS Report will be generated. | +| Report Presentation | In the tabular format as agreed in document XYZ. | +| Monitoring Approach* | -- | +| Detecting Mechanisms* | Using Probes | +| SC Auditing Process* | -- | +| Performance Assessment* | -- | +| Additional Information* | | + +# Appendix II + +## Lists of QoS Parameters to be selected in a SLA + +This appendix contains a list of QoS Performance Parameters that may be selected in the "QoS Metric" Proforma of SLA representation templates. The provided QoS Parameters are for information only, which means they are not the whole set of QoS Parameters that may occur in a specific SLA. The definitions of these QoS Parameters can be found in other ITU-T Recommendations, TMF specifications (such as TMF GB917 [15][16]), or other standards. + +## II.1 A List of QoS Parameters from TMF GB917 + +This clause lists some example QoS Parameters captured from TMF GB917 specifications, which may be selected in a SLA. + +- 1) *General QoS Parameters* + - Average call response time; + - Bit Error Ratio (BER); + - Errored Seconds (ES); + - Outage Intensity (OI); + - Service Availability (SA); + - Service Degradation Factor (SDF); + - Service UnAvailability (SUA); + - Severely Errored Seconds (SES); + - Time to first yield; + - Unavailable Seconds (UAS). +- 2) *Technology/Service-Specific Service Individual User View* + - Maximum Errored Seconds Radio; + - Maximum Severely Errored Seconds Ratio; + - Maximum Background Block Error Ratio; + - Maximum Transfer Delay; + - Maximum Delay Variation. +- 3) *Technology-Independent Service Individual User View* + - Maximum Unavailability Time; + - Maximum Time To Restore; + - Minimum Time Between Failures. +- 4) *Technology/Service-Specific Service Aggregate View* + - Mean Errored Seconds Radio; + - Mean Severely Errored Seconds Ratio; + - Mean Transfer Delay; + - Mean Bit Error Ratio. + +- 5) *Technology-Independent Service Aggregate View* + - Total Unavailability Seconds; + - Mean Time Between Failures (MTBF); + - Mean Time Between Outages (MTBO); + - Mean Time To Repair (MTTR); + - Mean Time to Provide Service (MTPS); + - Mean Time to Restore Service (MTRS). + +## **II.2 A List of QoS Parameters from ITU-T Rec. E.802** + +This clause lists some example QoS Parameters captured from ITU-T Rec. E.802 [3], which may be selected in a SLA. + +- 1) *Applicable to any service* + - Supply time for fixed network access; + - Supply time for Internet access; + - Proportion of problems with number portability procedures; + - Fault report rate per fixed access lines; + - Fault repair time for fixed access lines; + - Response time for operator services; + - Response time for directory enquiry services; + - Response time for admin/billing enquiries; + - Bill correctness complaints; + - Prepaid account credit correctness complaints; + - Bill presentation quality; + - Frequency of customer complaints; + - Customer complaints resolution time; + - Customer relations; + - Professionalism of help line; + - Complaint Rate regarding Coverage of Traffic Jam; + - Availability of Call center; + - Availability of Attendants in Call center; + - Customer Request resolution time; + - Fault repair time for general defects. +- 2) *Voice telephony (and voice-band related services like fax, data transmission and SMS)* + - Unsuccessful call ratio; + - Call set-up time; + - Speech connection quality; + - Fax connection quality; + - Data rate of Dial-up access to the Internet; + - Successful SMS Ratio; + - Completion Rate for SMS; + - End-to-End delivery time for SMS. + +- 3) *Mobile services (voice telephony parameters as listed above also apply)* + - Unsuccessful call ratio; + - Dropped call ratio; + - Coverage. +- 4) *Internet access* + - Login time; + - Data transmission speed achieved; + - Unsuccessful data transmissions ratio; + - Successful log-in ratio; + - Delay (one-way transmission time). + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c75be847ac4f88426e56c2b1fef2903ef4df618 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf35cc88a601e7da41b8190beac8d27e798f2043e1265d18c95a9d3a7f5f38ec +size 54478 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f493e599aaed1f4f59adae1520d5ec43a149d1f3 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/01e00200a536673d6cd0e6d8705047a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82630b9965992a62ddf6e512431e1154a91c46cb3368d74a87398f0c7c1a3e80 +size 159796 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e526c131a5e07a5989d0aeb244578ff2020e03a9 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b493536cd2b24ebc39167225b88390145be1a4d1d592b81cf1ec885972a2f8b +size 60235 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6687cff4e21747c31723fa67dc09b8a58ec7ed8 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7897b27919b015db15540ddd3b7459235c1fdd741ed6605796a1fcca2283eb27 +size 51438 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..066552dafb1abd67550d7520cb7acefe72016136 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f21035ebe5fce80d1a5e02cc98c4e292167aaf698854831c79292157cb7c4a4 +size 34430 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d337de6843b08d40f231d82967e9f34bbf09c83f --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c25d5064c531a9da9111673fb94ce40e52302dfdd67b3dd50ab21dd8d5759595 +size 173626 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e625d07115d77037e15c2795ec929d0d4687f963 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b2b584dcdd672aebeae20b59f08be0fd88bc81ddc3e0e95384fc87aeb8f2a2c +size 24593 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40611be19a6b0cd2d0bd3cc53fb9ead72ea88ba --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fcfeed2a1d2a8e6fb5783063e2e980faec7482e3bc5cb665e24f96f9ddcbdee +size 201395 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e04646de7f1727d3ecd607906144ca0cdaf0b7d --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef65a68b42c5fd6eef6217afc359f96aeb0ed5165a863bf164d6b5c307b8eb38 +size 90502 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d86c2ed95e383e1a761b29919081ea69506ad406 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23e81d59a440d30560bca79741505341602c056d2b36001fa5289b3ac0b58d9b +size 25620 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22cdeb254a44e86596462fb2542cbd1d14a3f608 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f117ee19e72a5d18c3414c8da1a047366858fea0315d2bcb4b483c23a218cec +size 59948 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..273a4995374f8237373cb626e6946400056a7e65 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd29883daa818044f654bfd4f0abffbe5b022c3706fa9db351f376dcf26e2184 +size 106363 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41214a13c3d2dba7cad425ba39d468511d0cbc09 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:859ef86b2431265f296100d05ebfc4f16de3c0812f39cd65db04163cfb33158b +size 24804 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa107028257ebe7c930ad744f9dbcc06c1f158b3 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a10085861a7fc603046cf512c34205bb1a5973dd8483f152324e6fbf0160ef30 +size 48888 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..825dc0cf1f16be0517305aedf2bd6a9afa0be140 --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c064d44fa6cb92f3d4eef8db9e6da9e12c0ec24878606a083d9ce9c873c92711 +size 98022 diff --git a/marked/M/T-REC-M.3343-200701-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/M/T-REC-M.3343-200701-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..418ad4123f437847924e16ece11004cca928692f --- /dev/null +++ b/marked/M/T-REC-M.3343-200701-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cefd4e725751223f5942c7421e9e05cb8916003419604d8b5e46dcc4807ee56a +size 34462 diff --git a/marked/M/T-REC-M.3344-201101-I_PDF-E/raw.md b/marked/M/T-REC-M.3344-201101-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24e10e037bd5f7f6ed59320020a1cc8ed0c22af7 --- /dev/null +++ b/marked/M/T-REC-M.3344-201101-I_PDF-E/raw.md @@ -0,0 +1,2931 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3344** + +(01/2011) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Requirements and analysis for NGN +appointment management across the business- +to-business and customer-to-business +interfaces** + +Recommendation ITU-T M.3344 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3344 + +# Requirements and analysis for NGN appointment management across the business-to-business and customer-to-business interfaces + +## Summary + +Recommendation ITU-T M.3344 contains the requirements and analysis for appointment management for the business-to-business and customer-to-business interfaces in support of NGN. Appointment management covers appointment processes for managing the establishment of a mutually acceptable appointment time between the service provider (SP) and the service customer (SC). Appointment management is needed for handling visits to shared facilities or customer facilities: for example, to access customer premises, locked engineering or other facilities, or for joint testing between two enterprises. Appointment management can be used in either the service provisioning or the service assurance process. + +The requirements and analysis are provided using the management interface specification methodology described in Recommendation ITU-T M.3020. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3344 | 2008-02-06 | 4 | +| 2.0 | ITU-T M.3344 | 2011-01-13 | 2 | + +## Keywords + +Analysis, appointment, appointment management, NGN, requirement, service customer, service provider. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2011 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Concepts and background..... | 3 | +| 7 Requirements ..... | 5 | +| 7.1 Business level requirements ..... | 5 | +| 7.2 Specification level requirements ..... | 8 | +| 8 Analysis ..... | 25 | +| 8.1 Information object classes ..... | 25 | +| 8.2 Interface definition ..... | 36 | + +## **Introduction** + +This Recommendation contains the requirements and analysis for the appointment management across the business-to-business (B2B) and customer-to-business (C2B) interfaces. + +In a NGN service supply chain, the service customer, the service provider, and the network operator/service provider interwork with each other for service provisioning and service assurance. In both the service provisioning and the service assurance processes, it may be necessary to access the customer premises, locked engineering or other facilities, or to carry out joint testing between two enterprises. So, there are some processes for managing the establishment of a mutually acceptable appointment between two parties which may be service customer and service provider, or network operator/service provider and service provider. This Recommendation includes the requirements and analysis for all of these processes for the exchange of appointment management information across B2B and C2B interfaces in support of NGN. + +# Recommendation ITU-T M.3344 + +## Requirements and analysis for NGN appointment management across the business-to-business and customer-to-business interfaces + +# 1 Scope + +This Recommendation contains the requirements and analysis for the business-to-business (B2B) and customer-to-business (C2B) interfaces of appointment management for NGN. It assumes a multi-service provider environment and is aimed at appointment management to support the deployment of NGN and includes both the B2B and C2B interfaces. + +Appointment management consists of some processes which include scheduling an appointment, confirming an appointment, updating or modifying an appointment, cancelling an appointment, reporting appointment(s), tracking the history of an appointment and retrieving an appointment. For regulatory oversight, it is assumed that detailed record-keeping will be maintained within the service provider (SP) to support the service level agreement (SLA) or regulatory statute. + +Third-party request/response operations are dependent upon the privacy business rules defined in the SC's/SP's contract and consequently are considered out of scope for this Recommendation. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3020] Recommendation ITU-T M.3020 (2010), *Management interface specification methodology*. + +[ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the Management of Next Generation Networks*. + +[ITU-T M.3320] Recommendation ITU-T M.3320 (1997), *Management requirements framework for the TMN X-Interface*. + +[ITU-T M.3340] Recommendation ITU-T M.3340 (2009), *Framework for NGN service fulfilment and assurance management across the business to business and customer to business interfaces*. + +[ITU-T M.3343] Recommendation ITU-T M.3343 (2007), *Requirements and analysis for NGN trouble administration across B2B and C2B interfaces*. + +[ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN*. + +## 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 B2B/C2B interface** [ITU-T M.3060]: Synonymous to X interface. + +**3.1.2 next generation network (NGN)** [ITU-T Y.2001]: A packet-based network able to provide telecommunication services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independent from underlying transport-related technologies. It enables unfettered access for users to networks and to competing service providers and/or services of their choice. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users. + +**3.1.3 network operator** [ITU-T M.3343]: An organization that operates a NGN transport stratum. A network operator may offer both transport stratum and service stratum. A NGN network operator may or may not provide NGN service stratum services. + +**3.1.4 service customer** [ITU-T M.3320]: The Customer is an organization which has a business relationship with a Service Provider for the provision of network services. A Customer may encompass one or more end users of telecommunications services. [ITU-T M.3320] defines this term simply as "customer". + +**3.1.5 service provider** [ITU-T M.3320]: A general reference to an entity who provides telecommunication services to customers and other users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +NOTE – SP and SC used in this Recommendation mean SP role and SC role. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 appointment:** An arrangement between the service provider (SP) and the service customer (SC) which allows the SP to access the SC premises to carry out activities (e.g., install facilities, repair activities, test, etc.) at a particular time and place. + +**3.2.2 time limit:** The time at which the activity is targeted for completion. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +B2B Business-to-business + +C2B Customer-to-business + +NGN Next Generation Networks + +NNI Network Node Interface + +SC Service Customer + +SDP Service Delivery Point + +SLA Service Level Agreement + +SP Service Provider + +UML Unified Modelling Language + +UNI User Network Interface + +## **5 Conventions** + +This Recommendation follows the conventions defined in [ITU-T M.3020]. + +## 6 Concepts and background + +Appointment management covers appointment processes for managing the establishment of a mutually acceptable appointment time between the SP and SC. Appointment management is needed for handling visits to shared facilities or customer facilities: for example, to access customer premises, locked engineering or other facilities, or for joint testing between two enterprises. Appointment management can be used in either the service provisioning or the service assurance process. Appointment management is part of service fulfilment or service assurance as defined in [ITU-T M.3340]. + +There are two types of business context as to B2B/C2B interfaces. One is that the SC role is taken by an end-user entity. Another is that the SC role is taken by another service provider organization in the overall supply chain. + +In the first business context, the service provider needs to access customer premises. The appointment management interface is used to schedule appointments. + +In the second business context, it is possible that a service provider provides a service to the end-user with the co-operation of other service providers or transport providers. The SP providing telecommunication services to the end-user plays a SC role, while other service providers or transport providers play the SP role. The B2B/C2B interface is used to convey appointment management information between the other service providers or transport providers (acting as SP) and the service provider (acting as SC). In the overall supply chain, the SC and SP roles may change depending on the circumstances. However, in any particular situation, even when the SP and the SC are in a peer-to-peer relationship, one entity will play the SC role, while the other will play the SP role. + +It is the responsibility of the SP to perform activities in accordance with the performance limits defined by SLAs or by a regulatory mandate. + +When a regulator defines the time-frame for the SP to perform an activity, the SP may negotiate the time with the SC only within the bounds of the regulatory-defined performance time. In the case of a national provider of services, the SP and SC roles may be performed by the same organization. In that case, the regulator may define, on behalf of the "public" the maximum time allowed for the SP to perform the activity. + +The initial offered time slot by the SP shall be such that the activity must be performed within the SLA or the maximum time allowed by regulatory mandate. + +Co-location is a practice where a service provider will lease space in one of its facilities, e.g., a central office, to another service provider. In co-location, the roles of the SC and SP are reversed. The requirements to support the needs of appointment scheduling for co-location can be met by reversing the roles. + +Figure 1 describes the procedure of the appointment management. This figure provides two columns, the left side shows the activities performed by the SP, and the right side shows the activities performed by the SC. If needed, both the SP and the SC can request an appointment to each other. Before all the time slots for the appointment are provided, the state of appointment is "unscheduled". Here, both the SP and the SC can offer their convenient time slots for the appointment, and they also can accept or deny the time slots offered by the other side. After all the time slots for the appointment are provided and accepted, the SP needs to request the SC to confirm the appointment. If the SC confirms it, the state of appointment changes to "confirmed", and the SP can perform his or her work according to the appointment. Otherwise, the SP and SC must renegotiate until the appointment can be confirmed by the SC. + +![Flowchart of appointment management procedure showing SP and SC activities.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph TD + subgraph SP_activities [SP activities] + SP_Start([Start]) --> SP_Request[SP requests an Appointment to SC] + SP_Offer[SP offers convenient time slots] --> SP_Acceptable{acceptable to SP?} + SP_Acceptable -- No --> SP_Deny[SP denies the time slots] + SP_Acceptable -- Yes --> SP_Accepts[SP accepts the time slots] + SP_RequestConfirm[SP requests SC to confirm the appointment] --> SP_Visit[SP visits the SC's premise & finishes the work] + end + + subgraph SC_activities [SC activities] + SC_Start([Start]) --> SC_Request[SC requests an Appointment to SP] + SC_Offer[SC offers convenient time slots] --> SC_Acceptable{acceptable to SC?} + SC_Acceptable -- No --> SC_Deny[SC denies the time slots] + SC_Acceptable -- Yes --> SC_Accepts[SC accepts the time slots] + SC_Acceptable2{acceptable to SC?} -- No --> SC_Reject[SC rejects the appointment] + SC_Acceptable2 -- Yes --> SC_Confirm[SC confirms the appointment] + end + + SP_Request --> Unscheduled([Appointment unscheduled]) + SC_Request --> Unscheduled + Unscheduled --> SP_Offer + Unscheduled --> SC_Offer + SP_Deny --> Unscheduled + SC_Deny --> Unscheduled + SP_Accepts --> Scheduled([Appointment scheduled & unconfirmed]) + SC_Accepts --> Scheduled + Scheduled --> SP_RequestConfirm + SP_RequestConfirm --> SC_Acceptable2 + SC_Reject --> Unscheduled + SC_Confirm --> Confirmed([Appointment confirmed]) + Confirmed --> SP_Visit + SP_Visit --> Done([Appointment done]) + Done --> End([End]) + +``` + +The flowchart illustrates the procedure of appointment management, divided into SP (Service Provider) activities and SC (Service Consumer) activities. It begins with both SP and SC starting their respective processes. SP requests an appointment to SC, and SC requests an appointment to SP. Both lead to a common state: 'Appointment unscheduled'. From this state, SP offers convenient time slots, and SC offers convenient time slots. SP then checks if the time slots are acceptable to SP. If not, SP denies the time slots, returning to the 'Appointment unscheduled' state. If yes, SP accepts the time slots. SC then checks if the time slots are acceptable to SC. If not, SC denies the time slots, returning to the 'Appointment unscheduled' state. If yes, SC accepts the time slots. Both SP and SC accepting the time slots lead to a common state: 'Appointment scheduled & unconfirmed'. From this state, SP requests SC to confirm the appointment. SC then checks if the appointment is acceptable to SC. If not, SC rejects the appointment, returning to the 'Appointment unscheduled' state. If yes, SC confirms the appointment. This leads to a common state: 'Appointment confirmed'. From this state, SP visits the SC's premise & finishes the work. This leads to a common state: 'Appointment done'. Finally, the process ends. + +Flowchart of appointment management procedure showing SP and SC activities. + +**Figure 1 – Procedure of appointment management** + +## 7 Requirements + +## 7.1 Business level requirements + +### 7.1.1 Requirements + +The appointment management processes between the SP and the SC is part of a business relationship between their organizations. The appointment management processes are concerned with the establishment of mutually acceptable appointment time slots between the SP and the SC. + +#### 7.1.1.1 Appointment scheduling + +Appointment scheduling is a process prior to the appointment confirmation process. The negotiation procedure in the scheduling process between the SP and SC is iterative. + +REQ-AM-FUN-101 Appointment management is appropriate for service ordering (pre-ordering), repairing, and service decommissioning (service termination). + +The SC shall be able to schedule an appointment for the SP to gain access to the SC's premises, and the SP shall be able to schedule an appointment to gain access to the SC's premises, e.g., to install/remove equipment, or where the results of service tests/diagnostics indicate that a site visit is required. + +The SP may be able to offer the SC the convenient time slots for carrying out activities at the SC's premises. + +The SC may be able to offer convenient time slots for the SP to visit the SC's premises. + +Although the time slot(s) is to be negotiated between the SC and the SP, the final determination of the actual appointment time slot is determined by the customer. + +The information of an appointment, when it can be established, contains the following: + +- location to be visited (address, including the premises); +- SDP (service delivery point) (which is a physical entity aware to the SP, maybe UNI, NNI, equipment, etc.); +- time slots for the appointment; +- duration of the appointment. + +When all the above information is agreed by both the SP and the SC, an appointment can be established. + +If the SC requests an appointment beyond the SLA time-scale, despite the SP offering time slots which fall within the SLA, the SP shall not be held responsible for the SLA violation due to SC's choice of a later appointment. + +NOTE 1 – It may be necessary for the SP to request from the SC several time slots to carry out an activity at each SC's location. + +NOTE 2 – Time slot reservation is outside the scope of this interface. + +REQ-AM-FUN-102 The SC shall be able to accept or decline the time slots offered by the SP. The SP shall offer available time slot(s) within the SLA time-scale for the service. + +The SC should be able to offer the available access time slot(s) from the SC's point of view for each specified location by request. + +REQ-AM-FUN-103 The SP shall be able to accept or decline the access time slot(s) offered by the SC. + +When the SC offers less time than is actually required for the SP to perform the activity, the SP must, in this case, be able to negotiate additional time slot(s) from the SC in order to perform the activity. In this situation, the SP may offer time slots which the SC may select or the SP may request additional time slots from the SC, which the SP will select, and the SC will confirm. + +Although the time slot(s) is to be negotiated between the SC and the SP, the final determination of the actual appointment time slot(s) is determined by the customer. + +If the SP is not allowed sufficient time by the SC to perform an activity, such that an objective within the SLA (or a regulatory statute) will be missed, then the SP shall not be held responsible for the SLA violation due to the SC's inability to provide an acceptable appointment. This may occur when the SP is performing chargeable work, where the cost authorized by the SC is insufficient to cover the required work. + +REQ-AM-FUN-104 When the SP is waiting for the response from the SC, the SLA violation clock should stop so that the SP will not be punished as violating the SLA when an appointment cannot be arranged due to the SC's reason. + +#### 7.1.1.2 Appointment confirmation + +REQ-AM-FUN-201 Confirmation of the appointment slot(s) agreement/reservation by the SC shall form a bilateral agreement. + +REQ-AM-FUN-202 If the appointments/access time offered by the SC does not enable the SP to fulfil its contractual obligations, the SP shall be able to reject the appointments. The rejection reason must be recorded as being caused by the SC. For example, the access times are outside the SLA working hours. + +REQ-AM-FUN-203 If the appointment is denied by the SC, the SP shall be able to request other appointment time slots until the appointment is mutually accepted. + +#### 7.1.1.3 Appointment change + +REQ-AM-FUN-301 Prior to the appointment time, and subject to the terms specified in the contract, the SP or SC can modify the information related to the appointment, such as additional information, contact change, etc. This information may be attributes of the appointment derived from the order or trouble ticket which is made available to the SP field engineer. + +REQ-AM-FUN-302 Prior to the appointment time, and subject to the terms specified in the contract, the SP or SC may request to reschedule an agreed appointment (time, location). The reason why the SP or SC wishes to reschedule the appointment shall be given. The SC shall not arbitrarily reschedule an appointment so as to cause the SP to miss the SLA or a regulatory statute. + +REQ-AM-FUN-303 Either the SP or the SC shall be able to accept or decline the appointment change request. If the change request is denied, the SP or SC shall reschedule the appointment until the appointment is mutually agreed. + +- REQ-AM-FUN-304 The SP or the SC shall be able to request additional time slots during the period when an appointment is being performed. + +#### 7.1.1.4 Appointment cancellation + +- REQ-AM-FUN-401 Prior to the appointment time, and subject to the terms specified in the contract, the SP or the SC may request the cancellation of an agreed appointment. The reason why the SP or SC cancels the appointment shall be given. The SC shall not arbitrarily cancel an appointment so as to cause the SP to miss the SLA or a regulatory statute. +- REQ-AM-FUN-402 On receipt of the appointment cancellation request, the receiving party shall acknowledge and accept or reject the request. +- The SP or the SC accepting the cancellation shall provide a tracking mechanism to assure against repudiation and non-repudiation. +- REQ-AM-FUN-403 The SP may only cancel an appointment it sets up. + +#### 7.1.1.5 Appointment report + +- REQ-AM-FUN-501 The SP or SC may be able to notify each other of the failures to keep the appointment. +- REQ-AM-FUN-502 The SP may, at its option, periodically provide an appointment report to the SC. +- REQ-AM-FUN-503 The SP shall provide, at the request of the SC, a report of the activities performed by the SP at the SC's location(s) as specified in the SLA. + +#### 7.1.1.6 Appointment information retrieval + +- REQ-AM-FUN-601 The SCs shall be able to query the complete description of a specific set of their current or historical appointments. The period of the retention of these records, by the SP, shall be subject to the SLA or regulatory statute. +- The filters to be applied to the information can be any relevant parameter exchanged as part of the interaction operations during scheduling an appointment, confirming an appointment, updating or modifying an appointment, or cancelling an appointment. +- REQ-AM-FUN-602 The SC shall be able to obtain detailed tracking information about the status transitions of an appointment (including time-stamps). + +### 7.1.2 Actor roles + +The capabilities described in this Recommendation are available to the relevant service provider and service customer. + +Service provider: The entity performing the service provider role. + +Service customer: The entity performing the service customer role. + +### 7.1.3 Telecommunication resources + +The SC's facilities are viewed as relevant telecommunication resources in this Recommendation. + +### 7.1.4 High-level use case diagrams + +This clause contains a high-level use case diagram that summarizes the functionality and interfaces of the appointment management as shown in Figure 2. + +![High-level use case diagram showing interactions between SC (Service Customer) and SP (Service Provider) actors through six use cases: Appointment scheduling, Appointment confirming, Appointment change, Appointment cancellation, Appointment report, and Appointment information retrieval. The diagram is labeled M.3344(11)_F02.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + SC[SC] --> US1([Appointment scheduling]) + SP[SP] --> US1 + SC --> US2([Appointment confirming]) + SP --> US2 + SC --> US3([Appointment change]) + SP --> US3 + SC --> US4([Appointment cancellation]) + SP --> US4 + SC --> US5([Appointment report]) + SP --> US5 + SC --> US6([Appointment information retrieval]) + SP --> US6 + +``` + +High-level use case diagram showing interactions between SC (Service Customer) and SP (Service Provider) actors through six use cases: Appointment scheduling, Appointment confirming, Appointment change, Appointment cancellation, Appointment report, and Appointment information retrieval. The diagram is labeled M.3344(11)\_F02. + +**Figure 2 – High-level use case diagram** + +## 7.2 Specification level requirements + +### 7.2.1 Specification level use case diagram + +Figures 3 and 4 give the specification-level use-case diagrams. Use cases initiated by the SP are shown in Figure 3 first followed by use cases initiated by the SC in Figure 4. Use case descriptions are provided in clause 7.2.2 for every use case pictured in these diagrams. + +![A diagram showing a stick figure labeled 'SC' on the left connected by arrows to eleven yellow ovals representing use cases. The use cases are: SP notify available time slot(s), SP requests additional time slots, SP request appointment availability, SP accept/decline available time slot(s), SP request appointment confirmation, SP request appointment change, SP request appointment cancellation, SP notify modification of appointment attribute value, SP report appointment, SP notify of failure to keep appointment, and SP notify appointment cancellation approved/denied.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram illustrates the relationship between a Service Consumer (SC) and various Service Provider (SP) initiated use cases. The SC is represented by a stick figure on the left, and the use cases are represented by yellow ovals. Arrows point from each use case to the SC, indicating that the SC is the recipient of these actions. + +- SP notify available time slot(s) +- SP requests additional time slots +- SP request appointment availability +- SP accept/decline available time slot(s) +- SP request appointment confirmation +- SP request appointment change +- SP request appointment cancellation +- SP notify modification of appointment attribute value +- SP report appointment +- SP notify of failure to keep appointment +- SP notify appointment cancellation approved/denied + +A diagram showing a stick figure labeled 'SC' on the left connected by arrows to eleven yellow ovals representing use cases. The use cases are: SP notify available time slot(s), SP requests additional time slots, SP request appointment availability, SP accept/decline available time slot(s), SP request appointment confirmation, SP request appointment change, SP request appointment cancellation, SP notify modification of appointment attribute value, SP report appointment, SP notify of failure to keep appointment, and SP notify appointment cancellation approved/denied. + +**Figure 3 – SP initiated use cases** + +![A diagram showing SC initiated use cases. An actor labeled 'SC' is connected to eleven use case ellipses. The use cases are: SC requests additional time slots, SC initiates the establishment of an appointment, SC notify available time slot(s), SC notify appointment approved/denied, SC request modification of appointment attribute value, SC request appointment change, SC request appointment cancellation, SC notify appointment cancellation accepted/rejected, SC accept/decline available time slots, SC notify of failure to keep appointment, SC get appointment report, SC retrieve appointment(s) tracking information, and SC retrieve appointment(s) information.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +graph LR + SC((SC)) --> UC1[SC requests additional time slots] + SC --> UC2[SC initiates the establishment of an appointment] + SC --> UC3[SC notify available time slot(s)] + SC --> UC4[SC notify appointment approved/denied] + SC --> UC5[SC request modification of appointment attribute value] + SC --> UC6[SC request appointment change] + SC --> UC7[SC request appointment cancellation] + SC --> UC8[SC notify appointment cancellation accepted/rejected] + SC --> UC9[SC accept/decline available time slots] + SC --> UC10[SC notify of failure to keep appointment] + SC --> UC11[SC get appointment report] + SC --> UC12[SC retrieve appointment(s) tracking information] + SC --> UC13[SC retrieve appointment(s) information] + +``` + +A diagram showing SC initiated use cases. An actor labeled 'SC' is connected to eleven use case ellipses. The use cases are: SC requests additional time slots, SC initiates the establishment of an appointment, SC notify available time slot(s), SC notify appointment approved/denied, SC request modification of appointment attribute value, SC request appointment change, SC request appointment cancellation, SC notify appointment cancellation accepted/rejected, SC accept/decline available time slots, SC notify of failure to keep appointment, SC get appointment report, SC retrieve appointment(s) tracking information, and SC retrieve appointment(s) information. + +**Figure 4 – SC initiated use cases** + +### 7.2.2 Use cases + +#### 7.2.2.1 SC Initiate the establishment of an appointment + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | When the SC initiates ordering (pre-ordering), repairing, and service decommissioning, and it is necessary for the SP to access the SC's premises; the SC shall provide an appointment request to the SC. | | +| Actors and roles | The SP is the consumer of the request from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SC needs the SP to access the SC's premises. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
An SLA or contract exists between the SC and the SP, a regulatory statute may exist which specifies additional requirements. | | +| Begins when | The SC needs to schedule or reschedule an appointment. | | +| Step 1 (M) | 1) (M) The SC initiates a request to the SP for appointment establishment. The SC shall specify certain parameters as part of the request, including the type of the request (ordering, pre-ordering, repairing, and service decommissioning).
When it is for pre-ordering (ordering), service ID, SAP (physical address, CLLI code), service priority, and service customer information should be included.
When it is for repairing, service ID, customer name, other information ([ITU-T M.3343] mandatory information) should be included.
When it is for service decommissioning, service ID, customer name, reason code (optional), and service termination date should be included.
2) (O) The SC may offer his or her available time slot(s) in the request for negotiation purposes. | | +| Ends when | The request is emitted by the SC. | | +| Exceptions | – A network problem exists.
– Missing or incorrect parameter values.
– The SP is unable to respond to the request. | | +| Post-conditions | The SP receives the request. | | +| Traceability | REQ-AM-FUN-101 | | + +#### 7.2.2.2 SP Request appointment availability + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | When it is necessary for the SP to access the SC's premises, the SP shall provide an appointment request to the SC.
During the scheduling or rescheduling process, the SP shall enquire about the SC's available time slots for locations where the SP needs to have access. | | +| Actors and roles | The SC is the consumer of the request from the SP. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Telecom resources | Any SC's facility. | | +| Assumptions | The SP needs to access the SC's premises. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
An SLA or contract exists between the SC and the SP; a regulatory statute may exist which specifies additional requirements. | | +| Begins when | The SP needs to schedule or reschedule an appointment. | | +| Step 1 (M) | 1) (M) The SP initiates a request to the SC for available time slots for each location where the SP needs to have access. The SP shall specify certain parameters as part of the request (e.g., ID, activities to be performed, location(s) to be accessed, time limit, severity, estimated duration, contact person, etc.).
2) (O) The SP may offer his or her available time slot(s) in the request for negotiation purposes.
3) (O) If a time slot has already been agreed by the SP and SC, that time slot should be indicated in the request. | | +| Ends when | The request is emitted by the SP. | | +| Exceptions | – A network problem exists.
– Missing or incorrect parameter values.
– The SC is unable to respond to the request. | | +| Post-conditions | The SC receives the request. | | +| Traceability | REQ-AM-FUN-101, REQ-AM-FUN-202, REQ-AM-FUN-203 | | + +#### 7.2.2.3 SP Notify available time slot(s) + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SP offers the available time slots for the specific location(s) associated with an appointment. | | +| Actors and roles | The SC is the consumer of the notification from the SP. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SP had received a Request appointment availability from the SC. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SP offers available time slots. | | +| Step 1 (M) | The SP offers a set of available time slots for the specific location(s) associated with the appointment. The parameters (e.g., appointment ID, location(s), available time slot(s), etc.) should be specified. | | +| Ends when | The notification is emitted by the SP. | | +| Exceptions | – A network problem exists.
– Invalid appointment ID.
– Missing or incorrect parameter values. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------|-------------------------| +| Post-conditions | The SC is informed of the SP available time slot(s). | | +| Traceability | REQ-AM-FUN-101 | | + +#### 7.2.2.4 SC Notify available time slot(s) + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SC offers the available time slots for the specific location(s) associated with an appointment by a request to the SP. | | +| Actors and roles | The SP is the consumer of the notification from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SC had received a Request appointment availability from the SP. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC offers available time slots. | | +| Step 1 (M) | The SC offers a set of available time slots for the specific location(s) associated with the appointment. The parameters (e.g., appointment ID, location(s), available time slot(s), etc.) should be specified. | | +| Ends when | The notification is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The SP is informed of the SC available time slot(s). | | +| Traceability | REQ-AM-FUN-102 | | + +#### 7.2.2.5 SP Accept/decline available time slot(s) + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| Goal | The SP accepts or declines the time slots offered by the SC in the notification of available time slots, or in the request for additional time slots. | | +| Actors and roles | The SC is the consumer of the notification from the SP. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SP had received a notification of the available time slots from the SC. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SP accepts or declines the offered time slots. | | +| Step 1 (M) | The SP accepts or declines the time slots offered by the SC in the notification of available time slots. | Request appointment availability | +| Ends when | The notification is emitted by the SP. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The SC is informed of the notification from the SP.
The SC received a Request appointment availability if the SP had sent a Request appointment availability to the SC. | | +| Traceability | REQ-AM-FUN-103 | | + +#### 7.2.2.6 SC Accept/decline available time slot(s) + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SC accepts or declines the time slots offered by the SP in the notification of available time slots, or in the request for additional time slots. | | +| Actors and roles | The SP is the consumer of the notification from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SC had received a notification of available time slots from the SP. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC accepts or declines the offered time slots. | | +| Step 1 (M) | The SC accepts or declines the time slots offered by the SP in the notification of available time slots, or in the request for additional time slots. | | +| Ends when | The notification is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The SP is informed of the notification from the SC. | | +| Traceability | REQ-AM-FUN-102 | | + +#### 7.2.2.7 SP Request appointment confirmation + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SP asks the SC to confirm all the time slots and locations related to an appointment. | | +| Actors and roles | The SC is the consumer of the request from the SP. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SP can select the appropriate time slots which can satisfy both the SP and SC through negotiation. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Begins when | The SP selects the appropriate time slots. | | +| Step 1 (M) | The SP initiates a request to the SC for appointment confirmation. All the appointment time slots should be indicated in the request. | | +| Ends when | The request is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The request is received by the SC. | | +| Traceability | REQ-AM-FUN-201 | | + +#### 7.2.2.8 SC Notify appointment approved/denied + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | Upon receiving a request confirming an appointment or receiving a request changing an appointment, the SC notifies the SP of either approving or denying the time slots indicated in the request. | | +| Actors and roles | The SP is the consumer of the notification from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SC had received a request confirming an appointment or changing an appointment from the SP. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC approves or denies the appointment. | | +| Step 1 (M) | The SC accepts or denies each time slot indicated in the request. | | +| Ends when |

The notification is emitted by the SC.

NOTE – If all the time slots are accepted by the SC, then the appointment is mutually accepted. If the appointment is denied by the SC, the SP can reject the appointment and the rejection reason must be recorded as being caused by the SC. Then the SP can invoke the use case "SP Request appointment availability" to request other appointment time slots until the appointment is mutually accepted.

| | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The SP is informed of the result. | | +| Traceability | REQ-AM-FUN-201, REQ-AM-FUN-202, REQ-AM-FUN-303 | | + +#### 7.2.2.9 SC Request modification of appointment attribute value + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | Prior to the appointment time, the SC can modify the information related to the appointment, e.g., additional information, contact change, etc.
NOTE – This use case cannot be used to modify such parameters as locations and times. | | +| Actors and roles | The SP is the consumer of the request from the SC and the SP modifies the parameters of the request. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment to be modified is confirmed. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC modifies some parameters associated with an appointment. | | +| Step 1 (M) | The SC shall specify certain parameters as part of the request (e.g., ID of the appointment for which parameters are to be modified, and new values for the parameters to be modified, etc.). This information may be attributes of the appointment derived from the order or trouble ticket which is made available to the SP field engineer. | | +| Ends when | The SP returns the result to the SC that the new parameter value(s) are being changed. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
  • – Requested appointment is not permitted to be modified now according to the predefined contract.
| | +| Post-conditions | The parameter value(s) of the appointment for which the modification was requested is(are) updated. | | +| Traceability | REQ-AM-FUN-301 | | + +#### 7.2.2.10 SP Notify modification of appointment attribute value + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | Prior to the appointment time, the SP can modify the information related to the appointment, e.g., additional information, contact change, etc.
NOTE – This use case cannot be used to modify such parameters as locations and times. | | +| Actors and roles | The SC is the consumer of the notification from the SP. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment to be modified is confirmed. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SP modifies some parameters associated with an appointment. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 (M) | The SP shall specify certain parameters as part of the notification (e.g., ID of the appointment for which parameters are to be modified, new values for the parameters to be modified, etc.). This information may be attributes of the appointment derived from the order or trouble ticket which is made available to the SP field engineer. | | +| Ends when | The notification is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
  • – Requested appointment is not permitted to be modified now according to the predefined contract.
| | +| Post-conditions | The SC is informed of the new parameter values. | | +| Traceability | REQ-AM-FUN-301 | | + +#### 7.2.2.11 SP Request appointment change + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| Goal | Prior to the appointment time, the SP may request changing times or locations associated with an appointment. This use case is valid until the time interval before the appointment, specified in the SLA or by a regulatory statute. | | +| Actors and roles | The SC is the consumer of the request from the SP. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment to be changed is confirmed. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
A predefined contract about the appointment service has been established, and the interval prior to the appointment has been specified. | | +| Begins when | The SP initiates a change of an appointment. | | +| Step 1 (M) |
  1. 1) (M) The SP specifies certain parameters as part of the request (e.g., ID of the appointment, the time slot(s) and location(s) to be modified, etc.) in the request. The reason why the SP changes the appointment shall be specified.
  2. 2) (O) The SP can invoke the use case "SP Request appointment availability" to reschedule the appointment.
| Request appointment availability | +| Ends when | The request is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
  • – Requested appointment is not permitted to be changed now according to the predefined contract.
| | +| Post-conditions | The request is received by the SC. | | +| Traceability | REQ-AM-FUN-302 | | + +#### 7.2.2.12 SC Request appointment change + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | Prior to the appointment time, the SC may request changing times or locations associated with an appointment. | | +| Actors and roles | The SP is the consumer of the request from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment to be changed is confirmed. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
A predefined contract about the appointment service has been established, and the interval prior to the appointment has been specified. | | +| Begins when | The SC initiates a change of an appointment. | | +| Step 1 (M) | The SC specifies certain parameters as part of the request (e.g., ID of the appointment, the time slot(s) and/or location(s) to be modified, etc.) in the request. The reason why the SC changes the appointment shall be specified. | | +| Ends when | The request is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
  • – Requested appointment is not permitted to be changed now according to the predefined contract.
| | +| Post-conditions | The request is received by the SP. | | +| Traceability | REQ-AM-FUN-302 | | + +#### 7.2.2.13 SP Request appointment cancellation + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | Prior to the appointment time, the SP initiates a request for cancelling an appointment. | | +| Actors and roles | The SC is the consumer of the request. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment to be cancelled exists. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
A predefined contract about the appointment service has been established, and the interval prior to the appointment has been specified. | | +| Begins when | The SP initiates a request for cancelling an appointment. | | +| Step 1 (M) | The SP shall specify certain parameters as part of the request (e.g., ID of the appointment, the reason why the SP cancels the appointment, etc.). | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Ends when | The request is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Contract violation of time interval to cancel an appointment.
| | +| Post-conditions | The SC should return a response to the SP indicating acknowledgement. | | +| Traceability | REQ-AM-FUN-401 | | + +#### 7.2.2.14 SC Request appointment cancellation + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | Prior to the appointment time, the SC initiates a request cancelling an appointment. | | +| Actors and roles | The SP is the consumer of the request from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment to be cancelled exists. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
A predefined contract about the appointment service has been established, and the interval prior to the appointment has been specified. | | +| Begins when | The SC initiates a request for cancelling an appointment. | | +| Step 1 (M) | The SC shall specify certain parameters as part of the request (e.g., ID of the appointment, the reason why the SC cancels the appointment, etc.). | | +| Ends when | The request is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Failure due to contract violation of interval.
| | +| Post-conditions | The SP should return a response to the SC indicating acknowledgement. | | +| Traceability | REQ-AM-FUN-401 | | + +#### 7.2.2.15 SC Notify appointment cancellation accepted/rejected + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | After receiving a request for cancelling an appointment initiated by the SP, the SC may accept or reject the request. | | +| Actors and roles | The SP is the consumer of the notification. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SC had received a request for cancelling an appointment from the SP. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
A predefined contract about the appointment service has been established, and the interval prior to the appointment has been specified. | | +| Begins when | The SC accepts or denies the request. | | +| Step 1 (M) | The SC accepts or rejects the request for cancelling an appointment. The appointment ID should be specified in the notification. | | +| Ends when | The notification is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Invalid reject reason code.
| | +| Post-conditions | The SP is informed of the result. | | +| Traceability | REQ-AM-FUN-402 | | + +#### 7.2.2.16 SP Notify appointment cancellation accepted/rejected + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | After receiving a request cancelling an appointment initiated by the SC, the SP shall accept or reject the request. | | +| Actors and roles | The SC is the consumer of the notification. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SP had received the request for cancelling an appointment from the SC. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system.
A predefined contract about the appointment service has been established, and the interval prior to the appointment has been specified. | | +| Begins when | The SP accepts or denies the request for cancelling an appointment. | | +| Step 1 (M) | The SP accepts or rejects the request cancelling an appointment. The appointment ID should be specified in the notification. | | +| Ends when | The notification is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Invalid reject reason code.
| | +| Post-conditions | The SC receives the notification. | | +| Traceability | REQ-AM-FUN-402 | | + +#### 7.2.2.17 SC Notify failure to keep appointment + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | If the SP fails to keep an agreed appointment, the SC should notify the SP of the failure. | | +| Actors and roles | The SP is the consumer of the notification. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SP failed to keep an appointment. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC notifies the SP of the failure to keep an appointment. | | +| Step 1 (M) | The SC shall specify certain parameters as part of the notification (e.g., ID of the appointment, locations, times, etc.). | | +| Ends when | The notification is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Incorrect parameters.
| | +| Post-conditions | The SP is informed of the failure. | | +| Traceability | REQ-AM-FUN-501 | | + +#### 7.2.2.18 SP Notify failure to keep appointment + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | If the SC fails to keep an agreed appointment, the SP should notify the SC of the failure. | | +| Actors and roles | The SC is the consumer of the notification. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The SC failed to keep the appointment. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SP notifies the SC of the failure to keep an appointment. | | +| Step 1 (M) | The SP shall specify certain parameters as part of the notification (e.g., ID of the appointment, locations, times, etc.). | | +| Ends when | The notification is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Incorrect parameters.
| | +| Post-conditions | The SC is informed of the failure. | | +| Traceability | REQ-AM-FUN-501 | | + +#### 7.2.2.19 SP Report appointment + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SP should give an appointment report to the SC periodically or non-periodically. | | +| Actors and roles | The SC is the consumer of the report. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment is created. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SP submits an appointment report. | | +| Step 1 (M) | The SP reports the appointment information (e.g., activities carried out, actual duration, keep or fail, etc.). | | +| Ends when | The report is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Invalid parameters.
| | +| Post-conditions | The SC is informed of the report. | | +| Traceability | REQ-AM-FUN-502, REQ-AM-FUN-503 | | + +#### 7.2.2.20 SC Get appointment report + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SC can request a report for activities performed by the SP at the SC's location(s) for a certain period, as specified in the SLA. | | +| Actors and roles | The SP is the consumer of the request. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The appointment is created, and the SC has signed a SLA which has the terms about the appointment report with the SP. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC sends a request to get a report of the specified appointment. | | +| Step 1 (M) |

1) (M) The SC sends a request to the SP to get the appointment report, and the following parameters should be provided in the request:

  • – appointment ID,
  • – start time,
  • – stop time, etc.

2) The SP will return the appointment report when receiving the request from the SC.

| | +| Ends when | The SP returns the report of the requested appointment. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
| | +| Post-conditions | The SC receives the complete report of the requested appointments. | | +| Traceability | REQ-AM-FUN-503 | | + +#### 7.2.2.21 SC Retrieve appointment(s) tracking information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SC can query the complete tracking information of one or more current or historical appointments. | | +| Actors and roles | The SP is the consumer of the request. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | Appointments were created. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC sends a query request to receive detailed tracking information of the specific appointments. | | +| Step 1 (M) | 1) (M) The SC specifies certain parameters as part of the request (i.e., filter definition for the specific appointment set, etc.).
2) The request is emitted by the SC. | | +| Ends when | The SP returns the detailed tracking information of the requested appointments. | | +| Exceptions |
  • – A network problem exists.
  • – Incorrect filter definition.
  • – Invalid parameters.
  • – Invalid appointment ID.
| | +| Post-conditions | The SC receives the complete information list of the requested appointments. | | +| Traceability | REQ-AM-FUN-602 | | + +#### 7.2.2.22 SC Retrieve appointment(s) information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The SC can query the complete description of one or more current or historical appointments. | | +| Actors and roles | The SP is the consumer of the request. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | Appointments were created. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system. | | +| Begins when | The SC sends a query request to receive information of the specific appointments. | | +| Step 1 (M) | 1) (M) The SC specifies certain parameters as part of the request (i.e., filter definition for the specific appointment set, etc.).
2) The request is emitted by the SC. | | +| Ends when | The SP returns the list of appointments to complete the information. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions |
  • – A network problem exists.
  • – Incorrect filter definition.
  • – Invalid parameters.
| | +| Post-conditions | The SC receives the complete information list of the requested appointments. | | +| Traceability | REQ-AM-FUN-601 | | + +#### 7.2.2.23 SP Request additional time slots + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | During the period when an appointment is being performed, the SP can request additional time slots. | | +| Actors and roles | The SC is the consumer of the request from the SP. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The confirmed time slots for the appointment are insufficient to finish the work. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system, and the appointment is being performed. | | +| Begins when | The SP initiates a request for additional time slots. | | +| Step 1 (M) | The SP offers a set of additional time slots for the specific location(s) associated with the appointment. The parameters (e.g., appointment ID, location(s), additional time slot(s), etc.) should be specified. | | +| Ends when | The request is emitted by the SP. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The request is received by the SC. | | +| Traceability | REQ-AM-FUN-304 | | + +#### 7.2.2.24 SC Request additional time slots + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | During the period when an appointment is being performed, the SC can request additional time slots. | | +| Actors and roles | The SP is the consumer of the request from the SC. | | +| Telecom resources | Any SC's facility. | | +| Assumptions | The confirmed time slots for the appointment are insufficient to finish the work. | | +| Pre-conditions | There is an open communication channel between the SP management system and the SC management system, and the appointment is being performed. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Begins when | The SC initiates request for additional time slots. | | +| Step 1 (M) | The SC offers a set of additional time slots for the specific location(s) associated with the appointment. The parameters (e.g., appointment ID, location(s), additional time slot(s), etc.) should be specified. | | +| Ends when | The request is emitted by the SC. | | +| Exceptions |
  • – A network problem exists.
  • – Invalid appointment ID.
  • – Missing or incorrect parameter values.
| | +| Post-conditions | The request is received by the SP. | | +| Traceability | REQ-AM-FUN-304 | | + +# 8 Analysis + +## 8.1 Information object classes + +### 8.1.1 Imported information entities and local labels + +There are no imported information entities here. + +### 8.1.2 Class diagram + +This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of the various aspects of these support object classes. + +#### 8.1.2.1 Attributes and relationships + +![UML class diagram showing Appointment management information object classes and their relationships.](d9843ac5dfc4bbe9e4d21b8898723b5e_img.jpg) + +``` + +classDiagram + class AppointmentHistoryRecord { + +appointmentHistoryID + +appointmentState + +appointmentStateTime + +appointmentStateTransitionReason + } + class AppointmentReport { + +appointmentReportID + +reportContent + } + class Appointment { + +appointmentID + +appointmentPremiseList + +spContactPerson + +spContactInfo + +scContactPerson + +scContactInfo + +appointmentState + +appointmentStateTime + +appointmentStateTransitionReason + +reportPeriod + +appointmentHistoryList + +additinalInfo + +slaViolationIndicator + +requirementFulfilledIndicator + } + class AppointmentPremise { + +appointmentPremiseID + +location + +appointmentTimeSlotList + +visitPurpose + +estimatedDuration + } + class AppointmentTimeSlot { + +appointmentTimeSlotID + +planBeginTime + +planEndTime + +actualBeginTime + +actualEndTime + +suggestPerson + +respondPerson + +slotState + +slotStateTime + +activityInfo + +failtoKeepIndicator + } + + AppointmentHistoryRecord "0..n" -- "1" Appointment + AppointmentReport "0..n" -- "1" Appointment + AppointmentPremise "1" -- "1..n" Appointment + AppointmentTimeSlot "1" -- "1..n" Appointment + +``` + +UML class diagram showing Appointment management information object classes and their relationships. + +Figure 5 – Appointment management information object classes + +#### 8.1.2.2 Inheritance + +![UML class diagram showing Appointment management IOC inheritance hierarchy.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` + +classDiagram + class Top + class AppointmentAgent + class AppointmentPremise + class AppointmentTimeSlot + class Appointment + class AppointmentHistoryRecord + + Top <|-- AppointmentAgent + Top <|-- AppointmentPremise + Top <|-- AppointmentTimeSlot + Top <|-- Appointment + Top <|-- AppointmentHistoryRecord + +``` + +UML class diagram showing Appointment management IOC inheritance hierarchy. + +Figure 6 – Appointment management IOC inheritance + +### 8.1.3 Information object class definitions + +| Class name | Qualifier | Requirement IDs | +|--------------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Appointment | M | REQ-AM-FUN-101, REQ-AM-FUN-102, REQ-AM-FUN-103, REQ-AM-FUN-201, REQ-AM-FUN-301, REQ-AM-FUN-303, REQ-AM-FUN-401, REQ-AM-FUN-402, REQ-AM-FUN-501, REQ-AM-FUN-602 | +| AppointmentPremise | M | REQ-AM-FUN-101, REQ-AM-FUN-102, REQ-AM-FUN-103 | +| AppointmentTimeSlot | M | REQ-AM-FUN-101, REQ-AM-FUN-102, REQ-AM-FUN-103, REQ-AM-FUN-501, REQ-AM-FUN-503 | +| AppointmentReport | M | REQ-AM-FUN-502, REQ-AM-FUN-503 | +| AppointmentHistoryRecord | M | REQ-AM-FUN-601, REQ-AM-FUN-602 | + +#### 8.1.3.1 Appointment + +##### 8.1.3.1.1 Definition + +Appointment contains the basic attributes (such as appointmentID, contact person, appointmentState, appointmentStateTransitionReason, etc.) of an appointment. It is created when the SP or the SC wants to make an appointment with the other side. + +##### 8.1.3.1.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------------------------|-------------------|----------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------| +| appointmentID | M | – | – | REQ-AM-FUN-101 | +| appointmentPremiseList | M | – | – | REQ-AM-FUN-101 | +| spContactPerson | O | – | – | REQ-AM-FUN-301 | +| spContactInfo | O | – | – | REQ-AM-FUN-301 | +| scContactPerson | O | – | – | REQ-AM-FUN-301 | +| scContactInfo | O | – | – | REQ-AM-FUN-301 | +| appointmentState | M | – | – | REQ-AM-FUN-101, REQ-AM-FUN-102, REQ-AM-FUN-103, REQ-AM-FUN-201, REQ-AM-FUN-401, REQ-AM-FUN-402, REQ-AM-FUN-501, REQ-AM-FUN-602 | +| appointmentStateTime | M | – | – | REQ-AM-FUN-602 | +| appointmentStateTransitionReason | M | – | – | REQ-AM-FUN-202
REQ-AM-FUN-302
REQ-AM-FUN-401 | +| reportPeriod | O | – | – | REQ-AM-FUN-502 | +| appointmentHistoryList | M | – | – | REQ-AM-FUN-602 | + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-------------------------------|-------------------|----------------|-----------------|-----------------| +| additionalInfo | O | – | – | REQ-AM-FUN-301 | +| slaViolationIndicator | M | – | – | REQ-AM-FUN-104 | +| requirementFulfilledIndicator | M | – | – | REQ-AM-FUN-101 | + +##### 8.1.3.1.3 State diagram + +The appointment state is described in Figure 7: + +![State diagram for Appointment class showing states: Unscheduled, Scheduling, Confirming, Rescheduling, Confirmed, Cancelling, Cancelled, Performing, Done, FailedToKeep, and NewTimeSlotsUnconfirmed. Transitions include create, offer time slots, reject, accept, request to reschedule, confirm, request to confirm, request to cancel, and events like 'When the first time slot begins time is reached'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Unscheduled : create + Unscheduled --> Scheduling : offer time slots + Unscheduled --> Rescheduling : reject + Scheduling --> Unscheduled : reject + Scheduling --> Confirming : offer time slots, accept or deny time slots + Scheduling --> Cancelling : request to cancel + Confirming --> Unscheduled : reject + Confirming --> Rescheduling : request to confirm + Confirming --> Confirmed : confirm + Rescheduling --> Unscheduled : accept + Rescheduling --> Confirmed : reject + Rescheduling --> Cancelling : request to reschedule + Confirmed --> Performing : When the first time slot begins time is reached + Confirmed --> Cancelling : request to cancel + Cancelling --> Unscheduled : reject + Cancelling --> Confirmed : reject + Cancelling --> Cancelled : accept + Cancelling --> Scheduling : request to cancel + Performing --> Done : When all the work is done according to the appointment + Performing --> FailedToKeep : When the SP or SC fails to keep the appointment + Performing --> NewTimeSlotsUnconfirmed : All of the additional time slots are accepted or denied + NewTimeSlotsUnconfirmed --> Performing : SP or SC requests additional time slots + Done --> [*] + FailedToKeep --> [*] + +``` + +State diagram for Appointment class showing states: Unscheduled, Scheduling, Confirming, Rescheduling, Confirmed, Cancelling, Cancelled, Performing, Done, FailedToKeep, and NewTimeSlotsUnconfirmed. Transitions include create, offer time slots, reject, accept, request to reschedule, confirm, request to confirm, request to cancel, and events like 'When the first time slot begins time is reached'. + +Figure 7 – Appointment state diagram + +#### 8.1.3.2 AppointmentPremise + +##### 8.1.3.2.1 Definition + +The AppointmentPremise class contains information describing the locations which the SP needs to visit, and the reasons for visiting these locations. For each location to visit, an AppointmentPremise object is created. + +##### 8.1.3.2.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-------------------------|-------------------|----------------|-----------------|-----------------------------------| +| appointmentPremiseID | M | – | – | REQ-AM-FUN-101,
REQ-AM-FUN-102 | +| location | M | – | – | REQ-AM-FUN-101,
REQ-AM-FUN-102 | +| appointmentTimeSlotList | M | – | – | REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| visitPurpose | M | – | – | REQ-AM-FUN-101 | +| estimatedDuration | O | – | – | REQ-AM-FUN-101 | + +##### 8.1.3.2.3 State diagram + +There is no state for this class. + +#### 8.1.3.3 AppointmentTimeSlot + +##### 8.1.3.3.1 Definition + +The AppointmentTimeSlot class contains information describing the time when the SP wants to visit the SC's premises, and the visit actually takes place. The SP may want to visit the premises more than one time, so for each premises to be visited, there may be more than one time slot. + +##### 8.1.3.3.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-----------------------|-------------------|----------------|-----------------|------------------------------------------------------| +| appointmentTimeSlotID | M | – | – | REQ-AM-FUN-101,
REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| planBeginTime | M | – | – | REQ-AM-FUN-101,
REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| planEndTime | M | – | – | REQ-AM-FUN-101,
REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| actualBeginTime | M | – | – | REQ-AM-FUN-501,
REQ-AM-FUN-503 | +| actualEndTime | M | – | – | REQ-AM-FUN-501,
REQ-AM-FUN-503 | +| suggestPerson | M | – | – | REQ-AM-FUN-101,
REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| respondPerson | M | – | – | REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| slotState | M | – | – | REQ-AM-FUN-102,
REQ-AM-FUN-103,
REQ-AM-FUN-501 | +| slotStateTime | M | – | – | REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| activityInfo | M | – | – | REQ-AM-FUN-503 | +| failtoKeepIndicator | M | – | – | REQ-AM-FUN-501 | + +##### 8.1.3.3.3 State diagram + +The `AppointmentTimeSlot` state is described, as shown in Figure 8: + +![State diagram for AppointmentTimeSlot. States: Suggested, Accepted, Cancelled, Declined, Done, FailToKeep. Transitions: create to Suggested; Suggested to Accepted (Accept), Suggested to Cancelled (Cancel), Suggested to Declined (Decline); Accepted to Cancelled (Cancel), Accepted to Done (The work done according to the appointment), Accepted to FailToKeep (SP or SC fails to keep this time slot); Cancelled to Done; Declined to Done; FailToKeep to Done.](1142ba0197b158bb198186fe8baccc32_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Suggested : create + Suggested --> Accepted : Accept + Suggested --> Cancelled : Cancel + Suggested --> Declined : Decline + Accepted --> Cancelled : Cancel + Accepted --> Done : The work done according to the appointment + Accepted --> FailToKeep : SP or SC fails to keep this time slot + Cancelled --> Done + Declined --> Done + FailToKeep --> Done + +``` + +M.3344(11)\_F08 + +State diagram for AppointmentTimeSlot. States: Suggested, Accepted, Cancelled, Declined, Done, FailToKeep. Transitions: create to Suggested; Suggested to Accepted (Accept), Suggested to Cancelled (Cancel), Suggested to Declined (Decline); Accepted to Cancelled (Cancel), Accepted to Done (The work done according to the appointment), Accepted to FailToKeep (SP or SC fails to keep this time slot); Cancelled to Done; Declined to Done; FailToKeep to Done. + +Figure 8 – `AppointmentTimeSlot` state diagram + +#### 8.1.3.4 AppointmentReport + +##### 8.1.3.4.1 Definition + +The `AppointmentReport` class contains information describing the report which the SP needs to provide to SC. For one appointment, the SP may provide many reports to the SC. + +##### 8.1.3.4.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------------------------|-------------------|----------------|-----------------|-----------------------------------| +| appointmentReportID | M | – | – | REQ-AM-FUN-502,
REQ-AM-FUN-503 | +| reportContent | M | – | – | REQ-AM-FUN-503 | + +##### 8.1.3.4.3 State diagram + +There is no state for this class. + +#### 8.1.3.5 AppointmentHistoryRecord + +##### 8.1.3.5.1 Definition + +The `AppointmentHistoryRecord` class contains detailed tracking information about the state transitions of an appointment (including time-stamps and state transition reasons). When there is any change in the appointment state, an `AppointmentHistoryRecord` object must be created. + +##### 8.1.3.5.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|------------------------------------------------|-------------------|----------------|-----------------|-----------------------------------| +| appointmentHistoryID | M | – | – | REQ-AM-FUN-601
REQ-AM-FUN-602 | +| appointmentState | M | – | – | REQ-AM-FUN-602 | +| appointmentStateTime | M | – | – | REQ-AM-FUN-602 | +| appointmentStateTransition Reason | M | – | – | REQ-AM-FUN-601,
REQ-AM-FUN-602 | + +##### 8.1.3.5.3 State diagram + +There is no state for this class. + +### 8.1.4 Information relationship definitions + +| Relationship | Support qualifier | Requirement IDs | +|-------------------------------------------------|-------------------|------------------------------------------------------| +| relation-Appointment-AppointmentPremise | M | REQ-AM-FUN-101,
REQ-AM-FUN-102 | +| relation-AppointmentPremise-AppointmentTimeSlot | M | REQ-AM-FUN-101,
REQ-AM-FUN-102,
REQ-AM-FUN-103 | +| relation-Appointment-AppointmentReport | O | REQ-AM-FUN-502,
REQ-AM-FUN-503 | +| relation-Appointment-AppointmentHistory | M | REQ-AM-FUN-601,
REQ-AM-FUN-602 | + +#### 8.1.4.1 relation-Appointment-AppointmentPremise (M) + +##### 8.1.4.1.1 Definition + +This represents the containment relationship between Appointment and AppointmentPremise. + +##### 8.1.4.1.2 Roles + +| Name | Definition | +|----------------------------|--------------------------------------------------------------| +| identifyAppointment | It represents the appointment. | +| identifyAppointmentpremise | It represents the premises to be visited in the appointment. | + +##### 8.1.4.1.3 Constraints + +There is no constraint for this relationship. + +#### 8.1.4.2 relation-AppointmentPremise-AppointmentTimeSlot (M) + +##### 8.1.4.2.1 Definition + +This represents the containment relationship between AppointmentPremise and AppointmentTimeSlot. + +##### 8.1.4.2.2 Roles + +| Name | Definition | +|-----------------------------|--------------------------------------------------------------| +| identifyAppointmentPremise | It represents the premises to be visited in the appointment. | +| identifyAppointmentTimeSlot | It represents the time slots for each premises. | + +##### 8.1.4.2.3 Constraints + +There is no constraint for this relationship. + +#### 8.1.4.3 relation-Appointment-AppointmentReport (O) + +##### 8.1.4.3.1 Definition + +This represents the containment relationship between Appointment and AppointmentReport. + +##### 8.1.4.3.2 Roles + +| Name | Definition | +|---------------------------|--------------------------------------------------| +| identifyAppointment | It represents the appointment. | +| identifyAppointmentReport | It represents the reports about the appointment. | + +##### 8.1.4.3.3 Constraints + +There is no constraint for this relationship. + +#### 8.1.4.4 relation-Appointment-AppointmentHistory (M) + +##### 8.1.4.4.1 Definition + +This represents the containment relationship between appointment and AppointmentHistoryRecord. + +##### 8.1.4.4.2 Roles + +| Name | Definition | +|----------------------------|-----------------------------------------------| +| identifyAppointment | It represents the appointment. | +| identifyAppointmentHistory | It represents the history of the appointment. | + +##### 8.1.4.4.3 Constraints + +There is no constraint for this relationship. + +### 8.1.5 Information attribute definitions + +#### 8.1.5.1 Definition and legal values + +| Attribute name | Definition | Information type/
Legal values | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| appointmentID | It is the identifier of the appointment. | String | +| appointmentPremiseList | It indicates the premises where the SP needs to visit. | SET OF String | +| spContactPerson | It indicates the SP's contact person for the appointment. | String | +| spContactInfo | It indicates the SP's contact person's contact information. | ContactInfoType ::=
SEQUENCE
{ tel String,
fax String,
mobile String,
email String } | +| scContactPerson | It indicates the SC's contact person for the appointment. | String | +| scContactInfo | It indicates the SC's contact person's contact information. | ContactInfoType | +| appointmentState | It indicates the state of the appointment. An appointment may have the following states:
"Unscheduled": An appointment is created without any time slot | AppointmentStateType ::=
ENUMERATED {
Unscheduled, Scheduling,
Confirming, Confirmed,
Rescheduling, Cancelling, | + +| Attribute name | Definition | Information type/
Legal values | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| |

provided;

"Scheduling": one or more time slots for the appointment have been provided, but the appointment has not been confirmed by the SC;

"Confirming": the SP has requested the SC to confirm the appointment, and the SC has not responded yet;

"Confirmed": the appointment has been confirmed by the SC;

"Rescheduling": after the appointment has been confirmed, the SP or the SC has requested to reschedule it, and the other side has not responded yet;

"Cancelling": after the appointment has been confirmed, the SP or the SC has requested to cancel it, and the other side has not responded yet;

"Cancelled": the appointment has been cancelled;

"Performing": the appointment is being performed;

"NewTimeSlotsUnconfirmed": When the appointment is being performed, the SP or the SC has requested additional time slots, and not all of these time slots have been accepted or denied;

"Done": all the work for the appointment has been finished;

"FailedToKeep": the SP or the SC fails to keep the appointment.

The transition among these states can be found in clause 8.1.3.1.3.

| Cancelled, Performing, NewTimeSlotsUnconfirmed, Done, FailedToKeep } | +| appointmentStateTime | It indicates the state time of the appointment. | GeneralizedTime | +| appointmentStateTransitionReason | It indicates the reason of why an appointment state has changed. | String | +| reportPeriod | It indicates the report period of the appointment. | INTEGER (Units: day) | +| appointmentHistoryList | It indicates the state transition history of the appointment. | SET OF String | +| additionalInfo | Additional appointment information. | String | +| appointmentPremiseID | It is the identifier of the AppointmentPremise. | String | +| location | It indicates the location of the premises. | String | + +| Attribute name | Definition | Information type/
Legal values | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| appointmentTimeSlotList | It indicates the related time slots of the AppointmentPremise. | SET OF String | +| visitPurpose | It indicates the work to be done at the premises. | String | +| estimatedDuration | It indicates the estimated duration at the premises. | INTEGER (Units: hour) | +| appointmentTimeSlotID | It is the identifier of the AppointmentTimeSlot. | String | +| planBeginTime | It indicates the plan begin time of the time slot. | GeneralizedTime | +| planEndTime | It indicates the plan end time of the time slot. | GeneralizedTime | +| actualBeginTime | It indicates the actual begin time of the time slot. | GeneralizedTime | +| actualEndTime | It indicates the actual end time of the time slot. | GeneralizedTime | +| suggestPerson | It indicates the person who suggests this time slot. | String | +| respondPerson | It indicates the person who responds to this time slot. | String | +| slotState | It indicates the state of the time slot. Time slot may have the following states:
"Suggested": the time slot has been suggested by the SP or the SC, but has not been accepted or declined by the other side;
"Accepted": the time slot has been accepted;
"Declined": the time slot has been declined;
"Cancelled": the time slot has been cancelled;
"Done": the work for this time slot has been finished according to the appointment;
"FailToKeep": the SP or the SC fails to keep this time slot.
The transition among these states can be found in clause 8.1.3.3.3. | SlotStateType ::=
ENUMERATED {
Suggested, Accepted,
Declined, Cancelled, Done,
FailToKeep} | +| slotStateTime | It indicates the state time of the time slot. | GeneralizedTime | +| activityInfo | It indicates the activity information performed in this time slot. | ActivityInfoType ::=
SEQUENCE
{ staffID: String,
workDone: String} | +| appointmentReportID | It is the identifier of the AppointmentReport. | String | + +| Attribute name | Definition | Information type/
Legal values | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reportContentList | It indicates the premises and activities in this report. | SET OF ReportContentType
ReportContentType ::= SEQUENCE {
premiseLocation: String,
beginTime:
GeneralizedTime,
endTime: GeneralizedTime,
activityInfo:
ActivityInfoType } | +| appointmentHistoryID | It is the identifier of the AppointmentHistoryRecord. | String | +| slaViolationIndicator | It indicates whether there is a SLA violation. This attribute may have the following states:
"None": There is no SLA violation;
"SPViolated": the SP has violated the SLA;
"SCViolated": the SC has violated the SLA. | SlaViolationIndicatorType ::= ENUMERATED { None, SPViolated, SCViolated } | +| requirementFulfilledIndicator | It indicates whether the SC's requirement has been fulfilled. | RequirementFulfilledIndicatorType ::= ENUMERATED { Yes, No } | +| failtoKeepIndicator | It indicates who has failed to keep the time slot. This attribute may have the following states:
"None": No one has failed to keep this time slot;
"SPFailtoKeep": the SP has failed to keep this time slot;
"SCFailtoKeep": the SC has failed to keep this time slot. | FailtoKeepIndicatorType ::= ENUMERATED { None, SPFailtoKeep, SCFailtoKeep } | + +#### 8.1.5.2 Constraints + +| Name | Affected attribute(s) | Definition | +|---------------------------|-----------------------|------------------------------------------------------------------------------------------------| +| inv_appointmentID | appointmentID | appointmentIDs shall be unique across all appointments. | +| inv_appointmentPremiseID | appointmentPremiseID | appointmentPremiseIDs shall be unique across all premises of a particular appointment. | +| inv_appointmentTimeSlotID | appointmentTimeSlotID | appointmentTimeSlotIDs shall be unique across all premises of a particular AppointmentPremise. | +| inv_planEndTime | planEndTime | The planEndTime shall be later than the planBeginTime of the same time slot. | + +| Name | Affected attribute(s) | Definition | +|--------------------------|-----------------------|-----------------------------------------------------------------------------------------------| +| inv_actualEndTime | actualEndTime | The actualEndTime shall be later than the actualBeginTime of the same time slot. | +| inv_appointmentReportID | appointmentReportID | appointmentReportIDs shall be unique across all reports of a particular appointment. | +| inv_appointmentHistoryID | appointmentHistoryID | appointmentHistoryIDs shall be unique across all history records of a particular appointment. | + +## 8.2 Interface definition + +### 8.2.1 Class diagram representing interfaces + +![UML Class diagram for Appointment management. The central class is 'Appointment' (Information Object Class). It is associated with four interfaces: 'AppointmentOperations_1', 'AppointmentNotifications_1', 'AppointmentOperations_2', and 'AppointmentNotifications_2'. The associations are: Appointment (1) to AppointmentOperations_1, Appointment (1) to AppointmentNotifications_1, Appointment (0..1) to AppointmentOperations_2, and Appointment (0..1) to AppointmentNotifications_2. Each interface box lists its operations.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +classDiagram + class AppointmentOperations_1 { + <> + +offerTimeSlots() + +acceptTimeSlot() + +denyTimeSlot() + +confirmAppointment() + +queryAppointment() + +queryTrackingInformation() + +failureToKeepApp() + +acceptRescheduleAppointment() + +rejectRescheduleAppointment() + +acceptCancelAppointment() + +rejectCancelAppointment() + +queryAppointmentReport() + } + class AppointmentNotifications_1 { + <> + +notifyRequestForTimeSlots() + +notifyRequestForConfirmation() + +notifyAcceptanceOfRescheduleAppointment() + +notifyRejectionOfRescheduleAppointment() + +notifyAcceptanceOfCancelAppointment() + +notifyRejectionOfCancelAppointment() + +notifyAcceptanceOfTimeSlot() + +notifyRejectionOfTimeSlot() + } + class AppointmentOperations_2 { + <> + +changeAppointment() + +cancelAppointment() + +requestRescheduleAppointment() + +requestCancelAppointment() + } + class AppointmentNotifications_2 { + <> + +notifyTimeSlotsOffered() + +notifyAppointmentChanged() + +notifyAppointmentCancelled() + +notifyRequestOfRescheduleAppointment() + +notifyRequestOfCancelAppointment() + +notifyFailureToKeepApp() + +notifyReportProvided() + } + class Appointment { + <> + } + Appointment "1" -- "1" AppointmentOperations_1 + Appointment "1" -- "1" AppointmentNotifications_1 + Appointment "0..1" -- "0..1" AppointmentOperations_2 + Appointment "0..1" -- "0..1" AppointmentNotifications_2 + +``` + +UML Class diagram for Appointment management. The central class is 'Appointment' (Information Object Class). It is associated with four interfaces: 'AppointmentOperations\_1', 'AppointmentNotifications\_1', 'AppointmentOperations\_2', and 'AppointmentNotifications\_2'. The associations are: Appointment (1) to AppointmentOperations\_1, Appointment (1) to AppointmentNotifications\_1, Appointment (0..1) to AppointmentOperations\_2, and Appointment (0..1) to AppointmentNotifications\_2. Each interface box lists its operations. + +Figure 9 – Appointment management class diagram + +### 8.2.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 regard 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 that is raised when an internal problem occurs, and that the operation cannot be completed. The exception has the same entry and exit state. + +### 8.2.3 Interface AppointmentOperations\_1(M) + +| Operation name | Qualifier | Requirement IDs | +|-----------------------------|-----------|------------------------------------------------| +| offerTimeSlots | M | REQ-AM-FUN-101, REQ-AM-FUN-102, REQ-AM-FUN-103 | +| acceptTimeSlot | M | REQ-AM-FUN-102, REQ-AM-FUN-103 | +| denyTimeSlot | M | REQ-AM-FUN-102, REQ-AM-FUN-103 | +| confirmAppointment | M | REQ-AM-FUN-201 | +| queryAppointment | M | REQ-AM-FUN-601 | +| queryTrackingInformation | M | REQ-AM-FUN-602 | +| failureToKeepApp | M | REQ-AM-FUN-501, REQ-AM-FUN-103 | +| acceptRescheduleAppointment | M | REQ-AM-FUN-303 | +| rejectRescheduleAppointment | M | REQ-AM-FUN-303 | +| acceptCancelAppointment | M | REQ-AM-FUN-402 | +| rejectCancelAppointment | M | REQ-AM-FUN-402 | +| queryAppointmentReport | M | REQ-AM-FUN-503 | + +#### 8.2.3.1 Operation offerTimeSlots(M) + +##### 8.2.3.1.1 Definition + +Before the appointment has been confirmed, the SC can invoke this operation to offer time slots for the premises. During the period when an appointment is being performed, the SC can invoke this operation to request additional time slots. + +##### 8.2.3.1.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|-------------------------|-------------------|----------------------------------------|-------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be scheduled. | +| appointmentPremiseID | M | String | To indicate the premises to be visited. | +| appointmentTimeSlotList | M | SET OF String | To indicate a set of time slots when to visit the premises. | + +##### 8.2.3.1.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|-----------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| status | M | OperationStatusType:=
ENUMERATED
{OperationSucceeded,
OperationFailed,
OperationPartiallySucceeded} | It indicates if the operation succeeded or failed. | +| appointment
TimeSlotID
List | M | SET OF
AppointmentTimeSlot.appointmentTimeSlotID | It indicates the list of IDs of the created AppointmentTimeSlot objects. | + +##### 8.2.3.1.4 Pre-condition + +anOpenChannel + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | + +##### 8.2.3.1.5 Post-condition + +TimeSlotsSet + +| Assertion name | Definition | +|----------------|------------------------------------------| +| TimeSlotsSet | All the time slots are set as requested. | + +##### 8.2.3.1.6 Exceptions + +###### 8.2.3.1.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.3.2 Operation acceptTimeSlot(M) + +##### 8.2.3.2.1 Definition + +The SC invokes this operation to accept specific time slots for the premises offered by the SP. + +##### 8.2.3.2.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|------------------------|-------------------|----------------------------------------|------------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be accepted. | +| appointmentPremiseID | M | String | To indicate which appointment premises time slot to be accepted. | +| appointmentTimeSlotIDs | M | SET OF String | To indicate the time slots to be accepted. | + +##### 8.2.3.2.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.2.4 Pre-condition + +anOpenChannel + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| offeredBySP | The time slots to be accepted are offered by the SP. | + +##### 8.2.3.2.5 Post-condition + +TimeSlotsStateChanged. + +| Assertion name | Definition | +|-----------------------|----------------------------------------------------------| +| TimeSlotsStateChanged | The related time slots slotState are set to be accepted. | + +##### 8.2.3.2.6 Exceptions + +###### 8.2.3.2.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.2.6.2 inappropriate\_invoking + +| Exception name | Definition | | +|------------------------|--------------------|------------------------------------------------------| +| inappropriate_invoking | Condition | The time slots to be accepted are offered by the SC. | +| | Return info | InappropriateInvoking | +| | Exit state | Entry state | + +#### 8.2.3.3 Operation denyTimeSlot(M) + +##### 8.2.3.3.1 Definition + +The SC invokes this operation to deny specific time slots for the premises. + +##### 8.2.3.3.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|------------------------|-------------------|----------------------------------------|----------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be denied. | +| appointmentPremiseID | M | String | To indicate which appointment premises time slot to be denied. | +| appointmentTimeSlotIDs | M | SET OF String | To indicate the time slots to be denied. | + +##### 8.2.3.3.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.3.4 Pre-condition + +anOpenChannel + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| offeredBySP | The time slots to be denied are offered by the SP. | + +##### 8.2.3.3.5 Post-condition + +TimeSlotsStateChanged. + +| Assertion name | Definition | +|-----------------------|----------------------------------------------------------| +| TimeSlotsStateChanged | The related time slots slotState are set to be declined. | + +##### 8.2.3.3.6 Exceptions + +###### 8.2.3.3.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.3.6.2 inappropriate\_invoking + +| Exception name | Definition | | +|------------------------|--------------------|----------------------------------------------------| +| inappropriate_invoking | Condition | The time slots to be denied are offered by the SC. | +| | Return info | InappropriateInvoking | +| | Exit state | Entry state | + +#### 8.2.3.4 Operation confirmAppointment(M) + +##### 8.2.3.4.1 Definition + +The SC invokes this operation to confirm the appointment. This means the negotiation is completed. + +##### 8.2.3.4.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|----------------------------------------------| +| appointmentID | M | String | To indicate the appointment to be confirmed. | + +##### 8.2.3.4.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.4.4 Pre-condition + +anOpenChannel AND timeSlotState. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| timeSlotState | The selected time slots can satisfy both the SP and the SC, and their states are set to be accepted. | + +##### 8.2.3.4.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------| +| AppointmentStateChanged | The appointment state is set to be confirmed. | + +##### 8.2.3.4.6 Exceptions + +###### 8.2.3.4.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.3.5 Operation queryAppointment(M) + +##### 8.2.3.5.1 Definition + +The SC can invoke this operation to query the complete descriptions of a specific set of current or historical appointments. + +##### 8.2.3.5.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|------------------|-------------------|----------------------------------------|-----------------------------------------------------------------| +| appointmentID | M | String | To indicate the appointmentID of the queried appointment | +| spContactPerson | O | String | To indicate the spContactPerson of the queried appointment | +| spContactInfo | O | ContactInfoType | To indicate the spContactInfo of the queried appointment | +| scContactPerson | O | String | To indicate the scContactPerson of the queried appointment | +| scContactInfo | O | ContactInfoType | To indicate the scContactInfo of the queried appointment | +| appointmentState | O | AppointmentStateType | To indicate the appointmentState of the queried appointment | +| location | O | String | To indicate the location of the queried appointment premises | +| planBeginTime | O | GeneralizedTime | To indicate the planBeginTime of the queried appointment | +| planEndTime | O | GeneralizedTime | To indicate the planEndTime of the queried appointment time | +| actualBeginTime | O | GeneralizedTime | To indicate the actualBeginTime of the queried appointment time | +| actualEndTime | O | GeneralizedTime | To indicate the actualEndTime of the queried appointment time | +| suggestPerson | O | String | To indicate the suggestPerson of the queried appointment time | +| respondPerson | O | String | To indicate the respondPerson of the queried appointment time | +| slotState | O | SlotStateType | To indicate the slotState of the queried appointment time | + +##### 8.2.3.5.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|-----------------|-------------------|------------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | +| AppointmentList | M | SET OF Name | The query results. | + +##### 8.2.3.5.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | + +##### 8.2.3.5.5 Exceptions + +###### 8.2.3.5.5.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.3.6 Operation queryTrackingInformation(M) + +##### 8.2.3.6.1 Definition + +The SC can invoke this operation to query detailed tracking information about the state transitions of an appointment (including time-stamps). + +##### 8.2.3.6.2 Input parameters + +| Parameter name | Support qualifier | Matching information
type/Legal values | Comment | +|----------------|-------------------|-------------------------------------------|----------------------------------------------------------| +| appointmentID | M | String | To indicate the appointmentID of the queried appointment | + +##### 8.2.3.6.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|------------------------------|-------------------|------------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | +| AppointmentHistoryRecordList | M | SET OF Name | The query results. | + +##### 8.2.3.6.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | + +##### 8.2.3.6.5 Exceptions + +###### 8.2.3.6.5.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.6.5.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.3.7 Operation failureToKeepApp(M) + +##### 8.2.3.7.1 Definition + +The SC can invoke this operation to set the appointment and time slot state to clarify the failure to keep the appointment. + +##### 8.2.3.7.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|-------------------------|-------------------|----------------------------------------|-------------------------------------------------------| +| appointmentID | M | String | To indicate the failure appointment appointmentID. | +| appointmentPremiseID | O | String | To indicate which premises time slot failure to keep. | +| appointmentTimeSlotList | O | SET OF String | To indicate which time slot failure to keep. | +| appointmentState | O | AppointmentStateType | To indicate the appointment state to be set. | +| slotState | O | SlotStateType | To indicate the time slot state to be set. | + +##### 8.2.3.7.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|----------------|-------------------|------------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.7.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | + +##### 8.2.3.7.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------------------------------------------------------| +| AppointmentStateChanged | The appointment state or the AppointmentTimeSlots slotState is set to be the specified state. | + +##### 8.2.3.7.6 Exceptions + +###### 8.2.3.7.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.7.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.3.8 Operation acceptRescheduleAppointment(M) + +##### 8.2.3.8.1 Definition + +The SC can invoke this operation to accept the request to reschedule an agreed appointment. + +##### 8.2.3.8.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|-----------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be accepted to be rescheduled. | + +##### 8.2.3.8.3 Output parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.8.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| requestedBySP | The reschedule request to be accepted is offered by the SP. | + +##### 8.2.3.8.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|--------------------------------------------------| +| AppointmentStateChanged | The appointment state is changed to unscheduled. | + +##### 8.2.3.8.6 Exceptions + +###### 8.2.3.8.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.8.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.8.6.3 inappropriate\_invoking + +| Exception name | Definition | | +|------------------------|--------------------|-------------------------------------------------------------| +| inappropriate_invoking | Condition | The reschedule request to be accepted is offered by the SC. | +| | Return info | InappropriateInvoking | +| | Exit state | Entry state | + +#### 8.2.3.9 Operation rejectRescheduleAppointment(M) + +##### 8.2.3.9.1 Definition + +The SC can invoke this operation to reject the request to reschedule an agreed appointment. + +##### 8.2.3.9.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|----------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be rejected to be rescheduled | + +##### 8.2.3.9.3 Output parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.9.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| requestedBySP | The reschedule request to be rejected is offered by the SP. | + +##### 8.2.3.9.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|------------------------------------------------| +| AppointmentStateChanged | The appointment state is changed to confirmed. | + +##### 8.2.3.9.6 Exceptions + +###### 8.2.3.9.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.9.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.9.6.3 inappropriate\_invoking + +| Exception name | Definition | | +|------------------------|--------------------|-------------------------------------------------------------| +| inappropriate_invoking | Condition | The reschedule request to be rejected is offered by the SC. | +| | Return info | InappropriateInvoking | +| | Exit state | Entry state | + +#### 8.2.3.10 Operation acceptCancelAppointment(M) + +##### 8.2.3.10.1 Definition + +SC can invoke this operation to accept the request to cancel an agreed appointment. + +##### 8.2.3.10.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|--------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be accepted to be cancelled | + +##### 8.2.3.10.3 Output parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.10.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| requestedBySP | The cancel request to be accepted is offered by the SP. | + +##### 8.2.3.10.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|------------------------------------------------| +| AppointmentStateChanged | The appointment state is changed to cancelled. | + +##### 8.2.3.10.6 Exceptions + +###### 8.2.3.10.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.10.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.10.6.3 inappropriate\_invoking + +| Exception name | Definition | | +|------------------------|--------------------|---------------------------------------------------------| +| inappropriate_invoking | Condition | The cancel request to be accepted is offered by the SC. | +| | Return info | InappropriateInvoking | +| | Exit state | Entry state | + +#### 8.2.3.11 Operation rejectCancelAppointment(M) + +##### 8.2.3.11.1 Definition + +The SC can invoke this operation to reject the request to cancel an agreed appointment. + +##### 8.2.3.11.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|---------------------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be rejected to be cancelled. | + +##### 8.2.3.11.3 Output Parameters + +| Parameter name | Support qualifier | Matching information/Information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.3.11.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| requestedBySP | The cancel request to be rejected is offered by the SP. | + +##### 8.2.3.11.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|------------------------------------------------------| +| AppointmentStateChanged | The appointment state is changed to the entry state. | + +##### 8.2.3.11.6 Exceptions + +###### 8.2.3.11.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.11.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.11.6.3 inappropriate\_invoking + +| Exception name | Definition | | +|------------------------|--------------------|---------------------------------------------------------| +| inappropriate_invoking | Condition | The cancel request to be rejected is offered by the SC. | +| | Return info | InappropriateInvoking | +| | Exit state | Entry state | + +#### 8.2.3.12 Operation queryAppointmentReport(M) + +##### 8.2.3.12.1 Definition + +The SC can invoke this operation to retrieve the appointment report on request. + +##### 8.2.3.12.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/
Legal values | Comment | +|----------------|-------------------|--------------------------------------------|---------------------------------------------------------| +| appointmentID | M | String | To indicate the report of which appointment to be read. | + +##### 8.2.3.12.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|----------------|-------------------|------------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | +| reportContent | M | AppointmentReport.reportContent | It indicates the content of the report. | + +##### 8.2.3.12.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | + +##### 8.2.3.12.5 Post-condition + +SCgotAppointmentReport. + +| Assertion name | Definition | +|------------------------|--------------------------------------------------------------------| +| SCgotAppointmentReport | The SC receives the complete report of the requested appointments. | + +##### 8.2.3.12.6 Exceptions + +###### 8.2.3.12.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.3.12.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +### 8.2.4 Interface AppointmentOperations\_2(O) + +| Operation name | qualifier | Requirement IDs | +|------------------------------|-----------|-----------------| +| changeAppointment | O | REQ-AM-FUN-301 | +| cancelAppointment | O | REQ-AM-FUN-401 | +| requestRescheduleAppointment | O | REQ-AM-FUN-302 | +| requestCancelAppointment | O | REQ-AM-FUN-401 | + +#### 8.2.4.1 Operation changeAppointment(O) + +##### 8.2.4.1.1 Definition + +Prior to the appointment time, the SC can invoke this operation to modify the information related to the appointment, e.g., additional information, contact change, etc. + +##### 8.2.4.1.2 Input Parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|-----------------|-------------------|----------------------------------------|----------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be changed. | +| spContactPerson | O | String | The new spContactPerson. | +| spContactInfo | O | ContactInfoType | The new spContactInfo. | +| scContactPerson | O | String | The new scContactPerson. | +| scContactInfo | O | ContactInfoType | The new scContactInfo. | +| reportPeriod | O | INTEGER | The new reportPeriod. | +| additionalInfo | O | String | The new additionalInfo. | + +##### 8.2.4.1.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.4.1.4 Pre-condition + +anOpenChannel AND timeLimited. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| timeLimited | This operation only can be done before the appointment time. | + +##### 8.2.4.1.5 Post-condition + +AppointmentInformationChanged. + +| Assertion name | Definition | +|-------------------------------|-----------------------------------------| +| AppointmentInformationChanged | The appointment information is changed. | + +##### 8.2.4.1.6 Exceptions + +###### 8.2.4.1.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.4.2 Operation cancelAppointment(O) + +##### 8.2.4.2.1 Definition + +After the cancel request is accepted, the SC can invoke this operation to cancel an appointment. + +##### 8.2.4.2.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|------------------------------------------------| +| appointmentID | M | String | To indicate which appointment to be cancelled. | + +##### 8.2.4.2.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.4.2.4 Pre-condition + +anOpenChannel. + +| Assertion name | Definition | +|----------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | + +##### 8.2.4.2.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------| +| AppointmentStateChanged | The appointment state is set to be cancelled. | + +##### 8.2.4.2.6 Exceptions + +###### 8.2.4.2.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.4.3 Operation requestRescheduleAppointment(O) + +##### 8.2.4.3.1 Definition + +Prior to an appointment time, and subject to the terms specified in the contract, the SC may invoke this operation to request to reschedule an agreed appointment (time, location). The reason why the SC reschedules the appointment shall be given. + +##### 8.2.4.3.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|------------------|-------------------|----------------------------------------|---------------------------------------------------| +| appointmentID | M | String | To indicate the appointmentID to be rescheduled. | +| rescheduleReason | M | String | To indicate the reason of the reschedule request. | + +##### 8.2.4.3.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.4.3.4 Pre-condition + +anOpenChannel AND appointmentConfirmed. + +| Assertion name | Definition | +|----------------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| appointmentConfirmed | The appointment state should be Confirmed. | + +##### 8.2.4.3.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|---------------------------------------------------| +| AppointmentStateChanged | The appointment state is changed to Rescheduling. | + +##### 8.2.4.3.6 Exceptions + +###### 8.2.4.3.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.4.3.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +#### 8.2.4.4 Operation requestCancelAppointment(O) + +##### 8.2.4.4.1 Definition + +Prior to an appointment time, and subject to the terms specified in the contract, the SC may invoke this operation to request to cancel an agreed appointment. The reason why the SC cancels the appointment shall be given. + +##### 8.2.4.4.2 Input parameters + +| Parameter name | Support qualifier | Matching information type/Legal values | Comment | +|----------------|-------------------|----------------------------------------|------------------------------------------------| +| appointmentID | M | String | To indicate the appointmentID to be cancelled. | +| cancelReason | M | String | To indicate the reason of the cancel request. | + +##### 8.2.4.4.3 Output parameters + +| Parameter name | Support qualifier | Matching information/ Information type/ Legal values | Comment | +|----------------|-------------------|------------------------------------------------------|----------------------------------------------------| +| status | M | OperationStatusType | It indicates if the operation succeeded or failed. | + +##### 8.2.4.4.4 Pre-condition + +anOpenChannel and appointmentConfirmed. + +| Assertion name | Definition | +|----------------------|-------------------------------------------------------------------------------------------------------| +| anOpenChannel | There is an open communication channel between the SP management system and the SC management system. | +| appointmentConfirmed | The appointment state should be Confirmed. | + +##### 8.2.4.4.5 Post-condition + +AppointmentStateChanged. + +| Assertion name | Definition | +|-------------------------|-------------------------------------------------| +| AppointmentStateChanged | The appointment state is changed to Cancelling. | + +##### 8.2.4.4.6 Exceptions + +###### 8.2.4.4.6.1 operation\_failed\_network\_fault + +| Exception name | Definition | | +|--------------------------------|--------------------|------------------------------------------------------------------------| +| operation_failed_network_fault | Condition | There is a fault in the network, so the operation cannot be completed. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +###### 8.2.4.4.6.2 invalid\_appointmentID + +| Exception name | Definition | | +|-----------------------|--------------------|-------------------------------------| +| invalid_appointmentID | Condition | The input appointmentID is invalid. | +| | Return info | OperationFailed | +| | Exit state | Entry state | + +### 8.2.5 Interface AppointmentNotifications\_1(M) + +| Notification name | Qualifier | Requirement IDs | +|-----------------------------------------|-----------|--------------------------------| +| notifyRequestForTimeSlots | M | REQ-AM-FUN-101, REQ-AM-FUN-203 | +| notifyRequestForConfirmation | M | REQ-AM-FUN-101, REQ-AM-FUN-103 | +| notifyAcceptanceOfRescheduleAppointment | M | REQ-AM-FUN-303 | +| notifyRejectionOfRescheduleAppointment | M | REQ-AM-FUN-303 | +| notifyAcceptanceOfCancelAppointment | M | REQ-AM-FUN-402 | +| notifyRejectionOfCancelAppointment | M | REQ-AM-FUN-402 | +| notifyAcceptanceOfTimeSlot | M | REQ-AM-FUN-103 | +| notifyRejectionOfTimeSlot | M | REQ-AM-FUN-103 | + +#### 8.2.5.1 Notification notifyRequestForTimeSlots(M) + +##### 8.2.5.1.1 Definition + +When there are no times slots offered, or when the SP thinks the time slots offered are not enough to complete the work, the SP notifies the SC to offer some time slots. + +##### 8.2.5.1.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------------|------------|------------------------------------------------------------|------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the appointment. | +| appointmentPremiseID | O, Y | AppointmentPremise.appointmentPremiseID | To indicate the premises request for the time slots. | + +##### 8.2.5.1.3 Triggering event + +###### 8.2.5.1.3.1 From state + +Unscheduled OR Scheduling. + +| Assertion name | Definition | +|----------------|---------------------------------------------------------------------------------------------| +| Unscheduled | There is no time slot for the appointment. | +| Scheduling | There are some time slots but these time slots offered are not enough to complete the work. | + +###### 8.2.5.1.3.2 To state + +WaitingForTimeSlots. + +| Assertion name | Definition | +|---------------------|----------------------------------------------| +| WaitingForTimeSlots | Waiting for the SC to offer some time slots. | + +#### 8.2.5.2 Notification notifyRequestForConfirmation(M) + +##### 8.2.5.2.1 Definition + +When the SP thinks the accepted time slots of the appointment are enough to do the work, the SP notifies the SC to confirm the appointment. + +##### 8.2.5.2.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|----------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointment to be confirmed. | + +##### 8.2.5.2.3 Triggering event + +###### 8.2.5.2.3.1 From state + +TimeSlotAcceptedEnough. + +| Assertion name | Definition | +|------------------------|-------------------------------------------------------------------------------------| +| TimeSlotAcceptedEnough | The SP thinks the accepted time slots of the appointment are enough to do the work. | + +###### 8.2.5.2.3.2 To state + +WaitingForSCConfirm. + +| Assertion name | Definition | +|---------------------|------------------------------------------------| +| WaitingForSCConfirm | Waiting for the SC to confirm the appointment. | + +#### 8.2.5.3 Notification notifyAcceptanceOfRescheduleAppointment(M) + +##### 8.2.5.3.1 Definition + +When the SP wants to accept the SC's request of rescheduling an appointment, the SP notifies the SC of the acceptance. + +##### 8.2.5.3.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|---------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the rescheduled appointment. | + +##### 8.2.5.3.3 Triggering event + +###### 8.2.5.3.3.1 From state + +Rescheduling. + +| Assertion name | Definition | +|----------------|------------------------------------------------------| +| Rescheduling | Waiting for the SP to accept or decline the request. | + +###### 8.2.5.3.3.2 To state + +Unscheduled. + +| Assertion name | Definition | +|----------------|---------------------------------------------------| +| Unscheduled | Waiting for the SC to reschedule the appointment. | + +#### 8.2.5.4 Notification notifyRejectionOfRescheduleAppointment(M) + +##### 8.2.5.4.1 Definition + +When the SP wants to reject the SC's request of rescheduling an appointment, the SP notifies the SC of the rejection. + +##### 8.2.5.4.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|---------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the rescheduled appointment. | + +##### 8.2.5.4.3 Triggering event + +###### 8.2.5.4.3.1 From state + +Rescheduling. + +| Assertion name | Definition | +|----------------|------------------------------------------------------| +| Rescheduling | Waiting for the SP to accept or decline the request. | + +###### 8.2.5.4.3.2 To state + +Confirmed. + +| Assertion name | Definition | +|----------------|--------------------------------------------------------------------------------------------------------------------| +| Confirmed | The SP rejects the SC's request to reschedule the appointment, so the state of the appointment is still Confirmed. | + +#### 8.2.5.5 Notification notifyAcceptanceOfCancelAppointment(M) + +##### 8.2.5.5.1 Definition + +When the SP wants to accept the SC's request to cancel an appointment, the SP notifies the SC of the acceptance. + +##### 8.2.5.5.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|-------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the cancelled appointment. | + +##### 8.2.5.5.3 Triggering event + +###### 8.2.5.5.3.1 From state + +Cancelling. + +| Assertion name | Definition | +|----------------|------------------------------------------------------| +| Cancelling | Waiting for the SP to accept or decline the request. | + +###### 8.2.5.5.3.2 To state + +Cancelled. + +| Assertion name | Definition | +|----------------|-------------------------------| +| Cancelled | The appointment is cancelled. | + +#### 8.2.5.6 Notification notifyRejectionOfCancelAppointment(M) + +##### 8.2.5.6.1 Definition + +When the SP wants to reject the SC's request to cancel an appointment, the SP notifies the SC of the rejection. + +##### 8.2.5.6.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|-------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the cancelled appointment. | + +##### 8.2.5.6.3 Triggering event + +###### 8.2.5.6.3.1 From state + +Cancelling. + +| Assertion name | Definition | +|----------------|------------------------------------------------------| +| Cancelling | Waiting for the SP to accept or decline the request. | + +###### 8.2.5.6.3.2 To state + +TheEntryState. + +| Assertion name | Definition | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| TheEntryState | The SP rejects the SC's request to cancel the appointment, so the state of the appointment is to return to the original state before the cancel request. | + +#### 8.2.5.7 Notification notifyAcceptanceOfTimeSlot(M) + +##### 8.2.5.7.1 Definition + +When the SP wants to accept the time slots offered by the SC, the SP notifies the SC of the acceptance. + +##### 8.2.5.7.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|-------------------------|------------|------------------------------------------------------------|-------------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the accepted appointment. | +| appointmentPremiseID | M, N | AppointmentPremise.appointmentPremiseID | To indicate the appointmentPremiseID of the accepted premises. | +| appointmentTimeSlotList | M, N | SET OF
AppointmentTimeSlot.appointmentTimeSlotID | To indicate the appointmentTimeSlotID of the accepted time slots. | + +##### 8.2.5.7.3 Triggering event + +###### 8.2.5.7.3.1 From state + +WaitingForSPAcceptTimeSlots. + +| Assertion name | Definition | +|-----------------------------|---------------------------------------------------------------------------| +| WaitingForSPAcceptTimeSlots | Waiting for the SP to accept or decline the time slots offered by the SC. | + +###### 8.2.5.7.3.2 To state + +SCAcknowledgedAcceptance. + +| Assertion name | Definition | +|--------------------------|------------------------------------------------------------| +| SCAcknowledgedAcceptance | The SC acknowledges the SP's acceptance to the time slots. | + +#### 8.2.5.8 Notification notifyRejectionOfTimeSlot(M) + +##### 8.2.5.8.1 Definition + +When the SP wants to reject the time slots offered by the SC, the SP notifies the SC of the rejection. + +##### 8.2.5.8.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|-------------------------|------------|------------------------------------------------------------|-------------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the rejected appointment. | +| appointmentPremiseID | M, N | AppointmentPremise.appointmentPremiseID | To indicate the appointmentPremiseID of the rejected premise. | +| appointmentTimeSlotList | M, N | SET OF
AppointmentTimeSlot.appointmentTimeSlotID | To indicate the appointmentTimeSlotID of the rejected time slots. | + +##### 8.2.5.8.3 Triggering event + +###### 8.2.5.8.3.1 From state + +WaitingForSPAcceptTimeSlots. + +| Assertion name | Definition | +|-----------------------------|---------------------------------------------------------------------------| +| WaitingForSPAcceptTimeSlots | Waiting for the SP to accept or decline the time slots offered by the SC. | + +###### 8.2.5.8.3.2 To state + +SCAcknowledgedRejection. + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------------------| +| SCAcknowledgedRejection | The SC acknowledges the SP's rejection to the time slots. | + +### 8.2.6 Interface AppointmentNotifications\_2(O) + +| Notification name | Qualifier | Requirement IDs | +|--------------------------------------|-----------|--------------------------------| +| notifyTimeSlotsOffered | O | REQ-AM-FUN-101, REQ-AM-FUN-103 | +| notifyAppointmentChanged | O | REQ-AM-FUN-301 | +| notifyAppointmentCancelled | O | REQ-AM-FUN-401 | +| notifyRequestOfRescheduleAppointment | O | REQ-AM-FUN-302, REQ-AM-FUN-303 | +| notifyRequestOfCancelAppointment | O | REQ-AM-FUN-401, REQ-AM-FUN-402 | +| notifyFailureToKeepApp | O | REQ-AM-FUN-501 | +| notifyReportProvided | O | REQ-AM-FUN-502 | + +#### 8.2.6.1 Notification notifyTimeSlotsOffered(O) + +##### 8.2.6.1.1 Definition + +When the SP offers some time slots for the appointment, the SP notifies the SC to confirm them. + +Before the appointment has been confirmed, the SP offers some time slots for the appointment, and notifies the SC to accept them. During the period when the appointment is being performed, the SP can use this notification to request additional time slots. + +##### 8.2.6.1.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|-------------------------|------------|------------------------------------------------------------|-------------------------------------------------------------------| +| appointmentID | M,N | Appointment.appointmentID | To indicate the appointmentID of the offered appointment. | +| appointmentPremiseID | M,N | AppointmentPremise.appointmentPremiseID | To indicate the appointment PremiseID of the offered premises. | +| appointmentTimeSlotList | M,N | SET OF AppointmentTimeSlot.appointmentTimeSlotID | To indicate the appointmentTime SlotID of the offered time slots. | + +##### 8.2.6.1.3 Triggering event + +###### 8.2.6.1.3.1 From state + +Unscheduled AND Scheduling. + +| Assertion name | Definition | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unscheduled | There is no time slot for the appointment; the SP wants to offer the SC some convenient time slots for carrying out activities at the SC's premises. | +| Scheduling | There are some time slots but these time slots offered are not enough to complete the work, and the SP wants to offer the SC some convenient time slots for carrying out the activities at the SC's premises. | + +###### 8.2.6.1.3.2 To state + +WaitingForConfirmation. + +| Assertion name | Definition | +|------------------------|-------------------------------------------------------| +| WaitingForConfirmation | Waiting for the SC to confirm the offered time slots. | + +#### 8.2.6.2 Notification notifyAppointmentChanged(O) + +##### 8.2.6.2.1 Definition + +After the attributes of the appointment have been changed, the SP notifies the SC of the changed values. + +##### 8.2.6.2.2 Input parameters + +| Parameter name | Qualifiers | Matching Information/
Information Type/
Legal Values | Comment | +|-----------------|------------|------------------------------------------------------------|-----------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the appointment to be changed. | +| spContactPerson | O, Y | Appointment.spContactPerson | The new spContactPerson. | +| spContactInfo | O, Y | Appointment.spContactInfo | The new spContactInfo. | +| scContactPerson | O, Y | Appointment.scContactPerson | The new scContactPerson. | +| scContactInfo | O, Y | Appointment.scContactInfo | The new scContactInfo. | +| reportPeriod | O, Y | Appointment.reportPeriod | The new reportPeriod. | +| additionalInfo | O, Y | Appointment.additionalInfo | The new additionalInfo. | + +##### 8.2.6.2.3 Triggering event + +###### 8.2.6.2.3.1 From state + +AppointmentAttrChangedBySP. + +| Assertion name | Definition | +|----------------------------|----------------------------------------------------------------| +| AppointmentAttrChangedBySP | The attributes of the appointment have been changed by the SP. | + +###### **8.2.6.2.3.2 To state** ChangeAcknowledgedBySC. + +| Assertion name | Definition | +|------------------------|----------------------------------------------------| +| ChangeAcknowledgedBySC | The changed attributes are acknowledged by the SC. | + +#### **8.2.6.3 Notification notifyAppointmentCancelled(O)** + +##### **8.2.6.3.1 Definition** + +After the appointment has been cancelled, the SP notifies the SC. + +##### **8.2.6.3.2 Input parameters** + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|-------------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the appointment to be cancelled. | + +##### **8.2.6.3.3 Triggering event** + +###### **8.2.6.3.3.1 From state** + +AppointmentCancelled. + +| Assertion name | Definition | +|----------------------|-------------------------------------| +| AppointmentCancelled | The appointment has been cancelled. | + +###### **8.2.6.3.3.2 To state** + +CancellationAcknowledgedBySC. + +| Assertion name | Definition | +|------------------------------|----------------------------------------------------------------| +| CancellationAcknowledgedBySC | The cancellation of the appointment is acknowledged by the SC. | + +#### **8.2.6.4 Notification notifyRequestOfRescheduleAppointment(O)** + +##### **8.2.6.4.1 Definition** + +When the SP wants to reschedule an appointment, the SP notifies the SC of the request. + +##### **8.2.6.4.2 Input parameters** + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|------------------------|------------|------------------------------------------------------------|---------------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the appointment to be rescheduled. | +| rescheduleReason | M, N | Appointment.rescheduleReason | To indicate the reschedule reason. | +| appointmentPremiseList | O, Y | SET OF AppointmentPremise.appointmentPremiseID | To indicate the appointment of the premises to be rescheduled. | + +##### 8.2.6.4.3 Triggering event + +###### 8.2.6.4.3.1 From state + +Confirmed&PriorToAppTime. + +| Assertion name | Definition | +|--------------------------|------------------------------------------------------------------------------| +| Confirmed&PriorToAppTime | The appointment state is confirmed, and it is prior to the appointment time. | + +###### 8.2.6.4.3.2 To state + +Rescheduling. + +| Assertion name | Definition | +|----------------|------------------------------------------------------| +| Rescheduling | Waiting for the SC to accept or decline the request. | + +#### 8.2.6.5 Notification notifyRequestOfCancelAppointment(O) + +##### 8.2.6.5.1 Definition + +When the SP wants to cancel an appointment, the SP notifies the SC of the request. + +##### 8.2.6.5.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|-------------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the appointment to be cancelled. | +| cancelReason | M, N | Appointment.rescheduleReason | To indicate the cancel reason. | + +##### 8.2.6.5.3 Triggering event + +###### 8.2.6.5.3.1 From state + +PriorToAppTime. + +| Assertion name | Definition | +|----------------|--------------------------------------| +| PriorToAppTime | It is prior to the appointment time. | + +###### 8.2.6.5.3.2 To state + +Cancelling. + +| Assertion name | Definition | +|----------------|------------------------------------------------------| +| Cancelling | Waiting for the SC to accept or decline the request. | + +#### 8.2.6.6 Notification notifyFailureToKeepApp(O) + +##### 8.2.6.6.1 Definition + +When the SP wants to notify the failures to keep an appointment to the SC, the SP notifies the SC. + +##### 8.2.6.6.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|-------------------------|------------|------------------------------------------------------------|------------------------------------------------------------------| +| appointmentID | M, N | Appointment.appointmentID | To indicate the appointmentID of the failure appointment. | +| appointmentPremiseID | O, Y | AppointmentPremise.appointmentPremiseID | To indicate the appointmentPremiseID of the failure premises. | +| appointmentTimeSlotList | O, Y | SET OF AppointmentTimeSlot.appointmentTimeSlotID | To indicate the appointmentTimeSlotID of the failure time slots. | + +##### 8.2.6.6.3 Triggering event + +###### 8.2.6.6.3.1 From state + +SPFailureToKeepAppointment. + +| Assertion name | Definition | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| SPFailureToKeepAppointment | The SP has changed the appointment and AppointmentTimeSlot state to FailureToKeep, but the SC has not acknowledged this information. | + +###### 8.2.6.6.3.2 To state + +SCAcknowledgedRejection. + +| Assertion name | Definition | +|-------------------------|---------------------------------------------------------------| +| SCAcknowledgedRejection | The SC acknowledges the SP's failure to keep the appointment. | + +#### 8.2.6.7 Notification notifyReportProvided (O) + +##### 8.2.6.7.1 Definition + +When the SP wants to provide an appointment report to the SC, the SP can use this notification to notify the SC. + +##### 8.2.6.7.2 Input parameters + +| Parameter name | Qualifiers | Matching information/
Information type/
Legal values | Comment | +|----------------|------------|------------------------------------------------------------|-----------------------------------------| +| reportContent | M | AppointmentReport.reportContent | It indicates the content of the report. | + +##### 8.2.6.7.3 Triggering event + +###### 8.2.6.7.3.1 From state + +ReportOfAppointmentGenerated. + +| Assertion name | Definition | +|------------------------------|---------------------------------------------| +| ReportOfAppointmentGenerated | The SP has generated an appointment report. | + +###### 8.2.6.7.3.2 To state + +ReportSentToSC. + +| Assertion name | Definition | +|----------------|---------------------------| +| ReportSentToSC | The report is sent to SC. | + +### 8.2.7 Scenario + +#### 8.2.7.1 Appointment scheduling + +##### 8.2.7.1.1 SP requests SC to offer time slots and SP accepts them + +![Sequence diagram of appointment scheduling scenario 1](4d5d6207a6d444ae745057ebc3ddcd86_img.jpg) + +``` +sequenceDiagram + actor SP + actor SC + Note left of SC: : SC + Note right of SP: : SP + SP->>SC: 1: notifyRequestForTimeSlots() + activate SC + SC-->>SP: 2: offerTimeSlots() + activate SP + SP-->>SC: 3: notifyAcceptanceOfTimeSlot() + deactivate SP + deactivate SC +``` + +The sequence diagram illustrates the interaction between two lifelines, **: SC** (Service Controller) and **: SP** (Service Provider). The interaction consists of three messages: 1. **notifyRequestForTimeSlots()** sent from SP to SC; 2. **offerTimeSlots()** sent from SC to SP; 3. **notifyAcceptanceOfTimeSlot()** sent from SP to SC. Activation bars are shown on each lifeline to indicate the period of execution for each message. + +Sequence diagram of appointment scheduling scenario 1 + +Figure 10 – Sequence diagram of appointment scheduling scenario 1 + +##### **8.2.7.1.2 SP offers time slots, SC declines them and offers some new time slots, SP accepts them** + +![Sequence diagram for appointment scheduling scenario 2](e5ded249943a879ef58cae5b6b87c576_img.jpg) + +``` +sequenceDiagram + actor SC + actor SP + Note left of SC: SC + Note right of SP: SP + SP->>SC: 1: notifyTimeSlotsOffered() + activate SC + SC->>SP: 2: denyTimeSlot() + deactivate SC + activate SC + SC->>SP: 3: offerTimeSlots() + deactivate SC + activate SP + SP->>SC: 4: notifyAcceptanceOfTimeSlot() + deactivate SP +``` + +This sequence diagram illustrates the interaction between a Service Consumer (SC) and a Service Provider (SP) for appointment scheduling. The sequence of messages is: 1. SP sends `notifyTimeSlotsOffered()` to SC; 2. SC responds with `denyTimeSlot()`; 3. SC then sends `offerTimeSlots()` to SP; 4. Finally, SP replies with `notifyAcceptanceOfTimeSlot()` to SC. Activation bars are shown for both participants during the message exchanges. + +Sequence diagram for appointment scheduling scenario 2 + +**Figure 11 – Sequence diagram of appointment scheduling scenario 2** + +#### **8.2.7.2 Appointment confirmation** + +![Sequence diagram for appointment confirmation scenario](b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg) + +``` +sequenceDiagram + actor SC + actor SP + Note left of SC: SC + Note right of SP: SP + SP->>SC: 1: notifyRequestForConfirmation() + activate SC + SC->>SP: 2: confirmAppointment() + deactivate SC +``` + +This sequence diagram shows the interaction for appointment confirmation between SC and SP. The sequence consists of two messages: 1. SP sends `notifyRequestForConfirmation()` to SC; 2. SC responds with `confirmAppointment()` to SP. Activation bars are present for both participants during the interaction. + +Sequence diagram for appointment confirmation scenario + +**Figure 12 – Sequence diagram of appointment confirmation scenario** + +#### 8.2.7.3 Appointment change + +##### 8.2.7.3.1 SC requests to reschedule appointment and SP accepts it + +![Sequence diagram for scenario 1: SC requests to reschedule appointment and SP accepts it.](c06fd7dbef68a8b788158f2081d9d734_img.jpg) + +``` +sequenceDiagram + actor SC + actor SP + Note left of SC: SC + Note right of SP: SP + SC->>SP: 1: requestRescheduleAppointment() + activate SP + SP-->>SC: 2: notifyAcceptanceOfRescheduleAppointment() + deactivate SP + activate SC + deactivate SC +``` + +This sequence diagram illustrates the interaction between a Service Controller (SC) and a Service Provider (SP) for scenario 1. The SC sends a message '1: requestRescheduleAppointment()' to the SP. The SP activates and responds with '2: notifyAcceptanceOfRescheduleAppointment()'. The SC then activates to process the response. + +Sequence diagram for scenario 1: SC requests to reschedule appointment and SP accepts it. + +Figure 13 – Sequence diagram of appointment change scenario 1 + +##### 8.2.7.3.2 SP requests to reschedule appointment and SC rejects it + +![Sequence diagram for scenario 2: SP requests to reschedule appointment and SC rejects it.](a634891d16b60b21df90a35c2af72c67_img.jpg) + +``` +sequenceDiagram + actor SC + actor SP + Note left of SC: SC + Note right of SP: SP + SP->>SC: 1: notifyRequestOfRescheduleAppointment() + activate SC + SC-->>SP: 2: rejectRescheduleAppointment() + deactivate SC + activate SP + deactivate SP +``` + +This sequence diagram illustrates the interaction between a Service Controller (SC) and a Service Provider (SP) for scenario 2. The SP sends a message '1: notifyRequestOfRescheduleAppointment()' to the SC. The SC activates and responds with '2: rejectRescheduleAppointment()'. The SP then activates to process the response. + +Sequence diagram for scenario 2: SP requests to reschedule appointment and SC rejects it. + +Figure 14 – Sequence diagram of appointment change scenario 2 + +##### **8.2.7.3.3 SP requests additional time slots when appointment is being performed and SC accepts them** + +![Sequence diagram for appointment change scenario 3](c98721cd60df9be3ed129ce2345d763d_img.jpg) + +A sequence diagram showing the interaction between two lifelines, **: SC** (left) and **: SP** (right). The sequence of messages is as follows: + +- 1: `notifyTimeSlotsOffered()` from **: SP** to **: SC** +- 2: `acceptTimeSlot()` from **: SC** to **: SP** + +Sequence diagram for appointment change scenario 3 + +**Figure 15 – Sequence diagram of appointment change scenario 3** + +#### **8.2.7.4 Appointment cancellation** + +##### **8.2.7.4.1 SC requests to cancel appointment and SP accepts it** + +![Sequence diagram for appointment cancellation scenario](60a40901e77feeb97ab6cf9c6d9418c3_img.jpg) + +A sequence diagram showing the interaction between two lifelines, **: SC** (left) and **: SP** (right). The sequence of messages is as follows: + +- 1: `requestCancelAppointment()` from **: SC** to **: SP** +- 2: `notifyAcceptanceOfCancelAppointment()` from **: SP** to **: SC** +- 3: `cancelAppointment()` from **: SC** to **: SP** + +Sequence diagram for appointment cancellation scenario + +**Figure 16 – Sequence diagram of appointment cancellation scenario** + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3345-200905-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3345-200905-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2e3c3dd5b553db73173babc260ef90dcafb1c6b --- /dev/null +++ b/marked/M/T-REC-M.3345-200905-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81351660026f219f0f6b8034e7a8b0024dd436e5b5b3f403f84dbd083acbeb2a +size 107624 diff --git a/marked/M/T-REC-M.3345-200905-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/M/T-REC-M.3345-200905-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a20d4d517006b02d2524a5d878d35424ad968f6b --- /dev/null +++ b/marked/M/T-REC-M.3345-200905-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e67048e0376c020c4d3855158814e97e2a0a59291cbf0db0c6d69f5ceefce21 +size 123113 diff --git a/marked/M/T-REC-M.3345-200905-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3345-200905-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa5890d7660182e6ea2597ef6f4f97b38dc528f --- /dev/null +++ b/marked/M/T-REC-M.3345-200905-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2759a9d96780947e8b6f3adf0ab0278c50853804bbc381405464bb9b4dd91ad +size 6986 diff --git a/marked/M/T-REC-M.3345-200905-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/M/T-REC-M.3345-200905-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8130da1a9f4de956069c0d20bbaa5810fc825cf0 --- /dev/null +++ b/marked/M/T-REC-M.3345-200905-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5372a12f4240df2cf0dd1afcbdebc495e5486f78240e995c0f211429d759279c +size 284948 diff --git a/marked/M/T-REC-M.3345-200905-I_PDF-E/raw.md b/marked/M/T-REC-M.3345-200905-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..be0214efe0eb05643cf4829903dece96a8926f39 --- /dev/null +++ b/marked/M/T-REC-M.3345-200905-I_PDF-E/raw.md @@ -0,0 +1,627 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3345** + +(05/2009) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Principles for self-service management** + +Recommendation ITU-T M.3345 + +![ITU logo: International Telecommunication Union](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a stylized globe with a red lightning bolt striking through it, and the text "ITU International Telecommunication Union" to its right. + +ITU logo: International Telecommunication Union + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T M.3345** + +# **Principles for self-service management** + +## **Summary** + +Recommendation ITU-T M.3345 defines the requirements and a generic framework for self-service management. It provides a basic description of self-service management and its importance to service providers in NGN. This Recommendation also illustrates the benefits and application of self-service management. + +## **Source** + +Recommendation ITU-T M.3345 was approved on 29 May 2009 by ITU-T Study Group 2 (2009-2012) under Recommendation ITU-T A.8 procedures. + +## **Keywords** + +Customer, next generation network, self-service, self-service authorized user, self-service management, self-service manager, self-service management actor, self-service management interface, ssm reference point, user. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|-----------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Introduction ..... | 3 | +| 5.1 General ..... | 3 | +| 5.2 Basic function of self-service management..... | 5 | +| 5.3 Other features ..... | 5 | +| 6 Basic objective of self-service management..... | 6 | +| 6.1 Field of application..... | 9 | +| 7 Requirements ..... | 9 | +| 7.1 Basic SSM requirements ..... | 9 | +| 7.2 Security requirements ..... | 10 | +| 7.3 SSM interface requirements ..... | 11 | +| 8 SSM architecture overview..... | 11 | +| Appendix I – Examples of self-service management scenarios..... | 12 | +| Bibliography..... | 16 | + +# Introduction + +In the telecommunications market, most service providers are facing a business transformation produced by the open-market transition initiatives of regulatory bodies, resulting in the need to lower their costs and increase their responsiveness to customers. Service providers need to: + +- offer more flexible service choices to the customer/user; +- provide greater customer/user involvement in managing their service; +- increase the quality of interaction between the customer/user and the service provider; +- increase the service availability; +- provide customers/users with self-help in lifecycle operations of the service (i.e., from pre-order to decommissioning); and +- reduce the service provider's costs of operation. + +Self-service capabilities offer reduced operation costs for service providers and enhanced quality of experience (QoE) to the customer. Self-service enables the service provider to maintain high service quality and lower operations cost. By empowering customer/user to manage his/her own services, the service provider drives up the QoE for the customer/user and enhances customer loyalty. + +The purpose of this Recommendation is to define the self-service management requirements and provide a base self-service management implementation for all types of telecommunication services (traditional network and telecommunication, NGN, etc.). The self-service management is applicable to service provider, network operator, and content provider's operations support systems for the whole lifecycle processes. In this Recommendation, self-service can be applied to all phases of the service lifecycle from pre-order to termination and transition. + +NOTE – Content providers also benefit from enhanced customer self-service experience. Customers may use self-service to browse, select and subscribe to content from product catalogues without involving directly the content provider. + +## Recommendation ITU-T M.3345 + +# Principles for self-service management + +# 1 Scope + +This Recommendation defines the requirements, functional architecture and the concepts for self-service management. + +The self-service management functions covered in this Recommendation include customer relationship management, fulfilment, assurance, and billing. The applicability of self-service management to drive strategy, infrastructure and product lifecycle management is considered for further study and outside the scope of this Recommendation. + +# 2 References + +None. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 B2B/C2B interface** [b-ITU-T M.3060]: Synonymous to X interface. + +**3.1.2 b2b/c2b reference point** [b-ITU-T M.3060]: Synonymous to x reference point. + +**3.1.3 business process** [b-ITU-T M.3050.4]: Activity that a business can engage in (and for which it would generally want one or more partners). + +**3.1.4 content provider (CP)** [b-ITU-T J.90]: The entity that provides the creative content of a programme (e.g., the programme producer or the owner of its rights). + +**3.1.5 customer:** [b-ITU-T M.3050.1] The customer buys products and services from the service provider or enterprise, or receives free offers or services. A customer may be a person or a business. + +**3.1.6 enterprise** [b-ITU-T M.3050.1]: Enterprise is used to refer to the overall business, corporation or firm, which is using the eTOM framework for modelling its business processes. The enterprise is responsible for delivering products and services to the customer. It is assumed that the enterprise is an information and communications service provider or consumer. + +**3.1.7 interface** [b-ITU-T M.3010]: An architectural concept that provides interconnection between physical blocks at reference points. + +**3.1.8 managed resource** [b-ITU-T M.3010]: The abstraction of those aspects of a telecommunication resource (logical or physical) required for telecommunications management. + +**3.1.9 management function** [b-ITU-T M.3010]: The smallest part of a management service as perceived by the user of the service. + +**3.1.10 management service** [b-ITU-T M.3010]: A management service is an offering fulfilling specific telecommunications management needs. + +**3.1.11 next generation networks management (NGNM)** [b-ITU-T M.3060]: Planning, provisioning, installation, maintenance, operation and administration of next generation telecommunications equipment for transmission or control of resources and services within NGN transport and service strata. + +**3.1.12 operations system (OS)** [b-ITU-T M.3010]: A physical block which performs operations systems functions. + +**3.1.13 product** [b-ITU-T M.3050.1]: Product is what an entity (supplier) offers or provides to another entity (customer). Product may include service, processed material, software or hardware, or any combination thereof. A product may be tangible (e.g., goods) or intangible (e.g., concepts) or a combination thereof. However, a product ALWAYS includes a service component. + +**3.1.14 reference point** [b-ITU-T M.3010]: An architectural concept used to delineate management function blocks and which defines a service boundary between two management function blocks. + +**3.1.15 service** [b-ITU-T M.3050.1]: Services are developed by a service provider for sale within products. The same service may be included in multiple products, packaged differently, with different pricing, etc. + +**3.1.16 service provider (SP)** [b-ITU-T M.3050.1]: A service provider enterprise that sells information and/or communications services to other parties. + +**3.1.17 telecommunications management network** [b-ITU-T M.3010]: An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services. + +**3.1.18 user** [b-ITU-T M.3050.1]: The user is the actual user of the products or services offered by the service provider or enterprise. The user consumes the product or service. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 authorization:** It presents how, and under what conditions, self-service management actors can use self-service functions and what self-service actions they are permitted to perform. + +**3.2.2 self-service authorized user:** The user of the self-service management service with authorization obtained from the self-service manager, limited to the use of Self-service management. The authorizations may be for services or content, provided independently of the service provider defined in the contract. + +**3.2.3 self-service management (SSM):** The management service which supports management functions for telecommunication services or networks at an SSM actor's request. + +**3.2.4 self-service management actor (SSM actor):** The user of self-service management who may be either a self-service manager or a self-service authorized user. + +**3.2.5 self-service management interface:** An interface applied at the self-service management reference point, which provides connection and interaction between a self-service management actor and the self-service management function block defined in the SP's domain or OSS. + +**3.2.6 self-service manager:** The user of the self-service management functions with the highest levels of authorization, which means that they can perform all contractually defined self-service actions between the service provider and the customer. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------| +| B2B | Business-to-Business | +| C2B | Customer-to-Business | +| eTOM | enhanced Telecom Operations Map | +| NGN | Next Generation Networks | +| NGNM | NGN Management | +| NO | Network Operator | +| OS | Operations System | +| OSS | Operations Support System | +| PSTN | Public Switched Telephone Network | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| SC | Service Customer | +| SLA | Service Level Agreement | +| SMS | Security Management System | +| SP | Service Provider | +| SS | Self-Service | +| SSM | Self-Service Management | +| SSMA | Self-Service Management Actor | +| SU | Service User | +| TMF | TeleManagement Forum | + +# **5 Introduction** + +## **5.1 General** + +Self-service in telecommunications is generally a new kind of service from both the customer's and user's perspective. This service provides new capabilities, features and benefits in service for the customer/user. By transferring management responsibility for the use of the service to the customer, self-service establishes a customer-facing interface for the service's OSS. The service provider benefits from reduced operational costs and a customer-perceived increase in ease of use and in the quality of service. + +Self-service may be used differently by different customers: individuals, family members, enterprise authorized users, or other self-service users. + +Self-service users may be either a manager within a customer organization, who manages the service directly, or other users authorized to manage some service instances. Users duly authorized to perform management operations on the service are SSM authorized users. Users who cannot change any aspect of the service are called SSM users. SSM users may only execute the functions enabled by the authorized users. Authorized users are not allowed to propagate authorizations. + +Self-service management provides management functions for both the telecommunication network and services at a SSM actor's request and provides a more efficient interaction between SSM actors and service providers. As an example, interactions performed by the SSM actor include user initiated ordering, service inquiry, billing inquiry, trouble reporting, maintenance oversight and management, performance reporting and management, and network management for resource intensive services. The goal of SSM is to enable zero-touch interactions, where appropriate, and to facilitate multi-touch by the service provider, when needed. Zero touch means the execution of a user request to configure or re-configure a service without a human at the service provider helpdesk or provisioning group having to take any action. Zero touch means that a user orders, configures, and manages his/her service without the need to get another human involved in the process to manage the service. + +### **5.1.1 Customer/user benefits** + +Some customer/user benefits from self-service are listed below: + +- allows for self-configuration of: + - service selection, + - change of service parameters at the customer level, super-user level, or user level, + - activation and deactivation of a service, + - service restriction for authorization controls, + - service termination; +- service and resource availability check; +- service notification, alarm, payment setting; +- trouble-shooting; +- support functions access; +- online ordering; +- online billing; +- customer/user experience report to the service provider; +- improved customer satisfaction; +- improved customer loyalty; +- shortened delivery time for provisioning; +- shortened outage period for repair; +- improved access to market and product/service information; +- improved interaction with the service provider and content provider; +- service specific help, independently of helpdesk functions. + +### **5.1.2 Service provider benefits** + +Some of service provider benefits are listed below: + +- enhanced capability to track customer/user experience of a service; +- ability to create a service customer/user profile, based on the customer/user actions, collected in a historical period of use; +- reduced maintenance cost; +- reduced operation cost; +- reduced marketing cost; +- ability to target marketing based on the customer/user history; + +- ability to target marketing based on the geographic location and other demographics; +- ability to target trials based on customer/user history, or the geographic location or other demographics; +- improved user-perceived quality of service; +- provide new product/service easier; +- provide directed marketing and drive impulse buying; +- enhanced service rollout process; +- simplified business processes; +- retain service customer loyalty through enhancing the service customer QoE; +- shortened delivery time of fulfilment of telecom product/service; +- shortened time to resolve problems of customer service; +- improved publishing of marketing and promotion information through ancillary service product use; +- improved interaction with the customer/user; +- reduced workload on service customer resources; +- increased service provider's profit. + +## **5.2 Basic function of self-service management** + +Self-service management has the following aspects: + +- to manage SSM actor requests for fulfilment, assurance and billing; +- to enable a user-friendly way for the SSM actor, to use self-service management; +- to enable an efficient and user-friendly communication mechanism between the SSM actor and the service provider. + +## **5.3 Other features** + +### **5.3.1 Online customer self-analysis** + +Service customers, like large enterprises and call-centres, are very sensitive to the telecom service they are using because the telecom service is one of the key factors that impact their business. Like call centres, the customers always need incoming-call analysis to measure and manage: + +- resource usage and availability ration analysis; +- traffic flow analysis; +- total calls received per month or per day; +- ratio of calls lost or received; +- busy call time window; +- average lasting-time per call. + +Under these situations, a SSM actor's service analysis will provide the features that the customers require to analyse the telecom service impacting their business. Key performance indicators are selected on a service-specific basis and are monitored to accurately reflect the impact of performance issues on the customer's business, to enable effective governance and allowing service providers to focus on process improvements. + +### **5.3.2 Online interaction management** + +This feature provides an interaction capability between customers/users and service providers, even among the customers/users who are using services from multiple service providers or content providers like IPTV or online gaming. + +The online interaction management has the following different types of interactions: + +- service evaluation, like the user-perceived quality of experience; +- SSM actors active comments or suggestions to improve the service received during the online session; +- new customization requirements; +- community exchange or sharing of online interactions to strengthen the links among the customers/users. + +The online interaction may be real-time during service usage or may be after the service session is terminated. + +### **5.3.3 Message publishing** + +It is necessary for most telecom operators to publish some messages or information to their service customers via web or mobile content. In SSM, features of message publishing, combined with effective mobile marketing and management, will offer to the customers enhanced user-specific targeted marketing to drive up impulse purchases of services. The messages can be categorized as follows: + +- new service message announcement; +- marketing promotion messages; +- telecom service/network event report including specials and promotions; +- general notifications (e.g., disaster or other public service announcements). + +### **5.3.4 Customer online shopping** + +Customers/users can use SSM for online business purposes including: + +- service shopping provided by telecom operators; +- online shopping: prepaid card, handsets, MP3 players, books, etc.; +- online billing payment; +- service customer credits exchange; +- subscriber or customer management. + +# **6 Basic objective of self-service management** + +SSM requires an agreement and a contractual relationship between customers and service providers as an optional precondition. In all cases, use of a service or content implies a contractual relationship only between the customer/user and the service or content provider. However, in some cases, the service provider "offers" the services or content to the customer/user as an agent of the service or content provider. In that case, the contract is still between the service or content provider and the transport or other service provider. The service customer always is the recipient party in the n-party contract for services. A customer/user who uses a SSM function is a SSM user. In some cases, the customer/user may give rights and authority to another user to act on their behalf in granting access to services or content. This special class of user is the SSM manager; i.e., a user authorized to act as an agent of the customer/user to grant others access to "use" the service. The + +SSM user, customer/user, and SSM manager are key SSM actors in the delivery of self-service management. + +This Recommendation will consider two possible roles of SSM user: + +Role 1: an SSM user with overall authorization is a self-service manager (SS manager), + +Role 2: an SSM user with authorization obtained from the self-service manager is a self-service authorized user (SS authorized user) + +Authorization determines how and under what conditions and what functions are available to the SSM users. It is anticipated that the role of the SSM manager is the customer or subscriber responsible for the payment of the bill. SSM users utilize SSM services to obtain content provider or service provider services after being authorized by the SSM manager to perform the actions. + +Figure 1 shows the SSM roles and interfaces (SS manager, self-service authorized user, service provider, SSM, SSM interfaces) in the general services framework from [b-ITU-T M.3340]. + +![Diagram illustrating the roles and interfaces in SSM (Service Service Management).](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +The diagram illustrates the roles and interfaces in SSM (Service Service Management). The central component is a stack of boxes labeled "Service provider", with a dashed box labeled "SSM" inside the top box. The "SSM" box is highlighted with a red lightning bolt symbol. + +Key roles and their interactions: + +- Service customer**: Interacts with the "Service provider" via "Contract" and "Use management service" interfaces. It also "Authorizes" the "Self-service manager (SSM actor)" and "Service user". +- Self-service manager (SSM actor)**: Receives authorization from the "Service customer" and "Authorizes" two "Self-service authorized user (SSM actor)" boxes. It has a red line labeled "SSM interface" connecting to the "SSM" box, which is marked with a red lightning bolt and an 'X'. +- Self-service authorized user (SSM actor)**: Two boxes receive authorization from the "Self-service manager (SSM actor)". +- Service user**: Receives authorization from the "Service customer" and "Use NGN service" from the "Network". +- Content Provider**: Provides content to the "Service provider" via "Provide content" and "Contract" interfaces. +- Service provider**: A stack of boxes below the main "Service provider" box. It interacts with the main "Service provider" via "Contract" and "Use management service" interfaces. +- Network operator**: A stack of boxes that interacts with the main "Service provider" via "Contract" and "Use management service" interfaces. It "Manages" the "Network". +- Network**: Represented by an oval, it provides "Use NGN service" to the "Service user" and is managed by the "Network operator". + +Diagram illustrating the roles and interfaces in SSM (Service Service Management). + +Figure 1 – Roles and interfaces in SSM + +The SSM interfaces augment the SC to SP, SU to NO, and SC to SU entities shown above. The SSM actor is "authorized" by the SC to not only perform SSM, but also to authorize other users as SSM authorized users. Once authorized to perform SSM functions, the SSM authorized users or SSM actors utilize the SSM interface to the SSM processes in the service provider to perform SSM. Each user or subscriber must be mapped to a profile entity in the SSM to perform any SSM functions. The SSM will maintain historical usage information related to service provider or content provider service to customize a product catalogue for each user. + +## 6.1 Field of application + +Here are some service examples that may be managed by a SSM, at SSM actors requests: + +- fixed phone service, +- mobile phone service, +- IP-based service like IPTV. + +See scenario 2 in Appendix I. + +# 7 Requirements + +## 7.1 Basic SSM requirements + +- The ability to exchange and transfer management information between the SSM actor and the service provider. +- The ability to analyse and react appropriately to management information. +- The ability to manipulate management information into a form which is useful and/or meaningful to the SSM actor. +- The ability to deliver management information to the SSM actor and the SP, and to present it with the appropriate representation. +- The ability to ensure secure access to management information by the SSM actor. +- Build service customer profile based on information other than basic service customer account information (e.g., name, address, billing information) to get more service customer information and feedback to guide selling. +- The ability for the service provider to offer marketing to service customers. +- The ability for SSM actors to choose multiple services. +- The ability for SSM actors to select options and parameters and personalize services (e.g., select service options, personalize billing, personalize trouble reports). +- Fulfil the following requirements from [b-ITU-T M.3060]: + - Provide the management capabilities that will enable organizations offering NGN end-user services to offer customers the ability to personalize end-user services and to create new services from service capabilities (potentially from different service providers). + - Provide the management capabilities that will enable organizations offering NGN services to provide end-user service improvements including customer self-service (e.g., provision of service, reporting faults, online billing reports). +- To provide to the SSM actors the following service fulfilment requirements: + - Telecom product/service catalogue and price check. + - Telecom service check and selection. + - Telecom resource and service availability check. + +- Service ordering and activation online. +- Service change or update, service parameter self-configuration. +- Service pause. +- Service termination. +- Service notification, alarm, payment setting. +- To provide to the SSM actors the following service assurance requirements: + - Online fault/problems report. + - Online service parameter test like broadband test. + - Online real-time performance/SLA test. + - Online resource availability and status check. + - Trouble report and troubleshooting. + - Historic data inquiries, including quality test and fault. + - Online customer service, etc. +- To provide to the SSM actors the following service billing requirements: + - Historic bill report and inquiries. + - Real-time billing report and inquiries. + - Real-time usage report and inquiries. + - Billing and usage contrast. + - Billing mode selection and change. + - Online payment. + - Prepaid service check: + - Rest money check. + - Usage check. + - Electronic bill setting: + - Email bill setting. + - Email bill cancel. + +## 7.2 Security requirements + +SSM deals with proprietary content and important data and information about the service customer and service user. For that reason, data and information security must be a high priority. + +For the secure use of a SSM, the following items need to be considered: + +- authentication: This is required to verify the claimed identity. SSM actor ID, static password and dynamic password may be used for SSM actor authentication; +- authorization: Enables certain actions after authentication. This ensures that only the authorized SSM actor can be allowed access to the SSM; +- access control: To ensure that actors are prevented from gaining access to information that they are not authorized to access. Access control security mechanisms ensure that only SSM actors are allowed to manage system security resources; +- security event and alarm reporting: When SSM actors are performing key activities like logging-in, activating or modifying service parameters, logging-out, it is important to ensure that security alerts be monitored, logged, and monitored for compliance with the service security policy; +- data and information assurance is high priority; + +- service customer and service user information protection is high priority. + +## **7.3 SSM interface requirements** + +General requirements for the SSM interface which provide a SSM actor access (connection and interaction) to the self-service management consist of the following: + +- access is independent from the type of service; +- due to the varieties of devices, mapping of interface functions to user controls should be intuitive and easy to use; +- SSM interface should be supported by all terminals. + +NOTE – This requirement does not mean that all content or service types shall be capable on all terminal types. + +# **8 SSM architecture overview** + +The detailed self-service management architecture (business process, functional architecture, information architecture and physical architecture) will be for further study. + +# Appendix I + +## Examples of self-service management scenarios + +(This appendix does not form an integral part of this Recommendation) + +### Scenario 1 of SSM + +Service provider: Mobile service provider. + +Service: Mobile (business group). + +Customer: Company. + +Users: Employers. + +SSM user: SSM actor. + +Access to the self-service management: Via internet or via mobile phone. + +**Select from the menu:** Service configuration (performed by SSM actor with authorization 1): + +For the number 0XX/xxxxx0: in period ..... , only received calls, + +For the number 0XX/xxxxx1: in period ..... , only received calls and dial numbers from the group, + +For the number 0XX/xxxxx2: possibility to dial only next three numbers 1), 2), 3), + +For the number 0XX/xxxxx3: monthly amount is ..... , after that, dial only number ..... + +**Select from the self-service menu:** Service check (performed by SSM actor with authorization 2): + +Number 0XX/xxxxx4 is not available at the moment: check (is it a network problem, or is the mobile phone turned off?). + +**Select from the self-service menu:** Customer/user experience (performed by SSM actor with authorization 1): + +In region ..... signal is very low, + +In region ..... mobile service is not available. + +**Select from the self-service menu:** Billing/billing check (performed by SSM actor with authorization 3): for the numbers 1), 2) and 3) in period ..... they spend? + +**Select from the self-service menu:** Billing/pay the service (performed by self-service manager with overall authorization), (electronic confirmation, no more paper bill, no need to go to the bank, spend time, pay provision....) + +Figure I.1 shows an example of the SSM described in this appendix. + +Figure I.2 shows the 2 roles of the SSM actors: one as a self-service manager and the other as an SSM authorized user. + +![Diagram illustrating the SSM implementation architecture. It shows a Mobile network Service Provider connected to two Internet Service Providers via the internet. The provider's Self-service Management system is connected to an SSM Manager laptop. The SSM Manager is linked to a Private net and a workstation. Two mobile base stations are shown, each connected to an SSM Authorized User (represented by a person icon) who has access to a SELF SERVICE MENU. The entire system is centered around a POSSIBLE SSMA WORKSTATION.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the SSM implementation architecture. At the top left, a **Mobile network Service Provider** (represented by a building with a satellite dish) contains a **Self-service Management** system. This system is connected via a red arrow to an **internet** cloud, which is further connected to **Internet Service Provider 1**. Another red arrow from the **Self-service Management** system points to a second **internet** cloud, which is connected to **Internet Service Provider 2**. Both **internet** clouds have red arrows pointing to a central **SSM Manager** (represented by a laptop). The **SSM Manager** is connected to a **Private net** cloud and a workstation. The workstation is connected to an **SSM Authorized User** (represented by a person icon) who has access to a **SELF SERVICE MENU**. The **SSM Manager** is also connected to a **POSSIBLE SSMA WORKSTATION** (represented by a yellow oval). Two **Mobile base station** icons (representing cell towers) are shown, each connected to an **SSM Authorized User** (represented by a person icon) who has access to a **SELF SERVICE MENU**. The **POSSIBLE SSMA WORKSTATION** is connected to all three **SELF SERVICE MENU** boxes via red dashed lines. + +Diagram illustrating the SSM implementation architecture. It shows a Mobile network Service Provider connected to two Internet Service Providers via the internet. The provider's Self-service Management system is connected to an SSM Manager laptop. The SSM Manager is linked to a Private net and a workstation. Two mobile base stations are shown, each connected to an SSM Authorized User (represented by a person icon) who has access to a SELF SERVICE MENU. The entire system is centered around a POSSIBLE SSMA WORKSTATION. + +Figure I.1 – An example of the SSM implementation + +### Scenario 2 of SSM: Scenario for IPTV service provisioning + +The SSM could provide a product that is provided by one specific service provider only, and also provide a product that is combined with other service, network or contents providers products. + +In the following scenario, the first one is the predefined product, and the second, a customizable product. + +![Sequence diagram for IPTV service provisioning showing interactions between SSM actor, SSM, SP, NO, and CP.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +| SSM actor
(SS manager, authorized user) | Self-service management (SSM) | Service provider (SP) | Network operator (NO) | Contents provider (CP) | +|--------------------------------------------|-------------------------------|-----------------------|-----------------------|------------------------| +|--------------------------------------------|-------------------------------|-----------------------|-----------------------|------------------------| + +The diagram illustrates the following sequence of interactions: + +- 1:** SSM actor requests account creation from SSM if they do not have one. +- 2:** SSM actor logs in (authorization) to the SSM. +- 3:** SSM actor requests product information (Product catalogue mgmt). +- 4:** SSM actor navigates and selects a product. A decision is made if it is a 'Predefined product'. +- 5:** If 'Yes', a request for detailed information is sent to SP 1. +- 5.1/5.2:** Order information is entered and a product offering is requested from the selected service provider (SP 1). +- 5.3/5.4:** Network or contents provisioning is requested from NO 1 or CP 1 if needed. +- 6:** If 'No' (Customizable product), the process enters a sub-flow for customization. +- 6.1/6.1':** SSM requests product info from SP 1 through SP n. +- 6.2/6.3:** SSM actor requests product info from NPs (Network Providers/Operators). +- 6.4/6.4':** SSM requests product info from NO 1 through NO n. +- 6.5/6.6:** SSM actor requests product info from CPs. +- 6.7/6.7':** SSM requests product info from CP 1 through CP n. +- 6.8/6.9:** Final selection and request for customizable product offering. +- 7 & 8:** Final confirmation and return messages between SSM and the actor. + +M.3345(09)\_FI.2 + +Sequence diagram for IPTV service provisioning showing interactions between SSM actor, SSM, SP, NO, and CP. + +**Figure I.2 – Scenario of SSM for product offering for IP-based service (IPTV)** + +- 1: Request the account creation. +- 2: Login (authorization) to the SSM. +- 3: Request product information. +- 4: Navigate (shopping) and select product. +- 5: Request the detailed information for ordering the product from SP1. +- 5.1/5.2: Enter the required order information and request product offering to the selected service provider. +- 5.3/5.4: Request the network provisioning or contents provisioning (if needed). The NO and content provider probably are predefined in the selected product by the SP. + +- 6: Request the customizable (or personalized) product, which is combined with more than two products provided by different providers. +- 6.1/6.1': Request the detailed information for ordering the product of service providers with whom there is an agreement. +- 6.2/6.3: Select product and enter the required order information, request product offering to the selected service provider. +- 6.4/6.4': Request the detailed information for ordering the product related with network provisioning from the NOs with whom there is an agreement. +- 6.5/6.6: Select product and enter the required order information, request network provisioning to the selected network provider. +- 6.7/6.7': Request the detailed information for ordering the product related with contents provisioning from the content providers with whom there is an agreement. +- 6.8/6.9: Select product and enter the required order information, request contents provisioning to the selected contents provider. +- 7: Request the progress status/state information for the requested order. +- 8: Notification of the completion of requested order. + +# Bibliography + +- [b-ITU-T J.90] Recommendation ITU-T J.90 (2000), *Electronic programme guides for delivery by digital cable television and similar methods – Reference operating scenario and requirements.* +- [b-ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network.* +- [b-ITU-T M.3016.0] Recommendation ITU-T M.3016.0 (2005), *Security for the management plane: Overview.* +- [b-ITU-T M.3016.1] Recommendation ITU-T M.3016.1 (2005), *Security for the management plane: Security requirements.* +- [b-ITU-T M.3020] Recommendation ITU-T M.3020 (2008), *Management interface specification methodology.* +- [b-ITU-T M.3050.0] Recommendation ITU-T M.3050.0 (2007), *Enhanced Telecom Operations Map (eTOM) – Introduction.* +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework.* +- [b-ITU-T M.3050.2] Recommendation ITU-T M.3050.2 (2007), *Enhanced Telecom Operations Map (eTOM) – Process decompositions and descriptions.* +- [b-ITU-T M.3050.3] Recommendation ITU-T M.3050.3 (2007), *Enhanced Telecom Operations Map (eTOM) – Representative process flows.* +- [b-ITU-T M.3050.4] Recommendation ITU-T M.3050.4 (2007), *Enhanced Telecom Operations Map (eTOM) – B2B integration: Using B2B inter-enterprise integration with the eTOM.* +- [b-ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401(2006), *Principles for the Management of Next Generation Networks.* +- [b-ITU-T M.3340] Recommendation ITU-T M.3340 (2008), *Framework for NGN service assurance management across the business to business and customer to business interfaces.* +- [b-ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c8e09512d28b9a9f0accd838a1beadfdc7e84a4 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a668697e49f1f51f10065155129742eace084c231694f6e445496fac33535090 +size 52276 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bb17156686dbb8cbed26b5cc25706c8ec7c8c5d --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeb6901656be5486d9a9a49be88130ab3fda06684b3b9315471c707880f42052 +size 40512 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0b75dd4add9bffc52ffeb565f6f8555d60bd059 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:664fce11982bca4f01d9277c05ba449ce92d3aaeec2716142a12efecff231a62 +size 31378 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f898d54735bda791f09618c3930f8d41e7179fc5 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4c20c2ca264b4e37841c384bda64f697991bf0e90d0a9bcecfc085c31e59ab +size 35925 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f59d5e1201e0070ff9baf213f20c5762df80b94a --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:948ac31a00ee6093824733124261677d91ffa4a08a451abd07d7f79dd4f4a711 +size 55201 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec349407992c0d7c4e6e5ee844035e679004f520 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77fcc34632adaf72bb4001044530834c061337073b4616b10daa98da98f19c7e +size 34861 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13b420e8e2dff03f04e06e9a3ea42e391ed488e2 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72ebf46ceef77088bb23e5e05ae447fda09fd91bf1f1173d5264501a22d9b02c +size 4034 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3540dab9f81b1c97d70dff66954a01abf5ef58d8 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d96c4aa48b7b5b56c00506484de5ed9a0bee67f69f866956c4cd408a547bb238 +size 28552 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3347-201205-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f83fc2fe90f373fbc1fafbe8c2f743c6278d560 --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e940afe19c6f6134b95fe132550cfcbc61580a255451eed8cb8418cd76c19717 +size 23382 diff --git a/marked/M/T-REC-M.3347-201205-I_PDF-E/raw.md b/marked/M/T-REC-M.3347-201205-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0ed0e0c095dc5615d36198b73fd5f12934d3e5ef --- /dev/null +++ b/marked/M/T-REC-M.3347-201205-I_PDF-E/raw.md @@ -0,0 +1,980 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3347** + +(05/2012) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Requirements for the NGN service activation +across the interface between the network +management system and the element +management system** + +Recommendation ITU-T M.3347 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3347 + +# Requirements for the NGN service activation across the interface between the network management system and the element management system + +## Summary + +Recommendation ITU-T M.3347 describes the requirements for the next generation network (NGN) service activation across the interface between the network management system (NMS) and the element management system (EMS) in the service provisioning business process. The requirements are provided using the telecommunications management network (TMN) interface specification methodology described in Recommendation ITU-T M.3020. The general requirements include subscriber configuration, user configuration, subscribed service configuration, user service relation configuration, user service relation update notification and bulk configuration. This Recommendation defines the interface requirements for each configuration function. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3347 | 2012-05-14 | 2 | + +## Keywords + +Agent, manager, NGN, OS, requirements, service, service activation, service provider. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Concepts and background..... | 3 | +| 7 Requirements ..... | 4 | +| 7.1 Business level requirements ..... | 4 | +| 7.2 Specification level requirements ..... | 10 | + +## Introduction + +ITU-T has described the provisioning function set group which is contained in configuration management [ITU-T M.3400]. The provisioning function set group consists of procedures which are necessary to bring equipment into service, not including installation. However, the interface between the network management system (NMS) and the element management system (EMS) of the service provisioning has not been defined. + +With the rapid growth of next generation networks (NGNs) and the expansion of new NGN services, it is more important for the service provider (SP) to improve the end-user experience. Consequently, it is necessary to define the NMS-EMS interface for service activation in order to improve the automation capability, effectiveness and quality of service provisioning. + +This Recommendation contains the requirements for the NGN service activation across the NMS-EMS interface. + +# Recommendation ITU-T M.3347 + +## Requirements for the NGN service activation across the interface between the network management system and the element management system + +## 1 Scope + +This Recommendation contains the requirements for the NGN service activation across the interface between the network management system (NMS) and the element management system (EMS) in the service provisioning business process. The requirements are provided using the telecommunications management network (TMN) interface specification methodology described in [ITU-T M.3020]. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T F.500] Recommendation ITU-T F.500 (1992), *International public directory services*. +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2009), *Management interface specification methodology*. +- [ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. +- [ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the Management of Next Generation Networks*. +- [ITU-T M.3208.1] Recommendation ITU-T M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*. +- [ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*. +- [ITU-T M.3702] Recommendation ITU-T M.3702 (2010), *Common management services – Notification management – Protocol neutral requirement and analysis*. +- [ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **element management function (EMF)** [ITU-T M.3060] +- 3.1.2 **interface** [ITU-T M.3010] +- 3.1.3 **network management function (NMF)** [ITU-T M.3060] +- 3.1.4 **next generation network (NGN)** [ITU-T Y.2001] + +- 3.1.5 **operations system** [ITU-T M.3010] +- 3.1.6 **Q interface** [ITU-T M.3010] +- 3.1.7 **service** [ITU-T M.3050.1] +- 3.1.8 **service provider** [ITU-T M.3208.1] +- 3.1.9 **subscriber** [ITU-T M.3050.1] +- 3.1.10 **user** [ITU-T F.500] + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 **service activation**: The procedure of making a service ready for use, which processes information related to the telecommunications management for the purpose of configuration and activation of the resources reserved for supporting a specific service instance. +- 3.2.2 **subscribed service**: A service instance subscribed by the subscriber. +- 3.2.3 **user service**: A service instance configured by the subscriber and assigned to a user. +- 3.2.4 **user service relation**: The relationship between a user and a user service, which contains the information including user identifier, the service instance identifier, and the user usage preference for the service instance. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|----------------------------------------| +| EMF | Element Management Function | +| NGN | Next Generation Network | +| NMF | Network Management Function | +| OS | Operations System | +| OSF | Operations Systems Function | +| QoS | Quality of Service | +| RMF | Resource Management Function | +| SLA | Service Level Agreement | +| SMF | Service Management Function | +| SP | Service Provider | +| SRM | Service Resource Management | +| SRMF | Service Resource Management Function | +| TMN | Telecommunications Management Network | +| TRMF | Transport Resource Management Function | + +## 5 Conventions + +In this Recommendation, mandatory requirements are indicated by the use of the word "shall". Desirable requirements are indicated by the use of the word "should". Optional requirements are indicated by the use of the word "may" or "can". + +## 6 Concepts and background + +The "service" used in this Recommendation refers to "service instance" in all the cases. + +In the NGN management functional view reference to [ITU-T M.3060], the service provisioning is supported by several operations systems functions (OSFs) laid in different management layers. + +The service management function (SMF) is dedicated to service management and manages the service life cycles and service profiles. Each service profile expresses the transport and service resources requirements needed to activate the service and the underlying service resource management function (SRMF) and transport resource management function (TRMF) map these requirements into network parameters of the underlying network elements. The SMF also manages the service and transport resources required for enabling the activation of services according to the subscription contract, including the required connectivity and its associated characteristics: bandwidth, quality of service (QoS), and level of subscriber line access (SLA). + +All management functions in SMF are resource/technology independent and will not provide any technical knowledge on the underlying resources involved in the provisioning of services to the customers: no information about transport or service platforms is available through service management functions. + +The SMF relies on the SRMF and TRMF to map its service-oriented view and information to the required entities in the appropriate NGN resources. + +The network management function (NMF) interprets the requirements from the SMF into network parameters of the underlying network elements and performs service activation action through the element management function (EMF) to activate the related resources for a specific service. + +Figure 1 shows the interface addressed in this Recommendation. The operations system (OS) (managing system) realizes the service activation related function of the NMF and the OS (managed system) realizes the service activation related function of the EMF. The interface is a Q interface. + +![Diagram of the NMS-EMS interface architecture. At the top is a purple box labeled 'OS (Managing System)' containing a white circle labeled 'SNMF'. Below it are two light blue boxes, each labeled 'OS (Managed System)' containing a white circle labeled 'SEMF'. Two lines, each labeled 'NMS-EMS Interface', connect the 'SNMF' circle to each of the 'SEMF' circles.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +``` +graph TD; subgraph OS_Managing_System [OS (Managing System)]; SNMF((SNMF)); end; subgraph OS_Managed_System_1 [OS (Managed System)]; SEMF1((SEMF)); end; subgraph OS_Managed_System_2 [OS (Managed System)]; SEMF2((SEMF)); end; SNMF ---|NMS-EMS Interface| SEMF1; SNMF ---|NMS-EMS Interface| SEMF2; +``` + +Diagram of the NMS-EMS interface architecture. At the top is a purple box labeled 'OS (Managing System)' containing a white circle labeled 'SNMF'. Below it are two light blue boxes, each labeled 'OS (Managed System)' containing a white circle labeled 'SEMF'. Two lines, each labeled 'NMS-EMS Interface', connect the 'SNMF' circle to each of the 'SEMF' circles. + +**Figure 1 – The NMS-EMS interface addressed in this Recommendation** + +This Recommendation defines the requirements for the NGN service activation across the NMS-EMS interface in the service provisioning business process. + +The subscriber is an entity that can subscribe some services for an SP. The subscribed service must be activated in the SP's network before it can be used; this process has been illustrated in the above paragraphs of this clause. A subscriber is associated with one or more users, who actually use the service. A subscriber needs to assign services to users, and a service assigned to a user is a user service. As users can have different usage preference for a service, the user service relationship is used to record this requirement. To support the service activation process, the information about the + +subscriber, user, subscribed service and user service need to be configured in the managed system through the interface addressed in this Recommendation. The service in the managed system can be configured by the user after activation for usage preference via the telecommunication network, and if the managing system wants to receive updated information on the user service relation, it can subscribe to the managed system for notification of updates of the user service relation. + +## **7 Requirements** + +### **7.1 Business level requirements** + +#### **7.1.1 Requirements** + +The general requirements include: + +- Subscriber configuration +- User configuration +- Subscribed service configuration +- User service relation configuration +- User service relation update notification +- Bulk configuration +- Non-functional requirements + +#### **7.1.1.1 Subscriber configuration** + +REQ-SA-FUN-101 The managing system shall be able to request the managed system to create a new subscriber with the subscriber's identification. The managed system shall return the creation result. + +The subscriber's identification cannot be modified after creation. + +The information of a specific subscriber includes subscriber ID, subscriber name, subscriber type (organization, individual), etc. + +REQ-SA-FUN-102 The managing system shall be able to request the managed system to modify the existing subscriber's information identified by the subscriber's identification. The information that can be modified includes subscriber name and subscriber type. The managed system shall return the modification result. + +REQ-SA-FUN-103 The managing system shall be able to request the managed system to delete the existing subscriber identified by the subscriber's identification. If the subscriber to be deleted still has subscribed services in use, it cannot be deleted. The managed system shall return the deletion result. + +REQ-SA-FUN-104 The managing system shall be able to request the managed system to query the information of the existing subscriber identified by the subscriber's identification. The managed system shall return the query result. + +#### 7.1.1.2 User configuration + +- REQ-SA-FUN-201 The managing system shall be able to request the managed system to create a new user with the user's identification. The managed system shall return the creation result. +- The user's identification cannot be modified after creation. +- The information of a specific user includes user ID, user name, user type (person, process, etc.), and user credential information (username/password, etc.). +- REQ-SA-FUN-202 The managing system shall be able to request the managed system to modify an existing user's information identified by the user's identification. The information that can be modified includes user name, user type (person, process, etc.), and user credential information. The managed system shall return the modification result. +- REQ-SA-FUN-203 The managing system shall be able to request the managed system to delete an existing user identified by the user's identification. If the user to be deleted still has user services in use, it cannot be deleted. The managed system shall return the deletion result. +- REQ-SA-FUN-204 The managing system shall be able to request the managed system to query the information of an existing user identified by the user's identification. The managed system shall return the query result. + +#### 7.1.1.3 Subscribed service configuration + +- REQ-SA-FUN-301 The managing system shall be able to request the managed system to create a new service with the service's identification associated with the subscriber information. The managed system shall return the creation result. +- The service's identification cannot be modified after creation. +- The information of a specific subscribed service includes service ID, service specification ID1, effective time, expiration time, service status, service credential information (network access number, username/password, etc.), service QoS information, service characteristics (bandwidth, payment form (prepaid/postpaid), mailbox size, etc.), service resources. Different kinds of services may have different characteristics and may be based on different resources. There should be a mechanism to extend the characteristics and resources of services. +- REQ-SA-FUN-302 The managing system shall be able to request the managed system to modify the information of an existing service identified by the service's identification. The information that can be modified includes effective time, expiration time, service credential information, service QoS information, service characteristics, and service resources. The managed system shall return the modification result. + +--- + +1 A service specification is a service template that describes the characteristics of the service. + +- REQ-SA-FUN-303 The managing system shall be able to request the managed system to suspend or resume an existing service identified by the service's identification. The managed system shall return the operation result and the status of the service. +- REQ-SA-FUN-304 The managing system shall be able to request the managed system to remove an existing service identified by the service's identification. The managed system shall return the removing result. +- REQ-SA-FUN-305 The managing system shall be able to request the managed system to query the information of an existing service identified by the service's identification. The managed system shall return the query result. + +#### 7.1.1.4 User service relation configuration + +- REQ-SA-FUN-401 The managing system shall be able to request the managed system to create a user service relation between a user and a subscribed service. The managed system shall return the creation result. +- The user service relation's identification cannot be modified after creation. +- The information of a specific user service includes user service relation ID, user ID, service ID, and the user's usage preference information about this service. +- REQ-SA-FUN-402 The managing system shall be able to request the managed system to modify an existing user service identified by the user service's identification. The information that can be modified includes usage preference information. The managed system shall return the modification result. +- REQ-SA-FUN-403 The managing system shall be able to request the managed system to delete an existing user service identified by the user service's identification. The managed system shall return the deletion result. +- REQ-SA-FUN-404 The managing system shall be able to request the managed system to query an existing user service relationship by the user service relation's identification. The managed system shall return the query result. + +#### 7.1.1.5 User service relation update notification + +- REQ-SA-FUN-501 The managing system shall be able to request the managed system to subscribe notifications of user service relation updates, so that when a user service relation is updated in a managed system without request by the managing system, the managing system can be informed. The managed system shall return the notification subscription result. +- REQ-SA-FUN-502 The managing system shall be able to request the managed system to unsubscribe notifications of a user service relation update not requested by the managing system. The managed system shall return the notification unsubscription result. +- REQ-SA-FUN-503 The managed system shall be able to generate notifications based on notification subscription to the managing system when a user service relation is updated in the managed system not requested by the managing system. + +#### 7.1.1.6 Bulk configuration + +REQ-SA-FUN-601 All the operations of subscriber configuration, user configuration, subscribed service configuration, and user service relation configuration can be performed in a batch mode. + +The managing system shall be able to send a bulk configuration request to the managed system. The request contains the address information of a bulk configuration data file to be downloaded and performed by the managed system. The managed system shall be able to get this data file, analyse it and perform the configuration operations. + +Then the managed system shall be able to send a notification of the bulk configuration result to the managing system. The notification contains the address information of a bulk configuration result data file to be downloaded by the managing system. + +#### 7.1.1.7 Non-functional requirements + +REQ-SA-NON-101 The NMS-EMS interface provided by the managed system shall be able to support both the synchronous and asynchronous interaction mode. All of the operations illustrated in this Recommendation, except for the bulk configuration and user service update notification, are synchronous. + +REQ-SA-NON-102 The NMS-EMS interface provided by the managed system shall be able to support a security mechanism and policy to verify the validation of the managing system. + +REQ-SA-NON-103 The NMS-EMS interface provided by the managed system shall be able to support a parallel transaction. + +#### 7.1.2 Actor roles + +Managed system: The entity performing the agent role. + +Managing system: The entity performing the manager role. + +#### 7.1.3 Telecommunication resources + +The managed network resources are viewed as relevant telecommunications resources in this Recommendation. + +### 7.1.4 High level use case diagrams + +The following seven figures illustrate the high-level use case diagrams that summarize the functionality and interfaces of the service provisioning provided by the managed system. Figure 2 illustrates the general use cases, Figure 3 illustrates the subscriber configuration function set, Figure 4 is the user configuration function set, Figure 5 is the subscribed service configuration function set, Figure 6 is the service configuration function set, Figure 7 is the user service update notification function set, and Figure 8 is the bulk configuration function set. + +![UML Use Case Diagram for Figure 2 showing a Managing system actor connected to seven use cases: Subscriber configuration, User configuration, Subscribed service configuration, User service relation configuration, User service relation update notification, and Bulk configuration. The diagram is labeled M.3347(12)_F02.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +usecaseDiagram + actor Managing system + usecase Subscriber configuration + usecase User configuration + usecase Subscribed service configuration + usecase User service relation configuration + usecase User service relation update notification + usecase Bulk configuration + Managing system --> Subscriber configuration + Managing system --> User configuration + Managing system --> Subscribed service configuration + Managing system --> User service relation configuration + Managing system --> User service relation update notification + Managing system --> Bulk configuration + +``` + +M.3347(12)\_F02 + +UML Use Case Diagram for Figure 2 showing a Managing system actor connected to seven use cases: Subscriber configuration, User configuration, Subscribed service configuration, User service relation configuration, User service relation update notification, and Bulk configuration. The diagram is labeled M.3347(12)\_F02. + +**Figure 2 – General use cases** + +![UML Use Case Diagram for Figure 3 showing a Managing system actor connected to a Subscriber configuration use case, which includes Create subscriber, Modify subscriber, Delete subscriber, and Query subscriber. The diagram is labeled M.3347(12)_F03.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +``` + +usecaseDiagram + actor Managing system + usecase Subscriber configuration + usecase Create subscriber + usecase Modify subscriber + usecase Delete subscriber + usecase Query subscriber + Managing system --> Subscriber configuration + Subscriber configuration <> Create subscriber + Subscriber configuration <> Modify subscriber + Subscriber configuration <> Delete subscriber + Subscriber configuration <> Query subscriber + +``` + +M.3347(12)\_F03 + +UML Use Case Diagram for Figure 3 showing a Managing system actor connected to a Subscriber configuration use case, which includes Create subscriber, Modify subscriber, Delete subscriber, and Query subscriber. The diagram is labeled M.3347(12)\_F03. + +**Figure 3 – Subscriber configuration use cases** + +![UML Use Case Diagram for Figure 4 showing a Managing system actor connected to a User configuration use case, which includes Create user, Modify user, Delete user, and Query user. The diagram is labeled M.3347(12)_F04.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +usecaseDiagram + actor Managing system + usecase User configuration + usecase Create user + usecase Modify user + usecase Delete user + usecase Query user + Managing system --> User configuration + User configuration <> Create user + User configuration <> Modify user + User configuration <> Delete user + User configuration <> Query user + +``` + +M.3347(12)\_F04 + +UML Use Case Diagram for Figure 4 showing a Managing system actor connected to a User configuration use case, which includes Create user, Modify user, Delete user, and Query user. The diagram is labeled M.3347(12)\_F04. + +**Figure 4 – User configuration use cases** + +![UML Use Case Diagram for Subscribed service configuration. The central use case is 'Subscribed service configuration', which includes 'Create subscribed service', 'Modify subscribed service information', 'Suspend subscribed service', 'Resume subscribed service', 'Remove subscribed service', and 'Query subscribed service'. The actor 'Managing system' is associated with the central use case. Reference M.3347(12)_F05.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +usecaseDiagram + actor Managing system + usecase Subscribed service configuration + usecase Create subscribed service + usecase Modify subscribed service information + usecase Suspend subscribed service + usecase Resume subscribed service + usecase Remove subscribed service + usecase Query subscribed service + + Managing system --> Subscribed service configuration + Subscribed service configuration <> Create subscribed service + Subscribed service configuration <> Modify subscribed service information + Subscribed service configuration <> Suspend subscribed service + Subscribed service configuration <> Resume subscribed service + Subscribed service configuration <> Remove subscribed service + Subscribed service configuration <> Query subscribed service + +``` + +M.3347(12)\_F05 + +UML Use Case Diagram for Subscribed service configuration. The central use case is 'Subscribed service configuration', which includes 'Create subscribed service', 'Modify subscribed service information', 'Suspend subscribed service', 'Resume subscribed service', 'Remove subscribed service', and 'Query subscribed service'. The actor 'Managing system' is associated with the central use case. Reference M.3347(12)\_F05. + +**Figure 5 – Subscribed service configuration use cases** + +![UML Use Case Diagram for User service relation configuration. The central use case is 'User service relation configuration', which includes 'Create user service relation', 'Modify user service relation', 'Remove user service relation', and 'Query user service relation'. The actor 'Managing system' is associated with the central use case. Reference M.3347(12)_F06.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +``` + +usecaseDiagram + actor Managing system + usecase User service relation configuration + usecase Create user service relation + usecase Modify user service relation + usecase Remove user service relation + usecase Query user service relation + + Managing system --> User service relation configuration + User service relation configuration <> Create user service relation + User service relation configuration <> Modify user service relation + User service relation configuration <> Remove user service relation + User service relation configuration <> Query user service relation + +``` + +M.3347(12)\_F06 + +UML Use Case Diagram for User service relation configuration. The central use case is 'User service relation configuration', which includes 'Create user service relation', 'Modify user service relation', 'Remove user service relation', and 'Query user service relation'. The actor 'Managing system' is associated with the central use case. Reference M.3347(12)\_F06. + +**Figure 6 – User service relation configuration use cases** + +![UML Use Case Diagram for User service relation update notification. The central use case is 'User service relation update notification', which includes 'Subscribe user service relation update notification', 'Unsubscribe user service relation update notification', and 'Notify user service relation update'. The actor 'Managing system' is associated with the central use case. 'Subscribe user service relation update notification' uses 'Subscribe notification [ITU-T M.3702]'. 'Unsubscribe user service relation update notification' uses 'Unsubscribe notification [ITU-T M.3702]'. 'Notify user service relation update' uses 'Notification report [ITU-T M.3702]'. Reference M.3347(12)_F07.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +usecaseDiagram + actor Managing system + usecase User service relation update notification + usecase Subscribe user service relation update notification + usecase Unsubscribe user service relation update notification + usecase Notify user service relation update + usecase Subscribe notification [ITU-T M.3702] + usecase Unsubscribe notification [ITU-T M.3702] + usecase Notification report [ITU-T M.3702] + + Managing system --> User service relation update notification + User service relation update notification <> Subscribe user service relation update notification + User service relation update notification <> Unsubscribe user service relation update notification + User service relation update notification <> Notify user service relation update + Subscribe user service relation update notification <> Subscribe notification [ITU-T M.3702] + Unsubscribe user service relation update notification <> Unsubscribe notification [ITU-T M.3702] + Notify user service relation update <> Notification report [ITU-T M.3702] + +``` + +M.3347(12)\_F07 + +UML Use Case Diagram for User service relation update notification. The central use case is 'User service relation update notification', which includes 'Subscribe user service relation update notification', 'Unsubscribe user service relation update notification', and 'Notify user service relation update'. The actor 'Managing system' is associated with the central use case. 'Subscribe user service relation update notification' uses 'Subscribe notification [ITU-T M.3702]'. 'Unsubscribe user service relation update notification' uses 'Unsubscribe notification [ITU-T M.3702]'. 'Notify user service relation update' uses 'Notification report [ITU-T M.3702]'. Reference M.3347(12)\_F07. + +**Figure 7 – User service relation update notification use cases** + +![UML Use case diagram for Bulk configuration. An actor labeled 'Managing system' is shown. A solid arrow points from the actor to a use case oval labeled 'Send bulk configuration request'. Another solid arrow points from a use case oval labeled 'Notify bulk configuration result' back to the actor. A dashed arrow labeled '<>' points from the 'Notify bulk configuration result' oval to a third use case oval labeled 'Notification report [ITU-T M.3702] M.3347(12)_F08'.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +UML Use case diagram for Bulk configuration. An actor labeled 'Managing system' is shown. A solid arrow points from the actor to a use case oval labeled 'Send bulk configuration request'. Another solid arrow points from a use case oval labeled 'Notify bulk configuration result' back to the actor. A dashed arrow labeled '<>' points from the 'Notify bulk configuration result' oval to a third use case oval labeled 'Notification report [ITU-T M.3702] M.3347(12)\_F08'. + +**Figure 8 – Bulk configuration use cases** + +## **7.2 Specification level requirements** + +### **7.2.1 Requirements** + +There are no specification level requirements. + +### **7.2.2 Actor roles** + +See clause 7.1.2. + +#### **7.2.3 Telecommunications resources** + +See clause 7.1.3. + +### **7.2.4 Use cases** + +#### **7.2.4.1 Create subscriber** + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests the Agent to create a new subscriber with the subscriber's identification. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | None. | | +| Begins when | The Manager sends a request to create a new subscriber. | | +| Step 1 (M) | The Manager sends a request to the Agent to create a new subscriber; the request should include the following information:
– subscriber's identification (subscriber ID)
– subscriber name
– subscriber type (organization, individual). | | +| Step 2.1 (M) | When the requested subscriber creation has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the creation fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | + +| Use case stage | Evolution/specification | <>
Related use | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | User ID repeated, Unknown parameter, Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the subscriber is created successfully, or the creation fails because of some errors. | | +| Traceability | REQ-SA-FUN-101 | | + +#### 7.2.4.2 Modify subscriber + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager modifies the basic information of a specific subscriber through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified subscriber exists in the Agent. | | +| Begins when | The Manager sends a request to modify the basic information associated with a specific subscriber. | | +| Step 1 (M) | The manager sends a request to the Agent to modify the basic information of a specific subscriber; the request should include the following information:
  • – subscriber ID
  • – list of attribute name and new value pairs of the subscriber to be modified. The modifiable basic subscriber attributes include subscriber name, subscriber type.
| | +| Step 2.1 (M) | When the requested subscriber modification has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the modification fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown subscriber ID, Unknown parameter, Incorrect parameter values, Attribute not modifiable, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the subscriber is modified successfully, or the modification fails because of some errors. | | +| Traceability | REQ-SA-FUN-102 | | + +#### 7.2.4.3 Delete subscriber + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests the Agent to delete a specific subscriber. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified subscriber exists in the Agent.
The subscriber to be deleted does not have subscribed services in use. | | +| Begins when | The Manager sends a request to delete a specific subscriber. | | +| Step 1 (M) | The manager sends a request to the Agent to delete a specific subscriber; the request should include the following information:
– subscriber ID. | | +| Step 2.1 (M) | When the requested subscriber deletion has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the deletion fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown subscriber ID, Has subscribed services in use, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the subscriber is deleted successfully, or the deletion fails because of some errors. | | +| Traceability | REQ-SA-FUN-103 | | + +#### 7.2.4.4 Query subscriber + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager queries the information of specific subscribers through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified subscribers exist in the Agent. | | +| Begins when | The Manager sends a request to query the information associated with specific subscribers. | | +| Step 1 (M) | The manager sends a request to the Agent to query the information of specific subscribers; the request should include the following information:
– list of subscriber IDs. | | + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Step 2.1 (M) | When the requested query has completed, the Agent returns the subscriber(s) information, which should contain a LIST of the following information:
  • – subscriber ID
  • – subscriber name
  • – subscriber type
  • – user ID list.
| | +| Step 2.2 (M) | If the query fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown subscriber IDs, Communication or Process Failure. | | +| Post-conditions | The Manager receives the information of the requested subscribers list. | | +| Traceability | REQ-SA-FUN-104 | | + +#### 7.2.4.5 Create user + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The Manager requests the Agent to create a new user with the user's identification. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | None. | | +| Begins when | The Manager sends a request to create a new user. | | +| Step 1 (M) | The manager sends a request to the Agent to create a new user; the request should include the following information:
  • – user's identification (user ID)
  • – user name
  • – user type (person, process, etc.)
  • – user credential information (username/password, etc.)
  • – subscriber ID (indicating which subscriber this user belongs to).
| | +| Step 2.1 (M) | When the requested user creation has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the creation fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | + +| Use case stage | Evolution/specification | <>
Related use | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions | User ID repeated, Unknown parameter, Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the user is created successfully, or the creation fails because of some errors. | | +| Traceability | REQ-SA-FUN-201 | | + +#### 7.2.4.6 Modify user + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager modifies the basic information of a specific user through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified user exists in the Agent. | | +| Begins when | The Manager sends a request to modify the basic information associated with a specific user. | | +| Step 1 (M) | The Manager sends a request to the Agent to modify the basic information of a specific user; the request should include the following information:
– user ID
– list of attribute name and new value pairs of the user to be modified. The modifiable basic user attributes include user name, user type, user credential information. | | +| Step 2.1 (M) | When the requested user modification has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the modification fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user ID, Unknown parameter, Incorrect parameter values, Attribute not modifiable, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the user is modified successfully, or the modification fails because of some errors. | | +| Traceability | REQ-SA-FUN-202 | | + +#### 7.2.4.7 Delete user + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests the Agent to delete a specific user. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified user exists in the Agent.
The user to be deleted does not have user services in use. | | +| Begins when | The Manager sends a request to delete a specific user. | | +| Step 1 (M) | The manager sends a request to the Agent to delete a specific user; the request should include the following information:
– user ID. | | +| Step 2.1 (M) | When the requested user deletion has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the deletion fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user ID, Has user services in use, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the user is deleted successfully, or the deletion fails because of some errors. | | +| Traceability | REQ-SA-FUN-203 | | + +##### 7.2.4.8 Query user + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager queries the information of specific users through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified users exist in the Agent. | | +| Begins when | The Manager sends a request to query the information associated with specific users. | | +| Step 1 (M) | The manager sends a request to the Agent to query the information of specific users; the request should include the following information:
– list of user IDs. | | + +| Use case stage | Evolution/specification | <>
Related use | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 2.1 (M) | When the requested query has completed, the Agent returns the users information, which should contain a list of the following information:
– user ID
– user name
– user type
– user credential information
– subscriber ID. | | +| Step 2.2 (M) | If the query fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user IDs, Communication or Process Failure. | | +| Post-conditions | The Manager receives the information of the requested users list. | | +| Traceability | REQ-SA-FUN-204 | | + +##### 7.2.4.9 Create subscribed service + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests the Agent to create a new service with the service's identification associated with the subscriber. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | None. | | +| Begins when | The Manager sends a request to create a new service. | | +| Step 1 (M) | The Manager sends a request to the Agent to create a new service; the request should include the following information:
– service ID
– service specification ID
– effective time
– expiration time
– service status
– service credential information (network access number, username/password, etc.)
– service QoS information
– service characteristics values (bandwidth, payment form (prepaid/postpaid), mailbox size, etc.)
– service resources. | | +| Step 2.1 (M) | When the requested service creation has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the creation fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | + +| Use case stage | Evolution/specification | <>
Related use | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions | Unknown parameter, Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the service is created successfully, or the creation fails because of some errors. | | +| Traceability | REQ-SA-FUN-301 | | + +##### 7.2.4.10 Modify subscribed service information + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager modifies the basic information of a specific service through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified service exists in the Agent. | | +| Begins when | The Manager sends a request to modify the basic information associated with a specific service. | | +| Step 1 (M) | The manager sends a request to the Agent to modify the basic information of a specific service; the request should include the following information:
  • – service ID
  • – list of name and new value pairs of the service attributes to be modified. The modifiable basic service attributes include effective time, expiration time, service credential information service, QoS information, service characteristics values and service resources.
| | +| Step 2.1 (M) | When the requested service modification has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the modification fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown service ID, Unknown parameter, Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the service is modified successfully, or the modification fails because of some errors. | | +| Traceability | REQ-SA-FUN-302 | | + +##### 7.2.4.11 Suspend subscribed service + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager sends a request to suspend a specific service through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified service exists in the Agent and it is not suspended. | | +| Begins when | The Manager sends a request to suspend a specific service. | | +| Step 1 (M) | The Manager sends a request to the Agent to suspend a specific service; the request should include the following information:
– service ID | | +| Step 2.1 (M) | When the requested service suspending has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the suspension fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown service ID, Service Already Suspended, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the service is suspended successfully, or the suspension fails because of some errors. | | +| Traceability | REQ-SA-FUN-303 | | + +##### 7.2.4.12 Resume subscribed service + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager sends a request to resume a suspended service through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified service exists in the Agent. And it is suspended. | | +| Begins when | The Manager sends a request to resume a specific service. | | +| Step 1 (M) | The manager sends a request to the Agent to resume a specific service; the request should include the following information:
– service ID. | | +| Step 2.1 (M) | When the requested service resumption has completed, the Agent returns the success indication. | | + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Step 2.2 (M) | If the resumption fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown service ID, Service Already Resumed, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the service is resumed successfully, or the resumption fails because of some errors. | | +| Traceability | REQ-SA-FUN-303 | | + +##### 7.2.4.13 Remove subscribed service + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The Manager requests the Agent to remove a specific service. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified service exists in the Agent. The specified service is not in use. | | +| Begins when | The Manager sends a request to remove a specific service. | | +| Step 1 (M) | The Manager sends a request to the Agent to remove a specific service, the request should include the following information:
– service ID. | | +| Step 2.1 (M) | When the requested service removal has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the deletion fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown service ID, Still in use, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the service is removed successfully, or the removal fails because of some errors. | | +| Traceability | REQ-SA-FUN-304 | | + +##### 7.2.4.14 Query subscribed service + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager queries the information of a specific service through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified service exists in the Agent. | | +| Begins when | The Manager sends a request to query the information associated with specific services. | | +| Step 1 (M) | The manager sends a request to the Agent to query the information of specific services; the request should include the following information:
– list of service IDs. | | +| Step 2.1 (M) | When the requested query has completed, the Agent returns the requested information, which should contain a LIST of the following information:
– service ID
– service specification ID
– effective time
– expiration time
– service status
– service credential information
– service QoS information
– service characteristics values
– service resources
– service state. | | +| Step 2.2 (M) | If the query fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown service ID, Communication or Process Failure. | | +| Post-conditions | The Manager receives the information of the requested services list. | | +| Traceability | REQ-SA-FUN-305 | | + +##### 7.2.4.15 Create user service relation + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests the Agent to create a user service relation between a user and a subscribed service. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified user and the service exist in the Agent. | | +| Begins when | The Manager sends a request to create a new user service relation. | | +| Step 1 (M) | The manager sends a request to the Agent to create a new user service relation; the request should include the following information:
– user service relation ID
– user ID
– service ID
– the user's usage preference information about this service. | | +| Step 2.1 (M) | When the requested user service relation creation has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the creation fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user ID, Unknown service ID, Unknown parameter, Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the user service relation is created successfully, or the creation fails because of some errors. | | +| Traceability | REQ-SA-FUN-401 | | + +##### 7.2.4.16 Modify user service relation + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager modifies the basic information of a specific user service relation through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified user service relation exists in the Agent. | | +| Begins when | The Manager sends a request to modify the basic information associated with a specific user service relation. | | + +| Use case stage | Evolution/specification | <>
Related use | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 (M) | The manager sends a request to the Agent to modify the basic information of a specific user service relation; the request should include the following information:
– user service relation ID
– name and new value of the usage preference information. | | +| Step 2.1 (M) | When the requested user service modification has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the modification fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user service relation ID, Unknown parameter, Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the user service relation is modified successfully, or the modification fails because of some errors. | | +| Traceability | REQ-SA-FUN-402 | | + +##### 7.2.4.17 Remove user service relation + +| Use case stage | Evolution/Specification | <>
Related use | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests the Agent to remove a specific user service relation. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified user service relation exists in the Agent. | | +| Begins when | The Manager sends a request to delete a specific user service relation. | | +| Step 1 (M) | The manager sends a request to the Agent to remove a specific user service relation; the request should include the following information:
– user service relation ID. | | +| Step 2.1 (M) | When the requested service relation removal has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the removal fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user service relation ID, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the user service is removed successfully, or the removal fails because of some errors. | | +| Traceability | REQ-SA-FUN-403 | | + +##### 7.2.4.18 Query user service relation + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager queries the information of a specific user service through the management interface. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The specified user service relation exists in the Agent. | | +| Begins when | The Manager sends a request to query the information associated with specific user service relations. | | +| Step 1 (M) | The Manager sends a request to the Agent to query the information of specific user service relations; the request should include the following information:
– list of user service relation IDs. | | +| Step 2.1 (M) | When the requested query has completed, the Agent returns the request user service relation information, which should contain a LIST of the following information:
– user service relation ID
– user ID
– service ID
– user's usage preference information about this service. | | +| Step 2.2 (M) | If the query fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown user service relation IDs, Communication or Process Failure. | | +| Post-conditions | The Manager receives the information of the requested user service relation list. | | +| Traceability | REQ-SA-FUN-404 | | + +##### 7.2.4.19 Subscribe to user service relation update notification + +| Use case stage | Evolution/specification | <>
Related use | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager requests to subscribe notifications of user service relation update through the management interface.
This use case reuses the "subscribe notification" use case in [ITU-T M.3702]. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | None. | | + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Begins when | The Manager sends a request to subscribe notifications of user service relation update. | | +| Step 1 (M) | The manager sends a request to the Agent to subscribe notifications of user service relation update. See [ITU-T M.3702] for more details. | Subscribe notification in [ITU-T M.3702] | +| Step 2.1 (M) | When the requested subscription has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the subscription fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Already Subscribed; Incorrect parameter values, Communication or Process Failure. | | +| Post-conditions | The Agent gives the Manager a response indicating that the subscription is successful, or the subscription fails because of some errors. | | +| Traceability | REQ-SA-FUN-501 | | + +##### 7.2.4.20 Unsubscribe to user service relation update notification + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The Manager requests to unsubscribe notifications of user service relation update through the management interface.
This use case reuses the "unsubscribe notification" use case in [ITU-T M.3702]. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The Manager has subscribed notifications of user service relation update. | | +| Begins when | The Manager sends a request to unsubscribe notifications of user service relation update. | | +| Step 1 (M) | The manager sends a request to the Agent to unsubscribe notifications of user service relation update. See [ITU-T M.3702] for more details. | Unsubscribe notification in [ITU-T M.3702] | +| Step 2.1 (M) | When the unsubscription has completed, the Agent returns the success indication. | | +| Step 2.2 (M) | If the unsubscription fails, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the Agent, or some error occurs. | | +| Exceptions | Unknown subscription, Not subscribed, Communication or Process Failure. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Post-conditions | The Agent gives the Manager a response indicating that the unsubscribe is successful, or the unsubscribe fails because of some errors. | | +| Traceability | REQ-SA-FUN-502 | | + +##### 7.2.4.21 Notify user service relation update + +| Use case stage | Evolution/Specification | <>
Related use | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| Goal | The Agent notifies the changed user service relation information to the Manager through the management interface.
This use case reuses the "report notification" use case in [ITU-T M.3702]. | | +| Actors and roles | The Manager is the consumer of the notification from the Agent. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The Manager has already subscribed notifications from the Agent. | | +| Begins when | The user service information has changed not requested by the Manager. | | +| Step 1 (M) | The Agent sends a user service change notification to the Manager, and the notification should include the following information:
– user service relation ID;
– list of name and new value pairs of the changed user service information | Notification report in [ITU-T M.3702] | +| Ends when | The notification is delivered to the subscribed managers. | | +| Exceptions | None. | | +| Post-conditions | The manager receives the user service relation update notification. | | +| Traceability | REQ-SA-FUN-503 | | + +##### 7.2.4.22 Send bulk configuration request + +| Use case stage | Evolution/Specification | <>
Related use | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The Manager sends a bulk configuration request to the Agent through the management interface. The request contains the address information of a bulk configuration data file to be downloaded and performed by the Agent. | | +| Actors and roles | The Agent is the consumer of the request. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Pre-conditions | The bulk configuration data file to be performed has been prepared by the Manager. | | +| Begins when | The Manager sends the configuration request to the Agent. | | +| Step 1 (M) | The Manager sends the configuration request to the Agent. The request should include the following information:
– operation to be performed (create subscriber, modify subscriber, delete subscriber, create user, modify user, delete user, create subscribed service, modify subscribed service information, suspend subscribed service, resume subscribed service, remove subscribed service, create user service relation, modify user service relation information, remove user service relation) (NOTE – There will only appear one operation for a bulk configuration data file.)
– the download address of the bulk configuration data file. | | +| Step 2.1 (M) | After receiving this request, the Agent will check the bulk configuration request. If it can be performed, the Agent will return a confirmation to the Manager. | | +| Step 2.2 (M) | If the bulk configuration request cannot be performed, or there is something wrong with the request, the Agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The Agent gives the Manager a response indicating that the request is received successfully, or some error occurs. | | +| Exceptions | Unknown Operation, Bulk Configuration Unsupported, Communication or Process Failure. | | +| Post-conditions | The Manager received the response from the Agent. | | +| Traceability | REQ-SA-FUN-601 | | + +##### 7.2.4.23 Notify bulk configuration result + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The Agent sends a notification of bulk configuration result to the Manager through the management interface. The notification contains the address information of a bulk configuration result data file to be downloaded by the Manager. | | +| Actors and roles | The Manager is the consumer of the notification from the Agent. | | +| Telecom resources | See clause 7.1.3. | | +| Assumptions | The communication between the Manager and the Agent is available. | | +| Pre-conditions | The Bulk configuration is performed by the Agent.
The manager has subscribed to this type of notifications and the subscription is not suspended. | Subscribe notification in [ITU-T M.3702] | +| Begins when | The Agent sends the notification of bulk configuration result to the Manager. | | + +| Use case stage | Evolution/specification | <<Uses>>
Related use
| +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Step 1 (M) | The Agent sends a notification of bulk configuration result to the Manager, and the notification should include the following information:
– the download address of the bulk configuration result data file. | Report notification in [ITU-T M.3702] | +| Ends when | A notification of bulk configuration result is delivered to all subscribed Managers. | | +| Exceptions | Communication or Process Failure. | | +| Post-conditions | The Manager receives the bulk configuration result notification. | | +| Traceability | REQ-SA-FUN-601 | | + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3348-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3348-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..007c1980afcf79b08af620838765a70ed49e48db --- /dev/null +++ b/marked/M/T-REC-M.3348-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7892cfc054d8d59fafada3a72928ddf9db33ed3643414bb601a1b26920859dbf +size 6560 diff --git a/marked/M/T-REC-M.3348-201101-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3348-201101-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c5fa31444b864155847e654459c202d9ab5b7e8 --- /dev/null +++ b/marked/M/T-REC-M.3348-201101-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d6bd31faa1096137903d0c8583f18aa4f2f6e40c3d8b4eac6fff06fa24fe276 +size 87221 diff --git a/marked/M/T-REC-M.3348-201101-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/M/T-REC-M.3348-201101-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b298d4f307c14b5ebdfcb758d8455adf2542e0be --- /dev/null +++ b/marked/M/T-REC-M.3348-201101-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d81bb060afcd67caead1d7cec4233f09ce1da4ffa64dffc5a649a1bf4e4ba02f +size 78960 diff --git a/marked/M/T-REC-M.3348-201101-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/M/T-REC-M.3348-201101-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bac8bfc16f252d177290e48ff7b78598adb5d085 --- /dev/null +++ b/marked/M/T-REC-M.3348-201101-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b4cd9a4cfd7573d09d2c0510ac0f447f4257464d16e37b615128340ffbb55bb +size 69765 diff --git a/marked/M/T-REC-M.3348-201101-I_PDF-E/ff2492be4fa814905acbad18f261b8a5_img.jpg b/marked/M/T-REC-M.3348-201101-I_PDF-E/ff2492be4fa814905acbad18f261b8a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef8a8046d1ab0eac217700f4fd92b9c5c21bd66b --- /dev/null +++ b/marked/M/T-REC-M.3348-201101-I_PDF-E/ff2492be4fa814905acbad18f261b8a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bce169031385b46362b8db459cc2015b6f85f1f1c6f4bd91381d1658cacdcf5 +size 66029 diff --git a/marked/M/T-REC-M.3348-201101-I_PDF-E/raw.md b/marked/M/T-REC-M.3348-201101-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5eee4cc5fa31784cd10613a55a2fb31bc9c49039 --- /dev/null +++ b/marked/M/T-REC-M.3348-201101-I_PDF-E/raw.md @@ -0,0 +1,601 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3348** + +(01/2011) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Requirements of the NMS-EMS management interface for NGN service platforms** + +Recommendation ITU-T M.3348 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T M.3348** + +# **Requirements of the NMS-EMS management interface for NGN service platforms** + +## **Summary** + +Recommendation ITU-T M.3348 describes the requirements of the NMS-EMS management interface for NGN service platforms. The requirements are provided using the TMN interface specification methodology described in Recommendation ITU-T M.3020. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3348 | 2011-01-13 | 2 | + +## **Keywords** + +EMS, interface, NGN, NMS, requirements, service platform. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2011 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Requirements ..... | 3 | +| 6.1 Concepts and background..... | 3 | +| 6.2 Business-level requirements ..... | 5 | +| 6.3 Specification-level requirements ..... | 8 | + +# Introduction + +The ITU-T M.370x series of Recommendations defines the management functions applicable in the network management system-element management system (NMS-EMS) interface which includes object management, state management, notification management, performance management and fault management. These common management functions are network independent. + +While in NGN environment or in a mixed environment of NGN and non-NGN technologies, there are many kinds of service platforms to provide various services. The management and administration interface for controlling the service platform is proprietary to each vendor currently. The service platform consists of IT resources (including hardware and software aspects), service support applications and services. IETF has created detailed specifications related to the management of IT resources. Moreover, regarding service platforms, the management and administration to services and the service support applications are more significant. The specification of the service support applications and services is seldom covered in the current Recommendations so, it is necessary to specify the NMS-EMS management interface for the NGN service platforms. + +# Requirements of the NMS-EMS management interface for NGN service platforms + +# 1 Scope + +This Recommendation defines the requirements for managing service platforms used to introduce new service types (e.g., multimedia service) in NGN. The management functions include monitoring and controlling service support applications and services supported by service platforms. The purpose of this Recommendation is to provide a standardized interface to manage these services and service support applications. It is out of the scope of this Recommendation to manage the resources based on which the services are provided. Management of service instances is out of the scope of this Recommendation. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2010), *Management interface specification methodology*. +- [ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. +- [ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the Management of Next Generation Networks*. +- [ITU-T M.3703] Recommendation ITU-T M.3703 (2010), *Common management services – Alarm management – Protocol neutral requirements and analysis*. +- [ITU-T M.3704] Recommendation ITU-T M.3704 (2010), *Common management service – Performance management – Protocol neutral requirements and analysis*. +- [ITU-T Y.110] Recommendation ITU-T Y.110 (1998), *Global Information Infrastructure principles and framework architecture*. +- [ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN*. +- [ITU-T Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for next generation networks*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +3.1.1 **application:** [ITU-T Y.110]. + +3.1.2 **interface:** [ITU-T M.3010]. + +3.1.3 **next generation network (NGN):** [ITU-T Y.2001]. + +3.1.4 **NGN service stratum:** [ITU-T Y.2011]. + +3.1.5 **operations system (OS):** [ITU-T M.3010]. + +3.1.6 **Q interface:** [ITU-T M.3010]. + +3.1.7 **service:** [ITU-T M.3050.1]. + +3.1.8 **service element management function (SEMF):** [ITU-T M.3060]. + +3.1.9 **service network management function (SNMF):** [ITU-T M.3060]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +3.2.1 **service delivery platform (SDP):** A complete environment or system architecture designed to enable rapid, cost efficient service creation, deployment, execution, orchestration and management. + +3.2.2 **service execution environment:** The software and hardware which support the execution of the service. The basic environment information of a service includes memory size, disk size, JDK (Java development kit) path, database URI (uniform resource identifier), process priority, etc. + +3.2.3 **service exposure:** An interface provided by the service platform or SDP (service delivery platform), through which the user (can be a system or an end user) can use the function of the service. The basic service exposure information includes service URI (service hostname, service port and service path), service access policies (permitted access user, permitted access time, etc.), etc. + +3.2.4 **service platform:** The collection of software and hardware on the server side, which is constructed by the service provider and used to deliver one or more specific services to end users. + +3.2.5 **service support application:** The software which provides the function of the service using the resource of the service platform. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +EMS Element Management System + +FM Fault Management + +ID Identifier + +IT Information Technology + +JDK Java Development Kit + +NGN Next Generation Network + +NMS Network Management System + + + +As described in [ITU-T Y.2011], the service stratum may involve a complex set of geographically distributed service platforms or in the simple case just the service functions in two end-user sites. The service platforms provide the user services, such as a telephone service, a web service, etc. To provide these services, 'the application support functions and service support functions' and related control functions in NGN should be covered by the service platform. The dashed rectangle in Figure 2 shows the functions covered by the service platform in the NGN functional architecture. + +![Figure 2: Functions covered by the service platform in the NGN functional architecture. The diagram shows a layered architecture. At the top is 'Applications'. Below it is the 'Service stratum' (enclosed in a dashed red rectangle), which contains 'Application support functions and service support functions', 'Service user profiles', and 'Service control functions'. Below the service stratum is the 'Transport stratum'. On the left, 'Management functions' and 'End-user functions' are shown. On the right, 'Other networks' are shown. Interfaces are labeled: ANI (between Applications and Service stratum), UNI (between End-user functions and Transport stratum), and NNI (between Transport stratum and Other networks). A legend at the bottom indicates: Control (green dashed line), Media (grey dashed line), and Management (red dashed line).](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +Figure 2: Functions covered by the service platform in the NGN functional architecture. The diagram shows a layered architecture. At the top is 'Applications'. Below it is the 'Service stratum' (enclosed in a dashed red rectangle), which contains 'Application support functions and service support functions', 'Service user profiles', and 'Service control functions'. Below the service stratum is the 'Transport stratum'. On the left, 'Management functions' and 'End-user functions' are shown. On the right, 'Other networks' are shown. Interfaces are labeled: ANI (between Applications and Service stratum), UNI (between End-user functions and Transport stratum), and NNI (between Transport stratum and Other networks). A legend at the bottom indicates: Control (green dashed line), Media (grey dashed line), and Management (red dashed line). + +**Figure 2 – Functions covered by the service platform in the NGN functional architecture** + +According to the networks of telecom operators, there are two kinds of service platforms: traditional service platform and service delivery platform (SDP). (Both the service platform and the SDP are viewed as network elements in this Recommendation.) + +![Figure 3: Scenario 1 for management of service platforms. The diagram shows a hierarchical management structure. At the top is 'Service network management function' (SNMS). Below it are three service platforms: 'Service platform_1', 'Service platform_2', and 'Service platform_n'. Each platform contains a 'Service element management function' (SEMS), a 'Service' (Service 1, Service 2, Service n), 'Service support applications', and 'Resources'. Arrows show management flow from SNMS to each SEMS, and from each SEMS to its corresponding Service, Support Applications, and Resources. A label 'M.3348(11)_F03' is at the bottom right.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Figure 3: Scenario 1 for management of service platforms. The diagram shows a hierarchical management structure. At the top is 'Service network management function' (SNMS). Below it are three service platforms: 'Service platform\_1', 'Service platform\_2', and 'Service platform\_n'. Each platform contains a 'Service element management function' (SEMS), a 'Service' (Service 1, Service 2, Service n), 'Service support applications', and 'Resources'. Arrows show management flow from SNMS to each SEMS, and from each SEMS to its corresponding Service, Support Applications, and Resources. A label 'M.3348(11)\_F03' is at the bottom right. + +**Figure 3 – Scenario 1 for management of service platforms** + +Figure 3 shows the traditional service platform scenario. Each service platform provides a specific service, and its service element management function (SEMF) is provided either by a dedicated SEMS or by itself. The service network management function (SNMF) is provided by a SNMS. This should be supported. + +Service platform consists of three aspects: Resources, service support applications and service. Resources are common IT infrastructures of the service platform, which consist of hardware and software. Hardware consists of network devices, storage devices and servers. Software consists of baseware (e.g., operating system, JAVA virtual machine) and middleware (e.g., database, web server, application server). Service support applications are the system procedures to support the services' runtime environments, which consist of service creation, service execution, service exposure, service management, security, etc. + +In Figure 4, the concept of SDP is introduced, so that multiple services can be provided or flexibly created through this. The SEMF is provided either by a dedicated SEMS or by the SDP itself, and the SNMF is provided by a SNMS. + +![Figure 4 – Scenario 2 for management of service platforms](ff2492be4fa814905acbad18f261b8a5_img.jpg) + +The diagram illustrates the management architecture for service platforms. At the top is the 'SNMS' containing the 'Service network management function'. It has bidirectional arrows pointing to two entities below: 'SEMS\_1' and 'Service platform\_2'. + 'SEMS\_1' contains the 'Service element management function' and is linked via a bidirectional arrow to 'Service platform\_1'. + 'Service platform\_1' is a large box containing: + - A row of services: 'Service 1', 'Service 2', ..., 'Service n'. + - A 'Service delivery platform' layer below the services. + - 'Service support applications' box. + - 'Resources' box at the bottom. + 'Service platform\_2' contains: + - A 'Service element management function' box at its top. + - 'Service x' and 'Service y' below it. + - A 'Service delivery platform' box at the bottom. + The caption below the diagram reads 'Figure 4 – Scenario 2 for management of service platforms' and a reference code 'M.3348(11)\_F04'. + +Figure 4 – Scenario 2 for management of service platforms + +### 6.2 Business-level requirements + +### 6.2.1 Requirements + +This Recommendation only focuses on the management interface between the manager and the agent, and the interface management functions associated with them. Through the interface, the manager can query and modify configuration information, and the agent can report changes in configuration, performance data, and fault information to the manager. + +Since the functions and information of configuration management, performance management (PM) and fault management (FM) are varied with different service platforms, only the common requirements that are independent of any specific service platform will be covered in this Recommendation. + +**Rec. ITU-T M.3348 (01/2011)**       5 + +Besides the requirements for the common management functions of NMS-EMS interfaces which are described in the ITU-T M.370x series of Recommendations, the requirements of NMS-EMS management interfaces for NGN service platforms are described as follows. + +#### **6.2.1.1 Configuration management** + +##### **6.2.1.1.1 Service configuration management** + +| Identifier | Definition | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-SP-FUN-101 | The manager shall be able to query the service configuration information. The information of a specific service includes service ID, service name, service description, service version, service status, service owner, service QoS information, service exposure information, etc. | +| REQ-SP-FUN-102 | The manager shall be able to configure the basic service information. The basic service attributes include service name, service description, service version, service status, service owner, etc. | +| REQ-SP-FUN-103 | The agent shall be able to notify the changed information of the service configuration to the manager. When the service configuration information changes, the agent shall send a message to the manager about this. The message type includes update, delete and add. When the message type is add, the content of the message is the basic information of the newly added service. When the message type is deleted, the content of the message is the service ID. When the message type is update, the content of the message is service ID and the update attributes of the service. | +| REQ-SP-FUN-104 | The manager shall be able to stop/start a specific service. The manager can enable, disable, and upgrade a service by this function. | +| REQ-SP-FUN-105 | The manager shall be able to configure the service QoS information. The basic QoS information of a service includes service QoS level, service capacity, assigned resources, etc. | +| REQ-SP-FUN-106 | The manager shall be able to configure the service execution environment parameters. | +| REQ-SP-FUN-107 | The manager shall be able to configure the service exposure parameters. | + +##### **6.2.1.1.2 Configuration management for service support application** + +| Identifier | Definition | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-SP-FUN-201 | The manager shall be able to query the configuration information related to service support applications. The information of application includes application ID, application name, software provider information (i.e., vendor name, vendor contact, etc.), release version, release time, licence, patch version, application components contained, contained application components information, etc. | +| REQ-SP-FUN-202 | The manager shall be able to configure the basic configuration information related to a service support application. The parameters that can be modified include running status (i.e., start-up, suspended, stop, etc.), enable status (e.g., enable, disable, replace, etc.), etc. | +| REQ-SP-FUN-203 | The manager shall be able to inform the service support applications of new patches to download. | + +REQ-SP-FUN-204 The agent shall be able to notify the changed information of the service support application's configuration to the manager. When the service support application's configuration information changes, the agent shall send a message to the manager about this. + +#### 6.2.1.2 Fault management + +The requirements for the common parts of FM are described in [ITU-T M.3703], which will be reused in this Recommendation. + +For NGN service platforms, the alarm report can be generated from several managed object classes. + +The alarm information mentioned below is for example purpose. It is outside the scope of this Recommendation to define the detailed alarm information. + +| Identifier | Definition | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-SP-FUN-301 | An alarm event will be generated if the service or service function is in the fault condition or the service performance measurement data crosses the thresholds, e.g., service (or service function) unavailability, failure ratio of service (or service function) alarm, response time of service (or service function) alarm, etc. | +| REQ-SP-FUN-302 | An alarm event will be generated if the service support application is in the fault condition or the application performance measurement data crosses the thresholds, e.g., status abnormal, usage ratio of memory alarm, etc. | +| REQ-SP-FUN-303 | An alarm event will be generated if the resources are in the fault condition or the resources performance measurement data crosses the thresholds, e.g., connecting failure, response time alarm, etc. | + +#### 6.2.1.3 Performance management + +The requirements for the common parts of PM are described in [ITU-T M.3704], which will be reused in this Recommendation. + +The performance measurement data of the service platform includes performance measurement data related to services, service support application, resources. + +The performance parameter mentioned below is for example purpose. It is outside the scope of this Recommendation to define the detailed performance parameters. + +| Identifier | Definition | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-SP-FUN-401 | The service platforms provide the user services, such as telephone service, data service and media service, etc. The service performance measurement data is different among the various service types, such as a telephone service including connecting ratio, call failure, holding time, etc., a data service including success ratio, data rate, data transfer time, etc., and a media service including streaming accessibility, streaming access time, video quality, audio quality, etc. | +| REQ-SP-FUN-402 | The service support application performance measurement data includes CPU usage ratio, memory usage ratio, usage ratio of files, idle size of files, number of processes, number of handles, etc. | + +### 6.2.2 Actor roles + +The SEMS or service platform providing embedded SEMF: The entity acts as an agent role. + +The SNMS: The entity acts as a manager role. + +### 6.2.3 Telecommunication resources + +The managed objects contained in the service platforms are viewed as relevant telecommunication resources in this Recommendation. + +### 6.2.4 High-level use cases + +The use-case diagram in Figure 5 shows the overall interaction of the service platform management interface. + +![Use-case diagram of the service platform management interface showing a Manager actor interacting with 13 use cases.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates the interaction between a 'Manager' actor and various service management functions. The Manager is represented by a yellow stick figure icon on the left. Thirteen yellow oval use cases are arranged in a semi-circle to the right of the Manager. Red arrows point from the Manager to each use case, indicating the flow of interaction. The use cases are: Query service configuration information, Modify service basic information, Notify service configuration information change, Stop service, Start service, Modify service QoS configuration information, Modify service execution environment information, Modify service exposure information, Query service support application configuration information, Modify status of service support application, Release patches of service support application, Notify service support application configuration information change, and Notify service support application patch installation failure. At the bottom left of the diagram, the text 'M.3348(11)\_F05' is present. + +Use-case diagram of the service platform management interface showing a Manager actor interacting with 13 use cases. + +**Figure 5 – The use-case diagram of the service platform management interface** + +## 6.3 Specification-level requirements + +### 6.3.1 Requirements + +There are no specification-level requirements. + +### 6.3.2 Actor roles + +See clause 6.2.2. + +### 6.3.3 Telecommunication resources + +See clause 6.2.3. + +### 6.3.4 Use cases + +#### 6.3.4.1 Query service configuration information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager queries the configuration information of the specific service provided by the agent through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to get the configuration information of the specific service. | | +| Step 1 (M) |

The manager sends a request to the agent to get the complete information of specific services or all services in the service platform. The request should include the following information:

  • – service ID list.

When the manager needs to get information of all services in a service platform, the service ID list can be empty.

| | +| Step 2.1 (M) |

When the requested retrieval has completed, the agent returns the service information, which should contain the following:

  • – Service basic information:
    • • service ID;
    • • service name;
    • • service description;
    • • service version;
    • • service status;
    • • service owner.
  • – Service QoS information:
    • • service QoS level;
    • • service capacity;
    • • assigned resources.
  • – Service execution environment information:
    • • memory size;
    • • disk size;
    • • JDK path;
    • • database URI;
    • • process priority.
  • – Service exposure information:
    • • service URI;
    • • service access policies.
| | +| Step 2.2 (M) | If the retrieval fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the agent, or some error occurs. | | +| Exceptions | Invalid parameter, Invalid filter definition, Communication or process failure. | | +| Post-conditions | The manager receives the information of the requested services list. | | +| Traceability | REQ-SP-FUN-101 | | + +#### 6.3.4.2 Modify service basic information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager configures the basic information of a specific service through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to modify the basic information associated with a specific service. | | +| Step 1 (M) | The manager sends a request to the agent to modify the service parameters of a specific service. The request should include the following information:
  • – service ID;
  • – list of name and new value pairs of the service attributes to be modified. The modifiable basic service attributes include service name, service description, service version, service owner, etc.
| | +| Step 2.1 (M) | When the requested service modification has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the modification fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The agent gives the manager a response indicating that the specified attribute values are modified successfully, or the modification fails because of some errors. | | +| Exceptions | Unknown service ID, Unknown parameter, Incorrect parameter values, Communication or process failure. | | +| Post-conditions | The attribute values of the specified service are modified. | | +| Traceability | REQ-SP-FUN-102 | | + +#### 6.3.4.3 Notify service configuration information change + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The agent shall be able to notify the changed information of the service configuration to the manager. | | +| Actors and roles | The manager is the consumer of the notification from the agent. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | The manager has already subscribed notifications from the agent. | | +| Begins when | The service configuration information has changed. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 (M) | The agent sends a service change notification to the manager, and the notification should include the following information:
– service ID;
– list of name and new value pairs of the changed service configuration information. | | +| Ends when | The agent has sent out the notification. | | +| Exceptions | None. | | +| Post-conditions | The manager receives the service change notification. | | +| Traceability | REQ-SP-FUN-103 | | + +#### 6.3.4.4 Stop service + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager stops a specific service through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | The status of the service is "Started". | | +| Begins when | The manager sends a request to stop a specific service. | | +| Step 1 (M) | The manager sends a request to the agent to stop a specific service; the request should include the following information:
– service ID. | | +| Step 2.1 (M) | When the requested service stop has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the operation fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The agent gives the manager a response indicating that the specified service is stopped successfully, or the operation fails because of some errors. | | +| Exceptions | Unknown service ID, Service already stopped, Communication or process failure. | | +| Post-conditions | The status of the specified service is "Stopped". | | +| Traceability | REQ-SP-FUN-104 | | + +#### 6.3.4.5 Start service + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager starts a specific service through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | The status of the service is "stopped". | | +| Begins when | The manager sends a request to start a specific service. | | +| Step 1 (M) | The manager sends a request to the agent to start a specific service; the request should include the following information:
– service ID. | | +| Step 2.1 (M) | When the requested service start has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the operation fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The agent gives the manager a response indicating that the specified service is started successfully, or the operation fails because of some errors. | | +| Exceptions | Unknown service ID, Service already started, Communication or process failure. | | +| Post-conditions | The status of the specified service is "Started". | | +| Traceability | REQ-SP-FUN-104 | | + +#### 6.3.4.6 Modify service QoS configuration information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager configures the QoS parameters of a specific service through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to modify the QoS configuration parameters associated with a specific service. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 1 (M) | The manager sends a request to the agent to modify the QoS configuration parameters of a specific service; the request should include the following information:
– service ID;
– list of name and new value pairs of the QoS configuration parameters to be modified. The modifiable QoS information of a service includes service QoS level, service capacity, assigned resources, etc. | | +| Step 2.1 (M) | When the requested service modification has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the modification fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The agent gives the manager a response indicating that the specified attribute values are modified successfully, or the modification fails because of some errors. | | +| Exceptions | Unknown service ID, Unknown parameter, Communication or process failure, Invalid parameter values. | | +| Post-conditions | The attribute values of the specified service are modified. | | +| Traceability | REQ-SP-FUN-105 | | + +#### 6.3.4.7 Modify service execution environment information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager modifies one or more execution environment parameters of a specific service through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to modify one or more execution environment parameters associated with a specific service. | | +| Step 1 (M) | The manager sends a request to the agent to modify one or more execution environment parameters of a specific service; the request should include the following information:
– service ID;
– list of name and new value pairs of the execution environment to be modified. The modifiable environment information of a service includes memory size, disk size, process priority, etc. | | +| Step 2.1 (M) | When the requested service modification has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the modification fails, the agent will return error information. The possible errors are listed under "Exceptions". | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Ends when | The agent gives the manager a response indicating that the specified attribute values are modified successfully, or the modification fails because of some errors. | | +| Exceptions | Unknown service ID, Unknown parameter, Communication or process failure, Invalid parameter values. | | +| Post-conditions | The attribute values of the specified service are modified. | | +| Traceability | REQ-SP-FUN-106 | | + +#### 6.3.4.8 Modify service exposure information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager modifies one or more exposure parameters of a specific service through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to modify one or more exposure parameters associated with a specific service. | | +| Step 1 (M) | The manager sends a request to the agent to modify service exposure parameters of a specific service; the request should include the following information:
  • – service ID;
  • – list of name and new value pairs of the exposure parameters to be modified. The modifiable service exposure information includes service URI, service access policies, etc.
| | +| Step 2.1 (M) | When the requested service modification has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the modification fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The agent gives the manager a response indicating that the specified attribute values are modified successfully, or the modification fails because of some errors. | | +| Exceptions | Unknown service ID, Unknown parameter, Communication or process failure, Invalid parameter values. | | +| Post-conditions | The attribute values of the specified service are modified. | | +| Traceability | REQ-SP-FUN-107 | | + +#### 6.3.4.9 Query service support application configuration information + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager queries the configuration information of the specific service support application provided by the agent through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to get the configuration information of the specific service support application. | | +| Step 1 (M) | The manager sends a request to the agent to get the complete information of a specific service support application; the request should include the following information:
– application ID. | | +| Step 2.1 (M) | When the requested retrieval has completed, the agent returns the service support application information, which should contain the following:
– application ID;
– application name;
– software provider information;
– release version;
– release time;
– licence;
– patch version;
– application components contained;
– contained application components information;
– running status;
– enable status;
– etc. | | +| Step 2.2 (M) | If the retrieval fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The result is returned by the agent, or some error occurs. | | +| Exceptions | Invalid parameter, Invalid filter definition, Communication or process failure. | | +| Post-conditions | The manager has received the information list of the requested service support applications. | | +| Traceability | REQ-SP-FUN-201 | | + +#### 6.3.4.10 Modify status of service support application + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager modifies the status of a specific service support application through the management interface. | | +| Actors and roles | The agent is the consumer of the request. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | None. | | +| Begins when | The manager sends a request to modify the status of a specific service support application. | | +| Step 1 (M) | The manager sends a request to the agent to modify the status of a specific service support application; the request should include the following information:
  • – application ID;
  • – list of name and new value pairs of the application status attributes to be modified. The modifiable attributes include running status (e.g., start-up, suspended, stop, etc.), enable status (e.g., enable, disable, replace, etc.).
| | +| Step 2.1 (M) | When the requested service support application modification has completed, the agent returns the result successful indication. | | +| Step 2.2 (M) | If the modification fails, the agent will return error information. The possible errors are listed under "Exceptions". | | +| Ends when | The agent gives the manager a response indicating that the specified attribute values are modified successfully, or the modification fails because of some errors. | | +| Exceptions | Unknown application ID, Unknown parameter, Communication or process failure, Invalid parameter values. | | +| Post-conditions | The attribute values of the specified service support application are modified. | | +| Traceability | REQ-SP-FUN-202 | | + +#### 6.3.4.11 Release service support application patch + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager notifies the agent of new service support application patch. The agent downloads this patch and upgrades the specified service support application according to the policies received from the manager. (The procedures of downloading and installation of the patch is outside the scope of this Recommendation.) | | +| Actors and roles | The agent is the consumer of the notification from the manager. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Pre-conditions | The service support application patch is ready. | | +| Begins when | The manager sends notification of new patches of service support application and updates policies. | | +| Step 1 (M) | The manager sends a new patch notification to the agent, and the notification should include the following information:
  • – application ID;
  • – patch information (patch name, patch version);
  • – the download address of the patch;
  • – updating policies (restart is needed or not, backup is needed or not, etc.).
| | +| Step 2 (M) | The agent receives the notification and returns the confirmation to the manager. | | +| Ends when | The agent gives the manager a response indicating that the patch information is received successfully, or some error occurs. | | +| Exceptions | Unknown application ID, Unknown parameter, Communication or process failure. | | +| Post-conditions | The manager has received the response from the agent. | | +| Traceability | REQ-SP-FUN-203. | | + +#### 6.3.4.12 Notify service support application configuration information change + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The agent shall be able to notify the changed configuration information of the service support application to the manager. | | +| Actors and roles | The manager is the consumer of the notification from the agent. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | The manager has already subscribed notifications from the agent. | | +| Begins when | The service configuration information has changed. | | +| Step 1 (M) | The agent sends a service support application change notification to the manager, and the notification should include the following information:
  • – application ID;
  • – list of name and new value pairs of the changed service support application configuration information.
| | +| Ends when | The agent has sent out the notification. | | +| Exceptions | None. | | +| Post-conditions | The manager receives the service support application change notification. | | +| Traceability | REQ-SP-FUN-204 | | + +#### 6.3.4.13 Notify service support application patch installation failure + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | When the agent cannot install the service support application's patch successfully, the agent shall be able to notify this information to the manager. | | +| Actors and roles | The manager is the consumer of the notification from the agent. | | +| Telecom resources | See clause 6.2.3. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Pre-conditions | The manager has already subscribed notifications from the agent. | | +| Begins when | The installation of the service support application's patch fails. | | +| Step 1 (M) | The agent sends a service support application patch installation failure notification to the manager, and the notification should include the following information:
  • – application ID;
  • – patch information (patch name, patch version);
  • – fail reason.
| | +| Ends when | The agent has sent out the notification. | | +| Exceptions | None. | | +| Post-conditions | The manager receives the service support application patch installation failure notification. | | +| Traceability | REQ-SP-FUN-203 | | + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b08862bdd946d21848f6670da40606d071a440e --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1028c6dc6ef394eb8864479ba798fc993df92f779d4d80218a44ff6e1fb9d469 +size 102053 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99f3067cfdb98fd7a6de0923eadb8052a4b30dbc --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19481d84bd104b28429cae123e8fbc91da3104fdc5bdc9d300b88a311e409f15 +size 49371 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82a16fe7e70c0a6bd16b3393ada527d0d1a3e18c --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6074d2f74260ae6cb2376dd0283652ed2047fc8c1e73ac051f0fab30e55d242 +size 13784 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b766996d9530ca05d6cc6ed6caf5fbce9d4424a6 --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfc88036e412698739867ee97f562105af1347d3054438776ab382df11a03ef9 +size 104119 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..007c1980afcf79b08af620838765a70ed49e48db --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7892cfc054d8d59fafada3a72928ddf9db33ed3643414bb601a1b26920859dbf +size 6560 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd4dde6bc0106c68d0ef62ef4ee1266b6249af21 --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:741104d911aed2037e97729ac4bdebb5be7c8fa693c39416ad7d556a320e579c +size 136374 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c62a6ea974d8227f1adf340956c72780896d038 --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8effcf3155b47dba512822a057d491e64f388603e605c47d2c9b566fa37eeab +size 136931 diff --git a/marked/M/T-REC-M.3349-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3349-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2489aa1e808496690c7f94f09287d04d6b9ef7c --- /dev/null +++ b/marked/M/T-REC-M.3349-201303-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2cd355254e362e182fec4944651dcb9cfd28a80cdc0c3c09022de9aa0598dac +size 51272 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30 --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359 +size 8245 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f27f9b874ab425190d24201d3b9d3e1dc923ac5d --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:033f98d3414a8dfcf7409fcb1e2472747b5cd9697aa9db9c1cf9e848a7361df0 +size 120263 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40ad895c0af940dca5c3019946a8786ef652bae3 --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da4ea8c3ee82305861c96746893b512f6d310c3b6a996115c5809cffa0e39c70 +size 79351 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4625c3b7d8987b8f85f7304f8719756c6ea5161d --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69142174adf83d5efb469de38964121410199536dd94fcfeab7f4efe71955276 +size 31100 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97f36de5a8ea4b7fbeafa220d29b938c32b9ed58 --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:497b85f94c71a30428114c6a80ec930e2eca9f1ed5d65c744f5065b0824bcb26 +size 12856 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32967648c633be54634543f1435a1a8427306a99 --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad2ce0bb29b2496913677ffa35fb3c39bd178dbd7b69f94633c7dda6cb996ea +size 20543 diff --git a/marked/M/T-REC-M.3350-200405-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/M/T-REC-M.3350-200405-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b00e23bac8fdad05191bafc1795fd1e87e56c997 --- /dev/null +++ b/marked/M/T-REC-M.3350-200405-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23fa5282b6a47935e41ae46368474636df674f7de60160bc8dd77bdcaee17d07 +size 38780 diff --git a/marked/M/T-REC-M.3351-202408-I_PDF-E/raw.md b/marked/M/T-REC-M.3351-202408-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0ac9662c6ef597ee6eac4e47e61bfcb4849dbf03 --- /dev/null +++ b/marked/M/T-REC-M.3351-202408-I_PDF-E/raw.md @@ -0,0 +1,415 @@ + + +# Recommendation **ITU-T M.3351 (08/2024)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +# **Framework of knowledge management for telecom operation and management** + +![ITU logo](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3351 + +# Framework of knowledge management for telecom operation and management + +## Summary + +The complexity of telecom operation and management for networks and services is increasing significantly. To realise advanced intelligence, even full intelligence, in telecom operation and management, it is necessary to utilize knowledge to fulfil the complex requirements in different scenarios. The knowledge required for telecom operation and management for network and service is characterized as highly fragmented and difficult to reuse. + +Knowledge management in telecom operation and management aims to construct, integrate, store, validate, refine, provide and share knowledge of telecom operation and management in specified forms. It is required to provide the clear functions and mechanisms so that given tasks can be accomplished with better operational efficiencies and, ultimately, to achieve precise application of knowledge. + +The contents of Recommendation ITU-T M.3351 include the following: + +- Background and overview of knowledge management +- Knowledge classification in telecom operation and management +- Framework of knowledge management for telecom operation and management. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3351 | 2024-08-13 | 2 | 11.1002/1000/16017 | + +## Keywords + +Knowledge management, telecom operation and management. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2024 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Background and overview of knowledge management..... | 2 | +| 7 Knowledge classification in telecom operation and management..... | 3 | +| 8 Framework of knowledge management for telecom operation and management..... | 3 | +| 8.1 Functional framework ..... | 3 | +| 8.2 Functions in knowledge management ..... | 4 | +| Appendix I – A use case on knowledge management of RAN network optimization ..... | 8 | +| Bibliography..... | 10 | + + + +# Recommendation ITU-T M.3351 + +## Framework of knowledge management for telecom operation and management + +# 1 Scope + +This Recommendation provides the framework of knowledge management for telecom operation and management, to further improve the usage efficiency of knowledge while fulfilling the service requirements in different scenarios. + +The scope of this Recommendation is as follows: + +- Background and overview of knowledge management +- Knowledge classification in telecom operation and management +- Framework of knowledge management for telecom operation and management. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 knowledge** [b-ETSI GS ENI 005]: Analysis of data and information, resulting in an understanding of what the data and information mean. + +NOTE – Knowledge represents a set of patterns that are used to explain, as well as predict, what has happened, is happening, or is possible to happen in the future; it is based on acquisition of data, information, and skills through experience and education. + +**3.1.2 knowledge graph** [b-ETSI GR ENI 031]: Structured representation of knowledge that uses a graph data structure and formal logic to represent entities and their relationships. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 knowledge management**: The process of acquiring, constructing, storing, maintaining, applying and sharing knowledge for the performance enhancement of specific fields. + +**3.2.2 knowledge maintenance**: The activities of knowledge update, construction process management, version management, and classification management for effective and efficient use of knowledge in telecom operation and management. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------------------------------| +| AI | Artificial Intelligence | +| KMTOM | Knowledge Management for Telecom Operation and Management | +| NoSQL | Not Only SQL | +| PDF | Portable Document Format | +| Q&A | Question and Answer | +| RAN | Radio Access Network | +| RDF | Resource Description Framework | +| SQL | Structured Query Language | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +# 6 Background and overview of knowledge management + +The complexity of telecom operation and management for network and service is increasing significantly. To realise advanced intelligence even full intelligence in telecom operation and management, it is necessary to utilize knowledge to fulfil the complex requirements in different scenarios. The knowledge in telecom operation and management for networks and services is characterized as highly fragmented and difficult to reuse. + +Knowledge management for telecom operation and management is required to support the construction, storage, and maintenance of knowledge generated during the operation and management process. It also provides standardized knowledge services and builds diverse telecom operation and management knowledge scenario applications. It is required to provide the clear functions and mechanisms so that given tasks can be accomplished with better operational efficiencies and, ultimately, to achieve precise application of knowledge. + +Knowledge management for telecom operation and management is required to manage knowledge which is: + +- generated from different raw data sources within multiple services and networks, such as home service, individual service, wireless network, optical network, and radio access network (RAN). +- represented in different formats and structures, such as vector-based, tree-based, graph-based, model-based, and document-based. + +NOTE – The knowledge graph, which is a graph-based structured representation of knowledge, is composed of a set of entities and their relations, and is commonly used to denote knowledge itself and its relationships. + +- stored in various databases and environments, such as relational databases, cloud databases, object-oriented databases and graph databases; +- utilized to applications in different domains or users with various open and flexible services via knowledge retrieval, question and answer (Q&A) and recommendation. + +# **7 Knowledge classification in telecom operation and management** + +Knowledge in telecom operation and management can be classified from different perspectives: + +- telecommunications management perspectives, such as RAN-related knowledge, transport network-related knowledge, and core network-related knowledge. +- scenario perspectives, such as on-site support-related knowledge, operation decision-making-related knowledge, and customer service-related knowledge. +- process perspectives, such as network planning, construction, maintenance, optimization, and operation-related knowledge. + +Knowledge can be labelled with multiple tags based on different knowledge classifications and flexibly applied to practical telecom operation and management. + +# **8 Framework of knowledge management for telecom operation and management** + +## **8.1 Functional framework** + +The functional framework of knowledge management for telecom operation and management, containing six functional blocks, as shown in Figure 1, is composed of knowledge scenario application, knowledge service, knowledge construction, knowledge storage, knowledge maintenance and knowledge raw data management. + +Knowledge scenarios application is built on standardized knowledge services to be used in different telecom operation and management scenarios. + +Knowledge service provides and manages standardized services based on already constructed, stored and updated knowledge. + +Knowledge construction provides capabilities, such as knowledge modelling, knowledge annotation, knowledge extraction, knowledge fusion, knowledge reasoning, and knowledge validation, to support the transformation of raw data, generated in network operation and management processes, to knowledge. + +Knowledge storage provides storage capabilities and knowledge base for telecom operation and management knowledge. + +Knowledge maintenance provides capabilities, such as knowledge update, knowledge construction process management, knowledge version management, and knowledge classification management, to ensure the effectiveness of the telecom operation and management knowledge. + +Knowledge raw data management provides capabilities such as raw data lifecycle management and raw data quality management. + +The knowledge management for telecom operation and management could exchange multi-source and multiform knowledge with other systems. + +![Functional framework of knowledge management for telecom operation and management diagram](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +The diagram illustrates the functional framework of knowledge management for telecom operation and management. It is structured as a nested hierarchy within a large rectangular box labeled "Knowledge management for telecom operation and management". + +- External system:** Located on the left, outside the main box, with a double-headed arrow labeled "Knowledge input and share" pointing to the main box. +- Knowledge scenario application:** The top-level sub-box, containing five horizontal boxes: "Planning and construction", "Operation support and readiness", "Fulfilment", "Assurance", and "Billing". +- Knowledge service:** The second-level sub-box, containing five horizontal boxes: "Intent analysis", "Knowledge retrieval", "Knowledge recommendation", "Knowledge Q&A", and "Knowledge service management". +- Knowledge construction:** A sub-box on the left side of the third level, containing a 3x2 grid of boxes: + - Row 1: "Knowledge modelling", "Knowledge annotation" + - Row 2: "Knowledge extraction", "Knowledge fusion" + - Row 3: "Knowledge reasoning", "Knowledge validation" +- Knowledge storage:** A central vertical box between "Knowledge construction" and "Knowledge maintenance". +- Knowledge maintenance:** A sub-box on the right side of the third level, containing four horizontal boxes: "Knowledge update", "Knowledge construction process management", "Knowledge version management", and "Knowledge classification management". +- Knowledge raw data management:** The bottom-most horizontal box spanning the width of the inner structure. + +M.3351(24) + +Functional framework of knowledge management for telecom operation and management diagram + +**Figure 1 – Functional framework of knowledge management for telecom operation and management** + +## 8.2 Functions in knowledge management + +### 8.2.1 Knowledge scenario application + +Knowledge scenario application is built with the support of well-defined and tested knowledge service. The knowledge application could be classified into five types, which are planning and construction, operations support and readiness, fulfilment, assurance, and billing, in alignment with [ITU-T M.3050.1]. + +### 8.2.2 Knowledge service + +Knowledge service for telecom operation and management provides fundamental and reusable knowledge capabilities, packaged as service to enable knowledge application utilization in different ways. + +Knowledge services for telecom operation and management include, but are not limited to, intent analysis, knowledge retrieval, knowledge recommendation, and knowledge Q&A. + +- Intent analysis supports the use of telecom operation and management knowledge to analyse the needs and intentions, and achieves intelligent understanding and transformation to machine-understandable format. +- Knowledge retrieval supports the use of telecom operation and management knowledge for input retrieval, provides relevant knowledge output matching knowledge storage repositories, and supports precise retrieval, fuzzy retrieval, semantic retrieval, etc. +- Knowledge recommendation supports the use of telecom operation and management knowledge to provide associative recommendations, including network operation management strategy and resolution to assist decision-making, and personalized topics of interest, combining current and historical user searches. +- Knowledge Q&A supports the use of telecom operation and management knowledge to provide basic and reasoning answers to questions, which could be in the natural language, + +graph, table or document form. It also provides single-turn or multi-turn dialogue capabilities, candidate sorting and explanation of answers. + +NOTE – Intent analysis, knowledge retrieval, knowledge recommendation and knowledge Q&A services can be provided separately as independent knowledge services to meet telecom operation and management scenario application requirements. Knowledge Q&A service could reuse intent parsing capabilities in intent analysis service, retrieval and matching capabilities in knowledge retrieval service, and recommendation capabilities in knowledge recommendation service. Additionally, knowledge Q&A service pays more attention to question reasoning, multi-turn dialogue, and answer generation. + +- Knowledge service management monitors the performance and quality of the telecom operation and management of knowledge services, in addition to troubleshooting and lifecycle management for these services. + +### **8.2.3 Knowledge construction** + +#### **8.2.3.1 Overview** + +Knowledge construction for telecom operation and management provides the capability to support the transformation of raw data, generated in network operation and management processes, to knowledge, including knowledge modelling, knowledge annotation, knowledge extraction, knowledge fusion, knowledge reasoning, and knowledge validation. + +#### **8.2.3.2 Knowledge modelling** + +Knowledge modelling clarifies and sets up the knowledge ontology model for telecom operation and management and knowledge presentation, to instruct the whole knowledge construction process. + +- Ontology modelling defines specific meanings and relations of knowledge (e.g., network fault cause, network fault phenomenon, and network fault resolution, and their relations are focused on the ontology modelling in the troubleshooting domain). It supports ontology creation, viewing, destruction, and quality management. +- Knowledge representation supports the symbolic or numerical representation of ontology models that machines can recognize, process and store (e.g., resource description framework [b-ITU-T F.750], and web ontology language [b-ITU-T Y.4563]). + +#### **8.2.3.3 Knowledge annotation** + +Knowledge annotation tags the desired knowledge elements to raw data in the manual or artificial intelligence (AI)-assisted way, to identify the telecom operation and management knowledge. The annotated data can be used to train the knowledge extraction model. Knowledge annotation supports: + +- intelligent annotation functions, such as directly calling predefined algorithms to automatically annotate data, or automatic annotation through training algorithms on the basis of a small amount of manual annotation; +- customized annotation functions, such as configuring combinations based on annotation components provided by the system to meet different types of annotation tasks; +- annotation evaluation or quality inspection, such as evaluating the accuracy and effectiveness of annotation; +- visual annotation function, with a clear annotation interface, and the annotation information can be presented intuitively on the original raw data. + +#### **8.2.3.4 Knowledge extraction** + +Knowledge extraction automatically identifies and acquires telecom operation and management knowledge defined by knowledge ontology (e.g., entities and relations in the knowledge graph) from various raw data, in different manners (e.g., extract "network device physical port down" from raw data as one of entities belonging to "network fault cause" entity type). Knowledge extraction supports: + +- extraction from structured, unstructured and semi-structured raw data. +- different extraction manners, such as template-based extraction, customized extraction and model-based extraction. +- visualization of extraction results. + +#### **8.2.3.5 Knowledge fusion** + +Knowledge fusion integrates the telecom operation and management knowledge generated from different sources, to remove redundancy, eliminate ambiguity and form a globally unified knowledge identifier (e.g., "network device physical port down" and "network device port down" are the same kind of knowledge in some condition). Knowledge fusion supports: + +- different fusion manners, such as template-based fusion, customized fusion and model-based fusion; +- visual comparison before and after fusion. + +#### **8.2.3.6 Knowledge reasoning** + +Knowledge reasoning discovers implicit and unknown telecom operation and management knowledge or corrects error knowledge using specified rules or algorithms. Knowledge reasoning supports: + +- different reasoning manners, such as template-based reasoning, customized reasoning and model-based reasoning; +- visualization of reasoning results. + +#### **8.2.3.7 Knowledge validation** + +Knowledge validation provides both automatic and manually assisted validation functions and optional quality evaluation methods and indicators to validate the telecom operation and management knowledge accuracy, relevance, integrity, degree of confidence, and so on. + +#### **8.2.4 Knowledge storage** + +Knowledge storage provides appropriate storage functions and repositories for data, models, rules, policies and knowledge generated in different environments, categories and formats. Knowledge storage supports: + +- multiple database types, such as relational databases, graph databases, document-oriented databases, wide column, time series and so on; +- different knowledge structures and relationships, such as vector-based, tree-based, graph-based, model-based and document-based; +- storage of knowledge in relational databases, such as triplet tables, horizontal tables, attribute tables and vertical tables. Supports structured query language (SQL) operations such as add, delete, modification, and query of stored knowledge; +- storage of knowledge graph in a graph database, such as Neo4j. Support cypher operations such as add, delete, modification, and query of graph entities and relationships; +- storage of knowledge in a not only SQL (NoSQL) database, such as a document-oriented database. Supports query operations for add, delete, modification, and query of stored knowledge. + +#### **8.2.5 Knowledge maintenance** + +#### **8.2.5.1 Knowledge update** + +Knowledge update provides online manual editing methods and automatic update methods to modify and supplement telecom operation and management knowledge. Continuous knowledge update is + +achieved automatically via process loop covering knowledge construction and storage, based on new raw data from additional sources or domains. + +#### **8.2.5.2 Knowledge construction process management** + +Knowledge construction process management manages configuration information (including used methods, rules and strategies in the process of telecom operation and management knowledge modelling, annotation, extraction, fusion, reasoning and validation) and pipeline in knowledge construction, and supports visual traceability of the knowledge construction process. + +#### **8.2.5.3 Knowledge version management** + +Knowledge version management achieves telecom operation and management knowledge publishing. Offline, it also supports setting versions and enables version backup, version rollback, version switching and version comparison analysis. + +#### **8.2.5.4 Knowledge classification management** + +Knowledge classification management categorizes telecom operation and management knowledge and manages the classification labels to facilitate knowledge query and use. + +### **8.2.6 Knowledge raw data management** + +Knowledge raw data management provides the telecom operation and management raw data preparation functions before knowledge construction, storage, update and management including, but not limited to, knowledge raw data life-cycle management and raw data quality management. + +Knowledge raw data life-cycle management covers knowledge raw data acquisition, knowledge pre-processing, and raw data storage and destruction. + +- Knowledge raw data acquisition provides multi-channel and multi-model acquisition methods from various knowledge raw data including, but not limited to, support for obtaining knowledge through service interface and database. +- Knowledge raw data acquisition supports offline acquisition in text, Excel, pictures, audio, video, and portable document format (PDF) formats. +- Knowledge raw data acquisition supports access by configuring data storage tools (e.g., relational databases, Hadoop, HBase, graph databases, and Elasticsearch) and connecting to cloud data storage tools (cloud disks). +- Knowledge pre-processing supports preliminary knowledge pre-processing of the acquired raw data, including data cleaning and data verification. +- Knowledge raw data storage supports storage of acquired and pre-processed raw data. +- Knowledge raw data destruction provides the capability to destroy expired, acquired and pre-processed knowledge raw data. + +Knowledge raw data quality management supports raw data performance and quality evaluation management in terms of consistency, accuracy, timeliness, and completeness. + +# Appendix I + +## A use case on knowledge management of RAN network optimization + +(This appendix does not form an integral part of this Recommendation.) + +|

Title

|

Knowledge management of RAN network optimization based on framework of KMTOM

| +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Description

|

This is a use case that uses framework of knowledge management to manage and apply RAN network optimization knowledge graphs. This use case gives the knowledge graph management process for RAN network optimization, as shown in the following image:

Image: Diagram showing the knowledge management process for RAN network optimization. It starts with 'RAN network optimization raw data' in a cloud at the bottom, leading to 'Knowledge raw data management'. This leads to 'Knowledge modelling', which then leads to 'Knowledge extraction'. Above 'Knowledge extraction' is a central box containing 'Knowledge storage', 'Knowledge fusion', and 'Knowledge validation'. These three boxes all point upwards to 'Knowledge reasoning', which finally points to 'Knowledge service' at the very top.

 graph TD     RD([RAN network optimization raw data]) --> KRDM[Knowledge raw data management]     KRDM --> KM[Knowledge modelling]     KM --> KE[Knowledge extraction]     subgraph Process [ ]         KE --> KF[Knowledge fusion]         KS[Knowledge storage] --> KR[Knowledge reasoning]         KF --> KR         KV[Knowledge validation] --> KR         KE --> KS         KE --> KV     end     KR --> KService[Knowledge service]     style Process fill:none,stroke:#333,stroke-dasharray: 5 5 

The RAN network optimization knowledge graph is constructed, stored and applied to meet the customer's retrieval requirements.

M.3186(24)

| +|

The process of knowledge management for RAN network optimization

|

Knowledge raw data management

The raw data of RAN network optimization is acquired from RAN network management systems and pre-processed, stored and verified through knowledge raw data management function. The acquired raw data involves RAN network issues number, issues description, issues type, issue root cause, equipment vendor, network performance parameters (e.g., connection rate, drop rate, switching success rate, user downlink rate and coverage rate), and optimization plan (e.g., parameter modification, and work parameter adjustments). The cleaned and verified raw data are used for knowledge construction.

Knowledge construction

  • – Knowledge modelling, the ontology model of RAN network optimization, can be set up and represented by resource description framework (RDF) through knowledge modelling function. The results of knowledge modelling can be applied to knowledge extraction, fusion, storage, reasoning and validation (e.g., "issue type", "root cause of the issue", "optimization plan" and their
| + +| Title | Knowledge management of RAN network optimization based on framework of KMTOM | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

relationship can be defined as entity type and relation in the ontology model).

  • – Knowledge extraction: multiple knowledge triplets are extracted by entity extraction and relation extraction from raw data (output triplets such as "issues number01" – "issues type" – "low wireless connection rate", "issues number 01" – "issues root cause" – "Interference-D6 interference", "issues number 01" – "optimization plan" – "power control").
  • – Knowledge fusion: knowledge from different RAN network sources is integrated to move redundancy and eliminate ambiguity through the knowledge fusion function, to ensure a unified and unique identifier.
  • – Knowledge reasoning: the missing and incomplete RAN network optimization knowledge, could be found through reasoning with some algorithms.
  • – Knowledge validation: the comprehensive knowledge quality evaluation analysis of knowledge evaluation indicators, including accuracy, recall and integrity, is carried out in knowledge validation function to validate the results of the knowledge extraction, fusion and reasoning.

Knowledge storage
The qualified knowledge is stored in the knowledge graph database.

Knowledge service
To meet the customer's retrieval requirements about RAN resource coverage optimization (e.g., through the keyword "coverage optimization"), the RAN resource coverage optimization-related knowledge in the graph is provided to the customer, using knowledge retrieval in knowledge service.

| + +## Bibliography + +- [b-ITU-T F.750] Recommendation ITU-T F.750 (2005), *Metadata framework*. +- [b-ITU-T Y.4563] Recommendation ITU-T Y.4563 (2021), *Requirements and functional model to support data interoperability in Internet of things environments*. +- [b-ETSI GS ENI 005] ETSI GS ENI 005 V2.1.1 (2021-12), *Experiential Networked Intelligence (ENI); System Architecture*. +- [b-ETSI GR ENI 031] ETSI GR ENI 031 (2024), *Experiential Networked Intelligence (ENI); Construction and application of fault maintenance network knowledge graphs*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03d5758c21d96732a486b7f715b2139db01b5feb --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d5d3822ffd91b69e9a4fcb9bae44738b993af131c504d3f176abaf2920049f0 +size 23120 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d431d8615891f29408658a59652b32a872eae1c --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24306c5a7f6d9dcefb7cc578cd1767c8588ec616d623b5f0aa2c533c0e092ef4 +size 24720 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..140d8770ca5c00982ace54002915865e25f71d53 --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b36992ac99867b38062d7c92248d4a8590a7ea609d7fb166db322b65e56b6b50 +size 37590 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60fd6415e63d1e4d5ff092fced362630eb564bcf --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e945568f7c25a04cd0f1aa236c04b8722d270dda72851dcf728ef43c5690bc23 +size 25436 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f558281cbe4a244fe72971132a0f21a86405954 --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4be47939fa1e977ec4934ec721416c42f25a415877e1baf4fdf5d6516ca19b9 +size 44394 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7046a543d096b444a8c1ece34ba983045745bdd9 --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26af1eb37e5c51c2192a31486a10e284c1011fa61541a91ccc7f21d42b07e246 +size 30190 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..945fc2e6d663759c8fe1a40747f912f2d39de5b7 --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5b246edbe12279b3407add12a215adcbd0271bec547052661afd23a1288cf82 +size 141854 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfc9f1abc32ab41e3aa7fd7ba440f14aed49b26b --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:033710c872ec66b020680ab2faa63391f22cc60e45bc75d0749f880a0caeee48 +size 18254 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3c47b5aa0d9ede745a731859a9b7b33ca3ae11e --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b4b282be314f996292d6d55370bc5c6a6a2d512bcd4e62448e354d4163bbef0 +size 21144 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29cbfdd3d065249af2cc5cfe6bc4a930580efacd --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc154abfc2f46762a7890423b5bfa3e9ef5941a54aeb05148a577fd9f331a160 +size 56942 diff --git a/marked/M/T-REC-M.3351.2-202510-I_PDF-E/raw.md b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..63f624d30d7a562b869094d147619c58e761b693 --- /dev/null +++ b/marked/M/T-REC-M.3351.2-202510-I_PDF-E/raw.md @@ -0,0 +1,1142 @@ + + +# Recommendation**ITU-T M.3351.2 (10/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +# **Process of telecommunication operation and management knowledge graph construction** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3351.2 + +# Process of telecommunication operation and management knowledge graph construction + +## Summary + +The complexity of telecommunication operation and management for networks and services is increasing significantly due to evolving network architectures and service demands. To address this, knowledge graphs offer a structured approach to modelling domain knowledge and support intelligent applications in telecommunication operation and management, such as fault diagnosis, service optimization, and network planning. The constructed telecommunication operation and management knowledge graph describes various concepts and their relationships in telecommunication scenarios. It forms a semantic graph that systematizes and interconnects knowledge in the field of telecommunication operation and management. It is required to outline the process and detailed steps for building telecommunication operation and management knowledge graph to guide its construction in telecommunication operation and management scenarios. + +Recommendation ITU-T M.3351.2 provides principles, process and typical use cases for the construction of telecommunication operation and management knowledge graph. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3351.2 | 2025-10-14 | 2 | 11.1002/1000/16467 | + +## Keywords + +Knowledge graph construction, telecommunication operation and management knowledge graph. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|-----|---------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Introduction..... | 2 | +| 7 | Principles for telecommunication operation and management knowledge graph construction..... | 3 | +| 8 | Process of telecommunication operation and management knowledge graph construction..... | 4 | +| 8.1 | Overview ..... | 4 | +| 8.2 | Step 1: Knowledge modelling ..... | 5 | +| 8.3 | Step 2: Knowledge raw data management ..... | 5 | +| 8.4 | Step 3: Knowledge annotation..... | 6 | +| 8.5 | Step 4: Knowledge extraction ..... | 7 | +| 8.6 | Step 5: Knowledge fusion ..... | 8 | +| 8.7 | Step 6: Knowledge reasoning..... | 9 | +| 8.8 | Step 7: Knowledge validation ..... | 10 | +| 8.9 | Step 8: Knowledge graph storage..... | 11 | +| | Appendix I – A use case on knowledge graph construction for network fault diagnosis..... | 12 | +| | Appendix II – A use case on knowledge graph construction for proactive network optimisation ..... | 18 | +| | Bibliography..... | 23 | + + + +# Recommendation ITU-T M.3351.2 + +# Process of telecommunication operation and management knowledge graph construction + +# 1 Scope + +This Recommendation provides principles and processes of telecommunication operation and management knowledge graph construction based on the functions defined in [ITU-T M.3351.1]. + +The scope of this Recommendation includes: + +- Principles for telecommunication operation and management knowledge graph construction. +- Processes of telecommunication operation and management knowledge graph construction. +- Some typical use cases of telecommunication operation and management knowledge graph construction. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[[ITU-T M.3351.1](#)] Recommendation ITU-T M.3351.1 (2024), *Framework of knowledge management for telecom operation and management*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 knowledge graph** [b-ETSI GR ENI 031]: Structured representation of knowledge that uses a graph data structure and formal logic to represent entities and their relationships. + +**3.1.2 ontology** [b-ITU-T Y.4500.12]: Formal specification of a conceptualization, i.e., defining concepts as objects with their properties and relationships versus other concepts. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 telecommunication operation and management knowledge graph (TOMKG)**: Structured representation of knowledge utilizing a graph data structure and formal logic to represent entities and their relationships within telecommunication operation, management and maintenance activities. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------------| +| AI | Artificial Intelligence | +| API | Application Programming Interface | + +| | | +|--------|------------------------------------------------------------| +| BERT | Bidirectional Encoder Representations from Transformers | +| CSV | Comma Separated Values | +| GPT | Generative Pre-trained Transformer | +| JSON | JavaScript Object Notation | +| KPI | Key Performance Indicators | +| OWL | Web Ontology Language | +| PRB | Physical Resource Block | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| RDF | Resource Description Framework | +| SLA | Service Level Agreement | +| SPARQL | SPARQL protocol and RDF Query Language | +| SQL | Structured Query Language | +| SWRL | Semantic Web Rule Language | +| TOMKG | Telecommunication Operation and Management Knowledge Graph | +| URLLC | Ultra-Reliable Low Latency Communication | +| VNF | Virtual Network Function | +| XML | extensible Markup Language | +| XPath | XML Path Language | + +# 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +# 6 Introduction + +The complexity of telecommunication operation and management for networks and services is increasing significantly due to evolving network architectures and service demands. To address this, knowledge graphs offer a structured approach to modelling domain knowledge and support intelligent applications in telecommunication operation and management, such as fault diagnosis, service optimization, and network planning. + +[ITU-T M.3351.1] proposes a framework of knowledge management in telecommunication operation and management, as shown in Figure 1. In this framework, the knowledge raw-data management provides capabilities of raw data lifecycle management and raw data quality management. The knowledge construction provides capabilities such as knowledge modelling, knowledge annotation, knowledge extraction, knowledge fusion, knowledge reasoning, and knowledge validation to accomplish the transformation from raw data to knowledge for telecommunication operation and management. The knowledge storage provides storage capabilities and knowledge base. + +This Recommendation aims to provide the process and detailed steps of telecommunication operation and management knowledge graph (TOMKG) construction involving defined functions in [ITU-T M.3351.1], which are knowledge raw data management, knowledge construction and knowledge storage to instruct the complete construction for telecommunication operation and management knowledge graph. + +![Figure 1 – Framework of knowledge management for telecommunication operation and management in [ITU-T M.3351.1]. The diagram shows a hierarchical structure of knowledge management. At the top is 'Knowledge management for telecom operation and management'. Below it are two horizontal bars: 'Knowledge scenario application' (Planning and construction, Operations support and readiness, Fulfilment, Assurance, Billing) and 'Knowledge service' (Intent analysis, Knowledge retrieval, Knowledge recommendation, Knowledge question and answering, Knowledge service management). The central part is a large orange box containing 'Knowledge construction' (Knowledge modelling, Knowledge annotation, Knowledge extraction, Knowledge fusion, Knowledge reasoning, Knowledge validation), 'Knowledge storage', and 'Knowledge update and management' (Knowledge update, Knowledge construction process management, Knowledge version management, Knowledge classification management). At the bottom is a horizontal bar for 'Knowledge raw data management'. An 'External system' on the left is connected via a double-headed arrow labeled 'Knowledge input and share'.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +The diagram illustrates the framework of knowledge management for telecommunication operation and management. It is structured as follows: + +- External system**: Located on the left, connected to the main framework via a double-headed arrow labeled **Knowledge input and share**. +- Knowledge management for telecom operation and management**: The top-level container, which includes: + - Knowledge scenario application**: A horizontal bar containing five sub-functions: **Planning and construction**, **Operations support and readiness**, **Fulfilment**, **Assurance**, and **Billing**. + - Knowledge service**: A horizontal bar containing five sub-functions: **Intent analysis**, **Knowledge retrieval**, **Knowledge recommendation**, **Knowledge question and answering**, and **Knowledge service management**. + - Central Core**: A large orange box containing: + - Knowledge construction**: A 3x2 grid of sub-functions: **Knowledge modelling**, **Knowledge annotation**, **Knowledge extraction**, **Knowledge fusion**, **Knowledge reasoning**, and **Knowledge validation**. + - Knowledge storage**: A vertical orange box. + - Knowledge update and management**: A vertical stack of four sub-functions: **Knowledge update**, **Knowledge construction process management**, **Knowledge version management**, and **Knowledge classification management**. + - Knowledge raw data management**: A horizontal orange bar at the bottom. + +Figure 1 – Framework of knowledge management for telecommunication operation and management in [ITU-T M.3351.1]. The diagram shows a hierarchical structure of knowledge management. At the top is 'Knowledge management for telecom operation and management'. Below it are two horizontal bars: 'Knowledge scenario application' (Planning and construction, Operations support and readiness, Fulfilment, Assurance, Billing) and 'Knowledge service' (Intent analysis, Knowledge retrieval, Knowledge recommendation, Knowledge question and answering, Knowledge service management). The central part is a large orange box containing 'Knowledge construction' (Knowledge modelling, Knowledge annotation, Knowledge extraction, Knowledge fusion, Knowledge reasoning, Knowledge validation), 'Knowledge storage', and 'Knowledge update and management' (Knowledge update, Knowledge construction process management, Knowledge version management, Knowledge classification management). At the bottom is a horizontal bar for 'Knowledge raw data management'. An 'External system' on the left is connected via a double-headed arrow labeled 'Knowledge input and share'. + +M.3351.2(25) + +**Figure 1 – Framework of knowledge management for telecommunication operation and management in [ITU-T M.3351.1]** + +# 7 Principles for telecommunication operation and management knowledge graph construction + +It is required to comply with the following principles for constructing TOMKG: + +- 1) **Compatibility**: It is required to align with the framework outlined in [ITU-T M.3351.1]. +- 2) **Data accuracy**: It is required to ensure that the collected and organized raw data originates from credible and authoritative sources. +- 3) **Knowledge consistency**: It is required to ensure knowledge within the graph is coherent, avoiding contradictory or mutually exclusive information. +- 4) **Scalability and extensibility**: The TOMKG is required to be highly scalable, enabling it to be updated and expanded as new network knowledge and information emerge. +- 5) **Security and privacy**: The construction of the knowledge graph is required to consider security and privacy protection. Appropriate measures, such as data anonymization, data encryption, access control and authentication, are required to be implemented to safeguard the security and privacy of knowledge graph data. + +# 8 Process of telecommunication operation and management knowledge graph construction + +## 8.1 Overview + +The telecommunication operation and management knowledge graph construction process as shown in Figure 2 aligns with the knowledge management framework in [ITU-T M.3351.1]. The process is recommended to comprise nine steps: knowledge modelling, knowledge raw data management, knowledge annotation, knowledge extraction, knowledge fusion, knowledge reasoning, knowledge validation, knowledge graph storage and knowledge service. + +![Figure 2: The overview of telecommunication operation and management knowledge graph construction process. The diagram shows a flow from step 1 (Knowledge modelling) to step 9 (Knowledge service). Step 1 points to steps 3, 4, 5, and 6. Step 2 (Knowledge raw data management) points to steps 3 and 4. Steps 3, 4, 5, and 6 point to step 7 (Knowledge validation). Step 7 points to step 8 (Knowledge graph storage), which points to step 9 (Knowledge service).](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` +graph LR; 1[① Knowledge modelling] --> 3[③ Knowledge annotation]; 1 --> 4[④ Knowledge extraction]; 1 --> 5[⑤ Knowledge fusion]; 1 --> 6[⑥ Knowledge reasoning]; 2[② Knowledge raw data management] --> 3; 2 --> 4; 3 --> 4; 4 --> 5; 5 --> 6; 6 --> 7[⑦ Knowledge validation]; 7 --> 8[⑧ Knowledge graph storage]; 8 --> 9[⑨ Knowledge service]; +``` + +Figure 2: The overview of telecommunication operation and management knowledge graph construction process. The diagram shows a flow from step 1 (Knowledge modelling) to step 9 (Knowledge service). Step 1 points to steps 3, 4, 5, and 6. Step 2 (Knowledge raw data management) points to steps 3 and 4. Steps 3, 4, 5, and 6 point to step 7 (Knowledge validation). Step 7 points to step 8 (Knowledge graph storage), which points to step 9 (Knowledge service). + +M.3351.2(25) + +**Figure 2 – The overview of telecommunication operation and management knowledge graph construction process** + +- 1) **Knowledge modelling.** This step involves defining the ontology of the knowledge graph and expressing knowledge formally. The results of knowledge modelling can be used in various steps, including knowledge annotation, knowledge extraction, knowledge fusion, and knowledge reasoning. +- 2) **Knowledge raw data management.** This step involves acquiring, pre-processing, and evaluating raw data collected from different data sources. Data that meets quality requirements is used for knowledge extraction and annotation. +- 3) **Knowledge annotation.** This step involves labelling raw data to provide accurate labelled knowledge usable for supervised machine learning in other steps. The annotated data can be used for model training in knowledge extraction, fusion, and reasoning. +- 4) **Knowledge extraction.** This step involves extracting knowledge graph elements from raw data of various sources and structures based on rules, general or customized artificial intelligence (AI) models. The customized extraction model can be trained on the annotated data. +- 5) **Knowledge fusion.** This step involves integrating knowledge based on rules, general or customized AI models to form a globally unified knowledge identifier. The customized fusion model can be trained on the annotated data. +- 6) **Knowledge reasoning.** This step involves performing logical inference to discover, locate and handle incomplete, implicit, or erroneous knowledge based on rules, general or customized AI models. The customized reasoning model can be trained using the annotated data. +- 7) **Knowledge validation.** This step involves assessing the quality of the generated knowledge in the TOMKG during the overall construction process. +- 8) **Knowledge graph storage.** This step involves storing knowledge graph including entities, attributes, and relations in storage database. + +- 9) **Knowledge service.** This step involves providing knowledge services based on the constructed knowledge graph. + +NOTE – The application of knowledge graph is the purpose of constructing knowledge graph. Knowledge service will not be elaborated on in this Recommendation. + +## 8.2 Step 1: Knowledge modelling + +Based on [ITU-T M.3351.1], knowledge modelling is a fundamental sub-process for TOMKG construction, aiming to organize and represent scenario-specific knowledge in a structured and formalized manner. In this step, it is required to define the ontology model and knowledge representation for TOMKG construction to instruct the other steps. + +A general flowchart for knowledge modelling is shown in Figure 3. + +![Flowchart of Step 1: Knowledge modelling](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates the sub-process of knowledge modelling, titled "Step 1: Knowledge modelling". It is divided into two main stages: "Ontology model determination" and "Knowledge representation determination". + +**Ontology model determination** consists of two sub-steps: "Analyse scenario and define scope" followed by "Conceptualise and abstract ontology". + +**Knowledge representation determination** consists of two sub-steps: "Select formal ontology language" followed by "Leverage ontology constructs". + +An arrow connects the end of the first stage ("Conceptualise and abstract ontology") to the start of the second stage ("Select formal ontology language"). + +M.3351.2(25) + +Flowchart of Step 1: Knowledge modelling + +**Figure 3 – Sub-process of knowledge modelling** + +The sub-process of knowledge modelling encompasses the following sub-steps: + +### 1) Ontology model determination + +- Analyse scenario and define scope.** Conduct thorough research to understand the specific scenario, for which the TOMKG is being developed, such as troubleshooting, alarm location, network optimization, etc. Clearly delineate the boundaries of the TOMKG, focusing exclusively on the most relevant aspects of the identified scenario. +- Conceptualize and abstract ontology.** + - Define the core concepts and categories of information essential to the scenario (e.g., network devices, services, alarms). + - Develop a hierarchical structure to organize concepts and define relationships between concepts to capture how they interact or are associated within the scenario (e.g., connects-to, triggers, provides). + +### 2) Knowledge representation determination + +- Select formal ontology language.** Select a formal standardized and machine-processable ontology language such as resource description framework (RDF) or web ontology language (OWL) to ensure ontology compatibility and interoperability with other knowledge graphs and systems. +- Leverage ontology constructs.** Utilize ontology constructs such as classes, properties, and instances to represent concepts and relationships within the scenario. Clearly specify the properties of each concept and the constraints that govern their usage. + +## 8.3 Step 2: Knowledge raw data management + +Based on [ITU-T M.3351.1], knowledge raw data management aims to ensure the accuracy, completeness, and relevance of the knowledge represented in the TOMKG. In this step, it is required to clarify and prepare the network, service and customer data to meet TOMKG construction requirements. + +A general flowchart for knowledge raw data management is shown in Figure 4. + +![Flowchart of Step 2: Knowledge raw data management](007b053fe94a8348f75128a584503fd0_img.jpg) + +``` +graph LR; subgraph Step2 [Step 2: Knowledge raw data management]; A[Raw data acquisition] --> B[Raw data pre-processing]; B --> C[Raw data quality evaluation]; end; +``` + +The diagram shows a flowchart titled "Step 2: Knowledge raw data management". It consists of three rectangular boxes connected by arrows in a linear sequence: "Raw data acquisition", "Raw data pre-processing", and "Raw data quality evaluation". The entire flow is enclosed in a larger rectangular box. The text "M.3351.2(25)" is located at the bottom right of the diagram. + +Flowchart of Step 2: Knowledge raw data management + +**Figure 4 – Sub-process of knowledge raw data management** + +The sub-process of knowledge raw data management encompasses the following sub-steps: + +- 1) **Raw data acquisition** + - a) **Identify data sources.** Determine where the data resides (e.g., internal databases, external application programming interfaces (APIs), web scraping, third-party providers). Verify the data sources are accessible and the necessary permissions have been obtained for use. + - b) **Acquire data.** Utilize appropriate tools and techniques to acquire data from the identified sources. Get both structured data (e.g., databases, spreadsheets) and unstructured data (e.g., text documents, web pages, images) for comprehensive representation in the TOMKG. +- 2) **Raw data pre-processing.** Clean the data to remove inconsistencies, errors, and duplicates, ensuring that the information is accurate and reliable. Standardize data formats, units, and terminology to facilitate integration and comparison across different sources. +- 3) **Raw data quality evaluation** + - a) **Establish evaluation criteria** + - Check the accuracy of the data, ensuring that it conforms to expected patterns and constraints. + - Verify that the data covers all relevant aspects of the scenario and includes all necessary information. + - Monitor the update frequency of the data sources and ensure that the TOMKG is regularly updated to reflect the latest information. + - b) **Evaluate the quality of raw data.** Perform quality evaluation on raw data according to the evaluation criteria. + +## 8.4 Step 3: Knowledge annotation + +Based on [ITU-T M.3351.1], knowledge annotation involves labelling accurate knowledge to facilitate effective knowledge extraction, fusion and reasoning. In this step, it is required to label accurate entities and relationships as training samples to train models. + +A general flowchart for knowledge annotation is shown in Figure 5. + +![Flowchart of Step 3: Knowledge annotation](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` +graph LR; subgraph Step3 [Step 3: Knowledge annotation]; A[Annotation methods selection] --> B[Entity, attribute and relation annotation]; B --> C[Model training, validation and deployment]; end; +``` + +The diagram shows a flowchart titled "Step 3: Knowledge annotation". It consists of three rectangular boxes connected by arrows in a linear sequence: "Annotation methods selection", "Entity, attribute and relation annotation", and "Model training, validation and deployment". The entire flow is enclosed in a larger rectangular box. The text "M.3351.2(25)" is located at the bottom right of the diagram. + +Flowchart of Step 3: Knowledge annotation + +**Figure 5 – Sub-process of knowledge annotation** + +The process of knowledge annotation encompasses the following sub-steps: + +### 1) Annotation methods selection + +- a) **Manual annotation.** Employ human experts to label raw data, particularly suited for small datasets, highly complex information, or situations requiring nuanced judgement and domain expertise. +- b) **Semi-automated annotation.** Leverage AI models to generate initial annotations, which are then reviewed, corrected, and validated by human experts. This approach balances efficiency with accuracy. +- c) **Fully automated annotation.** Utilize advanced AI models trained on existing annotated data to label data with minimal or no human intervention. This method is optimal for large-scale, high-volume, and repetitive annotation tasks where patterns are well-established. + +### 2) Entity, attribute and relationship annotation + +- a) **Identify and label entities.** Identify and label entities (e.g., network devices, services, customers, faults) according to requirements. Assign unique identifiers to each entity to ensure consistency across the TOMKG. +- b) **Identify and label relationships.** Identify and label semantic relationships between entities, such as "was linked to," "was founded by," or "was caused by" according to requirements. Ensure relationship labels accurately reflect the nature of the interaction. +- c) **Assign attributes.** Assign attributes to entities, providing additional details such as parameters, alarm description or other descriptive information according to requirements. + +### 3) Model training, validation and deployment + +- a) **Model training.** Utilize the high-quality annotated data as input to train AI models specifically designed for knowledge extraction, fusion and reasoning. +- b) **Model validation.** Calculate relevant metrics to evaluate the trained model on a separate and unseen validation dataset. Based on the validation results, refine the model iteratively by adjusting parameters, modifying the architecture, augmenting the training data, or improving annotation quality. +- c) **Model deployment.** Integrate the validated and refined model into the telecommunication environment. This entails deploying the model to production infrastructure, enabling it to process data and carry out its designated extraction, fusion, or reasoning tasks. + +## 8.5 Step 4: Knowledge extraction + +Based on [ITU-T M.3351.1], knowledge extraction involves extracting and structuring telecommunication operation and management knowledge from raw data and representing it in a graph format. In this step, it is required to transform raw network, service, or customer data into knowledge graph elements by explicitly defining entities, their attributes, and the relationships between them. + +A general flowchart for knowledge extraction is shown in Figure 6. + +![Figure 6 – Sub-process of knowledge extraction. The diagram shows 'Step 4: Knowledge extraction' containing two main boxes. The left box is 'Extraction methods determination'. An arrow points from this box to the right box, which is 'Perform extraction'. Inside the 'Perform extraction' box, there are three stacked sub-boxes: 'Entity extraction', 'Attribute extraction', and 'Relationship extraction'. The text 'M.3351.2(25)' is at the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +``` + +graph LR + subgraph Step4 [Step 4: Knowledge extraction] + A[Extraction methods determination] --> B[Perform extraction] + subgraph B [Perform extraction] + B1[Entity extraction] + B2[Attribute extraction] + B3[Relationship extraction] + end + end + +``` + +M.3351.2(25) + +Figure 6 – Sub-process of knowledge extraction. The diagram shows 'Step 4: Knowledge extraction' containing two main boxes. The left box is 'Extraction methods determination'. An arrow points from this box to the right box, which is 'Perform extraction'. Inside the 'Perform extraction' box, there are three stacked sub-boxes: 'Entity extraction', 'Attribute extraction', and 'Relationship extraction'. The text 'M.3351.2(25)' is at the bottom right. + +**Figure 6 – Sub-process of knowledge extraction** + +The sub-process of knowledge extraction encompasses the following sub-steps: + +### **1) Extraction methods determination** + +- a) **Structured extraction.** Directly extract structured data from sources with predefined schemas (e.g., relational databases, comma separated values (CSV) files, extensible markup language (XML) / JavaScript object notation (JSON) logs) using structured query language (SQL) queries, XML path language (XPath), or schema-specific parsers. +- b) **Unstructured extraction.** Apply AI techniques to extract knowledge from unstructured or semi-structured sources (e.g., trouble tickets, alarm logs, configuration notes, technician reports, email threads). + - Utilize custom-trained AI models developed using scenario-specific labelled data from the knowledge annotation step. + - Employ general AI techniques such as rule matching, transformer-based models (e.g., bidirectional encoder representations from transformers (BERT), Generative pre-trained transformer (GPT) variants) fine-tuned in telecommunication context. + +### **2) Perform extraction** + +- a) **Entity extraction.** Identify and isolate distinct entities within the source data. Entities represent core concepts in the telecommunication domain (e.g., service instance, fault, alarm, work order). +- b) **Attribute extraction.** For each identified entity, parse the source data to extract relevant properties that provide descriptive details (e.g., device status, alarm severity, service bandwidth, customer SLA level, timestamp, location, or configuration parameters). +- c) **Relationship extraction.** Identify and define the semantic connections between pairs of entities. Typical telecommunication relationships include: + - Causal relationships: fault A causes service degradation B. + - Dependency relationships: service instance C depends on network element D. + - Connectivity relationships: router E connects to switch F. + - Ownership/containment relationships: customer G owns service instance H; physical site I contains device J. + - Correlation relationships: alarm K correlates with alarm L. + +## **8.6 Step 5: Knowledge fusion** + +Based on [ITU-T M.3351.1], knowledge fusion is a critical sub-process that establishes unique identifiers and consistent relationships for TOMKGs. In this step, it is required to integrate diverse TOMKGs to create a unified, coherent and non-redundant knowledge graph. + +A general flowchart for knowledge fusion is shown in Figure 7. + +![Figure 7: Sub-process of knowledge fusion flowchart](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +``` + +graph LR + subgraph Step5 [Step 5: Knowledge fusion] + A[Acquisition of multi-source TOMKGs] --> B[Ontology alignment] + B --> C[Entity, attribute, and relationship alignment] + end + style Step5 fill:none,stroke:none + style A fill:#fff,stroke:#000 + style B fill:#fff,stroke:#000 + style C fill:#fff,stroke:#000 + +``` + +M.3351.2(25) + +Figure 7: Sub-process of knowledge fusion flowchart + +**Figure 7 – Sub-process of knowledge fusion** + +The sub-process of knowledge fusion encompasses the following sub-steps: + +- 1) **Acquisition of multi-source TOMKGs.** Obtain knowledge graphs which are constructed from multiple sources. +- 2) **Ontology alignment.** Ontology schemas from different graph sources are integrated to create a unified ontology. + - a) Obtain ontology data of different knowledge graphs. + - b) Calculate the similarities between ontology data based on the intelligent model. + - c) Integrate ontologies with similarity scores exceeding a predefined threshold (e.g., $> 0.9$ ) to establish a unified ontology framework and TOMKGs aligned with the ontology. +- 3) **Entity, attribute and relationship alignment.** Entity alignment involves matching entities from different sources that represent the same telecommunication operation and management object or concept. Attribute and relationship alignment involve comparing attribute values and relationship types to determine their equivalence or similarity. + - a) Obtain entities, attributes and relationships in TOMKGs aligned with the ontology. + - b) In embedding layer, input entities, attributes and relationships and perform structural embeddings and semantic embeddings on those data by different embedding models to obtain their structural embedding vectors and semantic embedding vectors. + - c) In the alignment layer, input mixed embedding vectors from embedding layer and compare match results by different alignment models so as to obtain entities, attributes and relationships that can be fully aligned. + +## 8.7 Step 6: Knowledge reasoning + +Based on [ITU-T M.3351.1], knowledge reasoning is required to leverage logical inference and predictive analytics to identify, complete, and correct entities and relationships within the TOMKG, enhancing its completeness, accuracy, and predictive power. + +A general flowchart for knowledge reasoning is shown in Figure 8. + +![Figure 8: Sub-process of knowledge reasoning flowchart](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` + +graph LR + subgraph Step6 [Step 6: Knowledge reasoning] + A[Entity and relationship completion] --> B[Entity and relationship correction] + end + style Step6 fill:none,stroke:none + style A fill:#fff,stroke:#000 + style B fill:#fff,stroke:#000 + +``` + +M.3351.2(25) + +Figure 8: Sub-process of knowledge reasoning flowchart + +**Figure 8 – Sub-process of knowledge reasoning** + +The sub-process of knowledge reasoning encompasses the following sub-steps: + +- 1) **Entity and relationship completion.** It is required to identify and fill in missing entities and relationships in the TOMKG. + - a) **Missing entities and relationships identification.** Conduct a thorough review of the existing TOMKG to identify potentially missing entities (e.g., undiscovered network + +devices, latent services) and relationships (e.g., untraced dependencies, unresolved fault correlations). Use automated tools or manual checks to discover these gaps. + +- b) **Entities and relationships prediction.** Predict and infer missing and potential entities and relationships using rule-based reasoning (e.g., semantic web rule language (SWRL) rules), statistical analysis (e.g., link prediction via matrix factorization), and AI-based methods (e.g., graph neural networks, transformer-based models fine-tuned in telecommunication context). +- 2) **Entity and relationship correction.** It is required to detect, locate and correct errors in entities and relationships within the knowledge graph. +- a) **Errors detection.** Errors in the TOMKG are identified using rule matching (e.g., an entity cannot belong to two mutually exclusive categories), statistical analysis (e.g., topological features or data distribution patterns of the graph), and AI-based methods. + - b) **Error localization.** Locate the detected errors to determine their specific positions and scopes for subsequent error correction (e.g., incorrect "connection" relationship between entity "switch X" and "port Y"). + - c) **Error correction.** Rectify erroneous entities and relationships based on rule-driven correction (e.g., adjusting "device temperature of 1000°C" to a reasonable range), statistical correction (e.g., correcting abnormal values using the average lifespan of similar devices), and AI-assisted correction (e.g., use AI models to predict reasonable entities or relationships to replace erroneous content). + +## 8.8 Step 7: Knowledge validation + +Based on [ITU-T M.3351.1], knowledge validation is required to ensure the TOMKG meets quality standards for accuracy, consistency, and relevance through systematic evaluation against defined criteria. + +A general flowchart for knowledge validation is shown in Figure 9. + +![Flowchart of Step 7: Knowledge validation sub-process](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` +graph LR; A[Define evaluation objectives] --> B[Establish validation criteria]; B --> C[Prepare evaluation tools and methods]; C --> D[Data collection]; D --> E[Execute evaluation]; E --> F[Analyse results]; +``` + +The diagram illustrates the sub-process of knowledge validation as a linear flowchart. It is titled "Step 7: Knowledge validation" and consists of six sequential steps: "Define evaluation objectives", "Establish validation criteria", "Prepare evaluation tools and methods", "Data collection", "Execute evaluation", and "Analyse results". Each step is represented by a rectangular box connected by an arrow pointing to the next. The entire flowchart is enclosed in a rectangular border. In the bottom right corner, outside the main flow but inside the border, is the text "M.3351.2(25)". + +Flowchart of Step 7: Knowledge validation sub-process + +M.3351.2(25) + +**Figure 9 – Sub-process of knowledge validation** + +The sub-process of knowledge validation encompasses the following sub-steps: + +- 1) **Define evaluation objectives.** Clarify the purpose of the evaluation and specify validation targets (e.g., post-extraction graph, fused knowledge graph, reasoning outputs). +- 2) **Establish validation criteria.** Define specific evaluation metrics and standards aligned with telecommunication requirements including relevance, accuracy, consistency, timeliness, etc. +- 3) **Prepare evaluation tools and methods.** Select appropriate tools and technologies for conducting the evaluation (e.g., SPARQL protocol and RDF query language (SPARQL) queries, cypher queries, python scripts). +- 4) **Data collection.** Extract necessary data from the TOMKG for assessment including sample extraction and full-scale data processing. +- 5) **Execute evaluation.** Conduct a detailed inspection and analysis of the TOMKG according to predetermined criteria and methods. + +- 6) **Analyse results.** Quantify performance against criteria and generate evaluation results. Analyse the evaluation results, identify the problematic steps and implement corresponding improvements. + +## 8.9 Step 8: Knowledge graph storage + +Based on [ITU-T M.3351.1], knowledge graph storage is required to store the TOMKG in a database in an organized way. + +A general flowchart for knowledge storage is shown in Figure 10. + +![Flowchart of Step 8: Knowledge graph storage sub-process](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +graph LR; A[Storage design] --> B[Graph data loading]; B --> C[Maintenance and update]; +``` + +The diagram illustrates the sub-process of knowledge storage, titled "Step 8: Knowledge graph storage". It consists of three sequential steps: "Storage design", "Graph data loading", and "Maintenance and update", connected by arrows. The reference "M.3351.2(25)" is noted at the bottom right. + +Flowchart of Step 8: Knowledge graph storage sub-process + +**Figure 10 – Sub-process of knowledge storage** + +The sub-process of knowledge storage encompasses the following sub-steps: + +- 1) **Storage design.** Select appropriate storage solutions based on the knowledge representation such as RDF-based storage, native graph database storage or customized storage solutions. +- 2) **Graph data loading.** Load the TOMKG into the chosen storage system. + - a) It is required to support bulk import operations. + - b) It is required to build indexes on stored data and perform necessary optimizations. +- 3) **Maintenance and update.** Regularly maintain and update the knowledge graph to reflect the latest information, including adding new graph data and removing outdated knowledge. + +# Appendix I + +## A use case on knowledge graph construction for network fault diagnosis + +(This appendix does not form an integral part of this Recommendation.) + +| | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Knowledge graph construction for network fault diagnosis | +| Description |

Scenario: This use case focuses on knowledge graph construction process for network fault diagnosis. The network fault diagnosis knowledge graph captures the relationships between network alarms, root causes, fault handling steps, and solutions. The knowledge graph integrates historical fault-handling experience and domain expert knowledge to achieve rapid and accurate fault diagnosis, improving network operation and maintenance efficiency, and supporting multiple application scenarios such as intelligent fault location, cause analysis, and handling recommendations.

| +| Process of knowledge graph construction |

The process of knowledge graph construction for network fault diagnosis is as follows.

Step 1: Knowledge modelling

1) Ontology model determination

Systematically analyse the fault diagnosis workflow to identify key entities and relationships to establish a complete domain ontology model.

Core concepts include network device classes (e.g., base stations, core network equipment, transmission equipment), alarm classes (e.g., alarm levels, alarm codes), fault types (hardware faults, software faults), and solutions (e.g., handling steps, required tools).

Relationship definitions cover inclusion and connection relationships between devices, fault-related trigger and impact relationships, and resolution and mitigation relationships in the handling process.

2) Knowledge representation determination

For knowledge representation, web ontology language (OWL) is chosen as the formal ontology language.

It is an example that describes the output of knowledge modelling.

<owl:Ontology rdf:about="http://example.org/alarm-ontology">   <owl:versionInfo>1.0</owl:versionInfo>   <rdfs:comment>An ontology for modeling devices, alarms, and their resolution in industrial systems.</rdfs:comment> </owl:Ontology>  <owl:Ontology rdf:about="http://example.org/alarm-ontology"/>   <owl:Class rdf:about="Device"/>   <owl:Class rdf:about="Alarm"/>   <owl:Class rdf:about="Solution"/>    <owl:ObjectProperty rdf:about="triggers">     <rdfs:domain rdf:resource="Device"/>     <rdfs:range rdf:resource="Alarm"/>     <rdfs:label>TRIGGERS</rdfs:label>   </owl:ObjectProperty>    <owl:ObjectProperty rdf:about="impacts">     <rdfs:domain rdf:resource="Alarm"/>     <rdfs:range rdf:resource="Device"/>     <rdfs:label>IMPACTS</rdfs:label>   </owl:ObjectProperty>
| + +``` + +``` + +``` + + + + RESOLVES + +``` + +### Step 2: Knowledge raw data management + +#### 1) Raw data acquisition + +The raw data management adopts a multi-source data fusion approach, integrating multiple data sources such as network management system alarm logs, fault work tickets, equipment maintenance records, expert knowledge documents, and device configuration data. + +It is an example that describes raw alarm data: + +``` +{ + "alarmID": "ALM2025010501", + "deviceID": "BS001", + "alarmLevel": "Critical", + "alarmDescription": "Cell Drop Rate Exceeds Threshold", + "occurrenceTime": "2025-01-05 10:30:00" +} +``` + +#### 2) Raw data pre-processing + +Data pre-processing includes cleaning work to remove duplicate and erroneous data, standardization of time formats and alarm descriptions, and multi-source data correlation integration. + +#### 3) Raw data quality evaluation + +Meanwhile, data quality assessment standards are established to evaluate data quality from dimensions such as accuracy, completeness, and timeliness, ensuring the data foundation for subsequent knowledge construction. + +### Step 3: Knowledge annotation + +#### 1) Annotation methods selection + +The knowledge annotation processes raw data through manual and semi-automatic annotation methods. + +#### 2) Entity, attribute and relation annotation + +Entity annotation covers core entities such as devices, alarms, fault types, and solutions. Relationship annotation focuses on the relationships between alarms and devices, causal relationships between alarms, and the correspondence between solutions and faults. Entity recognition and relationship extraction models are trained based on annotated data, and model effectiveness is evaluated through validation sets. + +It is an example that describes the input and output of knowledge annotation. + +Input text: "Base station BS001 experienced a cell drop rate threshold alarm, inspection revealed it was caused by antenna azimuth deviation, resolved by adjusting the antenna angle." + +The output is the annotation result as follows. + +Entities: + +``` +[Device] Base station BS001 +[Alarm] Cell drop rate threshold alarm +[Cause] Antenna azimuth deviation +[Solution] Adjust antenna angle +``` + +Relationships: + +``` +Base station BS001 -[TRIGGERS]-> Cell drop rate threshold alarm +``` + +Antenna azimuth deviation -[CAUSES]-> Cell drop rate threshold alarm + +Adjust antenna angle -[RESOLVES]-> Cell drop rate threshold alarm + +### **Step 4: Knowledge extraction** + +#### **1) Extraction methods determination** + +For structured data, direct extraction techniques SPARQL queries are used. + +For unstructured data, knowledge extraction is performed using deep learning models and custom-trained artificial intelligence (AI) models. + +#### **2) Entity, attribute and relationship extraction** + +Deep learning models are used to identify network elements information from management data and recognize alarm information from alarm logs. Text classification model trained with annotated data is utilized to extract fault types and solutions information from work tickets. + +It is an example that describes the input and output of knowledge extraction. + +The input text is: "At 10:30 on January 5, 2025, base station BS001 triggered a cell drop rate threshold alarm (ALM2025010501). Analysis revealed signal coverage insufficiency caused by antenna azimuth deviation, maintenance personnel resolved the issue by adjusting the antenna angle." + +The output is the extraction result as follows: + +``` +{ + "entities": { + "device": "Base station BS001", + "alarm": "Cell drop rate threshold alarm (ALM2025010501)", + "fault": "Signal coverage insufficiency", + "cause": "Antenna azimuth deviation", + "solution": "Adjust antenna angle" + }, + "relationships": { + "trigger": ["Base station BS001 triggers Alarm ALM2025010501"], + "causal": ["Antenna azimuth deviation causes Signal coverage insufficiency"], + "resolution": ["Adjust antenna angle resolves Alarm ALM2025010501"] + } +} +``` + +### **Step 5: Knowledge fusion** + +#### **1) Acquisition of multi-source TOMKGs** + +The knowledge fusion is to integrate the knowledge graphs from different sources. + +Example knowledge graph 1: + +``` +{ + "device": "BS_001", + "alarm": "High Cell Drop Rate", + "time": "2025-01-05 10:30:00", + "location": "Site A" + "relationships": { + "occurs_at": " BS_001 -> Site-A", + "triggers": " BS_001 -> High Cell Drop Rate " + } +} +``` + +Example knowledge graph 2: + +``` +{ + "baseStation": "BaseStation001", + "faultType": "Cell Drop Rate Exceeded", + "occurrence": "Jan 5, 2025 10:30", +} +``` + +``` +"site": "Site-A" +``` + +``` +"relationships": { +``` + +``` + "occurs_at": " BaseStation001-> Site-A", +``` + +``` + "triggers": " BaseStation001 -> Cell Drop Rate Exceeded " +``` + +``` +} +``` + +#### 2) Ontology alignment + +Ontology alignment is performed to standardize equipment naming conventions and alarm description formats. + +#### 3) Entity, attribute and relationship alignment + +The entity alignment includes device name standardization, alarm description standardization, and fault type hierarchical standardization. Relationship fusion focuses on causal chain integration and temporal relationship organization. + +It is an example that describes the results after knowledge fusion. + +``` +{ +``` + +``` + "device": { +``` + +``` + "standardId": "BS001", +``` + +``` + "type": "BaseStation", +``` + +``` + "location": "Site A", +``` + +``` + "aliases": ["BS_001", "BaseStation001"] +``` + +``` + }, +``` + +``` + "alarm": { +``` + +``` + "standardCode": "ALM_DROP_RATE_HIGH", +``` + +``` + "standardDescription": "Cell Drop Rate Threshold Exceeded", +``` + +``` + "originalDescriptions": ["High Cell Drop Rate", "Cell Drop Rate Exceeded"], +``` + +``` + "timestamp": "2025-01-05T10:30:00Z", +``` + +``` + "severity": "Critical" +``` + +``` + }, +``` + +``` + "relationships": { +``` + +``` + "occurs_at": "BS001 -> Site-A", +``` + +``` + "triggers": "BS001 -> ALM_DROP_RATE_HIGH" +``` + +``` + } +``` + +``` +} +``` + +### Step 6: Knowledge reasoning + +#### 1) Entity and relationship completion + +For knowledge completion, the system identifies and fills in missing knowledge in the fault diagnosis graph by leveraging historical records of the same alarm – along with corresponding fault diagnosis results extracted from network logs. For instance, when a new "Cell drop rate high" alarm is triggered on base station BS002, the system predicts potential missing causes and associated relationships based on historical patterns of this alarm. It also calculates the cumulative probability for each potential cause and, based on these probabilities, generates a list of recommended solutions. + +It is an example that describes entity and relationship completion: + +``` +Input: New Alarm { +``` + +``` + "device": "BS002", +``` + +``` + "alarm": "Cell drop rate threshold exceeded", +``` + +``` + "time": "2023-12-02" +``` + +``` +} +``` + +Reasoning results based on all historical "Cell drop rate threshold exceeded" alarm records from base stations, the possible causes are calculated with probability and corresponding solutions are listed: + +``` +{ +``` + +``` + + "possibleCauses": [ + {"cause": "Antenna azimuth deviation", "probability": 0.8}, + {"cause": "High device load", "probability": 0.15}, + {"cause": "Interference source", "probability": 0.05} + ], + "recommendedSolutions": [ + {"solution": "Check and adjust antenna angle", "priority": 1}, + {"solution": "Analyze load conditions", "priority": 2}, + {"solution": "Investigate nearby interference", "priority": 3} + ] + } +} + +``` + +#### 2) Entity and relationship correction + +For correction, the system uses rules to detect and fix errors in the knowledge graph. For example, when conflicting causes are found for a coverage issue, the system localizes the error and corrects it based on historical data and expert rules, ensuring the accuracy of knowledge graph for fault diagnosis. + +### Step 7: Knowledge validation + +#### 1) Define evaluation objectives + +Conduct a comprehensive validation of the entities, attributes, and relationships describing network devices, alarms, fault causes, and solutions generated during the processes of knowledge extraction, fusion, and reasoning. + +#### 2) Establish validation criteria + +Specific evaluation metrics and standards include accuracy (verifying whether the information about network devices, alarm descriptions, fault causes, and resolution steps is correct), consistency (checking for conflicts or contradictions in the knowledge graphs constructed from different data sources, such as inconsistencies in device names or alarm levels), and timeliness (ensuring that the fault information in the knowledge graph is updated in a timely manner to accurately reflect the current network status). + +#### 3) Prepare Evaluation tools and methods + +Utilize cypher queries suitable for graph databases to inspect the associations between devices and alarms, and employ python scripts to conduct automated data checks on fault descriptions, alarm timestamps, and reasoning results. + +#### 4) Data collection + +Extract data samples from the constructed network fault diagnosis knowledge graph, covering all key entities (e.g., base stations, core equipment, alarm information) and relationships (e.g., device triggering alarms, causal relationships of faults, and associations with solutions). + +#### 5) Execute evaluation + +In accordance with the predetermined validation criteria, systematically inspect each entity and relationship. Specific operations include using automated queries to verify the accuracy of device information, alarm records, and fault reasoning results, and checking the match between the predicted fault causes in the knowledge graph and the actual situation. + +#### 6) Analyse result + +Organize and analyse the results obtained during the validation process to identify errors, inconsistencies, or omissions in the network fault diagnosis knowledge graph. Clearly point out issues such as incorrect alarm descriptions, inaccurate device information, or missing fault causes, and promptly provide feedback on the analysis results to knowledge extraction, fusion, and reasoning. + +### Step 8: Knowledge graph storage + +#### 1) Storage design + +Neo4j is selected as the graph database. + +| | | +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

2) Graph data loading
This step implements bulk import operations and creates necessary indices for efficient querying.

3) Maintenance and update
This step establishes procedures for regular graph data freshness checks and performance optimization. It provides standardized application programming interfaces (APIs) to ensure the knowledge graph remains efficiently accessible and maintainable.

Step 9: Knowledge service
This step provides knowledge services based on the network fault diagnosis constructed knowledge graph.
Fault cause inference: Automatically infer potential root causes of faults.
Fault-related knowledge query: Allow quick retrieval of relevant knowledge such as fault definitions, common symptoms, and handling precautions.

| +|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# Appendix II + +## A use case on knowledge graph construction for proactive network optimisation + +(This appendix does not form an integral part of this Recommendation.) + +| | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Knowledge graph construction for proactive network optimisation | +| Description | Scenario: This use case focuses on knowledge graph construction process for proactive network optimisation. The knowledge graph is used to enable proactive network optimisation by predicting service degradation risks during public events (e.g., concerts, sports games). The knowledge graph integrates event data, service level agreement (SLA) data, and resource utilization data to trigger pre-emptive slice scaling, ensuring uninterrupted quality of service (QoS) and SLA compliance. | +| Process of knowledge graph construction |

The process of knowledge graph construction for proactive network optimisation is as follows:

Step 1: Knowledge modelling

1) Ontology model determination

Systematically analyse the proactive network optimisation workflow to establish a complete domain ontology model.

Core concepts: public events (e.g., type, location, attendance), network slices, SLA metrics (e.g., latency, throughput), infrastructure resources e.g., (radio access network (RAN), core nodes), and optimization actions (e.g., resource scaling, traffic rerouting).

Relationships: "TRIGGER_OPTIMIZATION" (event→slice), "IMPACT" (event→SLA), "REQUIRE_ACTION" (SLA_violation→action), "HISTORICAL_PATTERN" (event→traffic_spike), "TARGET" (action→infrastructure resource), "ASSOCIATED_WITH" (slice→infrastructure resource).

2) Knowledge representation determination

Use RDF/RDF-star to represent statements with temporal annotations.

For example, Statement: "Event_X caused 50% traffic increase at 2025-07-12T20:00" is represented as:

<< :Event_X :caused "50% traffic increase" >> :occurredAt "2025-07-12T20:00"^^xsd:dateTime .

Step 2: Knowledge raw data management

1) Raw data acquisition

Sources: Public event calendars, social media trends, historical network key performance indicators (KPIs), service level agreement (SLA) logs, and geolocation APIs.

Example raw data:

{   "event_data": {     "event_id": "Stadium_Concert_2025",     "type": "MusicConcert",     "location": "Lat:34.05, Lon:-118.25",     "expected_attendees": 80000,     "date": "2025-07-12",     "start_time": "2025-07-12T19:30:00",   },   "slice_data": {     "slice_id": "Slice_#22",     "slice_type": "eMBB",     "baseline_throughput": "300Mbps",     "priority_level": "High",   }, }
| + +``` + + "serving_event": "Stadium_Concert_2025" + }, + "SLA_log": { + "metric_type": "latency", + "threshold": "15ms", + "current_value": "18ms", + "record_time": "2025-07-12T18:00:00", + "associated_slice": "Slice_#22" + }, + "resource_data": { + "resource_id": "RAN_Node_08", + "type": "RAN", + "serving_cell": "Cell_#302", + "current_load": "75%", + "max_capacity": "100Gbps" + }, + "historical_data": { + "past_event": "Stadium_Concert_2024", + "attendees_2024": 75000, + "traffic_spike_2024": "40%", + "associated_slice_2024": "Slice_#22", + "adopted_action_2024": "ResourceBoost", + "action_effect_2024": "latency reduced to 12ms" + } +} + +``` + +#### 2) Raw data pre-processing + +Normalize event attendance estimates, align timestamps across datasets, etc. + +#### 3) Raw data quality evaluation + +Criteria: Event data completeness ( $\geq 90\%$ coverage), SLA log accuracy (validated against ground truth). + +### Step 3: Knowledge extraction + +#### 1) Extraction methods determination + +For structured data, direct extraction techniques SPARQL queries are used on SLA logs, device configuration tables, structured event calendars. + +For unstructured data, natural language processing techniques are used to detect trending events and potential relationships from social media posts. + +#### 2) Entity, attribute and relationship extraction + +The example output of extraction results is as follows: + +``` + +{ + "entities": { + "event": "Stadium_Concert_2025", + "slice": "Slice_#22", + "SLA_metric": "latency", + "infrastructure_resource": "RAN_Node_08", + "optimization_action": "ResourceBoost", + }, + "relationships": { + "Stadium_Concert_2025 -TRIGGER_OPTIMIZATION→ Slice_#22", + "Stadium_Concert_2025 -IMPACT→ latency", + "latency-REQUIRE_ACTION→ ResourceBoost", + } +} + +``` + +``` + + "ResourceBoost -TARGET→ RAN_Node_08", + "Slice_#22 -ASSOCIATED_WITH→ RAN_Node_08" + } +} + +Step 4: Knowledge fusion +1) Acquisition of multi-source TOMKGs +Several knowledge graphs are collected. +Example knowledge graph 1 (2025 Stadium Concert): +{ + "entities": { + "event": "Stadium_Concert_2025", + "eventType": "Concert", + "location": "Stadium_Cell_#5", + "attendance": 80000, + "date": "2025-07-12", + "networkSlice": "Slice_22 (Enhanced_Mobile_Broadband)", + "infrastructure_resource": "RAN_Cluster_5, Core_Node_7", + "optimizationAction": "Resource_Boost_20 (Resource_Scaling, 20%)", + "trafficImpact": "50% spike at 2025-07-12T20:00 (affecting Slice_22)", + "SLAImpact": "15ms latency increase, 200Mbps throughput drop" + }, + "relationships": { + "Stadium_Concert_2025 -TRIGGER_OPTIMIZATION→ Slice_22", + "Stadium_Concert_2025 -IMPACT→ latency ", + "latency -REQUIRE_ACTION→ Resource_Boost_20", + "Resource_Boost_20 -TARGET→ RAN_Cluster_5", + "Resource_Boost_20 -TARGET→ Core_Node_7", + } +} + +Example knowledge graph 2 (2024 Olympic Opening Ceremony): +{ + "entities": { + "event": "Olympics_Opening_2024", + "eventType": "Global_Sporting", + "location": "Stadium_Cell_#5", + "attendance": 80000, + "date": "2024-07-26", + "networkSlice": "URLLC_Streaming (Ultra_Reliable_Low_Latency)", + "infrastructure_resource": "Core_Node_Alpha", + "optimizationAction": "CoreNode_Scaling (Horizontal_Scaling, scale factor 3.5)", + "trafficForecast": "70% increase (forecasted on 2024-06-15, 85% confidence)", + "SLAImpact": "Projected 8ms latency (mitigation: Traffic_Rerouting)" + }, + "relationships": { + "Olympics_Opening_2024 -TRIGGER_OPTIMIZATION→ URLLC_Streaming", + "Olympics_Opening_2024 -IMPACT→ latency", + "latency -REQUIRE_ACTION→ Traffic_Rerouting", + "CoreNode_Scaling -TARGET→ Core_Node_Alpha", + "URLLC_Streaming -ASSOCIATED_WITH→ Core_Node_Alpha" + } +} + +``` + +} +} + +#### 2) **Ontology alignment** + +Based on the unified ontology framework (covering classes like public events, network slices, infrastructure resources, etc.), terminology and attribute standards across the two knowledge graphs are unified. + +#### 3) **Entity, attribute and relationship alignment** + +Entity alignment: Align "Stadium\_Cell\_#5" as the same geographical entity. Link infrastructure entities (e.g., "Core\_Node\_7" and "Core\_Node\_Alpha") as "co-located resources" via spatial proximity (<1km from the location). Associate the two events as "same-venue large-scale events" (shared attendance/location). + +Attribute alignment: Standardize formats (e.g., "date" as "YYYY-MM-DD"). + +Relationship alignment: Establish "located\_at" for both events with the shared location. Create cross-event relationships (e.g., "shares\_location", "shares\_attendance\_scale"). + +### Step 5: **Knowledge reasoning** + +#### 1) **Entity and relationship completion** + +Infer optimization rules: If Event\_Attendance > 50K and Historical\_Traffic\_Spike > 30% → recommend "Pre-Scale Slice\_Resources\_by\_40%". + +#### 2) **Entity and relationship correction** + +Detect over-provisioning: Flag unnecessary scaling actions if predicted attendance drops by 50%. + +### Step 6: **Knowledge validation** + +#### 1) **Define evaluation objectives** + +Ensure the fused knowledge graph can produce reliable reasoning outputs. + +#### 2) **Establish validation criteria** + +Metrics: SLA compliance rate during events (≥ 99.9%), prediction accuracy (mean absolute percentage error < 10%). + +#### 3) **Prepare evaluation tools and methods** + +SPARQL queries: Used to test reasoning rules, such as automatically generating recommended optimization actions for high-risk events (e.g., recommending "Pre-Scale Slice\_Resources\_by\_40%" for events with over 50,000 attendees and historical traffic spikes exceeding 30%). + +Python validation scripts: Leverage libraries like rdflib for knowledge graph traversal, pandas for SLA log analysis, and scikit-learn for mean absolute percentage error calculation. + +SLA compliance simulator: Conduct time-series comparisons of predicted and actual KPIs using historical event data to verify SLA compliance. + +#### 4) **Data collection** + +Extract data samples from the constructed graphs covering all key entities and relationships. + +#### 5) **Execute evaluation** + +In accordance with the predetermined validation criteria, systematically inspect each entity and relationship. + +Consistency check: Run SPARQL queries to detect conflicting actions (e.g., an event requiring two different optimization actions) by querying events associated with multiple distinct actions. + +Accuracy validation: Calculate mean absolute percentage error for forecasts (e.g., the 2024 Olympics traffic spike forecast, with an actual spike of 68% and a predicted spike of 70%, resulting in a mean absolute percentage error of 2.94% which meets the < 10% criterion). + +Timeliness stress test: Inject 10 concurrent event alerts and measure the latency of the reasoning engine to assess its responsiveness. + +| | | +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

6) Analyse result
Based on the evaluation findings, generate an observable dashboard to display key metrics. Provide targeted improvement suggestions, such as implementing geospatial alignment rules for multi-venue events to enhance spatial association accuracy.

Step 7: Knowledge graph storage

1) Storage design
Select Amazon Neptune with temporal graph extensions to track event-driven changes.

2) Graph data loading
The graph data loading step implements bulk import operations and creates necessary indices for efficient querying.

3) Maintenance and update
Perform regular data freshness checks and performance optimization. Integrate with orchestration tools (e.g., Kubernetes) for slice reconfiguration.

Step 8: Knowledge service
This step provides knowledge services based on the proactive network optimisation constructed knowledge graph.

Dynamic slice scaling: Auto-allocate additional physical resource blocks (PRBs) or virtual network function (VNF) instances pre-event.

Traffic rerouting: Shift non-critical traffic to underutilized nodes during peak loads.

| +|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# Bibliography + +- [b-ITU-T Y.4500.12] Recommendation ITU-T Y.4500.12 (2018), *oneM2M base ontology*. +- [b-ETSI GR ENI 031] ETSI GR ENI 031 (2024), *Experiential Networked Intelligence (ENI); Construction and application of fault maintenance network knowledge graphs*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3361-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3361-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..254f166a79bbae0f895e4c4c2663318e6f9181a7 --- /dev/null +++ b/marked/M/T-REC-M.3361-201101-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41f627022c4be40893d34139af3e39b677ffa4806a0b81696ecb365a700cd741 +size 6650 diff --git a/marked/M/T-REC-M.3361-201101-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/M/T-REC-M.3361-201101-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b04db9f8c1af5b727e68e6393ecc842e82a2fd3c --- /dev/null +++ b/marked/M/T-REC-M.3361-201101-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5e8dae7140c13dde89ff9dd00e68be49ff50fc7fbac0c6e09fa0b8018b60713 +size 186138 diff --git a/marked/M/T-REC-M.3361-201101-I_PDF-E/raw.md b/marked/M/T-REC-M.3361-201101-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cf15fa65ccd10eec1e314a162993c3f1f94f6c97 --- /dev/null +++ b/marked/M/T-REC-M.3361-201101-I_PDF-E/raw.md @@ -0,0 +1,343 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3361** + +(01/2011) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +# --- **Requirements for business-to-government management interfaces – B2G interfaces – Introduction** + +Recommendation ITU-T M.3361 + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a stylized globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +## ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T M.3361** + +## **Requirements for business-to-government management interfaces – B2G interfaces – Introduction** + +## **Summary** + +Recommendation ITU-T M.3361 introduces the specification for high level requirements of business-to-government (B2G) management interfaces, including its general requirements, specific requirements, as well as security requirements. This Recommendation also defines the concept of B2G management interfaces and its relationship with existing business-to-business and customer-to-business management interfaces (B2B and C2B) Recommendations. + +The B2G management interface has additional requirements to those of B2B/C2B interfaces, which has impacts on the activities of both the service provider/network operator (SP/NO) as well as on the National Administrations/Government (G) activities. + +The interactions between SP/NO and G entities are addressed in clauses 6 to 9. B2B and C2B interface specifications will be reused in the development of the B2G management interface. + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3361 | 2011-01-13 | 2 | + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2011 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Background..... | 2 | +| 6 Content, scope, and type of information to be exchanged through the B2G interface ..... | 3 | +| 7 B2G interface requirements ..... | 3 | +| 8 Guidelines to elaborate a roadmap for the reuse of existing ITU-T Recommendations: architecture, methodology, and security ..... | 4 | +| 8.1 Relationship with other ITU-T Recommendations ..... | 4 | +| 8.2 Candidate ITU-T Recommendations to be reused in order to meet B2G interface requirements ..... | 4 | +| 9 Potential changes, enhancements or revisions on the business processes described in ITU-T M.3050 series and other related ITU-T Recommendations ..... | 4 | +| Appendix I – B2G chart..... | 5 | + + + +## Recommendation ITU-T M.3361 + +## Requirements for business-to-government management interfaces – B2G interfaces – Introduction + +## 1 Scope + +The scope of this Recommendation aims to introduce the high level requirements of the business-to-government management interfaces – B2G interfaces. It gives an overview of the B2G interface including objectives and goals to be achieved, the content, scope and information to be exchanged across the B2G interface. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3016.1] Recommendation ITU-T M.3016.1 (2005), *Security for the management plane: Security requirements*. +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2007), *Management interface specification methodology*. +- [ITU-T M.3050.0] Recommendation ITU-T M.3050.0 (2007), *Enhanced Telecom Operations Map (eTOM) – Introduction*. +- [ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. +- [ITU-T M.3050.2] Recommendation ITU-T M.3050.2 (2007), *Enhanced Telecom Operations Map (eTOM) – Process decompositions and descriptions*. +- [ITU-T M.3190] Recommendation ITU-T M.3190 (2008), *Shared information and data model (SID)*. +- [ITU-T M.3200] Recommendation ITU-T M.3200 (1997), *TMN management services and telecommunications managed areas: Overview*. +- [ITU-T M.3320] Recommendation ITU-T M.3320 (1997), *Management requirements framework for the TMN X-Interface*. +- [ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*. +- [ITU-T X.805] Recommendation ITU-T X.805 (2003), *Security architecture for systems providing end-to-end communications*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +3.1.1 **enterprise:** [ITU-T M.3050.1]. + +3.1.2 **enterprise management process area:** [ITU-T M.3050.1]. + +3.1.3 **entity:** [ITU-T M.3050.1]. + +3.1.4 **eTOM:** [ITU-T M.3050.0]. + +3.1.5 **process:** [ITU-T M.3050.1]. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +3.2.1 **B2G interface:** The business-to-government (B2G) interface (or B2G management interface) is the interface where government entities or a National Administration can interact with service providers/network operators (SP/NO) and other regulated entities to exchange information to support regulatory processes. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +G Government entity and National Administration + +GUI Graphic User Interface + +KPI Key Performance Indicator + +KQI Key Quality Indicator + +NO Network Operator + +SC Service Customer + +SP Service Provider + +## 5 Background + +Traditionally, relationships between government entities or a National Administration (G) and SP/NO have been made under manual processes or, alternatively, some mechanized means or a mixture of two types. + +B2G interfaces were not standardized or modernized to meet government/National Administration and business entities processes requirements to cover service licensing authorization, key performance indicator (KPI), key quality indicator (KQI), surveillance methods and regulatory requirements. + +Service providers and network operators face very different regulatory environments in different countries and sometimes within a particular country, when exchanging information with national administrations. Diverse paper form (non-mechanized processes) and graphic user interface (GUI) processes between G and SP/NO frequently become a significant financial burden to both parties. + +To illustrate the scenario in the previous paragraph, some SPs/NOs deal with requests for licensing in paper forms, and fill in forms of telecom taxes and fees. Others process the notification of fines and other penalties. On the other hand, Government entities are interested to issue licences more + +quickly to meet the needs of a broader number of telecom SPs/NOs. Those tasks are ordinarily time- and cost-consuming because of their semi-mechanized or fully-manual activities. + +Concerning this limitation imposed by the present communication structure, it is important to note that: + +- SPs/NOs and a National Administration are deeply dependent upon effective management of information and communications in their regulatory processes; +- the adoption of an automated communication structure by SPs/NOs and a National Administration based on a standardized framework will smooth the planning, implementation and provision of services processes and ease the government regulatory processes. + +For the reasons cited above, a B2G interface standard has an enormous potential to improve the quality of a communication process between national administrations and SPs/NOs. + +Therefore, it is vital to create a technical standard to meet the various communication requirements between the National Administrations/Governments and SPs/NOs. + +This Recommendation introduces the high level requirements for B2G interfaces, mainly by the reuse of B2B and C2B interface specifications. + +## **6 Content, scope, and type of information to be exchanged through the B2G interface** + +The information to be exchanged in the B2G interface is strongly dependent on the businesses as well as on the government processes requirements. + +For the purpose of this Recommendation, five categories of information are expected to be exchanged over the B2G interface: licensing, taxation, financial, service quality, and infrastructure as well as other regulatory issues. + +Even though security requirements shall be treated when defining B2G interface security requirements to support the interconnection needs of the B2G interfaces, as stated in clause 8, it is important to emphasize that security has to be approached in two ways. Primarily, security is seen as a generic requirement; in this sense, it is useful to refer to [ITU-T M.3016.1] and [ITU-T X.805]. Alternatively, security might be considered as a specific requirement in the same level of abstraction of: licensing, taxation, financial, service quality, and infrastructure as well as other regulatory issues. + +## **7 B2G interface requirements** + +B2G interface requirements refer to [ITU-T M.3320], i.e., functional, service and network-level requirements for the exchange of information between G and "SP/NO and other regulated entities". + +The government processes requirements are mandatory for the National Administration's activities that necessarily involve interactions with SPs/NOs. + +The SP/NO requirements must be defined in order to satisfy their processing needs related to the interactions with G. + +The list below, though not exhaustive, includes the essential requirements for the B2G management interface: + +- management framework and architecture requirements for B2G management interfaces; +- application specific requirements for B2G management interfaces; +- B2G interface security requirements to support the interconnection needs of the SPs/NOs to G interfaces; +- generic management requirements for licensing management across the B2G interface; + +- generic management requirements for taxation management across the B2G interface; +- generic management requirements for financial management across the B2G interface; +- generic management requirements for service quality management across the B2G interface; +- generic management requirements for infrastructure management across the B2G interface; +- generic management requirements for regulatory issues management across the B2G interface. + +## **8 Guidelines to elaborate a roadmap for the reuse of existing ITU-T Recommendations: architecture, methodology, and security** + +As the intent is to reuse and build on previous work, it is fundamental to design a roadmap for utilizing existing ITU-T Recommendations. This roadmap has to be understood as an auxiliary tool to optimize the implementation of B2G management interface specifications. Prior to this design, there should be an objective analysis, which takes into consideration mandatory requirements to be met. + +The drivers to select existing ITU-T Recommendations for useful reuse are, among others, in principle, the requirements cited above in clause 7. + +The roadmap itself shall be elaborated in order to meet B2G requirements. In this sense, for each requirement, it is useful to elaborate its associated ITU-T Recommendation. + +### **8.1 Relationship with other ITU-T Recommendations** + +#### **8.1.1 Relationship with [ITU-T M.3020]** + +To be aligned with the management interface development specification methodology described in [ITU-T M.3020], B2G management interface development has to adopt the three-phase process: requirements, analysis and design. + +#### **8.1.2 Relationship with [ITU-T M.3190] (SID)** + +To elaborate an implementation-independent specification for B2G management interface, a conceptual information model is required, which calls for ITU-T M.3190 shared information and data model, or an alternative industry standard information model. + +## **8.2 Candidate ITU-T Recommendations to be reused in order to meet B2G interface requirements** + +The following ITU-T Recommendations can be quoted in advance as candidates: [ITU-T M.3050] series, [ITU-T M.3010], [ITU-T M.3020], [ITU-T M.3200], [ITU-T M.3400], and [ITU-T M.3190]. + +The roadmap of reuse shall be derived from the definition of B2G interface requirements. + +## **9 Potential changes, enhancements or revisions on the business processes described in ITU-T M.3050 series and other related ITU-T Recommendations** + +According to [ITU-T M.3050.1], "The eTOM is a business process framework, or a reference framework or model for categorizing all the business activities that a service provider will use". It is also stated, "A business process framework is one part of the strategic business model and plan for a service provider". + +The enterprise management process area of the eTOM is likely to require updating, and in particular the "Stakeholder and external relations management" process needs modifications as of the B2G emergence. The reason for this is the necessity to specify the regulator, operators and other regulated entities' relationship in their communication processes. + +## Appendix I + +## B2G chart + +(This appendix does not form an integral part of this Recommendation) + +The purpose of this appendix is to present the main ideas of this Recommendation in a graphical form. + +![B2G chart flowchart showing the relationship between content definition, interface requirements, reuse roadmap, and specific management requirements.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` +graph TD; 1[Definition of content, scope, and type of information to be exchanged through the B2G interface. 1] --> 2[Definition of B2G interface requirements 2]; 2 --> 3[Roadmap for the reuse of existing ITU-T Recommendations 3]; 3 --> 4[Definition of requirements: - Management framework and architecture requirements for B2G management interfaces; - Application specific requirements for B2G management interfaces; - B2G interface security requirements to support the interconnection needs of the SP/NO to G interfaces; - Generic management requirements for licensing management across the B2G interface; - Generic management requirements for taxation management across the B2G interface; - Generic management requirements for financial management across the B2G interface; - Generic management requirements for service quality management across the B2G interface; - Generic management requirements for infrastructure management across the B2G interface; - Generic management requirements for regulatory issues management across the B2G interface. 4]; 4 --> 5[Potential changes in ITU-T M.3050 and other related ITU-T Recommendations 5]; 4 --> 6[Future ITU-T Recommendations to meet B2G interface requirements 6]; +``` + +Definition of content, scope, and type of information to be exchanged through the B2G interface. 1 + +Definition of B2G interface requirements 2 + +Roadmap for the reuse of existing ITU-T Recommendations 3 + +Definition of requirements: + +- Management framework and architecture requirements for B2G management interfaces; +- Application specific requirements for B2G management interfaces; +- B2G interface security requirements to support the interconnection needs of the SP/NO to G interfaces; +- Generic management requirements for licensing management across the B2G interface; +- Generic management requirements for taxation management across the B2G interface; +- Generic management requirements for financial management across the B2G interface; +- Generic management requirements for service quality management across the B2G interface; +- Generic management requirements for infrastructure management across the B2G interface; +- Generic management requirements for regulatory issues management across the B2G interface. + +4 + +Potential changes in ITU-T M.3050 and other related ITU-T Recommendations 5 + +Future ITU-T Recommendations to meet B2G interface requirements 6 + +B2G chart flowchart showing the relationship between content definition, interface requirements, reuse roadmap, and specific management requirements. + +Figure I.1 – B2G chart + +Block 1 defines the information to be exchanged in the B2G interface. It provides the basis for Block 2. + +Block 2 specifies requirements: functional, service and network-level requirements for the exchange of information between government entities or a National Administration with operators and other regulated entities. It provides the basis for Block 3. + +Block 3 specifies the roadmap for the reuse of existing ITU-T Recommendations. It provides the basis for Block 4. + +Block 4 specifies B2G interface requirements. It provides the basis for Block 5 and Block 6. + +Block 5 specifies the potential changes in [ITU-T M.3050] and other related ITU-T Recommendations. + +Block 6 specifies future ITU-T Recommendations to meet B2G interface requirements. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3364-202002-I_PDF-E/raw.md b/marked/M/T-REC-M.3364-202002-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..314ecf674307cedee161c07275689dcf67996a65 --- /dev/null +++ b/marked/M/T-REC-M.3364-202002-I_PDF-E/raw.md @@ -0,0 +1,439 @@ + + +International Telecommunication Union + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3364** + +(02/2020) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Requirements for on-site telecommunication +smart maintenance management function** + +Recommendation ITU-T M.3364 + +ITU-T + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'.](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "ITU" is written in a large, bold, blue font, and below it, "International Telecommunication Union" is written in a smaller, blue font. + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'. + +# ITU-T M-SERIES RECOMMENDATIONS + +# TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T M.3364 + +## Requirements for on-site telecommunication smart maintenance management function + +## Summary + +Recommendation ITU-T M.3364 introduces requirements for on-site telecommunication smart maintenance management function. In this Recommendation, the requirements for telecommunication smart maintenance function are provided, which include on-site patrol, on-site overhaul, on-site troubleshooting, evaluation of maintenance work, management of maintenance knowledge base, management of service activation function, management of network resource, and management of smart maintenance assistant toolkit (SMAT). This Recommendation also provides use cases of SMAT in telecommunication smart maintenance system (TSMS). + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.3364 | 2020-02-13 | 2 | 11.1002/1000/14183 | + +## Keywords + +Function requirements, telecommunication smart maintenance. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2020 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------------|------| +| 1 Scope..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Convention..... | 2 | +| 6 Overview..... | 2 | +| 7 Requirements for telecommunication smart maintenance function ..... | 3 | +| 7.1 Requirements for on-site patrol ..... | 3 | +| 7.2 Requirements for on-site overhaul ..... | 4 | +| 7.3 Requirements for on-site troubleshooting ..... | 4 | +| 7.4 Requirements for evaluation of maintenance work..... | 5 | +| 7.5 Requirements for management of maintenance knowledge base..... | 6 | +| 7.6 Requirements for management of service activation function ..... | 6 | +| 7.7 Requirements for network resource management ..... | 7 | +| 7.8 Requirements for management of SMAT ..... | 7 | +| Appendix I – Use cases of SMAT in TSMS ..... | 8 | + + + +# Requirements for on-site telecommunication smart maintenance management function + +# 1 Scope + +This Recommendation proposes requirements for on-site telecommunication smart maintenance management function, which include on-site patrol, on-site overhaul, on-site troubleshooting, evaluation of maintenance work, management of maintenance knowledge base, management of service activation function, management of network resource, management of smart maintenance assistant toolkit (SMAT). This Recommendation also applies to the design and development of on-site telecommunications smart maintenance system. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3040] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 telecommunication smart maintenance** [ITU-T M.3040]: The maintenance carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system, which can provide strong human-computer interaction capabilities and online guidance to personnels, to achieve higher efficiency and precision of actions. + +**3.1.2 on-site overhaul** [ITU-T M.3040]: A kind of on-demand preventive maintenance performed at a facility site in the condition of natural disasters or major events. + +**3.1.3 on-site patrol** [ITU-T M.3040]: A kind of routine preventive maintenance periodically performed at a facility site. + +**3.1.4 on-site troubleshooting** [ITU-T M.3040]: A kind of corrective maintenance performed at a facility site when the quality of equipment degrades. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 maintenance executor**: A drone, or an intelligent maintenance robot, or a maintenance personnel equipped with a wearable device, to carry out maintenance tasks. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------------------------| +| AI | Artificial Intelligence | +| AR | Augmented Reality | +| IoT | Internet of Things | +| NEF | Network Element Function | +| OSF | Operations Systems Function | +| RFID | Radio Frequency Identification | +| SMAT | Smart Maintenance Assistant Toolkit | +| SMATF | Smart Maintenance Assistant Toolkit Function | +| TMN | Telecommunication Management Network | +| TSMS | Telecommunication Smart Maintenance System | +| TSMSF | Telecommunication Smart Maintenance System Function | + +# 5 Convention + +None. + +# 6 Overview + +The telecommunication smart maintenance system (TSMS) shall realize intelligent monitoring of the maintenance site, support the general flow of intelligent maintenance of the telecommunication network and elements, and improve the operational level of on-site maintenance executors. + +This Recommendation presents management function requirements for on-site telecommunication smart maintenance. The purpose is to apply smart wearable device, drone or intelligent maintenance robot, which is a combination of Internet of things (IoT) and augmented reality (AR), in the maintenance of communication network equipment and lines. + +The functional architecture of telecommunication smart maintenance is defined in [ITU-T M.3040] as shown in Figure 1. + +![Functional architecture diagram of on-site telecommunication smart maintenance. The diagram shows four main components: Maintenance personnel (represented by an icon), SMATF, TSMSF, and OSF. SMATF, TSMSF, and OSF are grouped under 'Smart maintenance'. SMATF is connected to Maintenance personnel via interface 'g'. SMATF is connected to TSMSF via interface 'f'. TSMSF is connected to OSF via interface 'q'. SMATF is also connected to NEF via interface 'q'. OSF is connected to NEF via interface 'q'. NEF is connected to TMN via interface 'q'. The diagram is labeled M.3364(20)_F01.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph LR + subgraph Smart_maintenance [Smart maintenance] + SMATF[SMATF] -- f --> TSMSF[TSMSF] + TSMSF -- q --> OSF[OSF] + SMATF -- q --> NEF[NEF] + OSF -- q --> NEF + end + Maintenance_personnel[Maintenance personnel] -- g --> SMATF + NEF -- q --> TMN[TMN] + style Maintenance_personnel image + +``` + +Functional architecture diagram of on-site telecommunication smart maintenance. The diagram shows four main components: Maintenance personnel (represented by an icon), SMATF, TSMSF, and OSF. SMATF, TSMSF, and OSF are grouped under 'Smart maintenance'. SMATF is connected to Maintenance personnel via interface 'g'. SMATF is connected to TSMSF via interface 'f'. TSMSF is connected to OSF via interface 'q'. SMATF is also connected to NEF via interface 'q'. OSF is connected to NEF via interface 'q'. NEF is connected to TMN via interface 'q'. The diagram is labeled M.3364(20)\_F01. + +**Figure 1 – Functional architecture of on-site telecommunication smart maintenance [ITU-T M.3040]** + +This Recommendation gives a detailed description of the specific functional requirements of telecommunication smart maintenance system function (TSMSF) in Figure 1. + +# 7 Requirements for telecommunication smart maintenance function + +The telecommunication smart maintenance function consists of two parts: the application part and the resource data part. + +The application part includes on-site patrol, on-site overhaul, on-site troubleshooting, maintenance work evaluation, management of maintenance knowledge base and service activation. + +The resource data part collects and stores the information about communication network resource and maintenance assistant toolkit resource, and provides data support for the application part. + +## 7.1 Requirements for on-site patrol + +### 7.1.1 Requirements for patrol task management + +TSMS is recommended to support the addition, deletion, modification, investigation, and graphic presentation of combined spatial coordinates information. Information related to the patrol work task can be retrieved and combined with the resource list. The chronologically reversed sequence list shows the current day's patrol work tasks in the system, as well as details of these work tasks, including real-time status, completion status, and data list to be collected. + +Before performing the patrol work task, it is necessary to ensure the safety of the patrol environment, the relevant qualifications of the operators, and the integrity of the patrol device. + +### 7.1.2 Requirements for patrol route design + +The patrol route consists of several patrol points in series. Based on the selected spatial coordinates and order of the patrol points, TSMS is recommended to generate patrol routes intelligently by using satellite navigation positioning and satellite navigation technology. For example, during a patrol process based on a wearable device, TSMS sends graphical patrol routes, directions and patrol points to the wearable device in conjunction with the patrol site plan. Also, TSMS could monitor the patrol route of the drone or the intelligent maintenance robot in real time during a patrol process based on a drone or an intelligent maintenance robot. + +### **7.1.3 Requirements for generation of smart identification data related to patrol object** + +According to the patrol route and the designed checkpoints, smart identification data related to patrol object, such as a virtual resource view and an operation panel map that can present the maintained resource in the wearable device, is generated and downloaded in advance to SMAT. In this way, during the patrol process, the smart identification data in SMAT can increase the recognition efficiency as long as there is pre-stored smart identification data related to the object to be patrolled. + +### **7.1.4 Requirements for report of patrol record** + +TSMS is recommended to provide the function of returning the scene image and video data to support on-site abnormal situation reporting and trouble reporting. + +### **7.1.5 Requirements for supervision of patrol** + +TSMS is recommended to provide surveillance functions based on satellite navigation, radio frequency identification (RFID), two-dimensional code that gives the location of the SMAT and the maintained resource object. It can supervise whether the SMAT carries out patrol work according to the planned patrol procedures and patrol object or not. + +## **7.2 Requirements for on-site overhaul** + +### **7.2.1 Requirements for management of maintenance job** + +TSMS is recommended to support the addition, deletion, modification, and search of the maintenance job. During an overhaul process based on a wearable device, TSMS sends the resource object to be overhauled to SMAT with the panel image. TSMS present the details of the maintenance job combined with the resource list, including real-time status and maintenance record. + +### **7.2.2 Requirements for push of guidance information** + +TSMS is recommended to push the guidance to SMAT according to the information returned from the overhaul site. For example, during a overhaul process based on a wearable device, according to the actual execution situation of the on-site maintenance executor at the overhaul site, the steps to be performed and the objects to be overhauled, TSMS obtains the maintenance data and steps information related to the work task list and pushes them to the SMAT. The AR-based information enhancement technology is integrated with the actual scene to provide real-time operational training guidance in the wearable device through animation, voice and text. + +### **7.2.3 Requirements for record of overhaul process** + +SMAT is recommended to support detailed record of the overhaul operation process and return the overhaul record to TSMS. TSMS is recommended to provide standardized operation comparison technology, complete the determination of whether the maintenance job content is correct, and notify the on-site maintenance executor of the judgment result in order to undertake smart maintenance. + +### **7.2.4 Requirements for remote assistance** + +TSMS is recommended to provide a video conference channel between SMAT and experts. Experts can remotely view the overhaul objects through video and provide overhaul guidance. + +## **7.3 Requirements for on-site troubleshooting** + +### **7.3.1 Requirements for trouble management** + +TSMS is recommended to support trouble management functions. Trouble management includes trouble information collection, trouble information display, trouble confirmation and clearing, and trouble query and statistics. + +TSMS is recommended to support real-time monitoring of the operational status of resources such as telecommunication infrastructure, applications and SMAT. The trouble information is presented in + +the form of a list, a view, a color, etc., and the relevant maintenance executors are notified in time by means of mail, short message and banner. + +TSMS is recommended to provide the function of trouble confirmation and clearing. + +TSMS is recommended to provide trouble query function. Users can specify the query conditions to query the trouble information. The query conditions include the trouble object, the time range, the trouble cause, the trouble severity, the alarm type, whether the trouble is acknowledged, and whether the trouble is cleared. + +TSMS is recommended to support trouble statistics. It can classify and compare trouble according to the trouble object, type, level, time, and cause in the form of reports, graphs, and so on. + +### **7.3.2 Requirements for trouble analysis** + +TSMS is recommended to support the analysis of the trouble based on the information such as network resource object, location, time, service, trouble type, content, etc. For example, during a maintenance process based on a wearable device, TSMS is recommended to simultaneously display the trouble location in the wearable device panel with the virtual resource view. A list of possible trouble causes will be given. + +### **7.3.3 Operational guidance push combined with trouble phenomenon** + +TSMS is recommended to push operation guidance in conjunction with the trouble phenomenon. Combined with the maintenance knowledge base, TSMS is recommended to automatically identify troubles, obtain corresponding knowledge and provide a trouble solution, process flow or play the troubleshooting operation instruction video. + +### **7.3.4 Requirements for remote assistance** + +TSMS is recommended to match experts according to the type of trouble. On-site maintenance executors can use dial-up video conferencing with remote experts to communicate through text, pictures and video, and return the on-site information to remote experts in the form of text, pictures, video, etc. A number of experts can be accessed at the same time for failure consultation. + +### **7.3.5 Requirements for update maintenance knowledge base** + +If a trouble is solved according to the existing knowledge information, TSMS is recommended to submit the trouble-related information to update the maintenance knowledge base and establish a reference relationship between the knowledge and the trouble. + +## **7.4 Requirements for evaluation of maintenance work** + +### **7.4.1 Requirements for management of evaluation criteria** + +According to the evaluation requirements, TSMS is recommended to establish a dynamic assessment baseline for the intelligent maintenance work quality of telecommunication. TSMS is recommended to provide management functions for the evaluation criteria of intelligent maintenance work, including the addition, deletion, modification and research of evaluation criteria. + +### **7.4.2 Requirements for collection of record** + +TSMS is recommended to use SMAT for intelligent acquisition of on-site maintenance operation data. SMAT automatically takes photos and record data according to the progress of the work, and upload them to TSMS. + +### **7.4.3 Requirements for management of evaluation report** + +TSMS is recommended to evaluate the quality of telecommunication smart maintenance work according to the evaluation criteria. The evaluation includes star rating and explanation information. + +TSMS is recommended to generate evaluation reports based on the quality evaluation results of the maintenance work. TSMS is recommended to support the addition, deletion, modification, query and batch operation of evaluation reports. + +## **7.5 Requirements for management of maintenance knowledge base** + +### **7.5.1 Requirements for collection of maintenance record** + +TSMS is recommended to collect the maintenance records submitted by SMAT. The content includes text, pictures, videos, and voice information. TSMS provides a variety of maintenance record collection methods such as collection from external files, web pages, automatic generation and manual entry, and then stores them in the database according to a predefined classification. + +### **7.5.2 Requirements for evaluation and generation of maintenance knowledge** + +TSMS is recommended to combine data mining, machine learning and other big data processing techniques to analyze and evaluate maintenance work records, form useful maintenance knowledge, and use it for subsequent maintenance jobs, such as smart matching of maintenance instruction videos and smart push of maintenance jobs, etc. + +### **7.5.3 Requirements for updating maintenance knowledge base** + +TSMS is recommended to support the update of maintenance knowledge base. TSMS performs routine maintenance of maintenance knowledge records in the knowledge base, and evaluates maintenance knowledge by counting usage. TSMS updates the knowledge in the knowledge base according to the evaluation results. + +### **7.5.4 Requirements for use of maintenance knowledge base** + +TSMS is recommended to automatically select the appropriate knowledge based on certain reasoning principles. During work task execution process, if on-site training function is performed, TSMS automatically performs knowledge search and query pre-processing and provides applicable knowledge for training. + +## **7.6 Requirements for management of service activation function** + +### **7.6.1 Download of new service activation job** + +TSMS is recommended to provide the function of downloading an order related to service activation work task. On-site maintenance executors obtain the service activation work task list from the TSMS, and receive the service activation work task according to their own service duty and scope of responsibility. + +### **7.6.2 Service activation** + +The on-site maintenance executors are recommended to perform service activation tasks sent by TSMS, such as gateway installation and configuration, take photos automatically according to the work schedule. + +### **7.6.3 Upload service activation record** + +TSMS is recommended to provide the function of service activation. During and after the execution of service activation work task, on-site maintenance executors feedback the execution of the on-site work tasks and upload information, such as the photos of the on-site resource tables to be constructed, through SMAT to provide a record of the execution of the on-site service activation work tasks to TSMS. + +## **7.7 Requirements for network resource management** + +The objects of network resource management include resources that can be maintained with the aid of intelligent means in various types of communication networks such as transport networks, mobile networks, and data networks. For example, the resource can be racks, boards, pipes, optical fibers and so on. Network resource management should provide the following functions that are outlined in clauses 7.7.1 to 7.7.2. + +### **7.7.1 Requirements for basic resource management** + +TSMS is recommended to support the addition, deletion, modification, search and batch of network resources information. For example, during the smart maintenance of communication networks based on wearable devices, TSMS is recommended to support AR modeling of resource objects, that is, the virtual resource view presented in the AR operation panel. It can be used to generate a virtual operation panel view corresponding to the real resource after the wearable device identifies the resource object. + +### **7.7.2 Requirements for position guidance** + +TSMS is recommended to assist SMAT to locate construction locations related to resources in the maintenance work task by the location information and spatial information, and prompt the best routes from the current positions to the construction locations. + +### **7.7.3 Requirements for resource smart identification** + +TSMS is recommended to support SMAT load the resource smart identification data, and obtain the detailed information of the resource by invoking the resource information interface provided by the system, including but not limited to the vendor information, history trouble, beared service, etc. + +### **7.7.4 Requirements for resource synchronization** + +TSMS is recommended to compare the image recognition results of the on-site network resource with the data stored in the system, and modify the system data according to the real on-site information to complete the whole lifetime management of the network resources in a smart way. + +## **7.8 Requirements for management of SMAT** + +### **7.8.1 Requirements for management of toolkit information** + +TSMS is recommended to support the addition, deletion, modification, query and batch information of SMAT. + +### **7.8.2 Requirements for management of toolkit status** + +TSMS is recommended to provide the function of managing the status of SMAT, which can show the list of displayed toolkits, current usage status and whether or not it is lost. TSMS can also provide information about requisition record, return record and upgrade record of SMAT. + +# Appendix I + +## Use cases of SMAT in TSMS + +(This appendix does not form an integral part of this Recommendation.) + +With the TMN management architecture as a guide, network management technology, products and applications have been rapidly developed, and a complete industrial chain has been established. However, due to insufficient development of technologies such as Internet of things (IoT) and artificial intelligence (AI), on-site maintenance work concerning non-intelligent parts (such as racks, boards, pipes, optical fibers, lines and other dummy resources) that constitute the network have required a large amount of manpower for a long period of time. It is hard to reach a closed-loop maintenance, and the low degree of intelligence level, resulting in the difficult to ensure the consistency and completeness of dummy resource information seriously affects the quality of network management. Therefore, using SMAT in telecommunication smart maintenance can complete on-site patrol, on-site overhaul, on-site troubleshooting effectively, and save time and manpower. At present, SMAT mainly includes wearable devices, drones and intelligent maintenance robots. The use cases of SMAT are shown below. + +Wearable devices can help telecommunication smart maintenance in on-site patrol, on-site overhaul, on-site troubleshooting. For example, in the process of on-site patrol, TSMS will visually display the patrol route, direction and patrol points in the wearable device in a graphical way, so that the staff can conduct quick and efficient patrol. In the process of on-site overhaul, TSMS obtains the relevant maintenance data and operation steps according to the actual situation and operation objects, and send them to wearable devices. Based on AR technology, integrated with the actual scene, wearable devices can provide real-time operation training guidance through animation, voice, text and other forms. + +Drone is mainly used for on-site patrol in telecommunication smart maintenance, especially for communication tower and line network quality. As shown in Figure I.1, during the patrol of communication tower, the drone can carry a variety of sensors (including but not limited to visible light sensor, infrared sensor, laser rangefinder and laser radar). After receiving the patrol task, the drone will hover to inspect the corresponding communication tower, detect whether the temperature, light and other indicators around the tower are normal or not, and upload the data to TSMS. Besides, in the line network quality patrol, the drone carries the mobile communication network test instrument (including but not limited to spectrum instrument, DT test instrument, etc.), the drone will hover to detect the line network quality, check whether there is any problem in the line, and upload the patrol information to TSMS. + +![Diagram of Drone patrol interaction with TSMS](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram illustrates the interaction between a drone and a telecommunication smart maintenance system (TSMS). On the left, a box labeled 'Drone patrol' contains icons of a communication tower and a drone. On the right, a box is labeled 'Telecommunication smart maintenance system'. Two arrows connect them: a top arrow pointing from the system to the drone labeled 'Download patrol task', and a bottom arrow pointing from the drone to the system labeled 'Report patrol information'. + +Diagram of Drone patrol interaction with TSMS + +M.3364(20)\_FI.1 + +Figure I.1 – Drone patrol + +The intelligent maintenance robot is also mainly used for on-site patrol in telecommunication smart maintenance, mainly for the patrol of indoor communication equipment, power environment and outdoor communication infrastructure. As shown in Figure I.2, during the patrol, the intelligent maintenance robot downloads the patrol task from TSMS. The intelligent maintenance robot can integrate infrared, visual, sound and other multi-functional sensors, use the autonomous navigation and positioning function to follow the patrol route, and use visible image analysis, infrared temperature measurement and other technologies to carry out the intelligent identification of resource defects and temperature measurement of infrared area. Then, the intelligent maintenance robot reports the patrol information to the smart maintenance system. + +![Diagram of intelligent maintenance robot patrol showing interaction between the robot and the telecommunication smart maintenance system.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg) + +The diagram illustrates the interaction between an intelligent maintenance robot and a telecommunication smart maintenance system. On the left, a box titled "Intelligent maintenance robot patrol" contains a cloud icon and a stack of server racks. A small robot is shown next to the racks. On the right, a box is labeled "Telecommunication smart maintenance system". Two arrows connect the robot to the system: an arrow pointing from the system to the robot labeled "Download patrol task", and an arrow pointing from the robot to the system labeled "Report patrol information". Below the right box, the text "M.3364(20)\_FI.2" is present. + +Diagram of intelligent maintenance robot patrol showing interaction between the robot and the telecommunication smart maintenance system. + +**Figure I.2 – Intelligent maintenance robot patrol** + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3367-202304-I_PDF-E/raw.md b/marked/M/T-REC-M.3367-202304-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..71099c50bde753ffd3c40b25e3072fccfbc4c258 --- /dev/null +++ b/marked/M/T-REC-M.3367-202304-I_PDF-E/raw.md @@ -0,0 +1,347 @@ + + +# Recommendation**ITU-T M.3367 (04/2023)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +# **Requirements for robot-based on-site smart patrol of telecommunication networks** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +### **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3367 + +## Requirements for robot-based on-site smart patrol of telecommunication networks + +## Summary + +Recommendation ITU-T M.3367 introduces requirements for intelligent maintenance robots (IMRs) based on-site smart patrol of telecommunication networks, includes the network elements to be patrolled, requirements for management function of IMR-based patrol and related management interfaces. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3367 | 2023-04-29 | 2 | 11.1002/1000/15515 | + +## Keywords + +Intelligent maintenance robot, IMR, robot, telecommunication smart maintenance. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview..... | 2 | +| 7 Requirements for IMR-based on-site smart patrol of telecommunication networks .... | 3 | +| 7.1 Framework of management function ..... | 3 | +| 7.2 Network elements to be patrolled..... | 3 | +| 7.3 Requirements for IMR-based on-site smart patrol ..... | 4 | +| 7.4 Requirements for management interface of IMR-based patrol ..... | 6 | +| Bibliography ..... | 7 | + + + +# Recommendation ITU-T M.3367 + +## Requirements for robot-based on-site smart patrol of telecommunication networks + +# 1 Scope + +This Recommendation proposes requirements for on-site smart patrol of telecommunication networks based on intelligent maintenance robots (IMRs), principally including the network elements to be patrolled, requirements for the management function of IMR-based patrols and related management interface technology to develop the IMR itself. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3040] Recommendation ITU-T M.3040 (2019), *Principles for on-site telecommunication smart maintenance*. + +[ITU-T M.3364] Recommendation ITU-T M.3364 (2020), *Requirements for on-site telecommunication smart maintenance management function*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 robot** [b-ISO 8373]: Programmed actuated mechanism with a degree of autonomy to perform locomotion, manipulation or positioning. + +**3.1.2 telecommunication smart maintenance** [ITU-T M.3040]: The maintenance carried out with advanced technology-based (IoT, AR, wearable technology, etc.) toolkit and system, which can provide strong human-computer interaction capabilities and online guidance to personnel, to achieve higher efficiency and precision of actions. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following term: + +**3.2.1 intelligent maintenance robot**: A kind of smart wearable maintenance assistant toolkit, a smart information collection device that integrates infrared, visual, sound and other multi-functional sensors, uses the autonomous navigation and positioning function to follow the patrol route, and uses visible image analysis, infrared temperature measurement and other technologies to carry out on-site patrol, information collection and dispatch of reports to a telecommunication smart maintenance system. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|--------------------------------------------| +| AR | Augmented Reality | +| GIS | Geographic Information System | +| IMR | Intelligent Maintenance Robot | +| IoT | Internet of Things | +| TSMS | Telecommunication Smart Maintenance System | + +# 5 Conventions + +In this Recommendation: + +The phrase "is required" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. + +The phrase "is recommended" indicates a requirement that is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The phrase "can optionally" indicates an optional requirement that is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Overview + +The telecommunications smart maintenance system shall realize intelligent support and monitoring of the maintenance site, support the general flow of intelligent maintenance of communication networks, and improve the operation level of on-site maintenance personnel and the management level of on-site maintenance operations as described in [ITU-T M.3040]. + +[ITU-T M.3364] focuses on requirements for on-site telecommunication smart maintenance management function, which includes on-site patrol, on-site overhaul, on-site troubleshooting, maintenance work evaluation, management of a maintenance knowledge base and service activation. [ITU-T M.3364] describes the complete set of maintenance management functions. This Recommendation focuses only on the on-site smart patrol part with the aid of a intelligent maintenance robot. + +This Recommendation presents requirements for IMR-based on-site smart patrol of telecommunication networks. This Recommendation describes the network elements to be patrolled, requirements for the management function of IMR-based patrol and related management interface technology. The purpose is to apply IMR-based smart patrol technology, which is a combination of Internet of things (IoT) and artificial intelligence technology, in the maintenance of communication network equipment and lines, in order to enhance the level of smart network maintenance. + +The overall architecture for the IMR-based on-site smart patrol part of telecommunication networks consists of a telecommunication smart maintenance system (TSMS), IMR-based smart patrol systems and patrol objects. As shown in Figure 1, with reference to [ITU-T M.3040], the TSMS implements some of the functions related to on-site smart patrol in the TSMS function. The IMR-based smart patrol systems are one specific scenario of the smart maintenance assistant toolkit function in the functional architecture of on-site telecommunication smart maintenance [ITU-T M.3040]. + +![Architecture for IMR-based on-site smart patrol of telecommunication networks diagram](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +This diagram illustrates the architecture for IMR-based on-site smart patrol of telecommunication networks. It consists of three main layers connected vertically. At the top is a box labeled 'TSMS'. Below it is a box labeled 'IMR-based smart patrol system', which contains two sub-boxes: 'Smart patrol software' and 'IMRs'. At the bottom is a box labeled 'Patrol objects'. The connections between the layers are marked with 'f' between TSMS and the IMR-based system, and 'q' between the IMR-based system and Patrol objects. The reference code 'M.3367(23)' is shown at the bottom right. + +Architecture for IMR-based on-site smart patrol of telecommunication networks diagram + +**Figure 1 – Architecture for IMR-based on-site smart patrol of telecommunication networks** + +# **7 Requirements for IMR-based on-site smart patrol of telecommunication networks** + +## **7.1 Framework of management function** + +The framework of a management function for IMR-based on-site smart patrol of telecommunication networks is shown in Figure 2. + +![Framework of management function diagram](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +This diagram shows the framework of management function, divided into two main sections by a dashed horizontal line. The top section, labeled 'TSMS', includes 'Resource management' and 'Patrol task management'. Below these are two columns: 'Route design and patrol process' (containing 'Patrol route design' and 'IMRs monitoring') and 'Patrol record and abnormal report' (containing 'Data integration' and 'Report generation'). The bottom section, labeled 'IMR-based smart patrol system', includes 'Autonomous guidance', 'Patrol route uploading', 'Patrol object inspection', 'Abnormal identification', and 'Patrol information uploading'. At the very bottom is a box labeled 'IMR control'. The reference code 'M.3367(23)' is shown at the bottom right. + +Framework of management function diagram + +**Figure 2 – Framework of management function** + +## **7.2 Network elements to be patrolled** + +The objects of IMR-based on-site smart patrol include resources that can be patrolled by aid of intelligent means in various types of communication networks, such as communication devices, power devices and conditions. Some examples of patrol objects and tasks are listed in Table 1. + +**Table 1 – Examples of patrol objects and tasks** + +| Patrol object | Patrol task | +|---------------------------------------------|----------------------------------------------------------------------------------| +| Equipment rack | Rack temperature | +| Cable | Equipment power line, optical cable | +| Network management and maintenance terminal | Equipment status and performance, current alarm, historical alarm | +| Communication power supply equipment | Power supply, battery pack | +| Communication line | Whether the identification is clear, whether the optical cable is well protected | + +## **7.3 Requirements for IMR-based on-site smart patrol** + +On-site patrol means that on-site patrol personnel or IMR who go to the job site, perform maintenance management functions, identify problems and solve problems in a timely manner. IMR-based on-site smart patrol of telecommunication networks is recommended to provide the subfunctions specified in clauses 7.3.1 to 7.3.5. + +### **7.3.1 Requirements for resource management** + +The TSMS should support resource management functions, mainly to complete the registration and viewing functions of IMRs and other facilities. There are requirements for the TSMS of resource management, which are as follows: + +- 1) the TSMS is required to provide addition, deletion, modification and checking of information in IMR-based smart patrol systems; +- 2) the TSMS is recommended to support the query and view of the current patrol tasks of the IMR-based smart patrol system; +- 3) the TSMS is recommended to view the name, logo, model and description of the IMRs and patrol objects during the patrol process. + +### **7.3.2 Requirements for patrol task management** + +A TSMS is recommended to support the addition, deletion, modification, investigation and graphic presentation of combined spatial coordinate information. With patrol task management, a TSMS is supposed to achieve the closed-loop accompaniment with feedback of rapid data collection, real-time information transmission, intelligent analysis and emergency decision-making. + +There are requirements for a TSMS for patrol task management, which are as follows. + +- 1) A TSMS is recommended to support centralized control and real-time visualization of all patrol points in the system. The TSMS can provide efficient information processing capabilities because of powerful computing resources. According to centralized control, the system is able to analyse and coordinate feedback data from distributed patrol points. +- 2) A TSMS is recommended to support the addition, deletion, modification and query of patrol tasks, as well as a graphic presentation combined with a geographic information system (GIS) and space. The information related to IMR-based patrol tasks can be retrieved through the resource list. The patrol tasks of the current day in the current system can be displayed in chronological and reverse order, as well as the detailed information of these tasks, including real-time status and patrol results. Through the GIS system, the information about the IMR-based patrol task in the selected geographical range can be retrieved. Relevant patrol tasks can be filtered and queried according to real-time status and early warning information. + +### **7.3.3 Requirements for route design and patrol process** + +There are requirements for the IMR-based smart patrol system of route design and patrol process, which are as follows. + +- 1) The IMR-based smart patrol system is required to provide the functions of autonomous guidance of patrol routes and obstacle detection. The IMR-based smart patrol system is recommended to have the mechanism of emergency stop to prevent accidents happening. +- 2) The patrol route of IMR is composed of a series of patrol points connected in series. The IMR-based smart patrol system is recommended to upload patrol routes to the TSMS after the inspection is completed. +- 3) The IMR-based smart patrol system is recommended to identify patrol objects according to patrol tasks, and shoot pictures or videos around patrol objects through various sensors and multiple angles. + +There are requirements for the TSMS of route design and patrol process, which are as follows: + +- 1) the TSMS can optionally support real-time monitoring of the performance of the IMRs during the patrol process; +- 2) the TSMS is recommended to design patrol routes for the IMRs according to the location of the patrol points. + +### **7.3.4 Requirements for patrol record and abnormal report** + +There are requirements for the IMR-based smart patrol system of patrol record and abnormal report, which are as follows: + +- 1) the IMR-based smart patrol system is recommended to recognize the remainder of the machine fault, which include warning light or alarm whistle; +- 2) the IMR-based smart patrol system is required to support the return function of patrol position information, patrol status information, on-site image and video data, and support on-site abnormal situations and machine fault reporting to TSMS. + +There are requirements for the TSMS of patrol record and abnormal report, which are as follows. + +- 1) The TSMS is recommended to produce the patrol record and abnormal report automatically. By checking the abnormal report, maintenance can be conducted on time. +- 2) The TSMS can optionally integrate the data from every patrol point in the system for comprehensive data processing to ensure the feedback data of every patrol point refer to each other. + +### **7.3.5 Requirements for IMR control** + +There are requirements for IMR-based smart patrol system of IMR control, which are as follows. + +- 1) The IMR-based smart patrol system is recommended to communicate with mobile communication networks to obtain IMR sensor data, the IMR image and the IMR basic information through wireless fidelity, fourth generation, fifth generation, Bluetooth and other methods. +- 2) The IMR-based smart patrol system is recommended to support self-check, and the detection content includes various sensors in the IMR, global positioning system sensors, motor status, battery status, communication module, storage system, etc. If any abnormality is found in the self-check, the IMR will automatically return for maintenance. If no abnormality is found in the self-check, the IMR continues the patrol task. + +## 7.4 Requirements for management interface of IMR-based patrol + +### 7.4.1 The interface between IMR-based smart patrol system and TSMS + +A TSMS achieves the information collection of IMR resources through the interface with the smart patrol function of an IMR. At the same time, the interface completes the message interaction between the TSMS and IMR-based smart patrol system. + +As shown in Figure 3, in the field inspection function, an IMR-based smart patrol system obtains and downloads inspection tasks and intelligent identification data of inspection objects from a TSMS, and sends inspection record report messages to the TSMS. + +![Interaction diagram between an IMR-based smart patrol system and TSMS](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` +sequenceDiagram + participant TSMS + participant IMR as IMR-based smart patrol system + Note right of TSMS: M.3367(23) + TSMS->>IMR: 1. Download patrol task + TSMS->>IMR: 2. Download patrol object intelligent recognition data + IMR->>TSMS: 3. Patrol record report +``` + +The diagram shows a sequence of three messages between a TSMS and an IMR-based smart patrol system. The TSMS sends two messages to the IMR: '1. Download patrol task' and '2. Download patrol object intelligent recognition data'. The IMR then sends a message back to the TSMS: '3. Patrol record report'. The diagram is labeled 'M.3367(23)'. + +Interaction diagram between an IMR-based smart patrol system and TSMS + +**Figure 3 – Interaction diagram between an IMR-based smart patrol system and TSMS** + +### 7.4.2 The interface between IMR-based smart patrol system and patrol object + +As shown in Figure 4, the interface between an IMR-based smart patrol system and the patrol object can realize the information interaction between the IMR-based smart patrol system and the patrol object, and the communication methods include but are not limited to the near-field communication means. The physical interface of an IMR-based smart patrol system can include Bluetooth, wireless local area network, near field communication, universal serial bus and wireless charging. An IMR-based smart patrol system can connect with the inspection object through Bluetooth to obtain the inspection object number. The IMR-based smart patrol system can also obtain basic information about the inspection object by, for example, scanning code, taking photos, video recording and sensor collection. A TSMS can process and analyse the relevant state information of the inspection object. + +![Interaction diagram between IMR-based smart patrol system and patrol object](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` +sequenceDiagram + participant PatrolObject as Patrol object + participant IMR as IMR-based smart patrol system + Note right of PatrolObject: M.3367(23) + IMR->>PatrolObject: 1. Get patrol object number + IMR->>PatrolObject: 2. Status information +``` + +The diagram shows a sequence of two messages from an IMR-based smart patrol system to a Patrol object. The first message is '1. Get patrol object number' and the second is '2. Status information'. The diagram is labeled 'M.3367(23)'. + +Interaction diagram between IMR-based smart patrol system and patrol object + +**Figure 4 – Interaction diagram between IMR-based smart patrol system and patrol object** + +## Bibliography + +[b-ISO 8373] ISO 8373:2021, *Robotics – Vocabulary*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3368-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3368-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/M/T-REC-M.3368-202408-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3b7e07231c0f3e116c99c493bdda98ecd52313b6735faa6cea23815cf3162b +size 7190 diff --git a/marked/M/T-REC-M.3368-202408-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg b/marked/M/T-REC-M.3368-202408-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d372c8a01d673f93500c4f2374b00d933031888f --- /dev/null +++ b/marked/M/T-REC-M.3368-202408-I_PDF-E/acfc53eca625d62b38aa2563efa95c3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab768dfcbac8085775337de5751a2ab55e9869ee8d6675bda332acf27d535e59 +size 78222 diff --git a/marked/M/T-REC-M.3368-202408-I_PDF-E/df6babe297323feb1575ba89f5cf3b09_img.jpg b/marked/M/T-REC-M.3368-202408-I_PDF-E/df6babe297323feb1575ba89f5cf3b09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..589a9990784c85540d7fce9057aebed262290c40 --- /dev/null +++ b/marked/M/T-REC-M.3368-202408-I_PDF-E/df6babe297323feb1575ba89f5cf3b09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e86f53379a1498be8c773cb4c04db27897edfbcf28e0f5361745782dec97e8e +size 91058 diff --git a/marked/M/T-REC-M.3369-202408-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/M/T-REC-M.3369-202408-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a15d2bd24c8b3c7bdefa2ce1e03f46914d8835c0 --- /dev/null +++ b/marked/M/T-REC-M.3369-202408-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd93cf76040bd85c8c6de290391448032005500c3dde990cbcb14f5779952ac5 +size 58709 diff --git a/marked/M/T-REC-M.3369-202408-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.3369-202408-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79f03234d21b13ba2a7f6f405b069e45589898dd --- /dev/null +++ b/marked/M/T-REC-M.3369-202408-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa6a3968683d53e3caeb828cabef00e5a220088ea32d94e02d21b0dfe246d869 +size 15341 diff --git a/marked/M/T-REC-M.3369-202408-I_PDF-E/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/M/T-REC-M.3369-202408-I_PDF-E/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..372019cae111a67022eed6c5c18921fd56a1af00 --- /dev/null +++ b/marked/M/T-REC-M.3369-202408-I_PDF-E/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bf60ca3c3104ff38abff65e90c5a5368c246220e23f6957484546a01bd6a884 +size 78855 diff --git a/marked/M/T-REC-M.3369-202408-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3369-202408-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d8969f805414689ab79cfd08c333d454d482b3 --- /dev/null +++ b/marked/M/T-REC-M.3369-202408-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636c3839edff955a5b6208530b05fa1c983ab153d90f00216517a7a99478b988 +size 7074 diff --git a/marked/M/T-REC-M.3371-201610-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3371-201610-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d --- /dev/null +++ b/marked/M/T-REC-M.3371-201610-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c +size 4070 diff --git a/marked/M/T-REC-M.3371-201610-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/M/T-REC-M.3371-201610-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1635296d815e123052b56f68819deb03055bf344 --- /dev/null +++ b/marked/M/T-REC-M.3371-201610-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c0b42609853321e0c8aaf1b4110fa6586550f23295ef7a84b49dcc26202d740 +size 89169 diff --git a/marked/M/T-REC-M.3371-201610-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.3371-201610-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42bffa7b309a18d83f4bbef4be327f776b7dd36a --- /dev/null +++ b/marked/M/T-REC-M.3371-201610-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db6876f7bef39038538b0aa07f6f75b554d7e956bf9c6d86de81969de3e5f45c +size 39438 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/106404c26bd0d9c15c7b8546bc776a91_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/106404c26bd0d9c15c7b8546bc776a91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0f43ed04299903ce536bb9483ba4ca612782235 --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/106404c26bd0d9c15c7b8546bc776a91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:540ede8664c1b99fd33ff901d171440f781813b24e236469752c3b2d42154628 +size 53510 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/16f64b266536c4f0747e0cdd07dc57c0_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/16f64b266536c4f0747e0cdd07dc57c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59536102fcd7415a87f2f7fb8d2a9e0e67763d1d --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/16f64b266536c4f0747e0cdd07dc57c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72fd617968afeaf867e38bc159939b9e8fad387cb69fc086c44feac7bc786e1c +size 48731 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fe34f067b991ce2204ec30e6fa379527e4bc950 --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44d02250960dd0542175b10d309484248e5cd691323309cfe9eebe11309dc33c +size 6079 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/a105234ed1806a90bf96e710be7ccca4_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/a105234ed1806a90bf96e710be7ccca4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bc108d5c0571383abe0b859ff45fdc677320c50 --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/a105234ed1806a90bf96e710be7ccca4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc6a40c25670fea1fabd6afae81abe16007f47df0f4021dff1e63edb4958db49 +size 51657 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..372f12f284d3040f7d582957d72fb5c97d50b05b --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed495f7c8fec9d546e95e6c7ec5968253bda17212dbed45e0a559504c0ac192 +size 105212 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d06787d56e0b84216e3426488833e8ceb9fa5d78 --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52748339010a9cd39f670477579a93e4ba40decb2fd3e60990f59ed99d6f5e74 +size 117216 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/ea0e870e2f3087f34e4061d806b0356e_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/ea0e870e2f3087f34e4061d806b0356e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c37d9057a4a28b12c6461afc3cde0f055bda617d --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/ea0e870e2f3087f34e4061d806b0356e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:195184e04aa4f5d2b8107990368023bcce0dc3e19b0e241d818f4fba78db4449 +size 47559 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/ec788ac3d43f427d6dca7fa19dce3874_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/ec788ac3d43f427d6dca7fa19dce3874_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b37bcf171a1fd8a61d1414e1707643e79837ba47 --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/ec788ac3d43f427d6dca7fa19dce3874_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4d6b5e3d30814fac1dd76164949908360d1051d07e9bb9f164ed70757e7f5bb +size 54504 diff --git a/marked/M/T-REC-M.3381-202201-I_PDF-E/f21e92d35cd06ae5fb4bacb52ceedfb9_img.jpg b/marked/M/T-REC-M.3381-202201-I_PDF-E/f21e92d35cd06ae5fb4bacb52ceedfb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27c63023411847c7b30ca08b7b161516f74e7257 --- /dev/null +++ b/marked/M/T-REC-M.3381-202201-I_PDF-E/f21e92d35cd06ae5fb4bacb52ceedfb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c5f82711d48be0b8b9e131315f3a9766ec134c7e1be6bc2fa731d31d7f03a8f +size 49230 diff --git a/marked/M/T-REC-M.3383-202304-I_PDF-E/raw.md b/marked/M/T-REC-M.3383-202304-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..44b28f5148b5b5a82ad41997da64e5922b5792e4 --- /dev/null +++ b/marked/M/T-REC-M.3383-202304-I_PDF-E/raw.md @@ -0,0 +1,557 @@ + + +# Recommendation **ITU-T M.3383 (04/2023)** + +SERIES M: Telecommunication management, including TMN +and network maintenance + +Telecommunications management network + +--- + +# **Requirements for log analysis in telecom management with artificial intelligence** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +### **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3383 + +# Requirements for log analysis in telecom management with artificial intelligence + +## Summary + +Recommendation ITU-T M.3383 introduces the requirements for log analysis in telecom management with artificial intelligence (AI) and includes a functional framework, functional requirements, and typical scenarios of log analysis in telecom management with AI. This Recommendation gives examples of some log types and characteristics. This Recommendation also describes use cases of log analysis in telecom management with AI. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3383 | 2023-04-29 | 2 | 11.1002/1000/15516 | + +## Keywords + +AI log data, AI log acquisition, data processing, log analysis, telecom management with AI. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|----------------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation ..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Convention..... | 2 | +| 6 Overview..... | 3 | +| 7 Function framework for log analysis in telecom management with AI..... | 3 | +| 7.1 AI log acquisition module..... | 4 | +| 7.2 AI log data processing module ..... | 4 | +| 7.3 AI log storage module..... | 4 | +| 7.4 AI log analysis module..... | 4 | +| 8 The relationship between functional framework for log analysis in telecom management with AI and AITOM ..... | 5 | +| 9 Requirements for log analysis in telecom management with AI..... | 6 | +| 9.1 Requirements for AI log acquisition module..... | 6 | +| 9.2 Requirements for AI log data processing module ..... | 6 | +| 9.3 Requirements for the AI log storage module..... | 7 | +| 9.4 Requirements for the AI log analysis module ..... | 7 | +| Appendix I – Examples of several log types and characteristics ..... | 9 | +| Appendix II – Use cases of log analysis in telecom management with AI ..... | 11 | +| Bibliography ..... | 17 | + + + +# Recommendation ITU-T M.3383 + +# Requirements for log analysis in telecom management with artificial intelligence + +## 1 Scope + +This Recommendation specifies, for log analysis in telecom management with artificial intelligence (AI), including functional framework, functional requirements, and typical scenarios of log analysis in telecom management with AI. This Recommendation is applicable to the design, development, and application of log analysis in telecom management with AI. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3080] Recommendation ITU-T M.3080 (2021), *Framework of artificial intelligence enhanced telecom operation and management (AITOM)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 artificial intelligence capability set** [ITU-T M.3080]: A set of functions that are provided based on orchestrated artificial intelligence (AI) models to meet the requirement of some specific application scenarios. + +NOTE 1 – Specific application scenarios are to realize quality assurance, efficiency improvement, cost management, security assurance and industry applications, which are used for telecom operation and management. + +NOTE 2 – An AI capability can be generated through AI model orchestration based on the requirement of a specific application scenario. + +NOTE 3 – These functions may, but do not have to, be used based on the requirements of specific application scenarios. + +**3.1.2 artificial intelligence engine** [ITU-T M.3080]: The realization and mechanization, in software or hardware, of one or more functions dedicated to performing a specific artificial intelligence (AI) task. + +**3.1.3 artificial intelligence model** [ITU-T M.3080]: The model created by applying artificial intelligence (AI) technology to data to learn from. + +**3.1.4 artificial intelligence pipeline** [ITU-T M.3080]: A set of logical nodes, each with specific functionalities, that can be combined to form an artificial intelligence (AI) application in systems of telecom operation and management. + +**3.1.5 artificial intelligence sandbox** [ITU-T M.3080]: An environment in which artificial intelligence (AI) models can be trained and tested, and their effects on the network are evaluated. + +**3.1.6 customer-oriented marketplace** [ITU-T M.3080]: A collection of functional sets that exposes capability to external telecom customers, especially enterprises and industries. The exposed capability includes applications, services, data, and artificial intelligence (AI) capability. + +**3.1.7 management** [b-ITU-T Y.3100]: In the context of IMT-2020, the processes aiming at fulfilment, assurance, and billing of services, network functions, and resources in both physical and virtual infrastructure including compute, storage, and network resources. + +### **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|-----------------------------------------------| +| 5GC | 5G Core network | +| AI | Artificial Intelligence | +| AITOM | AI enhanced Telecom Operation and Management | +| BSS | Business Support System | +| EPC | Evolved Packet Core | +| ETH | Ethernet | +| E-UTRAN | Evolved UMTS Terrestrial Radio Access Network | +| HDFS | Hadoop Distributed File System | +| LTE | Long-Term Evolution | +| NG-RAN | Next Generation Radio Access Network | +| NMS | Network Management System | +| NoSQL | Not Only SQL | +| OS | Operations System | +| OSS | Operation Support Systems | +| OTN | Optical Transmission Network | +| RAB | Radio Access Bearer | +| RAN | Radio Access Network | +| RDBMS | Relational Database Management System | +| RRC | Radio Resource Control | +| SQL | Structured Query Language | +| SVM | Support vector machine | +| UMTS | Universal Mobile Telecommunications System | + +# **5 Convention** + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. + +The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Overview + +With the rapid development of network scale, operation and maintenance management have become more complicated. During the operation of the network and management information system such as network management system (NMS), operation support systems (OSS), etc., a large amount of log data will be generated, including network connection status, system database operating status, service process operating status and so on. + +There are many sources to collect logs, such as operations system (OS) server logs, network element logs, etc. Each type of log records different behaviours in the network elements or management systems. For example, network element logs focus on recording network behaviours at the network layer, while OS server logs record the running status and operation records of OS applications. + +Traditional operation and maintenance management does not make full use of log data and is mostly based on relatively simple processing algorithms such as statistical analysis and association rules. It relies more on the experience of maintenance personnel and experts, and the value of log data is not yet fully explored. With the development of artificial intelligence technology, it is necessary to use AI technology to realize the intelligent processing of log analysis, realize more efficient abnormal monitoring and early warning based on log analysis, and improve the level of operation and maintenance management. So, with the development of network scale, it is urgent to use artificial intelligence technology to realize the intelligent processing of log analysis, realize more efficient abnormal monitoring and early warning based on log analysis, and improve the level of operation and maintenance management. + +Appendix I gives some examples of different log types and characteristics which also contains some possible abnormal behaviours. Appendix II gives some use cases and scenarios of log analysis in telecom management with AI. + +# 7 Function framework for log analysis in telecom management with AI + +The function framework of log analysis in telecom management with AI is shown in Figure 1. + +The input data for log analysis in telecom management with AI include log records collected from network elements such as optical transmission network (OTN) terminal multiplexing device, etc. and OS servers that run management systems such as NMS, OSS, etc. + +After log analysis with AI, the analysis results such as anomaly monitoring information, fault classification information, and fault prediction information are formed to provide a decision-making basis for operation and maintenance personnel. It can improve the efficiency and quality of operation and maintenance work. + +![Figure 1: Function framework for log analysis in telecom management with AI. The diagram shows a four-tier architecture. At the base is the 'AI log acquisition module' containing 'Log for management system (Such as NMS, OSS, etc.)' and 'Log for network element (Such as OTN terminal multiplexing device)'. Above it is the 'AI log data processing module'. Above that is the 'AI log storage module'. At the top is the 'AI log analysis module' containing 'Pattern recognition', 'Model training', 'abnormal alarm', and 'Fault prediction'. Arrows indicate a bottom-up flow of data between adjacent modules, and a long arrow on the left side points from the processing module back to the analysis module. The label 'M.3383(23)' is at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +``` + +graph TD + subgraph AIA [AI log analysis module] + PR[Pattern recognition] + MT[Model training] + AA[abnormal alarm] + FP[Fault prediction] + end + ALSM[AI log storage module] + ALDM[AI log data processing module] + ALQM[AI log acquisition module] + subgraph ALQM + LMS[Log for management system (Such as NMS, OSS, etc.)] + LNE[Log for network element (Such as OTN terminal multiplexing device)] + end + LNE --> LMS + LMS --> ALDM + ALDM --> ALSM + ALSM --> AIA + ALDM --> AIA + M338323[M.3383(23)] + +``` + +Figure 1: Function framework for log analysis in telecom management with AI. The diagram shows a four-tier architecture. At the base is the 'AI log acquisition module' containing 'Log for management system (Such as NMS, OSS, etc.)' and 'Log for network element (Such as OTN terminal multiplexing device)'. Above it is the 'AI log data processing module'. Above that is the 'AI log storage module'. At the top is the 'AI log analysis module' containing 'Pattern recognition', 'Model training', 'abnormal alarm', and 'Fault prediction'. Arrows indicate a bottom-up flow of data between adjacent modules, and a long arrow on the left side points from the processing module back to the analysis module. The label 'M.3383(23)' is at the bottom right. + +**Figure 1 – Function framework for log analysis in telecom management with AI** + +## 7.1 AI log acquisition module + +This module is used to collect various types of logs. In order to distinguish the types of logs and understand the contents of logs, the module should have the ability to collect and use various types of logs to train AI models, such as OS server logs and network element logs. The collected information includes alarm ID/name, alarm type, alarm severity, alarm source, occurrence time, etc. For a specific alarm, the detailed illustration (definition, type, impact) is reported as context. Dealing with alarm data is important for failure management, including alarm compression, alarm correlation analysis, and alarm root cause identification. + +## 7.2 AI log data processing module + +This module is used to extract valid information in a log. Based on the characteristics of different types of log information, it converts unstructured or semi-structured multi-source heterogeneous log files into structured files and stores parameter values in the AI log storage module, so as to facilitate data mining and learning in the AI log analysis module. This module has the ability to identify and match the data according to the format and structure of data characteristics, and quickly extract the effective information in the data by referring to the extraction method of historical data. + +## 7.3 AI log storage module + +This module is used for storage data. The AI log storage module will record the knowledge information processed by the AI log data processing module to assist knowledge reasoning and data analysis in AI log analysis module. + +## 7.4 AI log analysis module + +This function module includes the basic AI functions that must be possessed for log analysis with AI. AI log analysis module models and trains log data, deeply excavates the hidden information and potential of the log and generates analysis results to guide the operation and maintenance of the network. AI log analysis module supports the choosing of different built-in function modules in different scenarios. This module collects the pre-processed log information in certain scenarios from the AI log storage module and the use in order to train the model and realize the pattern recognition and adjust and improve the parameter and performance of the models after making clear the usage scenario. + +- Model training: Train and test the model based on pre-processed log data and common AI models according to the requirements from the customer-oriented marketplace layer and other layers. Adjust and improve the parameter and performance of the models. + +NOTE – The functions of the customer-oriented marketplace layer are a reference to [ITU-T M.3080] which include a standardized capability directory and capability customization. The customer-oriented marketplace layer can build and maintain the AI capability requirements of external customers and expose applications, services, data and AI capability set to external customers. + +- Pattern recognition: Realize pattern recognition to mine the pre-processed data, find the hidden patterns and extract abnormal information from the log based on trained models. The abnormal information involves abnormal log number, abnormal log total number, abnormal log keyword, and so on. This process involves algorithms such as statistical analysis, clustering, classification, association rules, and sequential pattern recognition. +- Fault prediction: Predict potential faults and performance failures ahead of time based on the trained models and excavated information. +- Abnormal alarm: Alarm and report anomaly detection and prediction results based on the trained models and excavated information. The analysis results (such as log anomaly detection and log prediction results) and management and maintenance of log analysis strategy can be visualized. The abnormal alarm has the capabilities to create, configure, deliver, customize and manage the visual presentation of analysis results and analysis strategy. + +# 8 The relationship between functional framework for log analysis in telecom management with AI and AITOM + +Log analysis in telecom management with AI is a typical application scenario based on the AI enhanced telecom operation and management (AITOM) framework. + +The functional framework for log analysis in telecom management with AI references and AITOM framework. The relationship between the framework for log analysis in telecom management with AI and AITOM framework in Figure 2 can be described as follows: + +- The block name and functions of the "AI log acquisition module", "AI log data processing module" and "AI log storage module" correspond to "data acquisition", "data processing" and "data storage" respectively of the AITOM framework. But these three modules in this Recommendation are based on log analysis scenarios and they are extended to support AI methods. + +NOTE 1 – These three blocks correspond to red circle 1, red circle 2, and red circle 3 respectively in Figure 2. + +- The block name and functions of the "AI log analysis module" corresponds to the "AI engine" of the AITOM framework. The functions of "model training" are mainly guided by that of the "AI sandbox training" of AI engine, and the orchestration of "pattern recognition", "fault prediction" and "abnormal alarm" is mainly guided by "AI capability orchestration" of the AI engine. + +NOTE 2 – This block corresponds to red circle 4 in Figure 2. + +![Figure 2: Mapping relationship between functional framework for log analysis in telecom management with AI and AITOM [ITU-T M.3080].](d4af765160d04ecef538e5066006dc77_img.jpg) + +The diagram illustrates the mapping between the functional framework for log analysis and the AITOM framework. On the left, the 'Function framework for log analysis with AI-enhanced management system' consists of four modules: AI log acquisition module (1), AI log data processing module (2), AI log storage module (3), and AI log analysis module (4). The AI log acquisition module (1) includes 'Log from management system (Such as NMS, OSS, etc.)' and 'Log from network element (Such as OTN terminal multiplexing device, optical amplifier, etc.)'. The AI log analysis module (4) includes 'Pattern recognition', 'Model training', 'abnormal alarm', and 'Fault prediction'. Arrows indicate a sequential flow from module 1 to 4, with a bidirectional arrow between modules 3 and 4. On the right, the 'Functional framework of AITOM' is shown as a layered structure: Customer-oriented marketplace layer, SOMM (Scenario application layer, Management service layer, Data convergence and management layer, Infrastructure management layer), and Network. Red circles with numbers 1, 2, 3, and 4 map the log analysis modules to specific layers in AITOM: Module 1 maps to the Data convergence sub-layer (Data acquisition), Module 2 maps to the Data convergence sub-layer (Data processing), Module 3 maps to the Data convergence sub-layer (Data storage), and Module 4 maps to the SOMM (Scenario application layer). A vertical 'AI pipeline' on the right side of AITOM includes 'AI engine', 'AI capabilities management', 'AI capability orchestration', 'AI sandbox training', 'Common AI model repository management', and 'Computing engine framework management'. + +Figure 2: Mapping relationship between functional framework for log analysis in telecom management with AI and AITOM [ITU-T M.3080]. + +**Figure 2 – Mapping relationship between functional framework for log analysis in telecom management with AI and AITOM [ITU-T M.3080]** + +NOTE 3 – The symbols of the red circle with a number represent the mapping relationship between the "function framework for log analysis in telecom management with AI" and the AITOM framework. + +# 9 Requirements for log analysis in telecom management with AI + +## 9.1 Requirements for AI log acquisition module + +The requirements of the AI log acquisition module include: + +- 1) It is required that the AI log acquisition module supports collecting multi-source heterogeneous log, such as data from network management system (NMS), element management system, and network equipment. +- 2) It is recommended that log data be collected in time, which can timely obtain the operation status of the managed network and provide timely data support for the decision-making of the management system. +- 3) It is recommended that the AI log acquisition module supports conducting preliminary analysis, including the format, storage mode and generation speed of different logs. +- 4) It is recommended that operation-related anomalies log be collected and pre-processed. +- 5) It is required that the AI log acquisition module supports the accuracy and completeness of data collection. Data loss and corruption should be prevented during acquisition. +- 6) It is recommended that a proper collection period should be supported in the AI log acquisition module based on the different types of logs. +- 7) It is recommended that the interface of AI log acquisition is open to ensure real-time and is stable for log collection. +- 8) It can optionally support the parallel collection of log data, and collect multi-source data simultaneously in a multi-channel parallel mode. + +## 9.2 Requirements for AI log data processing module + +The requirements of the AI log data processing module include: + +- 1) It is recommended that the AI log acquisition module supports pre-processing function, including log cleaning and missing value handling. Log cleaning is to filter the unnecessary log information, remove noise data and correct the inconsistency of the data. Missing value handling can be filled by AI algorithms to ensure data integrity. +- 2) It is required that the AI log data processing module supports the normalization and unification of log data format, including multi-source heterogeneous log data, for further storage and analysis. +- 3) It is recommended that the AI log data processing module supports analysing the user-defined analysis strategy and feature data pre-processing for the log data, so that the heterogeneous data can be converted into a standard format, including feature data selection, normalization or standardization, and feature data enhancement and enrichment, etc. + +## **9.3 Requirements for the AI log storage module** + +The requirements of the AI log storage module include: + +- 1) It is required that the AI log storage module supports the classification storage of different log types and log formats. +- 2) It is recommended that the AI log storage module supports the storage of intermediate output data and final analysis results. +- 3) It is recommended that the AI log storage module supports multiple file systems for storing logs, such as traditional relational database management system (RDBMS) or distributed cluster system not only structured query language (NoSQL), and Hadoop distributed file system (HDFS). +- 4) It is recommended that the AI log storage module supports full-text retrieval, phrase query, field filtering and other functions to achieve fast log search. +- 5) It is recommended that the AI log storage module needs a reasonable storage period based on the data collection period and data storage space to prevent storage space overflow. + +## **9.4 Requirements for the AI log analysis module** + +The requirements of the AI log analysis module include: + +- 1) It is required that the AI log analysis module supports various types and formats of logs. +- 2) It is recommended that the AI log analysis module supports a variety of log analysis algorithms. The AI models are stored in the common artificial intelligence model library. The log analysis algorithms include statistical analysis, association rules, clustering, classification, sequence pattern, transaction recognition, etc. +- 3) It is recommended that the AI log analysis module supports user-defined algorithms. The AI models are stored in the telecom specific artificial intelligence model library. The common AI models in management systems can be added for fault monitoring, root cause analysis, etc. +- 4) It is recommended that the AI log analysis module supports the training of log data in a sandbox. The training object is a pre-defined AI model suitable for specific situations. In the training process, it is necessary to estimate and analyse the model and predict the accuracy of the model. Through the test and evaluation of the model, constantly adjust the parameters, optimize the model, and improve the accuracy and practicability of the model. +- 5) It is recommended that the AI log analysis module supports fault detection. + +NOTE 1 – Log analysis based on fault detection can comprehensively manage and analyse system faults. AI log analysis module can monitor the running state of the system in real time through a log analysis service. The log analysis module can automatically classify the fault logs and analyse the correlation of the system faults. + +- 6) It is recommended that the AI log analysis module supports a variety of predictions, such as fault prediction, error prediction, user access prediction, regulatory prediction, etc. +- 7) It is recommended that the AI log analysis module supports pattern recognition. + +NOTE 2 – Pattern recognition is a technology that uses various algorithms, rules and models to mine the pre-processed data and find the hidden patterns from the log. The algorithm includes statistical analysis, clustering, classification, association rules, sequential pattern recognition, etc. +- 8) It is recommended that the AI log analysis module supports anomaly assessment with logs. + +NOTE 3 – Three steps need to be done to assess a log anomaly. Firstly, construct a structured log by extracting keywords and matching it to a log template that is learned from existing log files. Secondly, carry out pattern mining to extract features from structured logs. Finally, judge the log's anomaly from the quantitative perspective as well as the perceived perspective. +- 9) It is recommended that the AI log analysis module supports abnormal alarms based on the result of fault prediction and reports anomaly detection and prediction results in real time or regularly. +- 10) It is recommended that the AI log analysis module supports fast log information search and log query, including fuzzy query, range query, combined query, etc. +- 11) It is recommended that the AI log analysis module supports the determination of log training time, scope, process, and method according to the requirements from the customer-oriented marketplace layer and other layers. +- 12) It is recommended that the AI log analysis module supports the reporting of analysis results to the customer-oriented marketplace layer for customized analysis strategy. +- 13) It is recommended that the AI log analysis module supports the visualization of log anomaly detection and log prediction results. +- 14) It is recommended that the AI log analysis module supports the visualization of multiple data sources fusion. +- 15) It is recommended that the AI log analysis module supports real-time data display and interaction. + +## Appendix I + +### Examples of several log types and characteristics + +(This appendix does not form an integral part of this Recommendation.) + +AI log acquisition module can collect OS server logs, network element logs, etc. Each kind of log has its characteristics. The log records different types of behaviours in the network. Network element logs record network behaviours in the network layer, while OS server logs record the running status of system application processes and the operator's behaviours. Table I.1 shows examples of the different types of logs and the corresponding behaviours that may be detected. Table I.2 lists the characteristics of several typical logs and the possible abnormal behaviours. + +Some fault logs can be compared to determine the current system anomalies, realizing real-time alarm and fault processing. Combining log information of different times and different types and mining the internal association of logs with AI technology, the management system can have a comprehensive understanding of the current status, potential risk, and so on. + +**Table I.1 – Examples of different log types and corresponding behaviours** + +| Log types | Behaviours may be detected | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OS server log | OS server log is classified into information, warning, and error levels. Most event records generated by the OS server are related to the following aspects: running status and operation records of OS applications, modifications of executable files, unsafe system reconfiguration or damage, authentication or authorization failure, etc. | +| OTN equipment log | OTN equipment log can record the operating status of equipment in the optical transmission network. The equipment includes OTN terminal multiplexing devices, OTN optical cross-connected devices (such as OTN electrical crossover devices, OTN optical crossover devices and devices having both OTN electrical and optical crossover functions), etc. OTN equipment log records a large number of forward events, configuration changes, outbound and inbound transfer bytes, the connection status of different devices, etc. | +| Optical transmission link log | Identify the transmission link information, for example, the ETH (Ethernet) end port information, automatic protection switching information, input optical power information of the link, etc. | +| Database log | Database log can record the operating status of the database, including error log, query log, slow query log, event log, binary log, relay log and so on. For example, the database log can record the customer interface status of the database, the execution status of the program statement (e.g., SQL) and error information. | +| Operation support systems (OSS) and business support system (BSS) log | The OSS and BSS log includes the module log, application log, and security log. The OSS and BSS log can record the information of the hardware, software, and system problems in the OSS and the BSS. Moreover, the OSS and BSS log can also monitor the events that occur in the OSS and BSS. The OSS and BSS log can be used to check the cause of the error and to find the traces left by the attacker when it was attacked. | + +**Table I.1 – Examples of different log types and corresponding behaviours** + +| Log types | Behaviours may be detected | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5G core network (5GC) and evolved packet core (EPC) network function log | 5GC and EPC network functions include the network elements and virtual network elements in the 5GC and EPC.
The network function log includes the system log, operation log, and security log. The system log can record the running information of (virtual) network elements of 5GC and EPC. The operation log can record the operation log of (virtual) network elements of 5GC and EPC. The security log can record the security events and security audits that occur in the (virtual) network elements of 5GC and EPC. | +| Long-term evolution (LTE) evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) and 5G next generation radio access network (NG-RAN) performance measurement log | Record the RAN performance measurement information, which includes radio resource control (RRC) connection related measurements, radio access bearer (RAB) related measurements, handover related measurements, radio source utilization related measurements, paging related measurements, equipment resource related measurements, etc. | + +**Table I.2 – The characteristics of several typical logs and the possible abnormal behaviours** + +| Log characteristics | Possible abnormal behaviours | +|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OS server log generates alarm information | Identify events that may have problems in the future. For example, critical system files have been deleted and disk space is running out, abnormal program results in a device restart, a memory usage error occurs, and device memory utilization reaches the limit. | +| OS server log generates failure auditing information. | Identify the audited security events that did not complete successfully. For example, users cannot access network drives. | +| OTN transmission interrupt information | Identify events that caused the interruption, for example, an abnormal clock signal (SerDes), E1/T1 port error, etc. | +| OTN status abnormal information | The abnormal information collected by the OTN equipment contains a variety of fault information, including loss of continuity, path trace mismatch, payload type mismatch, forward / backward indication missing, etc. | +| Database abnormal information | The abnormal information collected by the database contains the abnormal frequency of keyword occurrences (e.g., error, failure), and log volume changes (e.g., sudden rise or drop). | +| OSS and BSS abnormal information | The abnormal information collected by the OSS and BSS contains the abnormal frequency of keyword occurrences (e.g., alarm, error), and log volume changes (e.g., sudden rise or drop). | +| 5GC and EPC network function abnormal information | The abnormal information collected by the (virtual) network elements of 5GC and EPC contains the abnormal frequency of keyword occurrences (e.g., error, warning), and log volume changes (e.g., sudden rise or drop). | +| LTE E-UTRAN and 5G NG-RAN base station generates frequently performance false alarm | Usually, LTE E-UTRAN and 5G NG-RAN base station performance measurements are below the threshold predefined by the operator, an alarm will be generated, but sometimes performance fault recovery occurs by the equipment itself and the corresponding alarms are closed, the reasons may be due to transmission flash break and wind (antenna of a base station could be affected), etc. Thus, it is necessary to distinguish the true performance alarm from all of the alarms. The method of threshold adjusted, and delay set is not valid in most of the cases. | + +## Appendix II + +### Use cases of log analysis in telecom management with AI + +(This appendix does not form an integral part of this Recommendation.) + +After log analysis with AI, the analysis results such as anomaly monitoring information, fault classification information, and fault prediction information are formed, as shown in the following tables. + +**Table II.1 – An intelligent system of real-time monitoring and anomaly warning** + +| Title | An intelligent system of real-time monitoring and anomaly warning | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description |

This case is an intelligent system with real-time monitoring and anomaly warning function. Each log has its unique characteristics. For example, when automatic protection warning occurs, the OTN transmission link log information will be created. With these feature behaviours of the managed elements, whether there is real automatic protection anomaly, can be determined.

  1. 1) Collect log data including possible fault information from OS servers and network elements through the AI log acquisition module.
  2. 2) Analyse the log analysis strategy and pre-process log data to convert it into a standard format in the AI log data processing module.

NOTE 1 – The information can be extracted directly from some log data which has a fixed format (e.g., IP address, etc.).

  1. 3) Store the pre-processed data in the AI log storage module.
  2. 4) Acquire the pre-processed data from the database, knowledge base and diagnosis database of the expert system in the AI log storage module and form the training data and test data sets.
  3. 5) Train the model in AI log analysis module according to the train data sets and update the parameter of the model by test data sets.
  4. 6) Acquire online log data which has been collected, pre-processed and stored, then match the pre-processed log to a log template based on the trained models.
  5. 7) Carry out pattern mining on unmatched log data to extract log features from pre-processed logs.
  6. 8) Extract anomaly detection to carry out real-time monitoring.
  7. 9) Visualize the anomaly results and anomaly warning.
  8. 10) The online data is used to retrain existing models to improve model quality.

NOTE 2 – Existing models also can be incrementally retrained, and parameters are updated to improve model quality by periodically updating the training data.

| + +**Table II.1 – An intelligent system of real-time monitoring and anomaly warning** + +![Diagram of an intelligent system of real-time monitoring and anomaly warning. The system consists of three main modules: AI log acquisition module (1), AI log data processing module (2), and AI log storage module (3). The AI log storage module feeds into the AI log analysis module. The AI log analysis module contains three sub-modules: Model training (4, 5), Pattern recognition (6, 7, 10), and Extract anomaly results and real-time monitoring (8, 9). The flow is: 1) Log from OS servers and network elements are collected by the AI log acquisition module. 2) The data is processed by the AI log data processing module. 3) The processed data is stored in the AI log storage module. 4) The AI log storage module feeds into the Model training sub-module, where a data set is formed (4) and the model is trained (5). 5) The trained model is used in the Pattern recognition sub-module, where data is matched to a template (6) and patterns are mined (7). 6) The mined patterns are used in the Extract anomaly results and real-time monitoring sub-module (8). 7) The results are visualized (9). 10) A feedback loop exists from the Pattern recognition sub-module back to the Model training sub-module. Red arrows indicate development state using offline data, and blue arrows indicate operation state using online data.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +| Title | An intelligent system of real-time monitoring and anomaly warning | +|-------------|-------------------------------------------------------------------| +| Figure II.1 |

M.3383(23)

| + +Diagram of an intelligent system of real-time monitoring and anomaly warning. The system consists of three main modules: AI log acquisition module (1), AI log data processing module (2), and AI log storage module (3). The AI log storage module feeds into the AI log analysis module. The AI log analysis module contains three sub-modules: Model training (4, 5), Pattern recognition (6, 7, 10), and Extract anomaly results and real-time monitoring (8, 9). The flow is: 1) Log from OS servers and network elements are collected by the AI log acquisition module. 2) The data is processed by the AI log data processing module. 3) The processed data is stored in the AI log storage module. 4) The AI log storage module feeds into the Model training sub-module, where a data set is formed (4) and the model is trained (5). 5) The trained model is used in the Pattern recognition sub-module, where data is matched to a template (6) and patterns are mined (7). 6) The mined patterns are used in the Extract anomaly results and real-time monitoring sub-module (8). 7) The results are visualized (9). 10) A feedback loop exists from the Pattern recognition sub-module back to the Model training sub-module. Red arrows indicate development state using offline data, and blue arrows indicate operation state using online data. + +**Table II.2 – An intelligent system of fault prediction** + +| Title | An intelligent system of fault prediction | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description |

This case is an intelligent system with a fault prediction function. AI log collection module will collect information (including possible fault information) from the OS server log and network element log in the AI log storage module after being structured and normalized by the AI log data processing module. AI log analysis module will use the AI model stored in a common artificial intelligence model library or telecom specific artificial intelligence model library for fault prediction according to the requirements.

  1. 1) Collect the current log with potential faults from the OS servers and network elements through the AI log acquisition module.
  2. 2) Analyse the log analysis strategy and pre-process log data to convert it into a standard format in the AI log data processing module.

NOTE 1 – The information can be extracted directly from some log data which has a fixed format (e.g., IP address, etc.).

  1. 3) Store the pre-processed data in the AI log storage module.
  2. 4) Acquire the pre-processed data from the database, knowledge base and diagnosis database of the expert system in the AI log storage module, which includes the normal log with the label "1" and fault log with the label "0", to form the training data and test data sets.
  3. 5) Train the model in AI log analysis module according to the train data sets and update the parameter of the model by test data sets.
  4. 6) Generate the predicted value based on the trained model.
  5. 7) Compare the predicted value with the threshold.
  6. 8) If the value is larger than the threshold, which means a potential fault is identified.

NOTE 2 – Existing models also can be incrementally retrained, and parameters are updated to improve model quality by periodically updating the training data.

| + +**Table II.2 – An intelligent system of fault prediction** + +![Diagram of an intelligent system of fault prediction. It shows three main modules: 1. AI log acquisition module (collecting logs from OS servers and network elements), 2. AI log data processing module, and 3. AI log storage module. These modules feed into the AI log analysis module. The analysis module contains a 'Model training' sub-module (4. Form data set, 5. Train model) and a 'Potential failure assessment' sub-module (6. Compare predicted value with the threshold, 7. Potential failure assessment). Arrows indicate the flow of data, with red arrows for development state (offline data) and blue arrows for operation state (online data).](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +| Title | An intelligent system of fault prediction | +|-------------|----------------------------------------------| +| Figure II.2 |

M.3383(23)

| + +Diagram of an intelligent system of fault prediction. It shows three main modules: 1. AI log acquisition module (collecting logs from OS servers and network elements), 2. AI log data processing module, and 3. AI log storage module. These modules feed into the AI log analysis module. The analysis module contains a 'Model training' sub-module (4. Form data set, 5. Train model) and a 'Potential failure assessment' sub-module (6. Compare predicted value with the threshold, 7. Potential failure assessment). Arrows indicate the flow of data, with red arrows for development state (offline data) and blue arrows for operation state (online data). + +**Table II.3 – An intelligent system of fault classification** + +| Title | An intelligent system of fault classification | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Description |

This case is an intelligent system with a fault classification function. The AI log acquisition module collects real-time log data, inputs the processed data into the AI log analysis module, and finally outputs the fault classification results to realize the classification of the fault.

  1. 1) Collect all the abnormal events and attack events on the current network, including fault information from the OS servers and network elements through the AI log acquisition module.
  2. 2) Analyse the log analysis strategy and pre-process log data to convert it into a standard format in the AI log data processing module.

NOTE 1 – The information can be extracted directly from some log data which has a fixed format (e.g., IP address, etc.).

  1. 3) Store the pre-processed data in the AI log storage module.
  2. 4) Acquire the pre-processed data from the diagnosis database of the expert system in the AI log storage module and form the training data and test data sets to train the model. Apply the model to classify the current log.
  3. 5) Compare the value of the maximum matching probability with the specified threshold.
  4. 6) If the value is larger than the threshold, the current fault is identified as the maximum matching fault; while the value is smaller than the threshold, the current is identified as a new fault, which will be deeply analysed.
  5. 7) Confirm new fault types with expert experience and cluster analysis.
  6. 8) The online data is used to retrain the existing model to improve model quality with a new fault type label.

NOTE 2 – Existing models also can be incrementally retrained, and parameters are updated to improve model quality by periodically updating the training data.

| + +**Table II.3 – An intelligent system of fault classification** + +![Diagram of an intelligent system of fault classification. The system consists of three main modules: 1. AI log acquisition module (Log from OS servers, Log from network elements), 2. AI log data processing module, and 3. AI log storage module. The AI log storage module feeds into the AI log analysis module. The AI log analysis module contains: 4. Model training (Form data set, Train model), 5. Compare the maximum predicted probability with the threshold, 6. Confirm fault, 7. Analyse new fault, and 8. Feedback loop. Red arrows indicate development state using offline data, and blue arrows indicate operation state using online data.](83852ec55d4802521a727926336bedab_img.jpg) + +| Title | An intelligent system of fault classification | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Figure II.3 |

The diagram illustrates an intelligent system of fault classification. It is divided into two main parts: the AI log storage and processing part, and the AI log analysis module.

  • AI log storage and processing part:
    • 1 AI log acquisition module: Contains 'Log from OS servers' and 'Log from network elements'.
    • 2 AI log data processing module: Receives data from the acquisition module.
    • 3 AI log storage module: Receives data from the processing module and sends it to the analysis module.
  • AI log analysis module:
    • 4 Model training: Consists of 'Form data set' and 'Train model'. A red arrow (development state) goes from 'Form data set' to 'Train model'.
    • 5 Compare the maximum predicted probability with the threshold: A blue arrow (operation state) goes from 'Train model' to this step.
    • 6 Confirm fault / Analyse new fault: Two blue arrows (operation state) go from step 5 to these steps.
    • 7 Analyse new fault: A blue arrow goes from 'Confirm fault' to 'Analyse new fault'.
    • 8 Feedback loop: A blue arrow goes from 'Analyse new fault' back to 'Train model'.

Legend:

  • Red arrow: In development state using offline data
  • Blue arrow: In operation state using online data

M.3383(23)

| + +Diagram of an intelligent system of fault classification. The system consists of three main modules: 1. AI log acquisition module (Log from OS servers, Log from network elements), 2. AI log data processing module, and 3. AI log storage module. The AI log storage module feeds into the AI log analysis module. The AI log analysis module contains: 4. Model training (Form data set, Train model), 5. Compare the maximum predicted probability with the threshold, 6. Confirm fault, 7. Analyse new fault, and 8. Feedback loop. Red arrows indicate development state using offline data, and blue arrows indicate operation state using online data. + +Here we provide several scenarios of log analysis with AI that could help network operators manage and maintain the network better. + +#### Scenario 1: managed element alarm optimization + +**Data type:** Bit error rate data of communication transmission network and optical power monitoring log data of transmission equipment. + +**Apply scenario:** Communication transmission network. + +**Requirement description:** Due to the problems of real-time measurement error, network error code and packet loss in the communication transmission network, the bad data will affect the real-time status evaluation results of the transmission network, and then lead to wrong operation and maintenance decisions. + +**Processing method:** By using the bad data evaluation algorithm, the mining algorithm based on the relative density is used to mine the measured data, the historical log data, and the corresponding network alarm information. Based on the results of the bad data mining, the running state of the transmission network is evaluated and comprehensively analysed. + +**Contribution:** The influence of real-time measurement error, network error code, and packet loss on the bit error rate of communication network and optical power of transmission equipment is solved, and the occurrence of error alarm is reduced. + +#### Scenario 2: operation and maintenance of optical cable + +**Data type:** Operation and maintenance log data of optical cable of the communication network. + +**Apply scenario:** Optical transmission network. + +**Requirement description:** Due to the lack of real-time data analysis of resource performance, equipment aging, and fault information are difficult to timely monitor. The lack of external weather data makes it difficult to prevent cable failure in extreme weather. + +**Processing method:** Based on the analysis of fibre optic cable performance log data, fibre optic cable operation and maintenance log data, and fibre optic cable environment meteorological log data, the relevant performance data and environmental data were extracted to model the operation of a fibre optic cable, and classification algorithms such as decision tree and support vector machine (SVM) + +combined algorithms such as bagging and boosting were used to carry out fault warning for fibre optic cable. + +**Contribution:** Real-time monitoring and early warning of optical cable deterioration can be realized to reduce the risk of optical cable failure caused by meteorological disasters. + +#### **Scenario 3: managed element temperature monitoring** + +**Data type:** Temperature monitoring log data of communication network elements. + +**Apply scenario:** All kinds of communication network elements. + +**Requirement description:** The original alarm method by setting the temperature detection threshold of the power environment in the communication room is sensitive to the distance between the monitoring point and the communication equipment, which is easy to lead to a large temperature measurement deviation. At the same time, the accuracy of the temperature alarm is difficult to control because of the different equipment specifications and sensitivity of each network element manufacturer. + +**Processing method:** The temperature parameters are extracted from the massive log data generated by the integrated temperature measurement module, and the analysis and early warning of historical data are realized through temperature data collection, model normalization, data analysis, and function presentation by using the processing technology and idea of big data processing methods (such as the ARMA model). + +**Contribution:** Compared with the traditional monitoring and processing methods, the temperature monitoring system based on the log file historical record of the communication network is more sensitive to temperature changes, can detect temperature anomalies in advance, can reduce the accident level of substation and communication room, and improve the system security. + +#### **Scenario 4: OTN fault diagnosis** + +**Data type:** OTN alarm log data. + +**Apply scenario:** OTN. + +**Requirement description:** Traditional alarm methods get a lot of interference, redundancy, and incomplete information in OTN alarm information, and cost a long time to locate the problem. In practical application, it is necessary to properly determine the location, type, and cause of the fault within the shortest time, to repair or isolate the fault in time. + +**Processing method:** Through analysing OTN alarm log files, the algorithm adopts alarm time synchronization processing, alarm information sorting and field extraction, alarm compression, and other methods to realize the standardized processing of alarm information, and finally transforms the alarm transaction database. By using neural network and data characteristics of association rule alarm transaction database, alarm events are modelled, and fault diagnosis of alarm events is realized. + +**Contribution:** With the help of real-time data and historical data in OTN alarm logs, the standardized management of alarms for optical transmission network equipment of different manufacturers is realized, and the correlation of log data is analysed by using data mining technology, and the intelligent alarm cause diagnosis is realized. + +#### **Scenario 5: LTE E-UTRAN and 5G NG-RAN base station false alarm distinguished** + +**Data type:** Base station false alarm log data. + +**Apply scenario:** LTE E-UTRAN and 5G NG-RAN base station. + +**Requirement description:** Traditional LTE E-UTRAN and 5G NG-RAN base station false alarm distinguished methods that performance threshold adjusted, and time windows set are not valid to most of the cases, it leads to a lot of effort for the operator to distinguish them by hand, and the + +accuracy is low. Since the number of base stations is large for operators, it is necessary to find a new way to distinguish fault alarms quickly and accurately. + +**Processing method:** LTE E-UTRAN and 5G NG-RAN base station performance measurement log files are analysed by an AI-enhanced management system, the process includes performance indicators data extraction, standard format transformation, loaded to the database and the AI method applied. In the data pre-processing phase, data features are calculated from the statistical characteristics, fitting features and radio service features, and combined by serial or parallel concatenation. In the AI processing phase, the decision tree and LightGBM method are used, and the parameters are optimised according to experience. + +**Contribution:** With the help of real-time data and historical data in LTE E-UTRAN and 5G NG-RAN base station performance logs, the standardized management of performance false alarms for LTE E-UTRAN and 5G NG-RAN base station equipment of different manufacturers is realized, and the false alarm is analysed by using data mining technology quickly and accurately. + +## Bibliography + +- [b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3385-202304-I_PDF-E/raw.md b/marked/M/T-REC-M.3385-202304-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0b1f284b133123bfd7d676fc07f8b8120bc2497e --- /dev/null +++ b/marked/M/T-REC-M.3385-202304-I_PDF-E/raw.md @@ -0,0 +1,565 @@ + + +# Recommendation**ITU-T M.3385 (04/2023)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **Intelligence levels evaluation framework of artificial intelligence enhanced telecom operation and management** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue circular emblem with a stylized globe and the letters 'ITU' in white. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3385 + +### Intelligence levels evaluation framework of artificial intelligence enhanced telecom operation and management + +## Summary + +Recommendation ITU-T M.3385 provides a detailed evaluation framework, evaluation rating method and automatic evaluating process for intelligence levels of systems which follow the framework of artificial intelligence enhanced telecom operation and management (AITOM). + +This Recommendation is included in the series of Recommendations about intelligence levels of artificial intelligence enhanced telecom operation and management (IL-AITOM). + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3385 | 2023-04-29 | 2 | 11.1002/1000/15518 | + +## Keywords + +Artificial intelligence enhanced telecom operation and management (AITOM), evaluation framework, intelligence level. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Background..... | 2 | +| 7 Evaluation framework of IL-AITOM ..... | 2 | +| 7.1 Overview ..... | 2 | +| 7.2 Evaluated object ..... | 3 | +| 7.3 Evaluation dimensions ..... | 4 | +| 7.4 Evaluation sub-dimensions ..... | 4 | +| 7.5 Evaluation tasks ..... | 5 | +| 8 Evaluation rating method of IL-AITOM ..... | 5 | +| 8.1 Criteria of evaluation task evaluation..... | 5 | +| 8.2 Evaluation rating method of evaluated object ..... | 6 | +| 9 Automatic evaluating process of IL-AITOM ..... | 7 | +| Appendix I – An evaluation use case of intelligence levels about quality assurance capability for IMT-2020 and beyond network operation and management system..... | 9 | +| Bibliography ..... | 20 | + + + +## Recommendation ITU-T M.3385 + +## Intelligence levels evaluation framework of artificial intelligence enhanced telecom operation and management + +## 1 Scope + +This Recommendation is included in the series of Recommendations about intelligence levels of artificial intelligence enhanced telecom operation and management (IL-AITOM). [ITU-T M.3384] provides principles of IL-AITOM including the definition, classification rules, evaluated objects and the general evaluation implementation architecture of IL-AITOM. Based on [ITU-T M.3384], this Recommendation provides a detailed evaluation framework, evaluation rating method and automatic evaluating process for intelligence levels of systems which follow the framework of artificial intelligence enhanced telecom operation and management (AITOM) presented in [ITU-T M.3080]. This Recommendation is used to guide the evaluation implementation of IL-AITOM and is helpful in discerning the telecom operation and management weak points for improvement. + +The scope of this Recommendation comprises: + +- Overall evaluation framework of IL-AITOM and detailed definitions; +- Evaluation rating method of IL-AITOM; +- Automatic evaluating process of IL-AITOM. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3080] Recommendation ITU-T M.3080 (2021), *Framework of artificial intelligence enhanced telecom operation and management (AITOM)*. + +[ITU-T M.3384] Recommendation ITU-T M.3384 (2023), *Intelligence levels of artificial intelligence enhanced telecom operation and management*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 artificial intelligence (AI)** [b-ITU-T F.749.13]: An interdisciplinary field, usually regarded as a branch of computer science, dealing with models and systems for the performance of functions generally associated with human intelligence, such as reasoning and learning. + +**3.1.2 operation stage** [ITU-T M.3384]: General subsets for processes of telecom operation and management. + +## 3.2 Terms defined in this Recommendation + +None. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|---------------------------------------------------------------------| +| AHP | Analytic Hierarchy Process | +| AI | Artificial Intelligence | +| AITOM | AI enhanced Telecom Operation and Management | +| IL-AITOM | Intelligence Levels of AI enhanced Telecom Operation and Management | +| IMT | International Mobile Telecommunication | +| QoS | Quality of Service | +| SLA | Service Level Agreement | +| SOMM | Smart Operation Maintenance and Management | + +## 5 Conventions + +In this Recommendation: + +The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +The keywords "is recommended to" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. + +# 6 Background + +Research is ongoing in standards development organizations (SDOs) on methods for intelligence levels evaluation in artificial intelligence enhanced telecom operation and management (AITOM). Currently [b-3GPP TS 28.100] studying intelligence level evaluation of IMT-2020 network is in progress. [b-ITU-T Y.3173] containing a framework for evaluating the intelligence levels of future networks is proposed. [b-TM Forum IG1252] describes the autonomous networks level methodology. The above studies are mainly focused on certain network fields. This Recommendation however specifies a detailed evaluation framework and evaluation rating method focusing on intelligence levels of AI enhanced telecom operation and management (IL-AITOM). Due to the numerous parameters in the method, the automatic evaluating process for IL-AITOM is further proposed to realise automatic evaluation and so improve evaluating efficiency. + +## 7 Evaluation framework of IL-AITOM + +## 7.1 Overview + +The evaluation framework of IL-AITOM is proposed in Figure 7-1 and includes six parts: + +- Classification on the intelligence level of AITOM defined five generic levels ranging from Level 1 to Level 5. +- The selection model of an evaluated object gives a three-dimensional model that considers the operation stage, system granularity, and service to identify an evaluated object. +- Evaluation dimensions including intent mapping, data collection, analysis, decision and action implementation create a complete closed-loop from the requirement to the realization in operation and management activities. +- Evaluation sub-dimensions are further fine-grained divisions of evaluation dimensions as a guide to break down the evaluation task. +- Evaluation tasks are minimum evaluated units for an evaluated object. + +- Evaluation rating gives the convergence calculation process from scores of evaluation tasks to the intelligence level of an evaluated object. + +![Figure 7-1 – Evaluation framework of IL-AITOM. The diagram shows a hierarchical structure for evaluating IL-AITOM objects. At the top is 'Classification on intelligence level of AITOM' with five levels. Below it is the 'Selection model of evaluated object' with Service, Operation stage, and System granularity. The 'Evaluation dimensions' include Intent mapping, Data collection, Analysis, Decision, and Action implementation. These lead to 'Evaluation sub-dimensions' like Intent acquisition, Data processing, Resource analysis, Customer analysis, Policy generation, Policy judgement, System implementation, and Network element implementation. These sub-dimensions are linked to 'Evaluation tasks' (Task 1 to Task n). A vertical bar on the right shows the flow to 'Evaluation rating'. A legend at the bottom indicates orange boxes are from ITU-T M.3384 and blue boxes are from this recommendation.](acfc53eca625d62b38aa2563efa95c3e_img.jpg) + +**Classification on intelligence level of AITOM** + +Level 1    Level 2    Level 3    Level 4    Level 5 + +**Selection model of evaluated object** + +Service    Operation stage    System granularity + +**Evaluation dimensions** + +Intent mapping    Data collection    Analysis    Decision    Action implementation + +**Evaluation sub-dimensions** + +Intent acquisition    Intent parsing    ....    Intent feedback    Data collection    Data processing    Resource analysis    Service analysis    ....    Customer analysis    Policy generation    ....    Policy judgement    System implementation    Network element implementation + +**Evaluation tasks** + +Task 1    Task 2    Task 3    Task 4    Task 5    Task 6    Task ...    Task n + +**Evaluation rating** + +  First proposed in [ITU-T M.3384] +   Proposed in this Recommendation + +M.3385(23) + +Figure 7-1 – Evaluation framework of IL-AITOM. The diagram shows a hierarchical structure for evaluating IL-AITOM objects. At the top is 'Classification on intelligence level of AITOM' with five levels. Below it is the 'Selection model of evaluated object' with Service, Operation stage, and System granularity. The 'Evaluation dimensions' include Intent mapping, Data collection, Analysis, Decision, and Action implementation. These lead to 'Evaluation sub-dimensions' like Intent acquisition, Data processing, Resource analysis, Customer analysis, Policy generation, Policy judgement, System implementation, and Network element implementation. These sub-dimensions are linked to 'Evaluation tasks' (Task 1 to Task n). A vertical bar on the right shows the flow to 'Evaluation rating'. A legend at the bottom indicates orange boxes are from ITU-T M.3384 and blue boxes are from this recommendation. + +**Figure 7-1 – Evaluation framework of IL-AITOM** + +## 7.2 Evaluated object + +Referred to [ITU-T M.3384], the evaluated object of IL-AITOM is identified with three features namely: service, operation stage and system granularity. To refine evaluation granularity, the operation stages including planning and construction, operations readiness and support, fulfilment, assurance, billing and revenue are further expanded into multiple operation sub-stages. + +- a) Planning and construction includes but is not limited to the following sub-stages: + - i) Requirements assessment: the activities in this operation sub-stage are to understand, forecast and analyse cloud or network requirements. + - ii) Installation and deployment: the activities in this operation sub-stage are to import cloud or network design and complete deployment. + - iii) Configuration and test: the activities in this operation sub-stage are to complete cloud or network configuration, service test, etc. +- b) Operations readiness and support includes but is not limited to the following sub-stages: + - i) Process support: the activities in this operation sub-stage are to design a process for other operation stages. + - ii) Staff support: the activities in this operation sub-stage are to manage staff assignments for other operation stages. +- c) Fulfilment includes but is not limited to the following sub-stages: + - i) Service ordering: the activities in this operation sub-stage are to select customer services and place orders through different channels. + - ii) Service provision: the activities in this operation sub-stage are to complete automatic service configuration, activation and testing on completion. +- d) Assurance includes but is not limited to the following sub-stages: + - i) Troubleshooting: the activities in this operation sub-stage are to implement monitoring, diagnosis and analysis of network and service faults, deal with complaints, generate fault recovery solutions, etc. + +- ii) Quality optimization: the activities in this operation sub-stage are to implement monitoring of customer experience quality, service quality and network performance, analyse the deterioration issues, generate optimization solutions, etc. + - iii) Cutover maintenance: the activities in this operation sub-stage are to implement cutover, upgrade and maintenance operations for network equipment, pipeline resources or services. + - iv) Daily inspection: the activities in this operation sub-stage are to implement patrolling, and find and eliminate hidden trouble in a timely manner. +- e) Billing and revenue include but are not limited to the following sub-stages: +- i) Bill management: the activities in this operation sub-stage are to manage the bill process, manage the lifecycle of bills, and perform bill trend analysis. + - ii) Payment management: the activities in this operation sub-stage are to manage methods to make payments, manage payment plans, handle payments, and collect debt. + +## 7.3 Evaluation dimensions + +The five evaluation dimensions given in [ITU-T M.3384] create a complete closed-loop from the requirement to the realization, covering intent mapping, data collection, analysis, decision, and action implementation. + +## 7.4 Evaluation sub-dimensions + +Based on actual operation conditions, evaluation dimensions are recommended to be broken down into multiple sub-dimensions. An overview of evaluation dimensions and sub-dimensions is presented in Table 7-1. + +**Table 7-1 – Evaluation dimensions and sub-dimensions** + +| Evaluation dimensions | Evaluation sub-dimensions | Description | +|-----------------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Intent mapping | Intent acquisition | Obtain different sources, types and forms of intent | +| | Intent parsing | Parse the intent, get the parameters of the specific requirements | +| | Intent scheduling | Carry out the process scheduling according to intent | +| | Intent feedback | Feedback the results of the intent execution | +| Data collection | Data collection | Collect the corresponding data from the network side and system side | +| | Data processing | Simply process the collected data and verify necessary data | +| Analysis | Resource analysis | Perform the resource analysis according to the intent, such as verification and analysis of port resources, IP resources, bandwidth resources, etc. | +| | Service analysis | Perform end-to-end or segmented service analysis, such as service quality analysis, routing analysis, etc. | +| | Fault analysis | Perform fault analysis including root cause analysis, fault delimitation analysis, potential risk prediction analysis, etc. | +| | Customer analysis | Perform analysis on customer perception | +| Decision | Policy generation | Generate policy to meet the intent | +| | Policy verification | Verify the feasibility and effectiveness of the generated policy through simulations | + +**Table 7-1 – Evaluation dimensions and sub-dimensions** + +| Evaluation dimensions | Evaluation sub-dimensions | Description | +|------------------------------|----------------------------------|-------------------------------------------------| +| | Policy judgment | Judge whether to immediately execute the policy | +| Action implementation | Network element implementation | Execute the policy by network element system | +| | Operation system implementation | Execute the policy by operation system | + +## 7.5 Evaluation tasks + +Each evaluation task as a minimum evaluation unit is recommended to cover the following 6 attributions: + +- Service. +- Operation sub-stage. +- Evaluation dimension. +- Evaluation sub-dimension. +- Task descriptions which indispensably interpret the operational activity. +- System. + +Based on the above attributions, each evaluation task is defined atomically and distinctly. The principles for determining whole evaluation tasks are required to follow: + +- Independence: The granularity of each evaluation task is consistent and there is no repetition or intersection. All the evaluation tasks are independent and unique. +- Completeness: The evaluation tasks are required to cover all activities in the operation and management process. + +# 8 Evaluation rating method of IL-AITOM + +## 8.1 Criteria of evaluation task evaluation + +Referring to classification on intelligence levels of AITOM, the evaluation score of each evaluation task is required to range from 1 to 5. The detailed criteria used to classify the five levels are recommended to consider the AI applications provided by an AI engine: + +- To score 1: Operations are implemented manually and off-line based on existed templates or experience, the AITOM-followed system assists in recording the results. +- To score 2: The AITOM-followed system automatically implements operations based on the statically programmed rules. +- To score 3: The AITOM-followed system automatically implements operations based on the dynamically configurable policies. +- To score 4: The AITOM-followed system automatically implements operations based on flexibly intelligent policies that are assisted by AI engine. +- To score 5: The AITOM-followed system automatically implements operations based on self-evolution policies that are generated and iterated autonomously by AI engine. + +## 8.2 Evaluation rating method of evaluated object + +As evaluation dimensions, evaluation sub-dimensions and evaluation tasks have different levels of difficulty, importance and some potential factors, weight distribution is recommended to be taken into consideration. According to the evaluation criteria and weight, it takes the weighted summation to get aggregation results of evaluation tasks and this rating method is shown in Figure 8-1. + +![Figure 8-1: Evaluation rating method of evaluated object. The diagram shows a hierarchical aggregation process. On the left, four boxes represent the levels of evaluation: 'Evaluated object', 'Evaluation dimensions', 'Evaluation sub-dimensions', and 'Evaluation tasks'. Arrows point from each box to a corresponding level on the right. The right side shows a vertical stack of boxes: 'Final results' at the top, followed by 'Results and weights', 'Results and weights', and 'Scores and weights' at the bottom. Upward-pointing arrows between these boxes are labeled 'Summation', indicating the aggregation of scores and weights from lower levels to higher levels. The label 'M.3385(23)' is at the bottom right.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) + +Figure 8-1: Evaluation rating method of evaluated object. The diagram shows a hierarchical aggregation process. On the left, four boxes represent the levels of evaluation: 'Evaluated object', 'Evaluation dimensions', 'Evaluation sub-dimensions', and 'Evaluation tasks'. Arrows point from each box to a corresponding level on the right. The right side shows a vertical stack of boxes: 'Final results' at the top, followed by 'Results and weights', 'Results and weights', and 'Scores and weights' at the bottom. Upward-pointing arrows between these boxes are labeled 'Summation', indicating the aggregation of scores and weights from lower levels to higher levels. The label 'M.3385(23)' is at the bottom right. + +**Figure 8-1 – Evaluation rating method of evaluated object** + +The calculation method is described in Equation 8-1. + +$$L_o = \sum_{k=1}^n d_k \sum_{j=1}^{k,m} s_{k,j} \sum_{i=1}^{j,q} t_{j,i} S_i \quad (8-1)$$ + +Where: + +- $L_o$ Intelligence level of evaluated object +- $d_k$ Weight of $k_{th}$ evaluation dimension, $n$ denotes the number of evaluation dimensions +- $s_{k,j}$ Weight of $j_{th}$ evaluation sub-dimension of $k_{th}$ evaluation dimension, $m$ denotes the number of evaluation sub-dimensions +- $t_{j,i}$ Weight of $i_{th}$ evaluation task of $j_{th}$ evaluation sub-dimension, $q$ denotes the number of evaluation tasks +- $S_i$ The score of $i_{th}$ evaluation task +- $\sum$ Weighted summation notation. + +Finally, the overall evaluation rating method of IL-AITOM is presented in Figure 8-2, which includes the following 4 steps: + +- i) Identify the evaluated object with three features including service, operation stage and system granularity. +- ii) Determine evaluation dimensions, evaluation sub-dimensions, evaluation tasks and the weight of each. +- iii) Access the scores of all evaluation tasks based on evaluation criteria. +- iv) Aggregate the overall evaluation results according to the scores of evaluation tasks and weights. + +![Figure 8-2 – Evaluation rating method of IL-AITOM. This diagram illustrates the evaluation framework for IL-AITOM, showing the flow from the evaluated object to evaluation dimensions, tasks, and scores, with a feedback loop for rating methods.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +The diagram illustrates the evaluation rating method of IL-AITOM, structured into four main vertical columns and a bottom feedback section. + +- Evaluated object (Left Column):** This column is divided into three main sections: + - Service:** Includes Individual service, Home service, Enterprise service, and Internal service. + - Operation stage:** Subdivided into Planning and construction (Requirement assessment, Planning support, ...), Operations readiness and support (Process support, Staff support, ...), Fulfilment (Service ordering, Service provision, ...), Assurance (Troubleshooting, Quality optimization, ...), and Billing and revenue (Bill/invoice management, Payment management, ...). + - System granularity:** Includes Entire system, Function set, and Function block. +- Evaluation dimensions and sub-dimensions (Second Column):** This column lists five dimensions and their sub-dimensions: + - Intent mapping:** Intent acquisition, Intent parsing, Intent scheduling, Intent feedback. + - Data collection:** Data collection, Data processing. + - Analysis:** Customer analysis, Service analysis, Fault analysis, Customer analysis (repeated). + - Decision:** Policy generation, Policy verification, Policy judgement. + - Action implementation:** Network element implementation, System implementation. +- Evaluation tasks (Third Column):** This column lists five tasks corresponding to the dimensions: + - Service + - Operation sub-stage + - Evaluation dimension + - Evaluation sub-dimension + - Task description + - System +- Scores of evaluation tasks (Right Column):** This column shows five numbered boxes (1-5) representing scores, with the label "Evaluation criteria" at the bottom. + +Arrows indicate a sequential flow from left to right, with a plus sign (+) between the first and second columns. A large bracket groups the first four columns, pointing down to a bottom section. + +**Intelligence levels of evaluated object (Bottom Left):** A list of five levels (Level 1 to Level 5). + +**Evaluation rating method (Bottom Right):** A flow diagram showing "Summation" → "Results and weights" → "Summation" → "Scores and weights". + +**Legend:** + +- Orange box: First proposed in [ITU-T M.3384] +- Blue box: Proposed in this Recommendation + +Figure 8-2 – Evaluation rating method of IL-AITOM. This diagram illustrates the evaluation framework for IL-AITOM, showing the flow from the evaluated object to evaluation dimensions, tasks, and scores, with a feedback loop for rating methods. + +**Figure 8-2 – Evaluation rating method of IL-AITOM** + +# 9 Automatic evaluating process of IL-AITOM + +The automatic evaluating process comprises necessary orderly activities to implement automatic evaluating consisting of evaluation requirement input, evaluation session creation, evaluation session management, evaluation results management and evaluation report generation. These activities of the automatic evaluating process are shown in Figure 9-1. + +- Evaluation requirement input is responsible for importing evaluation requirements from an external system and identifying the evaluated object. The requirements can be in any form such as natural language or configuration files. +- Evaluation session creation is responsible for determining evaluation dimensions, evaluation sub-dimensions, evaluation tasks and the weight of each based on the results of the evaluation requirement input block and subsequently creating a session. +- Evaluation session management is responsible for the monitors distribution, session life circle management, session suspend and session termination. + +The monitors are distributed to AITOM-followed systems in line with the evaluated tasks. + +- Evaluation result management is responsible for the evaluation data collection, processing, analysis and evaluation results calculation. The multiple and numerous data is collected + +from monitors and evaluation results are then calculated based on the evaluation rating method. + +- Evaluation report generation is responsible for generating a visualized evaluation report to users which involves evaluated objects, evaluation dimensions, evaluation sub-dimensions, evaluation tasks, evaluation time and place, evaluation rating method and evaluation results. + +![Figure 9-1 – Automatic evaluating process of IL-AITOM. A complex architectural diagram showing the flow between an External System, Intelligence Level Classification, and the AITOM framework (comprising SOMM and AI Engine).](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +The diagram illustrates the automatic evaluating process of IL-AITOM. At the top, an **External system** interacts with the **Intelligence level classification** block via step ①. This block contains a sequence of five steps: **Evaluation requirement input** (connected to step ②), **Evaluation session creation**, **Evaluation session management** (connected to step ③), **Evaluation result management** (connected to step ④), and **Evaluation report generation** (connected to step ⑤). Step ⑤ also feeds back to the External system. + +Below this is the **AITOM** framework. It starts with a **Customer-oriented marketplace layer** containing 'Standardized capability directory' and 'Capability customization'. Underneath is the **SOMM** (Service Oriented Management) section, which is divided into four layers: + +- Scenario application layer**: Includes 'Smart operation', 'Smart management', 'Smart maintenance', 'Smart comprehensive analysis', and 'Traditional B-OSFs'. +- Management service layer**: Divided into a 'Service opening sub-layer' (Service directory, Service management) and a 'Service providing sub-layer' (SDN/NFV aware orchestration, Traditional S-OSFs, N-OSFs and E-OSFs). +- Data convergence and management layer**: Divided into a 'Data management sub-layer' (Data lifecycle management, Data security management) and a 'Data convergence sub-layer' (Data acquisition, Data processing, Data storage, Traditional N-OSFs and E-OSFs). +- Infrastructure management layer**: Includes 'Infrastructure maintenance' and 'Infrastructure monitoring'. + +To the right is the **AI engine**, containing: 'AI capabilities management', 'AI capability orchestration', 'AI sandbox training', 'Common AI model repository management', and 'Computing engine framework management'. + +The diagram uses several symbols and arrows: + +- Blue circles represent **Monitor** points located in various sub-layers. +- Blue dashed arrows represent **Examples of evaluation data collection** flowing from monitors in the SOMM layers to the 'Evaluation result management' and 'AI engine'. +- Red dashed arrows represent **Examples of monitor distribution** flowing from 'Evaluation session management' to various SOMM components. +- Large red curved arrows indicate **AI pipeline** flows between the AI engine and the SOMM layers. + +A legend at the bottom defines: ● Monitor; Blue dashed arrow: Examples of evaluation data collection; Red dashed arrow: Examples of monitor distribution. The reference M.3385(23) is in the bottom right corner. + +Figure 9-1 – Automatic evaluating process of IL-AITOM. A complex architectural diagram showing the flow between an External System, Intelligence Level Classification, and the AITOM framework (comprising SOMM and AI Engine). + +**Figure 9-1 – Automatic evaluating process of IL-AITOM** + +## Appendix I + +### An evaluation use case of intelligence levels about quality assurance capability for IMT-2020 and beyond network operation and management system + +(This appendix does not form an integral part of this Recommendation.) + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Evaluation of intelligence levels about quality assurance capability for IMT-2020 and beyond network operation and management system | +| Description | Scenario: quality assurance is a typical application of AITOM framework [ITU-T M.3080]. The AITOM-followed IMT-2020 and beyond network operation and management system supports the quality assurance for enterprise services. AI-based quality assurance technologies are applied in the assurance stage to ensure that services delivered to customers are continuously available and performing to service level agreement (SLA) or QoS performance levels. | +| Evaluation rating method | Referring to the evaluation rating method provided in clause 8.2, the final intelligence level of quality assurance for IMT-2020 and beyond network operation and management system is the weighted summation for all evaluation dimensions. The conducted evaluation method for quality assurance for IMT-2020 and beyond network operation and management system is shown as: | + +| | | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Title

|

Evaluation of intelligence levels about quality assurance capability for IMT-2020 and beyond network operation and management system

| +| |

Image: Flowchart of the evaluation process. It starts with 'Start', followed by 'Identify the evaluated object' (Entire system at operation stage which provide service for quality assurance), 'Determine dimensions, sub-dimensions and evaluation tasks' (Decomposing the evaluation at different levels), and 'Determine weights' (1) Compare the comparative importance to form the judgement matrix at evaluation task level, sub-dimension level, and dimension level, respectively). A dashed box contains 'Determine weights' (2) construct weights at evaluation task level, sub-dimension level and dimension level, respectively) and a decision diamond 'Determine weights' (3) Matrix is consistent). If 'Yes', it proceeds to 'Access intelligence level for evaluation tasks' (Identify the score for all quality assurance evaluation tasks based on evaluation criteria) and 'Aggregate intelligence level of evaluated object' (Aggregate final results of evaluated entire system based on determined weights and evaluation task scores), ending at 'End'. If 'No', it goes to 'Adjust the judgement matrix' and loops back to the first 'Determine weights' step.

 graph TD     Start([Start]) --> A["Identify the evaluated object:
Entire system at operation stage which
provide service for quality assurance"] A --> B["Determine dimensions, sub-dimensions
and evaluation tasks:

Decomposing the evaluation at different levels"] B --> C["Determine weights:
1) Compare the comparative importance to form
the judgement matrix at evaluation task level, sub-
dimension level, and dimension level, respectively"] C --> D subgraph DashedBox [ ] D["Determine weights:
2) construct weights at evaluation task level, sub-
dimension level and dimension level, respectively"] E{"Determine weights:
3) Matrix is consistent"} D --> E end E -- Yes --> F["Access intelligence level for evaluation tasks
Identify the score for all quality assurance
evaluation tasks based on evaluation criteria"] E -- No --> G["Adjust the judgement
matrix"] G --> C F --> H["Aggregate intelligence level of evaluated object
Aggregate final results of evaluated entire system
based on determined weights and evaluation task scores"] H --> I([End]) style DashedBox fill:none,stroke-dasharray: 5 5
| +|

Evaluated object

|

The AITOM-followed entire system of quality assurance for IMT-2020 and beyond network operation and management system includes related function sets of customer-oriented marketplace layer, smart operation maintenance and management (SOMM) comprising scenarios application layer, management service layer, data convergence and management layer and infrastructure management layer, and AI engine.

The evaluated object for IL-AITOM consists of:

Service: service for IMT-2020 and beyond network operation and management quality assurance

Operation stage: assurance – troubleshooting

System granularity: entire system

| + +M.3385(23) + +| | | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | Evaluation of intelligence levels about quality assurance capability for IMT-2020 and beyond network operation and management system | +| Determine evaluation dimensions, evaluation sub-dimensions and evaluation tasks |

The entire system aims to provide accurate perception of quality assurance, at the same time to improve system efficiency. The evaluation covering the process of monitoring and analysis various indicators of system operation, such as system scale, business logic, connectivity performance and frequency, so that the potential operation problems can be found and handled in a timely manner.

The determined evaluation dimensions and evaluation sub-dimensions are provided in Table 7-1 in clause 7.3.

The determined evaluation tasks are shown in Column "Evaluation task" of Table I.1.

| +| Determine weights |

The weights determination in this use case is based on the analytic hierarchy process (AHP) [b-Saaty]. For genericity, "factor" is used to represent different elements in each evaluation hierarchy level, i.e., dimension level, sub-dimension level and evaluation task level. For each level, the comparative importance for factor i and factor j is noted as a_{ij}, then the judgement matrix A is

$A(a_{ij})_{n \times n} = \begin{pmatrix} a_{11} & a_{12} & \cdots & a_{1n} \\ a_{21} & a_{22} & \cdots & a_{2n} \\ \vdots & \vdots & & \vdots \\ a_{n1} & a_{n2} & \cdots & a_{nn} \end{pmatrix}$

where n is the number of factors.

Taking geometrically average for the row vectors of matrix A, after normalisation, the weight w_i of factor i and eigenvector W can be obtained as

$w_i = \bar{W}_i / \sum_{i=1}^n \bar{W}_i, W = \begin{Bmatrix} w_1 \\ w_2 \\ \vdots \\ w_n \end{Bmatrix}$

To test the consistency of the judgement matrix, first calculate the max feature root \lambda_{\max} as

$\lambda_{\max} = \frac{1}{n} \sum_{i=1}^n \frac{(AW)_i}{w_i}$

then, the consistency index (CI) is:

$CI = \frac{\lambda_{\max} - n}{n - 1}$

The Consistency Ratio (CR) is

$CR = \frac{CI}{RI}$

where the statistical Random Index (RI) can be found in [b-Saaty].

If CR < 0.1, the consistency of matrix is satisfied, otherwise, the matrix needs to be adjusted.

The calculated weights for each dimension, sub-dimension and evaluation task are shown in Table I.2.

| +| Scores of evaluation tasks | Based on clause 8.1, the scores for evaluation tasks are shown in Table I.2. | +| Intelligence levels of evaluated object | Based on Equation (8-1) provided in clause 8.2, then intelligence level of evaluated object is calculated based on weights, scores of evaluation tasks in Table I.2. | + +**Table I.1 – Evaluation tasks** + +| Evaluation task | Service | Operation sub-stage | Evaluation dimension | Evaluation sub-dimension | System | Task description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------|-----------------------------|---------------------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Task 1:
Collection of intent based on customer side requirements | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Intent mapping | Intent acquisition | IMT-2020 and beyond network operation and management system | The enterprises can provide various services, such as Vehicle to everything assisted driving services, live video streaming services, cloud gaming services with IMT-2020 and beyond networks.
The collected intent from the enterprise side can be expected system operation status, including requirements, objectives or limitations of the system. | +| Task 2:
Based on collected intent information to extract network operation parameters or service performance indicators to ensure the service quality | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Intent mapping | Intent parsing | IMT-2020 and beyond network operation and management system | To fulfil services requirements, the network operation and management system should support low latency, high-definition video backhauling, super uplink rate, etc. The operation parameters and service performance indicators are extracted based on manual defined parsing policies, such as regular expression parsing, key-value parsing, separator parsing and so on. | +| Task 3:
Intent scheduling management to fulfil different scenario requirements | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Intent mapping | Intent scheduling | IMT-2020 and beyond network operation and management system | Based on priority of intents in different scenario, network conditions, taking system operation status into account, intents can be scheduled to perform intent management. | +| Task 4:
Performance feedback related with intent objectives, system/network performance and user experience | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Intent mapping | Intent feedback | IMT-2020 and beyond network operation and management system | Based on monitored network operation and management performance, feedback is provided in terms of intent scheduling impact/achievements, such as coverage of system operation, network feature data, business feature data, monitored KPIs and so on. | + +**Table I.1 – Evaluation tasks** + +| Evaluation task | Service | Operation sub-stage | Evaluation dimension | Evaluation sub-dimension | System | Task description | +|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------|-----------------------------|---------------------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Task 5:
System operation data collection | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Data collection | Data collection | IMT-2020 and beyond network operation and management system | System operation and management data can be collected from various sources, including network side, business side and system side.
The standard data collection methods can be formalised based on data features such as data volume, data format, generation frequency and so on. | +| Task 6:
Data cleaning, data storage, data correlation and so on | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Data collection | Data processing | IMT-2020 and beyond network operation and management system | Data pre-processing, data storage, and data association between network element alarms, network element performance alarms, service performance, and services linkage with network element performance alarms. | +| Task 7:
Resource analysis, such as verification and analysis of port resources, IP resources, bandwidth resources, etc | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Analysis | Resource analysis | IMT-2020 and beyond network operation and management system | Analysis for monitoring data of core network, wireless access network, other resources and their performance data, and alarm data. Analysis results including the resource utilization rate, abnormal information and so on. Resource analysis type including offline resource analysis, near real-time resource analysis, history resource usage analysis, energy saving analysis and so on. | +| Task 8:
End-to-end service analysis, such as service quality analysis, routing analysis, etc | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Analysis | Service analysis | IMT-2020 and beyond network operation and management system | Service analysis based on terminal data, user signalling data, connection quality data and end-to-end business assurance data. | +| Task 9:
Fault analysis for system operation | IMT-2020 and beyond network | assurance – troubleshooting | Analysis | Fault analysis | IMT-2020 and beyond network operation and | Discovery of failures that have occurred at network device/performance based on data such as alarms, performance, and configuration. Fault analysis including | + +**Table I.1 – Evaluation tasks** + +| Evaluation task | Service | Operation sub-stage | Evaluation dimension | Evaluation sub-dimension | System | Task description | +|--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------|-----------------------------|---------------------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | operation and management quality assurance | | | | management system | root cause analysis (e.g., coverage, interference, capacity, equipment, etc.), fault delimitation analysis, potential risk prediction analysis, etc. | +| Task 10:
Customer perception analysis | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Analysis | Customer analysis | IMT-2020 and beyond network operation and management system | Evaluation and analysis for user perception in terms of service quality, connection quality, business satisfaction and so on. | +| Task 11:
Policy generation for operation troubleshooting | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Decision | Policy generation | IMT-2020 and beyond network operation and management system | Generate operation troubleshooting policies (e.g., network configuration parameter adjustment, hardware restart, software re-boot/fall-back/upgrade, etc.) and required related actions (e.g., point-of-failure isolation scheme, etc.) | +| Task 12:
Verify the feasibility and effectiveness of the generated policy through simulations | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Decision | Policy verification | IMT-2020 and beyond network operation and management system | Execute potential troubleshooting rulesets in a sandbox environment to simulate impact of the potential troubleshooting policies and actions. | +| Task 13:
Decision for policy execution | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Decision | Policy judgment | IMT-2020 and beyond network operation and management system | Provide recommendations on troubleshooting policy selection based on sandbox simulation results. | + +**Table I.1 – Evaluation tasks** + +| Evaluation task | Service | Operation sub-stage | Evaluation dimension | Evaluation sub-dimension | System | Task description | +|---------------------------------------------------|------------------------------------------------------------------------|-----------------------------|-----------------------------|---------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------| +| Task 14:
Execute the policy by network element | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Action implementation | Network element implementation | IMT-2020 and beyond network operation and management system | Execute selected troubleshooting policy at one or more network elements. | +| Task 15:
Execute the policy by system | IMT-2020 and beyond network operation and management quality assurance | assurance – troubleshooting | Action implementation | System implementation | IMT-2020 and beyond network operation and management system | Execute the selected troubleshooting policy at system. | + +**Table I.2 – Weights and evaluation results** + +| Evaluation task | | | Evaluation sub-dimension | | | Evaluation dimension | | | Evaluation object | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------------------|---------------------------------|-------------------------------|-------------------|-----------------------------|---------------|----------------------------------------------|-------------------------------------------------| +| Name | Weight under sub-dimension | Score | Name | Weight under dimension | Result | Name | Weight | Result | Result | +| Task 1:
Collection of intent based on customer side requirements | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 3. | Intent acquisition | 0.39 | $3*0.39*1 = 1.17$ | Intent mapping | 0.10 | | | +| Task 2:
Based on collected intent information to extract network operation parameters or service performance indicators to ensure the service quality | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 2. | Intent parsing | 0.30 | $2*0.30*1 = 0.60$ | | | $(1.17 + 0.60 + 0.42 + 0.30) * 0.10 = 0.249$ | $0.249 + 1.04 + 1.728 + 0.2849 + 0.17 = 3.4719$ | +| Task 3:
Intent scheduling management to fulfil different scenario requirements | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 2. | Intent scheduling | 0.21 | $2*0.21*1 = 0.42$ | | | | | +| Task 4:
Performance feedback related with intent objectives, system/network performance and user experience | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 3. | Intent feedback | 0.10 | $3*0.10*1 = 0.30$ | | | | | + +**Table I.2 – Weights and evaluation results** + +| Evaluation task | | | Evaluation sub-dimension | | | Evaluation dimension | | | Evaluation object | | +|----------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------------------|---------------------------------|-------------------------------|-----------------|-----------------------------|---------------|--------------------------------------------|--------------------------|--| +| Name | Weight under sub-dimension | Score | Name | Weight under dimension | Result | Name | Weight | Result | Result | | +| Task 5:
System operation data collection | 1 | Based on the criteria of clause 8.1, the score of this task is 4. | Data collection | 0.5 | $4*0.5*1=2$ | Data collection | Weight: 0.26 | $(2+2)*0.26=1.04$ | | | +| Task 6:
Data cleaning, data storage, data correlation and so on. | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 4. | Data processing | 0.5 | $4*0.5*1=2$ | | | | | | +| Task 7:
Resource analysis, such as verification and analysis of port resources, IP resources, bandwidth resources, etc. | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 4. | Resource analysis | 0.21 | $4*0.21*1=0.84$ | Analysis | Weight: 0.48 | $(0.84 + 0.9 + 1.56 + 0.3) * 0.48 = 1.728$ | | | +| Task 8:
End-to-end service analysis, such as service quality analysis, routing analysis, etc | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 3. | Service analysis | 0.30 | $3*0.30*1=0.9$ | | | | | | + +**Table I.2 – Weights and evaluation results** + +| Evaluation task | | | Evaluation sub-dimension | | | Evaluation dimension | | | Evaluation object | +|---------------------------------------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------------------|---------------------------------|-------------------------------|-------------------|-----------------------------|---------------|----------------------------------------|--------------------------| +| Name | Weight under sub-dimension | Score | Name | Weight under dimension | Result | Name | Weight | Result | Result | +| Task 9:
Fault analysis for system operation | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 4. | Fault analysis | 0.39 | $4*0.39*1 = 1.56$ | Decision | Weight: 0.11 | $(1.77 + 0.68 + 0.14) * 0.11 = 0.2849$ | | +| Task 10:
Customer perception analysis | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 3. | Customer analysis | 0.10 | $3*0.10*1 = 0.3$ | | | | | +| Task 11:
Policy generation for operation troubleshooting | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 3. | Policy generation | 0.59 | $3*0.59*1 = 1.77$ | | | | | +| Task 12:
Verify the feasibility and effectiveness of the generated policy through simulations. | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 2. | Policy verification | 0.34 | $2*0.34*1 = 0.68$ | | | | | +| Task 13:
Decision for policy execution | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 2. | Policy judgment | 0.07 | $2*0.07*1 = 0.14$ | | | | | + +**Table I.2 – Weights and evaluation results** + +| Evaluation task | | | Evaluation sub-dimension | | | Evaluation dimension | | | Evaluation object | +|---------------------------------------------------|-----------------------------------|------------------------------------------------------------------------------|---------------------------------|-------------------------------|---------------------|-----------------------------|---------------|-----------------------------|--------------------------| +| Name | Weight under sub-dimension | Score | Name | Weight under dimension | Result | Name | Weight | Result | Result | +| Task 14:
Execute the policy by network element | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 4. | Network element implementation | 0.7 | $4 * 0.7 * 1 = 2.8$ | Action implementation | Weight: 0.05 | $(2.8 + 0.6) * 0.05 = 0.17$ | | +| Task 15:
Execute the policy by system | 1 | Based on the criteria of clause 8.1, the score of this evaluation task is 2. | System implementation | 0.3 | $2 * 0.3 * 1 = 0.6$ | | | | | + +## Bibliography + +- [b-ITU-T F.749.13] Recommendation ITU-T F.749.13 (2021), *Framework and requirements for civilian unmanned aerial vehicle flight control using artificial intelligence*. +- [b-ITU-T Y.3173] Recommendation ITU-T Y.3173 (2020), *Framework for evaluating intelligence levels of future networks including IMT-2020*. +- [b-3GPP TS 28.100] 3GPP TS 28.100 V17.1.0 (2022), *Levels of autonomous network*. +- [b-Saaty] Saaty T. *The analytic hierarchy process*. 1st ed. McGraw-Hill, New York; 1980. doi: 10.1002/ 0470011815.b2a4a002 +- [b-TM Forum IG1252] TM Forum IG1252 (2021), *Autonomous network levels evaluation methodology*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3387-202403-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3387-202403-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8b9892f78b0e2874841f59e03c0c4ce65b75bd1 --- /dev/null +++ b/marked/M/T-REC-M.3387-202403-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68790afd0434f832bc5db83cce6775355efa0d89785ad99324ab9ba72055239f +size 7145 diff --git a/marked/M/T-REC-M.3387-202403-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/M/T-REC-M.3387-202403-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a68c9bef5de4718dea4e10307e48180adb16d90 --- /dev/null +++ b/marked/M/T-REC-M.3387-202403-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8917628da30c8d2de8db5bbce623d51896ffe7ab53b70e05ce12aa0d2c57384c +size 174563 diff --git a/marked/M/T-REC-M.3387-202403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3387-202403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52731fdfd55fbf25e679975100bc94506accaceb --- /dev/null +++ b/marked/M/T-REC-M.3387-202403-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c78cc819caefe5a2224c941223357b2f631743d0d63882fa6774740964c38f1 +size 79346 diff --git a/marked/M/T-REC-M.3389-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3389-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3389-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3389-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3389-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d3463098cd90f3a0c866f44960db054f077ef17 --- /dev/null +++ b/marked/M/T-REC-M.3389-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:206d079d36aa7374492995c94d543740494cefb266abb7b954439674eea42cc1 +size 24923 diff --git a/marked/M/T-REC-M.3389-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3389-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e381b7b463ae4a55de5ee7a864254a6f432c52f --- /dev/null +++ b/marked/M/T-REC-M.3389-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92f56081ee940815bb7a2ea57db3e117601997fa477dce70e07460a1abf5d0ef +size 135490 diff --git a/marked/M/T-REC-M.3390-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3390-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3390-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3390-202503-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/M/T-REC-M.3390-202503-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77418789dd53c3a5088ca7d484d379f152aac5f2 --- /dev/null +++ b/marked/M/T-REC-M.3390-202503-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f885f7adc9f5a7f18e70824e8d495ade5e38abf1807b087b2df5f0de849a5634 +size 205224 diff --git a/marked/M/T-REC-M.3390-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3390-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f65a318bb38b27cf83a8343a7f2461dab2545262 --- /dev/null +++ b/marked/M/T-REC-M.3390-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17b86c21099e59853d14b05d61342b22cac1e73c95c3037290c0966bc769aaf +size 108624 diff --git a/marked/M/T-REC-M.3390-202503-I_PDF-E/raw.md b/marked/M/T-REC-M.3390-202503-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3f462fff41ef2b4e509a3ad46b98995b0b93bde5 --- /dev/null +++ b/marked/M/T-REC-M.3390-202503-I_PDF-E/raw.md @@ -0,0 +1,524 @@ + + +# Recommendation**ITU-T M.3390 (03/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **Requirements for smart comprehensive analysis within artificial intelligence enhanced telecom operation and management (AITOM)** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3390 + +# Requirements for smart comprehensive analysis within artificial intelligence enhanced telecom operation and management (AITOM) + +## Summary + +Recommendation ITU-T M.3390 proposes the requirements for smart comprehensive analysis within artificial intelligence enhanced telecom operation and management (AITOM), which includes network resource assurance analysis, network service quality analysis, End-to-End (E2E) service quality analysis, strategy generation of service quality assurance and other requirements. The goal of the Recommendation is to specify the requirements of using AI technology to achieve smart comprehensive analysis, focusing on service quality assurance, from the operation support system (OSS) level. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3390 | 2025-03-29 | 2 | 11.1002/1000/16283 | + +## Keywords + +Service quality assurance, smart comprehensive analysis. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|--------------------------------------------------------------------------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview ..... | 3 | +| 7 Requirements for smart comprehensive analysis within AITOM ..... | 4 | +| 7.1 Network resource assurance analysis ..... | 4 | +| 7.2 Network service quality analysis..... | 5 | +| 7.3 E2E service quality analysis..... | 7 | +| 7.4 Strategy generation of service quality assurance..... | 8 | +| 7.5 Other requirements ..... | 9 | +| Annex A – Implementation process of smart comprehensive analysis within AITOM ..... | 11 | +| Appendix I – A typical use case for smart comprehensive analysis within AITOM..... | 13 | +| I.1 End-to-end IMT-2020 network service quality assurance with root cause analysis of smart comprehensive analysis within AITOM..... | 13 | +| Bibliography..... | 15 | + + + +# Recommendation ITU-T M.3390 + +## Requirements for smart comprehensive analysis within artificial intelligence enhanced telecom operation and management (AITOM) + +# 1 Scope + +This Recommendation specifies the requirements for smart comprehensive analysis within artificial intelligence enhanced telecom operation and management (AITOM), which includes network resource assurance analysis, network service quality analysis, End-to-End (E2E) service quality analysis, strategy generation of service quality assurance and other requirements. The goal of the draft is to specify the requirements of using AI technology to achieve smart comprehensive analysis, focus on service quality assurance, from the operation support system (OSS) level. + +This Recommendation also considers the implementation process of smart comprehensive analysis within AITOM in Annex A, and a typical use case of smart comprehensive analysis within AITOM is provided in Appendix I. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +[ITU-T M.3080] Recommendation ITU-T M.3080 (2021), *Framework of AI enhanced Telecom Operation and Management (AITOM)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 artificial intelligence engine** [ITU-T M.3080]: The realization and mechanization, in software or hardware, of one or more functions dedicated to performing a specific artificial intelligence (AI) task. + +**3.1.2 artificial intelligence model** [ITU-T M.3080]: The model created by applying artificial intelligence (AI) technology to data to learn from. + +**3.1.3 artificial intelligence sandbox** [ITU-T M.3080]: An environment in which artificial intelligence (AI) models can be trained and tested, and their effects on the network are evaluated. + +**3.1.4 computing engine framework** [ITU-T M.3080]: A framework which provides an operation environment or coding resources in the context of artificial intelligence (AI)-based applications or developments. + +**3.1.5 functional block (in SDL)** [b-ITU-T Q.9]: A functional block is an object of manageable size and relevant internal relationship, containing one or more processes. + +**3.1.6 orchestration** [b-ITU-T Y.3100]: In the context of IMT-2020, the processes aiming at the automated arrangement, coordination, instantiation and use of network functions and resources for both physical and virtual infrastructures by optimization criteria. + +**3.1.7 service** [b-ITU-T M.3050.1]: Services are developed by a Service Provider for sale within Products. The same service may be included in multiple products, packaged differently, with different pricing, etc. + +**3.1.8 user** [b-ITU-T M.3010]: A person or process applying management services for the purpose of fulfilling management operations. + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|-------------------------------------------------------------------| +| AI | Artificial Intelligence | +| AITOM | Artificial Intelligence enhanced Telecom Operation and Management | +| BGP | Border Gateway Protocol | +| DPI | Deep Packet Inspection | +| E2E | End-to-End | +| IDC | Internet Data Centre | +| IFIT | In-situ Flow Information Telemetry | +| IGP | Internal Gateway Protocol | +| IMT-2020 | International Mobile Telecommunications for 2020 | +| NFV | Network Function Virtualization | +| OAM | Operations, Administration and Maintenance | +| OPEX | Operating Expense | +| OSS | Operation Support System | +| SLA | Service Level Agreement | +| SRv6 | Segment Routing IPv6 | +| VPN | Virtual Private Network | + +# **5 Conventions** + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "can optionally" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor can optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Overview + +With the rapid development of network scale, telecom operation management becomes more complex. Improving the quality of network operation to enhance the perception of users is a key focus of network operation and management. Network operation assurance is the main stage of network operation management. By analysing, diagnosing, and predicting network quality in operation management system, network problems can be detected in time, and network performance can be improved. Single network side analysis has some limitations. It needs to integrate network data, service data and user data from different sources, to achieve cross-professional, cross-domain E2E network big data analysis. + +![Functional framework of AITOM in [ITU-T M.3390]](562f471e8153729557e6a4ee6343c32c_img.jpg) + +The diagram illustrates the functional framework of AITOM, organized into several layers: + +- AITOM** (Top level): + - Customer-oriented marketplace layer**: Includes **Standardized capability directory** and **Capability customization**. +- SOMM** (Second level): + - Scenario application layer**: Contains **Smart operation**, **Smart management**, **Smart maintenance**, **Smart comprehensive analysis** (highlighted with a red box), and **Traditional B-OSFs**. + - Management service layer**: Divided into **Service opening sub-layer** (with **Service directory** and **Service management**) and **Service providing sub-layer** (with **SDN/NFV aware orchestration** and **Traditional S-OSFs, N-OSFs and E-OSFs**). + - Data convergence and management layer**: Divided into **Data management sub-layer** (with **Data lifecycle management** and **Data security management**) and **Data convergence sub-layer** (with **Data acquisition**, **Data processing**, **Data storage**, and **Traditional N-OSFs and E-OSFs**). + - Infrastructure management layer**: Contains **Infrastructure maintenance** and **Infrastructure monitoring**. +- AI engine** (Right side): + - Contains **AI capabilities management**, **AI capability orchestration**, **AI sandbox training**, **Common AI model repository management**, and **Computing engine framework management**. + - Two red curved arrows labeled **AI pipeline** connect the **AI engine** components to the **Scenario application layer** and the **Data convergence sub-layer**. + +Below the SOMM layers, a dashed oval represents the **Network** layer. + +M.3390(25) + +Functional framework of AITOM in [ITU-T M.3390] + +**Figure 6-1 – Functional framework of AITOM in [ITU-T M.3390]** + +As shown in Figure 6-1, smart comprehensive analysis is a typical application scenario in AITOM framework. The goal of the Recommendation is to specify the requirements of using AI technology to achieve smart comprehensive analysis, with a focus on service quality assurance, at the OSS level. Through AI-based service quality assurance analysis, network operators can more efficiently implement network assurance services and further improve the utilization of network resources, thereby reducing the OPEX. + +The smart comprehensive analysis includes: + +- 1) Network resource assurance analysis: It analyses if network resources can meet the requirements of critical business operations, including topology analysis and routing analysis. +- 2) Network service quality analysis: It analyses if the services and businesses provided over the network can meet the predetermined performance and reliability standards, thereby ensuring users receive a good experience and service level, including network traffic analysis and network path analysis. +- 3) E2E service quality analysis: It monitors and analyses the data transmission performance from source to destination within the network to ensure smooth business operations and meet the required quality of service. +- 4) Service quality assurance strategy generation: It generates service quality assurance strategy based on analysis results of service quality assurance, including network bandwidth optimization and network path optimization. + +# **7 Requirements for smart comprehensive analysis within AITOM** + +## **7.1 Network resource assurance analysis** + +### **7.1.1 Topology analysis** + +It is necessary to analyse both the physical topology and logical topology, and to establish formulate rules such as storage cycle and storage time. The following requirements should be followed in topology analysis. + +- It is required to collect and update topology and connection information of physical network components, such as core network elements, access network elements, carrier network elements, NFV, IDC and cloud, etc. +- It is required to collect network resource and traffic information to generate and update topology strategy to support network resource usage optimisation and ensure E2E service quality assurance for scenarios such as networking slicing and edge cloud computing, etc. +- It is required to support topology planning and optimisation strategy for network resource based on network capacity, node operation status, connection frequency, service requirements and so on. +- It is required to enable topology-based network resource management, including resource order management, resource audit, resource configuration and cutover, etc. +- It is required to support network event configuration and connection configuration based on resource topology analysis, such as hidden risks discover for network resource, network fault demarcation and location. +- It is recommended to enable digital twin visualization and configuration of network physical topology together with network node geographic information, operation and statistical data, e.g., alarm overlay, interface performance display, available-zone terminal link performance, etc. + +### **7.1.2 Routing analysis** + +It is necessary to perform multi-dimensional analysis on routing protocol such as IGP and BGP to detect route flapping in a timely manner and provide early warnings. The following requirements should be followed in routing analysis. + +- It is required to enable smart routing management and optimisation based on changes in physical and/or logical topology and service quality requirements. + +- It is required to support routing prediction analysis, particularly for cross-domain E2E services, to enable generation of network resource adjustment and optimization strategies. +- It is required to support routing statistical analysis based on automatically collected data, e.g., protocol type information, routing information table and so on. +- It is recommended to analyse the performance of network routing, including indicators such as router forwarding speed, delay, packet loss rate, in order to optimize network routing performance. +- It can optionally optimize the routing policy based on the actual situation of the network, such as adjusting the connection relationship between routers, in order to improve the performance and reliability of the network. + +## 7.2 Network service quality analysis + +### 7.2.1 Network traffic analysis + +Reasonable network design optimization requires forecasting of traffic changes in advance. The correlation between services and traffic flows should be considered to further improve the prediction accuracy. The following requirements should be followed in network traffic analysis. + +- It is required to have traffic prediction capability for different services, such as VPN and IMT-2020 dedicated lines. +- It is required to determine the traffic prediction value in the period to be predicted based on the historical traffic value of the same period. +- It is required to consider network traffic prediction for network bandwidth adjustment, and adjust the bandwidth according to the peak traffic data of the period to be predicted. The process of network traffic prediction includes: + - Obtain the peak traffic data of each unit period in the predetermined time interval. + - Classify peak traffic data into busy hour data peak traffic data and idle hour data peak traffic data. + - Select a plurality of prediction algorithms to form a candidate prediction algorithm set. + - Calculate the prediction result according to the peak traffic data and the prediction algorithm, and calculate the traffic deviation rate for the prediction algorithm according to the actual value of the historical period and the prediction result of the corresponding historical period. + - Determine the traffic deviation value of the period to be predicted according to the traffic deviation value of the historical period. + - Calculate the traffic value of the period to be predicted according to the peak traffic data of the period to be predicted and the traffic deviation rate of the period to be predicted. + - Compare the prediction intervals of different prediction algorithms with the actual values, calculate the average interval accuracy, and use the prediction algorithm with the highest average interval accuracy as the traffic prediction algorithm. +- It is recommended to have the capability of multiple AI prediction algorithms models in order to enable multi-model integration. +- It is recommended to classify the service type based on the service traffic, and associate it with E2E configuration data and performance data based on the source IP address and the destination IP address in the IP quintuple. + +### 7.2.2 Network path analysis + +Based on the traffic and fault conditions of the entire network, the path calculation function of path management is invoked to formulate the best path adjustment or optimization strategy. The following requirements should be followed in network path analysis. + +- It is required to obtain the original traffic data for the original network path and the alternative traffic data of the alternative network path, and overlay the traffic of the original network path in the alternative network path to get the superimposed traffic. The process includes: + - Obtain the original network path data and the alternative network path data, and the two types of data are processed by data cleaning to obtain the cleaned original and alternative data. + - The cleaned original and alternative data are calculated to get the original and alternative data features (such as delay, packet loss rate, bandwidth load, etc.), and the original data features and the original network path data (such as SLA delay, SLA packet loss rate, etc.) are compared to get the results of data comparison. + - If the data comparison result is that the original data does not satisfy the original path data, the original network path anomaly is determined, and the original traffic data in the original path data and the alternative traffic data in the alternative path data are obtained. And obtain the original traffic data in the original path data and the alternative traffic data in the alternative path data. + - Compare the message type of original network path and alternative network path, if the same, service traffic can be stacked directly, if different, service traffic need to be recalculated based on the number and length of data packets. +- It is required to obtain the network path data of the alternative network path and process the superimposed traffic data and network path data to get the path evaluation data. The process includes: + - Obtain the network path data in the alternative path data. + - Evaluate the traffic data and the network path data to obtain the network assessment data. + - Get the historical prediction data of the current time stamp and the alternative network path. + - Use the current time stamp and the historical prediction data to predict the time delay to get the target prediction data, to determine the network evaluation data and target forecast data for the path evaluation data. +- It is required to acquire the network preference data (such as packet loss rate, delay, bandwidth load) corresponding to the path evaluation data. Then, process the path recommendation data and the network preference data, to determine the optimal alternative path for the original network path in the alternative network path. The process includes: + - Clean the alternative network path data to obtain the cleaned alternative data, and the cleaned alternative data is calculated to get the alternative data features (such as Delay, packet loss rate, bandwidth load, etc.) + - Obtain feature threshold data in the alternative cleaning data, and obtain the alternative comparison results by comparing the alternative feature data and the feature threshold data. + - Standardize the network path evaluation results to obtain standard evaluation data. + - Process the standard evaluation data and network preference data to get the path recommendation parameters corresponding to the alternative network path. + +- Identify the recommendation degree based on the path recommendation parameters to determine the optimal alternative path of the original network path in the alternative network path. + +## 7.3 E2E service quality analysis + +In specific E2E application scenarios, customer services may experience a surge in traffic, resulting in link congestion or interruption, and deterioration of customer SLA indicators, affecting customer perception. The following requirements should be followed in E2E service quality analysis. + +- It is required to combine service quality assurance technology with customer SLA and network traffic congestion analysis to achieve network-wide SRv6 service quality assurance. The service quality assurance technology process includes: + - Obtain the E2E in-band telemetry performance index data and port data of the target service in the current acquisition cycle. + - Perform E2E service quality classification and evaluation processing on the E2E in-band telemetry performance index data and port data of the target service within the collection period, and obtain E2E service quality results. + - Obtain the in-band telemetry performance index data and port data of each hop-by-hop link of the target service in the current collection period, if the E2E service quality result is poor or interruption. + - Perform hop-by-hop link quality classification and evaluation processing on the in-band telemetry performance index data and port data of each hop-by-hop link of the target service in the current collection period, and obtain each hop-by-hop link service quality results. + - Locate the faulty link of the target service within the collection period according to the hop-by-hop link service quality results of each hop-by-hop link. +- It is required to consider assessing the quality of E2E network service in the same traffic direction. The network service quality assessment method process includes: + - Obtain an E2E network IP quintuple performance data, and service data. + - Determine the network traffic flow direction based on the source IP address and the destination IP address in the IP quintuple. + - Classify the service according to the network traffic flow direction and the performance data, and if the service type is the same, the network traffic in the same flow direction and similar performance. + - Classify the free time and busy time based on the performance data and time characteristics of the same type of service. + - Determine whether there is historical label data for business quality. If there is historical tag data of service quality, use performance data and historical tag data of service quality to evaluate the service quality of the same network traffic flow direction and get the evaluation result, the assessment results are normal or of poor quality. Otherwise, the traffic quality of the same network flow direction is evaluated based on the pre-set evaluation rules combined with the SLA performance data +- It is recommended to intelligently predict the E2E service quality for the next moment, and send timely abnormal early warning notifications, so as to identify and resolve issues in advance. +- It is recommended to diagnose and analyse the reason of abnormal network service quality and locate the fault intelligently. + +## 7.4 Strategy generation of service quality assurance + +### 7.4.1 Network bandwidth adjustment + +Before performing dynamic bandwidth adjustment of the network, it is required to formulate bandwidth adjustment and optimization strategies based on the results of dynamic traffic interval prediction. The following requirements should be followed in network bandwidth adjustment. + +- It is required to compare and analyse the network traffic interval prediction result with the current bandwidth to generate the corresponding dynamic bandwidth adjustment strategy of the network. +- It is required to recalculate the route and plan a new path, if the bandwidth adjustment still cannot guarantee the service requirements of users. +- It is required to monitor network traffic data in real-time, including the volume of incoming and outgoing data, as well as information on data transmission speed and latency, in order to facilitate intelligent adjustments. +- It is required to possess self-learning and optimization capabilities, being able to continuously refine adjustment strategies based on network traffic fluctuations and the effects of bandwidth adjustments, thereby enhancing the utilization and efficiency of network bandwidth. +- It is required to have flexible configuration and management features, allowing for personalized bandwidth adjustment strategy settings and management according to different business and user requirements, while also providing convenient monitoring and reporting functions for network administrators to facilitate network management and optimization. +- It can optionally analyse bandwidth limit or traffic limit based on business demand and traffic peak, to ensure that each device or user does not use excessive bandwidth resources. + +### 7.4.2 Network path optimization + +Network path optimization is required to be triggered based on network operating status or changes in latency, packet loss, and congestion indicators. Conditions for triggering path optimization calculation conditions is required to be set. After network path optimization calculation, the policy execution is required to be carried out either through manual confirmation or automatic execution. The following requirements should be followed in network path optimization. + +- It is required to obtain results data of network path evaluation analysis to achieve optimal network path recommendation for services. +- It is required to comprehensively consider customer SLA requirements in the process of optimal path recommendation. +- It is recommended to determine the target alternative network path according to the traffic congestion of each alternative network path in the future time and SLA risk assessment. +- It is required to identify the shortest candidate alternative network path as the target alternative network path when there are multiple candidate alternative network paths. +- It is recommended to store and analyse historical network path data in order to predict future network trends and potential issues, thereby optimizing path adjustment strategies. +- It is recommended to provide an intuitive user interface that displays the status and adjustment of network paths, as well as detailed reports to assist administrators in making decisions and diagnosing problems. +- It can optionally change the network transport path by using the routing protocol analysis to automatically discover and maintain the network router paths. +- It can optionally change the network transmission path through load balancing analysis to ensure a more even distribution of traffic. + +## 7.5 Other requirements + +### 7.5.1 Data acquisition and data storage + +The data for smart comprehensive analysis includes cross-domain network data, service data and user data from different sources. The following requirements should be followed in the data acquisition. + +- It is required to collect network data, service data (such as service type data) and user data (such as user order data) from multiple domains. Among them, network data includes network performance data (e.g., link bandwidth, link utilization, link delay, resource utilization), network operational data (e.g., network traffic, network topology, alarms, logs), network management data (network fault data, O&M work order, signalling) and so on. +- It is recommended to collect E2E network configuration data (including IP quintuple, AS domain, link information data and time feature data) and performance data based on IFIT technology. + +NOTE 1 – IP quintuple includes source IP address, source port, destination IP address, destination port, and transport layer protocol. + +NOTE 2 – performance data includes incoming traffic, outgoing traffic, packet loss rate, one-way delay, two-way delay, bandwidth, bandwidth load and jitter. + +- It is recommended to collect service traffic data based on NetFlow and DPI technology. +- It is recommended to collect user data to analysis behaviour of users, such as what services are frequently visited by users, to recommend optimal strategies. + +After collection, the data need to be stored in the database, and the following requirements should be followed for each database to storage and manage data. + +- It is required to storage data from different sources uniformly. Consistent data format, classified storage for different data and reasonable storage period are recommended to be considered. +- It is recommended to update and synchronize data regularly or in real time to ensure data accuracy and real-time. +- It is recommended to select the appropriate database system for data storage, such as relational database (such as MySQL, Oracle, etc.), non-relational database (such as MongoDB, Redis, etc.). +- It is recommended to design appropriate data tables according to the data structure and relationship to improve the efficiency of data query and access. + +### 7.5.2 Data processing and feature data pre-processing + +Data processing and feature data pre-processing can be handled according to different application scenarios to enhance the data and features of AI models. The following requirements should be followed in data processing. + +- It is required to consider the raw data parsing to extract data fields, e.g., regular expression parsing, key-value parsing, separator parsing and so on. +- It is required to support data format conversion, such as conversion of data encoding, conversion of data units, and so on. +- It is required to enable data cleaning, missing value handling, unit consistency, outlier handling and so on during data processing. + +The following requirements should be followed in feature data pre-processing. + +- It is required to consider feature data selection, feature data addition, feature data normalization or standardization and feature extraction based on the specific application scenario of service quality assurance analysis and strategy generation within AITOM. + +- It is required to carry out time feature data processing based on service quality assurance analysis requirements, such as time feature classification of free time and busy time. +- It is required to enable catalogue management for feature data based on application scenarios. +NOTE – Catalogue management for feature data refers to a set of information which can reflect key features of a typical application scenario. For example, the feature data for alarm including but not limited to network element ID, alarm code, generation time, and recovery time. +- It is required to enable data dimensionality reduction based on feature data. +- It is required to have the capability of spatiotemporal correlation analysis in order to extract spatiotemporal characteristics of traffic data. +- It is recommended to standardize the feature data to make the data between [0,1]. +- It can optionally consider processing large datasets, including distributed processing, parallel computing, and so on. + +### 7.5.3 Service quality assurance models repository management + +Service quality assurance models repository management provides service quality assurance models, such as anomaly detection, fault diagnosis, fault self-healing, and fault prediction. The following requirements should be followed in service quality assurance models repository management. + +- It is required to supports various repositories formats for model access management, model storage and version management, model configuration management. The repositories format can be proxy repositories, hosted repositories, repository groups and so on. +- It is required to support management for model operations, e.g., search, order, sort, import, modify, delete and so on. +- It is required to support navigation of service quality assurance models to build operation & management services from scenarios such as fault discovery, diagnosis, self-healing, and prediction, as well as intelligent question & answer and capacity planning. +- It is required to support for updating and replacing models, including uploading new model versions, replacing old model versions, and so on. +- It is required to reference "AI sandbox training" of clause 8.2.4 in [ITU-T M.3080], including common AI model selection, offline training and model decision. +- It is required to reference the functions of common AI model repository management of [ITU-T M.3080], including data analysis model management, machine learning model management and deep learning model management. +- It is required to include the functions of computing engine framework management of [ITU-T M.3080], including provision of open-source framework tools management, provision of partner tools management and provision of self-developed tools management. +- It is recommended to support model compression according to user-defined parameters, e.g., model quantification, distillation, pruning and so on. + +# Annex A + +## Implementation process of smart comprehensive analysis within AITOM + +(This annex forms an integral part of this Recommendation.) + +The implementation process of smart comprehensive analysis within AITOM is shown in Figure A.1, which includes the whole process from data acquisition to network application or system application. + +![Figure A.1: Implementation process of smart comprehensive analysis within AITOM. The diagram illustrates a 7-step process. Step 1: Data acquisition from Network and Resource management system/... (Network data/SLA data). Step 2: Data storage. Step 3: Data processing. Step 4: Data processing to AI engine. Step 5: AI engine to Smart comprehensive analysis (specifically Network service quality analysis). Step 6: Smart comprehensive analysis (Strategy generation of service quality assurance and Network resource assurance analysis) to Data acquisition. Step 7: Smart comprehensive analysis to Service directory, Other systems, and Standardized capability directory. The Smart comprehensive analysis block contains Strategy generation of service quality assurance (Network bandwidth adjustment, Network path adjustment) and Network resource assurance analysis (Topology analysis, Routing analysis, Network service quality analysis, E2E service quality analysis).](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +graph TD + subgraph Step1_4 [Steps 1-4] + direction LR + S1[Data acquisition] -- "Step 2" --> S2[Data storage] + S2 -- "Step 3" --> S3[Data processing] + S3 -- "Step 4" --> S4[AI engine] + end + S1 -- "Step 1: Network data/SLA data" --> Network((Network)) + S1 -- "Step 1: Network data/SLA data" --> RMS[Resource management system/...] + S4 -- "Step 5" --> SCA[Smart comprehensive analysis] + subgraph SCA [Smart comprehensive analysis] + direction TB + subgraph SCA_L [Strategy generation of service quality assurance] + SCA_L1[Network bandwidth adjustment] + SCA_L2[Network path adjustment] + end + subgraph SCA_R [Network resource assurance analysis] + SCA_R1[Topology analysis] + SCA_R2[Routing analysis] + SCA_R3[Network service quality analysis] + SCA_R4[E2E service quality analysis] + end + SCA_R -- "Step 6" --> SCA_L + end + SCA -- "Step 7" --> SD[Service directory] + SCA -- "Step 7" --> OS[Other systems] + SCA -- "Step 7" --> SC[Standardized capability directory] + SCA -- "Step 7: Network optimization strategies" --> Network +``` + +Figure A.1: Implementation process of smart comprehensive analysis within AITOM. The diagram illustrates a 7-step process. Step 1: Data acquisition from Network and Resource management system/... (Network data/SLA data). Step 2: Data storage. Step 3: Data processing. Step 4: Data processing to AI engine. Step 5: AI engine to Smart comprehensive analysis (specifically Network service quality analysis). Step 6: Smart comprehensive analysis (Strategy generation of service quality assurance and Network resource assurance analysis) to Data acquisition. Step 7: Smart comprehensive analysis to Service directory, Other systems, and Standardized capability directory. The Smart comprehensive analysis block contains Strategy generation of service quality assurance (Network bandwidth adjustment, Network path adjustment) and Network resource assurance analysis (Topology analysis, Routing analysis, Network service quality analysis, E2E service quality analysis). + +M.3390(25) + +**Figure A.1 – Implementation process of smart comprehensive analysis within AITOM** + +The implementation steps of smart comprehensive analysis within AITOM includes: + +**Step 1:** Collect network data or SLA data in "Data acquisition block" from network and resource management system or other management system. + +**Step 2:** Storage network data or SLA data from "Data acquisition block" and provides data for the "Data processing" to process. + +**Step 3:** Clean or tag the stored network data or SLA data in "Data processing block". + +**Step 4:** Prepare the pre-processed offline feature data for training AI model and online feature data for generating AI-based service quality assurance strategy to train, store and manage different service quality assurance models in "AI Engine". + +**Step 5:** Perform network resource assurance analysis, network service quality analysis or E2E service quality analysis based on the models from "AI Engine". + +**Step 6:** Generates network bandwidth optimization strategy or network path optimization strategy based on the analysis results. + +**Step 7:** Send the strategy to the network to optimize the network, and it also will be stored in service directory and standardized capability directory to be used by AITOM-based systems or other systems. + +NOTE 1 – The two-way arrows in Figure A.1 represent feedback capabilities, such as the feedback on usage status, model parameter optimization, etc. + +NOTE 2 – The functions about service directory and standardized capability directory are defined in [ITU-T M.3080], so they are not defined again in this Recommendation. + +# Appendix I + +## A typical use case for smart comprehensive analysis within AITOM + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 End-to-end IMT-2020 network service quality assurance with root cause analysis of smart comprehensive analysis within AITOM + +| | | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | End-to-end IMT-2020 network service quality assurance with root cause analysis of smart comprehensive analysis within AITOM | +| Description |

Smart comprehensive analysis within AITOM provides end-to-end IMT-2020 network service quality assurance with capabilities such as abnormal detection, root cause analysis, alarm prediction and fault self-healing to improve network operation efficiency.

Especially, AI capabilities can be used in mining, analysing, learning and training root cause analysis rules based on large amount of historical data and end-to-end network topology. The real-time alarms can be handled according to RCA rules to obtain root cause alarms. For a given alarm, the time duration to identify the root cause of the alarm based on the alarm correlation analysis can be shorten to less than 10 minutes with AI enhancement.

The process to realize end-to-end IMT-2020 network service quality assurance with root cause analysis of smart comprehensive analysis within AITOM is as follows:

  1. 1) Collect network data in data acquisition block, such as network traffic, network topology, resource utilization, delay, alarms, logs, O&M work tickets, signalling and so on.
  2. 2) Aggregate historical data in data acquisition block or data storage block and perform data processing with the aim of overseeing the networking and operation environments.
  3. 3) Extract feature data to support generation of models for network operation status, network traffic and services performance in feature data pre-processing block. The generated models will be managed via service quality assurance model repository management block.
    NOTE 1 – Service quality assurance models will be helpful to locate root cause alarms and support alarm convergence and compression, alleviate alarm storms, and improve the accuracy of dispatch rate.
  4. 4) Detect abnormal indicators which may reflect potential faults and failures by comparing the collected data with historical records, required performance based on SLA and QoS requirements in Analysis of service quality assurance block.
    NOTE 2 – With AI, the traditional static threshold detection methods can be upgraded with regression, classification or correlation models, such as linear regression, random forests, decision tree and spatiotemporal correlation analysis, etc., to intelligently discover and sent alarm once the abnormal fluctuations are detected.
  5. 5) Conduct root cause analysis (RCA) to diagnose the problem by automatically discovering potential alarm master-slave relationships and generating alarm relationship rules in analysis of service quality assurance block.
    NOTE 3 – This type of diagnosis can be applied in various situations, such as business alarms, network failures, base station service alarm, call chain failure, multi-indicator correlation and database disconnection.
  6. 6) Perform hop-by-hop service quality analysis to predict potential impact of the identified root cause of the alarm in analysis of service quality assurance block. If the impact or damage exceed the configured threshold, an optimal self-healing strategy will be generated automatically to avoid potential connection interruption.
| + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Title | End-to-end IMT-2020 network service quality assurance with root cause analysis of smart comprehensive analysis within AITOM | +| |

NOTE 4 – Machine learning algorithms can be used for prediction and analysis the state of network traffic flows, QoS and SLA requirements with flexible resource configuration in different network domains (e.g., radio access network, core network, transport network), resource topology and routing strategies.

7) Generate network path adjustment strategy to ensure service quality assurance in strategy generation of service quality assurance block. List available paths which can met the service requirements under the current network status constraints (such as activation time, bandwidth, traffic and resource deployment location, etc.). Manual confirmation and execution of faults resume operations.

NOTE 5 – AI models are applied to automatically generate applicable stop-loss and self-healing strategies, such as pre-arranged processing flows and operations based on identified risks and operation status, based on identified specified O&M scenario. Manual confirmation and execution of faults resume operations.

| +| Roles | OAM engineer, Communication service provider | +| Figure (optional) |

Image: Flowchart of the service quality assurance process. It consists of seven blocks: 1. Data acquisition block (Collect network data), 2. Data acquisition block or data storage block (Aggregate and process collected data to oversee networking and operation environments), 3. Feature data preprocessing block (Extract feature data to generate different service quality assurance models), 4. Analysis of service quality assurance block (Detect abnormal indicators of potential faults and failures), 5. Analysis of service quality assurance block (Conduct root cause analysis (RCA) to diagnosis the problem), 6. Analysis of service quality assurance block (Perform hop-by-hop service quality analysis to predict potential impact of the identified root cause of the alarm), and 7. Strategy generation of service quality assurance block (Generate network path adjustment strategy to ensure service quality assurance. Then, manual confirmation and execution of faults resume operations). The flow is: 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> 7.

 graph TD     1[1. Data acquisition block:
Collect network data] --> 2[2. Data acquisition block or data storage block:
Aggregate and process collected data to oversee networking and operation environments] 2 --> 3[3. Feature data preprocessing block:
Extract feature data to generate different service quality assurance models] 2 --> 4[4. Analysis of service quality assurance block:
Detect abnormal indicators of potential faults and failures] 3 --> 5[5. Analysis of service quality assurance block:
Conduct root cause analysis (RCA) to diagnosis the problem] 4 --> 5 5 --> 6[6. Analysis of service quality assurance block:
Perform hop-by-hop service quality analysis to predict potential impact of the identified root cause of the alarm] 6 --> 7[7. Strategy generation of service quality assurance block:
Generate network path adjustment strategy to ensure service quality assurance. Then, manual confirmation and execution of faults resume operations]

M.3390(25)

| +| Pre-conditions (optional) | Network data are collected from network operation management and resource management systems. | +| Post-conditions (optional) | Optimal network path adjustment is executed and performed. | +| Derived requirements | All requirements take clause 7 as the basis. | + +NOTE – The use case table template is based on [b-ITU-T M.3381]. + +# Bibliography + +- [b-ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [b-ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) – The business process framework*. +- [b-ITU-T M.3381] Recommendation ITU-T M.3381 (2022), *Requirements for energy saving management of 5G radio access network (RAN) systems with artificial intelligence (AI)*. +- [b-ITU-T Q.9] Recommendation ITU-T Q.9 (1990), *Vocabulary of switching and signalling terms*. +- [b-ITU-T Y.3100] Recommendation ITU-T Y.3100 (2017), *Terms and definitions for IMT-2020 network*. + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3391-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3391-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3391-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3391-202503-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/M/T-REC-M.3391-202503-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfcb77fab0e2a2141a89f959bc0d63979229d6aa --- /dev/null +++ b/marked/M/T-REC-M.3391-202503-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c5ecb8187e67399efc34997439fd0e209750000ec53412e48a63f0d35ec575 +size 84935 diff --git a/marked/M/T-REC-M.3391-202503-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/M/T-REC-M.3391-202503-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4623785ae645aebee50d927cdc0f6b1af52d5be7 --- /dev/null +++ b/marked/M/T-REC-M.3391-202503-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09e3f42843365b928cacde3cf9b123abbf44a3fa25ff73c3cb40e73d53c1c8e3 +size 30388 diff --git a/marked/M/T-REC-M.3393-202510-I_PDF-E/1298f18cf995a7a0e2f4555ff628ef38_img.jpg b/marked/M/T-REC-M.3393-202510-I_PDF-E/1298f18cf995a7a0e2f4555ff628ef38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f8a369d79aca76975837cb508a4be5265f7d2b3 --- /dev/null +++ b/marked/M/T-REC-M.3393-202510-I_PDF-E/1298f18cf995a7a0e2f4555ff628ef38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd011f52aa7dc8fa260216396794c7ef4e9217faa63e51102023ad82617a57df +size 32359 diff --git a/marked/M/T-REC-M.3393-202510-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/M/T-REC-M.3393-202510-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..639b576d29ac572ac509470e1b16f7e381a3e83b --- /dev/null +++ b/marked/M/T-REC-M.3393-202510-I_PDF-E/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5361e9ddd0c345b3539b9b21143a81796996a2db8a218ba660bb0b8b50d34c50 +size 13897 diff --git a/marked/M/T-REC-M.3393-202510-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3393-202510-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d8969f805414689ab79cfd08c333d454d482b3 --- /dev/null +++ b/marked/M/T-REC-M.3393-202510-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636c3839edff955a5b6208530b05fa1c983ab153d90f00216517a7a99478b988 +size 7074 diff --git a/marked/M/T-REC-M.3393-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3393-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddb2e30d592069382858993e11980602ae9810a7 --- /dev/null +++ b/marked/M/T-REC-M.3393-202510-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e45dcfd0fa54a91be780d6caf2255961c23763cde8523a1306a64a8d5cd11a3 +size 70845 diff --git a/marked/M/T-REC-M.3393-202510-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/M/T-REC-M.3393-202510-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74737484ee11ea06f2b1316250fabfbb7ae8e646 --- /dev/null +++ b/marked/M/T-REC-M.3393-202510-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:613deb4d6148006e2a0e9ab29e34e980c8da5a14b6b9b123b16c2e2a4cbf35a1 +size 28421 diff --git a/marked/M/T-REC-M.3393-202510-I_PDF-E/ec788ac3d43f427d6dca7fa19dce3874_img.jpg b/marked/M/T-REC-M.3393-202510-I_PDF-E/ec788ac3d43f427d6dca7fa19dce3874_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..701225e95c3bd8195192f1c05d1948c3af8230ed --- /dev/null +++ b/marked/M/T-REC-M.3393-202510-I_PDF-E/ec788ac3d43f427d6dca7fa19dce3874_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6166c31b69c00f3077c9693ae4239c17f057b6211708c8439ac2aef32ba40413 +size 46847 diff --git a/marked/M/T-REC-M.34-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.34-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.34-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.340-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.340-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0415ef19d9dffe1740e76c420582d638c54bb5d7 --- /dev/null +++ b/marked/M/T-REC-M.340-198811-I_PDF-E/raw.md @@ -0,0 +1,55 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.340** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**NUMBERING OF SUPERGROUPS +WITHIN A MASTERGROUP** + +**ITU-T Recommendation M.340** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.340 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# NUMBERING OF SUPERGROUPS WITHIN A MASTERGROUP + +The position of a supergroup within a mastergroup is identified by a number in the series from 4 to 8 which refers to one of the numbers of the supergroups constituting the basic mastergroup in the supergroup arrangement of the standard 4-MHz coaxial system. + +The numbering is shown in Figure 1/M.340. + +![Diagram showing the numbering of supergroups (4-8) and the basic mastergroup (300) within a frequency band (812-2044 kHz).](a854aa286b14d26d27047ee5893ffaa7_img.jpg) + +The diagram illustrates the frequency allocation for supergroups and the basic mastergroup. It consists of two horizontal axes representing frequency in kHz, both ranging from 812 to 2044. The top axis shows five supergroups, numbered 4, 5, 6, 7, and 8, each represented by a right-angled triangle with a base of 60 kHz. The bottom axis shows the 'Basic mastergroup' as a single right-angled triangle with a base of 300 kHz. The text 'CCITT - 36700 d01-sc' is located in the bottom right corner of the diagram area. + +Diagram showing the numbering of supergroups (4-8) and the basic mastergroup (300) within a frequency band (812-2044 kHz). + +FIGURE 1/M.340 + +Numbering of supergroups within the basic mastergroup \ No newline at end of file diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa2600525c5eef7f1a525542308035bd10aa0a5a --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16ed31ba5501a0ca85717104312ad3d6510aeabae67ddd7c6df895307f50f948 +size 190909 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/140bd031d724324269168296afd1e04d_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/140bd031d724324269168296afd1e04d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f0c69f6a444c97d6eb16e1d8d419f2a0cd7e610 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/140bd031d724324269168296afd1e04d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3664c4e366ceb26e65427c5aa9a2ac845cd6915ed7917f68320c931736eff38d +size 105783 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c85ef4f4f6d5bc7d933fbf830330db3c4b3b3ba --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f93b0d88948a7690aa616cc4bf4700765105c4fcfcb5b1fa6343b0890041d08d +size 94681 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/184d3d9a856c77aae93652f4fe30f752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d25b0faff0edfa46eb4e96b8feb776b04fd03a2 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/184d3d9a856c77aae93652f4fe30f752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc3c63b3d7601af64123495751b1849d48af17894b89e8a99e1aacb59e88325f +size 103085 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fccfd7a8663f8ec24e74c834bef45010978414de --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51719e354386d2db5fdba709c55af3cd5671c5181701531cbff4247b436a8068 +size 148936 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73abf64b289f3bdd0072fb55fc3f43df2a912273 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fb61826bfb42a8d0a0bc2cee0261fba60acb0582e933a716fe63e579db78ea2 +size 144958 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/27b09ea51378a0f896d21b3ebad0b22f_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/27b09ea51378a0f896d21b3ebad0b22f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c4fec1eb638a0b005e5d6b6584cd1e1017d3729 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/27b09ea51378a0f896d21b3ebad0b22f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1f709adc9a5905c2f95bae4c3dce98c48fcf9e11bb3318e3f6c1efb97e90e11 +size 51182 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3061437d8f0df9b65a92b9f1083faccd5ba54d33 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec59dfaafa97a5a81812b87b278053d860f7ad631efc34d46824057cf264041e +size 216151 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/38d82ffe820e339811b396206f40a201_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a6d69b42283d28986f0d013fe552c5a9bc91929 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2330195402663a38fb3301cf36cc06f6f5701ce538e70029456b84f7102773cc +size 176297 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/4cf20a1cc0755dff37937135bda4e2c6_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/4cf20a1cc0755dff37937135bda4e2c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42b5db98ae1540731417ffdd52ba4d3ea450a199 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/4cf20a1cc0755dff37937135bda4e2c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acffcd8ee4567112231578528adc488fae657dc57dba01679046e85df06a0ccd +size 153114 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db88d48d3c8b6a92e26c0afd7bde0309d04188db --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afb01ca37fa510c65d0dd1314dd48802bfaf8d669d4b7ec9efb0922223cf18a3 +size 199279 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d63dc3efa917916a2ee1f20748f852d32221ca5 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef8deb1a537a274a563d9cacb66969c2d17b53838c6120373279f371797e705c +size 103589 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30640a7cc6f7a5fdf7ae7afdc737084f10ee4de6 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a832d9933b70c964573cf7adbba08e11b60fc166d9e8ce661598081e2c2db50c +size 29378 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/88ffa3d2537be96753fe9243edefd095_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/88ffa3d2537be96753fe9243edefd095_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56a37a4de8e7ca90b4fec6b66324b20a9f7c4373 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/88ffa3d2537be96753fe9243edefd095_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b61a9ba76a06bbf8d88fa494fc4aaa82ec0e232f7c3118c475dd51fbd89d258 +size 140301 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/8b2fede7511dc55ca8474f946371bb6b_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/8b2fede7511dc55ca8474f946371bb6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2c1f1197f90a6ad9e09ab180f07b65e0b095c4f --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/8b2fede7511dc55ca8474f946371bb6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18947b6120366db82e0e348440ead7f109c6807c03076e3ead87d4e29878a955 +size 118141 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2c81f3c5f72ff05e6bcca7806121bac0c3e3e16 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87fbb4db2751ff5c03666f6980f7bf142923adb1974272caa33f2c7ff6a11a8b +size 64024 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b03d7b9761784454db140c9e2aa6947aa9ef931a --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2a3d43b63207a7635b66cfce10dec8445ba777d91aec4f99f8ed6293fde6bc0 +size 155595 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac888403cc8385609db47ad3f34fc3124185c992 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c22d687392d351f628e0428bdd5361e79d57e5c7ad9516ad45e12c7ed9c6e8a +size 117429 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77d04d6007b7e4319608252c78a83fd1b1cfa401 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dddf162e64a288bd5ef91520c2190481974f48417fd2a0630ee99b29d529c46b +size 190724 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8a65bbca10a47427a11dac91cb6ad84337bd9b7 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7629dd38a24398d75982df38d736e8131e66acd15cfd1393e6623b8c9efbcc70 +size 140350 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48dea43fc3e29ff70451ff2179ef280cd765fa3e --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b41ae161e5c88169a4ade0b1fe7f86bb85c7fb1f48e987b7619d41926d8fd2a0 +size 322826 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64eb0a0a8a670be3e0728eec182ed87343f95bb5 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f83c784fbb40b82e4453df075e2ed3ba7cec20b7eea68aed8cc7a9188a53ec0f +size 161408 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87921adca54b656d90df52e6119276b2189797b7 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fd29b8e8235d09f494080b3e6daa16523f15881bbfdbd41560f4c53f2c9255c +size 25217 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b67f4873a3a29424d8c295a68ac4cd9dc9fb0e2a --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9823e60845f0b13b3a4fd6d5769502a7f052fa27d6da2f4c58fe641cc54d4fd7 +size 28238 diff --git a/marked/M/T-REC-M.3400-200002-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/M/T-REC-M.3400-200002-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..defc71a1a8ae81102cc59ca04bf96f073d8a1550 --- /dev/null +++ b/marked/M/T-REC-M.3400-200002-I_PDF-E/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90084f8ab30bd55c5fee16e453b3006d05b94e091e86d6ecd4862bb33036c732 +size 66099 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b399841359c9e4f6784e6ce9bc66435272728f0f --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3143cbe6ea7e1f5af292638afa5bb7237295ed92e6340328f28c479d96cbbf66 +size 49846 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..818330a2200305da529c632bc824130ee76f6b6d --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:131711fd652a6d651894f355766f5d9000dcc444183ebd25c81acbeb374cf8d7 +size 46557 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1129ff11d5f02c17e1abacc504054dc58fda96cf --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9df820311f8f6d12de6dc9832d0eded8cf4f926e9f5add2f98d9dd64760c095d +size 62337 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62afe5c138281f339d974c4b4512bbf150fd97fe --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912ffb5601cafd51734edec083f13de98865036b57ce6da20ebaae549baa27c6 +size 44495 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6ff5fd41604cf176c3bc6af4fc706c774cb731d --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2f58c3416b85a796487fb2d7333f7ed4cf505fcb9e9681baa089abcdd232a9f +size 33356 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71b150782455f4c73850f409a8369d07b5e97df9 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b961eb2b9c90381b16aaaedb0e0fb339ad09067bed5baf2c5b25e58ef7fe490c +size 101864 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..450dbea6434897c25c45339953b8b4c4090d6687 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ee69bba79118089baba4c27612b5d22f27c4bc4c394e82435a39e12d8e18011 +size 106450 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32c70c9d0abd7d4de2e7256e88829e3112a59fe4 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/7f7211748473542096717109ebe5a9d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:996d66f581330e88eb9e4a206af7c1e7fec7eb04ed8ada3c83cdf148f1163aae +size 97797 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33cc03aea8077bf4f43e6e209fe6e8ba8107b51b --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a32b2008e1fd36fd5ce3c69a39cb9f67da351f96f1fd834620f343b6a99d7b6 +size 49896 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d0e205183499f6aa48f3b722faaa3cabfd66cd2 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee80ef8eebf543d3ab5df2c64a82a8e2656e9f76ef87304ff4a0abb3f1666279 +size 59527 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3dbc9afab0f44a6fd72f9459d2887f37edc44a9 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaaf272df22553166e7e13169ecf991233fc169fa13b29da358e2ec2230efc5c +size 172960 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cf51f8ba07e44aa7a4b009f3ba08eb2b570b1c --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11780faeee75ba39ab4ed9de67a9e67abec0d9ba3068ebec661dea70c16e29d3 +size 4338 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5642f115f4d3fdbc8e3574124ca16acf9725dc7 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0565e49abbbfaf96064448ccc73c99aba726d456902fd9690e4af106f9906f2b +size 55395 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53b0bec5780a42b4166db1376f8cf6b3cb5efb96 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97c0c03e6ad6a8b65c33ecd13c53530ea631a9210a0c0bb7e0da6307b4f14b31 +size 91801 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9c40d4aa3ed385e7d61f110b708d3b2c7bc1691 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ccb680d75edd7371a6b66e0ed5d7fad4610f1fd3bc00ac4edaa8b7090bff3c4 +size 90089 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78e301f907272e5b61011a1721222ec64bf3ba58 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fe4b5c2c6a51c1f40ff98cfb94fe0a931875e6f91e93edac0c6fa7c9814b123 +size 72083 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e212f3e1eafd522846ce3311bf1c4436560aa267 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4505022d797de04c8ca8c252efaf0cc3ff615d4cbeba022c3b78a256074ec9cd +size 27847 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4754e69be440f8c8250d7c3b41f26f3be897508 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d4903e518cd1b18ea768e20ccd8cf2625cf5c1a3ed754e1637fac0e64336f8a +size 56604 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/M/T-REC-M.3410-200808-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e4e42e2fcfdbcce1ad74abd4c287dda24a8c4c0 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db246abd82fb4c48e9caf0ebe36673f9157a9fd21a4c9b8c6e92f82174c7a36a +size 33427 diff --git a/marked/M/T-REC-M.3410-200808-I_PDF-E/raw.md b/marked/M/T-REC-M.3410-200808-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bfeb678aa60b05ea42ac832fa201f332e74cfd21 --- /dev/null +++ b/marked/M/T-REC-M.3410-200808-I_PDF-E/raw.md @@ -0,0 +1,3442 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3410** + +(08/2008) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Telecommunications management network + +--- + +**Guidelines and requirements for security +management systems to support +telecommunications management** + +Recommendation ITU-T M.3410 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# **Recommendation ITU-T M.3410** + +# **Guidelines and requirements for security management systems to support telecommunications management** + +## **Summary** + +Recommendation ITU-T M.3410 describes a set of functions considered necessary for the management of security mechanisms deployed in current and next generation packet-oriented networks. A logical collection of management functionality used to perform "operations, administration, maintenance and provisioning" (OAM&P) of security mechanisms, policies and services within a services and communications infrastructure. + +## **Source** + +Recommendation ITU-T M.3410 was approved on 6 August 2008 by ITU-T Study Group 4 (2005-2008) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +Authentication, authorization, confidentiality, FCAPS, management, security. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2009 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | | Page | +|------------|---------------------------------------------------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 2 | +| 3 | Definitions ..... | 3 | +| 3.1 | Terms defined elsewhere ..... | 3 | +| 3.2 | Terms defined in this Recommendation..... | 5 | +| 4 | Abbreviations and acronyms ..... | 6 | +| 5 | Conventions ..... | 9 | +| 6 | Security management system (SMS) overview ..... | 9 | +| 6.1 | Security management concepts relationship to next generation networks..... | 11 | +| 6.2 | Security management relationship to [ITU-T X.800] and [ITU-T X.805] security concepts ..... | 11 | +| 6.3 | Security management concepts relationship to ITU-T Recommendations M.3016-series ..... | 12 | +| 6.4 | Security management concepts relationship to ITU-T management Recommendations ..... | 12 | +| 7 | Security management system functional requirements ..... | 12 | +| 7.1 | Administrator interface FG..... | 16 | +| 7.2 | Administrator account management FG..... | 16 | +| 7.3 | Credentials management FG ..... | 19 | +| 7.4 | Configuration management FG ..... | 20 | +| 7.5 | Fault management FG ..... | 22 | +| 7.6 | Security policy management FG ..... | 25 | +| 7.7 | Verification and validation management FG ..... | 26 | +| 7.8 | Corrective action management FG..... | 27 | +| 7.9 | Security management information FG ..... | 29 | +| 7.10 | Communications interface FG..... | 30 | +| Annex A | – Proforma – M.3410 – SMS requirements..... | 32 | +| A.1 | Basis of profile proforma for security requirements ..... | 32 | +| A.2 | Guidelines and instructions for proforma specification ..... | 32 | +| A.3 | Proforma ..... | 32 | +| Appendix I | – Relationship of security management concepts to [ITU-T X.800]..... | 35 | +| I.1 | Trust domains ..... | 35 | +| I.2 | Security management information bases..... | 35 | +| I.3 | Trust domain SMIB content ..... | 36 | +| I.4 | Communication of security management information ..... | 37 | +| I.5 | Distributed security management administration..... | 38 | +| I.6 | Security mechanism management ..... | 42 | + +| | | +|--------------------------------------------------------------------------------------------------------------|----| +| Appendix II – SMS relationship with the role of security in other TSP management frameworks and systems..... | 47 | +| II.1    SMS relationship to ITU-T management Recommendations ..... | 47 | +| II.2    Security of legacy/existing management systems ..... | 56 | +| Appendix III – TSP infrastructure and security service managed elements ..... | 64 | +| III.1    TSP NGN security service managed elements ..... | 64 | +| III.2    Framework and topology of the NGN..... | 64 | +| III.3    NGN decomposition..... | 67 | +| III.4    Security mechanisms within an NGN ..... | 73 | +| III.5    NGN computing platform security mechanisms ..... | 77 | +| Bibliography..... | 94 | + +# Recommendation ITU-T M.3410 + +## Guidelines and requirements for security management systems to support telecommunications management + +# 1 Scope + +This Recommendation describes the functional requirements of a security management system (SMS) that offers a centralized view for control and security oversight of a telecommunications service provider's (TSP) infrastructure. The SMS spans the management of the management security plane, the control security plane, and the end-user security plane. The TSP's infrastructure spans, at a minimum: + +- Application servers (e.g., servers for mail, instant messaging, database, web, file, voice over IP (VoIP) and other applications); +- Support servers (e.g., DNS [b-IETF RFC 2181], DHCP [b-IETF RFC 2131], NTP [b-IETF RFC 1305], backup, and other infrastructure support services); +- Internetworking/transport components (e.g., multiplexers, switches, routers, transport gateways, application gateways, gateway controllers, packet-filters a.k.a. firewalls, content filters, access points, bridges, wired and wireless telephony devices and monitoring probes for QoS, and network activity, to name a few); +- End user host systems (e.g., laptop systems, desktop systems, workstations, printers, etc.); and +- Management systems (e.g., element management, network management, service management, and business management systems). + +All of the above entities are referred to in this Recommendation as managed elements (MEs) from a security management perspective. + +The requirements specified in this Recommendation should be applicable to a TSP's current infrastructure and also infrastructure evolution necessary for building their next generation networks (NGNs) (see [ITU-T Y.2001] and [ITU-T Y.2012]). + +This Recommendation draws on an ATIS standard [b-ATIS 0300074] as a major source of information and text. + +A key aspect of this Recommendation is that it defines a logical architecture and set of functionality independent of physical implementation. Functionality is defined in terms of functional entities, their logical relationships as well as aggregation of functional entities (FEs) into functional groups (FGs). Deployment and implementation of these FEs and FGs, within an infrastructure, can take many forms, such as centralized, hierarchical, distributed, or some combination of these. This Recommendation takes no stand as to the implementation of FEs and FGs in so far as implementation decisions do not have security-related ramifications. The detailed description of the interactions between FGs is not described in this Recommendation. + +Annex A contains a normative proforma wherein specific SMS requirements are documented. Appendices I, II and III are informative and cover: + +Appendix I: The relationship between the SMS and the security concepts covered in [ITU-T X.800]. + +Appendix II: The relationship between the SMS and other TSP management systems and frameworks. + +Appendix III: The structure and organization of NGN networks and their growing complexity. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network.* +- [ITU-T M.3016.0] Recommendation ITU-T M.3016.0 (2005), *Security for the management plane: Overview.* +- [ITU-T M.3016.1] Recommendation ITU-T M.3016.1 (2005), *Security for the management plane: Security requirements.* +- [ITU-T M.3016.2] Recommendation ITU-T M.3016.2 (2005), *Security for the management plane: Security services.* +- [ITU-T M.3016.3] Recommendation ITU-T M.3016.3 (2005), *Security for the management plane: Security mechanism.* +- [ITU-T M.3016.4] Recommendation ITU-T M.3016.4 (2005), *Security for the management plane: Profile proforma.* +- [ITU-T M.3050.2] Recommendation ITU-T M.3050.2 (2004), *Enhanced Telecom Operations Map (eTOM) – Process decompositions and descriptions.* +- [ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the management of Next Generation Networks.* +- [ITU-T X.500] Recommendation ITU-T X.500 (2005) | ISO/IEC 9594-1:2005, *Information technology – Open Systems Interconnection – The Directory: Overview of concepts, models and services.* +- [ITU-T X.509] Recommendation ITU-T X.509 (2000) | ISO/IEC 9594-8:2001, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks.* +- [ITU-T X.700] Recommendation ITU-T X.700 (1992), *Management framework for Open Systems Interconnection (OSI) for CCITT applications.* +- [ITU-T X.733] Recommendation ITU-T X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function.* +- [ITU-T X.736] Recommendation ITU-T X.736 (1992) | ISO/IEC 10164-7:1992, *Information technology – Open Systems Interconnection – Systems Management; Security alarm reporting function.* +- [ITU-T X.800] Recommendation ITU-T X.800 (1991), *Security architecture for Open Systems Interconnection for CCITT applications.* +- [ITU-T X.805] Recommendation ITU-T X.805 (2003), *Security architecture for systems providing end-to-end communications.* + +- [ITU-T X.810] Recommendation ITU-T X.810 (1995) | ISO/IEC 10181-1:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Overview*. +- [ITU-T X.811] Recommendation ITU-T X.811 (1995) | ISO/IEC 10181-2:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Authentication framework*. +- [ITU-T X.812] Recommendation ITU-T X.812 (1995) | ISO/IEC 10181-3:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Access control framework*. +- [ITU-T X.816] Recommendation ITU-T X.816 (1995) | ISO/IEC 10181-7:1996, *Information technology – Open Systems Interconnection – Security frameworks for open systems: Security audit and alarms framework*. +- [ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN*. +- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*. +- [ISO/IEC 15408-1] ISO/IEC 15408-1:2005, *Information technology – Security techniques – Evaluation criteria for IT security – Part 1: Introduction and general model*. +<[http://www.iso.org/iso/iso\\_catalogue/catalogue\\_tc/catalogue\\_detail.htm?csnumber=40612](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40612)> +- [ISO/IEC 27002] ISO/IEC 27002:2005, *Information technology – Security techniques – Code of practice for information security management*. +<[http://www.iso.org/iso/iso\\_catalogue/catalogue\\_tc/catalogue\\_detail.htm?csnumber=50297](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50297)> + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **access control**: [ITU-T X.800] +- 3.1.2 **access control list**: [ITU-T X.800] +- 3.1.3 **alarm**: [ITU-T X.733] +- 3.1.4 **active threat**: [ITU-T X.800] +- 3.1.5 **asymmetric authentication method**: [ITU-T X.811] +- 3.1.6 **audit trail, see security audit trail**: [ITU-T X.800] +- 3.1.7 **authenticated identity**: [ITU-T X.811] +- 3.1.8 **authentication**: [ITU-T X.800] +- 3.1.9 **authentication information**: [ITU-T X.800] +- 3.1.10 **authorization**: [ITU-T X.800] +- 3.1.11 **business management layer**: [ITU-T M.3010] +- 3.1.12 **ciphertext**: [ITU-T X.800] +- 3.1.13 **cleartext**: [ITU-T X.800] +- 3.1.14 **confidentiality**: [ITU-T X.800] +- 3.1.15 **control security plane**: Clause 8.2 of [ITU-T X.805] +- 3.1.16 **credentials**: [ITU-T X.800] + +- 3.1.17 **cryptanalysis:** [ITU-T X.800] +- 3.1.18 **cryptography:** [ITU-T X.800] +- 3.1.19 **data integrity:** [ITU-T X.800] +- 3.1.20 **decipherment:** [ITU-T X.800] +- 3.1.21 **decryption:** [ITU-T X.800] +- 3.1.22 **denial of service:** [ITU-T X.800] +- 3.1.23 **digital signature:** [ITU-T X.800] +- 3.1.24 **element management layer:** [ITU-T M.3010] +- 3.1.25 **encipherment:** [ITU-T X.800] +- 3.1.26 **encryption:** [ITU-T X.800] +- 3.1.27 **end-to-end encipherment:** [ITU-T X.800] +- 3.1.28 **end-user security plane:** Clause 8.3 of [ITU-T X.805] +- 3.1.29 **hash function:** [ITU-T X.810] +- 3.1.30 **initiator:** [ITU-T X.812] +- 3.1.31 **integrity:** [ITU-T X.800] +- 3.1.32 **key:** [ITU-T X.800] +- 3.1.33 **key management:** [ITU-T X.800] +- 3.1.34 **network element:** [ITU-T M.3010] +- 3.1.35 **network management layer:** [ITU-T M.3010] +- 3.1.36 **managed element (ME):** [ITU-T M.60] +- 3.1.37 **managed resources:** [ITU-T M.60] +- 3.1.38 **management security plane:** Clause 8.1 of [ITU-T X.805] +- 3.1.39 **management system:** [ITU-T M.60] +- 3.1.40 **masquerade:** [ITU-T X.800] +- 3.1.41 **non-repudiation:** [ITU-T X.800] +- 3.1.42 **object:** [ITU-T M.60] +- 3.1.43 **one-way hash function:** [ITU-T X.810] +- 3.1.44 **operations system:** [ITU-T M.3010] +- 3.1.45 **passive threat:** [ITU-T X.800] +- 3.1.46 **password:** [ITU-T X.800] +- 3.1.47 **peer-entity authentication:** [ITU-T X.800] +- 3.1.48 **physical security:** [ITU-T X.800] +- 3.1.49 **privacy:** [ITU-T X.800] +- 3.1.50 **private key:** [ITU-T X.810] +- 3.1.51 **public key:** [ITU-T X.810] +- 3.1.52 **public-key certificate:** [ITU-T X.509] +- 3.1.53 **repudiation:** [ITU-T X.800] + +- 3.1.54 **risk:** [ISO/IEC 27002] +- 3.1.55 **role:** [ISO/IEC 15408-1] +- 3.1.56 **secret key:** [ITU-T X.810] +- 3.1.57 **security alarm:** [ITU-T X.736] +- 3.1.58 **security audit:** [ITU-T X.800] +- 3.1.59 **security audit record:** [ITU-T X.816] +- 3.1.60 **security audit trail:** [ITU-T X.800] +- 3.1.61 **security certificate:** [ITU-T X.810] +- 3.1.62 **security management information base (SMIB):** [ITU-T X.700] +- 3.1.63 **security policy:** [ITU-T X.800] +- 3.1.64 **security-related event:** [ITU-T X.736] +- 3.1.65 **service management layer (SML):** [ITU-T M.3010] +- 3.1.66 **service management layer operations system function block (S-OSF):** [ITU-T M.3010] +- 3.1.67 **signature:** [ITU-T X.800] +- 3.1.68 **stratum/strata:** [ITU-T Y.2012] +- 3.1.69 **subject:** [ISO/IEC 15408-1] +- 3.1.70 **symmetric authentication method:** [ITU-T X.811] +- 3.1.71 **target:** [ITU-T X.812] +- 3.1.72 **threat:** [ITU-T X.800] +- 3.1.73 **trust:** [ITU-T X.810] +- 3.1.74 **trusted third party:** [ITU-T X.810] + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 **application security administrator:** An application security administrator is an individual who has responsibility for the administration of those attributes and capabilities of an application (sub-) system related to security of the application (e.g., application administrative and user accounts and authorizations). +- 3.2.2 **application system administrator:** An application system administrator is an individual who has responsibility for the administration of all non-security-related attributes and capabilities of an application (sub-) system (e.g., application features, capabilities, configuration parameters and monitoring of the application). +- 3.2.3 **business management system (BMS):** A business management system is a business management layer [ITU-T M.3010] operations system. +- 3.2.4 **element management system (EMS):** An element management system is an element management layer [ITU-T M.3010] operations system. +- 3.2.5 **functional entity (FE):** A functional entity is a cluster of functionality (sub-functions) that are viewed as a single entity from the point of view of the end-to-end functional architecture. +- 3.2.6 **functional group (FG):** A functional group is a cluster of functional entities grouped (and named) solely for convenience and architectural clarity. + +**3.2.7 managed element operator(s):** A managed element operator is an individual who has responsibility to perform specified tasks/activities on a managed element that are administrative in nature (e.g., backup, patching, surveillance, etc.). + +**3.2.8 managed element security administrator:** A managed element security administrator is an individual who has responsibility for the administration of those attributes and capabilities of a managed element related to security of the managed element, regardless of what applications execute on the managed element (e.g., managed element administrative and user accounts and authorizations). + +**3.2.9 managed element system administrator:** A managed element system administrator is an individual who has responsibility for the administration of all non-security-related attributes and capabilities of a managed element (e.g., managed element features, capabilities, configuration parameters and monitoring of the managed element). + +**3.2.10 network management system (NMS):** A network management system is a network management layer [ITU-T M.3010] operations system. + +**3.2.11 role:** The description of an individual's sphere of responsibility. + +NOTE – It may be used for enforcing access control in accordance with the principle of least privilege (see: managed element operator(s), managed element system administrator, managed element security administrator, application system administrator, application security administrator above). + +**3.2.12 security administrator:** An authority (a person or group of people) responsible for implementing the security policy for a security domain. + +**3.2.13 security event:** A security-related event [ITU-T X.736]. + +**3.2.14 security management system (SMS):** A logical collection of management functionality used to perform "operations, administration, maintenance and provisioning" (OAM&P) of security mechanisms, policies and services within a services and communications infrastructure. + +**3.2.15 service management system:** A service management system is a service management layer [ITU-T M.3010] operations system. + +**3.2.16 telecommunications service provider (TSP) infrastructure:** A TSP infrastructure includes all managed elements deployed by a TSP that provide management, application/services, service control or transport strata functionality. + +**3.2.17 trust domain:** A set of information and associated resources consisting of users, networks, data repositories, and applications that manipulate the data in those data repositories. Different trust domains may share the same physical components. Also, a single trust domain may employ various levels of trust, depending on what the users need to know and the sensitivity of the information and associated resources. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------------------------| +| 2G | Second Generation | +| 3G | Third Generation | +| AAA | Authentication, Authorization, and Accounting | +| ACL | Access Control List | +| ADF | Access control Decision Function | +| AEF | Access control Enforcement Function | +| AH | Authentication Header | + +| | | +|--------|------------------------------------------------------------------------| +| API | Application Programming Interface | +| APP-SA | Application Process Security Associations | +| ASIC | Application-Specific Integrated Circuit | +| BMS | Business Management System | +| CA | Certificate Authority | +| CLEC | Competitive Local Exchange Carrier | +| CORBA | Common Object Request Broker Architecture | +| CPU | Central Processing Unit | +| CRL | Certificate Revocation List | +| DCE | Distributed Computing Environment | +| DDoS | Distributed Denial-of-Service | +| DHCP | Dynamic Host Configuration Protocol | +| DLEC | Data Local Exchange Carrier | +| DLL | Data Link Layer | +| DNS | Domain Name System | +| DoS | Denial-of-Service | +| DSL | Digital Subscriber Line | +| DTLS | Datagram Transport Layer Security | +| EMS | Element Management System | +| ENNI | External Network-Network Interface | +| ESP | Encapsulating Security Payload | +| eTOM | enhanced Telecom Operations Map | +| FCAPS | Fault, Configuration, Accounting, Performance, and Security management | +| FE | Functional Entity | +| FG | Functional Group | +| FTP | File Transfer Protocol | +| GPS | Global Positioning System | +| GSS | General Security Service | +| HTTP | HyperText Transfer Protocol | +| HTTPS | HyperText Transfer Protocol Secure | +| IDS | Intrusion Detection System | +| IKE | Internet Key Exchange | +| INNI | Internal Network-Network Interface | +| IP | Internet Protocol | +| IPS | Intrusion Prevention System | +| IPSec | IP Security | +| ISAKMP | Internet Security Association and Key Management Protocol | + +| | | +|--------|----------------------------------------------------------| +| ISDN | Integrated Services Digital Network | +| KDC | Key Distribution Centre | +| LDAP | Lightweight Directory Access Protocol | +| ME | Managed Element | +| ME-SA | Managed Element Security Association | +| MIB | Management Information Base | +| MNE | Managed Network Element | +| NE | Network Element | +| NEL | Network Element Layer | +| NGN | Next Generation Network | +| NMS | Network Management System | +| NNI | Network-Network Interface | +| NOC | Network Operations Centre | +| NTP | Network Time Protocol | +| OAM&P | Operations, Administration, Maintenance and Provisioning | +| OCSP | Online Certificate Status Protocol | +| OS | Operations System | +| OSI | Open Systems Interconnection | +| OSP | Outside Plant | +| OSS | Operations Support System, same as OS | +| PIN | Personal Identification Number | +| PKCS | Public-Key Cryptography Standards | +| PKI | Public Key Infrastructure | +| PON | Passive Optical Network | +| PSTN | Public Switched Telephone Network | +| PUC | Public Utilities Commission | +| QoS | Quality of Service | +| RA | Registration Authority | +| RADIUS | Remote Authentication Dial In User Service | +| RBAC | Role-Based Access Control | +| RVM | Reference Validation Mechanism | +| S&C | Signalling and Control | +| SA | Security Association | +| SC | Service Control | +| SDU | Service Data Unit | +| SMAP | Security Management Application Process | +| SMI | Security Management Information | + +| | | +|--------|-----------------------------------------------------| +| SMIB | Security Management Information Base | +| SML | Service Management Layer | +| SMS | Security Management System | +| SNMP | Simple Network Management Protocol | +| S-OSF | Service Management Layer Operations System Function | +| SPDF | Security Policy Decision Function | +| SPEF | Security Policy Enforcement Function | +| SQL | ANSI Structured Query Language | +| SSH | Secure Shell | +| SSL | Secure Sockets Layer | +| TACACS | Terminal Access Controller Access-Control System | +| TCP | Transmission Control Protocol | +| TDM | Time-Division Multiplexing | +| TFTP | Trivial File Transfer Protocol | +| TL1 | Transaction Language 1 | +| TLS | Transport Layer Security | +| TMN | Telecommunications Management Network | +| TSP | Telecommunications Service Provider | +| UNI | User-to-Network Interface | +| VoIP | Voice over IP | +| WLAN | Wireless Local Area Network | +| XML | eXtensible Markup Language | +| XSL | eXtensible Stylesheet Language | + +# 5 Conventions + +The term "should" is used within this Recommendation to denote those functional capabilities that are appropriate in performing the activities of managing security mechanisms in an integrated manner. A proforma for SMS realization is in Annex A that contains specific requirements. + +# 6 Security management system (SMS) overview + +The *security management system* (SMS) described in this Recommendation is primarily an operations system intended to mechanize the application of various security services and security management tools. The SMS supports the management of security of the TSP infrastructure by providing supporting services to protect the information and resources in TSP networks and systems. It manages the security in accordance with the applicable trust domains and their security policies. + +A *trust domain* is a set of information and associated resources. It consists of users, networks, data repositories, and applications that manipulate the data in those data repositories. Different trust domains may share the same physical components. Also, a single trust domain may employ various levels of trust, depending on what the users need to know and the sensitivity of the information and associated resources. + +*Security management* is concerned with the management of security services and mechanisms. Such management requires distribution of management information to those services and mechanisms, as well as the collection of information concerning the operation of the services and mechanisms. Objects are resources that may be managed. *Management information* is information associated with an object that is operated upon to manage that object. + +A human administrator employs a *security management application process* to use and maintain management information contained in a logical repository called a *security management information base* (SMIB). The contents of a single logical SMIB may exist in several end systems – referred to in this Recommendation as *Managed Elements* (MEs) – as well as the networks that connect them and their users. To ensure efficient and flexible system management, it is generally required that administrators have local or remote access to SMIBs. + +MEs that support multiple trust domains must provide the ability to manage each trust domain independently. In addition, the use of security services and security mechanisms shared among multiple trust domains requires security management coordination at the ME level. Thus, an ME security policy is necessary to specify how the shared use of security functions and resources among trust domains is accomplished. This ME policy also must be managed. + +Security management of MEs is concerned with the installation, maintenance, and enforcement of the security policy rules and the information about users, security services, and security mechanisms needed to achieve the security policy. Not all security management activities are performed in MEs. There are always supporting security management activities that are related to administrative and environmental security mechanisms or which are prerequisite to the use of ME security management functions (e.g., issuance of credentials to users, scheduling human activities, auditing, or carrying out routine maintenance). These supporting activities must be understood to be an integral part of security management. Examples of trust domain security policy elements include: + +- A description of the security services and mechanisms that the trust domain supports +- A description of the objects and their attributes, including rules pertaining to creation and use of multi-domain objects +- Membership criteria +- Rules for inter-domain transfers, if any +- Rules for intra-domain transfers, if any +- Security service requirements (including strength of service) appropriate to meet the risks determined by a threat analysis. Security services should be allocated to MEs +- Criteria for acceptable security mechanisms to implement the required security services +- Security management-specific requirements +- Interaction of the security management of each trust domain to other trust domains +- Criteria for security administrators +- Roles, privileges, and duties of security administrators +- Identities of security administrators +- Configuration management requirements for the establishment or modification of trust domain security policy rules +- Identification of one or more members of the trust domain who are responsible for approving MEs that will be deployed within the trust domain + +The security policy for an ME that supports multiple trust domains must specify the management rules for conducting the following activities: + +- Providing strict isolation among trust domains + +- Invoking and managing security mechanisms that implement the security services required by the security policies of the individual trust domains +- Developing rules for the management of multi-domain objects, including criteria for user access, display labelling, and transfers within and among MEs +- Controlling and maintaining security management mechanisms and objects that enable a security manager of a particular trust domain to control that trust domain independently of others + +The security policy rules for both ME security management and trust domain security management are part of their SMIBs. For a trust domain that is supported in more than one ME, the security administrator may have physical access to only some of those MEs. Thus, the security management application process that operates on the portion of a SMIB in a particular ME must be accessible to the security administrator both locally and remotely. A security management application process is like any other application in that it operates in a security context that represents a security administrator (or process) operating in a particular security management trust domain. Thus, it is subject to the same strict separation mechanisms as other applications in the same trust domains. + +### 6.1 Security management concepts relationship to next generation networks + +As defined in [ITU-T Y.2001], a next generation network (NGN) is a packet-based network that is able to provide telecommunication services and able to make use of multiple broadband, QoS-enabled transport technologies, and in which service-related functions are independent from underlying transport-related technologies. It enables unfettered access for subscribers to networks and to competing service providers and/or services of their choice. It supports generalized mobility that will allow consistent and ubiquitous provision of services to users. A goal of NGN is to provide the capabilities to make the creation, deployment, and management of all kinds of services possible. In order to achieve this goal, it decouples the service creation/deployment infrastructure from and independent of the transport infrastructure. Such decoupling is reflected in the NGN architecture as the separation of the transport and service strata and shown as two independent stratums. Figure 1 of [ITU-T M.3060] shows the scope of the management architecture in the context of NGN. + +From a TSP's perspective, the information and resources of the NGN transport and service strata are part of the TSP's infrastructure and are within the scope of the security management system architecture and requirements defined in this Recommendation. + +## 6.2 Security management relationship to [ITU-T X.800] and [ITU-T X.805] security concepts + +[ITU-T X.800] and [ITU-T X.805] define the general security-related architectural elements that are necessary for providing end-to-end security, and which can be applied appropriately in the circumstances for which protection of communication between open systems is required. + +This Recommendation uses information from these ITU-T Recommendations to develop system level, operating environment and software requirements to assure secure management of TSP network infrastructures. + +The security management structure of these ITU-T Recommendations is adopted as the basis for the infrastructure security architecture, and is extended to apply to all aspects of open systems security management. Security domains and security policy are introduced in these ITU-T Recommendations. Other topics covered at the concept level include: security management information repository, communications security, and security management functions. Using this as the basis, the security management system architecture is defined in this Recommendation to address these topics. Even though the details – such as the management information base definition – are not part of this Recommendation, the architecture is defined with the need to + +support these elements required for interoperability and assure secure management of TSP network infrastructure. + +## 6.3 Security management concepts relationship to ITU-T Recommendations M.3016-series + +ITU-T Recommendations M.3016-series: [ITU-T M.3016.0] [ITU-T M.3016.1] [ITU-T M.3016.2] [ITU-T M.3016.3] [ITU-T M.3016.4] address the requirements, services, and mechanisms in support of securing the management plane of the telecommunications infrastructure. In this context, they are focused on management plane end-to-end security, both in the case where management traffic is separate from user traffic and when they are mixed together. The reference model for deriving the requirements shows the interfaces where management traffic is to be secured. Given these end-to-end security requirements, this Recommendation focuses on requirements of a management system that offers the tools necessary to manage the security of the TSP's infrastructure. The management plane traffic addressed in the ITU-T Recommendations M.3016-series is a subset of the TSP's infrastructure to be secured by the requirements in this Recommendation. The reference model in the ITU-T Recommendations M.3016-series is further expanded in this Recommendation to include other MEs that are not specific to management plane such as the application servers, etc. While there are similarities in the functions to be supported in all these Recommendations, the ITU-T Recommendations M.3016-series relate to the interfaces between the MEs and operations systems (OSs) and between OSs, and this Recommendation addresses functions to be supported by systems that oversee all the infrastructure components. + +## 6.4 Security management concepts relationship to ITU-T management Recommendations + +Appendix II provides a discussion of the relationship between the SMS and existing ITU-T management Recommendations other than the ITU-T Recommendations M.3016-series. + +# 7 Security management system functional requirements + +The functions of an SMS can be logically organized into the following FGs which include FEs providing logically-related functionality: + +### - *Administrator interface FG* + +This FG provides the ability of administrative personnel to interact with other SMS FGs/FEs and, at a minimum, typically would include one or more of the following FEs: + +- Local command line administrator interface FE +- Remote command line administrator interface FE +- Local graphical administrator interface FE +- Remote graphical administrator interface FE + +### - *Administrator account management FG* + +This FG provides the ability to centrally administer and manage administrative user accounts to include managing administrator subjects, groups and roles and includes one or more of the following: + +- Authentication credentials, subject group memberships, and access rules +- Group identifiers and privileges +- Account propagation +- Authentication, identification and other administrative account related demographic information. + +### - *Credentials management FG* + +This FG provides the ability to centrally administer/manage authentication, and possibly authorization credentials. + +FEs within this FG interact with: + +- Existing authentication and authorization functionality (such as RADIUS [b-IETF RFC 2865], Diameter [b-IETF RFC 3588], TACACS+ and Lightweight directory access protocol (LDAP) [b-IETF RFC 4510] [b-IETF RFC 4511] [b-IETF RFC 4512] [b-IETF RFC 4513] servers) +- X.509 certificate and registration authorities (including online certificate status protocol (OCSP) servers and DNS/LDAP certificate and certificate revocation list (CRL) repositories) +- Security token and 'one-time pad' systems +- Key distribution centres (KDCs) (such as Kerberos [b-IETF RFC 4120]) +- Public key infrastructures (PKIs) +- Certificate authorities (CAs) + +### - *Configuration management FG* + +This FG provides the ability to centrally administer/manage security-related attributes and configurable parameters within MEs, such as: + +- Objects and object groups +- Object's subject and subject group access and authorization rights +- Security functionality configuration + +FEs within this FG interact with: + +- Existing configuration management and provisioning applications. + +### - *Fault management FG* + +This FG provides the ability to centrally manage security-related events, security-related alarms, security alarms and logs within MEs, as well as identification of attack-related activities, such as: + +- Security-related events [ITU-T X.736], including adjunct security devices reporting +- Security-related alarms [ITU-T X.733] and security alarms [ITU-T X.736] +- Security log entry reconciliation and analysis of security audit trails + +FEs within this FG interact with: + +- Existing fault management and surveillance applications + +### - *Security Policy Management FG* + +This FG provides the ability to centrally manage security policy and procedures information and can include: + +- Policy development and version tracking +- Operational procedures development and version tracking +- Document repository +- Policy and procedure periodic reviews + +### - *Verification and Validation Management FG* + +This FG provides the ability to centrally administer and manage the verification and validation that deployed network and ME security mechanisms are configured and operating according to policy. + +FEs within this FG interact with: + +- Network deployed intrusion detection and prevention systems (IDS/IPS) +- ME deployed intrusion detection and prevention systems (IDS/IPS) +- ME vulnerability and intrusion scanning applications +- *Corrective action management FG, including reporting corrective action and receiving corrective action completion report* + +This FG provides the ability to centrally administer/manage activities required to contain, isolate, investigate and restore services following security-related, or other, event occurrences. + +FEs within this FG interact with: + +- Existing trouble-ticket and workforce management applications +- System surveillance and performance management applications +- *Security management information FG* + +This FG provides the ability to centrally administer/manage security-related information in a security management information base (SMIB) repository. FEs within this FG should be able to transpose information, stored using various formats and organizational structures both locally and by remote MEs, into and from a common Meta-language usable by all SMS FEs. Meta-data should be relied on for locating (i.e., local vs remote storage location) and controlling both translations (i.e., or syntax, structure) and access attributes (i.e., access control lists (ACLs), rights, views). + +FEs within this FG interact with: + +- Currently deployed Management MEs (element management systems (EMSs), network management systems (NMSs), business management systems (BMSs), service management systems, operations systems (OSs)) and other MEs that retain security management information. + - *Communications interface FG* +- This FG provides the ability to communicate with other MEs via standards based and proprietary networking and application protocols. All other SMS FEs rely on the FEs within this FG to serve as a communications and translation proxy whenever any SMS FE exchanges information with other MEs. These FEs include those necessary to support those management protocols in use by deployed MEs. + +It is anticipated that the majority of SMS FEs will be co-located, but co-location is not required. A foundation concept behind the SMS is to leverage existing security management capabilities into a flexible interoperable framework for achieving unified and consistent adherence to organizational security policies and requirements. As such, SMS FEs not just interact with other management systems but should allow delegation of SMS FE functionality to existing management applications. From a communications perspective, SMS FEs will interact with peer OSs, existing EMS/NMS applications and MEs within the application/services, service control and transport strata. + +The platforms that host SMS FGs/FEs have their own security hardening requirements given the sensitivity of the very information processed and the control capabilities of these FEs. A basic SMS logical block structure by FG is pictured in Figure 1 below. + +![Figure 1 – SMS logical block structure diagram showing functional groups and their relationships.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +The diagram illustrates the SMS logical block structure. At the top, seven functional groups are listed in a row: Administrator account management functional group, Credentials management functional group, Configuration management functional group, Fault management functional group, Security policy management functional group, Verification and validation management functional group, and Corrective action management functional group. Below these is a bar labeled 'SMS communications infrastructure'. Underneath this bar are three functional groups: Communications interface functional group, Administrator interface functional group, and Security management information functional group. The Communications interface functional group is connected to two hexagonal nodes labeled 'ME' (Management Entity) with an ellipsis between them. The Administrator interface functional group is connected to a circular node labeled 'Local security management information base (SMIB) repository'. The Security management information functional group is connected to two circular nodes labeled 'Remote security management information base (SMIB) repository' with an ellipsis between them. Arrows indicate bidirectional relationships between the functional groups and the MEs/SMIB repositories. A small label 'M.3410(08)\_F01' is in the bottom right corner. + +Figure 1 – SMS logical block structure diagram showing functional groups and their relationships. + +**Figure 1 – SMS logical block structure** + +An example relationship between FGs is pictured in Figure 2 below. + +![Figure 2 – Example SMS flow logic diagram showing interactions between functional groups.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram shows an example of SMS flow logic. It starts with 'Administrator login ' pointing to 'Subject – Access rights to OS and subject groups membership '. This in turn points to 'Subject group – Access rights to object and privileges '. The 'Subject – Access rights to OS and subject groups membership' block has an 'Object access attempt' to 'Subject – Access rights to OS and subject groups membership '. This attempt is 'Denied' or 'Allowed'. 'Allowed' leads to 'Object Access '. 'Denied' leads to 'Security management information base (SMIB) '. Both 'Allowed' and 'Denied' lead to 'Log all attempts' which points to ''. 'Log all attempts' also points to 'Add, modify and delete' which points to 'Security management information base (SMIB) '. 'Security management information base (SMIB) ' points to 'Retrieve' which points to 'Subject – Access rights to OS and subject groups membership '. 'Retrieve' also points to 'Subject group – Access rights to object and privileges '. '' points to 'Isolation-repair' and 'Recovered' which both point to ''. '' points to 'Events/logs' which points to ''. A small label 'M.3410(08)\_F02' is in the bottom right corner. + +Figure 2 – Example SMS flow logic diagram showing interactions between functional groups. + +**Figure 2 – Example SMS flow logic** + +Security administrators must have available a set of security management functions to assist them in performing their functions efficiently and conveniently. Not all of the security management functions discussed here are available currently, and steps will need to be taken to ensure their timely creation. + +Each of the security management functions discussed in the following subclauses will require automated support for security administrators. The applications that provide this support are concerned with the various aspects of the security management information base (SMIB) maintenance, credential management, examination, processing, and correlation of information – such as security audit records. These management applications should work together smoothly, but they must also be separable if it is desired to assign certain activities to specific security administrators. In some instances, it will be necessary to integrate security management applications + +with other applications. For example, X.500 Directory service agents might be used to store portions of a SMIB so that user public-key certificates are easily available to a user community. + +## **7.1 Administrator interface FG** + +The administrator interface FG is the aggregation of all available administrative interfaces (FEs) presented to the security personnel managing the security network operations centre (NOC). These user interface FEs include local and remote command line and graphical user interface technologies that are operated on by SMS managed element security administrator(s) and/or SMS managed element system administrator(s). + +**SEC-1:** The administrator interface FG should support standards-based web browsers using de jure standards (e.g., XML and XSL). + +**SEC-2:** The administrator interface FG should use HTTPS to communicate over the network with the management system server. + +**SEC-3:** The administrator interface FG should be able to invoke all authorized functions within SMS FEs. + +**SEC-4:** There should not be FG functions that must be performed via another method, such as a command line interface, unless a mechanism is used that provides strong authentication and confidentiality, such as secure shell (SSH). + +**SEC-5:** Administrator interface FEs should communicate with other SMS FEs through the use of a de jure standards-based method, such as CORBA, HTTPS/XML, etc. in compliance with [ITU-T M.3016.1]. + +All SNMP and CORBA references are referring to the communications mechanisms and NOT the middleware or are presented simply as examples of common protocols used in management. This Recommendation at no time requires the use of any of these protocols. + +#### **7.1.1 Local command line administrator interface FE** + +The local command line administrator interface FE provides a command line interface for SMS FG commands. + +#### **7.1.2 Remote command line administrator interface FE** + +The remote command line administrator interface FE provides a command line interface for commands sent to and executed on MEs. + +#### **7.1.3 Local graphical administrator interface FE** + +The local graphical administrator interface FE provides a graphical user interface (e.g., web-based user interface) for SMS FG commands. + +#### **7.1.4 Remote graphical administrator interface FE** + +The remote graphical administrator interface FE provides a graphical user interface (e.g., web-based user interface) for commands sent to and executed on MEs. + +### **7.2 Administrator account management FG** + +Administrator account management encompasses the addition, modification, and deletion of entity accounts that are authorized to manage MEs and the objects contained within each ME. Administrator account management includes subject, subject group, subject propagation, and authorization management. There are two levels of administrator account management: 1) administrator accounts for SMS FEs; and 2) administrator accounts for MEs. + +FEs within administrator account management FG interact with deployed transport, signalling and control, application service delivery and management MEs, as defined in [ITU-T Y.2012], as well as non-NGN MEs. + +**SEC-6:** The administrator account management FG should communicate with other SMS FGs through the use of a de jure standards-based method, such as CORBA, HTTPS/XML, etc. in compliance with [ITU-T M.3016.1]. + +#### **7.2.1 Subject management FE** + +A subject is an entity that causes information to flow among objects or changes their state. A subject can be a person, process, or device. + +**SEC-7:** The management of subjects should include the ability to add the entity's authentication credentials. + +**SEC-8:** The management of subjects should include the ability to modify the entity's authentication credentials. + +**SEC-9:** The management of subjects should include the ability to delete the entity's authentication credentials. + +**SEC-10:** The management of subjects should include the ability to invalidate and revoke the entity's authentication credentials. + +Examples of credentials are user name, passwords, biological identifiers, and public-key certificates. + +#### **7.2.2 Subject group management FE** + +Subject grouping is a method to define role-based access control. A subject group is an identifier for a uniquely identifiable group of subjects. A subject or subject group may have multiple roles within their work definition. By assigning identifiers to these groups of subjects, if the role is no longer valid, the subject's appropriate rights can be easily removed from objects managed by that subject group identifier. This is a necessary means when controlling access to tens of millions of objects. Examples of subject groups are ME system administrator and ME system operator. + +**SEC-11:** The security management system should include the ability to add subject group identifiers and the privileges each identifier holds. + +**SEC-12:** The management system should include the ability to modify subject group identifiers and the privileges each identifier holds. + +**SEC-13:** The management system should include the ability to delete subject group identifiers and the privileges each identifier holds. + +**SEC-14:** The management system should include the ability to map subjects to subject groups. + +#### **7.2.3 Subject propagation management FE** + +Because there will be situations where management of an object through the OS may not be available, subjects and subject groups related information must be combined and propagated to the object. This requires the management of the distribution, modification, and removal of authentication credentials, access rules, and privileges to the object. + +**SEC-15:** The subject and subject group attributes should be passed to the managed elements in the appropriate supported protocol, such as XML, SNMPv3, HTTP, HTTPS, telnet, ssh, FTP, TFTP, setp, sftp, etc., in compliance with [ITU-T M.3016.1]. + +These protocols are defined in the identified IETF RFCs: XML, SNMPv3 [b-IETF RFC 3414], HTTP [b-IETF RFC 2616], HTTPS [b-IETF RFC 2818], telnet [b-IETF RFC 854], ssh + +[b-IETF RFC 4251], FTP [b-IETF RFC 959], TFTP [b-IETF RFC 1350], sctp [b-IETF RFC 4960], and sftp [b-IETF RFC 913]. + +#### 7.2.4 Authentication management FE + +Authentication includes validation of systems or administrative users, and permissions assigned to those systems/users. + +Application user authentication is responsible for ensuring that when a subject claims to own a specific identity, the identity can be verified as truly belonging to that subject. The subject can be: + +- A human logging into an application executing within a ME; or +- An application executing within one ME initially communicating with a peer application executing within a different ME. + +This service performs: + +- The initial identity authentication; +- Verification of authentication credentials validity, as necessary; and +- Negotiation of any security attributes necessary for data-origin authentication within applications, if applicable. + +One example of peer-entity authentication within applications is the "classic" log-in identifier (ID) and log-in password for human subjects. A variation on this theme is the RADIUS protocol typically used for remote access. RADIUS can work in a simple log-in ID and password mode or in a "Challenge/Response" mode. Other recent techniques are the physical token, which contains authentication information that may be used to authenticate the claimed identity of a human subject, and keyboards, which contain built-in biometric fingerprint readers. The most recent technology in this space are "smart-cards": credit card like intelligent devices that include processing capabilities and non-volatile storage for asymmetric cryptographic private keys and digital public-key certificates of a PKI. + +For communication between application processes, some of the mechanisms based on the use of cryptographic material are: + +- A digital authenticator created by producing a message digest from an application message and a shared symmetric secret key (used by many routing protocols, network protocols such as NTPv3 [b-IETF RFC 1305] and management protocols such as SNMPv3). +- Digital signatures (frequently combined with digital public-key certificates of a PKI) as used by the transport layer security (TLS) protocol [b-IETF RFC 4346], the secure sockets layer (SSL) protocol, the secure shell (SSH) protocol replacement for FTP, and telnet. However TLS, SSL, and SSH only support applications that rely on TCP [b-IETF RFC 793]. TLS and SSL are also used with the common object request broker architecture (CORBA). +- The Kerberos [b-IETF RFC 4120] security framework used either as part of the distributed computing environment (DCE) or by itself with "kerberized" applications. +- IPSec, including the Internet key exchange (IKE) [b-IETF RFC 4306] [b-IETF RFC 4307] protocol, Internet security association key and management protocol (ISAKMP), the authentication header (AH) [b-IETF RFC 4302], and or the encapsulating security payload (ESP) [b-IETF RFC 4303], usable by numerous application and management protocols. + +**SEC-16:** All authentication information that traverses a data communications network, regardless of being private or public, should not travel in "clear" text or otherwise be able to be read by an eavesdropping third party. + +## 7.3 Credentials management FG + +![Figure 3 – Credentials management FG logical block diagram](a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg) + +The diagram illustrates the logical block structure of the Credentials management FG. On the left, three external entities are shown: 'Public key infrastructure (PKI) (e.g., CAs, RAs, OCSP/LDAP)', 'Key distribution (e.g., Kerberos)', and 'Other AAA (e.g., RADIUS, TACACS+, Diameter)'. Arrows point from these entities to a central box. This central box is divided into two vertical sections: 'External credentials management client FE' on the left and 'Credentials management processing FE' on the right. Below this central box, a dashed line connects to a box labeled ''. To the right of this box is another box labeled ''. A double-headed arrow between these two boxes is labeled 'Credential responses' and 'Credential requests'. The text 'M.3410(08)\_F03' is located in the bottom right corner of the diagram. + +Figure 3 – Credentials management FG logical block diagram + +**Figure 3 – Credentials management FG logical block diagram** + +Credentials management is responsible for managing all authentication credentials related to subject identities for both human and non-human subjects. Credentials management includes the creation, assignment, storage, revocation, resetting, and escrowing of credentials. These credentials include log-in passwords, asymmetric cryptographic public-private key pairs, predefined symmetric cryptographic secret key pairs, X.509v3 digital public-key certificates [ITU-T X.509], and Kerberos tickets. Also part of this FG are the servers used to host RADIUS authentication services, Kerberos authentication services, PKI public-key certificate authority and registration authority services, and LDAP public-key certificate repositories. One need remember that the management of credentials is a different set of functions vs the use of credentials for authentication of authorization enforcement. + +**SEC-17:** The credentials management FG should communicate with other SMS FGs through the use of a de jure standards-based method, such as CORBA, HTTPS/XML, etc. in compliance with [ITU-T M.3016.1]. + +#### 7.3.1 External credentials management client FE + +There may actually be multiple external credentials management client FEs, one, or more, for each type of external credentials management. As an example, the client interacting with registration authorities (RAs) within a PKI will likely use public-key cryptography standards (PKCS) (such as [b-RSA]) defined messages for requesting, retrieving and revoking digital certificates. A different client FE may be used to manage credentials information in LDAP and OCSP servers/directories. There will be other client FEs determined by the various external AAA and key distribution centres (KDC) systems deployed. + +#### 7.3.2 Credentials management processing FE + +The credentials management processing FE is responsible for controlling the administration of credentials. This FE provides storage and retrieval of passwords, pass phrases, and static secret keys. ME private keys are also escrowed by this FE. The information handled by this FE is of such significance that it should be stored in an encrypted form directly within this FE. + +### 7.4 Configuration management FG + +![Figure 4 – Configuration management FG logical block diagram](0c08e48c08f96934cd6bc6911f3069dc_img.jpg) + +The diagram illustrates the logical block structure of the Configuration Management Functional Group (FG). On the left, three external entities are shown: 'Operations system', 'ME' (Management Entity), and another 'ME'. Arrows point from each of these entities to a central block. This central block is divided into three vertical sections: 'External configuration management client FE' (left), a middle section containing two stacked boxes labeled 'Object and object group management FE' (top) and 'Object management of subject rights FE' (bottom), and a right section labeled 'Configuration management processing FE'. Below this central block, a dashed line connects to a box labeled ''. This box is connected via a double-headed arrow to another box labeled ''. In the bottom right corner, the text 'M.3410(08)\_F04' is present. + +Figure 4 – Configuration management FG logical block diagram + +**Figure 4 – Configuration management FG logical block diagram** + +The configuration management FG is responsible for what is sometimes referred to as "the management of security". As an example, it is responsible for the provisioning of credentials and other parameters (such as encryption parameters) for security associations between MEs. Configuration management is responsible for providing the ability to set, modify, and reset security-related configurable parameters within objects, especially object access control lists and the security policy criteria that transport and application plane security mechanisms require. The configuration management FG is also responsible for ensuring that any issued commands meet the currently established security policy. + +**SEC-18:** The configuration management FG should communicate with other SMS FGs through the use of a dejure standards-based method, such as CORBA, HTTPS/XML, etc. in compliance with [ITU-T M.3016.1]. + +The administrator should have the ability to enter commands in a pseudo type (Meta) language, e.g., XML, as the different type of MEs may not be consistent across like devices, i.e., routers from vendor A and vendor B. In this context, a Meta language would use syntax and semantics that are not specific and unique to any specific vendor products. While configuration may be similar, the administrator should not need to know the exact syntax for each. + +The administrator will enter the generic command and which objects or object groups will be targeted for that command. + +In the future, this function should migrate to provide security policy management where management of objects is directed by policy statements. For example, if the policy statement is "no TFTP access is allowed," the policy statement is converted into the appropriate commands to modify each object to which the policy would apply. To continue the example, the routers and firewalls would block access to the TFTP port, the host would stop the local TFTP service, the intrusion detection system would detect of the use of TFTP, etc. This capability will allow for consistent security configuration and monitoring across the entire network. + +#### 7.4.1 Object and object group management FE + +An object is an entity that contains or passes information. Examples of objects include records, blocks, pages, segments, files, directories, directory trees, programs, video displays, keyboards, clocks, printers, laptops, access points, and MEs. Object groups are similar objects that share common access and authorization rights; an example of an object group could be "all routers within a building." Object management includes the ability to place objects into trust domains. + +**SEC-19:** SMS FEs should be able to scale to accommodate the number of subjects to be managed within the enterprise; this could result in very large numbers of subjects. + +**SEC-20:** SMS FEs should be able to scale to accommodate the number of objects to be managed within the enterprise; this could result in very large numbers of objects. + +Most TSPs will deploy a growing number of MEs and distributed services that the number of subjects will grow tremendously over time. + +#### **7.4.2 Object management of subject rights FE** + +The management of objects and object groups must include the ability to manipulate the access rights (time of day, entry method, etc.) and authorization rights (read, write, delete, backup, etc.), based upon subject and subject groups. These access and authorization rights establish the rules for security functionality configuration. + +**SEC-21:** The management of objects and object groups should include the ability to add the access and authorization rights. + +**SEC-22:** The management of objects and object groups should include the ability to modify the access and authorization rights. + +**SEC-23:** The management of objects and object groups should include the ability to delete the access and authorization rights. + +#### **7.4.3 External configuration management client FE** + +There may actually be multiple external configuration management client FEs, one, or more, for each type of external configuration management systems deployed. Each client will likely use XML, or proprietarily defined messages for interacting with these external systems. + +#### **7.4.4 Configuration management processing FE** + +The configuration management processing FE is responsible for controlling, at a logical level, interaction between SMS FG components and external systems with configuration management responsibility. + +## 7.5 Fault management FG + +![Figure 5 – Fault management FG logical block diagram. The diagram shows the internal structure of the Fault Management Functional Group (FG) and its interactions with other Functional Groups (FGs).](d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg) + +The diagram illustrates the logical block structure of the Fault Management Functional Group (FG). At the top, a large box contains five stacked functional elements (FEs): + +- Security event management FE (ME events and security events) +- Security alarm management FE (ME alarms and security alarms) +- Security audit trail collection FE (ME security audit trails) +- ME log management FE (ME security log collection, storage/archiving, retrieval and reporting) +- Security log reconciliation and security audit trail analysis FE (ME security log correlation, reconciliation, analysis of security log and audit information and reporting) +- Attack analysis FE (Determination if an attack is imminent/ongoing and what corrective action is necessary) + +Below this stack, three boxes represent interactions with other FGs: + +- ** sends "Events, alarms, logs" to the central ****. +- The central **** sends "Isolation-repair" and "Recovered" information to the ****. + +A dashed line connects the bottom of the internal FE stack to the central **** box. The text "M.3410(08)\_F05" is located in the bottom right corner. + +Figure 5 – Fault management FG logical block diagram. The diagram shows the internal structure of the Fault Management Functional Group (FG) and its interactions with other Functional Groups (FGs). + +**Figure 5 – Fault management FG logical block diagram** + +The fault management FG is composed of FEs which focus on events and alarms that either are security relevant or specifically security-related. Security logs and security audit trail information are also processed by FEs in this FG. The fault management FG may also communicate to peer OSs for the transmission of SMS generated alarms and security alarms and for any alarms generated from the correlation and analysis of security events, alarms and security alarms. + +**SEC-24:** The fault management FG should communicate with the other FGs and interface modules through the use of protocols specified in [ITU-T M.3016.1]. + +#### 7.5.1 Security event management FE + +The security event management FE is responsible for receiving security events from the activity logging and alarm reporting mechanisms within transport and service stratum, along with application and management MEs. Upon receipt, these events are indexed and stored for further analysis and reporting purposes. This FE is also responsible for archiving and retrieval of prior events to/from off-site long-term storage. Each event will be received from the managed element and contains certain attributes that define the event. These attributes can include (among others): the managed element that sent the event (ME name), the ME's IP address [b-IETF RFC 791], and the time of the event as generated by the ME. This information will be used to compare to the security alarm management FE's attribute table to determine the proper notification and correct action. + +**SEC-25:** The security event management FE should be able to receive information from the following types of sources: + +- Passive logging, such as syslog and security audit trail logs; +- Active polling, such as SNMP GET/GET-Next; and +- Active alerting, such as SNMP notifications. + +A table of security-related events is stored within the SMS SMIB. + +**SEC-26:** The table for security-related events should contain a list of each managed element's security-related events. + +**SEC-27:** Each event should contain administrator defined attributes. + +**SEC-28:** The security event management FE should be responsible for archiving and retrieval of current and prior event information to/from off-site long-term storage. + +#### **7.5.2 Security alarm management FE** + +Security alarm management is responsible for collecting and reviewing managed element security-related alarms and security alarms. + +**SEC-29:** The security alarm management FE should, upon receipt of security-related alarms/security alarms, index and store these alarms for further analysis. + +**SEC-30:** The security alarm management FE should, upon receipt of security-related alarms/security alarms, index and store these alarms for reporting purposes. + +**SEC-31:** The security alarm management FE should be responsible for archiving and retrieval of current and prior security-related alarms/security alarms to/from off-site long-term storage. + +#### **7.5.3 ME log management FE** + +ME log management is responsible for receiving, archiving and retrieval of log records and files from MEs. This FE provides: + +- The ability to retrieve/receive log entries/files from MEs, as well as the operating environment logs, by time stamps and other criteria. +- Retrieval capabilities based on time, polling and ME initiated. +- Alarm generation based on failure to receive log information according to policy and other criteria. +- Definable reporting capabilities. +- Sending log information to designated repositories (both local and remote). + +**SEC-32:** The ME log management FE should provide retrieval capabilities based on time, polling and ME initiated transfers. + +**SEC-33:** The ME log management FE should provide alarm generation capabilities based on the failure to receive log information according to policy and other criteria. + +**SEC-34:** The ME log management FE should provide definable reporting capabilities. + +**SEC-35:** The ME log management FE should provide the ability to send log information to designated local repositories. + +**SEC-36:** The ME log management FE should provide the ability to send log information to designated remote repositories (both electronically and physically). + +**SEC-37:** The ME log management FE should be responsible for archiving and retrieval of current and prior security logs to/from off-site long-term storage. + +In the absence of a common message format, a translation FE will be needed to meet the above requirements. This translation FE would include the ability to convert the syntax, and perhaps the semantics, of messages between different syntax formats. + +#### **7.5.4 Security audit trail collection FE** + +Security audit trail collection is responsible for collecting and processing managed element security audit trails. Security audit trails include logs of network element executed command, and other data collected to be potentially used to facilitate a security audit. + +**SEC-38:** The SMS FGs should maintain a security audit trail of all commands issued by SMS FGs. + +**SEC-39:** The Security Audit Trail Collection FE should upon receipt of managed element security audit trails, index and store these security audit trails for further analysis. + +**SEC-40:** The Security Audit Trail Collection FE should upon receipt of managed element security audit trails, index and store these security audit trails for reporting purposes. + +**SEC-41:** The Security Audit Trail Collection FE should be responsible for archiving and retrieval of current and prior security audit trails to/from off-site long-term storage. + +#### **7.5.5 Security log reconciliation and security audit trail analysis FE** + +The security log reconciliation and security audit trail analysis FE is responsible for ascertaining criticality of each security-related event, alarm and security alarm as to the seriousness of the potential security breach each signifies. This FE provides: + +- The ability to reconcile log entries from MEs, as well as the operating environment logs, by time stamps and other criteria. +- Trend analysis capabilities. +- Alarm generation based on the results of statistical, and other criteria. +- Definable reporting capabilities. +- Sending corrective action requests and receiving notification of completion of the corrective action. + +In the context of the following five requirements, "security breach" refers to any actual or suspected compromise of confidentiality, integrity, authenticity, availability or authorized functionality. + +**SEC-42:** The security log reconciliation and security audit trail analysis FE should provide recommendations to operations personnel for ascertaining the extent of a security breach. + +**SEC-43:** The security log reconciliation and security audit trail analysis FE should provide recommendations to operations personnel for limiting the extent of any security breach. + +**SEC-44:** The security log reconciliation and security audit trail analysis FE should provide recommendations to operations personnel for acquisition of forensic information. + +**SEC-45:** The security log reconciliation and security audit trail analysis FE should provide recommendations to operations personnel for re-establishing normal services as quickly as possible, without increasing the risk of continued or further security breaches. + +**SEC-46:** The security log reconciliation and security audit trail analysis FE should be responsible for archiving and retrieval of current and prior log files and security audit trails to/from off-site long-term storage. + +In the absence of a common message format, a translation FE will be needed to meet the above requirements. This translation FE would include the ability to convert the syntax, and perhaps the semantics, of messages between different syntax formats. + +#### **7.5.6 Attack analysis FE** + +The attack analysis FE is responsible for ascertaining criticality of each security-related event and alarm as to the seriousness of the potential security breach each signifies. The attack analysis FE differs from the security log reconciliation and security audit trail analysis FE as each FE relies on different inputs, and produces different output when performing analyses. As an example, the attack + +analysis FE is driven by many different types of data including alarms and events, whereas the security log reconciliation and security audit trail analysis FE is driven by log and security audit trail inputs. This FE also provides: + +- The ability to reconcile event and alarm notifications, possibly in conjunction with performance status, from MEs, by time stamps and other criteria. +- Trend analysis capabilities. +- Alarm generation based on the results of statistical, and other criteria. +- Definable reporting capabilities. +- Sending corrective action requests and receiving notification of completion of the corrective action. + +In the context of the following five requirements, "security breach" refers to any actual or suspected violation of organizational security policies resulting in compromise of confidentiality, integrity, authenticity, availability or authorized functionality. + +**SEC-47:** The attack analysis FE should provide recommendations to operations personnel for ascertaining the extent of a security breach. + +**SEC-48:** The attack analysis FE should provide recommendations to operations personnel for limiting the extent of any security breach. + +**SEC-49:** The attack analysis FEs should provide recommendations to operations personnel for acquisition of forensic information. + +**SEC-50:** The attack analysis FE should provide recommendations to operations personnel for re-establishing normal services as quickly as possible, without increasing the risk of continued or further security breaches. + +**SEC-51:** The attack analysis FE should be responsible for archiving and retrieval of current and prior forensic information to/from off-site long-term storage. + +In the absence of a common message format, a translation function will be needed to meet the above requirements. + +## 7.6 Security policy management FG + +![Figure 6 – Security policy management FG logical block diagram](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +The diagram illustrates the logical block structure for the Security Policy Management Functional Group (FG). At the top, a box labeled '' is connected via a double-headed arrow to the central box ''. The label for this connection is 'Security policy viewing, modification, scheduling and initiation'. The central box is connected to the left box '' via a double-headed arrow labeled 'Initiated policies' and 'Security policy results'. Below the 'Communications Interface FG' box, there are two circles labeled 'ME' (Management Entity) connected by a dashed double-headed arrow, with an ellipsis between them. The central box is also connected to the right box '' via a double-headed arrow labeled 'Security policies' and 'Security policy updates'. Below the 'Security Management Information FG' box, there are two ovals labeled 'Security policy repository' and 'Security policy audit trail' connected by a dashed double-headed arrow, with an ellipsis between them. The diagram is labeled 'M.3410(08)\_F06' in the bottom right corner. + +Figure 6 – Security policy management FG logical block diagram + +**Figure 6 – Security policy management FG logical block diagram** + +The security policy management FG assists in or performs the translation of security policies to security policy rules that can be communicated, interpreted and implemented by MEs and audited by the security policy management FG. Security policy management FG includes the capabilities to develop, communicate and schedule security policy decisions throughout an organization. Security policies may include organization-wide password complexity and aging, organization-wide single sign-on use, organization-wide encryption algorithm settings, organization-wide revoking of credentials, etc. The security policy management FG can provide: + +- Security policy viewing, modification, versioning, revocation and initiation +- Security policy dissemination to MEs +- Security policy auditing +- Security policy repository, including security policy audit trail +- Security policies scheduling +- Periodic security policy review and policy updates + +**SEC-52:** The security policy management FG should maintain a repository of initiated security policies, pending security policies, potential security policies, draft/revoked security policies and a security audit trail of security policy modifications and initiations. + +**SEC-53:** The security policy management FG should include the ability to add, modify, delete, schedule, revoke and initiate security policies. + +**SEC-54:** The security policy management FG should communicate initiated security policies to MEs. + +**SEC-55:** The security policy management FG should include the ability to audit MEs as to their application of the current security policies. + +### 7.7 Verification and validation management FG + +![Figure 7 – Verification and validation management FG logical block diagram. The diagram shows a central block representing the 'Verification & validation Management FG'. This block is divided into three vertical sections: 'Adjunct security, device, and application interface FE', 'ME report translation to Meta language FE', and 'Fault management forwarding FE'. On the left, four boxes ('Intrusion detection', 'Vulnerability scanning', 'Compliance management', and 'Other adjunct security devices') point to the first section. A dashed line connects the bottom of the central block to a box labeled ''. An arrow labeled 'Events/alarms/logs' points from this box to another box labeled ''. The text 'M.3410(08)_F07' is in the bottom right corner.](94fd137860c16c8dfd75512f10161fe8_img.jpg) + +Figure 7 – Verification and validation management FG logical block diagram. The diagram shows a central block representing the 'Verification & validation Management FG'. This block is divided into three vertical sections: 'Adjunct security, device, and application interface FE', 'ME report translation to Meta language FE', and 'Fault management forwarding FE'. On the left, four boxes ('Intrusion detection', 'Vulnerability scanning', 'Compliance management', and 'Other adjunct security devices') point to the first section. A dashed line connects the bottom of the central block to a box labeled ''. An arrow labeled 'Events/alarms/logs' points from this box to another box labeled ''. The text 'M.3410(08)\_F07' is in the bottom right corner. + +**Figure 7 – Verification and validation management FG logical block diagram** + +The verification and validation management FG receives reports through interface modules from security subsystems, devices and applications, which are adjunct to other FEs; these include intrusion detection systems, intrusion prevention systems, vulnerability scanners, integrity checkers, firewalls, compliance managers, etc. The information received by the verification and validation + +management FG is translated into the SMS Meta language. These converted reports will be sent to other SMS FEs where they are indexed and stored for further analysis and reporting purposes. + +#### 7.7.1 Adjunct security, device and application interface FE + +There may actually be multiple adjunct security, device and application interface FEs, one, or more, for each type of external security system deployed. Each interface FE will likely have used XML, or proprietarily, defined messages for interacting with these external systems, such as: intrusion detection systems, intrusion prevention systems, firewalls, vulnerability scanners, and compliance managers. + +#### 7.7.2 ME report translation to meta language FE + +The ME report translation to meta language FE is responsible for translating the information received from external security products and software into a common meta language representation used by all SMS FGs and FEs. This FE can also be responsible for consolidation or otherwise reducing the volume of information. + +#### 7.7.3 Fault management forwarding FE + +The fault management forwarding FE is responsible for interfacing with FEs within the SMS fault management FG and any other TSP specified OSs. + +**SEC-56:** The verification and validation management FG should communicate with the other SMS FGs through the use of protocols specified in [ITU-T M.3016.1]. + +**SEC-57:** The vendor of SMS FEs should provide an application programming interface (API) so that vendors of adjunct security subsystems, devices and applications can produce an interface module for their product. + +## 7.8 Corrective action management FG + +![Figure 8 – Corrective action management FG logical block diagram. The diagram shows the internal structure of the Corrective Action Management FG and its interaction with the Fault Management FG. The Corrective Action Management FG contains four functional elements: Alarm processing FE, Notification FE, Response FE, and Adjunct trouble ticket FE. The Alarm processing FE, Notification FE, and Response FE are stacked vertically and connected to the Adjunct trouble ticket FE. The Adjunct trouble ticket FE is connected to two external 'Adjunct trouble ticket' systems via 'Repair' and 'Fixed' messages. The Fault Management FG is connected to the Corrective Action Management FG via 'Isolation-repair' and 'Recovered' messages. The diagram is labeled M.3410(08)_F08.](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +``` +graph LR + subgraph CAM_FG [Corrective Action Management FG] + AP[Alarm processing FE] + N[Notification FE] + R[Response FE] + ATT[Adjunct trouble ticket FE] + AP --- ATT + N --- ATT + R --- ATT + end + FMG[Fault Management FG] -- "Isolation-repair" --> CAM_FG + CAM_FG -- "Recovered" --> FMG + ATT -- "Repair" --> ATT1((Adjunct trouble ticket)) + ATT1 -- "Fixed" --> ATT + ATT -- "Repair" --> ATT2((Adjunct trouble ticket)) + ATT2 -- "Fixed" --> ATT + ATT2 -.-> Dots[...] + Dots -.-> ATT3((Adjunct trouble ticket)) + ATT3 -- "Fixed" --> ATT +``` + +Figure 8 – Corrective action management FG logical block diagram. The diagram shows the internal structure of the Corrective Action Management FG and its interaction with the Fault Management FG. The Corrective Action Management FG contains four functional elements: Alarm processing FE, Notification FE, Response FE, and Adjunct trouble ticket FE. The Alarm processing FE, Notification FE, and Response FE are stacked vertically and connected to the Adjunct trouble ticket FE. The Adjunct trouble ticket FE is connected to two external 'Adjunct trouble ticket' systems via 'Repair' and 'Fixed' messages. The Fault Management FG is connected to the Corrective Action Management FG via 'Isolation-repair' and 'Recovered' messages. The diagram is labeled M.3410(08)\_F08. + +Figure 8 – Corrective action management FG logical block diagram + +The corrective action management FG includes the ability to generate a message to a third-party produced corrective action system, i.e., trouble ticket system, and self-maintain its own trouble ticket or work order system. + +**SEC-58:** The corrective action management FG should have a configurable table of security events, alarms and security alarms that can be received from the fault management FG. + +**SEC-59:** The corrective action management FG's configurable table of security events, alarms and security alarms should be populated from the fault management FG. + +**SEC-60:** The corrective action management FG's configurable table of security events, alarms and security alarms should be able to receive corresponding attributes from the fault management FG as to which trouble system the information is to be forwarded. + +The information sent to the corrective action system identifies which objects need correction, the reason for the correction, and suggested repairs for the object. Once the object has been repaired, the SMS must be able to receive a security-related event that indicates that the object has been repaired or notification that the correction cannot be made due to a negative impact on the production environment. + +**SEC-61:** Reports from the corrective action management FG should be stored as part of the fault management FG for further analysis and reporting purposes. + +#### **7.8.1 Fault management interface FE** + +The fault management interface FE provides the interface from the fault management FG FEs. It potentially collects security events, alarms, security alarms, security logs, security audit trails, attack analysis, etc. It is also responsible for any translation and volume reduction required by the corrective action management FG and notification of any in-progress attacks that the fault management FG is able to identify. + +#### **7.8.2 Alarm processing FE** + +The alarm processing FE is responsible, through the processing of fault management information, for determining what type of responses and/or actions are appropriate for isolating those MEs under attack or mitigating the impact of an attack. Isolation may involve identifying those MEs, and the associated network segments, likely to be compromised by the attack and shutting down still unaffected links that interconnect the compromised MEs from still operational MEs. Mitigation actions should include identifying whether traffic throttling (changing session admission controls or QoS-related parameters), increased levels of packet filtering (as in deep packet inspection via intrusion prevention systems) or even the blocking of usually acceptable application protocols (as altering the rules of boarder or internally deployed state full firewall functionality). + +#### **7.8.3 Notification FE** + +The notification FE is responsible for interacting with ME security administrative personnel, via the administrative interface FG, to present notifications of recommended corrective actions and allow the said personnel to edit, create, modify and make action decisions regarding recommended corrective actions. Administrative decisions are forwarded to the Response FE as appropriate. + +#### **7.8.4 Response FE** + +The Response FE is responsible for constructing directives to be sent to peer management systems and MEs as a result of the alarm processing FE activities. This FE not only constructs appropriate messages and scripts, it also handles the storage (relying on security management information FG capabilities), retrieval and overseeing the execution of these scripts or corrective action scenarios. The Response FE is subordinate to the Notification FE for what response actions are to occur. + +#### **7.8.5 Adjunct trouble ticket FE** + +An important OAM&P activity is the management of field and facility located repair and emergency response personnel. + +There may actually be multiple adjunct trouble ticket FEs, one, or more, for each type of external adjunct trouble ticket or workforce management system deployed. The adjunct trouble ticket FE receives the results of the alarm processing and response FEs, translates the results to the appropriate adjunct trouble ticket system format and synchronizes with the adjunct trouble ticket system when trouble ticket updates are made. The adjunct trouble ticket systems provide the ability to generate, store, track and close out work orders associated with the construction, repair and + +administration of security issues. The adjunct trouble ticket FE may also provide an SMS-based trouble ticket/workforce management system when an adjunct system is not available. + +## 7.9 Security management information FG + +![Figure 9 – Security management information FG logical block diagram](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) + +The diagram illustrates the logical block structure of the Security Management Information Functional Group (FG). At the top, a large circle is divided into three vertical sections. The left section is labeled 'OS application interface (LDAP, ANSI-SQL, etc.)'. The middle section is labeled 'Local information' and lists 'Subjects', 'Objects', 'MEs', 'Attributes', 'Events', 'Alarms, etc.'. The right section contains two circles labeled 'Remote security management information base repository' with an ellipsis between them. Below this large circle, a dashed line connects it to a rectangular box labeled 'OS application infrastructure non-proprietary (CORBA, DCE, Socket/XML, Java, etc.)'. This box is connected by a double-headed arrow to a box labeled ''. Another dashed line connects the large circle to a circle labeled 'Security management information base (SMIB) repository'. This circle is connected by a double-headed arrow to the 'OS application infrastructure non-proprietary' box. The label 'M.3410(08)\_F09' is located at the bottom right of the diagram. + +Figure 9 – Security management information FG logical block diagram + +**Figure 9 – Security management information FG logical block diagram** + +The security management information FG provides the functionality to manage the storage security-related information, and meta-data, both local to the SMS and remotely on other non-SMS systems. The purpose of this FG is to make the location, management of storage, and even format, of security information transparent to requesting SMS FGs. + +**SEC-62:** The security management information base repository should be a de jure standards-based approach, such as ANSI structured query language (ANSI-SQL) or LDAP accessible database. + +**SEC-63:** The security management information base repository should contain each managed element's security attributes. + +**SEC-64:** The security management information base repository's attributes should contain: + +- The name of the attribute; +- The current value of the attribute; +- The allowable values or ranges for the attribute; +- The subject groups that can access the attribute; +- The rights of each subject group to the attribute; and +- The event type for each change of the attribute value. + +SMS FEs communicate with the repository through the use of appropriate non-proprietary protocols, such as LDAP or ANSI-SQL. + +**SEC-65:** The security management information base repository should have the ability to know where information is stored (local vs remote). + +**SEC-66:** The security management information base repository should be able to add information at the storing location. + +**SEC-67:** The security management information base repository should be able to modify information at the storing location. + +**SEC-68:** The security management information base repository should be able to delete information at the storing location. + +**SEC-69:** The security management information base repository should be able to retrieve information from the storing location. + +**SEC-70:** The security management information base repository may be front-ended by an intermediary that can perform some of the responsibilities normally provided by FEs within this FG. + +### 7.10 Communications interface FG + +![Figure 10 – Communications Interface FG logical block diagram. The diagram shows a central box for the Communications Interface FG containing ME communications interface FE (authentication and command execution), Translation FE, Authentication set-up FE, Transport protocol set-up FE, and Configuration management interface FE. This central box is connected to MEs (Managed Elements) via dashed arrows. Below the central box, a box labeled '' receives 'Credentials' from a box labeled 'Required subject login authentication credentials ' and sends 'Allowed' responses to a box labeled 'Object access and authorization rights '. Dashed arrows also connect the central box to the '' box. A small label 'M.3410(08)_F10' is in the bottom right corner.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +M.3410(08)\_F10 + +Figure 10 – Communications Interface FG logical block diagram. The diagram shows a central box for the Communications Interface FG containing ME communications interface FE (authentication and command execution), Translation FE, Authentication set-up FE, Transport protocol set-up FE, and Configuration management interface FE. This central box is connected to MEs (Managed Elements) via dashed arrows. Below the central box, a box labeled '' receives 'Credentials' from a box labeled 'Required subject login authentication credentials ' and sends 'Allowed' responses to a box labeled 'Object access and authorization rights '. Dashed arrows also connect the central box to the '' box. A small label 'M.3410(08)\_F10' is in the bottom right corner. + +**Figure 10 – Communications Interface FG logical block diagram** + +The communications interface FG provides the interfaces between SMS FGs, between SMS FEs and between SMS FGs and the MEs. As an example, the communications interface FG converts the generic configuration statements defined in the configuration management FG into the specific commands for each type of ME. The commands are passed to each ME in the appropriate supported protocol, such as IP, X.25, XML, SNMPv3, HTTP, HTTPS, telnet, FTP, TFTP, scp, sftp, etc. The communications interface FG also provides the SMS communications infrastructure between the SMS FGs. + +**SEC-71:** The SMS FGs will communicate with the SMS FGs and other interface modules through the use of protocols in compliance with [ITU-T M.3016.1]. + +**SEC-72:** The communications interface FEs should set up the authentication request to the managed element and authenticate itself prior to the execution of the commands. + +**SEC-73:** The vendor of SMS FEs should provide an API in their application so that managed element vendors may supply their own interface modules. + +**SEC-74:** The communications interface FEs should obtain any necessary authentication credentials from a credentials management FE (or delegated authentication application), when required, for authenticating interaction with other MEs. + +**SEC-75:** Confidentiality should be supported for all ME – SMS interaction. + +#### **7.10.1 ME communications interface FE** + +The ME communications interface FE is responsible for the management protocol level interaction between the SMS FGs and the MEs. This FE may include multiple modules necessary to support the wide diversity of deployed MEs, many using different *de facto* or *de jure* management protocols. + +#### **7.10.2 Translation FE** + +The translation FE is responsible for translating commands and responses from the SMS meta language format to the format(s) required for particular types of MEs. Similarly, it is responsible for translating commands and responses from the ME-specific format to the format required by the SMS. This translation may require converting messages between a number of syntactical, and possibly semantically, different formats. There may be multiple translation FEs based on the different types of ME communication required, different areas of ME communication (such as alarm-specific translation) and different ME protocols (such as translation based on a specific SNMP MIB). This FE is necessary as there is no common standardized communication protocol deployed in modern infrastructures. + +#### **7.10.3 Authentication set-up FE** + +The authentication set-up FE is responsible for interacting with the ME communications interface FE to handle authentication and dynamic credentials negotiation not directly handled by the ME communications interface FE or the transport protocol set-up FE. + +#### **7.10.4 Transport protocol set-up FE** + +The transport protocol set-up FE is responsible for controlling dynamic credentials negotiation not directly handled by the ME communications interface FE or the authentication set-up FE. This FE determines, based on policy, whether layer 3 (e.g., IPSec) mechanisms or layer 4 (e.g., TLS, SSL, DTLS, SSH) mechanisms are required and ensures that the appropriate security mechanism is engaged. + +#### **7.10.5 Configuration management interface FE** + +The configuration management interface FE provides the interface to and from the configuration management FG FEs. + +# Annex A + +## Proforma – M.3410 – SMS requirements + +(This annex forms an integral part of this Recommendation) + +### A.1 Basis of profile proforma for security requirements + +#### A.1.1 Overview + +This Recommendation specifies the functional requirements of a security management system (SMS) that offers a centralized view for control and security oversight of a telecommunications service provider's infrastructure. Because different administrations and organizations require varying levels of security support, this Recommendation does not specify whether a requirement is mandatory or optional. + +The proforma defined in this Recommendation is to assist administrations and other national/international organizations to specify the mandatory and optional support of the requirements. + +The proforma is specified using the numbered requirements from this Recommendation. + +### A.2 Guidelines and instructions for proforma specification + +The proforma is specified using tabular representation. The proforma table has the following columns: + +- a) The requirement number from the Recommendation; +- b) Status; +- c) Comments or notes. + +The tables in this Recommendation have the first column completed. Organizations using the profiles should complete the tables as follows. + +For each requirement in the status column indicate: + +- m Mandatory; +- o Optional; +- c Conditional; +- x Prohibited ("x" stands for "excluded"); +- Not applicable or out of scope. + +If status is "c", the comment column should define the condition that must be true for supporting the requirement. + +The comment column is used to include information relevant for implementing the requirement according to that profile. + +### A.3 Proforma + +#### A.3.1 M.3410 security requirements + +Table A.1 contains the requirements from this Recommendation and the user should complete the other columns according to the guidelines provided above. + +**Table A.1 – Proforma for requirements in Recommendation ITU-T M.3410** + +| Security requirements | Status | Comments | +|------------------------------|---------------|-----------------| +| SEC-1 | | | +| SEC-2 | | | +| SEC-3 | | | +| SEC-4 | | | +| SEC-5 | | | +| SEC-6 | | | +| SEC-7 | | | +| SEC-8 | | | +| SEC-9 | | | +| SEC-10 | | | +| SEC-11 | | | +| SEC-12 | | | +| SEC-13 | | | +| SEC-14 | | | +| SEC-15 | | | +| SEC-16 | | | +| SEC-17 | | | +| SEC-18 | | | +| SEC-19 | | | +| SEC-20 | | | +| SEC-21 | | | +| SEC-22 | | | +| SEC-23 | | | +| SEC-24 | | | +| SEC-25 | | | +| SEC-26 | | | +| SEC-27 | | | +| SEC-28 | | | +| SEC-29 | | | +| SEC-30 | | | +| SEC-31 | | | +| SEC-32 | | | +| SEC-33 | | | +| SEC-34 | | | +| SEC-35 | | | +| SEC-36 | | | +| SEC-37 | | | +| SEC-38 | | | +| SEC-39 | | | + +**Table A.1 – Proforma for requirements in Recommendation ITU-T M.3410** + +| Security requirements | Status | Comments | +|------------------------------|---------------|-----------------| +| SEC-40 | | | +| SEC-41 | | | +| SEC-42 | | | +| SEC-43 | | | +| SEC-44 | | | +| SEC-45 | | | +| SEC-46 | | | +| SEC-47 | | | +| SEC-48 | | | +| SEC-49 | | | +| SEC-50 | | | +| SEC-51 | | | +| SEC-52 | | | +| SEC-53 | | | +| SEC-54 | | | +| SEC-55 | | | +| SEC-56 | | | +| SEC-57 | | | +| SEC-58 | | | +| SEC-59 | | | +| SEC-60 | | | +| SEC-61 | | | +| SEC-62 | | | +| SEC-63 | | | +| SEC-64 | | | +| SEC-65 | | | +| SEC-66 | | | +| SEC-67 | | | +| SEC-68 | | | +| SEC-69 | | | +| SEC-70 | | | +| SEC-71 | | | +| SEC-72 | | | +| SEC-73 | | | +| SEC-74 | | | +| SEC-75 | | | + +# Appendix I + +## Relationship of security management concepts to [ITU-T X.800] + +(This appendix does not form an integral part of this Recommendation) + +Clause 8 of [ITU-T X.800] addresses many aspects of security management for open systems interconnection. The X.800 security management structure is adopted as the basis for the infrastructure security architecture and is extended to apply to all aspects of open systems security management. + +### I.1 Trust domains + +Clause 8.1.2 of [ITU-T X.800] begins its security management discussion by considering security policy and security domains. There can be many security policies imposed by the administration(s) of distributed open systems, and open systems interconnection (OSI) security management standards should support such policies. Entities that are subject to a single security policy, administered by a single authority, are sometimes collected into what has been called a "security domain". + +In the TSP environment, trust domain is substituted for security domain. Some of the future extensions noted above have been included in [ITU-T X.810], the OSI security frameworks overview. The frameworks overview allows, but does not require, security domains to have subset and superset relationships. The TSP security architecture does allow trust domains to be hierarchically related, and so has the need for the subset and superset notions. + +### I.2 Security management information bases + +Clause 8.1.4 of [ITU-T X.800] describes security management information bases as follows: + +"The security management information base (SMIB) is the conceptual repository for all security-relevant information needed by open systems. This concept does not suggest any form for the storage of the information or its implementation. However, each end system must contain the necessary local information to enable it to enforce an appropriate security policy. The SMIB is a distributed information base to the extent that it is necessary to enforce a consistent security policy in a (logical or physical) grouping of end systems. In practice, parts of the SMIB may or may not be integrated with the MIB." + +The TSP security architecture uses SMIBs to conduct trust domain and ME management, rather than for only ME management, as implied above by the appropriate security policy for each ME. A distinct security management trust domain may be responsible for the management of a single trust domain (1:1) or several trust domains (1:many), or the trust domain may contain its security management trust domain (embedded). The SMIB in these cases, respectively, contains security information for the single trust domain, contains security information for all of the several trust domains, or is contained in the trust domain with its objects. In the "1:many" case, the trust domains may or may not be related to the same service or function. This flexibility allows a security administrator (or group of security administrators) to manage more than one trust domain from the same SMIB. Also, it implies that each security administrator has the same attributes (privileges) with respect to the security management information of all of the trust domains that share a management trust domain. (However, not every security administrator necessarily has the same attributes as the other security administrators in other areas.) + +### **I.3 Trust domain SMIB content** + +The following examples of objects might be placed in a SMIB to manage a trust domain: + +- Trust domain security policy rules; +- Member registration information; +- Member authentication criteria (e.g., strength of mechanism required); +- Member authentication information; +- Member attributes (privileges) (e.g., access privileges, release authority for inter-domain transfers); +- Visible security label information (i.e., what label, if any, is attached to information that is printed or displayed); and +- Security service and security mechanism requirements for specific applications, including intra-domain communications and inter-domain information transfer. + +#### **I.3.1 ME SMIB content** + +The ME SMIB contains information for management of security functions and resources shared by several trust domains, including hardware resources, security-critical functions (particularly security services and mechanisms), and supporting applications (e.g., credential management). More detail is given in later clauses on several of the supporting security applications and related functions. The following example classes of objects might be included in the SMIB: + +- Trust domain security policy rules. +- Security services management information. +- Security mechanisms management information. +- Supporting services and mechanisms management information (e.g., alarm reporting, information system auditing, cryptographic key distribution, security contexts, security-critical functions, security-related applications). + +#### **I.3.2 SMIB examples** + +Information is required in the ME SMIBs and the trust domain SMIBs to support secure infrastructure operations. Trust domain SMIB information items include: + +- X.509v3 certificates [ITU-T X.509] to carry appropriate security information, such as subject identity authentication certificates and subject access privilege certificates. +- User access control information for distributed operations not already contained in certificates. +- Manually distributed traffic and message shared secret keys. +- User account information not already contained in certificates (such as group memberships, demographic information). +- Accumulated security log, security event, security-related alarm, security alarm and audit data. +- ME security-related configuration data for those security services supported within each ME within the TSP infrastructure. This information will include, for each ME, object access control lists, network layer packet filtering rules, application layer message filtering rules, credential management, encryption, integrity, signature algorithm identifiers, and security protocol objects for both managed element security associations (ME-SAs) and application process security associations (APP-SAs), ME-SA default parameters, ME-SA options, APP-SA default parameters, APP-SA options, security event reporting parameters, security log management parameters, etc. + +ME SMIB security information items include: + +- Credential management, encryption, integrity, signature algorithm identifiers, and security protocol objects. +- ME access control information. +- Encryption algorithm initialization information. +- Security association configuration information. +- Compromise action information (e.g., revoked certificate lists). +- Contingency plan parameters (e.g., auto-purge and security policy replacement actions under emergency conditions). + +Some SMIB items may be held in the Directory services for ease of access by many users. Such items might include credential management information (e.g., certificates and user keying material). SMIB information stored in X.500 directories [ITU-T X.500] must be integrity-protected. + +### **I.4 Communication of security management information** + +Clause 8.1.5 of [ITU-T X.800] observes the following about the communication of security management information: + +"Management protocols, especially security management protocols, and the communication channels carrying the management information, are potentially vulnerable. Particular care shall therefore be taken to ensure that the management protocols and information are protected such that the security protection provided for usual instances of communication is not weakened." + +Security management information will be protected in accordance with the security policy of each management trust domain. Management applications used to communicate security management information will rely upon the same protocol infrastructure as other applications. Management applications operate in security contexts. Security associations that ensure secure communications between security contexts in different MEs are described in clause 6. + +Interactive distributed security exists when two different MEs are joined securely using a set of mechanisms that is referred to as security associations (SAs). The TSP security architecture utilizes two different types of SAs: + +- 1) Inter-ME security associations +- 2) Inter-application process security associations. + +#### **I.4.1 Inter-ME security associations (ME-SAs)** + +ME-SAs ensure secure communication between the two MEs engaged in communication. These ME-SAs provide continuous ME data origin authentication, data integrity, and optional message level confidentiality. The TSP security architecture relies on the capabilities within the IPsec protocol suite for the establishment of ME-SAs. However, alternative forms of security associations provided by TLS v1, SSL v3, datagram transport layer security (DTLS) v1 [b-IETF RFC 4347] and SSH are reasonable substitutes for IPsec, provided the default encryption does not have a performance or functionality impact. + +#### **I.4.2 Inter-application process security associations (APP-SAs)** + +APP-SAs ensure secure communication between a pair of application processes executing within different MEs. These APP-SAs provide peer-entity authentication and selective field data confidentiality. The TSP security architecture relies on the capabilities within the existing application layer protocols for the establishment of ME-SAs. APP-SAs between two MEs may share the same cryptographic algorithm and keys used by an ME-SA, or use different ME-SAs between the two communication MEs. The choice of which APP-SA to ME-SA arrangement must + +be specifiable for interactive communication within the same trust domain or between different trust domains. + +The security management information for a security association is contained in a SMIB and includes all the security-relevant attributes required to establish and maintain a security association, such as the trust domain label and secure communications attributes (e.g., cryptographic algorithm identifiers and keys). + +Making a decision about whether to allow establishment of a security association may require several related functions to be performed, such as the exchange and processing of security attributes of the user or ME (e.g., authenticated identity, access privileges). These attributes might be contained in a security certificate such as that defined in [ITU-T X.509]. The information contained in an X.509v3 certificate [ITU-T X.509] may be signed by any number of hierarchically related certificate-issuing authorities, down to a trust domain-specific certificate-issuing authority if that level of granularity is required. This signature verification adds greater assurance to the credibility of the information contained in the certificate. + +### **I.5 Distributed security management administration** + +Clause 8.1.6 of [ITU-T X.800] describes distributed security management administration: + +"Security management may require the exchange of security-relevant information between various system administrations, in order that the SMIB can be established or extended. In some cases, the security-relevant information will be passed through non-OSI ["out-of-band"] paths, and the local systems administrators will update the SMIB through methods not standardized by OSI [direct interaction with the MNE]. In other cases, it may be desirable to exchange such information over an OSI communication path in which case the information will be passed between two security management applications running in the real open systems. The security management application will use the communicated information to update the SMIB. Such updating of the SMIB may require the prior authorization of the appropriate security administrator." + +The TSP security architecture is consistent with this view, and uses it as the basis for TSP distributed security management. Each management trust domain uses and maintains the SMIB for the trust domain it manages. Cooperation with local administrators may be necessary for functions that cannot be managed remotely (e.g., aspects of credential management that require physical access and personal accountability dictated by administrative and environmental considerations). + +When a distributed approach for management of information systems is used, the distributed management functionality is responsible for administering MEs within the transport plane and, at the same time, relies upon the transport planes MEs for correct transport operation. Management systems will rely upon the same transport plane security structures (security services, security associations, and security protocols) as any other application. + +When distributed information systems become very large, their management becomes very complex. To make the complexity manageable, hierarchical management approaches are often adopted. It then becomes necessary to coordinate the levels of delegated management authority. The coordination is achieved by the way management information is organized and through the control of that information, as required by security policies. Hierarchical management relationships are not reflected in the way management applications communicate with one another. That is, management protocols are peer oriented, not hierarchically related. When the term hierarchical management system is used, it must be understood that a set of information relationships is being described, not a communications structure. This means that the hierarchical aspect of management is a human, organizational function. The organizations, administrators, and management systems may be organized hierarchically, but the MEs in which management applications are implemented only communicate as peers. + +Management systems are composed of management applications implemented in MEs. Some management applications must coexist with other applications in MEs within the network element layer (NEL) of the telecommunications management network (TMN) model. For logistical reasons, it is necessary to dedicate some MEs to management system activities. This is especially true at the element, network, system, and business management layers of the TMN model. Management systems can be grouped into categories based on the particular type of management function being performed. While these categories are logically separate, they often support one another. The categories are: + +- Element management; +- Network management; +- Service management; and +- Business management. + +Traditional element management systems and network management systems are located within network control centres that monitor and configure network components, perform fault isolation functions, manage ME configuration attributes, and collect accounting and performance information. Security management systems typically provide information to support security services and mechanisms in all MEs. + +#### **I.5.1 Security management application protocols** + +Clause 8.1.7 of [ITU-T X.800] requires security management application protocols for the exchange of security-relevant information. The general management application protocols used within the TSP security architecture are specified in [ITU-T M.3016.1]. + +#### **I.5.2 ME security management functions** + +Clause 8.2.1 of [ITU-T X.800] observes the following about system security management: + +"System security management is concerned with the management of security aspects of the overall OSI environment. The following list is typical of the activities, which fall into this category of security management: + +- a) overall security policy management, including updates and maintenance of consistency; +- b) interaction with other OSI management functions; +- c) interaction with security service management and security mechanism management; +- d) event handling management; +- e) security audit management; and +- f) security recovery management." + +As noted previously, the TSP security architecture broadens the view of ME security management to the entire systems environment, especially with respect to the support of multiple trust domains. The topics of event handling, security audit, and security recovery management are interrelated and will be treated together. + +Clause 8.3.1 of [ITU-T X.800] describes event-handling management as follows: + +"The management aspects of event handling visible in OSI are the remote reporting of apparent attempts to violate system security and the modification of thresholds used to trigger event reporting." + +Clause 8.3.2 of [ITU-T X.800] describes security audit management as follows: + +"Security audit management may include: + +- a) the selection of events to be logged and/or remotely collected; +- b) the enabling and disabling of audit trail logging of selected events; +- c) the remote collection of selected audit records; and +- d) the preparation of security audit reports." + +Clause 8.3.3 of [ITU-T X.800] describes security recovery management as follows: + +"Security recovery management may include: + +- a) maintenance of the rules used to react to real or suspected security violations; +- b) the remote reporting of apparent violations of system security; +- c) security administrator interactions." + +These security functions are related since the event handling function deals with all the apparent security violations recognized by an ME, the audit function selects those events that will be recorded, and the recovery function acts upon some of the selected events. The selection of audited events and those requiring a recovery action is determined by trust domain security policies or by the ME security policy. + +Event handling includes local as well as remote reporting of security-related events. Depending on whether a management entity (a security manager or a security recovery application) or a user is expected to examine or act on various alarms or audit records, alarm or audit objects may be recorded in a particular management trust domain SMIB, an ME SMIB, or a user-accessible file in a trust domain. + +Security recovery actions might include terminating a particular security context, temporarily prohibiting certain activities within a trust domain, or disabling a particular communications interface. Some security recovery actions may depend on specialized data structures, such as a compromised cryptographic key material list, which controls continued use of key materials. + +#### **I.5.3 Security service management** + +Clause 8.2.2 of [ITU-T X.800] describes security service management as follows: + +"Security service management is concerned with the management of particular security services. The following list is typical of the activities which may be performed in managing a particular security service: + +- a) determination and assignment of the target security protection for the service; +- b) assignment and maintenance of rules for the selection (where alternatives exist) of the specific security mechanism to be employed to provide the requested security service; +- c) negotiation (locally and remotely) of available security mechanisms which require prior management agreement; +- d) invocation of specific security mechanisms via the appropriate security mechanism management function e.g., for the provision of administratively-imposed security services; and +- e) interaction with other security service management functions and security mechanism management functions." + +A trust domain security policy may be very specific about how security service requirements are to be met (by mandating particular security mechanisms). Alternatively, it may give only a general requirement for a security service of a particular strength and allow the security management application process to select an appropriate mechanism from those available. Each of the activities + +in the list above is concerned with an aspect of determining how security service requirements are satisfied by security mechanisms, as discussed below. + +#### **I.5.4 Determining and assigning strength of service** + +Determining security services to be used and their strength is one aspect of developing a security policy for a trust domain or an ME. The choices made are dependent on threats, vulnerabilities, and acceptable risk. That is, for large classes of information processing activities, a single determination of required security services can be made in advance because the value of the information being protected does not change often or quickly, nor do the vulnerabilities and risk. There are other classes of information activities for which it may be appropriate to choose whether or not to employ a particular security service. For example, within the same trust domain, some electronic mail messages may be of an informal or personal nature and not require a non-repudiation service, but other messages may be official business and thus may be required (by written policy) to employ a non-repudiation service. In cases like these, a selective means of invoking the security service must be available, but the strength of the service is likely to be predetermined. + +#### **I.5.5 Assigning and maintaining rules for mechanism selection** + +For a given security service, one or more security mechanisms, alone or in combination with others, may be able to implement the service. Some security mechanisms may be able to support more than one security service. + +One of the aspects of the principle of protection is that the security services chosen within a trust domain security policy each have a minimum strength associated with them. Not all the security mechanisms that support a given security service need to be provided within MEs. In particular, the ME may employ various administrative and environmental security mechanisms that contribute to the provision of one or more security services. As a result, the security mechanisms that support a given security service may be different when protecting information within an ME than when protecting information between MEs within the same trust domain or between MEs in different trust domains. The resulting security service implementations must provide at least the minimum protection demanded by the security policy in all situations. Thus, to the extent that an ME supports security services with different mechanisms and a security management application process is aware (or can be made aware) of the distinctions among activities within a trust domain, between MEs in the same trust domain, and between MEs in different trust domains, alternate choices of security mechanisms could be made. + +The added complexity involved in making such choices might lead information system security architects to use only one set of mechanisms that satisfies a trust domain security policy in all cases. However, in some situations, this strategy would not be appropriate. For example, if some MEs in the same trust domain often exchange large files, but only infrequently with MEs in different trust domains, a confidentiality mechanism necessary in the latter case might introduce an unacceptable performance penalty in the local situation, but administrative and environmental mechanisms could be relied upon to achieve the required level of protection. + +#### **I.5.6 Negotiating available security mechanisms** + +One or more MEs that support the same trust domain may be able to support a particular security service with more than one security mechanism, but it may not be known in advance of attempted communications which of these security mechanisms may be implemented in a specific ME. In such cases, the specific security mechanisms to be employed must be negotiated between the security services in the MEs at the time the security association is established between them. + +#### **I.5.7 Invoking security mechanisms** + +The invocation of security services and security mechanisms within the TSP security architecture involves several functions. Most applications will rely upon the resident operating system for use of + +a security service. If a request for a security service does not specify a security mechanism, the security management application process makes a choice among the available security mechanisms based on the trust domain policy and invokes it through an appropriate operating system call. Otherwise, the security management application process invokes the default security mechanism. + +Although each application could make requests for security services and security mechanisms directly to the security management application process, there are significant advantages to adopting an application programming interface (API) approach. APIs provide a common set of subroutine calls to a related set of programming functions or services. An API not only relieves application designers of creating a specific set of interfaces, but also allows underlying services to be replaced (by equivalent mechanisms) without affecting the application implementation. Various efforts define APIs for the invocation of security mechanisms. One such effort is the general security service (GSS) API intended for use with the Internet suite of communications protocols. The GSS API and other related APIs could be used to invoke all security functions by making them the standard interfaces to the security management application process (they could be incorporated into the security management application process). + +The use of a combination of the GSS API, security management application processes, and the standard kernel interface can contribute to the independence of security services and security mechanisms and to their transparency to users and applications. This independence allows different security mechanisms to be accommodated at various stages in an ME life cycle, and for MEs to accommodate trust domains with different security service requirements. + +### **I.6 Security mechanism management** + +Clause 8.2.3 of [ITU-T X.800] describes security mechanism management as follows: + +"Security mechanism management is concerned with the management of particular security mechanisms. The following list of security mechanism management functions is typical but not exhaustive: + +- a) key management; +- b) encipherment management; +- c) digital signature management; +- d) access control management; +- e) data integrity management; +- f) authentication management; +- g) traffic padding management; +- h) routing control management; and +- i) notarization management." + +The TSP security architecture adopts this list and adds availability management. + +#### **I.6.1 Key management** + +Clause 8.4.1 of [ITU-T X.800] describes key management as follows: + +"Key management may involve: + +- a) generating suitable keys at intervals commensurate with the level of security required; +- b) determination, in accordance with access control requirements, of which entities should receive a copy of each key; and +- c) making available or distributing the keys in a secure manner to entity instances in real open systems." + +It is understood that some key management functions will be performed outside the OSI environment. These include the physical distribution of keys by trusted means. + +Exchange of working keys for use during an association is a normal layer protocol function. Selection of working keys may also be accomplished by access to a key distribution centre or by pre-distribution via management protocols or manual means. + +The TSP security architecture relies upon standard key management techniques, specifically the Internet key exchange (IKE) protocol and the Internet security association key management protocol (ISAKMP) within the IETF IP security (IPSec) suite of protocols. + +#### **I.6.2 Encryption management** + +Clause 8.4.2 of [ITU-T X.800] describes encryption (encipherment) management as follows: + +"Encipherment management may involve: + +- a) interaction with key management; +- b) establishment of cryptographic parameters; +- c) cryptographic synchronization." + +The existence of an encryption mechanism implies the use of key management and of common ways to reference the cryptographic algorithms. + +The degree of discrimination of protection afforded by encryption is determined by which entities within the environment are independently keyed. This is in turn determined, in general, by the security architecture and specifically by the key management mechanism. + +A common reference for cryptographic algorithms can be obtained by using a register for cryptographic algorithms or by prior agreements between entities. + +It is expected that new cryptographic products will support multiple algorithms that can be selected by each application. In such an environment, the registration of cryptographic algorithms will be necessary so that algorithm selection can be negotiated between MEs. The ability to select a cryptographic algorithm has implications for the security management of the devices involved, such as determining under what conditions an algorithm can be employed and for auditing algorithm use. + +The creation of distributed security services, which provide communications and information security, is usually dependent on cryptographic mechanisms. Thus, the availability of low-cost cryptographic capabilities is a critical element of the TSP security architecture. These cryptographic capabilities must be sufficiently flexible to support requirements of different trust domains in the same ME. + +This flexibility will be achieved if the mechanisms accommodate multiple cryptographic algorithms and multiple key management schemes, including public key encryption schemes and various key distribution centre schemes. Otherwise, a multiplicity of cryptographic devices will be needed, resulting in increased costs. To manage these devices, there must be a registry of cryptographic algorithms and key management schemes so that the specific choices can be negotiated for a particular security association. + +#### **I.6.3 Digital signature and authenticator management** + +Clause 8.4.3 of [ITU-T X.800] describes digital signature management as follows: + +"Digital signature management may involve: + +- a) interaction with key management; +- b) establishment of cryptographic parameters and algorithms; and +- c) use of protocols between communicating entities and possibly a third party." + +There exist strong similarities between digital signature management, digital authenticator management and encryption management. + +When digital signatures support a non-repudiation service that relies upon a trusted third party, additional security management responsibilities may be added with respect to long-term archiving of keys and algorithm identifiers so that transactions can be verified well after they occur. + +#### **I.6.4 Access control management** + +Clause 8.4.4 of [ITU-T X.800] describes access control management as follows: + +"Access control management may involve distribution of security attributes (including passwords) or updates to access control lists or capabilities lists. It may also involve the use of a protocol between communication entities and other entities providing access control services." + +The distribution of security attributes includes their initial installation in a SMIB. Since not all the information in a trust domain SMIB is necessarily locally present in every ME that supports a trust domain, it may be necessary to convey access control attributes between MEs. Note that user-specific access control attributes may not always be required since a trust domain security policy may confer certain access rights on all its members. + +#### **I.6.5 Data integrity management** + +Clause 8.4.5 of [ITU-T X.800] describes data integrity management as follows: + +"Data integrity management may involve: + +- a) interaction with key management; +- b) establishment of cryptographic parameters and algorithms; and +- c) use of protocol between communicating entities." + +When using cryptographic techniques to support the data integrity service, similarities exist between data integrity management and encryption management. In some instances, within a single ME, data integrity can be attained as a by-product of strong access control mechanisms. When a strong communications data integrity service is required, cryptographic mechanisms are likely candidates. + +#### **I.6.6 Authentication management** + +Clause 8.4.6 of [ITU-T X.800] describes authentication management as follows: + +"Authentication management may involve distribution of descriptive information, passwords, or keys (using key management) to entities required to perform authentication. It may also involve use of a protocol between communicating entities and other entities providing authentication services." + +Authentication mechanisms rely upon particular authentication information to validate a given identity. The authentication information against which user-supplied authentication information is verified is stored in the SMIB and is subject to similar considerations as access control attributes. + +Authentication of the claimed identities of individuals, as individuals or as members of a group, is a typical security policy requirement. Authentication mechanisms provide varying degrees of credibility that such claims are correct. Authentication responsibilities are often shared between administrative, environmental, and technical (i.e., hardware and software) mechanisms. Probably the most common mechanism is the picture badge and the guard. The picture on the badge matching the appearance of the holder affirms the association of the individual with what the badge represents. The identity of the individual is thereby authenticated and, in some cases, the possession of the badge establishes further claims. The reading of the magnetic code on a badge matched with + +the entry of a personal identification number is similar in capability to picture confirmation. Similarly, the matching of fingerprints or retina images authenticates the identity of an individual. + +The use of keys with locks, passwords, or cipher lock codes authenticates identity only to the extent of the probability that the presenter is a valid holder of the object or information. That probability is based on the administrative handling and physical protection of such mechanisms or information. The same considerations apply to the use of smart cards, cryptographic ignition keys, and other credentials that make no positive connection with the holder. In general, non-forgeable information bound to the holder is the strongest type of authentication mechanism. Security mechanisms for authentication depend upon system security administrators who perform the initial assignment of the badge or other credential to an individual. + +The TSP security architecture relies on the use of smart cards that contain cryptographic processing and storage capabilities. These smart cards serve as picture badges for visual identification and authentication and also provide electronic authentication via the use of asymmetric (public key) cryptographic mechanisms used in conjunction with X.509v3 digital certificates. The positive connection between the possessor of a smart card picture badge and the badge is accomplished by one, or more, of the following alternatives: + +- 1) The badge holder knowing a numeric personal identification number (PIN) that matches the PIN stored within the card. +- 2) The digitized fingerprint image from one of the fingers of the badge holder matching the digitized fingerprint image stored within the card. +- 3) The combination of alternatives 1 and 2 above; namely the digitized fingerprint image and PIN supplied by the badge holder must match the corresponding objects within the smart card badge. + +The same type of asymmetric (public key) cryptographic mechanisms used in conjunction with X.509v3 digital certificates will provide electronic authentication of ME identities. With MEs, the certificates and ME private keys are stored within the ME or can be stored in a smart card that is inserted into a smart card reader built into the ME. When using smart cards with MEs, the smart card reader needs to include a lockable access door to reduce the probability of unauthorized smart card removal. + +#### **I.6.7 Traffic padding management** + +Clause 8.4.7 of [ITU-T X.800] describes traffic padding management as follows: + +"Traffic padding management may include maintenance of the rules to be used for traffic padding. For example, this may include: + +- a) pre-specified data rates; +- b) specifying random data rates; +- c) specifying message characteristics such as length; and +- d) variation of the specification, possibly in accordance with time of day and/or calendar." + +Traffic padding in physical layer communications devices is often managed as a configuration parameter. In an open systems environment, traffic padding in the physical layer will occur infrequently. Traffic padding in application layer protocols could be invoked as the result of a user request or as the result of a trust domain security policy requirement applied to all or some class of communications. The critical management aspect of satisfying such a request is to assure that the padding is applied at the correct stage of processing with respect to other security services, such as data integrity or data confidentiality. + +#### **I.6.8 Routing control management** + +Clause 8.4.8 of [ITU-T X.800] defines routing control management as follows: + +"Routing control management may involve the definition of the links or sub-networks which are considered to be either secured or trusted with respect to particular criteria." + +Routing control in open systems meeting TSP security architecture requirements will normally be restricted to choosing a particular network interface when an ME is connected to multiple networks. + +#### **I.6.9 Notarization management** + +Clause 8.4.9 of [ITU-T X.800] defines notarization management as follows: + +"Notarization management may include: + +- a) the distribution of information about notaries; +- b) the use of a protocol between a notary and the communicating entities; and +- c) interaction with notaries." + +The role of notarization management within the TSP security architecture is to be determined. + +#### **I.6.10 Availability management** + +Availability management is not described in [ITU-T X.800]. Availability mechanisms in communications networks and MEs satisfy security policy requirements for availability of communications and processing resources. The ability of communications networks to provide timely and regular service depends upon the total security architecture, implementation, and management of those systems. The techniques of redundancy, diversity, contingency reserves, and contingency planning play a large part in communications network availability. + +# Appendix II + +## SMS relationship with the role of security in other TSP management frameworks and systems + +(This appendix does not form an integral part of this Recommendation) + +### II.1 SMS relationship to ITU-T management Recommendations + +Both [b-ITU-T M.3400] and [ITU-T M.3050.2] consider system/network management capabilities. [b-ITU-T M.3400] looks at management from a functionality perspective; whereas [ITU-T M.3050.2] takes a services perspective. + +#### II.1.1 SMS relationship to [ITU-T M.3010] + +[ITU-T M.3010] addresses the functional principles and organization of a telecommunications management network (TMN) for managing networks. This Recommendation only touches on security in clause 7 as part of the following FCAPS management functional areas: + +- Fault management; +- Configuration management; +- Accounting management; +- Performance management; +- Security management. + +#### II.1.2 SMS relationship to [ITU-T M.3050.2] + +[ITU-T M.3050.2] addresses the requirements, services, and structure of the enhanced telecom operations map (eTOM) concepts for managing networks. Table II.1 provides an example of mapping the SMS FGs to eTOM processes in [ITU-T M.3050.2]. + +**Table II.1 – Mapping [ITU-T M.3050.2] services to SMS framework** + +| Administrator interface FG | Administrator account management FG | Credentials management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | [b-ITU-T M.3400] function name | eTOM process ID [ITU-T M.3050.2] | eTOM process name | +|----------------------------|-------------------------------------|---------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-----------------------------|--------------------------------|----------------------------------|---------------------------------------------| +| | | | | | | | | | | | Security management | 1.A.3.4 | Resource Performance Management | +| | | | | | | | | | | | | 1.E.2 | Enterprise Risk Management | +| | | | | | | | | | | | | 1.E.6 | Stakeholder & External Relations Management | +| | | | | | | | | | | | | 1.OFAB.1 | Customer Relationship Management | +| | | | | | | | | | | | | 1.OFAB.2 | Service Management & Operations | +| | | | | | | | | | | | | | | +| | | | | | | | | | | X | Prevention | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.6.5 | Legal Management | +| | | | | | | | | | | | | 1.F.1.5 | Order Handling | +| | | | | | | | | | | X | Legal review function set | | | + +**Table II.1 – Mapping [ITU-T M.3050.2] services to SMS framework** + +| Administrator interface FG | Administrator account management FG | Credentials management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | [b-ITU-T M.3400] function name | eTOM process ID [ITU-T M.3050.2] | eTOM process name | +|----------------------------|-------------------------------------|---------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-----------------------------|-------------------------------------------------------------|----------------------------------|----------------------------------------| +| | | | | | | | | | | | | 1.E.6.5 | Legal management | +| | | | | | | | | | | X | Physical access security function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.2 | Security Management | +| | | | | | | | | | | X | Guarding function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.2 | Security Management | +| | | | | | | | | | | X | Personnel risk analysis function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.2 | Security Management | +| | | | | | | | | | | X | Security screening function set | 1.F.1.5.2 | Authorize Credit | +| | | | | | | | | | | | | 1.F.1.5.2 | Authorize Credit | +| | | | | | | | | | | X | Detection | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.3 | Fraud Management | +| | | | | | | | | | | | | 1.F.AB.4.6 | S/P Interface Management | +| | | | | | | | | | | | | 1.O.3.1 | Resource Data Collection & Processing | +| | | | | | | | | | | | | 1.SIP.3 | Resource Development & Management | +| X | | | X | | | X | | X | X | | Investigation of changes in revenue patterns function set | 1.E.2.3 | Fraud Management | +| | | | | | | | | | | | | 1.E.2.3 | Fraud Management | +| X | | | X | X | | | | X | X | | Support element protection function set | 1.AB.3.5.1 | Collect Resource Data | +| | | | | | | | | | | | | 1.AB.3.5.2 | Process Resource Data | +| | | | | | | | | | | | | 1.AB.3.5.3 | Report Resource Data | +| | | | | | | | | | | | | 1.AB.3.5.4 | Audit Resource Usage Data | +| | | | | | | | | | | | | 1.AB.3.5.4 | Audit Resource Usage Data | +| X | | | X | X | | | X | X | X | | Customer security alarm function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.2 | Security Management | +| X | | | X | | | X | | X | X | | Customer (external user) profiling function set | 1.E.2.3 | Fraud Management | +| | | | | | | | | | | | | 1.E.2.3 | Fraud Management | +| X | | | X | | | X | | X | X | | Customer usage pattern analysis function set | 1.AB.3.5.2 | Process Resource Data | +| | | | | | | | | | | | | 1.AB.3.5.4 | Audit Resource Usage Data | +| | | | | | | | | | | | | 1.E.2.3 | Fraud Management | +| | | | | | | | | | | | | 1.E.2.3 | Fraud Management | +| X | | | X | | | X | | X | X | | Investigation of theft of service function set | 1.E.2.3 | Fraud Management | +| | | | | | | | | | | | | 1.F.AB.1.9.3 | Analyse and Manage Customer Risk | +| X | | | X | | | X | | X | X | | Internal traffic and activity pattern analysis function set | 1.O.3.1.2 | Enable Resource Performance Management | +| | | | | | | | | | | | | 1.O.3.1.2 | Enable Resource Performance Management | + +**Table II.1 – Mapping [ITU-T M.3050.2] services to SMS framework** + +| Administrator interface FG | Administrator account management FG | Credentials management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | [b-ITU-T M.3400] function name | eTOM process ID [ITU-T M.3050.2] | eTOM process name | +|----------------------------|-------------------------------------|---------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-----------------------------|--------------------------------------------------------------|----------------------------------|----------------------------------------------| +| | | | | | | | | | | | | 1.I.O.3.1.4 | Enable Resource Data Collection & Processing | +| X | | | X | X | | | X | X | X | | Network security alarm function set | 1.I.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.I.O.3.1.4 | Enable Resource Data Collection & Processing | +| X | | | X | | | X | | X | X | | | | | +| | | | | | | | | | | | Software intrusion audit function set | 1.A.B.3.5.4 | Audit Resource Usage Data | +| | | | | | | | | | | | | 1.I.E.2.2 | Security Management | +| X | | | X | X | | | X | X | X | | | | | +| | | | | | | | | | | | Support element security alarm reporting function set | 1.I.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.I.O.3.1.4 | Enable Resource Data Collection & Processing | +| | | | | | | | | | | | | | | +| | | | | | | | | | | | Containment and Recovery | 1.I.E.2.1 | Business Continuity Management | +| | | | | | | | | | | | | 1.I.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.I.E.6.5 | Legal management | +| | | | | | | | | | | | | 1.S.3.1 | Resource Strategy & Planning | +| X | | X | X | | | | | X | X | | Protected storage of business data function set | 1.I.E.2.1 | Business Continuity Management | +| X | | X | | X | | | X | X | X | | | | | +| | | | | | | | | | | | Network intrusion recovery function set | 1.F.3.2.2 | Configure & Activate Resource | +| X | | X | X | | | | | X | X | | | | | +| | | | | | | | | | | | Administration of network revocation list function set | 1.I.E.2.2 | Security Management | +| X | | X | X | | | | | X | X | | | | | +| | | | | | | | | | | | Protected storage of network configuration data function set | 1.I.E.2.1 | Business Continuity Management | +| X | | X | X | | | | X | X | X | | | | | +| | | | | | | | | | | | Severing internal connections function set | 1.F.3.2.2 | Configure & Activate Resource | +| X | | X | | X | | | X | X | X | | | | | +| | | | | | | | | | | | NE(s) intrusion recovery function set | 1.F.3.2.2 | Configure & Activate Resource | +| X | | X | X | | | | | X | X | | | | | +| | | | | | | | | | | | Administration of NE(s) revocation list function set | 1.I.E.2.2 | Security Management | +| X | | X | X | | | | | X | X | | | | | +| | | | | | | | | | | | Protected storage of NE(s) configuration data function set | 1.I.E.2.1 | Business Continuity Management | + +**Table II.1 – Mapping [ITU-T M.3050.2] services to SMS framework** + +| Administrator interface FG | Administrator account management FG | Credentials management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | [b-ITU-T M.3400] function name | eTOM process ID [ITU-T M.3050.2] | eTOM process name | +|----------------------------|-------------------------------------|---------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-----------------------------|---------------------------------------------------------|------------------------------------------------------|-------------------| +| X | | X | | X | | | X | X | X | | Exception report action function set | | | +| | | | | | | | | | | | 1.F.3.2.2 | Configure & Activate Resource | | +| | | | | | | | | | | | 1.F.3.2.4 | Collect, Update & Report Resource Configuration Data | | +| X | | X | | X | | | X | X | X | | Theft of service action function set | | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | +| | | | | | | | | | | | 1.E.6.5 | Legal Management | | +| | | | | | | | | | | | 1.F.3.2.4 | Collect, Update & Report Resource Configuration Data | | +| | | | | | | | | | | X | Legal action function set | | | +| | | | | | | | | | | | 1.E.6.5 | Legal Management | | +| | | | | | | | | | | X | Apprehending function set | | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | +| X | | X | | X | | | X | X | X | | Service intrusion recovery function set | | | +| | | | | | | | | | | | 1.F.2.2.4 | Implement & Configure Service | | +| X | | X | X | | | | | X | X | | Administration of customer revocation list function set | | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | +| X | | X | X | | | | | X | X | | Protected storage of customer data function set | | | +| | | | | | | | | | | | 1.E.2.1 | Business Continuity Management | | +| X | | X | | | | | X | X | X | | Severing external connections function set | | | +| | | | | | | | | | | | 1.F.3.2.2 | Configure & Activate Resource | | +| | | | | | | | | | | | Security Administration | | | +| | | | | | | | | | | | 1.B.2.5 | Service & Specific Instance Rating | | +| | | | | | | | | | | | 1.E.2.1 | Business Continuity Management | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | +| | | | | | | | | | | | 1.E.2.4 | Audit Management | | +| | | | | | | | | | | | 1.F.AB.4.6 | S/P Interface Management | | +| | | | | | | | | | | | 1.S.3.1 | Resource Strategy & Planning | | +| | | | | | X | | | | | X | Security policy function set | | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | +| | | | | | | | | | | X | Disaster recovery planning function set | | | +| | | | | | | | | | | | 1.E.2.1 | Business Continuity Management | | +| | | | | | | | | | | X | Manage guards function set | | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | + +**Table II.1 – Mapping [ITU-T M.3050.2] services to SMS framework** + +| Administrator interface FG | Administrator account management FG | Credentials management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | [b-ITU-T M.3400] function name | eTOM process ID [ITU-T M.3050.2] | eTOM process name | +|----------------------------|-------------------------------------|---------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-------------------------------------------------------------|-----------------------------------------------------|----------------------------------|-------------------| +| X | | | X | X | | | | X | X | Audit trail analysis function set | | | | +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| X | | | X | X | | | X | X | X | Security alarm analysis function set | | | | +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| | | | | | | | | | | X | Assessment of corporate data integrity function set | | | +| | | | | | | | | | | | 1.E.2.2 | Security Management | | +| X | X | X | X | | | | | X | X | Administration of external authentication function set | | | | +| | | | | | | | | | | | | | | +| X | X | | X | | | | | X | X | Administration of external access control function set | | | | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | Administration of external certification function set | | | | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | Administration of external encryption and keys function set | | | | +| | | | | | | | | | | | | | | +| X | | | X | | | | | X | X | Administration of external security protocols function set | | | | +| | | | | | | | | | | | | | | +| X | | | X | X | | | | X | X | Customer audit trail function set | | | | +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| X | | | X | X | | | X | X | X | Customer security alarm management function set | | | | +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | +| X | | | X | X | | | | X | X | Testing of audit trail mechanism function set | | | | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | Administration of internal authentication function set | | | | +| | | | | | | | | | | | | | | +| X | X | | X | | | | | X | X | Administration of internal access control function set | | | | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | Administration of internal certification function set | | | | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | Administration of internal encryption and keys function set | | | | +| | | | | | | | | | | | | | | +| X | | | X | X | | | | X | X | Network audit trail management function set | | | | + +**Table II.1 – Mapping [ITU-T M.3050.2] services to SMS framework** + +| Administrator interface FG | Administrator account management FG | Credentials management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | [b-ITU-T M.3400] function name | eTOM process ID [ITU-T M.3050.2] | eTOM process name | +|----------------------------|-------------------------------------|---------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-----------------------------|------------------------------------------------|----------------------------------|------------------------------------------------------| +| | | | | | | | | | | | | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.4 | Audit Management | +| | | | | | | | | | | | | 1.F.3.2.4 | Collect, Update & Report Resource Configuration Data | +| X | | | X | X | | | X | X | X | | Network security alarm management function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.O.3.1.4 | Enable Resource Data Collection & Processing | +| | | | | | | | | | | | | | | +| X | | | X | X | | | | X | X | | NE(s) audit trail management function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.E.2.4 | Audit Management | +| | | | | | | | | | | | | 1.F.3.2.4 | Collect, Update & Report Resource Configuration Data | +| | | | | | | | | | | | | | | +| X | | | X | X | | | X | X | X | | NE(s) security alarm management function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | 1.O.3.1.4 | Enable Resource Data Collection & Processing | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | | Administration of keys for NEs function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | | | +| X | X | X | X | | | | | X | X | | Administration of keys by an NE function set | 1.E.2.2 | Security Management | +| | | | | | | | | | | | | | | + +Decomposition of SMS functionality sufficient for detailed mapping to all eTOM Processes, and sub-processes, requires further study. + +#### II.1.3 SMS relationship to [ITU-T M.3060] + +[ITU-T M.3060] addresses the requirements, services, and structure of the NGN management architecture. Although clause 9.5 of [ITU-T M.3060], security considerations, notes "Security is an extensive domain with a mission to protect important business assets against different types of threats." and cites both ITU-T Recommendations M.3016-series and [ITU-T X.805]. [ITU-T M.3060] simply states that "To deal with the complexity of securing all of the NGN, including its management plane, there is a need to mechanize the application of various security services, mechanisms, and tools by employing operation systems to automate the process. Requirements and architecture for such operations systems, also known as Security Management Systems (SMS), is for further study." + +#### II.1.4 SMS relationship to [b-ITU-T M.3400] management service function sets + +[b-ITU-T M.3400] notes that a "TMN management function is a cooperative interaction between application processes in managing and managed systems for the management of telecommunications resources, and is the smallest functional part of a TMN management service as perceived by the TMN users." + +[b-ITU-T M.3400] goes on to say: + +"Within the scope of TMN management context, TMN management services are defined by the descriptions of roles, related resources and TMN functions. The TMN management functions that belong together according to context are grouped into TMN management function sets (and the sets into groups) for the purpose of management information modelling. TMN management function sets may be reusable for TMN management services applied to different telecommunications managed areas. + +TMN management function sets are described from the TMN users' perspective and they are independent from the individual protocols as well as management information modelling so that the applicability to the diversified protocols in TMN interfaces will be maintained. + +The managers and agents identified in this Recommendation are capabilities of function blocks in TMN building blocks: Operations Systems (OSs), Mediation Devices, Network Elements (NEs), Work Stations, or Q Adaptors. Function blocks in NEs and Q Adaptors act as agents when interacting with function blocks in OSs and Mediation Devices. Further information is provided in specific Recommendations on TMN Management Services. + +Each TMN Management Function Set contains a list of the TMN Management Functions that are supported by a function block. + +The Management Requirements subclause for each TMN Management Function Set describes the purpose, internal functionality and overall input and output information flow to the function block that supports the TMN Function Set. + +A recommended assignment to a logical layer is provided for each function block (where possible). For example, a function block that deals with requests for a service sent by a service customer to a service provider would be assigned to the Service Management Layer (the block would be called an S-OSF, an Operations System Function block of the Service Management Layer). Such an assignment would imply that the TMN Management Functions, in the context of that TMN Management Function Set, could be used within the Service Management layer, or between that layer and any other layer (as specified in the General Functional Model)." + +Table II.2 provides an example of mapping the SMS FGs to function sets in [b-ITU-T M.3400]. + +**Table II.2 – Mapping [b-ITU-T M.3400] services to SMS framework** + +| [b-ITU-T M.3400] clause | [b-ITU-T M.3400] function set | Administrator interface FG | Administrator account management FG | Credential management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | +|-------------------------|----------------------------------------------|----------------------------|-------------------------------------|--------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|--------|-----------------------------|-----------------------------| +| 9 | Security Management | – | – | – | – | – | – | – | – | – | – | – | +| 9.1 | Prevention | – | – | – | – | – | – | – | – | – | – | – | +| 9.1.1 | Legal review | | | | | | | | | | | X | +| 9.1.2 | Physical access security | | | | | | | | | | | X | +| 9.1.3 | Guarding | | | | | | | | | | | X | +| 9.1.4 | Personnel risk analysis | | | | | | | | | | | X | +| 9.1.5 | Security screening | | | | | | | | | | | X | +| 9.2 | Detection | – | – | – | – | – | – | – | – | – | – | – | +| 9.2.1 | Investigation of changes in revenue patterns | X | | | X | | | X(1) | | X | X | | +| 9.2.2 | Support element protection | X | | | X | X(2) | | | | X | X | | + +**Table II.2 – Mapping [b-ITU-T M.3400] services to SMS framework** + +| [b-ITU-T M.3400] clause | [b-ITU-T M.3400] function set | Administrator interface FG | Administrator account management FG | Credential management FG | Configuration management FG | Fault management FG | Security policy management FG | Verification & validation management FG | Corrective action management FG | SMI FG | Communications interface FG | No corresponding SMS clause | +|-------------------------|-------------------------------------------------|----------------------------|-------------------------------------|--------------------------|-----------------------------|---------------------|-------------------------------|-----------------------------------------|---------------------------------|----------|-----------------------------|-----------------------------| +| 9.2.3 | Customer security alarm | X | | | X | X(3) | | | X(4) | X | X | | +| 9.2.4 | Customer (external user) profiling | X | | | X | | | X(5) | | X | X | | +| 9.2.5 | Customer usage pattern analysis | X | | | X | | | X(6) | | X | X | | +| 9.2.6 | Investigation of theft of service | X | | | X | | | X(7) | | X | X | | +| 9.2.7 | Internal traffic and activity pattern analysis | X | | | X | | | X(8) | | X | X | | +| 9.2.8 | Network security alarm | X | | | X | X(3) | | | X(4) | X | X | | +| 9.2.9 | Software intrusion audit | X | | | X | | | X(9) | | X | X | | +| 9.2.10 | Support element security alarm reporting | X | | | X | X(3) | | | X(4) | X | X | | +| 9.3 | Containment and Recovery | – | – | – | – | – | – | – | – | – | – | – | +| 9.3.1 | Protected storage of business data | X | | X | X | | | | | X | X | | +| 9.3.2 | Exception report action | X | | X | | X(10) | | | X(4) | X | X | | +| 9.3.3 | Theft of service action | X | | X | | X(10) | | | X(4) | X | X | | +| 9.3.4 | Legal action | | | | | | | | | | | X | +| 9.3.5 | Apprehending | | | | | | | | | | | X | +| 9.3.6 | Service intrusion recovery | X | | X | | X(10) | | | X(4) | X | X | | +| 9.3.7 | Administration of customer revocation list | X | | X | X | | | | | X | X | | +| 9.3.8 | Protected storage of customer data | X | | X | X | | | | | X | X | | +| 9.3.9 | Severing external connections | X | | X | | | | | X(4) | X | X | | +| 9.3.10 | Network intrusion recovery | X | | X | | X(10) | | | X(4) | X | X | | +| 9.3.11 | Administration of network revocation list | X | | X | X | | | | | X | X | | +| 9.3.12 | Protected storage of network configuration data | X | | X | X | | | | | X | X | | +| 9.3.13 | Severing internal connections | X | | X | X | | | | X(4) | X | X | | +| 9.3.14 | NE(s) intrusion recovery | X | | X | | X(10) | | | X(4) | X | X | | +| 9.3.15 | Administration of NE(s) revocation list | X | | X | X | | | | | X | X | | +| 9.3.16 | Protected storage of NE(s) configuration data | X | | X | X | | | | | X | X | | +| 9.4 | Security Administration | – | – | – | – | – | – | – | – | – | – | – | +| 9.4.1 | Security policy | | | | | | X | | | | | X | +| 9.4.2 | Disaster recovery planning | | | | | | | | | | | X | +| 9.4.3 | Manage guards | | | | | | | | | | | X | +| 9.4.4 | Audit trail analysis | X | | | X | X(11) | | | | X | X | | +| 9.4.5 | Security alarm analysis | X | | | X | X(3) | | | X(4) | X | X | | + +**Table II.2 – Mapping [b-ITU-T M.3400] services to SMS framework** + +| [b-ITU-T M.3400]
clause | [b-ITU-T M.3400]
function set | Administrator
interface FG | Administrator account
management FG | Credential
management FG | Configuration
management FG | Fault management FG | Security policy
management FG | Verification
& validation
management FG | Corrective action
management FG | SMI FG | Communications
interface FG | No corresponding
SMS clause | +|----------------------------|------------------------------------------------|-------------------------------|----------------------------------------|-----------------------------|--------------------------------|---------------------|----------------------------------|-----------------------------------------------|------------------------------------|--------|--------------------------------|--------------------------------| +| 9.4.6 | Assessment of corporate data integrity | | | | | | | | | | | X | +| 9.4.7 | Administration of external authentication | X | X(12) | X | X | | | | | X | X | | +| 9.4.8 | Administration of external access control | X | X(13) | | X | | | | | X | X | | +| 9.4.9 | Administration of external certification | X | X | X | X | | | | | X | X | | +| 9.4.10 | Administration of external encryption and keys | X(14) | X(14) | X(14) | X(14) | | | | | X(14) | X(14) | | +| 9.4.11 | Administration of external security protocols | X | | | X | | | | | X | X | | +| 9.4.12 | Customer audit trail | X | | | X | X(11) | | | | X | X | | +| 9.4.13 | Customer security alarm management | X | | | X | X(3) | | | X(4) | X | X | | +| 9.4.14 | Testing of audit trail mechanism | X | | | X | X(11) | | | | X | X | | +| 9.4.15 | Administration of internal authentication | X | X(12) | X | X | | | | | X | X | | +| 9.4.16 | Administration of internal access control | X | X(13) | | X | | | | | X | X | | +| 9.4.17 | Administration of internal certification | X | X | X | X | | | | | X | X | | +| 9.4.18 | Administration of internal encryption and keys | X(14) | X(14) | X(14) | X(14) | | | | | X(14) | X(14) | | +| 9.4.19 | Network audit trail management | X | | | X | X(11) | | | | X | X | | +| 9.4.20 | Network security alarm management | X | | | X | X(3) | | | X(4) | X | X | | +| 9.4.21 | NE(s) audit trail management | X | | | X | X(11) | | | | X | X | | +| 9.4.22 | NE(s) security alarm management | X | | | X | X(3) | | | X(4) | X | X | | +| 9.4.23 | Administration of keys for NEs | X(14) | X(14) | X(14) | X(14) | | | | | X(14) | X(14) | | +| 9.4.24 | Administration of keys by an NE | X(14) | X(14) | X(14) | X(14) | | | | | X(14) | X(14) | | + +**Table II.3 – Notes for Table II.2** + +| X(n) where n = | SMS Functional Entities (FEs) within SMS Functional Groups (FGs) | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | External (Adjunct) Revenue Analysis FE that interacts with the Verification & Validation FG | +| 2 | Security Event Mgt. FE within the Fault Mgt. FG | +| 3 | Security Alarm Mgt. FE and attack analysis FE within the Fault Mgt. FG | +| 4 | Response FE within the Corrective Action Mgt. FG | +| 5 | Adjunct Security, Device and Application Interface FE within the Verification & Validation FG that interacts with an external system | +| 6 | External system that interacts with the Adjunct Security, Device and Application Interface FE within the Verification & Validation FG | +| 7 | Adjunct Security, Device and Application Interface FE within the Verification & Validation FG that interacts with an external system | +| 8 | Adjunct Security, Device and Application Interface FE within the Verification & Validation FG that interacts with an external system | +| 9 | Adjunct Security, Device and Application Interface FE within the Verification & Validation FG that interacts with an external system | +| 10 | Attack Analysis FE within the Fault Mgt. FG | +| 11 | ME Log Mgt. FE within the Fault Mgt. FG | +| 12 | Authentication Mgt. FE within the Administrator Account Mgt. FG | +| 13 | Subject Mgt, Subject Group Mgt., Subject Propagation Mgt., Authentication Mgt. FEs within the Administrator Account Mgt. FG | +| 14 | SMS FEs involved to the extent necessary to support key distribution and session symmetric keys not dynamically managed by MEs via IPSec, TLS/SSL, SSH, XML type mechanisms | + +Decomposition of SMS functionality sufficient for detailed mapping to all [b-ITU-T M.3400] function sets requires further study. + +### **II.2 Security of legacy/existing management systems** + +Operations systems (OSs), also referred to as OSSs, are the computerized and automated systems that help enable TSPs manage their services, share information, process orders and billing, handle maintenance, and report requests of new customers. It is a generic name provided to any software system that is used to manage these very services, but was originally coined for voice line entities. Since then it has mushroomed into support for voice, data, and application/presentation level interfaces. + +As the OS is nothing more than a software-based system (each with its own security complexities), it can all be thought of as an application/presentation level entity exhibiting those same levels of need. Each has its own way of providing policy and privilege management. Each has its own authoritative source of data with its own integrity confidentiality issues. Finally, each has at least one northbound and one southbound interface with its own key systems, notarization, and privilege/policy management. More importantly, each has its own model of securing the specific features it exhibits: + +- User Level access and authentication. +- Authoritative source integrity and access controls. +- Security and user action audit logs. +- North and southbound interfaces. + +- Wholesale access bus. + +To add to the level of control required, the OS systems also have been developed and created in a number of different ways using many different hardware and software services and methodologies. The first would be mainframe systems where presentation and application level services all extend from the same physical system. Newer OS deployments are now making use of open systems as well as client-server models, where the presentation layer is completely separate from the application layer and each requires its own level of security management based upon the services it offers. For example, the application layer maintains the golden source, provides for user actions, and provides for all the north and southbound external system interfaces. The presentation layer can be another piece of software running on a completely different machine that allows the user to interact with the application layer through a communications channel across (very typically) unsecured and open networks. By using a myriad of different architecture types and systems as well, the management of this becomes ever more complex, purely due to the total number of different platforms and how services can and are exhibited on each. + +Very similar to the needs of the OS are the requirements placed upon security by the element management systems (EMSs) as well as the network management systems (NMSs). Therefore, woven into this clause will be a description of the additional requirements above and beyond those needed by the OS. + +In the following subclause is a brief description of the various services that the OS and EMSs support in today's environment, and what specifically those systems export that require security management. In some cases, the OS and EMSs are specified to support features that do not exist today but are planned in the future. As such, some assumptions are made to provide a holistic view of the needs for the SMS OS. This clause is then concluded with a description of the services that are or will exist within the OS and EMSs that require management by the SMS. + +#### **II.2.1 Order entry and business workflow** + +The starting point for any customer driven work performed at a TSP is to take an order via a service representative within the call centres, and enter the order into the system that initiates work to provide services for the customer. The order can appear through a few different input portals. One method is for a user to enter the order information by hand via a GUI or a text-based terminal interface. In all cases, access to these systems is restricted by a request for credentials for each user that is then associated to a roles-based security system to lock access to different features of the system and the underlying supportive data. + +The second method is via the wholesale gateway, which is simply a message broker that bridges the traffic from competitive local exchange carrier (CLEC)/data local exchange carrier (DLEC) companies. + +The message brokers utilize asymmetric key pairs to provide for end point authentication. + +There are a number of transports – including the likes of CORBA, XML Web Services, and batch files – to fulfil the movement of that data once authenticated. + +The public key is typically physically shared between the endpoints by hand and the private key is stored locally in a Key ring to support the message broker in order to ensure the identity of the requester and the provider of each request. + +In some cases, the use of a certificate authority is provided for. + +Where possible, the use of managed certificate authorities should be – and is – utilized for single point of access for public key requests and to ensure its authenticity, as well as the proper local key ring management for security access to the private keys. Of course, any one single trust model does not always fit when dealing with external companies, so various trust models need to be supported such as cross-certification, hierarchical, user-centric, and inter-domain. This is driven by the + +authorities that signed the certificates provided by the remote partner and the level of security required in dealing with CLEC/DLECs. This differs from interface to interface and the sensitivity of the data that is carried over it. It should be also noted that for the wholesale gateways, the requests may not always be transported over private networks and therefore, as there is confidential customer information contained in the requests, the underlying transport is authenticated, verified, and confidentially protected. + +Once the order has been entered into the system, the business workflow takes over the responsibility to flow that order to all the necessary underlying systems via southbound interfaces. There are many different manners of communicating these orders from order entry system to all of these supporting systems. Each system provides for its own method of secured communications, or lack thereof. Obviously the origination, integrity, confidentiality, and authentication of that request must be managed as much as possible from system to system, thereby placing these very needs on the south bound interface of the ordering system. + +Finally, the ordering system and its supporting workflow maintain all of the customer details, network information, and any billing details taken on the original order in a local database or golden source of information. This information is considered highly sensitive and therefore undergoes a level of backup and security commensurate with the level of sensitivity. + +Both local and external orders are stored in a long-term storage system, as well as all security audits and any generalized security logging. All of these must be stored in such a way to ensure non-repudiation and data integrity of the logs. + +#### **II.2.2 Provisioning and activation services** + +Once an order has been taken, the next major step to perform is to ensure the necessary network resources exist to provide the requested level of service to the customer. If those resources do in fact exist, then the necessary changes are made to the network to support that new service. It is the provisioning and activation systems that provide for this level of functionality. This request for service would appear via the southbound interface to the provisioning and activation system. If the provisioning system determines there are sufficient resources, then those resources are locked and a request is sent to the activation modules for real-time modification of the underlying managed elements to support the requested services. As the provisioning system maintains the holistic view of the network from end to end, it is also responsible for providing these details via northbound interfaces to test and fault management OS systems to initiate the careful monitoring of the new service and to enter the proper tickets, where applicable. + +It should be noted at this point that this level of provisioning is considered service level provisioning. There is yet another layer called infrastructure that is preformed prior to services turn up. This is when the engineers build new equipment and place it in the proper central offices, and then build the necessary physical interconnects, as well as the one-time logical resources within the device to support auto-flow provisioning. + +Once the provisioning system has fully allocated and locked down the resources, the activation systems take over and communicate either to the EMS/NMS or to the managed element directly through a number of different protocol types and stacks. Each protocol and stack has its own security requirements and needs. The activation systems communicate with the physical MEs to make the necessary changes to support the new service for the customer. It has the capability to pull back all the data within the MEs for the purposes of reconciliation of the golden source for the provisioning system to the physical network as well. + +Another area of security control is the golden source of data that represents the global view of the network. Obviously this data is a corporate asset that must be secured: who is able to alter that view must also be controlled as well, and whether that request appears from a machine-to-machine interface or a user-to-machine interface. + +Of course, with any changes to the network, all actions and requests are greatly audited and stored for long term retrieval. This raises concerns for repudiation and data integrity for those audits as well as generalized security logging. + +#### **II.2.3 Testing services** + +Once a new service has been turned up by the activation and provisioning system, all of the necessary customer service path information is sent to the test system, and a request to verify the integrity of the new service is specified. The test systems will then issue various tests that can be either disruptive or non-disruptive to ensure that the service is in fact working as it should be. The request for this will appear via a northbound interface from the provisioning system. + +Another mode of request is when the operations organization is provided a ticket specifying that a customer indicated service is in a non-working state. This very system will be used to determine where the fault, if any, may lie. The requests to the test OS are submitted from a presentation layer interface on a secured communications channel (a.k.a. northbound interface). + +It should be noted that the requests to test could only appear from personnel within the TSP. Any DLEC or CLEC issues will appear via the operations groups as described above. Therefore, the need for confidentiality of the requests is not as important. + +To perform these services, the test system is provided a complete services view of the new customer which is stored in a local golden source database. The specification for new service arrives via one of the two northbound interfaces that should be across an authenticated and notarized channel. As these tests can, in some cases, be service-affecting, it is important that the policy and privilege management also be very well managed to ensure that the request is legitimate before service disruption occurs. + +#### **II.2.4 Fault management services** + +After a service has been turned up and has undergone test to ensure it is working, it is then turned over to the fault management systems to monitor that service to ensure it is always working. If at any time a disruption occurs for that service, it is the responsibility of the fault management system to alert the necessary operations personnel that can investigate the problem and fix it, if necessary. + +Once the service has been turned up and tested, the entire service order and the entire layout of the underlying infrastructure required to support that service are transmitted to the fault management system. This information is provided via a message bus (a.k.a. northbound interface). This information is then stored in a golden source or database. The incoming information is authenticated, authorized, and then it is stored for monitoring. Of course, this data is considered sensitive so the necessary controls and retention are undertaken to ensure this data and its origin are not corrupted by accident or maliciously. + +Now that the service is properly committed to the golden source, the fault management system monitors the resources supporting all the services in the database. In most cases, the fault management communicates to either an EMS/NMS or directly to the managed elements. All of these interfaces must undergo authentication and authorization and be placed in the proper role to ensure the sufficient levels of access to the managed elements for monitoring. + +There is no one single system that supports fault management for all services. These services are broken up into a number of different systems. Unfortunately, in today's world, each system is not an island. There are a number of places where the services are layered one on top of the other. When a problem occurs, the monitoring systems must coordinate to ensure a single ticket is issued to the proper network operations centre (NOC) based upon where in the layering of resources the problem has occurred. Because of this, it means the fault management systems must all intercommunicate and share data. As such, all those communications channels as well as data sharing are authenticated, authorized, confidentially secured (if transmitted outside of local networks), and finally each sub-request is notarized. + +#### **II.2.5 Billing** + +Once the order has been completed, it is sent to the billing system so that the necessary charges can be sent to the customer. The data is transmitted on a message bus that, as with all the other systems, requires the proper levels of authentication and authorization. As the result of accepting the incoming service, a customer will be billed. It is important to ensure who sent the request and that it is a proper request. The data contained in the request for billing also will contain customer information that is highly confidential, and if subverted, could cost the customer money that is not valid. Beyond the normal services typically the data is treated properly for confidentiality. This is seen in the communication channel when securing the transmission of the data, as well as ensuring the proper levels of policy and privilege management upon the golden source of data. This of course is true, not just of the hot data, but also all backups be they standby or long term. + +#### **II.2.6 Engineering** + +To support any customer service, a number of MEs must be installed and managed. The systems that perform this role are used by the engineering groups, which store the new equipment, the exact instance of each equipment type (i.e., number of cards, type, etc), and where it is located. The information is, in most cases, transmitted either by batch transactions or on a real-time message bus to the provisioning systems. This is done so that the equipment can be used immediately for customer services. It is also done to ensure proper synchronization with the provisioning systems and the actual network, which reduces lost dollars in lack of automated flow through as well as the loss of money due to mistracked assets. The provisioning systems need to ensure that the incoming infrastructure assets are, in fact, from an authenticated source identity, and that the requesting engineer has the authorization to inject that product for service. As such, coordinated policy and privilege systems must exist between the two systems. + +#### **II.2.7 Ticketing systems** + +When a customer calls the TSP to report trouble, a ticket is entered which is then tracked through the various support organizations that will fix and monitor the problem until resolution. This ticket is opened for the lifetime of that trouble. The number of troubles reported and the duration of each is tracked daily for reports to management and, more importantly, to the Federal Communications Commission (FCC)/Public Utilities Commissions (PUCs) on fineable outages. As with any system, the normal privilege and policy management is very important to prevent spoofed tickets, which could result in lost dollars due to wasted truck roles or misplaced workforce. More importantly, the tickets must also be verified to be correct in their data validity. The long term storage as well as the reporting must ensure proper authenticity of the ticket, that it was time stamped with a secured source of time to ensure proper duration, and, most importantly, to ensure non-repudiation. + +#### **II.2.8 Outside plant management** + +Outside plant management includes not only systems to manage the work force outside of the central offices, but also any supporting system that assists them in the roles they perform. As such, work requests will arrive into outside plant (OSP) management systems via batch or on a real-time message bus. These requests are authenticated and then processed. They can either appear from the ticketing systems or the provisioning systems. + +There are a number of supporting services that assist the OSP workforce. For example, global positioning system (GPS) tracking systems can ensure the location and duration of each unit of work. Mobile devices that have the authority to take customers in and out of service or the ability to perform tests that can be service disrupting. Each of these systems communicates in batch or on a wireless channel and therefore requires identity, policy, and privilege management, as well as high levels of confidentiality. + +#### II.2.9 EMS security needs + +The element management system (EMS) is responsible for the management of MEs in the network. It typically provides for the entire FCAPS umbrella. FCAPS (fault-management, configuration, accounting, performance, and security – see [b-ITU-T M.3400] for details) is an acronym for a categorical model of the working objectives of network management. There are five levels called: the fault-management level (F), the configuration level (C), the accounting level (A), the performance level (P), and the security level (S). + +To support the FCAPS model, the EMS provides for interfaces to all the MEs under its control. At the same time, it must support interfaces to all of the OS systems that make use of these FCAPS features, in addition to presentation level services that make use of the EMS that also require policy and privilege management. + +The ability to inject security through the northbound interfaces of the EMS is not a major effort as most have been, or can be standardized on a few different technologies such as CORBA and secured XML. Of course, there are a few technologies such as TL1 that do present needs for security above and beyond the transport. In most cases, the EMS runs on operating systems that allow for the ability to plug IPSec under the covers, such that the EMS requires no code change to support authenticated communication channels, which is the primary need. The only caveat is that the EMS be capable of existing on a specific version of the operating system that supports this feature. + +The major issue is securing the southbound interfaces of the EMS. There are a myriad of protocols and each has its own issues to solve. Driving security to the ME adds cost to the device as well as complexity. Most MEs provide for a simple central processing unit (CPU) or application-specific integrated circuit (ASIC) that has very little capability and barely provides for the basic ME management. As such, an additional processing capability needs to either be built into the CPU/ASIC, or an offload security card is added to the chassis thereby reducing open slots for the device. There is really no good answer here, but the industry is slowly starting to respond. As such, in the upcoming years, the need to manage security down to the ME itself will then provide for a host of PKI capabilities that will be required. The ME will support asymmetric key authentication, data confidentiality, intrusion detection, virus detection, notarization, and many other needs. In addition, this need grows as features like firewalls are pushed directly into the managed elements. + +The EMS OS will be required to support the policy and privilege management for all of the interfaces, including the presentation layer. It must support and manage all of the PKI usage by the south- and northbound interfaces of the EMS. It must support security infrastructure on the MEs, such as firewalls. It must also support the ability to manage all of the audits and security logging that are generated from this layer of the network, which is a very large volume of information. + +#### II.2.10 NMS security additions + +The network management system (NMS) provides for all the features of the EMS but with one additional benefit. The EMS will treat the managed element as an island. Services are looked at from a single managed element perspective. The NMS takes a holistic view of the network and then provides for true end point provisioning and management. This means all of the support MEs in the network between ingress and egress points to the network are hidden from the user as it applies to provisioning. Instead, only the ingress points and egress points are specified. Of course, to do this, it means that all of the MEs that provide for that part and layer of the network must all be managed out of the single NMS. + +From a security perspective, this is not always desired. The issue is that operations groups are not always a single point of control in one geographic area. In some cases, they can be spread out regionally, such that each group has a responsibility to a single part of the network. Global access to the entire network is not always desired. In most cases, the EMS is regionalized by itself, which provides for this, but with the NMS this cannot be done. A finer level of policy and privilege + +management is required to provide for domains in the network where access and visibility can be controlled at a regional level. In some cases, this is required at even at a finer level of detail based upon access to only certain features of managed elements in each domain. The ability to delegate responsibility based upon workload, "follow the sun" support, and other business drivers is also a requirement. + +#### **II.2.11 Key system requirements** + +With the provided understanding of the OS and EMS environments, below is a list of requirements needed for the interfaces and systems described above. With these interfaces and security needs arises the need for the SMS OS to ensure the proper overall management of these resources. + +#### **II.2.12 Key management** + +Key management is a critical service required for the OS and EMS systems. Use of asymmetrical keys for all of the methodologies described above is of great importance. The proper management and centralization of keys will greatly reduce the complexity of rolling out new services as well as reduce the duplication of identities, or even worse misidentification within the company. Unfortunately, there is no one single method of centralized key authority today. Therefore, the SMS must be capable of supporting the various types of key authorities. The methods used are prescribed not just by TSP but by the various wholesale partners as well. A number of trust models must be supported and managed by the SMS OS. + +Beyond centralized key repositories, proper key management such as key rings, backup and restore, automatic key updates, and key signature management will all be critical services offered and managed by the SMS OS. + +#### **II.2.13 Non-repudiation** + +As data is moved back and forth between systems and, more importantly, wholesale partners, the capability to non-repudiate the request is of high importance. Use of technologies described elsewhere in this Recommendation are being utilized today in OS and EMS systems. But to provide a cohesive system, the ability to manage the archival of secured data and its signatures, as well as the proper archival of the keys used to sign the data, will be required in support of SMS. This of course provides for a single point of management, and thereby a single point of contact, for all repudiation issues. + +#### **II.2.14 Time-stamping** + +The use of security level time-stamping is required and used throughout security services. It is used by security audit and logging systems, key management, notarization services, data integrity, and many other areas. Therefore, the support and management of proper timing will be required for SMS as it relates to OS systems. A common time source should be available to all managed elements to facilitate time-stamp synchronization. Note that this need is broader than just security. + +#### **II.2.15 Privilege and policy management** + +The single greatest need for OS and EMSs today is the need for privilege and policy management. Each system today implements its own identity and authorization services. The ability to standardize on a single method, such as single sign on, a single method to create a corporate identity, the use of standardized roles and responsibilities, and a single point of management for all of this is required for SMS OS support. + +This not only reduces points of management but also assists in potential areas for mistakes or mis-mapping of identities to capabilities. It will also reduce the amount of time required to map a new identity to the network, and, more importantly, provides for the ability to immediately revoke capabilities. Finally, the ability to delegate responsibility by security administration allows for the seamless flow of work regardless of the need to delegate tasks for whatever reason. With a single + +point of control, this task now becomes manageable in the face of the ever-growing number of OS and EMS systems and sub-systems. + +#### **II.2.16 Notarization** + +As specified previously, while all OS and EMS systems support north- and southbound interfaces, it is not always sufficient to just authenticate the identity of the communication channel. In many cases, a single channel can be used for numerous identities. The ability to notarize each managed element of data based upon the sender becomes very important. The task of doing this grows more complex with each system deployed into the network. As such, the standardized methodology and the proper management of such a task will fall to the SMS OS. + +#### **II.2.17 Confidentiality and integrity** + +For most OS and EMS systems, the need to provide for confidentiality with the data is not as important unless that data must travel across networks that are not within the private corporate network, for example, any managed elements sent back and forth between the TSP and CLEC/DLECs. The ability to monitor and manage this service with sufficient performance levels becomes very important. + +Beyond just communication channels, the confidentiality and integrity of data maintained in global OS and data repositories, both online and offline, is required. The centralized management of such systems would fall under the tasking of the SMS OS. + +#### **II.2.18 Audit and logging** + +Most, if not all, OS and EMS systems generate copious amounts of security logging and security audit trails. The ability to collect and maintain these data trails will need to be centralized for a single point of control and thereby a single point of contact. The SMS OS will be required to interface with the various OS systems to collect this material in real time. Furthermore, the SMS is required to collect that information in such a way to ensure proper repudiation and proper long-term storage. + +#### **II.2.19 Intrusion detection** + +Every OS and EMS runs on a piece of hardware, which is provided access to the managed networks. As such, it is open to intrusion by an outside party that was not provided identified access to that box. The ability to detect and counteract the intrusions is highly important due to the sensitivity of the data contained in the OS and EMS. As such, the proper management of intrusion detection systems to ensure for a cohesive policy for this feature will be paramount. + +#### **II.2.20 Virus detection** + +The ability to either detect viruses or manage virus systems will be the key. The injection of a virus or worm into the OS and EMS or to the devices it manages is highly important. These viruses and worms can create huge breaches in the security of the network. As such, systems watching the operating systems of the OS and EMS will be required. + +#### **II.2.21 Secured software distribution** + +Most, if not all EMS, NMS, and OSs, provide for a means to automatically distribute software either to the OS itself for self-upgrade or to the ME provided by the vendor. In all cases, the management of notarization of that software load is very important. When a vendor ships a piece of software, it should also provide for the notarization of that software via a secured hash or digital signature to ensure the validity of the load as provided by the author. The same is true of the OS and EMS where software upgrades are done by either IT or external vendors. In all cases, the software should be ensured by installation/distribution systems to be from the proper author by the same means. The SMS OS should manage all of the features listed above. + +# Appendix III + +## TSP infrastructure and security service managed elements + +(This appendix does not form an integral part of this Recommendation) + +### III.1 TSP NGN security service managed elements + +Service providers are rapidly evolving from the classic TDM based public switched telephone network (PSTN) to packet-based next generation networks (NGNs) that rely on numerous access technologies and provide a wide array of customer/subscriber/user services. The objective of this appendix is to provide a brief overview of the functional requirements and architecture of standards-based NGNs (as described in [ITU-T Y.2012] scope and [b-ITU-T Y.2201] NGN release 1 requirements) and relate the security services that an SMS needs to be able to manage to the NGN framework. The [ITU-T Y.2012] functional architecture Recommendation provides a clear distinction between the definition and specification aspects of services provided by the NGN and the actual specification of the network technologies used to support those services. + +### III.2 Framework and topology of the NGN + +The NGN increases the level of complexity over existing fixed networks as a result of its architecture and services. The addition of support for multiple access technologies and for mobility results in the need to support a wide variety of network configurations. Figure III.1 shows an NGN core network with a set of example access networks. + +![Diagram of NGN core and access networks showing various network types connected to a central NGN core.](0c88b98a59dd5d549fed7b13c0ca6536_img.jpg) + +The diagram illustrates the NGN core and access networks. At the center is a circle labeled "NGN core". Surrounding it are several ovals representing different network types, all connected to the central core. Starting from the top left and moving clockwise: "Internet", "Legacy networks (ISDN/PSTN, etc.)", "Mobile networks (2G, 3G, etc.)", "Other NGN networks", "WLAN access network", and "Cellular radio access network". Below the "Cellular radio access network" is a rectangle labeled "Mobile object", which is also connected to the "NGN core". The text "M.3410(08)\_FIII.1" is located at the bottom right of the diagram. + +Diagram of NGN core and access networks showing various network types connected to a central NGN core. + +**Figure III.1 – NGN core and access networks** + +In this figure, the core network is that part of the NGN that provides NGN services contracted by the user. It is different from access network(s) in that it provides common functions shared across one or more access networks. Access networks are different from the core in that they do not provide end-user services directly (other than transport). Access and core networks may be distinguished from each other based on aspects such as technology, ownership, or administrative needs. + +Figure III.2 depicts the high-level framework or structure that serves as the basis for the NGN functional reference model. As described in [ITU-T Y.2012], this framework is organized into four layers of functionality in the vertical direction plus three domains in the horizontal direction. These are discussed in the subclauses below. + +![Figure III.2 – Framework of the NGN functional reference model. The diagram shows four horizontal layers of functions across three domains: End-user domain, Access network domain, and Core network domain. Vertical dashed lines mark the UNI, INNI, and NNI interfaces. The layers are: 1. Management functions: End user management functions (UNI) ↔ Management protocols ↔ Provider management functions (INNI) ↔ Management based control (NNI). 2. Application functions: End user application functions (UNI) ↔ Application signalling ↔ Service provider application functions (INNI) with A/S stratum management (NNI). 3. Service functions: End user service control functions (UNI) ↔ E.g., session-based signalling ↔ Service support functions / Service control functions (INNI) with SC stratum management (NNI). 4. Transport functions: End user transport functions (UNI) ↔ Access transport control functions / Access transport functions (INNI) ↔ Transport control functions / Transport processing functions (INNI) with T stratum management (NNI). Control arrows connect stratum management blocks across layers. A legend on the right lists Other network domains: Partner carrier, Visited network, Transit network, Access network. Reference M.3410(08)_FIII.2 is at the bottom right.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +Figure III.2 – Framework of the NGN functional reference model. The diagram shows four horizontal layers of functions across three domains: End-user domain, Access network domain, and Core network domain. Vertical dashed lines mark the UNI, INNI, and NNI interfaces. The layers are: 1. Management functions: End user management functions (UNI) ↔ Management protocols ↔ Provider management functions (INNI) ↔ Management based control (NNI). 2. Application functions: End user application functions (UNI) ↔ Application signalling ↔ Service provider application functions (INNI) with A/S stratum management (NNI). 3. Service functions: End user service control functions (UNI) ↔ E.g., session-based signalling ↔ Service support functions / Service control functions (INNI) with SC stratum management (NNI). 4. Transport functions: End user transport functions (UNI) ↔ Access transport control functions / Access transport functions (INNI) ↔ Transport control functions / Transport processing functions (INNI) with T stratum management (NNI). Control arrows connect stratum management blocks across layers. A legend on the right lists Other network domains: Partner carrier, Visited network, Transit network, Access network. Reference M.3410(08)\_FIII.2 is at the bottom right. + +**Figure III.2 – Framework of the NGN functional reference model** + +The NGN architecture is divided into multiple interrelated, logical layers, shown in gray above. These logical layers define logical subsets of the NGN's functions without regard to the technology used to implement those functions. Each functional layer provides capabilities to adjacent layers. This grouping is useful in understanding the functionality involved but does not imply any physical implementation. + +#### III.2.1 Management functions + +The management functions contain the management functionality relating to QoS, security, and system and network management. This functionality is responsible for providing the FCAPS (fault, configuration, accounting, performance, and security) management functions to all functional entities within all layers, e.g., operational support functions such as provisioning, configuration management, accounting and performance. + +#### III.2.2 Application functions + +The application/services functionality is responsible for: + +- i) defining and managing subscribers, including their subscriptions, their preferences, and their key data items, + +- ii) defining and managing services, including the infrastructure to support services and the common data and media functions upon which they are built, +- iii) authenticating and authorizing service users, +- iv) providing the environment for the distinct service applications (application servers, proxies, etc.). + +#### **III.2.3 Service functions** + +The service functions are responsible for handling the call processing and real-time routing of application-layer traffic within the network. It manages assignable transport resources. + +#### **III.2.4 Transport functions** + +Transport functions provide: + +- i) basic cross-connect and flow management functions (including network-layer routing) between logical ports. It manages queuing functions, communicating state and availability information about its resources to the service control stratum, +- ii) the physical termination, logical connectivity, adaptation, connection provisioning, and port functions for the management, signalling, and bearer traffic connections. + +#### **III.2.5 Functional entities and groups** + +A key component of the NGN architecture is the concept of functional entities (FEs) and functional groups (FGs). A functional entity (FE) is a cluster of functionality (sub-functions) that is viewed as a single entity from the point of view of the end-to-end functional architecture. An FE may be localized at a single geographical location (e.g., a central office, a data centre) or it may be implemented across several cooperating physical managed elements. An FE is typically a software process, or a portion of a software process, running on some managed element. The correct granularity for an FE is based on the desired or required decomposition. If the functionality can be broken down into two or more processes that could advantageously be located at different geographical or physical locations, then it is better to define two or more separate, cooperating functional entities with a relationship or association between them rather than considering the given functionality as a single functional entity. + +It should be noted that it is the possibility (and potential desirability) of functional separation that matters here. Defining a set of sub-functions as a single, distinct FE (i.e., separately from some other set of sub-functions) does not constrain the mappings to a physical implementation. It simply allows for multiple physical scenarios for the same overall set of functionality. Of course, it is always possible to combine two or more distinct FEs in a single physical implementation. This might be dictated by a particular vendor implementation or driven by performance requirements. + +- A functional entity reference model is an abstract description of a system architecture that provides a framework or structure for examining significant FEs and their key associations or relationships. The granularity of the reference model will vary with the use objectives for the model. + +Each functional layer within the framework contains a functional entity reference model: + +- A functional group (FG) is a cluster of FEs grouped (and named) solely for convenience and architectural clarity. This concept is particularly useful in descriptions of functional reference models and functional architectures as it provides a means of organizing or clustering closely-related FEs. FGs are less useful once FEs have been assigned or allocated to physical entities, as often there may not be a one-to-one mapping of FGs to physical entities. + +However, FGs are not intended to constrain FE physical groupings. + +### III.3 NGN decomposition + +The NGN network can be logically decomposed into different sub-networks, as shown in Figure III.3. The emphasis on logical decomposition instead of physical decomposition is based on the fact that, in the future, physical equipment may have features of both the access network and the core network. A pure physical decomposition will encounter difficulties when such features are combined into a single managed element. + +![Diagram of NGN decomposition showing core and access networks with domains and managed elements.](7f7211748473542096717109ebe5a9d6_img.jpg) + +The diagram illustrates the logical decomposition of an NGN into a core network and an access network. The NGN core network (top) contains two domains: Network Domain A (orange) and Network Domain B (blue). Each domain consists of three Managed Elements (MEs) connected in a mesh. The NGN access network (middle) contains two domains: Network Domain C (orange) and Network Domain D (green), also each with three MEs. At the bottom, four Customer networks are shown. Connections are as follows: solid lines (INNI) connect MEs within a domain; dashed lines (NNI) connect MEs between domains within the same network (e.g., Domain A to Domain B, or Domain C to Domain D); and dotted lines (UNI) connect MEs in the access network to the Customer networks. A legend at the bottom identifies the line types: INNI (solid), NNI (dashed), and UNI (dotted). The diagram is labeled M.3410(08)\_FIII.3. + +Diagram of NGN decomposition showing core and access networks with domains and managed elements. + +**Figure III.3 – Major components of the NGN at the network level** + +The major components of an NGN network are as follows: + +- **End-user network:** An end-user network can be a network within a home or an enterprise network. It is connected to the service provider's network via a UNI (user-to-network interface). The UNI is also the demarcation point between the service provider and the user. An end-user network may obtain its content service from: + - the core network; + - another instance of the end-user network providing public services; or + - another instance of the end-user network providing private services, possibly with a private addressing scheme. +- **Access network:** An access network collects end-user traffic from the end-user network to the core network. The access network service provider is responsible for the access network. The access network can be further partitioned into different domains, with the intra-domain interface being termed an INNI (internal network-network interface) and the + +inter-domain interface being termed an NNI (network-network interface). The access network belongs to the transport layer of functionality. + +- Core network: The core network belongs to both the transport and the service layers of functionality. The core network service provider is responsible for the core network. The interface between the core network and the access network or between core networks can be an INNI (in the case of partitioning as a single domain) or an NNI. + +The concept of an NGN domain is introduced to outline the administrative boundaries. Detailed topology information may or may not be shared across the NNI, but may be shared if available for INNI links. As depicted in Figure III.3 above, the access network and the core network may or may not belong to the same NGN domain. + +#### **III.3.1 Domains** + +The domain perspective provides a view of organizational ownership, control and trust. Any, or all, of these domain attributes may be tightly held by the domain owner or shared/entrusted to another party. + +##### **III.3.1.1 Basic domains** + +There are four major domains to be considered: + +- End-user domain +- Access domain +- Core domain +- Transit domain + +##### **III.3.1.2 End-user domain** + +This domain aggregates the various access methods for services, ranging from plain old telephones to IP phones and appliances, as well as applications that provide web access, messaging and other non-verbal communication. + +##### **III.3.1.3 Access domain** + +The access domain has a number of technologies that implement layer 1 and layer 2 forwarding plane protocols in the access function. The access domain may also include distributed L3 functions. Typically, the equipment deployed in the access domain has a relatively simple ring-based topology to distribute traffic between the end-user and the edge-aggregation domain. The access domain may also implement a passive optical network (PON) as discussed in [b-ITU-T G.983.1] and [b-ITU-T G.984.1]. + +##### **III.3.1.4 Core domain** + +This domain includes functions central to the delivery of suites of services to customers. FEs in this domain interact with FEs in all the other domains. + +##### **III.3.1.5 Transit domain** + +This domain represents peer FEs from various Partner networks with which a network operator FE will interact according to agreed upon and established rules and business relationships. + +#### Relationship between the NGN and service domains + +The NGN provides access to a wide variety of services. The specific services offered by any service provider are determined by business needs and customer needs. Figure III.4 shows an example that illustrates multiple domains within which services may be accessed. + +![Diagram illustrating the NGN example of service domains. It shows two service providers, TSP A and TSP B, connected via a central Transit network. TSP A's domain includes Information services, Core network, and Communications services, with two Access network 1 units. TSP B's domain includes Information services, Core network, and Communications services, with two Access network 1 units. The Internet is shown as a separate cloud connected to the Transit network, with two computers labeled 'Internet located services'.](d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg) + +The diagram illustrates the architecture of an NGN. At the center is a purple cloud labeled 'Transit network'. To its left is a large circle representing 'TSP A'. Inside this circle, a yellow oval is labeled 'Information services', a blue cloud is labeled 'Core network', and a green oval is labeled 'Communications services'. Two smaller blue clouds, each labeled 'Access network 1', are connected to the core network. One is associated with a mobile phone icon, and the other with a desktop computer icon. To the right is a similar large circle for 'TSP B', containing the same 'Information services', 'Core network', and 'Communications services' components, with two 'Access network 1' units connected to its core network. One is associated with a laptop icon, and the other with a mobile phone icon. Above the transit network is a blue cloud labeled 'Internet', containing two computer icons and the text 'Internet located services'. Dashed lines connect the 'Internet' cloud to the 'Transit network', and from the 'Transit network' to the 'Communications services' of both TSP A and TSP B. A small label 'M.3410(08)\_FIII.4' is in the bottom right corner. + +Diagram illustrating the NGN example of service domains. It shows two service providers, TSP A and TSP B, connected via a central Transit network. TSP A's domain includes Information services, Core network, and Communications services, with two Access network 1 units. TSP B's domain includes Information services, Core network, and Communications services, with two Access network 1 units. The Internet is shown as a separate cloud connected to the Transit network, with two computers labeled 'Internet located services'. + +**Figure III.4 – NGN example of service domains** + +In this example, TSP A supports a single access network technology that provides access to three service domains via its core network. + +- 1) One service domain is the Communications services bubble. These services may be completely within TSP A's domain or may support end-to-end services to other TSPs. In this example, TSP A supports end-to-end communication services inter-operating with TSP B's communications services. They are interconnected through a transit network. Other transit network configurations are of course allowed, and the transit network may be null in the case where TSP A is directly connected to the other endpoint network. Network access control FEs are used to protect service domain FEs within a domain from FEs in other domains and the transit network. It should also be noted that the network on the other side of the transit network might be another type of external network, such as the PSTN. +- 2) A second service domain in this example is the Information services bubble of TSP A. This could provide services such as web hosting. These service FEs may be attached directly to TSP A's core network or may be provided by third parties through agreed upon security arrangements. +- 3) A third service domain shown here is access to Internet-based services. These services are not part of TSP A's domain, nor are they provided by business arrangements with TSP A. These services are accessed via TSP A transport connections to the Internet. + +As mentioned earlier, this example shows only a small set of the possible configurations that might be supported by TSP NGNs. + +#### III.3.2 Interfaces + +The interfaces between the various FEs, as well as the boundary points between the domains, provide meeting points for integration and interoperability. Figure III.5 depicts the notion that multiple NGN core networks may interoperate to provide an end-to-end service to the user. Although not depicted, a single TSP may deploy multiple core networks within and between metropolitan regions. In a simple case, an end-to-end session will have originating and terminating core networks. Depending on the TSP's particular configuration, one or more separate access networks might be involved. + +![Diagram illustrating an NGN example of home and visited networks. It shows three cloud-like nodes: 'Visited access' on the left, 'Home core NGN-1' at the top center, and 'Home core NGN-2' on the right. 'Visited access' is connected to 'Home core NGN-1' and has a line labeled 'User-1' extending downwards. 'Home core NGN-1' is connected to 'Home core NGN-2'. 'Home core NGN-2' has a line labeled 'User-1' extending downwards. The text 'M.3410(08)_FIII.5' is located below the 'Home core NGN-2' node.](e2dad48ec062e71202459a9ab82261e4_img.jpg) + +Diagram illustrating an NGN example of home and visited networks. It shows three cloud-like nodes: 'Visited access' on the left, 'Home core NGN-1' at the top center, and 'Home core NGN-2' on the right. 'Visited access' is connected to 'Home core NGN-1' and has a line labeled 'User-1' extending downwards. 'Home core NGN-1' is connected to 'Home core NGN-2'. 'Home core NGN-2' has a line labeled 'User-1' extending downwards. The text 'M.3410(08)\_FIII.5' is located below the 'Home core NGN-2' node. + +**Figure III.5 – NGN example of home and visited networks** + +Since, in many cases, the specific division of functionality between core and access networks, and between the originating and terminating networks is based on the, or multiple, TSP's business decisions, it is difficult to precisely define the attributes that make up each of these configuration managed elements. Rather than hard points of separation in the architecture, these aspects should be thought of as configurable topology managed elements that may be mixed and matched in many different ways. + +#### III.3.3 Enterprise role model + +The primary purpose of an enterprise model is to identify interfaces that are likely to be of general commercial importance. To do this, a number of roles are identified: + +- which describe reasonably well-defined business activities that are unlikely to be subdivided between a number of players +- players may aggregate roles as they see fit +- thereby not limit players in anyway +- does identify the roles that the architecture should enable. + +A basic role model for NGN is shown in Figure III.6. It identifies the following roles: + +- **Customer:** The role denoting a person or other entity that has a contractual relationship with a service provider on behalf of one or more users. +- **User:** The role in which a person or other entity authorized by a customer uses services subscribed to by the customer. +- **Retailing service provider:** The role that has overall responsibility for the provision of a service or set of services to users associated with a subscription as a result of commercial agreements established with the users (i.e., subscription relationships). The user profile is maintained by the retailing service provider. Service provision is the result of combining wholesale network services and service provider service capabilities. +- **Wholesale service provider:** The role that combines a retailing service provider's service capabilities with its own network service capabilities to enable users to obtain services. +- **Value-added service provider:** The role that provides services other than basic telecommunications service (e.g., content provision or information services) for which additional charges may be incurred. These may be billed via the customer's service provider or directly to the customer. + +![Figure III.6 – Basic NGN roles. A diagram showing the basic roles in an NGN. It includes Customer, User, Retailing service provider, Wholesale service provider, and Value-added service provider. Solid lines with dots represent technical relations and reference points, while dashed lines represent commercial relations. A looped line connects the User to the Wholesale service provider and back to the User, indicating a reference point. The diagram is labeled M.3410(08)_FIII.6.](3bf1696c3034743b5ab07a0b5e398347_img.jpg) + +Figure III.6 – Basic NGN roles. A diagram showing the basic roles in an NGN. It includes Customer, User, Retailing service provider, Wholesale service provider, and Value-added service provider. Solid lines with dots represent technical relations and reference points, while dashed lines represent commercial relations. A looped line connects the User to the Wholesale service provider and back to the User, indicating a reference point. The diagram is labeled M.3410(08)\_FIII.6. + +**Figure III.6 – Basic NGN roles** + +This basic model provides a kind of super-class for roles and their relations. Wholesale service provider players may need to combine their services to provision an end-to-end service. This is illustrated by the looped line and reference point in Figure III.6 above. The first step in wholesale provider role specialization is shown in Figure III.7. + +![Figure III.7 – NGN roles: First level of specialization. A diagram showing the first level of specialization of NGN roles. It includes User, Access transport provider, Core service provider, Retailing service provider, Value-added service provider, and Transit transport provider. Solid lines with dots represent technical relations and reference points, while dashed lines represent commercial relations. The User is connected to the Access transport provider and the Core service provider. The Access transport provider is connected to the Core service provider. The Core service provider is connected to the Retailing service provider, Value-added service provider, and Transit transport provider. The diagram is labeled M.3410(08)_FIII.7.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +Figure III.7 – NGN roles: First level of specialization. A diagram showing the first level of specialization of NGN roles. It includes User, Access transport provider, Core service provider, Retailing service provider, Value-added service provider, and Transit transport provider. Solid lines with dots represent technical relations and reference points, while dashed lines represent commercial relations. The User is connected to the Access transport provider and the Core service provider. The Access transport provider is connected to the Core service provider. The Core service provider is connected to the Retailing service provider, Value-added service provider, and Transit transport provider. The diagram is labeled M.3410(08)\_FIII.7. + +**Figure III.7 – NGN roles: First level of specialization** + +A basic tenet of the NGN architecture is the separation of transport and service layer functions so that the transport functions will support different types of service control systems. This can be taken further by specializing the core service provider into a "core transport" and a "service control and integration" provider role. The implication is that the reference points between functions in the transport and the service functional layers become security-trust domain boundaries and will have to support inter-TSP security requirements. + +The service control and integration provider role can be split into separate service control provider and integration service provider roles. Virtual network TSPs are players who perform this role, and these are so well established that it is deemed appropriate to reflect this in the second level of specialization. The resulting role model is depicted in Figure III.8. + +![Diagram illustrating NGN roles: Second level of specialization. The diagram shows a 'User' connected to an 'Access transport provider', which is connected to a 'Retailing service provider'. This 'Retailing service provider' is connected to three other 'Retailing service provider' boxes, which are in turn connected to a 'Value-added service provider' and a 'Transit transport provider'. The diagram is labeled M.3410(08)_FIII.8.](32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg) + +``` + +graph LR + User[User] --- ATP[Access transport provider] + ATP --- RSP1[Retailing service provider] + RSP1 --- RSP2[Retailing service provider] + RSP1 --- RSP3[Retailing service provider] + RSP1 --- VASP[Value-added service provider] + RSP1 --- TTP[Transit transport provider] + +``` + +Diagram illustrating NGN roles: Second level of specialization. The diagram shows a 'User' connected to an 'Access transport provider', which is connected to a 'Retailing service provider'. This 'Retailing service provider' is connected to three other 'Retailing service provider' boxes, which are in turn connected to a 'Value-added service provider' and a 'Transit transport provider'. The diagram is labeled M.3410(08)\_FIII.8. + +**Figure III.8 – NGN roles: Second level of specialization** + +Each of the new roles has a relationship with the retailing service provider role that holds the user profile database. A retailing role player may hold the user information for all three roles, or a user may have a relationship with multiple retailing role players. In summary, the second level of specialization of the NGN enterprise model defines the following roles: + +- **User:** The role in which a person or other entity authorized by a customer uses services subscribed to by the customer. +- **Retailing service provider:** The role that has overall responsibility for the provision of a service or set of services to users. The user profile is maintained by the retailing service provider. Service provision is the result of combining retailing service provider services with wholesale services from at least the access and core transport provider roles and at most from all other provider roles. +- **Integrating service provider:** The role that creates unique new service offerings from the wholesale services provided by other roles. +- **Service control provider:** The role that provides session and call control and related services, such as registration, presence, and location, wholesale to retailing and integrating service providers. +- **Value-added service provider:** The role that provides value-added services (e.g., content provision or information services) on top of the basic telecommunications service provided by the service control provider role. It does not provide a complete service on its own. +- **Core transport provider:** The role that provides connectivity either end-to-end or in part, and related services such as registration for connectivity service, by combining its own services with those of the access transport provider and transit provider roles as necessary. +- **Access transport provider:** The role that provides a wholesale connectivity service between the user and a core transport provider. +- **Transit transport provider:** The role that provides a wholesale connectivity service between core transport providers, in conjunction with other transit transport providers as necessary. It also provides related DNS services. + +A fundamental point is that many of the aforementioned roles align with individual, and independent domains, both from an ownership perspective and an administrative and security perspective. + +### III.4 Security mechanisms within an NGN + +Identification of security FEs and allocation of these FEs to security mechanisms proceeds from an initial allocation of security services and functions and then defines the types of components and security mechanisms that are available to implement the security services with particular strengths. + +#### III.4.1 Security services + +The security services described below are the basic security services within the NGN. In practice, they will be invoked at appropriate protocol layers and within computing elements, in appropriate combinations, to satisfy TSP security policy. Particular security mechanisms can be used to implement combinations of the basic security services. Practical realizations of systems may implement particular combinations of the basic security services for direct invocation. + +**Table III.1 – Necessary NGN security services** + +| Security service functional groupings | | Applies to communications assets | Applies to computing assets | +|---------------------------------------|------------------------------------------|----------------------------------|-----------------------------| +| 1 | Authentication | | | +| 1.1 | Peer entity authentication | Yes | | +| 1.2 | Data origin authentication | Yes | | +| 1.3 | User authentication | | Yes | +| 2 | Authorization | | | +| 2.1 | Communications access controls | Yes | | +| 2.1 | Computing system access controls | | Yes | +| 3 | Confidentiality | | | +| 3.1 | Connection confidentiality | Yes | | +| 3.2 | Connectionless confidentiality | Yes | | +| 3.3 | Selective field confidentiality | Yes | Yes | +| 3.4 | Traffic flow confidentiality | Yes | | +| 4 | Integrity | | | +| 4.1 | Information integrity | | | +| 4.1.1 | Separation of duties | | Yes | +| 4.1.2 | Well-formed transactions | | Yes | +| 4.1.3 | Logging & auditing | Yes | Yes | +| 4.2 | Data integrity | | | +| 4.2.1 | Connection integrity with recovery | Yes | | +| 4.2.2 | Connection integrity without recovery | Yes | | +| 4.2.3 | Selective field connection integrity | Yes | | +| 4.2.4 | Connectionless integrity | Yes | | +| 4.2.5 | Selective field connectionless integrity | Yes | | + +**Table III.1 – Necessary NGN security services** + +| Security service functional groupings | | Applies to communications assets | Applies to computing assets | +|----------------------------------------------|----------------------------------------|-----------------------------------------|------------------------------------| +| 5 | Non-repudiation | | | +| 5.1 | Non-repudiation with proof of origin | Yes | Yes | +| 5.2 | Non-repudiation with proof of delivery | Yes | Yes | +| 5.3 | Non-repudiation of actions | Yes | Yes | + +#### **III.4.2 Authentication** + +These services provide for the authentication of identities presented/asserted by entities (a.k.a. subjects) and the identity of sources of data as described below. + +##### **III.4.2.1 Peer entity authentication** + +This service is provided for use at the establishment of, or at times during, the data transfer phase of a connection to confirm the identities of one or more of the entities connected to one or more of the other entities. This service provides confidence, at the time of usage only, that an entity is not attempting a masquerade or an unauthorized replay of a previous connection. One-way and mutual peer entity authentication schemes, with or without a liveness check, are possible and can provide varying degrees of protection as discussed in [ITU-T X.800]. + +##### **III.4.2.2 Data origin authentication** + +The data origin authentication service provides the corroboration of the source of a data unit. The service does not provide protection against duplication or modification of data units as discussed in [ITU-T X.800]. + +##### **III.4.2.3 User authentication** + +This service is provided for confirming the identity of a human subject when logging into a computer system (managed element). This service provides confidence, at the time of log-in, that a human entity is not attempting a masquerade of a different human subject. + +#### **III.4.3 Authorization** + +This service provides protection against unauthorized use of resources. These may be communications or computing resources. This protection service may be applied to various types of access to a resource (e.g., the use of a communications resource; the reading, the writing, or the deletion of an information resource; the execution of a processing resource) or to all accesses to a resource. The control of access will be in accordance with various security policies. + +##### **III.4.3.1 Communications access controls** + +This service provides protection against unauthorized use of communications resources. The control of access will be in accordance with various security policies as discussed in [ITU-T X.800]. + +##### **III.4.3.2 Computing system access controls** + +This service provides protection against unauthorized use of computing resources. The control of access will be in accordance with various security policies. + +#### **III.4.4 Confidentiality** + +These services provide for the protection of data from unauthorized disclosure as described below. + +##### **III.4.4.1 Connection confidentiality** + +This service provides for the confidentiality of all (N)-user-data on an (N)-connection as discussed in [ITU-T X.800]. + +##### **III.4.4.2 Connectionless confidentiality** + +This service provides for the confidentiality of all (N)-user-data in a single connectionless (N)-SDU (service data unit) as discussed in [ITU-T X.800]. + +##### **III.4.4.3 Selective field confidentiality** + +This service provides for the confidentiality of selected fields within the (N)-user-data on an (N)-connection or in a single connectionless (N)-SDU as discussed in [ITU-T X.800]. + +Beyond what is in [ITU-T X.800], this service can also provide confidentiality of information within computing system storage devices (i.e., file systems) and dynamic memory. + +##### **III.4.4.4 Traffic flow confidentiality** + +This service provides for the protection of the information which might be derived from observation of traffic flows as discussed in [ITU-T X.800]. + +#### **III.4.5 Integrity** + +There are actually two parts to the concept of integrity: + +- 1) information integrity; and +- 2) data integrity. + +##### **III.4.5.1 Information integrity** + +Information integrity is not really a service but rather a way to implement services. Information integrity focuses on the correctness of information, namely, is a piece of information valid. The simplest way to express this is by example: + +An Accounts Payable clerk will not issue a payment on an invoice from a supplier unless the clerk can match the invoice against a purchase order and a set of shipping documents from the receiving department. + +The above example highlights that the legitimacy of the invoice is established from documentary evidence that the product was ordered and received. + +###### *Separation of duty* + +The concept of separation of duties, as part of information integrity, can also be seen in the above example. If: + +- employee A is only authorized to issue purchase orders, +- employee B is only authorized to receive shipments and shipping papers/receipts, and +- employee C is only authorized to issue checks to suppliers + +then any attempt by the supplier to get paid for an invalid invoice (products/services not ordered) would require the supplier to conspire with at least employees A and B. + +A successful conspiracy amongst suppliers and employees, or only amongst employees, becomes more difficult as the number of conspiracy members increases. By separating duties amongst multiple employees, a network operator reduces the probability that information is forged (not valid). + +###### *Well-formed transactions* + +The concept of well-formed transaction, as part of information integrity, can also be seen in the above example. If: + +- employee A is required to process purchase orders using a specific process, +- employee B is required to process shipping papers/receipts using a different specific process, and +- employee C is only authorized to issue checks using a third specific process + +then control over which employee is authorized to perform which operation may be controlled by which employee is allowed to invoke which of the three specific processes. Another aspect of well-formed transactions is that only production processes are allowed to be used for the aforementioned activities and that these production processes cannot be modified, circumvented, or replaced without authorization and detection. + +###### *Logging* + +The concept of logging, as part of information integrity, directly speaks to the last point made above regarding well-formed transactions. Specifically, all activities that alter information, or the processes that process information, need to generate log entries that allow for the auditing of the production processes. This auditing is critical, in conjunction with separation of duties and well-formed transaction, in providing a high level of assurance that information is correct and valid. This capability relies on the presence of non-circumventable logging mechanisms. + +##### **III.4.5.2 Data integrity** + +These services counter active threats and may take one of the forms described below. + +###### *Connection integrity with recovery* + +This service provides for the integrity of all (N)-user-data on an (N)-connection and detects any modification, insertion, deletion or replay of any data within an entire SDU sequence (with recovery attempted) as discussed in [ITU-T X.800]. + +###### *Connection integrity without recovery* + +Same as for connection integrity with recovery but with no recovery attempted as discussed in [ITU-T X.800]. + +###### *Selective field connection integrity* + +This service provides for the integrity of selected fields within the (N)-user data of an (N)-SDU as discussed in [ITU-T X.800]. + +###### *Connectionless integrity* + +This service, when provided by the (N)-layer, provides integrity assurance to the requesting (N+1)-entity as discussed in [ITU-T X.800]. + +###### *Selective field connectionless integrity* + +This service provides for the integrity of selected fields within a single connectionless SDU and takes the form of determination of whether the selected fields have been modified, as discussed in [ITU-T X.800]. + +#### **III.4.6 Non-repudiation** + +Non-repudiation is the ability to prevent an entity (a.k.a. subject, actor) from being able to deny that the entity performed some action as elaborated below. + +##### **III.4.6.1 Non-repudiation with proof of origin** + +The recipient of data is provided with proof of the origin of data. This will protect against any attempt by the sender to falsely deny sending the data or its contents, as discussed in [ITU-T X.800]. + +##### **III.4.6.2 Non-repudiation with proof of delivery** + +The sender of data is provided with proof of delivery of data. This will protect against any subsequent attempt by the recipient to falsely deny receiving the data or its contents, as discussed in [ITU-T X.800]. + +##### **III.4.6.3 Non-repudiation of actions** + +Non-repudiation of actions is provided by enforcing the sole use of well-formed transactions and logging to provide an accurate record of what occurred, when it occurred and by whom. This capability may be augmented by the use of authentication mechanisms such as digital signatures. + +### **III.5 NGN computing platform security mechanisms** + +All NGN managed elements contain FEs typically implemented as software, sometime as firmware. The primary managed element software components is its operating system. The operating system controls the execution of other software (applications) within which are implemented FEs. + +#### **III.5.1 NGN operating system security** + +All NGN deployed managed elements contain some form of operating software. This software can take the form of: + +- Type 1 A general purpose operating system, typically some form of UNIX/Linux like multi-tasking operating system, along with a full complement of file-system, graphical interface, command interpreters, network protocol stack and application server capabilities (as in DNS, HTTP, FTP, VoIP, packet/message filtering, etc.), +- Type 2 A general purpose operating system, typically some form of UNIX/Linux like multi-tasking operating system with real-time scheduling capabilities, with a minimized set of file-system, graphical interface, command interpreters, network protocol stack and application service capabilities configured to perform a limited set of functions, +- Type 3 A real-time operating system, typically some form of embedded operating system, along with file-system, graphical interface, command interpreters, network protocol stack and application server capabilities (as in DNS, HTTP, FTP, VoIP, packet/message filtering, etc.), or +- Type 4 A basic input-output set of functions for storage, memory, clock and interrupt management tightly bound with a single application service capability (as in DNS, HTTP, FTP, VoIP, packet/message filtering, etc.) + +The mapping of NGN security to computing security focuses primarily on conventional computer systems (Types 1 and 2 above), which represent a large portion of all managed elements. Other managed element types may need to implement only portions of the computing security architecture (Type 3 above). In other cases, such as simple sensor or probe devices, the managed element functions may be so limited that only specialized implementations of a small portion of the computing security architecture are appropriate (Type 4 above). + +Fundamental allocations of security services are made to managed elements (computing systems) within security domains. Managed element security makes additional security service allocations to managed element hardware and software. Not every security service allocation needs to be made identically in every managed element. + +Some security service allocations are implemented as physical and administrative security mechanisms within the security domain, such as access control to facilities and some aspects of authentication of personnel. + +##### **III.5.1.1 Hardware protects software** + +There are a variety of security mechanism choices available between the hardware and software portions of each managed element, but certain general allocations and properties can be stated for the hardware. The hardware is relied upon to function correctly, to enforce isolation of software functions, and to contribute to the protection of the integrity of the system applications and the operating system. It provides protected paths between users and trusted parts of the software. The hardware indirectly supports the isolation of information processed and stored in the managed element by protecting the integrity of the software. In some environments, specific hardware technologies (e.g., hardened or alarmed chassis) may be necessary to protect against tampering with managed element components. Availability of a managed element may be enhanced through technologies such as fault-tolerant and fault-detecting hardware features. Hardware cryptographic mechanisms are employed as needed to support various security services. Other hardware mechanisms (e.g., memory management/mapping) support specific aspects of the software architecture. + +##### **III.5.1.2 Software protects information** + +The security service allocations made to software are wide ranging. The networking subsystem supported by the managed element software is responsible for the confidentiality and integrity of information transferred amongst managed elements, for the authentication of managed elements to one another, and for user authentication and access control in distributed systems. Security services and the mechanisms that implement them must be managed. + +The managed element software is responsible for user authentication and access control, and for the integrity of information being processed and in storage. Correct operation of certain software is required to ensure managed element availability. Additionally, the software is expected to provide functions that support the security policies and requirements that are not directly expressed as security services, such as support for multiple security policies. The remainder of this clause refines the computing security architecture, which primarily is concerned with software structure. + +##### **III.5.1.3 Managed element security contexts** + +A computing security architecture must respond to the security allocations discussed earlier, and a security context is a combination of all the security domain, hardware, system software, user application software, and information supporting the activities of a user (or system function) operating in a security (sub-) domain. A security context builds on the common operating system notion of a user process space (sometimes called a context) as supported by hardware features and OS functions. The primary distinctions between an ordinary user process space and a security context are aspects of protection provided by the security domain are explicitly included, and that user applications operate in a controlled process space subject to a security domain security policy. + +A kernel manipulates the protection features of the managed element hardware (e.g., processor state registers, memory mapping registers) to maintain strict separation among security contexts by creating separate address spaces for each of them. A kernel also controls communications among security contexts to allow sharing or transfer of information and to allow services to be performed by one security context for another. All user security contexts and many system function security contexts are constrained to make requests for basic managed element services on the kernel through a standard kernel interface. The functions that make and enforce security policy decisions are intimately related to the kernel. + +The hardware (including any microcode or firmware) is considered very highly trusted in the sense that its operation is assumed to be correct. Less than highly trusted software is able to perform + +operations on basic system resources only through invocations of security-critical functions that are mediated by the kernel; inter-security context operations (e.g., inter-security domain communications) are performed by security-critical functions within the kernel. + +Trusted security-related functions (such as security management applications, portions of networking subsystem components, intrusion detection, configuration monitoring, host packet filtering and anti-virus) are expected to operate correctly to satisfy user operational needs, but need not be subjected to the rigorous scrutiny applied to the security-critical functions. Security-related software is not assumed to be free of security defects, although it is certainly prudent to obtain such software from reliable sources, test it before use, apply integrity safeguards to ensure it remains unchanged, and apply configuration management to it. Service functions (such as: + +- CORBA, DCE, Java Virtual Machines and .NET Application Framework software and +- FTP, ntp, DNS, Email, VoIP type application servers) + +should be assumed safe and obtained from reliable sources, apply integrity safeguards to ensure they remain unchanged, and apply configuration management to them. Application software (obtained from less than reliable sources) should be considered untrusted and may need to be inspected more carefully, test it before use, apply integrity safeguards to ensure it remains unchanged, and apply configuration management to it. Under these conditions, if faulty application software is introduced into a system it will, at worst, prevent certain operations, but information compromise will not result because of the combination of strict isolation of security domains enforced by the managed element, testing, and configuration management. + +The following subclauses provide additional detail on the managed element security software components, primarily for the kernel, security contexts, security-critical functions, and operating system implementations. + +##### **III.5.1.4 The kernel** + +The kernel presents abstractions of the fundamental resource management mechanisms to other, less primitive, service providers (information system functions and applications). In operating system implementations that attempt to provide a basis for secure information processing, the kernel software is carefully constructed and evaluated. To aid the evaluation process, the kernel functions are implemented as relatively small programs that are independent of one another to the maximum extent possible. A kernel is charged with the critical task of providing separation among process spaces by manipulating the protection features of the managed element hardware. + +The traditional operating system kernel functions are divided among the kernel, security policy enforcement and decision functions, and the remainder of the trusted operating system functions, called the security-critical functions. The kernel serves as the ultimate security policy enforcement function by mediating all use of the basic information system resources. The kernel notion is the foundation of the computing security architecture. + +The computing security architecture generalizes an approach that is becoming widely accepted concerning access control, namely the independence between the decision of whether or not an access to a resource is allowed and the enforcement of that decision. The separation of access control decision-making and access control enforcement functions allows the support of multiple access control policies. [ITU-T X.812] designates these functions the access control decision function (ADF) and the access control enforcement function (AEF), respectively. In fact, most existing secure operating system designs have concerned themselves only with access control policy. This managed element architecture extends the AEF concept to include the enforcement of all aspects of a security domain security policy. The resulting function is called the security policy enforcement function (SPEF). Similarly, the ADF concept is extended to a security policy decision function (SPDF). The kernel is the implementation of the SPEF. + +The kernel also is an extension (beyond access control) of the reference validation mechanism (RVM) described in the Trusted Computer System Evaluation Criteria [b-DoD 5200.28]. The basic properties of the RVM must be applied to any kernel implementation: it must be invoked for every security-critical operation, it must be small enough to be verified, and its integrity must be maintained. The kernel is reflected in Table III.2 as residing within ring 0. The concept of rings directly reflects the Biba Integrity model where integrity levels are associated with subjects and objects, such that: + +- A subject can have write access to objects on its own level or below but not above, +- A subject can have read access to objects on its own level or above but not below, + +and information flows downwards in this model. Integrity levels are not security levels as the issue is trustworthiness, not disclosure (access/confidentiality) so the higher the level, the more confidence that data is accurate/reliable or that a program will execute correctly. From a managed element software perspective, this is depicted in Table III.2: + +**Table III.2 – Mapping of ring to software objects** + +| Software processing ring | Integrity level | Object | +|--------------------------|-----------------|---------------------------------------| +| 0 | Highly trusted | Kernel | +| 1 | Trusted | Non-kernel operating system functions | +| 2 | Assumed Safe | Service functions | +| 3 | Untrusted | Application functions | + +The standard interface to the kernel is a single strongly controlled mechanism for functions residing within rings 1, 2 and 3 to make requests on kernel functionality. + +##### III.5.1.5 Security contexts + +From the perspective of the kernel, a security context is defined by a set of data and programs operating in accordance with a security domain security policy. As noted earlier, a security context also includes the physical and administrative security mechanisms of the security domain, and the hardware-based resources (e.g., registers, memory, disks) that are in use when the managed element is serving a particular user (or system function). That is, a security context encompasses all managed element resources and security mechanisms that support the activity of a user operating in a security domain. The kernel must maintain all the information needed to isolate one security context from another. When the managed element ceases performing operations in one security context and begins performing operations in another security context, no information can be allowed to pass from one security context to the other unless a specific request is made, and it is allowable under the security policies of the security domains involved. + +Examples of information that managed element security-critical functions (including the kernel) must maintain to support the operation and isolation of security contexts include: + +- A unique identification for each security context +- The identification of the security domain being supported +- Hardware register values related to control of managed element resources, including virtual memory and all devices in or attached to the managed element +- The authenticated identity of the user being served +- The users security attributes (permissions) +- Data structures needed to operate security-related functions and other untrusted system applications. + +Each security context supports a user (or a system function) operating in a particular security domain. Over a period of time, a managed element may maintain several security contexts to support one or more users operating in one or more security domains. A particular user might use (simultaneously or serially) security contexts operating in the same or different security domains. Different users may employ security contexts operating in the same or different security domains. + +Since security contexts are isolated from one another by the kernel, communications among security contexts (requests for service or information transfer) in a managed element can only take place in accordance with the security policies of the security domains supported by the security contexts. If the security policies of the supported security domains do not explicitly permit inter-security domain transfer, the SPDf will necessarily deny the request and the kernel will enforce that decision. Since a security domain contains the information of a particular user community, it would be unusual for a security domain security policy to prohibit information sharing between two security contexts supporting the same security domain. + +##### **III.5.1.6 Security critical functions** + +The security critical functions described in this clause implement the various security services allocated to the managed element and several additional supporting services. + +###### *Security policy decision function (SPDf)* + +The separation of security mechanisms from security policy enforcement and decisions is crucial to the flexibility of the computing security architecture. The SPDf is responsible for making all security policy decisions. The primary role of the SPDf is to isolate the rest of the managed element software from knowledge of security policies. The importance of this approach is threefold: + +- 1) First, the support of multiple security domains with different policies is accomplished easily because the security policies are represented in only one place and are interpreted by only one function. In many current secure system designs, it is difficult to point to the actual software code that implements the single security policy of those systems because it is embedded and scattered throughout the code that performs multiple functions. +- 2) Second, by keeping security policy representations in one place, it is relatively easy to install, modify, or even replace the security policy for a security domain. It is not necessary to rewrite trusted software that implements the security policy. Rather, the rules that the SPDf interprets for a security domain are updated or replaced. +- 3) Third, changing the implementation of the SPDf would be transparent to the operation of the remainder of the managed element software. Any correct implementation of the SPDf is acceptable, but it may be useful to standardize the representation of security attributes and security policy rules. + +The SPDf approach allows security critical functions to be implemented independently of particular security policies. + +###### *Authentication function* + +The authentication function invokes one or more mechanisms used by a managed element to identify and authenticate users (and to authenticate a managed element to users), and for managed elements to authenticate one another in a distributed environment. A common interface to the authentication function is used that is independent of any of the security domain security policy or the authentication mechanisms employed. That is, the authentication function is the service interface to the mechanisms used to identify and authenticate users and managed elements. The exact mechanisms selected will depend on the security domain policies in effect. A managed element supporting multiple security domain policies may need to implement more than one authentication mechanism. + +###### *Audit function* + +The audit function accepts audit messages from functions in the managed element in accord with the security domain and management security domain security policies. Audit records may become part of the security management information that is part of an information management domain (for one or more security domains or managed element domains). Audit records may be directed to multiple repositories. In some cases, the audit information may best be used by an individual user (for example, time and method of most recent managed element or security domain use). The audit function guarantees that audit messages cannot be lost and that the ordering of messages is preserved. As part of a distributed audit system, audit functions can forward the audit data they collect to a base-level, regional, or central audit centre to alleviate local audit data storage requirements and to coordinate audit information from different managed elements or security domains. Audit data must be protected from unauthorized access or modification. + +###### *Process scheduling function* + +In operating systems that share the managed element processor among multiple processes, the process scheduling function determines which of the processes next uses the processor (or processors in a multiprocessor managed element) and for how long. The process scheduling function must be included among the security critical functions so that no process can deny the processor to other processes either purposefully or inadvertently. + +###### *Device management functions and device controllers* + +The remainder of the security critical functions are each responsible for a particular class of managed element resources. These resources include memory, storage devices, display systems, inter-process communications, cryptographic services, and any other input/output devices controlled by the managed element. + +###### **Security-related functions** + +Some software functions within the managed element are required to manage information or to provide an interface to the security critical functions, but are not critical to system security. Of particular interest here are residual operating system functions, security management functions, and networking subsystem functions. + +###### *Operating system structure* + +Most of the security critical functions are part of traditional operating system structures. Many other operating system components are not included in the security critical functions, such as the user interface, utility functions, and high-level abstractions of information. These functions are present in varying forms in all traditional operating systems. The user interface, the particular utility functions, and the information abstractions provided characterize a particular operating system. That is, they distinguish one operating system from another even though they provide essentially the same services to a user. Because the security critical functions provide commonly used, low-level services, many different operating systems can be implemented using them. + +###### *Security management function* + +The primary role of the security management function is to control information needed by security-critical and security-related functions within the computing security architecture. Security management is a particular instance of general management functions. Examples of the information manipulated by the security management function include security domain security policy rules used by the SPD, configuration parameters for security mechanisms (e.g., cryptographic algorithms), configuration parameters for cryptographic mechanisms and managed element devices, and audit information. Some information is managed for specific security domains and some is managed for managed elements or security domains. + +###### *Networking subsystem function* + +The networking subsystem is defined in accordance with [b-ITU-T X.200] and [ITU-T X.800]. Communications applications and communications protocols used to communicate with other managed elements are implemented as trusted operating system functions within the computing security architecture. These applications make requests for security services (which process information and generate protocol information) that provide required protection. For information to be transferred between managed elements and within a security domain, a distributed security context is established through the use of security management and transfer system applications, and security critical functions. + +##### **III.5.1.7 Security management within NGN managed elements** + +Each NGN deployed managed element includes some set of security mechanisms and therefore must also include a local mechanism for managing these local security mechanisms. Local security management functionality is typically embodied within the general management/administrative functions within the managed element, referred to herein as a security management application process (SMAP). + +One or more managed elements within the same security domain may support a particular security service with more than one security mechanism, but it may not be known in advance of attempted communications which of these security mechanisms may be implemented in a specific managed element. In such cases, the specific security mechanisms to be employed must be negotiated between the SMAPs in the managed elements at the time a security association is established between them. + +The invocation of security services and security mechanisms within a managed element involves several functions. Since all security services are security-critical, they should be accessible only within the kernel, and applications should invoke them only through a standard kernel interface. Since most applications will rely upon the operating system for use of this standard kernel interface, the use of the interface should be transparent to those applications. If a request for a security service does not specify a security mechanism, the SMAPs should make a choice among the available security mechanisms based on the security domain policy and invokes it through an appropriate operating system call. Otherwise, the SMAPs invokes the specified security mechanism. + +Consistent with [ITU-T X.800], managed element security mechanism management is concerned with the management of particular security mechanisms. The following list of security mechanism management functions is typical but not exhaustive: + +- key management (for use with encryption, digital signature, data integrity, authentication and notarization mechanisms); +- encryption management; +- digital signature management; +- access control management; +- data integrity management; +- authentication management; +- traffic padding management; +- routing control management; +- notarization management; +- availability management. + +###### **III.5.1.7.1 Key management** + +[ITU-T X.800] describes key management as follows: + +"Key management may involve: + +- a) generating suitable keys at intervals commensurate with the level of security required; +- b) determining, in accordance with access control requirements, of which entities should receive a copy of each key; and +- c) making available or distributing the keys in a secure manner to entity instances in real open systems." + +Exchange of session keys will typically be negotiated within the security association establishment and renegotiation mechanisms of security protocols such as within IPSec IKE, TLS, DTLS and SSH. Key management functions for distribution of key distribution keys (master keys) and keys used in peer-entity authentication may be performed as part of a key management service such as a PKI. + +NGN managed element key management functionality should include the ability to securely store multiple sets of master keys (especially multiple asymmetric encryption private keys and associated X.509v3 certificate [ITU-T X.509] chains) as well as multiple shared secret keys used with symmetric encryption and 'keyed' hash based data origin authentication mechanisms. Managed element SMIBs are expected to support the ability to store security policy rules governing keys and their usage within the NGN security domain. + +###### **III.5.1.7.2 Encipherment (encryption) management** + +[ITU-T X.800] describes encryption management as follows: + +"Encipherment management may involve: + +- a) interaction with key management; +- b) establishment of cryptographic parameters; and +- c) cryptographic synchronization." + +Selection of cryptographic algorithms, parameters, synchronization and keys will typically be negotiated within the security association establishment and renegotiation mechanisms of security protocols such as within IPSec-ISAKMP, TLS, DTLS and SSH. These security protocols will require interaction with the managed element's key management functionality for access to master keys when a security protocol is performing peer entity authentication. The managed element SMIB will be expected to support the ability to store security policy rules governing encryption usage within the NGN security domain. + +###### **III.5.1.7.3 Digital signature management** + +[ITU-T X.800] describes digital signature management as follows: + +"Digital signature management may involve: + +- a) interaction with key management; +- b) establishment of cryptographic parameters and algorithms; and +- c) use of protocol between communicating entities and possibly a third party." + +NOTE – Generally, there exist strong similarities between digital signature management and encryption management. + +When digital signatures support a non-repudiation service that relies upon a trusted third party (public key infrastructure), additional security management responsibilities may be required within the managed element with respect to long-term archiving of keys and algorithm identifiers so that transactions can be verified well after they occur. This additional capability will typically reside + +within the application functionality of a managed element. The managed element SMIB will be expected to support the ability to store security policy rules governing long-term archiving of keys and algorithm identifiers within the NGN security domain along with the actual storage of keys and algorithm identifiers used in transactions. + +###### **III.5.1.7.4 Access control management** + +[ITU-T X.800] describes access control management as follows: + +"Access control management may involve distribution of security attributes (including passwords) or updates to access control lists or capabilities lists. It may also involve the use of a protocol between communication entities and other entities providing access control services." + +The distribution of security attributes includes their initial installation in a SMIB. Since not all the information in the NGN security domain SMIB is necessarily locally present in every managed element that is part of the security domain, it may be necessary to distribute access control attributes between managed elements. Given the complex nature of the application functionality now residing on a network operator's managed elements, it is recommended that the managed element implement role-based access control mechanisms (RBAC) for both general managed element and application specific access control. These managed elements should support secure reliable interaction with an SMS within the security domain. The managed element SMIB will be expected to support the ability to store security policy rules governing access controls within the security domain. + +##### **III.5.1.7.5 Data integrity management** + +[ITU-T X.800] describes data integrity management as follows: + +"Data integrity management may involve: + +- a) interaction with key management; +- b) establishment of cryptographic parameters and algorithms; and +- c) use of protocol between communicating entities." + +When using cryptographic techniques to support the data integrity service, similarities exist between data integrity management and encryption management. For information residing within a managed element, data integrity can be attained by use of strong access control mechanisms on memory and storage subsystems. When a strong communications data integrity service is required, reversible (symmetric) or non-reversible (hashing) cryptographic mechanisms are necessary. Selection of cryptographic data integrity mechanisms, parameters, and keys will typically be negotiated within the security association establishment and renegotiation mechanisms of security protocols such as within IPSec-ISAKMP, TLS, DTLS and SSH. The managed element SMIB will be expected to support the ability to store security policy rules governing both managed element internal and communications data integrity within the security domain. + +##### **III.5.1.7.6 Authentication management** + +[ITU-T X.800] describes authentication management as follows: + +"Authentication management may involve distribution of descriptive information, passwords or keys (using key management) to entities required to perform authentication. It may also involve use of a protocol between communicating entities and other entities providing authentication services." + +Authentication mechanisms rely upon particular authentication information (credentials) to validate a given identity. The authentication information against which user-supplied authentication information is verified is stored in the SMIB (where managed element data structures such as password files and registry heaps constitute part of the SMIB) and is subject to similar considerations as access control attributes. The managed element should provide support for + +peer-entity, data-origin and user login authentication. Selection of authentication mechanisms will typically be negotiated within the security association establishment and renegotiation mechanisms of security protocols such as within IPSec-IKE, TLS, DTLS and SSH. Managed element support for some form of security domain "single-sign on" is highly desirable to reduce managed element user login account authentication workload. These managed elements should support secure reliable interaction with an SMS within the security domain. The managed element SMIB will be expected to support the ability to store security policy rules and information governing both local and remote authentication to managed elements within the security domain. + +##### **III.5.1.7.7 Traffic padding management** + +Traffic padding in physical layer communications devices is often managed as a configuration parameter. In the NGN context, traffic padding in the physical layer will occur infrequently. Traffic padding in application layer protocols could be invoked as the result of a user request or as the result of a security domain security policy requirement applied to all or some class of communications. The critical management aspect of satisfying such a request is to assure that the padding is applied at the correct stage of processing with respect to other security services, such as data integrity or data confidentiality. + +##### **III.5.1.7.8 Routing control management** + +[ITU-T X.800] defines routing control management as follows: + +"Routing control management may involve the definition of the links or sub-networks which are considered to be either secured or trusted with respect to particular criteria." + +In an NGN, routing control should be effected through the use of strong peer-entity and data-origin authentication of data link and internetworking signalling and control protocols used to disseminate switching and routing information. This capability will require interaction between routing control, encryption and authentication management functions within the managed element. + +##### **III.5.1.7.9 Notarization management** + +In an NGN, notarization management is highly unlikely to be provided. + +##### **III.5.1.7.10 Availability management** + +Availability management is not described in [ITU-T X.800]. Availability management applies to: + +- interactions within an NGN for notifications of outages and, if applicable, alternate service information, and +- for those NGN managed elements that interconnect with other security domains, the ability to contend with likely denial-of-service (DoS and distributed DoS) attack events. + +The managed element SMIB will be expected to support the ability to store security policy rules and information governing the recognition of, logging information about, generation and distribution of alarms relative DoS/DDoS attacks targeting managed elements within the security domain. + +##### **III.5.1.8 Managed element security information storage management** + +Each NGN deployed managed element must contain the necessary local information to enable it to enforce an appropriate security policy. A managed element local security management information base (SMIB) is a necessary capability for the storage of security relevant configuration parameters, policy rules, cryptographic keys and other security associated information. The SMIB may be implemented using any number of approaches and not limited to concepts such as SNMP MIBs, nor be implemented as a monolithic or homogeneous structures within the managed element. Managed element SMIBs contain information for management and use of security functions and resources within the managed element the use of which is required by the security domain security policy, including hardware resources, security critical functions (particularly security services and + +mechanisms), and supporting applications (e.g., key management). The following example classes of objects should be included in the managed element SMIB: + +- End system security policy rules +- Security services management information +- Security mechanisms management information +- Supporting services and mechanisms management information (e.g., alarm reporting, information system auditing, cryptographic key distribution, security contexts, security critical functions, security related applications operating for the managed element). + +#### **III.5.2 NGN communications security mechanisms** + +[ITU-T X.800] defines the general security-related architectural elements that can be applied to communications systems. [ITU-T X.800] provides a general description of security services and the related mechanisms that may be used to provide the services based on the networking architecture concepts of [b-ITU-T X.200]. However, [ITU-T X.800] is concerned only with those visible aspects of a communications path that permit networked managed elements to achieve secure transfer of information between them. It does not attempt to provide any kind of implementation specification, and it does not provide the means to assess conformance of any implementation to this or any other security standard. Nor does it indicate, in any detail, the additional security mechanisms needed within the networked managed elements to ensure reliable secure computer operation. + +##### **III.5.2.1 Protocol layers and functional planes** + +[b-ITU-T X.200] states that there is a functional layering of protocols into what is commonly referred to as the ISO/OSI seven-layer protocol model comprising: + +- 1 Physical layer, +- 2 Data link layer, +- 3 Internetworking layer, +- 4 Transport layer, +- 5 Session layer, +- 6 Presentation layer; and +- 7 Application layer. + +It has been frequently argued that, for the most part, the Internet protocol model has displaced the ISO/OSI protocol model in virtually all modern networking infrastructures. This Internet model is essentially a five-layer protocol model comprising: + +- 1 Physical layer, +- 2 Data link layer, +- 3 Internetworking layer, +- 4 Transport layer, +- 5 Application layer, + +and for the purpose of a network operator security architecture, the 5-layer model is used. Since the publication of [b-ITU-T X.200], the concept that each protocol layer actually provides communications functionality to three forms of activities, namely: + +- User plane (a.k.a. Media), +- Signalling and control plane, and +- Management plane + +has become commonly accepted. + +##### III.5.2.2 Management communications + +Management activities certainly pertain to controlling the capabilities and behaviour of functions within each protocol layer. However, from a communications perspective, there is no management plane in protocol layers 1 through 4 as management activities are, in fact, simply a form of application activities where the application activity focuses specifically on (as defined in [ITU-T X.700]): + +- Fault management, +- Configuration management, +- Accounting management, +- Performance management, +- Security management, + +also referred to as FCAPS. Consequently, it is only appropriate to refer to a management plane within the application protocol layer. + +##### III.5.2.3 Physical layer + +Clause 7.7 of [b-ITU-T X.200] states the physical layer: + +"provides the mechanical, electrical, functional and procedural means to activate, maintain, and de-activate physical-connections for bit transmission between data-link-entities. A physical-connection may involve intermediate open systems, each relaying bit transmission within the Physical Layer. Physical Layer entities are interconnected by means of a physical medium." + +and, as such, does not meaningfully decompose into the aforementioned planes of functionality, thus it is reasonable to reference physical layer technologies relative to specific data link layer technologies, where relevant. + +Another complication is the concept of user-network interfaces (UNIs), internal network-network interfaces (INNNIs) and network-network interfaces (NNIs) sometimes referred to as external network-network interfaces (ENNNIs). This Recommendation will use the more common ITU-T terminology of NNI rather than ENNI. + +##### III.5.2.4 Mapping security services to the communications protocol layers + +Tables III.4 to III.11 depict which security services apply within the hierarchy of network interfaces, protocol layers and protocol functional planes. + +In the following tables: + +- Data link layer is abbreviated as DLL +- Signalling and control is abbreviated as S&C +- Internetworking protocol layer (IP versions 4 & 6) are simply referred to as IP +- "Apply" represents that a service is expected to be present +- "Should" represents that a service should be present +- "May" represents that a service may be present + +**Table III.3 – DLL user plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | MAY | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | MAY | +| | Connectionless Confidentiality | MAY | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | MAY | +| INNI | Peer-Entity Authentication | MAY | +| | Data-Origin Authentication | MAY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | MAY | +| | Connectionless Confidentiality | MAY | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | MAY | +| NNI | Peer-Entity Authentication | MAY | +| | Data-Origin Authentication | MAY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | MAY | +| | Connectionless Confidentiality | MAY | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | MAY | + +**Table III.4 – DLL S&C plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | MAY | +| | Connectionless Confidentiality | MAY | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | MAY | +| INNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | MAY | +| | Connectionless Confidentiality | MAY | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | MAY | +| NNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | MAY | +| | Connectionless Confidentiality | MAY | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | MAY | + +**Table III.5 – IP user plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| INNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| NNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | + +**Table III.6 – IP S&C plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| INNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| NNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | + +**Table III.7 – Transport layer user plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| INNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| NNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | + +**Table III.8 – Transport layer S&C plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| INNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| NNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | MAY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | MAY | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | MAY | +| | Connection Integrity without Recovery | MAY | +| | Selective Field Connection Integrity | MAY | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | MAY | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | + +**Table III.9 – Application layer user plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | SHOULD | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| INNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | SHOULD | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| NNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | SHOULD | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | + +**Table III.10 – Application layer S&C plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | SHOULD | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| INNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | SHOULD | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | +| NNI | Peer-Entity Authentication | SHOULD | +| | Data-Origin Authentication | SHOULD | +| | User Authentication | SHOULD | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | SHOULD | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | SHOULD | +| | Non-repudiation with Proof of Delivery | SHOULD | + +**Table III.11 – Application layer management plane** + +| I/F | Security service | Provided | +|------|------------------------------------------|----------| +| UNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | APPLY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | APPLY | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | APPLY | +| | Non-repudiation with Proof of Delivery | APPLY | +| INNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | APPLY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | APPLY | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | APPLY | +| | Non-repudiation with Proof of Delivery | APPLY | +| NNI | Peer-Entity Authentication | APPLY | +| | Data-Origin Authentication | APPLY | +| | User Authentication | APPLY | +| | Access Controls | APPLY | +| | Connection Confidentiality | SHOULD | +| | Connectionless Confidentiality | SHOULD | +| | Selective Field Confidentiality | SHOULD | +| | Traffic Flow Confidentiality | MAY | +| | Logging | APPLY | +| | Connection Integrity with Recovery | SHOULD | +| | Connection Integrity without Recovery | APPLY | +| | Selective Field Connection Integrity | SHOULD | +| | Connectionless Integrity | APPLY | +| | Selective Field Connectionless Integrity | SHOULD | +| | Non-repudiation with Proof of Origin | APPLY | +| | Non-repudiation with Proof of Delivery | APPLY | + +# Bibliography + +- [b-ITU-T G.983.1] Recommendation ITU-T G.983.1 (2005), *Broadband optical access systems based on Passive Optical Networks (PON)*. +- [b-ITU-T G.984.1] Recommendation ITU-T G.984.1 (2008), *Gigabit-capable passive optical networks (G-PON): General characteristics*. +- [b-ITU-T M.3050.0] Recommendation ITU-T M.3050.0 (2004), *Enhanced Telecom Operations Map (eTOM) – Introduction*. +- [b-ITU-T M.3400] Recommendation ITU-T M.3400 (2000), *TMN management functions*. +- [b-ITU-T X.200] Recommendation ITU-T X.200 (1994) | ISO/IEC 7498-1:1994, *Information technology – Open Systems Interconnection – Basic Reference Model: The basic model*. +- [b-ITU-T X.1051] Recommendation ITU-T X.1051 (2008) | ISO/IEC 27011:2008, *Information technology – Security techniques – Information security management guidelines for telecommunications organizations based on ISO/IEC 27002*. +- [b-ITU-T Y.2201] Recommendation ITU-T Y.2201 (2007), *NGN release 1 requirements*. +- [b-ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*. +- [b-ATIS 0100014] ATIS 0100014 (2007), *Information and Communications Security for NGN Converged Services IP Networks and Infrastructure*. +<[http://store.ihs.com/specsstore/controller;jsessionid=UFdMskSPeTYRCIqq5a6LpA\\*\\*.app12?event=DOCUMENT\\_DETAILS&docId=BDHYKCAAAAAAAAAA](http://store.ihs.com/specsstore/controller;jsessionid=UFdMskSPeTYRCIqq5a6LpA**.app12?event=DOCUMENT_DETAILS&docId=BDHYKCAAAAAAAAAA)> +- [b-ATIS 0300074] ATIS 0300074 (2006), *Guidelines and Requirements for Security Management Systems*. +<[http://global.ihs.com/family\\_search\\_res.cfm?currency\\_code=USD&customer\\_id=2125482C4E0A&shopping\\_cart\\_id=2624482B2F4B30204D0A&country\\_code=US&lang\\_code=ENGL&item\\_s\\_key=00481633&document\\_name=ATIS%200300074&stage=H](http://global.ihs.com/family_search_res.cfm?currency_code=USD&customer_id=2125482C4E0A&shopping_cart_id=2624482B2F4B30204D0A&country_code=US&lang_code=ENGL&item_s_key=00481633&document_name=ATIS%200300074&stage=H)> +- [b-3GPP TS 32.371] 3GPP TS 32.371 (2008), *Telecommunication management: Security Management concept and requirements*. +<[http://webapp.etsi.org/action/PU/20080729/ts\\_132371v070301p.pdf](http://webapp.etsi.org/action/PU/20080729/ts_132371v070301p.pdf)> +- [b-ANSI T1.276] ANSI T1.276-20031, *Operations, Administration, Maintenance, and Provisioning Security Requirements for the Public Telecommunications Network: A Baseline of Security Requirements for the Management Plane*. +<> +- [b-DoD 5200.28] DoD Standard 5200.28 (1985), *Department of Defense Trusted Computer System Evaluation Criteria*. +<> + +--- + +1 T1 standards are maintained since November 2003 by ATIS. + +- [b-ETSI TS 188 003] ETSI TS 188 003 v1.1.2 (2006), *Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); OSS requirements; OSS definition of requirements and priorities for further network management specifications for NGN.* <[http://webapp.etsi.org/workprogram/Report\\_WorkItem.asp?WKI\\_ID=24397](http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=24397)> +- [b-IETF RFC 791] IETF RFC 791 (1981), *Internet Protocol DARPA Internet Program Protocol Specification.* <> +- [b-IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol DARPA Internet Program Protocol Specification.* <> +- [b-IETF RFC 854] IETF RFC 854 (1983), *TELNET Protocol Specification.* <> +- [b-IETF RFC 913] IETF RFC 913 (1984), *Simple File Transfer Protocol.* <> +- [b-IETF RFC 959] IETF RFC 959 (1985), *File Transfer Protocol (FTP).* <> +- [b-IETF RFC 1305] IETF RFC 1305 (1992), *Network Time Protocol (Version 3), Specification, Implementation and Analysis.* <> +- [b-IETF RFC 1350] IETF RFC 1350 (1992), *The TFTP Protocol (Revision 2).* <> +- [b-IETF RFC 2104] IETF RFC 2104 (1997), *HMAC: Keyed-Hashing for Message Authentication.* <> +- [b-IETF RFC 2131] IETF RFC 2131 (1997), *Dynamic Host Configuration Protocol.* <> +- [b-IETF RFC 2181] IETF RFC 2181 (1997), *Clarifications to the DNS Specification.* <> +- [b-IETF RFC 2403] IETF RFC 2403 (1998), *The Use of HMAC-MD5-96 within ESP and AH.* <> +- [b-IETF RFC 2404] IETF RFC 2404 (1998), *The Use of HMAC-SHA-1-96 within ESP and AH.* <> +- [b-IETF RFC 2405] IETF RFC 2405 (1998), *The ESP DES-CBC Cipher Algorithm with Explicit IV.* <> +- [b-IETF RFC 2410] IETF RFC 2410 (1998), *The NULL Encryption Algorithm and Its Use With IPsec.* <> +- [b-IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1.* <> +- [b-IETF RFC 2818] IETF RFC 2818 (2000), *HTTP over TLS.* <> +- [b-IETF RFC 2865] IETF RFC 2865 (2000), *Remote Authentication Dial In User Service (RADIUS).* <> +- [b-IETF RFC 3268] IETF RFC 3268 (2002), *Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS).* <> + +- [b-IETF RFC 3414] IETF RFC 3414 (2002), *User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)*. +[](http://www.ietf.org/rfc/rfc3414.txt?number=3414) +- [b-IETF RFC 3588] IETF RFC 3588 (2003), *Diameter Base Protocol*. +[](http://www.ietf.org/rfc/rfc3588.txt?number=3588) +- [b-IETF RFC 4120] IETF RFC 4120 (2005), *The Kerberos Network Authentication Service (V5)*. [](http://www.ietf.org/rfc/rfc4120.txt?number=4120) +- [b-IETF RFC 4251] IETF RFC 4251 (2006), *The Secure Shell (SSH) Protocol Architecture*. +[](http://www.ietf.org/rfc/rfc4251.txt?number=4251) +- [b-IETF RFC 4301] IETF RFC 4301 (2005), *Security Architecture for the Internet Protocol*. +[](http://www.ietf.org/rfc/rfc4301.txt?number=4301) +- [b-IETF RFC 4302] IETF RFC 4302 (2005), *IP Authentication Header*. +[](http://www.ietf.org/rfc/rfc4302.txt?number=4302) +- [b-IETF RFC 4303] IETF RFC 4303 (2005), *IP Encapsulating Security Payload (ESP)*. +[](http://www.ietf.org/rfc/rfc4303.txt?number=4303) +- [b-IETF RFC 4306] IETF RFC 4306 (2005), *Internet Key Exchange (IKEv2) Protocol*. +[](http://www.ietf.org/rfc/rfc4306.txt?number=4306) +- [b-IETF RFC 4307] IETF RFC 4307 (2005), *Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)*. +[](http://www.ietf.org/rfc/rfc4307.txt?number=4307) +- [b-IETF RFC 4346] IETF RFC 4346 (2006), *The Transport Layer Security (TLS) Protocol Version 1.1*. [](http://www.ietf.org/rfc/rfc4346.txt?number=4346) +- [b-IETF RFC 4347] IETF RFC 4347 (2006), *Datagram Transport Layer Security*. +[](http://www.ietf.org/rfc/rfc4347.txt?number=4347) +- [b-IETF RFC 4510] IETF RFC 4510 (2006), *Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map*. +[](http://www.ietf.org/rfc/rfc4510.txt?number=4510) +- [b-IETF RFC 4511] IETF RFC 4511 (2006), *Lightweight Directory Access Protocol (LDAP): The Protocol*. [](http://www.ietf.org/rfc/rfc4511.txt?number=4511) +- [b-IETF RFC 4512] IETF RFC 4512 (2006), *Lightweight Directory Access Protocol (LDAP): Directory Information Models*. +[](http://www.ietf.org/rfc/rfc4512.txt?number=4512) +- [b-IETF RFC 4513] IETF RFC 4513 (2006), *Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms*. +[](http://www.ietf.org/rfc/rfc4513.txt?number=4513) +- [b-IETF RFC 4835] IETF RFC 4835 (2007), *Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)*. [](http://www.ietf.org/rfc/rfc4835.txt?number=4835) +- [b-IETF RFC 4960] IETF RFC 4960 (2007), *Stream Control Transmission Protocol*. +[](http://www.ietf.org/rfc/rfc4960.txt?number=4960) +- [b-RSA] RSA Laboratories PKCS 12 v1.0 (1999), *Personal Information Exchange Syntax*. [](http://www.rsa.com/rsalabs/node.asp?id=2138) + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d +size 7219 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66f7b8680e446762fbc9847e3ffb675039c7ba89 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98a5c6ff0384495a000924e3e09f2b2fe080d953caec0b0d699c6a31d4f96753 +size 37801 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a6c2f14542ea9a7550be1c2f4f3489be09133cf --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b72c9561849638c9624ebce93e87ecb9abf93662a7512bf01ee3871aac115e +size 28796 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43fed0d4da7cd5c0c27f4463d9a7b0fe1b87bb46 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781ee55acd12898be71eca7b80d71b38f5f2fad2716adddda01ff5f655cc123f +size 35822 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51035fd002266289b3bd919bb84b51251dec1f86 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2aefc98ac237dd56205311e7e56b964530cae495f74d02203dcea42c038ba5c0 +size 51482 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ab1477877244d20550442354025892ff4490cc1 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7e631b62b1f9814440da112591c05f1335090c2aa34b11d819fab0c889202a3 +size 26791 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40cf1c2cf5f6de5e8a9e48bcbf1fa2566a0f57d6 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dfba43621746a82ad65176e95f0a95727b29eddf451bcd0a326482b8349b9e1 +size 36777 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05b0641235a5555a992de7d6481b077366316e1f --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b88ef115bbc89d156bd379206aad2790d92001cb5698d9db74b4f5b92262981a +size 32072 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3411-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..940bc63adda22599723c8f973c280633beac7466 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869036056adca7c27b32fe36601c0bc867a55f1539ae4c3e851d239cb336a379 +size 41221 diff --git a/marked/M/T-REC-M.3411-202503-I_PDF-E/raw.md b/marked/M/T-REC-M.3411-202503-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ea408ca0cb2828aef0c19fead6d2e78251ead421 --- /dev/null +++ b/marked/M/T-REC-M.3411-202503-I_PDF-E/raw.md @@ -0,0 +1,501 @@ + + +# Recommendation**ITU-T M.3411 (03/2025)** + +SERIES M: Telecommunication management, including +TMN and network maintenance + +Telecommunications management network + +--- + +### **User identity and access management requirements for telecommunication management networks** + +![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T M-SERIES RECOMMENDATIONS + +## **Telecommunication management, including TMN and network maintenance** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 | +| International transmission systems | M.300-M.559 | +| International telephone circuits | M.560-M.759 | +| Common channel signalling systems | M.760-M.799 | +| International telegraph systems and phototelegraph transmission | M.800-M.899 | +| International leased group and supergroup links | M.900-M.999 | +| International leased circuits | M.1000-M.1099 | +| Mobile telecommunication systems and services | M.1100-M.1199 | +| International public telephone network | M.1200-M.1299 | +| International data transmission systems | M.1300-M.1399 | +| Designations and information exchange | M.1400-M.1999 | +| International transport network | M.2000-M.2999 | +| Telecommunications management network | M.3000-M.3599 | +| Integrated services digital networks | M.3600-M.3999 | +| Common channel signalling systems | M.4000-M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3411 + +## User identity and access management requirements for telecommunication management networks + +## Summary + +Recommendation ITU-T M.3411 specifies the user identity and access management requirements for telecommunication management networks (TMNs). It mainly consists of the architecture and the functional requirements for identity and access management (IAM) in TMN, which include identity management functions and access management functions. + +This Recommendation applies to the guidance of the design and development of IAM solutions for TMN. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T M.3411 | 2025-03-29 | 2 | 11.1002/1000/16286 | + +## Keywords + +Requirements, telecommunication management network, user identity and access management. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at . + +© ITU 2025 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Overview and background..... | 2 | +| 6.1 Overview of IAM for TMN..... | 2 | +| 6.2 Architecture of TMN with the IAM capability ..... | 3 | +| 6.3 General objectives of IAM for TMN..... | 5 | +| 7 Functional requirements for OS(IAM) ..... | 5 | +| 7.1 Functional framework of OS(IAM)..... | 5 | +| 7.2 Requirements of identity management function set ..... | 6 | +| 7.3 Requirements of access management function set..... | 7 | +| Appendix I – Use case examples of OS(IAM) in TMN ..... | 9 | +| I.1 Establish a user account..... | 9 | +| I.2 Authenticate user access request ..... | 9 | +| I.3 Verify user privilege..... | 10 | +| I.4 Terminate user connection ..... | 11 | +| Bibliography..... | 12 | + + + +# Recommendation ITU-T M.3411 + +## User identity and access management requirements for telecommunication management networks + +# 1 Scope + +This Recommendation specifies the requirements of user identity and access management (IAM) for telecommunications management network (TMN), which includes the following contents: + +- Architecture of TMN with IAM capability; +- General objectives of IAM for TMN; +- Functional framework of IAM for TMN; +- Requirements of identity management functions and access management functions. + +This Recommendation is for the guidance of the design and development of IAM solutions for TMN. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*. +- [ITU-T M.3016.0] Recommendation ITU-T M.3016.0 (2005), *Security for the management plane: Overview*. +- [ITU-T M.3016.1] Recommendation ITU-T M.3016.1 (2005), *Security for the management plane: Security requirements*. +- [ITU-T M.3016.2] Recommendation ITU-T M.3016.2 (2005), *Security for the management plane: Security services*. +- [ITU-T M.3410] Recommendation ITU-T M.3410 (2008), *Guidelines and requirements for security management systems to support telecommunications management*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 authentication** [b-ITU-T X.1257]: Formalized verification process that, if successful, results in an authenticated identity for an entity. + +NOTE – User authentication concerns verifying the identity of clients involved in the network management. It ensures the identity of legitimate users and prevents masquerading attacks by illegitimate users [ITU-T M.3016.2]. + +**3.1.2 access control** [b-ITU-T X.1252]: A procedure by which an administrator can restrict access to resources, facilities, services, or information based on pre-established rules and specific rights or authority associated with the requesting party. + +NOTE – A TMN must ensure that actors are prevented from accessing unauthorized information or resources. Access control mechanisms ensure that resources are accessed only by authorized subjects [ITU-T M.3016.0]. + +**3.1.3 access policy** [b-ITU-T X.1257]: An access control constraining mechanism (i.e., what business permissions a user can execute during run-time). + +**3.1.4 credential** [b-ITU-T X.1252]: Set of data presented as evidence of a claimed identity and/or entitlements. + +**3.1.5 entity** [b-ITU-T X.1252]: Something that has a separate and distinct existence and that can be identified in a context. + +**3.1.6 identity** [b-ITU-T X.1252]: The representation of an entity in the form of one or more information elements which allow the entities to be sufficiently distinguished within context. + +**3.1.7 role** [ITU-T M.3410]: The description of an individual's sphere of responsibility. + +NOTE – It can be used for enforcing access control according to the principle of least privilege. + +**3.1.8 user** [ITU-T M.3010]: A person or process applying management services for the purpose of fulfilling management operations. + +NOTE – This Recommendation usually refers to the staff that engaged in network operation, management and maintenance activities within the enterprise (such as telecommunications operators). + +## 3.2 Terms defined in this Recommendation + +None. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|-----------------------------------------------------| +| IAM | Identity and Access Management | +| NE | Network Element | +| NMS | Network Management System | +| OS | Operation System | +| OS(IAM) | Operation System for Identity and Access Management | +| TMN | Telecommunication Management Network | + +# 5 Conventions + +In this Recommendation: + +- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. +- The keywords "is recommended" indicate a requirement which is recommended but is not absolutely required. Thus, this requirement need not be present to claim conformance. + +# 6 Overview and background + +## 6.1 Overview of IAM for TMN + +The user identity represents a set of attributes that uniquely identify a user, including the user account and profile, credentials, roles, and privileges that indicate whether the user has the legal status to access a target and perform a certain management operation. In telecommunication management network (TMN), when a user accesses a management system, the user will act in a specific role. A + +one-to-one relationship exists between a user and a role when using a specific management function, but a user who accesses multiple management functions can have multiple roles in [ITU-T M.3016.0]. + +The relationships between these identity attributes are: + +- A user can have multiple credentials to enhance security or to support various security levels. +- A user can have multiple roles, but when accessing a TMN service, the user has a one-to-one relationship with a specific role. +- A role has multiple privileges. TMN uses roles to organize privileges, allowing users to have the set of privileges specified by the role by assigning the role to them. + +The attributes of identity and their relationships in identity and access management for TMN are shown in Figure 1. + +![Figure 1: Identity attributes and their relationship in IAM for TMN. The diagram shows four entities: User, Role, Privilege, and Credential. User is connected to Role (n to m), Role is connected to Privilege (1 to n), and User is connected to Credential (1 to n). The entities are grouped under the title 'Identity and the attributes'.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +``` +graph LR; User((User)) ---|n:m| Role((Role)); Role ---|1:n| Privilege((Privilege)); User ---|1:n| Credential((Credential)); +``` + +M.3411(25) + +Figure 1: Identity attributes and their relationship in IAM for TMN. The diagram shows four entities: User, Role, Privilege, and Credential. User is connected to Role (n to m), Role is connected to Privilege (1 to n), and User is connected to Credential (1 to n). The entities are grouped under the title 'Identity and the attributes'. + +**Figure 1 – Identity attributes and their relationship in IAM for TMN** + +The functions of identity and access management (IAM) for TMN can be categorized into two function sets of functions, which are identity management and access management. + +Identity management function set mainly manages the various identity attributes that uniquely identify a user, including user (account and profile), credential, role and privilege, and maintains the relationships between these attributes. + +Access management function set is primarily responsible for authentication and access control of access requests by users. The authentication is based on the user account and credentials to verify the legality of the user's identity and prevent unauthorized access. Access control, based on the user's identity, credentials, and roles (privileges), grants access to the target operating system (OS) for privileged users and denies access to users without permission. Access control is based on specific access control policies. The policies should allow for addition, deletion, modification, and query. Users who pass authentication should be able to access the target OS, and access management should take responsibility for ensuring access to the target OS. + +## 6.2 Architecture of TMN with the IAM capability + +The IAM for TMN is to enable a unified user authentication and access control gateway for any access to the management entities, i.e., operation systems (OSs), in TMN. When IAM is enabled, a user will interact with IAM to apply access to a target entity. Only when the identity of the user is verified, and its authorization is correct will IAM grant access permission (and approach) to the user. In this way, users will not have to keep massive accounts and passwords for different objects. After being verified by IAM, the user can access all objects for which the user has privilege. IAM will take over the + +complexity of assuring that the user accesses a specific object with the proper authentication and privilege. + +IAM functions can be implemented as a special OS, denoted as operation system for identity and access management (OS(IAM)). Figure 2 provides the architecture of TMN with IAM capability and X/F/Q interfaces exist between OS(IAM) and other OSs in TMN according to [ITU-T M.3010]. + +![Figure 2: Physical architecture of TMN with the IAM capability. A central DCN (Data Communication Network) is connected to various entities: OS (stack), OS(IAM), WS (stack), QMD (stack), NE (stack), and QA (stack). Interfaces are labeled: X/F/Q between OS and DCN; X/F/Q between OS(IAM) and DCN; F between DCN and WS; Q between DCN and QMD; Q between DCN and NE; Q/F/X between DCN and QA; and Q between QMD and NE. A legend indicates a circle with a diagonal line represents an 'Interface'. Reference M.3411(25) is noted.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Figure 2: Physical architecture of TMN with the IAM capability. A central DCN (Data Communication Network) is connected to various entities: OS (stack), OS(IAM), WS (stack), QMD (stack), NE (stack), and QA (stack). Interfaces are labeled: X/F/Q between OS and DCN; X/F/Q between OS(IAM) and DCN; F between DCN and WS; Q between DCN and QMD; Q between DCN and NE; Q/F/X between DCN and QA; and Q between QMD and NE. A legend indicates a circle with a diagonal line represents an 'Interface'. Reference M.3411(25) is noted. + +**Figure 2 – Physical architecture of TMN with the IAM capability** + +The OS(IAM) serves as a unified gateway for users to access all management entities involved in management activities in TMN to enhance the security in TMN. The security requirements of TMN have been specified in [ITU-T M.3016.1]. + +An implementation example of TMN with IAM capability is given in Figure 3. The F interface is located between WS and other OSs, including OS(IAM). The X interface is located between OS(IAM) and other OS entities, denoted as OS(Tele.Mgt) in another TMN domain. The Q interface is between OSs and NE in the same TMN domain. + +![Figure 3: Implementation example of TMN with the IAM capability. Two TMN domains are shown. The left domain contains WS, OS(Tele.Mgt) (stack), and NE connected by F and Q interfaces. The right domain contains WS, OS(IAM), OS(Tele.Mgt) (stack), and NE. WS connects to OS(IAM) via F and to OS(Tele.Mgt) via F. OS(IAM) connects to OS(Tele.Mgt) via Q and to the left domain's OS(Tele.Mgt) via X. OS(Tele.Mgt) connects to NE via Q. Reference M.3411(25) is noted.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +Figure 3: Implementation example of TMN with the IAM capability. Two TMN domains are shown. The left domain contains WS, OS(Tele.Mgt) (stack), and NE connected by F and Q interfaces. The right domain contains WS, OS(IAM), OS(Tele.Mgt) (stack), and NE. WS connects to OS(IAM) via F and to OS(Tele.Mgt) via F. OS(IAM) connects to OS(Tele.Mgt) via Q and to the left domain's OS(Tele.Mgt) via X. OS(Tele.Mgt) connects to NE via Q. Reference M.3411(25) is noted. + +**Figure 3 – Implementation example of TMN with the IAM capability** + +## 6.3 General objectives of IAM for TMN + +To support telecommunication operation management for security assurance, IAM for TMN should satisfy some high-level principles specified in [ITU-T M.3016.0] and [ITU-T M.3410]. The following requirements are included in the general objectives of IAM for TMN. + +- IAM for TMN is required to be compatible with TMN security related standards. +- IAM for TMN is required to support a unified identity and access management, which can be applied to both current and future TMN. +- IAM for TMN is required to support the identification of malicious access attempts to TMN. +- IAM for TMN is required to manage access to multiple different systems in the TMN domain. +- IAM for TMN is recommended to support the integration of emerging IT and AI technologies for improved efficiency. + +# 7 Functional requirements for OS(IAM) + +## 7.1 Functional framework of OS(IAM) + +The functional framework of OS(IAM) is illustrated in Figure 4. It mainly consists of a user identity management function set and an access management function set. + +![Functional framework of OS(IAM) diagram](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram illustrates the functional framework of OS(IAM). It is titled "OS(IAM)" and is divided into two main columns: "Identity management" and "Access management". + +- Identity management** column contains four stacked boxes: "User management", "Role management", "Privilege management", and "Credential management". +- Access management** column contains four stacked boxes: "Authentication management", "Access control", "Policy management", and "Temp credential application". + +At the bottom right of the diagram, the text "M.3411(25)" is present. + +Functional framework of OS(IAM) diagram + +**Figure 4 – Functional requirements of OS(IAM)** + +**Identity management** function set includes user management, role management, privilege management, and credential management. + +- **User management.** A user is an entity that uses the management entities or performs management operations on the managed entities (network elements (NE), etc.) in TMN. User management function is required to include the creation, deletion, modification, and view of user accounts and profile information, as well as the deactivation and activation of user accounts. +- **Role management.** A role is an identifier for a uniquely identifiable group of users and has a set of properties or attributes that describe the capabilities or functions performed by an entity. A user may have multiple roles. Role management function is required to include the addition, deletion, modification, and view of roles, as well as the assignment of roles to users. +- **Privilege management.** A privilege is a type of identity attribute that identifies whether a user has the right to access a target object. Privilege management function is required to include the assignment, removal, and view of privileges in roles. +- **Credential management.** A credential is an identity attribute used to verify that a user is who they claim to be. It typically includes elements such as passwords, certificates, or other forms of identification that confirm a user's identity. Credential management function is + +required to include generating, issuing, modifying, expiring, activating, and deactivating credentials. + +**Access management** function set includes authentication management, access control, access policy management, and temporary credential application. + +- **Authentication.** Authentication refers to the processes and systems used to verify the identity of users before granting them access to the target object. In TMN, user authentication function is required to include proving the identity of the legitimate user and preventing masquerading attacks by illegitimate users [ITU-T M.3016.2]. +- **Access control.** Access control refers to methods or processes that ensure only authorized users can access specific targets. Access control function is required to include granting permission, denying access requests, or terminating an established connection based on authentication results, privileges, and access control policies. +- **Access policy management.** An access policy is an access control constraining mechanism (i.e., what business permissions a user can execute during runtime). Access policy management function is required to include adding, deleting, modifying and viewing policies, deactivating, and activating an existing access policy, and translating an access policy into specific rules that can be implemented by authentication management and access control functions. +- **Temporary credential application.** After the successful verification of user identity and privilege, OS(IAM) will be responsible for getting correct access to the target entity. Although fixed credentials will work, temporary credentials or one-time credentials may be applied for certain access attempts. The temporary credential application function works in such scenarios and is recommended to include applying temporary credentials by providing necessary identity information and storing the temporary credentials applied. + +## 7.2 Requirements of identity management function set + +### 7.2.1 User management + +The requirements for user management consist of the following. + +- UM-01: It is required to support creation, deletion, modification, and view of user accounts and profiles. +- UM-02: It is required to support deactivating or activating the user account. +- UM-03: It is recommended to support synchronizing identity data from other identity registries, for example, other OSs in TMN. +- UM-04: It is recommended to support expiring user accounts without deleting them. + +### 7.2.2 Role management + +The requirements of the role management consist of the following. + +- RM-01: It is required to support the creation of different roles, including simple roles for single TMN functions, and composite roles for multiple TMN functions. +- RM-02: It is required to support the deletion, modification, and view of the roles. +- RM-03: It is required to support the view of role assignments, i.e., the roles and their related users. +- RM-04: It is required to be able to assign users with roles, multiple roles per user are permitted, but only one role per user for a specific management service. +- RM-05: It is required to allow for the view of role privileges. + +#### **7.2.3 Privilege management** + +The requirements of privilege management consist of the following. + +- PrM-01: It is required to support addition, deletion, modification, and view of privileges on specific targets and/or operations. +- PrM-02: It is required to be able to assign privileges to roles and then modify, remove, and view the assignments of the privileges. +- PrM-03: It is required to be able to approve, review, update, and remove privileges of users. +- PrM-04: It is required to delegate and distribute privileges. +- PrM-05: It is required to support authorization management to determine if a user is permitted to perform a given operation according to the related privileges. + +#### **7.2.4 Credential management** + +The requirements of credential management consist of the following. + +- CM-01: It is required to be able to generate, issue, and store credentials, such as security questions and answers used for password recovery. +- CM-02: It is required to support the self-service update of credentials, based on some stored information, such as the current passphrase or security questions. +- CM-03: It is required to be able to automatically expire a credential. +- CM-04: It is required to support account re-access based on the authentication technologies. + +## **7.3 Requirements of access management function set** + +### **7.3.1 Authentication** + +The requirements of authentication consist of the following. + +- AM-01: It is required to perform authentication when new access requests arrive. +- AM-02: It is required to support the use of access policies and different methods such as passkeys, strong passwords, passphrases, and passwordless technologies. +- AM-03: It is required to support throttling and locking accounts based on repeated or total bad password submissions. + +### **7.3.2 Access control** + +The requirements of access control consist of the following. + +- AC-01: It is required to allow only authorized accesses and operations. +- AC-02: It is required to terminate the access and/or operations when the permission expires or no longer exists. +- AC-03: It is required to be able to utilize rules, including the rules configured or derived from the access policies. + +#### **7.3.3 Access policy management** + +The requirements for access policy management are as follows. + +- PoM-01: It is required to support adding, deleting, modifying, and viewing an access policy. +- PoM-02: It is required to support the translation of access policies into specific access rules based on identity attributes such as user accounts, roles, privileges, and temporal and/or spatial factors. +- PoM-03: It is required to support tracking authorization levels based on the level of the verified credentials. + +- PoM-04: It is recommended to support the setting of policies on the applicability of temporary credential application. + +#### **7.3.4 Temporary credential application** + +The requirements of temporary credential management consist of the following. + +- TCA-01: It is recommended to support the application of temporary credentials from a provider (e.g., target OS with local identity management functions) for users who have passed the authentication and privilege verification. +- TCA-02: It is recommended to support pushing to or pulling from credential providers, the necessary identity attributes that help with the application process. +- TCA-03: It is recommended to store the received temporary credential and relate the credential to the user's identity. + +## Appendix I + +## Use case examples of OS(IAM) in TMN + +(This appendix does not form an integral part of this Recommendation.) + +This appendix illustrates use case examples in a typical scenario where a network administrator wants to access a target OS (e.g., network management system (NMS) via operation system for identity and access management (OS(IAM)). In this use case, the network administrator is regarded as a user of IAM in the telecommunication management network (TMN). Hereafter, we use the term "user" to represent the network administrator. The following steps illustrate how a user gets their account, credentials, etc., how the access request is authenticated, and how the connection is controlled and terminated by IAM. The OS(IAM) administrators who are responsible for the administration of OS(IAM) can be viewed as users who have the role and privilege to perform administration operations on OS(IAM). They should also be verified and authenticated by OS(IAM) before performing any operations. + +### I.1 Establish a user account + +The OS(IAM) administrator creates accounts, issues credentials, and sets privileges for TMN users, including the creation of new users, synchronizing existing accounts and related privilege information of the TMN system, and ensuring the consistency of user identity, credentials, and privileges. The existing administrative privileges created by each sub stream system should be supported by IAM and take over the unified authentication as shown in Figure I.1. + +![Sequence diagram for establishing a user account](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +The diagram is a sequence diagram with three lifelines: User (blue), OS(IAM) (yellow), and Target OS (green). A large grey rounded rectangle contains the OS(IAM) lifeline. Inside this rectangle, there is a yellow box containing two green boxes: "Synchronizing account data from NMS" and "Create accounts and set privileges". A dashed arrow points from the Target OS lifeline to the "Synchronizing account data from NMS" box. A dashed arrow points from the OS(IAM) lifeline to the User lifeline, labeled "Issue(Account, credential)". The text "M.3411(25)" is located at the bottom right of the diagram. + +Sequence diagram for establishing a user account + +Figure I.1 – Sequence diagram for establishing a user account + +### I.2 Authenticate user access request + +Users accessing a target operation system (OS) from a workstation should pass the authentication of OS(IAM) for identity and privilege verification. The access policy management module defines the access control model and rules according to the latest access policy. The authentication management module determines whether the user can access a target object and perform the expected operations, such as user account and status check and credential verification, based on identity as shown in Figure I.2. + +![Sequence diagram of authenticating user's access request. Lifelines: User (blue), OS(IAM) (yellow), Target OS (green). The User sends an 'Access request' to the OS(IAM). The OS(IAM) performs a 'User account and status check'. If it 'Fails', it sends an 'Access deny' back to the User. If it 'Passes', it performs a 'User credential verification'. If this 'Fails', it sends an 'Access deny' back to the User. If it 'Passes', it sends an 'Access grant' to the Target OS. A note 'M.3411(25)' is at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +``` + +sequenceDiagram + participant User + participant OS_IAM as OS(IAM) + participant Target_OS as Target OS + Note right of OS_IAM: User account and status check + User->>OS_IAM: Access request + OS_IAM-->>User: Access deny (Fail) + OS_IAM-->>OS_IAM: Pass + Note right of OS_IAM: User credential verification + OS_IAM-->>User: Access deny (Fail) + OS_IAM-->>OS_IAM: Pass + OS_IAM->>Target_OS: Access grant + +``` + +Sequence diagram of authenticating user's access request. Lifelines: User (blue), OS(IAM) (yellow), Target OS (green). The User sends an 'Access request' to the OS(IAM). The OS(IAM) performs a 'User account and status check'. If it 'Fails', it sends an 'Access deny' back to the User. If it 'Passes', it performs a 'User credential verification'. If this 'Fails', it sends an 'Access deny' back to the User. If it 'Passes', it sends an 'Access grant' to the Target OS. A note 'M.3411(25)' is at the bottom right. + +**Figure I.2 – Sequence diagram of authenticating user's access request** + +- If the authentication fails, the user is allowed to retry a certain number of times according to the access policy. After multiple failed attempts, the user is denied access, and abnormal access events are recorded. +- If the authentication passes, the user is allowed to access the target OS. + +### I.3 Verify user privilege + +When a user accesses the target OS through OS(IAM) after authentication, OS(IAM) informs the target OS of the user's identity including user account, role, and privilege information. The user privilege to perform specific operations within the target OS will be further confirmed by the target OS, as shown in Figure I.3. + +- If the privilege requirements are met, the user is allowed to take the operations. +- Otherwise, the user operation is denied, and abnormal operation events are recorded. + +![Sequence diagram of verifying user privilege. Lifelines: User (blue), OS(IAM) (yellow), Target OS (green). The OS(IAM) sends 'User identity' information to the Target OS. The Target OS performs a 'Privilege check'. It sends an 'Allow/deny' response to the OS(IAM), which in turn sends an 'Allow/deny' response to the User. A note 'M.3411(25)' is at the bottom right.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +``` + +sequenceDiagram + participant User + participant OS_IAM as OS(IAM) + participant Target_OS as Target OS + Note right of Target_OS: Privilege check + OS_IAM->>Target_OS: User identity + Target_OS-->>OS_IAM: Allow/deny + OS_IAM-->>User: Allow/deny + +``` + +Sequence diagram of verifying user privilege. Lifelines: User (blue), OS(IAM) (yellow), Target OS (green). The OS(IAM) sends 'User identity' information to the Target OS. The Target OS performs a 'Privilege check'. It sends an 'Allow/deny' response to the OS(IAM), which in turn sends an 'Allow/deny' response to the User. A note 'M.3411(25)' is at the bottom right. + +**Figure I.3 – Sequence diagram of verifying user privilege** + +### I.4 Terminate user connection + +Based on the access policy, OS(IAM) will disconnect the user link and terminate the user access when the user mistakenly operates at a certain time or reaches the preset access time limit, as shown in Figure I.4. + +![Sequence diagram of terminating user connection](2cde062fd82833415971a8bd1a2cafab_img.jpg) + +A sequence diagram illustrating the termination of a user connection. It features three lifelines: 'User' (blue box), 'OS(IAM)' (yellow box), and 'Target OS' (green box). The 'OS(IAM)' lifeline has a yellow activation bar. A message arrow labeled 'Terminate connection' originates from a green square on the 'OS(IAM)' activation bar and points to the 'User' lifeline. The background is a light gray rounded rectangle. The text 'M.3411(25)' is located at the bottom right of the diagram area. + +Sequence diagram of terminating user connection + +Figure I.4 – Sequence diagram of terminating user connection + +## Bibliography + +- [b-ITU-T X.1252] Recommendation ITU-T X.1252 (2021), *Baseline identity management terms and definitions.* +- [b-ITU-T X.1257] Recommendation ITU-T X.1257 (2016), *Identity and access management taxonomy.* + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.35-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.35-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.35-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.350-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.350-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a04b348f32791eaa466b7f9bc07e8b065c9e78f7 --- /dev/null +++ b/marked/M/T-REC-M.350-198811-I_PDF-E/raw.md @@ -0,0 +1,62 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.350** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**NUMBERING OF MASTERGROUPS +WITHIN A SUPERMASTERGROUP** + +**ITU-T Recommendation M.350** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.350 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# NUMBERING OF MASTERGROUPS WITHIN A SUPERMASTERGROUP + +The position of a mastergroup within a supermastergroup is identified by a number in the series from 7 to 9 which refers to one of the numbers of the mastergroups constituting the basic supermastergroup. + +The numbering is shown in Figure 1/M.350. + +![Diagram showing the numbering of mastergroups within a supermastergroup. It includes mastergroup numbers 7, 8, and 9, and their corresponding frequency ranges in kHz. A bracket on the right side groups these as a 'Basic supermastergroup'. Below this, a larger triangle shows the overall frequency range from 8516 kHz to 12388 kHz.](a854aa286b14d26d27047ee5893ffaa7_img.jpg) + +The diagram illustrates the numbering of mastergroups within a supermastergroup. It is divided into two horizontal sections. The top section shows three mastergroups, numbered 7, 8, and 9, each represented by a small right-angled triangle. Below each number are two frequency values in kHz: 8516 for mastergroup 7, 9748 and 9836 for mastergroup 8, and 11068 and 11156 for mastergroup 9. A large curly bracket on the right side of these three triangles is labeled 'Basic supermastergroup'. The bottom section shows a single, larger right-angled triangle representing the entire supermastergroup. Below its base are two frequency values in kHz: 8516 and 12388. At the bottom right of the diagram, the text 'CCITT - 36710' and 'd01-sc' is present. + +| Mastergroup No. | Frequency kHz | +|------------------------|---------------| +| 7 | 8516 | +| 8 | 9748, 9836 | +| 9 | 11068, 11156 | +| Basic supermastergroup | | +| | 8516, 12388 | + +Diagram showing the numbering of mastergroups within a supermastergroup. It includes mastergroup numbers 7, 8, and 9, and their corresponding frequency ranges in kHz. A bracket on the right side groups these as a 'Basic supermastergroup'. Below this, a larger triangle shows the overall frequency range from 8516 kHz to 12388 kHz. + +FIGURE 1/M.350 +Numbering of mastergroup within a supermastergroup \ No newline at end of file diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bdee1243abf897385b2cb8edc2e650da6380079 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/007b053fe94a8348f75128a584503fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd9d2d05965786da7881ca2109b236f350b26318a8c79f96b12f40bd9249d897 +size 48101 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2459d9b944c4f776cbba543b74a48ebaf375c3f --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b551b3826d1d760d55df18489c8a434efe4fbf324d783af317fcd6fc5d912d5d +size 29285 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..930eac183ddf6500e3851ad45bed7337e503c4db --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e3301e19979f64b2fe1b52e7cdf2e3c17da5e081b59347e67d057a2280264ff +size 8205 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ca61da5b04f27dc7cc6a2426e511376f3071f1e --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:143af61cd7e6a78e13c1c36d5a917ee65db49594c4dea31ef8c6fce72f896efb +size 28964 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/3ae74a33759ae31781f484406db4feed_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/3ae74a33759ae31781f484406db4feed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecde2fd69e64c580b7dced1adb0a12f78462b079 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/3ae74a33759ae31781f484406db4feed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aff0f5fe9db66be81261d988f3d6cc333f9ec5725984afa28a36d0f6ec8af105 +size 62786 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f34d6537127045e5aecdccedfba1ce7031596bb0 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ca15b0f9779856d02db06612a98a443c6be9c45d2dd67782a7e1616f1114bea +size 28360 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f390864289c323867ea64e7aef2f40a85aea78c --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35e07652f4b4a1073345f246e84965ebe860e1d843585b65e51b4ed9285e4043 +size 6819 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9500e5e9e07a54f6425c4e042ce3ccf1ef7922f --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:594ae155d4ed1a0d6c279357ad0aa59cdaa725b3cf2b953433392a18ecbbb7cf +size 26686 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebcb4979d97f76a8019a5148a90af278abe4cc67 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6112dbaf7d5738e8935728f4dd1e5c0bee9156dfd6e7f900ab2aa5acdf0311e7 +size 51645 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32e73dacd31913bf54521f0d36ce6e5fd8707780 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e536e4b0d0e352e99cc7134eb0c75017d0f3dec25bc4700fd9b9cea63883dce +size 20263 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31d93ec3f6cf0d74dd73ff0831702f49e5795121 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f33ac3253d2a44e85110ae0e05aeb38e8dfaf1af511afec7a536263783631dc +size 70604 diff --git a/marked/M/T-REC-M.3600-199210-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3600-199210-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84bff3fcbddf436bd625313016e9c5402b0b33c2 --- /dev/null +++ b/marked/M/T-REC-M.3600-199210-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c60b76398b69594a995dc43af2d3283faffaf226197182f974a6f9bed13984f5 +size 126557 diff --git a/marked/M/T-REC-M.3603-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/M/T-REC-M.3603-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a82cae4780fca00d30f8b3965937ccdc59204c17 --- /dev/null +++ b/marked/M/T-REC-M.3603-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd6b411cdffc3e752df8b68869257d7bc31a25bfa847001fd78a902b88874ee0 +size 33750 diff --git a/marked/M/T-REC-M.3603-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3603-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..094ad08ab3e4c1ce3aeef6280180677fb3dd1b65 --- /dev/null +++ b/marked/M/T-REC-M.3603-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e26379c3cb691f71e32b0eb8696c67adccc82d9f31a5becb97e336c35f665527 +size 8250 diff --git a/marked/M/T-REC-M.3603-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.3603-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..125dc3ad7a6f3d34e74ffe8cc1d9156912351a79 --- /dev/null +++ b/marked/M/T-REC-M.3603-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f38f1ef691d08e828c557c9ced483ef2f70ec83411422027a8af7cbf385dcad +size 5861 diff --git a/marked/M/T-REC-M.3603-199210-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/M/T-REC-M.3603-199210-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..093737f9debd4737a9193a2cfc8bdd8db40aec11 --- /dev/null +++ b/marked/M/T-REC-M.3603-199210-I_PDF-E/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c38036c7d7f20955ab004f2d8cb528802fb9cb12aad7af4cb3f898e0301e047b +size 20995 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3395b5f3aa2c65445c35ff6e14e6a76fcf86a1b --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53d8bfe42d21bc24e01429824b7491f79e7517a8f062f10eeef1b86a3a86ab82 +size 61294 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e166cd64c0e1f30749a505584de0df9bec23ea6b --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3741fec30ef801c5defa67a9a148557afc3350fc3a3da1b665e77c1d773c1953 +size 57785 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcda8598473f4947cd95d6a2d72c609da3240df4 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3aedfacefaf443ad368fc6e14bfd27e717d07ee664c3595ae7dd2ac60b1f96b5 +size 8222 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e31f63f2ddb51a4e554e19deb93c0afe2ff3992 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04e3b1186c219d4018069af88f464eebd93f705f545b3abbf319a3ed2080e1ca +size 45242 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ef5d77a56d0dcb34d900ea6ddd9b461849f4c6f --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6269243e2a01169792058f72c36a8fd125aecc81c01bfa98c59d5964efe5618 +size 48280 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98285d80d624f6fe4d85a95df4fd8eb4185a28d2 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e331e00aafa3b16063b31f8485be6b70db2f26615b6c7db948bf12c2aee7567a +size 6689 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/6f659142d4789aa889184459f884787e_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/6f659142d4789aa889184459f884787e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a57ddd56bca6bd475a026f66381f484ef0957aa --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/6f659142d4789aa889184459f884787e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cc860840989bb4adb946d30d60a2f2375909bd9c18602cbf73e7584c6cc5807 +size 16604 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08f82dfc69a8f71d4ac33651a849e9d95e14bd59 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e176985b4c04a362faa295173bd20b8c19599d9d8db3b8e2b550e23c7bbc5e02 +size 8441 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9a29bafcd9f4075fb7c1d6483adc0bf25ed9a8b --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0595cd29e62ccdb66e7e662b295be832f59ff7546bf84f153c9136a63d30db85 +size 31252 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65508ead607654bb0941612f4af2b326ea00b131 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0f728191d331a3db07dfd32f23f6c0829b7e63d4f6933c36a252a406320e7fa +size 34969 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8faf6a439105d68c291130ba29a14516ee74e024 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67555c3f03ba881565ece421ef3a3fd505086cf728e468cbac9b84c82c2b6aa8 +size 65221 diff --git a/marked/M/T-REC-M.3604-199210-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/M/T-REC-M.3604-199210-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7554e36204cb0c7964e6e0aecb43c25887846528 --- /dev/null +++ b/marked/M/T-REC-M.3604-199210-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73a6d20a6dadab2191244cdc262afbd983c07c9a7c5cb661c52b234d71c68f19 +size 35217 diff --git a/marked/M/T-REC-M.3610-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3610-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a16c16debfc5530f59783e0b541498a448580678 --- /dev/null +++ b/marked/M/T-REC-M.3610-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bc676c4500f11cc4624aff43b5f196e679f5cfaeb34bb963cab097ee62ca660 +size 8267 diff --git a/marked/M/T-REC-M.3610-199605-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.3610-199605-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97fc61137f54d2f975fd1649aa06eeb6640612bf --- /dev/null +++ b/marked/M/T-REC-M.3610-199605-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76ef215beb07a6bfecdc615528bf49b1ae0c086503fd08738852cfbb499509ab +size 111334 diff --git a/marked/M/T-REC-M.3610-199605-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/M/T-REC-M.3610-199605-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5992dbade7bbee5177949b53b9f7314df9dd544 --- /dev/null +++ b/marked/M/T-REC-M.3610-199605-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f2be0c4cc2c3b59c83bf7de5ffb5087ad3eff9bc9e2a373e48ba15683018b27 +size 47065 diff --git a/marked/M/T-REC-M.3610-199605-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/M/T-REC-M.3610-199605-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..417823c128c04a0e1ec76f8edd33d4a5f5b59ebf --- /dev/null +++ b/marked/M/T-REC-M.3610-199605-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff1e599198a517a1b717f0f151349e0eb01f1ea3c4b9f09008acbc588462ae07 +size 63521 diff --git a/marked/M/T-REC-M.3610-199605-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/M/T-REC-M.3610-199605-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d71c7a0a98e5c49de33cfa1cf8d4c57f6a89b13e --- /dev/null +++ b/marked/M/T-REC-M.3610-199605-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edc41018982be0ae988cfbd9732ffcf84e98ed5c6b4288b2533f8efa1103a2b6 +size 57335 diff --git a/marked/M/T-REC-M.3620-199210-I_PDF-E/raw.md b/marked/M/T-REC-M.3620-199210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..80f4e2adb85c97da389abbda0d1a3c2087b909a4 --- /dev/null +++ b/marked/M/T-REC-M.3620-199210-I_PDF-E/raw.md @@ -0,0 +1,205 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**CCITT** + +**M.3620** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +(10/92) + +**MAINTENANCE: ISDN** + +--- + +**PRINCIPLES FOR THE USE OF ISDN TEST +CALLS, SYSTEMS AND RESPONDERS** + +![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg) + +CCITT logo: A globe with the letters CCITT. + +**Recommendation M.3620** + +--- + +# FOREWORD + +The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). + +Recommendation M.3620 was prepared by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. + +## --- CCITT NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency. + +# **PRINCIPLES FOR THE USE OF ISDN TEST CALLS, SYSTEMS AND RESPONDERS** + +(1992) + +## *Abstract* + +This Recommendation provides the general principles associated with ISDN test calls originating from a test system and terminated by a test call responder. It lays down the requirements associated with test calls and lists the facilities that should be provided by a test call responder. + +## *Keywords* + +- bearer type; +- ISDN network; +- ISDN nodes; +- ISDN test calls; +- teleservice; +- test access; +- test responders; +- test systems. + +## **1 Overview** + +### **1.1 General principles for ISDN test calls** + +It is recognized that in the ISDN environment, use of controlled maintenance techniques outlined in Recommendation M.20 [1] will indicate areas where problems exist but not necessarily enable maintenance personnel to localize faults to specific equipment. To overcome this problem, the proposed ISDN test call facility should + +- enable rapid localization and diagnosis of faults without disruption to the ISDN network; +- avoid or minimise testing across sections of the ISDN network not directly associated with a failure condition; +- verify repaired equipment/restored connections before return to service; +- aid commissioning of new services; +- enable testing of new network interworking. + +## **1.2 Attributes of ISDN test calls** + +An ISDN test call may be steered and may generate diagnostic information. Where a failure would occur with live traffic, this should be unambiguously indicated (by actual failure or a failure message). + +The technician seeking to generate an ISDN test call should be able to relate types of ISDN call set-ups on which users may have experienced difficulties, to types of test calls which are available to simulate them. + +## 2 Test calls + +### 2.1 Test system functions + +### 2.1.1 ISDN test call capabilities + +Complex combinations of services and parameters should be transparent to the test technician who would recognize these as different types of available test calls. The following would be available: + +- any particular device or routing may be selected in combination with any available ISDN service; +- any available bearer type or teleservice may be selected in combination with some appropriate supplementary service; +- any invalid test call type should be abandoned by the test facility and indicated to the test technician; +- any ISDN call which would fail in service (because of unsupported services, for instance) should either fail as a test call or clearly indicate a failure condition; +- duplicate all types of valid ISDN call set-ups; +- route on destination; +- route selectively on bearer/equipment1). + +#### 2.1.2 Identify failure situations + +The ISDN test system should display clear information on an attempted ISDN call set-up. This should include + +- success or failure of the ISDN test call; and optionally; +- diagnostic information; +- display of call control messages. + +#### 2.1.3 Verification of routing + +The correct routing of an International ISDN test call should be positively confirmed to the originating maintenance personnel. This confirmation could take the form of + +- a coded message returned by the ISDN test termination giving the type and location of the termination or in its simplest form; +- a recorded announcement. + +#### 2.1.4 Network performance test + +##### 2.1.4.1 Transmission tests + +An ISDN test facility should provide access to the bearer(s) established in the call set-up for the following applications: + +- test of continuity and integrity to CCITT standards for digital circuits; +- trial interconnection for ISDN devices; +- telephony contact between test engineers. + +#### 2.1.4.2 Tests for other parameters + +For further study. + +#### 2.1.5 Single end testing + +An ISDN test termination shall enable single end testing by means of digital loopback as defined in Recommendation O.11. + +The test termination referred to here would be accessed as a dial-up facility. + +--- + +1) It is recognized that this facility will only be available when an ISDN test station is part of the fabric of a switching unit. + +## 2.2 *ISDN responder equipment* + +The ISDN test termination could be associated with equipment capable of + +- carrying out a pre-determined sequence of interactive tests; +- returning parameters and other service information to the originating test technician. + +These uses have implications for digital ATME and testing protocols under TMN, and are considered to be beyond the scope of this Recommendation. + +## 2.3 *ISDN responder facilities* + +### 2.3.1 *Valid test calls* + +The responder should respond automatically to any available bearer type or teleservice. This may be implemented in combination with some supplementary services. + +### 2.3.2 *Test access* + +A test access responder should have the capability to terminate calls from each of the available bearer capabilities (e.g. 64 kbit/s, 3.1 kHz or speech). + +#### 2.3.3 *Return messages* + +In the event of a test call being successfully routed to a responder, the responder should return an intelligible message to the originating node. The message should include + +- the responder's identity; +- the bearer capability (e.g. 64 kbit/s, 3.1 kHz or speech); +- the call teleservice (e.g. G4 Fax). + +The message should be returned by one of the following means: + +- in signalling user information provided by ISDN signalling; +- data returned over the bearer (i.e. in-band); +- voice message over the bearer. + +#### 2.3.4 *Test system to test responder interactions* + +It is anticipated that on seizure, the following sequence of events would take place: + +- the ISDN circuit termination would be seized; +- the return message would be returned using one of the methods discussed in § 3.3.3; +- the digital loopback would be established on the termination if required; +- the digital loopback would be disconnected if required; +- the bearer would be held available for interworking by the local test station with the distant end if required. + +## 3 **Destination of ISDN test calls** + +The ISDN test call system should have the capability to generate test calls to any ISDN signalling system or variant supported by the switching centre(s) with which it is associated. + +## 3.1 *International ISDN nodes* + +Test call facilities will be located at, and will operate between, major nodes on the international ISDN. Initially, it is proposed that these should be located on the national side of international gateways or at locations which are functionally equivalent. + +## 3.2 *Other ISDN nodes* + +It is recognized that the ISDN test call facilities defined in this Recommendation have possible implications throughout the ISDN network. + +The location of ISDN test call facilities in National networks is subject to + +- agreement between originating and receiving administrations; +- agreement between originating and transiting administrations; +- conformance to the general principles of testing “maintenance entities” as defined in Recommendation M.20 [1]. + +## 3.3 *Confidence testing* + +The routing of ISDN test calls to ISDN test terminations associated with the same switch or switching complex shall be possible for confidence and local testing purposes. + +## **Reference** + +- [1] CCITT Recommendation M.20 *Maintenance philosophy for telecommunications networks.* \ No newline at end of file diff --git a/marked/M/T-REC-M.3621-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3621-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e86be364c2e70dc0688295c12b1f0dfde871be1 --- /dev/null +++ b/marked/M/T-REC-M.3621-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f5a9bf4a6fdd6b2b1432e4a58154012788a8fe0b6a49989a97624d32d6d507c +size 8198 diff --git a/marked/M/T-REC-M.3621-199507-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/M/T-REC-M.3621-199507-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9826c34390a7152a8d449549deb1f0c812c5e89b --- /dev/null +++ b/marked/M/T-REC-M.3621-199507-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454f876e09c4dc297baab316a106d648c82693c0dc01ae9e9e7d0b19588aab59 +size 125374 diff --git a/marked/M/T-REC-M.3641-199410-I_PDF-E/raw.md b/marked/M/T-REC-M.3641-199410-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..692320aec4d0624fb54d017710a6d082bd403988 --- /dev/null +++ b/marked/M/T-REC-M.3641-199410-I_PDF-E/raw.md @@ -0,0 +1,2128 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3641** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(10/94) + +**MAINTENANCE** + +**INTEGRATED SERVICES DIGITAL NETWORKS** + +--- + +**MANAGEMENT INFORMATION MODEL FOR +THE MANAGEMENT OF THE DATA LINK +AND NETWORK LAYER OF THE ISDN +D-CHANNEL** + +**ITU-T Recommendation M.3641** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation M.3641 was prepared by ITU-T Study Group 4 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 15th of October 1994. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +Page + +| | | | +|------|-------------------------------------------------|----| +| 1 | Overview of the Model ..... | 1 | +| 2 | Managed object classes ..... | 4 | +| 2.1 | Access port ISDN ..... | 4 | +| 2.2 | D Channel ..... | 4 | +| 2.3 | D-channel log ..... | 4 | +| 2.4 | Error frames log record..... | 4 | +| 2.5 | Invalid frames log record..... | 4 | +| 2.6 | Managed data link D-channel ..... | 4 | +| 2.7 | Managed data link current data..... | 5 | +| 2.8 | Managed data link history data..... | 5 | +| 2.9 | Managed network layer D-channel ..... | 5 | +| 2.10 | Managed network layer current data ..... | 5 | +| 2.11 | Managed network layer history data..... | 5 | +| 2.12 | Message call reference error log record..... | 6 | +| 2.13 | Other special message log record ..... | 6 | +| 2.14 | Special message type log record..... | 6 | +| 2.15 | Timer expiry network log record ..... | 6 | +| 2.16 | Unexpected frames log record ..... | 6 | +| 3 | Packages..... | 6 | +| 3.1 | Access port ISDN ..... | 6 | +| 3.2 | D-channel..... | 7 | +| 3.3 | D-channel log ..... | 7 | +| 3.4 | Error frames log record..... | 7 | +| 3.5 | Invalid frames log record..... | 7 | +| 3.6 | Invalid frames current data ..... | 7 | +| 3.7 | Invalid frames history data ..... | 8 | +| 3.8 | Invalid frames notification..... | 8 | +| 3.9 | Message call reference error current data ..... | 8 | +| 3.10 | Message call reference error history data ..... | 8 | +| 3.11 | Message call reference error log record..... | 9 | +| 3.12 | Message call reference error notification..... | 9 | +| 3.13 | Managed data link D-channel ..... | 9 | +| 3.14 | Managed data link current data..... | 9 | +| 3.15 | Managed data link history data..... | 10 | +| 3.16 | Managed network layer D-channel ..... | 10 | +| 3.17 | Managed network layer current data ..... | 10 | +| 3.18 | Managed network layer history data..... | 11 | +| 3.19 | Other special message current data..... | 11 | +| 3.20 | Other special message log record ..... | 11 | +| 3.21 | Other special message notification ..... | 12 | + +3.22 Other special message history data..... 12 + +3.23 Special message type log record..... 12 + +3.24 Timer expiry network log record..... 12 + +3.25 Unexpected frames log record..... 12 + +4 Name bindings ..... 13 + +4.1 Access port ISDN – Managed element..... 13 + +4.2 D-channel log – Managed element ..... 13 + +4.3 D-channel – Access port ISDN..... 13 + +4.4 Managed data link D-channel – D-channel ..... 13 + +4.5 Managed network layer D-channel – D-channel ..... 14 + +4.6 Managed data link current data – Managed data link D-channel ..... 14 + +4.7 Managed network layer current data – Managed network layer D-channel ..... 14 + +5 Attributes..... 15 + +5.1 Call Reference Flag ..... 15 + +5.2 Call Reference Value..... 15 + +5.3 Cause Value..... 15 + +5.4 Data Link State ..... 16 + +5.5 Error Frames ..... 16 + +5.6 Frame Type..... 16 + +5.7 Invalid Frames ..... 16 + +5.8 Managed data link D-channel identification..... 16 + +5.9 Managed network layer D-channel identification..... 16 + +5.10 Message call reference error..... 17 + +5.11 Message call reference errors ..... 17 + +5.12 Messages too short..... 17 + +5.13 Messages with general information element missing ..... 17 + +5.14 Messages with mandatory information element missing..... 18 + +5.15 Message type ..... 18 + +5.16 Message with wrong protocol discriminator..... 18 + +5.17 Number of frames received..... 18 + +5.18 Number of frames retransmitted ..... 18 + +5.19 Number of frames transmitted ..... 18 + +5.20 Number of frames with frame check sequence error ..... 19 + +5.21 Number of invalid frames ..... 19 + +5.22 Number of timer 303 expiries ..... 19 + +5.23 Number of timer 310 expiries ..... 19 + +5.24 Oldest record age ..... 19 + +5.25 Other special message..... 20 + +5.26 Received ..... 20 + +5.27 Relating To Active Call..... 20 + +5.28 Restart messages received ..... 20 + +5.29 Restart messages transmitted ..... 20 + +5.30 Special message type ..... 20 + +5.31 Status messages received..... 21 + +5.32 Status messages transmitted..... 21 + +| | | Page | +|------|-------------------------------------------------------------|-------------| +| 5.33 | TEI value ..... | 21 | +| 5.34 | Timer expiry network ..... | 21 | +| 5.35 | Type Of Error Frame ..... | 21 | +| 5.36 | Type Of Timer ..... | 21 | +| 5.37 | Unexpected frames ..... | 22 | +| 6 | Notifications ..... | 22 | +| 6.1 | Error frames ..... | 22 | +| 6.2 | Invalid frames ..... | 22 | +| 6.3 | Message call reference error ..... | 23 | +| 6.4 | Oldest record less than limit ..... | 23 | +| 6.5 | Other special message..... | 23 | +| 6.6 | Special message type ..... | 24 | +| 6.7 | Timer expiry network ..... | 24 | +| 6.8 | Unexpected frames ..... | 24 | +| 7 | ASN.1 Type definitions module..... | 25 | +| 8 | Support objects from other ITU-T Recommendations ..... | 27 | +| 9 | Functional unit ..... | 27 | +| 9.1 | Definition of the fpmMonitorDchannel functional unit..... | 27 | +| 9.2 | Negotiation of the fpmMonitorDchannel functional unit ..... | 29 | +| 10 | Conformance ..... | 29 | +| 11 | References ..... | 30 | + +# **ABSTRACT** + +This Recommendation provides the management information model of the Q3-interface in a TMN [8] for the management of the D-channels in an ISDN switch. In particular, it focuses on the fault and performance management of the data link and network layer of ISDN D-channels. Managed objects are specified by using the OSI-management templates of Recommendation X.722 [5]. These specifications are based on the prosaic description of the D-channel management aspects as provided by Recommendation M.3640. + +## **KEYWORDS** + +Fault Management, Management of ISDN D-channel, Performance Management. + +# MANAGEMENT INFORMATION MODEL FOR THE MANAGEMENT OF THE DATA LINK AND NETWORK LAYER OF THE ISDN D-CHANNEL + +(Geneva, 1994) + +## 1 Overview of the Model + +This clause provides a conceptual framework for understanding how the various managed object classes are used to provide the performance monitoring services described in this Recommendation. The managed objects defined in this Recommendation are derived from the managed object class definitions in Recommendations Q.822 [2] and M.3100 [6]. They are based on the prosaic description of the D-channel management aspects as provided by Recommendation M.3640 [1] and supersedes the definitions as contained in the appendix of M.3640 [1]. + +The naming schema for the management of the ISDN D-channel data link and network layer is shown in Figure 1. + +![A hierarchical diagram showing the naming schema for managed object classes. At the top is 'Rec. M.3100': managed Element. Below it are 'accessPort ISDN', 'Rec. Q.822': threshold Data', 'Rec. X.721': eventForwarding Discriminator', and 'dChannelLog'. 'accessPort ISDN' points to 'dChannel', which points to 'mgdDataLink DChannel' and 'mgdNetwLayer DChannel'. 'mgdDataLink DChannel' points to 'mgdDataLink CurrentData', which points to 'mgdDataLink HistoryData'. 'mgdNetwLayer DChannel' points to 'mgdNetwLayer CurrentData', which points to 'mgdNetwLayer HistoryData'. 'dChannelLog' points to 'timerExpiry Network Log Record', 'errorFrames Log Record', 'invalidFrames Log Record', 'messageCall RefError Log Record', 'otherSpecial Message Log Record', 'specialMessage Type Log Record', 'unexpected Frames Log Record', 'Rec. X.721': objectCreation Record', 'Rec. X.721': objectDeletion Record', 'Rec. X.721': attributeValue ChangeRecord', 'Rec. X.721': stateChange Record', and 'Rec. X.721': alarm Record'. A small code 'T0405350-95/d01' is at the bottom right.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +``` + +graph TD + Root[""Rec. M.3100": managed Element"] --> AP["accessPort ISDN"] + Root --> Q822[""Rec. Q.822": threshold Data"] + Root --> X721ED[""Rec. X.721": eventForwarding Discriminator"] + Root --> DL["dChannelLog"] + + AP --> DC["dChannel"] + DC --> MDLDC["mgdDataLink DChannel"] + DC --> MNLDC["mgdNetwLayer DChannel"] + + MDLDC --> MDLCD["mgdDataLink CurrentData"] + MDLCD --> MDLHD["mgdDataLink HistoryData"] + + MNLDC --> MNLCD["mgdNetwLayer CurrentData"] + MNLCD --> MNLHD["mgdNetwLayer HistoryData"] + + DL --> TNL["timerExpiry Network Log Record"] + DL --> ELR["errorFrames Log Record"] + DL --> IFLR["invalidFrames Log Record"] + DL --> MRLR["messageCall RefError Log Record"] + DL --> OMLR["otherSpecial Message Log Record"] + DL --> SMLR["specialMessage Type Log Record"] + DL --> UFLR["unexpected Frames Log Record"] + DL --> OCR[""Rec. X.721": objectCreation Record"] + DL --> ODR[""Rec. X.721": objectDeletion Record"] + DL --> AVC[""Rec. X.721": attributeValue ChangeRecord"] + DL --> SCR[""Rec. X.721": stateChange Record"] + DL --> AR[""Rec. X.721": alarm Record"] + +``` + +T0405350-95/d01 + +A hierarchical diagram showing the naming schema for managed object classes. At the top is 'Rec. M.3100': managed Element. Below it are 'accessPort ISDN', 'Rec. Q.822': threshold Data', 'Rec. X.721': eventForwarding Discriminator', and 'dChannelLog'. 'accessPort ISDN' points to 'dChannel', which points to 'mgdDataLink DChannel' and 'mgdNetwLayer DChannel'. 'mgdDataLink DChannel' points to 'mgdDataLink CurrentData', which points to 'mgdDataLink HistoryData'. 'mgdNetwLayer DChannel' points to 'mgdNetwLayer CurrentData', which points to 'mgdNetwLayer HistoryData'. 'dChannelLog' points to 'timerExpiry Network Log Record', 'errorFrames Log Record', 'invalidFrames Log Record', 'messageCall RefError Log Record', 'otherSpecial Message Log Record', 'specialMessage Type Log Record', 'unexpected Frames Log Record', 'Rec. X.721': objectCreation Record', 'Rec. X.721': objectDeletion Record', 'Rec. X.721': attributeValue ChangeRecord', 'Rec. X.721': stateChange Record', and 'Rec. X.721': alarm Record'. A small code 'T0405350-95/d01' is at the bottom right. + +FIGURE 1/M.3641 +**Illustration of the naming schema** + (Arrows point from superior to subordinate object classes) + +The monitored entities are the protocol machine objects mgdDataLinkDChannel for layer 2 and mgdNetwLayerDChannel for layer 3 contained in the D-channel objects. + +The inheritance hierarchy for the management of the ISDN D-channel data link and network layer is shown in Figure 2. + +![Inheritance hierarchy diagram for Recommendation M.3641. The root node is 'top'. It branches into 'historyData (Q.822)', 'scanner (X.738)', 'mgdDataLink DChannel', 'mgdNetwLayer DChannel', 'log (X.721)', 'log Record (X.721)', and 'termination Point (M.3100)'. 'historyData' branches into 'mgdDataLink HistoryData' and 'mgdNetwLayer HistoryData'. 'scanner' branches into 'Current Data (Q.822)', which further branches into 'mgdDataLink CurrentData' and 'mgdNetwLayer CurrentData'. 'log' and 'log Record' both branch into 'dChannel Log' and 'event Log Record (X.721)'. 'event Log Record' branches into 'timerExpiry Network LogRecord', 'errorFrames Log Record', 'invalidFrames Log Record', 'messageCall RefError LogRecord', 'unexpected Frames LogRecord', 'otherSpecial Message LogRecord', and 'specialMessage Type LogRecord'. 'termination Point' branches into 'connection Termination Point Source (X.3100)', 'connection Termination Point Sink (X.3100)', 'trail Termination Point Source (X.3100)', and 'trail Termination Point Sink (X.3100)'. 'connection Termination Point Source' and 'connection Termination Point Sink' both lead to 'connection Termination Point Bidirectional (M.3100)', which leads to 'dChannel'. 'trail Termination Point Source' and 'trail Termination Point Sink' both lead to 'trail Termination Point Bidirectional (M.3100)', which leads to 'acces Port ISDN'. A small code 'T0405360-95/d02' is at the bottom right.](2ee59e629035d641140e55f4d215b0d7_img.jpg) + +``` + +graph TD + top[top] --> historyData["historyData (Q.822)"] + top --> scanner["scanner (X.738)"] + top --> mgdDataLinkDChannel["mgdDataLink DChannel"] + top --> mgdNetwLayerDChannel["mgdNetwLayer DChannel"] + top --> logX721["log (X.721)"] + top --> logRecordX721["log Record (X.721)"] + top --> terminationPoint["termination Point (M.3100)"] + + historyData --> mgdDataLinkHistoryData["mgdDataLink HistoryData"] + historyData --> mgdNetwLayerHistoryData["mgdNetwLayer HistoryData"] + + scanner --> currentData["Current Data (Q.822)"] + currentData --> mgdDataLinkCurrentData["mgdDataLink CurrentData"] + currentData --> mgdNetwLayerCurrentData["mgdNetwLayer CurrentData"] + + logX721 --> dChannelLog["dChannel Log"] + logX721 --> eventLogRecord["event Log Record (X.721)"] + logRecordX721 --> dChannelLog + logRecordX721 --> eventLogRecord + + eventLogRecord --> timerExpiry["timerExpiry Network LogRecord"] + eventLogRecord --> errorFrames["errorFrames Log Record"] + eventLogRecord --> invalidFrames["invalidFrames Log Record"] + eventLogRecord --> messageCallRefError["messageCall RefError LogRecord"] + eventLogRecord --> unexpectedFrames["unexpected Frames LogRecord"] + eventLogRecord --> otherSpecial["otherSpecial Message LogRecord"] + eventLogRecord --> specialMessageType["specialMessage Type LogRecord"] + + terminationPoint --> ctpSource["connection Termination Point Source (X.3100)"] + terminationPoint --> ctpSink["connection Termination Point Sink (X.3100)"] + terminationPoint --> ttpSource["trail Termination Point Source (X.3100)"] + terminationPoint --> ttpSink["trail Termination Point Sink (X.3100)"] + + ctpSource --> ctpBidirectional["connection Termination Point Bidirectional (M.3100)"] + ctpSink --> ctpBidirectional + ctpBidirectional --> dChannel["dChannel"] + + ttpSource --> ttpBidirectional["trail Termination Point Bidirectional (M.3100)"] + ttpSink --> ttpBidirectional + ttpBidirectional --> accesPort["acces Port ISDN"] + +``` + +T0405360-95/d02 + +Inheritance hierarchy diagram for Recommendation M.3641. The root node is 'top'. It branches into 'historyData (Q.822)', 'scanner (X.738)', 'mgdDataLink DChannel', 'mgdNetwLayer DChannel', 'log (X.721)', 'log Record (X.721)', and 'termination Point (M.3100)'. 'historyData' branches into 'mgdDataLink HistoryData' and 'mgdNetwLayer HistoryData'. 'scanner' branches into 'Current Data (Q.822)', which further branches into 'mgdDataLink CurrentData' and 'mgdNetwLayer CurrentData'. 'log' and 'log Record' both branch into 'dChannel Log' and 'event Log Record (X.721)'. 'event Log Record' branches into 'timerExpiry Network LogRecord', 'errorFrames Log Record', 'invalidFrames Log Record', 'messageCall RefError LogRecord', 'unexpected Frames LogRecord', 'otherSpecial Message LogRecord', and 'specialMessage Type LogRecord'. 'termination Point' branches into 'connection Termination Point Source (X.3100)', 'connection Termination Point Sink (X.3100)', 'trail Termination Point Source (X.3100)', and 'trail Termination Point Sink (X.3100)'. 'connection Termination Point Source' and 'connection Termination Point Sink' both lead to 'connection Termination Point Bidirectional (M.3100)', which leads to 'dChannel'. 'trail Termination Point Source' and 'trail Termination Point Sink' both lead to 'trail Termination Point Bidirectional (M.3100)', which leads to 'acces Port ISDN'. A small code 'T0405360-95/d02' is at the bottom right. + +FIGURE 2/M.3641 +**Illustration of the inheritance hierarchy** + (Arrows point from superclasses to their subclasses) + +The Current PM data is collected for the Monitored Objects by instances of mgdDataLinkCurrentData and mgdNetwLayerCurrentData object classes. Instances of the current data object classes are contained by the monitored object. The details on the behaviour of the current data objects regarding the collection and emission of reports are defined in Recommendation Q.822 [2]. mgdDataLink and mgdNetwLayer history data objects, defined as subclasses of historyData in Q.822 [2] are contained in the respective current data objects. The history objects store the information collected during the performance interval. + +The specific objects in the model are: + +- accessPortISDN Object – This object **reflects the management view of an ISDN access port in a switch and** is used for naming the D-channel objects1). +- dChannel Object – This object reflects the management view of an ISDN D channel in a switch and is used for naming the mgdDataLinkDChannel and mgdNetwLayerDChannel objects1). +- dChannelLog Object – This object is the managed object for logging in case the protocol machine has detected one of the following events which are defined in clause 7: an operational state change, the receipt of an invalid, error or unexpected frame, the receipt of a special message or other special message, a message call reference error or a timer expiry. +- errorFramesLogRecord Object – This object represents the logged information in the dChannelLog object in case of detection of the receipt of error frames. +- invalidFramesLogRecord Object – This object represents the logged information in the dChannelLog object in case an invalid frame other than a frame with an FCS error was received. +- messageCallReferenceErrorLogRecord Object – This object represents the logged information in the dChannelLog object in case a message with a call reference error was detected. +- mgdDataLinkDChannel Object – This object is the managed object for which the performance measurements are being collected. It represents the resource Layer 2 protocol machine. +- mgdNetwLayerDChannel Object – This object is the managed object for which the performance measurements are being collected. It represents the resource Layer 3 protocol machine. +- mgdDataLinkCurrentData Object – This object contains the measurements for the layer 2 protocol machine being monitored for a specified time interval (e.g. 15 minutes). +- mgdNetwLayerCurrentData Object – This object contains the measurements for the layer 3 protocol machine being monitored for a specified time interval (e.g. 15 minutes). +- mgdDataLinkHistoryData Object – This object will contain a copy of the performance attributes that are present in the mgdDataLinkCurrentData object at the end of the current interval (e.g. 15 minutes). A new instance of this object class is created at the end of each interval. +- mgdNetwLayerHistoryData Object – This object will contain a copy of the performance attributes that are present in the mgdnetwlayerCurrentData object at the end of the current interval (e.g. 15 minutes). A new instance of this object class is created at the end of each interval. +- other Special MessageTypeLogRecord Object – This object represents the logged information in the dChannelLog object in case a STATUS or RESTART message was received or transmitted. +- specialMessageTypeLogRecord Object – This object represents the logged information in the dChannelLog object in case of the receipt or transmission of a DISCONNECT, RELEASE or RELEASE COMPLETE message. +- timerExpiryNetworkLogRecord Object – This object represents the logged information in the dChannelLog object in case of the expiry of timers T308, T309, T316 or T317. + +--- + +1) The accessPort ISDN and D-channel objects are currently for further study and will be further specified in Q-Series Recommendations. + +- unexpectedFramesLogRecord Object – This object represents the logged information in the dChannelLog object in case of the receipt of unexpected frames. + +In addition, the generic thresholdData and scanner [X.738] support objects as defined in Recommendation Q.822 [2] and log and eventLogRecord support objects as defined in Recommendation X.721 [4] are included in the model. + +## 2 Managed object classes + +### 2.1 Access port ISDN2) + +``` +accessPortISDN MANAGED OBJECT CLASS + DERIVED FROM "Recommendation M.3100 : 1992": trailTerminationPointBidirectional; + CHARACTERIZED BY accessPortISDN-package; + +REGISTERED AS { m3641ManagedObjectClass 1 }; +``` + +### 2.2 D Channel2) + +``` +dChannel MANAGED OBJECT CLASS + DERIVED FROM "Recommendation M.3100 : 1992": connectionTerminationPointBidirectional; + CHARACTERIZED BY dChannel-package; + +REGISTERED AS { m3641ManagedObjectClass 2 }; +``` + +### 2.3 D-channel log + +``` +dChannelLog MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":log; + CHARACTERIZED BY dChannelLog-package; + +REGISTERED AS { m3641ManagedObjectClass 3 }; +``` + +### 2.4 Error frames log record + +``` +errorFramesLogRecord MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; + CHARACTERIZED BY errorFramesLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 4 }; +``` + +### 2.5 Invalid frames log record + +``` +invalidFramesLogRecord MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; + CHARACTERIZED BY invalidFramesLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 5 }; +``` + +### 2.6 Managed data link D-channel + +``` +mgdDataLinkDChannel MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":top; + CHARACTERIZED BY mgdDataLinkDChannel-package; + CONDITIONAL PACKAGES + invalidFramesNotification-package PRESENT IF + "the events of invalid frame received are to be logged3)."; + +REGISTERED AS { m3641ManagedObjectClass 6 }; +``` + +2) The accessPort ISDN and D-channel objects are currently for further study and will be further specified in Q-Series Recommendations. + +3) This case is one of two alternatives (see Recommendation M.3640): the events of *invalid frame received* may be counted or logged. + +### 2.7 Managed data link current data + +mgdDataLinkCurrentData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822 : 1993":currentData; +CHARACTERIZED BY "Recommendation Q.822 : 1993":thresholdPkg, +mgdDataLinkCurrentData-package; +CONDITIONAL PACKAGES +invalidFramesCurrentData-package PRESENT IF +"the events of *invalid frame received* are to be counted4)."; +REGISTERED AS { m3641ManagedObjectClass 7 }; + +### 2.8 Managed data link history data + +mgdDataLinkHistoryData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822 : 1993":historyData; +CHARACTERIZED BY mgdDataLinkHistoryData-package; +CONDITIONAL PACKAGES +invalidFramesHistoryData-package PRESENT IF +"the events of *invalid frame received* are to be counted4)" ; +REGISTERED AS { m3641ManagedObjectClass 8 }; + +### 2.9 Managed network layer D-channel + +mgdNetwLayerDChannel MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 : 1992":top; +CHARACTERIZED BY mgdNetwLayerDChannel-package; +CONDITIONAL PACKAGES +otherSpecialMessageNotification-package PRESENT IF +"the events of *other special message received* are to be logged5).", +messageCallRefErrorNotification-package PRESENT IF +"the events of *message Call Reference Error detected* are to be logged6)."; +REGISTERED AS { m3641ManagedObjectClass 9 }; + +### 2.10 Managed network layer current data + +mgdNetwLayerCurrentData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822 : 1993":currentData; +CHARACTERIZED BY "Recommendation Q.822 : 1993":thresholdPkg, +mgdNetwLayerCurrentData-package; +CONDITIONAL PACKAGES +otherSpecialMessageCurrentData-package PRESENT IF +"the events of *other special message received* are to be counted5).", +messageCallRefErrorCurrentData-package PRESENT IF +"the events of *message Call Reference Error detected* are to be counted6)."; +REGISTERED AS { m3641ManagedObjectClass 10 }; + +### 2.11 Managed network layer history data + +mgdNetwLayerHistoryData MANAGED OBJECT CLASS +DERIVED FROM "Recommendation Q.822 : 1993":historyData; +CHARACTERIZED BY mgdNetwLayerHistoryData-package; +CONDITIONAL PACKAGES +otherSpecialMessageHistoryData-package PRESENT IF +"the events of *other special message received* are to be counted5).", + +--- + +4) This case is one of two alternatives (see Recommendation M.3640): the events of *invalid frame received* may be counted or logged. + +5) This case is one of two alternatives (see Recommendation M.3640): the events of *other special message received* may be counted or logged. + +6) This case is one of two alternatives (see Recommendation M.3640): the events of *message Call Reference Error detected* may be counted or logged. + +messageCallRefErrorHistoryData-package PRESENT IF +"the events of *message Call Reference Error detected* are to be counted7)."; + +REGISTERED AS { m3641ManagedObjectClass 11 }; + +### 2.12 Message call reference error log record + +messageCallRefErrorLogRecord MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; +CHARACTERIZED BY messageCallRefErrorLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 12 }; + +### 2.13 Other special message log record + +otherSpecialMessageLogRecord MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; +CHARACTERIZED BY otherSpecialMessageLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 13 }; + +### 2.14 Special message type log record + +specialMessageTypeLogRecord MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; +CHARACTERIZED BY specialMessageTypeLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 14 }; + +### 2.15 Timer expiry network log record + +timerExpiryNetworkLogRecord MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; +CHARACTERIZED BY timerExpiryNetworkLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 15 }; + +### 2.16 Unexpected frames log record + +unexpectedFramesLogRecord MANAGED OBJECT CLASS +DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; +CHARACTERIZED BY unexpectedFramesLogRecord-package; + +REGISTERED AS { m3641ManagedObjectClass 16 }; + +## 3 Packages + +### 3.1 Access port ISDN + +accessPortISDN-package PACKAGE +BEHAVIOUR +accessPortISDNBehaviour BEHAVIOUR +DEFINED AS +"This package is contained by the access port ISDN object which reflects the management view of the +termination of an ISDN D-channel on a switch." +;; + +REGISTERED AS { m3641Package 1 }; + +--- + +7) This case is one of two alternatives (see Recommendation M.3640): the events of *message Call reference Error detected* may be counted or logged. + +### 3.2 D-channel + +dChannel-package PACKAGE +BEHAVIOUR +dChannelBehaviour BEHAVIOUR +DEFINED AS +"This package is contained by the D-channel object which reflects the management view of an ISDN D-channel on a switch." +;; +REGISTERED AS { m3641Package 2 }; + +### 3.3 D-channel log + +dChannelLog-package PACKAGE +BEHAVIOUR +dChannelLogBehaviour BEHAVIOUR +DEFINED AS +"This package contains the notification which will be sent by the dChannelLog object instance in case the D-channel Log is full and the oldest record in this log is younger than the value indicated by attribute oldestRecordAge." +;; +ATTRIBUTES +oldestRecordAge GET-REPLACE; +NOTIFICATIONS +oldestRecordLessThanLimit; +REGISTERED AS { m3641Package 3 }; + +### 3.4 Error frames log record + +errorFramesLogRecord-package PACKAGE +BEHAVIOUR +errorFramesLogRecordBehaviour BEHAVIOUR +DEFINED AS +"This managed object is used to represent logged information from notifications received from the mgdDataLinkDChannel managed object in case of detection of the receipt of error frames.";; +ATTRIBUTES +errorFrames GET; +REGISTERED AS { m3641Package 4 }; + +### 3.5 Invalid frames log record + +invalidFramesLogRecord-package PACKAGE +BEHAVIOUR +invalidFramesLogRecordBehaviour BEHAVIOUR +DEFINED AS +"This managed object is used to represent logged information from notifications received from the mgdDataLinkDChannel managed object in case an invalid frame other than a frame with an FCS error is received.";; +ATTRIBUTES +invalidFrames GET; +REGISTERED AS { m3641Package 5 }; + +### 3.6 Invalid frames current data + +invalidFramesCurrentData-package PACKAGE +BEHAVIOUR +invalidFramesCurrentDataBehaviour BEHAVIOUR +DEFINED AS +"This package contains the noOfInvalidFrames attribute. When this attribute exceeds a threshold, a qualityOfServiceAlarm notification is issued. The threshold corresponding to this attribute is contained in a thresholdData managed object. The mgdDataLinkHistoryData object corresponds to the mgdDataLinkCurrentData object according to the performance management model of Recommendation Q.822 [2].";; + +#### ATTRIBUTES + +noOfInvalidFrames REPLACE-WITH-DEFAULT +DEFAULT VALUE ASN1TypeModule.defaultZero +GET; + +REGISTERED AS { m3641Package 6 }; + +### 3.7 Invalid frames history data + +invalidFramesHistoryData-package PACKAGE + +#### BEHAVIOUR + +invalidFramesHistoryDataBehaviour BEHAVIOUR + +#### DEFINED AS + +"This package contains the history data of the noOfInvalidFrames attribute.";; + +#### ATTRIBUTES + +noOfInvalidFrames GET; + +REGISTERED AS { m3641Package 7 }; + +### 3.8 Invalid frames notification + +invalidFramesNotification-package PACKAGE + +#### BEHAVIOUR + +invalidFramesNotificationBehaviour BEHAVIOUR + +#### DEFINED AS + +"This package contains the notification which will be sent in case an invalid frame other than a frame with an FCS error is received.";; + +#### NOTIFICATIONS + +invalidFrames; + +REGISTERED AS { m3641Package 8 }; + +### 3.9 Message call reference error current data + +messageCallRefErrorCurrentData-package PACKAGE + +#### BEHAVIOUR + +messageCallRefErrorCurrentDataBehaviour BEHAVIOUR + +#### DEFINED AS + +"This package contains an attribute that counts the number of messages with a call reference error. When this attribute exceeds a threshold, a qualityofServiceAlarm notification is issued. The threshold corresponding to this attribute is contained in a thresholdData managed object. The mgdNetwLayerHistoryData object corresponds to the mgdNetwLayerCurrentData object according to the performance management model of Recommendation Q.822 [2].";; + +#### ATTRIBUTES + +messageCallReferenceErrors REPLACE-WITH-DEFAULT +DEFAULT VALUE ASN1TypeModule.defaultZero +GET; + +REGISTERED AS { m3641Package 9 }; + +### 3.10 Message call reference error history data + +messageCallRefErrorHistoryData-package PACKAGE + +#### BEHAVIOUR + +messageCallRefErrorHistoryDataBehaviour BEHAVIOUR + +#### DEFINED AS + +"This package contains the history data of the messageCallReferenceErrors attribute.";; + +#### ATTRIBUTES + +messageCallReferenceErrors GET; + +REGISTERED AS { m3641Package 10 }; + +### 3.11 Message call reference error log record + +**messageCallRefErrorLogRecord-package PACKAGE** +**BEHAVIOUR** +     **messageCallRefErrorLogRecordBehaviour BEHAVIOUR** +     **DEFINED AS** +     "This managed object is used to represent logged information from notifications received from the +     mgdNetwLayerDChannel managed object in case a message with a call reference error was detected.";; +**ATTRIBUTES** +     messageCallRefError      GET; +**REGISTERED AS { m3641Package 11 };** + +### 3.12 Message call reference error notification + +**messageCallRefErrorNotification-package PACKAGE** +**BEHAVIOUR** +     **messageCallRefErrorNotificationBehaviour BEHAVIOUR** +     **DEFINED AS** +     "This package contains the notification which will be sent by the mgdNetwLayerDChannel object instance in +     case a message with a call reference error was detected." + ;; +**NOTIFICATIONS** +     messageCallRefError; +**REGISTERED AS { m3641Package 12 };** + +### 3.13 Managed data link D-channel + +**mgdDataLinkDChannel-package PACKAGE** +**BEHAVIOUR** +     **mgdDataLinkDChannelBehaviour BEHAVIOUR** +     **DEFINED AS** +     "This managed object class reflects the management information for the data link layer protocol. The major +     part of this information is for fault and performance management.";; +**ATTRIBUTES** +     mgdDataLinkDChannelId      GET, +     "Recommendation X.721 : 1992":operationalState      GET; +**NOTIFICATIONS** +     errorFrames, +     unexpectedFrames, +     "Recommendation X.721 : 1992":stateChange; +**REGISTERED AS { m3641Package 13 };** + +### 3.14 Managed data link current data + +**mgdDataLinkCurrentData-package PACKAGE** +**BEHAVIOUR** +     **mgdDataLinkCurrentDataBehaviour BEHAVIOUR** +     **DEFINED AS** +     "When one of the attributes in this package exceeds a threshold, a qualityofServiceAlarm notification is issued. +     The thresholds corresponding to the attributes are contained in a thresholdData managed object. +     The mgdDataLinkHistoryData object is corresponding to the mgdDataLinkCurrentData object according to +     the performance management model of Recommendation Q.822 [2].";; +**ATTRIBUTES** +     noOffFramesWithFCSError      REPLACE-WITH-DEFAULT +         DEFAULT VALUE ASN1TypeModule.defaultZero +                                                                     GET, +     noOffFramesReceived      REPLACE-WITH-DEFAULT +         DEFAULT VALUE ASN1TypeModule.defaultZero +                                                                     GET, + +``` + +noOfFramesTransmitted REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, +noOfFramesRetransmitted REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET; + +``` + +REGISTERED AS { m3641Package 14 }; + +### 3.15 Managed data link history data + +``` + +mgdDataLinkHistoryData-package PACKAGE + BEHAVIOUR + mgdDataLinkHistoryDataBehaviour BEHAVIOUR + DEFINED AS + "The managed object, characterized by this package contains the history data of the performance attributes + for layer two of an ISDN D-channel.";; + ATTRIBUTES + noOfFramesWithFCSERROR GET, + noOfFramesReceived GET, + noOfFramesTransmitted GET, + noOfFramesRetransmitted GET; + +REGISTERED AS { m3641Package15 }; + +``` + +### 3.16 Managed network layer D-channel + +``` + +mgdNetwLayerDChannel-package PACKAGE + BEHAVIOUR + mgdNetwLayerDChannelBehaviour BEHAVIOUR + DEFINED AS + "This managed object class represents the management view of the basic call control function in the network + layer of the D-channel.";; + ATTRIBUTES + mgdNetwLayerDChannelId GET, + "Recommendation X.721 : 1992":operationalState GET; + NOTIFICATIONS + timerExpiryNetwork, + specialMessageType, + "Recommendation X.721 : 1992":stateChange; + +REGISTERED AS { m3641Package 16 }; + +``` + +### 3.17 Managed network layer current data + +``` + +mgdNetwLayerCurrentData-package PACKAGE + BEHAVIOUR + mgdNetwLayerCurrentDataBehaviour BEHAVIOUR + DEFINED AS + "When one of the attributes in this package exceeds a threshold, a qualityofServiceAlarm notification is issued. + The thresholds corresponding to the attributes are contained in a thresholdData managed object. + The mgdNetwLayerHistoryData object is corresponding to the mgdNetwLayerCurrentData object according + to the performance management model of Recommendation Q.822 [2].";; + ATTRIBUTES + messageWithWrongPdi REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + messagesTooShort REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + messagesWithGenInfoElemMissing REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + messagesWithMandInfoElemMissing REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + +``` + +``` + +noOft303Expiries REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, +noOft310Expiries REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET; + +REGISTERED AS { m3641Package 17 }; + +``` + +### 3.18 Managed network layer history data + +``` + +mgdNetwLayerHistoryData-package PACKAGE + BEHAVIOUR + mgdNetwLayerHistoryDataBehaviour BEHAVIOUR + DEFINED AS + "The managed object, characterized by this package contains the history data of the attributes it has.";; + ATTRIBUTES + messageWithWrongPdi GET, + messagesTooShort GET, + messagesWithGenInfoElemMissing GET, + messagesWithMandInfoElemMissing GET, + noOft303Expiries GET, + noOft310Expiries GET; + +REGISTERED AS { m3641Package 18 }; + +``` + +### 3.19 Other special message current data + +``` + +otherSpecialMessageCurrentData-package PACKAGE + BEHAVIOUR + otherSpecialMessageCurrentDataBehaviour BEHAVIOUR + DEFINED AS + "This package contains attributes that count the receipt or transmission of STATUS and RESTART messages. When one of these attributes exceeds a threshold, a qualityofServiceAlarm notification is issued. The thresholds corresponding to these attributes are contained in a thresholdData managed objet. The mgdNetwLayerHistoryData object is corresponding to the mgdNetwLayerCurrentData object according to the performance management model of Recommendation Q.822 [2].";; + ATTRIBUTES + sSTATUSMessagesReceived REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + sSTATUS MessagesTransmitted REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + rRESTARTMessagesReceived REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET, + rRESTARTMessagesTransmitted REPLACE-WITH-DEFAULT + DEFAULT VALUE ASN1TypeModule.defaultZero + GET; + +REGISTERED AS { m3641Package 19 }; + +``` + +### 3.20 Other special message log record + +``` + +otherSpecialMessageLogRecord-package PACKAGE + BEHAVIOUR + otherSpecialMessageLogRecordBehaviour BEHAVIOUR + DEFINED AS + "This managed object is used to represent logged information from notifications received from the mgdNetwLayerDChannel managed object in case a STATUS or RESTART message is received or transmitted.";; + ATTRIBUTES + otherSpecialMessage GET; + +REGISTERED AS { m3641Package 20 }; + +``` + +### 3.21 Other special message notification + +otherSpecialMessageNotification-package PACKAGE +BEHAVIOUR +otherSpecialMessageNotificationBehaviour BEHAVIOUR +DEFINED AS +"This package contains the notification which will be sent by the mgdNetwLayerDChannel object instance in case a status or restart message is received or transmitted." +;; +NOTIFICATIONS +otherSpecialMessage; +REGISTERED AS { m3641Package 21 }; + +### 3.22 Other special message history data + +otherSpecialMessageHistoryData-package PACKAGE +BEHAVIOUR +otherSpecialMessageHistoryDataBehaviour BEHAVIOUR +DEFINED AS +"This package contains the history data of the attributes it has.";; +ATTRIBUTES +sSTATUSMessagesReceived GET, +sSTATUSMessagesTransmitted GET, +rESTARTMessagesReceived GET, +rESTARTMessagesTransmitted GET; +REGISTERED AS { m3641Package 22 }; + +### 3.23 Special message type log record + +specialMessageTypeLogRecord-package PACKAGE +BEHAVIOUR +specialMessageTypeLogRecordBehaviour BEHAVIOUR +DEFINED AS +"This managed object is used to represent logged information from notifications received from the mgdNetwLayerDChannel managed object in case of the receipt or transmission of a DISCONNECT, RELEASE or RELEASE COMPLETE message.";; +ATTRIBUTES +specialMessageType GET; +REGISTERED AS { m3641Package 23 }; + +### 3.24 Timer expiry network log record + +timerExpiryNetworkLogRecord-package PACKAGE +BEHAVIOUR +timerExpiryNetworkLogRecordBehaviour BEHAVIOUR +DEFINED AS +"This managed object is used to represent logged information from notifications received from the mgdNetwLayerDChannel managed object in case of detection of the expiry of timers T308, T309, T316 or T317.";; +ATTRIBUTES +timerExpiryNetwork GET; +REGISTERED AS { m3641Package 24 }; + +### 3.25 Unexpected frames log record + +unexpectedFramesLogRecord-package PACKAGE +BEHAVIOUR +unexpectedFramesLogRecordBehaviour BEHAVIOUR + +#### **DEFINED AS** + +"This managed object is used to represent logged information from notifications received from the mgdDataLinkDChannel managed object in case of receipt of unexpected frames.";; + +#### **ATTRIBUTES** + +unexpectedFrames + +GET; + +**REGISTERED AS** { m3641Package 25 }; + +## **4 Name bindings** + +### **4.1 Access port ISDN – Managed element** + +**accessPortISDN-managedElement NAME BINDING** +**SUBORDINATE OBJECT CLASS** accessPortISDN AND SUBCLASSES; +**NAMED BY** +**SUPERIOR OBJECT CLASS** "Recommendation M.3100 : 1992":managedElement +AND SUBCLASSES; +**WITH ATTRIBUTE** "Recommendation M.3100 : 1992":tTPIId; +**CREATE** +**WITH-REFERENCE-OBJECT,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**DELETES-CONTAINED-OBJECTS;** + +**REGISTERED AS** { m3641NameBinding 1 }; + +### **4.2 D-channel log – Managed element** + +**dChannelLog-managedElement NAME BINDING** +**SUBORDINATE OBJECT CLASS** dChannelLog AND SUBCLASSES; +**NAMED BY** +**SUPERIOR OBJECT CLASS** "Recommendation M.3100 : 1992":managedElement +AND SUBCLASSES; +**WITH ATTRIBUTE** "Recommendation X.721 : 1992":logId; +**CREATE** +**WITH-REFERENCE-OBJECT,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**DELETES-CONTAINED-OBJECTS;** + +**REGISTERED AS** { m3641NameBinding 2 }; + +### **4.3 D-channel – Access port ISDN** + +**dChannel-accessPortISDN NAME BINDING** +**SUBORDINATE OBJECT CLASS** dChannel AND SUBCLASSES; +**NAMED BY** +**SUPERIOR OBJECT CLASS** accessPortISDN AND SUBCLASSES; +**WITH ATTRIBUTE** cTPIId; +**CREATE** +**WITH-REFERENCE-OBJECT,** +**WITH-AUTOMATIC-INSTANCE-NAMING;** +**DELETE** +**DELETES-CONTAINED-OBJECTS;** + +**REGISTERED AS** { m3641NameBinding 3 }; + +### **4.4 Managed data link D-channel – D-channel** + +**mgdDataLinkDChannel-dChannel NAME BINDING** +**SUBORDINATE OBJECT CLASS** mgdDataLinkDChannel AND SUBCLASSES; +**NAMED BY** + +``` + +SUPERIOR OBJECT CLASS dChannel AND SUBCLASSES; +WITH ATTRIBUTE mgdDataLinkDChannelId; +CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE + DELETES-CONTAINED-OBJECTS; + +``` + +REGISTERED AS { m3641NameBinding 4}; + +### 4.5 Managed network layer D-channel – D-channel + +``` + +mgdNetwLayerDChannel-dChannel NAME BINDING +SUBORDINATE OBJECT CLASS mgdNetwLayerDChannel AND SUBCLASSES; +NAMED BY + SUPERIOR OBJECT CLASS dChannel AND SUBCLASSES; + WITH ATTRIBUTE mgdNetwLayerDChannelId; +CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE + DELETES-CONTAINED-OBJECTS; + +``` + +REGISTERED AS { m3641NameBinding 5 }; + +### 4.6 Managed data link current data – Managed data link D-channel + +``` + +mgdDataLinkCurrentData-mgdDataLinkDChannel NAME BINDING +SUBORDINATE OBJECT CLASS mgdDataLinkCurrentData AND SUBCLASSES; +NAMED BY + SUPERIOR OBJECT CLASS mgdDataLinkDChannel AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.738 : 1992":scannerId; +CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE + DELETES-CONTAINED-OBJECTS; + +``` + +REGISTERED AS { m3641NameBinding 6 }; + +### 4.7 Managed network layer current data – Managed network layer D-channel + +``` + +mgdNetwLayerCurrentData-mgdNetwLayerDChannel NAME BINDING +SUBORDINATE OBJECT CLASS mgdNetwLayerCurrentData AND SUBCLASSES; +NAMED BY + SUPERIOR OBJECT CLASS mgdNetwLayerDChannel AND SUBCLASSES; + WITH ATTRIBUTE "Recommendation X.738 : 1992":scannerId; +CREATE + WITH-REFERENCE-OBJECT, + WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE + DELETES-CONTAINED-OBJECTS; + +``` + +REGISTERED AS { m3641NameBinding 7 }; + +The naming of mgdDataLinkHistoryData instances by mgdDataLinkCurrentData instances is specified in Recommendation Q.822 [2] by means of the name binding between currentData and historyData instances. This is also true for naming of mgdNetwLayerHistoryData instances by mgdNetwLayerCurrentData instances. The naming of thresholdData instances by managedElement instances is also specified in Recommendation Q.822 [2]. + +The naming of eventForwardingDiscriminator instances by managedElement instances is specified in Recommendation M.3100 [6]. + +The naming of the following generic and the following D-channel specific object instances by dChannelLog instances is specified in Recommendation X.721 [4] by means of the name binding between log and logRecord instances: + +- objectCreationRecord; +- objectDeletionRecord; +- attributeValueChangeRecord; +- stateChangeRecord; +- alarmRecord; +- errorFramesLogRecord; +- invalidFramesLogRecord; +- messageCallRefErrorLogRecord; +- otherSpecialMessageLogRecord; +- specialMessageTypeLogRecord; +- timerExpiryNetworkLogRecord; +- unexpectedFramesLogRecord. + +## 5 Attributes + +### 5.1 Call Reference Flag + +**callReferenceFlag** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.CallReferenceFlag; +MATCHES FOR EQUALITY; + +**BEHAVIOUR** +**callReferenceFlagBehaviour** BEHAVIOUR +DEFINED AS +"This attribute represents the value of the call reference flag.";; + +**REGISTERED AS** { m3641Attribute 1 }; + +### 5.2 Call Reference Value + +**callReferenceValue** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.CallReferenceValue; +MATCHES FOR EQUALITY; + +**BEHAVIOUR** +**callReferenceValueBehaviour** BEHAVIOUR +DEFINED AS +"This attribute represents the incorrect call reference value.";; + +**REGISTERED AS** { m3641Attribute 2 }; + +### 5.3 Cause Value + +**causeValue** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.CauseType; +MATCHES FOR EQUALITY; + +**BEHAVIOUR** +**causeValueBehaviour** BEHAVIOUR +DEFINED AS +"This attribute represents the octets three to five as defined in Recommendation Q.931, which includes the cause value, location and diagnostic field.";; + +**REGISTERED AS** { m3641Attribute 3 }; + +### 5.4 Data Link State + +**dataLinkState** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.DataLinkState; +MATCHES FOR EQUALITY; + +BEHAVIOUR +dataLinkStateBehaviour BEHAVIOUR +DEFINED AS +"This attribute represents the state of the data link.";; + +REGISTERED AS { m3641Attribute 4 }; + +### 5.5 Error Frames + +**errorFrames** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.ErrorFrames; +MATCHES FOR EQUALITY; +BEHAVIOUR +errorFramesAttrBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the specific error information that is stored in the +errorFramesLogRecord.";; + +REGISTERED AS { m3641Attribute 5 }; + +### 5.6 Frame Type + +**frameType** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.FrameType; +MATCHES FOR EQUALITY; + +BEHAVIOUR +frameTypeBehaviour BEHAVIOUR +DEFINED AS +"This attribute represents the type of the unexpected frame.";; + +REGISTERED AS { m3641Attribute 6 }; + +### 5.7 Invalid Frames + +**invalidFrames** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.InvalidFrames; +MATCHES FOR EQUALITY; +BEHAVIOUR +invalidFramesAttrBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the specific error information that is stored in the +invalidFramesLogRecord.";; + +REGISTERED AS { m3641Attribute 7 }; + +### 5.8 Managed data link D-channel identification + +**mgdDataLinkDChannelId** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.NameType; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR +mgdDataLinkDChannelIdBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the identification of the mgdDataLinkDChannel managed object +class.";; + +REGISTERED AS { m3641Attribute 8 }; + +### 5.9 Managed network layer D-channel identification + +**mgdNetwLayerDChannelId** ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.NameType; +MATCHES FOR EQUALITY, ORDERING; +BEHAVIOUR +mgdNetwLayerDChannelIdBehaviour BEHAVIOUR + +DEFINED AS "This attribute represents the identification of the mgdNetwLayerDChannel managed object class."; + +REGISTERED AS { m3641Attribute 9 }; + +### 5.10 Message call reference error + +messageCallRefError ATTRIBUTE + WITH ATTRIBUTE SYNTAX ASN1TypeModule.MessageCallRefError; + MATCHES FOR EQUALITY; + BEHAVIOUR + messageCallRefErrorAttrBehaviour BEHAVIOUR + DEFINED AS "This attribute represents the specific error information that is stored in the messageCallRefErrorLogRecord."; + +REGISTERED AS { m3641Attribute 10 }; + +### 5.11 Message call reference errors + +messageCallReferenceErrors ATTRIBUTE + DERIVED FROM "Recommendation X.721 : 1992":counter; + BEHAVIOUR + messageCallReferenceErrorsBehaviour BEHAVIOUR + DEFINED AS "A call reference is used to specify a call. This attribute represents the number of messages with call reference errors. In the following situations, the call reference error is not correct: + +| Messages | Call reference value | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| All messages except: SETUP, STATUS, RESUME | Which is not relating to an active call or a call in progress | +| SETUP, RESUME | Which is not relating to an active call or a call in progress and with a call reference flag set to "1" | +| SETUP | Which is relating to an active call or a call in progress | +| All messages except: RESTART, RESTART ACK, STATUS | Which is the global call reference | + +"; + +REGISTERED AS { m3641Attribute 11 }; + +### 5.12 Messages too short + +messagesTooShort ATTRIBUTE + DERIVED FROM "Recommendation X.721 : 1992":counter; + BEHAVIOUR + messagesTooShortBehaviour BEHAVIOUR + DEFINED AS "This attribute represents a counter for the number of messages that are too short to contain a complete message type."; + +REGISTERED AS { m3641Attribute 12 }; + +### 5.13 Messages with general information element missing + +messagesWithGenInfoElemMissing ATTRIBUTE + DERIVED FROM "Recommendation X.721 : 1992":counter; + BEHAVIOUR + messagesWithGenInfoElemMissingBehaviour BEHAVIOUR + DEFINED AS "This attribute represents a counter for counting the number of general information element errors. The counter is raised when an information element is out of sequence or when a duplicated information element was detected, see 5.8.5/Q.931."; + +REGISTERED AS { m3641Attribute 13 }; + +### 5.14 Messages with mandatory information element missing + +**messagesWithMandInfoElemMissing** ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +    **messagesWithMandInfoElemMissingBehaviour** BEHAVIOUR +    DEFINED AS "This attribute represents a counter for counting the number of messages with mandatory information element errors. The counter is raised when a mandatory information element is missing or when a mandatory information element content error was detected, see 5.8.5 and 5.8.6/Q.931.";; + +REGISTERED AS { m3641Attribute 14 }; + +### 5.15 Message type + +**messageType** ATTRIBUTE +    WITH ATTRIBUTE SYNTAX     ASN1TypeModule.MessageType; +    MATCHES FOR                 EQUALITY; +BEHAVIOUR +    **messageTypeBehaviour** BEHAVIOUR +    DEFINED AS +        "This attribute represents the type of layer 3 message.";; + +REGISTERED AS { m3641Attribute 15 }; + +### 5.16 Message with wrong protocol discriminator + +**messageWithWrongPdi** ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +    **messageWithWrongPdiBehaviour** BEHAVIOUR +    DEFINED AS "This attribute represents a counter. This counter holds the number of messages received with a protocol discriminator that is not valid, i.e. a protocol discriminator other than "Q.931 user-network call control message". The counter has an associated threshold.";; + +REGISTERED AS { m3641Attribute 16 }; + +### 5.17 Number of frames received + +**noOfFramesReceived** ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +    **noOfFramesReceivedBehaviour** BEHAVIOUR +    DEFINED AS "This attribute represents the total number of frames received for a D-channel.";; + +REGISTERED AS { m3641Attribute 17 }; + +### 5.18 Number of frames retransmitted + +**noOfFramesRetransmitted** ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +    **noOfFramesRetransmittedBehaviour** BEHAVIOUR +    DEFINED AS "This attribute represents the total number of frames retransmitted for a D-channel.";; + +REGISTERED AS { m3641Attribute 18 }; + +### 5.19 Number of frames transmitted + +**noOfFramesTransmitted** ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +    **noOfFramesTransmitted** BEHAVIOUR +    DEFINED AS "This attribute represents the total number of frames transmitted for a D-channel.";; + +REGISTERED AS { m3641Attribute 19 }; + +### 5.20 Number of frames with frame check sequence error + +**noOfFramesWithFCSERROR** ATTRIBUTE + +**DERIVED FROM "Recommendation X.721 : 1992":counter;** + +#### **BEHAVIOUR** + +**noOfFramesWithFCSERRORBehaviour            BEHAVIOUR** + +**DEFINED AS "This attribute represents a counter for the total number of frames received with FCS-error for a D-channel.";;** + +**REGISTERED AS { m3641Attribute 20 };** + +### **5.21    Number of invalid frames** + +**noOfInvalidFrames    ATTRIBUTE** + +**DERIVED FROM "Recommendation X.721 : 1992":counter;** + +#### **BEHAVIOUR** + +**noOfInvalidFramesBehaviour    BEHAVIOUR** + +**DEFINED AS "This attribute represents the number of invalid frames received.";;** + +**REGISTERED AS            { m3641Attribute 21 };** + +### **5.22    Number of timer 303 expiries** + +**noOfT303Expiries    ATTRIBUTE** + +**DERIVED FROM "Recommendation X.721 : 1992":counter;** + +#### **BEHAVIOUR** + +**noOfT303ExpiriesBehaviour    BEHAVIOUR** + +**DEFINED AS "This attribute represents the number of expiries of T303. The counter is raised after the second expiry. This implies that the user did not respond after a SETUP was sent to the user on a point-to-point link.";;** + +**REGISTERED AS { m3641Attribute 22 };** + +### **5.23    Number of timer 310 expiries** + +**noOfT310Expiries    ATTRIBUTE** + +**DERIVED FROM "Recommendation X.721 : 1992":counter;** + +#### **BEHAVIOUR** + +**noOfT310ExpiriesBehaviour    BEHAVIOUR** + +**DEFINED AS "This attribute represents the number of expiries of T310. T310 expires after receipt of a CALL PROCEEDING, no response has reached the network.";;** + +**REGISTERED AS { m3641Attribute 23 };** + +### **5.24    Oldest record age** + +**oldestRecordAge    ATTRIBUTE** + +**WITH ATTRIBUTE SYNTAX            ASN1TypeModule.OldestRecordAge +MATCHES FOR                            EQUALITY, ORDERING;** + +#### **BEHAVIOUR** + +**oldestRecordAgeBehaviour            BEHAVIOUR** + +**DEFINED AS "This attribute represents the time when the notification oldestRecordLessThanLimit will be emitted by object dChannelLog.";;** + +**REGISTERED AS { m3641Attribute 24 };** + +### 5.25 Other special message + +otherSpecialMessage ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.OtherSpecialMessage; +MATCHES FOR EQUALITY; +BEHAVIOUR +otherSpecialMessageAttrBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the specific error information that is stored in the +otherSpecialMessageLogRecord.";; +REGISTERED AS { m3641Attribute 25 }; + +### 5.26 Received + +received ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Received; +MATCHES FOR EQUALITY; +BEHAVIOUR +receivedBehaviour BEHAVIOUR +DEFINED AS +"This attribute indicates whether a message was received or not, i.e. sent.";; +REGISTERED AS { m3641Attribute 26 }; + +### 5.27 Relating To Active Call + +relatingToActiveCall ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.RelatingToActiveCall; +MATCHES FOR EQUALITY; +BEHAVIOUR +relatingToActiveCallBehaviour BEHAVIOUR +DEFINED AS +"This attribute indicates whether a call reference relates to an active call.";; +REGISTERED AS { m3641Attribute 27 }; + +### 5.28 Restart messages received + +rRESTARTMessagesReceived ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +rRESTARTMessagesReceivedBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the number of RESTART messages received.";; +REGISTERED AS { m3641Attribute 28 }; + +### 5.29 Restart messages transmitted + +rRESTARTMessagesTransmitted ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +rRESTARTMessagesTransmittedBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the number of RESTART messages transmitted.";; +REGISTERED AS { m3641Attribute 29 }; + +### 5.30 Special message type + +specialMessageType ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.SpecialMessageType; +MATCHES FOR EQUALITY; +BEHAVIOUR +specialMessageTypeAttrBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the specific error information that is stored in the +specialMessageTypeLogRecord";; +REGISTERED AS { m3641Attribute 30 }; + +### 5.31 Status messages received + +sSTATUSMessagesReceived ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +sSTATUSMessagesReceivedBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the number of STATUS messages received.";; +REGISTERED AS { m3641Attribute 31 }; + +### 5.32 Status messages transmitted + +sSTATUSMessagesTransmitted ATTRIBUTE +DERIVED FROM "Recommendation X.721 : 1992":counter; +BEHAVIOUR +sSTATUSMessagesTransmittedBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the number of STATUS messages transmitted.";; +REGISTERED AS { m3641Attribute 32 }; + +### 5.33 TEI value + +tEIValue ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.TEIValue; +MATCHES FOR EQUALITY; +BEHAVIOUR +tEIValueBehaviour BEHAVIOUR +DEFINED AS +"This attribute represents the TEI Value of the terminal involved.";; +REGISTERED AS { m3641Attribute 33 }; + +### 5.34 Timer expiry network + +timerExpiryNetwork ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.TimerExpiryNetwork; +MATCHES FOR EQUALITY; +BEHAVIOUR +timerExpiryNetworkAttrBehaviour BEHAVIOUR +DEFINED AS "This attribute represents the specific error information that is stored in the +timerExpiryNetworkLogRecord.";; +REGISTERED AS { m3641Attribute 34 }; + +### 5.35 Type Of Error Frame + +typeOfErrorFrame ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.TypeOfErrorFrame; +MATCHES FOR EQUALITY; +BEHAVIOUR +typeOfErrorFrameBehaviour BEHAVIOUR +DEFINED AS +"This attribute represents the type of error when a frame error was detected.";; +REGISTERED AS { m3641Attribute 35 }; + +### 5.36 Type Of Timer + +typeOfTimer ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.TypeOfTimer; +MATCHES FOR EQUALITY; +BEHAVIOUR +typeOfTimerBehaviour BEHAVIOUR + +DEFINED AS + +"This attribute represents the type of the timer expired.";; + +REGISTERED AS { m3641Attribute 36 }; + +### 5.37 Unexpected frames + +unexpectedFrames ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1TypeModule.UnexpectedFrames; + +MATCHES FOR EQUALITY; + +BEHAVIOUR + +unexpectedFramesAttrBehaviour BEHAVIOUR + +DEFINED AS "This attribute represents the specific error information that is stored in the unexpectedFramesLogRecord.";; + +REGISTERED AS { m3641Attribute 37 }; + +## 6 Notifications + +### 6.1 Error frames + +errorFrames NOTIFICATION + +BEHAVIOUR + +errorFramesBehaviour BEHAVIOUR + +DEFINED AS + +"This notification is issued when a protocol error is detected. It will contain one of the following messages: + +- The frames received with a control field that is undefined or not implemented: framesWithBadControlfield. +- The frames received with an information field that is not permitted: framesWithBadInfoField. +- The supervisory frames with incorrect length: supervisoryFramesWithBadLength. +- The unnumbered frames with incorrect length: unnumberedFramesBadLength. +- The frames received with an invalid receive sequence number (i.e. invalid N(R)) framesWithInvalidReceiveSeqNumber. +- The frames received with an information field that exceeds the maximum established length. A parameter is defined for the maximum established length. The default value is 260 octets: framesWithInfoFieldTooLong. +- The Frame Reject (FRMR) frames received: fRMReceived. +- The Disconnect Mode (DM) frames received in response to a Set Asynchronous Balanced Mode Extended (SABME) frame: dMFramesSentInResponseToSABME. +- The proper responses (i.e. unnumbered acknowledgement or disconnect mode frames not received to establish or restore the link after N200 SABME frames were sent: notProperResponseAfterN200SABMEs. +- The Disconnect Mode (DM) frames received in response to a Set Asynchronous Balanced Mode Extended (SABME) frame: dMFramesReceivedInResponseToSABME. + +It also contains the TEI value to identify the terminal involved.";; + +WITH INFORMATION SYNTAX ASN1TypeModule.ErrorFrames + +AND ATTRIBUTE IDS + +tEIValue tEIValue, + +typeOfErrorFrame typeOfErrorFrame; + +REGISTERED AS { m3641Notification 1 }; + +### 6.2 Invalid frames + +invalidFrames NOTIFICATION + +BEHAVIOUR + +invalidFramesBehaviour BEHAVIOUR + +DEFINED AS + +"This notification is emitted on receipt of an invalid frame. The notification contains the invalid frame. An invalid frame is a frame with any of the following: + +- is not properly bounded by two flags; +- has fewer than six octets between flags of frames that contain sequence numbers and fewer than five octets between flags of frames that do not contain sequence numbers; +- does not consist of an integral number of octets prior to zero bit insertion or following zero bit extraction; + +- contains a single address field; + - contains a service access point identifier, which is not supported by the receiver. +- ";; + +WITH INFORMATION SYNTAX ASN1TypeModule.InvalidFrames; + +REGISTERED AS { m3641Notification 2 }; + +### 6.3 Message call reference error + +**messageCallRefError NOTIFICATION** + +**BEHAVIOUR** + +**messageCallRefErrorBehaviour BEHAVIOUR** + +**DEFINED AS** + +"This notification is issued when a message with a call reference error was detected. A call reference is used to specify a call. In the following situations, the call reference error is not correct: + +| Messages | Call reference value | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| All messages except: SETUP, STATUS, RESUME | Which is not relating to an active call or a call in progress | +| SETUP, RESUME | Which is not relating to an active call or a call in progress and with a call reference flag set to "1" | +| SETUP | Which is relating to an active call or a call in progress | +| All messages except: RESTART, RESTART ACK, STATUS | Which is the global call reference | + +It also contains the TEI value to identify the terminal involved."; + +WITH INFORMATION SYNTAX ASN1TypeModule.MessageCallRefError + +AND ATTRIBUTE IDS + +| | | +|-----------------------------|------------------------------| +| messageType | messageType, | +| relatingToActiveCall | relatingToActiveCall, | +| callReferenceFlag | callReferenceFlag, | +| callReferenceValue | callReferenceValue, | +| tEIValue | tEIValue; | + +REGISTERED AS { m3641Notification 3 }; + +### 6.4 Oldest record less than limit + +**oldestRecordLessThanLimit NOTIFICATION** + +**BEHAVIOUR** + +**oldestRecordLessThanLimitBehaviour BEHAVIOUR** + +**DEFINED AS** + +"This notification is emitted when the oldest record in the full D-Channel Log is less old than the value indicated by attribute oldestRecordAge of object dChannelLog."; + +WITH INFORMATION SYNTAX ASN1TypeModule.OldestRecordLessThanLimit; + +REGISTERED AS { m3641Notification 4 }; + +### 6.5 Other special message + +**otherSpecialMessage NOTIFICATION** + +**BEHAVIOUR** + +**otherSpecialMessageBehaviour BEHAVIOUR** + +**DEFINED AS** + +"This notification is issued upon the receipt or transmission of a STATUS or RESTART message. The notification contains the information whether the message was received or transmitted and the message concerned. It also contains the TEI value to identify the terminal involved. In case of a STATUS message, it also contains the contents of the cause field. The cause field contains the octets three to five as defined in Recommendation Q.931. This includes the cause value, location and the diagnostic field."; + +WITH INFORMATION SYNTAX ASN1TypeModule.OtherSpecialMessage + +AND ATTRIBUTE IDS + +``` + +messageType messageType, +received received, +tEIValue tEIValue, +causeValue causeValue; + +``` + +REGISTERED AS { m3641Notification 5 }; + +### 6.6 Special message type + +specialMessageType NOTIFICATION + +BEHAVIOUR + +specialMessageTypeBehaviour BEHAVIOUR + +DEFINED AS + +"This notification is issued upon the receipt or transmission of a DISCONNECT, RELEASE and RELEASE COMPLETE message. This notification is only issued when the cause value indicates an other than normal event. The notification contains the information whether the message was received or transmitted and the message concerned. It also contains the TEI value to identify the terminal involved. It also contains the contents of the cause field. The cause field contains the octets three to five as defined in Recommendation Q.931. This includes the cause value, location and the diagnostic field."; + +WITH INFORMATION SYNTAX ASN1TypeModule.SpecialMessageType + +AND ATTRIBUTE IDS + +``` + +messageType messageType, +received received, +tEIValue tEIValue, +causeValue causeValue; + +``` + +REGISTERED AS { m3641Notification 6 }; + +### 6.7 Timer expiry network + +timerExpiryNetwork NOTIFICATION + +BEHAVIOUR + +timerExpiryNetworkBehaviour BEHAVIOUR + +DEFINED AS + +"This notification is issued upon expiry of timers: + +T308: A DISCONNECT was received from the user. The network answers with a RELEASE. T308 expires when no answer was received from the user after that. After the second expiry the B-channel will be placed in a maintenance condition. + +T309: The data link failure has not been recovered from a data link layer malfunction. + +T316: No RESTART ACKNOWLEDGE was received after a RESTART was transmitted. After "n" expiries the Operations System shall be notified. + +T317: After a RESTART was received, the restart procedure did not work. It also contains the TEI value to identify the terminal involved."; + +WITH INFORMATION SYNTAX ASN1TypeModule.TimerExpiryNetwork + +AND ATTRIBUTE IDS + +``` + +tEIValue tEIValue, +typeOfTimer typeOfTimer; + +``` + +REGISTERED AS { m3641Notification 7 }; + +### 6.8 Unexpected frames + +unexpectedFrames NOTIFICATION + +BEHAVIOUR + +unexpectedFramesBehaviour BEHAVIOUR + +DEFINED AS + +"This notification is emitted on receipt of an unexpected frame. The notification contains the unexpected frame. In Table 9/Q.921, an overview of unexpected frames is given. It also contains the TEI value to identify the terminal involved."; + +WITH INFORMATION SYNTAX ASN1TypeModule.UnexpectedFrames + +AND ATTRIBUTE IDS + +``` + +frameType frameType, +dataLinkState dataLinkState, +tEIValue tEIValue; + +``` + +REGISTERED AS { m3641Notification 8 }; + +## 7 ASN.1 Type definitions module + +This clause contains the abstract syntax in ASN.1 [10] for the management information defined in this Recommendation. + +ASN1TypeModule { itu(0) recommendation(0) m(13) m3641(3641) informationModel(0) asn1Module(2) asn1TypeModule(0) } + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN + +-- EXPORTS *everything* + +IMPORTS + +NameType FROM ASN1DefinedTypeModule { itu(0) recommendation(0) m(13) gnm(3100) informationModel(0) + +asn1Module(2) asn1DefinedTypesModule(0)}; + +m3641InformationModel OBJECT IDENTIFIER ::= { itu(0) recommendation(0) m(13) m3641(3641) informationModel(0) } + +m3641StandardSpecificExtension OBJECT IDENTIFIER ::= { m3641InformationModel standardSpecificExtension (0) } + +m3641ManagedObjectClass OBJECT IDENTIFIER ::= { m3641InformationModel managedObjectClass (3) } + +m3641Package OBJECT IDENTIFIER ::= { m3641InformationModel package(4) } + +m3641NameBinding OBJECT IDENTIFIER ::= { m3641InformationModel nameBinding (6) } + +m3641Attribute OBJECT IDENTIFIER ::= { m3641InformationModel attribute (7) } + +m3641Notification OBJECT IDENTIFIER ::= { m3641InformationModel notification (10) } + +defaultZero DefaultZero ::= 0 + +CallReferenceFlag ::= INTEGER + +CallReferenceValue ::= INTEGER + +CauseType ::= OCTETSTRING + +-- *The causeType contains the octets three to five as defined in Recommendation Q.931.* + +-- *This includes the cause value, location and the diagnostic field.* + +DataLinkState ::= ENUMERATED { + +waitingEstablishment (1), + +waitingRelease (2), + +multipleFrameEstablishedMode (3), + +multipleFrameTimeRecoveryMode (4), + +tEIAssigned (5), + +tEIUnassigned (6) } + +DefaultZero ::= INTEGER + +ErrorFrames ::= SEQUENCE { + +tEIValue TEIValue, + +typeOfErrorFrame TypeOfErrorFrame } + +FrameType ::= ENUMERATED { + +dISC (1), + +dM (2), + +fRMR (3), + +i (4), + +rEJ (5), + +rNR (6), + +rR (7), + +sABME (8), + +uA (9), + +uI (10), + +xID (11) } + +InvalidFrames ::= BITSTRING + +MessageCallRefError ::= SEQUENCE { + +messageType MessageType, + +relatingToActiveCall RelatingToActiveCall, + +callReferenceFlag CallReferenceFlag, + +callReferenceValue CallReferenceValue, + +tEIValue TEIValue } + +MessageType ::= ENUMERATED { + +aLERTING (1), + +cALLpROCEEDING (2), + +cONGESTIONcONTROL (3), + +cONNECT (4), + +cONNECTaCKNOWLEDGE (5), + +dISCONNECT (6), + +fACILITY (7), + iNFORMATION (8), + nOTIFY (9), + pROGRESS (10), + rELEASE (11), + rELEASEcOMplete (12), + rESTART (13), + rESUME (14), + rESUMEaCKNOWLEDGE (15), + rESUMErEJECT (16), + sETUP (17), + sETUPaCKNOWLEDGE (18), + sTATUS (19), + sTATUSeNQUIRY (20), + sUSPEND (21), + sUSPENDaCKNOWLEDGE (22), + sUSPENDrEJECT (23), + uSERiNFORMATION (24) } + +OtherSpecialMessage ::= SEQUENCE { + messageType MessageTyp, + received Received, + tEIValue TEIValue, + causeValue CauseType OPTIONAL } + +OldestRecordAge ::= GeneralizedTime + +OldestRecordLessThanLimit ::= BOOLEAN + +Received ::= BOOLEAN + +RelatingToActiveCall ::= BOOLEAN + +SpecialMessageType ::= SEQUENCE { + messageType MessageTyp, + received Received, + tEIValue TEIValue, + causeValue CauseType } + +TEIValue ::= INTEGER + +TimerExpiryNetwork ::= SEQUENCE { + tEIValue TEIValue, + typeOfTimer TypeOfTimer } + +TypeOfErrorFrame ::= ENUMERATED { + framesWithBadInfoField (1), + framesWithBadControlField (2), + supervisoryFramesWithBadLength (3), + unnumberedFramesBadLength (4), + framesWithInvalidReceiveSeqNumber (5), + framesWithInfoFieldTooLong (6), + fRMRRReceived (7), + dMFramesSentInResponseToSABME (8), + notProperResponseAfterN200SABMEs (9), + dMFramesReceivedInResponseToSABME (10)} + +TypeOfTimer ::= ENUMERATED { + t308 (0), + t309 (1), + t316 (2), + t317 (3) } + +UnexpectedFrames ::= SEQUENCE { + frameType FrameType, + dataLinkState DataLinkState, + tEIValue TEIValue } + +END + +## 8 Support objects from other ITU-T Recommendations + +The following support object classes (or their subclasses) should be used to support the ISDN D-channel performance and fault management functions specified in this Recommendation: + +- eventForwardingDiscriminator (defined in Recommendation X.721 [4]); +- eventLogRecord (defined in Recommendation X.721 [4]); +- thresholdData (defined in Recommendation Q.822 [2]); +- log (defined in Recommendation X.721 [4]). + +The following system management functions define management capabilities which are used in the management information model of the data link and network layer: + +- Object management function [11]; +- State management function [12]; +- Alarm reporting function [13]; +- Event report management function [14]; +- Log control function [15]; +- Summarization function [7]; +- Metric Objects and Attributes [16]. + +## 9 Functional unit + +### 9.1 Definition of the fpmMonitorDchannel functional unit + +One functional unit is defined in this Recommendation for the management of fault and performance monitor object classes: + +- fpmMonitorDchannel functional unit - This functional unit supports the following seven specific Event Reporting Services: + - Error Frames Reporting Service; + - Invalid Frames Reporting Service; + - Message with call reference error Reporting Service; + - Special Message Reporting Service; + - Other Special Message Reporting Service; + - Timer Expiry Reporting Service; + - Unexpected Frames Reporting Service. + +It requires support of the pmMonitor and pmControl functional units defined in Recommendation Q.822 [2]. + +To provide the mapping between the parameters for the event report (result of the notification) and CMIS M-EVENT-REPORT [3], [9], the seven specific Event Reporting Services are defined as follows. + +The Error, Invalid, Unexpected Frames Reporting Service, Timer Expiry, Message with call reference error, Special Message or Other Special Message Reporting Service allow a managed system to report that a protocol error, timer expiry or special message is detected. + +Table 1 contains the parameters for these specific Event Reporting Services. The Event Information parameter will indicate which Event Reporting Service is invoked (in this example the Error Frames Reporting Service). + +TABLE 1/M.3641 + +#### **D-channel specific Event Reporting Service Parameters in case of errorFrames Event Type** + +| Parameter Name | REQ/IND | RSP/CNF | +|-------------------------|---------|---------| +| Invoke Identifier | P | P | +| Mode | P | – | +| Managed Object Class | P | P | +| Managed Object Instance | P | P | +| Event Type | M | C(=) | +| Event Time | P | – | +| Event Information | | | +| ErrorFrames | M | – | +| Current Time | – | P | +| Event reply | – | C | +| Errors | – | P | + +NOTE – The meaning of the symbols “M”, “C” and “(=)” used in this table are the same as used in the tables for the CMISE description [3]. The symbol “P” means “subject to the constraints imposed on the parameter by Rec. X.710 | ISO/IEC 9595”. + +The following parameters are defined for use in the specific Event Reporting Services: + +- Invoke Identifier: see Invoke Identifier [3]. +- Mode: see Mode [3]. The values for this parameter are either confirmed or unconfirmed. +- Managed Object Class: see Managed Object Class [3]. This parameter shall indicate the mgdDataLinkDChannel or mgdNetwLayerDChannel object class. +- Managed Object Instance: see Managed Object Instance [3]. +- Event Type: This parameter specifies the type of event being reported and the value shall be as indicated by Table 2. + +TABLE 2/M.3641 + +##### **Event Type values for the D-channel specific Event Reporting Services** + +| Event reporting service | Event type value | +|-----------------------------------|---------------------| +| Error Frames | errorFrames | +| Invalid Frames | invalidFrames | +| Unexpected Frames | unexpectedFrames | +| Timer Expiry | timerExpiryNetwork | +| Message with call reference error | messageCallRefError | +| Special Message | specialMessageType | +| Other Special Message | otherSpecialMessage | + +The Event Type parameter may be included in the response if the Event Reply parameter is present in the response. + +- Event Time: see Event Time [3]. +- Event Information: see Event Information [3]. This parameter contains a sub-parameter which depends on the Event Type parameter. The sub-parameter specifies the following information as indicated by Table 3. +- Current Time: see Current Time [3]. +- Event Reply: see Event Reply [3]. The inclusion of this parameter in the response is conditional upon the successful receipt of the event report in the confirmed mode. +- Errors: see Errors [3]. This parameter shall be included in a failure confirmation. + +TABLE 3/M.3641 + +#### **Information included in Event Information Subparameters** + +| Sub-parameter Name | Information | +|---------------------|---------------------------------------------------------------------------------------------------| +| ErrorFrames | TEI value, type of error frame received | +| InvalidFrames | Incorrectness of frame received | +| UnexpectedFrames | Type of frame, datalink state, TEI value | +| TimerExpiryNetwork | TEI value, type of timer | +| MessageCallRefError | Message type, indication whether call was active or not, call reference flag and value, TEI value | +| SpecialMessageType | Message type, special message was sent or received, TEI value, cause value | +| OtherSpecialMessage | Message type, special message was sent or received, TEI value, cause value | + +### 9.2 Negotiation of the fpmMonitorDchannel functional unit + +This Recommendation assigns the following object identifier value + +{ itu(0) recommendation (0) m(13) m3641(3641) functionalUnitPackage(1) } as a value for the ASN.1 type FunctionalUnitPackageID defined in Rec. X.701 | ISO/IEC 10040 [17] to use for negotiation the following functional unit: + +0 fpmMonitorDchannel + +where the number (0) identifies the bit position in the BITSTRING assigned to the functional unit. + +In addition, the functional units identified in Recommendation Q.822 [2] are to be used in order to monitor and control the objects defined in this Recommendation. + +The mechanism for negotiating the functional units is described in X.701 | ISO/IEC 10040 [17]. + +## 10 Conformance + +A system claiming conformance to this Recommendation shall comply to the general static and dynamic conformance statements as included in Recommendation Q.822 [2]. In addition, the system shall comply to the conformance statements of Recommendation Q.822 [2] which address conformance to support managed object definitions. Finally, the system shall comply to the following ISDN D-channel specific conformance statement: + +The system shall: + +- support the role of manager or agent or both, with respect to the fpmMonitorDchannel functional unit defined in this Recommendation; +- For each dChannel managed object it should be possible to instantiate exactly one instance of the mgdDataLinkDChannel and mgdNetwLayerDChannel object. +- For each mgdDataLinkDChannel and mgdNetwLayerDChannel managed object it should be possible to instantiate at least one instance of the mgdDataLinkCurrentData or mgdNetwLayerCurrentData object. + +## 11 References + +- [1] CCITT Recommendation M.3640, *Management of the D-channel – Data link and network layer.* +- [2] ITU-T Recommendation Q.822: COM11\R\R002EV2, *Stage 1, stage 2 and stage 3 description for the Q3 interface – Performance management.* +- [3] CCITT Recommendation X.710, *Common management information service definition for CCITT applications.* +- [4] CCITT Recommendation X.721, *Definition of management information.* +- [5] CCITT Recommendation X.722, *Guidelines for the definition of managed objects.* +- [6] CCITT Recommendation M.3100, *Generic network information model.* +- [7] ITU-T Recommendation X.738, *Summarization function.* +- [8] CCITT Recommendation M.3010, *Principles for a telecommunication management network.* +- [9] CCITT Recommendation X.711, *Common management information protocol specification for CCITT applications.* +- [10] CCITT Recommendation X.208, *Specification of abstract syntax notation one (ASN.1).* +- [11] CCITT Recommendation X.730, *Object management function.* +- [12] CCITT Recommendation X.731, *State management function.* +- [13] CCITT Recommendation X.733, *Alarm reporting function.* +- [14] CCITT Recommendation X.734, *Event report management function.* +- [15] CCITT Recommendation X.735, *Log control function.* +- [16] ITU-T Recommendation X.739, *Metric objects and attributes.* +- [17] CCITT Rec. X.701 | ISO/IEC 10040:1992, *Information technology – Open Systems Interconnection – Systems management overview.* \ No newline at end of file diff --git a/marked/M/T-REC-M.3650-199704-I_PDF-E/raw.md b/marked/M/T-REC-M.3650-199704-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..162b61988a4387406f2c1d93644fa6855c83f13c --- /dev/null +++ b/marked/M/T-REC-M.3650-199704-I_PDF-E/raw.md @@ -0,0 +1,3118 @@ + + +![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +ITU logo: A globe with a lightning bolt and the letters ITU. + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.3650** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(04/97) + +SERIES M: TMN AND NETWORK MAINTENANCE: +INTERNATIONAL TRANSMISSION SYSTEMS, +TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE +AND LEASED CIRCUITS + +Integrated services digital networks + +--- + +**Network performance measurements of ISDN +calls** + +ITU-T Recommendation M.3650 + +(Previously CCITT Recommendation) + +--- + +# ITU-T M-SERIES RECOMMENDATIONS + +## **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to ITU-T List of Recommendations.* + +## **ITU-T RECOMMENDATION M.3650** + +# **NETWORK PERFORMANCE MEASUREMENTS OF ISDN CALLS** + +###### **Source** + +ITU-T Recommendation M.3650 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 19th of April 1997. + +# FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## INTELLECTUAL PROPERTY RIGHTS + +The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 1997 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# CONTENTS + +###### Page + +| | | | +|-------|------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Abbreviations and definitions..... | 3 | +| 3.1 | Abbreviations..... | 3 | +| 3.2 | Definitions ..... | 3 | +| 4 | Principles for network performance measurements..... | 3 | +| 5 | Network performance parameters..... | 4 | +| 5.1 | Access delay..... | 5 | +| 5.1.1 | Connection set-up delay ..... | 5 | +| 5.1.2 | Alerting delay ..... | 7 | +| 5.1.3 | Layer 1 activation delay..... | 10 | +| 5.1.4 | Layer 2 activation delay..... | 11 | +| 5.2 | Access accuracy..... | 11 | +| 5.3 | Access dependability..... | 11 | +| 5.4 | Information transfer time ..... | 13 | +| 5.5 | Information transfer accuracy..... | 13 | +| 5.6 | Information transfer dependability..... | 14 | +| 5.7 | Disengagement delay ..... | 15 | +| 5.8 | Disengagement accuracy..... | 16 | +| 5.9 | Disengagement dependability..... | 16 | +| 6 | Overview of measured parameters..... | 16 | +| 7 | Description of management information ..... | 17 | +| 8 | Management information model..... | 21 | +| 8.1 | Managed object classes..... | 21 | +| 8.1.1 | Call performance log ..... | 22 | +| 8.1.2 | Layer 1 performance log record..... | 22 | +| 8.1.3 | Layer 2 performance log record..... | 22 | +| 8.1.4 | Layer 3 performance log record..... | 23 | +| 8.1.5 | Monitored access ..... | 23 | +| 8.2 | Packages..... | 23 | +| 8.2.1 | Call performance log ..... | 23 | +| 8.2.2 | Layer 1 performance log record..... | 23 | +| 8.2.3 | Layer 1 performance notification..... | 24 | + +| | Page | +|---------------------------------------------------------|-------------| +| 8.2.4 Layer 2 performance log record..... | 24 | +| 8.2.5 Layer 2 performance notification..... | 24 | +| 8.2.6 Layer 3 access delay ..... | 24 | +| 8.2.7 Layer 3 access dependability ..... | 24 | +| 8.2.8 Layer 3 disengagement delay..... | 25 | +| 8.2.9 Layer 3 disengagement dependability..... | 25 | +| 8.2.10 Layer 3 information transfer dependability ..... | 25 | +| 8.2.11 Layer 3 information transfer time-package..... | 25 | +| 8.2.12 Layer 3 performance log record..... | 25 | +| 8.2.13 Layer 3 performance notification..... | 26 | +| 8.2.14 Monitored Access ..... | 26 | +| 8.3 Name bindings ..... | 26 | +| 8.3.1 callPerformanceLog-monitoredAccess..... | 26 | +| 8.3.2 monitoredAccess-accessPort ..... | 26 | +| 8.3.3 monitoredAccess-dChannel..... | 27 | +| 8.4 Attributes ..... | 27 | +| 8.4.1 Called number..... | 27 | +| 8.4.2 Called subaddress ..... | 27 | +| 8.4.3 Calling number ..... | 27 | +| 8.4.4 Calling subaddress..... | 27 | +| 8.4.5 Information transfer capability ..... | 27 | +| 8.4.6 Information transfer mode ..... | 28 | +| 8.4.7 Information transfer rate..... | 28 | +| 8.4.8 Layer 1 access delay ..... | 28 | +| 8.4.9 Layer 1 access dependability ..... | 28 | +| 8.4.10 Layer 1 information transfer dependability ..... | 28 | +| 8.4.11 Layer 2 access delay ..... | 29 | +| 8.4.12 Layer 2 access dependability ..... | 29 | +| 8.4.13 Layer 3 access delay ..... | 29 | +| 8.4.14 Layer 3 access dependability ..... | 29 | +| 8.4.15 Layer 3 disengagement delay..... | 29 | +| 8.4.16 Layer 3 disengagement dependability..... | 29 | +| 8.4.17 Layer 3 information transfer dependability ..... | 30 | +| 8.4.18 Layer 3 information transfer time..... | 30 | +| 8.4.19 Monitored Access Id..... | 30 | +| 8.4.20 Type of call..... | 30 | +| 8.4.21 Types monitoring..... | 30 | + +| | Page | +|-------------------------------------------------------------------------------------------|-------------| +| 8.5 Actions ..... | 31 | +| 8.5.1 Start Monitoring ..... | 31 | +| 8.5.2 Stop Monitoring..... | 31 | +| 8.6 Notifications..... | 31 | +| 8.6.1 Layer 1 performance recorded..... | 31 | +| 8.6.2 Layer 2 performance recorded..... | 31 | +| 8.6.3 Layer 3 performance recorded..... | 32 | +| 8.7 ASN.1 Type definitions module ..... | 32 | +| 9 Support objects from other Recommendations..... | 35 | +| 10 Functional unit ..... | 35 | +| 10.1 Definition of functional units..... | 35 | +| 10.2 Negotiation of functional units ..... | 37 | +| 11 Conformance..... | 37 | +| Annex A – MCS and MOCS proforma..... | 38 | +| A.0 MCS proforma ..... | 38 | +| A.0.1 Introduction..... | 38 | +| A.0.2 Identification of the implementation ..... | 38 | +| A.0.3 Identification of the document in which the management information is defined ..... | 39 | +| A.0.4 Management conformance summary..... | 39 | +| A.1 MOCS proforma ..... | 41 | +| A.1.1 Introduction..... | 41 | +| A.1.2 CallPerformanceLog..... | 42 | +| A.2 layer1PerformanceLogRecord ..... | 54 | +| A.3 layer2PerformanceLogRecord ..... | 59 | +| A.4 layer3PerformanceLogRecord ..... | 64 | +| A.5 monitoredAccess..... | 70 | +| Annex B – Network management level ..... | 77 | + + + +# **NETWORK PERFORMANCE MEASUREMENTS OF ISDN CALLS** + +*(Geneva, 1997)* + +## **1 Scope** + +This Recommendation defines in-service measurements of ISDN calls and defines the related management information that shall be available at management interfaces of the ISDN local exchanges. This information can be used by the TMN for performance management activities. ISDN-specific in-service measurements are defined for several of the I.350 [4] parameters in order to provide the TMN with an approximation of the user perspective of these parameters. The TMN capabilities defined by this Recommendation will be applicable to all ISDN D-channels. Actual measurements will take place on a selectable subset of the available D-channels. + +This Recommendation has been developed to: + +- provide a network or service provider with a means to get information about the performance of ISDN calls as far as they are related to the customer access and public part of ISDN. + +This Recommendation will: + +- provide the network performance measurement service descriptions at the network element management layer of the TMN as defined in Recommendation M.3010 [6]; +- specify the management information model to support this network performance measurement service. This will be done in terms of managed object classes, packages, attributes, notifications, actions and behaviour, using the OSI management templates defined in X.722 as notation tool and using ASN.1 for type definitions. Reuse of OSI Management specifications in the X.700-series of Recommendations will be performed as much as possible. + +This Recommendation currently only defines measurements on separate calls. It gives no information on how to determine statistical results over several calls. + +This Recommendation only gives performance information on the selected D-channels. It should be used in conjunction with Recommendation M.3641, which provides information on all D-channels. Besides, this Recommendation is only involved with performance aspects of the public part of the network. For performance or fault information on the user side, M.3641 management information needs to be used. + +## **2 References** + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. + +- [1] ITU-T Recommendation E.800 (1994), *Terms and definitions related to quality of service and network performance including dependability*. + +- [2] CCITT Recommendation E.845 (1988), *Connection accessibility objective for the international telephone service.* +- [3] ITU-T Recommendation G.960 (1993), *Access digital section for ISDN basic rate access.* +- [4] ITU-T Recommendation I.350 (1993), *General aspects of quality of service and network performance in digital networks, including ISDNs.* +- [5] ITU-T Recommendation I.352 (1993), *Network performance objectives for connection processing delays in an ISDN.* +- [6] ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network.* +- [7] ITU-T Recommendation M.2100 (1995), *Performance limits for bringing-into-service and maintenance of international PDH paths, sections and transmission systems.* +- [8] ITU-T Recommendation M.3100 (1995), *Generic network information model.* +- [9] CCITT Recommendation M.3640 (1992), *Management of the D-channel – Data link layer and network layer.* +- [10] ITU-T Recommendation M.3641 (1994), *Management information model for the management of the data link and network layer of the ISDN D-channel.* +- [11] ITU-T Recommendation Q.764 (1993), *ISDN user part signalling procedures.* +- [12] ITU-T Recommendation Q.824.0 (1995), *Stage 2 and stage 3 description for the Q3 interface – Customer administration: Common information.* +- [13] ITU-T Recommendation Q.824.1 (1995), *Stage 2 and stage 3 description for the Q3 interface – Customer administration: Integrated Services Digital Network (ISDN) basic and primary rate access.* +- [14] ITU-T Recommendation Q.850 (1993), *Usage of cause and location in the digital subscriber Signalling System No. 1 and in the Signalling System No. 7 ISDN user part.* +- [15] CCITT Recommendation X.701 (1992) | ISO/IEC 10040:1992, *Information technology – Open Systems Interconnection – Systems management overview.* +- [16] CCITT Recommendation X.710 (1991), *Common management information service definition for CCITT applications.* +- [17] CCITT Recommendation X.711 (1991), *Common management information protocol specification for CCITT applications.* +- [18] CCITT Recommendation X.721 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.* +- [19] CCITT Recommendation X.722 (1992), *Information technology – Open Systems Interconnection – Structure of management information: Guidelines for the definition of managed objects.* +- [20] CCITT Recommendation X.734 (1992), *Information technology – Open Systems Interconnection – Systems management: Event report management function.* +- [21] CCITT Recommendation X.735 (1992), *Information technology – Open Systems Interconnection – Systems management: Log control function.* +- [22] ITU-T Recommendation X.739 (1993), *Information technology – Open Systems Interconnection – Systems management: Metric objects and attributes.* + +# 3 Abbreviations and definitions + +## 3.1 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-------|-----------------------------------------| +| DS | Digital Section | +| ET | Exchange Termination | +| FE | Function Element | +| ISUP | ISDN User Part | +| LEX | Local EXchange | +| LPN | Private Network serving the Local user | +| LT | Line Termination | +| MPI | Measurement Point International | +| MPT | Measurement Point T interface | +| NT | Network Termination | +| OSF | Operations System Function | +| RPN | Private Network serving the Remote user | +| SABME | Set Asynchronous Balanced Mode Extended | +| TE | Terminal Equipment | +| TEX | Transit EXchange | +| U | User | +| UA | Unnumbered Acknowledgement | + +## 3.2 Definitions + +This Recommendation defines the following terms: + +**3.2.1 incoming call:** Call set-up from the network to the user and thus incoming to the user. + +**3.2.2 outgoing call:** Call set-up from the user to the network and thus outgoing from the user. + +# 4 Principles for network performance measurements + +Network performance measurements have to be performed at the ISDN local exchanges (LEXs). Measurements may be performed both for outgoing calls as well as incoming calls. An architectural overview is presented in Figure 1. + +![Figure 1/M.3650 – TMN functional architecture for performance measurements of ISDN calls. The diagram shows a sequence of components: TE/NT2, NT1/LT, ET (labeled LEX), TEX, TEX, ET (labeled LEX), LT/NT1, and NT2/TE. Above each ET (LEX) is an OSF connected via a q3 interface. A double-headed arrow labeled 'Network Operator Domain' spans across the TEX components.](d4af765160d04ecef538e5066006dc77_img.jpg) + +The diagram illustrates the TMN functional architecture for ISDN call performance measurements. It shows a chain of components: TE/NT2 connected to NT1/LT, which is connected to an ET (labeled LEX). Above this ET is an OSF connected via a q3 interface. The ET is connected to a TEX, which is connected to another TEX. The second TEX is connected to another ET (labeled LEX), which also has an OSF connected via a q3 interface. This second ET is connected to LT/NT1, which is connected to NT2/TE. A double-headed arrow labeled 'Network Operator Domain' spans across the two TEX components. + +Figure 1/M.3650 – TMN functional architecture for performance measurements of ISDN calls. The diagram shows a sequence of components: TE/NT2, NT1/LT, ET (labeled LEX), TEX, TEX, ET (labeled LEX), LT/NT1, and NT2/TE. Above each ET (LEX) is an OSF connected via a q3 interface. A double-headed arrow labeled 'Network Operator Domain' spans across the TEX components. + +T0406490-96 + +**Figure 1/M.3650 – TMN functional architecture for performance measurements of ISDN calls** + +At the Network Management level, information from several LEXs may be gathered. This Recommendation does not define how information from originating and destination LEXs can be related to a single call at the Network Management level. For more information, see Annex B. + +It shall be possible to perform performance measurements of ISDN calls on selected D-channels. Measuring a specific D-channel can be activated or deactivated. Finer filtering mechanisms can be implemented in an OSF and are therefore outside the scope of this Recommendation. + +The performance of an ISDN call has to be expressed by parameters. For this purpose this Recommendation will use the definitions of the I.350-Series. Recommendation I.352 involves connection processing delays. It defines two Measurement Points at which protocol events (e.g. transfer of a message) are detected: MPT at the T interface and MPI at the international border. At the MPTs, the end-to-end network performance between two T interfaces can be measured. This is on the boundary of the network of the operator. + +In the context of this Recommendation, a TMN needs to obtain management information to determine the performance of ISDN calls. This involves information about real traffic, using information from *within* the network of the operators. Arrival times of messages at the T interface cannot be extracted from a LEX, since the T interface is not directly accessible by a LEX. In the case of this Recommendation, arrival times of layer 2 and layer 3 messages at the Exchange Termination (ET) in a LEX are measured. In this way a service or network provider obtains a close approximation of the connection processing delays as defined in Recommendation I.352. It is noteworthy that an even closer approximation is possible when the transmission times between the T interfaces and LEXs are deduced on the basis of the length of the access line. These transmission times could also be deduced from loopback tests. + +Measurements at a LEX are required both at the D-channel protocols and at the SS No. 7 ISUP protocol, see [7]. + +# 5 Network performance parameters + +In Recommendation I.350, a list of generic parameters is given which can be used to derive specific parameters and required measurements. The derivation is done by applying the following three aspects for each of the three communication functions: *access*, *information transfer* and *disengagement*. + +- 1) Delay +Delay describes the time interval that is used to perform the communication function. +- 2) Accuracy +Accuracy describes the degree of correctness with which the function is performed. +- 3) Dependability +Dependability describes the degree of certainty with which the function is performed, regardless of delay or accuracy. +This results in the following parameters: + - access delay1; + - access accuracy; + - access dependability; + - information transfer time2; + - information transfer accuracy; + - information transfer dependability; + - disengagement delay; + - disengagement accuracy; + - disengagement dependability. + +In the following subclauses, these generic parameters will be specifically defined for the purpose of performance measurements for ISDN calls. For each aspect, specific requirements for management information are recommended. + +### 5.1 Access delay + +Access delay is the time that is needed to establish a connection. Two types of access delay are distinguished: connection set-up delay and alerting delay. Connection set-up delay is the period that begins immediately after the user has completed the connection request and ends when the user experiences that the connection has been established. Alerting delay (applicable in case of manual answering terminals and some automatic answering terminals) is the period that begins immediately after the user has completed the connection request until the user experiences that the called user alerting has been initiated. + +Connection set-up delay and alerting delay are determined at the destination LEX for incoming calls because they might be used for correction of measured delays at the side of the originating LEX. Relating measurements at the incoming and outgoing exchanges could be part of a TMN application. + +### 5.1.1 Connection set-up delay + +Measurements at D-channel layer 3 at the originating and destination LEXs can be used for this purpose. + +The time periods for outgoing calls measured at the originating LEXs include the delay in the called user equipment as well as the delay caused by the called user itself. These delays can be measured at incoming calls at the destination LEXs. + +--- + +1 Instead of the term "speed" used in Recommendation I.350, the term "delay" is used, because delay is expressed in units of time. + +2 Instead of the term "speed" used in Recommendation I.350, the term "time" is used, because it is not the information transfer speed, but the information transfer time that is experienced by a user. + +![Sequence diagram for en-bloc sending and receiving. It shows two vertical timelines for 'Originating LEX' (Outgoing call) and 'Destination LEX' (Incoming call). The sequence of messages is: SETUP (from Originating to Destination), ALERTING (from Destination to Originating), CONNECT (from Destination to Originating), and CONNECT (from Originating to Destination). The diagram is labeled T0406500-96.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Sequence diagram for en-bloc sending and receiving. It shows two vertical timelines for 'Originating LEX' (Outgoing call) and 'Destination LEX' (Incoming call). The sequence of messages is: SETUP (from Originating to Destination), ALERTING (from Destination to Originating), CONNECT (from Destination to Originating), and CONNECT (from Originating to Destination). The diagram is labeled T0406500-96. + +**Figure 2/M.3650 – Connection set-up delays for en-bloc sending and receiving** + +In case of en-bloc sending, the period that has to be measured for outgoing calls is: + +- the time between a layer 3 SETUP message is received from the calling user at the originating LEX and the time that a layer 3 CONNECT message is sent from the originating LEX to the calling user. + +In case of en-bloc receiving, the period that has to be measured for incoming calls is: + +- the time between a layer 3 SETUP message is sent from the destination LEX to the called user and the time that a layer 3 CONNECT message is received at the destination LEX from the called user. + +![Sequence diagram for overlap sending and receiving. It shows two vertical timelines for 'Originating LEX' (Outgoing call) and 'Destination LEX' (Incoming call). The sequence of messages is: SETUP (from Originating to Destination), SETUP ACK (from Destination to Originating), Last INFORMATION (from Originating to Destination), SETUP (from Destination to Destination user), SETUP ACK (from Destination user to Destination), Last INFORMATION (from Destination user to Destination), ALERTING (from Destination to Originating), and CONNECT (from Originating to Destination). The diagram is labeled T0406510-96.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +Sequence diagram for overlap sending and receiving. It shows two vertical timelines for 'Originating LEX' (Outgoing call) and 'Destination LEX' (Incoming call). The sequence of messages is: SETUP (from Originating to Destination), SETUP ACK (from Destination to Originating), Last INFORMATION (from Originating to Destination), SETUP (from Destination to Destination user), SETUP ACK (from Destination user to Destination), Last INFORMATION (from Destination user to Destination), ALERTING (from Destination to Originating), and CONNECT (from Originating to Destination). The diagram is labeled T0406510-96. + +**Figure 3/M.3650 – Connection set-up delays for overlap sending and receiving** + +In case of overlap sending, the following time periods have to be measured and added up for outgoing calls: + +- the time between a layer 3 SETUP message is received from the calling user at the originating LEX and the time that a layer 3 SETUP ACKNOWLEDGE message is sent from the originating LEX to the calling user; +- the time between the *last* layer 3 INFORMATION message is received from the calling user at the originating LEX, and the time that a layer 3 CONNECT message is sent from the originating LEX to the calling user. For the time of the reception of the last INFORMATION frame, the time of the first event that occurs of the following events is taken: + - reception of an INFORMATION message with "sending complete indication" from the calling user at the originating LEX; + - sending a CALL PROCEEDING message from the originating LEX to the calling user. + +In case of overlap receiving, the following time periods have to be measured and added up for incoming calls: + +- the time between a layer 3 SETUP message is sent from the destination LEX to the called user and the time that a layer 3 SETUP ACKNOWLEDGE message is received at the destination LEX from the called user; +- the time between the last layer 3 INFORMATION message is sent from the destination LEX to the called user, and the time that a layer 3 CONNECT message is received at the destination LEX from the called user. For the time of the sending of the last INFORMATION frame, the time of the first event that occurs of the following events is taken: + - sending of an INFORMATION message with "sending complete indication" from the destination LEX to the called user; + - receiving a CALL PROCEEDING, ALERTING or CONNECT message at the destination LEX from the called user3. + +### 5.1.2 Alerting delay + +Measurements at D-channel layer 3 at the originating and destination LEXs can be used for this purpose. The time periods measured for outgoing calls at the originating LEX include the delay in the called user equipment but not the delay caused by the called user itself. The delay in the called user equipment can be measured at incoming calls at the destination LEXs. + +--- + +3 Note that the whole time interval may be 0 seconds if the reception of the CONNECT message is the first event that occurs. + +![Sequence diagram for en-bloc sending and receiving. It shows two vertical lines for 'Originating LEX' and 'Destination LEX'. On the left, 'Outgoing call' messages are shown: SETUP, ALERTING, and CONNECT. On the right, 'Incoming call' messages are shown: SETUP, ALERTING, and CONNECT. Arrows indicate the flow: SETUP from Originating to Destination; ALERTING from Destination to Originating; CONNECT from Destination to Originating. A label 'T0406520-96' is at the bottom right.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Sequence diagram for en-bloc sending and receiving. It shows two vertical lines for 'Originating LEX' and 'Destination LEX'. On the left, 'Outgoing call' messages are shown: SETUP, ALERTING, and CONNECT. On the right, 'Incoming call' messages are shown: SETUP, ALERTING, and CONNECT. Arrows indicate the flow: SETUP from Originating to Destination; ALERTING from Destination to Originating; CONNECT from Destination to Originating. A label 'T0406520-96' is at the bottom right. + +**Figure 4/M.3650 – Alerting delays for en-bloc sending and receiving** + +In case of en-bloc sending, the period that has to be measured for outgoing calls is: + +- the time between a layer 3 SETUP message is received from the calling user at the originating LEX and the time that a layer 3 ALERTING message is sent from the originating LEX to the calling user. + +In case of en-bloc receiving, the period that has to be measured for incoming calls is: + +- the time between a layer 3 SETUP message is sent from the destination LEX to the called user and the time that a layer 3 ALERTING message is received at the destination LEX from the called user. + +![Sequence diagram for overlap sending and receiving. It shows two vertical lines for 'Originating LEX' and 'Destination LEX'. On the left, 'Outgoing call' messages are shown: SETUP, SETUP ACK, and Last INFORMATION. On the right, 'Incoming call' messages are shown: SETUP, SETUP ACK, Last INFORMATION, ALERTING, and CONNECT. Arrows indicate the flow: SETUP from Originating to Destination; SETUP ACK from Destination to Originating; Last INFORMATION from Originating to Destination; ALERTING from Destination to Originating; CONNECT from Destination to Originating. A label 'T0406530-96' is at the bottom right.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +Sequence diagram for overlap sending and receiving. It shows two vertical lines for 'Originating LEX' and 'Destination LEX'. On the left, 'Outgoing call' messages are shown: SETUP, SETUP ACK, and Last INFORMATION. On the right, 'Incoming call' messages are shown: SETUP, SETUP ACK, Last INFORMATION, ALERTING, and CONNECT. Arrows indicate the flow: SETUP from Originating to Destination; SETUP ACK from Destination to Originating; Last INFORMATION from Originating to Destination; ALERTING from Destination to Originating; CONNECT from Destination to Originating. A label 'T0406530-96' is at the bottom right. + +**Figure 5/M.3650 – Alerting delays for overlap sending and receiving** + +In case of overlap sending, the following time periods have to be measured and added up for outgoing calls: + +- the time between a layer 3 SETUP message is received from the calling user at the originating LEX and the time that a layer 3 SETUP ACKNOWLEDGE message is sent from the originating LEX to the calling user; +- the time between the last layer 3 INFORMATION message is received from the calling user at the originating LEX, and the time that a layer 3 ALERTING message is sent from the originating LEX to the calling user. For the time of the reception of the last INFORMATION frame, the time of the first event that occurs of the following events is taken: + - reception of an INFORMATION message with "sending complete indication" from the calling user at the originating LEX; + - sending a CALL PROCEEDING message from the originating LEX to the calling user. + +In case of overlap receiving, the following time periods have to be measured and added up for incoming calls: + +- the time between a layer 3 SETUP message is sent from the destination LEX to the called user and the time that a layer 3 SETUP ACKNOWLEDGE message is received at the destination LEX from the called user; +- the time between the last layer 3 INFORMATION message is sent from the destination LEX to the called user, and the time that a layer 3 ALERTING message is received at the destination LEX from the called user. For the time of the sending of the last INFORMATION frame, the time of the first event that occurs of the following events is taken: + - sending of an INFORMATION message with "sending complete indication" from the destination LEX to the called user; + - receiving a CALL PROCEEDING or ALERTING message at the destination LEX from the called user4. + +--- + +4 Note that the whole time interval may be 0 seconds if the reception of the ALERTING message is the first event that occurs. + +### 5.1.3 Layer 1 activation delay + +![Diagram illustrating Layer 1 activation delay for outgoing and incoming calls between an Originating LEX and a Destination LEX.](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +The diagram illustrates the Layer 1 activation delay for outgoing and incoming calls between an Originating LEX and a Destination LEX. It is divided into two vertical sections: 'Outgoing call' on the left and 'Incoming call' on the right. + +**Outgoing call:** This section shows the sequence of events at the Originating LEX. A vertical line represents the LEX. Three horizontal arrows point from the LEX to the right, labeled FE2, FE3, and FE4 from top to bottom. FE2 is the first arrow, FE3 is the second, and FE4 is the third. Vertical double-headed arrows are shown between FE2 and FE3, and between FE3 and FE4, indicating the time intervals for activation delays. + +**Incoming call:** This section shows the sequence of events at the Destination LEX. A vertical line represents the LEX. Four horizontal arrows point from the right towards the LEX, labeled FE1, FE2, FE3, and FE4 from top to bottom. FE1 is the first arrow, FE2 is the second, FE3 is the third, and FE4 is the fourth. Vertical double-headed arrows are shown between FE1 and FE2, FE2 and FE3, and FE3 and FE4, indicating the time intervals for activation delays. + +Below the diagram, the text 'T0406540-96' is visible. The labels 'Originating LEX' and 'Destination LEX' are placed below their respective columns. + +Diagram illustrating Layer 1 activation delay for outgoing and incoming calls between an Originating LEX and a Destination LEX. + +**Figure 6/M.3650 – Layer 1 activation delay** + +From Recommendation G.960, it follows that for outgoing calls for the access activation delay at layer 1, the following times have to be measured: + +- Digital Section (DS) activation time: time from the moment the originating LEX has received FE2 from the direction of the calling user (access activation initiated) until it receives FE3 (Digital Section activated) from the direction of the calling user. Note that the reception of FE2 from the direction of the calling user is accompanied by the issuing of the MPH-AWI (AWake Indication) primitive and that the reception of FE3 from the direction of the calling user, is accompanied by the issuing of the MPH-DSAI (Digital Section Activate Indication) primitive. +- Terminal Equipment (TE) activation time: time from the moment the originating LEX has received FE3 (Digital Section activated) until it receives FE4 (user-network interface at the T reference point is activated or loopback is operated). Note that the reception of FE3 from the direction of the calling user is accompanied by the issuing of the MPH-DSAI (Digital Section Activate Indication) primitive and that the reception of FE4 from the direction of the calling user, is accompanied by the issuing of the MPH-AI (Activate Indication) primitive. + +For incoming calls, the following times have to be measured: + +- Digital Section activation time: time from the moment the destination LEX has issued FE1 (activate access) towards the direction of the called user until it receives FE3 (Digital Section activated) from the direction of the called user. Note that the issuing of FE1 towards the direction of the called user is accompanied by the issuing of the MPH-AR (Activate Request) primitive and that the reception of FE3 from the direction of the called user, is accompanied by the issuing of the MPH-DSAI (Digital Section Activate Indication) primitive. +- Terminal Equipment activation time: time from the moment the destination LEX has received FE3 (Digital Section activated) until it receives FE4 (user-network interface at the T reference point is activated or loopback is operated). Note that the reception of FE3 from the direction of the called user is accompanied by the issuing of the MPH-DSAI (Digital + +Section Activate Indication) primitive and that the reception of FE4 from the direction of the called user, is accompanied by the issuing of the MPH-AI (Activate Indication) primitive. + +The Digital Section activation time is determined by network equipment behaviour. The Terminal Equipment activation time is determined by terminal equipment behaviour. + +### 5.1.4 Layer 2 activation delay + +![Sequence diagram illustrating Layer 2 activation delay for outgoing and incoming calls between a calling user and an originating LEX, and a destination LEX and a called user.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates the Layer 2 activation delay for two call scenarios. On the left, for an 'Outgoing call', a horizontal arrow labeled 'SABME' points from the calling user to the 'Originating LEX', and a horizontal arrow labeled 'UA' points from the 'Originating LEX' back to the calling user. On the right, for an 'Incoming call', a horizontal arrow labeled 'SABME' points from the 'Destination LEX' to the called user, and a horizontal arrow labeled 'UA' points from the called user back to the 'Destination LEX'. The diagram is labeled 'T0406550-96' at the bottom right. + +Sequence diagram illustrating Layer 2 activation delay for outgoing and incoming calls between a calling user and an originating LEX, and a destination LEX and a called user. + +**Figure 7/M.3650 – Layer 2 activation delay** + +For the access delay for outgoing calls at layer 2, the following has to be measured: + +- the time between a SABME frame was received from the calling user at the originating LEX and the time a UA is sent from the originating LEX to the calling user. This time is determined by network equipment behaviour. + +For the access delay for incoming calls at layer 2, the following has to be measured: + +- the time between a SABME frame was issued from the destination LEX to the called user and the time a UA is sent from the called user to the destination LEX. This time is determined by terminal equipment behaviour. + +## 5.2 Access accuracy + +The access accuracy is covered by the dependability aspect. (As a service access function is considered to be either successful or not, a degree of correctness is not considered useful.) + +## 5.3 Access dependability + +In order to determine the access dependability, this Recommendation will measure whether a call set-up was successful or not. There is an unsuccessful connection establishment, when a connection establishment attempt does not result in the target connection, while the connection establishment was not interrupted by the calling party or called party or caused by a failure in their equipment. An access dependability parameter that could be derived is the "Connection failure probability". This parameter is defined in [2] as "Probability that a desired connection is not established due to a failure in the network". This is the ratio between unsuccessful calls and successful calls. + +An unsuccessful connection establishment can be: + +- a connection establishment to the wrong destination; +- an unwanted termination of the connection establishment. + +The connection establishment to a wrong destination will not be considered in this Recommendation, as very complex detection methods would be needed for probably a few number of failed connection establishments. + +When a connection establishment is unsuccessful due to a network failure, the reason has to be registered. With these reasons registered, an indication can be given what to improve to be able to increase the performance of the ISDN-access. + +For determination of the access dependability, only measurements are performed for outgoing calls. + +For the determination of unsuccessful connection establishments caused by a network failure, measurements of the D-channel layer 2 and layer 3 protocols at the customer access can give useful information. In the context of this Recommendation, call establishments are only considered unsuccessful if the location field in the cause information element indicates a location in the public network, i.e. the location is not at the user (U), at the private network that serves the local user (LPN) or at the private network that serves the remote user (RPN) (see Recommendation Q.850 [14]). In the following situations, there is an unsuccessful connection establishment, caused by a network failure: + +- A SETUP or INFORMATION message is received from the calling user at the originating LEX, that is responded by a RELEASE COMPLETE message with cause value No. 58 "*bearer capability not presently available*". +- After the originating LEX has received a SETUP or INFORMATION message from the calling user, no call is established because that message is not answered by a permitted response message from the originating LEX to the calling user. +- A call set-up is terminated by a RELEASE, RELEASE COMPLETE or DISCONNECT message containing cause value No. 38 "*network out of order*". +- Calls in the overlap sending mode are cleared when layer 3 is informed of a data link layer reset. In that case, a DISCONNECT message is sent with cause value No. 41 "*temporary failure*". +- A call is released (initiated by ISUP) with cause value No. 42 "*switching equipment congestion*". +- A call is released with cause value No. 97 "*message type non-existent or not implemented, discarded*" as a result of an unrecognizable ISUP message. +- A call is released with the cause value No. 99 "*parameter non-existent or not implemented, discarded*" as a result of an unrecognizable ISUP parameter. + +When performance monitoring of the access dependability according to this Recommendation is not supported, it may be possible to monitor the access dependability per call in an alternative way. The log records of Recommendation M.3641 [10] could be processed and the relevant information could be extracted. This processing can take place in the Operations System. It will be complicated to relate the M.3641 events to a single call. One needs accurate time stamps for the M.3650 access delay events. Using these time stamps, M.3641 events in call establishment phase can be selected, but accurate time stamps for the M.3641 events and time synchronization with the M.3650 events is required. + +The following ISUP events are indications for unsuccessful call set-ups: + +- Upon expiry of ISUP timer T7, no ISUP Address Complete Message or ISUP Connect message was received by the originating LEX after the latest address message was issued from the originating LEX. +- Upon expiry of ISUP timer T8, no ISUP Continuity message was received by the originating LEX after an ISUP Continuity Check request was issued from the originating LEX. + +Layer 1 and 2 errors may also result in an unsuccessful connection establishment. Layer 1 and layer 2 errors are only considered during the times that layer 3 does not exist yet. When layer 3 exists, it is assumed that unsuccessful connection establishments can be detected at layer 3. + +The following layer 1 event is an indication for unsuccessful call set-ups. At layer 1, it is not visible whether a call is setup, active or released. The only thing that makes sense is that a basic rate access may be activated when a call is setup. So, a failed basic rate access activation can be considered as an unsuccessful connection establishment: + +- After the originating LEX has received FE2 from the direction of the calling user (access activation initiated), it receives no FE3 (Digital Section activated) from the direction of the calling user. + +The following layer 2 event is an indication for unsuccessful call set-ups. Layer 2 may cause an unsuccessful connection establishment in the period between the sending of a SABME frame from the calling user to the originating LEX and the sending of a SETUP message from the calling user to the originating LEX: + +- A correct SABME frame, received at the originating LEX, is not responded by a UA frame, but is responded with a DM response with the F-bit set to the same binary value as the P-bit in the received SABME command. + +## 5.4 Information transfer time + +Information transfer time is the time that is needed to send user information through the network. This period is the time that elapsed from the moment that user information (via the D- or B-channel) is received at the originating LEX until it is issued from the destination LEX to the user at the other end. + +ISUP allows for determination of the propagation delay and for counting the number of satellite hops. In the ISUP connect message, the optional Call history information is returned which contains the propagation delay of the call. The propagation delay is determined by increasing a counter depending on the selected circuit. In ISUP also a hop counter has been defined for containing the number of satellite hops. + +## 5.5 Information transfer accuracy + +Information transfer accuracy is measured by the difference between the information that was offered to the LEX by one of the users and the information that was delivered by the peer LEX to the addressed user(s). + +In Recommendation M.2100 [7], a method is given for deriving information transfer accuracy parameters from in-service measurements. For network performance management, the following events have to be measured at layer 1, at the LEXs, transit exchanges and international exchanges: + +- Loss Of Signal (LOS); +- Loss Of Frame alignment (LOF); +- Cyclic Redundancy Check error (CRC-error); + +- Remote Alarm Indication (RAI); +- Alarm Indication Signal (AIS); +- Activation/deactivation failure. + +For in-service determination of the above-listed information transfer accuracy parameters and events by only measuring at the LEXs, no standardized solutions are available. Only methods for determining the transmission performance of single links (primary rate paths) are available, but not for determining the overall transmission accuracy of, for instance, 64-kbit/s end-to-end paths. + +Information transfer accuracy can be determined on a statistical base. However, that is out of the scope of this Recommendation. Note that the information transfer accuracy could be considered as satisfactory for all calls when all primary rate paths that are involved with an end-to-end path fulfil the requirements of Recommendation M.2100. + +## 5.6 Information transfer dependability + +In order to determine the information transfer dependability, this Recommendation will measure whether a call was prematurely released or not. Prematurely released calls are calls that are released for a reason other than intentionally by any of the parties involved in the call. An information transfer dependability parameter that could be derived is the "Premature release probability". This parameter is defined in [1] as "The probability that an established connection will be released, for a reason other than intentionally by one of the parties involved in the call". This is the ratio between prematurely released calls and successful calls. + +With respect to the information transfer dependability, the same measurements are performed at both outgoing and incoming calls. In the context of this Recommendation, calls are only considered prematurely released if the location field in the cause information element indicates a location in the public network, i.e. the location is not at the user (U), at the private network that serves the local user (LPN), or at the private network that serves the remote user (RPN) (see Recommendation Q.850 [14]). + +In the following situations, there are prematurely released connections when they occur when a call is in the active (established) state: + +- When a DL-RELEASE-INDICATION primitive was received from layer 2, timer T309 shall be started. Upon T309 expiry, the network connection shall be cleared. The remote user shall be informed by a DISCONNECT message with cause value No. 27 "*destination out of order*". This is not necessarily caused by a network failure, but may also be caused due to a failure at the user side. +- When a STATUS message is not returned by a LEX after the maximum number of retransmissions of a STATUS ENQUIRY message received from the user. In that case, the network connection shall be cleared by a DISCONNECT message, using cause value No. 41 "*temporary failure*". +- A RESUME message was received from the user at the network, but no RESUME ACKNOWLEDGE or RESUME REJECT was returned before T318 expiry. In that case, the user clears the call, by sending a RELEASE message with cause value No. 102 "*recovery on timer expiry*" (T318). + +When performance monitoring of the information dependability according to this Recommendation is not supported, it may be possible to monitor the information transfer dependability per call in an alternative way. The log records of Recommendation M.3641 [10] could be processed and the relevant information could be extracted. This processing can take place in the Operations System. It will be complicated to relate the M.3641 events to a single call. One needs accurate time stamps for + +the M.3650 access delay events and for the disengagement delay events. In that case, the time that the call existed is known. M.3641 events in that time interval can be used, but accurate time stamps for the M.3641 events and time synchronization with the M.3650 events is required. + +The following layer 1 event causes a prematurely released connection, in the case when a call is in the active state: + +- FE7, see [3], is received from the direction of the calling user at the originating LEX or from the direction of the called user at the destination LEX, and this is followed by issuing FE5 (access is deactivated) from the LEX to the direction where the FE7 was received from. In this case, Loss Of Signal or Loss Of Frame alignment occurred on the transmission system or power has been lost at the NT. + +There are no layer 2 events that are relevant for indicating a prematurely released connection. + +### 5.7 Disengagement delay + +Disengagement delay is measured by the time that is needed to release a connection. This is the time elapsed between the moment the user issues the termination request and ending when the user experiences that the connection has been released and the same resources can be used to establish a new connection. Disengagement delay is measured both at the side(s) where the user initiates call clearing (disconnecting side) and at the side where the network initiates call clearing (disconnected side). It is meaningful because resources used by the network could be claimed longer than expected by the user. + +Measurements at D-channel layer 3 at the customer access can be used for this purpose. + +![Sequence diagram illustrating disengagement delays between a Disconnecting side (NT) and a Disconnected side (NT) via two LEX nodes. The diagram shows the flow of DISCONNECT, RELEASE, and RELEASE COMPLETE messages. The Disconnecting side sends a DISCONNECT message to the first LEX, which then forwards it to the second LEX and finally to the Disconnected side. The Disconnected side responds with a RELEASE message, which is forwarded back through the LEX nodes to the Disconnecting side. The Disconnecting side then sends a RELEASE COMPLETE message, which is forwarded back through the LEX nodes to the Disconnected side. The Disconnected side receives the RELEASE COMPLETE message. The diagram also shows the 'null state' being reached at the LEX nodes.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +The diagram illustrates the message exchange for disengagement delay measurement. It features four vertical lines representing the Disconnecting side (NT), LEX, LEX, and Disconnected side (NT). The sequence of messages is as follows: 1. DISCONNECT is sent from the Disconnecting side (NT) to the first LEX. 2. The first LEX forwards the DISCONNECT message to the second LEX. 3. The second LEX forwards the DISCONNECT message to the Disconnected side (NT). 4. The Disconnected side (NT) sends a RELEASE message back to the second LEX. 5. The second LEX forwards the RELEASE message to the first LEX. 6. The first LEX forwards the RELEASE message to the Disconnecting side (NT). 7. The Disconnecting side (NT) sends a RELEASE COMPLETE message to the first LEX. 8. The first LEX forwards the RELEASE COMPLETE message to the second LEX. 9. The second LEX forwards the RELEASE COMPLETE message to the Disconnected side (NT). The Disconnected side (NT) receives the RELEASE COMPLETE message. The diagram also shows the 'null state' being reached at the LEX nodes. + +Sequence diagram illustrating disengagement delays between a Disconnecting side (NT) and a Disconnected side (NT) via two LEX nodes. The diagram shows the flow of DISCONNECT, RELEASE, and RELEASE COMPLETE messages. The Disconnecting side sends a DISCONNECT message to the first LEX, which then forwards it to the second LEX and finally to the Disconnected side. The Disconnected side responds with a RELEASE message, which is forwarded back through the LEX nodes to the Disconnecting side. The Disconnecting side then sends a RELEASE COMPLETE message, which is forwarded back through the LEX nodes to the Disconnected side. The Disconnected side receives the RELEASE COMPLETE message. The diagram also shows the 'null state' being reached at the LEX nodes. + +Figure 8/M.3650 – Disengagement delays + +The period that has to be measured at the side where the user initiates call clearing is: + +- the time between a layer 3 DISCONNECT message is received at the LEX and the time that a layer 3 RELEASE message is sent back to the terminal that sent the termination request. + +The following time period should be added: + +- the time between a layer 3 RELEASE COMPLETE message is received at the LEX and the time the B-channel is released by the LEX5. + +In this way, a correction is made for the delay caused by the user equipment. This is the time between a RELEASE sent from the LEX to the user and the time a RELEASE COMPLETE is received at the LEX. + +The period that has to be measured at the side where the network initiates call clearing is: + +- the time between the layer 3 RELEASE message is sent by the user and the time the RELEASE COMPLETE message is sent to the user. + +## **5.8 Disengagement accuracy** + +The disengagement accuracy is covered by the dependability aspect. (As a service disengagement function is considered to be successful or not, a degree of correctness is not considered useful.) + +## **5.9 Disengagement dependability** + +In order to determine the disengagement dependability, this Recommendation will measure whether a call termination was successful or not. There is a failed connection release if a release request was issued, but the allocated resources were not really released. Difference is made between call clearing initiated by the user and call clearing initiated by the network (remote user). No difference is made between outgoing or incoming calls. + +#### **Call clearing initiated by the user** + +A failed connection release caused by a network failure is detected when: + +- the user sends a correct layer 3 DISCONNECT message to the LEX that does not result in at least a layer 3 RELEASE message sent from the LEX to that user. Note that this is not a likely event. + +#### **Call clearing initiated by the network (remote user)** + +A failed connection release caused by a network failure is detected when: + +- after the LEX sent a DISCONNECT to the user, the user sends a layer 3 RELEASE message to the LEX that does not result in at least a layer 3 RELEASE COMPLETE message sent from the LEX to the user. + +## **6 Overview of measured parameters** + +The first column in Table 1 gives the generic performance parameters used in this Recommendation. The access accuracy, information transfer accuracy and disengagement accuracy parameters are not in the table, because no measurements are defined for these parameters. The second column indicates which aspects can be determined when measurements are performed for outgoing calls. The third column indicates which aspects can be determined when measurements are performed for incoming calls. + +--- + +5 The accurate detection of the moment when the B-channel resources are freed by the LEX can only be done by the LEX. Therefore, care is needed that the measurement of this moment does not interfere with the actual freeing of the resources. + +**Table 1/M.3650 – Overview of measured parameters** + +| | Measurements at outgoing calls; the following aspects can be determined: | Measurements at incoming calls; the following aspects can be determined: | +|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Access delay | Connection set-up delay and alerting delay without correction for delays caused by the called user or called user equipment. | Connection set-up delay and alerting delay cannot be measured. The delays caused by the called user or called user equipment can be determined. | +| Access dependability | Failed connection set-ups due to a network failure can be determined. | Not applicable. | +| Information transfer time | If the ISUP option for determination of the propagation delay is supported, this parameter can be determined. Also, the number of satellite hops can be counted. | If the ISUP option for determination of the propagation delay is supported, this parameter can be determined. Also, the number of satellite hops can be counted. | +| Information transfer dependability | Prematurely released connections due to a network failure can be detected, but not in all cases. | Prematurely released connections due to a network failure can be detected, but not in all cases. | +| Disengagement delay | The delay for releasing a connection can be determined. | The delay for releasing a connection can be determined. | +| Disengagement dependability | Unsuccessful released connections due to a network failure can be detected. | Unsuccessful released connections due to a network failure can be detected. | + +# 7 Description of management information + +For the selected D-channels, for each of the outgoing and incoming calls a log record will be created. The log record contains the information specified below. The GDMO and ASN.1 is normative and can be found in clause 8. At the Network Element level, outgoing call performance records and incoming call performance records are defined for layers 1, 2 and 3. The corresponding managed objects shall be contained in the Q.824.1 D-channel managed object or in the Q.824.1 accessPortISDN managed object. They shall at least have the following contents: + +| Information for the layer 1 outgoing call performance record | | +|---------------------------------------------------------------------|-----------------------------------| +| Attribute name | Attribute value type | +| For access delay: | | +| Layer 1 FE2 received | Time stamp | +| Layer 1 FE3 received | Time stamp | +| Layer 1 FE4 received | Time stamp | +| For access dependability: | | +| Causes non-successful | Layer 1 activation failure | +| For information transfer dependability: | | +| Causes non-successful | FE7 received, layer 1 deactivated | + +| Information for the layer 1 incoming call performance record | | +|---------------------------------------------------------------------|---------------------------------------------------------------------| +| Attribute name | Attribute value type | +| For access delay: | | +| Layer 1 FE1 sent | Time stamp | +| Layer 1 FE2 received | Time stamp | +| Layer 1 FE3 received | Time stamp | +| Layer 1 FE4 received | Time stamp | +| For access dependability: | | +| Causes non-successful | Layer 1 activation failure | +| For information transfer dependability: | | +| Causes non-successful | FE7 received, layer 1 deactivated | +| Information for the layer 2 outgoing call performance record | | +| Attribute name | Attribute value type | +| For access delay: | | +| Layer 2 SABME received | Time stamp | +| Layer 2 UA issued | Time stamp | +| For access dependability: | | +| Causes non-successful | Layer 2 establishment failure | +| Information for the layer 2 incoming call performance record | | +| Attribute name | Attribute value type | +| For access delay: | | +| Layer 2 SABME issued | Time stamp | +| Layer 2 UA received | Time stamp | +| Information for the layer 3 outgoing call performance record | | +| Attribute name | Attribute value type | +| General information: | | +| Called Number | Directory number | +| Calling Number | Directory number | +| Called Subaddress | Numericstring | +| Calling Subaddress | Numericstring | +| Information transfer capability | Speech
3.1 kHz Audio
Unrestricted digital information
etc. | +| Information transfer mode | Circuit mode
Packet mode | +| Information transfer rate | 64 kbit/s
etc. | +| For access delay | | +| Start-time call initiation (SETUP received) | Time stamp | + +| | | +|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Confirmation of call set-up (SETUP ACK issued) | Time stamp | +| All address information received (last INFORMATION received) | Time stamp | +| Start-time route ready (CONNECT or ALERTING issued, which comes first) | Time stamp | +| Start-time connection established (CONNECT issued) | Time stamp | +| For access dependability: | | +| Causes non-successful | Bearer capability not presently available
No response on SETUP or INFORMATION
Network out of order
Temporary failure
ISUP timer T7 expired
ISUP timer T8 expired
Switching equipment congestion
ISUP message type non-existent or not implemented/discard
ISUP parameter non-existent or not implemented, discarded | +| For information transfer time: | | +| Information transfer time | Number of satellite hops
Propagation delay | +| For information transfer dependability: | | +| Causes non-successful | FE7 received, layer 1 deactivated
T309 expired, destination out of order
Temporary failure, no STATUS response
Network out of order
Recovery on timer T318 expiry | +| For disengagement delay: | | +| Disengagement initiation (DISCONNECT received) | Time stamp | +| Exchange side released (RELEASE issued) | Time stamp | +| User side released (RELEASE COMPLETE received) | Time stamp | +| End-time call (B-channel is released) | Time stamp | +| For disengagement dependability: | | +| Causes non-successful | No RELEASE issued from LEX
No RELEASE COMP issued from LEX | +| Information for the layer 3 incoming call performance record | | +| General Information: | | +| Called Number | Directory number | +| Calling Number | Directory number | +| Called Subaddress | Numericstring | +| Calling Subaddress | Numericstring | + +| | | +|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Information transfer capability | Speech
3.1 kHz Audio
Unrestricted digital information
etc. | +| Information transfer mode | Circuit mode
Packet mode | +| Information transfer rate | 64 kbit/s
etc. | +| For access delay: | | +| Start-time call initiation (SETUP sent to called party) | Time stamp | +| Confirmation of call set-up (SETUP ACK received) | Time stamp | +| All address information issued (last INFORMATION issued) | Time stamp | +| Start-time route ready (CONNECT or ALERTING received, which comes first) | Time stamp | +| Start-time connection established (CONNECT received) | Time stamp | +| For information transfer time: | | +| Information transfer time | Number of satellite hops
Propagation delay | +| For information transfer dependability: | | +| Causes non-successful | T309 expired, destination out of order
Temporary failure, no STATUS response
Network out of order
Recovery on timer T318 expiry
ISUP timer T33 expired
ISUP timer T36 expired | +| For disengagement delay: | | +| Disengagement initiation (DISCONNECT received) | Time stamp | +| Exchange side released (RELEASE issued) | Time stamp | +| User side released (RELEASE COMPLETE received) | Time stamp | +| End-time call (B-channel is released) | Time stamp | +| For disengagement dependability: | | +| Causes non-successful | No RELEASE issued from LEX
No RELEASE COMP issued from LEX | + +In order to fulfil the requirement to indicate in the LEXs for which D-channels this Recommendation's measurements need to be performed, a monitoredAccess managed object will be defined that will be contained by the Q.824.1 D-channel managed object or by the accessPortISDNBasicRate or accessPortISDNPrimaryRate managed object. The monitoredAccess + +managed object will have actions for starting and ending call performance monitoring and will contain the following information: + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Start-time monitoring: | Date and time stamp | +| End-time monitoring: | Date and time stamp | +| Types of calls to be monitored: | layer 1 outgoing
layer 1 incoming
layer 2 outgoing
layer 2 incoming
layer 3 outgoing
layer 3 incoming | + +# **8 Management information model** + +## **8.1 Managed object classes** + +The managed objects within the dotted box are defined in this Recommendation. + +![Figure 9/M.3650 – Illustration of the naming schema. The diagram shows a hierarchy of managed elements. At the top is 'Rec. M.3100': managed Element. Below it is 'Rec. Q.824.1': accessPortISDN Basic/Primary Rate, which points to the top element. Below that are two branches. The left branch contains 'monitored Access', 'callPerformanceLog', and 'layerX Performance LogRecord' (grouped by a dashed box). The right branch contains 'Rec. Q.824.1': dChannel, which points to two 'Rec. M.3641': mgdDataLink DChannel elements. Below these is another dashed box containing 'monitored Access', 'callPerformanceLog', and 'layerX Performance LogRecord'. A label T0406570-96 is at the bottom right.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +``` + +graph TD + subgraph LeftGroup [ ] + L1[layerX Performance LogRecord] --> L2[callPerformanceLog] + L2 --> L3[monitored Access] + end + subgraph RightGroup [ ] + R1[layerX Performance LogRecord] --> R2[callPerformanceLog] + R2 --> R3[monitored Access] + end + D["Rec. Q.824.1": dChannel] --> M3641_1["Rec. M.3641": mgdDataLink DChannel] + D --> M3641_2["Rec. M.3641": mgdDataLink DChannel] + D --> R3 + AP["Rec. Q.824.1": accessPortISDN Basic/Primary Rate] --> L3 + AP --> D + AP --> ME["Rec. M.3100": managed Element] + style LeftGroup fill:none,stroke-dasharray: 5 5 + style RightGroup fill:none,stroke-dasharray: 5 5 + +``` + +Figure 9/M.3650 – Illustration of the naming schema. The diagram shows a hierarchy of managed elements. At the top is 'Rec. M.3100': managed Element. Below it is 'Rec. Q.824.1': accessPortISDN Basic/Primary Rate, which points to the top element. Below that are two branches. The left branch contains 'monitored Access', 'callPerformanceLog', and 'layerX Performance LogRecord' (grouped by a dashed box). The right branch contains 'Rec. Q.824.1': dChannel, which points to two 'Rec. M.3641': mgdDataLink DChannel elements. Below these is another dashed box containing 'monitored Access', 'callPerformanceLog', and 'layerX Performance LogRecord'. A label T0406570-96 is at the bottom right. + +Figure 9/M.3650 – Illustration of the naming schema + +### 8.1.1 Call performance log + +callPerformanceLog MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":log; + CHARACTERIZED BY callPerformanceLog-package; + REGISTERED AS { m3650ManagedObjectClass 1 }; + +### 8.1.2 Layer 1 performance log record + +layer1PerformanceLogRecord MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; + CHARACTERIZED BY layer1PerformanceLogRecord-package; + REGISTERED AS { m3650ManagedObjectClass 2 }; + +### 8.1.3 Layer 2 performance log record + +layer2PerformanceLogRecord MANAGED OBJECT CLASS + DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; + +CHARACTERIZED BY layer2PerformanceLogRecord-package; +REGISTERED AS { m3650ManagedObjectClass 3 }; + +### 8.1.4 Layer 3 performance log record + +layer3PerformanceLogRecord MANAGED OBJECT CLASS + +DERIVED FROM "Recommendation X.721 : 1992":eventLogRecord; + +CHARACTERIZED BY layer3PerformanceLogRecord-package; + +#### CONDITIONAL PACKAGES + +| | | +|-----------------------------------------------------------------------------------------|------------| +| layer3AccessDelay-package | PRESENT IF | +| "The implementation supports monitoring of layer 3 access delay", | | +| layer3AccessDependability-package | PRESENT IF | +| "The implementation supports monitoring of layer 3 access dependability", | | +| layer3InformationTransferTime-package | PRESENT IF | +| "The implementation supports monitoring of layer 3 information transfer time", | | +| layer3InformationTransferDependability-package | PRESENT IF | +| "The implementation supports monitoring of layer 3 information transfer dependability", | | +| layer3DisengagementDelay-package | PRESENT IF | +| "The implementation supports monitoring of layer 3 disengagement delay", | | +| layer3DisengagementDependability-package | PRESENT IF | +| "The implementation supports monitoring of layer 3 disengagement dependability"; | | + +REGISTERED AS { m3650ManagedObjectClass 4 }; + +### 8.1.5 Monitored access + +monitoredAccess MANAGED OBJECT CLASS + +DERIVED FROM "Recommendation X.721 : 1992":top; + +CHARACTERIZED BY monitoredAccess-package; + +#### CONDITIONAL PACKAGES + +| | | +|------------------------------------------------------|------------| +| layer1PerformanceNotification-package | PRESENT IF | +| "The implementation supports monitoring of layer 1", | | +| layer2PerformanceNotification-package | PRESENT IF | +| "The implementation supports monitoring of layer 2", | | +| layer3PerformanceNotification-package | PRESENT IF | +| "The implementation supports monitoring of layer 3"; | | + +REGISTERED AS { m3650ManagedObjectClass 5 }; + +## 8.2 Packages + +### 8.2.1 Call performance log + +callPerformanceLog-package PACKAGE + +#### BEHAVIOUR + +callPerformanceLogBehaviour BEHAVIOUR + +##### DEFINED AS + +"The callPerformanceLog contains all log records for performance management of ISDN calls.";; + +REGISTERED AS { m3650Package 1 }; + +### 8.2.2 Layer 1 performance log record + +layer1PerformanceLogRecord-package PACKAGE + +#### BEHAVIOUR + +layer1PerformanceLogRecordBehaviour BEHAVIOUR + +##### DEFINED AS + +"This package characterizes the layer 1 performance log record object and contains information on the performance of layer 1 establishment. The layer1PerformanceLogRecord managed object is used to represent logged information from the layer1PerformanceRecorded notification received from the monitoredAccess managed object.";; + +#### ATTRIBUTES + +| | | +|---------------------------|------| +| typeOfCall | GET, | +| layer1AccessDelay | GET, | +| layer1AccessDependability | GET, | + +layer1InformationTransferDependability GET; +REGISTERED AS { m3650Package 2 }; + +### 8.2.3 Layer 1 performance notification + +layer1PerformanceNotification-package PACKAGE +BEHAVIOUR +layer1PerformanceNotificationBehaviour BEHAVIOUR +DEFINED AS +"This package defines the layer1PerformanceRecorded notification.";; +NOTIFICATIONS +layer1PerformanceRecorded; +REGISTERED AS { m3650Package 3 }; + +### 8.2.4 Layer 2 performance log record + +layer2PerformanceLogRecord-package PACKAGE +BEHAVIOUR +layer2PerformanceLogRecordBehaviour BEHAVIOUR +DEFINED AS +"This package characterizes the layer 2 performance log record object and contains information on the performance of layer 2 establishment. The layer2PerformanceLogRecord managed object is used to represent logged information from the layer2PerformanceRecorded notification received from the monitoredAccess managed object.";; +ATTRIBUTES +typeOfCall GET, +layer2AccessDelay GET, +layer2AccessDependability GET; +REGISTERED AS { m3650Package 4 }; + +### 8.2.5 Layer 2 performance notification + +layer2PerformanceNotification-package PACKAGE +BEHAVIOUR +layer2PerformanceNotificationBehaviour BEHAVIOUR +DEFINED AS +"This package defines the layer2PerformanceRecorded notification.";; +NOTIFICATIONS +layer2PerformanceRecorded; +REGISTERED AS { m3650Package 5 }; + +### 8.2.6 Layer 3 access delay + +layer3AccessDelay-package PACKAGE +BEHAVIOUR +layer3AccessDelayPackageBehaviour BEHAVIOUR +DEFINED AS +"This package contains information on the layer 3 access delay.";; +ATTRIBUTES +layer3AccessDelay GET; +REGISTERED AS { m3650Package 6 }; + +### 8.2.7 Layer 3 access dependability + +layer3AccessDependability-package PACKAGE +BEHAVIOUR +layer3AccessDependabilityPackageBehaviour BEHAVIOUR +DEFINED AS +"This package contains information on the layer 3 access dependability.";; +ATTRIBUTES +layer3AccessDependability GET; +REGISTERED AS { m3650Package 7 }; + +### **8.2.8 Layer 3 disengagement delay** + +**layer3DisengagementDelay-package PACKAGE** + +**BEHAVIOUR** + +**layer3DisengagementDelayPackageBehaviour BEHAVIOUR** + +**DEFINED AS** + +**"This package contains information on the layer 3 disengagement delay.";;** + +**ATTRIBUTES** + +**layer3DisengagementDelay GET;** + +**REGISTERED AS { m3650Package 8 };** + +### **8.2.9 Layer 3 disengagement dependability** + +**layer3DisengagementDependability-package PACKAGE** + +**BEHAVIOUR** + +**layer3DisengagementDependabilityPackageBehaviour BEHAVIOUR** + +**DEFINED AS** + +**"This package contains information on the layer 3 disengagement dependability.";;** + +**ATTRIBUTES** + +**layer3DisengagementDependability GET;** + +**REGISTERED AS { m3650Package 9 };** + +### **8.2.10 Layer 3 information transfer dependability** + +**layer3InformationTransferDependability-package PACKAGE** + +**BEHAVIOUR** + +**layer3InformationTransferDependabilityPackageBehaviour BEHAVIOUR** + +**DEFINED AS** + +**"This package contains information on the layer 3 information transfer dependability.";;** + +**ATTRIBUTES** + +**layer3InformationTransferDependability GET;** + +**REGISTERED AS { m3650Package 10 };** + +### **8.2.11 Layer 3 information transfer time-package** + +**layer3InformationTransferTime-package PACKAGE** + +**BEHAVIOUR** + +**layer3InformationTransferTimePackageBehaviour BEHAVIOUR** + +**DEFINED AS** + +**"This package characterizes the layer 3 performance log record object and contains information on the performance of layer 3 establishment.";;** + +**ATTRIBUTES** + +**layer3InformationTransferTime GET;** + +**REGISTERED AS { m3650Package 11 };** + +### **8.2.12 Layer 3 performance log record** + +**layer3PerformanceLogRecord-package PACKAGE** + +**BEHAVIOUR** + +**layer3PerformanceLogRecordBehaviour BEHAVIOUR** + +**DEFINED AS** + +**"This package characterizes the layer 3 performance log record object and contains information on ISDN layer 3 parameters and on the performance results of call. The layer3PerformanceLogRecord managed object is used to represent logged information from the layer3PerformanceRecorded notification received from the monitoredAccess managed object.";;** + +**ATTRIBUTES** + +**typeOfCall GET,** + +**callingNumber GET,** + +**calledNumber GET,** + +**callingSubaddress GET,** + +**calledSubaddress GET,** + +**informationTransferCapability GET,** + +**informationTransferMode GET,** + +**informationTransferRate GET;** + +**REGISTERED AS { m3650Package 12 };** + +### 8.2.13 Layer 3 performance notification + +layer3PerformanceNotification-package PACKAGE + +BEHAVIOUR + +layer3PerformanceNotificationBehaviour BEHAVIOUR + +DEFINED AS + +"This package defines the layer3PerformanceRecorded notification.";; + +NOTIFICATIONS + +layer3PerformanceRecorded; + +REGISTERED AS { m3650Package 13 }; + +### 8.2.14 Monitored Access + +monitoredAccess-package PACKAGE + +BEHAVIOUR + +monitoredAccessBehaviour BEHAVIOUR + +DEFINED AS + +"This package is used by the Monitored Access managed object class. It contains actions to start and stop call performance monitoring for a specific ISDN access.";; + +ATTRIBUTES + +monitoredAccessId GET, + +typesMonitoring INITIAL VALUE ASN1TypeModule.initialTypesMonitoring +GET-REPLACE; + +ACTIONS + +startMonitoring, + +stopMonitoring; + +REGISTERED AS { m3650Package 14 }; + +## 8.3 Name bindings + +### 8.3.1 callPerformanceLog-monitoredAccess + +callPerformanceLog-monitoredAccess NAME BINDING + +SUBORDINATE OBJECT CLASS callPerformanceLog AND SUBCLASSES; + +NAMED BY + +SUPERIOR OBJECT CLASS + +monitoredAccess + +AND SUBCLASSES; + +WITH ATTRIBUTE + +"Recommendation X.721 : 1992":logId; + +CREATE + +WITH-REFERENCE-OBJECT, + +WITH-AUTOMATIC-INSTANCE-NAMING; + +DELETE + +DELETES-CONTAINED-OBJECTS; + +REGISTERED AS { m3650NameBinding 1 }; + +### 8.3.2 monitoredAccess-accessPort + +monitoredAccess-accessPortISDN NAME BINDING + +SUBORDINATE OBJECT CLASS monitoredAccess AND SUBCLASSES; + +NAMED BY + +SUPERIOR OBJECT CLASS + +"Recommendation Q.824.1:1995":accessPort + +AND SUBCLASSES; + +WITH ATTRIBUTE + +monitoredAccessId; + +CREATE + +WITH-REFERENCE-OBJECT, + +WITH-AUTOMATIC-INSTANCE-NAMING; + +DELETE + +DELETES-CONTAINED-OBJECTS; + +REGISTERED AS { m3650NameBinding 2 }; + +### 8.3.3 monitoredAccess-dChannel + +monitoredAccess-dChannel NAME BINDING + +SUBORDINATE OBJECT CLASS monitoredAccess AND SUBCLASSES; +NAMED BY +SUPERIOR OBJECT CLASS "Recommendation Q.824.1:1995":dChannel +AND SUBCLASSES; +WITH ATTRIBUTE monitoredAccessId; +CREATE +WITH-REFERENCE-OBJECT, +WITH-AUTOMATIC-INSTANCE-NAMING; +DELETE +DELETES-CONTAINED-OBJECTS; +REGISTERED AS { m3650NameBinding 3 }; + +## 8.4 Attributes + +### 8.4.1 Called number + +calledNumber ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.DirectoryNumber; +MATCHES FOR EQUALITY; +BEHAVIOUR +calledNumberBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the called party number.";; +REGISTERED AS { m3650Attribute 1 }; + +### 8.4.2 Called subaddress + +calledSubaddress ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Subaddress; +MATCHES FOR EQUALITY; +BEHAVIOUR +calledSubaddressBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the called party subaddress.";; +REGISTERED AS { m3650Attribute 2 }; + +### 8.4.3 Calling number + +callingNumber ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.DirectoryNumber; +MATCHES FOR EQUALITY; +BEHAVIOUR +callingNumberBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the calling party number.";; +REGISTERED AS { m3650Attribute 3 }; + +### 8.4.4 Calling subaddress + +callingSubaddress ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Subaddress; +MATCHES FOR EQUALITY; +BEHAVIOUR +callingSubaddressBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the calling party subaddress.";; +REGISTERED AS { m3650Attribute 4 }; + +### 8.4.5 Information transfer capability + +informationTransferCapability ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.InformationTransferCapability; +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +informationTransferCapabilityBehaviour BEHAVIOUR + +##### **DEFINED AS** + +"This attribute contains the information transfer capability of the call, see Recommendation Q.931.";; + +REGISTERED AS { m3650Attribute 5 }; + +### **8.4.6 Information transfer mode** + +informationTransferMode ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1TypeModule.InformationTransferMode; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +informationTransferModeBehaviour BEHAVIOUR + +##### **DEFINED AS** + +"This attribute contains the information transfer mode of the call, see Recommendation Q.931.";; + +REGISTERED AS { m3650Attribute 6 }; + +### **8.4.7 Information transfer rate** + +informationTransferRate ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1TypeModule.InformationTransferRate; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +informationTransferRateBehaviour BEHAVIOUR + +##### **DEFINED AS** + +"This attribute contains the information transfer capability of the call, see Recommendation Q.931.";; + +REGISTERED AS { m3650Attribute 7 }; + +### **8.4.8 Layer 1 access delay** + +layer1AccessDelay ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer1AccessDelay; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +layer1AccessDelayBehaviour BEHAVIOUR + +##### **DEFINED AS** + +"This attribute contains the several important events for layer 1 access delay. The events that did not happen in an aborted call get a value -1 for all integers in the TimeStamp type.";; + +REGISTERED AS { m3650Attribute 8 }; + +### **8.4.9 Layer 1 access dependability** + +layer1AccessDependability ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer1AccessDependability; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +layer1AccessDependabilityBehaviour BEHAVIOUR + +##### **DEFINED AS** + +"This attribute indicates successful or unsuccessful layer 1 establishment.";; + +REGISTERED AS { m3650Attribute 9 }; + +### **8.4.10 Layer 1 information transfer dependability** + +layer1InformationTransferDependability ATTRIBUTE + +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer1InformationTransferDependability; + +MATCHES FOR EQUALITY; + +#### **BEHAVIOUR** + +layer1InformationTransferDependabilityBehaviour BEHAVIOUR + +##### **DEFINED AS** + +"This attribute indicates successful or unsuccessful layer 1 information transfer. In the latter case, it contains the cause of the unsuccessful information transfer. For a call that was not + +successfully established, this attribute gets the value not applicable.";; +REGISTERED AS { m3650Attribute 10 }; + +### 8.4.11 Layer 2 access delay + +layer2AccessDelay ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer2AccessDelay; +MATCHES FOR EQUALITY; +BEHAVIOUR +layer2AccessDelayBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the several important events for layer 2 access delay. The events that +did not happen in an aborted call get a value 0 for all digits in the GeneralizedTime type.";; +REGISTERED AS { m3650Attribute 11 }; + +### 8.4.12 Layer 2 access dependability + +layer2AccessDependability ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer2AccessDependability; +MATCHES FOR EQUALITY; +BEHAVIOUR +layer2AccessDependabilityBehaviour BEHAVIOUR +DEFINED AS +"This attribute indicates successful or unsuccessful layer 2 establishment.";; +REGISTERED AS { m3650Attribute 12 }; + +### 8.4.13 Layer 3 access delay + +layer3AccessDelay ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer3AccessDelay; +MATCHES FOR EQUALITY; +BEHAVIOUR +layer3AccessDelayBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the several important events for layer 3 access delay. The events that +did not happen in an aborted call get a value -1 for all integers in the Timestamp type.";; +REGISTERED AS { m3650Attribute 13 }; + +#### 8.4.14 Layer 3 access dependability + +layer3AccessDependability ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer3AccessDependability; +MATCHES FOR EQUALITY; +BEHAVIOUR +layer3AccessDependabilityBehaviour BEHAVIOUR +DEFINED AS +"This attribute indicates successful or unsuccessful layer 3 establishment.";; +REGISTERED AS { m3650Attribute 14 }; + +#### 8.4.15 Layer 3 disengagement delay + +layer3DisengagementDelay ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer3DisengagementDelay; +MATCHES FOR EQUALITY; +BEHAVIOUR +layer3DisengagementDelayBehaviour BEHAVIOUR +DEFINED AS +"This attribute contains the several important events for layer 3 disengagement delay. The +events that did not happen in an aborted call get a value -1 for all integers in the Timestamp +type.";; +REGISTERED AS { m3650Attribute 15 }; + +#### 8.4.16 Layer 3 disengagement dependability + +layer3DisengagementDependability ATTRIBUTE +WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer3DisengagementDependability; + +**MATCHES FOR EQUALITY;** +**BEHAVIOUR** +layer3DisengagementDependabilityBehaviour **BEHAVIOUR** +**DEFINED AS** +"This attribute indicates successful or unsuccessful layer 3 disengagement. In the latter case, it contains the cause of the unsuccessful disengagement. For a call that was not successfully established, this attribute gets the value not applicable.";; +**REGISTERED AS { m3650Attribute 16 };** + +#### **8.4.17 Layer 3 information transfer dependability** + +layer3InformationTransferDependability **ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer3InformationTransferDependability;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR** +layer3InformationTransferDependabilityBehaviour **BEHAVIOUR** +**DEFINED AS** +"This attribute indicates successful or unsuccessful information transfer. In the latter case, it contains the cause of the unsuccessful information transfer. For a call that was not successfully established, this attribute gets the value not applicable.";; +**REGISTERED AS { m3650Attribute 17 };** + +### **8.4.18 Layer 3 information transfer time** + +layer3InformationTransferTime **ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1TypeModule.Layer3InformationTransferTime;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR** +layer3InformationTransferTimeBehaviour **BEHAVIOUR** +**DEFINED AS** +"This attribute contains the relevant parameters of the information transfer time of a call.";; +**REGISTERED AS { m3650Attribute 18 };** + +#### **8.4.19 Monitored Access Id** + +monitoredAccessId **ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1TypeModule.NameType;** +**MATCHES FOR EQUALITY, ORDERING;** +**BEHAVIOUR** +monitoredAccessIdBehaviour **BEHAVIOUR** +**DEFINED AS** +"This attribute represents the identification of the monitoredAccess managed object class.";; +**REGISTERED AS { m3650Attribute 19 };** + +### **8.4.20 Type of call** + +typeOfCall **ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1TypeModule.TypeOfCall;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR** +typeOfCallBehaviour **BEHAVIOUR** +**DEFINED AS** +"This attribute specifies whether the monitored call was an incoming or an outgoing call.";; +**REGISTERED AS { m3650Attribute 20 };** + +#### **8.4.21 Types monitoring** + +typesMonitoring **ATTRIBUTE** +**WITH ATTRIBUTE SYNTAX ASN1TypeModule.TypesMonitoring;** +**MATCHES FOR EQUALITY;** +**BEHAVIOUR** +typesMonitoringBehaviour **BEHAVIOUR** +**DEFINED AS** +"This attribute specifies whether layer 1, 2 and 3 outgoing calls and incoming calls have to be + +monitored or not.";; +REGISTERED AS { m3650Attribute 21 }; + +## 8.5 Actions + +#### 8.5.1 Start Monitoring + +startMonitoring ACTION +BEHAVIOUR +startMonitoringBehaviour BEHAVIOUR +DEFINED AS +"This action initiates performance monitoring of the calls at the ISDN access at the specified time. When the action is performed while performance monitoring was already active, performance monitoring is continued. If the value of the TypesMonitoring attribute had been changed, the ISDN access or D-channel is now monitored according to the modified TypesMonitoring.";; +MODE CONFIRMED; +WITH INFORMATION SYNTAX ASN1TypeModule.MonitoringTimeStamp; +REGISTERED AS { m3650Action 1 }; + +### 8.5.2 Stop Monitoring + +stopMonitoring ACTION +BEHAVIOUR +stopMonitoringBehaviour BEHAVIOUR +DEFINED AS +"This action ends performance monitoring of the calls at the ISDN access at the specified time.";; +MODE CONFIRMED; +WITH INFORMATION SYNTAX ASN1TypeModule.MonitoringTimeStamp; +REGISTERED AS { m3650Action 2 }; + +## 8.6 Notifications + +#### 8.6.1 Layer 1 performance recorded + +layer1PerformanceRecorded NOTIFICATION +BEHAVIOUR +layer1PerformanceRecordedBehaviour BEHAVIOUR +DEFINED AS +"This notification is emitted when layer 1 is terminated or not successfully established.";; +WITH INFORMATION SYNTAX ASN1TypeModule.Layer1PerformanceRecorded +AND ATTRIBUTE IDS +typeOfCall, typeOfCall, +layer1AccessDelay, layer1AccessDelay, +layer1AccessDependability, layer1AccessDependability, +layer1InformationTransferDependability, layer1InformationTransferDependability; +REGISTERED AS { m3650Notification 1 }; + +### 8.6.2 Layer 2 performance recorded + +layer2PerformanceRecorded NOTIFICATION +BEHAVIOUR +layer2PerformanceRecordedBehaviour BEHAVIOUR +DEFINED AS +"This notification is emitted when layer 2 is terminated or not successfully established.";; +WITH INFORMATION SYNTAX ASN1TypeModule.Layer2PerformanceRecorded +AND ATTRIBUTE IDS +typeOfCall, typeOfCall, +layer2AccessDelay, layer2AccessDelay, +layer2AccessDependability, layer2AccessDependability; +REGISTERED AS { m3650Notification 2 }; + +### 8.6.3 Layer 3 performance recorded + +layer3PerformanceRecorded NOTIFICATION + +BEHAVIOUR + +layer3PerformanceRecordedBehaviour BEHAVIOUR + +DEFINED AS + +"This notification is emitted when layer 3 is terminated or not successfully established."; + +WITH INFORMATION SYNTAX ASN1TypeModule.Layer3PerformanceRecorded + +AND ATTRIBUTE IDS + +| | | +|----------------------------------------|-----------------------------------------| +| typeOfCall | typeOfCall, | +| callingNumber | callingNumber, | +| calledNumber | calledNumber, | +| callingSubaddress | callingSubaddress, | +| calledSubaddress | calledSubaddress, | +| informationTransferCapability | informationTransferCapability, | +| informationTransferMode | informationTransferMode, | +| informationTransferRate | informationTransferRate, | +| layer3AccessDelay | layer3AccessDelay, | +| layer3AccessDependability | layer3AccessDependability, | +| layer3InformationTransferTime | layer3InformationTransferTime, | +| layer3InformationTransferDependability | layer3InformationTransferDependability, | +| layer3DisengagementDelay | layer3DisengagementDelay, | +| layer3DisengagementDependability | layer3DisengagementDependability; | + +REGISTERED AS { m3650Notification 3 }; + +## 8.7 ASN.1 Type definitions module + +This subclause contains the abstract syntax in ASN.1 for the management information defined in this Recommendation. + +ASN1TypeModule { itu-t(0) recommendation(0) m(13) m3650(3650) informationModel(0) asn1Module(2) + +asn1TypeModule(0)} + +DEFINITIONS IMPLICIT TAGS ::= + +BEGIN + +-- EXPORTS *everything* + +IMPORTS + +DirectoryName FROM CAISDNModule { itu-t(0) recommendation(0) q(17) q824(824) informationModel(0) asn1Module(2) asn1DefinedTypesModule(0) } + +NameType FROM ASN1DefinedTypesModule { ccitt(0) recommendation(0) m(13) gnm(3100) + +informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0) } + +TimePeriod FROM MetricModule { joint-iso-ccitt ms(9) function(2) part11(11) asn1Module(2) 0 }; + +m3650InformationModel OBJECT IDENTIFIER ::= { itu-t(0) recommendation(0) m(13) m3650(3650) informationModel(0) } + +m3650StandardSpecificExtension OBJECT IDENTIFIER ::= { m3650InformationModel standardSpecificExtension (0) } + +m3650ManagedObjectClass OBJECT IDENTIFIER ::= { m3650InformationModel managedObjectClass (3) } + +m3650Package OBJECT IDENTIFIER ::= { m3650InformationModel package(4) } + +m3650NameBinding OBJECT IDENTIFIER ::= { m3650InformationModel nameBinding (6) } + +m3650Attribute OBJECT IDENTIFIER ::= { m3650InformationModel attribute (7) } + +m3650Action OBJECT IDENTIFIER ::= { m3650InformationModel action (9) } + +m3650Notification OBJECT IDENTIFIER ::= { m3650InformationModel notification (10) } + +initialTypesMonitoring TypesMonitoring ::= { TRUE, TRUE, TRUE, TRUE, TRUE, TRUE } + +``` + +InformationTransferCapability ::= ENUMERATED { + speech (0), + unrestrictedDigitalInformation (1), + restrictedDigitalInformation (2), + threeDotOneKHzAudio (3), + sevenKHzAudio (4), + video (5)} + +InformationTransferMode ::= ENUMERATED { + circuitMode (0), + packetMode (1)} + +InformationTransferRate ::= ENUMERATED { + packetMode (0), + kBits64 (1), + kBits2x64 (2), + kBits384 (3), + kBits1536 (4), + kBits1920 (5)} + +Layer1AccessDelay ::= SEQUENCE { + layer1FE1 TimeStamp, + layer1FE2 TimeStamp, + layer1FE3 TimeStamp, + layer1FE4 TimeStamp} + +Layer1AccessDependability ::= ENUMERATED { + successfulLayer1AccessDependability (0), + layer1Failure (1)} + +Layer1InformationTransferDependability ::= ENUMERATED { + successfulInformationTransfer (0), + layer1Failure (1)} + +Layer1PerformanceRecorded ::= SEQUENCE { + typeOfCall TypeOfCall, + layer1AccessDelay Layer1AccessDelay, + layer1AccessDependability Layer1AccessDependability, + layer1InformationTransferDependability Layer1InformationTransferDependability} + +Layer2AccessDelay ::= SEQUENCE { + layer2SABME TimeStamp, + layer2UA TimeStamp} + +Layer2AccessDependability ::= ENUMERATED { + successfulLayer2AccessDependability (0), + layer2Failure (1)} + +Layer2PerformanceRecorded ::= SEQUENCE { + typeOfCall TypeOfCall, + layer2AccessDelay Layer2AccessDelay, + layer2AccessDependability Layer2AccessDependability} + +Layer3AccessDelay ::= SEQUENCE { + layer3SETUP [0] TimeStamp, + layer3SETACK [1] TimeStamp OPTIONAL, + layer3INF [2] TimeStamp OPTIONAL, + layer3ALERT [3] TimeStamp OPTIONAL, + layer3CONNECT [4] TimeStamp OPTIONAL} + +``` + +``` + +Layer3AccessDependability ::= ENUMERATED { + successfulLayer3AccessDependability (0), + bearerCapabilityNotAvailable (1), + noResponseSETUPorINF (2), + networkOutOfOrder (3), + temporaryFailure (4), + iSUPT7Expired (5), + iSUPT8Expired (6), + switchingEquipmentCongestion (7), + iSUPMessageError (8), + iSUPParameterError (9), + otherUnsuccessful (10)} + +Layer3DisengagementDelay ::= SEQUENCE { + layer3DISCONNECT Timestamp, + layer3RELEASE Timestamp, + layer3RELCOMP Timestamp, + bChannelFree Timestamp} + +Layer3DisengagementDependability ::= ENUMERATED { + successfulDisengagement (0), + noRELEASE (1), + noRELCOMP (2), + otherUnsuccessful (3), + notApplicable (4)} + +Layer3InformationTransferDependability ::= ENUMERATED { + successfulInformationTransfer (0), + destinationOutOfOrder (1), + t318Expired (2), + temporaryFailure (3), + networkOutOfOrder (4), + otherUnsuccessful (5), + notApplicable (6)} + +Layer3InformationTransferTime ::= SEQUENCE { + numberOfSatelliteHops INTEGER OPTIONAL, + propagationDelay TimePeriod OPTIONAL} + +Layer3PerformanceRecorded ::= SEQUENCE { + typeOfCall TypeOfCall, + callingNumber DirectoryNumber, + calledNumber DirectoryNumber, + callingSubaddress Subaddress, + calledSubaddress Subaddress, + informationTransferCapability InformationTransferCapability, + informationTransferMode InformationTransferMode, + informationTransferRate InformationTransferRate, + layer3AccessDelay Layer3AccessDelay, + layer3AccessDependability Layer3AccessDependability, + layer3InformationTransferTime Layer3InformationTransferTime, + layer3InformationTransferDependability Layer3InformationTransferDependability, + layer3DisengagementDelay Layer3DisengagementDelay, + layer3DisengagementDependability Layer3DisengagementDependability} + +MonitoringTimeStamp ::= GeneralizedTime + +Subaddress ::= OCTET STRING + +``` + +``` + +TimeStamp ::= SEQUENCE { + hours INTEGER, -- -1 to 23 + minutes INTEGER, -- -1 to 59 + seconds INTEGER, -- -1 to 59 + milliseconds INTEGER} -- -1 to 999 + +``` + +``` + +TypesMonitoring ::= SEQUENCE { + outgoingLayer1 BOOLEAN, + incomingLayer1 BOOLEAN, + outgoingLayer2 BOOLEAN, + incomingLayer2 BOOLEAN, + outgoingLayer3 BOOLEAN, + incomingLayer3 BOOLEAN} + +``` + +``` + +TypeOfCall ::= ENUMERATED { + outgoing (0), + incoming (1)} + +``` + +END + +# 9 Support objects from other Recommendations + +The following support object classes (or their subclasses) should be used to support the performance measurements of ISDN calls management functions specified in this Recommendation: + +- eventForwardingDiscriminator (defined in Recommendation X.721 [18]); +- eventLogRecord (defined in Recommendation X.721 [18]); +- log (defined in Recommendation X.721 [18]). + +The following system management functions define management capabilities which are used in the management information model of the performance measurements of ISDN calls: + +- event report management function [20]; +- log control function [21]. + +## 10 Functional unit + +## 10.1 Definition of functional units + +Three functional units are defined in this Recommendation for performance measurements of ISDN calls: + +- *iSDNLayer1PerfMeasurements functional unit* + +This functional unit supports the following Event Reporting Service: + +- Layer1 Performance Recorded Reporting Service; + +- *iSDNLayer2PerfMeasurements functional unit* + +This functional unit supports the following Event Reporting Service: + +- Layer2 Performance Recorded Reporting Service; + +- *iSDNLayer3PerfMeasurements functional unit* + +This functional unit supports the following Event Reporting Service: + +- Layer3 Performance Recorded Reporting Service. + +To provide the mapping between the parameters for the event reports (result of the notifications) and CMIS M-EVENT-REPORT [16], [17], the Event Reporting Services are defined as follows: + +The Layer1 Performance Recorded Reporting Service, the Layer2 Performance Recorded Reporting Service and the Layer3 Performance Recorded Reporting Service allow a managed system to report that a call has been completed and gives detailed information on the performance of the call. + +Table 2 contains the parameters for these Event Reporting Services. The Event Information parameter will indicate which Event Reporting Service is invoked. + +**Table 2/M.3650 – Event Reporting Service parameters** + +| Parameter name | Req./Ind. | Rsp./Cnf. | +|-------------------------|-----------|-----------| +| Invoke Identifier | P | P | +| Mode | P | – | +| Managed Object Class | P | P | +| Managed Object Instance | P | P | +| Event Type | M | C(=) | +| Event Time | P | – | +| Event Information | M | – | +| Current Time | – | P | +| Event reply | – | C | +| Errors | – | P | + +The meaning of the symbols "M", "C" and "(=)" used in this table are the same as used in the tables for the CMISE description [16]. The symbol "P" means "subject to the constraints imposed on the parameter by CCITT Rec. X.710 | ISO/IEC 9595". + +The following parameters are defined for use in the Event Reporting Service: + +- Invoke Identifier: see Invoke Identifier [16]. +- Mode: see Mode [16]. The values for this parameter are either confirmed or unconfirmed. +- Managed Object Class: see Managed Object Class [16]. This parameter shall indicate the monitoredAccess managed object class. +- Managed Object Instance: see Managed Object Instance [16]. +- Event Type: this parameter specifies the type of event being reported and the value shall be as indicated by Table 3. + +**Table 3/M.3650 – Event Type values for the Event Reporting Services** + +| Event Reporting Service | Event Type value | +|-----------------------------|---------------------------| +| Layer1 Performance Recorded | layer1PerformanceRecorded | +| Layer2 Performance Recorded | layer2PerformanceRecorded | +| Layer3 Performance Recorded | layer3PerformanceRecorded | + +The Event Type parameter may be included in the response if the Event Reply parameter is present in the response. + +- Event Time: see Event Time [16]. +- Event Information: see Event Information [16]. This parameter contains a subparameter. The subparameter specifies the following information as indicated by Table 4. + +**Table 4/M.3650 – Information included in Event Information Subparameter** + +| Subparameter Name | Information | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Layer1PerformanceRecorded | type of call, layer1 access delay, layer 1 access dependability, layer 1 information transfer dependability | +| Layer2PerformanceRecorded | type of call, layer2 access delay, layer 2 access dependability | +| Layer3PerformanceRecorded | type of call, calling number, called number, calling subaddress, called subaddress, information transfer capability, information transfer mode, information transfer rate, layer3 access delay, layer 3 access dependability, layer 3 information transfer time, layer 3 information transfer dependability, layer 3 disengagement delay, layer 3 disengagement dependability | + +- Current Time: see Current Time [16]. +- Event Reply: see Event Reply [16]. The inclusion of this parameter in the response is conditional upon the successful receipt of the event report in the confirmed mode. +- Errors: see Errors [16]. This parameter shall be included in a failure confirmation. + +## 10.2 Negotiation of functional units + +This specification assigns the following object identifier value: + +{itu(0) recommendation (0) m(13) m3650(3650) functionalUnitPackage(1)} as a value for the ASN.1 type FunctionalUnitPackageID defined in X.701 | ISO/IEC 10040 [15] to use for negotiation the following functional units: + +- 0 iSDNLayer1PerfMeasurements +- 1 iSDNLayer2PerfMeasurements +- 2 iSDNLayer3PerfMeasurements + +where the numbers (0), (1) and (2) identify the bit position in the BITSTRING assigned to the functional unit. + +The mechanism for negotiating the functional units is described in Recommendation X.701 | ISO/IEC 10040 [15]. + +# 11 Conformance + +The system shall comply to the following conformance statements: + +- support the role of manager or agent or both, with respect to the functional units defined in this Recommendation; +- for each dChannel, accessPortISDNBasicRate and accessPortISDNPrimaryRate managed object, it should be possible to instantiate exactly one instance of the monitoredAccess managed object; +- for each monitoredAccess managed object, it should be possible to instantiate the callPerformanceLog managed object. + +The MCS and MOCS proforma for this Recommendation are defined in Annex A. + +# ANNEX AMCS and MOCS proforma + +## **A.0 MCS proforma** + +### **A.0.1 Introduction** + +#### **A.0.1.1 Purpose and structure** + +The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and provides information on whether the implementation claims conformance to any of the listed set of documents that specify conformance requirements to OSI management. + +The MCS proforma is a document in the form of a questionnaire that when completed by the supplier of an implementation becomes the MCS. + +#### **A.0.1.2 Instructions for completing the MCS proforma to produce an MCS6** + +The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is provided in the text which precedes each table. + +### **A.0.2 Identification of the implementation** + +#### **A.0.2.1 Date of statement** + +The supplier of the implementation shall enter the date of this statement in the box below. Use the format DD-MM-YYYY. + +| | +|-------------------| +| Date of statement | +|-------------------| + +#### **A.0.2.2 Identification of the implementation** + +The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the system(s) in which it may reside, in the box below. + +| | +|--| +| | +|--| + +--- + +6 Instructions for MCS proforma are specified in ITU-T Rec. X.724 | ISO 10165-6. + +#### **A.0.2.3 Contact** + +The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the content of the MCS, in the box below. + +| | +|--| +| | +|--| + +### **A.0.3 Identification of the document in which the management information is defined** + +The supplier of the implementation shall enter the title, reference number and date of the publication of the document which specifies the management information to which conformance is claimed in the box below. + +| | +|------------------------------------------| +| Document to which conformance is claimed | +|------------------------------------------| + +#### **A.0.3.1 Technical corrigenda implemented** + +The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify the specification in the identified document, in the box below. + +| | +|--| +| | +|--| + +#### **A.0.3.2 Amendments implemented** + +The supplier of the implementation shall state the titles and reference numbers of implemented addenda to the identified document, in the box below. + +| | +|--| +| | +|--| + +### **A.0.4 Management conformance summary** + +The supplier of the implementation shall provide information on whether the implementation claims conformance to any of the set of documents globally representing the implementation under claim. For each document the supplier of the implementation claims conformance to, the corresponding + +conformance statement(s) shall be filled in, or referenced by, the MCS. Columns 7 (Support), 8 (Table numbers of PICS/MOCS/MRCS ) and 9 (Additional information) are to be filled in by the supplier of the implementation. + +The following common notations, defined in CCITT Recommendation X.291 | ISO/IEC 9646-2 and ITU-T Recommendation X.296 | ISO/IEC 9646-7 are used for the status value column: + +- m mandatory; +- o optional; +- c conditional; +- x prohibited; +- not applicable or out of scope. + +NOTE 1 – The notations "c", "m", "o", and "x" are prefixed by a "c:" when nested under a conditional or optional item of the same table. + +NOTE 2 – The notation "o" may be suffixed by ".n" (where "n" is a unique number) for mutually exclusive or selectable options among a set of status values. The requirement for this numbered set shall be explicitly stated, preferably in a footnote to the relevant table. + +The following common notations, defined in CCITT Recommendation X.291 | ISO/IEC 9646-2 and ITU-T Recommendation X.296 ISO/IEC 9646-7 are used for the support answer column: + +- Y implemented; +- N not implemented; +- no answer required; +- Ig the item is ignored (i.e. processed syntactically but not semantically). + +In the status column, the static requirements are stated. The status will be as follows: + +- m for characteristics contained in mandatory packages or in conditional packages if the GDMO condition is always true; +- o for characteristics of conditional packages with GDMO conditions that indicate static optionality, e.g. "if an instance supports it"; +- cn for all other conditions, where "n" is a unique integer and "cn" is a reference to a conditional status expression. +- x for characteristics explicitly prohibited in the definition; +- for characteristics that are not mentioned in the definition. + +**Table A.0.1 – PICS support summary** + +| Index | Identification of the document that includes the PICS proforma | Table numbers of PICS proforma | Description | Constraints and values | Status | Support | Table numbers of PICS | Additional information | +|-------|----------------------------------------------------------------|--------------------------------|-------------|------------------------|--------|---------|-----------------------|------------------------| +| | | | | | | | | | +| | | | | | | | | | + +**Table A.0.2 – MOCS support summary** + +| Index | Identification of the document that includes the MOCS proforma | Table numbers of MOCS proforma | Description | Constraints and values | Status | Support | Table numbers of MOCS | Additional information | +|-------|----------------------------------------------------------------|--------------------------------|----------------------------|------------------------|--------|---------|-----------------------|------------------------| +| 1 | "ITU-T Rec. M.3650 (1996)" | A.1.1-
A.1.10 | callPerformanceLog | | | | A.1.1-
A.1.10 | | +| 2 | "ITU-T Rec. M.3650 (1996)" | A.2.1-
A.2.10 | layer1PerformanceLogRecord | | | | A.2.1-
A.2.10 | | +| 3 | "ITU-T Rec. M.3650 (1996)" | A.3.1-
A.3.10 | layer2PerformanceLogRecord | | | | A.3.1-
A.3.10 | | +| 4 | "ITU-T Rec. M.3650 (1996)" | A.4.1-
A.4.10 | layer3PerformanceLogRecord | | | | A.4.1-
A.4.10 | | +| 5 | "ITU-T Rec. M.3650 (1996)" | A.5.1-
A.5.10 | monitoredAccess | | | | A.5.1-
A.5.10 | | + +**Table A.0.3 – MRCS support summary** + +| Index | Identification of the document that includes the MRCS proforma | Table numbers of MRCS proforma | Description | Constraints and values | Status | Support | Table numbers of MRCS | Additional information | +|-------|----------------------------------------------------------------|--------------------------------|------------------------------------------------------------------|------------------------|--------|---------|-----------------------|------------------------| +| 1 | "ITU-T Rec. M.3650 (1996)" | A.1.10 | callPerformanceLog-monitoredAccess | | | | A.1.10 | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992" | A.1.10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":log-system | | | | A.1.10 | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992" | A.2.10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":logRecord-log | | | | A.2.10 | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992" | A.3.10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":logRecord-log | | | | A.3.10 | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992" | A.4.10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":logRecord-log | | | | A.4.10 | | +| 6 | "ITU-T Rec. M.3650 (1996)" | A.5.10 | monitoredAccess-accessPortISDN | | | | A.5.10 | | +| 7 | "ITU-T Rec. M.3650 (1996)" | A.5.10 | monitoredAccess-dChannel | | | | A.5.10 | | + +## A.1 MOCS proforma + +### A.1.1 Introduction + +The purpose of this MOCS proforma is to provide a mechanism for a supplier of an implementation which claims conformance to a managed object class to provide conformance information in a standard form. + +#### A.1.1.1 Instructions for completing the MOCS proforma to produce a MOCS7 + +The supplier of the implementation shall state which items are supported in the tables below and if necessary provide additional information. + +#### A.1.1.2 Statement of conformance to the managed object class + +These tables have been prepared without regard to manager or agent role, so they can be used in either situation. An implementation that supports both roles could either use one set of tables if all support details are the same, or a different set of tables for each role. + +These tables were generated mechanically from the GDMO templates, with additions and clarifications added by hand. + +These tables have columns for the "Base Status" and the "Profile Status", where the entries are identical, allowing the tables to be used directly. Other profiles, such as an Ensemble, may modify these tables by replacing the "Profile Status" entries, using the normal rules for defining a profile. + +### A.1.2 CallPerformanceLog + +**Table A.1.1 – callPerformanceLog Managed object class support** + +| Index | Managed object class template label | Value of object identifier for class | Support of all mandatory features? (Y/N) | Is the actual class the same as the managed object class to which conformance is claimed? (Y/N) | +|-------|-------------------------------------|--------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------| +| 1 | callPerformanceLog | {0 0 13 3650 0 3 1} | | | + +**Table A.1.2 – callPerformanceLog Actual class support** + +| Index | Managed object class template for actual class | Value of object identifier for managed object class definition of actual class | Additional information | +|-------|------------------------------------------------|--------------------------------------------------------------------------------|------------------------| +| | | | | +| | | | | + +7 Instructions for MOCS proforma are specified in ITU-T Rec. X.724 | ISO/IEC 10165-6. + +**Table A.1.3 – callPerformanceLog Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": availabilityStatusPackage | {2 9 3 2 4 22} | "any of the scheduling packages (duration, weekly scheduling, external) are present. The presence of this package makes available the off-duty value of the available status attribute to the object." | c1 | | | +| 3 | callPerformanceLog-package | {0 0 13 3650 0 4 1} | Mandatory | m | | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": dailyScheduling | {2 9 3 2 4 25} | "both the weekly scheduling package and external scheduler packages are not present in an instance and daily scheduling is supported by that instance." | c2 | | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": duration | {2 9 3 2 4 26} | "the logging function is scheduled to start at a specified time and stop at either a specified time or function continuously." | c3 | | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": externalScheduler | {2 9 3 2 4 27} | "both the daily scheduling package and weekly scheduling packages are not present in an instance and external scheduling is supported by that instance." | c4 | | | +| 7 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": finiteLogSizePackage | {2 9 3 2 4 12} | "an instance supports it" | o | | | +| 8 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logAlarmPackage | {2 9 3 2 4 13} | "a log is of finite size and halts logging when the availability status has the log full value." | c5 | | | +| 9 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logPackage | | Mandatory | m | | | +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package has been instantiated" | c6 | | | +| 11 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | +| 12 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": weeklyScheduling | {2 9 3 2 4 29} | "both the daily scheduling package and external scheduler packages are not present in an instance and weekly scheduling is supported by that instance." | c7 | | | + +**Table A.1.4 – callPerformanceLog Attribute support** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|----------------------------------------------------------------------------|------------------------------------------|------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": administrativeState | {2 9 3 2 7 31} | ENUMERATED | m | | m | | m | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | – | | m | | – | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": availabilityStatus | {2 9 3 2 7 33} | SET OF INTEGER | – | | – | | – | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": capacityAlarmThreshold | {2 9 3 2 7 52} | SET OF INTEGER | c5 | | c5 | | c5 | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": currentLogSize | {2 9 3 2 7 54} | INTEGER | – | | o | | – | | +| 7 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": discriminatorConstruct | {2 9 3 2 7 56} | CHOICE | m | | m | | m | | +| 8 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": intervalsOfDay | {2 9 3 2 7 57} | SET OF SEQUENCE | c2 | | c2 | | c2 | | +| 9 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logFullAction | {2 9 3 2 7 58} | ENUMERATED | m | | m | | m | | +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logId | {2 9 3 2 7 2} | CHOICE | – | | m | | – | | +| 11 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": maxLogSize | {2 9 3 2 7 62} | INTEGER | o | | o | | o | | +| 12 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | + +**Table A.1.4 – callPerformanceLog Attribute support (continued)** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|-------------------------------------------------------------------------|------------------------------------------|--------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 13 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
numberOfRecords | {2 9 3 2 7 64} | INTEGER | – | | o | | – | | +| 14 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 15 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
operationalState | {2 9 3 2 7 35} | ENUMERATED | – | | m | | – | | +| 16 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c6 | | – | | +| 17 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
schedulerName | {2 9 3 2 7 67} | CHOICE | – | | c4 | | – | | +| 18 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
startTime | {2 9 3 2 7 68} | GeneralizedTime | c3 | | c3 | | c3 | | +| 19 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
stopTime | {2 9 3 2 7 69} | CHOICE | c3 | | c3 | | c3 | | +| 20 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
weekMask | {2 9 3 2 7 71} | SET OF SEQUENCE | c7 | | c7 | | c7 | | + +**Table A.1.4 – callPerformanceLog Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | c5 | | c5 | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | c2 | | c2 | | c2 | | | + +**Table A.1.4 – callPerformanceLog Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | c3 | | | +| 20 | c7 | | c7 | | c7 | | | + +**Table A.1.5 – callPerformanceLog Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table A.1.6 – callPerformanceLog Action support** + +There are no actions specified for this managed object class. + +**Table A.1.7 – callPerformanceLog Notification support** + +| Index | Notification type template label | Value of object identifier for notification type | Constraints and values | Status | Support | | Additional information | +|-------|--------------------------------------------------------------------------|--------------------------------------------------|------------------------|--------|-----------|---------------|------------------------| +| | | | | | Confirmed | Non-confirmed | | +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": attributeValueChange | {2 9 3 2 10 1} | | m | | | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": objectCreation | {2 9 3 2 10 6} | | m | | | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": objectDeletion | {2 9 3 2 10 7} | | m | | | | + +**Table A.1.7 – callPerformanceLog Notification support (continued)** + +| Index | Notification type template label | Value of object identifier for notification type | Constraints and values | Status | Support | | Additional information | +|-------|--------------------------------------------------------------------------|--------------------------------------------------|------------------------|--------|-----------|---------------|------------------------| +| | | | | | Confirmed | Non-confirmed | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": processingErrorAlarm | {2 9 3 2 10 10} | | m | | | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": stateChange | {2 9 3 2 10 14} | | m | | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|--------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| 1 | 1.1 | AttributeValueChangeInfo | | Information Syntax SEQUENCE | m | | | +| | 1.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 1.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 1.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.1 | | | +| | 1.1.2.2 | localForm | – | INTEGER | c:o.1 | | | +| | 1.1.3 | attributeValueChangeDefinition | {2 9 3 2 7 10} | SET OF SEQUENCE | m | | | +| | 1.1.3.1 | attributeID | – | CHOICE | m | | | +| | 1.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.2 | | | +| | 1.1.3.1.2 | localForm | – | INTEGER | o.2 | | | +| | 1.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 1.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 1.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 1.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 1.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 1.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 1.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.3 | | | +| | 1.1.5.2.1.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.1.2 | value | – | ANY | c:m | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| | 1.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.3 | | | +| | 1.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.3 | | | +| | 1.1.5.2.3.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.5.2.3.2 | value | – | ANY | c:m | | | +| | 1.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 1.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 1.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 1.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 1.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 2 | 2.1 | ObjectInfo | | Information Syntax
SEQUENCE | m | | | +| | 2.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 2.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | o | | | +| | 2.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 2.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.4 | | | +| | 2.1.2.1.2 | localForm | – | INTEGER | c:o.4 | | | +| | 2.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 2.1.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 2.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 2.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 2.1.4.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 2.1.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.1.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.1.2 | value | – | ANY | c:m | | | +| | 2.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.5 | | | +| | 2.1.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.5 | | | +| | 2.1.4.2.3.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.4.2.3.2 | value | – | ANY | c:m | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|------------------------------------|--------|---------|------------------------| +| | 2.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 2.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 2.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 2.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 2.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 3 | 3.1 | ObjectInfo | | Information Syntax SEQUENCE | m | | | +| | 3.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 3.1.2 | attributeList | {2 9 3 2 7 9} | SET OF SEQUENCE | o | | | +| | 3.1.2.1 | attributeId | – | CHOICE | c:m | | | +| | 3.1.2.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.6 | | | +| | 3.1.2.1.2 | localForm | – | INTEGER | c:o.6 | | | +| | 3.1.2.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 3.1.3 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 3.1.4 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 3.1.4.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 3.1.4.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 3.1.4.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.1.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.1.2 | value | – | ANY | c:m | | | +| | 3.1.4.2.2 | nonSpecificForm | – | OCTET STRING | c:o.7 | | | +| | 3.1.4.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.7 | | | +| | 3.1.4.2.3.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 3.1.4.2.3.2 | value | – | ANY | c:m | | | +| | 3.1.5 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 3.1.6 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 3.1.6.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|---------------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| | 3.1.6.2 | significance | – | BOOLEAN | c:o | | | +| | 3.1.6.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 4 | 4.1 | AlarmInfo | | Information Syntax
SEQUENCE | m | | | +| | 4.1.1 | probableCause | {2 9 3 2 7 18} | CHOICE | m | | | +| | 4.1.1.1 | globalValue | – | OBJECT IDENTIFIER | o.8 | | | +| | 4.1.1.2 | localValue | – | INTEGER | o.8 | | | +| | 4.1.2 | specificProblems | {2 9 3 2 7 27} | SET OF OBJECT IDENTIFIER | o | | | +| | 4.1.3 | perceivedSeverity | {2 9 3 2 7 17} | ENUMERATED | m | | | +| | 4.1.4 | backedUpStatus | {2 9 3 2 7 11} | BOOLEAN | o | | | +| | 4.1.5 | backUpObject | {2 9 3 2 7 40} | CHOICE | o | | | +| | 4.1.5.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.9 | | | +| | 4.1.5.1.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.1.2 | value | – | ANY | c:m | | | +| | 4.1.5.2 | nonSpecificForm | – | OCTET STRING | c:o.9 | | | +| | 4.1.5.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.9 | | | +| | 4.1.5.3.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.5.3.2 | value | – | ANY | c:m | | | +| | 4.1.6 | trendIndication | {2 9 3 2 7 30} | ENUMERATED | o | | | +| | 4.1.7 | thresholdInfo | {2 9 3 2 7 29} | SEQUENCE | o | | | +| | 4.1.7.1 | triggeredThreshold | – | CHOICE | c:m | | | +| | 4.1.7.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.10 | | | +| | 4.1.7.1.2 | localForm | – | INTEGER | c:o.10 | | | +| | 4.1.7.2 | observedValue | – | CHOICE | c:m | | | +| | 4.1.7.2.1 | integer | – | INTEGER | c:o.11 | | | +| | 4.1.7.2.2 | real | – | REAL | c:o.11 | | | +| | 4.1.7.3 | thresholdLevel | – | CHOICE | c:o | | | +| | 4.1.7.3.1 | up | – | SEQUENCE | c:o.12 | | | +| | 4.1.7.3.1.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.1.1.1 | integer | – | INTEGER | c:o.13 | | | +| | 4.1.7.3.1.1.2 | real | – | REAL | c:o.13 | | | +| | 4.1.7.3.1.2 | low | – | CHOICE | c:o | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|---------------|-------------------------------|--------------------------------------------------------------------|-----------------------------|--------|---------|------------------------| +| | 4.1.7.3.1.2.1 | integer | – | INTEGER | c:o.14 | | | +| | 4.1.7.3.1.2.2 | real | – | REAL | c:o.14 | | | +| | 4.1.7.3.2 | down | – | SEQUENCE | c:o.12 | | | +| | 4.1.7.3.2.1 | high | – | CHOICE | c:m | | | +| | 4.1.7.3.2.1.1 | integer | – | INTEGER | c:o.15 | | | +| | 4.1.7.3.2.1.2 | real | – | REAL | c:o.15 | | | +| | 4.1.7.3.2.2 | low | – | CHOICE | c:m | | | +| | 4.1.7.3.2.2.1 | integer | – | INTEGER | c:o.16 | | | +| | 4.1.7.3.2.2.2 | real | – | REAL | c:o.16 | | | +| | 4.1.7.4 | armTime | – | GeneralizedTime | c:o | | | +| | 4.1.8 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 4.1.9 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 4.1.9.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 4.1.9.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 4.1.9.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.17 | | | +| | 4.1.9.2.1.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.1.2 | value | – | ANY | c:m | | | +| | 4.1.9.2.2 | nonSpecificForm | – | OCTET STRING | c:o.17 | | | +| | 4.1.9.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.17 | | | +| | 4.1.9.2.3.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.9.2.3.2 | value | – | ANY | c:m | | | +| | 4.1.10 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | o | | | +| | 4.1.10.1 | attributeID | – | CHOICE | c:m | | | +| | 4.1.10.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.18 | | | +| | 4.1.10.1.2 | localForm | – | INTEGER | c:o.18 | | | +| | 4.1.10.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | c:o | | | +| | 4.1.10.3 | newAttributeValue | – | ANY DEFINED BY attributeID | c:m | | | +| | 4.1.11 | monitoredAttributes | {2 9 3 2 7 15} | SET OF SEQUENCE | o | | | +| | 4.1.11.1 | attributeId | – | CHOICE | c:m | | | +| | 4.1.11.1.1 | globalForm | – | OBJECT IDENTIFIER | c:o.19 | | | +| | 4.1.11.1.2 | localForm | – | INTEGER | c:o.19 | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|------------------------------------|--------|---------|------------------------| +| | 4.1.11.2 | attributeValue | – | ANY DEFINED BY attributeId | c:m | | | +| | 4.1.12 | proposedRepairActions | {2 9 3 2 7 19} | SET OF OBJECT IDENTIFIER | o | | | +| | 4.1.13 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 4.1.14 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 4.1.14.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 4.1.14.2 | significance | – | BOOLEAN | c:o | | | +| | 4.1.14.3 | information | – | ANY DEFINED BY identifier | c:m | | | +| 5 | 5.1 | StateChangeInfo | | Information Syntax SEQUENCE | m | | | +| | 5.1.1 | sourceIndicator | {2 9 3 2 7 26} | ENUMERATED | o | | | +| | 5.1.2 | attributeIdentifierList | {2 9 3 2 7 8} | SET OF CHOICE | o | | | +| | 5.1.2.1 | globalForm | – | OBJECT IDENTIFIER | c:o.20 | | | +| | 5.1.2.2 | localForm | – | INTEGER | c:o.20 | | | +| | 5.1.3 | stateChangeDefinition | {2 9 3 2 7 28} | SET OF SEQUENCE | m | | | +| | 5.1.3.1 | attributeID | – | CHOICE | m | | | +| | 5.1.3.1.1 | globalForm | – | OBJECT IDENTIFIER | o.21 | | | +| | 5.1.3.1.2 | localForm | – | INTEGER | o.21 | | | +| | 5.1.3.2 | oldAttributeValue | – | ANY DEFINED BY attributeID | o | | | +| | 5.1.3.3 | newAttributeValue | – | ANY DEFINED BY attributeID | m | | | +| | 5.1.4 | notificationIdentifier | {2 9 3 2 7 16} | INTEGER | o | | | +| | 5.1.5 | correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | o | | | +| | 5.1.5.1 | correlatedNotifications | {2 9 3 2 7 12} | SET OF INTEGER | c:m | | | +| | 5.1.5.2 | sourceObjectInst | – | CHOICE | c:o | | | +| | 5.1.5.2.1 | distinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.22 | | | +| | 5.1.5.2.1.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.5.2.1.2 | value | – | ANY | c:m | | | +| | 5.1.5.2.2 | nonSpecificForm | – | OCTET STRING | c:o.22 | | | +| | 5.1.5.2.3 | localDistinguishedName | – | SEQUENCE OF SET OF SEQUENCE | c:o.22 | | | + +**Table A.1.7 – callPerformanceLog Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-------------|-------------------------------|--------------------------------------------------------------------|---------------------------|--------|---------|------------------------| +| | 5.1.5.2.3.1 | type | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.5.2.3.2 | value | – | ANY | c:m | | | +| | 5.1.6 | additionalText | {2 9 3 2 7 7} | GraphicString | o | | | +| | 5.1.7 | additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | o | | | +| | 5.1.7.1 | identifier | – | OBJECT IDENTIFIER | c:m | | | +| | 5.1.7.2 | significance | – | BOOLEAN | c:o | | | +| | 5.1.7.3 | information | – | ANY DEFINED BY identifier | c:m | | | + +**Table A.1.8 – callPerformanceLog Parameter support** + +There are no parameters specified for this managed object class. + +**Table A.1.9 – callPerformanceLog Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 1.3/2 THEN m ELSE – | "any of the scheduling packages (duration, weekly scheduling, external) are present. The presence of this package makes available the off-duty value of the available status attribute to the object." | +| c2 | IF 1.3/4 THEN m ELSE – | "both the weekly scheduling package and external scheduler packages are not present in an instance and daily scheduling is supported by that instance." | +| c3 | IF 1.3/5 THEN m ELSE – | "the logging function is scheduled to start at a specified time and stop at either a specified time or function continuously." | +| c4 | IF 1.3/6 THEN m ELSE – | "both the daily scheduling package and weekly scheduling packages are not present in an instance and external scheduling is supported by that instance." | +| c5 | IF 1.3/8 THEN m ELSE – | "a log is of finite size and halts logging when the availability status has the log full value." | +| c6 | IF 1.3/10 THEN m ELSE – | "any registered package, other than this package, has been instantiated" | +| c7 | IF 1.3/12 THEN m ELSE – | "both the daily scheduling package and external scheduler packages are not present in an instance and weekly scheduling is supported by that instance." | + +**Table A.1.10 – callPerformanceLog Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------------------|---------------------------------------------|----------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | callPerformanceLog-monitoredAccess | {0 0 13 3650 0 6 1} | Superior class:
monitoredAccess
AND SUBCLASSES | o | | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
log-system | {2 9 3 2 6 2} | Superior class:
"CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
system
AND SUBCLASSES | o | | | + +**Table A.1.10 – callPerformanceLog Name Binding support (concluded)** + +| Index | Subindex | Operation | Constraints and values | Status | Support | Additional information | +|-------|----------|---------------------------------------|------------------------|--------|---------|------------------------| +| 1 | 1.1 | Create support | | c:m | | | +| | 1.2 | Create with reference object | | c:m | | | +| | 1.3 | Create with automatic instance naming | | c:m | | | +| | 1.4 | Delete support | | c:m | | | +| | 1.5 | Delete only if no contained objects | | c:x | | | +| | 1.6 | Delete contained objects | | c:m | | | +| 2 | 2.1 | Create support | | c:m | | | +| | 2.2 | Create with reference object | | c:m | | | +| | 2.3 | Create with automatic instance naming | | c:m | | | +| | 2.4 | Delete support | | c:m | | | +| | 2.5 | Delete only if no contained objects | | c:m | | | +| | 2.6 | Delete contained objects | | c:x | | | + +### A.2 layer1PerformanceLogRecord + +**Table A.2.1 – layer1PerformanceLogRecord Managed object class support** + +| Index | Managed object class template label | Value of object identifier for class | Support of all mandatory features? (Y/N) | Is the actual class the same as the managed object class to which conformance is claimed? (Y/N) | +|-------|-------------------------------------|--------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------| +| 1 | layer1PerformanceLogRecord | {0 0 13 3650 0 3 2} | | | + +**Table A.2.2 – layer1PerformanceLogRecord Actual class support** + +| Index | Managed object class template for actual class | Value of object identifier for managed object class definition of actual class | Additional information | +|-------|------------------------------------------------|--------------------------------------------------------------------------------|------------------------| +| | | | | +| | | | | + +**Table A.2.3 – layer1PerformanceLogRecord Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalInformation Package | {2 9 3 2 4 18} | "the Additional information parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | c1 | | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalTextPackage | {2 9 3 2 4 19} | "the Additional text parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | c2 | | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": correlatedNotifications Package | {2 9 3 2 4 23} | "the correlatedNotifications parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | c3 | | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventLogRecordPackage | | Mandatory | m | | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventTimePackage | {2 9 3 2 4 11} | "the event time parameter was present in the received event report" | c4 | | | +| 7 | layer1PerformanceLogRecord-package | {0 0 13 3650 0 4 2} | Mandatory | m | | | +| 8 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logRecordPackage | | Mandatory | m | | | +| 9 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": notificationIdentifier Package | {2 9 3 2 4 24} | "the notification Identifier parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | c5 | | | + +**Table A.2.3 – layer1PerformanceLogRecord Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------|--------|---------|------------------------| +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package, has been instantiated" | c6 | | | +| 11 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | + +**Table A.2.4 – layer1PerformanceLogRecord Attribute support** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|--------------------------------------------------------------------------------|------------------------------------------|------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | – | | c1 | | – | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
additionalText | {2 9 3 2 7 7} | GraphicString | – | | c2 | | – | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | – | | c3 | | – | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
eventTime | {2 9 3 2 7 13} | GeneralizedTime | – | | c4 | | – | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
eventType | {2 9 3 2 7 14} | CHOICE | – | | m | | – | | +| 7 | layer1AccessDelay | {0 0 13 3650 0 7 8} | SEQUENCE | – | | m | | – | | +| 8 | layer1AccessDependability | {0 0 13 3650 0 7 9} | ENUMERATED | – | | m | | – | | +| 9 | layer1InformationTransfer Dependability | {0 0 13 3650 0 7 10} | ENUMERATED | – | | m | | – | | +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
logRecordId | {2 9 3 2 7 3} | CHOICE | – | | m | | – | | + +**Table A.2.4 – layer1PerformanceLogRecord Attribute support (continued)** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|----------------------------------------------------------------------------|------------------------------------------|--------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 11 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": loggingTime | {2 9 3 2 7 59} | GeneralizedTime | – | | m | | – | | +| 12 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": managedObjectClass | {2 9 3 2 7 60} | CHOICE | – | | m | | – | | +| 13 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": managedObjectInstance | {2 9 3 2 7 61} | CHOICE | – | | m | | – | | +| 14 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 15 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": notificationIdentifier | {2 9 3 2 7 16} | INTEGER | – | | c5 | | – | | +| 16 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 17 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c6 | | – | | +| 18 | typeOfCall | {0 0 13 3650 0 7 20} | ENUMERATED | – | | m | | – | | + +**Table A.2.4 – layer1PerformanceLogRecord Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | + +**Table A.2.4 – layer1PerformanceLogRecord Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | + +**Table A.2.5 – layer1PerformanceLogRecord Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table A.2.6 – layer1PerformanceLogRecord Action support** + +There are no actions specified for this managed object class. + +**Table A.2.7 – layer1PerformanceLogRecord Notification support** + +There are no notifications specified for this managed object class. + +**Table A.2.8 – layer1PerformanceLogRecord Parameter support** + +There are no parameters specified for this managed object class. + +**Table A.2.9 – layer1PerformanceLogRecord Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 2.3/1 THEN m ELSE – | "the Additional information parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | +| c2 | IF 2.3/2 THEN m ELSE – | "the Additional text parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | +| c3 | IF 2.3/4 THEN m ELSE – | "the correlatedNotifications parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | +| c4 | IF 2.3/6 THEN m ELSE – | "the event time parameter was present in the received event report" | +| c5 | IF 2.3/9 THEN m ELSE – | "the notification Identifier parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | +| c6 | IF 2.3/10 THEN m ELSE – | "any registered package, other than this package has been instantiated" | + +**Table A.2.10 – layer1PerformanceLogRecord Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
logRecord-log | {2 9 3 2 6 3} | Superior class:
"CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
log
AND SUBCLASSES | o | | | + +**Table A.2.10 – layer1PerformanceLogRecord Name Binding support (concluded)** + +| Index | Subindex | Operation | Constraints and values | Status | Support | Additional information | +|-------|----------|---------------------------------------|------------------------|--------|---------|------------------------| +| 1 | 1.1 | Create support | | – | | | +| | 1.2 | Create with reference object | | – | | | +| | 1.3 | Create with automatic instance naming | | – | | | +| | 1.4 | Delete support | | c:m | | | +| | 1.5 | Delete only if no contained objects | | c:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +### A.3 layer2PerformanceLogRecord + +**Table A.3.1 – layer2PerformanceLogRecord Managed object class support** + +| Index | Managed object class template label | Value of object identifier for class | Support of all mandatory features? (Y/N) | Is the actual class the same as the managed object class to which conformance is claimed? (Y/N) | +|-------|-------------------------------------|--------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------| +| 1 | layer2PerformanceLogRecord | {0 0 13 3650 0 3 3} | | | + +**Table A.3.2 – layer2PerformanceLogRecord Actual class support** + +| Index | Managed object class template for actual class | Value of object identifier for managed object class definition of actual class | Additional information | +|-------|------------------------------------------------|--------------------------------------------------------------------------------|------------------------| +| | | | | +| | | | | + +**Table A.3.3 – layer2PerformanceLogRecord Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
additionalInformationPackage | {2 9 3 2 4 18} | "the Additional information parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | c1 | | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
additionalTextPackage | {2 9 3 2 4 19} | "the Additional text parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | c2 | | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
correlatedNotificationsPackage | {2 9 3 2 4 23} | "the correlatedNotifications parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | c3 | | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
eventLogRecordPackage | | Mandatory | m | | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
eventTimePackage | {2 9 3 2 4 11} | "the event time parameter was present in the received event report" | c4 | | | +| 7 | layer2PerformanceLogRecord-package | {0 0 13 3650 0 4 4} | Mandatory | m | | | +| 8 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
logRecordPackage | | Mandatory | m | | | +| 9 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
notificationIdentifierPackage | {2 9 3 2 4 24} | "the notification Identifier parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | c5 | | | +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package, has been instantiated" | c6 | | | +| 11 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
topPackage | | Mandatory | m | | | + +**Table A.3.4 – layer2PerformanceLogRecord Attribute support** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|-----------------------------------------------------------------------------|------------------------------------------|------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | – | | c1 | | – | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalText | {2 9 3 2 7 7} | GraphicString | – | | c2 | | – | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | – | | c3 | | – | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventTime | {2 9 3 2 7 13} | GeneralizedTime | – | | c4 | | – | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventType | {2 9 3 2 7 14} | CHOICE | – | | m | | – | | +| 7 | layer2AccessDelay | {0 0 13 3650 0 7 11} | SEQUENCE | – | | m | | – | | +| 8 | layer2AccessDependability | {0 0 13 3650 0 7 12} | ENUMERATED | – | | m | | – | | +| 9 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logRecordId | {2 9 3 2 7 3} | CHOICE | – | | m | | – | | +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": loggingTime | {2 9 3 2 7 59} | GeneralizedTime | – | | m | | – | | +| 11 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": managedObjectClass | {2 9 3 2 7 60} | CHOICE | – | | m | | – | | +| 12 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": managedObjectInstance | {2 9 3 2 7 61} | CHOICE | – | | m | | – | | +| 13 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | + +**Table A.3.4 – layer2PerformanceLogRecord Attribute support (continued)** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|----------------------------------------------------------------------------|------------------------------------------|--------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 14 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": notificationIdentifier | {2 9 3 2 7 16} | INTEGER | – | | c5 | | – | | +| 15 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 16 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c6 | | – | | +| 17 | typeOfCall | {0 0 13 3650 0 7 20} | ENUMERATED | – | | m | | – | | + +**Table A.3.4 – layer2PerformanceLogRecord Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | + +**Table A.3.5 – layer2PerformanceLogRecord Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table A.3.6 – layer2PerformanceLogRecord Action support** + +There are no actions specified for this managed object class. + +**Table A.3.7 – layer2PerformanceLogRecord Notification support** + +There are no notifications specified for this managed object class. + +**Table A.3.8 – layer2PerformanceLogRecord Parameter support** + +There are no parameters specified for this managed object class. + +**Table A.3.9 – layer2PerformanceLogRecord Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 3.3/1 THEN m ELSE – | "the Additional information parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | +| c2 | IF 3.3/2 THEN m ELSE – | "the Additional text parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | +| c3 | IF 3.3/4 THEN m ELSE – | "the correlatedNotifications parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | +| c4 | IF 3.3/6 THEN m ELSE – | "the event time parameter was present in the received event report" | +| c5 | IF 3.3/9 THEN m ELSE – | "the notification Identifier parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | +| c6 | IF 3.3/10 THEN m ELSE – | "any registered package, other than this package, has been instantiated" | + +**Table A.3.10 – layer2PerformanceLogRecord Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
logRecord-log | {2 9 3 2 6 3} | Superior class:
"CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
log
AND SUBCLASSES | o | | | + +**Table A.3.10 – layer2PerformanceLogRecord Name Binding support (concluded)** + +| Index | Subindex | Operation | Constraints and values | Status | Support | Additional information | +|-------|----------|---------------------------------------|------------------------|--------|---------|------------------------| +| 1 | 1.1 | Create support | | – | | | +| | 1.2 | Create with reference object | | – | | | +| | 1.3 | Create with automatic instance naming | | – | | | +| | 1.4 | Delete support | | c:m | | | +| | 1.5 | Delete only if no contained objects | | c:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +### A.4 layer3PerformanceLogRecord + +**Table A.4.1 – layer3PerformanceLogRecord Managed object class support** + +| Index | Managed object class template label | Value of object identifier for class | Support of all mandatory features? (Y/N) | Is the actual class the same as the managed object class to which conformance is claimed? (Y/N) | +|-------|-------------------------------------|--------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------| +| 1 | layer3PerformanceLogRecord | {0 0 13 3650 0 3 4} | | | + +**Table A.4.2 – layer3PerformanceLogRecord Actual class support** + +| Index | Managed object class template for actual class | Value of object identifier for managed object class definition of actual class | Additional information | +|-------|------------------------------------------------|--------------------------------------------------------------------------------|------------------------| +| | | | | +| | | | | + +**Table A.4.3 – layer3PerformanceLogRecord Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalInformationPackage | {2 9 3 2 4 18} | "the Additional information parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | c1 | | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalTextPackage | {2 9 3 2 4 19} | "the Additional text parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | c2 | | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | + +**Table A.4.3 – layer3PerformanceLogRecord Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|-------------------------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": correlatedNotifications Package | {2 9 3 2 4 23} | "the correlatedNotifications parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | c3 | | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventLogRecordPackage | | Mandatory | m | | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventTimePackage | {2 9 3 2 4 11} | "the event time parameter was present in the received event report" | c4 | | | +| 7 | layer3AccessDelay-package | {0 0 13 3650 0 4 6} | "The implementation supports monitoring of layer 3 access delay" | c5 | | | +| 8 | layer3AccessDependability-package | {0 0 13 3650 0 4 7} | "The implementation supports monitoring of layer 3 access dependability" | c6 | | | +| 9 | layer3DisengagementDelay-package | {0 0 13 3650 0 4 8} | "The implementation supports monitoring of layer 3 disengagement delay" | c7 | | | +| 10 | layer3Disengagement Dependability-package | {0 0 13 3650 0 4 9} | "The implementation supports monitoring of layer 3 disengagement dependability" | c8 | | | +| 11 | layer3InformationTransfer Dependability-package | {0 0 13 3650 0 4 10} | "The implementation supports monitoring of layer 3 information transfer dependability" | c9 | | | +| 12 | layer3InformationTransfer Time-package | {0 0 13 3650 0 4 11} | "The implementation supports monitoring of layer 3 information transfer time" | c10 | | | +| 13 | layer3PerformanceLog Record-package | {0 0 13 3650 0 4 12} | Mandatory | m | | | +| 14 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logRecordPackage | | Mandatory | m | | | +| 15 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": notificationIdentifier Package | {2 9 3 2 4 24} | "the notification Identifier parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | c11 | | | +| 16 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package, has been instantiated" | c12 | | | +| 17 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table A.4.4 – layer3PerformanceLogRecord Attribute support** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|-----------------------------------------------------------------------------|------------------------------------------|------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalInformation | {2 9 3 2 7 6} | SET OF SEQUENCE | – | | c1 | | – | | +| 2 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": additionalText | {2 9 3 2 7 7} | GraphicString | – | | c2 | | – | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 4 | calledNumber | {0 0 13 3650 0 7 1} | SEQUENCE | – | | m | | – | | +| 5 | calledSubaddress | {0 0 13 3650 0 7 2} | OCTET STRING | – | | m | | – | | +| 6 | callingNumber | {0 0 13 3650 0 7 3} | SEQUENCE | – | | m | | – | | +| 7 | callingSubaddress | {0 0 13 3650 0 7 4} | OCTET STRING | – | | m | | – | | +| 8 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": correlatedNotifications | {2 9 3 2 7 12} | SET OF SEQUENCE | – | | c3 | | – | | +| 9 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventTime | {2 9 3 2 7 13} | GeneralizedTime | – | | c4 | | – | | +| 10 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": eventType | {2 9 3 2 7 14} | CHOICE | – | | m | | – | | +| 11 | informationTransfer Capability | {0 0 13 3650 0 7 5} | ENUMERATED | – | | m | | – | | +| 12 | informationTransferMode | {0 0 13 3650 0 7 6} | ENUMERATED | – | | m | | – | | +| 13 | informationTransferRate | {0 0 13 3650 0 7 7} | ENUMERATED | – | | m | | – | | +| 14 | layer3AccessDelay | {0 0 13 3650 0 7 13} | SEQUENCE | – | | c5 | | – | | +| 15 | layer3AccessDependability | {0 0 13 3650 0 7 14} | ENUMERATED | – | | c6 | | – | | +| 16 | layer3DisengagementDelay | {0 0 13 3650 0 7 15} | SEQUENCE | – | | c7 | | – | | +| 17 | layer3Disengagement Dependability | {0 0 13 3650 0 7 16} | ENUMERATED | – | | c8 | | – | | +| 18 | layer3InformationTransfer Dependability | {0 0 13 3650 0 7 17} | ENUMERATED | – | | c9 | | – | | + +**Table A.4.4 – layer3PerformanceLogRecord Attribute support (continued)** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|----------------------------------------------------------------------------|------------------------------------------|--------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 19 | layer3InformationTransfer Time | {0 0 13 3650 0 7 18} | SEQUENCE | – | | c10 | | – | | +| 20 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": logRecordId | {2 9 3 2 7 3} | CHOICE | – | | m | | – | | +| 21 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": loggingTime | {2 9 3 2 7 59} | GeneralizedTime | – | | m | | – | | +| 22 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": managedObjectClass | {2 9 3 2 7 60} | CHOICE | – | | m | | – | | +| 23 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": managedObjectInstance | {2 9 3 2 7 61} | CHOICE | – | | m | | – | | +| 24 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 25 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": notificationIdentifier | {2 9 3 2 7 16} | INTEGER | – | | c11 | | – | | +| 26 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 27 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c12 | | – | | +| 28 | typeOfCall | {0 0 13 3650 0 7 20} | ENUMERATED | – | | m | | – | | + +**Table A.4.4 – layer3PerformanceLogRecord Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| | | | | | | | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | +| 7 | – | | – | | – | | | +| 8 | – | | – | | – | | | +| 9 | – | | – | | – | | | +| 10 | – | | – | | – | | | +| 11 | – | | – | | – | | | +| 12 | – | | – | | – | | | +| 13 | – | | – | | – | | | +| 14 | – | | – | | – | | | +| 15 | – | | – | | – | | | +| 16 | – | | – | | – | | | +| 17 | – | | – | | – | | | +| 18 | – | | – | | – | | | +| 19 | – | | – | | – | | | +| 20 | – | | – | | – | | | +| 21 | – | | – | | – | | | +| 22 | – | | – | | – | | | +| 23 | – | | – | | – | | | +| 24 | – | | – | | – | | | +| 25 | – | | – | | – | | | +| 26 | – | | – | | – | | | +| 27 | – | | – | | – | | | +| 28 | – | | – | | – | | | + +**Table A.4.5 – layer3PerformanceLogRecord Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table A.4.6 – layer3PerformanceLogRecord Action support** + +There are no actions specified for this managed object class. + +**Table A.4.7 – layer3PerformanceLogRecord Notification support** + +There are no notifications specified for this managed object class. + +**Table A.4.8 – layer3PerformanceLogRecord Parameter support** + +There are no parameters specified for this managed object class. + +**Table A.4.9 – layer3PerformanceLogRecord Conditions** + +| Condition number | Condition | Reference | +|------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| c1 | IF 4.3/1 THEN m ELSE – | "the Additional information parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | +| c2 | IF 4.3/2 THEN m ELSE – | "the Additional text parameter is present in the notification or report corresponding to the instance of event record or an instance of its subclasses" | +| c3 | IF 4.3/4 THEN m ELSE – | "the correlatedNotifications parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | +| c4 | IF 4.3/6 THEN m ELSE – | "the event time parameter was present in the received event report" | +| c5 | IF 4.3/7 THEN m ELSE – | "The implementation supports monitoring of layer 3 access delay" | +| c6 | IF 4.3/8 THEN m ELSE – | "The implementation supports monitoring of layer 3 access dependability" | +| c7 | IF 4.3/9 THEN m ELSE – | "The implementation supports monitoring of layer 3 disengagement delay" | +| c8 | IF 4.3/10 THEN m ELSE – | "The implementation supports monitoring of layer 3 disengagement dependability" | +| c9 | IF 4.3/11 THEN m ELSE – | "The implementation supports monitoring of layer 3 information transfer dependability" | +| c10 | IF 4.3/12 THEN m ELSE – | "The implementation supports monitoring of layer 3 information transfer time" | +| c11 | IF 4.3/15 THEN m ELSE – | "the notification Identifier parameter is present in the notification or event report corresponding to the instance of an event record or an instance of its subclasses" | +| c12 | IF 4.3/16 THEN m ELSE – | "any registered package, other than this package, has been instantiated" | + +**Table A.4.10 – layer3PerformanceLogRecord Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|----------------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
logRecord-log | {2 9 3 2 6 3} | Superior class:
"CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992":
log
AND SUBCLASSES | o | | | + +**Table A.4.10 – layer3PerformanceLogRecord Name Binding support (concluded)** + +| Index | Subindex | Operation | Constraints and values | Status | Support | Additional information | +|-------|----------|---------------------------------------|------------------------|--------|---------|------------------------| +| 1 | 1.1 | Create support | | – | | | +| | 1.2 | Create with reference object | | – | | | +| | 1.3 | Create with automatic instance naming | | – | | | +| | 1.4 | Delete support | | c:m | | | +| | 1.5 | Delete only if no contained objects | | c:m | | | +| | 1.6 | Delete contained objects | | c:x | | | + +## A.5 monitoredAccess + +**Table A.5.1 – monitoredAccess Managed object class support** + +| Index | Managed object class template label | Value of object identifier for class | Support of all mandatory features? (Y/N) | Is the actual class the same as the managed object class to which conformance is claimed? (Y/N) | +|-------|-------------------------------------|--------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------| +| 1 | monitoredAccess | {0 0 13 3650 0 3 5} | | | + +**Table A.5.2 – monitoredAccess Actual class support** + +| Index | Managed object class template for actual class | Value of object identifier for managed object class definition of actual class | Additional information | +|-------|------------------------------------------------|--------------------------------------------------------------------------------|------------------------| +| | | | | +| | | | | + +**Table A.5.3 – monitoredAccess Package support** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|------------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------|--------|---------|------------------------| +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphicPackage | {2 9 3 2 4 17} | "if an object supports allomorphism" | o | | | +| 2 | layer1Performance Notification-package | {0 0 13 3650 0 4 3} | "The implementation supports monitoring of layer 1" | c1 | | | +| 3 | layer2Performance Notification-package | {0 0 13 3650 0 4 5} | "The implementation supports monitoring of layer 2" | c2 | | | +| 4 | layer3Performance Notification-package | {0 0 13 3650 0 4 13} | "The implementation supports monitoring of layer 3" | c3 | | | + +**Table A.5.3 – monitoredAccess Package support (continued)** + +| Index | Package template label | Value of object identifier for package | Constraints and values | Status | Support | Additional information | +|-------|---------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------|--------|---------|------------------------| +| 5 | monitoredAccess-package | {0 0 13 3650 0 4 14} | Mandatory | m | | | +| 6 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packagesPackage | {2 9 3 2 4 16} | "any registered package, other than this package, has been instantiated" | c4 | | | +| 7 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": topPackage | | Mandatory | m | | | + +**Table A.5.4 – monitoredAccess Attribute support** + +| Index | Attribute template label | Value of object identifier for attribute | Constraints and values | Set by create | | Get | | Replace | | +|-------|-----------------------------------------------------------------|------------------------------------------|--------------------------|---------------|---------|--------|---------|---------|---------| +| | | | | Status | Support | Status | Support | Status | Support | +| 1 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": allomorphs | {2 9 3 2 7 50} | SET OF CHOICE | – | | o | | – | | +| 2 | monitoredAccessId | {0 0 13 3650 0 7 19} | CHOICE | – | | m | | – | | +| 3 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": nameBinding | {2 9 3 2 7 63} | OBJECT IDENTIFIER | o | | m | | – | | +| 4 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": objectClass | {2 9 3 2 7 65} | CHOICE | – | | m | | – | | +| 5 | "CCITT Rec. X.721 (1992) ISO/IEC 10165-2 : 1992": packages | {2 9 3 2 7 66} | SET OF OBJECT IDENTIFIER | o | | c4 | | – | | +| 6 | typesMonitoring | {0 0 13 3650 0 7 21} | SEQUENCE | m | | m | | m | | + +**Table A.5.4 – monitoredAccess Attribute support (concluded)** + +| Index | Add | | Remove | | Set to default | | Additional information | +|-------|--------|---------|--------|---------|----------------|---------|------------------------| +| | Status | Support | Status | Support | Status | Support | | +| 1 | – | | – | | – | | | +| 2 | – | | – | | – | | | +| 3 | – | | – | | – | | | +| 4 | – | | – | | – | | | +| 5 | – | | – | | – | | | +| 6 | – | | – | | – | | | + +**Table A.5.5 – monitoredAccess Attribute group support** + +There are no attribute groups specified for this managed object class. + +**Table A.5.6 – monitoredAccess Action support** + +| Index | Action type template label | Value of object identifier for action type | Constraints and values | Status | Support | Additional information | +|-------|----------------------------|--------------------------------------------|------------------------|--------|---------|------------------------| +| 1 | startMonitoring | {0 0 13 3650 0 9 1} | | m | | | +| 2 | stopMonitoring | {0 0 13 3650 0 9 2} | | m | | | + +**Table A.5.6 – monitoredAccess Action support (concluded)** + +| Index | Subindex | Action field name label | Constraints and values | Status | Support | Additional information | +|-------|----------|-------------------------|----------------------------------------------|--------|---------|------------------------| +| 1 | 1.1 | MonitoringTimeStamp | Information Syntax
GeneralizedTime | m | | | +| 2 | 2.1 | MonitoringTimeStamp | Information Syntax
GeneralizedTime | m | | | + +**Table A.5.7 – monitoredAccess Notification support** + +| Index | Notification type template label | Value of object identifier for notification type | Constraints and values | Status | Support | | Additional information | +|-------|----------------------------------|--------------------------------------------------|------------------------|--------|-----------|---------------|------------------------| +| | | | | | Confirmed | Non-confirmed | | +| 1 | layer1PerformanceRecorded | {0 0 13 3650 0 10 1} | | c1 | | | | +| 2 | layer2PerformanceRecorded | {0 0 13 3650 0 10 2} | | c2 | | | | +| 3 | layer3PerformanceRecorded | {0 0 13 3650 0 10 3} | | c3 | | | | + +**Table A.5.7 – monitoredAccess Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-----------|-----------------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| 1 | 1.1 | Layer1PerformanceRecorded | | Information Syntax
SEQUENCE | c1 | | | +| | 1.1.1 | typeOfCall | {0 0 13 3650 0 7 20} | ENUMERATED | c:m | | | +| | 1.1.2 | layer1AccessDelay | {0 0 13 3650 0 7 8} | SEQUENCE | c:m | | | +| | 1.1.2.1 | layer1FE1 | – | SEQUENCE | c:m | | | +| | 1.1.2.1.1 | hours | – | INTEGER | c:m | | | +| | 1.1.2.1.2 | minutes | – | INTEGER | c:m | | | +| | 1.1.2.1.3 | seconds | – | INTEGER | c:m | | | +| | 1.1.2.1.4 | milliseconds | – | INTEGER | c:m | | | +| | 1.1.2.2 | layer1FE2 | – | SEQUENCE | c:m | | | +| | 1.1.2.2.1 | hours | – | INTEGER | c:m | | | +| | 1.1.2.2.2 | minutes | – | INTEGER | c:m | | | +| | 1.1.2.2.3 | seconds | – | INTEGER | c:m | | | +| | 1.1.2.2.4 | milliseconds | – | INTEGER | c:m | | | +| | 1.1.2.3 | layer1FE3 | – | SEQUENCE | c:m | | | +| | 1.1.2.3.1 | hours | – | INTEGER | c:m | | | +| | 1.1.2.3.2 | minutes | – | INTEGER | c:m | | | +| | 1.1.2.3.3 | seconds | – | INTEGER | c:m | | | +| | 1.1.2.3.4 | milliseconds | – | INTEGER | c:m | | | +| | 1.1.2.4 | layer1FE4 | – | SEQUENCE | c:m | | | +| | 1.1.2.4.1 | hours | – | INTEGER | c:m | | | +| | 1.1.2.4.2 | minutes | – | INTEGER | c:m | | | +| | 1.1.2.4.3 | seconds | – | INTEGER | c:m | | | +| | 1.1.2.4.4 | milliseconds | – | INTEGER | c:m | | | +| | 1.1.3 | layer1AccessDependability | {0 0 13 3650 0 7 9} | ENUMERATED | c:m | | | +| | 1.1.4 | layer1InformationTransfer Dependability | {0 0 13 3650 0 7 10} | ENUMERATED | c:m | | | +| 2 | 2.1 | Layer2PerformanceRecorded | | Information Syntax
SEQUENCE | c2 | | | +| | 2.1.1 | typeOfCall | {0 0 13 3650 0 7 20} | ENUMERATED | c:m | | | +| | 2.1.2 | layer2AccessDelay | {0 0 13 3650 0 7 11} | SEQUENCE | c:m | | | +| | 2.1.2.1 | layer2SABME | – | SEQUENCE | c:m | | | +| | 2.1.2.1.1 | hours | – | INTEGER | c:m | | | +| | 2.1.2.1.2 | minutes | – | INTEGER | c:m | | | +| | 2.1.2.1.3 | seconds | – | INTEGER | c:m | | | +| | 2.1.2.1.4 | milliseconds | – | INTEGER | c:m | | | +| | 2.1.2.2 | layer2UA | – | SEQUENCE | c:m | | | + +**Table A.5.7 – monitoredAccess Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|-----------|-------------------------------|--------------------------------------------------------------------|---------------------------------------|--------|---------|------------------------| +| | 2.1.2.2.1 | hours | – | INTEGER | c:m | | | +| | 2.1.2.2.2 | minutes | – | INTEGER | c:m | | | +| | 2.1.2.2.3 | seconds | – | INTEGER | c:m | | | +| | 2.1.2.2.4 | milliseconds | – | INTEGER | c:m | | | +| | 2.1.3 | layer2AccessDependability | {0 0 13 3650 0 7 12} | ENUMERATED | c:m | | | +| 3 | 3.1 | Layer3PerformanceRecorded | | Information Syntax
SEQUENCE | c3 | | | +| | 3.1.1 | typeOfCall | {0 0 13 3650 0 7 20} | ENUMERATED | c:m | | | +| | 3.1.2 | callingNumber | {0 0 13 3650 0 7 3} | SEQUENCE | c:m | | | +| | 3.1.2.1 | countryCode | – | NumericString | c:o | | | +| | 3.1.2.2 | nationalSignificantNumber | – | SEQUENCE | c:m | | | +| | 3.1.2.2.1 | nationalDestinationNumber | – | NumericString | c:o | | | +| | 3.1.2.2.2 | subscriberNumber | – | NumericString | c:m | | | +| | 3.1.3 | calledNumber | {0 0 13 3650 0 7 1} | SEQUENCE | c:m | | | +| | 3.1.3.1 | countryCode | – | NumericString | c:o | | | +| | 3.1.3.2 | nationalSignificantNumber | – | SEQUENCE | c:m | | | +| | 3.1.3.2.1 | nationalDestinationNumber | – | NumericString | c:o | | | +| | 3.1.3.2.2 | subscriberNumber | – | NumericString | c:m | | | +| | 3.1.4 | callingSubaddress | {0 0 13 3650 0 7 4} | OCTET STRING | c:m | | | +| | 3.1.5 | calledSubaddress | {0 0 13 3650 0 7 2} | OCTET STRING | c:m | | | +| | 3.1.6 | informationTransferCapability | {0 0 13 3650 0 7 5} | ENUMERATED | c:m | | | +| | 3.1.7 | informationTransferMode | {0 0 13 3650 0 7 6} | ENUMERATED | c:m | | | +| | 3.1.8 | informationTransferRate | {0 0 13 3650 0 7 7} | ENUMERATED | c:m | | | +| | 3.1.9 | layer3AccessDelay | {0 0 13 3650 0 7 13} | SEQUENCE | c:m | | | +| | 3.1.9.1 | layer3SETUP | – | SEQUENCE | c:m | | | +| | 3.1.9.1.1 | hours | – | INTEGER | c:m | | | +| | 3.1.9.1.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.9.1.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.9.1.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.9.2 | layer3SETACK | – | SEQUENCE | c:o | | | +| | 3.1.9.2.1 | hours | – | INTEGER | c:m | | | +| | 3.1.9.2.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.9.2.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.9.2.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.9.3 | layer3INF | – | SEQUENCE | c:o | | | +| | 3.1.9.3.1 | hours | – | INTEGER | c:m | | | +| | 3.1.9.3.2 | minutes | – | INTEGER | c:m | | | + +**Table A.5.7 – monitoredAccess Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|------------|-----------------------------------------|--------------------------------------------------------------------|------------------------|--------|---------|------------------------| +| | 3.1.9.3.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.9.3.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.9.4 | layer3ALERT | – | SEQUENCE | c:o | | | +| | 3.1.9.4.1 | hours | – | INTEGER | c:m | | | +| | 3.1.9.4.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.9.4.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.9.4.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.9.5 | layer3CONNECT | – | SEQUENCE | c:o | | | +| | 3.1.9.5.1 | hours | – | INTEGER | c:m | | | +| | 3.1.9.5.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.9.5.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.9.5.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.10 | layer3AccessDependability | {0 0 13 3650 0 7 14} | ENUMERATED | c:m | | | +| | 3.1.11 | layer3InformationTransferTime | {0 0 13 3650 0 7 18} | SEQUENCE | c:m | | | +| | 3.1.11.1 | numberOfSatelliteHops | – | INTEGER | c:o | | | +| | 3.1.11.2 | propagationDelay | – | CHOICE | c:o | | | +| | 3.1.11.2.1 | days | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.2 | hours | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.3 | minutes | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.4 | seconds | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.5 | milliseconds | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.6 | microseconds | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.7 | nanoseconds | – | INTEGER | c:o.1 | | | +| | 3.1.11.2.8 | picoseconds | – | INTEGER | c:o.1 | | | +| | 3.1.12 | layer3InformationTransfer Dependability | {0 0 13 3650 0 7 17} | ENUMERATED | c:m | | | +| | 3.1.13 | layer3DisengagementDelay | {0 0 13 3650 0 7 15} | SEQUENCE | c:m | | | +| | 3.1.13.1 | layer3DISCONNECT | – | SEQUENCE | c:m | | | +| | 3.1.13.1.1 | hours | – | INTEGER | c:m | | | +| | 3.1.13.1.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.13.1.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.13.1.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.13.2 | layer3RELEASE | – | SEQUENCE | c:m | | | +| | 3.1.13.2.1 | hours | – | INTEGER | c:m | | | +| | 3.1.13.2.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.13.2.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.13.2.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.13.3 | layer3RELCOMP | – | SEQUENCE | c:m | | | + +**Table A.5.7 – monitoredAccess Notification support (concluded)** + +| Index | Subindex | Notification field name label | Value of object identifier of attribute type associated with field | Constraints and values | Status | Support | Additional information | +|-------|------------|-----------------------------------|--------------------------------------------------------------------|------------------------|--------|---------|------------------------| +| | 3.1.13.3.1 | hours | – | INTEGER | c:m | | | +| | 3.1.13.3.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.13.3.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.13.3.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.13.4 | bChannelFree | – | SEQUENCE | c:m | | | +| | 3.1.13.4.1 | hours | – | INTEGER | c:m | | | +| | 3.1.13.4.2 | minutes | – | INTEGER | c:m | | | +| | 3.1.13.4.3 | seconds | – | INTEGER | c:m | | | +| | 3.1.13.4.4 | milliseconds | – | INTEGER | c:m | | | +| | 3.1.14 | layer3Disengagement Dependability | {0 0 13 3650 0 7 16} | ENUMERATED | c:m | | | + +**Table A.5.8 – monitoredAccess Parameter support** + +There are no parameters specified for this managed object class. + +**Table A.5.9 – monitoredAccess Conditions** + +| Condition number | Condition | Reference | +|------------------|------------------------|--------------------------------------------------------------------------| +| c1 | IF 5.3/2 THEN m ELSE – | "The implementation supports monitoring of layer 1" | +| c2 | IF 5.3/3 THEN m ELSE – | "The implementation supports monitoring of layer 2" | +| c3 | IF 5.3/4 THEN m ELSE – | "The implementation supports monitoring of layer 3" | +| c4 | IF 5.3/6 THEN m ELSE – | "any registered package, other than this package, has been instantiated" | + +**Table A.5.10 – monitoredAccess Name Binding support** + +| Index | Name binding template label | Value of object identifier for name binding | Constraints and values | Status | Support | Additional information | +|-------|--------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------|--------|---------|------------------------| +| 1 | monitoredAccess-accessPortISDN | {0 0 13 3650 0 6 2} | Superior class:
"Recommendation Q.824.1:1995":
accessPort
AND SUBCLASSES | o | | | +| 2 | monitoredAccess-dChannel | {0 0 13 3650 0 6 3} | Superior class:
"Recommendation Q.824.1:1995":
dChannel
AND SUBCLASSES | o | | | + +**Table A.5.10 – monitoredAccess Name Binding support (concluded)** + +| Index | Subindex | Operation | Constraints and values | Status | Support | Additional information | +|-------|----------|---------------------------------------|------------------------|--------|---------|------------------------| +| 1 | 1.1 | Create support | | c:m | | | +| | 1.2 | Create with reference object | | c:m | | | +| | 1.3 | Create with automatic instance naming | | c:m | | | +| | 1.4 | Delete support | | c:m | | | +| | 1.5 | Delete only if no contained objects | | c:x | | | +| | 1.6 | Delete contained objects | | c:m | | | +| 2 | 2.1 | Create support | | c:m | | | +| | 2.2 | Create with reference object | | c:m | | | +| | 2.3 | Create with automatic instance naming | | c:m | | | +| | 2.4 | Delete support | | c:m | | | +| | 2.5 | Delete only if no contained objects | | c:x | | | +| | 2.6 | Delete contained objects | | c:m | | | + +# ANNEX B + +## Network management level + +At this moment, it is not feasible to relate measurements at the originating and destination LEXs to one call at the network management layer. The main problem is that there is no end-to-end call identifier for ISDN calls. + +Here, two methods are given for relating measurements at the originating and destination LEXs. They are not standardized in this Recommendation, because of their complexity: + +- 1) tracing the call, by consulting all network nodes involved; +- 2) use the combinations of called and calling party numbers together with the time stamps. + +## ITU-T RECOMMENDATIONS SERIES + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of the ITU-T | +| Series B | Means of expression: definitions, symbols, classification | +| Series C | General telecommunication statistics | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks and open system communication | +| Series Z | Programming languages | \ No newline at end of file diff --git a/marked/M/T-REC-M.3660-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3660-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..608a8ace64d7ac6b15aab685f0c1f028ef62aa71 --- /dev/null +++ b/marked/M/T-REC-M.3660-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da624c99115246a268e57d35487fc55ab0093615b64cbe2daae789be4dccaa96 +size 8199 diff --git a/marked/M/T-REC-M.3660-199210-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg b/marked/M/T-REC-M.3660-199210-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c22881259c2338ee9a757766d7ccb44964ead7f5 --- /dev/null +++ b/marked/M/T-REC-M.3660-199210-I_PDF-E/690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1d03d1e83524f1dd6ef0210e5dcccf5be3a39650b3228ef1c3ae17e48629898 +size 54584 diff --git a/marked/M/T-REC-M.3660-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.3660-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29da708df095cac2ba086329ae10380b0f865fbe --- /dev/null +++ b/marked/M/T-REC-M.3660-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6430a6c6837158889925575ded6e7fd027a44739a4d0d1302fe07d8beee985aa +size 5924 diff --git a/marked/M/T-REC-M.3700-201001-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/M/T-REC-M.3700-201001-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d9c40a68ca7d07b0c8d39701b0bf6d3d0814b7 --- /dev/null +++ b/marked/M/T-REC-M.3700-201001-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:785b8bc0b7b9c8eb94f94ae79dd083e06f9fc4df6adaaafb5606185f0a709d60 +size 48006 diff --git a/marked/M/T-REC-M.3700-201001-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3700-201001-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0fb86bed5c15f945554d480f5198abb401cd4b4 --- /dev/null +++ b/marked/M/T-REC-M.3700-201001-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0433bfe9212db0be4acb1b5d1b8a39f72024b5355444ed641c1e1a1d5da63e5 +size 52308 diff --git a/marked/M/T-REC-M.3700-201001-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3700-201001-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7891ad4da866f8afa77ca25dc85476b390f8447 --- /dev/null +++ b/marked/M/T-REC-M.3700-201001-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a02d9c72e32cfb302c5fd9b64b961d1940f565b2e5e663e9ed88d0336be29b1 +size 7391 diff --git a/marked/M/T-REC-M.3700-201001-I_PDF-E/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg b/marked/M/T-REC-M.3700-201001-I_PDF-E/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16802da4541b94ab5eafa8ff9df58ae82e6ccefa --- /dev/null +++ b/marked/M/T-REC-M.3700-201001-I_PDF-E/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b269abe4fb1e2f8a81903a7458a0358927ea7d5858f7298699a86beed971ef5b +size 26429 diff --git a/marked/M/T-REC-M.3700-201001-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/M/T-REC-M.3700-201001-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eeb5a0ec57e5c97abe52af30f3e58a2ae20ed5f --- /dev/null +++ b/marked/M/T-REC-M.3700-201001-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d528ca3465f0a827b8a7237fdc0f1f2d6ac984b98fa39afef7783c9f9ef6b6fd +size 28990 diff --git a/marked/M/T-REC-M.3700-201001-I_PDF-E/raw.md b/marked/M/T-REC-M.3700-201001-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0e5b2e4a85b4e9c2b7324ed863d7af82783c6a80 --- /dev/null +++ b/marked/M/T-REC-M.3700-201001-I_PDF-E/raw.md @@ -0,0 +1,799 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3700** + +(01/2010) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Integrated services digital networks + +--- + +**Common management services – Object +management – Protocol neutral requirements +and analysis** + +Recommendation ITU-T M.3700 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, and the text "ITU International Telecommunication Union" to the right. + +ITU logo + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## **Recommendation ITU-T M.3700** + +## **Common management services – Object management – Protocol neutral requirements and analysis** + +## **Summary** + +Recommendation ITU-T M.3700 provides the requirements and analysis for one of the common management services – object management. The object management capabilities are intended for re-use by specific information object classes (IOCs). + +## **History** + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3700 | 2010-01-13 | 2 | + +## **Keywords** + +Common management service, object management. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2010 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## CONTENTS + +| | Page | +|---------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Requirements ..... | 2 | +| 6.1 Business level requirements ..... | 2 | +| 7 Analysis ..... | 8 | +| 7.1 System context..... | 8 | +| 7.2 Information object classes ..... | 9 | +| 7.3 Interface definition ..... | 9 | +| Bibliography..... | 25 | + + + +## Recommendation ITU-T M.3700 + +## Common management services – Object management – Protocol neutral requirements and analysis + +# 1 Scope + +This Recommendation defines the requirements for basic object management, including retrieve object information, create object, delete object, modify object attribute, cancel operation, subscribe notification, receive notification, generate attribute value change notification, generate state change notification, generate object create notification, generate object delete notification. + +The operations and notifications specified in this document shall be used, where applicable, in information object class (IOC) definitions of other management interface specifications. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2009), *Management interface specification methodology*. +- [ITU-T M.3060] Recommendation ITU-T M.3060/Y.2401 (2006), *Principles for the Management of the Next Generation Networks*. +- [ITU-T M.3701] Recommendation ITU-T M.3701 (2010), *Common management services – State management – Protocol neutral requirements and analysis*. +- [ITU-T M.3702] Recommendation ITU-T M.3702 (2010), *Common management services – Notification management – Protocol neutral requirements and analysis*. +- [ITU-T X.680] Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, *Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation*. + +# 3 Definitions + +For the purposes of this Recommendation, the following terms and definitions apply. + +This Recommendation uses the following terms from [ITU-T M.3020]: + +- agent; +- association; +- data; +- manager; +- information object class (IOC). + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----|-----------------------------| +| EM | Element Manager | +| IOC | Information Object Class | +| IRP | Integration Reference Point | +| NE | Network Element | +| NM | Network Manager | +| OS | Operations System | +| UML | Unified Modelling Language | + +# 5 Conventions + +This Recommendation uses the conventions defined in [ITU-T M.3020] for requirements capture and analysis. + +# 6 Requirements + +## 6.1 Business level requirements + +### 6.1.1 Requirements + +#### 6.1.1.1 General requirements + +This service uses the following services and thus implicitly imports all the requirements defined therein: + +- notification management [ITU-T M.3702]; +- state management [ITU-T M.3701]. + +In addition, the following specific requirements apply for object management as specified in this and subsequent clauses. + +| Identifier | Definition | +|---------------|------------------------------------------------------------------------------------------------------------------------------| +| REQ-OM-FUN-01 | The object management functions shall be able to operate on any information object. | +| REQ-OM-NON-01 | The definitions of new object types may specify which object management functions are applicable. | +| REQ-OM-FUN-02 | The object management capabilities shall be independent of any specific definitions of information objects, attributes, etc. | + +#### 6.1.1.2 Information retrieval + +| Identifier | Definition | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-OM-FUN-03 | The agent will provide an operation to retrieve the value of attributes from one or more IOC instances. | +| REQ-OM-FUN-04 | An operation to retrieve the containment relationships between the IOC instances of a containment tree of information objects shall be provided. | +| REQ-OM-FUN-05 | An operation to retrieve the interface versions that are supported by the agent may be provided. | + +REQ-OM-FUN-06 An operation to cancel a previously initiated operation if it has not completed may be provided. This operation shall, as a minimum, be able to cancel the operation that retrieves attributes. It may be specified to cancel any operation. + +#### 6.1.1.3 Life cycle operations + +Life cycle operations are not intended to be implemented without implementation of the information retrieval requirements. + +##### Identifier + +##### Definition + +REQ-OM-FUN-07 An operation to create an instance of a information object shall be provided. + +REQ-OM-FUN-08 An operation to delete one or more instances of information objects shall be provided. + +REQ-OM-FUN-09 An operation to modify one or more attributes of one or more instances of information objects shall be provided. + +REQ-OM-FUN-10 A manager may subscribe to notifications about a set of object management operations: object creation, object deletion, object modification and when part or the whole configuration information should be synchronized. + +### 6.1.2 Actor roles + +The capabilities described in this Recommendation are available and relevant to all agents and managers. + +### 6.1.3 Telecommunication resources + +The object management functionality is applicable to all types of telecommunication resources. + +### 6.1.4 High-level use cases + +The first overview use-case diagram in Figure 1 shows the overall interaction of the object management function. + +![High level use case diagram for object management](9283a3f6b39120df9dc9aee4712b3a0a_img.jpg) + +The diagram illustrates the interaction of the 'Manager' actor with the 'Object management' use case. The Manager is represented by a stick figure icon on the left, with a solid horizontal arrow pointing to the 'Object management' use case. The 'Object management' use case is shown as a central oval. From this oval, two dashed arrows labeled '<>' point downwards to 'Information retrieval' and 'Life cycle operations' respectively. To the right of the 'Object management' oval, two dashed arrows labeled '<>' point to 'State management' and 'Notification management' respectively. The diagram is labeled 'M.3700(10)\_F01' in the bottom right corner. + +High level use case diagram for object management + +**Figure 1 – High level use case for object management** + +#### 6.1.4.1 Retrieve object information + +| Use-case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Goal | The agent returns to the manager attribute values from one or more information object class instances. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Telecom resources | The object management functionality is applicable to all types of telecommunication resources. | | +| Assumptions | The use case is applicable to any information object class.
One or several information objects may be retrieved – based on the containment hierarchy.
There is an open communication channel between the manager and the agent.
This general service is used to get attributes unless a specific service has been defined by one of the common management services. | | +| Pre conditions | None. | | +| Begins when | The manager sends a request to retrieve information on one or more IOC instances. | | +| Step 1 | The manager invokes the information retrieval operation on the agent. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | Cancel pending operation | +| Exceptions |
  • • operationFailed
  • • duplicateInvocation
  • • resourceLimitation
  • • operationCancelled
  • • complexityLimitation
| | +| Post conditions | None. | | +| Traceability | REQ-OM-FUN-01, REQ-OM-FUN-03, REQ-OM-FUN-04, REQ-OM-FUN-05 | | + +#### 6.1.4.2 Cancel pending operation + +| Use-case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager invokes this operation to cancel an on-going operation it issued before. | | +| Actor and roles | The manager invokes the cancel operation on the agent. | | +| Telecom resources | The object management functionality is applicable to all types of telecommunication resources. | | + +| Use-case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Assumptions | The use case is applicable when specified by the relevant information object, Ref. REQ-OM-FUN-01.
The previous operation is either already being processed or waiting for processing by the agent.
There is an open communication channel between the manager and the agent. | | +| Pre conditions | The previous operation invoked by this manager has not been completed. | | +| Begins when | The manager sends a request to cancel a previously issued operation. | | +| Step 1 | The manager invokes the cancel operation on the agent. | | +| Ends when | The requested operation is cancelled or an exception is returned to the manager. | | +| Exceptions |
  • operationFailed
| | +| Post conditions | The operation identified by the operation is cancelled. | | +| Traceability | REQ-OM-FUN-06 | | + +#### 6.1.4.3 Create object + +| Use-case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | This operation is invoked by the manager to request the agent to create a Information object class instance in the MIB maintained by the agent. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecom resources | The object management functionality is applicable to all types of telecommunication resources. | | +| Assumptions | The use case is applicable when specified by the relevant information object, Ref. REQ-OM-FUN-01.
This operation will create only one IOC instance.
There is an open communication channel between the manager and the agent. | | +| Pre conditions | A IOC instance with the same distinguished name as the object specified for creation does not exist. | | +| Begins when | The manager sends a request to create a IOC instance in the MIB maintained by the agent. | | +| Step 1 | The manager invokes the create information object operation on the agent. | | +| Ends when | The requested IOC instance is created or an exception is returned to the manager. | | + +| Use-case stage | Evolution/Specification | <>
Related use | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions |
  • • operationFailed
  • • objectClassSpecificationMismatch
  • • invalidObjectInstance
  • • createNotAllowed
  • • noSuchObjectClass
  • • classInstanceConflict
  • • noSuchAttribute
  • • invalidAttributeValue
  • • missingAttributeValue
  • • parentObjectDoesNotExist
  • • objectExists
| | +| Post conditions |

a) The IOC instance of the specified object class has been created with the specified distinguished name.

b) An object creation notification is emitted for the created object, if notifiable. Notifiable means here that the notification is supported and not suppressed.

| | +| Traceability | REQ-OM-FUN-07 | | + +#### 6.1.4.4 Delete object + +| Use-case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | This operation is invoked by the manager to request the deletion of one or more information object class instances from the MIB maintained by the agent. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecom resources | The object management functionality is applicable to all types of telecommunication resources. | | +| Assumptions |

The use case is applicable when specified by the relevant information object, Ref. REQ-OM-FUN-01.

This operation will delete one or more IOC instances.

There is an open communication channel between the manager and the agent.

| | +| Pre conditions |

a) The IOC instances specified in the operation exists.

b) For any IOC instance specified for deletion, all of its IOC instances must be specified for deletion.

| | +| Begins when | The manager sends a request to delete one or more IOC instances in the MIB maintained by the agent. | | +| Step 1 | The manager invokes the delete information object operation on the agent. | | +| Ends when | The requested IOC instance(s) are deleted or an exception is returned to the manager. | | + +| Use-case stage | Evolution/Specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions |
  • operationFailed
  • invalidObjectInstance
  • deleteNotAllowed
  • resourceLimitation
  • complexityLimitation
| | +| Post conditions |
  • All of the IOC instances selected for deletion are deleted.
  • Some but not all of the selected instances were deleted and for any of the instances deleted all of the child instances of that instance is deleted.
  • An object deletion notification is emitted for each notifiable deleted object. Notifiable means here that the notification is supported and not suppressed. An object deletion notification of a information object containing a sub-tree implies deletion of all information objects in the sub-tree. The agent should make the best effort to reduce the number of object deletion notifications, for example by sending only one notification for the sub-tree root object in the event of a successful deletion of an entire sub-tree.
| | +| Traceability | REQ-OM-FUN-08 | | + +#### 6.1.4.5 Modify object + +| Use-case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | This operation is invoked by the manager to request the modification of management information (information object attribute values) in the MIB maintained by the agent. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecom resources | The object management functionality is applicable to all types of telecommunication resources. | | +| Assumptions |

The use case is applicable when specified by the relevant information object, Ref. REQ-OM-FUN-01.

Attributes of one or several information objects may be modified – based on the containment hierarchy.

There is an open communication channel between the manager and the agent.

| | +| Pre conditions | The IOC instance specified in the operation exists. | | +| Begins when | The manager sends a request to modify one or more IOC instance in the MIB maintained by the agent. | | +| Step 1 | The manager invokes the modify information object operation on the agent. | | +| Ends when | The requested IOC instance(s) are modified or an exception is returned to the manager. | | + +| Use-case stage | Evolution/Specification | <>
Related use | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions |
  • operationFailed
  • modifyNotAllowed
  • noSuchAttribute
  • invalidAttributeValue
  • missingAttributeValue
  • resourceLimitation
  • complexityLimitation
| | +| Post conditions |
  • All of the attributes of all of the IOC instances selected for modification are modified as specified.
  • Some attributes of some of the selected IOC instances were modified but not all attributes of all selected IOC instances.
  • An Attribute Value Change notification is emitted for the notifiable attributes of each modified object instance. Notifiable means here that the notification is supported and not suppressed.
| | +| Traceability | REQ-OM-FUN-09 | | + +#### 6.1.4.6 Subscribe for object management notification + +Notification subscription use cases are defined in [ITU-T M.3702]. + +# 7 Analysis + +## 7.1 System context + +The object management service makes use of the following common management services, as shown in Figures 2 and 3. + +![Figure 2 – System context A: A diagram showing the interaction between a Manager (in a Managing system), an Agent (in a Managed system), and Resources. The Manager and Agent are connected by a solid line. The Agent is connected to Resources by a dashed line. Below the Agent, a vertical dashed line separates the Managed system from the Object Management Service. The Object Management Service is connected to the Agent by a curved arrow pointing to a list of services: Notification Management Service and State Management Service.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram illustrates the system context for object management. On the left, a 'Manager' box is enclosed in a dashed rectangle labeled 'Managing system'. On the right, an 'Agent' box is enclosed in a dashed rectangle labeled 'Managed system'. A solid horizontal line connects the Manager and the Agent. To the right of the Agent, a dashed horizontal line connects it to a 'Resources' box. Below the Agent, a vertical dashed line acts as a boundary. To the left of this boundary is the 'Object Management Service'. A curved arrow points from the Object Management Service to a list of two services: 'Notification Management Service' and 'State Management Service'. + +Figure 2 – System context A: A diagram showing the interaction between a Manager (in a Managing system), an Agent (in a Managed system), and Resources. The Manager and Agent are connected by a solid line. The Agent is connected to Resources by a dashed line. Below the Agent, a vertical dashed line separates the Managed system from the Object Management Service. The Object Management Service is connected to the Agent by a curved arrow pointing to a list of services: Notification Management Service and State Management Service. + +Figure 2 – System context A + +![Figure 3 – System context B. A diagram showing a 'Managing system' (Manager) and a 'Managed system' (Agent, Resources). The Manager is connected to the Agent. A vertical dashed line separates the two systems. Below the line, 'Object Management Service' is listed. To the right of the line, 'Notification Management Service' and 'State Management Service' are listed. An arrow points from the Agent to the services.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Figure 3 – System context B. A diagram showing a 'Managing system' (Manager) and a 'Managed system' (Agent, Resources). The Manager is connected to the Agent. A vertical dashed line separates the two systems. Below the line, 'Object Management Service' is listed. To the right of the line, 'Notification Management Service' and 'State Management Service' are listed. An arrow points from the Agent to the services. + +Figure 3 – System context B + +## 7.2 Information object classes + +This Recommendation defines the common management function for object management. There is no information object class defined in this Recommendation. + +## 7.3 Interface definition + +### 7.3.1 Class diagram representing interfaces + +![Figure 4 – Class diagram. A class diagram showing a 'proxyClass' named 'Agent' with a realization relationship to an 'ObjectManagement' interface. The interface lists five operations: cancelOperation(), setAttributes(), getAttributes(), createObject(), and deleteObject().](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` + +classDiagram + class Agent { + <> + } + class ObjectManagement { + cancelOperation() + setAttributes() + getAttributes() + createObject() + deleteObject() + } + Agent ..|> ObjectManagement : <> + +``` + +Figure 4 – Class diagram. A class diagram showing a 'proxyClass' named 'Agent' with a realization relationship to an 'ObjectManagement' interface. The interface lists five operations: cancelOperation(), setAttributes(), getAttributes(), createObject(), and deleteObject(). + +Figure 4 – Class diagram + +### 7.3.2 Generic rules + +The following rules are relevant for all specifications. 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\_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.* + +NOTE – Security considerations and resulting generic rules are for further study. + +### 7.3.3 Interface object management (M) + +Each interface is defined by its name and by a sequence of operations or notifications, as defined below. + +| Operation name | Qualifier | Requirement IDs | +|-----------------|-----------|------------------------------------------------------------| +| getMoAttributes | M | REQ-OM-FUN-01, REQ-OM-FUN-03, REQ-OM-FUN-04, REQ-OM-FUN-05 | +| cancelOperation | O | REQ-OM-FUN-01, REQ-OM-FUN-06 | +| createObject | O | REQ-OM-FUN-01, REQ-OM-FUN-07 | +| deleteObject | O | REQ-OM-FUN-01, REQ-OM-FUN-08 | +| setMoAttributes | O | REQ-OM-FUN-01, REQ-OM-FUN-09 | + +In the following operation definitions, there is a 'status' parameter in the output parameter definitions. In total, there are 6 values enumerated, but a specific operation may support only part of them, as listed in the operation output parameters definition table. + +``` +Status ::= ENUMERATED{ + operationSucceeded, + operationFailed, + operationPartiallySucceeded, + cancelSucceeded, + operationAlreadyCompleted, + cannotCancel +} +``` + +#### 7.3.3.1 Operation getAttributes (M) + +##### 7.3.3.1.1 Definition + +This operation is invoked by manager to request the retrieval of management information (information object attribute names and values) from the MIB maintained by the agent. One or several information objects may be retrieved – based on the containment hierarchy. A design may choose to split this operation in several operations (e.g., operations to get "handlers" or "iterators" to information objects fulfilling the scope/filter criteria and other operations to retrieve attribute names/values from these "handlers"). + +##### 7.3.3.1.2 Input parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|--------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| invokeIdentifierIn | CM | INTEGER
A unique identifier that is Solution Set dependent. | This parameter identifies the current invocation. This parameter is used in the 'cancelOperation' operation to cancel an on-going 'getMOAttributes' operation. | +| baseObjectInstance | M | Name | The MO instance that is to be used as the starting point for the selection of information objects to which the filter (when supplied) is to be applied. | +| scope | O | SEQUENCE {
scopeType ENUMERATED {
base-object-only,
nTH-Level-subordinates,
base-nTH-level,
base-all
},
theLevel INTEGER
}

NOTE – The level contains valid information if nTH-Level-subordinates or base-nTH-level is used. | This parameter defines how many levels of the containment hierarchy to select for the filter defined below. The selection starts from the MO given by the baseObjectInstance parameter. The levels of selection that may be performed are:
base-object-only: the base object alone (default);
nTH-Level-subordinates: the nth level subordinates of the base object;
base-nTH-level: the base object and all of its subordinates down to and including the nth level;
base-all: the base object and all of its subordinates. | +| filter | O | See comment | This parameter defines a filter test to be applied to the scoped Information object(s). If the filter is empty, all of the information objects included by the scope are selected. The actual syntax and capabilities of the filter is solution set specific. However, each solution set should support a filter consisting of one or several assertions that may be grouped using the logical operators AND, OR and NOT. Each assertion is a logical expression of attribute existence, attribute value comparison ("equal to X, less than Y", etc.) and MO Class. | + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|-----------------|-------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attributeListIn | M | SET OF | This parameter identifies the attributes to be returned by this operation An empty list means "Return all attributes". For future releases the possibility to specify a list of attributes is expected. | + +##### 7.3.3.1.3 Output parameters + +This information is provided in a table. + +| Parameter name | Support qualifier | Matching information/Information type/Legal values | Comment | +|------------------------|-------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| invokeIdentifierOut | CM
(Note) | INTEGER
invokeIdentifierIn from the input parameters of this operation | This parameter identifies the current invocation in both IRPManager and IRPAgent. This parameter can be used together with the 'cancelOperation' operation to cancel an on-going 'getMOAttributes' operation. | +| managedObject Class | M | Name | For each returned MO: The class of the MO instance. | +| managedObject Instance | M | Name | For each returned MO: The name of the MO instance. | +| attributeListOut | M | SET OF SEQUENCE{
,

} | For each returned MO: A list of name/value pairs for MO. | +| status | M | ENUMERATED {
operationSucceeded,
operationFailed
} | An operation may fail because of a specified or unspecified reason. | + +NOTE – This parameter is meaningful only if the agent supports the cancelOperation. + +##### 7.3.3.1.4 Pre-condition + +baseObjectExists + +| Assertion Name | Definition | +|------------------|------------------------------------------------------------------------| +| baseObjectExists | The IOC instance specified by the baseObjectInstance parameter exists. | + +##### 7.3.3.1.5 Post-condition + +None specific. + +##### 7.3.3.1.6 Exceptions + +| Name | Definition | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailed | Condition: Pre-condition is false or post-condition is false.
Returned information: The output parameter status.
Exit state: Entry state. | +| duplicateInvocation | Condition: The invoke identifier specified was allocated to another operation
Returned information: The output parameter status.
Exit state: Entry state.
NOTE – This exception is conditional and applies only to designs where it is meaningful. | +| resourceLimitation | Condition: Operation not performed due to resource limitation.
Returned information: The output parameter status.
Exit state: Entry state. | +| operationCancelled | Condition: Operation cancelled by cancelOperation operation.
Returned information: The output parameter status.
Exit state: Entry state. | +| complexityLimitation | Condition: Operation not performed because a parameter was too complex.
Returned information: The output parameter status.
Exit state: Entry state. | +| baseObjectDoesNotExist | Condition: Operation not performed because the specified base object does not exist.
Returned information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.2 Operation cancelOperation (O) + +##### 7.3.3.2.1 Definition + +The manager invokes this operation to cancel an on-going operation it issued before. The set of operations that can be cancelled is specified for IOC as appropriate. + +##### 7.3.3.2.2 Input parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|--------------------|-------------------|----------------------------------------------------------------|------------------------------------------------------------------| +| invokeIdentifierIn | M | INTEGER
A unique identifier that is solution set dependent. | This parameter identifies an on-going operation to be cancelled. | + +##### 7.3.3.2.3 Output Parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|----------------|-------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| status | M | ENUMERATED {
cancelSucceeded,
operationAlreadyCompleted,
cannotCancel
} | An operation may fail because of a specified or unspecified reason. | + +##### 7.3.3.2.4 Pre-condition + +operationExits + +| Assertion name | Definition | +|----------------|----------------------------------------------------------------| +| operationExits | The operation identified by the invokeIdentifierIn is ongoing. | + +##### 7.3.3.2.5 Post-condition + +operationCancelled + +| Assertion name | Definition | +|--------------------|------------------------------------------------------------------| +| operationCancelled | The operation identified by the invokeIdentifierIn is cancelled. | + +##### 7.3.3.2.6 Exceptions + +| Name | Definition | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailed | Condition: Pre-condition is false or post-condition is false.
Returned information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.3 Operation createObject (O) + +##### 7.3.3.3.1 Definition + +This operation is invoked by the manager to request the agent to create a IOC instance in the MIB maintained by the agent. This operation will create only one IOC instance. + +##### 7.3.3.3.2 Input parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|-------------------------|-------------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| managedObjectClass | M | Name | This parameter specifies the class of the new IOC instance. | +| managedObjectInstance | M | Name | This parameter specifies the instance of the information object that is to be created and registered. | +| referenceObjectInstance | O | Name | This parameter may have a null value. When this parameter is supplied, it must specify an existing instance of a information object, called the reference object, of the same class as the new object to be created. Attribute values associated with the reference object instance become the default values for those not specified by the attributeListIn parameter. | + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|-----------------|-------------------|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attributeListIn | M | SET OF SEQUENCE{
,

} | This parameter may have a null value. When this parameter is supplied, it contains a list of name/value pairs specifying attribute identifiers and their values to be assigned to the new information object. These values override the values for the corresponding attributes derived from either the reference object (if the referenceObjectInstance parameter is supplied) or the default value set specified in the definition of the information object's class. | + +##### 7.3.3.3.3 Output parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|------------------|-------------------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| attributeListOut | M | SET OF SEQUENCE{
,

} | This list of name/value pairs contains the attributes of the new information object and the actual value assigned to each. | +| status | M | ENUMERATED {
operationSucceeded,
operationFailed
} | An operation may fail because of a specified or unspecified reason. | + +##### 7.3.3.3.4 Pre-condition + +IOCIDoesNotExist + +| Assertion name | Definition | +|------------------|------------------------------------------------------------------------------------------------------| +| IOCIDoesNotExist | A IOC instance with the same distinguished name as the object specified for creation does not exist. | + +##### 7.3.3.3.5 Post-condition + +IOCICreated AND objectCreationNotificationEmitted + +| Assertion name | Definition | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IOCICreated | The IOC instance of the specified object class has been created with the specified Distinguished Name. | +| objectCreation
NotificationEmitted | An object creation notification is emitted for the created object, if notifiable. Notifiable here means that the notification is supported and not suppressed. "Emitted" here corresponds to the association stereotyped as <> in [ITU-T M.3020]. | + +##### 7.3.3.3.6 Exceptions + +| Name | Definition | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailed | Condition: Pre-condition is false or post-condition is false.
Returned information: The output parameter status.
Exit state: Entry state. | +| objectClassSpecificationMismatch | Condition: The object class named by ObjectClassIdentifier input parameter does not match the object class of the information object specified by a non-null referenceObjectInstance input parameter.
Returned information: The output parameter status.
Exit state: Entry state. | +| invalidObjectInstance | Condition: The object instance name specified implied a violation of the naming rules;
Returned information: The output parameter status.
Exit state: Entry state. | +| createNotAllowed | Condition: The object to be created may not be created over the interface.
Returned information: The output parameter status.
Exit state: Entry state. | +| noSuchObjectClass | Condition: The class of the specified information object is not recognized.
Returned information: The output parameter status.
Exit state: Entry state. | +| classInstanceConflict | Condition: The specified IOC instance may not be created as member of the specified class.
Returned information: The output parameter status.
Exit state: Entry state. | +| noSuchAttribute | Condition: A specified attribute is not recognized or is not valid for specified object class.
Returned information: The output parameter status.
Exit state: Entry state. | +| invalidAttributeValue | Condition: Value specified for an attribute is not valid for that attribute.
Returned information: The output parameter status.
Exit state: Entry state. | +| missingAttributeValue | Condition: One or more required attribute values were not supplied and default values are not available.
Returned information: The output parameter status.
Exit state: Entry state. | +| parentObjectDoesNotExist | Condition: The parent MO instance of the IOC specified to be created does not exist.
Returned information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.4 Operation deleteObject (O) + +##### 7.3.3.4.1 Definition + +This operation is invoked by the manager to request the deletion of one or more IOC instances from the MIB maintained by the agent. + +##### 7.3.3.4.2 Input parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|--------------------|-------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| baseObjectInstance | M | Name | The MO instance that is to be used as the starting point for the selection of information objects to which the filter (when supplied) is to be applied. | +| scope | O | See corresponding parameter in getMOAttributes. | See corresponding parameter in getMOAttributes . | +| filter | O | See comment | See corresponding parameter in getMOAttributes . | + +##### 7.3.3.4.3 Output parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|----------------|-------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deletionList | M | SET OF SEQUENCE{
,

} | If the base object alone is specified, then this parameter is optional; otherwise it contains a list of Name of Instance and Name of object class pairs identifying the information objects deleted. | +| status | M | ENUMERATED {
operationSucceeded,
operationFailed,
operationPartiallySucceeded
} | An operation may fail because of a specified or unspecified reason. The operation is partially successful if some, but not all, objects selected to be deleted are actually deleted. | + +In lieu of a synchronization parameter, best effort synchronization will apply; that is, all information objects selected for this operation will perform the operation if possible regardless of whether some information objects fail to perform it. + +##### 7.3.3.4.4 Pre-condition + +baseObjectExists AND allChildrenOfObjectsToBeDeletedSpecifiedForDeletion + +| Assertion name | Definition | +|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| baseObjectExists | The IOC instance specified by the baseObjectInstance parameter exists. | +| allChildrenOfObjectsToBeDeletedSpecifiedForDeletion | For any IOC instance specified for deletion, all of its dependant IOC instances must be specified for deletion. | + +##### 7.3.3.4.5 Post-condition + +(*selectedObjectsDeleted* OR *someSelectedObjectsDeleted*) AND *objectDeletionNotificationEmitted* + +| Assertion name | Definition | +|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| selectedObjectsDeleted | All of the IOC instances selected for deletion are deleted. | +| someSelectedObjectsDeleted | Some but not all of the selected IOC instances were deleted and for any of the IOC instances deleted all of the child IOC instances of that IOC instance is deleted. | +| objectDeletionNotificationEmitted | An object deletion notification is emitted for each notifiable deleted object. Notifiable here means that the notification is supported and not suppressed. "Emitted" here corresponds to the association stereotyped as <> in Recommendation [ITU-T M.3020]. An object deletion notification of an information object containing a sub-tree implies deletion of all information objects in the sub-tree. The agent should make the best effort to reduce the number of object deletion notifications, for example by sending only one notification for the sub-tree root object in the event of a successful deletion of an entire sub-tree. | + +##### 7.3.3.4.6 Exceptions + +| Name | Definition | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailed | Condition: Pre-condition is false or post-condition is false.
Returned information: The output parameter status.
Exit state: Entry state. | +| invalidObjectInstance | Condition: The object instance name specified implied a violation of the naming rules.
Returned information: The output parameter status.
Exit state: Entry state. | +| deleteNotAllowed | Condition: Some of the object instances to be deleted may not be deleted over the interface.
Returned information: The output parameter status.
Exit state: Entry state. | +| resourceLimitation | Condition: Operation not performed due to resource limitation.
Returned information: The output parameter status.
Exit state: Entry state. | +| complexityLimitation | Condition: Operation not performed because a parameter was too complex.
Returned information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.5 Operation *setAttributes* (O) + +##### 7.3.3.5.1 Definition + +This operation is invoked by the manager to request the modification of management information (information object attribute values) in the MIB maintained by the agent. Attributes of one or several information objects may be modified – based on the containment hierarchy. + +##### 7.3.3.5.2 Input Parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|--------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| baseObjectInstance | M | Name | The MO instance that is to be used as the starting point for the selection of information objects to which the filter (when supplied) is to be applied. | +| scope | O | See comment | See corresponding parameter in getMOAttributes . | +| filter | O | See comment | See corresponding parameter in getMOAttributes . | +| modificationList | M |

SET OF SEQUENCE{
<Name of attribute>,
<Value of attribute>
OPTIONAL,
opType ENUMERATED{
replace,
add-values,
remove-values,
set-to-default
}
}

See comment for when attribute values are required and when they are optional.

|

This parameter contains a set of attribute modification specifications, each of which contains:

  1. 1. Name of attribute(s) to be modified.
  2. 2. the value(s) to be used in the modification of the attribute. The use of this parameter is defined by the modify operator. This parameter is optional when the set to default modify operator is specified and if supplied, shall be ignored.
  3. 3. modify operator: the way in which the attribute values(s) (if supplied) is(are) to be applied to the attribute. The possible operators are:
    replace: the attribute value(s) specified shall be used to replace the current values(s) of the attribute;
    add values: the attribute values(s) specified shall be added to the current value(s) of the of the attribute. This operator shall only be applied to a set-valued attribute and shall perform a set union (in the mathematical sense) between the current values(s) of the attribute and the attribute value(s) specified. Value(s) specified in the attribute value parameter which is(are) already in the current values of the attribute shall not cause an error to be returned.
| + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|----------------|-------------------|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | |

remove values: the attribute value(s) specified shall be removed from the current value(s) of the attribute. This operator shall only be applied to a set-valued attribute and shall perform a set difference (in the mathematical sense) between the current value(s) of the attribute and the attribute value(s) specified. Value(s) specified in the attribute value parameter which is(are) not in the current value(s) of the attribute shall not cause an error to be returned;

set to default: when this operator is applied to a single-valued attribute, the value of the attribute shall be set to its default value. When this operator is applied to a set-valued attribute, the value(s) of the attribute shall be set to their default value(s) and only as many values as defined by the default shall be assigned. If there is no default value defined, an error shall be returned.

NOTE – Set is used here in the mathematical sense so that a set-valued attribute is an unordered set of unique values.

The modify operator is optional, and if it is not specified, the replace operator shall be assumed.

The modificationList parameter contains a single set of attribute modification specifications and this same set is applied to each IOC instance to be modified.

| + +##### 7.3.3.5.3 Output Parameters + +| Parameter name | Support qualifier | Information type/Legal values | Comment | +|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| modificationList
Out | M | SET OF SEQUENCE{
,
,
modifiedAttrs SET OF
SEQUENCE{
,

}
} | This parameter will provide for each IOC instance the name of the IOC instance, the name of object class, and a list of name/value pairs of the modified attributes of the modified IOC instance after modification. The form of this information is solution set dependant and may be provided in one or many data structures. | +| status | M | ENUMERATED {
operationSucceeded,
operationFailed,
operationPartiallySucceeded
} | An operation may fail because of a specified or unspecified reason and no attributes have been updated. The operation is only successful if all specified attributes of all selected objects are actually modified. Otherwise, the operation is partially successful. | + +In lieu of a synchronization parameter, best effort synchronization will apply; that is, all information objects selected for this operation will perform the operation if possible regardless of whether some information objects fail to perform it. + +##### 7.3.3.5.4 Pre-condition + +baseObjectExists + +| Assertion name | Definition | +|------------------|------------------------------------------------------------------------| +| baseObjectExists | The IOC instance specified by the baseObjectInstance parameter exists. | + +##### 7.3.3.5.5 Post-condition + +(selectedObjectsModified OR someSelectedObjectsModified) AND +attributeValueChangeNotificationEmitted + +| Assertion name | Definition | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| selectedObjectsModified | All of the attributes of all of the IOC instances selected for modification are modified as specified. | +| someSelectedObjectsModified | Some attributes of some of the selected IOC instances were modified but not all attributes of all selected IOC instances. | +| attributeValueChangeNotificationEmitted | A notifyAttributeValueChange notification is emitted for the notifiable attributes of each modified object instance. Notifiable here means that the notification is supported and not suppressed. "Emitted" here corresponds to the association stereotyped as <> in Recommendation [ITU-T M.3020]. | + +##### 7.3.3.5.6 Exceptions + +| Name | Definition | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailed | Condition: Pre-condition is false or post-condition is false.
Returned information: The output parameter status.
Exit state: Entry state. | +| modifyNotAllowed | Condition: The object to be modified may not be modified over the interface.
Returned information: The output parameter status.
Exit state: Entry state. | +| noSuchAttribute | Condition: A specified attribute is not recognized or is not valid for specified object class.
Returned information: The output parameter status.
Exit state: Entry state. | +| invalidAttributeValue | Condition: Value specified for an attribute is not valid for that attribute.
Returned information: The output parameter status.
Exit state: Entry state. | +| missingAttributeValue | Condition: One or more required attribute values were not supplied and default values are not available.
Returned information: The output parameter status.
Exit state: Entry state. | +| resourceLimitation | Condition: Operation not performed due to resource limitation.
Returned information: The output parameter status.
Exit state: Entry state. | +| complexityLimitation | Condition: Operation not performed because a parameter was too complex.
Returned information: The output parameter status.
Exit state: Entry state. | +| noDefaultSpecified | Condition: Operation not performed because default values is not specified for one or more affected information objects.
Returned information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.6 Notification **attributeValueChanged** (O) + +##### 7.3.3.6.1 Definition + +Attribute Value Change Notification is a notification generated in case the value of attribute in an object instance is changed. Some object class may not support attribute value change notification, so it is optional. + +##### 7.3.3.6.2 Input parameters + +The notification header defined in [ITU-T M.3702] already includes general parameters needed in a notification. The following table only defines specific parameters. + +| Parameter name | Qualifiers | Matching information/
Information type/Legal values | Comment | +|------------------|------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attributeListOld | O | SET OF SEQUENCE{
,

} | This parameter may have a null value. When this parameter is supplied, it contains a list of name/value pairs specifying attribute identifiers and their values before change. | +| attributeListNew | M | SET OF SEQUENCE{
,

} | It contains a list of name/value pairs specifying attribute identifiers and their values newly set. | + +##### 7.3.3.6.3 Triggering event + +When Object class supports this notification and object instance's attribute value is changed. + +#### 7.3.3.7 Notification stateChanged (O) + +##### 7.3.3.7.1 Definition + +State Change Notification is a notification generated in case the value of state attribute in an object instance is changed. Some object class may not support state change notification, so it is optional. + +##### 7.3.3.7.2 Input parameters + +The notification header defined in [ITU-T M.3702] already includes general parameters needed in a notification. The following table only defines specific parameters. + +| Parameter name | Qualifiers | Matching information/
Information type/Legal values | Comment | +|------------------|------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attributeListOld | O | SET OF SEQUENCE{
,

} | This parameter may have a null value. When this parameter is supplied, it contains a list of name/value pairs specifying attribute identifiers and their values before change. | +| attributeListNew | M | SET OF SEQUENCE{
,

} | It contains a list of name/value pairs specifying attribute identifiers and their values newly set. | + +##### 7.3.3.7.3 Triggering event + +When Object class supports this notification and object instance's state attribute value is changed. + +#### 7.3.3.8 Notification objectCreated (M) + +##### 7.3.3.8.1 Definition + +Object Create Notification is a notification generated in case an object instance is created. + +##### 7.3.3.8.2 Input parameters + +The notification header defined in [ITU-T M.3702] already include general parameters needed in a notification. The following table only defines specific parameters. + +| Parameter name | Qualifiers | Matching information/
Information type/Legal values | Comment | +|------------------|------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| attributeListNew | M | SET OF SEQUENCE{
,

} | It contains a list of name/value pairs specifying attribute identifiers and their values newly set. | + +##### 7.3.3.8.3 Triggering event + +When Object class supports this notification and object instance is newly created. + +#### 7.3.3.9 Notification objectDeleted (M) + +##### 7.3.3.9.1 Definition + +Object Deleted Notification is a notification generated in case an object instance is deleted. + +##### 7.3.3.9.2 Input parameters + +The notification header defined in [ITU-T M.3702] already includes general parameters needed in a notification. The following table only defines specific parameters. + +| Parameter name | Qualifiers | Matching information/
Information type/Legal values | Comment | +|------------------|------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attributeListOld | O | SET OF SEQUENCE{
,

} | This parameter may have a null value. When this parameter is supplied, it contains a list of name/value pairs specifying attribute identifiers and their values before change. | + +##### 7.3.3.9.3 Triggering event + +When Object class supports this notification and object instance's attribute value is changed. + +# Bibliography + +The protocol-neutral object management capabilities defined in this specification are based on multiple sources identified in this bibliography. + +- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.* +- [b-ITU-T Q.827.1] Recommendation ITU-T Q.827.1 (2004), *Requirements and analysis for the common management functions of NMS-EMS interfaces.* +- [b-ITU-T X.730] Recommendation ITU-T X.730 (1992), *Information technology – Open Systems Interconnection – Systems Management: Object management function.* +- [b-3GPP TS 32.601] 3GPP TS 32.601 (2009), *Telecommunication management – Configuration management (CM); Basic CM Integration Reference Point (IRP); Requirements.* +- [b-3GPP TS 32.602] 3GPP TS 32.602 (2009), *Telecommunication management; Configuration management (CM); Basic CM Integration Reference Point (IRP): Information Service (SS).* +- [b-3GPP TS 32.661] 3GPP TS 32.661 (2009), *Telecommunication management; Configuration management (CM); Kernel CM; Requirements.* +- [b-3GPP TS 32.662] 3GPP TS 32.662 (2009), *Telecommunication management; Configuration management (CM); Kernel CM; Information Service (IS).* + + + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f42531875bfec8215e62adfeaaea98e746487ed7 --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9926f3f86dc69f0d1e5b04c6bab6ce09772b208b61a735142ea63820a3c31b55 +size 10087 diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..164b1365242e64249c7d124a1f768e81fe108ef8 --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e4b2194cedb51ff401ad45f88c5a417fce8ba51339e701471d1b29990e1d7cf +size 43441 diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b986f95a86acf370a6f1767b337f48a45869753f --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:323084b8602906e5ea52a788898705dd06d548fb5a400a0b032608cbfd6797c7 +size 39679 diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b38e9d6967e33eacaeceed2c13d28e81a31765 --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec4eb747d91fa521d53ae248ed7ac5a1d078db7aa4889fb7f6e72315409b18c2 +size 45157 diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4149601f1e305bbfad90e5ae91d42f9e6e863377 --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2a376dc7119a7e4f777292b23cefcb4b627382a7d63d5e2ae6f74c6dac0e06d +size 45874 diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c38964607097c2f5929502bd66ef27e7a7df2d --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f02c8a9543b14f9f0a17d3f18b0c6e54dfda85ea50f70fe3f3f0c8a72f9d0840 +size 3923 diff --git a/marked/M/T-REC-M.3701-201001-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/M/T-REC-M.3701-201001-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7d463080cda6ac516237631a53d87b04c7401e4 --- /dev/null +++ b/marked/M/T-REC-M.3701-201001-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ce6a61dd70972f1c6932affb5230249283e9660fd63a90c4662f75a93ddce47 +size 42185 diff --git a/marked/M/T-REC-M.3703-201006-I_PDF-E/raw.md b/marked/M/T-REC-M.3703-201006-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..686988daa0a366cf00fae3a904f8df2230ec18c6 --- /dev/null +++ b/marked/M/T-REC-M.3703-201006-I_PDF-E/raw.md @@ -0,0 +1,2637 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3703** + +(06/2010) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Integrated services digital networks + +--- + +**Common management services – Alarm +management – Protocol neutral requirements +and analysis** + +Recommendation ITU-T M.3703 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3703 + +## Common management services – Alarm management – Protocol neutral requirements and analysis + +## Summary + +Recommendation ITU-T M.3703 provides the requirements and analysis for one of the common management services – alarm management. The functional requirements for the alarm management interface include the management functions for alarm forwarding and filtering, clearing of alarms, storage and retrieval of alarms in/from the agent, configuration of alarms, alarm acknowledgement and alarm notification failure. In the analysis part, the detailed information model supporting the above functions across the management interface is provided. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3703 | 2010-06-29 | 2 | + +## Keywords + +Agent, alarm management, analysis, fault management, interface, manager, requirements. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2011 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-------------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations..... | 2 | +| 5 Conventions ..... | 3 | +| 6 Requirements ..... | 3 | +| 6.1 Concepts and background..... | 3 | +| 6.2 Business-level requirements ..... | 3 | +| 6.3 Specification-level requirements ..... | 7 | +| 7 Analysis ..... | 15 | +| 7.1 Concepts and background..... | 15 | +| 7.2 Information object classes ..... | 16 | +| 7.3 Interface definition ..... | 29 | +| Annex A – Event Types ..... | 53 | +| Annex B – Probable Causes..... | 54 | +| Appendix I – Examples of using notifyChangedAlarm..... | 63 | +| Appendix II – Background information about fault management ..... | 65 | +| II.1 Fault detection ..... | 65 | +| II.2 Alarm acknowledgement..... | 66 | +| II.3 Clearing of alarms ..... | 66 | +| II.4 Fault recovery ..... | 67 | +| Bibliography..... | 69 | + +## Introduction + +A network is composed of a multitude of network elements (NE) of various types and, typically, different vendors, which interoperate in a coordinated 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. Degradation of service may be detected by monitoring error rates. Threshold mechanisms on counters and gauges are a method of detecting such trends and providing a warning to managers when the rate becomes high. + +Alarms are a specific type of notification concerning detected faults or abnormal conditions. Managed object definers are encouraged to include in alarms information that will help understand the cause of the potentially abnormal situation, and other information related to side effects. An example of such diagnostic information is the current and past values of the configuration management state of the object. + +A single incident may cause the generation of several notifications; it is important to be able to specify in a notification some correlation with other notifications. However, the mechanism, if any, for determining the relationship between notifications resulting from a single incident is for further study. + +The functional areas specified in this Recommendation cover: + +- notification of alarms (including alarm cease) and operational state changes; +- retrieval of current alarms; +- alarm filtering; +- management of alarm severity levels; +- retention of alarm and operational state data in the NEs and the operations system (OS). + +Any (re)configuration activities exerted from the element manager (EM) as a consequence of faults is out of the scope of this Recommendation. + +This Recommendation defines the requirements for fault management. + +# Recommendation ITU-T M.3703 + +## Common management services – Alarm management – Protocol neutral requirements and analysis + +# 1 Scope + +This Recommendation defines an interface through which an agent (typically a network element or a network element manager) can communicate alarm information for its managed objects to one or several managers (typically network management systems). + +This Recommendation defines the semantics of alarms and the interactions visible across the reference point in a protocol neutral way. It defines the semantics of the operations and notifications visible on the interface. It does not define the syntax or encoding of the operations, notifications and their parameters. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2009), *Management interface specification methodology*. +- [ITU-T M.3100] Recommendation ITU-T M.3100 (1995), *Generic network information model*. +- [ITU-T M.3160] Recommendation ITU-T M.3160 (2008), *Generic, protocol-neutral management information model*. +- [ITU-T M.3702] Recommendation ITU-T M.3702 (2010), *Common management services – Notification management – Protocol neutral requirement and analysis*. +- [ITU-T X.701] Recommendation ITU-T X.701 (1997) | ISO/IEC 10040:1998, *Information technology – Open Systems Interconnection – Systems management overview*. +- [ITU-T X.721] Recommendation ITU-T X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information*. +- [ITU-T X.733] Recommendation ITU-T X.733 (1992) | ISO/IEC 10164-4:1992, *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function*. +- [ITU-T X.736] Recommendation ITU-T X.736 (1992) | ISO/IEC 10164-7:1992, *Information technology – Open Systems Interconnection – Systems Management: Security alarm reporting function*. +- [ITU-T X.790] Recommendation ITU-T X.790 (1995), *Trouble management function for ITU-T applications*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +3.1.1 **alarm** [ITU-T X.733]. + +3.1.2 **agent** [ITU-T M.3020]. + +3.1.3 **event** [ITU-T X.790]. + +3.1.4 **error** [ITU-T X.733]. + +3.1.5 **fault** [ITU-T X.733]. + +3.1.6 **manager** [ITU-T M.3020]. + +3.1.7 **notification** [ITU-T X.701]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +3.2.1 **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. + +3.2.2 **ADAC faults**: Faults that are automatically detected and automatically cleared by the system when they occur and when they are repaired. + +3.2.3 **ADMC faults**: Faults that are automatically detected by the system when they occur and manually cleared by the operator when they are repaired. + +3.2.4 **alarm notification**: Notification used to inform the recipient about the occurrence of an alarm. + +3.2.5 **clear alarm**: Notification used to inform the recipient about the cessation of an alarm and thus the underlying fault condition. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +ADAC Automatically Detected and Automatically Cleared + +ADMC Automatically Detected and Manually Cleared + +ASAP Alarm Severity Assignment Profile + +CO Conditional-Optional + +DN Domain Name + +EM Element Manager + +FM Fault Management + +FS Function Set + +IOC Information Object Class + +M Mandatory + +MO Managed Object + +MOC Managed Object Class + +MOI Managed Object Instance + +| | | +|-----|--------------------| +| NE | Network Element | +| NM | Network Manager | +| O | Optional | +| OS | Operations System | +| QoS | Quality of Service | + +# 5 Conventions + +This Recommendation uses the conventions defined in [ITU-T M.3020] for requirements capture and analysis. + +# 6 Requirements + +## 6.1 Concepts and background + +Any evaluation of the NEs' and the overall network health status requires 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 may be required by the system operator for further analysis. Additionally, test procedures may be used in order to obtain more detailed information if necessary, or to verify an alarm, a state or the proper operation of NEs and their logical and physical resources. + +This service uses the following other services and thus implicitly imports all the requirements defined therein: + +- Notification, defined in [ITU-T M.3702]. + +## 6.2 Business-level requirements + +Faults that may occur in the network can be grouped into one of the following categories: + +- Hardware failures, i.e., the malfunction of a physical resource within a NE. +- Software problems, e.g., software bugs, database inconsistencies. +- Functional faults, i.e., a failure of a 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. + +### 6.2.1 Requirements + +#### 6.2.1.1 Alarm forwarding and filtering + +REQ-FM-FUN-01 For each detected fault, the agent shall generate appropriate alarms (notifications of the fault), regardless of whether it is an ADAC or an ADMC fault. Each alarm should be uniquely identified. For each alarm, the agent shall supply the following information: + +- the managed entity; +- 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 and a description of the loss of capability of the affected resource; +- the type of the fault (communication, environmental, equipment, processing error, QoS, security types, etc.); + - the severity of the fault (indeterminate, warning, minor, major, critical); + - the probable cause of the fault; + - the specific problem; + - the time at which the fault was detected; + - 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). + +- REQ-FM-FUN-02 The manager shall be able to allow or suppress alarm reporting by setting the filtering on any combination of attributes. The following criteria shall minimally be supported for alarm notification filtering: +- the managed entity that generated the alarm, i.e., all alarm messages for that managed entity 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. + +#### 6.2.1.2 Clearing of alarms + +- REQ-FM-FUN-03 Each time an alarm is cleared, the agent shall generate an appropriate clear alarm event. A clear alarm is defined as an alarm. A clear alarm is identified as such through the use of perceived severity equal to CLEARED. +- REQ-FM-FUN-04 The manager may explicitly request the clearing of one or more alarms. Once the alarm(s) has/have been cleared, the agent should reissue those alarms (as new alarms) in case the fault situation still persists. + +#### 6.2.1.3 Storage and retrieval of alarms in/from the agent + +- REQ-FM-FUN-05 The manager shall be able to retrieve alarm information optionally using filters (active and/or historic). + +#### 6.2.1.4 Configuration of ASAP + +- REQ-FM-FUN-06 It may be possible for the manager to create an ASAP on an agent to define the relationship between severity level and problem. +- REQ-FM-FUN-07 It may be possible for the manager to modify the ASAP. +- REQ-FM-FUN-08 It may be possible for the manager to delete the ASAP on an agent. +- REQ-FM-FUN-09 It may be possible for the manager to request an agent to set or change the association between an ASAP and one or more specified managed entities. + +- REQ-FM-FUN-10 It may be possible for the manager to request an agent to remove the association between an ASAP and one or more of its associated managed entities. +- REQ-FM-FUN-11 The manager may query the attribute information of an ASAP, which includes the ID of the ASAP, the list of the problem and the corresponding severity, and the list of managed entities that have been associated with this ASAP. + +#### **6.2.1.5 Alarm acknowledgement and management** + +- REQ-FM-FUN-12 An agent may support alarm acknowledgement and unacknowledgement. Acknowledgement data shall include the current alarm state (active|cleared), the time of alarm acknowledgement and, optionally, the system (EM|NM) or the operator in charge of acknowledgement (the parameter operator name or, in case of auto-acknowledgement, a generic system name). +- REQ-FM-FUN-13 An alarm acknowledgement means that an acknowledgement performed by the agent is notified to the manager and vice versa, thus the acknowledgement-related status of this alarm is the same across the whole management hierarchy. +- REQ-FM-FUN-14 The agent may provide the ability to add a comment to an alarm. An agent may also have the capability to record more than one comment for each alarm. To make the same alarm look the same to all managers subscribing to the alarm, it will be possible to distribute the recorded comments. +- REQ-FM-FUN-15 Acknowledgement state shall be a filterable criteria for alarms if acknowledgement is supported by the agent. +- REQ-FM-FUN-16 Acknowledgement notifications shall be filtered with the same criteria applied to alarms. + +#### **6.2.1.6 Alarm notification failure** + +- REQ-FM-FUN-17 The manager should be able to request an agent to synchronize alarm information following a failure in communication between the agent and the manager. + +### **6.2.2 Actor roles** + +The capabilities described in this Recommendation are available and relevant to all agents and managers. + +### **6.2.3 Telecommunication resources** + +The alarm management functionality is applicable to all types of telecommunication resources. + +### **6.2.4 High-level use-case diagrams** + +The first overview use-case diagram in Figure 6-1 shows the overall interaction of the alarm interface. + +![Figure 6-1: Fault management function set diagram. A Manager actor is connected to a central 'Fault management FS' function. This function includes four sub-functions: 'Alarm report FS', 'Alarm handling FS', 'ASAP management FS', and 'Alarm synchronize FS'.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph LR + Manager((Manager)) --> FM[Fault management FS] + FM -.->|<>| ARF[Alarm report FS] + FM -.->|<>| AHF[Alarm handling FS] + FM -.->|<>| AMF[ASAP management FS] + FM -.->|<>| ASF[Alarm synchronize FS] + +``` + +M.3703(10)\_6-1 + +Figure 6-1: Fault management function set diagram. A Manager actor is connected to a central 'Fault management FS' function. This function includes four sub-functions: 'Alarm report FS', 'Alarm handling FS', 'ASAP management FS', and 'Alarm synchronize FS'. + +**Figure 6-1 – Fault management function set** + +Figure 6-2 shows the functions involved in the alarm report function set. + +![Figure 6-2: Alarm report function set diagram. A Manager actor is connected to a central 'Alarm report FS' function. This function includes four sub-functions: 'Alarm notification', 'Notification of alarm change', 'Set alarm filter', and 'Request alarm clear'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph LR + Manager((Manager)) --> ARF[Alarm report FS] + ARF -.->|<>| AN[Alarm notification] + ARF -.->|<>| NOAC[Notification of alarm change] + ARF -.->|<>| SAF[Set alarm filter] + ARF -.->|<>| RAC[Request alarm clear] + +``` + +M.3703(10)\_6-2 + +Figure 6-2: Alarm report function set diagram. A Manager actor is connected to a central 'Alarm report FS' function. This function includes four sub-functions: 'Alarm notification', 'Notification of alarm change', 'Set alarm filter', and 'Request alarm clear'. + +**Figure 6-2 – Alarm report function set** + +Figure 6-3 shows the functions involved in the alarm handling function set. + +![Figure 6-3: Alarm handling function set diagram. A Manager actor is connected to a central 'Alarm handling FS' function. This function includes three sub-functions: 'Acknowledge alarm', 'Unacknowledge alarm', and 'Add comment'.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +graph LR + Manager((Manager)) --> AHF[Alarm handling FS] + AHF -.->|<>| AA[Acknowledge alarm] + AHF -.->|<>| UA[Unacknowledge alarm] + AHF -.->|<>| AC[Add comment] + +``` + +M.3703(10)\_6-3 + +Figure 6-3: Alarm handling function set diagram. A Manager actor is connected to a central 'Alarm handling FS' function. This function includes three sub-functions: 'Acknowledge alarm', 'Unacknowledge alarm', and 'Add comment'. + +**Figure 6-3 – Alarm handling function set** + +Figure 6-4 shows the functions involved in the ASAP management function set. + +![Figure 6-4: ASAP management function set diagram. A Manager actor is connected to a central 'ASAP management FS' function. This function includes five sub-functions: 'Create ASAP', 'Delete ASAP', 'Modify ASAP', 'Assign ASAP', and 'Unassign ASAP'.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +``` + +graph LR + Manager((Manager)) --> AMF[ASAP management FS] + AMF -.->|<>| CASAP[Create ASAP] + AMF -.->|<>| DASAP[Delete ASAP] + AMF -.->|<>| MASAP[Modify ASAP] + AMF -.->|<>| ASASAP[Assign ASAP] + AMF -.->|<>| UASAP[Unassign ASAP] + AMF -.->|<>| QASAP[Query ASAP] + +``` + +M.3703(10)\_6-4 + +Figure 6-4: ASAP management function set diagram. A Manager actor is connected to a central 'ASAP management FS' function. This function includes five sub-functions: 'Create ASAP', 'Delete ASAP', 'Modify ASAP', 'Assign ASAP', and 'Unassign ASAP'. + +**Figure 6-4 – ASAP management function set** + +Figure 6-5 shows the functions involved in the alarm synchronize function set. + +![UML Use Case Diagram showing a Manager actor associated with 'Alarm synchronize FS' use case, which includes 'Get alarm list' use case.](4e4be0bd8b235167902f2c03e41da651_img.jpg) + +``` + + graph LR + Manager((Manager)) --> AlarmSynchronizeFS(Alarm synchronize FS) + AlarmSynchronizeFS -.-> GetAlarmList(Get alarm list) + +``` + +M.3703(10)\_6-5 + +UML Use Case Diagram showing a Manager actor associated with 'Alarm synchronize FS' use case, which includes 'Get alarm list' use case. + +**Figure 6-5 – Alarm synchronize function set** + +## 6.3 Specification-level requirements + +### 6.3.1 Requirements + +There are no specification-level requirements. + +### 6.3.2 Actor roles + +See clause 6.2.2. + +### 6.3.3 Telecommunication resources + +See clause 6.2.3. + +### 6.3.4 Use cases + +#### 6.3.4.1 Use case: Set alarm filter + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager sets a filter for alarm notification subscription. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | None. | | +| Begins when | The manager requests to set a filter to the agent. | | +| Step 1 | The manager requests to set a filter to subscribe alarm information; the manager provides the criteria parameters (e.g., the managed entities, severity level, event type, acknowledgement state, etc.) in the request. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | Invalid parameters. | | +| Post conditions | The filter is received by the agent. | | +| Traceability | REQ-FM-FUN-02, REQ-FM-FUN-15 | | + +#### 6.3.4.2 Use case: Alarm notification + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | An agent sends an alarm report notification of the relevant type to the manager. | | +| Actor and roles | The manager is a consumer of notifications from the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | A fault condition is detected. | | +| Begins when | The agent begins to send an alarm report notification to the manager. | | +| Step 1 | The agent sends notification of fault and gives parameters (e.g., identifier of alarm, time, severity level, event type, etc.) in the notification. | | +| Ends when | The notification is emitted by the agent. | | +| Exceptions | None. | | +| Post conditions | The manager is informed of the fault condition in the agent. | | +| Traceability | REQ-FM-FUN-01, REQ-FM-FUN-03 | | + +#### 6.3.4.3 Use case: Notification of alarm change + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | An agent notifies the subscribed manager of the information change of an alarm. | | +| Actor and roles | The manager is a consumer of notifications from the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The information (e.g., state, comment, etc.) of an alarm is changed. | | +| Begins when | The agent begins to send a notification to the subscribed managers. | | +| Step 1 | When the agent notifies the managers of the change of information of an alarm, the agent will give some parameters (e.g., identifier of alarm, the new state/status value, the new comment, etc.) as part of the notification. | | +| Ends when | The notification is emitted by the agent. | | +| Exceptions | None. | | +| Post conditions | The manager is informed of the change of an alarm. | | +| Traceability | REQ-FM-FUN-09, REQ-FM-FUN-10 | | + +#### 6.3.4.4 Use case: Request alarm clear + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager explicitly requests the clearing of one or more alarms. | | +| Actor and roles | The manager invokes the operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The alarm to be cleared exists. | | +| Begins when | The manager begins to request clearing of one or more alarms. | | +| Step 1 | The manager sends a request to the agent to clear one or more alarms, the parameters given in the request can be identifier of alarm, severity level and other parameters. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | Invalid parameters. | | +| Post conditions | The specified alarms are cleared and the agent sends a notification to the subscribed manager. | | +| Traceability | REQ-FM-FUN-04 | | + +#### 6.3.4.5 Use case: Get alarm list + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager requests and receives a list of alarms from the agent. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The manager sends a request to the agent to get alarm list. | | +| Begins when | The manager requests active alarm list from an agent with a filtering criteria. | | +| Step 1 | A list of alarms, starting at the oldest, according to the filtering criteria, is received by the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | Invalid criteria parameter. | | +| Post conditions | The complete list of alarms (active and/or historic) at the time of the initial request is received by the manager. | | +| Traceability | REQ-FM-FUN-05, REQ-FM-FUN-17 | | + +#### 6.3.4.6 Use case: Acknowledge alarm + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager requests an alarm to be acknowledged. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available.
The agent supports the acknowledged state alarm attribute. | | +| Preconditions | The specified alarm has not been acknowledged. | | +| Begins when | The manager requests an alarm to be marked as acknowledged. | | +| Step 1 | The manager sends a request to the agent to set the acknowledged state of an alarm to TRUE. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – unknown alarm;
– the alarm has been already acknowledged. | | +| Post conditions | The agent marks the alarm as acknowledged, and the agent sends a notification of the event to the subscribed managers. | | +| Traceability | REQ-FM-FUN-12, REQ-FM-FUN-13, REQ-FM-FUN-16 | | + +#### 6.3.4.7 Use case: Unacknowledge alarm + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager requests that an acknowledged alarm be unacknowledged. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available.
The agent supports the acknowledged state alarm attribute. | | +| Preconditions | The specified alarm has been acknowledged. | | +| Begins when | The manager requests an alarm be marked as not acknowledged. | | +| Step 1 | The manager sends a request to the agent to set the acknowledged state of an alarm to FALSE. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – unknown alarm;
– the alarm has not been acknowledged. | | +| Post conditions | The agent marks the alarm as not acknowledged, and the agent sends a notification of the event to the subscribed managers. | | +| Traceability | REQ-FM-FUN-12, REQ-FM-FUN-13, REQ-FM-FUN-16 | | + +#### 6.3.4.8 Use case: Create ASAP + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | A manager requests an agent to create an ASAP through the management interface. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The manager needs to assign the alarm severities for a set of problems, so that when an agent reports alarms, these pre-assigned severities can be referenced in the corresponding alarm notifications. | | +| Begins when | The manager sends a request to the agent to create an ASAP. | | +| Step 1 | The manager requests to create an ASAP, and gives the parameters (problems and their corresponding severity) in the request. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions |
  • – invalid parameter;
  • – unknown managed entity.
| | +| Post conditions | An ASAP is successfully created by the agent according to the request. The agent returns the identifier of the ASAP instance. The newly created ASAP will be associated with the managed entities, if specified in the request. | | +| Traceability | REQ-FM-FUN-06 | | + +#### 6.3.4.9 Use case: Delete ASAP + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | A manager requests an agent to delete an ASAP through the management interface. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified ASAP exists in the agent, and it is not associated with any managed entities. | | +| Begins when | The manager sends a request to the agent to delete an ASAP. | | +| Step 1 | The manager sends a request to the agent to delete an ASAP. The request parameter is the identifier of the ASAP. The ASAP to be deleted should not be associated with any managed object; otherwise it cannot be deleted. If the deletion operation succeeds, the agent returns a success indication, and may send an object deletion notification to the manager. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|-----------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| | If the operation fails, the agent will send back error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions |
  • – unknown ASAP;
  • – ASAP association not removed.
| | +| Post conditions | The ASAP is successfully deleted by the agent according to the request. | | +| Traceability | REQ-FM-FUN-08 | | + +#### 6.3.4.10 Use case: Modify ASAP + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | A manager requests an agent to modify, add or delete table entries (problem and the corresponding alarm severity) of an ASAP. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Telecom resources | All types of telecommunication resources. | | +| Preconditions | The manager needs to change the table entries of the alarm severity assignment of an ASAP. | | +| Begins when | The manager sends a request to an agent to modify an ASAP. | | +| Step 1 | The manager sends a request to the agent to modify an ASAP. The request parameter is the new list of the problems and their corresponding severity to be modified. If the modification operation succeeds, the agent will send success information. If the operation fails, the agent will send back error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions |
  • – unknown ASAP;
  • – invalid parameter.
| | +| Post conditions | An ASAP on the agent is successfully modified according to the request. | | +| Traceability | REQ-FM-FUN-07 | | + +#### 6.3.4.11 Use case: Assign ASAP + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | A manager requests an agent to set or change the association between an ASAP instance and one or more specified managed entities. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified ASAP exists in the agent. | | +| Begins when | The manager sends a request to the agent to change the association between an ASAP instance and one or more specified managed entities. | | +| Step 1 |

When an ASAP is created successfully, it will not take effect immediately until associated with managed entities. When a managed entity is about to report an alarm, it will first check in the associated ASAP whether the corresponding alarm severity is specified. If already specified, the corresponding severity is assigned to the alarm and then it is reported to the manager. Otherwise, the original severity is applied. In this use case, the manager sends a request to the agent to set or change the ASAP association. The request parameter is the ID or a list of IDs of the managed entities to be associated with the ASAP.

If the operation succeeds, the agent will return success information, and the ASAP starts to take effect on the specified managed entity(s). If the operation fails, the agent will return error information.

| | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions |
  • – unknown managed entity;
  • – unknown ASAP.
| | +| Post conditions | The association between the ASAP and the specified managed entity(s) is successfully assigned by the agent. The ASAP then takes effect on the associated managed entity(s). | | +| Traceability | REQ-FM-FUN-09 | | + +#### 6.3.4.12 Use case: Unassign ASAP + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-------------------------------------------------------------------------------------------------|-------------------------| +| Goal | A manager removes the association between an ASAP and some of its associated managed entity(s). | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Preconditions | The specified ASAP exists in agent. The association between the ASAP and the specified managed entity(s) has been assigned. The manager does not want the specified managed entity(s) to refer to this ASAP. | | +| Begins when | The manager sends a request to the agent to remove the association between an ASAP and some of its associated managed entity(s). | | +| Step 1 | When an ASAP is associated with a managed object, it starts to take effect. When the association between an ASAP and a managed element is no longer needed, it can be removed. If the manager wants to associate a managed object with another ASAP, the association with the previous ASAP must be removed first. In this use case, the manager sends a remove ASAP association request to the agent. The request parameter is: the ID or list of IDs of the managed entity(s) associated with the ASAP.
If the operation succeeds, the agent will return success information, and the ASAP associated with specified managed object(s) will not take effect any longer.
If the operation fails, the agent will return error information to the manager. | | +| Ends when | The requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – unknown managed entity;
– the association does not exist. | | +| Post conditions | The association between the ASAP and the specified managed object(s) is removed by the agent. The agent may send the related attribute value change notifications to the manager. | | +| Traceability | REQ-FM-FUN-10 | | + +#### 6.3.4.13 Use case: Query ASAP + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | A manager queries the information of an ASAP through the management interface. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified ASAP exists in the agent. | | +| Begins when | The manager sends a request to query the information of an ASAP. | | +| Step 1 | The manager sends a request to the agent to query the attribute information of an ASAP, which includes the ID of the ASAP, the list of the problem and the corresponding severity, and the list of managed entities that have been associated with this ASAP. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| | If the operation succeeds, the agent will return the corresponding attribute values of the ASAP. If the operation fails, the agent will return error information. | | +| Ends when | The requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | None. | | +| Post conditions | The corresponding ASAP information is returned by the agent. | | +| Traceability | REQ-FM-FUN-11 | | + +#### 6.3.4.14 Use case: Add Comment + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager requests that a comment be added to the attributes of an alarm. | | +| Actor and roles | The manager invokes operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available.
The agent supports an operation of adding comment. | | +| Preconditions | The alarm exists. | | +| Begins when | The manager requests a comment be added to an alarm. | | +| Step 1 | The manager sends a request to the agent to add a comment to an alarm, which includes the date and time of the annotation, the text of the comment, the userid, and the identifier of the manager. | | +| Ends when | The requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – invalid alarm identifier;
– invalid parameters. | | +| Post conditions | The agent adds the comment to the specified alarms and sends a notification of the event to subscribed managers. | | +| Traceability | REQ-FM-FUN-14 | | + +# 7 Analysis + +## 7.1 Concepts and background + +The alarm management service makes use of the common management services shown in Figures 7-1 and 7-2. + +![Figure 7-1 – System context A: A diagram showing a Manager (Managing system) connected to an Agent (Managed system), which is connected to Resources. A dashed vertical line separates the Managing system from the Managed system. The Alarm management service is associated with the Manager, and the Notification management service is associated with the Agent. The text M.3703(10)_F7-1 is present in the bottom right.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +Figure 7-1 – System context A: A diagram showing a Manager (Managing system) connected to an Agent (Managed system), which is connected to Resources. A dashed vertical line separates the Managing system from the Managed system. The Alarm management service is associated with the Manager, and the Notification management service is associated with the Agent. The text M.3703(10)\_F7-1 is present in the bottom right. + +**Figure 7-1 – System context A** + +![Figure 7-2 – System context B: A diagram showing a Manager (Managing system) connected to an Agent (Managed system). The Agent is connected to Resources. A dashed vertical line separates the Managing system from the Managed system. The Alarm management service is associated with the Manager, and the Notification management service is associated with the Agent. The text M.3703(10)_F7-2 is present in the bottom right.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +Figure 7-2 – System context B: A diagram showing a Manager (Managing system) connected to an Agent (Managed system). The Agent is connected to Resources. A dashed vertical line separates the Managing system from the Managed system. The Alarm management service is associated with the Manager, and the Notification management service is associated with the Agent. The text M.3703(10)\_F7-2 is present in the bottom right. + +**Figure 7-2 – System context B** + +## **7.2 Information object classes** + +### **7.2.1 Imported information entities and local label** + +| Label reference | Local label | +|-----------------------------------------------------------|-----------------| +| [ITU-T M.3702], information object class, NotificationIRP | NotificationIRP | +| [ITU-T M.3160], information object class, Top | Top | + +### **7.2.2 Class diagram** + +This clause introduces the set of information object classes (IOCs) that encapsulate information within the agent. The intent is to identify the information required for the alarm 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. + +#### 7.2.2.1 Attributes and relationships + +![UML Class Diagram showing Alarm management information object classes and their relationships.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +The <> MonitoredEntity represents a subset of information of an IOC that can emit alarms + +``` + +classDiagram + class MonitoredEntity { + <> + } + class ASAP { + <> + } + class AlarmInformation { + <> + } + class AlarmIRP { + <> + } + class AlarmList { + <> + } + class CorrelatedNotification { + <> + } + class AlarmInformation_O { + <> + } + class AlarmInformation_Clear { + <> + } + class AlarmInformation_Security { + <> + } + class Comment { + <> + } + + MonitoredEntity "1" -- "0..*" ASAP : relation-ASAP-MonitoredEntity + MonitoredEntity "1" -- "0..1" AlarmInformation : relation-BackUpObject-AlarmInformation + MonitoredEntity "1" -- "0..*" AlarmInformation : relation-AlarmedObject-AlarmInformation + ASAP "1" -- "0..*" MonitoredEntity : #identifyASAP + ASAP "1" -- "0..1" MonitoredEntity : #identifyMonitoredEntity + AlarmInformation "0..*" -- "1" MonitoredEntity : #identifyAlarmObject + AlarmInformation "0..*" -- "1" ASAP : #identifyAlarmInformation + AlarmInformation "0..*" -- "1" AlarmIRP : #identifyAlarmInformation + AlarmInformation "0..*" -- "1" AlarmList : #identifyAlarmInformation + AlarmInformation "0..*" -- "0..*" CorrelatedNotification : relation-AlarmInformation-CorrelatedNotification + AlarmInformation "0..*" -- "0..1" AlarmInformation_O : #theAlarmInformation + AlarmInformation "0..*" -- "0..1" AlarmInformation_Clear : #theAlarmInformation + AlarmInformation "0..*" -- "0..1" AlarmInformation_Security : #theAlarmInformation + AlarmInformation "0..*" -- "0..*" Comment : relation-AlarmInformation-Comment + AlarmIRP "1..*" -- "0..*" AlarmList : relation-AlarmIRP-AlarmList + AlarmList "1" -- "0..*" AlarmIRP : #identifyAlarmList + AlarmList "1" -- "0..*" AlarmInformation : relation-AlarmList-AlarmInformation + CorrelatedNotification "0..*" -- "0..*" AlarmInformation : #identifyCorrelatedNotification + +``` + +Detailed description of the diagram: The diagram illustrates the relationships between various information object classes in an alarm management system. At the top left, a note states that the <> MonitoredEntity represents a subset of information of an IOC that can emit alarms. MonitoredEntity is connected to ASAP (relation-ASAP-MonitoredEntity), AlarmInformation (relation-BackUpObject-AlarmInformation and relation-AlarmedObject-AlarmInformation), and AlarmIRP (via #identifyAlarmObject). ASAP is connected to MonitoredEntity (via #identifyASAP and #identifyMonitoredEntity). AlarmInformation is the central class, connected to MonitoredEntity, ASAP, AlarmIRP, AlarmList, CorrelatedNotification (relation-AlarmInformation-CorrelatedNotification), AlarmInformation\_O, AlarmInformation\_Clear, AlarmInformation\_Security, and Comment (relation-AlarmInformation-Comment). AlarmIRP and AlarmList are connected to each other (relation-AlarmIRP-AlarmList). CorrelatedNotification is connected to AlarmInformation (via #identifyCorrelatedNotification). The multiplicities and role names are as follows: MonitoredEntity (1) to ASAP (0..\*); MonitoredEntity (1) to AlarmInformation (0..1 and 0..\*); ASAP (1) to MonitoredEntity (0..\*); AlarmInformation (0..\*) to MonitoredEntity (1); AlarmInformation (0..\*) to ASAP (1); AlarmInformation (0..\*) to AlarmIRP (1); AlarmInformation (0..\*) to AlarmList (1); AlarmInformation (0..\*) to CorrelatedNotification (0..\*); AlarmInformation (0..\*) to AlarmInformation\_O (0..1); AlarmInformation (0..\*) to AlarmInformation\_Clear (0..1); AlarmInformation (0..\*) to AlarmInformation\_Security (0..1); AlarmInformation (0..\*) to Comment (0..\*); AlarmIRP (1..\*) to AlarmList (0..\*); AlarmList (1) to AlarmIRP (0..\*); AlarmList (1) to AlarmInformation (0..\*); CorrelatedNotification (0..\*) to AlarmInformation (0..\*). + +UML Class Diagram showing Alarm management information object classes and their relationships. + +Figure 7-3 – Alarm management information object classes + +#### 7.2.2.2 Inheritance + +![UML class diagram showing inheritance for Alarm management IOC. The central class is 'Top (M.3160)'. Subclasses inheriting from it are: 'AlarmInformation_Security', 'AlarmInformation_O', 'Comment', 'AlarmList', 'AlarmInformation', 'ASAP', 'NotificationIRP (M.3702)', and 'CorrelatedNotification'. 'CorrelatedNotification' inherits from 'NotificationIRP (M.3702)'.](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +``` + +classDiagram + class Top["<> Top (M.3160)"] + class AlarmInformation_Security["<> AlarmInformation_Security"] + class AlarmInformation_O["<> AlarmInformation_O"] + class Comment["<> Comment"] + class AlarmList["<> AlarmList"] + class AlarmInformation["<> AlarmInformation"] + class ASAP["<> ASAP"] + class NotificationIRP["<> NotificationIRP (M.3702)"] + class CorrelatedNotification["<> CorrelatedNotification"] + class AlarmInformation_Clear["<> AlarmInformation_Clear"] + + Top <|-- AlarmInformation_Security + Top <|-- AlarmInformation_O + Top <|-- Comment + Top <|-- AlarmList + Top <|-- AlarmInformation + Top <|-- ASAP + Top <|-- NotificationIRP + Top <|-- AlarmInformation_Clear + CorrelatedNotification <|-- NotificationIRP + +``` + +M.3703(10)\_7-4 + +UML class diagram showing inheritance for Alarm management IOC. The central class is 'Top (M.3160)'. Subclasses inheriting from it are: 'AlarmInformation\_Security', 'AlarmInformation\_O', 'Comment', 'AlarmList', 'AlarmInformation', 'ASAP', 'NotificationIRP (M.3702)', and 'CorrelatedNotification'. 'CorrelatedNotification' inherits from 'NotificationIRP (M.3702)'. + +Figure 7-4 – Alarm management IOC inheritance + +### 7.2.3 Information object class definitions + +| Class name | Qualifier | Requirement IDs | +|---------------------------|-----------------|------------------------------------------------------------------------------------------| +| AlarmInformation | M | REQ-FM-FUN-01, REQ-FM-FUN-02, REQ-FM-FUN-03, REQ-FM-FUN-12 | +| AlarmInformation_O | O | REQ-FM-FUN-01, REQ-FM-FUN-02, REQ-FM-FUN-03, REQ-FM-FUN-12 | +| AlarmInformation_Clear | CO (see Note 1) | REQ-FM-FUN-04 | +| AlarmInformation_Security | CO (see Note 2) | REQ-FM-FUN-01 | +| AlarmList | M | REQ-FM-FUN-05, REQ-FM-FUN-17 | +| Comment | M | REQ-FM-FUN-14 | +| CorrelatedNotification | M | REQ-FM-FUN-01 | +| ASAP | O | REQ-FM-FUN-06, REQ-FM-FUN-07, REQ-FM-FUN-08, REQ-FM-FUN-09, REQ-FM-FUN-10, REQ-FM-FUN-11 | +| AlarmIRP | M | REQ-FM-FUN-01, REQ-FM-FUN-05, REQ-FM-FUN-17 | + +NOTE 1 – These attributes and qualifiers are applicable only if the agent supports `clearAlarms()` (they are absent if `clearAlarms()` is not supported). + +NOTE 2 – These attributes must be supported if the agent emits `NewAlarmNotification` that carries security alarm information. + +#### 7.2.3.1 AlarmInformation + +##### 7.2.3.1.1 Definition + +`AlarmInformation` contains information about the alarm condition of an alarmed `MonitoredEntity`. + +One Agent is related to at most one AlarmList. The Agent or its related AlarmIRP or the related AlarmList assigns an identifier, called alarmId, to each AlarmInformation in the AlarmList. An alarmId unambiguously identifies one AlarmInformation in the AlarmList. + +##### 7.2.3.1.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-------------------|-------------------|----------------|-----------------|-----------------| +| alarmId | M | M | – | REQ-FM-FUN-01 | +| alarmRaisedTime | M | M | – | REQ-FM-FUN-01 | +| alarmClearedTime | M | M | M | REQ-FM-FUN-03 | +| eventType | M | M | – | REQ-FM-FUN-01 | +| probableCause | M | M | – | REQ-FM-FUN-01 | +| perceivedSeverity | M | M | M | REQ-FM-FUN-01 | +| ackTime | M | M | M | REQ-FM-FUN-12 | +| ackUserId | M | M | M | REQ-FM-FUN-12 | +| ackState | M | M | M | REQ-FM-FUN-12 | + +##### 7.2.3.1.3 State diagram + +Alarms have states. The alarm state information is captured in AlarmInformation in perceivedSeverity and ackState. + +The solid circle icon represents the Start State. The double circle icon represents the End State. In the End State, the alarm is Cleared and acknowledged. The AlarmInformation shall not be accessible via the IRP and is removed from the AlarmList. + +Note the state diagram uses " X / Y ^ Z " to label the arc that indicates state transition. The meanings of X, Y and Z are: + +- X identifies the triggering event; +- Y identifies the action of Agent because of the triggering event; +- Z is the notification to be emitted by Agent because of the triggering event. + +Note that acknowledgeAlarm^notifyAckStateChanged and the unacknowledgeAlarm^notifyAckStateChange refer to cases when the request of the Manager is successful for the AlarmInformation concerned. They do not refer to the cases when the request is a failure since in the failure cases, no state transition would occur. + +Note that, to reduce cluttering, the setComment^notifyComment is not included in the figure. One transition should be applied from unack&unclear to itself. Similarly, another transition should be applied from ack&unclear to itself and another one from unack&clear to itself. + +Note that "PS", used in the state diagram, stands for "perceived severity". + +![State transition diagram for Alarm state transfer. It shows four states: unack&unclear, ack&unclear, unack&clear, and ack&clear. Transitions are triggered by events like 'MO emits alarm', 'MO PS changes', or 'AlarmInformation deleted from AlarmList'. A callout box notes that matching-criteria-attributes are not identical to those in AlarmList.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +The MO alarm's matching-criteria-attributes are not identical to the matching-criteria-attributes of any AlarmInformation in AlarmList. See appendix for the definition of matching-criteria-attributes. + +``` + +stateDiagram-v2 + [*] --> unack&unclear : MO emits alarm & IRPAGENT creates a new AlarmInformation. ^notifyNewAlarm + unack&unclear --> [*] : MO PS changes to cleared ^notifyClearedAlarm + unack&unclear --> ack&unclear : acknowledgeAlarm ^notifyAckStateChanged + ack&unclear --> unack&unclear : unacknowledgeAlarm ^notifyAckStateChange + unack&unclear --> unack&clear : MO PS level changes to cleared ^notifyClearedAlarm + unack&clear --> ack&unclear : acknowledgeAlarm ^notifyAckStateChanged + ack&unclear --> unack&clear : MO PS changes and new level is not cleared & IRPAGENT supports notifyChangedAlarm ^notifyChangedAlarm + unack&clear --> ack&clear : acknowledgeAlarm ^notifyAckStateChanged + ack&clear --> [*] : AlarmInformation deleted from AlarmList + unack&unclear --> unack&unclear : MO emits alarm & IRPAGENT does not support notifyChangedAlarm ^notifyClearedAlarm, notifyNewAlarm + unack&unclear --> unack&unclear : MO emits alarm & IRPAGENT supports notifyChangedAlarm ^notifyChangedAlarm + unack&unclear --> unack&unclear : MO PS changes & new level is not cleared & IRPAGENT does not support notifyChangedAlarm ^notifyClearedAlarm... + +``` + +M.3703(10)\_7-5 + +State transition diagram for Alarm state transfer. It shows four states: unack&unclear, ack&unclear, unack&clear, and ack&clear. Transitions are triggered by events like 'MO emits alarm', 'MO PS changes', or 'AlarmInformation deleted from AlarmList'. A callout box notes that matching-criteria-attributes are not identical to those in AlarmList. + +Figure 7-5 – Alarm state transfer + +#### 7.2.3.2 AlarmInformation\_O + +##### 7.2.3.2.1 Definition + +AlarmInformation\_o contains optional information about the alarm condition of an alarmed MonitoredEntity. + +##### 7.2.3.2.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-------------------------|-------------------|----------------|-----------------|---------------------------------------------| +| alarmChangedTime | O | O | O | REQ-FM-FUN-03, REQ-FM-FUN-12 | +| vendorSpecificAlarmType | O | O | – | REQ-FM-FUN-01 | +| specificProblem | O | O | – | REQ-FM-FUN-01 | +| backedUpStatus | O | O | – | REQ-FM-FUN-01 | +| backedUpObject | O | O | – | REQ-FM-FUN-01 | +| trendIndication | O | O | – | REQ-FM-FUN-01 | +| stateChangedDefinition | O | O | – | REQ-FM-FUN-01, REQ-FM-FUN-03, REQ-FM-FUN-12 | +| monitoredAttributes | O | O | – | REQ-FM-FUN-01, REQ-FM-FUN-02 | + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-----------------------|-------------------|----------------|-----------------|-----------------| +| proposedRepairActions | O | O | – | REQ-FM-FUN-01 | +| additionalText | O | O | – | REQ-FM-FUN-01 | +| additionalInformation | O | O | – | REQ-FM-FUN-01 | +| ackSystemId | O | O | O | REQ-FM-FUN-12 | + +##### 7.2.3.2.3 State diagram + +The same as the state diagram for AlarmInformation. + +#### 7.2.3.3 AlarmInformation\_Clear + +##### 7.2.3.3.1 Definition + +AlarmInformation\_Clear contains optional information. These attributes and qualifiers are applicable only if the agent supports clearAlarms() (they are absent if clearAlarms() is not supported). + +##### 7.2.3.3.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------|-------------------|----------------|-----------------|-----------------| +| clearUserId | O | M | M | REQ-FM-FUN-04 | +| clearSystemId | O | O | O | REQ-FM-FUN-04 | + +##### 7.2.3.3.3 State diagram + +The same as the state diagram for AlarmInformation. + +#### 7.2.3.4 AlarmInformation\_Security + +##### 7.2.3.4.1 Definition + +AlarmInformation\_Security contains optional information. These attributes must be supported if the agent emits NewAlarmNotification that carries security alarm information. + +##### 7.2.3.4.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-----------------------|-------------------|----------------|-----------------|-----------------| +| serviceUser | O | O | – | REQ-FM-FUN-01 | +| serviceProvider | O | O | – | REQ-FM-FUN-01 | +| securityAlarmDetector | O | O | – | REQ-FM-FUN-01 | + +##### 7.2.3.4.3 State diagram + +The same as the state diagram for AlarmInformation. + +#### 7.2.3.5 AlarmList + +##### 7.2.3.5.1 Definition + +Agent maintains an AlarmList. It contains all currently active alarms (i.e., AlarmInformation whose perceivedSeverity is not Cleared) and alarms that are Cleared but not yet acknowledged. + +##### 7.2.3.5.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------|-------------------|----------------|-----------------|------------------------------| +| alarmListId | M | M | – | REQ-FM-FUN-05, REQ-FM-FUN-17 | +| alarmList | M | M | M | REQ-FM-FUN-05, REQ-FM-FUN-17 | + +##### 7.2.3.5.3 State diagram + +There is no state for this class. + +#### 7.2.3.6 ASAP + +##### 7.2.3.6.1 Definition + +The manager needs to assign the alarm severities for a set of problems, so that when an agent reports alarms, these pre-assigned severities can be referenced in the corresponding alarm notifications. The manager can create an ASAP on an agent to define the relationship between severity level and problem. + +##### 7.2.3.6.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------|-------------------|----------------|-----------------|-----------------| +| aSAPIId | M | M | – | REQ-FM-FUN-06 | +| aSAPInfoList | M | M | M | REQ-FM-FUN-06 | + +##### 7.2.3.6.3 State diagram + +There is no state for this class. + +#### 7.2.3.7 AlarmIRP + +##### 7.2.3.7.1 Definition + +AlarmIRP is the representation of the alarm management capabilities specified by the present Recommendation. Through AlarmIRP, the manager can configure ASAP, retrieve AlarmList and acknowledge/unacknowledge Alarm, etc. + +##### 7.2.3.7.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------|-------------------|----------------|-----------------|------------------------------| +| alarmIRPIId | M | M | – | REQ-FM-FUN-01 | +| alarmListId | M | M | – | REQ-FM-FUN-05, REQ-FM-FUN-17 | + +##### 7.2.3.7.3 State diagram + +There is no state for this class. + +#### 7.2.3.8 Comment + +##### 7.2.3.8.1 Definition + +Comment contains commentaries and associated information such as the time when the commentary is made. + +##### 7.2.3.8.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-----------------|-------------------|----------------|-----------------|-----------------| +| commentTime | M | M | M | REQ-FM-FUN-14 | +| commentText | M | M | M | REQ-FM-FUN-14 | +| commentUserId | M | M | M | REQ-FM-FUN-14 | +| commentSystemId | O | O | O | REQ-FM-FUN-14 | + +##### 7.2.3.8.3 State diagram + +There is no state for this class. + +#### 7.2.3.9 CorrelatedNotification + +##### 7.2.3.9.1 Definition + +It identifies one MonitoredEntity. For that MonitoredEntity identified, a set of notification identifiers is also identified. One or more CorrelatedNotification instances can be related to an AlarmInformation. In this case, the information of the AlarmInformation is said to be correlated to information carried in the notifications identified by the CorrelatedNotification instances. See further definition of correlated notification in clause 8.1.2.9 of [ITU-T X.733]. + +The meaning of correlation is dependent on the type of notification itself. See the comment column of the correlatedNotification input parameter for each type of notification, such as NewAlarmNotification. + +Notification carries AlarmInformation. The AlarmInformation instances referred to by the correlatedNotification may or may not exist in the AlarmList. For example, the AlarmInformation carried by the identified notification may have been acknowledged and Cleared and therefore, no longer exist in the AlarmList. + +##### 7.2.3.9.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|-------------------|-------------------|----------------|-----------------|-----------------| +| source | M | M | – | REQ-FM-FUN-01 | +| notificationIdSet | M | M | – | REQ-FM-FUN-01 | + +##### 7.2.3.9.3 State diagram + +There is no state for this class. + +### 7.2.4 Information relationship definitions + +| Relationship | Support qualifier | Requirement IDs | +|--------------------------------------------------|-------------------|------------------------------| +| relation-AlarmIRP-AlarmList (M) | M | REQ-FM-FUN-05, REQ-FM-FUN-17 | +| relation-AlarmList-AlarmInformation | M | REQ-FM-FUN-05, REQ-FM-FUN-07 | +| relation-AlarmInformation-Comment | M | REQ-FM-FUN-14 | +| relation-AlarmInformation-CorrelatedNotification | M | REQ-FM-FUN-01 | + +| Relationship | Support qualifier | Requirement IDs | +|-----------------------------------------|-------------------|-----------------| +| relation-AlarmedObject-AlarmInformation | M | REQ-FM-FUN-01 | +| relation-BackUpObject-AlarmInformation | O | REQ-FM-FUN-01 | +| relation-ASAP-MonitoredEntity | M | REQ-FM-FUN-06 | + +#### 7.2.4.1 relation-AlarmIRP-AlarmList (M) + +##### 7.2.4.1.1 Definition + +This represents the relationship between `AlarmIRP` and `AlarmList`. + +##### 7.2.4.1.2 Role + +| Name | Definition | +|-------------------|----------------------------------------------------------------------------------------------| +| identifyAlarmIRP | It represents the capability to obtain the identities of one or more AlarmIRP . | +| identifyAlarmList | It represents the capability to obtain the identity of one AlarmList . | + +##### 7.2.4.1.3 Constraint + +There is no constraint for this relationship. + +#### 7.2.4.2 relation-AlarmList-AlarmInformation (M) + +##### 7.2.4.2.1 Definition + +This represents the relationship between `AlarmList` and `AlarmInformation`. + +##### 7.2.4.2.2 Role + +| Name | Definition | +|--------------------------|---------------------------------------------------------------------------------------------------| +| identifyAlarmList | It represents the AlarmList . | +| identifyAlarmInformation | It represents a capability to obtain the information contained in AlarmInformation . | + +##### 7.2.4.2.3 Constraint + +| Name | Definition | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| inv_hasAlarmInformation1 | No AlarmInformation playing the role of the AlarmInformation shall have its perceivedSeverity = "cleared" and its ackState = "acknowledged". | +| inv_hasAlarmInformation2 | The alarmId of all AlarmInformation instances playing the role of the AlarmInformation are distinct. | + +#### 7.2.4.3 relation-AlarmInformation-Comment (M) + +##### 7.2.4.3.1 Definition + +This represents the relationship between `AlarmInformation` and `Comment`. + +##### 7.2.4.3.2 Role + +| Name | Definition | +|---------------------|----------------------------------------------------------------------------| +| theAlarmInformation | It represents the AlarmInformation. | +| identifyComment | It represents a capability to obtain the information contained in Comment. | + +##### 7.2.4.3.3 Constraint + +There is no constraint. + +#### 7.2.4.4 relation-AlarmInformation-CorrelatedNotification (M) + +##### 7.2.4.4.1 Definition + +This represents the relationship between AlarmInformation and CorrelatedNotification. + +##### 7.2.4.4.2 Role + +| Name | Definition | +|--------------------------------|-------------------------------------------------------------------------------------------| +| theAlarmInformation | It represents the AlarmInformation. | +| identifyCorrelatedNotification | It represents a capability to obtain the information contained in CorrelatedNotification. | + +##### 7.2.4.4.3 Constraint + +There is no constraint. + +#### 7.2.4.5 relation-AlarmedObject-AlarmInformation (M) + +##### 7.2.4.5.1 Definition + +This represents the relationship between MonitoredEntity and AlarmInformation. + +##### 7.2.4.5.2 Role + +| Name | Definition | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| identifyAlarmedObject | It represents the capability to obtain the identification, in terms of objectClass and objectInstance, of alarmed network resource. | +| identifyAlarmInformation | It represents the capability to obtain the identities of AlarmInformation. | + +##### 7.2.4.5.3 Constraint + +There is no constraint. + +#### 7.2.4.6 relation-backUpObject-AlarmInformation (O) + +##### 7.2.4.6.1 Definition + +The relationship represents the relationship between AlarmInformation and the backUpObject. + +##### 7.2.4.6.2 Role + +| Name | Definition | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------| +| identifyBackUpObject | It represents a capability to obtain the identification, in terms of objectClass and objectInstance, of the backUpObject. | +| identifyAlarmInformation | It represents the capability to obtain the identities of AlarmInformation. | + +##### 7.2.4.6.3 Constraint + +| Name | Definition | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------| +| inv_identifyBackUpObject | This relationship is present if and only if the AlarmInformation.backedUpStatus attribute is present and is indicating true. | + +#### 7.2.4.7 relation-ASAP-MonitoredEntity (M) + +##### 7.2.4.7.1 Definition + +This represents the relationship between ASAP and MonitoredEntity. + +##### 7.2.4.7.2 Role + +| Name | Definition | +|-------------------------|-------------------------------------------------------------------------------------| +| identifyASAP | It represents the capability to obtain the identities of one ASAP. | +| identifyMonitoredEntity | It represents the capability to obtain the identify of one or more MonitoredEntity. | + +##### 7.2.4.7.3 Constraint + +There is no constraint for this relationship. + +### 7.2.5 Information attribute definition + +#### 7.2.5.1 Definition and legal values + +| Name | Definition | Information type/Legal values | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| alarmId | It identifies one AlarmInformation in the AlarmList. | AlarmIdType ::= INTEGER | +| alarmRaisedTime | It indicates the date and time when the alarm is first raised by the alarmed resource. | GeneralizedTime | +| alarmChangedTime | It indicates the last date and time when the AlarmInformation is changed by the alarmed resource. Changes to AlarmInformation caused by invocations of the manager would not change this date and time. | GeneralizedTime | +| alarmClearedTime | It indicates the date and time when the alarm is cleared. | GeneralizedTime | +| eventType | It indicates the type of event. See Annex A for information on event type. | EventType ::= ENUMERATED {
communications_Alarm,
processing_Error_Alarm,
...}
--See Annex A for complete value set. | +| vendorSpecificAlarmType | It indicates the vendor-specific alarm that identifies the NE alarm type or NE related alarm type.
It is a vendor-specific expression of eventType. | String | + +| Name | Definition | Information type/Legal values | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| probableCause | It qualifies alarm and provides further information than eventType. See Annex B for a complete listing. | ProbableCauseType ::= ENUMERATED {
alarm_Indication_Signal
,
broadcast_Channel_Failure,...}
--See Annex B for
complete value set. | +| perceivedSeverity | It indicates the relative level of urgency for operator attention. This IRP does not recommend the use of indeterminate. | PerceivedSeverityType ::= ENUMERATED {
critical, major,
minor, warning,
indeterminate, cleared} | +| specificProblem | It provides further qualification on the alarm than probableCause. This attribute value shall be single-value and of simple type such as integer or string. See definition in clause 8.1.2.2 of [ITU-T X.733]. | String | +| backedUpStatus | It indicates if an object (the MonitoredEntity) has a back up. See definition in clause 8.1.2.4 of [ITU-T X.733]. | BOOLEAN | +| trendIndication | It indicates if some observed condition is getting better, worse, or is not changing. | TrendIndicationType ::= ENUMERATED {
less_Severe,
no_Change, more_Severe} | +| stateChangeDefinition | It indicates MO attribute value changes. See definition in clause 8.1.2.10 of [ITU-T X.733]. | String | +| monitoredAttributes | It indicates MO attributes whose value changes are being monitored. See definition in clause 8.1.2.11 of [ITU-T X.733]. | SET OF AttributeName
AttributeName ::= String | +| proposedRepairActions | It indicates proposed repair actions. See definition in clause 8.1.2.12 of [ITU-T X.733]. | SET OF AttributeName | +| additionalText | It carries semantics that is outside the scope of this IRP specification. It may provide the identity of the NE (e.g., RNC, Node-B) from which the alarm has been originated. It corresponds to the "user label" attribute of the object class representing the NE in the Generic Network Resource Model [b-3GPP TS 32.622].
It can contain further information on the alarm. | String | +| additionalInformation | It contains information on the alarm. Its semantics is outside the scope of this IRP. | String | +| ackTime | It identifies the time when the alarm was acknowledged or unacknowledged the last time. | GeneralizedTime | +| ackUserId | It identifies the last user who changed the Acknowledgement State. | String | + +| Name | Definition | Information type/Legal values | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ackSystemId | It identifies the system (EM or NM) from which the alarm was acknowledged or unacknowledged the last time. | String | +| ackState | It identifies the Acknowledgement State of the alarm. | AckStateType ::= ENUMERATED { acknowledged , unacknowledged }
-- acknowledged: the alarm has been acknowledged.
-- unacknowledged: the alarm has been unacknowledged or the alarm has never been acknowledged. | +| aSAPId | It identifies one ASAP in agent. | INTEGER | +| aSAPInfoList | It defines the relationship between severity level and problem. | ASAPInfoListType ::= SEQUENCE { problem ProbableCauseType, severityLevel PerceivedSeverityType } | +| commentTime | It carries the time when the comment has been added to the alarm. | GeneralizedTime | +| commentText | It carries the textual comment. | String | +| commentUserId | It carries the identification of the user who made the comment. | String | +| commentSystemId | It carries the identification of the system (EM or NM) from which the comment is made. That system supports the user that made the comment. | String | +| source | It identifies one MonitoredEntity. | String | +| notificationIdSet | It carries one or more notification identifiers. | SET OF AttributeName | +| clearUserId | It carries the identity of the user who invokes the clearAlarms operation. | String | +| clearSystemId | It carries the identity of the system in which the manager runs. That manager supports the user who invokes the clearAlarms(). | String | +| serviceUser | It identifies the service-user whose request for service provided by the serviceProvider led to the generation of the security alarm. | String | +| serviceProvider | It identifies the service provider whose service is requested by the serviceUser and the service request provokes the generation of the security alarm. | String | +| securityAlarmDetector | It carries the identity of the detector of the security alarm. | String | + +#### 7.2.5.2 Constraints + +| Name | Definition | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| inv_alarmChangedTime | Time indicated shall be later than that carried in alarmRaisedTime. | +| inv_alarmClearedTime | Time indicated shall be later than that carried in alarmRaisedTime. | +| inv_ackTime | Time indicated shall be later than that carried in alarmRaisedTime. | +| inv_notificationId | NotificationIds shall be chosen to be unique across all notifications of a particular Managed Object (representing the NE) throughout the time that alarm correlation is significant. The algorithm by which alarm correlation is accomplished is outside the scope of this IRP. | + +## 7.3 Interface definition + +### 7.3.1 Class diagram + +![UML Class diagram for Alarm management IRP. The central class is AlarmIRP (InformationObjectClass). It has relationships with five interfaces: AlarmIRPOperations, AlarmIRPAcknowledgementOperations, AlarmIRPAlarmListOperations, AlarmIRPAlarmNotifications, and AlarmIRPAlarmListNotifications. Relationships are labeled as <>, <>, or <>.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +``` + +classDiagram + class AlarmIRP { + <> + } + class AlarmIRPOperations { + <> + addComment() + clearAlarms() + } + class AlarmIRPAcknowledgementOperations { + <> + acknowledgeAlarms() + unacknowledgeAlarms() + } + class AlarmIRPAlarmListOperations { + <> + getAlarmList() + } + class AlarmIRPAlarmNotifications { + <> + newAlarmNotification() + alarmClearedNotification() + alarmChangeNotification() + } + class AlarmIRPAlarmListNotifications { + <> + alarmListRebuiltNotification() + potentiallyFaultyAlarmListNotification() + } + class AlarmIRPASAPOperations { + <> + createASAP() + deleteASAP() + modifyASAP() + assignASAP() + unassignASAP() + queryASAP() + } + + AlarmIRP --|> AlarmIRPOperations : <> + AlarmIRP --|> AlarmIRPAcknowledgementOperations : <> + AlarmIRP --|> AlarmIRPAlarmListOperations : <> + AlarmIRP --|> AlarmIRPAlarmNotifications : <> + AlarmIRP --|> AlarmIRPAlarmListNotifications : <> + AlarmIRP --|> AlarmIRPASAPOperations : <> + +``` + +UML Class diagram for Alarm management IRP. The central class is AlarmIRP (InformationObjectClass). It has relationships with five interfaces: AlarmIRPOperations, AlarmIRPAcknowledgementOperations, AlarmIRPAlarmListOperations, AlarmIRPAlarmNotifications, and AlarmIRPAlarmListNotifications. Relationships are labeled as <>, <>, or <>. + +M.3703(10)\_7-6 + +Figure 7-6 – Alarm management IRP class diagram + +AlarmIRP must realize the operations defined by AlarmIRPAcknowledgementOperations and AlarmIRPAlarmListOperations, and it may realize the operations defined by AlarmIRPOperations. At the same time, AlarmIRP must have the capability to emit the notifications defined by the AlarmIRPAlarmNotifications, and it may have the capability to emit the notifications defined by the AlarmIRPAlarmListNotifications. + +### 7.3.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 regard 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 that is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state. + +### 7.3.3 Interface AlarmIRPAcknowledgementOperations (O) + +| Operation name | Qualifier | Requirement IDs | +|---------------------|-----------|------------------------------------------------------------| +| acknowledgeAlarms | M | REQ-FM-FUN-12, REQ-FM-FUN-13, REQ-FM-FUN-15, REQ-FM-FUN-16 | +| unacknowledgeAlarms | O | REQ-FM-FUN-12 | + +#### 7.3.3.1 acknowledgeAlarms (M) + +##### 7.3.3.1.1 Definition + +The Manager invokes this operation to acknowledge one or more alarms. + +##### 7.3.3.1.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|------------------------------------------|-----------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmInformationAndSeverityReferenceList | M | SET OF SEQUENCE
{ alarmId
AlarmIdType,
perceivedSeverity
PerceivedSeverityType
OPTIONAL
} | It carries one or more identifiers identifying AlarmInformation instances in AlarmList, including optionally the perceivedSeverity of the AlarmInformation instance that is going to be acknowledged.
alarmInformationAndSeverityReferenceList
{ alarmId - Mandatory;
perceivedSeverity - Optional
} | +| ackUserId | M | String | It identifies the user acknowledging the alarm. | +| ackSystemId | O | String | It identifies the processing system on which the subject Manager runs. It may be absent implying that Manager does not wish this information be kept in AlarmInformation in AlarmList. | + +##### 7.3.3.1.3 Output parameters + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| badAlarmInformationReferenceList | M | SET OF BadAlarmInfo
BadAlarmInfo ::=
SEQUENCE {
alarmId AlarmIdType,
reason ENUMERATED {
unknownAlarmId,
acknowledgmentFailed,
wrongPerceivedSeverity
}
} |

If allAlarmsAcknowledged is true, it contains no information.

If someAlarmAcknowledged is true, then it contains identifications of AlarmInformation that are a) present in input parameter AlarmInformationReferenceList but are absent in the AlarmList = UnknownAlarmId; or

b) present in input parameter AlarmInformationReferenceList and are present in the AlarmList but the Acknowledgement Information (see note) has not changed, in contrast to Manager's request = AcknowledgmentFailed; or

c) present in input parameter AlarmInformationReferenceList and are present in the AlarmList but the perceivedSeverity to be acknowledged has changed and/or is different within the AlarmList = WrongPerceivedSeverity (applicable only if perceivedSeverity was provided).

| +| status | M | StatusType ::=
ENUMERATED
{ operationSucceeded,
operationFailed,
operationPartiallySucceeded
} |

If someAlarmAcknowledged is true, status = OperationPartiallySucceeded.

If allAlarmsAcknowledged is true, status = OperationSucceeded.

If operation_failed is true, status = OperationFailed.

| +| NOTE – Acknowledgement Information is defined as the information contained in AlarmInformation.ackTime, AlarmInformation.ackUserId, AlarmInformation.ackSystemId, AlarmInformation.ackState. | | | | + +##### 7.3.3.1.4 Pre-condition + +atLeastOneValidId. + +| Assertion name | Definition | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| atLeastOneValidId | The AlarmInformationReferenceList contains at least one identifier that identifies one AlarmInformation in AlarmList and this identified AlarmInformation shall have its ackState indicating "unacknowledged" and, if provided, an equal perceivedSeverity. | + +##### 7.3.3.1.5 Post-condition + +someAlarmAcknowledged OR allAlarmsAcknowledged. + +| Assertion name | Definition | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| someAlarmAcknowledged | At least one but not all AlarmInformation identified in input parameter AlarmInformationReferenceList has been acknowledged. Acknowledgement of an AlarmInformation means that the ackState attribute has been set to "acknowledged", that ackUserId, ackSystemId attributes of this AlarmInformation have been set to the values provided as input parameter and that the time of acknowledgeAlarms operation has been registered in ackTime attribute. | +| allAlarmsAcknowledged | All AlarmInformation identified in input parameter have been acknowledged. Acknowledgement of an AlarmInformation means that the ackState attribute has been set to "acknowledged", that ackUserId, ackSystemId attributes of this AlarmInformation have been set to the values provided as input parameter and that the time of acknowledgeAlarms operation has been registered in ackTime attribute. | + +##### 7.3.3.1.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.2 unacknowledgeAlarms (O) + +##### 7.3.3.2.1 Definition + +Manager invokes this operation to remove acknowledgement information kept in one or more AlarmInformation instances. + +##### 7.3.3.2.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|-----------------|-----------|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| correlatedIdSet | M | SET OF
CorrelatedIdInfo
CorrelatedIdInfo ::=
SEQUENCE {
source String,
alarmid AlarmIdType} | It carries one or more identifiers identifying AlarmInformation instances in AlarmList | +| ackUserId | M | String | It identifies the user that invokes this operation. | +| ackSystemId | O | String | It identifies the processing system on which the subject Manager runs. | + +##### 7.3.3.2.3 Output parameters + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|----------------------------------|-----------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| badAlarmInformationReferenceList | M | SET OF BadAlarmInfo |

If allAlarmsUnacknowledged is true, it contains no information.

If someAlarmUnacknowledged is true, then it contains identifications of AlarmInformation that are

  1. present in input parameter AlarmInformationReferenceList but are absent in the AlarmList; or
  2. present in input parameter AlarmInformationReferenceList and are present in the AlarmList but the acknowledgement information (see note) has not changed, in contrast to manager's request.
| +| status | M | StatusType |

If someAlarmUnacknowledged is true, status = OperationPartiallySucceeded.

If allAlarmsUnacknowledged is true, status = OperationSucceeded.

If operation_failed is true, status = OperationFailed.

| + +NOTE – Acknowledgement Information is defined as the information contained in AlarmInformation.ackTime, AlarmInformation.ackUserId, AlarmInformation.ackSystemId and AlarmInformation.ackState. + +##### 7.3.3.2.4 Pre-condition + +atLeastOneValidId. + +| Assertion name | Definition | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| atLeastOneValidId | The AlarmInformationReferenceList contains at least one identifier that identifies one AlarmInformation in AlarmList and that this identified AlarmInformation shall have its ackState indicating "acknowledged". | + +##### 7.3.3.2.5 Post-condition + +someAlarmUnacknowledged OR allAlarmsUnacknowledged. + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| someAlarmUnacknowledged | At least one but not all AlarmInformation identified in input parameter alarmListReferenceList has been unacknowledged. This means that the ackState attribute has been set to "unacknowledged", that ackTime, ackUserId, ackSystemId attributes of this AlarmInformation have been set to containing no information. | +| allAlarmsUnacknowledged | All AlarmInformation identified in input parameter have been unacknowledged. This means that the ackState attribute has been set to "unacknowledged", that ackTime, ackUserId, ackSystemId attributes of this AlarmInformation have been set to contain no information. | + +##### 7.3.3.2.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +### 7.3.4 Interface AlarmIRPOperations (O) + +| Operation name | Qualifier | Requirement IDs | +|----------------|-----------|-----------------| +| addComment | O | REQ-FM-FUN-14 | +| clearAlarms | O | REQ-FM-FUN-04 | + +#### 7.3.4.1 addComment (O) + +##### 7.3.4.1.1 Definition + +The Manager invokes this operation to record a comment in one or more AlarmInformation instances in AlarmList. + +If this operation is supported, the AlarmChangeNotification notification must be supported by the IRP for issuing notifications of invocations of this interface. + +##### 7.3.4.1.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|-------------------------------|-----------|-------------------------------|----------------------------------------------------------------------------------------------------------------------| +| alarmInformationReferenceList | M | SET OF AlarmIdType | It carries one or more identifiers identifying AlarmInformation instances in the AlarmList. | +| commentUserId | M | String | The Comment.commentUserId where Comment is involved in relation-AlarmInformation-Comment with an AlarmInformation. | +| commentSystemId | O | String | The Comment.commentSystemId where Comment is involved in relation-AlarmInformation-Comment with an AlarmInformation. | +| commentText | M | String | The comment.commentText where Comment is involved in relation-AlarmInformation-Comment with an AlarmInformation. | + +##### 7.3.4.1.3 Output parameter + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|------------------------------------|-----------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| badAlarm Information ReferenceList | M | SET OF BadAlarmInfo |

If allUpdated is true, it contains no information.

If someUpdated is true, then it contains identifications of AlarmInformation that are not present in AlarmList or that are present, but AlarmInformation.comments has not changed, in contrast to manager's request.

| +| status | M | StatusType |

If allUpdated is true, then status = OperationSucceeded.

If someUpdated is true, then status = OperationPartiallyFailed.

If exception operationFailed is raised, then status = OperationFailed.

| + +##### 7.3.4.1.4 Pre-condition + +atLeastOneValidId. + +| Assertion name | Properties | +|-------------------|-----------------------------------------------------------------------------------------------------------------------| +| atLeastOneValidId | The AlarmInformationReferenceList contains at least one identifier that identifies one AlarmInformation in AlarmList. | + +##### 7.3.4.1.5 Post-condition + +allUpdated OR someUpdated. + +| Assertion name | Properties | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allUpdated |

The AlarmInformation.comment of all alarms identified by the input parameter AlarmInformationReferenceList has been updated.

The input parameters commentText, commentUserId and commentSystemId are added to the AlarmInformation.comment. The time of the operation invocation is captured in the AlarmInformation.comment as well.

To make it possible to add the new comment, the agent may remove one or more old comments previously held by AlarmInformation.comments.

| +| someUpdated |

The AlarmInformation.comment attribute of at least one but not all alarms identified by the input parameter AlarmInformationReferenceList has been updated.

The input parameters commentText, commentUserId and commentSystemId are added to the AlarmInformation.comment. The time of the operation invocation is captured in the AlarmInformation.comment as well.

To add a new Comment, it may be necessary to remove one or more old Comment instances being held. The commentTime of the removed Comment instances shall be older than that of the remaining Comment instances.

| + +##### 7.3.4.1.6 Exceptions + +| Name | Properties | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: The pre-condition is false or the post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.4.2 clearAlarms (O) + +##### 7.3.4.2.1 Definition + +The Manager invokes this operation to clear one or more AlarmInformation instances in AlarmList. For example, this operation can be used to support the manual clearing of the ADMC. + +##### 7.3.4.2.2 Input parameter + +| Name | Qualifier | Information type/Legal values | Comment | +|-------------------------------|-----------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmInformationReferenceList | M | SET OF AlarmIdType | It carries one or more identifiers identifying AlarmInformation instances in the AlarmList. | +| clearUserId | M | String | It identifies the user clearing the alarm. | +| clearSystemId | O | String | It identifies the processing system on which the subject the manager runs. It may be absent implying that the manager does not wish this information be known to the agent. | + +##### 7.3.4.2.3 Output parameter + +| Name | Qualifier | Matching information/ Information type/Legal values | Comment | +|----------------------------------|-----------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| badAlarmInformationReferenceList | M | SET OF BadAlarmInfo | If allCleared is true, it contains no information.
If someCleared is true, then it contains identifications of AlarmInformation that are not present in AlarmList or that are present in AlarmList but remain unchanged, in contrast to manager's request. | +| status | M | StatusType | If allCleared is true, then status = OperationSucceeded.
If someCleared is true, then status = OperationPartiallyFailed.
If exception operationFailed is raised, then status = OperationFailed. | + +##### 7.3.4.2.4 Pre-condition + +atLeastOneValidId. + +| Assertion name | Properties | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| atLeastOneValidId | The input parameter alarmInformationReferenceList contains at least one identifier that identifies one AlarmInformation in AlarmList. | + +##### 7.3.4.2.5 Post-condition + +allCleared OR someCleared. + +| Assertion name | Properties | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allCleared | The AlarmInformation.perceivedSeverity of all instances identified by the input parameter alarmInformationReferenceList are set to 'cleared'. The AlarmInformation.clearUserId and AlarmInformation.clearSystemId of all instances identified are set with values carried by input parameters clearUserId and clearSystemId respectively. | +| someCleared | It has the same properties as allCleared except that it is applicable to one or more but not all instances identified by the input parameter alarmInformationReferenceList. | + +##### 7.3.4.2.6 Exceptions + +| Name | Properties | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: The pre-condition is false or the post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +### 7.3.5 Interface AlarmIRPAlarmListOperations (M) + +| Operation name | Qualifier | Requirement IDs | +|----------------|-----------|-----------------| +| getAlarmList | M | REQ-FM-FUN-05 | + +#### 7.3.5.1 getAlarmList (M) + +##### 7.3.5.1.1 Definition + +The Manager invokes this operation in order to request the Agent to provide either the complete list of AlarmInformation instances in the AlarmList, including the IOC instances associated with the AlarmInformation instances (full alarm alignment), or only a part of this list (partial alarm alignment). + +The parameters baseObjectClass and baseObjectInstance are used to identify the part of the alarm list to be returned. If they are absent, then the complete alarm list shall be provided (full alarm alignment). If they identify a certain MO, then only the AlarmInformation instances (and associated IOC instances) related to this MO and its subordinate MOs shall be provided (partial alarm alignment). If a baseObjectClass is specified but no baseObjectInstance, alarm information related to all MOs of the specified object type will be retrieved. + +##### 7.3.5.1.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmStateFilter | O | AlarmStateFilterType ::=
ENUMERATED {
all_Alarms,
all_Active_Alarms,
all_Active_And_Acknowledged_Alarms,
all_Active_And_Unacknowledged_Alarms,
all_Cleared_And_Unacknowledged_Alarms,
all_Unacknowledged
} | It carries a constraint. The Agent shall apply it on AlarmInformation instances in AlarmList when constructing its output parameter AlarmInformationList. | + +| Name | Qualifier | Information type/Legal values | Comment | +|--------------------|--------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| baseObjectClass | O,
(see Note 1) | String | If this parameter is absent, then all AlarmInformation instances in the AlarmList shall be returned.
If the parameter carries the object class of a certain MO, then all AlarmInformation instances (and associated IOC instances) of the MO identified by the parameter baseObjectInstance and its subordinate MOs shall be returned.
The AlarmInformation instances not related to the subject MO and its subordinate MOs shall not be returned (see Note 2). | +| baseObjectInstance | O,
(see Note 1) | Name | If the objectClass parameter is absent, then this parameter shall be absent.
If the baseObjectClass parameter carries the object class of a certain MO, then this parameter shall carry the DN of the related MO instance.
The AlarmList has to be returned only for alarms concerning that MO and its subordinate MOs. | +| filter | O | String | It carries a filter constraint. The agent shall apply it on AlarmInformation instances in AlarmList when constructing its output parameter AlarmInformationList. | + +NOTE 1 – If the notification AlarmListRebuiltNotification supports indicating that only a part of the alarm list has been rebuilt then the operation getAlarmList shall support partial alarm alignment. + +NOTE 2 – The legal values of the parameters baseObjectClass and baseObjectInstance are restricted to those carried by the parameters baseObjectClass and baseObjectInstance in the recent alarmListRebuiltNotification notifications. The timeline for "recent" is vendor-specific. + +##### 7.3.5.1.3 Output parameters + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|-----------------------|-----------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmInformation List | M | SET OF AlarmIdType | It carries the requested AlarmInformation instances including the associated IOC instances in AlarmList.
Case when synchronous mode of operation is used:
a) The agent shall apply the constraints expressed in alarmStateFilter and filter to AlarmInformation instances when constructing this output parameter. | + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|--------|-----------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | |

Case when asynchronous mode of operation is used (i.e., this output parameter is conveyed via notifications):

a) If the filter parameter is present, the agent shall apply the constraint when constructing this output parameter. Furthermore, if the alarmStateFilter constraint is present, the agent shall apply that constraint as well. The filter constraint, if any, that is currently active in the notification channel is not used for the construction of this output parameter.

b) If the filter parameter is absent, the agent shall apply the filter constraint currently active in the notification channel when constructing this output parameter. If the alarmAckState constraint is present, the agent shall apply that constraint as well.

| +| status | M | StatusType |

If allAlarmInformationReturned is true, status = OperationSucceeded.

If operation_failed is true, status = OperationFailed.

| + +##### 7.3.5.1.4 Pre-condition + +baseObjectExists. + +| Assertion name | Definition | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| baseObjectExists |

If the parameters baseObjectClass and baseObjectInstance are provided, the object identified by them has to exist.

If they are not provided, this pre-condition is not applicable.

| + +##### 7.3.5.1.5 Post-condition + +allAlarmInformationReturned. + +| Assertion name | Definition | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allAlarmInformationReturned |

All AlarmInformation that satisfy the constraints expressed in input parameters filter and alarmAckState and are present in the AlarmList at the moment of this operation invocation are returned. All AlarmInformation in AlarmList remains unchanged as the result of this operation.

| + +##### 7.3.5.1.6 Exceptions + +| Assertion name | Definition | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed |

Condition: At least one input parameter is invalid or the pre-condition is false or the post-condition is not true.

Returned Information: The output parameter status.

Exit state: Entry state.

| + +### 7.3.6 Interface AlarmIRPASAPOperations (O) + +| Notification name | Qualifier | Requirement IDs | +|-------------------|-----------|-----------------| +| createASAP | O | REQ-FM-FUN-06 | +| deleteASAP | O | REQ-FM-FUN-08 | +| modifyASAP | O | REQ-FM-FUN-07 | +| assignASAP | O | REQ-FM-FUN-09 | +| unassignASAP | O | REQ-FM-FUN-10 | +| queryASAP | O | REQ-FM-FUN-11 | + +#### 7.3.6.1 createASAP (O) + +##### 7.3.6.1.1 Definition + +Manager invokes this operation to create an ASAP. + +##### 7.3.6.1.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|--------------|-----------|-------------------------------|---------| +| aSAPInfoList | M | ASAPInfoListType | | + +##### 7.3.6.1.3 Output parameters + +| Name | Qualifier | Matching information/Information type/Legal values | Comment | +|--------|-----------|----------------------------------------------------|------------------------------------------------------| +| aSAPId | M | INTEGER | This parameter specifies the identifier of the ASAP. | +| status | M | StatusType | | + +##### 7.3.6.1.4 Pre-condition + +None. + +##### 7.3.6.1.5 Post-condition + +aSAPCreated. + +| Assertion name | Definition | +|----------------|----------------------------------------------------------------------| +| aSAPCreated | An ASAP is successfully created based on the specified aSAPInfoList. | + +##### 7.3.6.1.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.6.2 deleteASAP (O) + +##### 7.3.6.2.1 Definition + +Manager invokes this operation to delete an ASAP. + +##### 7.3.6.2.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|--------|-----------|-------------------------------|------------------------------------------------------| +| aSAPId | M | INTEGER | This parameter specifies the identifier of the ASAP. | + +##### 7.3.6.2.3 Output parameters + +| Name | Qualifier | Matching information/Information type/Legal values | Comment | +|--------|-----------|----------------------------------------------------|---------| +| status | M | StatusType | | + +##### 7.3.6.2.4 Pre-condition + +aSAPExists. + +| Assertion name | Definition | +|----------------|----------------------------------------------------| +| aSAPExists | The ASAP specified by the aSAPId parameter exists. | + +##### 7.3.6.2.5 Post-condition + +aSAPDeleted. + +| Assertion name | Definition | +|----------------|---------------------------------------------| +| aSAPDeleted | The specified ASAP is successfully deleted. | + +##### 7.3.6.2.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.6.3 modifyASAP (O) + +##### 7.3.6.3.1 Definition + +Manager invokes this operation to change the table entries of the alarm severity assignment of an ASAP. + +##### 7.3.6.3.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|--------------|-----------|-------------------------------|-----------------------------------------------------------------------------------| +| aSAPId | M | INTEGER | This parameter specifies the identifier of the ASAP. | +| aSAPInfoList | M | ASAPInfoListType | The new list of the problems and their corresponding severity are to be modified. | + +##### 7.3.6.3.3 Output parameters + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|--------|-----------|--------------------------------------------------------|---------| +| status | M | StatusType | | + +##### 7.3.6.3.4 Pre-condition + +aSAPExists. + +| Assertion name | Definition | +|----------------|----------------------------------------------------| +| aSAPExists | The ASAP specified by the aSAPId parameter exists. | + +##### 7.3.6.3.5 Post-condition + +aSAPModified. + +| Assertion name | Definition | +|----------------|----------------------------------------------| +| aSAPModified | The specified ASAP is successfully modified. | + +##### 7.3.6.3.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.6.4 assignASAP (O) + +##### 7.3.6.4.1 Definition + +Manager invokes this operation to set or change the association between an ASAP instance and one or more specified monitored entities. + +##### 7.3.6.4.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|---------------------|-----------|-------------------------------|------------------------------------------------------| +| aSAPId | M | INTEGER | This parameter specifies the identifier of the ASAP. | +| monitoredEntityList | M | SET OF Name | One or more specified monitored entities' Id. | + +##### 7.3.6.4.3 Output parameters + +| Name | Qualifier | Matching information/
Information type/Legal values | Comment | +|--------|-----------|--------------------------------------------------------|---------| +| status | M | StatusType | | + +##### 7.3.6.4.4 Pre-condition + +aSAPExists AND monitoredEntityExist. + +| Assertion name | Definition | +|----------------------|---------------------------------------------------------------------------| +| aSAPExists | The ASAP specified by the aSAPId parameter exists. | +| monitoredEntityExist | The MonitoredEntity specified by the monitoredEntityList parameter exist. | + +##### 7.3.6.4.5 Post-condition + +aSAPAssigned. + +| Assertion name | Definition | +|----------------|------------------------------------------------------------------------------| +| aSAPAssigned | The specified ASAP is successfully assigned to specified monitored entities. | + +##### 7.3.6.4.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.6.5 unassignASAP (O) + +##### 7.3.6.5.1 Definition + +Manager invokes this operation to remove the association between an ASAP and some of its associated monitored entity(s). + +##### 7.3.6.5.2 Input parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|---------------------|-----------|-------------------------------|------------------------------------------------------| +| aSAPId | M | INTEGER | This parameter specifies the identifier of the ASAP. | +| monitoredEntityList | M | SET OF Name | One or more specified monitored entities' Id. | + +##### 7.3.6.5.3 Output parameters + +| Name | Qualifier | Matching information/Information type/Legal values | Comment | +|--------|-----------|----------------------------------------------------|---------| +| status | M | StatusType | | + +##### 7.3.6.5.4 Pre-condition + +aSAPExists AND associationExist. + +| Assertion name | Definition | +|------------------|----------------------------------------------------------------------------------------------------------------------| +| aSAPExists | The ASAP specified by the aSAPId parameter exists. | +| associationExist | The association between the specified ASAP and MonitoredEntity specified by the monitoredEntityList parameter exist. | + +##### 7.3.6.5.5 Post-condition + +aSAPUnassigned. + +| Assertion name | Definition | +|----------------|---------------------------------------------------------------------------------------| +| aSAPUnassigned | The relationship between specified ASAP and monitored entity is successfully removed. | + +##### 7.3.6.5.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.6.6 queryASAP (O) + +##### 7.3.6.6.1 Definition + +Manager invokes this operation to query the information of an ASAP. + +##### 7.3.6.6.2 Input Parameters + +| Name | Qualifier | Information type/Legal values | Comment | +|--------|-----------|-------------------------------|------------------------------------------------------| +| aSAPId | M | INTEGER | This parameter specifies the identifier of the ASAP. | + +##### 7.3.6.6.3 Output parameters + +| Name | Qualifier | Matching information/Information type/Legal values | Comment | +|---------------------|-----------|----------------------------------------------------|--------------------------------------------------------------------------------| +| aSAPInfoList | M | ASAPInfoListType | The relationship between severity level and problem defined by specified ASAP. | +| monitoredEntityList | M | SET OF Name | The monitored entities using specified ASAP. | +| status | M | StatusType | | + +##### 7.3.6.6.4 Pre-condition + +aSAPExists. + +| Assertion name | Definition | +|----------------|----------------------------------------------------| +| aSAPExists | The ASAP specified by the aSAPId parameter exists. | + +##### 7.3.6.6.5 Post-condition + +None. + +##### 7.3.6.6.6 Exceptions + +| Name | Definition | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| operation_failed | Condition: Pre-condition is false or post-condition is false.
Returned Information: The output parameter status.
Exit state: Entry state. | + +### 7.3.7 Interface AlarmIRPAlarmNotifications (M) + +| Notification name | Qualifier | Requirement IDs | +|--------------------------|-----------|------------------------------| +| newAlarmNotification | M | REQ-FM-FUN-01 | +| alarmClearedNotification | M | REQ-FM-FUN-03 | +| alarmChangeNotification | M | REQ-FM-FUN-13, REQ-FM-FUN-14 | + +This Recommendation does not specify how the agent can determine if the manager has received alarms correctly. + +This Recommendation does not specify methods for the manager and the agent to recover alarm loss. The only mechanism recommended to deal with alarm loss is the use of getAlarmList operation. This Recommendation does not specify conditions under which the manager should invoke this operation. + +#### 7.3.7.1 newAlarmNotification (M) + +##### 7.3.7.1.1 Definition + +A new AlarmInformation has been added in the AlarmList. The subscribed manager instances are notified of this fact if the added AlarmInformation satisfies the current filter constraint of their subscription. + +##### 7.3.7.1.2 Input parameters + +| Parameter name | Qualifier | Matching information/
Information type/Legal values | Comment | +|-------------------------|-----------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| probableCause | M | ProbableCauseType | | +| perceivedSeverity | M | PerceivedSeverityType | | +| eventType | M | EventType | | +| vendorSpecificAlarmType | O | String | | +| specificProblem | O | String | | +| correlatedNotifications | O | SET OF AttributeName | It contains references to AlarmInformation instances whose perceivedSeverity levels are Cleared. In this way, alarms may replace older alarms. | +| backedUpStatus | O | BOOLEAN | | +| backUpObject | O | String | It carries the DN of the backup object. | +| trendIndication | O | TrendIndicationType | | +| stateChangeDefinition | O | String | | + +| Parameter name | Qualifier | Matching information/
Information type/Legal values | Comment | +|-----------------------|--------------------|--------------------------------------------------------|---------| +| monitoredAttributes | O | SET OF AttributeName
AttributeName ::= String | | +| proposedRepairActions | O | SET OF AttributeName | | +| additionalText | O | String | | +| additionalInformation | O | String | | +| serviceUser | CO
(see Note 1) | String | | +| serviceProvider | CO
(see Note 1) | String | | +| securityAlarmDetector | CO
(see Note 1) | String | | +| alarmId | M | AlarmIdType | | + +NOTE 1 – These attributes must be supported if the agent emits `NewAlarmNotification` that carries security alarm information. + +NOTE 2 – All the common attributes defined in the Notification Header as described in clause 7.3.5 of [ITU-T M.3702] will also be included, when this notification is instantiated. The value of the `notificationType` is "newAlarmNotification". + +##### 7.3.7.1.3 Triggering event + +###### 7.3.7.1.3.1 From-state + +`noMatchedAlarm`. + +| Assertion name | Definition | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| noMatchedAlarm | AlarmList does not contain an AlarmInformation that has the following properties:
Its matching-criteria-attributes values are identical to that of the newly generated network alarm and it is involved in relation- AlarmObject-AlarmInformation with the same MonitoredEntity as the one identified by the newly generated network alarm. | + +###### 7.3.7.1.3.2 To-state + +`newAlarmInAlarmList`. + +| Assertion name | Definition | +|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| newAlarmInAlarmList | AlarmList contains an AlarmInformation holding information conveyed by the newly generated network alarm. This AlarmInformation is involved in relation- AlarmObject-AlarmInformation with the same MonitoredEntity as the one identified by the newly generated network alarm.
The following attributes of the AlarmInformation shall be populated with information in the newly generated alarm:
alarmId , notificationId , alarmRaisedTime , eventType , perceivedSeverity .
The following attributes of the same AlarmInformation shall be populated with information in the newly generated alarm if the information is present (in the newly generated alarm) and if the attribute is supported:
specificProblem , backedUpStatus , trendIndication , thresholdInfo , stateChangedDefinition , monitoredAttributes , proposedRepairActions , additionalText , additionalInformation . | + +#### 7.3.7.2 alarmClearedNotification (M) + +##### 7.3.7.2.1 Definition + +Agent notifies the subscribed Manager of alarm clearing if the subject AlarmInformation satisfies the optional filter constraint expressed in the subscribe operation. + +The notification shall contain all parameters that are filterable and are present in the original (related) NewAlarmNotification notification. + +##### 7.3.7.2.2 Input parameters + +| Parameter name | Qualifier | Matching information/
Information type/Legal values | Comment | +|-------------------------|-----------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| probableCause | M | ProbableCauseType | | +| perceivedSeverity | M | PerceivedSeverityType | Its value shall indicate Cleared. | +| eventType | M | EventType | | +| correlatedNotifications | O | SET OF AttributeName
AttributeName ::= String | It contains references to other AlarmInformation instances whose perceivedSeverity levels are Cleared as well. In this way, perceivedSeverity level of multiple AlarmInformation instances can be Cleared by one notification. | +| clearUserId | O | String | It is present if the AlarmInformation is cleared by the Manager using clearAlarms. | +| clearSystemId | O | String | It is present if clearUserId is present and if AlarmInformation.clearSystemId contains information. | +| alarmId | M | AlarmIdType | | + +NOTE – All the common attributes defined in the Notification Header as described in clause 7.3.5 of [ITU-T M.3702] will also be included, when this notification is instantiated. The value of the notificationType is "notifyClearedAlarm". + +##### 7.3.7.2.3 Triggering event + +###### 7.3.7.2.3.1 From-state + +alarmMatchedAndCleared OR clearedByManager. + +| Assertion name | Definition | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmMatchedAndCleared | The matching-criteria-attributes of the newly generated network alarm have values that are identical (matched) with the ones in one AlarmInformation in AlarmList and the perceivedSeverity of the matched AlarmInformation is not Cleared;
AND the perceivedSeverity of the newly generated network alarm is cleared. | +| clearedByManager | Reception of a valid clearAlarms operation that identifies the subject AlarmInformation instances. This triggering event shall occur regardless of the perceivedSeverity state of the identified AlarmInformation instances. | + +###### 7.3.7.2.3.2 To-state + +AlarmInformationCleared\_1 OR AlarmInformationCleared\_2. + +| Assertion name | Definition | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AlarmInformationCleared_1 | Case if From-state is alarmMatchedAndCleared:
The following attributes of the subject AlarmInformation are updated:
notificationId, perceivedSeverity (updated to Cleared),
alarmClearedTime. | +| AlarmInformationCleared_2 | Case if From-state is clearedByManager:
The following attributes of the subject AlarmInformation are updated:
notificationId, perceivedSeverity (updated to Cleared), alarmClearedTime,
alarmClearedUserId, alarmClearedSystemId. | + +#### 7.3.7.3 alarmChangeNotification (M) + +##### 7.3.7.3.1 Definition + +The subscribed Manager instances are notified regarding changes in AlarmInformation in AlarmList. This notification is only triggered by a change in perceivedSeverity attribute value (except to the value "Cleared"), in a change to any of the acknowledgement status ackState, or a change in the comment attribute. The AlarmInformation carried in the notification shall satisfy the current filter constraint of the subscription. + +The notification shall contain all parameters that are filterable and are present in the original (related) NewAlarmNotification notification. + +##### 7.3.7.3.2 Input parameters + +| Parameter name | Qualifier | Matching information/
Information type/Legal values | Comment | +|-------------------|-----------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| probableCause | M | ProbableCauseType | | +| perceivedSeverity | CO (see Note 1) | PerceivedSeverityType | | +| eventType | M | EventType | | +| alarmId | M | AlarmIdType | | +| ackState | CO (see Note 2) | AckStateType | | +| ackUserId | M | String | If this AlarmInformation has been acknowledged by a human operator, then this parameter contains the operator identifier. If it has been acknowledged by a System (EM or NM), then this parameter contains the identifier of the system. | +| ackSystemId | M | String | This parameter always contains the identifier of the system (EM or NM) where the acknowledgement request was originated. | + +| Parameter name | Qualifier | Matching information/
Information type/Legal values | Comment | +|----------------|-----------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| comments | O | SET OF AttributeName | The set of Comment instances involved in a relationship with this AlarmInformation.
Required if triggering event is alarmCommentChanged | + +NOTE 1 – Required if triggering event is alarmSeverityChanged. +NOTE 2 – Required if triggering event is alarmAckStateHasChanged. +NOTE 3 – All the common attributes defined in the Notification Header as described in clause 7.3.5 of [ITU-T M.3702] will also be included, when this notification is instantiated. The value of the notificationType is "notifyChangedAlarm". + +##### 7.3.7.3.3 Triggering event + +###### 7.3.7.3.3.1 From-state + +alarmMatched AND ((alarmNotCleared AND alarmSeverityChanged) OR alarmAckStateHasChanged OR alarmCommentChanged) . + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alarmMatched | The matching-criteria-attributes of the newly generated network alarm have values that are identical (matches) with the ones in one AlarmInformation in AlarmList. | +| alarmNotCleared | The perceivedSeverity of the newly generated network alarm is not Cleared. | +| alarmSeverityChanged | The perceivedSeverity of the newly generated network alarm and of the matched AlarmInformation are different. | +| alarmAckStateHasChanged | The AlarmInformation.ackState of the AlarmInformation identified by from-state assertion alarmInformationExists has been updated. Specifically, the following attributes of the subject AlarmInformation are updated.
notificationId, ackTime, ackUserId, ackState, ackSystemId. | +| alarmCommentChanged | One Comment has been created and it is involved in a relationship with the AlarmInformation identified by from-state assertion alarmInformationExists. The following attributes of the newly created Comment instance shall be populated:
commentTime, commentText, commentUserId and commentSystemId. | + +### 7.3.8 Interface AlarmIRPAlarmListNotifications (O) + +| Notification name | Qualifier | Requirement IDs | +|----------------------------------------|-----------|-----------------| +| alarmListRebuiltNotification | O | REQ-FM-FUN-17 | +| potentiallyFaultyAlarmListNotification | O | REQ-FM-FUN-17 | + +#### 7.3.8.1 alarmListRebuiltNotification (O) + +##### 7.3.8.1.1 Definition + +The Agent or its related AlarmIRP maintains an AlarmList. It can lose confidence in the integrity of its AlarmList. Under this condition, Agent or its related AlarmIRP or the related AlarmList shall invoke AlarmListRebuiltNotification notification after the AlarmList has been rebuilt. + +The Agent can also invoke AlarmListRebuiltNotification notification indicating that part of the AlarmList has been rebuilt. In this case, the notification carries the managed object (MO) instance + +indicating that the AlarmList only has been rebuilt for alarms concerning this MO and its subordinate MOs. Furthermore, this notification indicates that there is no rebuilding going on for superior MOs of this MO. + +##### 7.3.8.1.2 Input parameters + +| Parameter name | Qualifier | Matching information/
Information type/Legal values | Comment | +|--------------------------------|--------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reason | M | ENUMERATED {
agent-
NE_Communication_Error, ag
ent_Restarts, indeterminat
e} | It carries the reason why the agent has rebuilt the AlarmList. This may carry different reasons than that carried by the immediate previous notifyPotentialFaultyAlarmList. | +| alarmListAlignment Requirement | CO
(see Note 1) | ENUMERATED {
alignmentRequired,
alignmentNotRequired} | It carries an enumeration of "alignmentRequired" and "alignmentNotRequired".
The agent uses alignmentRequired to indicate that Agent current AL is not identical to the one that could have been built using a) Agent AL information at the time it emits the immediate previous notifyPotentialFaultyAlarmList() and b) the notifications (carrying alarm information) emitted after the previously identified notification and before the subject notification. Otherwise, the agent uses alignmentNotRequired. When this parameter is absent, it implies alignmentRequired. | + +NOTE 1 – If the agent supports notifyPotentialFaultyAlarmList() notification, it shall support this parameter. If the agent does not support notifyPotentialFaultyAlarmList() notification, it shall not support this parameter. + +NOTE 2 – All the common attributes defined in the notification header as described in clause 7.3.5 of [ITU-T M.3702] will also be included, when this notification is instantiated. The value of the notificationType is "notifyAlarmListRebuilt". + +##### 7.3.8.1.3 Triggering event + +###### 7.3.8.1.3.1 From-state + +alarmListRebuilt\_0 OR alarmListRebuilt\_1. + +| Assertion name | Definition | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------| +| alarmListRebuilt_0 | The agent has cold-started, initialized, re-initialized or rebooted and it has initiated the procedure to rebuild its AlarmList. | +| alarmListRebuilt_1 | The agent loses confidence in part or the whole of its AlarmList. The agent has initiated the procedure to repair its AlarmList. | + +###### 7.3.8.1.3.2 To-state + +alarmListRebuilt\_2. + +| Assertion name | Definition | +|--------------------|---------------------------------------------------| +| alarmListRebuilt_2 | The agent rebuilt the whole or part of AlarmList. | + +#### 7.3.8.2 potentiallyFaultyAlarmListNotification (O) + +##### 7.3.8.2.1 Definition + +The agent or its related AlarmIRP maintains an AlarmList. It can lose confidence in the integrity of its AlarmList. Under this condition, the agent or its related AlarmIRP or the related AlarmList shall invoke PotentiallyFaultyAlarmListNotification. They then can begin to rebuild the faulty AlarmList, if necessary. After the successful rebuilding or the discovery that rebuilt is not necessary, they shall invoke AlarmListRebuiltNotification notification. + +This notification can identify a set of AlarmInformation that is potentially faulty or unreliable. This identification is done in the following way. If the MOI of an AlarmInformation is the same or is a subordinate to the MOI carried in the notification, then the AlarmInformation may be faulty or unreliable. + +This notification can identify all the AlarmInformation instances of the AlarmList that are potentially faulty or unreliable. In this case, the notification shall carry a MOI identifying the agent. + +The manager's behaviour, on reception of this PotentiallyFaultyAlarmListNotification notification, is not specified. The manager's behaviour is considered not essential for the specification of the interface itself. However, the following are recommended actions the manager should take, in case it receives this notification: + +- 1) The manager should not perform any task requiring the integrity of the AlarmInformation identified as faulty or unreliable by the subject notification. +- 2) The manager should not invoke operations that require integrity of the AlarmList, such as getAlarmList and acknowledgeAlarms operations. + +##### 7.3.8.2.2 Input parameters + +| Parameter name | Qualifier | Matching information/Information type/Legal values | Comment | +|----------------|-----------|--------------------------------------------------------------------------|-------------------------------------------------------------------| +| reason | M | ENUMERATED {agent-NE_Communication_Error, agent_Restarts, indeterminate} | It carries the reason why the agent has to rebuild its AlarmList. | + +NOTE – All the common attributes defined in the notification header as described in clause 7.3.5 of [ITU-T M.3702] will also be included when this notification is instantiated. The value of the notificationType is "notifyPotentialFaultyAlarmList". + +##### 7.3.8.2.3 Triggering event + +###### 7.3.8.2.3.1 From-state + +faultyAlarmListDetected. + +| Assertion name | Definition | +|-------------------------|-----------------------------------------------------------------| +| faultyAlarmListDetected | The agent detects faults in part or the whole of its AlarmList. | + +###### 7.3.8.2.3.2 To-state + +`faultyAlarmList` + +| Assertion name | Definition | +|------------------------------|----------------------------------------------------| +| faultyAlarmList | The agent initiates the AlarmList rebuild process. | + +# Annex A + +## Event Types + +(This annex forms an integral part of this Recommendation) + +This annex lists and explains event types used by this Recommendation. + +Event type is defined in [ITU-T X.733]. Table A.1 lists some of the event types referred to in this Recommendation. + +Notification IRP: Information Service in [b-3GPP TS 32.302] defines a parameter called `notificationType` that shall be present in all notifications. This Recommendation defines a parameter called `alarmType` that shall be present in all notifications carrying alarm information. Examples of `notificationType` are "notification of new alarm", "notification of AlarmList rebuilt", "notification of alarm cleared", etc. Examples of `alarmType` are the event types defined in Table A.1. + +This Recommendation also defines an attribute of `AlarmInformation` called `eventType`. The mapping of this `eventType` (internal attribute and not visible to Manager) to `notificationType` or `alarmType` (both visible to Manager) is defined in the relevant clauses of this Recommendation. The choice of using "`eventType`" is to keep the list of attributes of `AlarmList` unchanged (compared to 3GPP's Release 99). One can replace this `eventType` with two attributes, called `notificationType` and `alarmType` so that mapping of these two attributes to the externally visible parameters of the same name will be straight-forward. + +It is noted that the `AlarmInformation.eventType` can capture more information than the ITU-T defined event types [ITU-T X.733]. One example is "notification of alarm list rebuilt". + +**Table A.1 – Event types** + +| Event types | Explanation | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Communications | An alarm of this type is associated with the procedure and/or process required conveying information from one point to another ([ITU-T X.733]). | +| Processing error | An alarm of this type is associated with a software or processing fault ([ITU-T X.733]). | +| Environmental | An alarm of this type is associated with a condition related to an enclosure in which the equipment resides ([ITU-T X.733]). | +| Quality of service | An alarm of this type is associated with degradation in the quality of a service ([ITU-T X.733]). | +| Equipment | An alarm of this type is associated with an equipment fault ([ITU-T X.733]). | +| Integrity violation | An indication that information may have been illegally modified, inserted or deleted. | +| Operational violation | An indication that the provision of the requested service was not possible due to the unavailability, malfunction or incorrect invocation of the service. | +| Physical violation | An indication that a physical resource has been violated in a way that suggests a security attack. | +| Security service or mechanism violation | An indication that a security attack has been detected by a security service or mechanism. | +| Time domain violation | An indication that an event has occurred at an unexpected or prohibited time. | +| Unknown | Event type that cannot be supported by the above definitions. | + +# Annex B + +## Probable Causes + +(This annex forms an integral part of this Recommendation) + +This annex lists probable causes and their corresponding event types. + +Sources of these probable causes are [ITU-T M.3100], [ITU-T X.721], [ITU-T X.733] and [ITU-T X.736]. In addition, probable causes for 2G and 3G wireless systems are listed. + +**Table B.1 – [ITU-T M.3100] probable causes** + +| ITU-T M.3100 probable cause | Event type | +|------------------------------------|-------------------| +| Indeterminate | Unknown | +| Alarm indication signal (AIS) | Communications | +| Broadcast channel failure | Communications | +| Call setup failure | Communications | +| Communications receive failure | Communications | +| Communications transmit failure | Communications | +| Connection establishment error | Communications | +| Degraded signal | Communications | +| Demodulation failure | Communications | +| Far end receiver failure (FERF) | Communications | +| Framing error | Communications | +| Invalid message received | Communications | +| Local node transmission error | Communications | +| Loss of frame (LOF) | Communications | +| Loss of pointer (LOP) | Communications | +| Loss of signal (LOS) | Communications | +| Modulation failure | Communications | +| Payload type mismatch | Communications | +| Transmission error | Communications | +| Remote alarm interface | Communications | +| Remote node transmission error | Communications | +| Routing failure | Communications | +| Excessive bit error rate (EBER) | Communications | +| Path trace mismatch | Communications | +| Unavailable | Communications | +| Signal label mismatch | Communications | +| Loss of multi frame | Communications | +| Antenna failure | Equipment | +| Back plane failure | Equipment | +| Battery charging failure | Equipment | + +**Table B.1 – [ITU-T M.3100] probable causes** + +| ITU-T M.3100 probable cause | Event type | +|------------------------------------|-------------------| +| Data set problem | Equipment | +| Disk failure | Equipment | +| Equipment identifier duplication | Equipment | +| External if device problem | Equipment | +| Frequency hopping failure | Equipment | +| IO device error | Equipment | +| Line card problem | Equipment | +| Loss of redundancy | Equipment | +| Loss of synchronization | Equipment | +| Multiplexer problem | Equipment | +| NE identifier duplication | Equipment | +| Power problem | Equipment | +| Power supply failure | Equipment | +| Processor problem | Equipment | +| Protection path failure | Equipment | +| Protecting resource failure | Equipment | +| Protection mechanism failure | Equipment | +| Real time clock failure | Equipment | +| Receiver failure | Equipment | +| Replaceable unit missing | Equipment | +| Replaceable unit type mismatch | Equipment | +| Signal quality evaluation failure | Equipment | +| Synchronization source mismatch | Equipment | +| Terminal problem | Equipment | +| Timing problem | Equipment | +| Transceiver failure | Equipment | +| Transmitter failure | Equipment | +| Trunk card problem | Equipment | +| Replaceable unit problem | Equipment | +| Air compressor failure | Environmental | +| Air conditioning failure | Environmental | +| Air dryer failure | Environmental | +| Battery discharging | Environmental | +| Battery failure | Environmental | +| Commercial power failure | Environmental | +| Cooling fan failure | Environmental | +| Cooling system failure | Environmental | +| Engine failure | Environmental | +| Fire detector failure | Environmental | + +**Table B.1 – [ITU-T M.3100] probable causes** + +| ITU-T M.3100 probable cause | Event type | +|--------------------------------------|-------------------| +| Fuse failure | Environmental | +| Generator failure | Environmental | +| Low battery threshold | Environmental | +| Pump failure | Environmental | +| Rectifier failure | Environmental | +| Rectifier high voltage | Environmental | +| Rectifier low F voltage | Environmental | +| Ventilation system failure | Environmental | +| Enclosure door open | Environmental | +| Explosive gas | Environmental | +| External equipment failure | Environmental | +| External point failure | Environmental | +| Fire | Environmental | +| Flood | Environmental | +| High humidity | Environmental | +| High temperature | Environmental | +| High wind | Environmental | +| Ice build up | Environmental | +| Intrusion detection | Environmental | +| Low fuel | Environmental | +| Low humidity | Environmental | +| Low cable pressure | Environmental | +| Low temperature | Environmental | +| Low water | Environmental | +| Smoke | Environmental | +| Toxic gas | Environmental | +| Application subsystem failure | Processing error | +| Configuration or customisation error | Processing error | +| Database inconsistency | Processing error | +| File error | Processing error | +| Storage capacity problem | Processing error | +| Memory mismatch | Processing error | +| Corrupt data | Processing error | +| Loss of real time | Processing error | +| Out of CPU cycles | Processing error | +| Out of memory | Processing error | +| Reinitialized | Processing error | +| Software environment problem | Processing error | +| Software error | Processing error | + +**Table B.1 – [ITU-T M.3100] probable causes** + +| ITU-T M.3100 probable cause | Event type | +|------------------------------------|--------------------| +| Software download failure | Processing error | +| Timeout expired | Processing error | +| Underlying resources unavailable | Processing error | +| Version mismatch | Processing error | +| Bandwidth reduced | Quality of service | +| Congestion | Quality of service | +| Excessive error rate | Quality of service | +| Excessive response time | Quality of service | +| Excessive retransmission rate | Quality of service | +| Reduced logging capability | Quality of service | +| System resources overload | Quality of service | + +**Table B.2 – [ITU-T X.721], [ITU-T X.733] and [ITU-T X.736] probable causes** + +| ITU-T X.721/ITU-T X.733/ITU-T X.736 probable cause | Event type | +|-----------------------------------------------------------|-----------------------------------------| +| Adapter error | Equipment | +| Application subsystem failure | Processing error | +| Authentication failure | Security service or mechanism violation | +| Bandwidth reduction | Quality of service | +| Breach of confidentiality | Security service or mechanism violation | +| Cable tamper | Physical violation | +| Call establishment error | Communications | +| Communication protocol error | Communications | +| Communication subsystem failure | Communications | +| Configuration or customizing error | Processing error | +| Congestion | Quality of service | +| Corrupt data | Processing error | +| CPU cycles limit exceeded | Processing error | +| Data set or modem error | Equipment | +| Degraded signal | Communications | +| Delayed information | Time domain violation | +| Denial of service | Operational violation | +| DTE-DCE interface error | Communications | +| Duplicate information | Integrity violation | +| Enclosure door open | Environmental | +| Equipment malfunction | Equipment | +| Excessive vibration | Environmental | +| File error | Processing error | + +**Table B.2 – [ITU-T X.721], [ITU-T X.733] and [ITU-T X.736] probable causes** + +| ITU-T X.721/ITU-T X.733/ITU-T X.736 probable cause | Event type | +|-----------------------------------------------------------|-----------------------------------------| +| Fire detected | Environmental | +| Flood detected | Environmental | +| Framing error | Communications | +| Heating or ventilation or cooling system problem | Environmental | +| Humidity unacceptable | Environmental | +| Information missing | Integrity violation | +| Information modification detected | Integrity violation | +| Information out of sequence | Integrity violation | +| Input/output device error | Equipment | +| Input device error | Equipment | +| Intrusion detection | Physical violation | +| Key expired | Time domain violation | +| LAN error | Communications | +| Leak detection | Environmental | +| Local node transmission error | Communications | +| Loss of frame | Communications | +| Loss of signal | Communications | +| Material supply exhausted | Environmental | +| Multiplexer problem | Equipment | +| Non-repudiation failure | Security service or mechanism violation | +| Out of hours activity | Time domain violation | +| Out of memory | Processing error | +| Out of service | Operational violation | +| Output device error | Equipment | +| Performance degraded | Quality of service | +| Power problem | Equipment | +| Pressure unacceptable | Environmental | +| Procedural error | Operational violation | +| Processor problem | Equipment | +| Pump failure | Environmental | +| Queue size exceeded | Quality of service | +| Receive failure | Equipment | +| Receiver failure | Equipment | +| Remote node transmission error | Communications | +| Resource at or nearing capacity | Quality of service | +| Response time excessive | Quality of service | +| Re-transmission rate excessive | Quality of service | +| Software error | Processing error | +| Software program abnormally terminated | Processing error | + +**Table B.2 – [ITU-T X.721], [ITU-T X.733] and [ITU-T X.736] probable causes** + +| ITU-T X.721/ITU-T X.733/ITU-T X.736 probable cause | Event type | +|-----------------------------------------------------------|-----------------------------------------| +| Software program error | Processing error | +| Storage capacity problem | Processing error | +| Temperature unacceptable | Environmental | +| Threshold crossed | Quality of service | +| Timing problem | Equipment | +| Toxic leak detected | Environmental | +| Transmit failure | Equipment | +| Transmitter failure | Equipment | +| Unauthorized access attempt | Security service or mechanism violation | +| Underlying resource unavailable | Processing error | +| Unexpected information | Integrity violation | +| Unspecified reason | Operational violation | +| Unspecified reason | Physical violation | +| Unspecified reason | Security service or mechanism violation | +| Version mismatch | Processing error | + +Table B.3 identifies probable causes that are defined by more than one standard. This is for information only. + +**Table B.3 – Duplicated probable causes** + +| Duplicated probable cause | 2G and 3G | ITU-T X.721
ITU-T X.733
| ITU-T X.736 | ITU-T M.3100 | Event type | +|----------------------------------------------------------------------------------------------|------------------|------------------------------------|--------------------|---------------------|-------------------| +| Broadcast channel failure | X | | | X | Communications | +| Call establishment failure
(ITU-T X.721/ITU-T X.733)
call setup failure (ITU-T M.3100) | | X | | X | Communications | +| Connection establishment error | X | | | X | Communications | +| Degraded signal | | X | | X | Communications | +| Framing error | | X | | X | Communications | +| Invalid message received | X | | | X | Communications | +| Local node transmission error | | X | | X | Communications | +| Loss of frame | | X | | X | Communications | +| Loss of signal | | X | | X | Communications | +| Remote node transmission error | | X | | X | Communications | +| Routing failure | X | | | X | Communications | +| Antenna failure (ITU-T M.3100)
Antenna problem (2G and 3G) | X | | | X | Equipment | + +**Table B.3 – Duplicated probable causes** + +| Duplicated probable cause | 2G and 3G | ITU-T X.721
ITU-T X.733
| ITU-T X.736 | ITU-T M.3100 | Event type | +|-------------------------------------------------------------------------------------------------|------------------|------------------------------------|--------------------|---------------------|-------------------| +| Battery charging failure (ITU-T M.3100)
Battery charging fault (2G and 3G) | X | | | X | Equipment | +| Disk failure (ITU-T M.3100)
Disk problem (2G and 3G) | X | | | X | Equipment | +| Equipment failure (2G and 3G)
equipment malfunction (ITU-T X.721/ITU-T X.733) | X | X | | | Equipment | +| Frequency hopping failure | X | | | X | Equipment | +| IO device error (ITU-T M.3100)
Input/output device error (ITU-T X.721/ITU-T X.733) | | X | | X | Equipment | +| Loss of redundancy (ITU-T M.3100)
Lost redundancy (2G and 3G) | X | | | X | Equipment | +| Loss of synchronization | X | | | X | Equipment | +| Multiplexer problem | | X | | X | Equipment | +| Power problem | | X | | X | Equipment | +| Power supply failure | X | | | X | Equipment | +| Processor problem | | X | | X | Equipment | +| Receiver failure | X | X | | X | Equipment | +| Signal quality evaluation failure (ITU-T M.3100)
Signal quality evaluation fault (2G and 3G) | X | | | X | Equipment | +| Timing problem | | X | | X | Equipment | +| Transceiver failure (ITU-T M.3100)
Transceiver problem (2G and 3G) | X | | | X | Equipment | +| Transmitter failure | X | X | | X | Equipment | +| Cooling system failure | X | | | X | Environmental | +| External equipment failure | X | | | X | Environmental | +| Enclosure door open | | X | | X | Environmental | +| Fan failure (2G and 3G)
cooling fan failure (ITU-T M.3100) | X | | | X | Environmental | +| Fire detected (ITU-T X.721/ITU-T X.733)
fire (ITU-T M.3100) | | X | | X | Environmental | + +**Table B.3 – Duplicated probable causes** + +| Duplicated probable cause | 2G and 3G | ITU-T X.721
ITU-T X.733
| ITU-T X.736 | ITU-T M.3100 | Event type | +|-------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------|--------------------|---------------------|----------------------------------------------------------------------------------------| +| Flood detected
(ITU-T X.721/ITU-T X.733)
flood (ITU-T M.3100) | | X | | X | Environmental | +| High humidity | X | | | X | Environmental | +| High temperature | X | | | X | Environmental | +| Intrusion detected (2G and 3G)
intrusion detection
(ITU-T X.736/ITU-T M.3100) | X | | X | X | Environmental
(2G and 3G);
Physical violation
(ITU-T X.736/
ITU-T M.3100) | +| Low humidity | X | | | X | Environmental | +| Low temperature | X | | | X | Environmental | +| Pump failure | | X | | X | Environmental | +| Smoke detected (2G and 3G)
smoke (ITU-T M.3100) | X | | | X | Environmental | +| Application subsystem failure | | X | | X | Processing error | +| Bandwidth reduced
Bandwidth reduction
(ITU-T X.721/ITU-T X.733) | | X | | X | Quality of service | +| Configuration or customization
error (ITU-T M.3100)
Configuration or customizing
error (ITU-T X.721/
ITU-T X.733) | | X | | X | Processing error | +| Database inconsistency | X | | | X | Processing error | +| File error | | X | | X | Processing error | +| Storage capacity problem | | X | | X | Processing error | +| Excessive bit error rate
(ITU-T M.3100)
Excessive error rate (2G and 3G)
Excessive error rate | X | | | X | Communications
(ITU-T M.3100)
Quality of service
(GSM 12.11/
ITU-T M.3100) | +| Corrupt data | | X | | X | Processing error | +| Out of memory | | X | | X | Processing error | +| Software error | | X | | X | Processing error | +| Timeout expired | X | | | X | Processing error | +| Underlying resource unavailable
(ITU-T M.3100)
Underlying resource unavailable
(ITU-T X.721/ITU-T X.733) | | X | | X | Processing error | +| Version mismatch | | X | | X | Processing error | + +**Table B.3 – Duplicated probable causes** + +| Duplicated probable cause | 2G and 3G | ITU-T X.721
ITU-T X.733
| ITU-T X.736 | ITU-T M.3100 | Event type | +|----------------------------------------------------------------------------------------------------------|------------------|------------------------------------|--------------------|---------------------|--------------------| +| Congestion | | X | | X | Quality of service | +| Reduced logging capability | X | | | X | Quality of service | +| System resources overload | X | | | X | Quality of service | +| Excessive response time (ITU-T M.3100)
Response time excessive (ITU-T X.721/ITU-T X.733) | | X | | X | Quality of service | +| Excessive retransmission rate (ITU-T M.3100)
Re-transmission rate excessive (ITU-T X.721/ITU-T X.733) | | X | | X | Quality of service | + +# Appendix I + +## Examples of using notifyChangedAlarm + +(This appendix does not form an integral part of this Recommendation) + +This appendix describes a number of valid and invalid interactions governing the case when the agent reports a specific fault of a particular network resource whose alarm severity level changes from, e.g., "Critical" to "Minor" and then to "Cleared". + +In the following examples: + +- ni is notificationId, +- moc is managedObjectClass, +- moi is managedObjectInstance, +- et is eventType, +- pc is probableCause, +- sp is specificProblem, +- ps is perceivedSeverity and +- ai is alarmId. + +Example 1: Valid sequence 1 to support the hypothetical case: + +- (1) NotifyNewAlarm +(ni=1, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Critical) +- (2) NotifyChangedAlarm +(ni=2, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Minor) +- (3) NotifyClearedAlarm +(ni=3, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Cleared) + +Example 2: Valid sequence 2 to support the hypothetical case (assuming that the alarm with "ai=X" is acknowledged after either (1) or (2), but before (3)): + +- (1) NotifyNewAlarm +(ni=1, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Critical) + +NotifyClearedAlarm +(ni=2, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Cleared) + +- (2) NotifyNewAlarm +(ni=3, ai=Y, moc=A, moi=B, et=C, pc=D, sp=E, ps=Minor) + +NotifyClearedAlarm +(ni=4, ai=Y, moc=A, moi=B, et=C, pc=D, sp=E, ps=Cleared) + +Example 3: Invalid sequence 1 to support the hypothetical case: + +- (1) NotifyNewAlarm +(ni=1, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Critical) +- (2) NotifyChangedAlarm +(ni=2, ai=Y, moc=A, moi=B, et=C, pc=D, sp=E, ps=Minor) +- (3) NotifyClearedAlarm +(ni=3, ai=Y, moc=A, moi=B, et=C, pc=D, sp=E, ps=Cleared) + +Interaction (2) is illegal since it uses a different ai for the same alarm. It should use ai=X as in interaction (1). + +Example 4: Invalid sequence 2 to support the hypothetical case: + +``` +(1) NotifyNewAlarm + (ni=1, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Critical) + +(2) NotifyNewAlarm + (ni=2, ai=X, moc=A, moi=B, et=C, pc=D, sp=E, ps=Minor) +``` + +Interaction (2) is illegal since it invokes `notifyNewAlarm` using same `ai` value. It should use `notifyChangedAlarm` with the same `ai` value. + +# Appendix II + +## Background information about fault management + +(This appendix does not form an integral part of this Recommendation) + +This appendix contains some background information about fault detection, alarm acknowledgement, alarm clearance and fault recovery. This information is out of the scope of the interface between agent and manager, but useful for understanding the background of fault management. + +## II.1 Fault detection + +When a fault occurs within a network, the affected network entities shall be able to detect them immediately and generate an alarm. 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, see [b-ITU-T M.3704]. The fault detection mechanism as defined above shall cover both active and standby components of the network entities. + +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 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 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. + +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 this Recommendation 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. When an ADAC fault is detected, the appropriate alarm shall be generated by the faulty network entities. + +For some faults, no clearing condition exists. For the purpose of this Recommendation, 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. When an ADMC fault is detected, the appropriate alarm shall be generated by the faulty network entities. + +For faults which do not result in standing conditions 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. Such faults also shall be generated by the faulty network entities. + +A fault condition is uniquely identified by the combination of the managed object instance experiencing the fault and either the structured probable cause or the probable cause and the specific problem. + +An alarm is uniquely identified by the unique fault condition parameters and the time of fault detection. + +When an alarm is generated a corresponding active alarm is added to the active alarm list by the agent. The agent shall be able to provide such a list of active alarms to the manager when requested. + +## **II.2 Alarm acknowledgement** + +The acknowledgement of an alarm is a maintenance function that aids the operator 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: + +- all involved OSs have the same information about the alarms to be managed (including the current responsibility for alarm handling); +- all involved OSs have the capability to send and to receive acknowledgement messages associated to previous alarm reports. + +## **II.3 Clearing of alarms** + +The alarms originated in consequence of faults need to be cleared. To clear an alarm it is generally necessary to repair the corresponding fault. The procedures to repair faults are implementation dependent and are therefore out of the scope of this Recommendation, 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 agent behaves as for the ADAC faults repaired by the operator. + +In principle, the agent 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 agent 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 agent shall clear the fault(s). Consequently, the agent 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 agent should reissue those alarms (as new alarms) in case the fault situation still persists. +- The agent 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 agent shall clear the fault(s). Consequently, the agent shall clear all related alarms. +- The agent 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 agent to clear a threshold crossed alarm are implementation specific and depend on the definition of the threshold measurement, see also clause II.1. +- By definition, ADMC faults/alarms cannot be cleared by the agent autonomously. Therefore, system operator functions shall be available to request the clearing of ADMC alarms/faults in the agent. Once an ADMC alarm/fault has been cleared, the agent shall clear the associated ADAC fault/alarm. + +Details of these mechanisms are system/implementation specific. + +## II.4 Fault recovery + +After a fault has been detected and the replaceable faulty units/components have been identified, some management functions are necessary in order to perform system recovery and/or restoration, either automatically by the agent, or manually by the operator. + +The fault recovery functions are used in various phases of fault management (FM): + +- 1) Once a fault has been detected, the NE may 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 may 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. Data and configuration errors are treated similarly to software errors. + +If the faulty resource has no redundancy, the recovery actions should 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) Generate and forward appropriate notifications to inform the OS about all the changes performed. + +If the faulty resource has redundancy, the NE should perform actions a) and c) 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, etc.), and for each one, there is a specific sequence of actions to be performed in case of failure. This Recommendation 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 should start immediately upon detection of the failure. Before or during the changeover, a temporary and limited loss of service shall be acceptable. In the case of a management-initiated recovery 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 this Recommendation. + +# Bibliography + +- [b-ITU-T M.3704] Recommendation ITU-T M.3704 (2010), *Common management service – Performance management – Protocol neutral requirements and analysis.* +- [b-3GPP TS 32.101] 3GPP TS 32.101 V9.1.0 (2010), *Telecommunication management; Principles and high level requirements.* +- [b-3GPP TS 32.102] 3GPP TS 32.102 V9.0.0 (2009), *Telecommunication management; Architecture.* +- [b-3GPP TS 32.111-1] 3GPP TS 32.111-1 V9.0.0 (2009), *Telecommunication management; Fault Management; Part 1: 3G fault management requirements.* +- [b-3GPP TS 32.111-2] 3GPP TS 32.111-2 V9.1.0 (2010), *Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP); Information Service (IS).* +- [b-3GPP TS 32.150] 3GPP TS 32.150 V9.1.0 (2010), *Telecommunication management; Integration Reference Point (IRP) Concept and definitions.* +- [b-3GPP TS 32.302] 3GPP TS 32.302 V9.0.0 (2009), *Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS).* +- [b-3GPP TS 32.312] 3GPP TS 32.312 V9.0.0 (2009), *Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS).* +- [b-3GPP TS 32.401] 3GPP TS 32.401 V9.0.0 (2009), *Telecommunication management; Performance Management (PM); Concept and requirements.* +- [b-3GPP TS 32.622] 3GPP TS 32.622 V9.1.0 (2010), *Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM).* + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..092dfe4d51316e1a641522a8947821793cfbce8d --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed98c48ee46d8de8ddf3cf854e470700c2966c2e0c4316de6617bf2242c3151a +size 70523 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13b1ceb4c00e4189745e84aebcd04e6918634888 --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daff64831b8d2a555161dfee8b9c0d8a8f8cdfd4dd643a479b5080b5fdcccb0d +size 98136 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d55246ba068c0fef8b7a09f9c2e0278ff0d8b4ee --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25eff1649f88299b9f38a90f0c187b872c1372f31ab48c8035b010f1ea59e786 +size 32262 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0a1f63ab269bedd641da06d400c159e0603a7d --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:959966c5117a56a1062ae606136e91dd2bb57d7775e24ff3e3f17c9543e10f59 +size 125566 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42078fc631f96cea90209e4cda79418d15a1d51e --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/552265bdbcf6d43d341fd018a9076269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acda6ee1179caac3a463f5584339c1dd55e5eeda3d447b8bf1cea964ca77eecc +size 35678 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afe594282cd8ec32e8d9f1cebca5f39a3f44bc3b --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdb76cf51a501c95827231e863b82dfd2db45ef0f76420486756dc39ac872530 +size 42630 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50d29c4c5632b55beb63c80bbaf4409aacc493b2 --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51b107041b9f04fedf8702323ea706ef7e60144869a984002d5e2dfdf4b3459a +size 36481 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7891ad4da866f8afa77ca25dc85476b390f8447 --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a02d9c72e32cfb302c5fd9b64b961d1940f565b2e5e663e9ed88d0336be29b1 +size 7391 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..153638751a87d8f123642e0335c4735d09b0ffc5 --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ca86b3aa431ba58b1f12e5edf705d397bfcbff17e8f281a681945d2aac5530c +size 126326 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55953bf0c2b718c079e981809e364cfc16f8c405 --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfaaad2213b4339856fd585a15924db90d363a3e0fd9226eb716977b430c375c +size 34268 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7dac65d7693d4f097c54c888d0c0adfc5808dcc --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a77b60ee17ec2b73707979251cfd36829a8981b29cbbdbd4d15a742c60b11c5 +size 130795 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e033dc9b44066d4f8da263aabee0a6a460b70ab1 --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e93e716bfb63ff1ffca6b1bd88095f86281b93659c99577dd91a38fe69d16fce +size 40671 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7876326d7cf7a247a79aab38fd052252bbd9738f --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9234d3a2105623a176a8ba9ad4a56afe0ad39376c2caa50f6f9eba746ee6f58 +size 103815 diff --git a/marked/M/T-REC-M.3704-201001-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3704-201001-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3eec8dec60682b7786e9dcad7d3aab412761bcd --- /dev/null +++ b/marked/M/T-REC-M.3704-201001-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76a3591d294b41a1a5aad26fcac857519a2ffe2858f4153462e33310a6b7845b +size 79247 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da9afac3cd1ba34c93addd8112202dd7c2959df8 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c10cdf0efd8db4c16372964cacb4491fbd90dff4ad949c491e007af84d311ad3 +size 32660 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b215e20686d55cbaf99e3423bd5a65c8a829187 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddbc3829b7c121414bd664511fecad3276f94fe1345221515786f356c773a0d3 +size 25907 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e6a9477c9a14d00ed7dba6e3389bf7fbf59d7b2 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e443052a84059f8b5911961469c1ff7bfc3015866805d27865c9eb7869f32cc4 +size 48600 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..618398ac11e01f9c9db90192050ca870680368ea --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5868fe074df0769a36c43a24b35faed4f45ace7295adfdb49a8bb8101829bac +size 80928 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1262b961384354f78467b23dbbbaf788fb500955 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a57ebd4d073caeb46509832d3d3cff6bb38bcab43ae45ff038e6d3c45c3aaa8 +size 25763 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3441c9bf5fbaf0c4e7e3213e208bd559d4d9357f --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04fb16e924365e08d4f4eba534988b5fbdfc1f8e15fc3be2f79e0e9e74b5911d +size 50568 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.3705-201303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd19bf08db65064e4f74b008afbbd06015ddaf38 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:301ea64e706d50232682b48cfe838c0aaa1f7c19716bb8085fa783353afa4c09 +size 105028 diff --git a/marked/M/T-REC-M.3705-201303-I_PDF-E/raw.md b/marked/M/T-REC-M.3705-201303-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c6af2b2c01cf71e4df7d33aab9dce6c7ddc34d13 --- /dev/null +++ b/marked/M/T-REC-M.3705-201303-I_PDF-E/raw.md @@ -0,0 +1,881 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3705** + +(03/2013) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Integrated services digital networks + +--- + +**Common management services – Log +management – Protocol neutral requirements +and analysis** + +Recommendation ITU-T M.3705 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3705 + +## Common management services – Log management – Protocol neutral requirements and analysis + +## Summary + +Recommendation ITU-T M.3705 provides the requirements and analysis for one of the common management services – log management. This Recommendation is a rewrite of Recommendation ITU-T X.735 under the new methodology specified in Recommendation ITU-T M.3020 to provide a protocol neutral information model for log management. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T M.3705 | 2013-03-16 | 2 | + +## Keywords + +Common management service, log management. + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2013 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Requirements ..... | 2 | +| 6.1 Business level requirements ..... | 3 | +| 7 Analysis ..... | 13 | +| 7.1 Concepts and background..... | 13 | +| 7.2 Information object classes ..... | 14 | +| 7.3 Interface definition ..... | 20 | +| Bibliography..... | 24 | + + + +# Recommendation ITU-T M.3705 + +## Common management services – Log management – Protocol neutral requirements and analysis + +# 1 Scope + +This Recommendation defines the requirements for basic log management which includes the following: specify what to log, start/suspend/resume/stop logging, retrieve log records, and generate an alarm when encountering certain logging problems. The technique-specific and device-specific event and message logging will be derived from this Recommendation, and the generic logging management objects, attributes and operations will be reused. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2011), *Management interface specification methodology*. +- [ITU-T M.3160] Recommendation ITU-T M.3160 (2008), *Generic, protocol-neutral management information model*. +- [ITU-T M.3700] Recommendation ITU-T M.3700 (2010), *Common management services – Object management – Protocol neutral requirements and analysis*. +- [ITU-T M.3701] Recommendation ITU-T M.3701 (2010), *Common management services – State management – Protocol neutral requirements and analysis*. +- [ITU-T M.3702] Recommendation ITU-T M.3702 (2010), *Common management services – Notification management – Protocol neutral requirements and analysis*. +- [ITU-T M.3703] Recommendation ITU-T M.3703 (2010), *Common management services – Alarm management – Protocol neutral requirements and analysis*. +- [ITU-T X.680] Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, *Information Technology – Abstract Syntax Notation One (ASN.1) – Specification of basic notation*. +- [ITU-T X.701] Recommendation ITU-T X.701 (1997) | ISO/IEC 10040:1998, *Information technology – Open Systems Interconnection – Systems management overview*. +- [ITU-T X.735] Recommendation ITU-T X.735 (1992) | ISO/IEC 10164-6:1993, *Information Technology – Open Systems Interconnection – Systems Management: Log control function*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +### 3.1.1 notification [ITU-T X.701]. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 notification log:** A managed resource in which notifications are stored. Notification logs contain notification log records. A notification log may represent a physical or a logical/virtual storage, which may not be visible to a manager. + +**3.2.2 notification log record:** A notification log record records track information about when a particular notification entered the notification log and the details of the notification. Each notification log record is associated with one notification. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-------------------------------------------| +| CORBA | Common Object Request Broker Architecture | +| DN | Distinguished Name | +| EMS | Element Management System | +| IOC | Information Object Class | +| IRP | Integration Reference Point | +| NE | Network Element | +| NL | Notification Log | +| NM | Network Manager | +| NMS | Network Management System | +| NR | Network Resource | +| OS | Operations System | +| UML | Unified Modelling Language | +| XML | extensible Markup Language | + +## 5 Conventions + +This Recommendation uses the conventions defined in [ITU-T M.3020] for requirements capture and analysis. + +# 6 Requirements + +A general-purpose notification logging mechanism is required to hold notifications related to different functional areas in the network. + +This service uses the following services and thus implicitly imports all the requirements defined therein: + +- Notification management [ITU-T M.3702] +- State management [ITU-T M.3701] + +In addition, the following specific requirements apply for log management as specified in this and subsequent clauses. + +## 6.1 Business level requirements + +### 6.1.1 List of requirements + +#### 6.1.1.1 General requirements + +| Identifier | Definition | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-LM-FUN-01 | Any notification log must be capable of storing all data related to any type of notification (i.e., any class which extends Notification as defined in [ITU-T M.3702]). | +| REQ-LM-FUN-02 | The notification log control service will allow the selection of notification log records that are to be logged by a management system (NMS or EMS) in a new notification log or a particular existing notification log. | +| REQ-LM-FUN-03 | It will be possible to start and stop logging to a specific notification log or all notification logs. | +| REQ-LM-FUN-04 | The ability for a client system to modify the criteria used in logging notification records. | +| REQ-LM-FUN-05 | Specification of a mechanism to enable notification logging to be suspended and subsequently to be resumed. | +| REQ-LM-FUN-06 | The ability for a client system to retrieve and delete notification log records. | +| REQ-LM-FUN-07 | The ability for a client system to create and delete those notification logs. | +| REQ-LM-FUN-08 | The ability to log partial notifications. | +| REQ-LM-FUN-09 | The manager may request a list of all log activities currently managed by the agent. The agent returns a list of notification log identifiers to the manager. The manager may then use these identifiers to query a log or parts of it. | +| REQ-LM-FUN-10 | The agent will assign a unique identifier to each notification log whether created autonomously by the agent or on the request of a manager. | +| REQ-LM-FUN-11 | All notifications available at the agent for potential transmission shall be logged if requested by a start log request, irrespective of the notification subscriptions and filter settings. | +| REQ-LM-FUN-12 | The notification log record will contain a notification as specified by [ITU-T M.3702]. | +| REQ-LM-FUN-13 | 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. | +| REQ-LM-FUN-14 | The agent should avoid the logging of notifications resulting from asynchronous alarm synchronization. | + +#### 6.1.1.2 Status of the notification log state + +| Identifier | Definition | +|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-LM-FUN-15 | The ability for a client system to determine whether the logging characteristics were modified or whether any notification log records have been lost. | +| REQ-LM-FUN-16 | The notification log management system must notify all interested OS about its current state. An event-based approach is used to update OS 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 according to the object management functions defined in [ITU-T M.3700]. | +| REQ-LM-FUN-17 | 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 according to the object management functions defined in [ITU-T M.3700]. | + +| Identifier | Definition | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-LM-FUN-18 | To notify OSs about the loss or imminent loss of notification log records, the system is able to emit capacity threshold alarms as defined in [ITU-T M.3703] 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. | +| REQ-LM-FUN-19 | The system may emit other events to notify an OS of the completion of an I/O intensive operation, such as the deletion of notification log records. | + +#### 6.1.1.3 Notification log/notification log record retrieval + +| Identifier | Definition | +|---------------|------------------------------------------------------------------------------------------------------| +| REQ-LM-FUN-20 | An OS may retrieve notification log records by querying a particular notification log with a filter. | + +The ability of an OS to export some subsets of notification logs maintained by itself to the W3C XML log format is for further study. + +#### 6.1.1.4 Notification log full action + +| Identifier | Definition | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REQ-LM-FUN-21 |

The OS must be able to set the behaviour of a notification log when it becomes full. Two actions are recommended, 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.
| + +### 6.1.2 Actor roles + +The capabilities described in this Recommendation are available and relevant to all agents and managers. + +### 6.1.3 Telecommunication resources + +The log management functionality is applicable to all types of telecommunication resources. + +### 6.1.4 High level use case diagrams + +The first overview use-case diagram in Figure 1 shows the overall interaction of the Notification log management function. + +![UML Use case diagram for Log Management. The central use case is 'Log Management FS'. It includes 'Log Object Management FS', 'Log Record Management FS', and 'Notify capacity Alarm notification'. 'Log Object Management FS' includes 'Create Log', 'Delete Log', 'Modify logging criteria', 'Suspend logging', and 'Resume logging'. 'Log Record Management FS' includes 'Query list of logs', 'Delete Log record', and 'Retrieve Log records'. 'Notify capacity Alarm notification' includes 'Notify state of logging'. 'State Management FS', 'Fault Management FS', and 'Notification Management FS' extend 'Notify state of logging'. 'Object Management FS' extends 'Log Management FS'. An actor 'Manager' uses 'Log Management FS'.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +``` + +usecaseDiagram + actor Manager + usecase "Log Management FS" + usecase "Object Management FS" + usecase "Log Object Management FS" + usecase "Log Record Management FS" + usecase "Notify capacity Alarm notification" + usecase "Create Log" + usecase "Delete Log" + usecase "Modify logging criteria" + usecase "Suspend logging" + usecase "Resume logging" + usecase "Query list of logs" + usecase "Delete Log record" + usecase "Retrieve Log records" + usecase "Notify state of logging" + usecase "State Management FS" + usecase "Fault Management FS" + usecase "Notification Management FS" + + Manager -.-> "Log Management FS" : use + "Log Management FS" -.-> "Object Management FS" : extend + "Log Management FS" -.-> "Log Object Management FS" : include + "Log Management FS" -.-> "Log Record Management FS" : include + "Log Management FS" -.-> "Notify capacity Alarm notification" : include + "Log Object Management FS" -.-> "Create Log" : include + "Log Object Management FS" -.-> "Delete Log" : include + "Log Object Management FS" -.-> "Modify logging criteria" : include + "Log Object Management FS" -.-> "Suspend logging" : include + "Log Object Management FS" -.-> "Resume logging" : include + "Log Record Management FS" -.-> "Query list of logs" : include + "Log Record Management FS" -.-> "Delete Log record" : include + "Log Record Management FS" -.-> "Retrieve Log records" : include + "Notify capacity Alarm notification" -.-> "Notify state of logging" : include + "State Management FS" -.-> "Notify state of logging" : extend + "Fault Management FS" -.-> "Notify state of logging" : extend + "Notification Management FS" -.-> "Notify state of logging" : extend + +``` + +UML Use case diagram for Log Management. The central use case is 'Log Management FS'. It includes 'Log Object Management FS', 'Log Record Management FS', and 'Notify capacity Alarm notification'. 'Log Object Management FS' includes 'Create Log', 'Delete Log', 'Modify logging criteria', 'Suspend logging', and 'Resume logging'. 'Log Record Management FS' includes 'Query list of logs', 'Delete Log record', and 'Retrieve Log records'. 'Notify capacity Alarm notification' includes 'Notify state of logging'. 'State Management FS', 'Fault Management FS', and 'Notification Management FS' extend 'Notify state of logging'. 'Object Management FS' extends 'Log Management FS'. An actor 'Manager' uses 'Log Management FS'. + +Figure 1 – Log management function set + +#### 6.1.4.1 Use case: modify logging criteria + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager needs to change the attribute values of a log in the agent, such as the filtering criteria of event logging, the log full action, the capacity alarm threshold, and so on. The manager modifies the attribute values of a log through the management interface. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between manager and agent is available. The agent supports the function of modifying a log. | | +| Pre-conditions | The specified log exists in the agent and it is suspended. | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager sends a request to the agent to modify the attribute values of a log. The input parameters are the attribute names to be modified and the corresponding new values. The attributes that can be modified include: max log size, log full action, | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| | capacity alarm threshold, and filtering criteria. | | +| Step 2.1 | The agent updates the specific log with a new attribute value; if the modification succeeds, the log will use new criteria to record events and act according to these new attribute values. | | +| Step 2.2 | If the modification fails, the agent will return an exception. | | +| Ends when | The agent has finished the update on the log. | | +| Exceptions | Invalid parameter
Log not suspended
Agent processing error
Communication error | | +| Post-conditions | The log is modified by the agent on the request of the manager. The agent may send the corresponding attribute value change notification to the manager. The newly modified log then begins to record events with the new criteria and behaves according to the new attribute values. | | +| Traceability | REQ-LM-FUN-01, REQ-LM-FUN-03, REQ-LM-FUN-04 | | + +#### 6.1.4.2 Use case: suspend logging + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The manager temporarily needs to suspend a log-in agent. The manager temporarily does not want the log to record event information in the agent, or the manager needs to change the attribute values of the log object. The manager can suspend a log through the management interface. Thereafter, the log will not record any events until it has resumed. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of suspending a log. | | +| Pre-conditions | The specified log exists in the agent and it is not suspended. | | +| Begins when | The manager sends a request to suspend the log. | | +| Step 1 | In this use case, the manager sends a request to the agent to suspend a log, that is, to set the administrative state of the log object from "unlocked" to "locked". | | +| Step 2 | The agent updates the administrative state value. If the operation succeeds, the log object will not record any events until it has resumed. If the operation fails, Agent will return an exception. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Ends when | The agent suspends the log and a state change notification is sent. | | +| Exceptions | Log already suspended; agent processing error; communication error. | | +| Post-conditions | The log is suspended by the agent on the request of the manager. The agent may send the corresponding state change notification to the manager, and the log does not record any events until it has resumed. | | +| Traceability | REQ-LM-FUN-05 | | + +#### 6.1.4.3 Use case: resume logging + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The manager can resume a suspended log through the management interface, so that the log can record events again. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of resuming a log. | | +| Pre-conditions | The specified log exists in the agent and it is suspended. | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | In this use case, the manager sends a request to the agent to resume a suspended log, that is, to set the administrative state of the log object from "locked" to "unlocked". | | +| Step 2 | The agent updates the administrative state of the log. If the operation succeeds, the log object will begin to record events again. If the operation fails, the agent will return an exception. | | +| Ends when | The agent has finished updating the log and continues logging. | | +| Exceptions | Log not suspended
Agent processing error
Communication error | | +| Post-conditions | The log is resumed by the agent on the request of the manager. The agent may send the corresponding state change notification to the manager. The log continues to record events according to its filtering criteria. | | +| Traceability | REQ-LM-FUN-05 | | + +#### 6.1.4.4 Use case: create log + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager needs the agent to log event information so that the information may be queried in the future for some specific situations such as data loss. The manager creates a log through the management interface. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of creating a log.
In the case that the agent can initialize a log instance(s) by itself, it is not required to provide this function in the interface. | | +| Pre-conditions | | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager requests the agent creates a log. The parameters in the request include the initial administrative state, max log size, log full action, capacity alarm threshold, and filtering criteria of the log object. | | +| Step 2 | The agent creates a log object using given parameters.
If the log has been created successfully, the agent will then return the identifier of the log and send an object creation notification to the manager. Whether events will be recorded as log records, depends on the filtering criteria defined in the log. If the creation fails, the agent will return an exception. | | +| Ends when | Log object is created and the object create notification is sent. | | +| Exceptions | Invalid parameter
Agent processing error
Communication error | | +| Post-conditions | The log is created by the agent on the request of the manager. The agent returns the identifier of the log and may send the corresponding object creation notification to the manager. The events will be recorded according to the filtering criteria in the newly created log. | | +| Traceability | REQ-LM-FUN-02, REQ-LM-FUN-03, REQ-LM-FUN-06, REQ-LM-FUN-07, REQ-LM-FUN-10 | | + +#### 6.1.4.5 Use case: delete log + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager does not need the log in the agent to record any event information. The manager deletes a log through the management interface.
In the case that the agent system can initialize a log instance(s), it is not required to provide this function in the interface. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of deleting a log. | | +| Pre-conditions | The specified log exists in the agent and it is suspended. | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager requests the agent deletes a log. The parameter in the request is the ID of the log object. | | +| Step 2 | The agent deletes the specific log object.
If the log has been deleted successfully, the agent may then send the corresponding object deletion notification to the manager. If the deletion fails, the agent will return an exception. | | +| Ends when | The log is deleted and an object delete notification is sent. | | +| Exceptions | Unknown log
Log not suspended
Agent processing error
Communication error | | +| Post-conditions | The log and the associated log records are deleted by the agent on the request of the manager. The agent may send the corresponding object deletion notification to the manager. | | +| Traceability | REQ-LM-FUN-06, REQ-LM-FUN-07 | | + +#### 6.1.4.6 Use case: query list of logs + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager may query the attribute values of a log, including administrative state, operational state, max log size, current log size, log full action, number of records, alarm status, capacity alarm threshold, filtering criteria, and so on.
The manager queries a specific log or all log objects in the agent. | | +| Actor and roles | The manager invokes operations on the agent. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of querying a log. | | +| Pre-conditions | The specified log exists in the agent. | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager sends a request to query a log. The parameters in the request are the specific object name of the log to be queried and the attribute names to be queried. | | +| Step 2 | If the operation succeeds, the agent will return the corresponding attribute values. Otherwise, the agent will return an exception. | | +| Ends when | The query response is sent. | | +| Exceptions | Invalid parameter
Agent processing error
Communication error | | +| Post-conditions | The agent returns the attribute values of the log requested by the manager. | | +| Traceability | REQ-LM-FUN-09 | | + +#### 6.1.4.7 Use case: notify state of logging + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | The manager may want to know the latest logging state. The agent will notify the manager when the logging state has changed. | | +| Actor and roles | The agent notifies the manager. | | +| Assumptions | The communication between the manager and the agent is available.
The manager has subscribed to this kind of notifications. See [ITU-T M.3702] | | +| Pre-conditions | The notification service defined in [ITU-T M.3702] is supported. | | +| Begins when | The value of the state attributes defined in [ITU-T M.3700] has changed, including administrativeState, operationalState, availabilityStatus, loggingState. | | +| Step 1 | The agent constructs a state Change Notification as defined in [ITU-T M.3700], the content will include the changed state attributes and values. | | +| Step 2 | The agent sends the notification to the manager, following the notification service rule in [ITU-T M.3702]. | | +| Step 3 | The notification will also be logged if it satisfies the logging criteria. | | +| Ends when | The notification is logged if it satisfies the logging criteria. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|------------------------------------------------------------------------------------------------|---------------------------------------------| +| Exceptions | Invalid parameter
Agent processing error
Communication error | | +| Post-conditions | A new notification log record is generated if the notification satisfies the logging criteria. | | +| Traceability | REQ-LM-FUN-16 | | + +#### 6.1.4.8 Use case: retrieve log records + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Goal | In the case that the notification information between the manager and the agent is not synchronized due to broken communication, abnormal data, lost data or other reasons, the manager needs to query log records in the agent to synchronize the notification information between two systems.
The manager queries the log records contained in a log according to certain criteria. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of querying log records. | | +| Pre-conditions | The specified log exists in the agent. | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager sends a "query log record" request to the agent. The parameters in the request are the filtering criteria and the time boundary. | | +| Step 2 | If the query succeeds, the agent will return the log records that satisfy the criteria and the time boundary. Otherwise, if the query fails, the agent will return an exception. | | +| Ends when | The agent response with the log records according to the query condition. | | +| Exceptions | Invalid parameter
No such log records
Agent processing error
Communication error | | +| Post-conditions | The corresponding log records are returned by the agent. | | +| Traceability | REQ-LM-FUN-20 | | + +#### 6.1.4.9 Use case: delete log record + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | In the case where the information in some log records is of no use to the manager (too old or having been transferred to the manager), the manager can delete some or all log records in the agent. The manager deletes log records contained in a log according to certain criteria. | | +| Actor and roles | The manager invokes operations on the agent. | | +| Assumptions | The communication between the manager and the agent is available. The agent supports the function of deleting log records. | | +| Pre-conditions | The specified log exists in the agent. | | +| Begins when | The manager sends the request to the agent. | | +| Step 1 | The manager sends a deletion request to the agent. The parameters in the request are the filtering criteria and the time boundary. | | +| Step 2 | The agent will find out and delete the corresponding records that satisfy the criteria and the time boundary. If the deletion fails, the agent will return an exception. | | +| Ends when | Log records are successfully deleted. | | +| Exceptions | Invalid parameter
No such log records
Agent processing error
Communication error | | +| Post-conditions | The log records that satisfy the filtering criteria and the time boundary are deleted. | | +| Traceability | REQ-LM-FUN-06 | | + +#### 6.1.4.10 Use case: notify capacity alarm notification + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | In case the number of log records has reached the threshold of log record capacity, the agent will send an alarm notification to notify the manager. | | +| Actor and roles | The agent will send an alarm notification to the manager. | | +| Assumptions | The communication between the manager and the agent is available.
The manager had subscribed to such a notification.
See [ITU-T M.3702] | | +| Pre-conditions | The notification service defined in [ITU-T M.3702] is supported.
The alarm service defined in [ITU-T M.3703] is supported. | | + +| Use case stage | Evolution/Specification | <<Uses>>
Related use
| +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| Begins when | The number of log records reaches the threshold of log record capacity. | | +| Step 1 | The agent automatically maintains the number of log records. It will detect:
If the number of log records increases above the threshold of log record capacity, go to step 2.
If the number of log records decreases beneath the threshold of log record capacity, go to step 3. | | +| Step 2 | The agent will construct the alarm information data (see clause 7.2.3.1 of [ITU-T M.3703]) with the probable cause set to Log Capacity and alarmType set to QoS Alarm.
Follow the alarm reporting use case in clause 6.3.4.2 of [ITU-T M.3703].
Go to step 4. | | +| Step 3 | The agent will construct the alarm information data (see clause 7.2.3.1 of [ITU-T M.3703]) with the probable cause set to Log Capacity and alarmType set to QoS Alarm.
Follow the alarm clear use case in clause 6.3.4.4 of [ITU-T M.3703]. | | +| Step 4 | The notification will also be logged if it satisfies the logging criteria. | | +| Ends when | The notification has been sent. | | +| Exceptions | Agent processing error
Communication error | | +| Post-conditions | A new notification log record is generated if the notification satisfies the logging criteria. | | +| Traceability | REQ-LM-FUN-18 | | + +# 7 Analysis + +According to [ITU-T M.3020], the "Analysis" phase will include information object class definitions and interface definitions. + +## 7.1 Concepts and background + +The log management service makes use of the following common management services as shown in the two diagrams below. + +![Figure 2 – System context diagram showing a Manager (Managing system) connected to an Agent (Managed system), which is connected to Resources. The Manager provides Log management service, Notification management service, and Alarm management service to the Agent. Reference: M.3705(13)_F02](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +Figure 2 – System context diagram showing a Manager (Managing system) connected to an Agent (Managed system), which is connected to Resources. The Manager provides Log management service, Notification management service, and Alarm management service to the Agent. Reference: M.3705(13)\_F02 + +**Figure 2 – System context** + +![Figure 3 – System context B diagram showing a Manager (Managing system) connected to an Agent (Managed system). The Agent is connected to Resources. The Manager provides Log management service, Notification management service, and Alarm management service to the Agent. Reference: M.3705(13)_F03](5445597cceefaca1ac89e710fe339325_img.jpg) + +Figure 3 – System context B diagram showing a Manager (Managing system) connected to an Agent (Managed system). The Agent is connected to Resources. The Manager provides Log management service, Notification management service, and Alarm management service to the Agent. Reference: M.3705(13)\_F03 + +**Figure 3 – System context B** + +## **7.2 Information object classes** + +### **7.2.1 Information entities imported and local labels** + +| Label reference | Local label | +|---------------------------------------------------|-------------| +| [ITU-T M.3160], information object class, Top | Top | +| [ITU-T M.3160], information object class, Network | Network | + +### **7.2.2 Class diagram** + +#### **7.2.2.1 Attributes and relationships** + +This clause introduces the set of information object classes (IOCs) that encapsulate information within the agent. The intent is to identify the information required for operations and notification. This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specifications of the various aspects of these support object classes. + +![UML class diagram showing information object class relationships. A base class 'Network [ITU-T M.3160]' is at the top. Below it are 'Log' and 'NLIRP' classes. 'Log' has a 1-to-many relationship with 'Network' (role 'log'). 'NLIRP' has a 1-to-many relationship with 'Network' (role 'nlirp'). 'Log' and 'NLIRP' are associated with each other (roles 'log' and 'nlirp'). 'LogRecord' is associated with 'Log' (1-to-many).](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +``` + +classDiagram + class Network["«InformationObjectClass»\nNetwork [ITU-T M.3160]"] + class Log["«InformationObjectClass»\nLog"] + class NLIRP["«InformationObjectClass»\nNLIRP"] + class LogRecord["«InformationObjectClass»\nLogRecord"] + + Network "1" *-- "*" Log : log + Network "1" *-- "*" NLIRP : nlirp + Log "*" -- "1" NLIRP : Relation-NLIRP-Log + LogRecord "1" *-- "*" Log + +``` + +UML class diagram showing information object class relationships. A base class 'Network [ITU-T M.3160]' is at the top. Below it are 'Log' and 'NLIRP' classes. 'Log' has a 1-to-many relationship with 'Network' (role 'log'). 'NLIRP' has a 1-to-many relationship with 'Network' (role 'nlirp'). 'Log' and 'NLIRP' are associated with each other (roles 'log' and 'nlirp'). 'LogRecord' is associated with 'Log' (1-to-many). + +Figure 4 – Information object class relationships + +#### 7.2.2.2 Inheritance + +![UML class diagram showing information object class inheritance. A base class 'top [ITU-T M.3160]' is at the top. Below it are 'Log', 'LogRecord', and 'NLIRP' classes, which inherit from 'top'. 'Log' has attributes: administrativeState, availabilityStatus, capacityAlarmThreshold, discriminator, logFullAction, loggingState, logId, maxNumOfLogRecords, numOfLogRecords, operationalState, startTime, stopTime, weekMask. 'LogRecord' has attributes: loggedNotification, loggingTime, logRecordId. 'NLIRP' has attribute: maxLogs : Integer.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +classDiagram + class top["«InformationObjectClass»\ntop [ITU-T M.3160]"] + class Log["«InformationObjectClass»\nLog"] + class LogRecord["«InformationObjectClass»\nLogRecord"] + class NLIRP["«InformationObjectClass»\nNLIRP"] + + Log --|> top + LogRecord --|> top + NLIRP --|> top + +``` + +UML class diagram showing information object class inheritance. A base class 'top [ITU-T M.3160]' is at the top. Below it are 'Log', 'LogRecord', and 'NLIRP' classes, which inherit from 'top'. 'Log' has attributes: administrativeState, availabilityStatus, capacityAlarmThreshold, discriminator, logFullAction, loggingState, logId, maxNumOfLogRecords, numOfLogRecords, operationalState, startTime, stopTime, weekMask. 'LogRecord' has attributes: loggedNotification, loggingTime, logRecordId. 'NLIRP' has attribute: maxLogs : Integer. + +Figure 5 – Information object class inheritance + +### 7.2.3 Information object class definitions + +| Class name | Qualifier | Requirement IDs | +|------------|-----------|-----------------| +| NLIRP | O | | +| Log | M | REQ-LM-FUN-07 | +| LogRecord | M | REQ-LM-FUN-06 | + +#### 7.2.3.1 NLIRP(M) + +##### 7.2.3.1.1 Definition + +NLIRP is the representation of the notification log management capabilities specified by this Recommendation. This object is provisioned by Agent. + +##### 7.2.3.1.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|----------------|-------------------|----------------|-----------------|-----------------| +| maxLogs | O | O | – | | + +#### 7.2.3.2 Log + +##### 7.2.3.2.1 Definition + +The Log IOC is the representation of a notification log. + +##### 7.2.3.2.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|------------------------|-------------------|----------------|-----------------|--------------------------------| +| logId* | M | M | O | REQ-LM-FUN-10 | +| discriminator | M | M | M | REQ-LM-FUN-02
REQ-LM-FUN-04 | +| administrativeState | M | M | M | REQ-LM-FUN-05
REQ-LM-FUN-16 | +| operationalState | M | M | – | REQ-LM-FUN-16 | +| logFullAction | O | O | O | REQ-LM-FUN-21 | +| availabilityStatus | O | O | – | REQ-LM-FUN-16 | +| maxNumOfLogRecords | M | M | M | REQ-LM-FUN-18 | +| numOfLogRecords | M | M | – | REQ-LM-FUN-18 | +| capacityAlarmThreshold | O | O | O | REQ-LM-FUN-18 | +| startTime | O | O | O | REQ-LM-FUN-03 | +| stopTime | O | O | O | REQ-LM-FUN-03 | +| weekMask | O | O | O | REQ-LM-FUN-03 | +| loggingState | O | O | – | REQ-LM-FUN-16 | + +NOTE – \* indicates it is the naming attribute of this IOC. + +##### 7.2.3.2.3 State diagram + +![State diagram for logging. The diagram shows three states: Logging, Wrapping, and Halt. Logging is the initial state, entered via an entry point labeled '[in time schedule]'. Transitions from Logging to Wrapping are labeled '[log full and logFullAction = wrap]' and '[lower than capacity limit]'. Transitions from Logging to Halt are labeled '[log full and logFullAction = halt]' and '[lower than capacity]'. Transitions from Wrapping to Logging are labeled '[lower than capacity limit]'. Transitions from Halt to Logging are labeled '[lower than capacity]'. Both Wrapping and Halt have transitions to a final state (a solid circle) labeled '[timeout]'. The diagram is labeled 'M.3705(13)_F06'.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Logging : [in time schedule] + Logging --> Wrapping : [log full and logFullAction = wrap] + Logging --> Wrapping : [lower than capacity limit] + Logging --> Halt : [log full and logFullAction = halt] + Logging --> Halt : [lower than capacity] + Wrapping --> Logging : [lower than capacity limit] + Halt --> Logging : [lower than capacity] + Wrapping --> [*] : [timeout] + Halt --> [*] : [timeout] + +``` + +State diagram for logging. The diagram shows three states: Logging, Wrapping, and Halt. Logging is the initial state, entered via an entry point labeled '[in time schedule]'. Transitions from Logging to Wrapping are labeled '[log full and logFullAction = wrap]' and '[lower than capacity limit]'. Transitions from Logging to Halt are labeled '[log full and logFullAction = halt]' and '[lower than capacity]'. Transitions from Wrapping to Logging are labeled '[lower than capacity limit]'. Transitions from Halt to Logging are labeled '[lower than capacity]'. Both Wrapping and Halt have transitions to a final state (a solid circle) labeled '[timeout]'. The diagram is labeled 'M.3705(13)\_F06'. + +Figure 6 – State diagram for logging + +It is up to a vendor-specific functionality whether a log that has been stopped shall remain visible across the interface or not. The deletion time of logs is vendor specific. + +##### 7.2.3.2.2 Notifications + +| Name | Qualifier | Requirement IDs | Notes | +|----------------------------------------------------|-----------|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Object Create Notification [ITU-T M.3700] | M | REQ-LM-FUN-07
REQ-LM-FUN-17 | | +| Object Delete Notification [ITU-T M.3700] | M | REQ-LM-FUN-07
REQ-LM-FUN-17 | | +| Attribute Value Change Notification [ITU-T M.3700] | M | REQ-LM-FUN-02
REQ-LM-FUN-15
REQ-LM-FUN-16 | Notification will be generated in case the following attribute is changed:
discriminator, logFullAction, maxNumOfLogRecords, capacityAlarmThreshold, startTime, stopTime, interval | +| State Change Notification [ITU-T M.3700] | M | REQ-LM-FUN-02
REQ-LM-FUN-15
REQ-LM-FUN-16 | Notification will be generated in case the following attribute is changed:
administrativeState
operationalState
availabilityStatus
loggingState | +| Alarm Notification [ITU-T M.3703] | O | REQ-LM-FUN-18 | If capacityAlarmThreshold is not zero, in case numOfLogRecords reaches or is greater than capacityAlarmThreshold, an alarm is generated with probable cause " log capacity ". After numOfLogRecords is lower than capacityAlarmThreshold, the alarm disappeared. | + +#### 7.2.3.3 LogRecord + +##### 7.2.3.3.1 Definition + +The LogRecord IOC is the representation of an individual notification log record. + +##### 7.2.3.3.2 Attributes + +| Attribute name | Support qualifier | Read qualifier | Write qualifier | Requirement IDs | +|--------------------|-------------------|----------------|-----------------|-------------------------------------------------| +| logRecordId* | M | M | – | REQ-LM-FUN-13
REQ-LM-FUN-15 | +| loggingTime | M | M | – | REQ-LM-FUN-13 | +| loggedNotification | M | M | – | REQ-LM-FUN-01
REQ-LM-FUN-08
REQ-LM-FUN-12 | + +NOTE – \* indicates it is the naming attribute of this IOC. + +##### 7.2.3.3.3 Notifications (O) + +| Name | Qualifier | Requirement IDs | Notes | +|-------------------------------------------|-----------|-----------------|-------| +| Object Created Notification[ITU-T M.3700] | M | REQ-LM-FUN-19 | | +| Object Deleted Notification[ITU-T M.3700] | M | REQ-LM-FUN-19 | | + +### 7.2.4 Information relationship definitions + +| Relationship | Support qualifier | Requirement IDs | +|--------------------|-------------------|-----------------| +| Relation-nLIRP-log | M | | + +#### 7.2.4.1 Relation-NLIRP-Log (M) + +##### 7.2.4.1.1 Definition + +This represents the relationship between NLIRP and the log. + +##### 7.2.4.1.2 Role + +| Name | Definition | +|-------|--------------------------| +| nLIRP | It represents the NLIRP. | +| Log | It represents the log. | + +##### 7.2.4.1.3 Constraint + +| Name | Definition | +|-------------|-----------------------------------------------------------------------------------------| +| maxlog | The number of log object instances no greater than the maxlogs attribute value in NLIRP | +| uniqueLogId | The logId must be unique within Agent. | + +### 7.2.5 Information attribute definitions + +#### 7.2.5.1 Definition and legal values + +| Attribute name | Definition | Legal values | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| administrativeState | See [ITU-T M.3701] | | +| availabilityStatus | See [ITU-T M.3701] | | +| capacityAlarmThreshold | This attribute defines the threshold number of log records in a log. When numOfLogRecords reaches the threshold, it will generate a capacity alarm. | INTEGER
Integer greater or equal to 0, but smaller or equal to numOfLogRecords;
0 means no threshold. | +| discriminator | It specifies a filter constraint that Agent shall use to filter notifications; parameters in a notification can be used for filtering.
The support of a time-based filter is mandatory. Support of other filter constraints is optional. | Filter constraint grammar is protocol dependent | +| weekMask | This attribute defines the interval of logging. It may indicate the interval in each week or each day etc. to do logging. | WeekMask [ITU-T M.3160] | +| logFullAction | Indicate the action that will be taken by this instance of Log when the maxNumOfLogRecords has been reached. | LogFullActionType ::=
ENUMERATED {
wrap, halt }
• 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).
• halt: No more LogRecord(s) will be logged and all incoming events are discarded. LogRecord/s already in the log will be retained. | +| logRecordId | This attribute contains the id of a log record within a given log, assigned by the agent. | Name [ITU-T M.3020]
The value of this attribute must be unique amongst all log record contained by a given log. | +| loggingState | Provides an indication of the current state of a specific log. | LoggingStateType ::=
ENUMERATED {
logging, wrapping, halt, idle }
• logging
• wrapping
• halt
• idle (either not started or stopped) | +| loggingTime | This attribute defines the time that logged the notification. | GeneralizedTime [ITU-T X.680] | +| loggedNotification | This attribute defines the logged notification. | ANY, it can contain part of or all of the information of the logged notification. | + +| Attribute name | Definition | Legal values | +|--------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| maxNumOfLogRecords | This attribute defines the max number of log records supported in a log.
(Note) | INTEGER
Integer greater than 0 | +| numOfLogRecords | This attribute defines the current number of log records in a log. | INTEGER
Integer greater than or equal to 0. | +| operationalState | See [ITU-T M.3701] | | +| startTime | This attribute defines the time to start logging. It works with stopTime to mean the validated period of the log. | GeneralizedTime [ITU-T X.680] | +| stopTime | This attribute defines the time to end logging. | GeneralizedTime [ITU-T X.680] | + +NOTE – In [ITU-T X.735] it is indicated by bytes, but bytes are protocol related, so here use the number of records instead. + +#### 7.2.5.2 Constraints + +| Name | Definition | +|--------------------|-------------------------------------------------------------------------------------------------------| +| inv_logRecordCount | numOfLogRecords shall be less than or equal to maxNumOfLogRecords, and greater than or equal to zero. | +| Inv_logThreshold | capacityAlarmThreshold shall be less than or equal to maxNumOfLogRecords, and greater than zero. | + +## 7.3 Interface definition + +The common object management operations have been defined in [ITU-T M.3700], the creation, deletion and modification of log object can reuse the "create object", "delete object" and "modify object" operations in [ITU-T M.3700]. So there is no need to define create/delete/modify log operations in this Recommendation. + +There is an operation "getAttributes" defined in clause 7.3.1.1 of [ITU-T M.3700], which can be reused to retrieve log object with part or all of its attributes, so there is no need to define the "retrieve log object" operation in this Recommendation. + +This is the same for the deleting and retrieval of LogRecord object operations. + +### 7.3.1 Class diagram + +![UML Class diagram showing the relationship between NLIRP and LogInterface. NLIRP is an InformationObjectClass with attribute maxLogs: Integer. It implements LogInterface (suspendLogging(), resumeLogging()) and uses ObjectManagement (ITU-T M.3700) (createObject(), deleteObject(), getAttributes(), cancelOperation(), setAttributes()).](bb3354f497635d15bef873577125c48d_img.jpg) + +``` + +classDiagram + class NLIRP { + <> + NLIRP + maxLogs : Integer + } + class LogInterface { + <> + suspendLogging() + resumeLogging() + } + class ObjectManagement { + <> + ITU-T M.3700 + createObject() + deleteObject() + getAttributes() + cancelOperation() + setAttributes() + } + NLIRP --|> LogInterface : NLIRP-Realize-LogInterface + NLIRP ..> ObjectManagement : <> + +``` + +M.3705(13)\_F07 + +UML Class diagram showing the relationship between NLIRP and LogInterface. NLIRP is an InformationObjectClass with attribute maxLogs: Integer. It implements LogInterface (suspendLogging(), resumeLogging()) and uses ObjectManagement (ITU-T M.3700) (createObject(), deleteObject(), getAttributes(), cancelOperation(), setAttributes()). + +Figure 7 – Interface class diagram + +### 7.3.2 Generic rules + +This Recommendation follows the generic rules in clause B.2.3.2 of [ITU-T M.3020]. + +### 7.3.3 LogInterface interface(M) + +#### 7.3.3.1 Operation suspendLogging (M) + +##### 7.3.3.1.1 Definition + +Manager invokes this operation to suspend a log object. Thus, the log pauses logging and can be resumed later. + +##### 7.3.3.1.2 Input parameters + +The input parameters include the following: + +| Parameter name | Support qualifier | Information type/
Legal values | Comment | +|--------------------|-------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| invokeIdentifierIn | CM | INTEGER
A unique identifier that is Solution Set dependent. | This parameter identifies the current invocation. This parameter is used in the 'cancelOperation' operation [ITU-T M.3700] to cancel an on-going 'getMOAttributes' operation. | +| logObjectInstance | M | Name | It identifies the log object instance to be suspended. | + +##### 7.3.3.1.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|---------------------|-------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InvokeIdentifierOut | CM (Note) | INTEGER
invokeIdentifierIn from the input parameters of this operation | This parameter identifies the current invocation in both IRPManager and IRPAgent. This parameter can be used together with the 'cancelOperation' operation to cancel an on-going 'getMOAttributes' operation. | +| Status | M | ENUMERATED {
operationSucceeded,
operationFailed
} | An operation may fail because of a specified or unspecified reason. | + +##### 7.3.3.1.4 Pre-condition + +| Assertion name | Definition | +|------------------|-------------------------------------------| +| logSuspendAssert | Log must not be suspended before suspend. | + +##### 7.3.3.1.5 Post-condition + +| Assertion name | Definition | +|------------------------------------|-----------------------------------------------------------------------------------------------------------| +| logSuspended | The administrativeState attribute is set to locked. | +| stateChangeNotification
Emitted | A state change notification is sent after the administrativeState attribute in the log object is updated. | + +##### 7.3.3.1.6 Exceptions + +| Assertion name | Definition | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| logIsAlreadySuspended | Condition: the requested log object is "Already" suspended.
Returned information: The output parameter status.
Exit state: Entry state. | + +#### 7.3.3.2 Operation resumeLogging (M) + +##### 7.3.3.2.1 Definition + +Manager invokes this operation to resume a log object instance, so that the paused logging can be resumed. + +##### 7.3.3.2.2 Input parameters + +| Parameter name | Support qualifier | Information type/
Legal values | Comment | +|--------------------|-------------------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| invokeIdentifierIn | CM | INTEGER
A unique identifier that is Solution Set dependent. | This parameter identifies the current invocation. This parameter is used in the 'cancelOperation' operation [ITU-T M.3700] to cancel an on-going 'getMOAAttributes' operation. | +| logObjectInstance | M | Name | It identifies the log object instance to be suspended. | + +##### 7.3.3.2.3 Output parameters + +| Parameter name | Support qualifier | Matching information/
Information type/
Legal values | Comment | +|---------------------|-------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InvokeIdentifierOut | CM
(Note) | INTEGER
invokeIdentifierIn from the input parameters of this operation. | This parameter identifies the current invocation in both IRPManager and IRPAgent. This parameter can be used together with the 'cancelOperation' operation to cancel an on-going 'getMOAAttributes' operation. | +| Status | M | ENUMERATED {
operationSucceeded,
operationFailed
} | An operation may fail because of a specified or unspecified reason. | + +###### 7.3.3.2.4 Pre-condition + +| Assertion name | Definition | +|-----------------|--------------------------------------| +| logResumeAssert | Log must be suspended before resume. | + +##### 7.3.3.2.5 Post-condition + +| Assertion name | Definition | +|--------------------------------|---------------------------------------------------------------------------------------------| +| logResumed | The administrativeState attribute is set to unlocked. | +| stateChangeNotificationEmitted | A state change notification is sent after the state attribute in the log object is updated. | + +###### 7.3.3.2.6 Exceptions + +| Assertion name | Definition | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| logIsNotSuspended | Condition: the requested log object is not suspended.
Returned information: The output parameter status.
Exit state: Entry state. | + +## Bibliography + +[b-ITU-T Q.827.1] Recommendation ITU-T Q.827.1 (2004), *Requirements and analysis for the common management functions of NMS-EMS interfaces*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ceef75268bd7c200d2d37abb81d9e0b79a85fa3 --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e99a9a7edcb6c8026a16d850544bb2b04e38dfc01f193275d581a3736d2066b5 +size 36894 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d418267c5ece5a5496e8f0f6cc049616b40b7fc5 --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6083a8f1621f7fb9a5b3d9e550d869b85dfb79ac92e6a18db0c90ecf295e702b +size 44916 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779884e955fe847e02e985e53db7b7a9907274b6 --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a261427a402c5e9b8cbd9829529f46b9112333ee8cf800c0b7860db415572c1b +size 72583 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..675f7832b9567b5ea82af96e98b325caf527f46a --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:added7e035c94e6cd556f6cb63c517177aced13b8481373ae1764985acfc0fd9 +size 22618 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b43a05f69dcd4a9724e71e6f2e593f1e3d9c058 --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3cae62302403c2082c04392702cabd5bceec87aa35ebd6a4d9bf77c11b04346 +size 41228 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c096888336e5ba8fd6e0462390c84503ec339dc --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dda1a06d9278532a8187f4cc6825cf81981a898db768db37df4c0f153b1894d5 +size 25694 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad310e8f3640c8f69eb1ea3037c031e81120205b --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86bc807f64cfc50d8b0c3ba66af234eb3e2b4bd4ec5f662237a983d2bb2a27dc +size 55521 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3706-201311-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d39a818ff40aef1c0ee0c863b74222fbf65cd8 --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b5fe894e12d8ea21cb2c8d0fed1d759a4073d631bceea3fac4c19b0e22ac20a +size 32872 diff --git a/marked/M/T-REC-M.3706-201311-I_PDF-E/raw.md b/marked/M/T-REC-M.3706-201311-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..874969767cf3875674a8a1d7abefe35a555c761e --- /dev/null +++ b/marked/M/T-REC-M.3706-201311-I_PDF-E/raw.md @@ -0,0 +1,1289 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3706** + +(11/2013) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Integrated services digital networks + +--- + +**Common management services – Test +management – Protocol neutral requirements +and analysis** + +Recommendation ITU-T M.3706 + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T M.3706 + +## Common management services – Test management – Protocol neutral requirements and analysis + +## Summary + +Recommendation ITU-T M.3706 provides the requirements and analysis for test management which is one of the common management services. Test management functions are used to assist in various high level management function sets such as fault management or performance management. The purpose of testing is to obtain information about the functionality and performance of the managed network subjected to the test. + +The functional requirements for the test management interface include the management functions for test object controlling, test category, test object state monitoring, test result reporting, etc. + +In the analysis part, the detailed information model supporting the above functions across the management interface is provided. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.3706 | 2013-11-13 | 2 | 11.1002/1000/12045 | + +## Keywords + +Common management service, test management, test management IRP. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2014 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 2 | +| 3.1 Terms defined elsewhere ..... | 2 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Requirements ..... | 2 | +| 6.1 Concepts and background..... | 2 | +| 6.2 Business level requirements ..... | 3 | +| 6.3 Specification-level requirements ..... | 6 | +| 7 Analysis ..... | 12 | +| 7.1 Concepts and background..... | 12 | +| 7.2 Information object classes ..... | 13 | +| 7.3 Interface definition ..... | 19 | +| Bibliography..... | 30 | + + + +# Recommendation ITU-T M.3706 + +## Common management services – Test management – Protocol neutral requirements and analysis + +# 1 Scope + +The purpose of this Recommendation is to define an interface through which a manager can perform test functions on an agent. This document specifies the overall requirements and the analysis for test management and defines the semantics of operations (and their parameters) visible via the management interface. + +This Recommendation provides the protocol neutral model definition for notification. It defines, for the purpose of performing test functions on an agent, the information is observable and controlled by the management system's client and it also specifies the semantics of the interactions used to carry this information. + +This Recommendation does not define the syntax or encoding of the operations and their parameters. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T M.3020] Recommendation ITU-T M.3020 (2009), *Management interface specification methodology*. +- [ITU-T M.3160] Recommendation ITU-T M.3160 (2008), *Generic, protocol-neutral management information model*. +- [ITU-T M.3702] Recommendation ITU-T M.3702 (2010), *Common management services – notification management – Protocol neutral requirement and analysis*. +- [ITU-T X.680] Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, *Information technology – Abstract syntax Notation One (ASN.1): Specification of basic notation*. +- [ITU-T X.737] Recommendation ITU-T X.737 (1995) | ISO/IEC 10040:1998, *Information technology – Open Systems Interconnection – Systems Management: Confidence and diagnostic test categories*. +- [ITU-T X.745] Recommendation ITU-T X.745 (1993) | ISO/IEC 10164-12:1994, *Information technology – Open Systems Interconnection – Systems Management: Test management function*. + +# **3 Definitions** + +## **3.1 Terms defined elsewhere** + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 agent [ITU-T M.3020]** +- 3.1.2 information object class [ITU-T M.3020]** +- 3.1.3 manager [ITU-T M.3020]** +- 3.1.4 test category [ITU-T X.745]** +- 3.1.5 test conductor [ITU-T X.745]** +- 3.1.6 test object [ITU-T X.745]** +- 3.1.7 managed object referring to test [ITU-T X.745]** + +## **3.2 Terms defined in this Recommendation** + +This Recommendation has no new terms or definitions. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|----------------------------------| +| EMS | Element Management System | +| FS | Function Set | +| ID | Identifier | +| IOC | Information Object Class | +| IRP | Integration Reference Point | +| MORT | Managed Object Referring to Test | +| NE | Network Element | +| NMS | Network Management System | +| OS | Operating System | +| TO | Test Object | + +# **5 Conventions** + +This Recommendation follows the conventions defined in [ITU-T M.3020]. + +In this Recommendation, Test management IRP is an interface in an agent providing test management functions. + +# **6 Requirements** + +## **6.1 Concepts and background** + +The test management function is used to assist in various high level management function sets such as fault management or performance management. The purpose of testing is to obtain information about the functionality and performance of the managed network subjected to the test. + +Testing is an activity that involves the operator, the managing system (operating system (OS)) and the managed system (network element (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. + +Based on the descriptions in [ITU-T X.737], there are eight test categories: Connection test, Connectivity test, Data integrity test, Loopback test, Protocol integrity test, Resource boundary test, Resource self-test and Test infrastructure test. This Recommendation reuses the above test categories and provides a test category extension mechanism. + +In the 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 NMS-EMS in order to allow the NMS operator to perform tests on network resources. This capability is especially important at times when only the NMS but not the EMS is attended, which might be the case at night or during weekends. + +In the context of fault management the NMS operator may use the testing capabilities over the NMS-EMS interface 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 test management IRP bases its design on work referenced in [ITU-T X.745]. + +## **6.2 Business level requirements** + +### **6.2.1 Requirements** + +The test management requirements can be grouped into one of the following categories: + +- General, i.e., the test management requirements for general purposes, e.g., test identification, test result header format, etc. +- Test object management, e.g., initiate test object, terminate test object, subscribe test object, resume test object, query test object information. +- Test category, e.g., query or specify test types. +- Test result reporting, e.g., report test results. + +#### **6.2.1.1 General** + +The following requirements apply for general purposes. + +REQ-TM-FUN-01 An agent shall provide a mechanism for managers to perform test functions on managed networks. + +REQ-TM-FUN-02 An agent shall provide a mechanism to identify each test object initiated by a manager. + +- REQ-TM-FUN-03 It is required that all test results generated by agents support the same header format that contains enough information to identify the test category, the managed entities that are tested and the time stamp at which the test result is generated. + +#### 6.2.1.2 Test object management + +The following requirements apply to the test management interface. + +- REQ-TM-FUN-04 A manager shall be able to initiate a test object to be performed in an agent. +- REQ-TM-FUN-05 A manager shall be able to query the detailed information of a specified test object in an agent. +- REQ-TM-FUN-06 A manager shall be able to suspend the execution of a specified test object in an agent. +- REQ-TM-FUN-07 A manager shall be able to resume the execution of a suspended test object in agent. +- REQ-TM-FUN-08 A manager shall be able to terminate a specified test object in an agent. +- REQ-TM-FUN-09 The agent shall provide managers with the capability to monitor the states of a test object. The test state may assume one of the following values: not initialised, idle, initialising, testing, terminating or 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 X.745]. Any state change shall be reported to the manager using notifications. + +#### 6.2.1.3 Test category discovery + +The following requirements apply for test category discovery. + +- REQ-TM-FUN-10 An agent shall provide managers with the capability to discover the test categories (types) supported by the agent. The possible test categories include but are not limited to: Connection test, Connectivity test, Data integrity test, Loopback test, Protocol integrity test, Resource boundary test, Resource self-test and Test infrastructure test. These test categories are defined in [ITU-T X.737]. When there are new test categories to be used in the test management interface, an agent should provide means for a manager to discover the new test categories. + +#### 6.2.1.4 Test result management + +The following requirements apply for test result management. + +- REQ-TM-FUN-11 When predefined trigger events occur, the test result of the test object should be generated and stored in an agent. The test results shall be made available to the manager by one or more notifications. The notifications may contain either the test results themselves or the information of data files which store the test result in the case of a large amount of data. The triggering events depend on the test category and shall be defined in the behaviour of the test object. +- REQ-TM-FUN-12 A manager shall be able to specify the destination to which test results should be forwarded by an agent. + +- REQ-TM-FUN-13 A manager shall be able to request a list of available files related to a specified test object. +- REQ-TM-FUN-14 A manager shall be able to manage the transfer of data files contained the test result. + +The above requirements are documented in the subsequent use cases. + +### **6.2.2 Actor roles** + +The capabilities described in this document are available and relevant to all agents and managers. + +### **6.2.3 Telecommunication resources** + +The test management functionality is applicable to all types of telecommunication resources. + +### **6.2.4 High-level use case diagrams** + +The first overview use case diagram in Figure 6-1 shows the overall interaction of the notification management interface. + +![Use case diagram of the test management function set – overview. It shows a Manager actor connected to a 'Test management FS' use case, which includes 'Test job management FS', 'Get test categories', and 'Test result management FS'. Reference M.3706(13)_F6-1.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +``` + + graph LR + Manager((Manager)) --> TMFS(Test management FS) + TMFS -->|<>| TJMFS(Test job management FS) + TMFS -->|<>| GTC(Get test categories) + TMFS -->|<>| TRMFS(Test result management FS) + +``` + +M.3706(13)\_F6-1 + +Use case diagram of the test management function set – overview. It shows a Manager actor connected to a 'Test management FS' use case, which includes 'Test job management FS', 'Get test categories', and 'Test result management FS'. Reference M.3706(13)\_F6-1. + +**Figure 6-1 – Use case diagram of the test management function set – overview** + +![Use case diagram of the test object management function set. It shows a Manager actor connected to a 'Test job management FS' use case, which includes 'Initiate test job', 'Suspend test job', 'Resume test job', 'Terminate test job', 'Query test job information', and 'Test job state monitoring'. Reference M.3706(13)_F6-2.](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +``` + + graph TD + Manager((Manager)) --> TJMFS(Test job management FS) + TJMFS -->|<>| ITJ(Initiate test job) + TJMFS -->|<>| STJ(Suspend test job) + TJMFS -->|<>| RTJ(Resume test job) + TJMFS -->|<>| TTJ(Terminate test job) + TJMFS -->|<>| QTJ(QQuery test job information) + TJMFS -->|<>| TJM(Test job state monitoring) + +``` + +M.3706(13)\_F6-2 + +Use case diagram of the test object management function set. It shows a Manager actor connected to a 'Test job management FS' use case, which includes 'Initiate test job', 'Suspend test job', 'Resume test job', 'Terminate test job', 'Query test job information', and 'Test job state monitoring'. Reference M.3706(13)\_F6-2. + +**Figure 6-2 – Use case diagram of the test object management function set** + +![Use case diagram of the test result management function set. The diagram shows an actor 'Manager' connected to a central use case 'Test result management FS'. This central use case includes four other use cases via '<>' relationships: 'Test result reporting', 'Manage test report destination', 'List test result files', and 'Transfer of data files'. The reference 'M.3706(13)_F6-3' is noted below the 'Transfer of data files' use case.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph LR + Manager((Manager)) --> TRMFS((Test result management FS)) + TRMFS -->|<>| TRR((Test result reporting)) + TRMFS -->|<>| MTD((Manage test report destination)) + TRMFS -->|<>| LRF((List test result files)) + TRMFS -->|<>| TDF((Transfer of data files)) + M.3706(13)_F6-3 + +``` + +Use case diagram of the test result management function set. The diagram shows an actor 'Manager' connected to a central use case 'Test result management FS'. This central use case includes four other use cases via '<>' relationships: 'Test result reporting', 'Manage test report destination', 'List test result files', and 'Transfer of data files'. The reference 'M.3706(13)\_F6-3' is noted below the 'Transfer of data files' use case. + +**Figure 6-3 – Use case diagram of the test result management function set** + +## **6.3 Specification-level requirements** + +### **6.3.1 Requirements** + +There are no specification level requirements. + +### **6.3.2 Actor roles** + +See clause 6.2.2. + +### **6.3.3 Telecommunications resources** + +See clause 6.2.3. + +### **6.3.4 Use cases** + +The general exceptions (e.g., communication error, processing error) related to all uses cases will not be described in the following uses cases and will only be handled in design phases. + +#### **6.3.4.1 Initiate test object** + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to initiate a test object through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the agent and the manager is available. | | +| Pre-conditions | – | | +| Begins when | The manager sends a request to the agent to initiate a test object on one or more managed entity instances. | | +| Step 1 | The manager sends a request to the agent to start a test object. The test request may contain:
  • – the ID or criteria for the managed entities (network resources) to be tested,
  • – the test category to be performed,
  • – the test parameters to be performed on the managed entities (optional),
  • – the start time of the test task (optional),
  • – the stop time of the test task (optional).
| | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Step 2.1 | If the test object is initiated successfully, the unique test object ID will be returned to the manager, and the agent will start the execution of the test object on the specified network resources according to the parameters of the request.
Test result will be generated and are stored in files, and on each reporting interval, the test result information will be reported to the manager. | | +| Step 2.2 | Otherwise, it will return error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | Invalid parameter | | +| Post-conditions | A test object is initiated on request, and it starts to perform test execution based on the specified request parameters. The agent may send an object creation notification to the manager. | | +| Traceability | REQ-TM-FUN-01, REQ-TM-FUN-02, REQ-TM-FUN-04 | | + +#### 6.3.4.2 Suspend test object + +| Use case stage | Evolution/Specification | <>
Related use | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to suspend a test object through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resources | All types of telecommunication resources. | | +| Assumptions | The communication between the agent and the manager is available. | | +| Pre-conditions | The specified test object exists in the agent and it is not suspended. | | +| Begins when | The manager sends a request to suspend a test object. | | +| Step 1 | The manager sends a request to the agent to suspend a test measurement job. The request parameter is the identifier of the test object. | | +| Step 2.1 | If the operation succeeds, the test object will no longer perform any test actions until resumed. | | +| Step 2.2 | If the operation fails, it will return error information to the manager. | | +| Ends when | A success response or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – unknown test object;
– Test object already suspended. | | +| Post-conditions | The specified test object is suspended on request. The agent may send a state change notification to the manager. | | +| Traceability | REQ-TM-FUN-06 | | + +#### 6.3.4.3 Resume test object + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to resume a suspended test object through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified test object exists in the agent and it is suspended. | | +| Begins when | The manager sends a request to resume a test object. | | +| Step 1 | The manager sends a request to the agent to resume a test object. The request parameter is the identifier of the test object. | | +| Step 2.1 | If the operation succeeds, the test object will continue performing the test actions. | | +| Step 2.2 | If the operation fails, it will return error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions |
  • – unknown test object;
  • – test object not suspended.
| | +| Post conditions | The specified test object is resumed on request, and it continues to perform the test actions. The agent may send a state change notification to the manager. | | +| Traceability | REQ-PM-FUN-07 | | + +#### 6.3.4.4 Terminate test object + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to terminate a test object through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified test object exists in the agent and it is suspended. | | +| Begins when | The manager sends a request to terminate a test object. | | +| Step 1 | The manager sends a request to the agent to terminate a test object. The request parameter is the identifier of the test object. | | +| Step 2.1 | If the operation succeeds, the specified test object will stop working and the related testing resources, including the test result, will be released, and the agent will return success information. | | +| Step 2.2 | Otherwise, it will return error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Exceptions |
  • – unknown test object;
  • – test object not suspended.
| | +| Post conditions | The specified test object is terminated on request. The agent may send an object deletion notification to the manager. | | +| Traceability | REQ-PM-FUN-09 | | + +#### 6.3.4.5 Query test object information + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to query the parameter values of a test object through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified test object exists in the agent. | | +| Begins when | The manager sends a request to query the information of a test object. | | +| Step 1 |

The manager sends a request to the agent to query the parameters of a test object. The request parameter is the identifier of the test object. The following parameters can be queried:

  • – the ID or criteria for the managed entities (network resources) to be tested,
  • – the test category to be performed,
  • – the test parameters to be performed on the managed entities,
  • – the start time of the test object,
  • – the stop time of the test object,
  • – the report interval of the test object,
  • – the schedule of the test object, etc.
| | +| Step 2.1 | If the operation succeeds, the agent will return the attribute information of the test object. | | +| Step 2.2 | If the operation fails, it will return error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | Unknown test object. | | +| Post conditions | The corresponding attribute information is returned by the agent as requested. | | +| Traceability | REQ-PM-FUN-09 | | + +#### 6.3.4.6 Test object state monitoring + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can monitor the state of a test object. The state change of a test object should be reported to the test manager. | | +| Actor and roles | The manager receives notifications from the agent. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available, the manager already subscribed notifications from the agent. | | +| Preconditions | – | | +| Begins when | The state of a test object is changed. | | +| Step 1 | The agent sends a notification to the manager, indicating the state change of the test object. The notification includes the following parameters:
– the identifier of the test object,
– the new value of the test object state attribute, which can be one of the following: Not initialized, Idle, Initializing, Suspended, Testing, Terminating, Disabled. The meaning of the above states can be found in [ITU-T X.745],
– the timestamp indicating when the state change occurred. | | +| Ends when | The notification is sent to the manager or an exception occurred. | | +| Exceptions | Unknown test object. | | +| Post conditions | The state change notification is received by the manager. | | +| Traceability | REQ-PM-FUN-09 | | + +#### 6.3.4.8 Query test categories + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to query the supported test categories for a managed entity (MORT). | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified test object exists in the agent and it is suspended. | | +| Begins when | The manager sends a request to delete a measurement job. | | +| Step 1 | The manager sends a request to the agent to terminate a test object. The request parameter is the identifier of the test object. | | +| Step 2.1 | If the operation succeeds, the specified test object will stop working and the related testing resources, including the test result, will be released, and the agent will return success information. | | +| Step 2.2 | Otherwise, it will return error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – unknown test object;
– test object not suspended. | | +| Post conditions | The specified test object is terminated on request. The agent may send an object deletion notification to the manager. | | +| Traceability | REQ-PM-FUN-10 | | + +#### 6.3.4.9 Test result reporting + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | For controlled tests, the results may be emitted as notifications (unsolicited) from the test object to the manager. | | +| Actor and roles | The manager receives notifications from the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available, the manager already subscribed notifications from the agent. | | +| Preconditions | – | | +| Begins when | The result of a test object becomes ready. | | +| Step 1 | The agent sends one or more notifications containing the test results to the manager. The notification includes the following parameters:
  • – the test invocation identifier,
  • – the test outcome,
  • – any other information related to this TO.
| | +| Ends when | The notification(s) is sent to the manager or an exception occurred. | | +| Exceptions | – | | +| Post conditions | The test result notification is received by the manager. | | +| Traceability | REQ-PM-FUN-11 | | + +#### 6.3.4.10 Manage test result destination + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to manage the destinations where the test results should be sent through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified test performer exists in the agent. | | +| Begins when | The manager sends a request to modify destinations of test results. | | +| Step 1 | The manager sends a request to the agent to modify the destinations of test result to be sent. The request parameter is the following:
  • – identifier of the test action performer,
  • – the destination(s) to be operated,
  • – the operation type, which can be: ADD, REMOVE, REPLACE.
| | +| Step 2.1 | If the operation succeeds, it will return successful information, the modified result destination(s) will be recorded in the agent, and the test result will be forwarded to the new destination when ready. | | +| Step 2.2 | Otherwise, it will return error information to the manager. | | +| Ends when | Response or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | – unknown test performer;
– invalid destinations. | | + +| Use case stage | Evolution/Specification | <>
Related use | +|-----------------|------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Post conditions | The new destination(s) are setup on request. The test performer will forward the test results to the new destinations. | | +| Traceability | REQ-TM-FUN-12 | | + +#### 6.3.4.11 Query test results + +| Use case stage | Evolution/Specification | <>
Related use | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Goal | The manager can request the agent to query the test results of one or more test object(s) through the management interface. | | +| Actor and roles | The manager invokes an operation on the agent. | | +| Telecom resource | All types of telecommunication resources. | | +| Assumptions | The communication between the manager and the agent is available. | | +| Preconditions | The specified test objects exist in the agent. | | +| Begins when | The manager sends a request to query the test result of one or more test objects. | | +| Step 1 | The manager sends a request to the agent to query the test results of test objects. The request parameter is the identifiers of the test object. | | +| Step 2.1 | If the operation succeeds, the agent will return the test results information of the specified test objects. The output parameters contain a list of the following:
  • – the identifier of a test object,
  • – the test outcome of the test object,
  • – other information related to the test object.
| | +| Step 2.2 | If the operation fails, it will return error information to the manager. | | +| Ends when | Requested information or an exception is returned to the manager, or the operation is cancelled by the manager. | | +| Exceptions | Unknown test objects. | | +| Post conditions | The corresponding test results information is returned by the agent as requested. | | +| Traceability | REQ-TM-FUN-13, REQ-TM-FUN-14 | | + +# 7 Analysis + +## 7.1 Concepts and background + +The system contexts for test management service are shown in Figure 7-1. + +![Figure 7-1 – System context for test management service. The diagram shows a 'Manager' box inside a dashed box labeled 'Managing system'. An arrow points from the 'Manager' box to a central vertical dashed line labeled 'Test management interface'. From this interface, an arrow points to an 'Agent' box inside a dashed box labeled 'Managed system'. The 'Agent' box is connected to a 'Resources' box. Below the 'Managed system' box, there is a 'Notification management service' box. A label 'M.3706(13)_F7-1' is in the bottom right corner.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Figure 7-1 – System context for test management service. The diagram shows a 'Manager' box inside a dashed box labeled 'Managing system'. An arrow points from the 'Manager' box to a central vertical dashed line labeled 'Test management interface'. From this interface, an arrow points to an 'Agent' box inside a dashed box labeled 'Managed system'. The 'Agent' box is connected to a 'Resources' box. Below the 'Managed system' box, there is a 'Notification management service' box. A label 'M.3706(13)\_F7-1' is in the bottom right corner. + +Figure 7-1 – System context for test management service + +## 7.2 Information object classes + +### 7.2.1 Information entities imported and local label + +| Label reference | Local label | +|-----------------------------------------------------------|-----------------| +| [ITU-T M.3702], information object class, NotificationIRP | NotificationIRP | +| [ITU-T M.3160], information object class, Top | Top | +| [ITU-T M.3160], information object class, Network | Network | + +### 7.2.2 Class diagram + +This clause introduces the set of IOCs that encapsulate information within the agent. The intent is to identify the information required for the test management 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. + +#### 7.2.2.1 Attributes and relationships + +Figure 7-2 shows the class containment relationships of the performance management related information object classes. + +![Containment diagram of test management IOCs](12de9b926df0384ec07702671827c9cd_img.jpg) + +The diagram illustrates the containment hierarchy of information object classes. At the top is a box labeled '<> Network (ITU-T M.3160)'. A solid line with a diamond at the top box connects it to three boxes below: '<> TestManagementIRP', '<> TestActionPerformer', and '<> TestObject \*'. A dashed line extends from the 'TestObject \*' box to a note box containing the text '\* Include all its child classes'. The diagram is labeled 'M.3706(13)\_F7-2' at the bottom right. + +Containment diagram of test management IOCs + +Figure 7-2 – Containment diagram of test management IOCs + +Figure 7-3 shows the detailed class diagram of the information object class TestManagementIRP, TestActionPerformer, TestObject and its child classes, and the association relationships among them and the managed entities which are to be tested (MORTs). + +![UML class diagram showing relationships between TestActionPerformer, TestObject, and MORT classes. TestActionPerformer (1) has a 0..* association with TestObject. TestObject (1) has a 1..2 association with MORT. Callouts indicate that TestObject includes all its child classes and MORT represents managed entities to be tested.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +classDiagram + class TestActionPerformer { + <> + } + class TestObject { + <> + * + } + class MORT { + <> + ** + } + TestActionPerformer "1" -- "0..*" TestObject + TestObject "1" -- "1..2" MORT + note for TestObject "* Include all its child classes" + note for MORT "** Represents the managed entities to be tested" + +``` + +M.3706(13)\_F7-3 + +UML class diagram showing relationships between TestActionPerformer, TestObject, and MORT classes. TestActionPerformer (1) has a 0..\* association with TestObject. TestObject (1) has a 1..2 association with MORT. Callouts indicate that TestObject includes all its child classes and MORT represents managed entities to be tested. + +**Figure 7-3 – Test measurement information object classes** + +#### 7.2.2.2 Inheritance + +Figure 7-4 is the inheritance diagram of test management IOCs. + +![UML inheritance diagram showing TOP (ITU-T M.3160) as the root class for TestActionPerformer, TestObject, and TestManagementIRP. TestObject further inherits from ConnectionTestObject, DataIntegrityTestObject, ProtocolIntegrityTestObject, and ResourceSelfTestObject. These four classes further inherit from ConnectivityTestObject, LoopbackTestObject, ResourceBoundaryTestObject, and TestIntrastructureTestObject.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +classDiagram + class TOP { + <> + TOP (ITU-T M.3160) + } + class TestActionPerformer { + <> + } + class TestObject { + <> + } + class TestManagementIRP { + <> + } + class ConnectionTestObject { + <> + } + class DataIntegrityTestObject { + <> + } + class ProtocolIntegrityTestObject { + <> + } + class ResourceSelfTestObject { + <> + } + class ConnectivityTestObject { + <> + } + class LoopbackTestObject { + <> + } + class ResourceBoundaryTestObject { + <> + } + class TestIntrastructureTestObject { + <> + } + TOP <|-- TestActionPerformer + TOP <|-- TestObject + TOP <|-- TestManagementIRP + TestObject <|-- ConnectionTestObject + TestObject <|-- DataIntegrityTestObject + TestObject <|-- ProtocolIntegrityTestObject + TestObject <|-- ResourceSelfTestObject + ConnectionTestObject <|-- ConnectivityTestObject + DataIntegrityTestObject <|-- LoopbackTestObject + ProtocolIntegrityTestObject <|-- ResourceBoundaryTestObject + ResourceSelfTestObject <|-- TestIntrastructureTestObject + +``` + +M.3706(13)\_F7-4 + +UML inheritance diagram showing TOP (ITU-T M.3160) as the root class for TestActionPerformer, TestObject, and TestManagementIRP. TestObject further inherits from ConnectionTestObject, DataIntegrityTestObject, ProtocolIntegrityTestObject, and ResourceSelfTestObject. These four classes further inherit from ConnectivityTestObject, LoopbackTestObject, ResourceBoundaryTestObject, and TestIntrastructureTestObject. + +**Figure 7-4 – Test management IOCs inheritance** + +### 7.2.3 Information object class definitions + +| Class name | Qualifier | Requirement IDs | +|---------------------|-----------|------------------------------------------------------------------------------------------------------------------------| +| TestManagementIRP | M | REQ-TM-FUN-01 | +| TestActionPerformer | M | REQ-TM-FUN-01, REQ-TM-FUN-04, REQ-TM-FUN-05, REQ-TM-FUN-06, REQ-TM-FUN-07, REQ-TM-FUN-08, REQ-TM-FUN-09, REQ-TM-FUN-10 | +| TestObject | M | REQ-TM-FUN-01, REQ-TM-FUN-02, REQ-TM-FUN-03, REQ-TM-FUN-11, REQ-TM-FUN-12, REQ-TM-FUN-13 | +| MORT | O | REQ-TM-FUN-01 | + +#### 7.2.3.1 Information Object Class *TestManagementIRP* + +##### 7.2.3.1.1 Definition + +The IOC *TestManagementIRP* together with the IOC *TestActionPerformer* represent the test management capabilities defined by this Recommendation. To conduct a test of network resources, this object may require capabilities of other objects such as *TestObject*. The IOC *TestManagementIRP* inherits from the IOC *TOP* from [ITU-T M.3160]. + +##### 7.2.3.1.1 Attributes + +The IOC *TestManagementIRP* has no attributes specific to itself, only those inherited from the IOC *TOP*. + +#### 7.2.3.2 Information object class *TestActionPerformer* + +##### 7.2.3.2.1 Definition + +The IOC *TestActionPerformer* provides the ability to receive and react upon test requests. This class must also be able to instantiate and delete tester objects or, in the case where the tester objects are permanently instantiated, to allocate and reserve them for their usage. This Recommendation does not require this IOC to be instantiated. It may be abstract and used for inheritance purposes only. In this way the ability to receive and react upon test requests may be included in any other IOC. + +##### 7.2.3.2.1 Attributes + +| Attribute name | Visibility | Support Qualifier | Read Qualifier | Write Qualifier | +|-----------------------|------------|-------------------|----------------|-----------------| +| supportedTOClasses | + | M | M | – | +| testActionPerformerId | + | CM (Note) | M | – | +| associatedTOList | + | M | M | – | + +NOTE – This attribute is only mandatory in the case where the IOC *TestActionPerformer* is instantiated. In the case where this IOC is an abstract class and used for inheritance purposes only the attribute shall be omitted. + +#### 7.2.3.3 Information object class *TestObject* + +##### 7.2.3.3.1 Definition + +The IOC *TestObject* monitors and controls the testing of a *MORT* instance and reports the outcome of the test execution. Tester Objects (TOs) are instantiated by the IOC *TestActionPerformer* in response to a valid test initiation request (*initiateTests*). They are deleted after termination of the test. It is also possible that TOs are permanently instantiated. In this case they are allocated to a certain *TestActionPerformer* during the test execution. After termination of the test they are released. + +The IOC *TestObject* defines a generic TO. It shall be used as an abstract class from which more specific tester objects shall be derived by specialisation for each test category. Test categories and the associated test category specific TOs are defined in [ITU-T X.737]. The generic TO defines attributes pertaining to a test and required for all test categories. + +Each test invocation shall have only one associated TO. + +Only test category specific TOs shall be instantiated. + +For simplicity this Recommendation will often use only the term TO. In this case either the test category specific TO is referred to depending on which is actually instantiated. + +##### 7.2.3.3.2 Attributes + +| Attribute name | Visibility | Support Qualifier | Read Qualifier | Write Qualifier | +|-------------------------|------------|-------------------|----------------|-----------------| +| testOutcome | + | M | M | – | +| testState | + | M | M | – | +| testInvocationInitiator | – | C | M | – | +| additionalInformation | – | O | – | – | +| proposedRepairActions | – | O | – | – | +| fileReference | – | CM (Note 1) | – | – | +| fileExpiryDate | – | CM (Note 1) | – | – | +| testObjectId | + | CM (Note 2) | M | – | +| mortList | + | M | M | – | + +NOTE 1 – In the case where the TO does support capturing test results in a file this parameter shall be present and contain information. In the case where the TO does not support capturing test results in a file this parameter shall contain no information or shall be absent. +NOTE 2 – This attribute exists only when the IOC is instantiated, and it does not exist for an abstract Class. + +#### 7.2.3.4 Information object class *ResourceSelfTestObject* + +##### 7.2.3.4.1 Definition + +The IOC *ResourceSelfTestObject* is a specialised TO for the resource self-test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### 7.2.3.4.2 Attributes + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### 7.2.3.5 Information object class *ConnectivityTestObject* + +##### 7.2.3.5.1 Definition + +The IOC *ConnectivityTestObject* is a specialised TO for the connectivity test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### 7.2.3.5.2 Attributes + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### 7.2.3.6 Information object class *ConnectionTestObject* + +##### 7.2.3.6.1 Definition + +The IOC *ConnectionTestObject* is a specialised TO for the connection test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### 7.2.3.6.2 Attributes + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### 7.2.3.7 Information object class *LoopbackTestObject* + +##### 7.2.3.7.1 Definition + +The IOC *LoopbackTestObject* is a specialised TO for the loopback test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### 7.2.3.7.2 Attributes + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### **7.2.3.8 Information object class DataIntegrityTestObject** + +##### **7.2.3.8.1 Definition** + +The IOC *DataIntegrityTestObject* is a specialised TO for the data integrity test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### **7.2.3.8.2 Attributes** + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### **7.2.3.9 Information object class ResourceBoundaryTestObject** + +##### **7.2.3.9.1 Definition** + +The IOC *ResourceBoundaryTestObject* is a specialised TO for the resource boundary test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### **7.2.3.9.2 Attributes** + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### **7.2.3.10 Information object class ProtocolIntegrityTestObject** + +##### **7.2.3.10.1 Definition** + +The IOC *ProtocolIntegrityTestObject* is a specialised TO for the protocol integrity test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### **7.2.3.10.2 Attributes** + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### **7.2.3.11 Information object class TestInfrastructureTestObject** + +##### **7.2.3.11.1 Definition** + +The IOC *TestInfrastructureTestObject* is a specialised TO for the test infrastructure test integrity test. It inherits from the abstract IOC *TestObject*. It specifies the triggering events for the emission of the test result notifications. + +##### **7.2.3.11.2 Attributes** + +This IOC has no attributes specific to itself, only those inherited from the generic IOC *TestObject*. + +#### **7.2.3.12 Proxy Class *MORT*** + +##### **7.2.3.12.1 Definition** + +The ProxyClass *MORT* represents a network resource that is under test. Its class definition shall be one defined in the various Network Resource Model specifications. + +##### **7.2.3.12.2 Attributes** + +This IOC has no attributes. + +### 7.2.4 Information relationships definition + +#### 7.2.4.1 Relationship between *TestActionPerformer* and *TestObject* + +##### 7.2.4.1.1 Definition + +This relationship defines a binary association between the IOC *TestActionPerformer* and the IOC *TestObject*. The association is navigable from the *TestActionPerformer* to the *TestObject*. + +##### 7.2.4.1.2 Roles + +| Name | Definition | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| associatedTOList | This rolename provides a name allowing to navigate from an instance of TestActionPerformer to the associated instances of TestObject . If tap is an instance of TestActionPerformer , the expression tap.associatedTOList indicates the set of object instances of subclasses of TestObject . | + +#### 7.2.4.2 Relationship between *TestObject* and *MORT* + +##### 7.2.4.2.1 Definition + +This relationship defines a binary association between the IOC *TestObject* and the Proxy Class *MORT*. + +The association is navigable from the *TestObject* to the *MORT*. + +##### 7.2.4.2.2 Roles + +| Name | Definition | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mortList | This rolename provides a name allowing to navigate from an instance of subclasses of TestObject to the associated instances of MORT . If to is an instance of TestObject , the expression to.mortList indicates an object instance of MORT . | + +### 7.2.5 Information attributes definition + +#### 7.2.5.1 Definition and legal Values + +| Attribute name | Definition | Information type/Legal values | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| testState | This attribute reflects the actual test state ([ITU-T X.745]). | ENUM {notInitialized, idle, initializing, testing, terminating, disabled} | +| testOutcome | This attribute provides information about the test result, as perceived by the associated TO, in a standardised manner.
The information in this parameter is only valid after termination of the test activity.
This information shall be present in the last test result notification emitted by a TO prior to its deletion. | ENUM {pass, fail, inconclusive, timed-out, premature-termination}
Pass indicates that the test exercise of the test invocation has executed correctly and has found no problem.
Fail indicates that the test exercise of the test invocation has executed correctly and has found one or more problems.
Inconclusive indicates that the TO has not determined if the execution is Pass or Fail.
Timed-out indicates that the TO has terminated its execution because of the expiry of the timer (i.e., the current time – TestSession.sessionStartTime >= TestObject.timeOut).
Premature termination indicates that the TO has (a) never started execution or (b) terminated its execution prematurely, either by TestManagementRP and its associated objects internal problems or in response to a terminateTests operation. | + +| Attribute name | Definition | Information type/Legal values | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| supportedTOClasses | This attribute identifies the TO classes that are supported by a certain managed object instance whose class has inherited from TestActionPerformer or whose class is the TestActionPerformer . | SET OF TO String | +| testActionPerformerId | This attribute unambiguously identifies an instance of a TestActionPerformer . | String | +| TestObjectId | This attribute unambiguously identifies an instance of a TestObject . | String | +| testInvocationInitiator | It identifies the IRPManager. | String | +| additionalInformation | This attribute holds a set of additional information pertaining to the test. | String | +| proposedRepairActions | This attribute suggests one or more repair actions if the reason for a failure is known. | SET of String | +| actualStartTime | This attribute specifies the time at which the TO will enter or has entered the test state testing . Before the TO enters the testing state this is an estimated time. After entering the testing state this is the actual time. Note that this is not the time of the invocation of the operation initiateTests . | All values indicating a valid time. | +| actualStopTime | This attribute specifies the time at which the TO will leave or has left the test state testing . Before the TO leaves the testing state this is an estimated time. After leaving the testing state this is the actual time. Note that this is not the time of the invocation of the operation terminateTests . | All values indicating a valid time later than the actualStartTime . | +| maxTestingPhaseDuration | This attribute specifies the maximum amount of time that a TO may spend in the testing state. | All values indicating a valid amount of time. | +| fileReference | This attribute carries the reference to a file that contains the test result data set. | String | +| fileExpiryDate | This attribute carries the date and time after which the file, whose reference is carried by the fileReference attribute, may be removed. | GeneralizedTime
All values indicating a valid time. | +| testSourceAddress | This attribute provides the source address of the test. | An IP address indicating source. | +| testDestinationAddress | This attribute provides the destination address of the test. | An IP address indicating destination.
In a loopback test, it should be NULL. | +| testLoopbackAddress | This attribute provides the loopback address in a loopback test. | An IP address indicating loopback point in a loopback test.
In connection test, it should be NULL. | +| mortList | This attribute provides DN List of the MORT object instances. | SET of DN | +| associatedTOList | This attribute provides DN List of the TO instances that are associated with this TestActionPerformer . | SET of DN | + +#### 7.2.5.2 Constraints + +None. + +## 7.3 Interface definition + +### 7.3.1 Class diagram representing interfaces + +The following diagram depicts the interfaces of the test management IRP with their corresponding operations and notifications. + +![UML diagram showing the relationships between TestManagementIRPControlOperations, TestManagementIRPMonitorOperations, TestManagementIRPNotifications, TestActionPerformer, and TestObject.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +``` + +classDiagram + class TestManagementIRPControlOperations { + <> + +initiateTests() + +terminateTests() + } + class TestManagementIRPMonitorOperations { + <> + +monitorTest() + } + class TestManagementIRPNotifications { + <> + +notifyTestResults() + } + class TestActionPerformer { + <> + } + class TestObject { + <> + } + TestManagementIRPControlOperations ..|> TestActionPerformer + TestManagementIRPMonitorOperations ..|> TestActionPerformer + TestManagementIRPNotifications --|> TestObject : <> + +``` + +UML diagram showing the relationships between TestManagementIRPControlOperations, TestManagementIRPMonitorOperations, TestManagementIRPNotifications, TestActionPerformer, and TestObject. + +M.3706(13)\_F7-5 + +**Figure 7-5 – Operations and notifications of TestManagementIRP** + +### 7.3.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 regard 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 the operation cannot be completed. The exception has the same entry and exit state. + +### 7.3.3 Interface **testManagementIRPControlOperations** + +The interface **TestManagementIRPControlOperations** contains the operations *initiateTests*, *terminateTests*, *suspendTest*, and *resumeTest*. It must be implemented by every object with the ability to receive and react upon test requests, for example by every instance of **TestActionPerformer**. + +#### 7.3.3.1 Operation **initiateTests** (M) + +##### 7.3.3.1.1 Definition + +The IRPManager uses this operation to request the IRPAgent to initiate controlled tests. A single test request may initiate multiple (one or more) tests. + +For each test to be initiated the managed object representing the network resource to be tested and the tester object class must be specified. + +The initiated tests are independent and not related to each other. This implies that independent test result notifications are sent for each of the tests initiated by a single *initiateTests* operation. + +##### 7.3.3.1.2 Input parameters + +| Parameter name | Qualifier | Information type/
Legal values | Comment | +|-------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| testInvocationInitiator | C | TestObject. testInvocationInitiator | This parameter identifies the IRPManager. | +| testsToBeInitiated | M | SET OF SET {
maxTestingStateDuration (O)
toBeTestedMORT (O)
TestObjectClass (M)
TestObjectName (O)
TestObjectInitialAttributeList (O)
} | This sequence specifies the tests to be initiated. For each test the parameter maxTestingStateDuration specifies the timeout period of the tests to be initiated. One value shall indicate "No limit". toBeTestedMORT specifies the instance of the MORT to be tested. If the parameter is absent, the MORT is identical to the object instance to which the subject operation is directed to. The parameter TestObjectClass specifies the class of the associated tester object. Optionally, a name for the tester object instance may be specified in the parameter TestObjectName . The parameter TestObjectInitialAttributeList carries some or all the values of the attributes of the TO instance responsible for the test. The syntax and semantics of this attribute value is dependent on the specific TO class definition and is outside the scope of ITU. | + +##### 7.3.3.1.3 Output parameters + +| Parameter name | Qualifier | Matching information | Comment | +|----------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| response | M | SEQUENCE OF CHOICE {
testInitiated
testNotInitiated
}

testInitiated = SEQUENCE {
TestInvocation. testInvocationId (M)
TestObjectName (O)
}

testNotInitiated =
failureReason | The number and the order, related to the tests to be initiated, of elements in this sequence and in the set of the input parameter toBeInitiatedTests shall be identical. For a successfully instantiated test the parameter testInitiated returns the test invocation identifier of the test. In the case where the tester object name has not been specified in the request it shall be returned in TestObjectName . For a failed test instantiation the parameter testNotInitiated returns the reason for which the instantiation of the test failed. Failure reasons are TO class does not exist MORT does not exist MORT is not available others. | + +##### 7.3.3.1.4 Pre-condition + +The precondition must hold true before the operation is invoked. The pre-condition depends on the test category. + +For at least one of the specified tests to be instantiated the following must hold true: + +theIndicatedMORTIsExisting **AND** theIndicatedMORTIsAvailable **AND** +theIndicatedTOClassIsExisting + +| Assertion name | Definition | +|-------------------------------|-------------------------------------------------------------------------| +| theIndicatedMORTIsExisting | The MORT indicated by the subject operation for this test exists. | +| theIndicatedMORTIsAvailable | The MORT indicated by the subject operation for this test is available. | +| theIndicatedTOClassIsExisting | The TO class indicated by the subject operation for this test exists. | + +##### 7.3.3.1.5 Post-condition + +The post-condition must hold true after the completion of the operation: + +allIndicatedTOsInstantiated **OR** notAllTestsInitiated **OR** noTestInitiated + +| Assertion name | Definition | +|----------------------|----------------------------------------------------------------------------------------------| +| allTestsInitiated | All tests indicated by the subject operation were initiated successfully. | +| notAllTestsInitiated | Not all but at least one test indicated by the subject operation was initiated successfully. | +| noTestInitiated | No test indicated by the subject operation was initiated successfully. | + +##### 7.3.3.1.6 Exceptions + +| Exception name | Definition | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailedEntirely | Condition: noTestInitiated = TRUE
Returned information: The response parameter is returned
Exit state: Entry state | +| operationFailedPartly | Condition: notAllTestsInitiated = TRUE
Returned information: The response parameter is returned
Exit state: Entry state | + +#### 7.3.3.2 Operation *terminateTests* (M) + +##### 7.3.3.2.1 Definition + +The IRPManager uses this operation to request the IRPAgent to terminate tests during their life time. A single *terminateTests* operation may terminate multiple (one or more) tests. + +The tests to be terminated are identified by their test invocation identifiers. The IRPManager terminating a test may be different from the IRPManager that initiated the test. The *terminateTests* operation must be invoked on the object which received the corresponding *initiateTests* operation. + +##### 7.3.3.2.2 Input parameters + +| Parameter name | Qualifier | Information type | Comment | +|---------------------|-----------|-------------------------------------------|--------------------------------------------------------------| +| testsToBeTerminated | M | SET OF
TestInvocation.testInvocationId | This parameter specifies the tests that shall be terminated. | + +##### 7.3.3.2.3 Output parameters + +| Parameter name | Qualifier | Matching information | Comment | +|----------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| response | M | SEQUENCE OF CHOICE {
testTerminated
testNotTerminated
}
testTerminated =
TestInvocation.testInvocationId
testNotTerminated =
SEQUENCE {
TestInvocation.testInvocationId,
failureReason
} | The number and the order, related to the test invocation identifier, of elements in this sequence and in the set of the input parameter toBeTerminatedTests shall be identical.
It specifies the test invocation ids of the tests, that were successfully terminated, and the ids of the tests, that failed to be terminated successfully together with the reason for the failure.
Failure reasons are test invocation id does not exist, others. | + +##### 7.3.3.2.4 Pre-condition + +The precondition must hold true before the operation is invoked. + +allIndicatedTestInvocationIdsAreExisting **OR** notAllIndicatedTestInvocationIdsAreExisting + +| Assertion name | Definition | +|---------------------------------------------|------------------------------------------------------------------------------------------------| +| allIndicatedTestInvocationIdsAreExisting | All test invocation identifiers specified by the subject operation exist. | +| notAllIndicatedTestInvocationIdsAreExisting | Not all but at least one test invocation identifier specified by the subject operation exists. | + +##### 7.3.3.2.5 Post-condition + +The post-condition must hold true after the completion of the operation. + +allIndicatedTestsTerminated **OR** notAllIndicatedTestsTerminated **OR** noIndicatedTestTerminated + +| Assertion name | Definition | +|--------------------------------|------------------------------------------------------------------------------------------------| +| allIndicatedTestsTerminated | All tests indicated in the subject operation were terminated successfully. | +| notAllIndicatedTestsTerminated | Not all but at least one test indicated in the subject operation aaws terminated successfully. | +| noIndicatedTestTerminated | No test indicated in the subject operation aaws terminated successfully. | + +##### 7.3.3.2.6 Exceptions + +| Exception name | Definition | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailedEntirely | Condition: noIndicatedTestTerminated = TRUE
Returned information: The response parameter is returned
Exit state: Entry state | +| operationFailedPartly | Condition: notAllIndicatedTestInvocationIdsAreExisting = TRUE OR notAllIndicatedTestsTerminated = TRUE
Returned information: The response parameter is returned
Exit state: Entry state | + +#### 7.3.3.2 Operation *suspendTest* (M) + +##### 7.3.3.2.1 Definition + +The IRPManager uses this operation to request the IRPAgent to suspend a test represented by an instance of the derived class of abstract IOC TestObject. + +The test to be suspended is identified by the DN of the test object. The IRPManager suspending a test may be different from the IRPManager that initiated the test. The *suspendTest* operation must be invoked on the object which received the corresponding *initiateTests* operation. + +##### 7.3.3.2.2 Input parameters + +| Parameter name | Qualifier | Information Type | Comment | +|---------------------------|-----------|------------------------------------|-------------------------------------------------------------------| +| testObjectToBeSuspendeded | M | Name (DN of a TestObject instance) | This parameter specifies the Test Object that shall be suspended. | + +##### 7.3.3.2.3 Output parameters + +| Parameter name | Qualifier | Matching Information | Comment | +|------------------|-----------|----------------------|---------------------------------------------------------------------------------------------------| +| successIndicator | M | boolean | The successIndicator indicates whether the suspendTest operation performs successfully or failed. | + +##### 7.3.3.2.4 Pre-condition + +The precondition must hold true before the operation is invoked. + +| Assertion name | Definition | +|---------------------------|-------------------------------------------------------------------------| +| specifiedTestObjectExists | The test object DN specified by the subject operation exists. | +| specifiedTestNotSuspended | The test object DN specified by the subject operation is not suspended. | + +##### 7.3.3.2.5 Post-condition + +The post-condition must hold true after the completion of the operation. + +| Assertion name | Definition | +|------------------------|-------------------------------------------------------------------------| +| specifiedTestSuspended | The test indicated in the subject operation was suspended successfully. | + +##### 7.3.3.2.6 Exceptions + +| Exception name | Definition | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UnknownTestObject | Condition: specifiedTestObjectExists = FALSE
Returned information: The response parameter is returned
Exit state: Entry state | +| SpecifiedTestObjectAlreadySuspended | Condition: specifiedTestObjectSuspended = FALSE
Returned information: The response parameter is returned
Exit state: Entry state | + +#### 7.3.3.3 Operation resumeTest (M) + +##### 7.3.3.3.1 Definition + +The IRPManager uses this operation to request the IRPAgent to resume a suspended test represented by an instance of the derived class of abstract IOC TestObject. + +The test to be terminated is identified by their test invocation identifiers. The IRPManager resuming a test may be different from the IRPManager that initiated the test. The *resumeTest* operation should be invoked on the object which is already suspended. + +##### 7.3.3.3.2 Input parameters + +| Parameter name | Qualifier | Information type | Comment | +|-----------------------|-----------|------------------------------------|-----------------------------------------------------------------| +| testObjectToBeResumed | M | Name (DN of a TestObject instance) | This parameter specifies the test object that shall be resumed. | + +##### 7.3.3.3.3 Output parameters + +| Parameter name | Qualifier | Matching information | Comment | +|------------------|-----------|----------------------|--------------------------------------------------------------------------------------------------| +| successIndicator | M | Boolean | The successIndicator indicates whether the resumeTest operation performs successfully or failed. | + +##### 7.3.3.3.4 Pre-condition + +The precondition must hold true before the operation is invoked. + +| Assertion name | Definition | +|------------------------------|---------------------------------------------------------------------| +| specifiedTestObjectExists | The test object DN specified by the subject operation exists. | +| specifiedTestObjectSuspended | The test object DN specified by the subject operation is suspended. | + +##### 7.3.3.3.5 Post-condition + +The post-condition must hold true after the completion of the operation. + +| Assertion name | Definition | +|----------------------|-----------------------------------------------------------------------| +| specifiedTestResumed | The test indicated in the subject operation was resumed successfully. | + +##### 7.3.3.3.6 Exceptions + +| Exception name | Definition | +|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UnknownTestObject | Condition: specifiedTestObjectExists = FALSE
Returned information: The response parameter is returned
Exit state: Entry state | +| SpecifiedTestObjectAlreadyResumed | Condition: specifiedTestObjectSuspended = FALSE
Returned information: The response parameter is returned
Exit state: Entry state | + +### 7.3.4 Interface TestManagementIRPMonitorOperations + +The interface *TestManagementIRPMonitorOperations* contains the operation *monitorTest*. It has a realisation relationship with the IOC *TestActionPerformer*. + +#### 7.3.4.1 Operation *monitorTest* (M) + +##### 7.3.4.1.1 Definition + +IRPManager shall be able to retrieve information about the test as observed by the TO during the test execution by reading the relevant attributes of the TO associated with the test. Also after the test execution the manager shall be able to read these attributes as long as the TO exists. Attributes conveying information about the test execution are *testState* and *testOutcome*. Depending on the specific test category specific TO other attributes may also contain information about the test execution. In this case the subject operation may also allow the values of these attributes to be read. + +##### 7.3.4.1.2 Input parameters + +| Parameter name | Qualifier | Information type | Comment | +|----------------|-----------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| testObject | M | Name | This parameter specifies the instance of the tester object, whose attribute values of testState , testOutcome and other attributes shall be retrieved. | + +##### 7.3.4.1.3 Output parameters + +| Parameter name | Qualifier | Matching information | Comment | +|--------------------------|-----------|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| monitoredAttributeValues | M | SET {
TestObject.testState (M)
TestObject.testOutcome (M)
other attributes (O)
} | This parameter shall be returned if all attributes were read successfully and may be returned, if at least one attribute was read successfully. The values to be returned are those prevalent at the time of the reception of the subject operation. | +| error | M | failureReason | This parameter shall be returned if the specified tester object instance does not exist or, in the case where the tester object instance exists, at least one attribute could not be read, i.e., if operationFailedEntirely = TRUE OR operationFailedPartly = TRUE. The parameter returns the failure reason. | + +##### 7.3.4.1.4 Pre-condition + +The precondition must hold true before the operation is invoked. + +indicatedTOInstanceIsExisting + +| Assertion name | Definition | +|---------------------------|------------------------------------------------------------| +| toBeMonitoredTOIsExisting | The TO instance indicated by the subject operation exists. | + +##### 7.3.4.1.5 Post-condition + +The post-condition must hold true after the completion of the operation. + +allAttributeValuesRead **OR** notAllAttributeValuesRead **OR** noAttributeValueRead + +| Assertion name | Definition | +|---------------------------|---------------------------------------------------------------------------------------------------------| +| allAttributeValuesRead | All attributes of the TO indicated by the subject operation were read successfully. | +| notAllAttributeValuesRead | Not all but at least one attribute of the TO indicated by the subject operation were read successfully. | +| noAttributeValueRead | No attribute of the TO indicated by the subject operation was read successfully. | + +##### 7.3.4.1.6 Exception + +| Exception name | Definition | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| operationFailedEntirely | Condition: toBeMonitoredTOIsExisting = FALSE OR
noAttributeValueRead = TRUE
Returned information: The error parameter returns the object identifier of the TO that does not exist or the reasons for which the attributes could not be read
Exit state: Entry state | +| operationFailedPartly | Condition: toBeMonitoredTOIsExisting = TRUE AND
notAllAttributeValuesRead = TRUE
Returned information: The error parameter returns the reason for which an attribute could not be read. The attribute that could be read may be returned in the parameter error or the parameter attributeList
Exit state: Entry state | + +### 7.3.5 Interface TestManagementIRPNotifications + +#### 7.3.5.1 Notification *notifyTestResults* (M) + +##### 7.3.5.1.1 Definition + +Test results are made available to the IRPManager by one or more notifications *notifyTestResults* emitted by the TO that is related to the test invocation. + +Depending on the nature of the test and the specification of the TO behaviour, the TO may need to convey to the IRPManager a test result data set. There are two ways to convey this kind of information. One way is to use the parameter *additionalInformation* of the notification. In this case, the *fileReference* and *fileExpiryDate* shall contain no information or be absent. The other way is to use a file to capture the test result data set. In this case, the *additionalInformation* parameter may contain no information or be absent and the *fileReference* and *fileExpiryDate* shall be present. The file that captures the test result data set shall contain specific attributes and other attributes such as *TestObjectClass*, *testOutcome*, etc. + +The use of the *additionalInformation* parameter or a file to capture the test result data set is specified by the class specification of the TO. + +In case the TO uses *additionalInformation* (and not a file) to capture the test result data set, that TO may emit this notification to transfer intermediate (non-final) test results. In this kind of notifications, the *testOutcome* parameter shall be absent. The TO should emit at least one more notification regarding the subject test invocation in the future. The last notification pertaining to a particular test invocation shall be indicated by including the *testOutcome* parameter in the notification. + +In the case the TO uses a file to capture the test result data set, that TO shall not issue any notifications to transfer intermediate test results. The TO may capture the non-final test results in the file used to capture the final test result data set. + +The events triggering the emission of test result notifications depend on the specific test. They shall be specified by the TO that is actually instantiated, i.e., either by the test category specific TO. Some generic triggering events are included in this specification. It is expected that vendors specify more triggering events. + +| Parameter name | Qualifier | Matching information | Comment | +|-------------------------|----------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| objectClass | M, Y | TestObject.objectClass | Notification header – see [1]. It shall carry the TO class name. | +| objectInstance | M, Y | TestObject.objectInstance | Notification header – see [1]. It shall carry the DN of the TO. | +| notificationId | O, N | – | Notification header – see [1]. | +| eventTime | M, Y | – | Notification header – see [1]. | +| systemDN | C, Y | – | Notification header – see [1]. | +| notificationType | M, Y | "notifyTestResults" | Notification header – see [1]. | +| testInvocationInitiator | C, Y | TestObject.testInvocationInitiator | | +| testOutcome | O, N
(Note) | TestObject.testOutcome | It shall be included only in the last notification emitted by a TO. In this way the TO indicates that it is sending no more notifications. | +| mORT | O, N | TestObject.theMORT | It identifies the object instance of the MORT that was subject to the test. | +| proposedRepairActions | O, N | TestObject.proposedRepairActions | | +| additionalInformation | O, N
(Note) | TestObject.additionalInformation | It allows the inclusion of any additional information in the notification. As such, it may carry a test result data set. The exact semantics of this parameter is outside the scope of this specification. This parameter may contain no information or be absent, if the test results are captured in a file. It may be present if the test results are not captured in a file. | +| fileReference | M, N
(Note) | TestObject.fileReference | It shall contain no information or be absent if there is no test result captured in a file. It shall contain information if the test results are captured in a file. | +| fileExpiryDate | M, N
(Note) | TestObject.fileExpiryDate | It shall contain no information or be absent if fileReference carries no information or absent. Otherwise, it shall contain a valid future date and time. | + +NOTE – As for the correct interpretation of this qualifier refer to the comment column. + +##### 7.3.5.1.2 Triggering Events for the test + +For the test the events triggering the emission of test result notifications are: + +- Termination of the test execution. + +The test may be terminated explicitly by a test termination request. The events triggering an implicit termination are: + +- Fulfilment of the conditions for a successful termination of the test. +- Fulfilment of the conditions for a premature termination of the test. +- Occurrence of an error situation. + +###### 7.3.5.1.2.1 From-State + +testTerminateRequestReceived OR testCompleted OR prematureTermination OR testTimedOut OR errorSituationOccured. + +| Assertion name | Definition | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| testTerminateRequestReceived | The object with the ability to receive and react upon test requests has received a test termination request (Note). | +| testCompleted | The predefined conditions for a successful completion of the test are fulfilled (Note). | +| prematureTermination | The predefined conditions for a premature termination of the test are fulfilled (Note). | +| errorSituationOccured | An error situation has occurred during the test execution and the tester object has aborted the test invocation (Note). | +| NOTE – The conditions to satisfy this trigger are related to the specific TO definition and therefore their specifications are outside the scope of this Recommendation. | | + +###### 7.3.5.1.2.2 To-State + +testTerminated + +| Assertion name | Definition | +|----------------|--------------------------------------------| +| testTerminated | The test has been terminated successfully. | + +# Bibliography + +[b-3GPP TS 32.322] 3GPP TS 32.322 V11.0.0 (2012), *Telecommunication management; Test Management Integration Reference Point (IRP); Information Service (IS) (Release 11)*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|----------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.3710-201311-I_PDF-E/raw.md b/marked/M/T-REC-M.3710-201311-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..87e47f360bb3cc8d9b2226d663dd2a590f580e6c --- /dev/null +++ b/marked/M/T-REC-M.3710-201311-I_PDF-E/raw.md @@ -0,0 +1,463 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.3710** + +(11/2013) + +SERIES M: TELECOMMUNICATION MANAGEMENT, +INCLUDING TMN AND NETWORK MAINTENANCE + +Integrated services digital networks + +--- + +**Overview of an automated service test to +support cost-efficient telecom service +assurance** + +Recommendation ITU-T M.3710 + +![ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union'](84a1d09fb489061482111515543b60dc_img.jpg) + +ITU logo: A globe with a red lightning bolt and the text 'ITU International Telecommunication Union' + +# ITU-T M-SERIES RECOMMENDATIONS **TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE** + +| | | +|---------------------------------------------------------------------------------|----------------------| +| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 | +| International transmission systems | M.300–M.559 | +| International telephone circuits | M.560–M.759 | +| Common channel signalling systems | M.760–M.799 | +| International telegraph systems and phototelegraph transmission | M.800–M.899 | +| International leased group and supergroup links | M.900–M.999 | +| International leased circuits | M.1000–M.1099 | +| Mobile telecommunication systems and services | M.1100–M.1199 | +| International public telephone network | M.1200–M.1299 | +| International data transmission systems | M.1300–M.1399 | +| Designations and information exchange | M.1400–M.1999 | +| International transport network | M.2000–M.2999 | +| Telecommunications management network | M.3000–M.3599 | +| Integrated services digital networks | M.3600–M.3999 | +| Common channel signalling systems | M.4000–M.4999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T M.3710 + +## Overview of an automated service test to support cost-efficient telecom service assurance + +## Summary + +Recommendation ITU-T M.3710 provides an overview of an automated service test. It defines a general model for an automated service test and describes a set of functional requirements to support cost-efficient telecom service assurance. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T M.3710 | 2013-11-13 | 2 | 11.1002/1000/12046 | + +## Keywords + +Automated service test, QoS, test manager, test point, test programme. + +--- + +\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, . + +## FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at . + +© ITU 2014 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +| | Page | +|-----------------------------------------------------------------|------| +| 1 Scope ..... | 1 | +| 2 References..... | 1 | +| 3 Definitions ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 2 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Concepts and background..... | 3 | +| 6.1 Overview ..... | 3 | +| 6.2 Position in the eTOM business process framework ..... | 3 | +| 6.3 System and entity relationship in this Recommendation ..... | 4 | +| 7 General model of the automated service test..... | 5 | +| 8 Functional requirements for an automated service test ..... | 5 | +| 8.1 Programme template management ..... | 5 | +| 8.2 Test programme management ..... | 6 | +| 8.3 Test point management..... | 6 | +| 8.4 Test script management..... | 7 | +| 8.5 Test resource management ..... | 7 | +| 8.6 Test data management ..... | 7 | +| 8.7 Alarm notification ..... | 8 | +| 8.8 Security consideration ..... | 9 | +| Appendix I – Example of automated service test scenarios..... | 10 | +| I.1 Scenario 1 of automated service test ..... | 10 | +| I.2 Scenario 2 of automated service test ..... | 11 | +| Appendix II – Use cases of automated service tests ..... | 13 | + + + +## Recommendation ITU-T M.3710 + +## Overview of an automated service test to support cost-efficient telecom service assurance + +# 1 Scope + +This Recommendation provides an overview of an automated service test. It defines a general model for an automated service test and describes a set of functional requirements to support operators carrying out a customer-oriented telecom service test. + +The measurement parameters to be monitored for specific services are outside of the scope of this Recommendation. + +## 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T E.800] Recommendation ITU-T E.800 (2008), *Definitions of terms related to quality of service*. +- [ITU-T M.3050.1] Recommendation ITU-T M.3050.1 (2007), *Enhanced Telecom Operations Map (eTOM) –The business process framework*. +- [ITU-T M.3320] Recommendation ITU-T M.3320 (1997), *Management requirements framework for the TMN X-interface*. +- [ITU-T Q.3945] Recommendation ITU-T Q.3945 (2011), *Test specifications for next generation network services on model networks – Test set 1*. +- [ITU-T X.733] Recommendation ITU-T X.733 (1992) | ISO/IEC 10164-4:1992 , *Information technology – Open Systems Interconnection – Systems Management: Alarm reporting function*. +- [ITU-T X.745] Recommendation ITU-T X.745 (1993), *Information technology – Open Systems Interconnection – Systems Management: Test Management function*. + +# 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 network operator** [ITU-T M.3320]: An organization which operates a telecommunications network. A network operator may be a service provider and vice versa. A network operator may or may not provide particular telecommunications services. + +**3.1.2 quality of service (QoS)** [ITU-T E.800]: Totality of characteristics of a telecommunications service that bear on its ability to satisfy stated and implied needs of the user of the service. + +**3.1.3 service** [ITU-T M.3050.1]: Services are developed by a service provider for sale within products. The same service may be included in multiple products, packaged differently, with different pricing, etc. + +**3.1.4 service provider** [ITU-T M.3320]: A general reference to an entity that provides telecommunications services to customers and other users either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. + +**3.1.5 test operations** [ITU-T X.745]: Management operations concerned with tests. + +**3.1.6 test performer** [ITU-T X.745]: An agent which receives test operations. + +**3.1.7 test request** [ITU-T X.745]: An individual request issued by a test conductor to a test performer, in order to initiate one or more test invocations. + +**3.1.8 test results** [ITU-T X.745]: Information generated during test execution and made available to an open system. + +### **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 test point**: The function entity that takes the role of test performer and interacts with the telecom network. + +**3.2.2 test domain**: A set of test points that share some common characteristics and are subject to unified management. + +**3.2.3 test programme**: A test plan and an assembly of attributes to accomplish a specific test objective. + +**3.2.4 test script**: A service-specific software unit that can perform the test operations of a particular service automatically. + +## **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|---------------------------------| +| BSS | Business Support System | +| eTOM | enhanced Telecom Operations Map | +| MDN | Mobile Directory Number | +| NO | Network Operator | +| NTP | Network Time Protocol | +| OSS | Operation Support System | +| QoS | Quality of Service | +| SLA | Service Level Agreements | +| SP | Service Provider | + +# **5 Conventions** + +The following conventions are used in this Recommendation: + +- The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. + +- The keywords "**is prohibited from**" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. +- The keywords "**is recommended**" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance. +- The keywords "**is not recommended**" indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this Recommendation can still be claimed even if this requirement is present. +- The keywords "**can optionally**" indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with this Recommendation. + +# 6 Concepts and background + +## 6.1 Overview + +Providing high quality telecom services to end users in a cost-efficient manner is the key for a NO/SP aiming to gain a sustainable competitive advantage. The NO/SP needs to ensure that services delivered to customers are continuously available and meet the requirements of SLA or QoS levels. At the same time, reducing the operating costs and increasing operation efficiency is another important consideration for telecom operators. + +The automated service test is a solution for end-to-end service quality assurance that uses an automated test facility which can proactively search for network failure and/or service quality deterioration. Appendix I describes some examples of automated service test scenarios. The automated service test is able to ensure the quality of a wide range of telecom services such as voice services, messaging services, data services, value-added services, etc. Appendix II describes some use-cases of the automated service test. + +## 6.2 Position in the eTOM business process framework + +Figure 1 illustrates the position of the automated service test in the eTOM business process framework [ITU-T M.3050.1]. The automated service test is an element of the assurance operations process, which supports service problem management and service quality management of the service management and operations function. + +![Figure 1: Position of automated service test in eTOM framework. This diagram shows the eTOM framework structure with four main horizontal layers: Operations, Service management and operations, Resource management and operations, and Supplier/partner relationship management. Each layer is divided into four vertical columns: Operations support and readiness, Fulfilment, Assurance, and Billing. The 'Assurance' column is highlighted with a red box around 'Service problem management' and 'Service quality management'. The 'Customer' is shown at the top in a yellow oval. Various sub-functions are listed within each layer, such as 'Customer relationship management', 'Service configuration and activation', 'Resource provisioning', and 'S/P requisition management'. Reference numbers M.3710(13)_F01 are present at the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Figure 1: Position of automated service test in eTOM framework. This diagram shows the eTOM framework structure with four main horizontal layers: Operations, Service management and operations, Resource management and operations, and Supplier/partner relationship management. Each layer is divided into four vertical columns: Operations support and readiness, Fulfilment, Assurance, and Billing. The 'Assurance' column is highlighted with a red box around 'Service problem management' and 'Service quality management'. The 'Customer' is shown at the top in a yellow oval. Various sub-functions are listed within each layer, such as 'Customer relationship management', 'Service configuration and activation', 'Resource provisioning', and 'S/P requisition management'. Reference numbers M.3710(13)\_F01 are present at the bottom right. + +Figure 1 – Position of automated service test in eTOM framework + +## 6.3 System and entity relationship in this Recommendation + +As indicated in Figure 2, the systems and entities involved in the automated service test include BSS/OSS, the test manager, test points and telecom networks. + +![Figure 2: Systems and entities involved in automated service test. This diagram shows the flow of information and control between BSS and OSS, the Automated service test (containing Test manager and Test point), and the Telecom network. Arrows indicate 'Alarm reporting' from BSS and OSS to the Test manager, 'Control and management' between the Test manager and Test point, and 'Test' between the Test point and the Telecom network. Reference numbers M.3710(13)_F02 are present at the bottom right.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Figure 2: Systems and entities involved in automated service test. This diagram shows the flow of information and control between BSS and OSS, the Automated service test (containing Test manager and Test point), and the Telecom network. Arrows indicate 'Alarm reporting' from BSS and OSS to the Test manager, 'Control and management' between the Test manager and Test point, and 'Test' between the Test point and the Telecom network. Reference numbers M.3710(13)\_F02 are present at the bottom right. + +Figure 2 – Systems and entities involved in automated service test + +This Recommendation describes the management functions between the test manager and test points and the management functions between the test manager and BSS/OSS. The test interface between test points and the telecom networks should comply with the standardized network interface protocols. The corresponding function requirements are outside of the scope of this Recommendation. + +## 7 General model of the automated service test + +Figure 3 illustrates the model of the automated service test, which is principally comprised of the test manager and test points. The automated service test is controlled by test programmes defined by the test manager. Test points receive test requests from the test programme and invoke test scripts to perform service test operations. + +![Figure 3: Model of the automated service test. The diagram shows a 'Test manager' box containing a 'Test programme' (represented by two stacked ovals). Arrows point from the 'Test programme' to a stack of 'Test point' boxes (each containing a 'Test script' oval). The arrows are labeled 'Test request', 'Monitor and control', 'Result report', and 'Alarm notification'. A bracket on the right side of the 'Test point' stack is labeled 'Test domain'. The diagram is labeled 'M.3710(13)_F03' at the bottom right.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +Figure 3: Model of the automated service test. The diagram shows a 'Test manager' box containing a 'Test programme' (represented by two stacked ovals). Arrows point from the 'Test programme' to a stack of 'Test point' boxes (each containing a 'Test script' oval). The arrows are labeled 'Test request', 'Monitor and control', 'Result report', and 'Alarm notification'. A bracket on the right side of the 'Test point' stack is labeled 'Test domain'. The diagram is labeled 'M.3710(13)\_F03' at the bottom right. + +**Figure 3 – Model of the automated service test** + +- Test manager: The entity which controls and manages all the service test operations. The test manager can create and manage multiple test programme instances. +- Test programme: A test plan and an assembly of attributes to accomplish a specific test objective. A test programme can be instantiated from a test template, which can facilitate the effectively automated service test. +- Test point: The function entity that assumes the role of test performer. Test points can send and receive signals and interact with telecom networks. Figure 4 shows the typical structure of a telecom network for service testing (referenced from [ITU-T Q.3945]). Although test points can be deployed in any of the control points of Figure 4, test points are typically deployed at the UNIs of the network. + +![Figure 4: The structure of a typical model network for service testing. The diagram shows a network path from 'TE A' to 'TE B'. The path consists of: UNI (Control point 1) -> Access network (Control point 2) -> Session control segment (Control point 3) -> Transport network (Control point 4) -> Session control segment (Control point 5) -> Access network (Control point 6) -> UNI. The diagram is labeled 'Q.3945(11)_F01' at the bottom right.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Figure 4: The structure of a typical model network for service testing. The diagram shows a network path from 'TE A' to 'TE B'. The path consists of: UNI (Control point 1) -> Access network (Control point 2) -> Session control segment (Control point 3) -> Transport network (Control point 4) -> Session control segment (Control point 5) -> Access network (Control point 6) -> UNI. The diagram is labeled 'Q.3945(11)\_F01' at the bottom right. + +**Figure 4 – The structure of a typical model network for service testing** + +- Test script: A service-specific software unit that can be invoked by a test programme and perform the test operations automatically. +- Test domain: A set of test points that share some common management features, for example, they may belong to the same geographical area or administrative zone, or they may use the same interface protocol, or apply the same test policy, etc. Test points in the same test domain can be managed in the same way. + +# 8 Functional requirements for an automated service test + +### 8.1 Programme template management + +The programme template describes the common components of a test programme and helps in facilitating the quick and easy setup of a test programme. + +The general test programme template is required to include the following basic information: + +- Test programme ID: The unique identifier of the test programme. +- Test programme name: Name assigned to the test programme. +- Description: Brief introduction of the test programme. + +- Priority: Priority value controls the sequence in which concurrent test programmes need to be conducted so that any test resource requirement conflicts can be avoided. Test programmes with higher priority should be served first. +- Invocation cycle: Invocation cycle controls the time and frequency for the execution of a test programme. A test programme can be executed in both periodic and aperiodic ways. +- Report interval: The time interval for a test point to submit the test result and test data. +- Test item list: Number of test tasks that should be executed automatically in a predefined sequence by the test programme. The execution of each test item should invoke the corresponding test scripts to perform test operations on a specific service. +- Test domain and test point lists: Assignment of test domain and a list of test points which should perform this test. +- Resource: Physical and logical resources allotted for the test programme. + +It is required to allow the test manager to create, modify, interrogate or delete a programme template. + +### 8.2 Test programme management + +Test programme management is required to consist in the following: + +- The ability to create a test programme by instantiating the test programme template. +- The ability to configure a test programme based on the service test objective. The invocation cycle and the range of test points involved in the test should be designed carefully, so as to minimize the impact on the normal network traffic and service usage. +- Test manager support to activate, inquire, suspend, modify, reactivate, terminate and delete the programmes. The corresponding status of a test programme can refer to test states defined in [ITU-T X.745]. +- The ability to allow a test manager to centrally manage all test programmes. The test manager maintains the queues of all activated test programmes and starts test sessions with corresponding test points according to the time cycle assignment and the priority of test programmes. +- The ability to allow a test manager to monitor and control the execution of the service test in each test point. + +### 8.3 Test point management + +Test point management is required to consist in the following: + +- Configuring the network interface protocol of test points. +- Monitoring the state of all test points. +- Collecting test results and test data from test points periodically or by request. +- The test point is recommended to be able to store test data locally for a long enough period of time when test data are, for any reason, unable to be submitted to the test manager. +- All test points are required to be time synchronized based on the Network Time protocol. + +### 8.4 Test script management + +As there is significant diversity for different telecom services in service function and service process, a test script should be specifically designed for each type of service. Test scripts can be developed via a programming language or script/notation language, which is outside of the scope of this Recommendation. The management of test scripts consists of the following: + +- Test scripts are recommended to be downloaded, installed, updated or deleted by test points upon request from the test manager, either locally or remotely. +- Service parameters are recommended to be monitored and captured during the service test. The parameters to be captured for a specific service can optionally refer to ITU-T Q-series and ITU-T E-series Recommendations. + +All test operations are required to comply with the network interface, signalling and service protocols of the tested network and service and should not introduce unintended service failure or un-conformance. + +### 8.5 Test resource management + +Test resources consist of logical and physical resources necessary for performing an automated service test, for example, telephone number, IP address, test cards, test terminals and other instruments, etc. + +- All test resources are recommended to be centrally controlled by a test manager. The test manager should be able to manage the readiness and availability of all test resources. +- A test manager is required to be able to add, remove, activate, test and allocate all test resources. Only resources allocated by the test manager can be accessed and utilized by a corresponding test programme. +- A test manager is recommended to support priority-based resource scheduling, so as to satisfy the resource requirements of high-priority test programmes and harmonize the conflicts among different test programmes. +- A test manager can optionally support the discovery and force release of test resources when it is occupied by the hung test programmes. +- A test resource can optionally be multiplexed by different test programmes/test points on the basis of a time schedule. + +### 8.6 Test data management + +Test data management should support the further processing and analysis of test results and test data reported from test points, in order to find potential service problems in time, supervise the service quality and acquire information that can assist O&M staff to locate and resolve problems. + +Test data can be comprised from two parts. The first part of test data is test programme specific data that can reflect the process of how test programmes are scheduled and executed. The following data are required to be collected: + +- The point in time to start each test programme execution. +- The point in time to stop each test programme execution. +- The process of the programme that is scheduled. +- The process and result of test resource allocation. +- The result of programme execution: the success or failure of each test programme execution and the corresponding fault code or reasons if the test has failed. + +The second part of test data is service specific parameters that record the service flow and the critical service parameters that can help in analysis of the service quality. The following data is required to be collected: + +- The point in time to start the test of a specific service. +- The point in time to stop the test of a specific service. +- The process and result of a test resource invocation. +- The outcome of the test: the result of a specific service test, which can optionally refer to the test outcome definition of [ITU-T X.745]. The corresponding fault code or reasons for failure can optionally be provided when a service failure occurs. +- Service parameters: critical service dependent parameters that are captured during the service test. + +A test point can optionally report test results and test data to a test manager via the following methods: + +- Immediate: test points report test result/test data as soon as possible after the execution of the test in the case of the real-time service monitoring and service quality analysis. +- Periodic: test points report test result/test data in the predefined time and period in the case of routine service quality monitoring and assurance. +- By request: test point reports test result/test data whenever it receives the request from the test manager. + +It is recommended that all the test data reported from test points should be stored in the test database. + +The test manager is recommended to be able to process the test result and test data, calculate the service KQIs and verify end-to-end service QoS and its change trend. + +The basic classification of service quality metrics can optionally refer to the service quality characteristics of [ITU-T E.800] and particular service metrics definition and calculation can optionally refer to corresponding E series and Q series ITU-T Recommendations. + +The test manager can optionally conduct correlated analysis based on the test database, so as to identify possible service faults and to indicate the severity, affected area and fault location when network/service failure or quality deterioration occurs. + +The result analysis can optionally be presented in a graphical manner, visualizing the service status of test points, test domains and the overall network and service and indicating the area and the severity when network/service problems occur. + +### 8.7 Alarm notification + +Alarm management is an important function of real-time notification to the OSS/BSS and O&M staff of service problems that are found during the automated service test. + +- Alarm definition support. An alarm is recommended to include the following information: alarm title, alarm severity, alarm type, alarm content that explains the reason for raising the alarm, the point in time when the alarm is raised, test point/test programme ID and alarm trigger criteria. The alarm severity is recommended to comply with the definition of [ITU-T X.733]. +- The ability to configure the alarm trigger criteria or alarm policy for each test programme and the following conditions can be optionally supported when defining the alarm policy: + - Specific service quality metric is above or below the predefined threshold. + - The duration of service quality downgrading is detected. + - The trend of service quality indicates possible network/service failure or deterioration. + +- A test point is required to detect and raise an alarm in time when there is an occurrence of network and service unavailability. The test manager should forward alarms from test points to OSS/BSS and O&M staff. +- The test manager is required to analyse and find possible service quality problems and forward alarms to OSS/BSS and O&M staff in time. +- The test manager can optionally support the ability to assign the alarm forwarding destination and the real-time alarm notification in multiple forms including generating sounds or sending an SMS or e-mail. +- It is recommended to support the alarm operations including alarm enquiry, alarm clearing and alarm backup. + +## **8.8 Security consideration** + +It is recommended that the following security mechanisms should be implemented: + +- To allow only authorized users to access the automated service test facilities. +- To allow only authorized users to operate test programmes and access test results and test data. +- To allow only authorized test points to access the allocated test resources. + +## Appendix I + +### Example of automated service test scenarios + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Scenario 1 of automated service test + +| Legend | Scenario | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario title | Automated roaming test | +| Service Requirements | To ensure all frequently used mobile services work reliably both inside and outside of the home network, so that subscribers can access and use mobile services anywhere with the committed quality wherever the subscriber is roaming both home and abroad. | +| Scenario description |
  1. 1. Assuming that the following inbound roaming into City a of Country A should be tested: roaming from City b and City c of Country A to City a of Country A, and roaming from City d of Country B to City a of Country A.
  2. 2. Test points x, y, z had been deployed in City a of Country A, and all deployed test points should have downloaded the predefined test scripts.
  3. 3. After the test programme is activated (by request or via a predefined trigger event), test points should retrieve the user data from the SIM/UIM resource pool whose home location is City b and start the test operations under the control of test scripts which can carry out the test for frequently used mobile services such as voice communication, SMS, Internet surfing, etc.
  4. 4. Next, test points should then retrieve the user data from the SIM/UIM resource pool whose home location is City c and City d and then each test point should start the test alternately.
  5. 5. An alarm should be issued to the test manager and forwarded to BSS/OSS and O&M staff if consecutive test failures are found.
  6. 6. The test manager can suspend or terminate the test by sending a request to the test points during the course of the test.
  7. 7. After the test is completed or terminated, test results and test data should be collected by the test manager for further analysis.
| +| Figure describing the scenario |

Image: Diagram illustrating the automated roaming test scenario. A central circle represents 'City a of country A', containing three cell towers and three test points labeled 'Test point x', 'Test point y', and 'Test point z'. To the left, a box labeled 'UIM/SIM pool' contains three entries: 'City b of country A', 'City c of country A', and 'City d of country B'. A dashed blue arrow points from this pool to 'Test point x'. To the right, three ovals represent mobile services: 'Voice', 'SMS', and 'Internet surfing', with lines connecting them to the test points. The diagram is labeled 'M.3710(13)_FI.1' in the bottom right corner.

| + +**Figure I.1 – Automated roaming test** + +| Legend | Scenario | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Derived function requirements |
  1. 1. Service programme management, including the synchronization of test scripts to test points, the activation, suspension and/or termination of the service programme.
  2. 2. Test resource management, including the SIM/UIM information multiplexing.
  3. 3. Test point management for conducting the test operations.
  4. 4. An alarm should be issued and a test report should be collected and analysed.
| + +### I.2 Scenario 2 of automated service test + +| Legend | Scenario | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenario title | Benchmarking test | +| Service Requirements | In the competitive telecommunications environment, telecom operators need to acquire knowledge of the network performance and service quality of their competitors. Telecom operators also need to assess the situation of their own service delivery so that network/service optimization can be carried out and so that decisions can be taken on marketing policy. | +| Scenario description |
  1. 1. Assuming that telecom operator A is running a CDMA2000 network, telecom operator B is running a WCDMA network and that telecom operator C is running a GSM network. Telecom operator A needs to benchmark its voice service with the other two telecom operators (B and C).
  2. 2. Test points that support the GSM/CDMA2000/WCDMA air interface protocol are deployed.
  3. 3. The test manager specifies the test programme and the test resources that are required.
  4. 4. Test points download the predefined test scripts, retrieve the use data (UIM/SIM information) and consecutively and/or simultaneously carry the test calls through the GSM, CDMA2000, WCDMA networks.
  5. 5. Test data that can record the critical parameters and service flow of the test are collected. Test points periodically submit the test data to the test conductor.
  6. 6. The test manager collects the test data and calculates the service metrics for the voice call of different networks/operators, such as "Establish Duration", "Alert Duration", "Call Success Rate", etc.
  7. 7. If the service metrics are above/below predefined thresholds, an alarm should be raised and forwarded to BSS/OSS and O&M staff.
  8. 8. The KPIs and other analysis results are presented as a visual report and submitted to O&M staff and marketing staff for further use.
| + +| Legend | Scenario | +|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| High level figure describing the scenario | Diagram of a benchmarking test scenario showing a UIM/SIM pool connected to GSM, WCDMA, and CDMA2000 networks. Test points x, y, and z are marked within a coverage area. A 'Voice' call is indicated by a blue oval. The diagram is labeled M.3710(13)_FI.2.

Figure I.2 – Benchmarking test

| +| Derived function requirements |
  1. 1. Service programme management including the synchronization of test scripts to test points and the activation, suspension and/or termination of the service programme.
  2. 2. Test scripts should comply with the interface protocols and service processes of multiple networks.
  3. 3. Test data collection and service quality analysis.
| + +## Appendix II + +### Use cases of automated service tests + +(This appendix does not form an integral part of this Recommendation.) + +Use cases of automated service tests include but are not limited to: + +- Service quality supervision: perform 24/7 uninterrupted testing of network and service quality. The service quality characteristics are described in [ITU-T E.800]. +- Upgrade/rollout support: perform extensive testing before and after the installation or modification of network infrastructure or a new service rollout, so as to ensure a smooth upgrade and rollout and minimize the impact on the service user. +- Fault location: identify the range affected when a network failure or service quality downgrade occurs and assist in quickly locating the problems by providing an extensive test. +- Benchmarking: Operators need to benchmark their network and services against the competition via automated and continuous testing and measuring of corresponding service KPIs of different operators and find ways to surpass their competitors in terms of network and service quality. + + + + + +# SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|---------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | General tariff principles | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Terminals and subjective and objective assessment methods | +| Series Q | Switching and signalling | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/4086a572c080354982c11f1de4d6921d_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/4086a572c080354982c11f1de4d6921d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68ece254e07264ceddc2e6f2c71b6eed1d6f063b --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/4086a572c080354982c11f1de4d6921d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08a43138dfad96c77d0dbf42c0b9efb7e3ee3cbb13c25c5b2997693beec3e31a +size 52754 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01837e8eb09a2560f94a7eb0063c3f4e485b8a2d --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:480cbd4f4e3681afd816c706c3fc6796f000c9ddd673196cabaecf1eea2b4dd8 +size 69963 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/55d2bfe1c3d04e86df8d7a104d802172_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/55d2bfe1c3d04e86df8d7a104d802172_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..017a84e35b7b351e291846553476650a09ff86f2 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/55d2bfe1c3d04e86df8d7a104d802172_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fe53f5df284c300966d9003a6e7c81cbcef7ec16d78f1c055ba25351c43485e +size 34720 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/7a3561af571faf036baa93f5f4b1bdb9_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/7a3561af571faf036baa93f5f4b1bdb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..263ec28250fada18d44f34b46482f7c9a91d6d10 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/7a3561af571faf036baa93f5f4b1bdb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed46833500c32113aec7468da080606d85ae1417508fa707ae7288d0bf1d2eae +size 91748 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/84e2ac543ffc4145dc85b05a48ec62e3_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/84e2ac543ffc4145dc85b05a48ec62e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..520cd844593ea35911faa96091b04c73f6b49fba --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/84e2ac543ffc4145dc85b05a48ec62e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b359561b3b60a8136db16ae51743bc6cf645493594ad4a47b1a7844911ccda48 +size 42585 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/a71911ad87414271aeb190e0eebcb989_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/a71911ad87414271aeb190e0eebcb989_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e7a0a3e2505ccafc505cad016e3e3da805e15a9 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/a71911ad87414271aeb190e0eebcb989_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f61069da7501c2c3f4ef5955e8508aa15f925d8ed999329134287d7c37a01bf8 +size 31547 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/ab9eb65dcbc2696ec77b66f70f9e0e91_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/ab9eb65dcbc2696ec77b66f70f9e0e91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2094c439f504330d8c4923437e3d8b2fbbda2598 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/ab9eb65dcbc2696ec77b66f70f9e0e91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30da0c8f1af8c418f81c077a99c5ff1b286d03e66f760655f3ed8895cf36010a +size 44124 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/c0843c6d138705289960d9f53a6e72a1_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/c0843c6d138705289960d9f53a6e72a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cecc134c102078ac7375684dca70ceb1a1bb306 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/c0843c6d138705289960d9f53a6e72a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:119df304b011c76bb6cc38f413bf900523f2fbba8e43d979eef292ac32786bba +size 22834 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..837154c0ea4ac2cb20d6dfe56c61c43f87e04abf --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e966941095f79759e7f2319370e0193a8fe09a4b7634c59e63b66d5957b299b +size 36300 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c165d58552c20ab18c10b3edcb69d5172ed3c42 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:762ee129b84dd9d3f0a236ecb5da4d13118ec6cd00a92dda90aa5123f98b32b0 +size 83483 diff --git a/marked/M/T-REC-M.380-198811-I_PDF-E/ecb25d766719ce041cf4cc390791a098_img.jpg b/marked/M/T-REC-M.380-198811-I_PDF-E/ecb25d766719ce041cf4cc390791a098_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64830629213930944c4dd030b82e38e9b344f2e8 --- /dev/null +++ b/marked/M/T-REC-M.380-198811-I_PDF-E/ecb25d766719ce041cf4cc390791a098_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5fe046c15afa2960f1b68fde080507538db484717296ee5640a2fee3c32a919 +size 35584 diff --git a/marked/M/T-REC-M.400-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.400-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0dc24b32ef94754e43ad40a944c7a85471c4f975 --- /dev/null +++ b/marked/M/T-REC-M.400-198811-I_PDF-E/raw.md @@ -0,0 +1,51 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.400** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE :** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**NUMBERING IN RADIO-RELAY LINKS +OR OPEN-WIRE LINE SYSTEMS** + +**ITU-T Recommendation M.400** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.400 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **NUMBERING IN RADIO-RELAY LINKS OR OPEN-WIRE LINE SYSTEMS** + +For numbering in a radio-relay link using frequency division multiplex, the channels, groups, supergroups, etc., are considered in the position they occupy in the baseband to be transmitted by that link. + +In the interests of direct interconnection the CCIR and CCITT have collaborated in drawing up Recommendation G.423 [1] from which it follows that the numbering of the telephony channels, groups and supergroups, etc., of the radio-relay link is as described in Recommendations M.320 to M.390. + +The same rules are applied to carrier systems on open-wire lines providing at least one group having 12 telephone channels. + +## **Reference** + +- [1] CCITT Recommendation *Interconnection at the baseband frequencies of frequency-division multiplex radio-relay systems*, Vol. III, Rec. G.423. \ No newline at end of file diff --git a/marked/M/T-REC-M.4030-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.4030-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7155d2eb6cd660e324cddce7ac473bda7ee30cee --- /dev/null +++ b/marked/M/T-REC-M.4030-199210-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c12f0f1a214f462caee5097527ab6e046f9119501315181ce51465a205daeb4 +size 8234 diff --git a/marked/M/T-REC-M.4030-199210-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg b/marked/M/T-REC-M.4030-199210-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..824efb533e642b5003d77bf49166ce560e335d6b --- /dev/null +++ b/marked/M/T-REC-M.4030-199210-I_PDF-E/431b8889a0e7f676f0eef40859590349_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b393760799ebd0b69f155ded900a70e714a7bdf53bdedc3f3b19689a32baec88 +size 57939 diff --git a/marked/M/T-REC-M.4030-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg b/marked/M/T-REC-M.4030-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b4f96d7278a9ab19b8d5be3f5800865aaa46d27 --- /dev/null +++ b/marked/M/T-REC-M.4030-199210-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65f17bbec436d70f125d43636a8e5e1032f40c804ab2e05f6378ce27dd8bdc26 +size 6810 diff --git a/marked/M/T-REC-M.4030-199210-I_PDF-E/7a3561af571faf036baa93f5f4b1bdb9_img.jpg b/marked/M/T-REC-M.4030-199210-I_PDF-E/7a3561af571faf036baa93f5f4b1bdb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dab5c73eccca06ac5fa5828faed8f8813652e5a7 --- /dev/null +++ b/marked/M/T-REC-M.4030-199210-I_PDF-E/7a3561af571faf036baa93f5f4b1bdb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1496797999edae9e6bdb5b5e5eb1b0e9568cdb1c3cec19454badd1ab33f35d59 +size 32526 diff --git a/marked/M/T-REC-M.4030-199210-I_PDF-E/954ff3c220707f98bcb2c4b197bd7d9f_img.jpg b/marked/M/T-REC-M.4030-199210-I_PDF-E/954ff3c220707f98bcb2c4b197bd7d9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51e860df9ea2cc5a516550a869d4d773c7294d03 --- /dev/null +++ b/marked/M/T-REC-M.4030-199210-I_PDF-E/954ff3c220707f98bcb2c4b197bd7d9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c3fb0876d68b70b227470be66bffa08b80d87bd4273bad627872f0e9f1d3482 +size 40322 diff --git a/marked/M/T-REC-M.410-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.410-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..77f21131ad67fa1e4c38b1597956138ac8e92b2e --- /dev/null +++ b/marked/M/T-REC-M.410-198811-I_PDF-E/raw.md @@ -0,0 +1,150 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.410** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: INTERNATIONAL TRANSMISSION +SYSTEMS (ANALOGUE)** + +--- + +**NUMBERING OF DIGITAL BLOCKS IN +TRANSMISSION SYSTEMS** + +**ITU-T Recommendation M.410** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.410 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **NUMBERING OF DIGITAL BLOCKS IN TRANSMISSION SYSTEMS** + +## **1 General** + +This Recommendation gives the numbering of tributaries in digital blocks and the numbering of blocks within higher order blocks and digital line system. The Series G Recommendations referred to below can be found in Volume III (Digital networks, transmission systems and multiplexing equipments). + +## **2 Primary multiplex equipment** + +### **2.1 Primary PCM multiplex equipment operating at 2048 kbit/s (Recommendation G.732)** + +Channel time slots 1 to 15 and 17 to 31 are assigned to 30 telephone channels numbered from 1 to 30 as indicated in Figure 1/M.410. + +| | | +|---------------------------------|----------------------------------| +| Channel time slots | 0 1 2 ..... 15 16 17 18 ..... 31 | +| Numbering of telephone channels | – 1 2 ..... 15 – 16 17 ..... 30 | + +FIGURE 1/M.410 + +#### **Example of primary multiplex equipment assignments** + +### **2.2 Primary PCM multiplex equipment operating at 1544 kbit/s (Recommendation G.733)** + +Channel time slots 1 to 24 are assigned to 24 telephone channels numbered from 1 to 24. + +### **2.3 Synchronous digital multiplex equipment operating at 2048 kbit/s (Recommendation G.736)** + +Channel time slots 1 to 31 are assigned to 31 channels at 64 kbit/s numbered from 1 to 31. + +### **2.4 Synchronous digital multiplex equipment operating at 1544 kbit/s (Recommendation G.734)** + +Channel time slots 1 to 23 are assigned to 23 channels at 64 kbit/s numbered from 1 to 23. + +### **2.5 Primary PCM multiplex equipment at 2048 kbit/s and offering synchronous 64 kbit/s digital access options (Recommendation G.737)** + +It should be possible to assign channel time slots 1 to 15 and 17 to 31 to thirty telephone channels numbered from 1 to 30 as indicated in Figure 1/M.410. + +Provision should also be made to provide 64 kbit/s digital access to at least two of these channel time slots, allocated in an order of priority given in Recommendation G.737. + +If there are $n$ telephone channels and $(30 - n)$ 64 kbit/s digital accesses, the channels are numbered from 1 to 30, with the digital access channels having DA (digital access) appended to the channel number. + +## 3 Second order PCM multiplex equipments + +### 3.1 *Second order PCM multiplex equipment operating at 8448 kbit/s (Recommendation G.744)* + +#### 3.1.1 *Channel time slots assignment for the case of channel associated signalling* + +Channel time slots 5 to 32, 34 to 65, 71 to 98 and 100 to 131 are assigned to 120 telephone channels numbered from 1 to 120 as indicated in Figure 2/M.410. + +| | | +|-----------------------|------------------------------------------------| +| Channel time slots | 0 1 2 3 4 5 6 ..... 32 33 34 ..... 65 | +| Numbering of channels | - - - - - 1 2 ..... 28 - 29 ..... 60 | +| Channel time slots | 66 67 68 69 70 71 72 ..... 98 99 100 ..... 131 | +| Numbering of channels | - - - - - 61 62 ..... 88 - 89 ..... 120 | + +FIGURE 2/M.410 + +#### Example of second order PCM multiplex equipment assignments + +#### 3.1.2 *Channel time slot assignment for the case of common channel signalling* + +The telephone channels corresponding to channel time slots 2 to 32, 34 to 65, 67 to 98 and 100 to 131 are numbered from 1 to 127. + +When there is a bilateral agreement between the Administrations involved for using channel time slot 1 for another telephone or service channel, this channel will be numbered 0. + +### 3.2 *Second order digital multiplex equipment operating at 8448 kbit/s (Recommendations G.742 and G.745)* + +The four tributaries operating at 2048 kbit/s are numbered from 1 to 4 in the order of interleaving. + +### 3.3 *Second order digital multiplex equipment operating at 6312 kbit/s (Recommendation G.743)* + +The four tributaries operating at 1544 kbit/s are numbered from 1 to 4 in the order of interleaving. + +## 4 Higher order multiplex equipment + +### 4.1 *Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s (Recommendation G.751 and G.753)* + +The four tributaries operating at 8448 kbit/s are numbered from 1 to 4 in the order of interleaving. + +### 4.2 *Digital multiplex equipments operating at the fourth order bit rate of 139 264 kbit/s (Recommendations G.751 and G.754)* + +#### 4.2.1 *Method using a 3rd order bit rate in the digital hierarchy* + +The four tributaries operating at 34 368 kbit/s are numbered from 1 to 4 in the order of interleaving. + +#### 4.2.2 *Method by directly multiplexing 16 digital signals at 8448 kbit/s* + +The 16 tributaries at 8448 kbit/s are numbered from 1 to 16: 1 to 4 in the order of interleaving for the first intermediate tributary at 34 368 kbit/s, 5 to 8 for the second, 9 to 12 for the third and 13 to 16 for the fourth as indicated in Figure 3/M.410. + +| | | +|--------------------------------------------------------------------------------|------------------------------------------------------------------------| +| Four intermediate tributaries at 34 368 kbit/s
in the order of interleaving | 1                      2                      3                      4 | +| Tributaries at 8448 kbit/s in the order of
interleaving | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | + +FIGURE 3/M.410 + +#### **Example of third order multiplex equipment assignments** + +### 4.3    *Digital multiplex equipment based on a second order bit rate of 6312 kbit/s (Recommendation G.752)* + +#### 4.3.1    *Third order digital multiplex equipment operating at 32 064 kbit/s* + +The five tributaries operating at 6312 kbit/s are numbered from 1 to 5 in the order of interleaving. + +#### 4.3.2    *Third order digital multiplex equipment operating at 44 736 kbit/s* + +The seven tributaries operating at 6312 kbit/s are numbered from 1 to 7 in the order of interleaving. + +## **5        Digital line system at 564 992 kbit/s on coaxial pairs (Recommendation G.954)** + +The four tributaries operating at 139 264 kbit/s are numbered from 1 to 4 in the order of interleaving. \ No newline at end of file diff --git a/marked/M/T-REC-M.4100-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.4100-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c0c73a6b1c1452b28bdb9ace3364ef8712b040d --- /dev/null +++ b/marked/M/T-REC-M.4100-199605-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:918856d707d44d2b6816333bd3ab17245b7ca6e7d7dcbf81a5f92a45078c43f8 +size 8203 diff --git a/marked/M/T-REC-M.4100-199605-I_PDF-E/raw.md b/marked/M/T-REC-M.4100-199605-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e1c7906951e3c42fca4c7170fc6742fd4e6a8eb5 --- /dev/null +++ b/marked/M/T-REC-M.4100-199605-I_PDF-E/raw.md @@ -0,0 +1,299 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.4100** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(05/96) + +**MAINTENANCE** + +**COMMON CHANNEL SIGNALLING SYSTEMS** + +--- + +**MAINTENANCE OF COMMON CHANNEL +SIGNALLING SYSTEM No. 7** + +**ITU-T Recommendation M.4100** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation M.4100 was revised by ITU-T Study Group 4 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 12th of May 1996. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|----------------------------------------------------------------------------------|-------------| +| 1 General ..... | 1 | +| 2 Appointment of administrative control and sub-control ..... | 1 | +| 3 Functions and responsibilities of the administrative control ..... | 1 | +| 3.1 Day-to-day maintenance of signalling systems ..... | 2 | +| 3.2 History and long-term analysis ..... | 2 | +| 3.3 Operations under Signal Transfer Point (STP) configurations ..... | 3 | +| 3.4 Implementing a new signalling system or a change to an existing system ..... | 3 | +| 4 Functions and responsibilities of the administrative sub-control ..... | 6 | +| 5 Contact point information ..... | 6 | +| 6 Monitoring requirements for maintenance purposes ..... | 6 | +| 6.1 The software monitor ..... | 7 | +| 6.2 Monitoring point requirements ..... | 7 | +| 6.3 Requirements of test equipment used for monitoring purposes ..... | 7 | +| References ..... | 8 | + +# **ABSTRACT** + +This Recommendation considers the general administration of Common Channel Signalling System No. 7. It defines the administrative control and sub-control, their respective functions and responsibilities, contact point information and monitoring requirements for maintenance purposes. + +# **KEYWORDS** + +Administrations, Agreements, Assignment, CIC code, Common Channel Signalling System No. 7, Continuity check, Label, Links, Linkset, Maintenance, Mode, Routing, Signalling-transfer-point. + +# **MAINTENANCE OF COMMON CHANNEL SIGNALLING SYSTEM No. 7** + +*(Melbourne, 1988; revised in 1993, 1996)* + +## **1 General** + +**1.1** It is essential that a common channel signalling system perform with very high reliability over the long term. It is also desirable that maintenance staff perform at the highest practical efficiency. In order to achieve both of these objectives with regard to common channel signalling systems, maintenance responsibilities and actions must be clearly defined and controlled. Such objectives make it necessary, in some cases, to place limitations on the freedom of involved maintenance units in performing independent maintenance actions. + +**1.2** This Recommendation considers the signalling system as an integrated system. It is not intended to replace or supersede any Recommendation or procedure (national network or otherwise) which might apply to specific components or subsystems, for example a signalling terminal or the signalling data link; rather, it proposes criteria regarding when and how such actions are to be initiated. Moreover, the general administration of the systems is considered and not the detailed interworking of its various equipments. + +**1.3** Various maintenance organizational units may have functional responsibility for individual subsystems which comprise a common channel signalling system (for example signalling terminals, processors, etc.). As the activities of any of these units will have an effect on the overall operation of the signalling system, and because in some cases it may not be possible to independently determine a need for maintenance attention, one point should be designated as an overall signalling system control. This point is entitled signalling system administrative control. The corresponding point at the distant terminal is known as the signalling system administrative sub-control. + +## **2 Appointment of administrative control and sub-control** + +**2.1** The appointment of administrative control and sub-control will be made by agreement between the two Administrations (e.g. Administration No. 1 and Administration No. 2) involved. These two points must be assigned for each signalling system which is placed in operation. It is suggested that the most appropriate point to act as administrative control or sub-control is the maintenance unit having responsibility for the signalling terminal and processor. However, this matter is left to the discretion of the Administrations concerned. + +**2.2** In the case of multiple signalling systems between the same two points, it may be appropriate to divide control and sub-control assignments, therefore sharing the burden of control responsibility. This is a subject for agreement between the Administrations concerned; however, this assignment and that of the control station for the transfer link should be to the same Administration. + +## **3 Functions and responsibilities of the administrative control** + +These responsibilities fall into four main areas: + +- i) day-to-day maintenance of working systems; +- ii) history and long-term analysis; +- iii) operation under Signal Transfer Point (STP) configurations; +- iv) implementing a new signalling system or a change to an existing system. + +### **3.1 Day-to-day maintenance of signalling systems** + +**3.1.1** Except as noted in 3.1.2, maintenance activity on any part of a common channel signalling system must only be undertaken with the agreement and knowledge of the administrative control. Such activities might relate to routine maintenance measurement of the signalling link, services affecting reconfigurations of transmission systems over which signalling links are routed (i.e. planned outages), etc. + +#### **Routine maintenance activities** + +- a) It is recommended that all routine maintenance and scheduled work activities be performed during hours of minimum traffic so that any inadvertent failure impacts the least number of customers. +- b) At a minimum, high risk, potentially service affecting maintenance and growth procedures should be scheduled during weekend and off-hour. The overall methods, procedures and scheduling of these work activities should be reviewed by a sub-control maintenance organization. +- c) The activities that may affect other network service providers must be coordinated, which includes both intra- and inter-Administration networks. +- d) Non-scheduled work activities – if customer service is being impacted, the minimum work activity will occur to restore the system to a stable performance state. Complete system recovery activity will be scheduled for the next minimum traffic period. + +**3.1.2** In the event of total failure of a signalling system due to a malfunction of one of its parts, immediate steps should be taken to remedy the fault condition. As soon as possible, the administrative control should be informed so that the event can be correlated with other reported events or known signalling failure. + +In this scenario, when a total CCSS No. 7 failure is experienced, some means of communication between personnel in interconnecting Administration networks, may be required. The Administration should determine what emergency communications are already available and/or what alternative methods, if any, will be provided. + +**3.1.3** Faults which are observable only at a signalling system terminal, for example intermittent failures resulting from an apparently high data bit error rate, must be analysed by the administrative control (and sub-control, depending on the direction of the indicated fault) in order to determine where maintenance attention is required. Such dynamic analysis might involve terminal diagnostic tests, error performance tests with the distant terminal, etc. The result of this dynamic analysis and tests will be corrective action, taken either by the administrative control, if under its jurisdiction, or by the sub-control, if under its jurisdiction, or the referral by the administrative control to the indicated part of the maintenance organization, for example the control station for the transfer link. + +### **3.2 History and long-term analysis** + +**3.2.1** The administrative control should maintain a record of all recognized or reported faults pertaining to each signalling system for which it is responsible. + +This information includes (but is not limited to) the following: + +- i) date and time a fault was reported or actually occurred; +- ii) the nature of the reported fault; +- iii) the reported location; +- iv) the location of the fault, when found; +- v) the actual fault condition found and the corrective action taken. + +This information should become a part of the history record maintained by the administrative control. + +**3.2.2** History records will enable long-term analysis to identify repeated faults of a signalling system. These records provide an ability to identify and correct potential problems before they become serious enough to cause a fault. Such efforts should improve the long-term operation of a signalling system and therefore afford more economical maintenance. + +It is suggested that historical records should be retained for at least 12 months. From the provision of a new signalling system, the history record should be initiated and continue until 12 months have passed. After analysis, each succeeding month will permit the discarding of records accrued during that same month of the previous year. Therefore, an administrative control can examine 13 months of (possible) **events**, which should be adequate to identify persistent faulty conditions. + +### **3.3 Operations under Signal Transfer Point (STP) configurations** + +**3.3.1** With two or more signalling systems in tandem used to convey signalling information between two international centres, signal transfer point operation presents possible maintenance complications. Events which occur in one system can affect the functioning between centres which have no control or sub-control responsibility for the faulty signalling system. If an administrative control determines that a fault has occurred in its signalling system which is part of an STP configuration, it must apprise the administrative control of the signalling system not directly involved, that a fault exists that affects (or will affect) signalling processes. The advice should also include an estimate of the time necessary to correct the condition and, when appropriate, the time of correction and the condition actually corrected. + +**3.3.2** When a condition affecting signalling via an STP warrants coordinated testing in order to determine the faulty part of either signalling system, the administrative control first involved in the fault report should coordinate testing efforts. Once the fault is localized, referrals can be made via normal procedures to achieve maintenance action. The following types of information should be exchanged at the time of the trouble referral: + +- circuit identification number for circuit specific troubles; +- date and time of referral; +- nature of the trouble and any other information that may be of assistance in resolving the trouble; +- trouble ticket number(s) or equivalent and the name or initial of the person accepting the trouble. + +When the fault is corrected, the administrative control for each of the signalling systems should be advised that the trouble has been cleared, the nature of the trouble found and the action taken. The administrative control which was first involved should confirm proper signalling via the STP. + +### **3.4 Implementing a new signalling system or a change to an existing system** + +Conversion from in-band signalling to CCSS No. 7 cannot be accomplished without a thoroughly planned process. Two interconnecting Administrations implementation team should meet to discuss and identify all of the steps necessary for a successful trunk conversion. Each administration should establish a Cutover Committee consisting of permanent members from the Ordering, Provisioning, Engineering, Operations, CCSS No. 7 Administration Control Centre and Billing disciplines. The responsibility of the committee is to ensure a smooth conversion through scheduling and addressing, taking into consideration the concerns listed below. + +**3.4.1** The following guidelines are offered as a starting point for discussion between two interconnecting Administrations. They are not all inclusive. + +- TIME OF THE CONVERSION – On what day will the actual conversion start? What time during the day will it take place? If it is out of hours, there may be expense related concerns of work force adjustments. Times may have to be correlated with traffic volumes dependent upon trunk capacity. + +- TRUNK OPERATIONS TEST – Is this the first time a specific configuration has been tested? If so, a comprehensive test plan is suggested. If not, a substantially abbreviated test procedure may be appropriate. Will transmission test be performed? +- TRANSITION TRUNK REQUIREMENTS – Will a transition trunk group need to be built? It should also be determined how the trunks will be converted with minimal service interruption. One method is to create a new trunk group for the CCSS No. 7 trunks and overflow the MF trunk group to the CCSS No. 7 Group (or vice versa). Converting in this manner allows all trunks to be in service with the exception of those which are actively in the conversion process. +- MAXIMUM NUMBER OF TRUNKS FOR CONVERSION – During that time that the trunks are actually being converted, they will be out of service. It must be determined how many trunks can be removed from service without adversely affecting traffic. Dependencies are the size of the trunk group, spare capacity and the time of conversion. Specific identification of trunks must be coordinate between the Administrations to ensure that both Administrations are converting the same trunks at the same time. +- MANUAL VS AUTOMATIC – Will any one of the two interconnecting Administrations be using a mechanized procedure for converting the trunks? This information may be useful in scheduling the work. +- FACILITY CHANGES – It is not anticipated that there will be facility changes associated with the conversion of trunks. If they are required, the information should be conveyed at the pre-conversion meeting. +- EQUIPMENT CHANGES – Most trunk equipment used for in-band signalling should also work with CCSS No. 7. However, some manufacturers may have designed their trunk equipment to work properly in the off-hook state only. This equipment, when used for CCSS No. 7, would provide degraded transmission since, in relation to E&M signalling, the circuit will always be on-hook. +- SWITCH TYPES – The switch types involved in the conversion should be identified to address special needs of specific switches. For example, a switch may require that the Trunk Circuit Identification Code (TCIC) and the trunk number be of the same value. Identification of the switches will also allow the companies to determine the extent of testing that will take place. +- NMC NOTIFICATION – The Network Management Centre should be notified of the conversion to enable the centre to monitor the trunk group, especially during the time of conversion/reduced capacity. The NMC may also be able to inform the Conversion Team of any special calling events which may be occurring at the time of the conversion. +- TIMER VALUES – The two interconnecting Administrations switches and STPs have many timers associated with link operation and call set-up. Since only parameters and not the actual values are stated in technical references, it is likely that the Administrations will have different time settings for the same timer. Although there is no requirement that the value of specific timers be the same in both Administrations, the sharing of the values will provide each company with additional information for trouble resolution. +- POINT CODES – If an Administration is contemplating interconnecting, it is essential that point code range information be known well in advance to enable the Administration control centre to update the STP during the scheduled split mode operation. Point codes include those of the STP, the interconnecting switches and any alias point codes. + +- FREQUENCY OF CONTINUITY TESTS – When in-band signalling is used, continuity of the trunk selected is assured by call set-up. Continuity testing is also available on CCSS No. 7 trunks. The switch will automatically send, receive and measure tones placed on the trunk prior to setting up a call. The switch will perform continuity on a circuit at a variable rate (e.g. 1 out of $n$ times where $n$ has a value of 1 to 16). The Administrations need to agree on the value of $n$ for the continuity tests. + +**3.4.2** It is necessary to conduct tests on those signalling routes which could be affected by such implementations. The purpose of the tests is to provide confidence that the software, hardware and data for a signalling system is correct in that: + +- a traffic circuit using that route can enter, or be removed from service; +- changes made to signalling and traffic routes for which circuits are already in service function correctly. + +This objective must be achieved without disruption to live traffic. + +**3.4.3** Prior to tests being made, it should be ensured that: + +- exchange data has been loaded; +- diagnostic checks of the signalling terminals in each exchange have been made; +- test equipment and facilities are available (the precise requirements are a subject for further study). + +**3.4.4** The following situations require tests. The list is not exhaustive since combinations of situations may occur. + +For each situation it is necessary to consider whether or not traffic circuits are in service and whether they are being added to or ceased or whether there is no change: + +- i) *No signalling route existing between two switching centres:* + - Signalling Transfer Point (STP) route to be provided; + - direct linkset to be provided. +- ii) *STP signalling route existing between two switching centres:* + - STP route to be added; + - STP route to be ceased; + - direct linkset to be provided. +- iii) *Direct signalling route existing between two switching centres:* + - STP route to be added; + - STP route to be ceased; + - direct linkset to be provided. +- iv) *Direct linkset to be ceased:* + - link to be provided; + - link to be ceased. + +**3.4.5** For the present, tests should be chosen from those specified as compatibility tests in Recommendations Q.781 [1], Q.782 [2], Q.783 [3], Q.767 [4] and Q.750 [5] by agreement between the Administrations concerned. The question of whether particular tests can be specified for particular situations is a matter for bilateral agreement between Administrations. The actual tests chosen will depend on the nature of the changes which have been made to the signalling network and the relative experience of the participating Administrations. + +However, when implementing a new signalling system, the following aspects should be covered: + +- Level 1 and 2 tests which cover normal and failure conditions for synchronization and Message Transfer Part (MTP) functions. +- Level 3 tests which cover the application of failure conditions in order to test single recovery arrangements. + +- Level 4 tests which cover Telephone User Part (TUP) and ISDN User Part (ISUP) call processing functions and normal STP signalling functions. Test should cover normal, abnormal, transit and call failure sequences. +- Tests on individual speech circuits, e.g. using ATME No. 2. +- Limited period, live traffic tests. + +**3.4.6** The test equipment and facilities required remain as a subject for further study. + +**3.4.7** After completion of testing, there should be an increased level of supervision on the route for a period, the duration of which should be agreed by the Administrations concerned. Generally it should not be less than one week. During this period traffic signalling performance statistics should be obtained relating to both the Message Transfer Part (MTP) and Telephone User Part (TUP) in order to confirm that the route performance is functioning correctly. These should be chosen by agreement between the Administrations concerned. Those for the MTP should be taken from Recommendation Q.752 [6] (Monitoring and measurements for Signalling System No. 7 networks). + +**3.4.8** The administrative control should receive and record for future reference the results of tests carried out. In the event of subsequent failures, a reference to these test results may be valuable to the fault location process and also a significant factor in assessing signalling system performance and fault occurrences over the long term. + +## **4 Functions and responsibilities of the administrative sub-control** + +In general, the responsibilities of the administrative sub-control with respect to its own terminal are similar to those of the administrative control. Additionally, the administrative sub-control should: + +- cooperate with the administrative control in fault localization and clearing activities as necessary; +- respond with all relevant details of investigations and fault clearance activities to the administrative control; +- advise the administrative control of any known present or future event likely to affect the operation of the signalling system(s) for which it has responsibility. + +## **5 Contact point information** + +It is essential that contact point information be exchanged between Administrations to minimize maintenance difficulties and speed fault localization and clearance activities (see Recommendation M.1510 [9]). + +## **6 Monitoring requirements for maintenance purposes** + +This clause specifies the monitoring requirements for maintenance of common channel Signalling System No. 7. + +It considers three aspects of monitoring which are as follows: + +- A monitoring facility for the signalling system which is realized in the exchange software. It would be called into operation by command when required in order to manually observe signalling sequences. It is referred to hereafter as a software monitor. +- A facility (provided by means of hardware) which allows for the connection of monitoring equipment to the signalling link, i.e. a monitoring point. +- The requirements for testing equipment which is connected at the monitoring point. + +### 6.1 The software monitor + +**6.1.1** A software monitor should be provided which will allow signals handled in the implementation of the signalling system in the SPC exchange, to be selectively output to an input/output terminal for the purpose of manually observing signalling sequences. + +It is considered that this facility should be the primary means of manually observing signalling sequences. + +**6.1.2** The software monitor should meet the following requirements: + +- It must be capable of operations without interfering with the operation of the signalling system. +- It must be capable of monitoring Message Transfer Part (MTP), Telephone User Part (TUP), Signalling Channel Control Part (SCCP) and ISDN User Part (ISUP) messages. Other user parts are the subject of further study. +- It must be capable of displaying all MTP messages which relate to specified linksets or destinations or both. It should record registration time, direction, linkset identity, link identity, signal acronym and any change of signalling link state for all messages. It must be possible to monitor several destinations and linksets simultaneously. The precise number of destinations and linksets will depend upon such factors as the size of the exchange and its position in the network (i.e. local, transit, etc.). +- Must be capable of displaying the contents of all TUP and ISUP message signal units sent and received for specified circuits or groups of circuits. It would also be useful to register the link on which the signals have been sent and record any changes to the link used. It must be possible to monitor several circuits simultaneously. The precise number of circuits will depend on such factors as the size of the exchange and its position in the network (i.e. local, transit, etc.). + +### 6.2 Monitoring point requirements + +**6.2.1** A means of connecting independent monitoring equipment to a 64 kbit/s signalling link should be provided. This facility would be used either when more information is required than the software monitor is able to provide or when verification by an independent means is required of the information supplied by the software monitor. + +The means of connection to a 64 kbit/s signalling link should be either at the 64 kbit/s level, in which case interface requirements of clause 1/G.703 [7] apply, or at the primary order level, in which case the interface requirements of clause 2/G.703 [7] (1544 kbit/s) or clause 6/G.703 [7] (2048 kbit/s) apply. + +**6.2.2** The means of connection should be such that: + +- signals can be monitored in both directions simultaneously; +- the connection of monitoring equipment does not affect the signals present on the link or on other time slots in the primary order path which carried the link; +- signals may be monitored irrespective of the current link status; +- any or all the protocol levels of any signal units on the link may be observed. + +### 6.3 Requirements of test equipment used for monitoring purposes + +Requirements for test equipment used for monitoring purposes are: + +- The equipment should be self-contained and independent of the terminal equipment of the system. +- The equipment should be able to display all signals which are necessary to be examined in order to detect faults at all levels of the signalling system. +- The form in which signals are displayed should enable them to be easily recognizable to the maintenance staff. In particular, it should be possible to display specified fields of a message or all the fields. +- The equipment should be capable of storing information from the link for later off-line examination (amount and extent of this information has yet to be determined). + +- Information should be displayed (and recorded, where applicable) to allow the operator to determine the time when a signal or message was received. +- The equipment should be able to display and store information on the link at all times. +- The equipment should have the facility to allow the maintenance staff to determine which categories of signals or messages are to be displayed. +- The equipment should allow the maintenance staff to specify conditions such as the receipt of messages or signals which would trigger the commencement of display or storage. +- When triggered, the equipment should display, in chronological order the signals which occurred prior to the triggering and after it. The number of these messages has yet to be determined. + +NOTE – It is intended that a Recommendation in the O-Series will be developed which will specify this test equipment in detail. + +## References + +- [1] ITU-T Recommendation Q.781 (1993), *Signalling System No. 7 – MTP level 2 test specification.* +- [2] ITU-T Recommendation Q.782 (1993), *Signalling System No. 7 – MTP level 3 test specification.* +- [3] CCITT Recommendation Q.783 (1988), *TUP test specification.* +- [4] CCITT Recommendation Q.767 (1991), *Application of the ISDN user part of CCITT Signalling System No. 7 for international ISDN interconnections.* +- [5] ITU-T Recommendation Q.750 (1993), *Overview of Signalling System No. 7 management.* +- [6] ITU-T Recommendation Q.752 (1993), *Monitoring and measurements for Signalling System No. 7 networks.* +- [7] CCITT Recommendation G.703 (1991), *Physical/electrical characteristics of hierarchical digital interfaces.* +- [8] CCITT Recommendation M.4010 (1992), *Inter-Administration agreements on common channel Signalling System No. 6.* +- [9] CCITT Recommendation M.1510 (1992), *Exchange of contact point information for the maintenance of international services and the international network.* \ No newline at end of file diff --git a/marked/M/T-REC-M.4110-199605-I_PDF-E/raw.md b/marked/M/T-REC-M.4110-199605-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3ee55697d8f2886933db3b656cac28b936c1284f --- /dev/null +++ b/marked/M/T-REC-M.4110-199605-I_PDF-E/raw.md @@ -0,0 +1,268 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.4110** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(05/96) + +**MAINTENANCE** + +**COMMON CHANNEL SIGNALLING SYSTEMS** + +--- + +**INTER-ADMINISTRATION AGREEMENTS +ON COMMON CHANNEL +SIGNALLING SYSTEM No. 7** + +**ITU-T Recommendation M.4110** + +(Previously "CCITT Recommendation") + +--- + +# FOREWORD + +The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). + +ITU-T Recommendation M.4110 was revised by ITU-T Study Group 4 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 12th of May 1996. + +--- + +# NOTE + +In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# CONTENTS + +| | Page | +|-------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 1 Introduction..... | 1 | +| 2 Common Channel Signalling System No. 7..... | 2 | +| 3 Aspects of SS No. 7 requiring inter-Administration agreement..... | 2 | +| 3.1 Signalling links and signalling security arrangements..... | 2 | +| 3.2 Mode of signalling..... | 4 | +| 3.3 Signalling network consideration for cross-border traffic ..... | 4 | +| 3.4 Routing label assignment..... | 4 | +| 3.5 Circuit Identification Code ..... | 4 | +| 3.6 Reset of circuit and circuit group messages..... | 4 | +| 3.7 Use of the circuit continuity check procedure ..... | 5 | +| 3.8 Choice of the time slot to be used within the primary order digital path for the signalling link ..... | 5 | +| 3.9 Choice of tests to be performed ..... | 5 | +| 3.10 Changing from one specification of the signalling system to another ..... | 5 | +| 3.11 Use of MTP Routing Verification Tests (MRVT), SCCP Routing Verification Tests (SRVT), and Circuit Validation Tests (CVT) ..... | 5 | +| 3.12 Exchange of signalling system operational measurements..... | 5 | +| 4 Timing on inter-Administration agreements ..... | 5 | +| References ..... | 6 | + +# **ABSTRACT** + +Provides the various technical aspects that need to be considered when undertaking inter-administration agreements to establish Common Channel Signalling System No. 7. + +## **KEYWORDS** + +Agreements; common channel signalling; maintenance; propagation delay; signalling security; Signalling System No. 7. + +# **INTER-ADMINISTRATION AGREEMENTS ON COMMON CHANNEL SIGNALLING SYSTEM No. 7** + +*(Melbourne 1988 approved as M.770; revised and renumbered in 1992; revised in 1996)* + +## **1 Introduction** + +The bringing into service of new Signalling System No. 7 requires that a number of agreements be made in advance by the Administrations about the responsibilities involving the following issues: + +### – *Installation and maintenance* + +#### • *Link* + +Two inter-connecting Administrations are responsible for the portion of an CCSS No. 7 link, which they maintain. Both Administrations are also responsible for ensuring that its portion of the CCSS No. 7 link(s) are installed and functioning properly. In addition, the Administrations should work cooperatively to perform CCSS No. 7 protocol tests to ensure the ability of the interfaces to correctly transmit and respond to CCSS No. 7 messages being passed between their networks. + +#### • *Trunk* + +Conversion from in-band signalling to CCSS No. 7 cannot be accomplished without a thoroughly planned process. Two Administrations implementation team should meet to discuss and identify all of the steps necessary for a successful trunk conversion. The implementation team should include individuals from both Administrations. Each Administration should establish a Cutover Committee of its own to ensure a smooth conversion; the cutover committee consisting of permanent members from the ordering, provisioning, engineering, operations, and billing discipline. + +### – *Testing* + +CCSS No. 7 Inter-Network signalling testing should be a pre-cutover requirement. MTP, ISUP and SCCP compatibility tests1), are recommended to verify the compatibility of networks during interconnection. These tests are intended to be used as a recommended set of minimum tests of the CCSS No. 7 protocol. + +### – *Diversity* + +CCSS No. 7 route diversity, which assumes a network architecture that encompasses interconnecting STPs, is defined as signalling link sets that are on physically and electrically separate routes. + +### – *Screening and translations* + +Interconnecting Administrations should discuss their routing and Gateway Screening of Network Management Messages between interconnecting STPs to ensure that all appropriate messages can be routed in the presence of route failures. + +#### – *CCSS No. 7 security* + +In the remote event that a total CCSS No. 7 failure is experienced, some means of communication between personnel in interconnecting networks may be required. Two interconnecting Administrations should determine what emergency communications are already available and/or what alternative methods, if any, will be provided. + +--- + +1) See Recommendations Q.704, Q.781, Q.782, Q.784 and Q.785. + +#### – *CCSS No. 7 Software Validation* + +CCSS No. 7 Software Validation is essential to ensure that the software products perform according to “agreed upon” Administration product requirements and that all reasonable care has been taken to identify and correct any anomalies that have the potential to negatively impact the operation of switch/signalling nodes. + +#### – *Some additional issues also need to be considered and those are:* + +- routing of circuits (cable, satellite, etc.); +- mode of operation (incoming, outgoing, both-way); +- circuit designation; +- order of selection of both-way circuit. + +This Recommendation outlines the inter-Administration responsibilities for provisioning and maintaining of the Signalling System No. 7. It deals with the physical interconnecting trunks and link(s) as well as the software necessary to support the use of the link(s) to transport CCSS No. 7 messages between Administrations. It is limited to procedures relating to the installation and maintenance of the CCSS No. 7 trunks and link(s) and associated software used to interconnect and provide services between two Administrations. + +This Recommendation also explains the principal inter-Administration agreements which must be made in advance of opening service on a Signalling System No. 7, and is provided as guidance to those Administrations intending to operate such a service. + +## **2 Common Channel Signalling System No. 7** + +Many of the aspects covered by this Recommendation relate to matters contained in the specifications of SS No. 7, as appearing in the Q.700-Series Recommendations [1]. Where appropriate, cross references to such Recommendations are given. + +Recommendations Q.701 [2], Q.721 [3], Q.767 [13] and Q.750 [14] provide functional descriptions of the Message Transfer Part (MTP), Telephone User Part (TUP), ISDN User Part (ISUP), and Operation and Maintenance Application Part (OMAP), respectively. + +The Q.780-Series Recommendations [4] provide guidance on how to test SS No. 7 (levels 2, 3 and 4). + +## **3 Aspects of SS No. 7 requiring inter-Administration agreement** + +### **3.1 Signalling links and signalling security arrangements** + +Signals for a given group of speech circuits between two exchanges may be “associated” (routed on a signalling link between the two exchanges), or “non-associated” (routed on two or more signalling links in tandem, involving one or more signal-transfer points) or a mixture of both (see 3.1.2/Q.701 [2]). + +Before entering into detailed discussions on the type of signalling security arrangements required, it is desirable that the terminal Administrations exchange information on the type and manufacturer of their international signalling point (exchange, signalling transfer point, or network database) and the options available within their existing software systems. This information will enable each Administration to have an overall view of available signalling security arrangements. It will avoid misunderstandings and thus enable rapid progress in establishing detailed arrangements. Subsequently, agreement on the following matters will be required. + +#### **3.1.1 CCSS No. 7 Link Control** + +- a) Provides trained personnel. +- b) Designates a Control office(s) for the overall responsibility for CCSS No. 7 link(s). + +- c) Cooperates with the other Administration to ensure that the CCSS No. 7 link(s) are installed in accordance with the service request. +- d) Notifies the appropriate Administration service centre when the service due date is to be changed. +- e) Sectionalizes troubles to determine if the trouble is located in its facility, interface, or application or if the trouble is in other Administration facility, interface, or application. +- f) Ensures that any manually initiated tests performed on the CCSS No. 7 link(s) or applications will not negatively affect the other Administration CCSS No. 7 network. +- g) Coordinates any changes to its translations which may require changes to other Administration translations. +- h) Cooperatively participates with the other Administration to further identify, isolate and clear troubles which cannot be sectionalized into each other portions of the link or application software. +- i) Accepts and refers trouble reports from the other Administration relating to CCSS No. 7 and the services being provided over the link(s). +- j) Provides the other Administration Notification of Maintenance Releases. +- k) Overall coordination of control responsibilities: + - i) tracking of orders; + - ii) coordination of testing; + - iii) coordination of link specific maintenance releases; + - iv) referral to appropriate groups for repair; + - v) establishing of interface agreements; + - vi) responsibility for trouble agreements; + - vii) link(s) surveillance. +- l) Maintains complete and accurate installation and repair records. +- m) Notifies the other Administration of due date jeopardy in a timely manner. +- n) Coordinates any changes to its translations which may require changes to the Administration network's translations. +- o) Maintains complete and accurate installation and repair records. +- p) Provides a trouble reporting number(s) that is readily accessible 24 hours, 7 days a week. + +Some additional agreement on the following matters will be necessary for the reliability of CCSS No. 7 interconnection: + +- i) The use of "associated" and/or "non-associated" modes of signalling. +- ii) The choice of Signalling Transfer Points (STPs) in the case where the "non-associated" mode of signalling is used. +- iii) Security measures against signalling network link failure, e.g. the use of load sharing between link sets. If load sharing between link sets is to be used, agreement must be reached as to the number of link sets involved. +- iv) Alternative routing within the signalling network in the event of failure of a link set, i.e. if load sharing is not used, which STPs are available for a given signalling network relation, and the order of selection of these. Due regard must be paid to the limitation of the number of STPs in tandem in a given signalling network relation (see clause 5/Q.705 [5]). +- v) The routing of the signalling network links must ensure that the propagation delay of the links is as low as possible, and not significantly higher than that of the speech circuits which are served by Signalling System No. 7. This is to minimize the initial speech clipping of the verbal answer from the called party. The above factors must also be considered in any restoration plans, although the non-availability of links may force Administrations to accept the possibility of clipping under failure conditions. + +- vi) The nature of the signalling network link to be used, e.g. 4.8 kbit/s analogue or 64 kbit/s digital, transmission routing, etc. +- vii) The method of error correction to be employed in a given signalling relation, i.e. basic or preventive cyclic retransmission (see clause 5/Q.703 [6]). +- viii) Emergency restart conditions. (If there is automatic allocation of signalling terminals or signalling data links at the end of a signalling link, it must be ensured that the value (T2) of the time-out is different at each end (see 7.3/Q.703 [6] and 3.4.3/Q.704 [7]).) +- ix) For security reasons, the separation of routing of signalling links has to be considered when selecting higher order paths. + +### 3.2 Mode of signalling + +Signalling System No. 7 provides for two basic modes of sending signalling information namely, “*en bloc*” or “overlap” (see Recommendation Q.724 [8]). + +### 3.3 Signalling network consideration for cross-border traffic + +For cross-border traffic between signalling points, a bilateral agreement needs to be made for the routing label assignment of signalling point codes. + +Two alternative arrangements are described in clause 6/Q.705 [5]. One arrangement provides for signalling points which are handling cross-border traffic to be given signal point codes taken from the international numbering plan contained in Recommendation Q.708 [9]. The other provides for these signalling points to be identified by common national point codes. + +### 3.4 Routing label assignment + +The routing label is that part of the message label which contains the information necessary to deliver the message to its destination point. It comprises the following (see 2.2/Q.704 [7]): + +- Destination Point Code (DPC); +- Originating Point Code (OPC); +- Signalling Link Selection (SLS) field or Signalling Link Code (SLC). + +DPC and OPC labelling will be in accordance with Recommendation Q.708 [9]. However, it may be necessary to have a bilateral agreement for the SLS so that it can be assigned individually to signalling links. + +### 3.5 Circuit Identification Code + +The Circuit Identification Code (CIC) indicates one speech circuit among those directly interconnecting the destination and the originating points. The allocation of CICs to individual circuits is determined by bilateral agreement and/or in accordance with predetermined rules. See 2.2.3/Q.723 [10]. + +### 3.6 Reset of circuit and circuit group messages + +In systems which maintain status in memory, there may be occasions when the memory contains errors. In such cases the circuits must be reset to the idle condition in both exchanges to make them available for new traffic. Since the exchange with the erroneous memory has lost status information (idle, busy outgoing, busy incoming, blocked, etc.), reset-circuit signals or a circuit group reset should be sent as appropriate for the affected circuits (see 1.15/Q.724 [8]). + +Under certain fault conditions however, where a large number of circuits is involved, it is possible that some realizations of SS No. 7 terminal equipment will be unable to process the volume of reset messages generated. It is necessary, therefore, that Administrations agree bilaterally whether circuit and circuit group messages should both be used. + +### **3.7 Use of the circuit continuity check procedure** + +Because in SS No. 7 the signalling information does not pass over the circuit carrying the speech path, capabilities are provided for making an in-band continuity check of the circuit (see 1.4/Q.724 [8]). + +Use of the continuity check procedure on circuits will depend upon the type of transmission system(s) used (e.g. analogue, digital, mixed analogue/digital, DCME, PCME) for the circuit, and whether end-to-end supervision of the transmission path is available and is indicated to the switching system. A continuity check may be applied on a call by call basis, or on a statistical basis only. Where end-to-end transmission path supervision is not available, continuity checks are advised. Any exceptions to this are for bilateral agreement. + +### **3.8 Choice of the time slot to be used within the primary order digital path for the signalling link** + +In the case where time slot 16 is utilized for circuit supervision purposes (see A.1/Q.33 [11] and clause 7/Q.50 [12]), it is necessary to agree bilaterally on which time slot within the primary order digital path should be used for the signalling link. + +### **3.9 Choice of tests to be performed** + +Before bringing into service the first SS No. 7 link between two Administrations, a bilateral agreement has to be made on which compatibility and pre-service tests have to be performed (see Recommendations Q.781, Q.782, Q.783 [4], Q.767 [13] and Q.750 [14]). + +### **3.10 Changing from one specification of the signalling system to another** + +If an Administration changes from one version of the specification of the signalling system to another, distant Administrations should be informed as a precautionary measure before the change takes place, and to agree on the necessary tests, since potential interworking problems can then be anticipated. It is desirable therefore that Administrations should be aware of the need for, and agree to, this exchange of information. + +### **3.11 Use of MTP Routing Verification Tests (MRVT), SCCP Routing Verification Tests (SRVT), and Circuit Validation Tests (CVT)** + +Signalling System No. 7 provides for test facilities MRVT, SRVT and CVT (see Recommendation Q.750 [14]) and Administrations will need to discuss and agree on the scope and constraints of operating such functions across network boundaries. + +### **3.12 Exchange of signalling system operational measurements** + +Signalling System No. 7 provides for operational measurements (see Recommendation Q.752 [15]), and Administrations will need to discuss and agree on the scope and constraints for exchanging such measurements for the mutually effective management and maintenance of common channel signalling networks across network boundaries. + +## **4 Timing on inter-Administration agreements** + +Due to the differing practices and procedures of Administrations, no specific timetable for the inter-Administration agreements necessary on SS No. 7 can be offered. However, experience indicates that initial discussions between Administrations concerning the implementation of a new common channel signalling system should preferably commence about two years prior to the required "ready for service" date. + +## References + +- [1] Recommendations Q.700 to Q.795, *Specifications of Signalling System No. 7*. +- [2] ITU-T Recommendation Q.701 (1993), *Functional description of the Message Transfer Part (MTP) of Signalling System No 7*. +- [3] CCITT Recommendation Q.721 (1988), *Functional description of the Signalling System No. 7 Telephone User Part (TUP)*. +- [4] Recommendations Q.780 to Q.783, *Signalling System No. 7 test specification*. +- [5] ITU-T Recommendation Q.705 (1993), *Signalling System No. 7 – Signalling network structure*. +- [6] ITU-T Recommendation Q.703 (1993), *Signalling System No. 7 – Signalling link*. +- [7] ITU-T Recommendation Q.704 (1993), *Signalling System No. 7 – Signalling network functions and messages*. +- [8] CCITT Recommendation Q.724 (1988), *Specifications of Signalling System No. 7 – Signalling procedures*. +- [9] ITU-T Recommendation Q.708 (1993), *Numbering of international signalling point codes*. +- [10] CCITT Recommendation Q.723 (1988), *Formats and codes*. +- [11] CCITT Recommendation Q.33 (1988), *Protection against the effects of faulty transmission on groups of circuits*. +- [12] ITU-T Recommendation Q.50 (1993), *Signalling between Circuit Multiplication Equipments (CME) and International Switching Centres (ISC)*. +- [13] CCITT Recommendation Q.767 (1991), *Application of the ISDN user part of CCITT Signalling System No. 7 for international ISDN interconnections*. +- [14] ITU-T Recommendation Q.750 (1993), *Overview of Signalling System No. 7 management*. +- [15] ITU-T Recommendation Q.752 (1993), *Monitoring and measurements for Signalling System No. 7 networks*. \ No newline at end of file diff --git a/marked/M/T-REC-M.450-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/M/T-REC-M.450-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..874f572460e3711a6cda6f6874a61b260709fa72 --- /dev/null +++ b/marked/M/T-REC-M.450-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:514009a01d0c2fe8efba854cfb96450e83ea3528c6e86f865e26e32227330d33 +size 27478 diff --git a/marked/M/T-REC-M.450-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.450-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.450-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.470-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.470-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd315b4c7bee239c1ee4fd9eda9a90a56f480969 --- /dev/null +++ b/marked/M/T-REC-M.470-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba954e6b824197bc803bd1b4745836e940210f6b7003b7c41d46aad8930022a +size 7540 diff --git a/marked/M/T-REC-M.470-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.470-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..17f2a6a1f1322e125693875aaf077cfb499df1de --- /dev/null +++ b/marked/M/T-REC-M.470-198811-I_PDF-E/raw.md @@ -0,0 +1,73 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.470** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**SETTING UP AND LINING UP ANALOGUE +CHANNELS FOR INTERNATIONAL +TELECOMMUNICATION SERVICES** + +**ITU-T Recommendation M.470** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.470 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SETTING UP AND LINING UP ANALOGUE CHANNELS FOR INTERNATIONAL TELECOMMUNICATION SERVICES** + +## **1 Check of channel-translating equipment** + +The translating equipment, before it is connected to the ends of the link, must be checked and adjusted to ensure that it meets CCITT Recommendations and the other relevant specifications. The check should include a general visual inspection and vibration tests, if applicable. This is of particular importance if the equipment has remained unused since acceptance tests were carried out after installation. + +## **2 Setting up and lining up the analogue channels** + +### **2.1 *Measurement and adjustment of levels*** + +After the group link has been set up, and the channel-translating equipment at each end of the group link has been connected and checked, the channels are adjusted as follows. + +An 1020 Hz test1) signal is sent over each channel in turn at a level of $-10$ dBm0. At the transmitting end, the channel-translating equipment is adjusted so that the sideband level on each channel at its output is as near to nominal as possible. At the receiving end, the channel-translating equipment should then be adjusted to bring the received level on each channel as near as possible to its nominal value. + +### **2.2 *Checking the analogue channel performance*** + +Channel performance measurements are only required when the need is indicated during circuit line-up. On such occasions the parameters to be checked will depend on the particular difficulty experienced during circuit line-up. + +## **3 Check level of line signalling** + +In the case of groups which are intended to be used for telephone circuits employing Signalling System R2, the checks of signalling level stipulated in the Specifications of Signalling System R2 should be made [2]. + +For other signalling systems, the check of signalling level should be carried out at the circuit line-up stage (see Recommendation M.580, § 8). + +# **References** + +- [1] CCITT Recommendation *1020 Hz reference test frequency*, Vol. IV, Rec. O.6. +- [2] CCITT Recommendations *Specifications of Signalling System R2*, Vol. VI, Recs. Q.400 to Q.490. + +--- + +1) For further information about the choice of the test signal frequency, refer to Recommendation O.6 [1]. \ No newline at end of file diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1b8c317a0084dd02096ea5cb3bc074a3ec1c307 --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:effa3c7d1f32929bc977c856d628c45cbf53bed05b8bc4960e4e381c05829c9e +size 135871 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75ef5417969bcd56a06d339236a8c5cd584193b9 --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa9e08bf8ebd5012ad639bf010f70de34621bbc89965a96f958ba3bf9396febf +size 20191 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2cc240ab3bf92be843370a4ec43f241a1700693 --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126af16939bb1516ae7e0cdf857548f1de4f7ebfc9f494eeb79f0b4e9673eb62 +size 35609 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae72e2ef019333378f289dbfe13cef1afa543fe1 --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/c3c305cefbac2e7b13be34ab87054d1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70ed4a468b9a6ee4b2402ebef7903835f5ca4013bc9f9f646a5f9a99759fdda2 +size 56789 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31a22371d22900b5d0dd779c15f67e03eb35261e --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dfded54da7cd5d348fccbd8f5496b3658b07666d266a7a5f2db4179f291ce28 +size 18062 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/e2c1c672349c10dccb2563eff6d8260e_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/e2c1c672349c10dccb2563eff6d8260e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7288f3abe0c1aba013c7c67f1d600641214cb4fa --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/e2c1c672349c10dccb2563eff6d8260e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84e42a63f8de96d9c9dc89f704a90053ab9efbf2adf237ef8d45f930cb81e391 +size 26602 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg b/marked/M/T-REC-M.495-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8de37ec45f2d6a1af1ecbeca742459733eb404b1 --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/e394c2b5c61344f6a12397f430086072_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f77699fc16c0db1f5f8a09eaaddb4e2a93f497da60078dd3c8aefef69aea4299 +size 9876 diff --git a/marked/M/T-REC-M.495-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.495-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..92a606df18d384dcaaf57c28dbd60378495af09b --- /dev/null +++ b/marked/M/T-REC-M.495-198811-I_PDF-E/raw.md @@ -0,0 +1,429 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.495** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: INTERNATIONAL TRANSMISSION +SYSTEMS (ANALOGUE)** + +--- + +**TRANSMISSION RESTORATION AND +TRANSMISSION ROUTE DIVERSITY: +TERMINOLOGY AND GENERAL PRINCIPLES** + +**ITU-T Recommendation M.495** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.495 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **TRANSMISSION RESTORATION AND TRANSMISSION ROUTE DIVERSITY: TERMINOLOGY AND GENERAL PRINCIPLES** + +## **1 Purpose of transmission restoration and transmission route diversity** + +The purpose of transmission restoration and transmission route diversity is to protect the continuity and quality of international telecommunication services by minimizing the effects of potential effects of a transmission failure. + +This Recommendation applies to both analogue and digital transmission. + +*Note* – This Recommendation may also apply in the case of hazardous conditions. + +## **2 Causes of transmission failures** + +The causes of transmission failures can be divided into three major categories: + +- equipment failure: this can be reduced by improving equipment reliability; +- outages due to the operating organization. For example, maintenance work or human errors; +- external causes which are very difficult to prevent and for which specific protection might be needed. For example weather conditions or excavation work. + +In this Recommendation, failures or faults that are referred to may be either total or partial failures or faults. The relevant terminology concerning failures and faults can be found in Supplement No. 6 [1]. + +## **3 Definitions concerning transmission restoration and transmission route diversity** + +The purpose of this terminology is to define a vocabulary which can be used in connection with transmission restoration and transmission route diversity. + +*Note* – In this terminology, the term “link” is used as a generic term for digital section, digital path, group link or section, supergroup link or section, mastergroup link or section, supermastergroup link or section, line section, section and line link. + +### **3.1 Basic concepts** + +#### **3.1.1 transmission restoration** + +The different actions taken in order to restore the transmission of a signal affected by a transmission fault. + +#### **3.1.2 transmission restoration function** + +The ability to perform under stated conditions and within given time constraints the transmission restoration. + +*Note 1* – This function is aimed at increasing the transmission availability; it can provide transmission link supervision and control, the sending and receiving of control and check signals, and the changeover from normal to an alternative link, if necessary by assembling links. + +*Note 2* – This function can allow the restoration of failed transmission systems, links, groups, digital blocks, equipment, etc., as well as the restoration for maintenance purposes such as planned outages, or to remedy conditions that affect transmission such as fading. + +*Note 3* – The transmission restoration function can be implemented by equipment that is dedicated to it, or by equipment that has other functions, such as, for example, automatic digital distribution frames. + +#### **3.1.3 transmission restoration function: direct transmission restoration (protection link switching)** + +Direct transmission restoration is that category of transmission restoration function in which one transmission link between two stations is substituted for another between those two stations. + +*Note* – This reflects a configuration in which M links protect N links, or in which N + M links give redundancy to a relation requiring N links, with the extremities of all links in the same locations. It is recommended to use the expression N + M direct transmission restoration to designate such a configuration. See Figure 1/M.495. + +![Diagram of an N + M direct transmission restoration system (protection link switching) between Station A and Station B.](2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg) + +The diagram shows two rectangular blocks labeled 'Station A' and 'Station B'. Between them are two sets of parallel lines. The top set is labeled 'Normal links (N)' and the bottom set is labeled 'Restoration links (M)'. Each set consists of three lines. A small oval is drawn around each set of lines. The text 'T0400820-87' is located to the right of Station B. + +Diagram of an N + M direct transmission restoration system (protection link switching) between Station A and Station B. + +FIGURE 1/M.495 + +**N + M direct transmission restoration system +(protection link switching)** + +#### **3.1.4 transmission restoration function : automatic or semi-automatic transmission rerouting (protection network switching)** + +Automatic or semi-automatic transmission rerouting is that category of transmission restoration function in which transmission links are assembled together and substituted for another link. + +*Note* – This reflects a configuration in which a certain number of links form a restoration network and protect normal links. Within a given transmission station, or for a given switching equipment, M links protect N links. It is recommended to use the expression N + M automatic transmission rerouting to designate such a configuration. + +Figure 2/M.495 shows an example. In Station A, M restoration links can be used for restoration of N normal. A link between A and B can be restored, for example, directly or via C. + +![Diagram of an N + M automatic transmission rerouting system (protection network switching) involving Station A, Station B, and Station C.](6324b252294c0f5d4e34dad4a1202075_img.jpg) + +The diagram shows three rectangular blocks: 'Station A' (top left), 'Station B' (top right), and 'Station C' (bottom center). 'Normal links' are shown as three parallel lines between Station A and Station B, and between Station B and Station C. 'Restoration links' are shown as three parallel lines forming a triangle between Station A, Station B, and Station C. Small ovals are drawn around the link sets between A and B, A and C, and B and C. The text 'T0400830-87' is located to the right of Station C. + +Diagram of an N + M automatic transmission rerouting system (protection network switching) involving Station A, Station B, and Station C. + +FIGURE 2/M.495 + +**N + M automatic transmission rerouting system +(protection network switching)** + +#### 3.1.5 transmission restoration function: 1 + 1 restoration + +1 + 1 restoration is that category of transmission restoration function in which one transmission link is substituted for another associated link, generally on another transmission route. See Figure 3/M.495. + +![Diagram of a 1 + 1 restoration system showing a normal link and a restoration link between two equipment blocks.](e394c2b5c61344f6a12397f430086072_img.jpg) + +The diagram illustrates a 1 + 1 restoration system. It features two rectangular blocks representing transmission equipment, one on the left and one on the right. Two horizontal lines connect these blocks: the top line is labeled 'Normal link' and the bottom line is labeled 'Restoration link'. Each line has a small circle with a vertical line passing through it, representing a switch or tap point. The identifier 'T0400840-87' is located to the right of the bottom block. + +Diagram of a 1 + 1 restoration system showing a normal link and a restoration link between two equipment blocks. + +FIGURE 3/M.495 +**1 + 1 restoration system** + +#### 3.1.6 transmission restoration function: manual transmission rerouting + +Manual transmission rerouting is that category of transmission restoration function in which one transmission link is replaced manually by another when a complete or partial transmission route failure has occurred or when the normal route restoration link is not available due to a previous or simultaneous interruption, or when there is no such restoration link provided. + +*Note* – Such rerouting is normally effected using plugs and cords. + +#### 3.1.7 transmission restoration control function + +This is the function which decides whether restoration is necessary on the basis of information from the link supervision system or link alarms. + +*Note* – The control function might be included in a specific equipment, or in the transmission restoration equipment itself, or within a restoration control centre. Control decisions can also be taken by people in, for example, a control centre. + +### 3.2 Systems and equipment + +#### 3.2.1 transmission restoration system + +A system that can be used to implement the transmission restoration function. An example is shown in Figure 4/M.495. + +#### 3.2.2 transmission restoration equipment + +The part of the transmission restoration system that switches the transmission from the normal link to a restoration link. + +#### 3.2.3 normal transmission link/equipment; normal digital block, group, supergroup, etc. + +A transmission link/equipment or a digital block, group, supergroup, etc., which is used for transmission under normal operating conditions. + +#### 3.2.4 restoration link/equipment + +A transmission link/equipment which is used for transmission when the normal link/equipment is not available. + +*Note 1* – A restoration link or equipment is generally idle under normal operating conditions, but might be used under these conditions by low-priority traffic for which a lower degree of service availability is accepted. + +*Note 2* – Note 1 may not apply to 1 + 1 type restoration system where both links are carrying the traffic. + +#### 3.2.5 restoration network + +The network formed by all restoration links. + +![Diagram of a transmission restoration system architecture.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +The diagram illustrates a transmission restoration system architecture. At the top, a 'Restoration control centre' is connected via dashed lines to a 'Control equipment' located within a 'Controlled station(s)'. The 'Controlled station(s)' is represented by a large dotted rectangle. Inside this station, the 'Control equipment' is connected to a 'Link/equipment supervision' block. Below this, a 'Transmission restoration equipment' is shown. To the right of the station, there are two sets of horizontal lines: 'N normal links/equipments' and 'M restoration links/equipments'. Each of these lines passes through a small box labeled 'a)'. A bracket on the right side of the station, labeled 'Control circuits', encompasses the connections between the control equipment and the supervision block. The entire assembly of the controlled station and its internal equipment is contained within a larger rectangle labeled 'Restoration unit'. The reference code 'T0400850-87' is located at the bottom right of the diagram. + +Diagram of a transmission restoration system architecture. + +a) Line terminal equipments and/or multiplex equipments + +*Note* – This illustration is only an example. The structure of a transmission restoration system can be different (for example, the control function might be implemented within a restoration control centre, with no specific equipment). + +FIGURE 4/M.495 +Example of transmission restoration system + +### 3.3 Control (see also Figure 5/M.495) + +#### 3.3.1 control equipment + +An equipment that is used to implement the transmission restoration control function. + +#### 3.3.2 restoration control centre + +A centre supervising all or part of normal and restoration transmission systems. + +*Note* – A restoration control centre can be included within a control centre which is not dedicated to restoration. + +#### 3.3.3 controlled station + +The station that has its systems, links and other maintenance elements supervised, where the information and commands for switching are sent to and received from, the control centre, and where the switching is effected. + +#### 3.3.4 restoration unit + +All normal and restoration links and associated switching equipment capable of being controlled from a particular control centre. + +*Note* – Some networks areas may be controlled from more than one control centre. + +#### 3.3.5 control circuit + +A circuit used for the transmission of restoration control information. + +![Diagram of restoration control network showing a restoration control centre connected to three controlled stations via control circuits and transmission lines.](e2c1c672349c10dccb2563eff6d8260e_img.jpg) + +The diagram illustrates a restoration control network. At the top is a circle labeled 'Restoration control centre'. Below it are three squares, each labeled 'Controlled station'. Thin lines represent 'Control circuit' and thick lines represent 'Transmission'. The restoration control centre is connected to each of the three controlled stations by a thin control circuit line. The controlled stations are interconnected by thick transmission lines, forming a mesh. A label 'T0400860-87' is present near the bottom right station. + +Diagram of restoration control network showing a restoration control centre connected to three controlled stations via control circuits and transmission lines. + +FIGURE 5/M.495 + +##### Restoration control + +### 3.4 Time intervals associated with transmission restoration processes + +The following time intervals are intended to describe the different time components between the failure of a signal and its restoration. These time intervals can be used to characterize those transmission restoration systems, equipment etc. See also figure 6/M.495. + +![A timeline diagram illustrating the sequence of events in a transmission restoration process. The horizontal axis represents 'Time' and is marked with seven vertical lines representing key events: 1. Potential failure, 2. Recognition of potential failure, 3. Start of restoration procedure, 4. Last control signal or command received, 5. Last restoration operation finished, 6. Transmission fully restored. The time intervals between these events are labeled as follows: T1 (Detection time) between 1 and 2; T2 (Waiting time) between 2 and 3; T3 (Restoration procedure time) between 3 and 4; T4 (Restoration transfer time) between 4 and 5; T5 (Recovery time) between 5 and 6. Additionally, Tc (Confirmation time) is shown as the interval from 1 to 3; Tt (Transfer time) as the interval from 3 to 5; and Tr (Restoration time) as the interval from 1 to 5. The diagram is labeled 'T0400870-87' at the bottom right.](c3c305cefbac2e7b13be34ab87054d1e_img.jpg) + +$T_1$ Detection time                      $T_c$ Confirmation time + $T_2$ Waiting time                        $T_t$ Transfer time + $T_3$ Restoration procedure time    $T_r$ Restoration time + $T_4$ Restoration transfer time + $T_5$ Recovery time + +A timeline diagram illustrating the sequence of events in a transmission restoration process. The horizontal axis represents 'Time' and is marked with seven vertical lines representing key events: 1. Potential failure, 2. Recognition of potential failure, 3. Start of restoration procedure, 4. Last control signal or command received, 5. Last restoration operation finished, 6. Transmission fully restored. The time intervals between these events are labeled as follows: T1 (Detection time) between 1 and 2; T2 (Waiting time) between 2 and 3; T3 (Restoration procedure time) between 3 and 4; T4 (Restoration transfer time) between 4 and 5; T5 (Recovery time) between 5 and 6. Additionally, Tc (Confirmation time) is shown as the interval from 1 to 3; Tt (Transfer time) as the interval from 3 to 5; and Tr (Restoration time) as the interval from 1 to 5. The diagram is labeled 'T0400870-87' at the bottom right. + +FIGURE 6/M.495 + +#### **Defined restoration times** + +#### **3.4.1 detection time, $T_1$** + +Time interval between a potential failure of transmission and the recognition of that potential failure. + +#### **3.4.2 waiting time, $T_2$** + +Time interval after the recognition of a potential failure and its confirmation as a fault requiring restoration. + +#### **3.4.3 restoration procedure time, $T_3$** + +Time interval between the confirmation of a fault and completion of the processing and transmission of the control signals required to effect restoration. + +#### **3.4.4 restoration transfer time, $T_4$** + +Time interval between completion of the processing and transmission of the control signals required to effect restoration and the completion of transmission restoration operations. + +#### **3.4.5 recovery time, $T_5$** + +Time interval between the completion of transmission restoration operations and the full restoration of failed transmission. + +*Note* – This may include the verification of switching operations, re-synchronization of digital transmission, etc. + +#### **3.4.6 confirmation time, $T_c$** + +The time from the occurrence of the potential failure to the instant when the fault is confirmed as requiring a restoration: $T_c = T_1 + T_2$ . + +#### 3.4.7 **transfer time, $T_t$** + +The time interval after the confirmation that a fault requires a restoration to the completion of the transmission restoration operation; $T_t = T_3 + T_4$ . + +#### 3.4.8 **restoration time, $T_r$** + +The time from the occurrence of the failure to the restoration of the faulty transmission: + +$$T_r = T_1 + T_2 + T_3 + T_4 + T_5 = \text{confirmation time} + \text{transfer time} + T_5.$$ + +*Note* – An apparent fault might be detected by an equipment and not confirmed after the confirmation operations. In this case, only times $T_1$ and $T_2$ are relevant. + +### 3.5 *Software related terms* + +#### 3.5.1 **network image** + +Software description of the transmission network to be protected. + +#### 3.5.2 **fault definition program** + +Program which collects fault information and defines faulty transmission links. + +#### 3.5.3 **restoration algorithm** + +Method for forming restoration links for faulty normal transmission links. + +#### 3.5.4 **restoration control program** + +A decision making program which controls restoration processes. + +### 3.6 *Route diversity* + +#### 3.6.1 **transmission route** + +A transmission facility on a specific medium used by a certain number of transmission systems between two stations. + +*Note 1* – For example, one cable between two stations could be regarded as one transmission route (whatever the number of systems using this cable might be) and a radio system between these two points could be regarded as an other route. + +*Note 2* – This definition represents a physical route; this is different from the term “route” which is defined in the Recommendations E.600 [2], Q.9 [3] and Z.341 [4], which represents a logical route. + +#### 3.6.2 **transmission route diversity** + +The provision of at least two links between two nodes in a transmission network which are routed over different transmission routes. + +*Note* – In case of a failure of one link, transmission route diversity allows some traffic between the two nodes still to be carried over the remaining link(s). + +## 4 **Principles of transmission restoration and transmission route diversity** + +### 4.1 *General principles* + +4.1.1 In case of a fault of an international transmission system, complete and fast transmission restoration is a maintenance objective. Line and terminal equipment allocated for transmission restoration should be left available to the extent that the objective can be achieved. This equipment may sometimes be used for other purposes as required, e.g., planned outages. + +4.1.2 When planning new routes or changes to existing routes, account should be taken of the requirements of restoration. + +4.1.3 The responsibility for restoration should be based on the following principles in the case of an interruption due to a fault or to a planned outage of a transmission link: + +- a) when the fault of an international transmission link takes place on a national section, restoration is solely the affair of the Administration involved; +- b) when a fault takes place on an international section of an international route, restoration is the affair of the Administrations of the two countries directly involved, even if Administrations of other countries are concerned; +- c) in the case of a satellite fault, the responsibility to restore the satellite capability rests with the designated satellite system manager; +- d) restoration should be effected in the transmission network at the highest order of link permitted by the network (group link, supergroup link, etc.) taking into account the service which is carried; +- e) it would be desirable to arrive, if possible, at complete restoration based upon bilateral and/or multilateral agreements. Special consideration is necessary when, in practical cases, complete restoration cannot be achieved. When complete restoration is not possible the links to be restored should contain those circuits that satisfy the special needs of the Administrations involved to the extent possible. Sufficient restoration capacity should therefore be provided to reflect the special interests of each Administration involved. Certain services might be considered as priority services by bilateral agreements; in this case, they should be grouped on groups or digital blocks that are restored in priority; +- f) in the case where it is not possible to restore all circuits through the procedures envisaged under a), b), and c), each terminal Administration should make the necessary agreements to use all available routes lending themselves to restoration. + +### 4.2 *Transmission restoration systems* + +The following points regarding transmission restoration systems should be noted: + +- a) in the case when a transmission restoration network exists, it might be used under normal operating conditions for preemptible traffic. However, the restoration time might be a little longer when low priority traffic has to be interrupted before the restoration; +- b) transmission restoration systems might be used for specific maintenance purposes such as planned outages. In this case, a planned restoration should be effected in such a way that the resulting impact on transmission quality and availability is minimized; +- c) certain normal transmission links may have a priority restoration, with preemption on restoration links. On these links should be routed groups and digital blocks bearing services that are considered having priority; +- d) in general, when the normal transmission link can be used again, transmission is switched back from the restoration link. This switch-back can be made manually, semi-automatically or automatically; it should be made in such a way that the resulting impact on transmission quality and availability is minimized; +- e) in certain cases, restoration of transmission might be effected separately for the receive and transmit directions; +- f) in case of automatic or semi-automatic restoration systems, there should be a possibility of manual action for a forced restoration or an inhibition. This action has to be possible semi-automatically for automatic restoration systems; +- g) transmission restoration systems should be built in such a way that a fault of one of its components or a maintenance action on it will result, in most cases, in minimal impact on normal transmission quality and availability. + +### 4.3 *Transmission route diversity* + +Transmission route diversity is a way of protecting circuits groups (a number of circuits with the same terminal points) against the effects of transmission failures. Circuit groups are divided into smaller groups which are carried on different transmission routes. In this way, a transmission faults of one transmission route does not completely interrupt the service. + +For example, 60 public circuits between two exchanges can be divided into 2 groups of 30 circuits routed on cable and radio link. See Figure 7/M.495. + +![Diagram illustrating diverse routing between Exchange A and Exchange B. Two parallel paths are shown: an upper 'Radio link' and a lower 'Cable link'. Each path contains '30 public circuits'. The diagram is labeled 'T0400880-87'.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +The diagram shows two nodes, 'Exchange A' on the left and 'Exchange B' on the right, connected by two distinct transmission paths. The upper path is labeled 'Radio link' and contains '30 public circuits'. The lower path is labeled 'Cable link' and also contains '30 public circuits'. A reference code 'T0400880-87' is located at the bottom right of the diagram. + +Diagram illustrating diverse routing between Exchange A and Exchange B. Two parallel paths are shown: an upper 'Radio link' and a lower 'Cable link'. Each path contains '30 public circuits'. The diagram is labeled 'T0400880-87'. + +FIGURE 7/M.495 + +#### **Diverse routing** + +### 4.4 Restoration times + +4.4.1 It is useful to consider the restoration system in terms of the component time intervals involved. Some of these have been identified in the above terminology. These time intervals vary depending on whether the transmission system is analogue or digital. In the case of digital, the bit rate is also a factor. + +4.4.2 It might be necessary, when specifying restoration times, and especially the confirmation time, to examine the different transmission restoration systems that might be used at the same time on a given link: for example, a 1 + 1 restoration system with its normal link beared by a transmission system protected by an N + 1 direct transmission restoration system. + +4.4.3 The aim for restoration time performance objective will come from service interruption objectives which were currently under study by CCITT. + +There might be different aims for various types of failure and of restoration type: single transmission system or complete transmission route failure; automatic, semi-automatic or manual restoration, etc. + +### 4.5 Restoration criteria + +The criteria used to decide if a restoration action is necessary can be based upon transmission fault and also occurrence of bad quality (signal-to-noise ratio for analogue transmission, bit error ratio, thresholds of Recommendation G.821 [5] for digital transmission, etc.). + +## 5 Methods of transmission restoration + +### 5.1 General + +The links provided for transmission restoration can be used in the event of both faults and planned outages. Methods for restoration will necessarily vary according to the particular system and circumstances involved. They will include transmission restoration and physical repair using manual, semi-automatic or fully automatic methods. In order to choose the restoration method, it is appropriate for the Administrations involved to take into account the following elements in a bilateral or multilateral agreement: + +- the level of availability desired; +- the facilities that may be used for restoration; +- the economics related to the particular system being considered; +- the compatibility of transmission equipment at appropriate locations (for example analogue/digital, satellite/coaxial etc.). + +### 5.2 *Automatic restoration* + +Automatic restoration is possible with the use of automatic restoration systems, which can be of three main types: + +- 1 + 1 transmission restoration; +- direct transmission restoration (protection link switching); +- automatic transmission rerouting (protection network switching). + +The functional organization of these restoration systems is described within Recommendation M.496. + +### 5.3 *Semi-automatic restoration* + +Specific equipment and transmission restoration systems are introduced in order to allow automatic restoration. As any interruption of service is undesirable, especially in the case of planned outages, this equipment should generally allow the remote manual activation and control of automatic transmission rerouting systems in order to change from the normal route to a previously set-up and tested restoration route. + +### 5.4 *Manual restoration* + +The complexity of the evolving international transmission network demands flexibility in any transmission restoration arrangement. In general, transmission restoration can be achieved by manual switching, for example on analogue or digital distribution frames. In this case a distribution frame is necessary. The links used for transmission restoration are arranged in a network configuration with particular restoration requirements being met by using such links either singly or connected in tandem. This arrangement is flexible and maximizes the use of international restoration links which are expensive to provide and therefore limited in number. + +## 6 **Considerations involved in planning transmission restoration systems** + +### 6.1 *Parameters to be taken into account:* + +Restoration arrangements for transmission systems may be applied at any level in the multiplex hierarchy that is bilaterally or multilaterally agreed upon. The switching configuration itself may be a 1 + 1 or more complex N + M relationship, involving N normal links being protected by M restoration links. When planning a physical restoration system on an international basis the following considerations, among others, should be taken into account in the context of the desired availability and the economics involved. + +- a) availability of restoration capacity, taking into account the number of restoration and normal links; +- b) transmission characteristics of the restoration link(s); +- c) services to be restored and the acceptability of additional delay to confirm a fault and minimize switching (see § 4.4 of this Recommendation); +- d) threshold at which fault is to be established (this may be adjustable in a range) (see § 4.5); +- e) switching level in the multiplex hierarchy and whether any restorative switching is to be applied at more than one level; +- f) manual or automatic switch-back techniques; +- g) use of telemetry and control system, if required; +- h) the need of a unidirectional or bidirectional system; +- i) apportionment to the switches of the maximum degradation of the transmission characteristics (for example, maximum crosstalk, maximum unavailability . . . ); +- j) desirable restoration time (see § 4.4 of this Recommendation); +- k) changed propagation time resulting from restoration over another route (this may be particularly important in the case of data transmission); +- l) other functions that might be included in restoration equipment for maintenance purposes. + +### 6.2 *Restoration network planning* + +The restoration network should be dimensioned according to the objectives of the restoration capability for faulty transmission systems or equipment, as well as for planned outages. + +One example of a method for dimensioning a restoration network without the help of simulation software is to add systematically a certain proportion of restoration links to the normal links. + +Another method is to dimension the restoration network for the restoration of certain priority services in case of a single transmission route or transmission link fault. A priority protection for specific services would allow these services to have a better availability. This would allow the planning of a smaller and therefore cheaper restoration network that would be required for a systematic restoration of all transmission routes failures. The restoration network obtained in such a way would not only cost less in investment, but it would also serve to restore non-priority traffic when restoration links are available. + +## References + +- [1] CCITT Supplement *Terms and definitions for quality of service, network performance, dependability and trafficability studies*, Fascicle II.3, Supplement No. 6. +- [2] CCITT Recommendation *Terms and definitions of teletraffic engineering*, Vol. II, Rec. E.600. +- [3] CCITT Recommendation *Vocabulary of switching and signalling terms*, Vol. VI, Rec. Q.9. +- [4] CCITT Recommendation *Glossary of terms*, Vol. VI, Rec. Z.341. +- [5] CCITT Recommendation *Error performance of an international digital connection forming part of an Integrated Services Digital Network*, Vol.III, Rec. G.821. \ No newline at end of file diff --git a/marked/M/T-REC-M.496-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.496-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..92593080d3fac58d102da4eebd67f15e51efb7f6 --- /dev/null +++ b/marked/M/T-REC-M.496-198811-I_PDF-E/raw.md @@ -0,0 +1,159 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.496** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: INTERNATIONAL TRANSMISSION +SYSTEMS (ANALOGUE)** + +--- + +**FUNCTIONAL ORGANIZATION FOR +AUTOMATIC TRANSMISSION RESTORATION** + +**ITU-T Recommendation M.496** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.496 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **FUNCTIONAL ORGANIZATION FOR AUTOMATIC TRANSMISSION RESTORATION** + +This Recommendation is a description of the functional organization for three general types of automatic transmission restoration systems: + +- 1+1 transmission restoration; +- N+M direct transmission restoration (protection link switching); +- N+M automatic rerouting (protection network switching). + +The terminology and general principles of transmission restoration are described in Recommendation M.495. Specifications for equipment of the 1+1 restoration system type can be found in Recommendation G.181 [1]. Specifications for equipment of the N+M direct transmission restoration or automatic rerouting system type can be found in Recommendation G.180 [2]. + +## **1 1+1 transmission restoration** + +### **1.1 *Purpose of 1+1 transmission restoration*** + +1.1.1 1 + 1 restoration is used for the restoration of one group or digital block or link on one restoration link that is dedicated to its transmission restoration. + +1.1.2 This type of restoration is generally reserved for specific services with a need for a very high availability. + +1.1.3 As this method of restoration is rather expensive (duplication of transmission links), it is often effected, at the present time, at low hierarchical levels (for example, group or primary digital block). This is a preventive protection, adapted to specific services, whereas restoration at the highest order group or digital block is a corrective protection for part of the network. + +Figure 3/M.495 illustrates such a configuration. + +### **1.2 *Method of transmission restoration*** + +1.2.1 The transmission signal is sent on the normal link and generally also on the restoration link at the same time. + +1.2.2 In order to ensure the best availability of transmission, it is recommended to have the restoration link routed on a transmission route different from the route of the normal link. + +1.2.3 Control equipment or a control function implemented in equipment with other functions, at both ends of the link, ensures link supervision and control and detects the occurrence of such conditions that may need a restoration action. Generally, there is no control circuit in such a transmission restoration system: control and switching can be done at both receive ends of the signal. + +When a fault has been detected and confirmed, the switching equipment receives a command for a switching action. + +1.2.4 If a switchback function is provided, when the normal link becomes available again for transmission, it is advisable to perform the switchback at a time when there is the least impact on the traffic concerned. At that time, a switching command is sent by the control equipment. The switching equipment switches back the transmission to the normal link. + +This switching is normally effected in such a way that it has minimal impact on transmission quality and availability. + +### **1.3 *Restoration time*** + +Restoration time should be kept as short as possible, in order to have minimal impact on service availability. + +## 2 N+M direct transmission restoration (protection link switching) + +### 2.1 *Purpose of N+M direct transmission restoration* + +N+M direct transmission restoration systems provide M restoration links for N normal links. All the links have their terminal equipments located at the same locations. + +Figure 1/M.495 illustrates such a configuration. + +### 2.2 *Method of transmission restoration* + +2.2.1 The M restoration links may be routed on the same transmission route as all, or part, of the N normal link; but preferably, some restoration links may be routed over a different route, so that a fault of a whole transmission route allows the restoration of some links. + +2.2.2 This type of transmission restoration can be effected at all hierarchical levels. It is often used at the transmission system level. + +2.2.3 At both ends of the links, control equipment (or a control function implemented in equipment) ensures link supervision and control, and detects the occurrence of a failure. The control circuits for this function might be on a restoration link, or on another link which is not one of the N normal links, or duplicated on at least 2 of the N normal links. + +2.2.4 Some of the N normal links might have a higher priority. In this case, when one of them is in fault, it is restored in priority and can use a restoration link on a preemptive basis. This means that: + +- in case of a simultaneous fault of several links, and if a complete restoration is not possible, only the highest priority links are restored; +- if all restoration links are in use and if a normal link having a priority of one of the restored links has a failure, the lower priority restored link is interrupted so that the link in fault can be restored. + +2.2.5 When a restoration action has been detected, confirmed and accepted (restoration link available or priority link in fault), the switching equipment receives a command for a switching action. Switching might be effected at both ends systematically, but it is also possible to switch only the faulty direction, if necessary. + +2.2.6 In the case of automatic switchback, after the normal link is available again for a normal transmission, the control equipment sends a switchback command. In this case, the switching equipment switches back the signal transmitted from the restoration link to the normal link. This switching is normally effected in such a way that it has a minimal impact on transmission quality and availability. + +### 2.3 *Restoration time* + +N+M direct transmission restoration is characterized by a requirement to detect a degraded or faulty normal link and switch to a restoration link in a time interval that is short enough not to cause established telephone calls to be released. + +### 2.4 *Other considerations* + +2.4.1 A restoration link might be used, when a restoration is not needed, for other purposes such as planned outages or non- priority traffic. In this case, it can be preferable that the N normal links have a preemption of the restoration link when they are in fault. + +2.4.2 The maximum number N of normal links for one restoration has to be dimensioned correctly to avoid a too large number of non-restored faults. When a large number of links have to be restored, N+M direct transmission restoration (with $M > 1$ ) is necessary; in this case M restoration links can be used for the restoration of N normal ones. + +2.4.3 The N+M direct transmission restoration is an automatic system, but it should also allow manual or semi-automatic (remote manual) actions, in order to force switching or inhibit restoration. + +## **3 N+M automatic rerouting (protection network switching)** + +### **3.1 *Purpose of N+M automatic rerouting*** + +N+M automatic rerouting systems provide, on a single switching equipment, M restoration links to N normal ones. The restoration of 1 normal link is effected by a certain number of restoration links that are assembled together. + +The restoration systems belong to a restoration network. + +Figure 2/M.495 illustrates such a configuration. + +### **3.2 *Method of transmission restoration*** + +3.2.1 At the present time, this type of restoration is generally effected at high hierarchical levels. + +3.2.2 The organization of N+M automatic rerouting systems is generally complex: a network of normal links is protected by a network of restoration links. + +There is a supervision and control of every link that can be done by or under the control of one or several restoration control centres. Restoration can be a specific function of a more general control centre. + +3.2.3 After a failure is detected on a normal link, the restoration is normally effected according to certain preestablished restoration plans, if the restoration links are available. It is also possible to have a restoration plan computed after failure detection. + +A certain number of restoration links are assembled together through switches located at the nodes of the network and connected to the faulty link through switches located at its ends. + +3.2.4 It should also be possible to have manual or semi-automatic (remote-manual) action or inhibition of N+M automatic rerouting systems. + +3.2.5 If a restoration plan fails or a restoration link used for a restoration has a failure, all restoration links involved in the restoration plan should be released. + +3.2.6 After the fault of the normal link is removed, there can be a switchback to the normal link which should have a minimal impact on transmission quality and availability. + +3.2.7 Certain equipment, such as automatic digital distribution frames, might have a function of N+M automatic rerouting but might not be dedicated to it. + +### **3.3 *Restoration time*** + +As the operations of N+M automatic rerouting take network conditions into account, they can involve considerable data processing; they may entail all calls being cleared or lost before the operations are completed. Restoration times can be in the order of seconds, minutes, or even hours, depending on the complexity of the network and its state at that moment. + +### **3.4 *Other considerations*** + +3.4.1 Restoration links might be used under normal conditions by low-priority traffic. In this case, there is generally a preemption by normal traffic in case of normal link failure. + +3.4.2 As the restoration network might not be dimensioned for the total restoration of all transmission route interruptions and multiple failures, it might be necessary to define certain priorities among normal links. In this case, certain links might be restored in priority with preemption of restoration links used by non-priority links. + +# References + +- [1] CCITT Recommendation, *Characteristics of 1+1 type restoration systems for use on digital transmission links*, Rec. G.181. +- [2] CCITT Recommendation, *Characteristics of N+M type direct transmission restoration systems for use on digital sections, links or equipments*, Rec. G. 180. \ No newline at end of file diff --git a/marked/M/T-REC-M.500-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.500-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..12f56b610eebd36aa632e5d41c186e0b058cd46a --- /dev/null +++ b/marked/M/T-REC-M.500-198811-I_PDF-E/raw.md @@ -0,0 +1,105 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.500** + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**ROUTINE MAINTENANCE MEASUREMENTS +TO BE MADE ON REGULATED LINE SECTIONS** + +**ITU-T Recommendation M.500** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation M.500 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **ROUTINE MAINTENANCE MEASUREMENTS TO BE MADE ON REGULATED LINE SECTIONS** + +## **1 Radio-relay regulated line section** + +Measurements should be made as indicated below: + +### **1.1 *Regulated line section terminal stations:*** + +- a) daily reading of the line pilot level if necessitated by the type of system. It is preferable that such measurements should always be made at the same time of day; +- b) as necessary, readjustment to the nominal value as described in Recommendation M.510. + +### **1.2 *Radio-systems terminals*** + +1.2.1 At intervals to be determined by agreement between the Administrations concerned, and based on experience of the reliability of the system: + +- measurement of the loss/frequency distortion at frequencies in the baseband (additional measuring frequencies) (permissible limits $\pm 2$ dB); +- when there is no continuous recording of noise, measurement of the total noise level on the noise-measurement channels outside the baseband in accordance with CCIR Recommendation No. 3981) [1]. This measurement can be made without causing any interference in the transmission channel. + +1.2.2 When the measurement mentioned in § 1.2.1 above gives unacceptably high noise values, or more often, when the reliability of the system makes it desirable, check of the following measurements in accordance with the appropriate CCIR Recommendations for the radio-relay system concerned should be made, the radio-frequency channel being switched to the standby equipment, and the measurement results compared with the results of the reference measurements required by Recommendation M.450, § 3: + +- the deviation of the frequency at which the level is unchanged by pre-emphasis; +- the pilot frequency deviation; +- the central position of the intermediate frequency in the non-modulated condition of the system; +- the level of the baseband reference frequency (single frequency check); +- the relative level at the radio reference measurement frequencies (multifrequency check); +- the level of individual interfering signals in the baseband in the non-modulated condition of the system. + +1.2.3 So as to enable the limits for circuit loss variation to be met (see Recommendation M.160), the difference in response between two systems in diversity reception or between a working and standby system should be minimized. + +## **2 Coaxial regulated line section** + +The following measurements should be made at regulated line section terminal stations: + +- a) daily reading of the line pilot level if necessitated by the type of system. It is preferable that such measurements should always be made at the same time of day; +- b) as necessary, readjustment to the nominal value as described in Recommendation M.510. + +The Administrations concerned are left to decide for themselves about measurements at additional measuring frequencies and about checking the operation of the regulators. + +--- + +1) Where a protection channel is provided, and if Administrations so desire, noise measurements may be made on that channel with artificial loading, in accordance with CCIR Recommendation 399 [2]. + +*Note* – Precautions to be taken with additional measuring frequencies: + +- i) When the end of a regulated line section: + - is not the same as the end of a line link (i.e. when all the groups, supergroups, etc., are through-connected from one regulated line section to another without passing via the through-connection equipment to the basic groups); + - is the same as the end of a line link without complete demodulation to the groups, supergroups or mastergroups (i.e. when only part of the groups, supergroups, etc., are through-connected direct from one line link to another, without passing via the through-connection equipment to the basic groups);the maintenance personnel should: + - a) avoid sending a measuring frequency that is the same as a pilot frequency of a following regulated line section (unless the pilot frequency on such a following section is protected by a blocking filter at the beginning of the section); + - b) take into account the possibility of attenuation to additional measuring frequencies lying at the edges of the frequency band of a through-connected basic group, supergroup, etc., due to the presence of through-connection filters. +- ii) Interference between additional measuring frequencies on adjacent coaxial links is possible if precautions are not taken to avoid carrying out simultaneous measurements on adjacent links. For this reason: + - a) there should be different dates for routine maintenance measurements on two adjacent links; + - b) before making any measurement using an additional measuring frequency, and especially those made when clearing faults, repeater station staff should see to it that measurements are not in progress on an adjacent coaxial link. + +## 3 Symmetric pair regulated line section + +The following measurements should be made at regulated line section terminal stations: + +- a) daily reading of the line pilot level if necessitated by the type of system. It is preferable that such measurements should always be made at the same time of day; +- b) as necessary, readjustment to the nominal value as described in Recommendation M.510. + +The Administrations concerned are left to decide on measurements at additional measuring frequencies and on checking the operation of the regulators, if applicable. The same applies to any kind of measurement or pilot level reading at intermediate attended or unattended stations. + +# References + +- [1] CCIR Recommendation *Measurements of noise in actual traffic over radio-relay systems for telephony using frequency-division multiplex*, Vol. IX, Rec. 398, ITU, Geneva, 1986. +- [2] CCIR Recommendation *Measurement of noise using a continuous uniform spectrum signal on frequency-division multiplex telephony radio-relay systems*, Vol. IX, Rec. 399, ITU, Geneva, 1986. \ No newline at end of file diff --git a/marked/M/T-REC-M.510-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.510-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.510-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.510-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.510-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a3cd7c59b966ac861230980d694de665bce5977b --- /dev/null +++ b/marked/M/T-REC-M.510-198811-I_PDF-E/raw.md @@ -0,0 +1,53 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.510** + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**READJUSTMENT TO THE NOMINAL VALUE +OF A REGULATED LINE SECTION +( ON A SYMMETRIC PAIR LINE, A COAXIAL +LINE OR A RADIO RELAY LINK )** + +**ITU-T Recommendation M.510** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation M.510 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **READJUSTMENT TO THE NOMINAL VALUE OF A REGULATED LINE SECTION (ON A SYMMETRIC PAIR LINE, A COAXIAL LINE OR A RADIO-RELAY LINK)** + +After the routine measurement or clearance of the fault and when it has been ensured that no faults remain on the system, adjustments should be made as necessary to bring the levels of the line pilots and additional measuring frequencies as close as possible to their nominal value. + +Making the whole adjustment in the receiving terminal station should be avoided; adjustments should be made where they are necessary, under the direction of the control or sub-control station concerned. + +Methodical readjustment should be carried out when the level measured at the terminal station exceeds the maintenance limits for the carrier system. Due allowance should be made for measuring errors and for random effects which may cause slight short-term variation. The tolerance to be allowed depends on the type of system, its length and the periodicity of the measurements. + +For example, the following tolerances may be allowed: + +- a) in the case of a system with continuous gain control an adjustment should be made only if an improvement of at least 0.3 dB can be obtained; +- b) in the case of a system with step-by-step gain control allow a permissible tolerance of $\pm$ (one-half the gain control step $\pm$ 0.3 dB). \ No newline at end of file diff --git a/marked/M/T-REC-M.525-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.525-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.525-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.530-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.530-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.530-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.530-198811-I_PDF-E/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg b/marked/M/T-REC-M.530-198811-I_PDF-E/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2710b703f4d4f8f60b96642256d1e22494676d0 --- /dev/null +++ b/marked/M/T-REC-M.530-198811-I_PDF-E/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d453f882d470d4e6de454dca0f2968c446e4c32aa8a7d762dd3ba70e078ba31c +size 37493 diff --git a/marked/M/T-REC-M.540-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.540-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.540-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.540-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.540-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d80c55c099e88d0038273f78595f678c72c6d799 --- /dev/null +++ b/marked/M/T-REC-M.540-198811-I_PDF-E/raw.md @@ -0,0 +1,94 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.540** + +**MAINTENANCE:** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**ROUTINE MAINTENANCE OF CARRIER +AND PILOT GENERATING EQUIPMENT** + +**ITU-T Recommendation M.540** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation M.540 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **ROUTINE MAINTENANCE OF CARRIER AND PILOT GENERATING EQUIPMENT** + +**1** If a country has a national frequency standard, it is desirable to use it for checking the frequency of the master oscillators of carrier systems. (See Table 1/M.540 showing the recommended frequency accuracy for various carrier systems.) This frequency standard can be guaranteed to about 1 part in $10^8$ by means of the three-way frequency comparisons organized by the CCIR. However, we must note that a larger accuracy can be obtained in the countries that will use an atomic frequency standard (for example cesium or rubidium). + +**2** If a country has no national frequency standard, there are two possibilities: + +- a) to receive by radio the standard signals transmitted in accordance with CCIR Recommendations; +- b) to receive from a neighbouring country, over a metallic circuit, a frequency derived from the national standard of that country. + +It may be necessary in some cases to make a direct comparison of the frequency of the master oscillators of the carrier systems of different countries; this comparison will be effected by means of the frequency comparison pilots. + +**3** The changeover of master oscillators may cause a short interruption of a few milliseconds and a sudden phase-change. Because the effect of these interruptions and phase-changes is felt throughout the carrier system, changeover of master oscillators should be made only when absolutely necessary. + +TABLE 1/M.540 + +**Table showing the recommended frequency accuracy for reference pilots, carriers, etc., +in various carrier systems** + +| System | Frequency and accuracy | | | | | +|----------------------------------------------|--------------------------------------------|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------| +| | Reference pilot | | Carrier generator | | | +| (1) | (2) | | (3) | | | +| (1 + 3) open-wire | 16.110 kHz
31.110 kHz | $2.5 \times 10^{-5}$ | $2.5 \times 10^{-5}$ | | | +| 8 circuit open-wire | | | $10^{-5}$ | | | +| 12 circuit open-wire | $5 \times 10^{-6}$ | | $5 \times 10^{-6}$ | | | +| Symmetric pair

1, 2, 3, 4 or 5 groups | Line regulating
60 kHz

Auxiliary |
± 1 Hz

± 3 Hz | Channel virtual carriers of a group
± $10^{-6}$

Groups and supergroups
± $10^{-7}$

Mastergroups and supergroups
± $5 \times 10^{-8}$ | | | +| 2 supergroups | Line regulating
60 kHz
556 kHz | ± 1 Hz
± 3 Hz | | | | +| | 2,6 MHz | Line regulating
2 604 kHz | | ± 30 Hz | | +| | 4 MHz | Line regulating
60 kHz
308 kHz
4 092 kHz | | ± 1 Hz
± 3 Hz
± 40 Hz | | +| Coaxial pair
2.6/9.5 mm | | Auxiliary
2 792 kHz | | ± 5 Hz | | +| | | Additional measuring
frequencies (all) | | ± 40 Hz | | +| | | 12 MHz | | Line regulating
308 kHz
4 287 kHz
12 435 kHz | ± $1 \times 10^{-5}$ | +| | | | | Additional measuring
frequencies:
< 4 MHz
> 4 MHz |
± 40 Hz
± $1 \times 10^{-5}$ | +| | | 60 MHz | | Line regulating
4 287 kHz
12 435 kHz
22 372 kHz
40 920 kHz
61 160 kHz | ± $1 \times 10^{-5}$ | +| | Additional measuring
frequencies (all) | | | ± $1 \times 10^{-5}$ | | +| | Coaxial pair
1.2/4.4 mm | 1.3 MHz | | Line regulating
1 364 kHz
Auxiliary
60 or 308 kHz | ± $1 \times 10^{-5}$

± $1 \times 10^{-5}$ | +| | | 4 MHz | | Line regulating
60, 308, 4 287 kHz | ± $1 \times 10^{-5}$ | +| 6 MHz | | Line regulating
308, 4 287 kHz | | ± $1 \times 10^{-5}$ | | + +TABLE 1/M.540 (end) + +| System | Frequency and accuracy | | +|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| | Reference pilot | Carrier generator | +| (1) | (2) | (3) | +| 12 + 12 | 60 kHz $\pm 1$ Hz
Others by agreement
between Administrations | Error in reconstituted frequency over
a 140 km section and not to exceed
0.3 Hz (provisional value) | +| 6 MHz | | Video carrier
1056 kHz $\pm 5$ Hz | +| 12 MHz | | Video carrier
6799 kHz $\pm 100$ Hz | +| 4 kHz spacing
Basic group B
and
Basic supergroup | 84.080 kHz 104.080 kHz
411.920 kHz and 547.920 kHz $\pm 1$ Hz
84.140 kHz and 411.860 kHz $\pm 3$ Hz | | +| Basic mastergroup and
15-supergroup assembly | 1 552 kHz $\pm 2$ Hz | | +| Basic supermastergroup | 11 096 kHz $\pm 10$ Hz | | +| 3 kHz spacing | 84 kHz (or other frequency by
agreement) $\pm 1$ Hz | | +| Basic group and
Basic supergroup | a) | | + +a) A supergroup reference pilot frequency of 444 kHz with a tolerance of $\pm 1$ Hz is used. \ No newline at end of file diff --git a/marked/M/T-REC-M.556-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.556-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.556-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.560-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.560-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3cec219ba5a33fca924c6dab538494cd333ebcee --- /dev/null +++ b/marked/M/T-REC-M.560-198811-I_PDF-E/raw.md @@ -0,0 +1,161 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.560** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE :** + +**INTERNATIONAL TRANSMISSION SYSTEMS +(ANALOGUE)** + +--- + +**INTERNATIONAL TELEPHONE CIRCUITS – +PRINCIPLES, DEFINITIONS AND +RELATIVE TRANSMISSION LEVELS** + +**ITU-T Recommendation M.560** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.560 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# INTERNATIONAL TELEPHONE CIRCUITS – PRINCIPLES, DEFINITIONS AND RELATIVE TRANSMISSION LEVELS + +## 1 General + +The purpose of this Recommendation is to provide the necessary background information for other Recommendations in the M Series. + +The CCITT transmission plan and international telephone connections are explained. The Recommendation also introduces the concepts of “virtual analogue switching points”, and their conventional relative transmission levels. Appropriate definitions are given where necessary. + +Extracts from the relevant Recommendations in Volume III and from Recommendation Q.45 [1] are included in this Recommendation. + +## 2 The CCITT Transmission Plan + +### 2.1 *Principles* + +The CCITT transmission plan has been drawn up with the object of making use, in the international service, of the advantages offered by 4-wire switching. However, the recommendations in the plan are considered to be met if the use of technical media other than those described give an equivalent performance at the international centre. + +*Note* – Short transfrontier circuits are not covered by the transmission plan; they should be the subject of agreement between the Administrations concerned. + +### 2.2 *International telephone connections* + +A complete **international telephone connection** has three parts, as shown in Figure 1/M.560, namely: + +#### – an **international chain** + +an international chain is made up of one or more 4-wire international circuits. These are connected on a 4-wire basis to other international circuits in transit international centres or to national systems in terminal international centres; + +#### – two **national systems**, one at each end + +These may comprise one or more 4-wire amplified national circuits with 4-wire interconnection, and circuits with 2-wire connection to terminal exchanges and subscribers. + +![Diagram of an international telephone connection showing a four-wire chain between two national systems. The chain includes terminal and transit international exchanges, national exchanges, and subscriber's sets. A legend defines the symbols: circle for transit international exchange, circle with a vertical line for terminal international exchange, X for national exchange, and a telephone handset for subscriber's set. The diagram is labeled CCITT - 36850 and d01-sc.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +The diagram illustrates the constituent parts of an international telephone connection. It shows a 'Four-wire chain' (indicated by a double-headed arrow at the top) connecting two 'National system' segments (labeled at the bottom). The chain consists of two parallel lines representing the two-wire path. Along these lines, from left to right, the components are: a subscriber's set (handset icon), a national exchange (X), a terminal international exchange (circle with a vertical line), a transit international exchange (circle), another transit international exchange (circle), another terminal international exchange (circle with a vertical line), a national exchange (X), and finally a subscriber's set (handset icon). Vertical dashed lines separate the 'National system' segments from the 'International chain'. The text 'CCITT - 36850' and 'd01-sc' are present on the right side. + +Legend: + +- Transit international exchange +- ⊖ Terminal international exchange +- X National exchange +- ☎ Subscriber's set + +Diagram of an international telephone connection showing a four-wire chain between two national systems. The chain includes terminal and transit international exchanges, national exchanges, and subscriber's sets. A legend defines the symbols: circle for transit international exchange, circle with a vertical line for terminal international exchange, X for national exchange, and a telephone handset for subscriber's set. The diagram is labeled CCITT - 36850 and d01-sc. + +FIGURE 1/M.560 + +#### **Constituent parts of an international telephone connection** + +### **2.3 International telephone circuits, virtual analogue switching points and relative transmission levels** + +2.3.1 From a transmission planning point of view, an international telephone circuit is defined by its “virtual analogue switching points” in the international centre. + +#### **2.3.2 Virtual analogue switching points** + +Virtual analogue switching points are theoretical points with specified relative levels. + +For circuits terminating at a digital international centre, the concept of virtual analogue switching points postulates the existence of ideal analogue-to-digital coders and digital-to-analogue decoders, via which the desired analogue points could be derived. + +The virtual analogue switching points may not be the same as the points at which the circuit terminates physically in a switching equipment. These latter points are known as the circuit terminals; the exact position of the terminals is decided in each case by the Administration concerned (see Figure 2/M.560). + +For illustrative purposes, Figure 2/M.560 depicts the virtual analogue switching points for wholly digital and wholly analogue international telephone circuits. Recommendation M.562 deals in detail with circuits provided by a mixture of analogue and digital systems. + +#### **2.3.3 Relative transmission levels at virtual analogue switching points** + +The virtual analogue switching points of an international 4-wire telephone circuit are fixed by convention at points of the circuit where the nominal relative levels at the reference frequency are: + +- sending: –3.5 dBr; +- receiving: –4.0 dBr, for analogue circuits and the analogue end of mixed analogue/digital circuits; +–3.5 dBr for digital circuits. + +The nominal transmission loss of circuits at the reference frequency between virtual analogue switching points is therefore 0.5 dB for both analogue and mixed analogue/digital circuits and 0 dB for digital circuits. + +Two international circuits interconnected in an international centre are considered to be connected together directly at their virtual analogue switching points without any pad or amplifier between those virtual analogue switching points (see Figure 3/M.560). + +The relationship between the actual switching points and the virtual analogue switching points in a practical international exchange is illustrated in Figure 3/M.560. + +![Diagram (a) showing a wholly analogue circuit between International centre A and International centre B. It features two parallel lines representing circuit terminals. On the left, virtual analogue switching points are marked with 'X' and signal levels of -3.5 dBr and -4 dBr. On the right, similar points are marked with -4 dBr and -3.5 dBr. Arrows indicate signal flow between the centres. Labels include 'International centre A', 'International centre B', 'Circuit terminals in centre A', 'Circuit terminals in centre B', 'Virtual analogue switching points in centre A', and 'Virtual analogue switching points in centre B'. A reference code 'CCITT - 338' is present.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Diagram (a) showing a wholly analogue circuit between International centre A and International centre B. It features two parallel lines representing circuit terminals. On the left, virtual analogue switching points are marked with 'X' and signal levels of -3.5 dBr and -4 dBr. On the right, similar points are marked with -4 dBr and -3.5 dBr. Arrows indicate signal flow between the centres. Labels include 'International centre A', 'International centre B', 'Circuit terminals in centre A', 'Circuit terminals in centre B', 'Virtual analogue switching points in centre A', and 'Virtual analogue switching points in centre B'. A reference code 'CCITT - 338' is present. + +a) Wholly analogue circuit showing virtual analogue switching points and circuit terminals + +![Diagram (b) showing a wholly digital circuit between International centre A and International centre B. It uses dashed lines for digital switching and solid lines for analogue-digital conversion. Signal levels like 0 dBr, -3.5 dBr, and 3.5 dB are indicated at various points. Labels include 'International centre A', 'International centre B', 'Digital switching', 'Ideal digital-analogue decoder with 0 dBr output relative level', 'Ideal analogue-digital coder with 0 dBr input relative level', and 'Virtual analogue switching points in centre A/B'. Reference codes 'CCITT - 33831' and 'd02-sc' are present.](e394c2b5c61344f6a12397f430086072_img.jpg) + +Diagram (b) showing a wholly digital circuit between International centre A and International centre B. It uses dashed lines for digital switching and solid lines for analogue-digital conversion. Signal levels like 0 dBr, -3.5 dBr, and 3.5 dB are indicated at various points. Labels include 'International centre A', 'International centre B', 'Digital switching', 'Ideal digital-analogue decoder with 0 dBr output relative level', 'Ideal analogue-digital coder with 0 dBr input relative level', and 'Virtual analogue switching points in centre A/B'. Reference codes 'CCITT - 33831' and 'd02-sc' are present. + +b) Wholly digital circuit showing virtual analogue switching points + +FIGURE 2/M.560 + +## International telephone circuits + +## 3 Access points for line-up and maintenance purposes + +Recommendation M.565 describes the types of access points which should be provided on international telephone circuits for line-up and maintenance purposes. + +![Diagram (a) showing the actual arrangement of a transit connection. It features two horizontal lines representing circuits. The top circuit has a send point 'S' at -16 dBr on the right and a receive point 'R' at +7 dBr on the left. The bottom circuit has a receive point 'R' at +7 dBr on the right and a send point 'S' at -16 dBr on the left. In the center, 'Actual switching points' are marked with 'X'. Relative levels are indicated: 9.5 dB and 14 dB for both circuits. At the switching points, values are -2.5 dBr and -2 dB for the top circuit, and -2 dB and -2.5 dBr for the bottom circuit.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) + +Diagram (a) showing the actual arrangement of a transit connection. It features two horizontal lines representing circuits. The top circuit has a send point 'S' at -16 dBr on the right and a receive point 'R' at +7 dBr on the left. The bottom circuit has a receive point 'R' at +7 dBr on the right and a send point 'S' at -16 dBr on the left. In the center, 'Actual switching points' are marked with 'X'. Relative levels are indicated: 9.5 dB and 14 dB for both circuits. At the switching points, values are -2.5 dBr and -2 dB for the top circuit, and -2 dB and -2.5 dBr for the bottom circuit. + +a) Actual arrangement + +![Diagram (b) showing a hypothetical arrangement with virtual analogue switching points. It includes an 'International circuit' and an 'International or national circuit'. The international circuit has send/receive points at -4 dBr and -3.5 dBr. The other circuit has send/receive points at -3.5 dBr and -4 dBr. Virtual switching points are marked with 'X'. Relative levels include 9.5 dB, 14 dB, 1.5 dB, and T = 0.5 dB. Asterisks (*) mark values of -3.5 dBr at the far left and far right, labeled as '(Relative level at virtual analogue switching point of adjacent centre)'.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +\*These are the only values that are the subject of CCITT Recommendations; the other values are given as examples only. + +Diagram (b) showing a hypothetical arrangement with virtual analogue switching points. It includes an 'International circuit' and an 'International or national circuit'. The international circuit has send/receive points at -4 dBr and -3.5 dBr. The other circuit has send/receive points at -3.5 dBr and -4 dBr. Virtual switching points are marked with 'X'. Relative levels include 9.5 dB, 14 dB, 1.5 dB, and T = 0.5 dB. Asterisks (\*) mark values of -3.5 dBr at the far left and far right, labeled as '(Relative level at virtual analogue switching point of adjacent centre)'. + +b) Hypothetical arrangement indicating possible position of the virtual analogue switching points of the two circuits + +CCITT - 36870 d03-sc + +*Note* — Underlined values of relative level refer to the circuit on the right of the point concerned. Values of relative level not underlined refer to the circuit on the left of the point concerned. In an actual switching centre the virtual analogue switching points would not physically exist. + +FIGURE 3/M.560 + +Example showing a simplified representation of a transit connection in an international exchange with actual arrangement and possible location of virtual analogue switching points + +## Reference + +- [1] CCITT Recommendation *Transmission Characteristics of an International Exchange*, Vol. VI, Rec. Q.45. \ No newline at end of file diff --git a/marked/M/T-REC-M.562-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.562-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b6bb5bed6e405dc737f4676a77143ac4e0aaeae7 --- /dev/null +++ b/marked/M/T-REC-M.562-198811-I_PDF-E/raw.md @@ -0,0 +1,209 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.562** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**TYPES OF CIRCUIT AND CIRCUIT SECTION** + +**ITU-T Recommendation M.562** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.562 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **TYPES OF CIRCUIT AND CIRCUIT SECTION** + +## **1 General** + +1.1 The purpose of this Recommendation is to describe the terms “circuit section” and “circuit”, as they are used in the Series M Recommendations, taking into consideration analogue, digital, and mixed analogue/digital constitutions. + +1.2 The circuit types described in this Recommendation differ somewhat from those in Recommendation G.101 [1], in order to emphasize distinctions that are useful in setting forth maintenance procedures. + +## **2 Circuit sections** + +Each of the first three section types listed below corresponds to one of the three channel types defined in Recommendation M.300. Each of the last two circuit section types corresponds to one of the two terminal types also defined in Recommendation M.300. + +### **2.1 *Analogue circuit section*** + +An analogue circuit section comprises two analogue channels, one for each direction of transmission. + +### **2.2 *Mixed circuit section*** + +A mixed circuit section comprises two mixed channels, one for each direction of transmission. + +### **2.3 *Digital circuit section*** + +A digital circuit section comprises two digital channels, one for each direction of transmission. + +### **2.4 *Mixed analogue/digital terminal circuit section*** + +A mixed analogue/digital terminal circuit section comprises the two directions of transmission, for one equivalent voice-frequency signal, through a PCM multiplex equipment. In the analogue to digital direction, the mixed analogue/digital terminal circuit section extends from the audio input of the PCM multiplex equipment, to the associated 64 kbit/s time slot appearance at the digital output. In the digital to analogue direction, the mixed analogue/digital terminal circuit section extends from the 64 kbit/s time slot appearance of a particular channel at the digital input to the PCM multiplex equipment, to the associated audio output. + +### **2.5 *Digital terminal circuit section*** + +A digital terminal circuit section comprises the two directions of transmission, for one equivalent voice-frequency signal, through a digital terminal. For each direction of transmission, the digital terminal circuit section extends from a particular 64 kbit/s time slot appearance, in the input bit sequence to the digital terminal, to the corresponding 64 kbit/s time slot appearance in the output bit sequence of the digital terminal. + +## **3 Circuits** + +International circuits comprise various combinations of national and international circuit sections, together with ancillary equipment as required. The following circuit types are defined in terms of their constituent circuit sections, as a basis for recommending appropriate maintenance procedures. + +### 3.1 Analogue circuit + +An analogue circuit comprises one or more analogue circuit sections. These circuits terminate at both ends in analogue switching machines. A schematic drawing is shown in Figure 1/M.562. + +![Schematic drawing of an analogue circuit (ACS). Two horizontal lines represent the circuit paths between two dashed rectangular boxes representing station boundaries. The top path has an 'X' (analogue switching) at the left boundary, the label 'ACS' in the center, and an 'I' (attenuator) followed by an 'X' at the right boundary. The bottom path has an 'X' at the left boundary, an 'I' followed by an 'X' at the right boundary. Arrows indicate directionality. Reference code CCITT-71140 d01-sc is at the bottom right.](9e6062272bbe3ddbb7c0606721d64cf0_img.jpg) + +Schematic drawing of an analogue circuit (ACS). Two horizontal lines represent the circuit paths between two dashed rectangular boxes representing station boundaries. The top path has an 'X' (analogue switching) at the left boundary, the label 'ACS' in the center, and an 'I' (attenuator) followed by an 'X' at the right boundary. The bottom path has an 'X' at the left boundary, an 'I' followed by an 'X' at the right boundary. Arrows indicate directionality. Reference code CCITT-71140 d01-sc is at the bottom right. + +Symbols and nomenclature used in Figures 1/M.562 to 3/M.562 + +![Dashed rectangle Dashed line with X Solid line Solid line with X Dashed line Solid line with vertical bar I Solid line with cross T Solid line with bold cross Dashed line with cross T](d62e2e2281009c16f4ee61660e716cd9_img.jpg) + +| | | | | +|------|---------------------------------------------------|--|--------------------------------| +| ACS | – Analogue circuit section | | | +| MCS | – Mixed analogue/digital circuit section | | | +| DCS | – Digital circuit section | | | +| MTCS | – Mixed analogue/digital terminal circuit section | | | +| DTCS | – Digital terminal circuit section | | | +| | Station boundaries | | Digital switching | +| | Analogue transmission | | Analogue switching | +| | Digital transmission | | Analogue attenuator (see Note) | +| | Mixed terminal | | Transmultiplexer | +| | | | Digital terminal | + +Dashed rectangle Dashed line with X Solid line Solid line with X Dashed line Solid line with vertical bar I Solid line with cross T Solid line with bold cross Dashed line with cross T + +*Note* – The use of this symbol in the figures indicates the location of any analogue attenuation required to meet the CCITT transmission plan. + +FIGURE 1/M.562 + +#### Analogue circuit + +### 3.2 Mixed analogue/digital circuit + +A mixed analogue/digital circuit comprises any combination of circuit sections that includes one or more analogue to digital, or digital to analogue, conversion processes. Mixed analogue/digital circuits may terminate at either end in analogue or digital switching machines. Combinations of various types of circuit sections that are acceptable in making up mixed analogue/digital circuits are constrained by the need to avoid excessive transmission impairments. These constraints are discussed in § 5 below. Examples of permitted mixed analogue/digital circuit configurations are shown schematically in Figure 2/M.562. + +![Diagram (a) showing two parallel transmission paths between two boxes. The top path consists of a solid line segment labeled 'MTCS' at the left box, a dashed line segment labeled 'DCS' in the middle, and another solid line segment labeled 'MTCS' at the right box. The bottom path is identical. Both paths have 'X' marks at the interfaces with the boxes.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Diagram (a) showing two parallel transmission paths between two boxes. The top path consists of a solid line segment labeled 'MTCS' at the left box, a dashed line segment labeled 'DCS' in the middle, and another solid line segment labeled 'MTCS' at the right box. The bottom path is identical. Both paths have 'X' marks at the interfaces with the boxes. + +a) Analogue switching at each end; digital transmission; mixed terminals + +![Diagram (b) showing two parallel transmission paths between two boxes, with a third box in the middle. The top path has a solid line labeled 'MCS' from the left box to the middle box, a dashed line labeled 'DCS' from the middle box to the right box, and a solid line labeled 'MTCS' at the right box. The bottom path is identical. 'X' marks are at the interfaces.](e394c2b5c61344f6a12397f430086072_img.jpg) + +Diagram (b) showing two parallel transmission paths between two boxes, with a third box in the middle. The top path has a solid line labeled 'MCS' from the left box to the middle box, a dashed line labeled 'DCS' from the middle box to the right box, and a solid line labeled 'MTCS' at the right box. The bottom path is identical. 'X' marks are at the interfaces. + +b) Analogue switching at each end; both analogue and digital transmission, with transmultiplexer at transmission interface; mixed terminal + +![Diagram (c) showing two parallel transmission paths between two boxes. Both paths consist of a single solid line segment labeled 'MCS'. The left box has a transmultiplexer symbol (a circle with multiple lines) at the start of each path. The right box has 'X' marks at the interfaces.](53f1f7d17b3e7aae62169c41d2a88a77_img.jpg) + +Diagram (c) showing two parallel transmission paths between two boxes. Both paths consist of a single solid line segment labeled 'MCS'. The left box has a transmultiplexer symbol (a circle with multiple lines) at the start of each path. The right box has 'X' marks at the interfaces. + +c) Digital switching at one end, with analogue switching at the other end; analogue transmission; transmultiplexer + +![Diagram (d) showing two parallel transmission paths between two boxes, with a third box in the middle. The top path has a dashed line labeled 'DCS' from the left box to the middle box, a solid line labeled 'MCS' from the middle box to the right box, and an 'X' mark at the right box. The bottom path is identical. 'X' marks are also at the left box interfaces.](ca5566458a134032dd860e88fdaa0d2b_img.jpg) + +Diagram (d) showing two parallel transmission paths between two boxes, with a third box in the middle. The top path has a dashed line labeled 'DCS' from the left box to the middle box, a solid line labeled 'MCS' from the middle box to the right box, and an 'X' mark at the right box. The bottom path is identical. 'X' marks are also at the left box interfaces. + +d) Digital switching at one end, with analogue switching at the other end; both digital and analogue transmission, with transmultiplexer at transmission interface + +d02-sc + +FIGURE 2/M.562 + +Mixed analogue/digital circuits + +![Diagram e) showing digital switching at one end and analogue switching at the other end. It features two parallel transmission lines. The top line is labeled 'DCS' and has a digital switching symbol at the left end and a mixed terminal symbol (MTCS) at the right end. The bottom line is labeled 'MTCS' and has a mixed terminal symbol at the left end and a digital switching symbol at the right end. Both lines terminate in rectangular boxes representing switching machines.](547f726730e589392f239257a833ede3_img.jpg) + +Diagram e) showing digital switching at one end and analogue switching at the other end. It features two parallel transmission lines. The top line is labeled 'DCS' and has a digital switching symbol at the left end and a mixed terminal symbol (MTCS) at the right end. The bottom line is labeled 'MTCS' and has a mixed terminal symbol at the left end and a digital switching symbol at the right end. Both lines terminate in rectangular boxes representing switching machines. + +e) *Digital switching at one end, with analogue switching at the other end; digital transmission; mixed terminal* + +![Diagram f) showing digital switching and analogue transmission using a transmultiplexer. It features two parallel transmission lines. The top line is labeled 'MCS' and has a digital switching symbol at the left end and a transmultiplexer symbol at the right end. The bottom line is labeled 'MCS' and has a transmultiplexer symbol at the left end and a digital switching symbol at the right end. Both lines terminate in rectangular boxes representing switching machines.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) + +Diagram f) showing digital switching and analogue transmission using a transmultiplexer. It features two parallel transmission lines. The top line is labeled 'MCS' and has a digital switching symbol at the left end and a transmultiplexer symbol at the right end. The bottom line is labeled 'MCS' and has a transmultiplexer symbol at the left end and a digital switching symbol at the right end. Both lines terminate in rectangular boxes representing switching machines. + +f) *Digital switching; analogue transmission: transmultiplexer* + +![Diagram g) showing digital switching with both digital and analogue transmission, using transmultiplexers at the interfaces. It features three parallel transmission lines. The top line is labeled 'DCS' at the left, 'MCS' in the middle, and 'DCS' at the right. The middle line is labeled 'MCS' and has transmultiplexer symbols at both ends. The bottom line is labeled 'DCS' at the left, 'MCS' in the middle, and 'DCS' at the right. All lines terminate in rectangular boxes representing switching machines.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +Diagram g) showing digital switching with both digital and analogue transmission, using transmultiplexers at the interfaces. It features three parallel transmission lines. The top line is labeled 'DCS' at the left, 'MCS' in the middle, and 'DCS' at the right. The middle line is labeled 'MCS' and has transmultiplexer symbols at both ends. The bottom line is labeled 'DCS' at the left, 'MCS' in the middle, and 'DCS' at the right. All lines terminate in rectangular boxes representing switching machines. + +g) *Digital switching; both digital and analogue transmission; transmultiplexers at the transmission interfaces* + +CCITT 71210 +d03-sc + +*Note* – Explanation of symbols and nomenclature is given in Figure 1/M.562. + +FIGURE 2/M.562 (cont.) +**Mixed analogue/digital circuits** + +### 3.3 *Digital circuit* + +A digital circuit comprises one or more digital circuit sections. In addition to the digital circuit section(s), a digital circuit may include one or more digital terminal circuit sections. These circuits terminate at both ends in digital switching machines. A schematic drawing is shown in Figure 3/M.562. + +## 4 **Allocation of losses in mixed analogue/digital circuits** + +In Figure 2/M.562, the attenuators needed to control any variability in the analogue portions of the circuits, arising from loss variations with time, or attenuation distortion, are shown symmetrically for both directions of transmission. However, in practice, such arrangements may require nonstandard levels at the boundaries between circuit sections. + +Administrations are advised that should they prefer to adopt an asymmetric arrangement, e.g., by putting all the loss into the receive direction at only one end of a circuit or circuit section, then, provided that the loss is small, e.g., a total of not more than 1 dB, the small amount of asymmetry that results in the international portion of the connection will be acceptable, bearing in mind the small number of international circuits encountered in most actual connections. + +![Figure 3/M.562: Digital circuits. Diagram (a) shows a digital circuit with two DCS (Digital Circuit Switching) units connected by two parallel dashed lines. Diagram (b) shows a digital circuit with two DCS units connected by a DTCS (Digital Terminal Circuit Switching) unit. The diagram includes symbols for switches and labels for DCS and DTCS. A small note 'CCITT-71230 d04-sc' is present in the bottom right of diagram (b).](fc46871d72c65d3381d9201646d23439_img.jpg) + +a) Digital circuit + +b) Digital circuit with digital terminal circuit section + +CCITT-71230 +d04-sc + +Figure 3/M.562: Digital circuits. Diagram (a) shows a digital circuit with two DCS (Digital Circuit Switching) units connected by two parallel dashed lines. Diagram (b) shows a digital circuit with two DCS units connected by a DTCS (Digital Terminal Circuit Switching) unit. The diagram includes symbols for switches and labels for DCS and DTCS. A small note 'CCITT-71230 d04-sc' is present in the bottom right of diagram (b). + +*Note* – Explanation of symbols and nomenclature is given in Figure 1/M.562. + +FIGURE 3/M.562 + +### **Digital circuits** + +## 5 Number of unintegrated PCM digital processes + +### 5.1 General principle + +It is recognized that in the mixed analogue/digital period, there could be a considerable presence of unintegrated digital processes in the worldwide telephone network. Consequently, it is important that the incorporation of these processes should take place in such a way that when integration of functions can occur, unnecessary items of equipment will not remain in the all-digital network. + +### 5.2 Restrictions due to transmission impairments + +In the mixed analogue/digital period, it may be necessary to include a substantial number of unintegrated digital processes in international telephone connections. To ensure that the resulting transmission impairments (quantization, attenuation and group-delay distortion) introduced by such processes do not accumulate to the point where overall transmission quality can be appreciably impaired, it is recommended that the planning rule given in Recommendation G.113, § 3 [2], be complied with. The effect of this rule is to limit the number of unintegrated digital processes in both the national and international parts of telephone connections. + +In the case of all-digital connections, transmission impairments can also accumulate due to the incorporation of digital processes (e.g., digital pads). The matter of accumulating such impairments under all-digital conditions is also dealt with in Recommendation G.113, § 3 [2]. + +# References + +- [1] CCITT Recommendation *The transmission plan*, Vol. III, Rec. G.101. +- [2] CCITT Recommendation *Transmission Impairments*, Vol. III, Rec. G.113. \ No newline at end of file diff --git a/marked/M/T-REC-M.565-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.565-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4d5a3df5845636f1913d3c74f0a5d1a49ca0f4ea --- /dev/null +++ b/marked/M/T-REC-M.565-198811-I_PDF-E/raw.md @@ -0,0 +1,144 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.565** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**ACCESS POINTS FOR INTERNATIONAL +TELEPHONE CIRCUITS** + +**ITU-T Recommendation M.565** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.565 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +© ITU 1988, 1993 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# **ACCESS POINTS FOR INTERNATIONAL TELEPHONE CIRCUITS** + +## **1 General** + +This Recommendation specifies the access points required for testing and measuring purposes on international telephone circuits. (Access points for other types of circuit are dealt with in Recommendation M.110.) + +## **2 Types of access point and their uses** + +2.1 Three basic types of access points are required for international telephone circuits. These should be provided and used in accordance with the following principles: + +2.1.1 The international circuit for public telephony includes the international line (as defined in Recommendation M.700). Points serving to distinguish the ends of the international line should be provided, where possible, in the form of 4-wire access points called line access points as defined below. + +**line access points** (points d'accès à la ligne – puntos de acceso a la línea) + +Points used by the CCITT to define the limits of an international line, and from which measurements are made. Only one “line access point” exists at each end of an international line. The precise location of each such point depends on the Administration concerned1). + +Where a digital international exchange is interfaced with the transmission network by primary (or higher order) digital paths, a line access point at “circuit” level cannot generally be provided. In this case, any necessary testing of circuits normally carried out at the line access point may be performed at the digital path access point2) nearest to the international exchange. Circuit tests which involve the sending of test signals should be carried out from the circuit access point as defined in § 2.1.2 below. + +2.1.2 At the international switching centres, at the terminals of a circuit, “circuit access points” as defined below should be provided. + +**circuit access points** (points d'accès au circuit – puntos de acceso al circuito) + +Four-wire access points so located that as much as possible of the international circuit is included between corresponding pairs of these access points at the two centres concerned. These points, and their relative level (with reference to the transmission reference point) are determined in each case by the Administration concerned. They are taken as the basic practical reference points of known relative level to which other transmission measurements will be related. In other words, for measurement and lining-up purposes, the level at the appropriate circuit access point is the relative level with respect to which other levels are adjusted. + +The requirement to provide a circuit access point within a digital international exchange will be met by any suitable method of obtaining access to the digital bit sequence (time slot) corresponding to an individual telephone circuit. + +Where a circuit uses channel associated signalling it should be possible to identify and measure at the circuit access points, the signal-transmission parameters, e.g., type of signal, sequence, timing, duration, level and frequency. + +2.1.3 Where an international telephone circuit appears at its basic frequencies or basic bit rate within a transit country, an intermediate access point for testing and measuring purposes should be provided at that location in the transit country. + +2.2 The line access points and circuit access points (and any intermediate access points in transit countries) will be used by the appropriate testing points3) in all tests and measurements for the line-up and maintenance of international telephone circuits. + +--- + +1) A compandor, if fitted, should be connected on the line side of the line access points and not between the line access point and the circuit access point. In this way the relationship between the nominal transmission levels at these two points on a circuit with a compandor is the same as for other circuits. + +2) The access points required for digital leased circuits have yet to be specified. This matter is for further study by Study Group IV, in association with Study Group XV. + +3) For example, those defined in Recommendations M.717 and M.718. + +2.3 At the discretion of Administrations, means of giving access to the circuit access points and/or the line access points from remote locations may be provided – such remote locations being within or outside the international centre. Such arrangements avoid the need for staff to enter equipment areas for circuit testing purposes, and increase the flexibility and efficiency of the maintenance organization where large numbers of circuits must be maintained. + +2.4 In order to line-up and maintain circuits routed on a mixture of analogue and digital systems it is necessary to carry out measurements of analogue circuit parameters at digital international exchanges. If this requirement cannot be met by suitable digital test equipment, it may be necessary to provide a “test coder/decoder” to convert digital access points (operated at 64 kbit/s for example) to analogue access points (at voice frequency), thus enabling analogue measuring equipment to be used. + +2.5 Figure 1/M.565 shows typical access and test equipment arrangements for analogue and digital international exchanges. Subject to meeting the requirements in §§ 2.1 to 2.4 above, the actual arrangements at a particular international centre are left to the discretion of the Administration concerned. + +*Note* – Remote access arrangements, as described in § 2.3, are only a physical extension of the access points to a more convenient location(s). Thus, in the Series M Recommendations, the terms “line access points” and “circuit access points” are used (without qualification) irrespective of the manner in which the required access is obtained. + +## **3 Transmission characteristics and choice of levels at analogue access points** + +3.1 The impedance at analogue access points should have a return loss against the nominal impedance of the measuring apparatus of the station (for example 600 ohms, nonreactive) of not less than 20 dB over the range 600-3400 Hz and not less than 15 dB over the range 300-600 Hz. + +3.2 It should be recognized that the analogue link access point shown in Figure 1b/M.565 is suitable only as a maintenance access point. It is not intended for the setting-up or lining-up of individual circuits, because the circuits levels at these points are not specifically defined. This occurs because the shape of the group and supergroup filters have not been compensated for at this point by the channel translating equipment adjustments. + +3.3 It is not possible to recommend a value for the nominal transmission loss between the circuit access points of a switched public telephony circuit, because of the freedom accorded to Administrations in choosing the transmission levels at these points. However, bearing in mind that the attenuation between the circuit access points and the virtual analogue switching points will have a fixed and known value and that it is possible to build out the wiring to circuit access points to a known loss, the send and receive level at the circuit access point should be chosen such that the circuit level diagram is respected. + +3.4 It is advantageous to adopt the same value of relative level at the send line access points for every circuit connected to the exchange. Similarly, all the receive line access points could also be at a particular common nominal value of relative level. When relative levels are made uniform in this way, line-up and maintenance activity is greatly simplified. Also, lines can be readily cross-connected at the line access points, which is useful in the immediate replacement of faulty lines in an emergency. + +3.5 If the nominal relative level at the receive line access point is chosen to be higher than that at the send line access point of the same exchange, this level difference can be used to offset the inherent transmission loss in the signalling and switching equipment, and the requirements of the CCITT transmission plan can be met without the obligation to install supplementary audio-frequency amplifiers. + +*Note* – It is preferred to make transmission measurements between 4-wire access points but, as a permissible alternative, a terminating unit may be provided together with an associated 2-wire access point for measurement purposes. The transmission levels and losses must be chosen so that the nominal loss between virtual analogue switching points is 0.5 dB (or 0.0 dB for wholly digital circuits), and the circuit level diagram is respected. + +![Two block diagrams showing typical access and test equipment arrangements at international centres. Diagram (a) shows an analogue international centre with paths for digital and analogue transmission. Diagram (b) shows a digital international centre with digital and analogue transmission paths. Both diagrams include components like exchanges, relay sets, PCM multiplexers, and test equipment.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +*a) Analogue international centre* + +*b) Digital international centre* + +CCITT-71240 + +Two block diagrams showing typical access and test equipment arrangements at international centres. Diagram (a) shows an analogue international centre with paths for digital and analogue transmission. Diagram (b) shows a digital international centre with digital and analogue transmission paths. Both diagrams include components like exchanges, relay sets, PCM multiplexers, and test equipment. + +![Circuit access point symbol Line access point symbol Test access equipment symbol Circuit access point remotely extended symbol Digital path access point symbol PCM multiplex equipment symbol Analogue link access point symbol Analogue switching symbol Exchange terminal symbol Transmultiplexer symbol Audio equipment symbol Relay set or signalling converter symbol Digital switching symbol Channel translating equipment symbol Theoretical location of circuit access point symbol](690fce4fb5c9cbb8beb560cb2a3fcbeb_img.jpg) + +| | | | +|----------------------------------------|----------------------------------------------|----------------------------------| +| Circuit access point | Line access point | Test access equipment (see Note) | +| Circuit access point remotely extended | Digital path access point | | +| PCM multiplex equipment | Analogue link access point | Analogue switching | +| Exchange terminal | Transmultiplexer | | +| Audio equipment | Relay set or signalling converter | Digital switching | +| Channel translating equipment | Theoretical location of circuit access point | | + +d01-sc + +Circuit access point symbol Line access point symbol Test access equipment symbol Circuit access point remotely extended symbol Digital path access point symbol PCM multiplex equipment symbol Analogue link access point symbol Analogue switching symbol Exchange terminal symbol Transmultiplexer symbol Audio equipment symbol Relay set or signalling converter symbol Digital switching symbol Channel translating equipment symbol Theoretical location of circuit access point symbol + +*Note* — Access is normally provided by the exchange switching equipment. + +FIGURE 1/M.565 + +Typical access and test equipment arrangements at international centres + +## **4 Interface requirements at digital access points** + +- 4.1 Digital access points at 64 kbit/s should be operated in the contradirectional mode and should meet the interface requirements of § 1.2.3 of Recommendation G.703 [1]. +- 4.2 Digital path access points, operated at 1544 kbit/s or 2048 kbit/s (or higher hierarchical bit rates) should meet the interface requirements of Recommendation G.703 [1]. +- 4.3 Interface requirements for digital access points on circuits using an encoding technique other than PCM are under study by Study Group IV. + +## **Reference** + +- [1] CCITT Recommendation, *Physical electrical characteristics of hierarchical digital interfaces*, Vol. III, Rec. G.703. \ No newline at end of file diff --git a/marked/M/T-REC-M.570-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.570-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24aa7095d08e5d114daaee02c32d3cbfcfd33503 --- /dev/null +++ b/marked/M/T-REC-M.570-198811-I_PDF-E/raw.md @@ -0,0 +1,223 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.570** + +**MAINTENANCE : +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**CONSTITUTION OF THE CIRCUIT; +PRELIMINARY EXCHANGE OF INFORMATION** + +**ITU-T Recommendation M.570** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation M.570 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **CONSTITUTION OF THE CIRCUIT; PRELIMINARY EXCHANGE OF INFORMATION** + +1 As soon as it is decided to bring a new circuit into operation, the technical services of the terminal countries should agree upon the circuit control station, and the technical service of each transit country should advise the other technical services concerned of the name of the sub-control station chosen for its territory. If the circuit is routed in a direct group or block crossing a transit country without demodulation or demultiplexing, no sub-control station need be provided for the transit country. When a circuit is subjected to analogue-to-digital conversion using, for example, a transmultiplexer, the location of the transmultiplexer should be designated as circuit sub-control station. + +Also the technical services of all the countries concerned should send to the technical service responsible for the circuit control station information which will be required for the preparation of the circuit routing form (see the Appendix I to this Recommendation) using the letter and number code on the form. The information for a circuit without audio sections will consist of the numbers of the groups or blocks used and the number of the channel in each group or block. + +In the case of a both-way circuit, the circuit order of selection should be stated, including the method by which the International Switching Centre selects circuits (i.e., sequentially by circuit, fully randomly or sequentially by block of circuits but randomly within the block, etc.). + +When the circuit is assigned its designation (according to Recommendation M.140, § 1), the Administration with control station responsibility will assemble the necessary technical and operational information. This should be entered into the list of Related Information (as defined in Recommendation M.140, § 2) which consists of the items shown in Annex A. + +## **2 Exchange of information** + +The information should preferably be sent by telex and the examples below show typical telex messages concerning the provision of Bucuresti-London 1 when the circuit is analogue, digital or mixed analogue/digital. + +This method using the telex services enables agreement on routing details to be obtained quickly and also enables circuit routing forms to be completed by the technical services responsible for the circuit control stations as soon as a circuit is put into service or rearranged. + +*Example I* – Telex message from the technical services of the United Kingdom to the technical services of the Federal Republic of Germany, Austria, Hungary and Romania for an analogue circuit: + +NETWORK CONTROL DIVISION BTI LONDON TO FTZ DARMSTADT +GENTEL WIEN +GENTEL BUDAPEST +GENTEL BUCUREŞTI + +OUR REF. + +PROPOSE PROVISION OF BUCUREŞTI/A1 – LONDON/M B1 +USING FRANKFURT – LONDON 1201/9 SIGNALLING 500/20 +GRATEFUL FOR YOUR AGREEMENT OR COUNTER PROPOSALS. REGARDS. + +*Example II* – Telex message from the technical services of the Federal Republic of Germany in reply to telex in example I: + +FTZ SCHALT DMST A NETWORK CONTROL DIVISION BTI LONDON + +10 APR + +YOUR REF. + +OUR REF. + +2 = FEDERAL REPUBLIC OF GERMANY 3 – BUCUREŞTI – LONDON 1 + +5 = FRANKFURT/MAIN + +A = FFT – L 1201/9 B = 840 + +A = FFT – WIEN 1201/11 B = 740 + +REGARDS. + +COPIES TO WIEN, BUDAPEST, BUCUREŞTI. + +Similar messages could be used for a digital circuit. The channel to be used then could be, for example, Frankfurt-London 30N003/22. + +*Example III* – Telex message from the technical services of the United Kingdom to the technical services of the Federal Republic of Germany, Austria, Hungary, and Romania for a mixed analogue/digital circuit using a transmultiplexer at Frankfurt: + +NETWORK CONTROL DIVISION BTI LONDON TO FTZ DARMSTADT + +GENTEL WIEN + +GENTEL BUDAPEST + +GENTEL BUCUREŞTI + +OUR REF. + +PROPOSE PROVISION OF BUCUREŞTI – LONDON 1 + +USING FRANKFURT – LONDON 30NC004/7 SIGNALLING SYSTEM No.5 + +GRATEFUL FOR YOUR AGREEMENT OR COUNTER PROPOSALS. REGARDS. + +*Example IV* – Telex message from the technical services of the Federal Republic of Germany in reply to the telex in Example III: + +FTZ SCHALT DMST TO NETWORK CONTROL DIVISION BTI LONDON + +10 APR + +YOUR REF. + +OUR REF. + +2 = FEDERAL REPUBLIC OF GERMANY + +5 = BUCUREŞTI – LONDON 1 + +3 = FRANKFURT/MAIN + +19 = FRANKFURT/MAIN + +A = FFT – L 30N0004/7 B = 840 + +A = FFT – WIEN 12008/7 B = 740 + +REGARDS. + +COPIES TO WIEN BUDAPEST, BUCUREŞTI. + +Using the above-mentioned information and the data supplied by sub-control stations, the circuit control station makes out a *circuit routing form* which is used as a level diagram for voice-frequency sections (see Appendix I to this Recommendation, which can serve as a routing form or level diagram). This routing form shows the nominal relative levels at: + +- circuit control and sub-control stations; +- frontier stations, if the circuit is reduced to a voice-frequency section across a frontier; +- stations where the circuit is reduced to voice frequency, in those cases where the circuit passes via a series of groups or blocks. + +The technical service of the circuit control station sends the routing form to the technical services of the sub-control stations of the international circuit concerned: + +- a) only at the specific request of one of the Administrations concerned when the circuits are routed on one channel of a single international group link or digital path; +- b) in all cases for circuits otherwise constituted. + +The despatches are sent in duplicate, one copy for the technical service and one for the sub-control station. + +# ANNEX A + +(to Recommendation M.570) + +## **Designation information on international public switched circuits** + +### A.1 *Designation* + +The designation is according to Recommendation M.140, § 1. + +### A.2 *Related information* + +The additional information on public switched circuits is covered by the following items: + +- RI 1. Urgency for restoration; +- RI 2. Terminal countries; +- RI 3. Carriers' names; +- RI 4. Control and sub-control station(s); +- RI 5. Fault report points; +- RI 6. Routing; +- RI 7. Association; +- RI 8. Equipment information; +- RI 9. Use; +- RI 10. Transmission medium information; +- RI 11. Composition of transmission; +- RI 12. Bandwidth or bit rate; +- RI 13. Signalling information; + +The various items will be dealt with in § 2 of Recommendation M.140. + +# APPENDIX I (to Recommendation M.570) + +## **Routing form for an international circuit** + +1. Date of..... +2. Technical service of ..... American Telephone & Telegraph Co. +3. Circuit designation ..... New York (10) – Stockholm 1 +4. Length ..... 7870 km +- 5a. Control station..... New York +- 5b. Sub-control stations..... London, Stockholm +6. Date of putting into service ..... October 1972 +7. Type of ISC at control station end..... Analogue +8. Type of ISC at sub-control station end..... Analogue +- 9a. Echo suppressors at ..... New York (½), Stockholm (½) +- 9b. Echo cancellers at..... None +10. Compandors at ..... None +11. Signalling ..... System No. 5 +12. Switching equipment..... +13. Special equipment at ..... None +14. Special concentrator1 ..... None +15. Estimated weighted noise power ..... –48 dBm0 (36 dBA) +16. Special performance requirements at ..... None +17. Hangover time of suppressors at ..... New York: 50 ms +Stockholm: 50 ms +18. Estimated total distorsion power ..... Not applicable +19. Transmultiplexer at ..... None +20. Echo cancellation stages at..... +21. Echo path delay characteristics, per state, at ..... + +| Stations and constitution | Length of section (in km) | Nominal relative level at reference measurement point 2 (dBr) | | Estimated group delay time at 1020 Hz (milliseconds) | Remarks 3 | +|---------------------------|---------------------------|--------------------------------------------------------------------------|------------|------------------------------------------------------|------------------------------------------------------------------------| +| | | Direction↓ | Direction↑ | | | +| (A) | (B) | (C) | (D) | (E) | (F) | +| New York | | 0.0 | –4.5 | | | +| 34-A-/C-/8 | 522 | | | 3.2 | | +| Green Hill | | +7.0 | +7.0 | | {Through-group connection points Conil (Spain)
Sesimbra (Portugal)} | +| 1602-05-/A-/5 | 5813 | | | 36.5 | | +| London | | +4.0 | –4.0 | | | +| 1211/1 | 1535 | | | 9.5 | | +| Stockholm | | +3.5 | –11.0 | | | + +1 Insert CMS only, through and CMS, or none as appropriate (or equivalent). + +2 An asterisk after the relative level indicates that the nominal value of the impedance at the measuring point differs from 600 ohms. + +3 When this column is completed for loaded cables the effective bandwidth of the section will be inserted. \ No newline at end of file diff --git a/marked/M/T-REC-M.580-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.580-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f50bdd639d0adebc7b5fc97679ad2cbe6e50cdc --- /dev/null +++ b/marked/M/T-REC-M.580-198811-I_PDF-E/raw.md @@ -0,0 +1,503 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.580** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**SETTING UP AND LINING UP +AN INTERNATIONAL CIRCUIT +FOR PUBLIC TELEPHONY** + +**ITU-T Recommendation M.580** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation M.580 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SETTING UP AND LINING UP AN INTERNATIONAL CIRCUIT FOR PUBLIC TELEPHONY** + +## **1 Introduction** + +This Recommendation applies to all circuits operated on a manual, semi-automatic or fully automatic basis, whether provided solely by analogue transmission and switching systems or by a mixture of analogue and digital systems. + +As an alternative to the procedures given in §§ 7 to 14 which require testing personnel to be present at both ends of the circuit, § 15 gives a procedure involving the use of the CCITT Automatic Transmission Measuring and Signalling Testing Equipment (ATME) No. 2 (Recommendation O.22 [1]) (with Type a responding equipment) which may be used subject to the agreement of the Administrations involved. + +## **2 Organization** + +The guiding principles for the general maintenance organization of international circuits are given in Recommendation M.70. + +2.1 An international circuit may consist of various national and international circuit sections; these circuit sections consist of two telephony channels, one for each direction of transmission, or a mixed analogue/digital terminal section or a digital terminal section. The types of circuits and circuit sections for public telephony are described in Recommendation M.562. + +2.2 At the terminal stations of the circuit, access points are provided in accordance with Recommendation M.110 (see also Recommendation M.565). At intermediate stations an access point is provided (see also Recommendation M.110 for transit circuits), its position in the circuit being so chosen that as much as possible of the audio-frequency apparatus in the station is included in any measurement made at that station in the direction of transmission concerned. + +2.3 In establishing an international circuit, the circuit, line and circuit section access points define the limits of the circuit, line and circuit section, and these are used as the basic elements involved in setting-up, lining-up, and fault location. + +*Note* – The line access point at the terminal station will also be used as the circuit section access point at that station. + +## **3 Limits for the overall loss of a circuit and circuit sections** + +### **3.1 *Limits for overall loss at 1020 Hz*** + +The objective is to make the value of overall loss at 1020 Hz as near as possible to its nominal value. When adjustment is provided in steps, these should enable the loss to be adjusted to within $\pm 0.3$ dB of the nominal value. + +### **3.2 *Limits for the overall loss/frequency characteristic*** + +National telephone networks are planned and provided by Administrations to give satisfactory telephone transmission on national calls in the most economical way and will, in consequence, have but little margin against additional transmission impairment in calls on the longest connections. + +International telephone calls require the two corresponding parts of the national networks in the terminal countries to be interconnected by a switched chain of international circuits. The present CCITT plan for worldwide telephone connections specifies a maximum of six international circuits in a connection. In some circumstances the nominal reference equivalent of the connection could be 3 dB greater than in the past. This additional loss, in combination with increased line noise, makes it very desirable to minimize the transmission impairments introduced by the international circuits. + +In order to have an objective for a circuit for maintenance purposes, the following principles should be applied. + +3.2.1 The overall loss/frequency distortion of a circuit depends on whether it is set up entirely on 4-kHz spaced channels, or entirely on 3-kHz spaced channels or on combinations of such channels, even including small sections of audio cable. Three sets of limits are given in Tables 1/M.580, 2/M.580 and 3/M.580. + +The principles on which the tables are based are as follows: + +- the maximum loss in the relevant frequency range should not be greater than 9.0 dB relative to the loss at 1020 Hz in order to avoid disturbing the noise power distribution in the circuit to any extent; +- the use of equalizers at intermediate stations should be avoided as far as possible; +- where a mixed type of composition is used the arrangement of 3-kHz plus 4-kHz spaced channels in a circuit would cater for most of the cases of composition likely to be encountered in practice (for example, one 3-kHz channel in series with two 4-kHz channels); +- Administrations should be allowed some flexibility to use a measure of pre-equalization if necessary in order to avoid low-level signals entering a long section. + +TABLE 1/M.580 + +#### **Limits for the overall loss/frequency characteristic between circuit access points and the access points of circuit sections for circuits and circuit sections using 4 kHz spacing** + +| Frequency Hz | Overall loss relative to that at 1020 Hz | | +|--------------|------------------------------------------|----------------------------------------------| +| | Between circuit access points | At the access point at intermediate stations | +| | dB | dB | +| Below 300 | not less than 0.0 otherwise unspecified | not less than -3.0 otherwise unspecified | +| 300 to 400 | +3.5 to -1.0 | +9.0 to -3.0 | +| 400 to 600 | +2.0 to -1.0 | +6.0 a -3.0 | +| 600 to 2400 | +1.0 to -1.0 | +6.0 to -3.0 | +| 2400 to 3000 | +2.0 to -1.0 | +6.0 to -3.0 | +| 3000 to 3400 | +3.5 to -1.0 | +9.0 to -3.0 | +| Above 3400 | not less than 0.0 otherwise unspecified | not less than -3.0 otherwise unspecified | + +TABLE 2/M.580 + +#### **Limits for the overall loss/frequency characteristic between circuit access points and the access points of circuit sections for circuits and circuit sections using 3 kHz spacing** + +| Frequency Hz | Overall loss relative to that at 1020 Hz | | +|--------------|------------------------------------------|----------------------------------------------| +| | Between circuit access points | At the access point at intermediate stations | +| | dB | dB | +| Below 200 | not less than 0.0 otherwise unspecified | not less than -1.5 otherwise unspecified | +| 200 to 250 | +10.5 to -0.5 | not less than -1.5 otherwise unspecified | +| 250 to 300 | +6.5 to -0.5 | +9.0 to -1.5 | +| 300 to 2700 | +1.0 to -0.5 | +7.0 to -1.5 | +| 2700 to 2900 | +2.5 to -0.5 | +7.0 to -1.5 | +| 2900 to 3050 | +6.5 to -0.5 | +9.0 to -1.5 | +| Above 3050 | not less than 0.0 otherwise unspecified | not less than -1.5 otherwise unspecified | + +TABLE 3/M.580 + +#### **Limits for the overall loss/frequency characteristic between circuit access points and the access points of circuit sections for circuits and circuit sections using 3 kHz and 4 kHz spacing** + +| Frequency Hz | Overall loss relative to that at 1020 Hz | | +|--------------|------------------------------------------|----------------------------------------------| +| | Between circuit access points | At the access point at intermediate stations | +| | dB | dB | +| Below 300 | not less than 0.0 otherwise unspecified | not less than -3.0 otherwise unspecified | +| 300 to 400 | +3.5 to -1.0 | +9.0 to -3.0 | +| 400 to 600 | +2.0 to -1.0 | +6.0 to -3.0 | +| 600 to 2400 | +1.0 to -1.0 | +6.0 to -3.0 | +| 2400 to 2700 | +2.0 to -1.0 | +6.0 to -3.0 | +| 2700 to 2900 | +2.5 to -1.0 | +9.0 to -3.0 | +| 2900 to 3050 | +6.5 to -1.0 | +9.0 to -3.0 | +| Above 3050 | not less than 0.0 otherwise unspecified | not less than -3.0 otherwise unspecified | + +3.2.2 Table 1/M.580 is based on the limits recommended for a pair of 4-kHz channel equipments (Recommendation G.232 [2]), a small addition having been made to the recommended limits to allow for the additional distortions likely to be introduced by the group link and by the circuit and exchange apparatus. The equalization limits are three times the circuit limits. + +Table 2/M.580 is similarly based on the limits recommended for a pair of 3-kHz channel equipments (Recommendation G.235 [3]) with an allowance for the group link and for circuit and exchange apparatus. + +For international circuits composed of 4-kHz and 3-kHz sections, the limits given in Table 3/M.580 are a combination of the limits given in Tables 1/M.580 and 2/M.580, taking into account the factors given in 3.2.1 a) to 3.2.1 c) above. + +The limits to be imposed on the loss/frequency characteristic at intermediate stations are also shown in Tables 1/M.580, 2/M.580 and 3/M.580. + +Where a circuit or circuit section contains mixed analogue/digital channels, the table to be used should be based on the channel spacing of the analogue carrier associated with the mixed circuit or circuit section. + +A circuit section or that portion of a circuit made up of wholly digital channels should be treated as an analogue circuit section or circuit having 4 kHz spaced channels. + +Circuit sections made up of digital or mixed analogue/digital terminals should follow the limits given for measurements between circuit access points in Table 1/M.580. + +## **4 Setting up and lining up analogue and mixed circuit sections** + +4.1 The circuit sub-control stations responsible for the various national and international circuit sections should arrange to set up these sections. + +The circuit sections are lined up and the overall loss/frequency characteristic of each is recorded from terminated-level measurements. + +This is done by sending at a level of $-10 \text{ dBm}0$ at the reference test frequency at the access point at the intermediate sub-control station or at the line access point at the control station or terminal sub-control station and adjusting the received level at the access point at the adjacent intermediate sub-control station as close as possible to its nominal level in the direction of transmission concerned. + +4.2 The loss/frequency characteristic should then be measured at frequencies chosen from the following list, according to the characteristics of the circuit section to be set up: + +200, 250, 300, 400, 600, 800, 1000, 1400, 2000, 2400, 2700, 2900, 3000, 3050 and 3400 Hz. + +Technical services may agree to make measurements at other frequencies if it is considered useful to do so. The test signals should be applied at a level of $-10 \text{ dBm}0$ . + +For circuit sections effectively transmitting up to only 3000 Hz (for example, circuits using 3 kHz spaced channels) the measurement at 3400 Hz is, of course, not applicable. + +The overall loss at 1020 Hz1) should be as near as possible to the nominal value. + +The overall loss at other frequencies should lie within the limits given in Tables 1/M.580, 2/M.580 and 3/M.580 (see § 3.2.1). + +For each circuit section the results for each direction of transmission are forwarded to the control and terminal sub-control stations. + +At terminal stations, during these measurements, the signalling connections to the automatic equipment should be disconnected if the signalling units are incorporated in the carrier terminal equipment. When the line-signalling relay sets are included in the lines and apparatus being measured, any voice-frequency signalling receiver must be made inoperative. + +--- + +1) For further information about the choice of test signal frequency, refer to Recommendation O.6 [4]. + +## 5 Setting up and lining up mixed analogue/digital and digital terminal circuit sections + +5.1 As shown in Figure 2/M.562, mixed analogue/digital and digital terminal circuit sections can occur at both terminal and intermediate locations in a circuit. However, in both cases these terminal circuit sections fall wholly within an individual Administration's boundaries. Thus, they would normally be set up and lined up independently according to national practices. However, Administrations may bilaterally choose to apply a single procedure for setting up and lining up a combination of a digital circuit section terminated at each end by a mixed analogue/digital terminal section. In this case, the procedures and limits given in § 4 above for analogue circuit sections should be applied to this combination of circuit sections. + +5.2 In order to provide some guidelines for the setting up and lining up of mixed analogue/digital terminal sections, two suggested procedures are described in Annex A. + +## 6 Setting up and testing digital circuit sections + +6.1 As with digital channels, because the test procedures required for setting up and initially testing the digital path also set-up and test the digital circuit section, no additional tests on a circuit section are recommended. + +## 7 Setting up and lining up an international circuit2) + +### 7.1 *Setting up the circuit* + +7.1.1 The sub-control station responsible for the various circuit sections having completed the setting-up and lining-up of those sections should arrange to connect them together and advise the control station. In addition, the control and terminal sub-control stations, in conjunction with their testing points, should ensure that all associated signalling, switching and other terminal equipment has been connected, is free from faults, and is operating satisfactorily. + +7.1.2 When the control station has been advised by all the sub-control stations that the sections constituting the circuit have been connected together, the control station should agree with the sub-control stations upon a time at which the whole circuit may be lined up. + +### 7.2 *Lining up the circuit* + +#### 7.2.1 *Preliminary work* + +7.2.1.1 The receiving terminal sub-control station studies the test results of the individual circuit sections, particularly observing the way in which the variations within the permissible tolerances will accumulate when the sections are interconnected. The receiving terminal sub-control station for each direction of transmission determines from these studies and observations the amount of gain and equalization adjustment which will be required at intermediate and terminal stations to obtain a satisfactory overall characteristic. + +7.2.1.2 From the test results the cumulative overall loss over the frequency band at intermediate sub-control stations is calculated with respect to the overall loss at 1020 Hz. An equalizer should be fitted at the request of the receive terminal sub-control station at those stations at which the sum of the measured overall loss/frequency characteristics of the individual sections exceeds the provisional limits (see 3.2.2). In determining the limits, due account must be taken of the presence of 3-kHz spaced channel translating equipment. + +The number of intermediate equalizers should be kept to a minimum. When the receiving terminal sub-control station has been advised by all the other sub-control stations that the circuit sections and any prescribed equalizers have been connected together, a time at which the circuit can be lined up should be agreed upon. + +#### 7.2.2 *Adjustment of the overall loss at the reference test frequency* + +7.2.2.1 At the appropriate time of line-up, the control station, in cooperation with the various sub-control stations, proceeds with the overall line-up of the circuit, first at a frequency of 1020 Hz3). + +For this, the control station arranges to send an 1020 Hz test signal at a level of $-10$ dBm0, for example at the circuit access point of the circuit. In addition, the level at the line access point at the terminal stations should be adjusted as close as possible to the nominal value. + +2) The procedure given in § 15 may be followed as an alternative to those given in §§ 7 to 14 if agreement has been reached with the distant Administration to use ATME No. 2 for lining up, measurement of circuit noise and functional tests. It should be noted that this procedure does not include the tests in § 12. The Administrations involved should consider scheduling such tests, if applicable, when cooperative effort can be arranged. + +3) For further information about the choice of test signal frequency, refer to Recommendation O.6 [4]. + +7.2.2.2 The intermediate sub-control stations will then arrange to measure the level of the 1020 Hz test signal and to adjust it to the nominal value at the access points of the circuit (as defined in § 2.2) in that direction of transmission. Measurements and adjustments should also be made at frontier stations where the circuit includes an audio-frequency section crossing a frontier. + +7.2.2.3 At the distant terminal sub-control station the received level of the test signal should be adjusted until the required overall loss is obtained at the circuit access point. + +The procedure is then repeated for the other direction of transmission of the circuit. + +In order to minimize cumulative gain or loss at 1020 Hz the receive terminal sub-control station may request intermediate sub-control stations to alter the gain setting for the receive direction of their sections by not more than one gain control step. In this way it should be possible to compensate, at successive stations, the departures from the nominal value while staying within the permissible limits. Theoretically, this adjustment will be needed in not more than half the stations. + +7.2.2.4 It is not possible to recommend a value for the nominal transmission loss between the circuit access points of a switched public telephony circuit because of the freedom accorded to Administrations in arranging the relative levels at these points. However, bearing in mind that at each end of the circuit the attenuation between the circuit access point and the virtual switching points will have a fixed and known value and that it is possible to *build out* the wiring to circuit access points to a known loss, the send level at the circuit access point should be so chosen that, on the circuit, the circuit level diagram is respected. + +#### 7.2.3 *Measurement of the overall loss/frequency response* + +7.2.3.1 When the circuit has been lined up at 1020 Hz, measurements should be made between circuit access points at the terminal stations and also at intermediate sub-control stations and frontier stations when an audio-section crosses a frontier. The loss/frequency characteristic should then be measured at frequencies chosen from the following list, according to the characteristics of the circuit to be set up: + +200, 250, 300, 400, 600, 800, 1000, 1400, 2000, 2400, 2700, 2900, 3000, 3050 and 3400 Hz. + +Technical services may agree to make measurements at other frequencies if it is considered useful to do so. The test signals should be applied at a level of $-10 \text{ dBm0}$ . + +7.2.3.2 If necessary, the receiving terminal sub-control station may equalize the circuit at this stage by means of an equalizer in that station, so that the overall loss/frequency characteristic lies within the required limits. Minor adjustments to compensate for accumulated manufacturing tolerances in pad and equalizer values can now also be made at intermediate stations. Those stations at which receive equalizers were necessary should remeasure the section including the equalizer, making terminated-level measurements. The results of those measurements should be passed to the receive terminal station. + +These results now replace those previously submitted under operation § 7.2.1.2 for these sections, and are the results with which comparison is to be made in subsequent maintenance. (The overall loss/frequency characteristic of a *section + equalizer* may not now lie within the limits appropriate to a circuit section. It should be noted that one consequence of this is that such a combination cannot be used as a replacement for a faulty circuit section; for such replacement purposes the circuit section should be transferred without the equalizer.) + +7.2.4 When the above measurements and necessary adjustments have been carried out, the control and terminal sub-control stations ensure that the limits are achieved. The circuit can be regarded as being lined up. + +## 8 **Measurement of circuit noise** + +8.1 Where a circuit is routed via a circuit multiplication system employing digital speech interpolation techniques, it may not be possible to make a reliable noise test using the method described in this section. In this case, a total distortion measurement should be made instead, as described in § 9.3. + +8.2 The measurement of circuit noise should be made for both directions of transmission. + +For the measurements of noise in one direction of transmission, the far end of the circuit should be terminated at the circuit access point, with an appropriate value of pure resistance. + +At the circuit access point at the other end of the circuit (near end) a measurement of the psophometric voltage should be made, using a psophometer having the characteristics recommended by the CCITT (see the weighting curve for this psophometer in Recommendation O.41 [5]). + +8.3 Circuit line-up noise measurements should be compared with the noise maintenance objectives shown in Table 4/M.580 according to the length of the circuit concerned. The values in Table 4/M.580 apply to single + +measurements (see Note). It is assumed that the noise measurement will follow the measurements and adjustments outlined in §§ 7.2.2 and 7.2.3. + +8.4 Where the measured noise is higher by 5 decibels or more than the appropriate value from Table 4/M.580, or is higher than $-37$ dBm0p, whichever is the more stringent requirement, action should immediately be taken to locate and remedy any fault where possible. It may be useful to compare noise measurements on circuits of identical or similar constitution to help locate a possible fault. + +TABLE 4/M.580 +**Noise objectives for public telephone circuit maintenance** + +| | | | | | | | | +|------------------------|-------|------------|-------------|--------------|--------------|----------------|------------------| +| Distance in kilometres | < 320 | 321 to 640 | 641 to 1600 | 1601 to 2500 | 2501 to 5000 | 5001 to 10 000 | 10 001 to 20 000 | +| Noise (dBm0p) | $-55$ | $-53$ | $-51$ | $-49$ | $-46$ | $-43$ | $-40$ | + +*Note* – At the present time the section of a circuit provided by a satellite employing FDM techniques with an earth station at its receiving end conforming to the INTELSAT Standard A (Figure of merit 40.7 dB/K) or Standard C (Figure of merit 39.0 dB/K) contributes approximately 10 000 pW0p ( $-50$ dBm0p) of noise. The noise contributed by earth stations with revised figures of merit are for further study. Therefore, for the purpose of determining maintenance limits for noise measurements on international public telephony circuits, the length of this section may be considered to be equivalent to a terrestrial length of 2500 km. + +The section of a circuit provided by a satellite employing FDM techniques with an earth station at its receiving end conforming to the INTELSAT Standard B contributes approximately 80 000 pW0p ( $-41$ dBm0p) of noise for FM companded circuits. The methods of determining total distortion and/or noise objectives for such a circuit are given in Recommendation M.590. + +The contribution to noise of a circuit section provided by a satellite employing TDM techniques remains a subject for further study. + +8.5 Where the measured noise is greater than $-44$ dBm0p, and once it is ensured that no fault exists, the fitting of a compandor should be considered. Such consideration is particularly necessary if the circuit is likely to be used in a 6-circuit chain. Reference should be made to Recommendation G.143 [6] for technical guidance on the fitting of compandors. In particular, note should be taken of the need to restrict their use to circuit sections provided on inherently stable transmission systems. + +8.6 The noise measured at the circuit access point during the initial line-up should be recorded for comparison against subsequent maintenance measurements. + +## 9 Measurement of total distortion + +### 9.1 General + +This measurement is required for composite (i.e. mixed analogue/digital) circuits only. The measurement of total distortion should be made for both directions of transmission. The measuring equipment should be as specified in Recommendation O.132 [7]. The measurement equipment should be applied at the circuit access points. A test frequency of 1020 Hz should be used. + +It is assumed that the measurements and adjustments outlined in §§ 7.2.2 and 7.2.3 above have already been carried out. + +### 9.2 Measurement of total distortion using a test signal level of $-10$ dBm0 + +9.2.1 The results of the total distortion measurement should be compared with the total distortion objectives shown in Table 5/M.580 according to the number of Quantizing Distortion Units (QDUs) in the circuit and the total length of the analogue circuit sections. + +9.2.2 If these objectives are exceeded by a circuit which has satisfied the noise objectives described in § 8, then a fault on a digital equipment causing excessive quantizing distortion should be suspected. + +TABLE 5/M.580 + +#### **Signal-to-total distortion ratio for public telephone circuit maintenance using a test frequency level of –10 dBm0** + +| Type of circuit | Number of QDU
(Note 1) | Unit | Distance in analogue transmission (km)
(Note 3) | | | | | | | +|-------------------|---------------------------|------|----------------------------------------------------|------------------|-------------------|--------------------|--------------------|----------------------|------------------------| +| | | | < 320 | 321
to
640 | 641
to
1600 | 1601
to
2500 | 2501
to
5000 | 5001
to
10 000 | 10 001
to
20 000 | +| Analogue | 0
(Note 2) | dB | 45 | 43 | 41 | 39 | 36 | 33 | 30 | +| Composite circuit | 0.5 | dB | 35 | 35 | 34 | 34 | 33 | 31 | 29 | +| | 1 | dB | 33 | 33 | 32 | 32 | 31 | 30 | 28 | +| | 2 | dB | 30 | 30 | 30 | 29 | 29 | 28 | 27 | +| | 3 | dB | 28 | 28 | 28 | 28 | 28 | 27 | 26 | +| | 3.5 | dB | 27 | 27 | 27 | 27 | 27 | 26 | 26 | +| | 4 | dB | 27 | 27 | 27 | 27 | 26 | 26 | 25 | + +*Note 1* – The number of QDUs contributed by various digital processes are given in Table 1/G.113 [8]. + +*Note 2* – The values are idle noise terminated with a nominal impedance of 600 Ω. + +*Note 3* – The section of the circuit provided by satellite (between earth stations) employing FDM techniques contributes approximately 10 000 pWp (–50 dBm0p) of noise. Therefore, for the purpose of determining the total distortion limits for international public telephony circuits, the length of this section may be considered, from Table 4/M.580, to be equivalent to 2500 km. + +### 9.3 Measurement of total distortion using a test signal level of –25 dBm0 + +9.3.1 On circuits routed via a circuit multiplication system employing digital speech interpolation, this measurement may be regarded as a substitute for a measurement of circuit noise. The results of the measurement should be compared with the objectives shown in Table 6/M.580. + +9.3.2 If the measured total distortion is higher by 5 dB or more than the appropriate value from Table 6/M.580 or is higher than –37 dBm0p, whichever is the more stringent requirement, on a circuit which has satisfied the test in § 9.2 above, then a fault on an analogue circuit section causing excessive noise should be suspected. + +9.3.3 For maintenance purposes, a measurement of total distortion using a –25 dBm0 signal level can be useful on all composite circuits. In conjunction with a measurement using a –10 dBm0 signal level, it may be possible to identify whether a fault lies in an analogue or digital circuit section, from end-to-end measurements using the same instrument. If the circuit satisfies the objectives of Table 5/M.580 but exceeds the objectives of Table 6/M.580, a faulty analogue circuit section should be suspected. Conversely, if the objectives of Table 6/M.580 are satisfied but those of Table 5/M.580 are not, faulty digital equipment is likely. + +*Note* – If the number of QDUs is 4 and the analogue noise level is –55 dBm0p, this procedure will produce less accurate results. In this case, a –30 dBm0 test tone will be appropriate to check the analogue section, when a circuit is not fitted with an echo-canceller or the echo canceller can be disabled. + +TABLE 6/M.580 +**Signal-to-total distortion ratio for public telephone circuit maintenance using +a test frequency level of –25 dBm0** + +| Type of circuit | Number of QDU
(Note 1) | Unit | Distance in analogue transmission (km)
(Note 3) | | | | | | | +|-------------------|---------------------------|------|----------------------------------------------------|------------------|-------------------|--------------------|--------------------|----------------------|------------------------| +| | | | < 320 | 321
to
640 | 641
to
1600 | 1601
to
2500 | 2501
to
5000 | 5001
to
10 000 | 10 001
to
20 000 | +| Analogue | 0
(Note 2) | dB | 30 | 28 | 26 | 24 | 21 | 18 | 15 | +| Composite circuit | 0.5 | dB | 29 | 27 | 26 | 24 | 21 | 18 | 15 | +| | 1 | dB | 28 | 27 | 25 | 23 | 21 | 18 | 15 | +| | 2 | dB | 27 | 26 | 25 | 23 | 20 | 18 | 15 | +| | 3 | dB | 26 | 25 | 24 | 23 | 20 | 18 | 15 | +| | 3.5 | dB | 26 | 25 | 24 | 22 | 20 | 18 | 15 | +| | 4 | dB | 25 | 24 | 23 | 22 | 20 | 17 | 15 | + +*Note 1* – The number of QDUs contributed by various digital processes are given in Table 1/G.113 [8]. + +*Note 2* – The values are idle noise terminated with a nominal impedance of 600 Ω. + +*Note 3* – The section of the circuit provided by satellite (between earth stations) employing FDM techniques contributes approximately 10 000 pWp (–50 dBm0p) of noise. Therefore, for the purpose of determining the total distortion limits for international public telephony circuits, the length of this section may be considered, from Table 4/M.580, to be equivalent to 2500 km. + +## 10 Measurements of other parameters + +Circuits used for reserve purposes in certain applications, for example, data and facsimile transmission, have particular requirements in respect of group-delay distortion, noise, etc. Reference should be made to the CCITT Recommendations relating to the type of circuit concerned in order to find what these requirements are. + +## 11 Check of signalling level + +Measurements should also be made to check that the absolute power level of the signalling current at the transmitting end of the circuit in each direction of transmission has a nominal value in accordance with Table 7/M.580, or as agreed between Administrations for signalling systems not covered by CCITT Recommendations. + +Reference should be made to Recommendation M.470 for the check of Signalling System R2 line signals. The interregister signals will be found in Table 7/M.580. + +*Note* – Such a check is not appropriate for speech circuits of Signalling Systems No. 6 and No. 7. + +## 12 Functional tests + +12.1 When the line-up procedure as described above has been completed, a check should be made of the functioning of the compandors where appropriate in accordance with Recommendation M.590. This should be followed by a speaking test including a check of the satisfactory operation of echo suppressors and echo cancellers and a check that signalling transmission over the circuit is satisfactory. For an automatically operated circuit using channel-associated signalling, the signal-transmission testing facilities available at the control station should at least enable a check to be made of the line-signals transmitted between circuit access points, for example, to verify that the forward signals are followed by the return of the appropriate backward signals. + +12.2 For manually operated circuits a check should be made to confirm that line-signalling to the distant end is satisfactory. + +Where possible, both for manually and automatically operated circuits, test calls should be made to the distant-end operators or technical staff, as the case may be, to check the circuit both for signalling and transmission performance. + +12.3 Some Administrations find a rapid check of the echo control devices useful when setting up a circuit. A suitable method is described in [9] which can be carried out by agreement between Administrations. + +In addition, a check of the echo control device with the corresponding tester as specified in Recommendations O.22 [1] and O.25 [10] should be made if available. + +## **13 Exchange of information on echo canceller test capability** + +When echo cancellers are fitted to a circuit, tests by other Administrations using test facilities specified in Recommendation O.22 [1] can successfully be carried out only if the canceller stages and echo path delay characteristic are programmed into the test sequence. Therefore, the Administration placing echo cancellers in their international switching centre should so apprise the other Administration(s). This may be done by a specific communication, for example a telex message, or by including such information with the exchange of routine maintenance schedules (Recommendation M.605). + +## **14 Records of results** + +Each station should keep a careful record of the measurement results for the receiving direction of transmission of the sections terminating in the station. A record should be kept of the overall loss at the reference frequency and also of the overall loss/frequency characteristic relative to the overall loss at 1020 Hz. + +The measurements made must include the characteristics of any equalizers which have been fitted and the final choice of gain setting must be stated. + +The receiving terminal stations will also maintain a careful record of all the section measurements in the receiving direction of transmission. In addition the terminal sub-control station should send a copy of the overall records to the control station which thus will hold records for both directions of transmission. (Stations should prepare local records of in-station tests of equalizers and records of equalizer and gain settings.) + +Careful records of the results of tests given in §§ 4 to 13 above should be made by both terminal stations. The control station should hold a copy of the records for both directions of transmission. + +## **15 Setting up and lining up an international circuit using ATME** + +15.1 The following procedure should be followed when it has been agreed between the Administrations concerned that ATME No. 2 can be used. Generally, it is suitable only when there are no intermediate circuit sub-control stations and for circuits which do not have particular measurement requirements (see § 10). + +TABLE 7/M.580 +**Absolute power of signalling current** + +| Type of signalling | Signalling frequency | | Absolute power | +|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------| +| | Nominal value | Tolerance | Nominal value in dBm0
(tolerance $\pm 1$ dB) | +| Manual signalling (System No. 1) | 500 Hz
interrupted at
20 Hz | $\pm 2\%$ | uninterrupted
(500 Hz)
0 | +| | | $\pm 2\%$ | interrupted
(500/20 Hz)
-3 | +| One-frequency signalling (System No. 3) | 2280 Hz | $\pm 6$ Hz | -6 | +| Two-frequency signalling (System No. 4) | 2040 Hz
2400 Hz | $\pm 6$ Hz
$\pm 6$ Hz | -9
-9 | +| Multi-frequency systems (Systems No. 5 and 5 bis)
Line signals a) (two-frequency) | 2400 Hz
2600 Hz | $\pm 6$ Hz
$\pm 6$ Hz | -9
-9 | +| Register signals b) (multi-frequency) | 700 Hz
900 Hz
1100 Hz
1300 Hz
1500 Hz
1700 Hz | $\pm 6$ Hz
$\pm 6$ Hz
$\pm 6$ Hz
$\pm 6$ Hz
$\pm 6$ Hz
$\pm 6$ Hz | -7
-7
-7
-7
-7
-7 | +| Signalling System R1. Line signals | 2600 Hz | $\pm 5$ Hz | -8/-20 c) | +| Register signals d) | 700 Hz
900 Hz
1100 Hz
1300 Hz
1500 Hz
1700 Hz | $\pm 1.5\%$
$\pm 1.5\%$
$\pm 1.5\%$
$\pm 1.5\%$
$\pm 1.5\%$
$\pm 1.5\%$ | -7
-7
-7
-7
-7
-7 | +| Signalling System R2. Register signals b) | 1380 Hz
1500 Hz
1620 Hz
1740 Hz
1860 Hz
1980 Hz | $\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz | -8
-8
-8
-8
-8
-8 | +| Forward | | | | +| Backward | 540 Hz
660 Hz
780 Hz
900 Hz
1020 Hz
1140 Hz | $\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz
$\pm 4$ Hz | -8
-8
-8
-8
-8
-8 | + +- a) For compound signals, the difference between the sent levels of $f_1$ and $f_2$ should not exceed 1 dB. +- b) The difference between the sent levels of two frequencies of which a signal is composed should not exceed 1 dB. +- c) -8 dBm0 for the duration of the signal or for a minimum of 300 ms (whichever is the shorter) and for a maximum of 550 ms after which the level of the signal shall be reduced to -20 dBm0. +- d) The difference between the sent levels of the two frequencies of which a signal is composed should not exceed 0.5 dB. + +### 15.2 *Setting up the circuit* + +The circuit control and sub-control stations in conjunction with their testing points should ensure that all associated signalling, switching and other terminal equipment has been connected, is free from faults and is operating satisfactorily. This should include the check of signalling level specified in § 11. The sub-control station should advise the control station that these checks have been made. + +### 15.3 *Lining up the circuit* + +On receiving the advice from the sub-control station, the control station should test the circuit using ATME No. 2. The time at which the tests are performed should take into account the availability schedules of the ATME No. 2 responding equipments and the period of peak traffic at the distant terminal exchange (see Recommendation M.605, § 3). The ATME No. 2 should be programmed to perform the full range of transmission measurements and signalling tests. + +If the transmission level in the receive direction at the control station is not within $\pm 1$ dB of its nominal level, the level should be adjusted to within $\pm 0.3$ dB of its nominal level, and the circuit should then be retested. + +If the transmission level in the receive direction at the sub-control station distant end is not within $\pm 1$ dB of its nominal level or if any of the other limits specified in this Recommendation are not met in either direction of transmission, then the procedures given in §§ 7 to 14 should be followed. + +When the ATME No. 2 tests have been successfully completed, the control station informs the sub-control station of the results. + +### 15.4 *Other tests* + +When the line-up procedure, as described above, has been completed, a check should be made of the functioning of the compandors, where appropriate, in accordance with Recommendation M.590. This should be followed by a speaking test including a check of the satisfactory operation of echo suppressors and echo cancellers. + +### 15.5 *Recording of results* + +The control station should record all results given by ATME No. 2 for both directions of transmission. + +## ANNEX A + +(to Recommendation M.580) + +### **Methods proposed for setting up and lining up of mixed analogue/digital terminal sections** + +### A.1 *Check of the mixed analogue/digital terminal equipment* + +The mixed analogue/digital terminal equipment must be checked to ensure that it meets CCITT Recommendations and the other relevant specifications (e.g. the check should include a general visual inspection and vibration tests, if applicable). The check should, if possible, also include a test of both the equipment and transmission system related alarms and alarm indicators associated with the mixed terminal. This is of particular importance if the equipment has remained unused since acceptance tests were carried out after installation. + +#### A.2 *Measurement and adjustment of levels* + +Either of the methods A or B below may be used in lining up the circuit sections on a mixed terminal, depending on the features of the equipment and on the availability of digital test equipment. Note, both methods require all of the circuit sections associated with the particular primary block on the mixed terminal to be out-of-service. + +#### A.2.1 *Method A – use of internal test tone* + +This method is only applicable for mixed analogue/digital terminals equipped with an internally generated digital test signal with a power of $-10$ dBm0 at 1020 Hz4), which can be applied internally either in turn or simultaneously in the analogue receive output direction to all the circuits. + +--- + +4) For further information about the choice of test signal frequency, refer to Recommendation O.6 [4]. + +As shown in a) of Figure A-1/M.580, in the first step the internal digital test signal is actuated. Then for each internal circuit the analogue receive direction pad is adjusted, using an analogue meter to bring the receive level as near as possible to its nominal value. + +To complete the measurement in step 2 as shown in b) of Figure A-1/M.580, first the internal digital test signal is removed and the digital side of the terminal is looped (either internally or externally). Next, using external analogue test equipment a nominal 1020 Hz, -10 dBm0 tone is applied to the analogue transmit input port of each channel in turn. The transmit pad is then adjusted using the analogue meter connected to the analogue receive output port of the terminal to again bring the receive level as near as possible to its nominal value. + +##### A.2.2 *Method B – use of digital test equipment* + +This method, as shown in c) of Figure A-1/M.580, assumes that the appropriate digital test equipment is available to make measurements on individual 64 kbit/s time slots within the 2048 (1544) kbit/s digital path on the digital side of the mixed terminal section. + +To make the measurements on the circuit sections, in the analogue to digital direction, a nominal 1020 Hz test signal is sent over each circuit section in turn at a level of -10 dBm0. The 64 kbit/s time slot corresponding to each circuit is monitored in turn at the primary PCM hierarchical level, using appropriate digital test equipment, and each circuit is adjusted, where applicable, to obtain the correct bit sequence. + +Next, in the digital to analogue direction, a bit sequence corresponding to a nominal 1020 Hz test tone at -10 dBm0 is applied to the 64 kbit/s time slot corresponding to each circuit section in turn, at the primary PCM hierarchical level, using a digital word generator, and each circuit is adjusted to bring the received level as near as possible to its nominal value. + +#### A.3 *Other measurements* + +No other measurements are recommended at the time when the mixed analogue/digital terminal circuit sections are being set up and lined up. However, other measurements may be required when the need is indicated during circuit line-up. + +#### A.4 *Mixed analogue/digital sections at terminal exchanges* + +##### A.4.1 *At analogue switching exchanges* + +Where a mixed analogue/digital terminal circuit section is connected to an analogue switching exchange, method B described above could be extended to include all the audio equipment associated with the switching exchange. In this case the measurements would be made between the digital path access point and the circuit access points (see Figure 1/M.110). The types of measurements to be performed for this case should be dictated by national practices. + +##### A.4.2 *At digital switching exchanges* + +Where a mixed analogue/digital terminal circuit section is connected to a digital switching exchange, method B can also be applied. In this case the digital test equipment shown in c) of Figure A-1/M.580 would be connected at the circuit access point through the digital exchange. The analogue test equipment would be connected at an intermediate access point. The types of measurements to be performed for this case should be dictated by national practices. + +![Three diagrams (a, b, c) showing test configurations for a Mixed A/D terminal section. Diagram (a) shows Method A - Step 1 with a signal source and meters. Diagram (b) shows Method A - Step 2 with a signal source and a meter. Diagram (c) shows Method B with digital equipment and a meter. A legend defines the symbols for digital path access points and line access points.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +The figure consists of three sub-diagrams labeled a), b), and c), each illustrating a different test configuration for a "Mixed A/D terminal section". + +- a) Method A - Step 1:** A "Mixed A/D terminal" is shown. On its left side, two "Digital path access points" (squares with a diagonal line) are connected, labeled "1544 or 2048 kbit/s". A signal source (circle with a sine wave symbol) is connected to the top input of the terminal. On the right side, there are N outputs, labeled 1, ..., N. Each output is connected to a "Line access point" (square with an X). All line access points are connected to a single meter (circle with a needle). A dashed line with an arrow points from the top input of the terminal to the signal source. +- b) Method A - Step 2:** Similar to (a), but the signal source is connected to the bottom input of the terminal. The meter on the right is connected to only one of the line access points. +- c) Method B:** A "Digital equipment" block is connected to two "Digital path access points" (labeled "1544 or 2048 kbit/s"), which are then connected to the "Mixed A/D terminal". On the right side, N outputs (labeled 1, ..., N) are connected to "Line access points". These line access points are connected to a meter (circle with a sine wave symbol). A dashed line with an arrow points from the digital equipment to the first digital path access point. + +A legend at the bottom defines the symbols: + +- Digital path access point +- Line access point + +CCITT- 71250 +d01-sc + +Three diagrams (a, b, c) showing test configurations for a Mixed A/D terminal section. Diagram (a) shows Method A - Step 1 with a signal source and meters. Diagram (b) shows Method A - Step 2 with a signal source and a meter. Diagram (c) shows Method B with digital equipment and a meter. A legend defines the symbols for digital path access points and line access points. + +FIGURE A-1/M.580 + +## References + +- [1] CCITT Recommendation *CCITT automatic transmission measuring and signalling testing equipment ATME No. 2*, Vol. IV, Rec. O.22. +- [2] CCITT Recommendation *12-channel terminal equipments*, Vol. III, Rec. G.232. +- [3] CCITT Recommendation *16-channel terminal equipments*, Vol. III, Rec. G.235. +- [4] CCITT Recommendation *1020 Hz reference test frequency*, Vol. IV, Rec. O.6. + +- [5] CCITT Recommendation *Psophometer for use on telephone-type circuits*, Vol. IV, Rec. O.41. +- [6] CCITT Recommendation *Circuit noise and the use of compandors*, Vol. III, Rec. G.143. +- [7] CCITT Recommendation *Quantizing distortion measuring equipment using a sinusoidal test signal*, Vol. IV, Rec. O.132. +- [8] CCITT Recommendation *Transmission impairments*, Vol. III, Rec. G.113. +- [9] CCITT Supplement *Rapid verification test for echo control devices*, Vol. IV, Supplement No. 2.11. +- [10] CCITT Recommendation *Semi-automatic in-circuit echo suppressor testing system*, Vol. IV, Rec. O.25. \ No newline at end of file diff --git a/marked/M/T-REC-M.585-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.585-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5934c58c373506cd21e306f3291a79a4cc0616b9 --- /dev/null +++ b/marked/M/T-REC-M.585-198811-I_PDF-E/raw.md @@ -0,0 +1,64 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.585** + +**MAINTENANCE : +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**BRINGING AN INTERNATIONAL +DIGITAL CIRCUIT INTO SERVICE** + +**ITU-T Recommendation M.585** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation M.585 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **BRINGING AN INTERNATIONAL DIGITAL CIRCUIT INTO SERVICE** + +## **1        Organization** + +The guiding principles for a general maintenance organization for international circuits are given in Recommendation M.70. + +An international digital circuit may consist of one or more digital circuit sections and digital terminal circuit sections. The types of digital circuit and digital circuit sections for public telephony are described in Recommendation M.562. + +In establishing an international digital circuit, circuit access points define the limits of a circuit. These circuit access points are used as the means for performing functional tests including those for channel associated line signalling. + +## **2        Transmission tests** + +### **2.1      *Error performance*** + +When a circuit is brought into service immediately after the digital path(s) over which it is routed are commissioned, the procedures in Recommendation M.555 (see also Recommendation M.550) are adequate to ensure a satisfactory initial error performance for the circuit. + +When a circuit is brought into service some time after the digital path over which it is routed is commissioned, the circuit control station should ascertain, either directly or from the circuit sub-control station, that the digital path is satisfying the required performance objectives. + +### **2.2      *Other tests*** + +When the circuit is to be fitted with a 64 kbit/s device e.g. echo canceller or $\mu$ /A law converter, these should first be tested before bringing the circuit into service (for echo suppressors and echo cancellers, see Recommendations M.660 and M.665 respectively). + +## **3        Functional tests** + +A speaking test should be made including a subjective check of the satisfactory operation of echo control devices. + +For a circuit using channel-associated signalling, the signal-transmission test facilities available at the control station should at least enable a check to be made of the line-signals transmitted between circuit access points, for example, to verify that the forward signals are followed by the return of the appropriate backward signals. \ No newline at end of file diff --git a/marked/M/T-REC-M.590-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.590-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..52f1cfc6afe72e4f556c00f3a672869743cb6db4 --- /dev/null +++ b/marked/M/T-REC-M.590-198811-I_PDF-E/raw.md @@ -0,0 +1,148 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.590** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**SETTING UP AND LINING UP A CIRCUIT +FITTED WITH A COMPANDOR** + +**ITU-T Recommendation M.590** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.590 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SETTING UP AND LINING UP A CIRCUIT FITTED WITH A COMPANDOR** + +1 The compandor should first be tested in accordance with the appropriate design information which should be made available in a suitable form to repeater station staff. In particular, because the unaffected level of a compandor is defined with reference to an 800 Hz signal, it should be verified for each type of compandor that use of a reference test frequency of 1020 Hz produces the same results as using a reference test frequency of 800 Hz. + +2 Circuits fitted with compandors should be lined up to achieve the same limits as circuits without compandors. The compandor should be fitted to the circuit only after the circuit without its compandor is considered satisfactory in respect of loss and loss/frequency response. It should be noted that to achieve the limits for loss/frequency response on the companded circuit without equalization, it will be necessary for the loss/frequency response of the uncompanded circuit to be within one half of the circuit limits. + +## **3 Measurements of total distortion and idle channel noise** + +After compandors have been fitted, total distortion and idle channel noise measurements should be made. The test signal used for the total distortion measurement should be applied at the unaffected level of the compandor. + +In the case of a circuit which is fitted with a compandor to subjectively reduce the noise generated within a terrestrial circuit section, the measurements should be noted. + +In the case of a circuit which is fitted with a compandor to subjectively reduce the noise generated by a satellite circuit section, the procedure is as follows: + +- For analogue routed circuits1), the noise objectives given in Table 4/M.580 for the appropriate terrestrial length of circuit should be combined with the total distortion objective for the satellite channel2) to produce a total distortion objective for the whole circuit. See Annex A for an example of this calculation. +- For mixed analogue/digital routed circuits, the total distortion objectives given in Table 5/M.580 for the appropriate terrestrial length of circuit should be combined with the total distortion objective for the satellite channel2) to produce a total distortion objective for the whole circuit. See Annex A for an example of this calculation. +- If the measured total distortion is higher than the calculated total distortion objective, then a fault should be suspected and action should be taken to locate and remedy any fault where possible. +- When the total distortion measurement has been made and is found to meet the calculated total distortion objectives, an idle channel noise measurement should be made. +- The idle channel noise measurement should be compared with the maintenance objective given in Table 4/M.580 for the appropriate length of circuit, taking into account the note associated with that table which states that the satellite section of the circuit may be considered to have an equivalent length of 2500 km. This is a valid consideration provided that the total distortion objective of the satellite channel is not greater than –30 dBm0p. +- If the measured value is higher by 5 dB or more than the noise objective given in Table 4/M.580 or is higher than –37 dBm0p, whichever is the more stringent requirement, then a fault should be suspected and action should be taken to locate and remedy any fault where possible. + +4 A speaking test should be made on the circuit to verify the correct operation of the compandors. + +--- + +1) It should be noted that in the case of mixed analogue/digital circuits, if the unaffected level is other than –10 dBm0 then this procedure will produce less accurate results and in this case it should be used as a general guide only. + +2) The total distortion objective for INTEL SAT single sideband Standard B satellite channels is –41 dBm0p (FM companded circuit). + +## 5 Designations + +Companded circuits and groups of circuits which are all companded should be designated in accordance with Recommendation M.140. + +*Note* – Repeater station staff should be well instructed as to the subjective effect of errors and the location of faults affecting compandors. + +# ANNEX A + +(to Recommendation M.590) + +## **Total distortion and idle channel noise objectives for circuits which are fitted with compandors in order to subjectively reduce the effect of noise generated on satellite channels** + +A.1 A distinction is made between: + +- circuits which are fitted with compandors to subjectively improve the noise generated by a terrestrial section, and +- circuits which are fitted with compandors to subjectively improve the noise generated by a satellite section. + +This distinction is made because in case a) it is not possible to specify noise or total distortion objectives. However, in case b), the satellite system operator can specify noise objectives for the satellite section. Thus these limits can be combined with those contained in Recommendation M.580 to calculate an overall limit. + +A.2 *Examples of calculations of total distortion for case b)* + +### *Example 1* + +Consider an analogue circuit which has a terrestrial length of 1600 km and which is routed via a satellite which has a specified idle channel noise objective of $-41$ dBm0p for analogue channels. + +From Table 4/M.580, the noise objective for a length of 1600 km is $-51$ dBm0p. + +Combining $-41$ dBm0p and $-51$ dBm0p gives a total distortion of $-40.59$ dBm0p. + +Thus the total distortion objectives should be $-41$ dBm0p. + +### *Example 2* + +Consider a mixed analogue/digital circuit which has a terrestrial length of 1600 km, two analogue/digital conversions using 8 bit coding (i.e., 2 QDUs) and which is routed via a satellite which has a specified idle channel noise objective of $-41$ dBm0p for analogue channels. + +From Table 5/M.580, the total distortion objective for a length of 1600 km is $-30$ dB or $-40$ dBm0p. + +Combining $-41$ dBm0p and $-40$ dBm0p gives a total distortion of $-37.46$ dBm0p. + +Thus the total distortion objective should be $-37$ dBm0p. + +A.3 *Idle channel noise objectives for case b)* + +It is stated in § 3 that provided the total distortion objective of the satellite channel is not greater than $-30$ dBm0p, it is valid to consider that this section of the circuit has an equivalent length of 2500 km. + +This statement is justified because the compandor characteristic which is illustrated in Figure A-1/M.590 indicates that an idle channel noise of $-30$ dBm0p generated in a satellite section would be reduced to $-50$ dBm0p. This value of noise is that which from Table 4/M.580 is attributed to an equivalent circuit length of 2500 km. + +![Diagram of a compandor characteristic showing signal levels (dBm0) across a Compressor, Channel, and Expander. The diagram shows how signal levels are compressed in the compressor and then expanded back in the expander. Dashed lines indicate unaffected levels.](de6e8b740c69dac308cce9edfec3eff4_img.jpg) + +The diagram illustrates the signal level characteristics of a compandor system. The system is divided into three main sections: Compressor, Channel, and Expander. The signal levels are measured in dBm0. + +**Signal Levels (dBm0):** + +- 0 +- 10 (Unaffected level) +- 15 +- 20 +- 25 +- 30 +- 35 +- 40 +- 50 +- 60 + +**Compressor:** The compressor section shows signal levels being compressed. The input levels (0, -10, -20, -30, -40, -50, -60) are compressed to intermediate levels (-5, -10, -15, -20, -25, -30, -35) before entering the channel. + +**Channel:** The channel section shows the compressed signal levels being transmitted. The levels remain at -5, -10, -15, -20, -25, -30, and -35 dBm0. + +**Expander:** The expander section shows the signal levels being expanded back to their original levels (0, -10, -20, -30, -40, -50, -60) after exiting the channel. + +**Legend:** + +- : Unaffected level + +T0401400-89 +d01-sc + +Diagram of a compandor characteristic showing signal levels (dBm0) across a Compressor, Channel, and Expander. The diagram shows how signal levels are compressed in the compressor and then expanded back in the expander. Dashed lines indicate unaffected levels. + +FIGURE A-1/M.590 +Compandor characteristic \ No newline at end of file diff --git a/marked/M/T-REC-M.600-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.600-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.600-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.605-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.605-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.605-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.605-198811-I_PDF-E/643d86ebba41e16a88461bfcb3741de6_img.jpg b/marked/M/T-REC-M.605-198811-I_PDF-E/643d86ebba41e16a88461bfcb3741de6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9fd3e6b23892e9e154e92f41586ce1855b716c0 --- /dev/null +++ b/marked/M/T-REC-M.605-198811-I_PDF-E/643d86ebba41e16a88461bfcb3741de6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6abc2a343a16898bebf2c417c7f501584dab7149292dc4d13b6dd36bcfdb451d +size 302552 diff --git a/marked/M/T-REC-M.605-198811-I_PDF-E/7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg b/marked/M/T-REC-M.605-198811-I_PDF-E/7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a91c36aa0723adcf930e1e99fbcb73baa50dcafa --- /dev/null +++ b/marked/M/T-REC-M.605-198811-I_PDF-E/7c2f0efb2c5d10a52ce19ba33d9d3cec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f039808c252ceca7ce99f50ead39d8942d7f8d2328b36c785569653f4edef11d +size 249187 diff --git a/marked/M/T-REC-M.605-198811-I_PDF-E/eb903413d070b64f45cd763804ba443f_img.jpg b/marked/M/T-REC-M.605-198811-I_PDF-E/eb903413d070b64f45cd763804ba443f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f11f208780f3f658cb032ae3c398f14d9ad84f52 --- /dev/null +++ b/marked/M/T-REC-M.605-198811-I_PDF-E/eb903413d070b64f45cd763804ba443f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd3a57fc059388a74ac9e9ab859c22dbea4ddb733941348b7521b6dc165f22e8 +size 208728 diff --git a/marked/M/T-REC-M.610-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.610-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.610-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.630-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.630-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.630-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.630-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.630-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05914682cafa928d149dac52c290add13111ec33 --- /dev/null +++ b/marked/M/T-REC-M.630-198811-I_PDF-E/raw.md @@ -0,0 +1,51 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.630** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**MAINTENANCE OF CIRCUITS USING +CONTROL CHART METHODS** + +**ITU-T Recommendation M.630** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.630 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **MAINTENANCE OF CIRCUITS USING CONTROL CHART METHODS** + +Administrations may replace the periodical measurements specified in Recommendations M.610 and M.620 by measurements using sampling methods. They will need to arrange their own programme for these on a bilateral basis. Administrations applying such methods are requested to report their conclusions to the CCITT giving their comments on: + +- the method used (for information, some methods are described in [1]); +- the saving in manpower; +- the transference of work from field staff to administrative offices; +- any observed change in the quality of groups of circuits maintained by sampling methods. + +# **Reference** + +- [1] CCITT Handbook on *Quality of service, network management and network maintenance*, ITU, Geneva, 1984. \ No newline at end of file diff --git a/marked/M/T-REC-M.650-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.650-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..67bea688cbaf0f0dd92fc90ca7e0ef22414325a9 --- /dev/null +++ b/marked/M/T-REC-M.650-198811-I_PDF-E/raw.md @@ -0,0 +1,65 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.650** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**ROUTINE LINE MEASUREMENTS TO BE +MADE ON THE LINE REPEATERS OF +AUDIO-FREQUENCY SECTIONS OR CIRCUITS** + +**ITU-T Recommendation M.650** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.650 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +© ITU 1988, 1993 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +# ROUTINE LINE MEASUREMENTS TO BE MADE ON THE LINE REPEATERS OF AUDIO-FREQUENCY SECTIONS OR CIRCUITS + +Besides the routine tests made from end-to-end on the complete circuit, routine maintenance measurements of the equipment of audio-frequency circuits should be made throughout the line for purposes of repeater maintenance. + +These routine measurements comprise: + +- measurements of repeater gain (where there is little or no feedback); +- measurements of *relative level* at the output of the repeaters (when measuring overall loss on the complete circuit, in the frontier stations and wherever else such measurements are considered necessary); +- measurements of circuit *stability* and test for determining singing points (with 2-wire repeaters). + +The measurement of stability is obtained from the definition of stability $\sigma$ of the circuit considered: + +$$\sigma = q - (q_1 + q_2)/2$$ + +$q$ being the mean of the nominal overall loss of the circuit in each of the two directions of transmission under normal working conditions and $q_1$ and $q_2$ being the singing points measured for the two directions of transmission respectively. + +In order to measure these singing points in the case of a 2-wire circuit, singing is started by increasing, step-by-step and simultaneously for the two directions of transmission, the gains of one or of several repeaters (preferably those in the middle of the circuits because they are usually in the most critical position from the point of view of singing). Having done this, without touching the adjustment which has been obtained, the transmission in the reverse direction is suppressed and the overall loss of the circuit at 1020 Hz is measured for the forward direction of transmission; this is the singing point $q_1$ above. Next the transmission in the first direction is suppressed and the overall loss of the circuit at 1020 Hz is measured for the reverse direction of transmission: this is the singing point $q_2$ above. + +When the circuit is composed of 2-wire and 4-wire sections, or carrier sections, the method of measurement given for 2-wire circuits is valid. + +This stability should be determined with the ends of the circuit open-circuited; when there are high-impedance relays permanently connected across the line during a call, these relays may remain during stability tests. \ No newline at end of file diff --git a/marked/M/T-REC-M.660-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.660-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.660-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.675-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.675-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.675-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.675-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/M/T-REC-M.675-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0388c474151f825ac46712aa3dd6a0440d37459 --- /dev/null +++ b/marked/M/T-REC-M.675-198811-I_PDF-E/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a50f2fc27faa1d542e8b302e58e1fb816fcf7024184fdadab27be956de57988 +size 101015 diff --git a/marked/M/T-REC-M.675-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg b/marked/M/T-REC-M.675-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fffd8b015eb873b5594816de720bd5967220b9d --- /dev/null +++ b/marked/M/T-REC-M.675-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:784356d4f3d130f73e1625e063df66db1616343d30a648b68c38e8d953e41700 +size 55965 diff --git a/marked/M/T-REC-M.70-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.70-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.70-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.70-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.70-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24504ecb5946358ab49316f8864cbef21e63edb5 --- /dev/null +++ b/marked/M/T-REC-M.70-198811-I_PDF-E/raw.md @@ -0,0 +1,84 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.70** + +# **MAINTENANCE : INTRODUCTION AND GENERAL PRINCIPLES** --- + +## **GUIDING PRINCIPLES ON THE GENERAL MAINTENANCE ORGANIZATION FOR TELEPHONE - TYPE INTERNATIONAL CIRCUITS** + +**ITU-T Recommendation M.70** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +- 1 ITU-T Recommendation M.70 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **GUIDING PRINCIPLES ON THE GENERAL MAINTENANCE ORGANIZATION FOR TELEPHONE-TYPE INTERNATIONAL CIRCUITS** + +### **1 General** + +In order to furnish guiding principles to Administrations, the CCITT recommends the following principles for the general maintenance organization for international circuits. + +1.1 Definitions relating to the various maintenance elements, each representing a set of functions, are given in Recommendations M.710 to M.725 for automatic circuits, and in Recommendations M.1012 [1], M.1013 [2], M.1014 [3] for leased and special circuits. + +1.2 The size and complexity of the maintenance organization will depend on the particular case and the particular country concerned. In some instances it may be possible to carry out all sets of functions from a single location; in others only some of the functions might be combined and carried out from one location. The precise arrangement will depend on the Administration concerned, and the CCITT limits itself to defining the functions of the separate elements, leaving the manner in which the elements are grouped to be determined by the Administration. + +1.3 If a country so desires and/or if it judges that the complexity of its international telecommunications so requires, the international maintenance organization can be responsible for all types of circuit for which Study Group IV makes recommendations. + +### **2 Types of circuits to be catered for** + +The types of circuits to be catered for are as follows: + +public circuits: + +- telephone circuits, +- voice-frequency telegraph circuits, +- phototelegraph circuits, +- sound-programme circuits, etc.; + +leased circuits: + +- telephone circuits: point-to-point and multiterminal, +- voice-frequency telegraph circuits, +- data circuits: point-to-point and multiterminal, +- multi-facility circuits, that is, phototelegraph plus voice-frequency telegraph; speech plus voice-frequency telegraph; simultaneous or alternative transmission, +- phototelegraph circuits, +- sound-programme circuits, etc. + +### **3 Maintenance organization** + +The maintenance of international public telephone circuits relies upon the ability of each Administration to fulfil the various functions and responsibilities noted in the Series M Recommendations. Where such circuits are manual, as opposed to automatic, it is assumed that the Administration will select and provide the relevant elements such as the *fault report point (circuit)* and the *testing point (transmission)* together with *circuit control* and *sub-control station* assignments as appropriate. + +For automatic circuits all the elements noted in Recommendation M.710 apply. + +Leased and special international circuits require the services of a Transmission Maintenance Point (International Line) (TMP-IL) which is described in Recommendation M.1014 [3]. The circuit control and sub-control functions and responsibilities on leased and special international circuits are noted in Recommendations M.1012 [1] and M.1013 [2] and include a close cooperation with the TMP-IL. + +For operations at other levels (group, supergroup, etc.), specific responsibilities are allotted to particular repeater stations. At each level, maintenance is based on the appointment of a *control station* and one or more *sub-control stations*. Additional information concerning control and sub-control stations follows in Recommendations M.80 and M.90 and is supplemented by that contained in Recommendations M.1012 [1] and M.1013 [2], M.723, M.724, N.5 [4] and N.55 [5]. + +The attention of Administrations is drawn to the need for exchanging contact forms (similar to those for maintenance units for automatic circuits as described in Recommendation M.93) which give telephone numbers, staffing hours, etc. for units involved in the maintenance of leased circuits and the higher order transmission systems. + +## References + +- [1] CCITT Recommendation *Circuit control station for leased and special circuits*, Vol. IV, Rec. M.1012. +- [2] CCITT Recommendation *Sub-control station for leased and special circuits*, Vol. IV, Rec. M.1013. +- [3] CCITT Recommendation *Transmission maintenance point (international line) (TMP-IL)*, Vol. IV, Rec. M.1014. +- [4] CCITT Recommendation *Sound programme control, sub-control and send reference stations*, Vol. IV, Rec. N.5. +- [5] CCITT Recommendation *Organization, responsibilities and functions of control and sub-control stations for international television connections, links, circuits and circuit sections*, Vol. IV, Rec. N.55. \ No newline at end of file diff --git a/marked/M/T-REC-M.715-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.715-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.715-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.715-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.715-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d42901f7694435eed2b1b7a5bcc039f141bdd160 --- /dev/null +++ b/marked/M/T-REC-M.715-198811-I_PDF-E/raw.md @@ -0,0 +1,96 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.715** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**FAULT REPORT POINT (CIRCUIT)** + +**ITU-T Recommendation M.715** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.715 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **FAULT REPORT POINT (CIRCUIT)** + +## **1 Definition of fault report point (circuit)** + +The fault report point (circuit) is an element within the general maintenance organization for the international automatic and semi-automatic telephone service at each international centre or common for more than one international centre. + +The fault report point (circuit) is equipped with all the necessary facilities and arranged in such a way that it may receive fault reports relating to one or more specifically identified circuits from different sources or make such fault reports to other points and initiate the fault localization and clearing operations. + +The fault report point (circuit) will undertake its given responsibilities and functions for circuits provided by wholly analogue transmission and switching systems, and those provided by a mixture of analogue and digital systems. + +## **2 Responsibilities and functions** + +The fault report point (circuit) is responsible for the following set of functions: + +- 2.1 Receiving fault reports from: + - similar fault report points of other Administrations; + - fault report point (network); + - fault indication functions in repeater stations and the various testing points (e.g. transmission, line signalling, switching and interregister signalling). This can be done manually by the staff, or automatically by automatic supervision functions built into the switching and/or transmission system. +- 2.2 Recording the fault reports and keeping fault records up to date. +- 2.3 Performing preliminary diagnosis to determine to which maintenance unit the fault has to be assigned for clearance. +- 2.4 Initiating detailed fault location and subsequent clearing. +- 2.5 Sending fault reports as appropriate to: + - circuit control station in its own country in case of controlling end; + - the distant end fault report point (circuit) in case of non controlling end; + - the fault report point (network). +- 2.6 Providing the information and cooperation needed to deal with inquiries by traffic and maintenance staff or by the fault report point (circuit) at the distant end. +- 2.7 Advising the fault report point (network), the network analysis point, the system availability information point and the network management (implementation and control point) (see Recommendation E.413 [1]) of faults affecting the automatic telephone service as required. +- 2.8 Requesting the circuit control station within its own country, if controlling end, to arrange for the withdrawal from service of circuits reported faulty. +- 2.9 Keeping informed of the progress of fault clearance. +- 2.10 Receiving the information about the cause of the faults. +- 2.11 Notifying details of fault clearance to the point of origin of a fault report when the fault has been cleared. +- 2.12 Requesting the circuit control station to arrange for the return of the circuit of service, if controlling end. +- 2.13 Making or arranging for an analysis of faults as may be necessary. + +- 2.14 Identifying repeated faults and advising the circuit control station. +- 2.15 Forwarding details of faults found or faults the causes of which could not be found to the network analysis point for analysis to detect long-term trends. + +## **3 Facilities** + +The fault report point (circuit) should be provided with the following facilities: + +### **3.1 *Service circuits*** + +Access to various kinds of service circuits, e.g.: + +- direct telephone service circuits to relevant contact points within its Administration or to other Administrations in the home country, or in other countries; +- teleprinter circuits; +- telex, teletex, telefax, etc. + +### **3.2 Access to information concerning circuits in service, for instance, by means of data terminals.** + +### **3.3 Access to information from the internal and, where provided, external supervisory functions of stored-program control (SPC) exchanges and/or transmission systems, for instance, by means of data terminals.** + +### **3.4 Access to manual and automatic maintenance access lines as described in Recommendation O.11 [2].** + +# **References** + +- [1] CCITT Recommendation *International network management-Planning*, Vol. II, Rec. E.413. +- [2] CCITT Recommendation *Maintenance access lines*, Vol. IV, Rec. O.11. \ No newline at end of file diff --git a/marked/M/T-REC-M.716-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.716-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.716-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.720-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.720-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..67199315b6635e7732e33f8d7a70e3d4ba11d6cf --- /dev/null +++ b/marked/M/T-REC-M.720-198811-I_PDF-E/raw.md @@ -0,0 +1,99 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.720** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**NETWORK ANALYSIS POINT** + +**ITU-T Recommendation M.720** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.720 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **NETWORK ANALYSIS POINT** + +### **1 Definition of network analysis point** + +The network analysis point is an element within the general maintenance organization for the international automatic and semi-automatic telephone service associated with one or more international centres. + +It receives information concerning service quality and faults not associated with specific circuits. + +It analyses all relevant information to investigate the problems involved. The general considerations for checking the quality of the international telephone service are given in Recommendation E.420 [1]. + +The network analysis point may request the fault report point (network) to initiate investigatory and/or remedial actions in one or more maintenance centres in the home country or via a fault report point (network) in another country. It acts as a single point of contact for general enquiries concerning the day-to-day maintenance of the international telephone network, as may be made by the maintenance organizations of other Administrations. + +### **2 Responsibilities and functions** + +The network analysis point is responsible for the following set of functions: + +2.1 Analysing all fault reports received from the fault report point (network). + +2.2 Collecting and analysing all information necessary for the evaluation and supervision of the quality of the international service and the diagnosis and localization of faults reported to it. The following items are recommended for consideration: + +- a) Call failure information derived from operator and subscriber reports. +- b) Traffic service observations for preparation of Tables 1/E.422 [2] and 1/E.423 [3]. +- c) Traffic service observations undertaken for specific purposes. +- d) Results of manual and automatic test calls. +- e) Reports from fault report points (network) of other Administrations and also from maintenance units of its own Administration. +- f) Summarized information from group reference pilots. +- g) Information from automatic supervision of switching equipment. +- h) Information that all circuits on a route are busy. +- i) Summarized information from traffic monitoring and accounting equipment. +- j) Information derived from circuit and circuit group surveillance equipment. +- k) Periodic data from traffic measuring equipment, e.g. loading in erlangs, percentage occupancy and overflow intensities. + +2.3 Analysing summaries of transmission measurements that may be received from maintenance units of its own Administration. + +2.4 Receiving information concerning major breakdowns affecting the international telephone service and evaluating their effect with respect to network condition. + +2.5 Receiving reports of all events likely to affect the international telephone service. + +2.6 Analysing out-of-service times and cooperating with the maintenance units in their efforts to reduce such times to a minimum. + +2.7 Making optimum use of statistical methods (e.g. trouble pattern techniques) for determining the probable location of failure points. + +- 2.8 Cooperation with the network analysis points of other countries in order to coordinate action in case of service defects existing in the part of the network depending on those points. +- 2.9 Employing information concerning routing, signalling, switching, and transmission systems in its country and other countries to help locate and clear impediments to good service. +- 2.10 Advising the fault report point (network) of the results of its analyses as necessary. +- 2.11 Receiving general enquiries concerning the maintenance of the international telephone network from other Administrations, and answering such enquiries or undertaking any necessary analyses or investigations. + +### **3 Facilities** + +The network analysis point should be provided with the following facilities: + +- 3.1 Appropriate communication facilities in order to assume its responsibilities. +- 3.2 Access to information from the internal and, where provided, external supervisory and statistical functions of SPC-exchanges, for instance, by means of data terminals. +- 3.3 Means to receive and process information associated with the functions listed above. +- 3.4 Means of storing received and processed information. +- 3.5 Means of accessing stored information. + +# **References** + +- [1] CCITT Recommendation *Checking the quality of the international service*, Vol. II, Rec. E.420. +- [2] CCITT Recommendation *Observations on international outgoing telephone calls for quality of service*, Vol. II, Table 1/E.422 of Rec. E.422. +- [3] CCITT Recommendation *Observations on traffic set up by operators*, Vol. II, Table 1/E.423 of Rec. E.423. \ No newline at end of file diff --git a/marked/M/T-REC-M.721-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.721-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a9c685895b23e79cadf62213b44226e93e5207a --- /dev/null +++ b/marked/M/T-REC-M.721-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a4d6f1181fb021d7aea56d330d7892711e59dcf176b2c7c3c477e468224fe18 +size 7449 diff --git a/marked/M/T-REC-M.721-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.721-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a09b6a73696807cf175d47fab0d50060a11d7850 --- /dev/null +++ b/marked/M/T-REC-M.721-198811-I_PDF-E/raw.md @@ -0,0 +1,66 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.721** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**SYSTEM AVAILABILITY INFORMATION +POINT** + +**ITU-T Recommendation M.721** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.721 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **SYSTEM AVAILABILITY INFORMATION POINT** + +### **1 Definition of system availability information point** + +The system availability information point is an element within the general maintenance organization for the international automatic and semi-automatic telephone service associated with one or more international centres. It collects and disseminates information concerning the non-availability of telecommunications systems which affects the international service. The term availability is used here in the broadest sense of the word. + +### **2 Responsibilities and functions** + +The system availability information point is responsible for the following set of functions: + +- 2.1 Collecting information concerning major breakdowns, planned outages, or other special circumstances in the *national* and *international* networks which would materially affect international traffic whether incoming, outgoing or transit. +- 2.2 Keeping aware of the probable duration of major breakdowns and noting whether the relevant traffic load is such that service is likely to be affected. +- 2.3 Keeping close contact with the restoration control point(s) and assisting in restoration matters. +- 2.4 Collecting information concerning the status of restoration activities related to major failures, and the return to normal conditions. +- 2.5 Making available information concerning failures and restoration progress to interested parties and other centres not directly involved in the activities, as appropriate. +- 2.6 Furnishing reports to the operating authorities of abnormal conditions, as required, including progress reports in connection with prolonged disruptions. +- 2.7 Furnishing major breakdown information to network management or traffic operating personnel when a major breakdown occurs, so that suitable changes may be made in operating procedures. +- 2.8 Notifying other international centres as required, through the appropriate authorities, of actions taken in connection with major breakdowns. +- 2.9 Continuously observing system conditions and if a situation arises where service disturbances can be minimized with a change in normal procedures, advising the appropriate maintenance unit (e.g. concerning postponement of a planned outage). + +### **3 Facilities** + +The system availability information point should be provided with the following facilities: + +- 3.1 Appropriate communication facilities in order to assume its responsibilities. +- 3.2 Means to receive, store, have access to, and up-date system availability information. +- 3.3 Access to information concerning the availability of equipment and routes in SPC exchanges, for instance, by means of data terminals. \ No newline at end of file diff --git a/marked/M/T-REC-M.722-198011-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.722-198011-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12ad9e5a940718b25ace231487002b562f868994 --- /dev/null +++ b/marked/M/T-REC-M.722-198011-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ee4bd0be2498ecdfcea601945b3a32c416d2b423d5f33d2f6c9817f15813e05 +size 7494 diff --git a/marked/M/T-REC-M.724-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.724-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3ad418e436b654f54f8f54af358288b13e931a81 --- /dev/null +++ b/marked/M/T-REC-M.724-198811-I_PDF-E/raw.md @@ -0,0 +1,67 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, symbolizing global communication. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.724** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**CIRCUIT SUB-CONTROL STATION** + +**ITU-T Recommendation M.724** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.724 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **CIRCUIT SUB-CONTROL STATION** + +## **1 Definition of circuit sub-control station** + +The circuit sub-control station is a point within the general maintenance organization for the international automatic and semi-automatic telephone service that assists the circuit control station and fulfils the control responsibilities for a circuit section assigned to it. + +The responsibilities, functions and criteria for appointing circuit sub-control stations given in §§ 2 to 4 below apply to circuits provided solely by analogue transmission and switching systems and those involving a mixture of analogue and digital systems. + +## **2 Responsibilities** + +It is the responsibility of the circuit sub-control station to inform the circuit control station about all noted events likely to affect the circuit under their control. If the circuit sections are assigned to the circuit sub-control for the purpose of controlling them, the circuit sub-control is responsible for these circuit sections in the same way as the circuit control station is for the complete circuit. + +## **3 Functions** + +3.1 Performing the control functions for circuit sections, especially national sections, as given for the circuit control station. + +3.2 Cooperating with the circuit control station and other circuit sub-control stations in ensuring that routine maintenance fault location and clearance are carried out by the responsible testing points and/or maintenance units in a proper manner. + +3.3 Arranging that all relevant details concerning the location and subsequent clearance of faults are reported to the fault report point (circuit) at the controlling end. + +## **4 Appointment of circuit sub-control stations** + +For each circuit used for the automatic and semi-automatic telephone service a terminal circuit sub-control station is appointed. This is generally the end of the circuit remote from the circuit control station. In transit countries in which a circuit is brought to audio frequencies, an intermediate circuit sub-control station is appointed at a suitable point for each direction of transmission. It is left to the Administration concerned to choose: + +- where this point shall be, +- whether the sub-control functions for the two directions of transmission are vested in one station or two stations, +- whether, as may be desirable in the case of a large country, each direction of transmission has more than one circuit sub-control station per transit country. + +The technical service of the Administration concerned indicates its choice to the technical service of the Administration responsible for the control station. \ No newline at end of file diff --git a/marked/M/T-REC-M.725-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.725-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0bfe64f60bbd818f87e5e2f4268676d57dde214b --- /dev/null +++ b/marked/M/T-REC-M.725-198811-I_PDF-E/raw.md @@ -0,0 +1,85 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.725** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**RESTORATION CONTROL POINT** + +**ITU-T Recommendation M.725** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.725 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## **RESTORATION CONTROL POINT** + +### **1 Definition of restoration control point (RCP)** + +The restoration control point (RCP) is an element within the general maintenance organization for the international telecommunication services. It initiates and coordinates service restoration activities in case of failures or planned outages of transmission systems in accordance with plans and *ad hoc* arrangements agreed by the technical services of the Administrations concerned. + +Since two or more RCPs are involved in agreed restoration plans, it is practical to nominate one RCP as the Overall RCP which then initiates and controls implementation of the plan. The additional responsibilities and functions of an Overall RCP are given in § 3 below. + +### **2 Responsibilities and functions** + +The restoration control point (RCP) is responsible for the following set of functions: + +- 2.1 Initiating the implementation of a restoration plan and *ad hoc* arrangements with the other stations involved within its Administration's boundaries. +- 2.2 Monitoring the implementation of the restoration plan. +- 2.3 Coordinating the restoration activities of the repeater stations and other stations involved within its Administration's boundaries. +- 2.4 Liaising with restoration control points of other Administrations as necessary and agreeing the times of events with them. +- 2.5 Exchanging information with the network management (implementation and control point) (see Recommendation E.413 [1]) for coordination purposes as appropriate. +- 2.6 Monitoring and coordinating the return to normal service conditions after the fault has been cleared or the planned work has been finished. +- 2.7 Keeping, throughout the period during which the restoration and the return to normal conditions is executed, an accurate log of events, including any circuit, channel, group, supergroup, etc., or baseband patching which takes place. +- 2.8 Requesting and receiving reports from other RCPs and disseminating this information within its own Administration as required. +- 2.9 Reporting the events to the responsible authorities of its Administration as desired and advising the system availability information point about the progress of restoration. +- 2.10 Sending a final restoration report, after the return to normal, containing all relevant data (including agreed times) for accounting purposes to the responsible authorities within its Administration. +- 2.11 If no restoration plan exists or, for some reason, an existing plan cannot be implemented, advising the responsible authorities in its own Administration and suggesting suitable *ad hoc* arrangements in the light of the information available. + +### **3 Additional responsibilities of an overall RCP** + +The responsibilities of an overall RCP are much the same as an ordinary RCP but with additional responsibilities as follows: + +- 3.1 Initiating the implementation of a restoration plan with other RCPs concerned. +- 3.2 Requesting and receiving reports from other RCPs and disseminating this information as necessary. +- 3.3 Coordinating and controlling all restoration activities including the return to normal conditions. + +### **4 Facilities** + +The restoration control point should be provided with the following facilities: + +- 4.1 Appropriate communication facilities in order to assume its responsibilities. +- 4.2 Access to information appropriate to its functions and this includes: + - a) status of relevant international transmission systems; + - b) current restoration plans; + - c) list of the sections of border-crossing transmission traffic routes; + - d) routing information for international group, supergroup, etc., links; + - e) inventory of spare transmission facilities, in its own and neighbouring countries, lending themselves to restoration. + +## **Reference** + +- [1] CCITT Recommendation *International network management - Planning*, Vol. II, Rec. E.413. \ No newline at end of file diff --git a/marked/M/T-REC-M.726-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.726-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db7acaa57dd3e048863fda4ec147bb5daa2bf6ab --- /dev/null +++ b/marked/M/T-REC-M.726-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:241d044e00f2d11d49b65679320ec118f2b10b1fc3112c60435ec24dcebfc5aa +size 7421 diff --git a/marked/M/T-REC-M.726-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.726-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e355bfdf702df0ddf9364888cc0b30d850bcbec7 --- /dev/null +++ b/marked/M/T-REC-M.726-198811-I_PDF-E/raw.md @@ -0,0 +1,55 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.726** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**MAINTENANCE ORGANIZATION +FOR THE WHOLLY DIGITAL +INTERNATIONAL AUTOMATIC +AND SEMI-AUTOMATIC +TELEPHONE SERVICE** + +**ITU-T Recommendation M.726** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.726 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **MAINTENANCE ORGANIZATION FOR THE WHOLLY DIGITAL INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC TELEPHONE SERVICE** + +The recommended maintenance organization for a wholly digital international telephone service is under study by Study Group IV. The detailed development of such an organization cannot be undertaken until such time as Administrations have gained sufficient experience of the operation and maintenance of digital transmission and switching systems – these systems being relatively few in number in the international network at present. However, based on present knowledge and experience, Study Group IV intends that the maintenance organization for the fully digital international telephone service be based on the following principles and concepts: + +- That there be a gradual evolution of the current maintenance organization (which is intended to cover the wholly analogue and mixed analogue/digital situations) towards the organization suitable for the wholly digital network. The rate of this evolution will reflect the rate of introduction of digital systems in the international and national networks. + +According to this principle, it is recognized that, in the transition from a wholly analogue to a wholly digital network, the maintenance organization of a particular international centre may be responsible for wholly analogue, wholly digital and mixed analogue/digital circuits since the three types may be terminated at a single international centre. + +- That the “element” approach to defining a maintenance organization, as currently used in Recommendations M.710 to M.725, be used to define future maintenance organizations. + +By the intended adoption of this concept it is recognized that the maintenance element approach offers the means of specifying a maintenance organization which can meet the needs of all Administrations, irrespective of the number of international circuits and international switching centres they operate. + +In accordance with the current Study Group IV practice, significant national trends in the area of maintenance organization (for example, the trend towards increased centralization of maintenance) should be reflected in the Series M Recommendations where appropriate. \ No newline at end of file diff --git a/marked/M/T-REC-M.729-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.729-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fa382024b2100b0d31ca46764a4bc1ae778cfa5 --- /dev/null +++ b/marked/M/T-REC-M.729-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b7597024c784a60204e6630f817afd88992b741439892b6176c02b5a5cb49ae +size 7455 diff --git a/marked/M/T-REC-M.729-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.729-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3d329734b8e76041bff8036ade6272553180b594 --- /dev/null +++ b/marked/M/T-REC-M.729-198811-I_PDF-E/raw.md @@ -0,0 +1,65 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.729** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**ORGANIZATION OF THE MAINTENANCE +OF INTERNATIONAL PUBLIC +SWITCHED TELEPHONE CIRCUITS +USED FOR DATA TRANSMISSION** + +**ITU-T Recommendation M.729** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.729 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **ORGANIZATION OF THE MAINTENANCE OF INTERNATIONAL PUBLIC SWITCHED TELEPHONE CIRCUITS USED FOR DATA TRANSMISSION** + +## **1 General** + +1.1 Data transmissions may be made over the public switched telephone network in a manner similar to voice transmissions. Such data calls, while expected in most cases to be satisfactory, cannot always be assured success in view of the variety of routing and transmission characteristics that may be found in national extensions between international switching centers and user stations. + +1.2 As the exact configuration of an international call is essentially impossible to determine without an extensive and complicated tracing process, some means must be specified to enable each Administration to investigate, as it considers necessary, reports of data transmission difficulties. + +## **2 Fault investigations and maintenance** + +2.1 Each country agreeing to the transmission of data over the public switched telephone network shall set up a Data Coordinating Point (DCP)1). This point: + +- shall be the contact point between Administrations for referring data transmission difficulties for investigation in respective national networks; +- shall be the point to undertake discussions and agree on a course of action to be taken on public telephone network circuits regarding data transmission difficulties. It should be noted that agreement may be reached to take no actions regarding the international circuits; +- shall initiate any actions related to national network extensions in accordance with its national practices and procedures. + +2.2 Fault investigations undertaken should be on the basis of the transmission requirements of public telephone calls. Such investigations, while possibly initiated by a DCP, will be carried out by the maintenance organization (Recommendation M.710) according to standards defined by Recommendation M.580, etc. + +2.3 Transmission tests (*fault location or scheduled routine measurements*) between subscriber locations, that is, on an end-to-end basis, are not expected to be made. Considering routing complexities and the low probability of duplicating an exact connection, such end-to-end tests would not necessarily be meaningful and would be very difficult to coordinate. However, if end-to-end tests are deemed to be essential by an Administration, then such tests shall be implemented in accordance with agreements reached by the respective DCPs. + +2.4 Routine maintenance measurements will be accomplished according to agreements reached in conformity with Recommendation M.605. + +--- + +1) The term “point” is used in the same sense as in the M.700 series of Recommendation – see particularly Recommendations M.710. \ No newline at end of file diff --git a/marked/M/T-REC-M.730-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.730-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..70d775d916fb2ded94bae226207d82f6d2d4187a --- /dev/null +++ b/marked/M/T-REC-M.730-198811-I_PDF-E/raw.md @@ -0,0 +1,184 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.730** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**MAINTENANCE METHODS** + +**ITU-T Recommendation M.730** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.730 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **MAINTENANCE METHODS** + +## **1 General** + +In order to meet the service demands of a progressive and rapidly expanding international fully automatic telephone network with the best possible quality of service, it is essential that all factors adversely affecting the quality of service should be detected and service restored as quickly as possible. In setting this objective it is recognized that perfect performance is unattainable and that beyond a certain point, costs can rise sharply out of proportion compared with service quality gain. + +When choosing a suitable maintenance method or a combination of methods one should consider: + +- the reliability of the plant to be maintained; +- the availability of testing and supervisory facilities as well as the availability and quality of manpower in the maintenance organization; +- the availability of facilities in the plant that indicate the existence and frequency of disturbances; +- the availability of arrangements for automatic remedial action; +- the availability of automatic means to process and analyse operational data received from the plant; +- the final objective i.e. to ensure a satisfactory overall service quality (subscriber-to-subscriber) in the international connection, giving equal importance to the national and international parts of the chain that constitute the connection. + +It is recognized that a combination of maintenance methods may be applied. + +## **2 Preventive maintenance methods** + +### **2.1 General** + +The introduction of stored program control (SPC) exchanges and digital transmission systems reduce the need for preventive maintenance. SPC exchanges should in general be provided with functions which supervise the signalling, switching and transmission processes. If a fault occurs or if pre-set disturbance limits are reached, data which indicate the concerned device(s) or circuit(s) should be printed out. + +External supervision, testing and fault localization functions should be avoided if internal functions in SPC exchanges or digital transmission systems can provide the same facilities. + +### **2.2 Functional tests** + +2.2.1 In carrying out functional tests, ordinary working conditions apply and the equipment and circuits are taken as found. + +They are carried out on a systematic basis to discover faults that would influence the quality of service. The response to each signal may be tested by equipment provided for this purpose. Such tests may be applied to any part of the signalling path. + +2.2.2 Functional tests are carried out locally, or from either end of an international circuit to the other. + +2.2.3 The organization of the programme for carrying out functional tests locally is left to the discretion of the Administration responsible for the international exchange. + +2.2.4 Overall functional tests on an international circuit are such that they can be made from one end of the circuit without cooperation of technical personnel at the other end of the circuit. These tests may utilize the switching equipment at each end of the circuit, but such equipment is not being tested directly, only the circuit. + +The verification of satisfactory signalling operation may be done by using various types of tests: + +- Certain types of tests not requiring any special equipment, for example checking that a seizing signal is followed by the return of a proceed-to-send signal and that a clear-forward signal is followed by the return of a release-guard signal. + +- Other types combining several tests, using special equipment at both ends. Any type which is in general use by Administrations may be used if suitable and agreed between the Administrations concerned1). + +### 2.3 *Circuit limit tests* + +2.3.1 A circuit limit test is made to verify that the international circuit meets specified operating margins. These tests enable the performance of the whole international circuit to be checked. They will be made as required but normally at the following times: + +- before putting the circuit into service; +- according to a systematic test programme which may be based on measurement results or fault (trouble) statistics or quality of service observations (see Recommendation M.605). + +They may also be made if functional tests indicate a fault, in order to locate such a fault. + +Circuit limit tests may be made with respect either to transmission or to signalling conditions. + +2.3.2 The frequency of such tests will be determined by the Administrations concerned and the test conditions to be applied will be in conformity with CCITT Recommendations. + +2.3.3 The test equipment, the specifications and methods of gaining access to this equipment are described in the specifications of international signalling, switching and transmission equipment. + +### 2.4 *Limit tests on the constituent parts of a circuit* + +2.4.1 These limit tests are made to verify that the constituent parts of a circuit meet specified operating margins. They will be made as required but normally at the following times: + +- at installation; +- if functional or limit tests on the circuit indicate a fault, if such tests will help in fault location; +- systematic test programmes which may be based on measurement results or trouble statistics or quality of service observations. + +2.4.2 The frequency of such tests will be determined by the Administrations concerned and the test conditions to be applied will be in conformity with CCITT Recommendations. + +2.4.3 Limit tests on constituent parts may indicate that the latter need to be readjusted; in such a case, measurements are made on those constituent parts and they are then readjusted in accordance with the relevant CCITT Recommendations. + +2.4.4 The test equipment, its specification and the provision of access points will be determined by the Administration concerned taking into account the relevant CCITT Recommendations. + +### 2.5 *Maintenance measurements* + +#### 2.5.1 *General* + +Maintenance measurements are made periodically on complete circuits (and exceptionally, are indicated in Recommendation M.610 on their constituent parts). Their object is to indicate whether the circuits and equipments are maintained to their specified values when first put into service and, if not, to allow the necessary readjustment to be carried out. + +Some maintenance measurements are made to check signalling; others are made to check transmission. They are carried out by the respective technical services responsible for signalling and transmission. + +#### 2.5.2 *Measurements concerning signalling* + +The conditions for carrying out such measurements, the apparatus used and the periodicity of operations are determined by the relevant Series Q Recommendations. Interventions following such measurements are determined by: + +- a) CCITT Recommendations; +- b) equipment specifications when these are not given in detail by the CCITT. + +--- + +1) See the specification for the CCITT Automatic Transmission Measuring and Signalling Testing Equipment ATME No. 2 (Recommendation O.22 [1]). + +Information on the equipment and functions required are given in the Recommendations listed in Table 1/M.730. + +TABLE 1/M.730 + +| Signalling System | Recommendation | +|-------------------|----------------| +| No. 4 | Q.138 [2] | +| No. 5 | Q.164 [3] | +| No. 6 | Q.295 [4] | +| R2 | Q.490 [5] | +| No. 7 | Q.707 [6] | + +#### 2.5.3 *Measurements concerning transmission* + +These measurements include: + +- local measurements, for which the Administrations concerned decide the conditions and periodicity; +- circuit and line measurements for which the conditions are generally defined in the Series M Recommendations. + +These Series M Recommendations give, in particular, the periodicity of the measurements and the conditions for readjustment of transmission equipment. (See also Recommendation M.733.) + +The CCITT has already specified certain transmission measuring apparatus, and other apparatus specifications are being studied. + +## 3 **Corrective maintenance methods** + +These methods may apply to certain parts of the plant where it is possible to locate and clear faults solely after they have affected the service. Corrective maintenance, if exclusively practised in the entire plant, can create unsatisfactory service conditions due to extreme variations in functional quality and can cause very irregular application of maintenance effort. + +The application of exclusively corrective maintenance methods would presuppose such system design that even if breakdowns of single units or parts of the plant occur, they should have a minor effect on the service quality offered to the subscribers. + +## 4 **Controlled maintenance methods** + +Whereas it has been the practice to undertake programmes of preventive maintenance procedures together with day-to-day corrective maintenance procedures, recent equipment development has made it possible to introduce new maintenance methods. Modern systems can provide immediate information concerning the existence of irregularities and of abnormal conditions. Although preventive maintenance gives a comparatively good service, the number of defects caused by interference of preventive operations may be considerable. + +A maintenance method utilizing the supervising facilities now available may enable the maintenance organization to considerably reduce preventive routines in the maintenance work. Preventive routine tests may then be replaced by methods of continuous supervision of the function of the plant and by means which check continuously the performance of the equipment and give signals to the maintenance staff when the quality of service is below a preset acceptance limit. Alternatively, when facilities for continuous supervision are not available, a sampling technique could be introduced to determine the number of routine tests necessary to gain a reasonable assurance that all equipments are in proper order. + +Introduction of a system of maintenance control of this kind will necessitate a certain degree of centralization of administrative and technical means in the maintenance organization. Rapid and informative indication of the state and performance of the international and concerned parts of the national network is required from the maintenance point of view at strategic points in the network. + +Various types of information on operational conditions in the plant can be utilized for maintenance supervision purposes, such as: + +- traffic data; +- accounting data; +- maintenance data; +- service performance data. + +Such data may be analysed manually but could also be processed in computers, allowing for a more extensive analysis, for instance, to compare performance statistics with preset standards which are set for particular routes, circuits, etc. Information held in the computer store may be extracted on-line and could be made directly available to those maintenance and management centres where it is required. + +Application of computer processing as described necessitates a high degree of centralization, but also other factors support a centralized maintenance organization such as the increasing use of network management signals. The introduction of processor-controlled switching and digital transmission systems is also expected to increase the possibilities to apply remote controlled and centralized maintenance supervision methods in the future. + +# References + +- [1] CCITT Recommendation *CCITT automatic transmission measuring and signalling testing equipment ATME No. 2*, Vol. IV, Rec. O.22. +- [2] CCITT Recommendation *Instruments for checking equipment and measuring signals*, Vol. VI, Rec. Q.138. +- [3] CCITT Recommendation *Test equipment for checking equipment and signals*, Vol. VI, Rec. Q.164. +- [4] CCITT Recommendation *Testing and maintenance – Overall tests of Signalling System No. 6*, Vol. VI, Rec. Q.295. +- [5] CCITT Recommendation *Testing and maintenance*, Vol. VI, Rec. Q.490. +- [6] CCITT Recommendation *Testing and maintenance*, Vol. VI, Rec. Q.707. \ No newline at end of file diff --git a/marked/M/T-REC-M.731-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.731-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..13eb5a3c521daca7b2475bef44aadbe326bb95e4 --- /dev/null +++ b/marked/M/T-REC-M.731-198811-I_PDF-E/raw.md @@ -0,0 +1,64 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.731** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: +INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**SUBJECTIVE TESTING** + +**ITU-T Recommendation M.731** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.731 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# SUBJECTIVE TESTING + +1 The need for subjective testing of circuits depends to a great extent on whether or not automatic or semi-automatic supervisory, testing and fault localization equipment is already provided. For example, subjective testing of circuits is not necessary on routes where ATME No. 2 (as described in Recommendation O.22 [1]) is available. Also, the supervisory and fault localization functions built into SPC exchanges and digital transmission systems reduce or even remove the need for subjective testing. For those Administrations wishing to use subjective testing, the methods described in §§ 2-4 below are recommended. + +2 Circuits used for the automatic and semi-automatic telephone service may be tested subjectively to reveal gross faults, by systematic test calls from circuit Terminal A to a telephone located at circuit Terminal B. (See Figure 1/M.731.) Such test calling may be done independently of all other tests or combined with functional signalling test calls as described in the *Second method* in Recommendations Q.139 [2] and Q.163 [3] for Signalling Systems No. 4 and No. 5, respectively. Such test calls may be classed as type 3 test calls as defined in Recommendation E.424 [4]. They may be applied on a periodic basis for systematically checking each trunk in a group for excessive echo, clipping, loss, noise, distortion and crosstalk. Any fault suspected as a result of this subjective check should be investigated in the normal manner. When type 3 test calls are used in this manner a test telephone is assumed to exist at the distant international centre. The test telephone is connected to a local exchange, if possible, not located at the same point as the international centre so as to permit a realistic appraisal of the service quality. The test should be initiated at the outgoing terminal for one-way circuits and at both terminals sequentially on both-way circuits. Such test calls for checking service quality should be scheduled with the distant international centre during light load periods. + +3 Another method of subjective testing, that may be alternatively considered involves *type 1 test calls* as defined in Recommendation E.424 [4]. It permits systematic evaluation from Terminal A to a location at Terminal B which would not consist of a test telephone, as shown in Figure 1/M.731, but rather to a test location at Terminal B that is not associated with a local exchange. Such an arrangement might not be as effective in detecting echo control problems (since the simulation of a normal connection would be less realistic) but might be useful when the first technique suggested above is impractical due to local conditions. + +![Diagram of a type 3 test call setup. Terminal A (Switching machine or switchboard) is connected via traffic circuits to Terminal B (Switching machine or switchboard). A circuit test access point is shown at Terminal A. At Terminal B, a test telephone is connected to a local exchange, which is also connected to the switching machine or switchboard. The diagram is labeled CCITT - 36920 d01-sc.](d244183a8ff3d94b0dcf30140f51020d_img.jpg) + +The diagram illustrates the setup for a type 3 test call. On the left, 'Terminal A' contains a 'Switching machine or switchboard'. A 'Circuit test access point' is indicated by a vertical dashed line with arrows. Three horizontal lines represent 'Traffic circuits' connecting Terminal A to Terminal B. On the right, 'Terminal B' also contains a 'Switching machine or switchboard'. A 'Test telephone' is connected to this switching machine. The switching machine is also connected to a 'Local exchangea)'. The diagram is labeled 'CCITT - 36920 d01-sc' at the bottom right. + +Diagram of a type 3 test call setup. Terminal A (Switching machine or switchboard) is connected via traffic circuits to Terminal B (Switching machine or switchboard). A circuit test access point is shown at Terminal A. At Terminal B, a test telephone is connected to a local exchange, which is also connected to the switching machine or switchboard. The diagram is labeled CCITT - 36920 d01-sc. + +a) If possible, not located at the same point as Terminal B so as to develop a realistic return loss. + +FIGURE 1/M.731 +Use of a type 3 test call for systematic circuit evaluation + +4 In order to obtain the greatest value from subjective tests it might be advantageous to apply them in association with the tests prescribed in Recommendation M.610 and with *in-station* tests such as those for the maintenance of echo suppressors. + +# References + +- [1] CCITT Recommendation *Automatic transmission and signalling testing equipment ATME No. 2*, Vol. IV, Rec. O.22. +- [2] CCITT Recommendation *Manual testing*, Vol. VI, Rec. Q.139. +- [3] CCITT Recommendation *Manual testing*, Vol. VI, Rec. Q.163. +- [4] CCITT Recommendation *Test calls*, Vol. II, Rec. E.424. \ No newline at end of file diff --git a/marked/M/T-REC-M.732-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.732-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1c4db942b426ea213db7691ae22148b7642c02c3 --- /dev/null +++ b/marked/M/T-REC-M.732-198811-I_PDF-E/raw.md @@ -0,0 +1,74 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.732** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**SIGNALLING AND SWITCHING +ROUTINE MAINTENANCE TESTS +AND MEASUREMENTS** + +**ITU-T Recommendation M.732** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.732 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SIGNALLING AND SWITCHING ROUTINE MAINTENANCE TESTS AND MEASUREMENTS** + +The object of routine maintenance tests and measurements of signalling and switching is to detect changes in the functioning of signalling and switching which are likely to cause a reduction in the quality of service provided. These changes are those which occur in relation to the values indicated in the specifications for the signalling systems concerned (see the pertinent Series Q Recommendations). In the various sections of the Series Q Recommendations, limits are laid down within which: + +- no action is necessary, +- action is required by the maintenance service at either of the terminal exchanges. + +For Signalling Systems Nos. 4, 5, 6, 7 and R2, reference should be made to Recommendations Q.139 [1], Q.163 [2], Q.295 [3], Q.707 [4] and Q.490 [5] respectively which contain guidance on the methods to be used for signalling and switching routine tests, together with the minimum frequencies at which such tests should be carried out. On routes where ATME No. 2 (Recommendation O.22 [6]) is in use, many of the required tests and measurements can be performed by that equipment. Supervision and fault localization functions included in the exchange and/or in the transmission system also reduce or remove the need for routine maintenance tests and measurements. + +Where staffing arrangements permit, manual and semi-automatic routine maintenance of signalling and switching equipment should be done at times when traffic is light. Any routines performed during normal working hours must be carried out with great care to ensure that the effect on live traffic is minimized. + +In stored program control (SPC) and digital exchanges many of the required checks for correct functioning of signalling and switching equipment are carried out automatically by supervisory functions within the exchange, thus removing the need for the majority of manual and semi-automatic routine tests. One of the characteristics of such supervisory functions is that performance “thresholds” have to be set which, if exceeded, cause appropriate outputs to alert maintenance staff (for example, alarms, printouts, etc.). Maintenance staff should not only ensure that all relevant supervisory functions are invoked, but must regularly review the thresholds set to ensure that faults and problems will be detected before service is unacceptably affected. + +Where the outputs to maintenance staff from SPC and digital exchanges indicate that a fault exists or is suspected, suitable action must be taken to localize the problem. Before seeking cooperation from the distant maintenance centre, maintenance staff shall ensure that the problem is not within their own exchange. As examples, ATME No. 2 (Recommendation O.22 [6]) the facilities given in Recommendation O.11 [7] and the internal self-diagnostic routines within the exchange should be used to this end. + +In view of the variety of different types of international exchange now in use and the differing facilities offered by these exchanges, it is not possible to specify any particular periodicity for routine maintenance tests on signalling and switching equipment. The most appropriate periodicity must be established by the Administration concerned based on such factors as: + +- the availability of staff; +- the technology of the exchange (for example, crossbar, Strowger, digital); +- the incidence of faults and problems within the exchange; +- the possible need for cooperation from distant maintenance centres; +- the periodicities recommended by the manufacturer of the exchange or equipment involved; +- the periodicities given in the Series Q Recommendations cited above. + +# **References** + +- [1] CCITT Recommendation *Manual testing*, Vol. VI, Rec. Q.139. +- [2] CCITT Recommendation *Manual testing*, Vol. VI, Rec. Q.163. + +- [3] CCITT Recommendation *Testing and maintenance – Overall tests of Signalling System No. 6*, Vol. VI, Rec. Q.295. +- [4] CCITT Recommendation *Testing and maintenance*, Vol. VI, Rec. Q.707. +- [5] CCITT Recommendation *Testing and maintenance*, Vol. VI, Rec. Q.490. +- [6] CCITT Recommendation *CCITT automatic transmission measuring and signalling testing equipment ATME No. 2*, Vol. IV, Rec. O.22. +- [7] CCITT Recommendation *Maintenance access lines*, Vol. IV, Rec. O.11. \ No newline at end of file diff --git a/marked/M/T-REC-M.733-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.733-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa0f783c793659638d3c6be4cded52908ef1b6d1 --- /dev/null +++ b/marked/M/T-REC-M.733-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c829811ad79dad7df3dbf2988f3ad2cebf8ed72f402fba68408dac03a8da0acb +size 7460 diff --git a/marked/M/T-REC-M.733-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.733-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3a00db7ea795bdfad013129c4a65e1ad397c7efb --- /dev/null +++ b/marked/M/T-REC-M.733-198811-I_PDF-E/raw.md @@ -0,0 +1,58 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.733** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**TRANSMISSION ROUTINE MAINTENANCE +MEASUREMENTS ON AUTOMATIC AND +SEMI-AUTOMATIC TELEPHONE CIRCUITS** + +**ITU-T Recommendation M.733** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.733 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **TRANSMISSION ROUTINE MAINTENANCE MEASUREMENTS ON AUTOMATIC AND SEMI-AUTOMATIC TELEPHONE CIRCUITS** + +The object of routine maintenance measurements is to detect changes in transmission conditions before such changes cause a reduction in the quality of service provided. These changes are those which occur relative to the values recorded for maintenance purposes for the circuits or link concerned. In the various sections of the Series M Recommendations limits are laid down within which: + +- no readjustment is necessary, +- readjustment may be made at the terminal stations, +- readjustment must be made along the whole circuit or link. + +Routine maintenance measurements should be made according to an agreed maintenance schedule (see Recommendation M.605). The periodicities for the measurements are given in Tables 1/M.610 and 2/M.610. These are to be considered as recommended values and may be increased or reduced if special circumstances require. + +Routine maintenance measurements must normally be made at times of light traffic, where staffing arrangements permit. If such measurements have to be made on a large group of circuits, it may nevertheless be necessary to do the measurements on some of the circuits during the busy period, if the operating services are not adversely affected thereby. + +Circuits on a given route are generally measured in batches based on the way in which the maintenance schedule has been arranged (see Recommendation M.605). The advantages are: + +- once cooperation has been arranged for routine testing with a distant station, time is saved if test cooperation can be maintained for as long as necessary; +- testing a large number of circuits on one route within a fairly short period enables a more accurate overall notion of the route to be obtained than could be gained from measurements on only a few circuits. + +Routine maintenance measurements should be made on a complete circuit and should include measurements of overall loss and levels at one and several frequencies, stability (for 2-wire audio circuits only), and noise. \ No newline at end of file diff --git a/marked/M/T-REC-M.734-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.734-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9df01ffda8a7a24fccd88c5d74b89f8324b825ef --- /dev/null +++ b/marked/M/T-REC-M.734-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d20ef9d423710c2780d0b240b88fd8d8d79d37707de75c05a3423129e922d805 +size 7474 diff --git a/marked/M/T-REC-M.734-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.734-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c0a6113ada6444ccfcb680b75756f698a06e6b8 --- /dev/null +++ b/marked/M/T-REC-M.734-198811-I_PDF-E/raw.md @@ -0,0 +1,104 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.734** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEPHONE CIRCUITS** + +--- + +**EXCHANGE OF INFORMATION ON INCOMING +TEST FACILITIES AT INTERNATIONAL +SWITCHING CENTRES** + +**ITU-T Recommendation M.734** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.734 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **EXCHANGE OF INFORMATION ON INCOMING TEST FACILITIES AT INTERNATIONAL SWITCHING CENTRES** + +The attention of Administrations is drawn to the need to exchange information on the incoming test facilities which they have provided at their international switching centres. The exchange of such information has an important bearing on maintenance efficiency since it helps to avoid unnecessary requests for maintenance cooperation and the under utilization of the facilities which have been provided. + +The form to be used for this purpose is shown in Figure 1/M.734. It provides, for the international switching centre and signalling system concerned, a description of the available test facilities, their CCITT reference (where applicable), the access code to be used, and any necessary remarks (for example, an outline of the response to be expected where the facility is not specified by CCITT). Figure 2/M.734 shows a hypothetical example of this form completed for a particular international switching centre. + +Each Administration should distribute the completed forms to other Administrations as appropriate. Upon receipt, Administrations should arrange that the information be distributed to the appropriate points within their maintenance organization, for example, circuit control station, testing point (transmission). + +## **Reference** + +- [1] CCITT Recommendation *CCITT automatic transmission measuring and signalling testing equipment ATME No. 2*, Vol. IV, Rec. O.22. + +# PROVISION OF INCOMING TEST FACILITIES + +ADMINISTRATION: + +INTERNATIONAL SWITCHING CENTRE: + +DATE: + +SIGNALLING SYSTEM: + +| Test facilities | CCITT reference | Access code | Remarks | +|-----------------|-----------------|-------------|---------| +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | + +FIGURE 1/M.734 +**Form for incoming test facilities** + +# PROVISION OF INCOMING TEST FACILITIES + +ADMINISTRATION: United Kingdom + +INTERNATIONAL SWITCHING CENTRE: London/Mollison + +DATE: November, 1979 + +SIGNALLING SYSTEM: CCITT No. 5 + +| Test facilities | CCITT reference | Access code | Remarks | +|------------------------------|-----------------|-------------------|-----------------------------------------| +| Balanced test termination | — | KP1 C7 C12 022 ST | Answer signal, then 600 Ω termination | +| Reference test tone | — | KP1 C7 C12 031 ST | Answer signal, then 1000 Hz at -10 dBm0 | +| | | | | +| | | | | +| | | | | +| | | | | +| | | | | +| ATME No. 2: responder Type a | Rec. O.22 [1] | KP1 C7 C12 061 ST | | +| ATME No. 2: responder Type b | Rec. O.22 [1] | KP1 C7 C12 062 ST | | +| ATME No. 2: responder Type c | Rec. O.22 [1] | KP1 C7 C12 063 ST | | + +FIGURE 2/M.734 + +Form for incoming test facilities (hypothetical example only) \ No newline at end of file diff --git a/marked/M/T-REC-M.760-198811-I_PDF-E/163688ca8da9787f5d48edd68d8cc75b_img.jpg b/marked/M/T-REC-M.760-198811-I_PDF-E/163688ca8da9787f5d48edd68d8cc75b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac8f5ce7440222d9f684d2dd22fc216be63759c8 --- /dev/null +++ b/marked/M/T-REC-M.760-198811-I_PDF-E/163688ca8da9787f5d48edd68d8cc75b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c93cc9bbebfcee06f3c60709f8545a3635c0aa56b08cfb367b19c08d8b847e78 +size 65772 diff --git a/marked/M/T-REC-M.760-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.760-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.760-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.760-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/marked/M/T-REC-M.760-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10bf5cd727d8671ae22c4a81038d20512a0bac6e --- /dev/null +++ b/marked/M/T-REC-M.760-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d48adbfe7a799e5095730b87a906e86be5cb7298c4787f019bb3fb30c479a0e4 +size 253989 diff --git a/marked/M/T-REC-M.762-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.762-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.762-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.80-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.80-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.80-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.80-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.80-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3c55c6c764c3b5c908624bb924cb8b7e849bf5ab --- /dev/null +++ b/marked/M/T-REC-M.80-198811-I_PDF-E/raw.md @@ -0,0 +1,94 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**M.80** + +**MAINTENANCE : INTRODUCTION +AND GENERAL PRINCIPLES** + +--- + +**CONTROL STATIONS** + +**ITU-T Recommendation M.80** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation M.80 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **CONTROL STATIONS** + +## **1 Definition of control station** + +A control station is that point within the general maintenance organization which fulfils the control responsibilities for the circuit, group, supergroup, digital section, etc., assigned to it. + +## **2 Appointment of control stations** + +The following principles for control stations apply to: + +- every international circuit (circuit control station), +- every international group, supergroup, digital block, digital path, etc. (group control station, supergroup control station, digital block control station, digital path control station, etc.), +- every line link, every regulated line section and every digital section (line link control station, regulated line section control station, digital section control station) using a symmetric pair line, a coaxial line, an optical fibre or a radio-relay link. + +### **2.1 Circuit control station** + +A circuit control station is nominated for each international circuit used for public telephony or for leased or special purposes in accordance with Recommendations M.723 and M.1012 [1] as appropriate. In the case of sound-programme or television circuits, the terminal ISPC (International Sound-Programme Centre) or ITC (International Television Centre) at the receiving end should be nominated as the control station. (See Recommendations N.1 [2], N.5 [3] and N.55 [4].) + +### **2.2 Group, supergroup, digital block, etc. control stations** + +For each international group, supergroup, digital block, etc., the terminal repeater station is a control station for its incoming direction of transmission. There are thus two control stations, one for each direction of transmission. + +### **2.3 Regulated line section control station** + +The procedure is the same as for groups, supergroups, digital blocks, etc., that is to say, each of the terminal repeater stations is a control station for the incoming direction of transmission. + +### **2.4 Digital path control station** + +For each digital path, each terminal station is a control station for its incoming direction of transmission. There are thus two control stations, one for each direction of transmission. + +## **3 Responsibilities of circuit control stations** + +See Recommendations M.723 and M.1012 [1] concerning public automatic telephone circuits, leased circuits and special circuits, respectively. See Recommendations N.5 [3] and N.55 [4] in connection with sound-programme and television circuits. + +## **4 Responsibilities of control stations for groups, supergroups, digital paths, etc.** + +4.1 Group, supergroup, digital block, digital path, regulated line section, line link, etc. control stations are responsible for the incoming direction of transmission only. + +4.2 Each control station is responsible for ensuring that the group, supergroup, digital block, digital path, link, line, etc. with which it is concerned is set up and maintained to the required standards. In particular, it is responsible for: + +- a) controlling lining-up measurements to within the recommended limits and keeping records of reference measurements (initial measurements) for *analogue transmission systems*; +- b) ensuring that the performance of digital transmission systems is kept within recommended limits and keeping records of initial measurements; + +- c) ensuring that routine maintenance measurements are carried out on the due dates, using the specified methods and in such a way that interruptions to service are limited to the shortest possible duration; +- d) ensuring that the stations concerned take action when a fault occurs, and controlling the various tests or investigations necessary in clearing the fault. It must be possible to report faults discovered at any time of the day or night; +- e) informing the circuit control station of any condition which might affect the operation of the circuits under its control; +- f) seeking the authority of the circuit control station for any action which will take a circuit, or circuits, out of service; +- g) knowing what are the possibilities of rerouting any faulty groups, supergroups, etc.; +- h) recording, on forms provided for the purpose, all incidents which arise, giving the time of occurrence of the incident, the exact location if known, the action taken if any, and the time of restoration to service. + +4.3 Thus, for technical purposes (maintenance, lining-up) the control function for digital paths, groups, supergroups, mastergroups, supermastergroups and regulated line sections are divided between the two directions of transmission, the station at the incoming end being the control station in each case. However, it is considered desirable to have a single routing form for each, giving information about both directions of transmission, and in order that this and similar documentation may be prepared and distributed on a methodical basis, these documentary functions shall be added to the responsibilities of one of the control stations, this *control station for documentary purposes* being chosen by agreement between the Administrations concerned. + +# References + +- [1] CCITT Recommendation *Circuit control station for leased and special circuits*, Vol. IV, Rec. M.1012. +- [2] CCITT Recommendation *Definitions for application to international sound-programme transmissions*, Vol. IV, Rec. N.1. +- [3] CCITT Recommendation *Control and subcontrol stations for sound-programme circuits, connections, etc.*, Vol. IV, Rec. N.5. +- [4] CCITT Recommendation *Organization, responsibilities and functions of control and sub-control ITCs and control and sub-control stations for international television connections, links, circuits and circuit sections*, Vol. IV, Rec. N.55. \ No newline at end of file diff --git a/marked/M/T-REC-M.800-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/M/T-REC-M.800-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26e0aef5a8ef80eb8d225ffb8eaa37a9ee2637b0 --- /dev/null +++ b/marked/M/T-REC-M.800-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab7bc1ba342ab0c043977621d5aab71d2a2675b9e27e155c7257d9d4d37c1569 +size 67794 diff --git a/marked/M/T-REC-M.800-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.800-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cefb8bf531d09e039379b5383d7c131a21d5164 --- /dev/null +++ b/marked/M/T-REC-M.800-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ffa1c469cfcc9913e90bf5772604f91728eec8e0d7f7c8198796d3c1c6fb4c7 +size 7453 diff --git a/marked/M/T-REC-M.800-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/M/T-REC-M.800-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e868d6f583d3dbc995002a343f5aed3e0b7584a0 --- /dev/null +++ b/marked/M/T-REC-M.800-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc472e9eaca7284e96071bef9c84a4ef49fe347c291b0042eefe5a2ca45b90f +size 72602 diff --git a/marked/M/T-REC-M.810-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.810-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..412abaf8674d0ef4dbe6099d3523b3890805a83e --- /dev/null +++ b/marked/M/T-REC-M.810-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edbd28e126876911633b1cad90f0453f978448b49b6a504d851bb35da671f347 +size 7490 diff --git a/marked/M/T-REC-M.810-198811-I_PDF-E/f76f0f5dfff2511b51f6b875867c029f_img.jpg b/marked/M/T-REC-M.810-198811-I_PDF-E/f76f0f5dfff2511b51f6b875867c029f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7097f6205790ef6d4dd47920a8459c51db5f9d3a --- /dev/null +++ b/marked/M/T-REC-M.810-198811-I_PDF-E/f76f0f5dfff2511b51f6b875867c029f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70e9bc46753badba7e536c54574ee6e16a5cb748a5247dddb50a843ded093fb9 +size 26327 diff --git a/marked/M/T-REC-M.820-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.820-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd315b4c7bee239c1ee4fd9eda9a90a56f480969 --- /dev/null +++ b/marked/M/T-REC-M.820-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba954e6b824197bc803bd1b4745836e940210f6b7003b7c41d46aad8930022a +size 7540 diff --git a/marked/M/T-REC-M.820-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.820-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..588e27d0d1336c6b98511b505b0dc14e7639cd6d --- /dev/null +++ b/marked/M/T-REC-M.820-198811-I_PDF-E/raw.md @@ -0,0 +1,66 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.820** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **MAINTENANCE:** + +**INTERNATIONAL TELEGRAPH SYSTEMS +AND PHOTOTELEGRAPH TRANSMISSION** + +--- + +**PERIODICITY OF ROUTINE TESTS +ON INTERNATIONAL VOICE-FREQUENCY +TELEGRAPH LINKS** + +**ITU-T Recommendation M.820** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation M.820 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **PERIODICITY OF ROUTINE TESTS ON INTERNATIONAL VOICE-FREQUENCY TELEGRAPH LINKS** + +1 The recommendations concerning the periodicity of routine tests on international telephone circuits given in Recommendation M.610 [1] are applicable to international voice-frequency telegraph links. + +2 In certain cases and by agreement between the Administrations concerned, routine maintenance measurements may be omitted if those Administrations so wish. This applies in particular where the Administrations concerned consider that the telegraph traffic may be seriously disturbed due to the lack of a suitable reserve circuit or reserve sections. + +3 Routine measurements of level at one frequency (1020 Hz) should be made at the intervals recommended for international telephone circuits (see Table 1/M.610 [2]). + +Measurements at different frequencies should be made once every 12 months. Some Administrations make an annual reline of the voice-frequency telegraph link instead of routine measurements. + +4 It is desirable that the maintenance measurements on the voice-frequency telegraph reserve circuit should be made just before the maintenance measurements on the normal circuit, so that the reserve circuit can replace the normal circuit while the latter is being tested. + +5 When several voice-frequency telegraph systems are in use between two repeater stations and if the maintenance measurements on the telephone circuits between these stations are spread over several days, the measurements on the circuits carrying the voice-frequency telegraph systems should also be spread over these days; this makes it easier to carry out the measurements on the voice-frequency telegraph circuits. + +6 The periodicity of measurements on telephone circuits used as reserve circuits is as given in Table 1/M.610 [2]. + +For circuits providing reserve sections for an international voice-frequency telegraph link the periodicity of routine measurements will be agreed upon between the Administrations concerned. + +7 A check should be made when suitable opportunities occur, to see that the limits shown in Tables A-1/M.810, A-2/M.810 and A-3/M.810 for the permissible power per telegraph channel are not exceeded. + +# **References** + +[1] CCITT Recommendation *Periodicity of maintenance measurements on circuits*, Vol. IV, Rec. M.610. + +[2] *Ibid.*, Table 1/M.610. \ No newline at end of file diff --git a/marked/M/T-REC-M.850-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.850-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a6f8336072e491cd4d6437ad9ad762a312994260 --- /dev/null +++ b/marked/M/T-REC-M.850-198811-I_PDF-E/raw.md @@ -0,0 +1,172 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.850** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEGRAPH SYSTEMS +AND PHOTOTELEGRAPH TRANSMISSION** + +--- + +**INTERNATIONAL TIME DIVISION +MULTIPLEX (TDM) TELEGRAPH +SYSTEMS** + +**ITU-T Recommendation M.850** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.850 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **INTERNATIONAL TIME DIVISION MULTIPLEX (TDM) TELEGRAPH SYSTEMS** + +## **1 General description of an international TDM system** + +1.1 Figure 1/M.850 illustrates a basic international TDM telegraph system. The system operates via an international TDM telegraph link operated at 2400 bit/s and has a capacity of 46 telegraph channels at 50 bauds. Other modulation rates up to 300 bauds can be accommodated (with resulting reduction in channel capacity) as shown in Recommendation R.101, Table 1/R.101 [1]. + +1.2 The international TDM telegraph system may be carried over a dedicated voice-frequency link as shown in Figure 1/M.850 or multiplexed with other TDM systems or other services onto a higher bit rate data transmission system on a voice-frequency or digital data transmission link as shown in Figure 2/M.850. + +1.3 International telegraph systems may also be carried on high level (e.g. 50, 56 kbit/s) data transmission links utilizing analogue group band or on digital (64 kbit/s) paths. Examples of such multiplexing arrangements are illustrated in Recommendation M.1300. + +## **2 Basic TDM telegraph links (Figure 1/M.850)** + +2.1 Basic TDM telegraph links may be carried on 4-wire analogue telephone circuits. The link comprises two unidirectional transmission paths, one for each direction of transmission, between the terminal TDM telegraph equipments. The TDM telegraph links are terminated with data modems, usually (but not necessarily) located within the terminal TDM telegraph equipment, which operate at 2.4 kbit/s. + +2.2 The international TDM telegraph link consists of an international TDM telegraph line together with any terminal national sections connecting the international line to the terminal TDM telegraph equipment. Where the TDM equipment is located in the terminal international centres, the TDM link consists only of the international TDM telegraph line. + +2.3 The international TDM telegraph line (between terminal international centres) may be constituted by using a channel in a carrier group or channels in tandem on a number of groups. National and international sections can be interconnected to set up an international TDM telegraph link. + +Wherever possible, an international TDM telegraph line should be provided on a channel of a single carrier group, thereby avoiding intermediate audio-frequency points. However it is recognized that in some cases such a direct group may not exist or, for special routing reasons, it may not be possible to set up the international TDM line in this preferred way. + +### **2.4 *Terminal national sections connected to the international TDM telegraph line*** + +In some cases the TDM telegraph terminal equipment is remote from the terminal international centre of the international TDM telegraph line (Figure 1/M.850), and such cases necessitate the provision of terminal national sections in order to establish international TDM telegraph links. These sections may be routed on channels of carrier groups or on audio plant (amplified or unamplified) or on digital streams. + +## **3 TDM telegraph links multiplexed on higher bit rate data systems (Figure 2/M.850)** + +3.1 When TDM telegraph links are multiplexed onto higher bit rate data transmission systems, the associated analogue voice-frequency data links generally follow the principles outlined in § 2, with the exception that these data links are operated at higher bit rates (usually 4.8, 7.2 or 9.6 kbit/s). + +Should a TDM telegraph link be extended from the higher level multiplexer, for example, to a remote point such as a third country or to renters premises, then it is necessary to use an appropriate modem as shown in Figure 2/M.850. + +![Diagram of an international TDM telegraph system showing the flow from terminal national sections through international TDM telegraph centres to TDM telegraph terminal equipment.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +International TDM telegraph system + +International TDM telegraph link + +Terminal national section | International TDM telegraph line | Terminal national section + +1 → 46 | 1 → 46 + +1 ← 46 | 1 ← 46 + +TDM telegraph terminal equipment | Terminal international centre | Terminal international centre | TDM telegraph terminal equipment + +d01-sc CCITT - 82170 + +Diagram of an international TDM telegraph system showing the flow from terminal national sections through international TDM telegraph centres to TDM telegraph terminal equipment. + +*Note* — It is assumed that the TDM telegraph terminal equipment includes a modem. It should be noted, however, that modems may be provided separately. + +FIGURE 1/M.850 +**The components of an international TDM telegraph system** + +![Diagram showing two international TDM telegraph systems multiplexed onto a higher bit rate data transmission system via data channel equipment.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +TDM telegraph system + +TDM telegraph link + +Data transmission system + +Data transmission link + +TDM equipment | 2.4 kbit/s | MUX / Modem | Modem / MUX | 2.4 kbit/s | TDM equipment + +TDM equipment | 2.4 kbit/s | MUX / Modem | Modem / MUX | 2.4 kbit/s | Modem | TDM equipment (remote) + +Other service | 4.8 kbit/s | 4.8 kbit/s | Other service + +Data channel equipment | Data channel equipment + +TDM telegraph link + +TDM telegraph system + +CCITT - 82180 d02-sc + +Diagram showing two international TDM telegraph systems multiplexed onto a higher bit rate data transmission system via data channel equipment. + +FIGURE 2/M.850 +**Example of two international TDM telegraph systems multiplexed onto a higher bit rate data transmission system** + +3.2 TDM telegraph links multiplexed onto voice-frequency data transmission systems operated at 4.8, 7.2 or 9.6 kbit/s may be further multiplexed onto higher bit rate data transmission systems operated at 50, 56, 64 kbit/s etc. Examples of such arrangements are shown in Recommendation M.1300. + +## **4 Characteristics, line-up, and maintenance of TDM telegraph links and systems** + +### *4.1 Characteristics and line-up* + +Guidance on the transmission characteristics and line-up procedures for both analogue and digital TDM telegraph links may be found in Recommendation M.1350, §§ 2 and 3. In this regard, the TDM telegraph link is identical to a 2.4 kbit/s data transmission link. + +### *4.2 Maintenance* + +Maintenance procedures and limits for both analogue and digital TDM telegraph links may be found in Recommendation M.1355. + +Maintenance procedures and limits for TDM telegraph systems are under study. However, guidance on the maintenance of these systems may be found in Recommendations R.75 [2] and V.51 to V.53 [3]. + +## **5 Reserve arrangements for TDM telegraph links** + +### *5.1 General requirements* + +All necessary action should be taken to ensure that the number of interruptions on TDM telegraph systems be kept to a minimum, and further that interruptions, when they do occur, be kept as short as possible. + +### *5.2 Basic international telegraph links* + +Reserve arrangements for international TDM telegraph systems operated over links at 2.4 kbit/s should be in accordance with the principles and procedures specified for international voice frequency telegraph systems. Refer to Recommendation M.800, § 2. In some instances, it may be desirable to establish dual, diversely routed international TDM telegraph links and to change over from the active link to the reserve link when the international TDM telegraph system fails or becomes degraded. The change over may be done automatically, semi-automatically, or manually, by agreement between Administrations involved. Guidance on changeover arrangements may be found in Recommendations M.800 and R.150 [4]. + +### *5.3 TDM telegraph links multiplexed on higher level data transmission systems* + +When international TDM telegraph links are multiplexed onto higher bit rate data transmission systems, reserve arrangements will normally depend upon the principles and procedures adopted for the higher level data transmission link. Reserve arrangements for these data transmission links require further study. + +## **6 TDM telegraph link designation** + +The form of designation for the TDM telegraph link and its reserve is given in Recommendation M.140, § 1.2.2 [5]. + +## **7 Marking of equipment associated with TDM telegraph links** + +It is recommended that all equipment associated with the TDM telegraph link and nominated reserve circuits (channel translating equipment, distribution frames, etc.) be positively marked to make them readily identifiable to the maintenance staff. + +## **8 TDM telegraph link control and sub-control stations** + +8.1 One control station should be agreed bilaterally between the Administrations involved for each TDM telegraph link prior to setting up the link. Principles concerning the definition, responsibilities, functions, and appointment of control stations may be found in Recommendation M.1012. + +8.2 One sub-control station should be agreed bilaterally between Administrations involved for each TDM telegraph link prior to setting up the link. Principles concerning the definition, responsibilities, functions, and appointment of sub-control stations may be found in Recommendation M.1013. + +## References + +- [1] CCITT Recommendation *Code and speed dependent TDM system for anisochronous telegraph and data transmission using bit interleaving*, Vol. VII, Rec. R.101. +- [2] CCITT Recommendation *Maintenance measurements on code independent international sections of international telegraph circuits*, Vol. VII, Rec. R.75. +- [3] CCITT Recommendations on the *Maintenance of international telephone – Type circuits used for data transmissions*, Vol. VIII, Recs. V.51 to V.53. +- [4] CCITT Recommendation *Automatic protection switching of dual diversity bearers*, Vol. VII, Rec. R.150. +- [5] CCITT Recommendation *Designation of international circuits, groups, group and line links, digital blocks, digital paths, data transmission systems and related information*, Vol. IV, Rec. M.140. \ No newline at end of file diff --git a/marked/M/T-REC-M.880-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg b/marked/M/T-REC-M.880-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f03071e08d3b59fbbcaf874dce96049b5ea48c32 --- /dev/null +++ b/marked/M/T-REC-M.880-198811-I_PDF-E/2763901b7a1fd1b5d704cdc450d12ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:555f9ffca2e65a1ce2782b781acdccc83139b05b13f5841bd865e77d1b26256c +size 35439 diff --git a/marked/M/T-REC-M.880-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.880-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dc96fbdf7e430fd758a1af02be6f9506a89c0ed --- /dev/null +++ b/marked/M/T-REC-M.880-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0a3ffd2c190ab1e362e5924d4fc6df24766ffdaa3b94d8aab3b67e9b85c3c6 +size 7301 diff --git a/marked/M/T-REC-M.880-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.880-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..771ce9a430c5e109f4e9661bcb3af0581835df60 --- /dev/null +++ b/marked/M/T-REC-M.880-198811-I_PDF-E/raw.md @@ -0,0 +1,151 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.880** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE:** + +**INTERNATIONAL TELEGRAPH SYSTEMS +AND PHOTOTELEGRAPH TRANSMISSION** + +--- + +**INTERNATIONAL PHOTOTELEGRAPH +TRANSMISSION** + +**ITU-T Recommendation M.880** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.880 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **INTERNATIONAL PHOTOTELEGRAPH TRANSMISSION** + +## **1 Types of circuits** + +1.1 Permanent circuits used between phototelegraph stations should be set up and lined up as 4-wire circuits between these stations. + +1.2 Circuits used normally (and preferentially) will be nominated international telephone circuits, the international line of which is normally extended to the phototelegraph station on a 4-wire basis, it being ensured that the terminal equipment (line relay sets, terminating sets, echo suppressors, etc.) is disconnected. + +## **2 Line-up** + +2.1 The same conditions apply to the overall transmission loss of 4-wire circuits used for phototelegraphy as apply in general for telephony. + +2.2 If an international telephone circuit is used to provide a phototelegraph circuit and if the international line is extended to the phototelegraph station the levels of the circuit so established should be such as to maintain the levels found on the level diagram of the telephone circuit. + +## **3 Relative levels** + +If phototelegraph transmissions take place simultaneously from a transmitting station to several receiving stations, arrangements shall be made at the junction point so that, on the circuits following the junction point, the same power levels are maintained as those prescribed for individual transmissions. + +## **4 Loss/frequency distortion** + +4.1 For phototelegraph transmission using frequency modulation, the use of a telephone circuit having a loss/frequency characteristic as given in Recommendation M.580 [1] will generally make it unnecessary to equalize the loss/frequency distortion of the lines joining the phototelegraph stations to the terminal international repeater stations. Such lines will have characteristics that follow national practice. + +4.2 When amplitude modulation is used, the loss/frequency distortion between phototelegraph stations should not exceed 8.7 dB at any frequency in the band of frequencies transmitted. Since the band of frequencies required is less than the full bandwidth of the telephone-type circuit used for the phototelegraph transmission and the loss/frequency distortion over the bandwidth of the telephone-type circuit (see Recommendation M.580 [1]) is nominally much less than 8.7 dB, it will not in general be necessary to compensate for the loss/frequency distortion of the lines joining the phototelegraph stations to the international terminal repeater stations. + +4.3 Figure 1/M.880 shows, in respect of loss/frequency distortion, the relationship of the Recommendations relating to international phototelegraph links. + +## **5 Variation of overall loss with time** + +The overall loss should remain as constant as possible during picture transmissions. + +5.1 The difference between the mean value and the nominal value of the transmission loss should not exceed 0.5 dB. + +5.2 The standard deviation about the mean value should not exceed 1.0 dB. However, in the case of circuits wholly or partly on older-type equipment, and where the international line consists of two or more circuit sections, a standard deviation not exceeding 1.5 dB may be accepted. + +![Diagram showing the relationship between Recommendations M.580, M.880, and the overall circuit. The diagram shows a sequence of nodes: PS, TNC, TIC, TIC, TNC, PS. A 'Line M.580' is indicated between the two TIC nodes. A 'Link Not specified but recorded' is indicated between the two TNC nodes. A 'Circuit M.880' is indicated between the two PS nodes. A legend defines PS as phototelegraph station, TNC as terminal national centre, and TIC as terminal international centre. The diagram is labeled CCITT-36960 d01-sc.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +PS = phototelegraph station +TNC = terminal national centre +TIC = terminal international centre + +CCITT-36960 +d01-sc + +Diagram showing the relationship between Recommendations M.580, M.880, and the overall circuit. The diagram shows a sequence of nodes: PS, TNC, TIC, TIC, TNC, PS. A 'Line M.580' is indicated between the two TIC nodes. A 'Link Not specified but recorded' is indicated between the two TNC nodes. A 'Circuit M.880' is indicated between the two PS nodes. A legend defines PS as phototelegraph station, TNC as terminal national centre, and TIC as terminal international centre. The diagram is labeled CCITT-36960 d01-sc. + +FIGURE 1/M.880 +Relationship between Recommendations which apply to international phototelegraph links +in respect of loss/frequency distortion + +## 6 Phase/frequency distortion + +Phase/frequency distortion limits the range of satisfactory phototelegraph transmission. The differences in group-delay time of the telephone circuit, over the phototelegraph transmission range, should not exceed: + +$$\Delta t \leq \text{Error!}$$ + +where $f_p$ is the maximum modulating frequency for the definition and scanning speed concerned. + +(See Recommendation T.12 [2].) + +## 7 Sent signal power + +The conditions applying to the transmitted power in phototelegraph transmission are as follows: + +The sent voltage of the phototelegraph signal at maximum amplitude should be so adjusted that the absolute power of the signal, at a zero relative level point found from the level diagram of the telephone circuit, is for a double sideband amplitude-modulated phototelegraph transmission $-3$ dBm referred to 1 mW and for a frequency-modulated transmission $-13$ dBm. With amplitude modulation, the black level is usually 30 dB below the white level. + +In order to avoid the risk that phototelegraph signals be disturbed, for example by dial pulses transmitted over adjacent channels or by noise, it is important that the sending level should be as high as permissible; however, it shall not exceed $-13$ dBm0 on the multichannel system and the power at the output of the sending apparatus shall not exceed 1 mW. + +This value of $-13$ dBm0 is in accordance with Recommendation V.2 [3], since in all cases the phototelegraph transmissions are operated in simplex. This value may have to be revised if the percentage of circuits used for applications other than telephony should go beyond the assumptions indicated in Recommendation V.2 [3]. + +## 8 Marking of equipment + +When a telephone circuit is specially allocated for phototelegraph transmission (circuit identified by the letter F), the associated equipment should be specially marked to alert staff. All interruptions in a phototelegraph transmission, no matter how short, and all variations of level due to maintenance work should be avoided. + +## 9 Organization of maintenance + +The maintenance organization arrangements for international phototelegraph links should conform to the general principles given in Recommendation M.70 [4] concerning telephone-type circuits. + +The designation of control and sub-control stations should follow the principles given in Recommendations M.1012 and M.1013. + +## 10 Routine tests + +The recommendations for 4-wire telephone circuits concerning the periodicity of measurements are also applicable to phototelegraph circuits. + +Routine measurements should be made at the intervals recommended for international telephone circuits (see Table 1/M.610 [5]). + +## 11 Information concerning frequencies transmitted by phototelegraph equipment + +### 11.1 Amplitude modulation + +For audio circuits the recommended carrier frequency is about 1300 Hz. + +For circuits routed on carrier systems and effectively transmitting the band of frequencies 300-3400 Hz the recommended carrier frequency is about 1900 Hz. + +### 11.2 Frequency modulation + +| | | +|--------------------------|---------| +| Mean frequency | 1900 Hz | +| White frequency | 1500 Hz | +| Black frequency | 2300 Hz | +| Phasing signal frequency | 1500 Hz | + +12 Information about the characteristics to be taken into account when choosing the circuit used for phototelegraph transmissions is given in Recommendation T.12 [2]. + +## References + +- [1] CCITT Recommendation *Setting up and lining up an international circuit for public telephony*, Vol. IV, Rec. M.580. +- [2] CCITT Recommendation *Range of phototelegraph transmissions on a telephone-type circuit*, Vol. VII, Rec. T.12. +- [3] CCITT Recommendation *Power levels for data transmission over telephone lines*, Vol. VIII, Rec. V.2. +- [4] CCITT Recommendation *Guiding principles on the general maintenance organization for telephone-type international circuits*, Vol. IV, Rec. M.70. +- [5] CCITT Recommendation *Periodicity of maintenance measurements on circuits*, Vol. IV, Rec. M.610, Table 1/M.610. \ No newline at end of file diff --git a/marked/M/T-REC-M.90-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.90-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..521b4452f8d1a8826201fd6141fd858668476cc9 --- /dev/null +++ b/marked/M/T-REC-M.90-198811-I_PDF-E/raw.md @@ -0,0 +1,121 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.90** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE : +INTRODUCTION AND GENERAL PRINCIPLES** + +--- + +**SUB-CONTROL STATIONS** + +**ITU-T Recommendation M.90** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.90 was published in Fascicle IV.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SUB-CONTROL STATIONS** + +## **1 Definition of sub-control station** + +A sub-control station is a point within the general maintenance organization which fulfils the sub-control responsibilities of the circuit, group, supergroup, etc. digital section, assigned to it. + +## **2 Appointment of sub-control stations** + +The following principles apply to: + +- every international circuit (circuit sub-control station), for whatever purpose (telephony, telegraphy, sound-programme, data transmission, etc.). (See in particular Recommendations N.5 [1] in connection with sound-programme circuits and N.55 [2] in connection with television circuits); +- every international digital block, digital path, group, supergroup, mastergroup or supermastergroup (digital block sub-control station, digital path sub-control station, group sub-control station, supergroup sub-control station, etc.); +- every line link, every regulated line section and every digital line section (line link sub-control station, regulated line section sub-control station, digital line section sub-control station) using a symmetric pair line, a coaxial line, an optical fibre or a radio-relay link. + +The technical service of the Administration concerned designates the station that is to act as a sub-control station in its country and informs the technical service of the country responsible for the control station accordingly. + +### **2.1 Terminal sub-control stations** + +##### **2.1.1 Terminal sub-control stations for circuits** + +For each circuit a terminal circuit sub-control station is appointed in accordance with Recommendations M.724 and M.1013 [3] as appropriate. + +For unidirectional constituted circuits the terminal station at the sending end should be the terminal circuit sub-control station. In particular, in the case of sound-programme or television circuits, the terminal ISPC or ITC at the sending end should be the terminal sub-control station. (See Recommendations N.5 [1] and N.55 [2].) + +##### **2.1.2 Terminal sub-control stations for digital blocks, digital paths, groups, supergroups, etc.** + +At the two ends of a digital block, digital path, group, supergroup, etc., the terminal stations are designated as terminal digital block, digital path, group, supergroup, etc., sub-control stations for the direction of transmission for which they are not the digital block, digital path, group, supergroup, etc., control station. + +##### **2.1.3 Terminal sub-control station for a digital section, line link or a regulated line section** + +At the two ends of a digital section, line link or a regulated line section, the terminal stations are designated as terminal digital section, line link or regulated line section sub-control station for the direction of transmission for which they are not the digital section, line link or regulated line section control station. + +### **2.2 Intermediate sub-control stations** + +#### **2.2.1 Intermediate sub-control stations for circuits** + +In transit countries in which a circuit is brought to audio frequencies or 64 kbit/s, etc., an intermediate circuit sub-control station is appointed at a suitable point for each direction of transmission. It is left to the country concerned to choose: + +- where this point shall be; +- whether the sub-control functions for the two directions of transmission are vested in one station or two stations (see Figure 1/M.90); +- whether, as may be desirable in the case of a large country, each direction of transmission has more than one circuit sub-control station per transit country. + +![Diagram illustrating the possible choice for sub-control stations in a transit country. It shows a sequence of stations: F (frontier station), I (intermediate station), F, F, I, F, I, F. Sub-control stations are indicated by black squares within the station boxes. The diagram is labeled 'CCITT - 36490 d01-sc'.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +F = frontier station    I = intermediate station    —■— = sub-control station + +Diagram illustrating the possible choice for sub-control stations in a transit country. It shows a sequence of stations: F (frontier station), I (intermediate station), F, F, I, F, I, F. Sub-control stations are indicated by black squares within the station boxes. The diagram is labeled 'CCITT - 36490 d01-sc'. + +FIGURE 1/M.90 +Possible choice for sub-control stations in a transit country + +#### 2.2.2 Intermediate sub-control stations for paths and links + +In general, for digital paths and analogue links, in transit countries in which the path or link concerned appears in its characteristic bit rate or in its basic frequency range, an intermediate sub-control station is appointed for each direction of transmission. The countries concerned have the same prerogatives as those indicated above for circuits (see § 2.2.1 and Figure 1/M.90). + +#### 2.2.3 Intermediate sub-control stations for regulated line sections + +In transit countries, a regulated line section intermediate sub-control station is appointed for each direction of transmission, the same discretion as for circuits being given to the country concerned (see § 2.2.1 above and Figure 1/M.90). + +### 2.3 Combination of functions + +Any, or all, of the above functions may be vested in one station, depending on the arrangements in the country concerned. + +## 3 Responsibilities of sub-control stations for circuits + +See Recommendations M.724 and M.1013 [3] concerning automatic public telephone circuits, leased circuits and special circuits, respectively. See also Recommendations N.5 [1] and N.55 [2] in connection with sound-programme and television circuits. + +## 4 Responsibilities of sub-control stations for groups, supergroups, digital blocks, digital paths, etc. + +The responsibilities of sub-control stations are, for the sections which they control, similar to those given in Recommendation M.80 for control stations, but in addition they include: + +- cooperating with the control stations and other sub-control stations in locating and clearing faults; +- setting up and maintaining that part of the digital path, group link, supergroup link, mastergroup link, or regulated line link between the through-connection stations nearest to the two frontiers; +- seeing that the transmission on the national section with which they are concerned is within the prescribed limits; +- reporting to the control station all relevant details concerning the location and subsequent clearance of faults; +- keeping the necessary records on lining-up (analogue transmission) or initial measurements (digital transmission), fault location and fault clearing for the section for which they are responsible. + +In addition to the above responsibilities, an intermediate sub-control station (in a transit country) is responsible for initiating fault localization tests on the sections it controls in response to reports from other control or sub-control stations. + +## References + +- [1] CCITT Recommendation *Control and sub-control stations for sound-programme circuits, connections, etc.*, Vol. IV, Rec. N.5. +- [2] CCITT Recommendation *Organization, responsibilities and functions of control and sub-control ITCs and control and sub-control stations for international television connections, links, circuits and circuit sections*, Vol. IV, Rec. N.55. +- [3] CCITT Recommendation *Circuit sub-control station for leased and special circuits*, Vol. IV, Rec. M.1013. \ No newline at end of file diff --git a/marked/M/T-REC-M.910-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.910-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/M/T-REC-M.910-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e +size 7392 diff --git a/marked/M/T-REC-M.910-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg b/marked/M/T-REC-M.910-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb7f4c470a186578cf3c8b16101162eb9a9dc800 --- /dev/null +++ b/marked/M/T-REC-M.910-198811-I_PDF-E/de6e8b740c69dac308cce9edfec3eff4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67118ab099facdd6e4a8aee1acd026aee791c0b7422e47b20d82596d1580726e +size 45694 diff --git a/marked/M/T-REC-M.910-198811-I_PDF-E/raw.md b/marked/M/T-REC-M.910-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..404a7c80fc008a6b48d71e911c4f65d66f4f5543 --- /dev/null +++ b/marked/M/T-REC-M.910-198811-I_PDF-E/raw.md @@ -0,0 +1,176 @@ + + +![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +**M.910** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**MAINTENANCE: INTERNATIONAL LEASED GROUP +AND SUPERGROUP LINKS** + +--- + +**SETTING UP AND LINING UP +AN INTERNATIONAL LEASED GROUP +LINK FOR WIDE - SPECTRUM SIGNAL +TRANSMISSION** + +**ITU-T Recommendation M.910** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation M.910 was published in Fascicle IV.2 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). + +2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +# **SETTING UP AND LINING UP AN INTERNATIONAL LEASED GROUP LINK FOR WIDE-SPECTRUM SIGNAL TRANSMISSION** + +## **1 General** + +1.1 The international leased group links in this Recommendation relate to corrected group links in the Recommendation cited in [1]. + +1.2 The composition of a leased group link and the terminology used for maintenance purposes is given in Recommendation M.900. + +1.3 The procedure for setting up an international leased group link should as far as possible follow the principles given in Recommendation M.460 [2]. + +1.4 For the purpose of this Recommendation, the constitution and subsequent line-up and maintenance practice assumes that the group link between renters' premises is operated throughout in the frequency range 60-108 kHz. + +1.5 Where, as in some cases, modems are fitted at the terminal national centres the group link is defined as existing between defined access points at these centres. + +In such cases the terminal national section is treated for lining-up and maintenance purposes as a separate section and not part of the group link as defined in Recommendation M.900. + +1.6 In some cases, where the wide-spectrum transmission equipment located at the renter's premises is not frequency band restricted, it may be found necessary to include a through-group filter at the terminal national centre in the transmitting direction of transmission, in order to prevent interference by the wide-spectrum signals into adjacent groups in the carrier systems, over which the group is routed. + +Also, when measuring at the terminal national centre in the receiving direction of transmission, a through-group filter may be necessary in the measuring circuit, in order to prevent signals from adjacent groups affecting the measurement results. + +## **2 Setting-up of an international leased group link** + +### **2.1 *National and international main section*** + +With the exception of the terminal national section, the provisions of Recommendation M.460 [2] shall apply to the setting-up and the interconnection of the group sections constituting the national and international main section. + +### **2.2 *Terminal national sections*** + +Because of the particular arrangements adopted for providing these sections within the country concerned, the setting-up of such sections will follow the practice determined within the country concerned. + +### **2.3 *Application of the group reference pilot*** + +The application of a group reference pilot (preferably 104.08 kHz), whether injected into the group path at the renter's premises or whether it is injected at the terminal national centre, should conform to the requirements of Recommendation M.460 [2]. + +## **3 Lining up an international leased group link** + +### **3.1 *Lining up the national and international main sections*** + +3.1.1 The reference test frequency to be used should be 84 kHz. + +3.1.2 The lining-up of these sections should follow the procedure and method given in the Recommendation cited in [3]. + +3.1.3 The national main sections may be lined up separately from the international main sections since no international cooperation is needed. + +3.1.4 The limits given in Table 2/M.460 [4] should apply to these main sections. In addition, the group-delay distortion of the national and international sections should be measured and the results recorded. + +### 3.2 *Terminal national sections* + +The lining-up of these sections will follow the national practice of the country concerned. + +### 3.3 *Interconnection of terminal national sections and national main section* + +The levels and impedances in the frequency band concerned of the terminal national sections and the national main section at the terminal national centre should be made compatible with the levels and impedances specified for the access point at this centre. + +### 3.4 *Overall line-up of the link* + +When the national and international main sections have been lined up and interconnected using the necessary through-group equipment, measurements should be made between the terminal access points, either at the renter's premises or in exceptional cases at the terminal national centres. + +In addition to level measurements the group-delay distortion within the frequency band 68-100 kHz should be measured and the values relative to the minimum group-delay distortion within the band should be recorded for subsequent maintenance use. If necessary, group-delay equalizers have to be inserted into the link where appropriate. + +The procedure and method to be used for the line-up should follow that given in Recommendation M.460 [2], but the limits to be achieved are those given below. + +#### 3.4.1 *Overall loss at the reference frequency* + +The overall loss at the reference frequency between the renters' premises cannot normally be specified because of the freedom accorded to Administrations to adopt nominal relative levels which is their national or agency practice. + +If, however, it is necessary to specify a particular value of overall loss as a result of a request by a renter this may be done only after prior consultation and agreement between the Administrations concerned. + +#### 3.4.2 *Loss/frequency distortion* + +The loss/frequency distortion of the overall link is shown in Figure 1/M.910. It should be measured over the frequency range 60-108 kHz and equalized with a group link equalizer as necessary to meet the limits with respect to the loss at 84 kHz. + +*Note 1* – If the service channel is provided, additional equalization may be needed and there will be no possibility of employing simplified through-group filters. + +*Note 2* – 84 kHz is the reference frequency for the purposes of specifying and measuring attenuation distortion. The group reference pilot at 104.08 kHz may still be used as the regulating pilot, however, as required. + +![Figure 1/M.910: Limits for loss/frequency distortion. A graph showing Loss (dB) on the y-axis (from -2 to +5) versus Frequency (f) in kHz on the x-axis (from 68 to 107.7). The graph shows three shaded regions representing different loss limits: A (between 100 and 104.08 kHz, loss up to +5 dB), B (between 104.08 and 107.7 kHz, loss up to +2 dB), and C (below 68 kHz, loss down to -2 dB). A small circle with an 'x' is marked at 84 kHz on the 0 dB line. The text 'CCITT-36982' is in the bottom right corner.](de6e8b740c69dac308cce9edfec3eff4_img.jpg) + +Figure 1/M.910: Limits for loss/frequency distortion. A graph showing Loss (dB) on the y-axis (from -2 to +5) versus Frequency (f) in kHz on the x-axis (from 68 to 107.7). The graph shows three shaded regions representing different loss limits: A (between 100 and 104.08 kHz, loss up to +5 dB), B (between 104.08 and 107.7 kHz, loss up to +2 dB), and C (below 68 kHz, loss down to -2 dB). A small circle with an 'x' is marked at 84 kHz on the 0 dB line. The text 'CCITT-36982' is in the bottom right corner. + +- A: these limits apply if the group reference pilot (104.08 kHz) is injected at an intermediate point on the link (e.g., the terminal national centre) +- B: these limits apply if the group reference pilot is transmitted throughout the link (e.g., if it is injected by the terminal equipment) +- C: these limits apply if the service channel is provided + +FIGURE 1/M.910 +Limits for loss/frequency distortion + +#### 3.4.3 Group-delay distortion1) + +3.4.3.1 The group-delay distortion of the link should not exceed 45 $\mu\text{s}$ relative to the minimum value within the band of frequencies 68-100 kHz. + +3.4.3.2 If the group-delay distortion exceeds the value given in § 3.4.3.1 above, equalization should be provided as agreed by the two terminal Administrations concerned to bring the group-delay distortion of the link within this value and the results recorded. + +3.4.3.3 Where the group link terminates at the two terminal national centres, the value of the group-delay distortion given in § 3.4.3.1 above should apply between these two centres. + +#### 3.4.4 Level variations + +Irrespective of whether the group link terminates at the two renters' premises concerned, or at the two terminal national centres the link should be checked in accordance with the Recommendation cited in [5] in order to ensure that no faults exist. The following limits should not be exceeded: + +- short-term variations: $\pm 3$ dB, +- long-term variations: $\pm 4$ dB, relative to the nominal value. + +1) This limit can normally be met without overall link equalization for group links consisting of three group sections in tandem using corrected through-group connection equipment. + +#### 3.4.5 *Carrier leak* + +The group link should be subjected to measurement of each carrier leak individually at the receiving terminal in both directions of transmission. + +The objective for the level of any carrier leak, appearing in the frequency band 60-108 kHz is $-40$ dBm0. + +In some cases, however, because of the composition of the link, which will generally involve the use of both old and new types of equipment it may not be possible to achieve this value. + +At all events, no carrier leak in the band 60-108 kHz should exceed $-35$ dBm0. + +*Note* – The attention of users is drawn to the fact that failure to reach the value $-40$ dBm0 might cause difficulties in cases where links are used for data transmission. + +#### 3.4.6 *Impulsive noise* + +For the specification of an impulsive-noise measuring instrument for wideband data transmissions, see Recommendation H.16 (O.72) [6]. No limit value can be given at the present time. + +#### 3.4.7 *Frequency error* + +The frequency error over the group link should not exceed 5 Hz. When this measurement is necessary, it should be made according to bilateral agreement between Administrations. + +#### 3.4.8 *Background noise* + +At the present time it is not possible to specify a limit value for background noise for this class of group link. However, a check of the background noise should be made and recorded at every line-up. + +## **References** + +- [1] CCITT Recommendation *Characteristics of group links for the transmission of wide-spectrum signals*, Vol. III, Rec. H.14, § 2. +- [2] CCITT Recommendation *Bringing international group, supergroup, etc., links into service*, Vol. IV, Rec. M.460. +- [3] *Ibid.*, § 7.2. +- [4] *Ibid.*, Table 2/M.460. +- [5] *Ibid.*, § 8. +- [6] CCITT Recommendation *Characteristics of an impulsive-noise measuring instrument for wideband data transmission*, Vol. III, Rec. H.16. \ No newline at end of file